Changing the way we login and store keys

Instead of having another module just to write and load the key, we can move the function to the __main__.py file.
Instead of doing "try ... except" blocks, we do the following:

Check if the token is passed as an argument:

If it is, write the token into the key file (this will overwrite an older token)
If it is not, check if there is a key file
If it can't find the token, ask the user for it

This way, you can overwrite the token either changing or deleting the key file. Maybe we should check if the token is valid or ask for confirmation before erasing the previous one, so the user doesn't accidently delete a valid token.

Create instances of berserk.TokenSession(), berserk.Client() and berkserk.Board()

Call barserk.Client.account.get()

This is the first time we actually connect to Lichess. It is inside a try... exception, and we catch the specific exception that the token is not invalid, and we inform the user that this is specifically the problem.
There might be a differente exception raised if Lichess is offline, but I couldn't find it.
I also think we should look for other errors, like lacking of permissions, so we can guide the user on how to fix the issue. (There might be an api call to check permissions).
If everything is fine, we get to the "Login Menu".
I'm already working on another version of the menu ( #5 ).

I need some sleep so I'm going to merge this tommorow, but for now, Github says that there is some conflicts in your __main__.py file, and it links to the following piece of code:
# Gets your account data, e.g ["id"], ["username"]
    try:
<<<<<<< master
        account_data = client.account.get()
        player_id = account_data["id"]

    except berserk.exceptions.ResponseError as e:
        print("Error ", e, "occurred.")
        print("Unable to connect Lichess")
        print("Check if your token key is right")
        print("Or try again later")
        os._exit(0)

=======

What are the < and = symbols for?

Sorry, my branch is behind. I'll fix this issue and make a new PR.


Update backward incompatible planned changes in 5.5

@Maetveis @MathiasMagnus @Naraenda can you please add this to 5.5.1 release notes and 5.5.0? We will then highlight this in a later annoucement.


Consolidation, cleanup, and spec compliance

This builds upon #42, which makes PeerConnection and MediaStream proper event targets
Add or correct several Flow type annotations. -- Not that it matters right now since Flow isn't turned on for this project, but it would be nice to get there... In the meantime it's good source code documentation.
Rename RTCMediaStream to MediaStream as per spec
Fix #41 by folding RTCPeerConnectionBase into RTCPeerConnection and getUserMediaImpl into getUserMedia
Ensure DeviceEventEmitter handlers are removed when the RTCPeerConnection is closed.

you are the man!

I'm just getting started :)

Look good. I will test it later.

Ping?

Merge!


Could use an example for absolute rust newbies (like myself) on how to use an include_bytes! macro with this library.

//audio
// Get a output stream handle to the default physical sound device
let (_stream, stream_handle) = OutputStream::try_default().unwrap();
// Decode that sound file into a source
let my_slice = std::io::Cursor::new(include_bytes!("../title.mp3").as_ref());
let source = Decoder::new(my_slice).unwrap();
// Play the sound directly on the device
let _sound_result = stream_handle.play_raw(source.convert_samples());

Thanks so much for at least posting this! Was about to implement Seek myself for a slice of bytes, because I couldn't find the appropriate std library struct wrapper 😅

PRs welcome!

And if you are using tokio/async, this example looks like:
async fn emit_sound() {
    let (_stream, stream_handle) = OutputStream::try_default().unwrap();
    let sink = Sink::try_new(&stream_handle).unwrap();
    let my_slice = std::io::Cursor::new(include_bytes!("../assets/click.mp3").as_ref());
    let source = Decoder::new(my_slice).unwrap();
    sink.append(source);
    sink.sleep_until_end();
}


use ovirt host deploy to install cocpit-ovirt

It will need to:

install cocpit and cocpit-ovirt
setup certificates so once you accept the engine's CA you will not need to accept anything else while accessing cockpit
opens the 9090 port in firewall

(did not know we track issues here, why?)

What about dependencies, what are the deps. needed for it? (optional channel of CentOS? EPEL?)
The certificate issue is even more interesting - the host certificate is NOT intended for web browsing. Do we want to ask for another certificate (I sincerely hope not!) or just ensure the signing request DOES ask for web browsing?

@mykaul: deps on CentOS should not be a problem, AFAIK it's an issue just on RHEL. Worth describing'
about cert - yeah, I hope we can use the existing one. Still won't help much to NGN prior to registration in engine:/

why tracking issues here? - well, more convenient, faster, community friendly than bugzilla. So why not. Even though I was kind of expecting the mirroring from gerrit git is working..which is not:) But then it will make some sort of sense as you would have a read-only up-to-date sources visible here(synced from gerrit which has better code-review facilities) and issue tracker here

I think deps on CentOS are an issue, as you need to enable (AFAIR), the 'Extras' channel.


Hiding subscriptions

Is there a way to hide subscriptions that have no unread posts?

👍

Yes, please...

I really want to switch away from browser-based RSS for various reasons, and this was looking like a good candidate, but the lack of this feature makes it almost unusable.


Log filling up

When I tail my /var/log/openvpn/int.log file, every two seconds it adds the following entry:
Thu Oct 15 08:07:24 2015 us=130000 read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
Is this happening on yours as well? Wasn't sure if there was a better work around to prevent this. The check currently happens every minute and it takes a full minute for the connection refused to stop so it essentially never ends.
Here is the full text (<IP_ADDRESS> in this example would be my Nagios server):
Thu Oct 15 08:15:21 2015 us=396443 MULTI: multi_create_instance called
Thu Oct 15 08:15:21 2015 us=396513 <IP_ADDRESS>:54134 Re-using SSL/TLS context
Thu Oct 15 08:15:21 2015 us=396534 <IP_ADDRESS>:54134 LZO compression initialized
Thu Oct 15 08:15:21 2015 us=396601 <IP_ADDRESS>:54134 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Oct 15 08:15:21 2015 us=396613 <IP_ADDRESS>:54134 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Thu Oct 15 08:15:21 2015 us=396642 <IP_ADDRESS>:54134 Local Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-server'
Thu Oct 15 08:15:21 2015 us=396650 <IP_ADDRESS>:54134 Expected Remote Options String: 'V4,dev-type tun,link-mtu 1542,tun-mtu 1500,proto UDPv4,comp-lzo,cipher BF-CBC,auth SHA1,keysize 128,key-method 2,tls-client'
Thu Oct 15 08:15:21 2015 us=396665 <IP_ADDRESS>:54134 Local Options hash (VER=V4): '530fdded'
Thu Oct 15 08:15:21 2015 us=396676 <IP_ADDRESS>:54134 Expected Remote Options hash (VER=V4): '41690919'
Thu Oct 15 08:15:21 2015 us=396705 <IP_ADDRESS>:54134 TLS: Initial packet from <IP_ADDRESS>:54134, sid=01000000 00000000
Thu Oct 15 08:15:21 2015 us=396715 <IP_ADDRESS>:54134 TLS Error: reading acknowledgement record from packet
Thu Oct 15 08:15:24 2015 us=199771 read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
Thu Oct 15 08:15:26 2015 us=609427 read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
Thu Oct 15 08:15:29 2015 us=200170 read UDPv4 [ECONNREFUSED]: Connection refused (code=111)

Yes, this behavior might occur: the test works by opening a connection to the openvpn server. If the server logs all connection attempts the log will fill up.
If this is a concern for you please add log rotation or a logging filter.

We already had log rotate enabled, but even with, 67 MB daily logs were
already showing up on reports of relatively large unexpected file changes.
A few options I changed within openvpn config:
mute 5 (suppresses repeated messages) but still produces a lot of entries
ever minute
verb 0 (change verbosity from 4 to 0).
While muting does help, it still produces a lot of entries every minute. I
decided changing verbosity was the best of my options, it isn't my
preferred method but 0 is the only thing to prevent them from filling up.
Since this is a UDP connection, seems like my testing options are limited.
If you have any other solutions or recommendations, I would be open to it.
No matter what, just having this as a monitoring option is much better than
what I had before (which was nothing and complaints when discovered it
wasn't working).

The problem seems to me to be by design: the check actually opens a connection, thus you will have a logging action of the OpenVPN server. There is little the plugin can do here.
Alternatives are:

don't test the availability every two seconds but for example only every 10 seconds
do not use a connection test but a test checking if the process is alive (although that is not nearly as reliable)

However, if you need to test the availability every two seconds (!) please consider to route all OpenVPN logs through a log daemon as rsyslog, and add filter lines to drop all lines which contain the IP address of your monitoring server.
Hope that helps...


make modified raspi-config available in pi-gen stages

In general, it is preferred to make customisations in pi-gen stages using raspy-config in "nonint" mode, e.g. raspi-config nonint do_vnc 0 (see https://github.com/JanLahmann/RasQberry-pi-gen/blob/2a03dbea8da55aa75605693aa0523ace922d7c80/stage5/02-enable-vnc/00-run.sh#L5C33-L5C61)
For that, we need to make the modified version of pi-gen available in our pi-gen stages.

@JanLahmann assign this to me i will pick it up

This is already taken care as part of the build so we can close.


[terra-notification-dialog] Fixed A11y issues

Summary

What was changed:

Removed the 'BeginModalDialog' and 'EndModalDialog' messages from the ModalContent when it is called from the NotificationDialog.
The title was read twice by the screen readers. I've changed the ariaLabel, ariaLabelledBy and ariaDescribedBy to properly read the content of the NotificationDialog.

Why it was changed:
To Fix Accessibility issues as discussed with UX
Testing

This change was tested using:

[ ] WDIO
[x] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9855

Thank you for contributing to Terra.
@cerner/terra

+1


Telemetry fails to restart

This morning my cluster had nothing in grafana, traced it back to telemetry job.
Logs from mixer:
 Mixer started with
MaxMessageSize: 1048576
MaxConcurrentStreams: 1024
APIWorkerPoolSize: 1024
AdapterWorkerPoolSize: 1024
APIPort: 9091
APIAddress: unix:///sock/mixer.socket
MonitoringPort: 9093
EnableProfiling: true
SingleThreaded: false
NumCheckCacheEntries: 1500000
ConfigStoreURL: k8s://
ConfigDefaultNamespace: istio-system
LoggingOptions: log.Options{OutputPaths:[]string{"stdout"}, ErrorOutputPaths:[]string{"stderr"}, RotateOutputPath:"", RotationMaxSize:104857600, RotationMaxAge:30, RotationMaxBackups:1000, JSONEncoding:false, LogGrpc:true, outputLevels:"default:info", logCallers:"", stackTraceLevels:"default:none"}
TracingOptions: tracing.Options{ZipkinURL:"http://zipkin:9411/api/v1/spans", JaegerURL:"", LogTraceSpans:false}
IntrospectionOptions: ctrlz.Options{Port:0x2694, Address:"<IP_ADDRESS>"}
Unable to initialize Mixer: unable to listen: listen unix /sock/mixer.socket: bind: address already in use

kublectl describe:
 Mixer started with
MaxMessageSize: 1048576
MaxConcurrentStreams: 1024
APIWorkerPoolSize: 1024
AdapterWorkerPoolSize: 1024
APIPort: 9091
APIAddress: unix:///sock/mixer.socket
MonitoringPort: 9093
EnableProfiling: true
SingleThreaded: false
NumCheckCacheEntries: 1500000
ConfigStoreURL: k8s://
ConfigDefaultNamespace: istio-system
LoggingOptions: log.Options{OutputPaths:[]string{"stdout"}, ErrorOutputPaths:[]string{"stderr"}, RotateOutputPath:"", RotationMaxSize:104857600, RotationMaxAge:30, RotationMaxBackups:1000, JSONEncoding:false, LogGrpc:true, outputLevels:"default:info", logCallers:"", stackTraceLevels:"default:none"}
TracingOptions: tracing.Options{ZipkinURL:"http://zipkin:9411/api/v1/spans", JaegerURL:"", LogTraceSpans:false}
IntrospectionOptions: ctrlz.Options{Port:0x2694, Address:"<IP_ADDRESS>"}
Unable to initialize Mixer: unable to listen: listen unix /sock/mixer.socket: bind: address already in use

Noticed in the console an 'out of memory' error - so it is possible mixer container crashed, and k8s retried to restart the container in same pod and kept failing.

Thanks for catching this. We should set all istio pods with sidecars to have "restartPolicy=Never".

Marking as P0 since it affects stability of the system, if policy server has the same problem it can bring down everything.

Well, we should clean up the socket - restartPolicy is not the root cause here.

There are two issues:

OOMing Mixer -- why is that happening?
Partial Mixer pod restarts. There is no reason to keep the proxy running if mixer crashes.

If a process OOMs, good luck cleaning up dangling resources... Restarting pod is a safe procedure, since the whole sandbox goes away.

@costinm can you attach logs? what configuration is mixer running with?

I don't believe that "restartPolicy: Never" is valid for Deployments. We need a different approach.

Standard mixer - logs are gone after container restart. It is a load test cluster - but same config has ran for 1 month with 0.8.
So far crashes of pilot or mixer didn't cause the pod to get stuck - it's just a uds socket that needs to be remove (or reverted to tcp - do we have numbers on performance delta ? ). We still want istio components to work on other enviroments - like VMs - where we can't do the equivalent of restarting a pod.
Safest approach IMO is just use tcp socket for 1.0, and cleanup and test more for 1.1

This is a big problem for production users, too. Any application deployment with sidecars can get into this stuck state...

A standard liveness check is sufficient to fix this (and probably other issues). But we do need to check that proxy correctly handles retries and load balancing between policy pods.

Pretty sure no app deployment get stuck in this - it is a problem with the unix socket, and apps don't currently use that.
Just reverting to TCP socket or cleaning the unix socket will fix this - and will work for VMs too.

@kyessenov either you can revert to TCP or add liveness/readiness.
Reverting to TCP is a simpler fix.
That said, Mixer not using liveness / readiness is already an issue, so that should be fixed in 1.0 anyway.

I will add tcp back with uds option.
Can you use build from #7110 , I expect that I won’t get stuck.
More importantly though need to figure out why it is oom.

@costinm can you provide a profile of mixer when it OOMs? There is a pprof available. Let's focus on that, as UDS vs TCP is a triviality here.

Yes, please focus on load testing and making sure it doesn't crash.
You can use test/helm directory to reproduce - or fortio in any setup you
want, I'm running the cluster with around 3000 qps.
Last time it crashed memory was 20G - and I doubt pprof would respond, but
maybe you can catch it earlier.
It is a clear regression and it's far more urgent than the restart issue.
On Fri, Jul 13, 2018 at 6:09 PM Kuat<EMAIL_ADDRESS>wrote:

@costinm https://github.com/costinm can you provide a profile of mixer
when it OOMs? There is a pprof available. Let's focus on that, as UDS vs
TCP is a triviality here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/7050#issuecomment-404987787, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6gSpPqoRcL2p8cSH0MXExOsEPuF4ks5uGUS5gaJpZM4VNap7
.

You can check 'weekly10' cluster under istio-testing - that's where I run
the load tests.
On Fri, Jul 13, 2018 at 6:15 PM Costin Manolache<EMAIL_ADDRESS>wrote:

Yes, please focus on load testing and making sure it doesn't crash.
You can use test/helm directory to reproduce - or fortio in any setup you
want, I'm running the cluster with around 3000 qps.
Last time it crashed memory was 20G - and I doubt pprof would respond, but
maybe you can catch it earlier.
It is a clear regression and it's far more urgent than the restart issue.
On Fri, Jul 13, 2018 at 6:09 PM Kuat<EMAIL_ADDRESS>wrote:

@costinm https://github.com/costinm can you provide a profile of mixer
when it OOMs? There is a pprof available. Let's focus on that, as UDS vs
TCP is a triviality here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/7050#issuecomment-404987787, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFI6gSpPqoRcL2p8cSH0MXExOsEPuF4ks5uGUS5gaJpZM4VNap7
.

closing, as resolved in UDS fix #7110.


sizeChanged() method removed?

The TreeComponent.sizeChanged() method was recently removed by https://github.com/500tech/angular-tree-component/commit/f86c58366bc8f12af956fa2d7bf346a07e873557.
The docs say I need to call this method when a hidden tree with virtual scroll becomes visible. Is this no longer the case?

I have the same problem. The tree is hidden and looks weird when made visible but i can't call the sizeChanged() method since it's no longer present.

I have the same problem, but I found solution:
this.tree.treeModel.virtualScroll.setViewport(this.tree.treeModel.virtualScroll.viewport);

@adamkleingit could you explain why TreeComponent.sizeChanged() was removed? It's still mentioned in the docs here and here.

this.tree.treeModel.virtualScroll.setViewport(this.tree.treeModel.virtualScroll.viewport);
It cannot work. Is there any workaround?

I must have deleted it by mistake when doing some cleanup.
Will be returned in 6.0.0

Published in 6.0.0


Rewrite relative image URLs to absolute ones

Is it possible to add something like puppeteer to handle Youtube/Twitter contents that requires Javascript?
FYI: https://gist.github.com/MrOrz/fb48f27f0f21846d0df521728fda19ce

article-parser absolutify all  or
https://github.com/ndaidong/article-parser/blob/main/src/utils/linker.js#L109-L128
article-parser will try to find out the best url.
https://github.com/ndaidong/article-parser/blob/main/src/utils/linker.js#L16-L19
@ndaidong Why not the extract(html, url) be exported?

@nick008a if you can extract(html), it will automatically find original URL from meta tags.
As your issue, I see that it's not perfect and developer should be able to pass original URL into extract metho manually.

@SettingDust we just posted in the same time. Yes, that's problem we need to resolve!

@SettingDust I have some ideas:

Expose extractFromHTML as public method

At current extract method, do the checks.

if input is URL:
  extract with URL as normal
else:
  treat first argument as HTML, third parameter (`fetchOptions`) as orginal URL

How do you think?

How about overloads
export function extract(input: { url: string }, options: ParserOptions)
export function extract(input: { html: string }, options: ParserOptions)
export function extract(input: { url?: string, html?: string }, options: ParserOptions)
// @deprecated: the old logical
export function extract(input: string, options: ParserOptions)

@SettingDust that's good idea, except of changing api, we may need to break to new major version.

@SettingDust if we start a new major version, I suggest to:

Rewrite in TypeScript
Use only one argument:

export function extract(input: {
  url: string,
  html: string,
  parserOptions: ParserOptions,
  fetchOptions: FetchOptions
})

So it woud be more flexible for the updates in future.

How about
export function extract(options: {
  url: string,
  html: string,
  parser: ParserOptions,
  fetch: FetchOptions
})

And some maybe helpful https://github.com/SettingDust/article-extractor/tree/main/src

@SettingDust yes, I'm moving to Deno.

URL import is experiment in node. Maybe it will work both platform? Agree deno

@SettingDust still learning, I see many libs are being built for both platforms.

@SettingDust you are developing a completely new variant. Why we don't simple create an organization together, and move this lib to there? With more 700 stars, this lib should not belong to an individual developer. It should be @organization/article-parser.

It's fine

@SettingDust any idea about organization name?

@SettingDust any idea about organization name?

article-parser/article-parser? lul

@SettingDust it should cover more tools, I would like to move all its sibling too there: feed-reader, oembed-parser. And few more extractor tools in future: meta extractor, images extractor, price extractor...

In my own lib. I make it accept custom extractor to extract different metas. And the images and price should extractable with custom extractor. So, maybe "meta-extractor/meta-extractor"?

@SettingDust how about something strange, meaningless, greek style like extractorius or extractus?
In this organization will contain the repos name as x-extractor, and people can install them as @extractus/x-extractor.

@SettingDust I've added you as owner, and testing transfer function.

@nick008a if page HTML does not contain url meta tags, you may need to add them manually (using DOM manipulation).
It expects one of these lines:
<meta property="og:url" content="https://orginal-url.com/category/article/slug">
<meta property="twitter:url" content="https://orginal-url.com/category/article/slug">

@nick008a of course, they must be placed between . It's regular meta tag as you often see at the SEO standard websites.


Dont work!

Dont work!
Dont update UI
Dont fit width!

This gets the award for worst bug description ever. 🏆
either provide way more details or this will just get closed due to lack of details.

@Serjaru We wish you the best in learning how to use this library. Here is a video I watched the first time I used the library.: https://www.youtube.com/watch?v=tLDxMKub5WA Good luck.


Allow to synchronise GTIDs 'OnPosSynced'

We want to keep track of the GTID when a transaction has ended or a table has been updated

btw, need to run gofmt.
@siddontang @bejelith After running this in production for over a year, I think the concept of "forced" saving in OnXXXSynced is often not useful. Because we often have different requirements when to persist position metadata.
https://github.com/siddontang/go-mysql/pull/379
We use SyncedPosition and SyncedGTIDSet to get the gtid or binlog pos that is "processed", and save it with custom position metadata saver periodically.

@taylorchu on #379  i agree with you, but it all depends if u process the statements/rows synchronously or in batches... my idea is to execute the updates in the backend in a transactional way so that i dont endup in half applied transactions at the destination.

Thanks @bejelith

My initial idea was to change the paradigm of OnPosSynced from
OnPosSynced(p mysql.Position, f bool) to OnPosSynced(p mysql.Position, set mysql.GTIDSet, f bool)

I prefer this way even to break the compatibility. But we can provide another better name.
@taylorchu
does this change work for you?

PTAL @GregoryIan

i think OnPosSynced is quite self explanatory, an alternative could be OnTransactionEnd?

@siddontang I changed OnPosSynced, we should be good to go now.. unless u have another name to suggest

Thanks @bejelith
I guess your change is not conflicted with #379, right? if yes, I want to merge both of these two PRs.

Looks like it's sporadic

@siddontang this change is compatible with #379, i think is better to merge  #379 first and eventually i can work on the eventual conflicts.

LGTM now, Thanks @bejelith

@siddontang PTAL


Couchbase support

Hi,
Is there any plan to add couchbase support for feature store?
Or if not, would it be too difficult to base something off of the mongo store library?
Cheers,
Jack

Hello,
I would love to support CouchBase, it's the target. Seems that the Java client is straight forward but at the moment I am pretty busy with my "official" Job. Different strategy. I can work on it in the beginning of december.
I can create a skeletton of project with only method to implements if you are interested. It will look like a lot of ff4j-store-cassandra to be honest.
I am not expert on this DB, if you have any tips or idea for the underlying data model it woud be greate as well.

Cheers for the info - I've actually managed to get a basic working store with couchbase based off the cassandra store :)
I'll try and get it into a fully working state with some tests and submit a PR

Hi,
So I've written adapters for couchbase for the property and feature store (not the event store yet).
It's using spring data repositories - however I'm having some difficulty writing integration tests I think due to the versions that are defined in the ff4j parent pom.
Is this something you'd be interested in as a pull request?
Cheers

Of course I will ! Thank you so much.

@clun I've created a PR here: https://github.com/clun/ff4j/pull/269

Well still on refactoring. Would like to test : Cannot install on Windows10, and docker container even hen started do not show anaything on 8091... and you cannot change the port in the Java driver.
Because I used quite a wide set of DB I would like to say this one looks like not yet production ready right ? Still struggle to make it work, the DB, not the store so far...

You should be able to run something like this:
docker run -d --name db -p 8091-8094:8091-8094 -p 11210:11210 couchbase
And then access: http://localhost:8091/ui/index.html
(You'll then need to set up the cluster, create a bucket and add 2 views that I've documented in the readme).
I'm not able to test on Windows, but on OSX & Linux this works.
I would say couchbase is definitely production ready - we are using the enterprise version as a document store/cache performing thousands of requests per second.

So it turns out there's currently a bug with CouchbaseMock: https://github.com/couchbase/CouchbaseMock/issues/11
If this gets resolved I should be able to use an embedded database for the tests :)

I am totally on it. I contacted the Develper Advocate which is french as well (convenient). Problem seems on my station which already used port as even docker can be accessed on localhost:8091.
To my understading is there added value to create several views in a single bucket ?  I did not use it before before thinking about 1 bucket for each type : feature, properties and audit (not the same lifecycle).
Talk to you soon

Ah cool, let me know if you need any more help with it.
So it can be done with one bucket with 2 views, or different buckets can be passed to the stores (like you say, one for feature, one for property etc) and each have a single view - the user can implement it either way they choose

Could you have a look at the refactoring ? I put the Test as Ignored for now before CouchbaseMock.

Use 2 buckets because you may have different strategies for properties and features (persistance replication)
Reuse the FF4J objects, do not introduce extra document
Simplifications

Just having a look through the refactors - it looks like you've implemented N1QL rather than using the views.
This isn't necessarily a problem, however it will mean that FF4J can't be used on older versions of couchbase where N1QL isn't supported, might be something to bare in mind.


Consider adding pcm-memory option to display ECC Correctable Errors

Having one Intel® Xeon® Processor E5 v3 Family server class system in which mcelog was reporting ECC Correctable Errors, in https://github.com/Chester-Gillon/pcm hacked a quick change which added an option to report the ECC Correctable Errors counter. On the problematic server this showed one memory channel was having continuous ECC Correctable Errors, where the error rate varied according to the workload.
It might be worthwhile adding this as a pull-request for a permanent feature. However, not sure how to test this on all server class processors which support ECC Correctable Errors in the ServerUncoreMemoryMetrics

thanks for sharing your change. I am not sure if this is a right path as I don't see this event in the documentation (of more recent processors). May be using pcm-raw is a better way?
pcm-raw -e imc/config=0x09,name=ECC_CORRECTABLE_ERRORS/
documentation: https://github.com/opcm/pcm/blob/master/PCM_RAW_README.md


Cleanup URL create logging

/kind user-story
User Story
When I created URL, it displayed fmt print messages:
$ odo url create mondayspringbootlocal
componentPort is 8080, localUrl.port is 8080 ✓  URL mondayspringbootlocal created for component: mondayspringboot with exposed port: 54998

To apply the URL configuration changes, please use `odo push`

Acceptance Criteria

[ ] It should not display the fmt logs on console unless absolutely reqd

/kind cleanup

[root@bastion nodejs-ex]# odo url create mondayspringbootlocal
 ✓  URL mondayspringbootlocal created for component: nodejs-nodejs-ex-ybzc

To apply the URL configuration changes, please use `odo push`
[root@bastion nodejs-ex]# odo version
odo v1.2.0 (7f14dab08)

Server: https://api.ocp-test.redhat.com:6443
Kubernetes: v1.14.6+cd3a7d0

I didn't see it with 1.2.0 ,  is it in master branch output? both experiment = true / false has been tried


import {readFile} from 'fs/promises'; ESM syntax fails trying to import from a file

Describe the bug
A page component that imports promisified fs methods like this
<script context="module">
    import {readFile} from 'fs/promises';
</script>

...fails with the error Failed to resolve import "fs/promises" from "index.svelte". Does the file exist?:

Stacktrace
500
Failed to resolve import "fs/promises" from "index.svelte". Does the file exist?

Error: Failed to resolve import "fs/promises" from "index.svelte". Does the file exist?
    at formatError (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:44070:46)
    at TransformContext.error (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:44066:19)
    at normalizeUrl (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:68952:26)
    at async TransformContext.transform (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:69080:57)
    at async Object.transform (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:44268:30)
    at async transformRequest (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:58540:29)
    at async instantiateModule (/app/server/node_modules/vite/dist/node/chunks/dep-e9a16784.js:68145:10)

Information about your SvelteKit Installation:

Diagnostics

The output of npx envinfo --system --npmPackages svelte,@sveltejs/kit,@sveltejs/adapter-node,@sveltejs/adapter-static,@sveltejs/adapter-begin,@sveltejs/adapter-netlify,@sveltejs/adapter-vercel vite --binaries --browsers

  System:
    OS: Linux 5.10 Alpine Linux
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 2.36 GB / 7.77 GB
    Container: Yes
    Shell: 1.31.1 - /bin/ash
  Binaries:
    Node: 14.17.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.13 - /usr/local/bin/npm
  npmPackages:
    @sveltejs/adapter-node: next => 1.0.0-next.24
    @sveltejs/kit: ^1.0.0-next.115 => 1.0.0-next.115
    svelte: ^3.38.2 => 3.38.2

Severity
I can work around this like so:
<script context="module">
    import {promises as fsPromises} from 'fs';
    const {readFile} = fsPromises;
</script>

I've had a follow-up from @GrygrFlzr in Discord that my use-case would be better written as an endpoint rather than a page, but this import failure does still seem like a bug, or at least a limitation which needs to be documented.

And to add to my initial report - this same issue seems to affect endpoints as well.

I've never had any issue using ESM syntax in SvelteKit. I expect there's some usage issue or usage with the library you're using
I notice that the Node 16 docs have an example of using ESM syntax for fs promises: https://nodejs.org/api/fs.html#fs_promise_example
But the Node 14 docs do not: https://nodejs.org/dist/latest-v14.x/docs/api/fs.html#fs_promise_example
If you try on Node 16 does it work? (You can use nvm to switch between versions of Node)

Thanks Ben - I'll try on Node 16 and let you know.

same error with node 16

Can you provide a repo where this code fails in an endpoint?

A repro-repo is probably not necessary. Just a fresh svelte-kit + node v16.3.0 and import fs from 'fs/promises'; console.log(fs) is enough. But for the sake of repro. Here's the repro-repo => https://github.com/mdynnl/svelte-kit-issue-1689

This is surprising. I'm afraid I have no idea what's going on

I'm quite sure this is an issue caused by the fact that Vite uses this package to determine built-in node modules: https://github.com/sindresorhus/builtin-modules
I've opened two issues about this: https://github.com/sindresorhus/builtin-modules/issues/13, https://github.com/vitejs/vite/issues/4037

Thanks for the investigation! I'm going to close this in favor of the builtin-modules and vite issues.


06A Construct ZCTA pairs by state

The output only has the values of OZCTA, DZCTA, olat, olong, dlat, dlong. There are no values for the travel time and distance.

You will have to use the ZCTA points file ZCTA PWS for whole US (specifically, this file: ZCTA_Pop_weighted_Centroid_2010_Snap_state). The selected 200 zctas don't have a field for state name.


[travis] Get tested PHP version from Travis CI

I rewrite PR #1255
Badge for Symfony 2.8.0

Badge for Symfony 4.0.0

Attention
Testing Yii on HHVM starts, but fails and this affects the result.

And in .travis.yml #1258 badge it is not visible:

Warnings

:warning:

This PR modified helper functions in lib/ but not accompanying tests. That's okay so long as it's refactoring existing code.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @peter-gribanov!

:book:

We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS

summary table

Build failed because to exceeding GitHub limit.

Just a heads up that the test failure is a timeout in this badge request. It's not related to Github.
    gets the package version of yii
      1)
	[ GET http://localhost:1111/travis/php-tested/yiisoft/yii.json ]

As I wrote here, I appreciate the work you put into this. This badge is different from the ones you added in #1258 or #1372. However this makes a lot of requests so it's many times more expensive, and in my estimation the slight difference in the result isn't worth all the extra overhead. If there is demand for this badge from a lot of other people I'm open to reconsidering. I'm also open to adding Composer if you'd like.


How to get the permission to check detail build error logs?

Question: After submitting a PR, I got "continuous-integration/drone/pr — Build is failing" error. But I don't have the permission to check the details of the error. How to get the permission to check detail build error logs?
Related Issues:

Have you tried to connect with Github account?

@shouhong , We have confirmed that you can log into the Drone CI with your Github account and view the CI error report. I will close this issue, thanks.


JWE Initialization Vector missing or incorrect type

Environment

Operating System: Darwin
Node Version:     v18.14.0
Nuxt Version:     3.3.3
Nitro Version:    2.3.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      runtimeConfig, typescript, modules, imports, css, components, auth, vite, sourcemap
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
Minimal reproduction: https://github.com/LubosAngus/nuxt-auth-bug-reproduction
Describe the bug
After authorization, I store accessToken and refreshToken on jwt, based on this example https://authjs.dev/guides/basics/refresh-token-rotation.
I found a pattern, whenever data in auth session cookie is too large (more than 4kb), it will sign me out after refresh, with an error JWE Initialization Vector missing or incorrect type.
I think it might be related to this: https://next-auth.js.org/configuration/options#description-12
As stated in there:

Cookies in NextAuth.js are chunked by default, meaning that once they reach the 4kb limit, we will create a new cookie with the .{number} suffix and reassemble the cookies in the correct order when parsing / reading them.

In my cookies I see cookie that is split into two, that's when this error is appearing. Maybe it's related.

You can replicate this behaviour in the repository I've included.

If you want to see it working properly, just uncomment a return statement inside /server/api/auth/[...].ts file, it will not throw an error on refresh. There is just one session cookie, because it's smaller than 4kb.

I don't know, if that error is related to auth cookie being separated into chunks, but that's what I've noticed.
Additional context
No response
Logs
No response

@LubosAngus san
I hav the same issue.
Because the joining order of the split files is not correct, I think you should sort it.
next-auth/core/lib/cookie.js:
142:    } else {
143:      Object.keys(_cookies).sort().forEach(name => {
144:        if (name.startsWith(cookieName)) (0, _classPrivateFieldGet3.default)(this, _chunks)[name] = _cookies[name];
145:      })
146:    }

Thanks for reporting this, it is actually a duplicate of #293 - let's continue investigation and resolution over there (:


bloat.py: remove unused imports

Remove unused fileinput and pprint module imports
Signed-off-by: Maxin B. John<EMAIL_ADDRESS>

Thanks for the patch!  This tool is effectively unmaintained.  There might be a newer version in the Chrome tree too, if you're looking.


A short description of the bug

Hello,
I came across a security vulnerability and wanted to know the best way to privately share the details with y'all.  I don't see a Security Policy configured in the Security tab of the repo.
Thanks,
Elton

Hello Elton,
Could you please forward the security vulnerability details with the core
dev team? Particularly with Ryan Holstein and myself.
Our emails are:

@.***
@.***

Thank you.
Em seg., 27 de jun. de 2022 às 18:11, eltronn @.***>
escreveu:

Hello,
I came across a security vulnerability and wanted to know the best way to
privately share the details with y'all. I don't see a Security Policy
configured in the Security tab of the repo.
Thanks,
Elton
—
Reply to this email directly, view it on GitHub
https://github.com/datahub-project/datahub/issues/5263, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4L37V4U6HLPVBF24AGVWDVRHOCPANCNFSM5Z7BOSDQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi @eltronn!
Apologies for the confusion, looks like there's some interesting email masking happening with Pedro's message. Please feel free to send the vulnerability details to<EMAIL_ADDRESS>


[FLINK-26407][end-to-end-tests] Increase timeouts for MetricsAvailabi…

https://issues.apache.org/jira/browse/FLINK-26407
There was a fairly low 5s timeout for starting up Flink cluster, which could have been easily exhausted on CI. This increases  overall deadline for the test to 10m.

Test failure unrelated to the change: FLINK-26387
I'm going to create backports for this PR


Made Phaser.Text create a new object for this.style

... instead of using the same reference for style options object.
This helps when user is using options hierarchies for instantiating game objects.

I can't merge because it's the wrong branch, but it's a good idea so have merged locally.


Fix several typos

Hey! Thanks for creating the PR and cleaning things up for us.
A lot of those typos were actually me, so that's a bit embarrassing. ^-^'


How to opt out of Runme Cloud

I've been experimenting with Runme in VS Code, and I really love the set of capabilities.
But I'm a bit puzzled how and why it's uploading command output to Runme Cloud. At this time, I'm happy for output to just go straight to my disk. More importantly, I have not been able to find an option anywhere to opt out of my command output being uploaded to Runme Cloud. I'm sure I'm just missing something.
Could someone advise?
Thank you.

Hi @mt-ronkorving, thanks for filing the ticket!
In the most recent release, to disable the login prompt you can toggle following setting (runme.app.loginPrompt):

This will prevent the prompt from reoccurring. Btw, we are only a few days out from releasing a reworked Runme version where local-mode for Auto-Save is the only option which should solve the problem described altogether.
Please let me know if this helps, @mt-ronkorving.

Thank you, that worked! 🙇


Rust codegen doesn't handle offsets

Hello,
looking at the generated Rust for the car example we see:
/// MessageHeader
#[repr(C,packed)]
#[derive(Default)]
pub struct MessageHeader {
  pub block_length:u16,
  pub template_id:u16,
  pub schema_id:u16,
  pub version:u16,
}

and
/// MessageHeader Decoder entry point
pub fn start_decoding_message_header<'d>(data: &'d [u8]) -> CodecResult<(&'d MessageHeader, ScratchDecoderData<'d>)> {
  let mut scratch = ScratchDecoderData { data: data, pos: 0 };
  let v = scratch.read_type::<MessageHeader>(8)?;
  Ok((v, scratch))
}

Now if we change the schema to contain some padding:
inf@earth:~/build/simple-binary-encoding$ git d
diff --git a/sbe-samples/src/main/resources/common-types.xml b/sbe-samples/src/main/resources/common-types.xml
index fe94289a..cb3caacb 100644
--- a/sbe-samples/src/main/resources/common-types.xml
+++ b/sbe-samples/src/main/resources/common-types.xml
@@ -3,7 +3,7 @@
     <composite name="messageHeader" description="Message identifiers and length of message root.">
         <type name="blockLength" primitiveType="uint16"/>
         <type name="templateId" primitiveType="uint16"/>
-        <type name="schemaId" primitiveType="uint16"/>
+        <type name="schemaId" primitiveType="uint16" offset="8"/>
         <type name="version" primitiveType="uint16"/>
     </composite>
     <composite name="groupSizeEncoding" description="Repeating group dimensions.">

and then regenerate we get:
/// MessageHeader
#[repr(C,packed)]
#[derive(Default)]
pub struct MessageHeader {
  pub block_length:u16,
  pub template_id:u16,
  schema_id_padding_1:[u8;4],
  pub schema_id:u16,
  pub version:u16,
}

which is now correctly 12 bytes large. However, the decoding still tries to read only 8 bytes (ignores the padding):
/// MessageHeader Decoder entry point
pub fn start_decoding_message_header<'d>(data: &'d [u8]) -> CodecResult<(&'d MessageHeader, ScratchDecoderData<'d>)> {
  let mut scratch = ScratchDecoderData { data: data, pos: 0 };
  let v = scratch.read_type::<MessageHeader>(8)?;
  Ok((v, scratch))
}

This might somewhat work by accident if encoding and decoding from rust but will fail if generated from another language.
This is with latest master (0a51bb71). Let me know if that makes sense and or whether you need more info.
Thanks,
Stephan

Rust has been removed from project due to lack of community support.


Configure flask app logger and detail in readme for devs

Changes in this PR

Configure flask app logger and detail in readme for devs

JIRA ticket
https://national-archives.atlassian.net/jira/software/projects/AYR/boards/66?assignee=63b4326678aabbefa9d4400d&selectedIssue=AYR-502
Have verified that the logs come out as expected locally and when running on AWS lambda they come through as expected in cloudwatch logs.

do we need to configure conftest.py for mocking the logging object ?

Spoken offline, can just use pytests inbuilt fixture, caplog. Will add a line about this

do we need to configure conftest.py for mocking the logging object ?

Spoken offline, can just use pytests inbuilt fixture, caplog. Will add a line about this

Done


Client doesn't complete expanded build with over 11TB max size

On Windows 10. I had a 11TB build which I tried to expand using first:
dataserv-client.exe --address <BITCOIN_ADDRESS> build --rebuild
That failed because of a server issue which wasn't responding a couple of days ago. So then I tried this instead:
dataserv-client.exe --store_path <PATH_TO_FOLDER> --max_size <MAX_DATA_SIZE_IN_BYTES> --address <BITCOIN_ADDRESS> build
This failed again when it reached about 67K Height. Below is the traceback from the app.
Traceback (most recent call last):
File "dataserv-client", line 24, in
File "E:\dataserv-client\dataserv_client\cli.py", line 128, in main
File "E:\dataserv-client\dataserv_client\api.py", line 130, in build
File "E:\dataserv-client\dataserv_client\builder.py", line 64, in build
File "E:\dataserv-client\dataserv_client\api.py", line 126, in on_generate_shard
File "E:\dataserv-client\dataserv_client\api.py", line 68, in _url_query
File "C:\Python34\lib\urllib\request.py", line 161, in urlopen
return opener.open(url, data, timeout)
File "C:\Python34\lib\urllib\request.py", line 463, in open
response = self._open(req, data)
File "C:\Python34\lib\urllib\request.py", line 481, in _open
'_open', req)
File "C:\Python34\lib\urllib\request.py", line 441, in _call_chain
result = func(*args)
File "C:\Python34\lib\urllib\request.py", line 1210, in http_open
return self.do_open(http.client.HTTPConnection, req)
File "C:\Python34\lib\urllib\request.py", line 1185, in do_open
r = h.getresponse()
File "C:\Python34\lib\http\client.py", line 1171, in getresponse
response.begin()
File "C:\Python34\lib\http\client.py", line 351, in begin
version, status, reason = self._read_status()
File "C:\Python34\lib\http\client.py", line 321, in _read_status
raise BadStatusLine(line)
http.client.BadStatusLine: ''
Expanding should be easier and faster in my opinion, if we need to scale to 1PB we need to make sure that users can Build and Expand faster than it is currently possible. I have been trying for 3 days to add more storage to my build unsuccessfully. The amount of time it takes to check existing shards is also too long, we should skip that process and get the client to only create new shards for the required expanded storage. Also having to fall back to 0 Height when expanding or rebuilding doesn't sound right as usually I'll be still polling when doing that, so starting from the current build size would be ideal then see the increases as the expansion progresses.

The BadStatusLine bug has already been fixed and will be rolled out in the next version.


Auto save timed out encounter ( https://github.com/lunyx/CasualMeter/pull/68 ).
Auto switch from viewing saved encounter on boss aggro (not sure, whether it need to be configurable).

Added header to paste string

Not sure what to do with long boss names, causing saved encounter description to be clipped by meter window border/scrollbar.
May be put it to the end of string, so that clipping does not affect tracker stats.
Or clip name manually to ~20 symbols.
Or leave it as is now, since the number of bosses with long names is small enough.

I'm thinking we could just make the boss name a tooltip so that it shows up when you mouse over.

May be combination of clipped name and full tooltip? Searching for particular boss in long list only by tooltips is not comfortable.

There's an issue where resetting meter manually after hitting a boss still saves meter using ctrl + del.  Also doesn't work correctly on deso in fihm due to multiple bosses dying.

To fix FIHM tou need only update monster monsters-override.xml to the latest version.


add a link to xml source of current standard name table

In discuss issue 195, Luke @lhmarsden pointed to https://cfconventions.org/Data/cf-standard-names/current/src/cf-standard-name-table.xml as the URL of the xml source for the current version of the standard name table (whatever that version is). If this is a future-proof reliable location for software to refer to, it would be good to add a link to it somewhere on the website. If there is one, I haven't found it.

I imagine that this might be fairly easily solved. Currently, the upper part of the vocabularies web page is

where the links under the upper heading ("... current version ...) go to numbered versions, such as ..../83/...., where the numbers could easily be changed to  ..../current/..... And one could then consider to include links to the numbered versions (actually pointing to the same as current) under each of the heading below. The upper heading that now reads
"Standard Name Table (current version, v83, 17 October 2023)" could then be  changed to read either "Standard Name Table (current version~~, v83,~~ 17 October 2023".
As I have no insight into the workflow for creating and publishing new versions of the standard name table I leave this as a suggestion for others to consider if/how to practically implement (ping @efisher008, @japamment, @sadielbartholomew).

I have now created a PR implementing the idea put forth in the previous comment. Additionally, the PR fixes some typos noted elsewhere: bad link to Rules for updating, and v83 links  pointing to another version.
Test webpages are available here. Comments regarding style and layout are most welcome.
As there has been no comments to the suggestion for about 5 months, and support in the form of a "thumbs up" from @sadielbartholomew I think that maybe this PR can be merged soon to fix typos etc. if there are no comments (except minor changes to the style and layout).
ping @japamment, @efisher008, @JonathanGregory , @sadielbartholomew

Thanks for the PR, @larsbarring. I agree that the change proposed by this issue has been agreed. (Actually, for reference, we have said somewhere that thumbs-up does not count as explicit support for an enhancement. You have to say something to be counted. I think that's a good rule, but this is something we should discuss again when reviewing the rules, as needs to be done.) Also, the errors were reported as defects to be corrected more than three weeks ago, and no-one objected.
I think the PR is fine, except that the KWIK link doesn't work, because actually the KWIK index of the current version is not present in https://cfconventions.org/Data/cf-standard-names/current/build/kwic_index_for_cf_standard_names.html.

Thanks Jonathan,
Regarding counting thumbs-up or not, I have nothing against not counting them. It might even be good, because a thumbs-up is a bit vague as support ( I thought that it would pass for this particular PR, because it is a rather limited change that I would judge as rather uncontroversial).
Good that you spotted the non-working KWIC index!!
Now fixed.

Thanks for your quick KWIC fix, Lars. (That sounds like Dr Seuss speaking.) I will merge it now, which closes this issue.


Revert "Port crawling from WWDP (#578)"

Why / Balance
This crawling mechanic is too broken and bugged for now. Under table crawling just make you invincible to any ranged or melee weapons, except explosions.
:cl:

remove: Removed crawling.

Summary by CodeRabbit
Release Notes

New Features

Enhanced visual feedback for buckling states with updated rotation visualizers.

Removed Features

Eliminated the "Auto Get Up" option from the UI, affecting character recovery mechanics.
Removed the ability to toggle standing state via key bindings.
Discontinued the laying down state for characters, impacting gameplay dynamics.

Bug Fixes

Improved handling of standing and down states, ensuring more consistent gameplay behavior.

These changes aim to streamline user interactions and refine gameplay mechanics.

I think I'll just fix crawling problems later


HWKAPM-760 | HTTP recorder programatic intialization

https://issues.jboss.org/browse/HWKAPM-760

HTTP reporter renamed to recorder
Programmatic initialization of the recorder

@objectiser could you please review?

@objectiser PR updated. Could you please re-review?

@objectiser PR updated

@pavolloffay LGTM :+1:
Thanks for sorting out the checkstyle config on opentracing Java provider.

@objectiser thanks for reviews! At least now we know how to configure it. I have tried adding custom rules to pom.xml but it does not work to mix inline rules and external configuration xml.


[SPARK-31161][WEBUI] Refactor the on-click timeline action in streagming-page.js

What changes were proposed in this pull request?

Refactor streaming-page.js by making on-click timeline action customizable.
Why are the changes needed?

In the current implementation, streaming-page.js is used from Streaming page and Structured Streaming page but the implementation of the on-click timeline action is strongly dependent on Streamng page.
Structured Streaming page doesn't define the on-click action for now but it's better to remove the dependncy for the future.
Originally, I make this change to fix SPARK-31128 but #27883 resolved it.
So, now this is just for refactoring.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Manual tests with following code and confirmed there are no regression and no error in the debug console in Firefox.
For Structured Streaming:
spark.readStream.format("socket").options(Map("host"->"localhost", "port"->"8765")).load.writeStream.format("console").start

And then, visited Structured Streaming page and there were no error in the debug console when I clicked a point in the timeline.
For Spark Streaming:
import org.apache.spark.streaming._
val ssc = new StreamingContext(sc, Seconds(1))
ssc.socketTextStream("localhost", 8765)
dstream.foreachRDD(rdd => rdd.foreach(println))
ssc.start

And then, visited Streaming page and confirmed scrolling down and hilighting work well and there were no error in the debug console when I clicked a point in the timeline.

Build finished. Test PASSed.

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

Test build #119827 has started for PR 27921 at commit 7e591a7.

I'll fix the conflict.

Test build #119828 has started for PR 27921 at commit 96e8c58.

Merged build finished. Test PASSed.

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

Test build #119828 has finished for PR 27921 at commit 96e8c58.

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

Merged build finished. Test PASSed.

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

Test build #119827 has finished for PR 27921 at commit 7e591a7.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

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

Test build #120158 has started for PR 27921 at commit 0a0b4b6.

Merged build finished. Test PASSed.

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

Test build #120158 has finished for PR 27921 at commit 0a0b4b6.

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

Merged build finished. Test PASSed.

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

A late LGTM.
#27883 is merged into 3.0 as well.
@sarutak could you create a PR to cherry-pick this to branch-3.0? (In case there are more upcoming changes to 3.0..)

@gengliangwang Sure. I'll do it.


HDDS-6096. S3 copy object fails for source key with special char

What changes were proposed in this pull request?
S3 copy object fails for source key with special char.  Noticed with =, as in key=value, which is used for Spark SQL partitioned tables.
put-object creates the key with literal =:
Running command 'aws s3api --endpoint-url http://s3g:9878 put-object --bucket bucket-ozone-test-9766114691 --key ozone-test-7644827888/copyobject/key=value/f1 --body /tmp/copyfile'
...
Running command 'aws s3api --endpoint-url http://s3g:9878 list-objects --bucket bucket-ozone-test-9766114691 --prefix ozone-test-7644827888/copyobject/key=value/'
${output} = {
    "Contents": [
        {
            "LastModified": "2021-12-11T14:19:26.002Z",
            "ETag": "2021-12-11T14:19:26.002Z",
            "StorageClass": "STANDARD",
            "Key": "ozone-test-7644827888/copyobject/key=value/f1",
            "Size": 29
        }
    ]
}

But the source key path for copy-object is passed to S3 Gateway via a HTTP header, which is URL-encoded.  This mismatch results in the following error:
Running command 'aws s3api --endpoint-url http://s3g:9878 copy-object --bucket destbucket-85046 --key ozone-test-7644827888/copyobject/key=value/f1 --copy-source bucket-ozone-test-9766114691/ozone-test-7644827888/copyobject/key=value/f1'
${rc} = 255
${output} =
An error occurred (NoSuchKey) when calling the CopyObject operation: The specified key does not exist
...
<Error>
  NoSuchKey
  <Message>The specified key does not exist</Message>
  <Resource>ozone-test-7644827888/copyobject/key%3Dvalue/f1</Resource>
  <RequestId/>
</Error>

This patch fixes the error by URL-decoding the source key path.
https://issues.apache.org/jira/browse/HDDS-6096
How was this patch tested?
Changed unit and acceptance tests to cover key=value case.
Running command 'aws s3api --endpoint-url http://s3g:9878 copy-object --bucket destbucket-44546 --key ozone-test-2143247000/copyobject/key=value/f1 --copy-source bucket-ozone-test-8252066797/ozone-test-2143247000/copyobject/key=value/f1'
${rc} = 0
${output} = {
    "CopyObjectResult": {
        "LastModified": "2021-12-11T12:21:04.632Z",
        "ETag": "923bc384-0308-4d4a-b7e8-ededf46a4808"
    }
}

CI:
https://github.com/adoroszlai/hadoop-ozone/runs/4492631771

Thank You @adoroszlai for the contribution.

Thanks @bharatviswa504 for the review.


mobile_scanner compile error

/build/mobile_scanner/.transforms/148271336ddf4f705639ca4f24c50f9c/transformed/out/jars/classes.jar!/META-INF/mobile_scanner_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.

We are going to need more information about this compilation error.
What Kotlin version are you using? What version of mobile_scanner are you using?
Can you provide a minimal reproducible sample?


Restructure plans for OSS NA as it's become virtual

Items to review:

Planned co-located event, investigate options available now
Get sense of sponsorship changes and outlay-ed costs.

Done - plans now are...

Co-lo ( https://sched.co/cZMp )
Virtual booth
Engage on Slack channels potentially ( #57 )


Delayed Job triggered immediately

Hi,
I create a job with delay options, but instead of wait for the amount of delay, it triggered immediately just like ignoring the delay options. The strange is, this only happens in our production server. In the dev server, the delay works just fine.
We share same source code and Kue version between production and dev.
jobs.create( 'task1', {test:'123'} )
  .delay( 300000 )
  .save(function( error ) {
    console.log('saved')
})

jobs.process( 'task1', function( job, done ) {
  console.log('processed')
  done()
})

Is anyone ever have this issue?

I am having the same issue. Thing is, its not consistent. Some times delay would work, and some times for the first job (after server lifted) it getting processed immediately.

tianp's problem was a coding issue which resolved in another topic, it may be a race in your app, please debug and provide more info first

Apparently jobs witch were getting processed on the start are earlier job
delayed earlier. Witch came obvious after debugging.
ср, 17 июня 2015 г. в 20:36, Behrad<EMAIL_ADDRESS>
tianp's problem was a coding issue which resolved in another topic, it may
be a race in your app, please debug and provide more info first
—
Reply to this email directly or view it on GitHub
https://github.com/Automattic/kue/issues/639#issuecomment-112871116.

so can we close this now?

Yes.
чт, 18 июня 2015 г. в 19:22, Behrad<EMAIL_ADDRESS>
so can we close this now?
—
Reply to this email directly or view it on GitHub
https://github.com/Automattic/kue/issues/639#issuecomment-113190744.


Unable to remove the border/outline thing from a canvas created by Render.create()

On html side I'm just rendering a div element with id=matter-container
On JS side, i'm using this Render.create method from matter-js
const matterContainer = document.querySelector("#matter-container");
const THICKNESS = 60;
// module aliases
let Engine = Matter.Engine,
  Render = Matter.Render,
  Runner = Matter.Runner,
  Bodies = Matter.Bodies,
  Composite = Matter.Composite,
  Mouse = Matter.Mouse,
  MouseConstraint = Matter.MouseConstraint;
Body = Matter.Body;
Query = Matter.Query;

// create an engine
let engine = Engine.create();

// create a renderer
let render = Render.create({
  element: matterContainer,
  engine: engine,
  options: {
    width: matterContainer.clientWidth,
    height: matterContainer.clientHeight,
    wireframes: false,
    background: "transparent",
  },
});

Already tried extensively with CSS as welll but it doesn't seem to work.

Is this being rendered to the canvas or part of the css? Easy to confirm: just right click the canvas, save as image, open in an art package and look.
Has border? Then it's something added to the Matter world or config. No border? It's your css causing it and 100% nothing to do with Matter.

nope wasn't part of the CSS. definitely something from matter-js default render. I was only rendering a div element in my code, matter injected a canvas element to it, so I tried a bunch of CSS like border, outline, boxShadow and stuff and it was definitely on the canvas element but it didn't work out. Though, I was able to address it with a hack 😆 , since I didn't find any documentation on this or any related issues here:
.canvas-container {
  margin-right: 1px;
}

render.canvas.width = matterContainer.clientWidth - 1;

I'm curious though..


VACMS-9896 poc decoupled concerns

initial pass at splitting out the node/news_story component into "pure" components and a separate file for the wiring to drupal data.
adds a few more stories to media for different image styles
some minor ts housekeeping for storybook compilation

feedback very welcome!
also note the tests for the pure components are not done yet.. (src/components/news_story/index.test.tsx) hitting some type issues this afternoon but my brain is mush. will finish in the morning.

Closed in favor of #67


Heart container using attributes

Minecraft version & Mod Version:
Minecraft: 1.12.2
Forge: <IP_ADDRESS>27
Cyclic: 1.12.2-1.15.16 (changes based on https://github.com/PrinceOfAmber/Cyclic/commit/d49bf8f7f07b991e5e59812340411293488ae625)
Mods that change health:
Botania: r1.10-354
Nutrition: 1.12.2-3.4.0
ScalingHealth: 1.12-1.3.18-101
solcarrot: 1.12.2-1.3.3
Supporting mods in test profile:
AppleCore: mc1.12.2-3.1.3
Baubles: 1.12-1.5.2
CraftTweaker2: 1.12-4.1.9
Just Enough Items: 1.12.2-<IP_ADDRESS>
SilentLib: 1.12-2.2.18-100
Single player or Server:
Both are affected
Describe problem (what you were doing / what happened):
Cyclic heart canisters do not stack properly with other mods that modify health.
Especially apparant with Scaling Health, it also has a feature that changes starting health similar to starting heart canisters like Cyclic.
The cause of this is using setBaseValue on the health attribute. This would conflict with mods that either change the base value or base calculations on it in an incompatible way.
In Scaling Health's case it calculates bonus health based on getBaseValue to work out what it's modifier should be to adjust the starting health (starting health - base health + bonus health).
Potential Solutions and Notes
Least disruptive change (the one currently being PR'ed):
Modify the UtilEntity.setMaxHealth and UtilEntity.getMaxHealth to use an AttributeModifier instead of setBaseValue.
Here is a video with these changes
Change to being bonus health insted of max health:
This would involve updating Cyclic's player data store, in addition we should also make the health boost source the heart container itself so that in the future.
This change can be applied after the previous suggested change, if you make use of the same UUID but have it for the heart canisters it will replace it.
This is is not crucial if no plans for other methods to increase in the future, and might not be required if cyclic internally uses just a single attribute modifiers but collects the absolute modifier itself from the sources in the mod and they're all flat changes.
For reference the "operation" part of modifiers, I couldn't find it documented anywhere, but here's what the effect seems to be:
0 - Flat increase (+X)
1 - Additive Percentage increase (+X%)
2 - Multiplicative Percentage increase ((1+X)%)
RESULT = (BASE + SUM(T0_i)) * (1 + SUM(T1_i) * PRODUCT(1 + T2_i)
Related Issues
https://github.com/PrinceOfAmber/Cyclic/issues/614 (Original Issue)
https://github.com/PrinceOfAmber/Cyclic/issues/785 (Duplicate)
https://github.com/PrinceOfAmber/Cyclic/issues/833 (Semi-related, the root cause is similar)
Original

Click to expand
Dear PrinceOfAmber,
This is a minimal change that allows Cyclic's health modifier to be compatible with other mods that also affect health, by making use of attribute modifiers.
The downsides to this change is get/setMaxHealth being a misnomer since it'll be ignoring the health boosts from other mods, so it's really get/setBaseHealthPlusBonusCyclicHealth. In essence it's quite the bandaid fix, but also the least intrusive one.
Idealy there would be an attribute modifier for each source, so if cyclic were to add other health attribute modifiers in the future they would stack properly.
When first assessing potential changes, identified that it would be quite the intrusive change if this were to be changed from maxHealth to being bonusHealthFromHeartCanisters. It would involve making a breaking change to the Cyclic player data, which currently stores the maxHealth. This field would need to be changed, perhaps adding a "version" field to the cyclic player data would be a good way to keep track of the version of the player data, this way you could have the player data be updated by maintaining a method to update old player data in case of such breaking changes in the future.
This pull request is really opening the discussion, very interested to hear about what your thoughts on this are.
Regards,
BlueAgent

Noticed a a similar issue with the Block Reach enchantment as well, it's a similar case to this one and can also be fixed by making use of AttributeModifiers.

This looks really awesome! I have used IAttributeInstance type system for mobs and entities but not for players.
Ill grab this and test it today or tomorrow.   Looks like it should also be compatible with the command and the default config because of the util wrapper :D
https://github.com/PrinceOfAmber/Cyclic/blob/2605b8490eff291a7fa6617dd425681b7da1f15e/src/main/java/com/lothrazar/cyclicmagic/command/CommandHearts.java#L77
https://github.com/PrinceOfAmber/Cyclic/blob/2605b8490eff291a7fa6617dd425681b7da1f15e/src/main/java/com/lothrazar/cyclicmagic/event/EventPlayerData.java#L82

Also the PR description is amazing, very thurough.  If this was a job I would hire you on the spot!

Thanks for reviewing this PR and the nice comments.

Made use of the sethearts command in it which sems to work okay.
Actually, initially targeted the development branch cause it seemed to be a better match with the workflow (features are merged into develop then master), but switched it to the master branch cause I was unsure after taking a look at other PRs which targeted master.

I pretty much only PR into master when i do a release and then link to curse page, and develop is the working copy of future release
(if a PR is just a language file i usually get lazy and let it hit master first)

Also i just tested and this is backwards compatible.  Meaning, i had an old world with a character at 20 hearts, updated to this build and i still have 20 so no loss 💃

What may happen is if someone was previously at 19 hearts, and then eats a heart after the update, it'd give them another 10 hearts, ending up at 29 hearts, but it should reset if they die or exit the end through the portal.


Login routes to uphold's 404 page

Tapping on the login button in the uphold sample app opens chrome and then ends up on a 404 page.
Uphold's website 404's when trying to reach this url https://uphold.com/authorize/e67a4ca1f3654e9cc0c530a717d1ada1e89a61fe?scope=cards:read user:read&state=4ikd1ceuho61qhqnu9n9qglnkr

Hi @alexhidalgo,
the app that you are trying to use is only registered on our sandbox environment, thats why it generates a 404 error when you try to access to that app in our production environment.
Please let me know if you have any more doubts.


Add docs to help Windows users navigate through tricky builds

Hey all.
I noticed there is a lack of documentation on node-gyp so I figured I would try and help out. If this isn't the place for it, please let me know where I can contribute some helpful information!
I am definitely looking for suggestions/guidance on how we can make this better and more informative. This is just some info that I have compiled recently that helps me navigate builds. There may be some stuff I am missing or some solid info to help users better navigate build issues.
Please, let me know what you think!

👍 for putting this together.
There's a link buried in the middle of the On Windows section of README.md:

If the above steps didn't work for you, please visit Microsoft's Node.js Guidelines for Windows for additional tips.

Perhaps the link could be made more prominent, or we could add a Troubleshooting or FAQ section to the readme.

Well, read the README I guess! Thanks!


Current master: A few tests failed on macOS.

I thought this might be interesting to report:
95% tests passed, 8 tests failed out of 158

Total Test time (real) =  28.51 sec

The following tests FAILED:
	 57 - PropertyAttributeTest (Child aborted)
	 58 - PropertyAttributeTest_optimised (Child aborted)
	 59 - PropertyAttributeTest_legacy (Child aborted)
	 60 - PropertyAttributeTest_legacy_optimised (Child aborted)
	 61 - ProtocolExtendedProperties (Child aborted)
	 62 - ProtocolExtendedProperties_optimised (Child aborted)
	149 - category_properties (Child aborted)
	150 - category_properties_optimised (Child aborted)
Errors while running CTest
FAILED: CMakeFiles/test.util
cd /Users/Ingwie/Work/Git/libobjc2/out && /usr/local/Cellar/cmake/3.13.4/bin/ctest --force-new-ctest-process
ninja: build stopped: subcommand failed.
<EMAIL_ADDRESS>~/W/G/l/out $ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.3
BuildVersion:	18D42
<EMAIL_ADDRESS>~/W/G/l/out $ cd ..; git rev-parse HEAD
d015f0160cfeb3097c8d2321c0bfc648c0885047

Hope it helps :)

I haven't tested on macOS for a while, but the current code in clang doesn't support Mach-O platforms for the new ABI, so I'm not totally surprised things are broken - all of the non-_legacy tests are actually running their legacy versions.  category_properties and ProtocolExtendedProperties are expected fails, because the old ABI doesn't support the things that they're testing.
It would be helpful to see a stack trace of PropertyAttributeTest to see where it's failing.

If you can tell me how I can force a stacktrace to be shown, I’d be happy to provide it. :)

Am 13.02.2019 um 10:25 schrieb David Chisnall<EMAIL_ADDRESS>I haven't tested on macOS for a while, but the current code in clang doesn't support Mach-O platforms for the new ABI, so I'm not totally surprised things are broken - all of the non-_legacy tests are actually running their legacy versions. category_properties and ProtocolExtendedProperties are expected fails, because the old ABI doesn't support the things that they're testing.
It would be helpful to see a stack trace of PropertyAttributeTest to see where it's failing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/gnustep/libobjc2/issues/84#issuecomment-463123561, or mute the thread https://github.com/notifications/unsubscribe-auth/ACwnlOo9gRj_Ez1jrQJmyFXf3H8tyF7rks5vM9oagaJpZM4a37P9.

The tests are individual binaries in the Test subdirectory of your build directory.  You can run them in your favourite debugger to get a stack trace - they should fail either by crashing (hopefully not!) or by an assert failing (hopefully).  I think the rpath stuff works on macOS so it will find libobjc.dyld in the build directory, but if not then set the DYLD_LIBRARY_PATH environment variable to the build directory before running the test.

(lldb) r
Process 71324 launched: '/Users/Ingwie/Work/git/libobjc2/out/Test/PropertyAttributeTest' (x86_64)
Assertion failed: (outCount == 1), function main, file ../Test/PropertyAttributeTest.m, line 43.
Process 71324 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
    frame #0: 0x00007fff7e08a23e libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
->  0x7fff7e08a23e <+10>: jae    0x7fff7e08a248            ; <+20>
    0x7fff7e08a240 <+12>: movq   %rax, %rdi
    0x7fff7e08a243 <+15>: jmp    0x7fff7e0843b7            ; cerror_nocancel
    0x7fff7e08a248 <+20>: retq
Target 0: (PropertyAttributeTest) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
  * frame #0: 0x00007fff7e08a23e libsystem_kernel.dylib`__pthread_kill + 10
    frame #1: 0x00007fff7e140c1c libsystem_pthread.dylib`pthread_kill + 285
    frame #2: 0x00007fff7dff31c9 libsystem_c.dylib`abort + 127
    frame #3: 0x00007fff7dfbb868 libsystem_c.dylib`__assert_rtn + 320
    frame #4: 0x0000000100001648 PropertyAttributeTest`main at PropertyAttributeTest.m:43
    frame #5: 0x00007fff7df4aed9 libdyld.dylib`start + 1
    frame #6: 0x00007fff7df4aed9 libdyld.dylib`start + 1

There you go! :)

Thanks.  In frame 4, is the value of outCount 0?  It looks as if we're not seeing class property metadata, which is probably expected with older clang builds.  If you feel like it, I'd be interested in seeing if these go away with a recent clang from homebrew, but it's not very important.

You mean line Clang 7? I have a few LLVMs installed:
<EMAIL_ADDRESS>~/W/g/l/out $ find /usr/local/Cellar/ -name clang | grep "toolchain" | grep "bin/clang" |  xargs -t -I % sh -c '% --version'
sh -c<EMAIL_ADDRESS>--version
clang version 6.0.1 (tags/RELEASE_601/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir<EMAIL_ADDRESS>sh -c /usr/local/Cellar//llvm/7.0.1/Toolchains/LLVM7.0.1.xctoolchain/usr/bin/clang --version
clang version 7.0.1 (tags/RELEASE_701/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir: /usr/local/Cellar//llvm/7.0.1/Toolchains/LLVM7.0.1.xctoolchain/usr/bin
sh -c<EMAIL_ADDRESS>--version
clang version 3.9.1 (tags/RELEASE_391/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir<EMAIL_ADDRESS>sh -c<EMAIL_ADDRESS>--version
clang version 5.0.2 (tags/RELEASE_502/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir<EMAIL_ADDRESS>sh -c<EMAIL_ADDRESS>--version
clang version 4.0.1 (tags/RELEASE_401/final)
Target: x86_64-apple-darwin18.2.0
Thread model: posix
InstalledDir<EMAIL_ADDRESS>

Can you try with clang 8?

Mach-O object files are not supported by the next gen ABI. Closing this.


Update magnitude limits for Martin absolute magnitude calculation in results.py

Update Martin absolute magnitude calculation to use magnitude limits specified in config file (rather than hardcoded values of 16 and 23.0)

I suspect that there was a reason this wasn't done before. I'll need to take a look at it to remember/figure out why.

Ok, so I think the reason that I didn't pass in the config magnitude limits is because absolute_magnitude_martin doesn't actually deal with these limits self-consistently, and I didn't want to make things seem more rigorous than they actually were.  What actually happens in absolute_magnitude_martin is that a new isochrone is created with the same age, metallicity, distnace, but in the SDSS bandpass. Then stars are sampled from that isochrone and their V-band magnitude is calculated using the Jester et al. 2005 equations. The bright and faint magnitude limits are applied to the SDSS g-band magnitude of the stars drawn from the SDSS isochrone. This is not so bad when you are translating from DES g,r to SDSS g,r, but if you are working in DES r,i, then the magnitude limit should clearly be transformed.
Here is the code for reference:
https://github.com/DarkEnergySurvey/ugali/blob/e4f0a62527855dbe202bb48cf50a5edeaa17d189/ugali/isochrone/model.py#L369
The original motivation for doing things this way was the fact that we only had the Jester et al. 2005 transformation to get to V-band, and so we wanted to work in the SDSS frame. We now have transformations directly from DES g,r to V-band using Eqn B.8 of the DES DR2 Paper. So I think that really we should try to clean up the entire Martin magnitude calculation.

Also see #16, #56, #57, #95. I think that probably we should take this opportunity to resolve all these issues at once, but it will take a little thought to do it "right".


Filter f_proofpoint_pps_filter not capturing all events from proofpoint

After setting sc4s up to process proofpoint logs, I noticed that a lot of events were being sent to the osnix index with the sourcetype nix:syslog. This does not seem to happen for all events though. Some of them are going to the correct index (email) and the sourcetype is being set to pps_filter_log or pps_mail_log.
If I change the f_proofpoint_pps_filter by commenting out the line match('^rprt\s' value(MESSAGE) type("pcre")), no more events show up in the osnix index.
That line did capture the events where the message started with rprt but if does not capture events where the message starts with info, note, etc.
Is this correct or should some events be going to the osnix index?

In the case of proofpoint the OS events should come through properly to osnix can you be more specific on proofpoint email events by example that is not being picked up ?

Here are some of the events that look email related to me that are going to the osnix index.
queued-reinject[31146]: 059Ir0XR004181: to=<xxxx@xxxx>, delay=00:00:02, xdelay=00:00:02, mailer=esmtp, tls_verify=OK, pri=2213430, relay=[<IP_ADDRESS>] [<IP_ADDRESS>], dsn=2.0.0, stat=Sent (31g7c1fudu-1 Message accepted for delivery)
host = xxxx source = program:queued-reinject sourcetype = nix:syslog

queued-digest[22281]: 059JNdcO022281: from=<xxxx@xxxx>, size=23049, class=0, nrcpts=1<EMAIL_ADDRESS>proto=SMTP, daemon=MTA, tls_verify=NONE, auth=NONE, relay=xxxx [<IP_ADDRESS>]
host = xxxx source = program:queued-digest sourcetype = nix:syslog

filter_instance1[1306]: warn s=31g7c1yrpa m=1 x=31g7c1yrpa-1 mod=dmarc cmd=run problematic policy str="v=DMARC1; p=none; sp=none; fo=; ri=3600; rua=mailto:xxxx@xxxx,mailto:xxxx@xxxx; ruf=mailto:xxxxx@xxxx,mailto:xxxx@xxx"
host = xxxx source = program:filter_instance1 sourcetype = nix:syslog

filter_instance1[18743]: info s=31g7c1yqhj mod=pdr ttl=60 reply="\"reject rscore=100\""
host = xxxx source = program:filter_instance1 sourcetype = nix:syslog

filter_instance1[18743]: note s=31g7c1yqgt m=1 x=31g7c1yqgt-1 mod=dmarc cmd=run result=pass result_detail= result_record="v=DMARC1; p=quarantine; rua=mailto:xxx@xxxx,mailto:xxx@xxxx,mailto:xxxx@xxxx; ruf=mailto:xxxx@xxxx; fo=1; pct=40; rf=afrf"
host = xxxx source = program:filter_instance1 sourcetype = nix:syslog

Previously released failed to update issue


[Extensibility Request] Page 9207 "Sales Analysis Matrix" - protected vars (BaseApp_20.1)

Please make some variables as protected: AnalysisColumn, AnalysisReportMgt
Page 9207 "Sales Analysis Matrix"
    var
-       AnalysisColumn: Record "Analysis Column";
        AnalysisColumn2: Record "Analysis Column";
-       AnalysisReportMgt: Codeunit "Analysis Report Management";
        MatrixMgt: Codeunit "Matrix Management";
        MatrixColumnCaptions: array[32] of Text[1024];
        i: Integer;
        MatrixData: array[32] of Decimal;
        MatrixRounding: array[32] of Enum "Analysis Rounding Factor";
        FirstLineNo: Integer;
        LastLineNo: Integer;
        CachedContainsError: array[32] of Boolean;
        ...

+   protected var
+       AnalysisColumn: Record "Analysis Column";
+       AnalysisReportMgt: Codeunit "Analysis Report Management";

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 41095.


AMBARI-23219 - Set mariadb the default database for Hive on Amazon Linux 2 distribution

What changes were proposed in this pull request?
Mysql is not available in the amzn2-core.repo used by Amazon Linux 2 2017.12. However it is the default database dependency for Hive. Amazon Linux 2 alias set to redhat7 because in this case mariadb will be installed instead of Mysql.
How was this patch tested?
Manual testing using Virtual Box image: https://cdn.amazonlinux.com/os-images/2<IP_ADDRESS>71212.2/virtualbox/

Install ambari server and agent via yum.
Replace the value 'amazon6' to 'redhat7' in the os_family.json files for key 'amazon2017'
Run ambari server setup -s
Reset ambari agent
Run ambari server and deploy a cluster containing Hive.
Run Hive service check.

Please review:
@aonishuk @swagle

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1140/
Test FAILed.
Test FAILured.


Updated readme

Some people (including me) can't use the RPC because they don't have a lockfile. I updated this readme because I figured out that the lockfile only exists when Valorant is running so on first time use you need to start Valorant and then the RPC

or edit readme to ✨important!✨ Please run the valorant-rpc.exe after running the valorant.

Well, that's not really true? You can run valorant-rpc and it will run Valorant and wait for lockfile... So that's useless to add.


Rework crypto_hash_* bindings

If underlying call fails, throw.  Since failure is rare, and there's usually nothing the caller can do about it, I think an exception is better than a return value.  This is a backwards-incompatible change, unfortunately.
Reuse state buffer instead of making a copy.  The existing bindings made a copy of the state buffer on every update().  Not sure why.
Add tests for the init/update/final mode of operation.  There weren't any tests for the init/update/final mode of operation and I believe it wasn't working correctly (#141).  Things seem to work after these changes, but I didn't actually track down the bug in the original code.

Thank you for the pull request. I've merged all the changes except the exception handling. It's a great idea, but for consistency it needs to be implemented for all exported functions.
I'm in the process of porting all the tests from Libsodium itself. Once I finish that i will migrate the rest of the biding to "throw"model you suggest. thanks again!

Sounds good, thanks!


Waiting for another flutter command to release the startup lock...

Waiting for another flutter command to release the startup lock...
i try it. clear. flutter/bin/cache lockfile
reboot android studio
pls.help me

Please refer to this
https://stackoverflow.com/questions/51679269/waiting-for-another-flutter-command-to-release-the-startup-lock

Please refer to this
https://stackoverflow.com/questions/51679269/waiting-for-another-flutter-command-to-release-the-startup-lock

hello, Executing:xxx/adb/macosx/x86_64/adb devices -l
flutter: ProcessException: Permission denied
how to set file chmod u+x ,pls help me.

hello, Executing:xxx/adb/macosx/x86_64/adb devices -l
flutter: ProcessException: Permission denied
how to set file chmod u+x ,pls help me.

@chongbo2013
I believe @Abhishek01039  pointed you in the right direction
but if  you believe this is a bug with flutter
please provide your flutter doctor -v and  your flutter run -v

@chongbo2013
I believe @Abhishek01039  pointed you in the right direction
but if  you believe this is a bug with flutter
please provide your flutter doctor -v and  your flutter run -v


Deployment: Adds a routing option

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 58.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
2364

Relevant Lines:
4041

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.4%) to 58.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.4%

Covered Lines:
2364

Relevant Lines:
4041

💛  - Coveralls


Feat: publish pack npm

Dear all, we're pleased to announce that the library is now available for use 🥳🎉🚀

We'll address the Node version issue causing errors during the GitHub build shortly.

CI / Build, lint, and test on Node 10.x and ubuntu-latest
CI / Build, lint, and test on Node 12.x and ubuntu-latest
CI / Build, lint, and test on Node 14.x and ubuntu-latest


[BUG] Incompatibility with other tools

Describe the bug
Dexios is not compatable with other xchacha applications like hat.sh and picocrypt
To Reproduce
Encrypt a file with dexios and attempt to decrypt it with the other applications
Expected behavior
It should be cross-compatable as they use the same scheme
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Version: 8.8.1

I have a question if you dont mind.
My question is this; where does this issue come from? Is it a lack of documentation of a "standardization" for xchacha, are these developers doing it on purpose; or are they just not very good implementations of the algo? If you could point me in the right direction and provide some sources for me to read up on like blog posts wiki pages etc that'd be greatly appreciated.

XChaCha20 is just a cipher. There is much more to an encryption tool than just a cipher -- there needs to be key derivation and authentication, just to mention a few. Each tool uses its own set of algorithms outside of XChaCha20 and store values in their own format. XChaCha20 is standardized, but these individual header formats are not. No, developers don't intentionally try to break things. No, just because tools are not cross-compatible doesn't mean they are bad. No, there is not a lack of documentation, everything is well defined and standardized in the form of RFCs. So the "issue" is that each tool uses its own format that isn't compatible with other tools, although the algorithms used themselves are standardized.

Thanks that's incredibly informative and explains it perfectly

@brxken128 Of course, glad to help when I can! Thanks for the donation :)


Markdown inclusion

Related to #44, the following still need to be finalized:

[x] Can you make images links?
[x] Can code blocks be assigned a code type?
[ ] Is there a way to get sphinx to not strip white-space from the right?

Additionally, it would be nice to render reStructuredText and Markdown in command descriptions and help messages:

[x] reStructuredText
[x] Markdown

This would require an additional directive option (:renderHelp: reStructuredText or :renderHelp:Markdown maybe).

Progress on this can be tracked in the feature/implement44 branch.

There's no way to not strip white-space, this is done inside docutils.


:wrench: :pencil: Minor docs restruct/additions

Codecov Report

Merging #150 (34bc891) into master (98ca022) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #150   +/-   ##
=======================================
  Coverage   89.51%   89.51%
=======================================
  Files          11       11
  Lines        1192     1192
=======================================
  Hits         1067     1067
  Misses        125      125

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 98ca022...34bc891. Read the comment docs.


Export directly to *.jars

PAX is currently only able to export Curseforge-compatible modpacks with the manifest.json. Exporting to a .zip that contains the *.jars directly would also be very nice.

This will probably cause licensing issues because of distribution. There would have to be proper credits for each individual mod.

Hm. You mean proper credits as in a modlist.txt,or proper credits as lookup the license on how each mod can/should be distributed? How does Curseforge handle this with server packs then?
Imo for now I would just offload that responsibility to the users themselves, since they are the ones distributing the mods.

I agree that offload it to the authors is the best option.
As far as I know, CurseForge is including that in their ToS. The serverpack is hosted on CurseForge. Therefor you are only allowed to include CurseForge hosted mods in it which solves the licensing problem.

Exporting the *.jars to a folder without a .zip would be useful too.


Panics when testing files

oxc_cli lint all .

crashes with such messages
thread 'main' panicked at 'byte index 21 is not a char boundary; it is inside '\u{ae3a6}' (bytes 18..22) of `  static async * #򮎦W__NJ(value) {`', crates/oxc_diagnostics/src/graphic_reporter.rs:599:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error', crates/oxc_cli/src/lint/runner.rs:171:70

Broken files - Broken_138.zip

Thank you for trying out oxc! It's probably a unicode line ending \u{2028} or \u{2029} in one of the TypeScript files. Real code don't use unicode line endings so I neglected them 😅
One of the source code lookup is broken:
https://github.com/Boshen/oxc/blob/main/crates/oxc_linter/src/disable_directives.rs#L96

I tested the latest release (v0.0.4) and it all passed without panics.
npx oxidation-compiler@latest lint .

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error', crates/oxc_cli/src/lint/runner.rs:171:70

thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', crates/oxc_parser/src/lib.rs:228:44

Command oxc_cli lint -A all a.js --fix
Broken_355.zip

@qarmin Can you try the latest version  (v0.0.5) npx oxidation-compiler@latest lint .


Add a Solve Exercise page underneath the Tutorial lesson page

The route must be /html/lesson/{ID}/exercitii/{exerciseID}

Done!


IMPALA-12288: Add BUILD_WITH_NO_TESTS option to remove test targets

This patch adds a new option 'BUILD_WITH_NO_TESTS' to tell CMake not to generate test targets. The option is set ON when building impala using the command 'buildall.sh -notests'. This should be useful for a packing build because cpack build all targets prior to this change.
Testing:

Ran 'buildall.sh -release -package' with and without '-notests' flag and verified generated executables.

Change-Id: I575ce76176c9f6a05fd2db0f420ebe6926d0272a

Hi @zhangyifan27, thanks for your contribution! We don't use pull requests in Apache Impala, we use Gerrit instead: https://gerrit.cloudera.org/. https://cwiki.apache.org/confluence/display/IMPALA/Using+Gerrit+to+submit+and+review+patches has a walkthrough for uploading patches for review.
Thanks, Michael.


Add/edit CI jobs

PRB and master push.
They might already exist but point to spikes.

:raised_hands: