[ZEPPELIN-4331] Use latest version of Java driver for Cassandra

What is this PR for?
This change will allow to get access to latest fixes & improvements implemented in the
Datastax Java driver for Cassandra.
What type of PR is it?
Improvement
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-4331

How should this be tested?

Automated build: https://travis-ci.org/alexott/zeppelin/builds/585461796
Manually tested CQL commands

@doanduyhai would you mind to review this?

Looks good to me. Do not forget to modify documentation to update Java driver version there too

Good point, will push update slightly later
On Mon, 16 Sep 2019, 13:31 DuyHai DOAN<EMAIL_ADDRESS>wrote:

Looks good to me. Do not forget to modify documentation to update Java
driver version there too
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/zeppelin/pull/3447?email_source=notifications&email_token=AAAHNBRZK3ED4WLTMSIAJVLQJ54A7A5CNFSM4IW7DLN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Y7JAI#issuecomment-531756161,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHNBWQWE73JDKEED52UULQJ54A7ANCNFSM4IW7DLNQ
.

added changelog entry

LGTM

Thanks @alexott LGTM, will merge if no more comment


Capitalize badge titles

Problem:

The spelling of the badge titles is a bit mixed up. Some of them are capitalized, others are not.

Solution:

Capitalize all the status badges.

Implemented in the following PR:

https://github.com/geniusyield/atlas/pull/58


TypeScript Definitions

Before anything I want to thank you for this awesome library! :+1: :+1:
I've been experimenting with migrating Cycle.js over to TypeScript as well as some of it's drivers and I had the need to write some TypeScript definitions. I was wondering if that is something you would like to have PR'ed for your repo? I have them written here. I'll gladly rename/refactor things if you think it's necessary anywhere.

Thanks! I suppose this would be useful to people, yes. The only thing I'm wondering is if we could somehow make the thing DRYer - so that e.g. adding a tag wouldn't require changing both the source code and the TS definition. I have no experience on working with TS, so do you have any ideas?

I don't currently know of a better way to do this as a separate file, I just started learning/using TypeScript. The only way I know to keep from having to manually changing the TS definition is to write the source in TS as well, even then, the way things everything is dynamically created via an array of strings that might not even work as expected.

Welp, I guess we go with the separate file then. Can you add some kind of a test to make sure the definitions are up to date?

Sure, I'll definitely give that a go :+1:

I wasn't able to test it, but if you're okay with exporting TAG_NAMES from src/index.js I was able to write a short script that generates the definition file. I opened a PR with the possible changes


Fix an error for Style/GuardClause when if clause is empty and correction would not fit on single line

Erroring snippet:
if foo?
else
  raise 'very long and detailed description of the error that makes it too long to fit on one line'
end

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


add missing OCI docker labels

This PR solves #2511 by adding the missing OCI labels dynamically in the CI workflow-file.
Labels have been added as a workflow-variable to keep maintenance efforts low. Whereas possible, dnymic variables have been used.

@pxlfrk The label using env.NOW was not working so we had to remove it. But we are still getting build errors:

We'll have to remove this until a working build is found.


sysfs-gpio: assert WaitForEdge() and Halt() work as expected

Add gpiosmoketest to assert that WaitForEdge() can be unblock by Halt().
Make it live, #322.
Document this in package gpio.

Hi,
quick heads up:
The code snippet below produces the following results (on Pi0w):

Before the go routine with Halt() fires, falling edges are detected reliably (GPIO13 has a button connected)
after the go routine triggers Halt() no further edges are detected, when pushing/releasing the button, but the WaitForEdge call still blocks and thus the for loop never returns

func HaltTest() {
	host.Init()
	pButton := gpioreg.ByName("GPIO13")
	pRed := gpioreg.ByName("GPIO23")
	pGreen := gpioreg.ByName("GPIO24")
	pBlue := gpioreg.ByName("GPIO25")

	out := false

	pButton.In(gpio.PullDown, gpio.FallingEdge)
	//start go routine calling Halt on pButton after some seconds
	go func() {
		pRed.Out(gpio.Low)
		time.Sleep(20 * time.Second)
		pButton.Halt()
		pButton.In(gpio.PullNoChange, gpio.NoEdge)
		pRed.Out(gpio.High) //indicate Halt() fired
	}()

	pGreen.Out(gpio.High) //Indicate loop entry by LED
	for {
		if pButton.WaitForEdge(-1) {
			fmt.Println("Edge detected")
		} else {
			fmt.Println("Edge detection failed, stopping loop")
		}
		if out {
			pBlue.Out(gpio.High)
		} else {
			pBlue.Out(gpio.Low)
		}
		out = !out //toggle
	}
	pButton.In(gpio.PullNoChange, gpio.NoEdge)

	pGreen.Out(gpio.Low) //Indicate loop exit by LED
}

The GPIO out parts (GPIO23,24,25) could be safely ignored, but I kept them, as I mostly test with headless setup and help of LED indicators.
Additionally I noticed, that ones the parent process is suspended and resumed (f.e. with CTRL+Z on Linux bash terminal), the WaitForEdge call always returns false (?intended epoll behavior?).
As mentioned on twitter, toggling the internal pull resistor between PullUp and PullDown could be (mis)used from software side to "force release" a pending WaitForEdge (without an external change of the real GPIO level). Of course this wouldn't make WaitForEdge return false and thus needs an additional check condition (for example to terminate the for loop of the code snippet), but it is the only way I found so far to replace the non-working Halt().

Add up:
The syscall.EpollWait returns an event which has EPOLLERR set beginning from the second call (event[0].Events == 10).
If the value file is opened with unix.O_NONBLOCK in addition to syscall.O_RDWR, the pending EpollWait returns with n==0 after calling Halt().

Ok so I enabled gpiosmoketest to run on the gohci beaglebone worker, and I created https://github.com/google/periph/commits/gpiotest to test this behavior.
It currently fails as expected: https://gist.github.com/gohci-bot/7ef3d25a3cfbb07d58f2393debd54645
I hope I covered most cases there, but this gives a good test bed, making it easy to add more.

Filed #326 for the signal part. Let's focus on normal behavior here, then signals can be looked at afterward

I have done a bunch of tests, to find a way to interrupt epoll_wait if it is called with a timeout argument of -1.
To summarize: It isn't possible (at least not in a clean way)!
Possible solutions

For "endless blocking" (timeout == -1) epoll_wait could be called in a loop with a predefined timeout.
The loop continues calling epoll_wait, as long as the number of returned file descriptors is less than 1 (for a timeout the number of returned fds would be 0 instead of an EINTR, as documented in the man page). The abort condition for this epoll_wait loop would be p.edge == gpio.NoEdge. To get access to this attribute, the loop has to be implemented directly in WaitForEdge of host/sysfs/gpio.go.
The shortcoming of this method is that edges could be missed between successive calls to p.event.Wait (and thus to epoll_wait). Additionally there's a trade-off in responsiveness to setting p.Edge = gpio.NoEdge (and the time till the loop really exits) and CPU load (short timeouts increase CPU load, timeout == 0 would be busy waiting).

The intended way to interrupt epoll_wait (as well as poll/select) is to use a signal. By default every signal interrupts epoll_wait (as already highlighted). A signal filter could be set by using epoll_pwait instead of epoll_wait. In both cases a signal (f.e. USR1) has to be send to the process using the your gpio library. The logic to generate the signal could be placed in haltEdge. Anyways, to me this seems like an ugly solution, as it allows external processes to influence the behavior by sending signals, too.

So from my point of view the best solution would be to implement the looping method.
An example could look like this (periph/host/sysfs/gpio.go):
// WaitForEdge implements gpio.PinIn.
func (p *Pin) WaitForEdge(timeout time.Duration) bool {
	// Run lockless, as the normal use is to call in a busy loop.
	var ms int
	if timeout == -1 {
		ms = -1
	} else {
		ms = int(timeout / time.Millisecond)
	}
	start := time.Now()
	for {
		nr := 0
		var err error = nil
		if timeout == -1 {
			breakoutTimeoutMillis := 100
			for {
				//Note:
				// In contrast to man page, epoll_wait doesn't return EINTR error on timeout.
				// EINTR is only returned for signals (all signals to be more precise, if epoll_pwait isn't used)
				// This means, if p.Event.Wait returns nr == 0, no edge event was detected and we have to call
				// Wait again, unless p.edge has been set to gpio.NoEdge meanwhile.
				// If NoEdge is set, false will be returned, as the 'ms <= 0' condition becomes true.
				//
				// The only other valid solution to interrupt a pending epoll_wait, would be to send a SIGNAL.
				// Both methods dealing with endless timeouts (looping with a "breakoutTimeout" and sending a SIGNAL)
				// have shortcomings. The looping approach could miss edge interrupts between successive calls to
				// p.event.Wait(), the approach based on signals could be interrupted by external processes (which is
				// the case anyways, unless epoll_pwait is used instead of epoll_wait to get fine grained control over
				// valid signals)
				nr, err = p.event.Wait(breakoutTimeoutMillis)
				if nr != 0 || err !=nil || p.edge == gpio.NoEdge {
					break
				}
			}
		} else {
			nr, err = p.event.Wait(ms)
		}

		if err != nil {
			return false
		} else if nr == 1 {
			// TODO(maruel): According to pigpio, the correct way to consume the
			// interrupt is to call Seek().
			return true
		}
		// A signal occurred.
		if timeout != -1 {
			ms = int((timeout - time.Since(start)) / time.Millisecond)
		}
		if ms <= 0 {
			return false
		}
	}
}

Please understand that I can't file a PR, as neither solution seems clean to me and for my own use case I'm still fine with the idea of calling epoll_wait with timeout = -1 and raising pseudo "edge events" by toggling the internal pull resistors from PullUp to PullDown, till epoll_wait returns.
I hope you gonna find a valid fix. The code snippet from above should at least avoid the failing tests, without impacting other functionality.

I think implementing the signal method is better than looping; yes this opens the door to having WaitForEdge() return false spuriously, but it's not a big deal.

Another (promising) solution in the PR

Enabled GPIO smoke test on RPi as part of the continuous testing:
https://github.com/google/periph/commits/4d03182
-> https://gist.github.com/gohci-bot/1a1c1f8ae3f5fc4a79cc564644937b85#file-cmd12-in-10-356s
Code is at:
https://github.com/google/periph/blob/master/cmd/periph-smoketest/gpiosmoketest/gpiosmoketest.go

Any reason not to create another FD with eventfd() and use that to interrupt epoll_wait()? Seems cleaner than using a signal.

I have no idea, I'm not super familiar with linux's events (I'm a Windows guy).


create md-indicator for accessible indicator icons

as discussed here: https://github.com/angular/material2/pull/4665#discussion_r117855187

Closing this since the priority is low enough that we'd never realistically get to it.


Migrate 'Type checking with TypeScript' examples to static API in v7

Yeah, I think we should move the whole page content of https://reactnavigation.org/docs/7.x/static-typescript and basically the tabs will contain the full content of the page.
We should do similar for https://reactnavigation.org/docs/7.x/static-authentication as well.
Then https://reactnavigation.org/docs/7.x/static-combine-with-dynamic can be moved to under "Guides".
The remaining one https://reactnavigation.org/docs/7.x/static-api-reference can be then moved to under the "API references" section and renamed to "Static API reference"
These pages were written before we decided with the tab approach so that's why they are on different pages right now.

Superseded by 6765a7cab51103f8e69441d97426dad96d6d2d3f


Ceremony Zircuit - Active

Contributor: Rezaheydariii
SSH Public key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC0USXS5xZLghrMc3NmmibLn1vZ9aYLirkk911r4bX8+
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

hi... im ready. sorry

hi boss.. im ready. sorry. im here now

im ready... thanks

contribution has been uploaded.
I am done and thank you.

Download the latest contribution:
./download.sh
my cont... is<PHONE_NUMBER>.csrs

ok... ok

Warning: Permanently added 'sftp.ceremony.zircuit.com' (RSA) to the list of known hosts.
Welcome to Zircuit Mainnet Ceremony
Connected to sftp.ceremony.zircuit.com.
sftp> put ./contributions/0000000022.csrs
stat ./contributions/0000000022.csrs: No such file or directory
I have this problem.

I'm doing it again now I understand. thanks boss

@Rezaheydariii This not fair to others who are waiting for the contributing.
If you don't read guideline carefully, please don't engage this ceremony. You wasted a lot time of others.
@zvorcuit IMO we should skip the guys like @Rezaheydariii , pass chance to others who really cares about the ceremony

done done please wait

Please give me another chance...
my server has a problem... limited resources!
sorry for late

I had a question, I can in a new server (when you announced)
When should I participate in this campaign with a new public key?

im ready boss


Profiler: calculate scoped sierra statement weights

This PR extends the raw profiling info structure with a new field scoped_sierra_statement_weights which is basically stack trace and sierra statements weights combined.
The reason why this is necessary is because neither stack trace nor statements weights are informative enough for profiling a large execution trace. Additionally, recursive calls and loops make analysis harder, so in the proposed implementation recursive calls are collapsed and their weights are aggregated.
How is this used: for rendering flamegraph charts.

This change is


feat(choices): allow user select group header

User can now select header of group by option to select all item in this group
#1074 old pull request ref

It would also be nice if the keyboard navigation supported this as well

Hi, we will use it in production. I must complete some task then I will changes this PR.

@Jefiozie thanks for your review. I just push a new commit to create a new directive (ui-select-header-group-selectable) that must be added on ui-select-choices directive with multiple and groups check.
It's my first PR, just say me if I must improve something.
You can find two comment

Don't know why I must do this:
var $select = select[0];
And if it's the good way to find the group:
var group = $select.findGroupByName(element.text(), true);

How can I create a plunker with my repo to show the result? How can I insert my select.js and select.css?
@randdusing I don't know where I can find the code that catch up keyboard event... Can you help me?

I've heard this library is completely dead... so may not be worth investing time into a PR. I'm not exactly sure where the general keyboard handling is, but maybe try to find where DOWN is referenced.

You can use the examples plunkers to fork the default ui-select example. Next copy your local build select.js etc in it and share the url.
The keyboard codes are in the common.js

@Jefiozie here the plunker: http://plnkr.co/edit/Ujr9amwp3hYMHwSgNdMT?p=preview to try it.
For the keyboard, it's a little bit more complicated. Maybe I will try it in an another PR.
Is it ok for you?

Just small request: can we make it optional? I.e. scope: {isEnabled: "<uiSelectHeaderGroupSelectable"}.

@Klinton90 the new plunker with your option: http://plnkr.co/edit/xtJ0SEGneWijtkc06hw5?p=preview.

Many thanks!

@DarkIsDude.. Even, I need this feature in my application. When do you think you can resolve and have a PR ready? Do you have a timeline when will it be ready? Please let me know.
-Prabhu

@DarkIsDude Could you change something to test the build? Place the brackets on line 3195 and place it on line 3203
I cannot reproduce it but it looks a bit off. (but maybe its just me 😄

@kprabhuvel, I work on it when I can, it's not a priority in our team...
I hope it will be ready soon but the build fail and I don't know why... @Jefiozie do you an idea?

@DarkIsDude no I don't know why it does this. Merged other PR yesterday wasn't any problem there.  Looks like something is breaking for Firefox as it doesn't start.

So bad :( ... I just run gulp test on Firefox:
browsers: ['Firefox'],
on line 43 in karma.conf.js
And all pass... I don't know how can I fix it. Someone can help me?

Hi @DarkIsDude could you merge the master in your branch and see if the issue is fixed?
Thanks

@Jefiozie yeah!!! It works. Well done. I'm waiting this PR is merged and after I will work on the keyboard navigation.

Hi @DarkIsDude ,
Could you add a small part on the wiki that this is working from the upcoming version?
LGTM 👍

@Jefiozie did it ;).

Found couple related issues. PR is https://github.com/angular-ui/ui-select/pull/2069
It would be nice if @DarkIsDude  can review my changes in case I broke something.


BACKLOG-23301: Revert bump of jahia.plugin.version

JIRA

https://jira.jahia.org/browse/BACKLOG-23301
Description

Tests
The following are included in this PR

[ ] Unit Tests (Most changes should have unit tests)
[ ] Integration Tests

Checklist

I have considered the following implications of my change:

[ ] Security (in particular for changes to authentication, authorization, data fetching, ...)
[ ] Performance
[ ] Migration
[ ] Code maintainability

Documentation

[ ] Inline documentation
[ ] Internal Documentation (wiki)
[ ] User-facing Documentation

Change already done in https://github.com/Jahia/privateappstore/pull/22, closing this PR


Ideally, we should make all the wasm-bindgen generated code guarded by #[cfg(target_arch = wasm32)] or something like that.
The
[lib]
crate-type = ["cdylib"]

stuff is a little harder. It can be commented out just when running cargo bench, but that is clunky. Ideally that would not be necessary either.

One idea would be to use binaries as the output target rather than cdylib, and wasm-bindgen could presumably perform wasm-gc and keep the binaries small (and strip the main function or something like that)
That would still require you to separate code, however, into a binary and a library as only the library would be available for writing benchmarks and tests.
Overall I think the situation isn't great and this is somewhat of a Cargo issue. Ideally you'd be able to customize the crate-type more aggressively than only by what's written in the Cargo.toml.

I wonder, though, perhaps the project template for wasm could have two crates? One crate, the primary one, is an rlib which is benchmark-able and testable (and using wasm-bindgen). The other, a cdylib, is purely a reexport of the public contents of the rlib (aka pub use other_crate::*). I believe that should still produce a working wasm target and would be relatively low overhead? (maybe a pain to remember to build a different target for wasm, but scripts may be able to automate this)

cc https://github.com/rust-lang/cargo/pull/5367


Offshore wind curve for nl 2016 shows significant increase over the year

This curve is based on measured data.
For NL the installed capacity probably increased during 2016.

@DorinevanderVlies, I'm unclear about this issue:

Is there a problem? If so, what is it?
What kind of action is required? In other words: when can we close this ticket again?

Is there a problem? If so, what is it?

Problem: curve is unrealistic. The peaks in December are nearly twice as high as in January.

What kind of action is required? In other words: when can we close this ticket again?

Can be fixed by:

Correcting the curve for the change in installed capacity
Using a different data source which shows no big fluctuations during the year.


Write debug messages to stderr instead of stdout

First of all, thanks for the formatter, it's great because it preserves comments :tada:
Please write all debug messages to stderr instead of stdout. I'd like to integrate bh format --stdin-mode as a formatter for my editor Neovim using conform.nvim. But I noticed that in stdin-mode, the debug messages are sent to stdout as well as the resulting transaction, messing up my journal file.
Steps to reproduce
Given this journal:
$ cat simple.beancount
1970-01-01 open Assets:Cash
1970-01-01 open Expenses:Etc

2021-12-31 * "me" "chocolate"
  Expenses:Etc                                               3 EUR
  Assets:Cash

When I run run the formatter in stdin-mode, redirecting stdout and stderr to two different files:
$ cat simple.beancount | bh format --stdin-mode > bh.stdout 2> bh.stderr

$ cat bh.stdout
[21:33:31] INFO     Processing in stdin mode                        format.py:71
[21:33:32] INFO     Calculate column width                      formatter.py:646
           INFO     Collecting                                  formatter.py:130
1970-01-01 open Assets:Cash
1970-01-01 open Expenses:Etc

2021-12-31 * "me" "chocolate"
  Expenses:Etc                                               3 EUR
  Assets:Cash
           INFO     done                                           format.py:108

$ cat bh.stderr
$

Hi @varac, thanks for reporting the issue. Yes, you're right, logs should be written to stderr instead of stdout. I've already addressed the problem by #8 and I just released 1.4.1.
Please let me know if this addresses your problems.

Hi @fangpenlin, thank you for the fast fix! I confirm it's working as it should now, and created a PR to include beanhub-cli in the mason registry.


direct link to dataset

Crawling web archive links fails with read timed out (even on multiple retries)
Article `download()` failed with HTTPSConnectionPool(host='web.archive.org', port=443): Read timed out. (read timeout=7) on URL https://web.archive.org/web/20190910020532/https://www.cbc.ca/news/world/gas-explosion-suspected-after-blast-at-belgium-sports-centre-kills-1-1.3736509
Article `download()` failed with HTTPSConnectionPool(host='web.archive.org', port=443): Read timed out. (read timeout=7) on URL https://web.archive.org/web/20190910020459/https://www.cbc.ca/news/canada/toronto/stabbing-scarborough-1.3735718
Article `download()` failed with HTTPSConnectionPool(host='web.archive.org', port=443): Read timed out. (read timeout=7) on URL https://web.archive.org/web/20190910020833/https://www.dailymail.co.uk/wires/reuters/article-3764774/Huge-blast-Somali-capital-clouds-smoke-seen.html
Article `download()` failed with HTTPSConnectionPool(host='web.archive.org', port=443): Read timed out. (read timeout=7) on URL https://web.archive.org/web/20190910020949/https://www.foxnews.com/us/5-people-killed-in-midair-plane-crash-in-alaska-officials-say
Would be great to get a direct link to the complete dataset.
Thanks!

I meet the same situation like this, crawling web archive links fails with read timed out (even on multiple retries).
cloud you provide  a direct link to the complete dataset. Thanks!

Do you solve this issue? I got stuck in this place too.

The same issue, can you provide a link so that we can download the dataset directly?

Hi if you check https://github.com/chrishokamp/dynamic-transformer-ensembles there are some links to download a version of the dataset

There is a link in our readme now.


[Bug]: Changing login texts – An internal error occurred (V3-5jU5z)

Preflight Checklist

[X] I could not find a solution in the documentation, the existing issues or discussions
[X] I have joined the ZITADEL chat

Environment
Self-hosted
Version
2.42.2
Database
PostgreSQL
Database Version
15
Describe the problem caused by this bug
Page: https://domain.com/ui/console/org-settings?id=logintexts
Login Screen / Interface: Registration options
Lang: ru
After form submit I got an error: An internal error occurred (V3-5jU5z)
Logs: empty
Note: all other forms works fine
To reproduce
click, click, save :)
Screenshots
No response
Expected behavior
No response
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

hei @roquie
Unfortunately I couldn't reproduce.
When you are saying all the other forms work that means, for other languages and also other login form texts?

@roquie  I just noticed this also. I click saved and it resorted back to Bulgarian. Did you find a fix?

@roquie
I fixed my issue just now 😆
I was compliling my instance using git from the fork .
git clone  https://github.com/HungryHowies/zitadel.git

Tried something different, I grabbed the source instead.
wget https://github.com/zitadel/zitadel/archive/refs/tags/v2.42.10.tar.gz

Works l great, but I'm not sure  if it's a user error on my part.
Under "POLICY.LOGIN_TEXTS.LOCALE" it has  large text but everything works.  I need to test this more to ensure I didnt screw things up.

Created a summarized issue https://github.com/zitadel/zitadel/issues/8042, will move this into the backlog.


CLOUD-622 change the old web site.

Signed-off-by: yanggang<EMAIL_ADDRESS>/kind cleanup
change the old web site.

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

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1332/commits/bf3c7913f8478f14145742d07feb8f2375933377
image: perconalab/percona-xtradb-cluster-operator:PR-1332-bf3c7913

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-8-0
passed

demand-backup-cloud-8-0
failed

demand-backup-encrypted-with-tls-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-8-0
passed

scaling-proxysql-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1332/commits/da9a8455465fb088bb40b0df0bfc5791e6f35089
image: perconalab/percona-xtradb-cluster-operator:PR-1332-da9a8455

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1332/commits/da9a8455465fb088bb40b0df0bfc5791e6f35089
image: perconalab/percona-xtradb-cluster-operator:PR-1332-da9a8455

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
failure

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1332/commits/3ed925ff9ed6871f9be79bf425fc098eee7685e4
image: perconalab/percona-xtradb-cluster-operator:PR-1332-3ed925ff

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1332/commits/3ed925ff9ed6871f9be79bf425fc098eee7685e4
image: perconalab/percona-xtradb-cluster-operator:PR-1332-3ed925ff

@yanggangtony thank you for contribution


Add files via upload epatt.org

adding east palo alto tutoring and tennis to list of schools - epatt.org

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

@irJERAD Thank you for your patience while waiting for a review and processing your request. Pull request merged.


System.AccessViolationException

Hi
I developed C#.net wrapper for Tesseract4 . first i built leptonica.lib and other dependency .lib. After that, create /clr dll (managed dll) in visual studio 2015 and by solution reference  used that in Wcf service.
now when i call that by one client that work correctly without exception but when call it by several client in one time service thrown following exception at :
outText= api->GetUTF8Text();

System.AccessViolationException was unhandled
HResult=-2147467261
Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

can you help me how fix this bug (I could not find your email) ?

Are you using a different instance of the engine for each request?

For each request i define new Tesseract:
Tesseract tesseract= new Tesseract ();
tesseract.Init(root, language, OcrEngineMode.OEM_LSTM_ONLY, PageSegMode.PSM_AUTO_OSD);
string utf8String= tesseract.GetStringTest(imagePath);

oh, in tesseract.init i've comment api=new tesseract::TessBaseApi(). i uncomment it and test again, problem resolved for 3 parallel request.
Tanks for your comment.


Weird query generated when using Time Series Line Chart with Group By column

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.23.0rc2
Expected results
It should generate a normal and efficient SQL query.
Actual results
Weird SQL query syntax, like below one:

Steps to reproduce
Make a Time Series Line Chart and add any Group BY column, then click View Query.

After hours of researching, I found that overriding the default variable values of BaseEngineSpec in db_engine_specs.py may fix this problem.
For example:
class SqliteEngineSpec(BaseEngineSpec):
    engine = 'sqlite'
    time_secondary_columns = True // add this line
    time_groupby_inline = True // and this one too
    ……

We also observed this issue. Interestingly enough, if you change the 'Series Limit' field from 50 to 0, the SQL syntax will be written normally.
As a short-term solution, we changed the default value for this field to be 0.

It is the expected query if you want to get the time series for the top N dimension members. I agree the default should be to not apply this


Wrong Date Selected.

i have check deeply, a date is correct but  calendarview set on wrong position so please check it

I have this error too!

I have this error too!

Usually this happened when you have added horizontal (left or right) paddings and margins in any of the parent view.

This worked for me. Thanks @ankurgecr

Can someone provide solution here?

same error


Add Rolling Recorder multiple uploads test

Adds a new integration test to rolling recorder that runs and uploads
multiple recordings one after another, to test durability of the code.
Split functions in test_rolling_recorder_upload to accomodate this.

Closing, as this pull request has been superseded by https://github.com/aws-robotics/rosbag-uploader-ros1/pull/141.


[RN] Correctly pass sdkOptions down

Problem solved
Short description of the bug fixed or feature added
Changes made

[ ] Public API changes: list the public API changes made if any
[ ] Internal API changes: explain the internal logic changes

How to test

[ ] Automated tests: link to unit test file
[ ] Manual tests: step by step instructions on how to test

/release-pr


Fix multiplatform compatibility

Even though the builder image was pulling multi-arch images the final binary was being built for amd64 arch only.

In order for this to work, it needs to be built in an Arm machine, which Github currently does not offer.

I have built the docker image locally in my Arm machine in order to make this work!

Merged and tagged as v1.9.
Could you please double check that it still works with chuhlomin/render-template:v1.9?
If so, I'll update the v1 label.

It won’t work if it’s not compiled on Arm I think!
On Sat, 9 Dec 2023 at 07:15, Konstantin Chukhlomin @.***>
wrote:

Merged and tagged as v1.9.
Could you please double check that it still works with
chuhlomin/render-template:v1.9?
If so, I'll update the v1 label.
—
Reply to this email directly, view it on GitHub
https://github.com/chuhlomin/render-template/pull/17#issuecomment-1848239175,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIFOF5Z3DUG3OUOJ4ULE4TYIPXYNAVCNFSM6AAAAABAGQDFB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYGIZTSMJXGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Go supports cross compiling, I fixed it v1.9 version and tested it on ARM:
$ uname -m
aarch64

$ docker run --platform linux/arm/v7 -t -i chuhlomin/render-template:v1.9
::error::failed to render template: template file not found (".kube.yml")


[PLC] [AST] Added HOAS

This contains

an unfinished unpolished undocumented version of the HOAS machinery
a commented out alternative version that is barely started

This is not for review, but only if you want to run benchmarks or something.

Should be ready for review (modulo can't push the recently merged master issue).

Should be ready for review (modulo can't push the recently merged master issue).

Still ready for review! (even though I still haven't resolved the conflicts)

A tedious rebase did not fix the problem. But generating a new access token with more permissions did.

I ran the benchmarks on the HOAS machine and the CEK machine and got some mysterious results.  For the validation benchmarks
the HOAS version seem to be about 10% faster than the CEK machine, but for the nofib benchmarks it's a different story.
I got these figures by deleting the uses of spendBudget in Cek.hs and Apply.hs, then running the benchmarks on the CEK machine in the normal way; then I replaced uses of unsafeEvaludateCek with unsafeEvaludateHoas in the benchmark drivers and ran the benchmarks again.  Here are the results: all times are in milliseconds and the final column shows the CEK evaluation time divided by the HOAS evaluation time (so numbers > 1 mean that HOAS is faster, < 1 means that CEK is faster).  I didn't make any attempt to measure memory usage, but there wasn't anything noticeable going wrong.
Benchmark              CEK    HOAS    CEK/HOAS

crowdfunding/1        2.243   2.109   1.06
crowdfunding/2        2.218   2.119   1.05
crowdfunding/3        2.254   2.180   1.03
crowdfunding/4        1.034   0.9594  1.08
crowdfunding/5        1.028   0.9497  1.08
future/1              1.163   1.210   0.96
future/2              2.575   2.656   0.97
future/3              2.553   2.592   0.98
future/4              3.233   3.281   0.99
future/5              4.106   4.017   1.02
future/6              3.457   3.244   1.07
future/7              4.083   3.996   1.02
multisigSM/1          2.516   2.172   1.16
multisigSM/2          2.637   2.184   1.21
multisigSM/3          2.666   2.223   1.20
multisigSM/4          2.717   2.235   1.22
multisigSM/5          3.053   2.758   1.11
multisigSM/6          2.526   2.144   1.18
multisigSM/7          2.620   2.155   1.22
multisigSM/8          2.717   2.234   1.22
multisigSM/9          2.704   2.272   1.19
multisigSM/10         3.047   2.761   1.10
vesting/1             2.280   2.048   1.11
vesting/2             2.092   1.746   1.20
vesting/3             2.292   2.043   1.12
marlowe/trustfund/1   6.367   6.414   0.99
marlowe/trustfund/2   4.902   4.446   1.10
marlowe/zerocoupon/1  6.790   6.589   1.03
marlowe/zerocoupon/2  4.426   3.941   1.12

clausify/formula1     64.39   153.7   0.42
clausify/formula2     80.75   186.8   0.43
clausify/formula3     221.8   525.2   0.42
clausify/formula4     345.9   677.3   0.51
clausify/formula5     1546    3489    0.44
knights/4x4           193.0   296.4   0.65
knights/6x6           546.2   927.3   0.59
knights/8x8           903.0   1587    0.57
primetest/05digits    151.8   123.1   1.23
primetest/08digits    293.4   233.2   1.26
primetest/10digits    435.5   343.0   1.27
primetest/20digits    921.5   756.6   1.22
primetest/30digits    1387    1152    1.20
primetest/40digits    1970    1685    1.17
primetest/50digits    2205    1890    1.17
queens4x4/bt          33.41   58.79   0.57
queens4x4/bm          43.00   74.71   0.58
queens4x4/bjbt1       41.70   69.39   0.60
queens4x4/bjbt2       41.33   71.26   0.58
queens4x4/fc          84.03   160.4   0.52
queens5x5/bt          440.8   754.2   0.58
queens5x5/bm          528.3   855.4   0.62
queens5x5/bjbt1       545.3   880.0   0.62
queens5x5/bjbt2       550.7   917.8   0.60
queens5x5/fc          1088    2038    0.53

So for the nofib benchmarks, the CEK machine is usually about twice as fast as the HOAS evaluator, except for the primetest benchmark, where HOAS is about 20% faster.  Interesting, eh?
Speculation: the primetest example is mostly numerical computation, but the other nofib benchmarks are doing combinatorial searches, often involving nested data structures.  Could it be that the HOAS version is faster than the CEK version at evaluating builtins, but slower at working with Scott-encoded types (ie, lambdas)?  I'm not sure exactly how we'd find out, but it'd be good to know what's going on.

I forgot to ask this in the review, but is there any particular reason why this isn't in Evaluation/Machine? I suppose it's not a machine...

Could it be that the HOAS version is faster than the CEK version at evaluating builtins, but slower at working with Scott-encoded types (ie, lambdas)?

Well, it has a different builtin machinery, so it may indeed be faster at doing builtins. I think Roman was going to port the existing machines to use the new approach, which might remove even this advantage...

Needs an updateMaterialized

@kwxm

Could it be that the HOAS version is faster than the CEK version at evaluating builtins, but slower at working with Scott-encoded types (ie, lambdas)?

It could, I've been meaning to try out the other builtin application machinery for the CEK machine.
Thanks for providing the numbers, they are pretty shocking. But I haven't tried optimizing the HOAS evaluator yet, maybe there's some scope for improvement (or maybe not).

I forgot to ask this in the review, but is there any particular reason why this isn't in Evaluation/Machine? I suppose it's not a machine...

Yeah, "not a machine" is the only reason.

I had another look at this and I think I prefer this way of evaluating builtins to the previous one, since it cuts out all the annoying stuff involving arities (and that may help to speed things up since we're only checking some things once instead of twice).  It's worth pointing out that it does change the semantics slightly, since now the machine's  typechecking arguments to builtins as soon as it gets them, rather than waiting until it's got them all and then getting the application machinery to do the check.  This means that the program with body [(builtin addInteger) (con string "n")] now fails at runtime, whereas in the current version of the CEK machine it succeeds (and is returned to the user) since it never gets as far as the builtin evaluation code. This is surely a good thing!  On the other hand, it means that the details of the builtin evaluation code are leaking into the machine now, so we'd have to have TypeSchemes in the specification.  Again, that might be a good thing: I was trying to update the specification recently and ended up with some complicated stuff about arities, partly because I was trying to keep types out of the specification of the "untyped" machine.  It might be better just to come clean and put type schemes in there instead.

Could you reassure me that this really is evaluating PLC strictly?  I'm never very confident when laziness is involved, especially in conjunction with monads.

I think there are lots of ideas in here:

using HOAS to speed up and reduce boiler plate of substitution.
using a higher order representation of values.
using a higher order representation of partially applied builtins.
some kind of denotational machine.

is this right? I have only had a quick look.
From the formalisation point of view I think 1 is the most scary. There is both the term and the type level, and staying strictly positive etc. But, I guess related things have been done as @effectfully has pointed out in the past.
I think 1 is quite independent. I think 2 and 3 could be tried with the CEK machine. 4 is also something that can be tried separately I think.
In general I think it would be nice to analyse different changes separately.

Great suggestion from James, not sure how easy it is to check, though. I guess we could try applying the other parts to the CEK machine individually and seeing how they do.

Comments addressed (I think?). Sure be ready for merging.
@kwxm

It's worth pointing out that it does change the semantics slightly, since now the machine's typechecking arguments to builtins as soon as it gets them, rather than waiting until it's got them all and then getting the application machinery to do the check.

We could change that if we wanted to. Instead of unlifting arguments immediately, we could put them in a continuation or something and run it upon full saturation.

Could you reassure me that this really is evaluating PLC strictly? I'm never very confident when laziness is involved, especially in conjunction with monads.

But surely we should just have a const 0 error ~> error test case and maybe some others and check all the evaluators. I'll think about that and add them later.

using HOAS to speed up and reduce boiler plate of substitution.

It doesn't really seem to speed anything up, we still do lookups as @michaelpj noticed.

using a higher order representation of values.

Isn't it the same thing as the previous point?

using a higher order representation of partially applied builtins.

Right, this is tangential.

some kind of denotational machine.

We have to evaluate things somehow.

There is both the term and the type level, and staying strictly positive etc.

What do you mean by "the type level"? It's an evaluator for UPLC (I guess I misunderstood).

staying strictly positive etc

We could trying switching to PHOAS if that's a problem. But given that we want to formalize unbounded recursion, it seems natural to model it as one.

I think 2 and 3 could be tried with the CEK machine.

How would higher-order values work with the CEK machine where we store environments in values which makes the whole thing first-order? 3 + CEK -- definitely, I'm going to do that.

4 is also something that can be tried separately I think.

I guess the evaluator from your BSN paper is also some kind of denotational machine and it works with first-order values, so we probably could try that separately indeed. I'm more familiar with HOAS, though.

We could change that if we wanted to. Instead of unlifting arguments immediately, we could put them in a continuation or something and run it upon full saturation.

I don't know.  It seems a bit more sensible to get an error right away if you feed a builtin something of the wrong type; having ill-typed partial applications that will always fail if you fully apply them seems a bit like having an unexploded bomb around.  I suppose you could say the same about λn.n/0 though.
I don't really mind though. If the semantics of builtins change a little bit I don't think it's a big deal (at least until we deploy this stuff).


Add Sound with edit name from All Sounds to Soundboard

Add Dialog with Name and you can choose a soundboard


<LangVersion>latest</LangVersion>What occur in VS2022?

[Enter feedback here]
In this page have Important note about different version of VS but don't talk about VS2022 only VS2019 and VS2017 . Is VS2022 happened  like VS2019?

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

ID: 5694e62b-c756-1f62-4014-2ceafa54c011
Version Independent ID: 3f01c378-22e4-197c-a862-ab4a924506c7
Content: C# language versioning - C# Guide
Content Source: docs/csharp/language-reference/configure-language-version.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for reaching out @behroozbc
I missed updating this article for VS 2022 and .NET 6. The VS 2022 behavior is the same as VS 2019: You'll get the latest C# version (version 10) once you update to VS2022.
If that key is removed, you'll get the version of C# that matches the selected framework for the project.

I think this is not directly tied with Visual Studio version. It's more of what SDK version is being used. A global.json file can override the .NET SDK version being used. So I don't think tying the behavior of <LangVersion>latest</LangVersion> with VS version is accurate.

I did a quick test, and it seems that VS is still using the latest compiler even if I'm overriding the SDK from global.json. I can't explain this 😄
Someone needs to verify my previous comment before making such an update to docs.

@Youssef1313 @behroozbc
The purpose of this note was to alert developers who'd made updates for C# 7.1 - C# 7.3, when Latest was needed for the most recent point release.
It may be that this note should be removed now. I'll work on this early in January.

We experienced something strange in VS 2019 and VS 2022 using .NET 4.7.2 after we removed latest.
This code was running fine on VS 2022 but it was not building on VS 2019. My understanding is that it should work on both, because the default will be used for .NET 4.7.2 which is C# 7.3:
if (myResult is SuccessResult success == false)
{
 // do something
}
Debug.WriteLine($"Result was {success}");

How come is it handled differently if VS is picking up the default language for the .NET Framework selected? If we change the if to just use negation !(myResult is SuccessResult success) instead of == false at the end, it compiles for VS 2019 too. Should I open an issue for that?


Move breadcrumb attribute to attribute store.

Problem
Breadcrumb attribute was stored in the config manager originally, but should be moved over to use the attribute store.
Proposed Solution
Change code to use attribute store, remove from config manager.

Needed for spec compliance: this attribute is not supposed to persist across reboots.


Nturinski/enhancement110

Tabling null checks for now-- all other tsconfig rules are enforced.
Did not realize that I did not have the tslint file yet :(

Need to pend merge until Eric's PR is merged otherwise Travis CI build will break.


Unable to install databricks provider in version 2.4.3

I'm trying to install a data bricks provider on a newly created 2.4.3 environment but it fails to install the provider.
Below are the scheduler logs
ERROR: Could not find a version that satisfies the requirement aiohttp<4,>=3.6.3 (from apache-airflow-providers-databricks) (from versions: none)
ERROR: No matching distribution found for aiohttp<4,>=3.6.3
I'm using the ./mwaa-local-env package-requirements command to build the whl packages and syncing the same plugins.zip regenerated in the requirements folder.
requirements.txt which is synced to S3 bucket
--find-links /usr/local/airflow/plugins
--no-index
apache-airflow-providers-databricks==3.3.0

requirements.txt which is used to generated the whl file
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.4.3/constraints-3.10.txt"

apache-airflow-providers-databricks==3.3.0

are there any other changes that need to be done? Any help is much appreciated.

@srikanthgr did you fix it?
if yes then how?

@lilit-martirosyan-zocdoc yes, I was able to resolve this. So Instead of building the whl files using I used a Linux instance.

@srikanthgr can you elaborate a bit more on how you were able to fix this please?


Grafana Dashboards - No Data

Hi,
I have deployed this chart in to k8s cluster 1.16.11 today (tested and got same results on 1.15.*)
I have run through the steps provided in the repo README, all tests and returned results successfully.
I can access the control-center service ui and see everything healthy and all metrics.
I cant do this in prometheus, i can see a lot of metrics but when i check whats in the dashboards none of them are the same. So i dont get any data in the grafana dashboard: https://github.com/confluentinc/cp-helm-charts/blob/master/grafana-dashboard/confluent-open-source-grafana-dashboard.json

bump

bump

I think you have to manually add scrapers or ServiceMonitor (in prometheus-operator) for it to work

Add ServiceMonitor for example on namespace demo
apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata:   labels:     app: cp-kafka # or any other labels   name: kafka-connect spec:   selector:     matchLabels:   # select the Kafka Service       release: demo-kafka # or any other selector   namespaceSelector:     matchNames:     - demo   endpoints:     - port: metrics


Project status

Hey everyone 👋🏼 ,
I'm in the middle of evaluating different monorepo tools & I think bolt is leading the pack here for my use case. But I wonder what's the current status of the project? I can see some minor changes happening still from time to time. But there also a lot of issues & interesting ideas discussed even from 2018 with no action (for example https://github.com/boltpkg/bolt/issues/78), some commands are not implemented yet & the lack of documentation (bolt --help would be useful to help with this point but it's not implemented)
I know that it will be easy to switch from bolt to yarn workspaces if needed because they are nearly identical. But I'm curious to know about the current state & if there are any future plans for the project.

@lukebatchelor any insight?

Hey @Offirmo , @ahmedelgabri
Sorry about the delay there.
It's a good question for sure. There isn't anyone actively working on improving bolt day to day right now. Specific pieces are picked up as they're needed by companies who are using it essentially. There's definitely a ton of room for improvement, but at this point there's not much incentive to fix some of the glaring gaps.
Definitely not to say it's abandoned, I'm still happy to watch the repo, respond to people and look at good faith PRs, it's just mostly in my own time at this point.
In terms of choosing between the two, like you said, it's very easy to switch. The biggest differences are definitely bolt's strictness which is 100% non-negotiable when you get to a repo of the kind of size we're dealing with (480+ packages, I think around 1.5M loc) and then some nice tooling around upgrades, publishing and task running.
Does that help at all? Happy to chat if not.

Thanks, @lukebatchelor for the update.

I recently completed a brief tour of Atlassian as a front-ender and their rather large frontend monorepo, which contains all the Atlaskit packages plus many more internal packages, was my first real exposure to monorepos.
It may not be the most popular monorepo manager at the moment, but Atlassian is heavily invested in Bolt. I recently selected Bolt to manage a new frontend monorepo at my new job. I like its simplicity and strictness. It’s early days, but so far it’s going well.

Manypkg recently removed Bolt support. That means Changesets will also no longer support Bolt when it updates to Manypkg v2. This, to me, seems to be another nail in Bolt's coffin. So now I have to use an inferior but more popular package manager.


Support for custom state generator

org.springframework.security.oauth2.server.authorization.authentication.OAuth2AuthorizationCodeRequestAuthenticationProvider#DEFAULT_STATE_GENERATOR  Is it a static final field, can it support setting the generator through the setter method?

@chenzhenjia Why do you need the ability to set a custom state generator? Can you provide more details for your use case?

I want to use hashids with long to speed up the OAuth2Authorization query, so I need to customize the stateGenerator

@chenzhenjia

to speed up the OAuth2Authorization query

I'm curious, how do you find it slow? Can you provide more details on the metrics recorded?

According to my understanding, string query is slower in mysql compared to bigint type. If I add an index, bigint will be faster than blob or varchar

@chenzhenjia The OAuth2AuthorizationService.findByToken(String token, @Nullable OAuth2TokenType tokenType) receives a token of type String, so even if you can customize the state token type to a number, it still would need to be passed in as a String given the interface.

Can you provide more details on the metrics recorded so I can understand the performance issue?

I'm not sure there is much of a performance hit to warrant exposing a new public API to allow the state to be customized. Please keep in mind that we limit the APIs we expose publicly because it limits us from making changes in a passive way and it also increases our maintenance of the public APIs. We will only expose a public API if it makes sense and if we feel it will be widely used. I don't think it makes sense for this case.

I want to use hashids with long to speed up the OAuth2Authorization query, so I need to customize the stateGenerator

Instead of providing a setStateGenerator() you can supply your own OAuth2AuthorizationService that simply translates the incoming String token to a number using token.hashCode(). You would first need to save() the token using token.hashCode() and then the subsequent findByToken() can translate to token.hashCode() and then perform the query search.
I'm going to close this as the solution provided will work for your use case.

@jgrandja I think he didn't elaborate exactly what he want with a customizable state generator. He @chenzhenjia want more control of generated state string, i.e. length, characters, as query performance is not the only issue he may come up against. The present fixed default state generator generate 96 random long string, that is too long for general purpose. Characters and length of the state string should be application specific.
I hope i elaborated the issue well.


Is there any way to not treat numpy as a special dependency

I added numpy as a dependency to the sympy benchmarks and now there is a flag/parameter/category related to numpy (but not to other dependencies that we use). I have thousands of results in the database and now when I run with skip existing it no longer recognizes all of the pre-numpy depedency benchmark runs as the same thing. How do I tell asv not to treat numpy as a special dependency?

Not currently. You need to edit the old json files to make it go away.

Is there a way to edit the previous benchmarks to add the numpy designation to them?

I'm afraid the answer is to write your own script that mogrifies the
json and adds the numpy entry to old data files.


Separate out migrations from db definition

I talked to @reconbot today, and he talked to me a bit about how rails works. If I understood him correctly, it'd make sense to separate out migrations from the db definition.
The db definition should be an up-to-date description of what the db should look like, and then migrations should just be for converting old db backups to fit the new description.

I'm still interested in doing this, but it's so far off that I'm going to close this and revisit.


ESP-RFID Relay Blue Board drivers problem

I am trying to repeat a project but I can't send anything to my esp board. I tried a few things i found online such as  flashing the board which gave me: "error: Failed to open COM8", "error: espcomm_open failed" and "error: espcomm_upload_mem failed". In devices and printers i found COM8 with status: driver error.
Does anyone know which drivers I should download and what determins which are needed?

@nardev I'm not familiar with the errors reported here, can you help?

It seems the drivers on my pc were incorrect. I have found the right drivers here is link to the website with drivers and information about it
https://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41

Excellent!


deps: bump upstream Karpenter to v0.36.1

Fixes #N/A
Description
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
89 unchanged lines in 8 files lost coverage.
Overall coverage decreased (-0.3%) to 81.978%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/environment.go
2
95.28%

pkg/operator/operator.go
5
9.94%

pkg/fake/sqsapi.go
6
57.89%

pkg/providers/instanceprofile/instanceprofile.go
6
82.86%

pkg/providers/sqs/sqs.go
8
69.81%

pkg/controllers/controllers.go
9
0.0%

pkg/providers/instancetype/instancetype.go
20
88.78%

pkg/providers/launchtemplate/launchtemplate.go
33
83.39%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
5395

Relevant Lines:
6581

💛  - Coveralls


Fix incorrect reference to RobertaTokenizer.add_special_tokens_single_sequence()

Fixes #85

Also fixed calls to the Learner methods get_optimizer() and get_scheduler() in BertLMLearner.

is it finally working?
even after I have changed the above commits still i am getting the below error
AttributeError: 'RobertaTokenizer' object has no attribute 'add_special_tokens_single_sequence'

thanks I have just merged it.  Try this now.


test: tunning tests performance.

In this PR the next changes are included

removing force option from cy.click
custom entities creation feature level test.
Introduction to entities - use case test.
setting timeout values as part of beforeEach function as it seems to reset the values every time a new test step begins.

:tada: This PR is included in version 0.294.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


path does not find wget on Solaris

By default Solaris has an old version of wget at /usr/sfw/bin/ is it possible to get this path added (on the end)?
Thanks!
Dan

can you send a PR?

sorry, what would a PR be? I haven't used GitHub much.

pull request


Combine some options?

First thanks for the plugin, amazing!
So I want to combine some settings. First of all I want to use the latest EmojiOne (v2.2.7), using the latest version of EmojioneArea (v3.16), use local PNG images instead of using CDN and at last the result should be using tabs like this
Is this possible to combine, if so do you have an example?

You can add any supported emojione version and emojionearea will use what version,
for use use local PNG you need to set emojione.imagePathPNG


[WIP] Update hardcoded references to twitter-ext repo names / EC2 resources

This makes the basic changes to the Ansible rig to decouple it from the twitter-ext project:

Update the Docker image / container name values.
Plug in OSP deploy key names and EC2 resource ids. (Encrypted, because, why not.)
Un-gitignore Ansible "vault" files (which is where the EC2 resources are specified). These can be safely committed, since the vault password isn't included in the repo.

This is untested, just putting it up now for reference. Let's make sure the deploy flow works before merging?

I rebased onto master and I got tests passing on Travis CI. However, Ansible is only used in production (right?), which I have not tested yet.

This is fine, though going forward can we wait to merge PRs with WIP? (Or better, we should just use a GH label.)
I was going to wait to request a merge for this until we tested the deploy flow. Sorry, I wasn't clear about this.


[Feature Request]: Enable logging to configurable logging solution

Scenario
We want to use Teams-ai for production ready solutions. This means we want to be able to properly use Observability and be able to log the outcome of promptcompletions. We want herefor be able to get the complete result of a prompt completion and be able to log into a production ready logging solution the results of the prompt complete. This will allow us to add metrics for response time, token use etc.
Solution
In the code for js https://github.com/microsoft/teams-ai/blob/dc986b5f9b8ddda7dcc0e5aa21d1e5f5eed252f0/js/packages/teams-ai/src/models/OpenAIModel.ts#L316 there in OpenAIModel.completePrompt the output of the completePrompt is log hardcoded to the console. Also a subset of data is returned (an instance of PromptResponse) with limited data.
There are two possible solutions:

Allow to inject a custom logger where the logging with be send to instead of logging to console. This is however limited to process the result of the promptcomplete.
Return te complete result.output instead of a small subset as PromptResponse)

Additional Context

Thanks for the feature request. We have added it to the backlog and will be reviewing it.

Using the events (https://github.com/microsoft/teams-ai/blob/main/js/packages/teams-ai/src/models/OpenAIModel.ts#L185) might help to log what you need in the meantime.
const model = new OpenAIModel({
});

model.events.on("responseReceived", (context, memory, response, streamer) => {
  // log the user prompt with the bot's response
  log(context, response);
});


Fixed process type in TypeScript template.

Hi,
Please run the following commands in order to test my changes:

npx create-react-app my-react-app-01 --typescript
cd my-react-app-01
npm start

Expected result: no more compilation error appears.

Hi @fuszenecker, was this causing you an error?
I'm not a huge fan of this approach, as it's confusing for people... if this is an error, please let me know. It would be better to use the globals file for this, I feel.


Update DinD docs and URL to override STO images in pipeline

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://670d1e72da100beb77061f77--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://670d5d46b329c88d3ee485cf--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://670f9ab43a692642f35da8c5--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://671105e1bfb2cc1d8696dc02--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6711547c8de98d969c889454--harness-developer.netlify.app


Fixed project structure and remade gitignore

While I may have saved you from yourself this time, I really do hope you'll consider moving to IntelliJ and starting to use a dependency manager which I will gladly help you with. ~Blitz

¯_(ツ)_/¯ Thanks @iBlitzkriegi

Lol whoops closed it


Marksheet does not show in teacher, parents and students user.

Can you elaborate more on your issue

when i add marks of a student of an exam as a super admin, marksheet of student shows when login as a super admin. But marksheets does not show when login as that student, their parent or a teacher as a user.

where to check?

Check the settings and maybe post a screenshot

in setting Lock Exam is No selected

Post a screenshot of your issue
Maybe I'll understand more

ok wait

Check the screenshots

            @if(Qs::userIsTeamSA())

{{ $ex->name.' - '.$ex->year }}

                        {!! Qs::getPanelOptions() !!}

                        {{--Sheet Table--}}
                        @include('pages.support_team.marks.show.sheet')
                        {{--Print Button--}}

                            id, $year]) }}" class="btn btn-secondary btn-lg">Print Marksheet

        @endif
As I can see here there was an if statement check for super admin
Im not sure how the creator intended this to be
But if you do want everyone to be able to view it, remove the if statement

where is this?

It's located in resources/pages/support_team/marks/show/index.blade.php I think
From line 14 to maybe 31c

ok, let me check

Thanks it is working. I think creator wants to hide "AFFECTIVE TRAITS" and "PSYCHOMOTOR SKILLS" for students, parents and teachersbut he placed  if statement check in wrong place.

I remember seeing an issue in that page but I forgot about it
Can you please post a screenshot of the exam comments tab opened for all users

exam comments does not show when login as student and parent,
Login As a teacher show only one  "Teacher's Comment"
Login as SuperAdmin shows two "Teacher's Comment and "Head Teacher's Comment"

still you need screenshots?

Yes it would be appreciated

"Please improve" is written by me in user teacher

Ok
Everything works fine so the issue can be closed


Add a DistanceSensor

Add a DistanceSensor e.g. a HC-SR04 Ultrasonic Sensor to picozero.
The state of the sensor should be read "continously" (i.e. regularly using an interupt every 0.0x seconds).
The value of the sensor should be determined by taking the average of the last x number (gpiozero uses 9) of states. This will deal with fluctuations in the data and "smooth" the output
Thoughts on constructor, methods, properties.
Constructor
__init__(self, echo, trigger, max_distance=1, threshold_distance=0.3)
# max_distance is the maximum distance to report from the sensor, anything distance over this value will be truncated to this value
# the threshold_distance is the distance at which the "in_range" events will fire

Properties
.threshold # is the distance at which the "in_range" events will fire
.distance # the distance in metres up to the `max_distance`
.value # a value between 0 (where the sensor is too close to measure a distance) and 1 (where the distance is above the max_distance)
.when_in_range # a function to call when the distance moves below the threshold
.when_out_of_range # a function to call when the distance moves above the threshold

Methods
.wait_for_in_range(timeout=None)
.wait_for_out_of_range(timeout=None)

Created a prototype for DistanceSensor in branch distance_sensor

I have merged the current distance sensor into dev. The device doesnt support events as yet (e.g. when_in_range) suggest we implement this when/if it becomes a requirement given the constraints on the pico.

Release with v0.3.0


No 1.17 or 1.18 release, just tags?

Hi,
There are tags for 1.17 and 1.18, but the latest release is 1.17-beta2. Could binary releases be supplied for at least the latest version?

Hi,
See https://github.com/kohsuke/winsw#download

Ah, thanks. Might be good to make that more prominent - since there were some releases on GitHub, I figured that would be all of them.


[Event Request] - ItemJnlPostLine.Codeunit - OnApplyItemLedgEntryOnBeforeCloseSurplusTrackingEntry

We would like to request the following event:
Object: ItemJnlPostLine.Codeunit
Where is the event placed:
local procedure ApplyItemLedgEntry(var ItemLedgEntry: Record "Item Ledger Entry"; var OldItemLedgEntry: Record "Item Ledger Entry"; var ValueEntry: Record "Value Entry"; CausedByTransfer: Boolean)
var
    ...
    Handled: Boolean;
begin
    ...
    UseReservationApplication := ReservEntry.FindFirst;
    Handled := false;
    OnApplyItemLedgEntryOnBeforeCloseSurplusTrackingEntry(ItemJnlLine, StartApplication, UseReservationApplication, Handled);
    if not Handled then
        if not UseReservationApplication then begin // No reservations exist
            ReservEntry.SetRange(
            "Reservation Status", ReservEntry."Reservation Status"::Tracking,
            ReservEntry."Reservation Status"::Prospect);
            if ReservEntry.FindSet then
                repeat
                    ReservEngineMgt.CloseSurplusTrackingEntry(ReservEntry);
                until ReservEntry.Next() = 0;
            StartApplication := true;
        end;
        ...
end;

Event Code:
[IntegrationEvent(false, false)]
local procedure OnApplyItemLedgEntryOnBeforeCloseSurplusTrackingEntry(ItemJnlLine: Record "Item Journal Line"; var StartApplication: Boolean; var UseReservationApplication: Boolean; var Handled: Boolean)
begin
end;

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.


Support for custom formats

To date, the UI has only provided the ability to choose between preregistered formats in nodes like Constant and Resize. This provides the ability to enter custom formats as follows :

Renames FormatPlug to AtomicFormatPlug, recognising the fact that although a format is a compound value (display window and pixel aspect), the plug itself treats it as a single value.
Introduces a new FormatPlug which has child plugs for the display window and pixel aspect.
Uses the new FormatPlug in all user-facing "enter a format" scenarios.
Moves the default format mechanism from the Format class to the FormatPlug class, leaving the Format class as the simple maths class it should always have been.
Fixes all the default format bugs from #888.
Improves the PythonExpressionEngine to support compound plugs such as the FormatPlug.
Updates FormatPlugValueWidget to allow direct editing of the format values in addition to using the preset formats.

I've basically followed @HughMacdonald's  recommendation for what the FormatPlugValueWidget should look like, except he asked for two custom modes - "Custom" and "Custom with non-zero origin". When I started implementing it, it felt OK to display the origin by default, and a bit clunky to have two modes, once with a somewhat funny name. Hopefully that feels alright to you guys too...

I've just pushed an additional commit to fix the failing documentation test case.

I'm getting this when viewing the Reformat node:
Traceback (most recent call last):
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/Widget.py", line 889, in eventFilter
    self.__showHide( qObject, qEvent )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/Widget.py", line 955, in __showHide
    widget._visibilityChangedSignal( widget )
RuntimeError: Exception : Traceback (most recent call last):
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/LazyMethod.py", line 140, in __visibilityChanged
    cls.__doPendingCalls( widget, method )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/LazyMethod.py", line 174, in __doPendingCalls
    method( widget, *pendingCall.args, **pendingCall.kw )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/PlugLayout.py", line 241, in __updateLazily
    self.__update()
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/PlugLayout.py", line 246, in __update
    self.__updateLayout()
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/PlugLayout.py", line 286, in __updateLayout
    widget = self.__createPlugWidget( item )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/PlugLayout.py", line 355, in __createPlugWidget
    result = GafferUI.PlugValueWidget.create( plug )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferUI/PlugValueWidget.py", line 390, in create
    return creator( plug )
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferImageUI/FormatPlugValueWidget.py", line 77, in __init__
    self._updateFromPlug()
  File "/home/andrewk/apps/gaffer/<IP_ADDRESS>dev/cent7.x86_64/cortex/9/gaffer/python/GafferImageUI/FormatPlugValueWidget.py", line 114, in _updateFromPlug
    for widget in ( self.__minLabel, self.__minWidget, self.__maxLabel, self.__maxWidget, self.__pixelAspectLabel, self.__pixelAspectWidget ) :
AttributeError: 'FormatPlugValueWidget' object has no attribute '_FormatPlugValueWidget__minLabel'

Ah - that's because we're getting a FormatPlugValueWidget for the "format" plug, and the new features don't work with the old AtomicFormatPlug. I could fix the FormatPlugValueWidget but I'm actually tempted to simply deregister it from AtomicFormatPlug to avoid complicating all the code for a use case we really don't care about going forward.
If I did that, what would you prefer?

I do nothing. Reformat becomes very very very deprecated, because the UI doesn't even have a drop down menu for the format any more.
b. I update Reformat to use FormatPlug instead of AtomicFormatPlug.

Is there anything we can do with Reformat that we cant do with Resize now? If not, lets ditch it (remove it from the node menu). We're early enough days with GafferImage in production that people likely haven't used them in scenes yet, outside of auto-generated graphs (modelling turntables).

The only thing is the bugs when upsizing with a couple of the filters (catmull rom and lanczos) - those are fixed in OIIO now, but not yet backported to RB1.5 (I think they will be though). Using those particular filters for upsizing is a bit nonsensical anyway, since they sharpening and more suited to downsizing.

Yeah, seems fine. The turntables are likely downsizing only

Cool - I've pushed commits with those changes.

I've gotten through all the code now, but have a couple comments on the UI.

The Create Python Expression menu item isn't exposed on the Format plug itself (just on the individual elements of the custom format). Does it make sense to expose for the entire plug since we can drive it that way now?

I find it confusing that the Default Format menu item doesn't tell me the associated values the same way registered formats do. I guess that was the case on master too, but it somehow new to say "HD 1080p" in the Viewer, and HD 1080p shows up in the presets list as well (or is that just at IE?).

The custom origin feels a bit odd to me and @lucienfostier ... my first instinct (without recalling any earlier discussions) was to see a similar UI to a V3f (width, height, aspect). What was the reasoning for exposing the origin again? Does it perform differently than using an ImageTransform to offset upstream instead?

The Create Python Expression menu item isn't exposed on the Format plug itself (just on the individual elements of the custom format). Does it make sense to expose for the entire plug since we can drive it that way now?

Yeah, it does make sense. The problem is that the PythonExpressionEngine doesn't know about FormatPlug because it's in another module - it just happens that I designed the default handler in such a way that it would work with FormatPlug. We could either be gung-ho and add the python expression menu to everything with a getValue() method, or we could add some sort of registry mechanism for adding external handlers to the PythonExpressionEngine. The danger of the first is that there will be some plug types for which the default setter doesn't work (TransformPlug and SplinePlug I expect, although I can work around that). The second would be safer but a bit fiddlier.

I find it confusing that the Default Format menu item doesn't tell me the associated values the same way registered formats do. I guess that was the case on master too, but it somehow new to say "HD 1080p" in the Viewer, and HD 1080p shows up in the presets list as well (or is that just at IE?).

That is exactly the way it was before, yes. I guess you would prefer something like "Default (HD 1080p 1920x1080)" then?

The custom origin feels a bit odd to me and @lucienfostier ... my first instinct (without recalling any earlier discussions) was to see a similar UI to a V3f (width, height, aspect). What was the reasoning for exposing the origin again? Does it perform differently than using an ImageTransform to offset upstream instead?

OK, I guess that is a bit odd. It kinda does need to be possible to expose it, because it's possible to have a non-zero origin, so it needs to be possible to edit it. I honestly have no idea what a non-zero origin would be useful for - it's just that it's in the EXR spec that the displayWindow is a box, so that's what we have too. @HughMacdonald had suggested two menu items - "Custom" and "Custom (non-zero origin)", but I felt that that was a bit icky so went with one, which also turns out to have been icky. We could do the two menu items but call them "Custom Size" and "Custom Region"? I'll give that a go.
I'm not super-keen on putting aspect on the same row as width/height, since they're different quantities, and also because it's awkward for the full box view if one row has an extra column.

The custom origin feels a bit odd to me and @lucienfostier ... my first instinct (without recalling any earlier discussions) was to see a similar UI to a V3f (width, height, aspect). What was the reasoning for exposing the origin again? Does it perform differently than using an ImageTransform to offset upstream instead?

OK, I guess that is a bit odd. It kinda does need to be possible to expose it, because it's possible to have a non-zero origin, so it needs to be possible to edit it. I honestly have no idea what a non-zero origin would be useful for - it's just that it's in the EXR spec that the displayWindow is a box, so that's what we have too. @HughMacdonald had suggested two menu items - "Custom" and "Custom (non-zero origin)", but I felt that that was a bit icky so went with one, which also turns out to have been icky. We could do the two menu items but call them "Custom Size" and "Custom Region"? I'll give that a go.

My suggestions were purely based around the fact that Format does support non-zero origins. Personally, I can never think of a situation where I'd want to use a non-zero origin on a Format in practise.
Having a look at the options that Nuke gives for formats, the base level values are just width, height and pixel aspect ratio.
What do you guys think to the (potentially controversial) proposition of not allowing non-zero origin formats to be defined in the GUI... Maybe leave those plugs hidden from the GUI, and only allow them to be set programatically. Do people use them much?

What do you guys think to the (potentially controversial) proposition of not allowing non-zero origin formats to be defined in the GUI... Maybe leave those plugs hidden from the GUI, and only allow them to be set programatically. Do people use them much?

How about the "Custom" menu option shows only the size if the origin is zero (as we'd expect), but shows the full box in the unusual scenario that the origin has been made non-zero by some other process? I like the idea of discouraging non-zeroness (unless someone has a use case), but not of hiding the fact if it is non-zero, since that would be mighty confusing...

That would work for me. That would mean that people generally couldn't set new non-zero origin formats, but would know what's going on if one has either been set programatically or in a previous script.

OK, some updates.

"Create Python Expression…" is available directly for FormatPlugs. It's also now available for all types supported by the PythonExpressionEngine, since I rewrote it to use the same mechanism for both applying the expression to plugs and determining whether or not it can apply the expression to plugs.
The origin isn't shown in the GUI unless it has become non-zero through some other means.
I've reintroduced the HD format registration.

I haven't put extra information on the "Default Format" label yet, because it would lead to insane labels like "Default Format (PC Video (640x480) 640x480 1)". I don't really know why we've labelled our formats the way we have - I don't see any reason why it's a good idea to explicitly format the numbers into the label registered with Format.registerFormat(). They're derivable from the actual numbers at any time, so all you could do is get them wrong. Would anyone object to simpler format names like "2K Super 35", "VGA", etc? And would anyone like to propose a more up-to-date list of likely formats since we have a pretty small number registered by default at present.

I say register the formats purely based on their names, but show them in the drop-down to include the actual numbers...

I've also rebased to fix a merge conflict. Starting work on removing Reformat now, but since ImageTransform is using it internally it's not totally straightforward - we've been meaning to refactor ImageTransform to use Resample internally anyway, so it's worth doing.

I say register the formats purely based on their names, but show them in the drop-down to include the actual numbers…

Sounds reasonable to me - @andrewkaufman, @lucienfostier?
Anyone want to nominate some must-have formats to be registered?

Anyone want to nominate some must-have formats to be registered?

Here's a list of potentially common formats. The inclusion of the Alexa resolution is maybe a bit controversial, but it's probably the format I've used most in the last year.
I would generally say that this list should cover any formats that the base resolution might be. Obviously undistorted resolutions vary wildly, so any pipeline that needs that would need to deal with that situation itself.
The 2/4k 16:9 formats are, I've found, far more common than their Super 35 equivalents.
I don't like how Nuke classifies 2k Cinemascope as 1828 x 1556 - that may be the resolution of the final visible image area, but I've always worked on the full width 2048x1556. That would be like saying that Super 35 is often shown at

HD (1920 x 1080, 1.0)
UHD (3840 x 2160, 1.0)
2k Super 35 (2048 x 1556, 1.0)
2k 16:9 (2048 x 1152, 1.0)
2k Anamorphic (2048 x 1556, 2.0)
4k Super 35 (4096 x 3112, 1.0)
4k 16:9 (2048 x 2304, 1.0)
4k Anamorphic (4096 x 3112, 2.0)
Alexa 2.8k (2880 x 1620, 1.0)

When did anyone on here last use any resolution lower than HD? I haven't in years...

Registering by name only sounds fine, and I definitely do prefer seeing the numbers in the dropdown (as I don't want to memorize the mapping from name to resolution).
And yeah, showing the numers alongside "Default Format" sounds good too.

I'm getting an error on scene load for one of my scripts:
RuntimeError: Exception : Line 1097 : RuntimeError: Exception : Plug "gui.scripts.ScriptNode.daily.AspectFixExpression.__in" rejects input "gui.scripts.ScriptNode.daily.AspectFixSwitch.in.in0".
Here's the body of my expression:
import GafferImage

format = parent["AspectFixSwitch"]["in"]["in0"]["format"]
parent["AspectFixSwitch"]["index"] = format.getPixelAspect() != 1.0

parent["AspectFix"]["format"] = GafferImage.Format( int(format.width() * format.getPixelAspect()), format.height(), 1.0 )

Any ideas whats going wrong?

I agree with Hugh proposal,we somehow need to see the width and height resolution and pixel aspect ( always showing up the plugs?)with the format name.
Sent from my iPhone

On Oct 20, 2015, at 04:47, John Haddon<EMAIL_ADDRESS>wrote:
I say register the formats purely based on their names, but show them in the drop-down to include the actual numbers…
Sounds reasonable to me - @andrewkaufman, @lucienfostier?
Anyone want to nominate some must-have formats to be registered?
—
Reply to this email directly or view it on GitHub.

maybe add the 720p flavor of HD?
Sent from my iPhone

On Oct 20, 2015, at 05:05, Hugh Macdonald<EMAIL_ADDRESS>wrote:
Anyone want to nominate some must-have formats to be registered?
Here's a list of potentially common formats. The inclusion of the Alexa resolution is maybe a bit controversial, but it's probably the format I've used most in the last year.
I would generally say that this list should cover any formats that the base resolution might be. Obviously undistorted resolutions vary wildly, so any pipeline that needs that would need to deal with that situation itself.
The 2/4k 16:9 formats are, I've found, far more common than their Super 35 equivalents.
I don't like how Nuke classifies 2k Cinemascope as 1828 x 1556 - that may be the resolution of the final visible image area, but I've always worked on the full width 2048x1556. That would be like saying that Super 35 is often shown at
HD (1920 x 1080, 1.0)
UHD (3840 x 2160, 1.0)
2k Super 35 (2048 x 1556, 1.0)
2k 16:9 (2048 x 1152, 1.0)
2k Anamorphic (2048 x 1556, 2.0)
4k Super 35 (4096 x 3112, 1.0)
4k 16:9 (2048 x 2304, 1.0)
4k Anamorphic (4096 x 3112, 2.0)
Alexa 2.8k (2880 x 1620, 1.0)
When did anyone on here last use any resolution lower than HD? I haven't in years...
—
Reply to this email directly or view it on GitHub.

OK, I've pushed the new list of format registrations and the changes to append the resolutions to labels programmatically.
@andrewkaufman, about your problem script, I suspect that is caused by the FormatPlug/AtomicFormatPlug change, yes. Could you provide me a path to the script itself? Also, are you loading it with continueOnError = true, and if so does it recover from the error OK?

The email I just sent you about our performance discussion should include the problem expression (AspectFixExpression)

Ah wait, I'm getting the same expression issue on master (but not on <IP_ADDRESS>) so I guess its actually about this one https://github.com/ImageEngine/gaffer/pull/1511


[SPARK-12608][Streaming]Remove submitJobThreadPool since submitJob doesn't create a separate thread to wait for the job result

Before #9264, submitJob would create a separate thread to wait for the job result. submitJobThreadPool was a workaround in ReceiverTracker to run these waiting-job-result threads. Now #9264 has been merged to master and resolved this blocking issue, submitJobThreadPool can be removed now.

cc @tdas

Test build #48602 has started for PR 10560 at commit 6bef376.

Test build #48602 has finished for PR 10560 at commit 6bef376.

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

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

Merged build finished. Test PASSed.

LGTM.

Merging to master


New version: NetSarangComputer.PortX Version 2.2.6

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow
Microsoft Reviewers: Open in CodeFlow

URL: https://cdn.netsarang.net/0ac7ea20/PortX-2.2.6-Setup.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 881)

Automatic Validation ended with:

URI: https://cdn.netsarang.net/0ac7ea20/PortX-2.2.6-Setup.exe, Validation result: Failed, Http status code: NotFound

(Automated response - build 881.)

URL: https://cdn.netsarang.net/0ac7ea20/PortX-2.2.6-Setup.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 882)

The URL access issue has been resolved. Please resume reviewing pull requests.

URL: https://cdn.netsarang.net/0ac7ea20/PortX-2.2.6-Setup.exe
OK
(Automated message - build 882)

@wingetbot run


Slang need to print an error for an invalid system-value semantic name

Problem description
Slang should print an error when an invalid system-value sematic is used.
When a semantic name starts with SV_, it must be one of the reserved semantic names.
Slang silently allows any names but DXC prints an error.
Repro
The following example uses an invalid System-value-like semantic name, SV_DispatchThreadIndex.
A correct name is SV_DispatchThreadID with "ID" not "Index".
RWStructuredBuffer<int> outputBuffer;

[numthreads(1, 1, 1)]
void computeMain(uint tid : SV_DispatchThreadIndex)
{
    outputBuffer[tid] = tid;
}

Try the following command and observe that Slang doesn't print any errors.
$ slangc.sh -stage compute -entry computeMain test.slang

Try the following command and observe that DXC prints an error.
$ dxc.exe -T cs_6_4 -E computeMain test.slang
test.hlsl:4:31: error: invalid semantic 'SV_DispatchThreadIndex' for cs 6.4
void computeMain(uint tid_0 : SV_DispatchThreadIndex)
                              ^

I am working on a fix for this and I need a few clarifications.
Currently Slang does print an error when an invalid system-value sematic name is used, but only when a target is specified during IR legalization. This does not apply for HLSL however and no error is given. When no target is specified(i.e. the command specified in the repro descirption), no error is given. I just want to confirm that the desired behavior is:

Give an error that is backend/target agnostic when an invalid SV name is used. This will check against all valid SV names, for all targets.
"Unimplemented" errors can be given as well in target specific code when a valid SV name is unimplemented or invalid for the specific target(this currently already exists except for HLSL).

After some investigation this issue is best handled together with #411. I originally intended for a quick fix but a proper solution with semantics in the stdlib is a lot more involving since I do not have adequate knowledge(yet at least) on how write proper meta stuff, and my work on this will be paused for now.


jsconsole.com 504

Okay, it seems like some files on jsconsole.com got deleted and the whole thing is broken.
If anyone want to use JSConsole while remy fix it, I've hosted a mirror:
https://jsconsole.aquazus.fr/

Which files? I use jsconsole a lot and haven't had any issues, but then, you've not really specified what it is that was broken.

I don't know about files, but I am only getting "502: An error occurred with your deployment" on jsconsole.com.

Hmm. Okay. Can you send me a screenshot (including URL). I get the whole
thing loading, but its entirely possible that the service worker is hiding
this problem for me (though i tend to clear out regularly to retest).
On Sun, 2 Apr 2017, 10:02 Mark Kindy<EMAIL_ADDRESS>wrote:

I don't know about files, but I am only getting "502: An error occurred
with your deployment" on jsconsole.com.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/remy/jsconsole/issues/93#issuecomment-290973993, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hKAXXHjEa6pCOUugaQWdPtESWE1Pks5rr2QkgaJpZM4MwudX
.

Did my screenshot in the previous post not come out?  Try this:  http://imgur.com/a/8fFDm

Fixed.

Still not working
http://i.imgur.com/XP8jwYY.png

I have the same problem as @Aquazus with the same errors.  jsconsole is no longer working for me in Chrome

By doesn't work, specifically you mean the remote injection, rather than
jsconsole itself.
No one try to look at the code yet? I mean, i would, but I'm busy with paid
client work (and don't need to use the remote injection feature of
jsconsole right now).
On Mon, 17 Apr 2017, 01:50 Marcus Milne<EMAIL_ADDRESS>wrote:

I have the same problem as @Aquazus https://github.com/Aquazus with the
same errors. jsconsole is no longer working for me in Chrome
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/remy/jsconsole/issues/93#issuecomment-294384257, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hJnJ82CZCvpRxOYeYIbPG9y-LT_6ks5rwrc5gaJpZM4MwudX
.

This is still broken FYI. Getting the 502 bad gateway

I also get 502 for https://jsconsole.com/ on Chrome and Edge but not on Firefox or Opera.
And I get 404 for https://jsconsole.com/inject.html, https://jsconsole.com/remote-debugging.html and most important https://jsconsole.com/js/remote.js?some-random-id on all browsers.

Yeah, server keeps borking. It'll 404 on any URL except root whilst it's 50x'ing.

Back online for the time being.

still same error

same error

I was fine yesterday, today I am getting this too. Tested various sessions

Server has blown. Will need to look into why.
On Thu, 10 Aug 2017, 09:32 Josef Vančura<EMAIL_ADDRESS>wrote:

I was fine yesterday, today I am getting this too. Tested various sessions
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/remy/jsconsole/issues/93#issuecomment-321487667, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hKjZos22XFwaaoFoqjo7-3c30YJqks5sWsA0gaJpZM4MwudX
.

Ahem, jsconsole.com/remote-debugging.html [404]

Yep. Known. Cheers.
On Wed, 13 Sep 2017, 08:38 Mahmud<EMAIL_ADDRESS>wrote:

Ahem, jsconsole.com/remote-debugging.html [404]
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/remy/jsconsole/issues/93#issuecomment-329084935, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAA1hOtqrERfKheKgwow1qmEusLWxqEuks5sh4ZcgaJpZM4MwudX
.

Still broken, :listen doesn't answer anything

@aquazus - no, it's depreciated. Use 1.jsconsole.com but know that that service will be retired eventually


Bump to genesis 6.7

Bumping Genesis to Version 6.7.0 to allow users performing the training to benefit from the process reload functionality + enhancements to the Genesis Plugin.
I've also added .genesis_home to .gitignore so the files aren't prompted to be checked in.

Notice column REFRESH_TOKEN no longer exists in 6.7 and it has been dropped from Users.csv

Tested everything locally as part of going thru the training modules 1 and 2.

Thanks @rafaelnferreira. We are finishing a WebTraining review at the moment, and we are happy to see it after this task.
Cheers,

Thanks @dbarros1979  , I would recommend merging it before version 7 as it this would require probably other significant changes. V 6.7 contains significant changes on event handler process restart.