♻ Move to npm

Removed build from being checked in
Moved from yarn to npm. Which has more provisions than yarn these days
Fixed dependencies after running audit
Checked in package-lock.json

Coverage remained the same at 90.833% when pulling ab9b624967a7be22469646338d72480875606784 on varghesethomase:move-to-npm into c685b3455c4d690e4b0df9cbeca99d023bc96050 on tomasswood:master.

@tomasswood I went ahead and added that because it was a peer dependency for foundation-sites which you tend to use. But if you are only using its components which does not use its JS binded ones, I will remove this off.


RFC

@aboe76, @vutny, sorry to bother. What do you think, is this formula worth adding to the saltstack-formulas' repos? If so, do you think the name simpack is ok? I thought also of packager and spm (simple package manager), but both sounded kinda misleading to me, as it's not a 'packager' but a packages manager, and spm is confusing with Salt Package Manager.
Your comments are welcome. (if you know of another way of having some kind of PM, it'll be also welcome 😄)

@javierbertoli Thanks for pointing me to this, looks really great!
I would like to try it. Definitely it should be a part of @saltstack-formulas.
Just my opinion, but maybe simpack is not the best name here. It manages packages, although it does not bring in any new "package manager". By the way, the name is already taken by some 3D simulation software 😄
https://sourceforge.net/projects/simpack/
That could confuse somebody.
How about something as simple as packages-formula or installer-formula?

Great, I didn't even realize that a simpack thing already exists 😄
Renamed to packages-formula, and added it to the "saltstack-formulas" account
Thanks for your comments, @vutny !


autocrystal places obsidian

autocrystal sometimes places obsidian instead of crystals

im aware of this issue, is a little complicated cause of the speed of the ca, but ill look for a solutions to it. thank u.

yea the speed of the ac, when ur ping is very high and ur config fast, the ac places obsidian

Its a cool feature, good job moo 👍

yes thank u techale.

if u use onEnable switch mode u wont ever run into this problem btw.

Always call PlayerControllerMP.syncCurrentPlayItem after u set mc.player.inventory.currentItem

hi earth

hi earth with PYTHON ROFL


Lose trailing slash before making browserPath from permalink

I found what I think is a problem working with static web servers that redirect paths that point to a filesystem directory, expecting to pick up something like index.html from that directory, to insist on a slash at the end of the path. AWS S3 does this, I think without an option to disable it.
A Nuxt /page like /pages/PageItem.vue prerenders to /page-item/index.html. Similarly, /content/ContentItem prerenders through /pages/_content.vue to /content-item/index.html. When loaded from an S3 bucket like http://s3.server.com/page-item S3 helpfully redirects to "http://s3.server.com/page-item/". The page loads and rerenders in the browser.
A similar request for http://s3.server.com/content-item also gets redirected, to "http://s3.server.com/content-item/", but here things go wrong. requestContent.js builds a metadata request from the permalink by replacing all slashes but the first with dots, then appends '.json'. That leaves axios requesting "whatever/content-item..json" and getting 404.
I think the fix is to strip any trailing slash from the permalink when generating serializedPermalink in requestContent.js, something like this:
   const trailingSlash = /\/$/
   const allButFirstSlash = /(?!^\/)(\/)/g
   const serializedPermalink = permalink.replace(trailingSlash, '').replace(allButFirstSlash, '.')

With this in place the problem seems gone in my S3 testing. I'm brand new to nuxtent so please view this with skepticism, but it might be helpful in other static hosting situations.

I have a static generated site deployed and I don't seem to have this problem. Are you sure it's not a config problem?

It's a web server thing. "curl -v http://site.com/dirname" for one of the pagename/index.html links shows a 302 redirect from Amazon S3 with Location: http://site.com/dirname/ instead (trailing slash). Guessing the hosts you're using don't do that redirect. If they do then yes I have some other configuration problem. The patch made my deployment at S3 work. (It's for a campaign that has not yet launched so don't have an example to point you at for a week or so.)

Perhaps the subfolders is worth looking in to: https://nuxtjs.org/api/configuration-generate

This is related with #120 and is being fixed in the development branch.


[STORM-2901]: Reuse ZK connection for Nimbus [for 1.x-branch]

@HeartSaVioR
This is the 1.x-branch patch.
The original PR is here: #2522.

@HeartSaVioR
Can you help me to merge this ?

@danny0405
I have list of pull requests for 1.x version lines and waiting for ongoing release candidate. I'll see if we could get waiting pull requests in current release version when current RCs are cancelled.

@HeartSaVioR
Got it, thx for your work.


Syntax highlighting misidentifies method shorthand function blocks as object literals in TypeScript when the return type of the function is an object

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.74.1
OS Version: Windows 10.0.19045

In Typescript, tokenization misidentifies the code blocks of function properties declared using the object literal method shorthand that have an object return type as object literals.
Function properties can be declared on objects using the method shorthand syntax: ```
let obj = {
foo(){
//code
}
};
In TypeScript, these functions can also have a return type: ```
let obj = {
    foo():number {
        return 5;
    }
};

If this return type is an object type, and there is no space between the object type and the function body, tokenization thinks the function body is an object literal.
This issue does not appear if the function is created without the shorthand or without an object return type.

Steps to Reproduce:

Copy the following code: ```
({
foo():{}{
let bar;//This line is gray, because tokenization thinks it is inside an object literal scope.
//The issue goes away if a space is present between the return type and the method block.
},
foo: ():{}=>{
let bar;//This works fine.
}
});
let bar;
function baz():{}{
let bar;//This also works fine.
}

into VS Code.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Issue remains in latest version.


(maint) decrease build targets

With the switch to puppet 4, we are no longer building and shipping
individual package. Instead, we're shipping puppet as a part of the
puppet-agent package. This means we can reduce the number of cow and
mock build targets to only LTS releases (for community members who are
using the automation in the packaging repo to build puppet). We can also
stop building the dmg and the msi, as puppet will be delivered to those
platforms also with puppet-agent.

:+1:

From the PR against master:
@joshcooper I'm not sure if this is taking what we talked about too far, but this PR is pulling out a lot of stuff from build targets that we should no longer need. I'm not sure if this change will break things (ci, etc) or not... @haus also should participate in this.
Once puppetlabs/packaging#388 is merged, we can update this file again to make sure that we never build deb/rpm packages when an uber_build job is kicked off. That will leave us with only building the gem and tar

CLA signed by all contributors.

@haus we should be able to merge this. Since my packaging PR has been merged, this shouldn't break anything. Though, it looks like we're not even running the uber_build job anywhere for this branch of puppet

:+1:


Dockerfile is failing because of insufficient libraries

Scenario/Intent
Dockerfile is failing because of insufficient libraries
Expected Result
We should be able to build docker image successfully followed by running examples recipes in directory.

Adding Docker logs error which was failing:
Step 4/16 : RUN chef gem install oneview-sdk --no-document # Ignore the warning about the path not containing gem executables
---> Running in 7159406b3f2d
Chef Development Kit cannot execute without accepting the license
Removing intermediate container 7159406b3f2d
The command '/bin/sh -c chef gem install oneview-sdk --no-document # Ignore the warning about the path not containing gem executables' returned a non-zero code: 172


New terms added:
abnormal submucosal gland secretion MP_0014034
decreased submucosal gland secretion MP_0014035


Random performanceTest.wls failure "git tree must be clean"

The problem
Performance Test step sometimes fails on CI with "Current git tree must be clean.": example
#!/bin/bash -eo pipefail
./performanceTest.wls master @HEAD 2
Current git tree must be clean.
The product exited because an error occurred. For a product older than 12.1, this can mean that the product is unregistered.

Exited with code exit status 1
CircleCI received exit code 1

@maxitg what does @HEAD mean? @ is a synonym for HEAD I believe, so this looks wrong to me.

This issue has never happened since then, however, ./performanceTest.wls is indeed broken in this case because it fails with HEAD and silently fails with @HEAD by running the tests on the same branch again (so the performance report is always at zero).

This issue has never happened since then, however, ./performanceTest.wls is indeed broken in this case because it fails with HEAD and silently fails with @HEAD by running the tests on the same branch again (so the performance report is always at zero).


Edit: Discovery Channel (Chile)

Channel ID (required)
DiscoveryChannel.cl
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
No response
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
No response
Notes
No response

Hola buenas quiero crear cuentas


Dim terminal when app terminates

I have a profile which is used for SSH. When the connection is lost, I get a message saying the process has terminated and I am to press ENTER to restart. It's not always easy to spot this message, since it can appear at  the top or middle of the screen (wherever the cursor happened to be). I propose that at this time (optionally) dim the entire window. This way it will be easier to notice the app termination and hit ENTER before continuing.

Thanks for the request! For what it's worth... we have another visual indicator that the connection has been broken:

We're not likely to prioritize the "appearance matrix" work required to support the combinations of {terminated/running, admin/non-admin, focused/unfocused} required to make this possible, so we're committing it to the distant distant backlog for now.

and my stupid idea from triage:

connection dead? ---> deadConnectionAppearance
alive?

unfocused? ---> unfocusedAppearance
focused?

admin? ---> adminAppearance
standard ---> defaultAppearance

Thanks for the request! For what it's worth... we have another visual indicator that the connection has been broken:

what is "another visual indicator" ? the two lines of text? when using ssh and tmux they tend to appear anywhere on screen, hiding between whatever text happens to be on screen. it is not as clear as in the demo image you placed.

Good point.
It’s the (x) which appears to the left of the title. It’s visible in the tab.


Question: On Premise Use

Do you have a sample deployment to use the driver in on On Premise Kubernetes cluster? Or does the cluster need to be hosted in AWS?

The deployment YAML should work on an on prem cluster, are you seeing issues?

I'm trying to run it on a local kubernetes cluster (using Docker Desktop) and I get this error:
failed to mount secrets store object content" err="rpc error: code = Unknown desc = failed to retrieve region from node. error Region not found
Of course I'm not surprised it can't find a region, but I'd like to know how to work around this.


Ryan 2049 jsonvars nobean

for https://github.com/Activiti/Activiti/issues/2049
alternative to https://github.com/Activiti/activiti-examples/pull/31 - that one uses custom pojo
should we have both pojo and no-pojo examples?

Closing this and putting both approaches into one PR


How to put hidden per size (i.e. hidden-xs) on Col?

I am trying to do <Col xs={{hidden: true}}>... but it looks like hidden is not supported on the ColumnProps
Is there a simple way of adding this? Or should I just use className?
Thanks,
Ben

Since this is a utility and not restricted to just Col it is not supported by Col in that way. For now, className is how to achieve this.

I am closing this as the question has been answered and the issue is no longer active. If you are not satisfied with the answer or have further concerns on this topic, please feel free to reopen and/or comment

@TheSharpieOne Can you show us an example what this should look like? This won't work:
<Row>                         <Col xs="6" sm="4">.col-6 .col-sm-4</Col>                         <Col xs="6" sm="4">.col-6 .col-sm-4</Col>                         <Col className="hidden-xs" sm="4">.col .col-sm-4</Col>                     </Row>

Got it, I'm using v4 which uses something like d-*-none. See https://getbootstrap.com/docs/4.0/migration/#responsive-utilities

try with xs-hidden not hidden-xs
<Col xl="2" md="2" className="text-center xs-hidden">

FULL HD
HD
SD
MOBILE


Feature: Add option to ignore languages

Short:
Added an option to skip language highlighting.
Reason:
While working on an internal documentation system, we came across an issue with mermaid-graph rendering and language highlighting. We wanted highlighting for the code examples, but the mermaid graphs should be painted.
There was no easy way to achieve this, through editing the Prism configuration, so I added an option to filter out specific languages from being rendered out.
Solution:
Additional optional setting `languageFilter´.
Default assignment is an empty array, so it will not impact running Installations. This change should be fully backwards compatible.
In the highlighting modules (HighlightPairedShortcode, markdownSyntaxHighlightOption) the language will be checked before any linting, or reading action. It checks if the language is included in the option array. If it is a plain "" will be returned with the language as class and any additional preAttributes set as option.

This is an automated message to let you know that this issue requires additional input from the original poster and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

Do not let the issue’s closing deter you. After you’ve supplied the required information, the issue will be reopened. Thanks!


fix: serde filtering

Problem
Values in list objects will be accidently filtered out so that they will not be included in the output.
Solution
Remove unnecessary instance type check (which filters out single value by mistake) in Serde.

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

One-line summary:
Fix the bug that causes values in list objects being accidently filtered.
Checklist

[ ] You've signed-off your work
[ ] Your pull request title follows our guidelines

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

@xli-1026 I've let myself do the changes. Thank you a lot!


Remove job from wait

Removed the test also (relying on jobs, sooner or later that tests would be gone I suppose)
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

Go home @GordonTheTurtle you're drunk.

:joy:

LGTM

This is amazing ^

seriously amaze
On Thu, Apr 9, 2015 at 3:02 PM, Victor Vieux<EMAIL_ADDRESS>wrote:

[image: screen shot 2015-04-09 at 15 01 50]
https://cloud.githubusercontent.com/assets/1032519/7077892/652a00e6-dec9-11e4-82a0-49ba68ceb11b.png
This is amazing ^
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/12250#issuecomment-91367545.

But where is jenkins?

Amazing but should the test really go?

@icecrime test is broken I'm fixing it just now

Sorry, I was referring to TestRestartKillWait: I don't understand why removing job would make this test obsolete? Wasn't testing a valid use case?

@icecrime mmm I'll reimplement it in integration-cli, is it ok?

yes perfect def not in integration we want to get rid of those :D

Yes I've seen your issue @jfrazelle

Thanks @runcom you are simply awesome!

I wish I could do more :) @tiborvass

@icecrime @tiborvass Added the integration test and rebased

I really don't like this test... I you just moved it from integration to integration-cli.
But really this seems like a unit test and not an integration test.

@runcom Need rebase. Code is ok

done

LGTM

LGTM

Nice!


'fix issue' button reappears if you edit the Version number

The fix issue button reappears the moment you edit text in the Version number field.
I have not clicked the button (for fear!) to see if the behaviour changes as well.

@alexkent Don't click it if there are no emojis! :+1:

The proposed fix for #2 might also fix this. I can't test this right now, because I can't get the "Fix Issue" thing to appear in the project editor :/

Did anyone ever test this with the branch?

#YOLO and merge

I'm assuming #11 also fixes this.


One-line Label translations with word wrapping add a lot of vertical space

Godot version
4.0.1
System information
Windows 10
Issue description
When having a VBoxContainer contain a Label (ProblematicLabel) with translated text and word wrapping, but the translated text is only one line, plus having an HBoxContainer after ProblematicLabel with two labels with translated texts (doesn't matter if they have word wrapping or not), a lot of vertical space is added to ProblematicLabel.
If you download the minimal reproduction project and run it, you'll see what I mean, and if you then change the TEST_TRANSLATION to TWOLINE_TRANSLATION, you'll see that when ProblematicLabel has two lines or more, the vertical space isn't added.
This was also a problem in Godot 4.0.0 and the Release Candidates I tried.
Steps to reproduce
It's very specific, at least the case I found, so it would be very hard to explain properly, check the minimal reproduction project.
Minimal reproduction project
LabelIssue.zip

Hello again, I've been testing and found some other examples.
If you remove all blank spaces from the translated text, " ", when using word wrapping mode, the vertical space won't be added, however, it will still be added when using arbitrary wrapping mode.

Another find, it seems like the translation has nothing to do with it, having the label be a one liner with two spaces causes the same effect, so the translation part became irrelevant. I could swear I tried not using translation and it working fine before? But maybe I just didn't add the spaces when I tried it.
It definitely has to do with how the TextServer handles spaces when autowrapping is on, I tried poking around the source code to see if I could see the problem but since there's no comments I really can't find anything. The mess of Glyphs, flags, etc. is something that will take me a while to figure out.

Alright, I've been snooping around the source code again, and I found out that the "ascent" attribute used to calculate a label minsize, looks like the culprit, although I'm not entirely sure.
I tried commenting the ascent attribute in the text size formula

and the vertical space disappeared, however, as expected, the position of all the texts is then messed up.

This is what it looks like, when the ascent attribute is used:

So, what does this mean? I have no clue. I tried figuring out how this is generated exacly, and it seems like it comes either from a glyph offset???? or the ascender attribute from the font? Which I have no idea how both of them are calculated and this code is a labyrinth without any comments. I would appreciate if someone that has worked in text server before can help me out or something. This seems like a very important issue to fix, considering it affects any one line labels with white spaces.
I will however continue to look around to see if I can somehow figure it out.

Another update, after playing around with ascent I didn't find anything conclusive, or anything that seemed wrong to me, so I went back to the line breaks that happen when word wrapping is active.
I wanted to check what was happening with the width of the label when it's _shape() function was being called and some weird things are going on, at least I think so.
Let's check what happens to the width when there are no white spaces:

I will assume that the multiple calls to _shape() is normal, and as the calls go on, the width end up being the actual width that it's supposed to be, this being 500, the width you can see in the editor.
Now let's take a look at what happens when there are spaces:

It's basically the same thing, however, right before the final call that gets the width right, there's a second call that gets width 1 again. And that second call only happens to the label with white spaces, since the ones that only have "Yes" and "No", get the same amount of calls.
I don't know if this is normal behavior, just wanted to point it out.
I then went to see what happened with the number of lines when having white spaces or not. But before going into that, I'll show where I'm getting the number from. It's from this function in the _shape() function of Label:

In here, each line comes in 2, marking the first character of the line, and the last character of the line. So if line_breaks.size() is "2", that means there's only one line, if it's "4", it means there are two lines, etc.
Without white spaces:

As expected, the size of line_breaks is "2", so there's only 1 line.
With white spaces:

As you can see, the size of line_breaks becomes "6", which means there are three lines detected, which fits with the amount of vertical space being added if you check the pictures of my last comment.
And once again, even though we see that the last call correctly sets it back to "2", meaning only one line. There is a weird second call to _shape() right before that one.
So from this I kinda suspect that the vertical space is being maintained from that weird second to last call, and after the last one that correctly sets the lines, there's no "redraw" happening or whatever, which maybe means that this is only a visual bug from a lack of drawing the last update? It seems to be something along those lines, specially when considering what happens when a label with two lines is drawn:

As we can see, at the end, there is a second _shape() call that correctly sets the number of lines to two. This is missing from the one line example.
So I think it may come down to a lack of a final update of the label.
I'll try to see if I can find where this is happening, or rather, not happening.

Wellp, I'm convinced now that it has to do with a last update not occuring, because I've debugged and the final lines calculated are correct, the only difference is that a two or more lined label gets a last _shape() call from a resize function I don't remember the specific name of now.
As for why commenting the ascent variable fixed it, I believe that was just because it was getting rid of the ascent space of the extra lines and that's all, so it looked like it fixes it, but not really.
But yeah, if you set the custom minimum width of the label to the correct one before executing, the vertical space isn't added.
This pretty much tells me that what is happening is that the VBoxContainer is probably getting the minimum size from shape when the "minimum width" is 0 or 1, which leads to the height being that of "3" lines, so the VBoxContainer height is then set to that, and as a last step, it then sets it's own width to be the correct one, however, in the case of one line labels, this width set is not triggering the last _shape() call like it does for multi-line labels.
I'm on the verge of giving up. I feel like this is the closest I can get to the solution.

Yes, okay, 100% confirmed.
When I add a _shape() call to the resize notification, it works flawlesly.

However, I'm not sure this is the correct way of fixing it.

It seems that line_spacing is taken into account even when it's a single line, I'm not sure if this is expected.

It seems that line_spacing is taken into account even when it's a single line, I'm not sure if this is expected.

That doesn't seem to happen in Godot 3, but don't know if it's a wanted change they did. In any case, seems to be an unrelated issue, as the issue I exposed never used any line_spacing, and it wouldn't make sense to be fixed with a call to _shape() on resize.
But seeing as how weird the GUI code is, who knows if it has something to do with that.
The issue 74052 is also fixed with the added _shape() call and as far as I know, also never used line_spacing if I recall correctly from when I tried it.

In the Label with the text "TEST_TRANSLATION", if the autowrap_mode is set to AUTOWRAP_OFF, the issue disappears.

Duplicate of https://github.com/godotengine/godot/issues/74052.


errors in jellystat-db and jellystat-app containers

I checked my app and db container and found the following errors.
jellystat-app:
1] webpack compiled successfully
[0] Unexpected error on idle client error: terminating connection due to administrator command
[0]     at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:287:98)
[0]     at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)
[0]     at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)
[0]     at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
[0]     at Socket.emit (node:events:511:28)
[0]     at addChunk (node:internal/streams/readable:332:12)
[0]     at readableAddChunk (node:internal/streams/readable:305:9)
[0]     at Readable.push (node:internal/streams/readable:242:10)
[0]     at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
[0]   length: 116,
[0]   severity: 'FATAL',
[0]   code: '57P01',
[0]   detail: undefined,
[0]   hint: undefined,
[0]   position: undefined,
[0]   internalPosition: undefined,
[0]   internalQuery: undefined,
[0]   where: undefined,
[0]   schema: undefined,
[0]   table: undefined,
[0]   column: undefined,
[0]   dataType: undefined,
[0]   constraint: undefined,
[0]   file: 'postgres.c',
[0]   line: '3218',
[0]   routine: 'ProcessInterrupts',
[0]   client: Client {
[0]     _events: [Object: null prototype] { error: [Function (anonymous)] },
[0]     _eventsCount: 1,
[0]     _maxListeners: undefined,
[0]     connectionParameters: ConnectionParameters {
[0]       user: 'jellystat',
[0]       database: 'jfstat',
[0]       port: 5432,
[0]       host: 'jellystat-db',
[0]       binary: false,
[0]       options: undefined,
[0]       ssl: false,
[0]       client_encoding: '',
[0]       replication: undefined,
[0]       isDomainSocket: false,
[0]       application_name: undefined,
[0]       fallback_application_name: undefined,
[0]       statement_timeout: false,
[0]       lock_timeout: false,
[0]       idle_in_transaction_session_timeout: false,
[0]       query_timeout: false,
[0]       connect_timeout: 0
[0]     },
[0]     user: 'jellystat',
[0]     database: 'jfstat',
[0]     port: 5432,
[0]     host: 'jellystat-db',
[0]     replication: undefined,
[0]     _Promise: [Function: Promise],
[0]     _types: TypeOverrides { _types: [Object], text: {}, binary: {} },
[0]     _ending: true,
[0]     _connecting: false,
[0]     _connected: true,
[0]     _connectionError: false,
[0]     _queryable: false,
[0]     connection: Connection {
[0]       _events: [Object: null prototype],
[0]       _eventsCount: 23,
[0]       _maxListeners: undefined,
[0]       stream: [Socket],
[0]       _keepAlive: false,
[0]       _keepAliveInitialDelayMillis: 0,
[0]       lastBuffer: false,
[0]       parsedStatements: {},
[0]       ssl: false,
[0]       _ending: false,
[0]       _emitMessage: false,
[0]       _connecting: true,
[0]       [Symbol(kCapture)]: false
[0]     },
[0]     queryQueue: [],
[0]     binary: false,
[0]     processID: 31,
[0]     secretKey: -1913963847,
[0]     ssl: false,
[0]     _connectionTimeoutMillis: 0,
[0]     _connectionCallback: null,
[0]     saslSession: null,
[0]     serverVersion: '15.3 (Debian 15.3-1.pgdg110+1)',
[0]     release: [Function (anonymous)],
[0]     activeQuery: null,
[0]     readyForQuery: true,
[0]     hasExecuted: true,
[0]     _poolUseCount: 393,
[0]     [Symbol(kCapture)]: false
[0]   }
[0] }
npm ERR! path /app
npm ERR! command failed
npm ERR! signal SIGTERM
npm ERR! command sh -c concurrently "npm run start-server" "npm start"

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-05-30T11_36_13_530Z-debug-0.log

jellystat-db:
PostgreSQL Database directory appears to contain a database; Skipping initialization

2023-05-30 11:36:12.440 UTC [1] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-05-30 11:36:12.441 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-05-30 11:36:12.441 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-05-30 11:36:12.444 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-05-30 11:36:12.449 UTC [24] LOG:  database system was shut down at 2023-05-30 11:35:13 UTC
2023-05-30 11:36:12.454 UTC [1] LOG:  database system is ready to accept connections
2023-05-30 11:36:14.035 UTC [28] ERROR:  database "jfstat" already exists
2023-05-30 11:36:14.035 UTC [28] STATEMENT:  CREATE DATABASE jfstat
2023-05-30 11:38:39.352 UTC [1] LOG:  received fast shutdown request
2023-05-30 11:38:39.354 UTC [1] LOG:  aborting any active transactions
2023-05-30 11:38:39.354 UTC [31] FATAL:  terminating connection due to administrator command
2023-05-30 11:38:39.354 UTC [29] FATAL:  terminating connection due to administrator command
2023-05-30 11:38:39.355 UTC [1] LOG:  background worker "logical replication launcher" (PID 27) exited with exit code 1
2023-05-30 11:38:39.355 UTC [22] LOG:  shutting down
2023-05-30 11:38:39.358 UTC [22] LOG:  checkpoint starting: shutdown immediate
2023-05-30 11:38:39.373 UTC [22] LOG:  checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.008 s, total=0.018 s; sync files=3, longest=0.007 s, average=0.003 s; distance=1 kB, estimate=1 kB
2023-05-30 11:38:39.376 UTC [1] LOG:  database system is shut down

The strange thing is the database/backend seems to be up because the webinterface/frontend works.  I made a few changes to the example docker-compose file but even if I remove those change I still get these errors, I don't remember getting these errors before I did my last pull about the previous issue I reported.  I was wondering why I am seeing database errors even if the database is up?

$ cat jellystat.yml
services:
  jellystat-db:
    labels:
      - "io.containers.autoupdate=registry"
      -<EMAIL_ADDRESS>    image: docker.io/library/postgres:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
      TZ: Europe/Amsterdam
    volumes:
      - $HOME/data/jellystat/jellystat-db/postgres-data:/var/lib/postgresql/data
  jellystat-app:
    labels:
     - "io.containers.autoupdate=registry"
     -<EMAIL_ADDRESS>    image: docker.io/cyfershepard/jellystat:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: 'secret'
      TZ: Europe/Amsterdam
    ports:
      - "3000:3000" #Server Port
      - "3004:3004" #websocket port
    volumes:
      - $HOME/data/jellystat/jellystat-app/backup-data:/backup-data # Mounting the volume

    depends_on:
      - jellystat-db
networks:
  default:

When I use  your original docker-compose file I get the same, which looks like this.
services:
  jellystat-db:
    image: docker.io/library/postgres:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
    volumes:
      - $HOME/data/jellystat/jellystat-db/postgres-data:/var/lib/postgresql/data
  jellystat-app:
    image: docker.io/cyfershepard/jellystat:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: 'secret'
    ports:
      - "3000:3000" #Server Port
      - "3004:3004" #websocket port
    volumes:
      - $HOME/data/jellystat/jellystat-app/backup-data:/backup-data # Mounting the volume

    depends_on:
      - jellystat-db
networks:
  default:

can you try this compose file, your volume mount seems incorrect. Also id recommend a fresh db
services:
  jellystat-db:
    labels:
      - "io.containers.autoupdate=registry"
      -<EMAIL_ADDRESS>    image: docker.io/library/postgres:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
      TZ: Europe/Amsterdam
    volumes:
      - $HOME/data/jellystat/jellystat-db/postgres-data:/var/lib/postgresql/data
  jellystat-app:
    labels:
     - "io.containers.autoupdate=registry"
     -<EMAIL_ADDRESS>    image: docker.io/cyfershepard/jellystat:latest
    environment:
      POSTGRES_USER: jellystat
      POSTGRES_PASSWORD: 'password'
      POSTGRES_IP: jellystat-db
      POSTGRES_PORT: 5432
      JWT_SECRET: 'secret'
      TZ: Europe/Amsterdam
    ports:
      - "3000:3000" #Server Port
      - "3004:3004" #websocket port
    volumes:
      - $HOME/data/jellystat/jellystat-app/backup-data:/app/backend/backup-data # Mounting the volume

    depends_on:
      - jellystat-db
networks:
  default:

I hadn't caught that, must have had  removed too much when copying over my own path.  However that didn't fix the errors. I found out the problem was PEBKAC, since I hadn't used compose before because I normally only  dump what I want to run into a one liner bash script. What I was doing stopping my containers using podman instead of using "podman-compose -f  jellystat.yml down". After I used that  after having generated my systemd unit files  both the app and the db instances came up without errors. Here's what it looks like now.
jellystat-db:
]$ podman logs  compose_jellystat-db_1

PostgreSQL Database directory appears to contain a database; Skipping initialization

2023-05-30 17:55:24.778 CEST [1] LOG:  starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2023-05-30 17:55:24.778 CEST [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2023-05-30 17:55:24.778 CEST [1] LOG:  listening on IPv6 address "::", port 5432
2023-05-30 17:55:24.780 CEST [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-05-30 17:55:24.785 CEST [24] LOG:  database system was shut down at 2023-05-30 17:55:24 CEST
2023-05-30 17:55:24.789 CEST [1] LOG:  database system is ready to accept connections
2023-05-30 17:55:26.064 CEST [29] ERROR:  database "jfstat" already exists
2023-05-30 17:55:26.064 CEST [29] STATEMENT:  CREATE DATABASE jfstat

jellystat-app:
$ podman logs  compose_jellystat-app_1

><EMAIL_ADDRESS>start-app
> concurrently "npm run start-server" "npm start"

[0]
[0] ><EMAIL_ADDRESS>start-server
[0] > cd backend && node server.js
[0]
[1]
[1] ><EMAIL_ADDRESS>start
[1] > react-scripts start
[1]
[0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
[0] FS-related option specified for migration configuration. This resets migrationSource to default FsMigrations
[0] Server listening on http://<IP_ADDRESS>:3003
[0] Activity Interval: 1000
[0] LibraryMonitor Interval: 600000
[0] Backup Interval: 86400000
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> http://<IP_ADDRESS>:3003
[1] [HPM] Proxy created: /  -> ws://<IP_ADDRESS>:3004
[1] Proxy middleware applied
[1] (node:61) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
[1] (Use `node --trace-deprecation ...` to show where the warning was created)
[1] (node:61) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
[1] Starting the development server...
[1]
[1] Compiled successfully!
[1]
[1] You can now view jfstat in the browser.
[1]
[1]   Local:            http://localhost:3000
[1]   On Your Network:  http://<IP_ADDRESS>:3000
[1]
[1] Note that the development build is not optimized.
[1] To create a production build, use npm run build.
[1]
[1] webpack compiled successfully
[1] Compiling...
[1] Compiled successfully!
[1] webpack compiled successfully

Sorry  about the PEBKAC on my end. Still learning as I go with podman-compose and this new awesome app Jellystat! :)

No problem, I was sceptical that that would be the issue as it seemed so unrelated, but to prevent similar issues Il rework the code so that not having this mount doesn't affect the sync part

Thanks again for your time!


benchmark needed

are results tested without glyph instructions? also it better if you can provide eval dataset rather than prompts template for better reproduction

The full prompts of two eval benchmarks, which are related to the OCR results shown in the paper,  could be found in the text_prompts/paper folder.


Capturing frames rate is no more ok

(create a new branch to fix this bug)
The new mechanism for the display of camera captured frames is now ok, but still gets a concern with the refreshing rate of captures frames (about 20 fps rather than 30 fps).
Let's invertigate this, which might be due to not useful manipulations and/or copies on intermediate frames.

Took some days, interesting job and features.
Finally completed and tested. Some artifacts have not been fully solved. They seem to be due to the non-RTOS status of Windows (and of Linux as well).
[RTOS: Real-Time Operating System]
Notice: the closing of this issue closes also its related branch. Ouf!


Error running predict_frrn_a.py with the prerequisites mentioned in README

Hi !@TobyPDE
I installed all the prerequisites as mentioned in README file. But i still get an error when i try to run predict_frrn_a.py
Please help..
(frrn) mrl@mrl:~/FRRN$ python predict_frrn_a.py
Enter path to CityScapes folder [/home/mrl/FRRN/leftImg8bit_trainvaltestt/leftImg8bit]: /home/mrl/FRRN/cityscapes
Enter model filename [/home/mrl/FRRN/models/frrn_a.npz]: /home/mrl/FRRN/models/frrn_a.npz
Define network... [0.34s]
Load model... [0.37s]
Compile validation function... [0.27s]
Traceback (most recent call last):  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/type.py", line 267, in dtype_specs    }[self.dtype] KeyError: 'object'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 408, in constant_or_value    TensorType(dtype=x_.dtype, broadcastable=bcastable),  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/type.py", line 50, in init    self.dtype_specs()  # error checking is done there  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/type.py", line 270, in dtype_specs    % (self.class.name, self.dtype)) TypeError: Unsupported dtype for TensorType: object
During handling of the above exception, another exception occurred:
Traceback (most recent call last):  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 202, in as_tensor_variable    return constant(x, name=name, ndim=ndim)  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 422, in constant    dtype=dtype)  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 417, in constant_or_value    raise TypeError("Could not convert %s to TensorType" % x, type(x)) TypeError: not all arguments converted during string formatting
During handling of the above exception, another exception occurred:
Traceback (most recent call last):  File "predict_frrn_a.py", line 66, in     test_predictions = lasagne.layers.get_output(network.output_layers, deterministic=True)[0]  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/lasagne/layers/helper.py", line 190, in get_output    all_outputs[layer] = layer.get_output_for(layer_inputs, **kwargs)  File "/home/mrl/FRRN/dltools/layers.py", line 36, in get_output_for    return T.nnet.abstract_conv.bilinear_upsampling(input, self.factor)  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/nnet/abstract_conv.py", line 569, in bilinear_upsampling    row * ratio, col * ratio))  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/var.py", line 327, in reshape    return theano.tensor.basic.reshape(self, shape, ndim=ndim)
File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 4526, in reshape    newshape = as_tensor_variable(newshape)  File "/home/mrl/anaconda3/envs/frrn/lib/python3.5/sitepackages/theano/tensor/basic.py", line 208, in as_tensor_variable    raise AsTensorError("Cannot convert %s to TensorType" % str_x, type(x)) theano.tensor.var.AsTensorError: ('Cannot convert (None, None, Elemwise{mul,no_inplace}.0, Elemwise{mul,no_inplace}.0) to TensorType', <class 'tuple'>)

Can you try to rerun the test with the new release? Also make sure to check the dependencies via the provided script before.


Could you add settings to change colors please?

Could you add settings to change colors please? <3

Thanks a lot sir! <3
Your mod is awesome!


Index operation

Description
[Describe what this change achieves]
Issues Resolved
#284
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Create another PR for the merge, this one is no longer needed


How do we integrate robolectric with gradle?

I have some robolectric tests in @material-foundation/material-remix-android.
It's working fine.
This is what my build.gradle's deps look like
dependencies {
compile 'com.android.support:appcompat-v7:24.1.1'
compile 'com.android.support:design:24.1.1'
compile 'com.android.support:recyclerview-v7:24.1.1'
compile 'com.android.support:support-annotations:24.1.1'
compile project(':remixer_core')
testCompile 'junit:junit:4.12'
testCompile 'org.mockito:mockito-core:2.0.87-beta'
testCompile 'org.robolectric:robolectric:3.1.1'
}

Moved to https://github.com/material-motion/material-motion-team/issues/156.


Avro EOF Error

Hello, I am having a bit of an issue running functions in Python with Avro. I am creating a message from Java that is serialized using a schema file without compression that should be processed by a python function. After some tinkering around, the only way to get avro to deserialize was to use  schemaless_reader function not the normal reader, however this keeps throwing:
EOF Expected<PHONE_NUMBER>000 bytes, read 98350
If I try to use the normal reader from fastavro, it throws an error indicating that it can't read the header.
What should I do in this case?

What's the Python client version you used? Could you show the specific steps to reproduce with Python clients, not Python Functions?


Add Tsuwave website, #69

Signed-off-by: Istvan Csaki<EMAIL_ADDRESS>

Ignore and close that issue pls, I did that on wrong file


Incomplete sort

Hi,
Love your plugin but it's hard to use it. I found this file:
export * from './lib/ticker-wat/Wat'
export * from './lib/sticky-wat/Wat'
export * from './lib/client-wat/Wat'
export * from './lib/ticker-wat/Wat'
export * from './lib/custom-wat/Wat'
export * from './lib/rules-wat/Wat'
export * from './lib/send-wat/Wat'
export * from './assets/timezone'
export * from './hooks/useWat'
export * from './lib/avatar/Avatar'

doesnt get sorted properly. I have to --fix it twice to get entirely sorted.

Hi,
Thanks for raising an issue.
I hope to take a look at this at the end of the week.


Updating masthead text spacing

Collapsing the line-height and adding some bottom margin to the breadcrumb to match the comp more accurately
Removing bottom margin from the title and adding top margin to the strapline
Adding adjacent selector to add top margin to button (if no strapline)


wasi-cap-std-sync,  wasmtime* => 0.24

Not compiling with current versions:
   Compiling wasi-cap-std-sync v0.23.0
error[E0599]: no method named `set_times` found for struct `cap_std::fs::File` in the current scope
  --> /Users/scalderon/.cargo/registry/src/github.com-1ecc6299db9ec823/wasi-cap-std-sync-0.23.0/src/file.rs:84:14
   |
84 |             .set_times(convert_systimespec(atime), convert_systimespec(mtime))?;
   |              ^^^^^^^^^ method not found in `cap_std::fs::File`
   |

@vespa59 is this an upstream issue?

@softprops hmmm... I'm not sure. Super-novice with Rust. I was getting that compiler error on a fresh install and that's how I got past it.


Distribute 'keyof' union types

With this PR we transform keyof applied to a union type to an intersection of keyof applied to each union constituent. In other words, we rewrite types of the form keyof (A | B) to keyof A & keyof B.
Some examples:
type A = { a: string, c: string };
type B = { b: string, c: string };

type T1 = keyof (A | B);  // "c"
type T2<T> = keyof (T | B);  // (keyof T & "b") | (keyof T & "c")
type T3<U> = keyof (A | U);  // ("a" | keyof U) | ("c" & keyof U)
type T4<T, U> = keyof (T | U);  // keyof T & keyof U
type T5 = T2<A>;  // "c"
type T6 = T3<B>;  // "c"
type T7 = T4<A, B>;  // "c"

This PR is the mirror image of #22300 and finally brings symmetry to the type eqivalences:
keyof (A & B) <==> keyof A | keyof B
keyof (A | B) <==> keyof A & keyof B

Why it took so long to figure out I don't know!
Fixes #23618.

I somehow ended up with a bad merge on this branch so I'm abandoning this PR in favor of #23645.


Right-clicking with fire aspect does not properly emulate a flint-and-steel right-click.

With flint and steel, you can right click on creepers or tnt to directly ignite them, however with this tweak enabled, that is not possible. It does not do anything when clicking on a creeper and just places fire down as if on any other block when clicking on tnt.

Ah yeah, never did add handling for entity clicks. Not sure what's up with TNT, will need to look into it.


Add diagrams of player overlays to docs

Include diagrams showing where the various progress bars, play buttons, and other obscuring overlays show up on different platforms so you can better avoid them when designing a theme.

Closed by 5632195


Tying to run example locally using windows.

Hello. I have been trying to run this locally in windows machine but was unable to do so.
I follow the creating of the docker file and the r files as per the example in the repository.
Dockerfile:
FROM public.ecr.aws/lambda/provided:latest

ENV R_VERSION=4.0.3

RUN yum -y install wget

RUN yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm \
  && wget https://cdn.rstudio.com/r/centos-7/pkgs/R-${R_VERSION}-1-1.x86_64.rpm \
  && yum -y install R-${R_VERSION}-1-1.x86_64.rpm \
  && rm R-${R_VERSION}-1-1.x86_64.rpm

ENV PATH="${PATH}:/opt/R/${R_VERSION}/bin/"

# System requirements for R packages
RUN yum -y install openssl-devel

RUN Rscript -e "install.packages(c('httr', 'jsonlite', 'logger'), repos = 'https://cloud.r-project.org/')"

#COPY runtime.R functions.R ${LAMBDA_TASK_ROOT}/

COPY runtime.r ${LAMBDA_TASK_ROOT}/
COPY functions.r ${LAMBDA_TASK_ROOT}/
RUN chmod 755 -R ${LAMBDA_TASK_ROOT}/

RUN printf '#!/bin/sh\ncd $LAMBDA_TASK_ROOT\nRscript runtime.R' > /var/runtime/bootstrap \
  && chmod +x /var/runtime/bootstrap

functions.R
#' Determine if the given integer is even or odd
#'
#' @param number Integer
#'
#' @return "even" or "odd"
#' @export
#'
#' @examples
#' parity(3) # odd
#' parity(4) # even
parity <- function(number) {
  list(parity = if (as.integer(number) %% 2 == 0) "even" else "odd")
}

#' A nullary function that returns the current version of R
#'
#' @return character
#' @export
#'
#' @examples
#' hello()
hello <- function() {
  list(response = paste("Hello from", version$version.string))
}

and runtime.R as in the repository,
https://github.com/mdneuzerling/r-on-lambda/blob/main/runtime.R
Then in PowerShell I run the following successfully.
docker build -t mdneuzerling/r-on-lambda .
docker run -p 9000:8080 mdneuzerling/r-on-lambda "functions.parity"
and in a different PowerShell window the following command,
& 'C:\Program Files\Git\mingw64\bin\curl' -i -X POST -H "Content-Type:application/json" -d '{"number": 5}' "http://localhost:9000/2015-03-31/functions/function/invocations"
which gives me the following result:
HTTP/1.1 200 OK

Date: Tue, 08 Mar 2022 14:43:29 GMT

Content-Length: 0

and in the PowerShell where the docker was build and run I get the following message:
08 Mar 2022 15:21:49,924 [INFO] (rapid) exec '/var/runtime/bootstrap' (cwd=/var/task, handler=)
START RequestId: 9274a11f-ad28-4091-adf1-eb9e9ebd0107 Version: $LATEST
08 Mar 2022 15:22:01,741 [INFO] (rapid) extensionsDisabledByLayer(/opt/disable-extensions-jwigqn8j) -> stat /opt/disable-extensions-jwigqn8j: no such file or directory
08 Mar 2022 15:22:01,741 [WARNING] (rapid) Cannot list external agents error=open /opt/extensions: no such file or directory
Fatal error: cannot open file 'runtime.R': No such file or directory
08 Mar 2022 15:22:01,759 [WARNING] (rapid) First fatal error stored in appctx: Runtime.ExitError
08 Mar 2022 15:22:01,759 [WARNING] (rapid) Process 15(bootstrap) exited: Runtime exited with error: exit status 2
08 Mar 2022 15:22:01,759 [ERROR] (rapid) Init failed error=Runtime exited with error: exit status 2 InvokeID=
08 Mar 2022 15:22:01,759 [WARNING] (rapid) Reset initiated: ReserveFail
08 Mar 2022 15:22:01,759 [WARNING] (rapid) Cannot list external agents error=open /opt/extensions: no such file or directory
Fatal error: cannot open file 'runtime.R': No such file or directory
08 Mar 2022 15:22:01,775 [WARNING] (rapid) First fatal error stored in appctx: Runtime.ExitError
08 Mar 2022 15:22:01,775 [WARNING] (rapid) Process 30(bootstrap) exited: Runtime exited with error: exit status 2
END RequestId: b86265e8-e17d-4894-a410-dc743cb434bc
REPORT RequestId: b86265e8-e17d-4894-a410-dc743cb434bc  Init Duration: 0.14 ms  Duration: 33.99 ms      Billed Duration: 34 ms  Memory Size: 3008 MB  Max Memory Used: 3008 MB

Is there something I am missing? cannot get it to return the result 'odd'.  The message "First fatal error stored in appctx: Runtime.ExitError" does not seem to appear in the example.
I also tried to push the image to aws-ecr and creating a function in aws-lambda as per the example unsuccessfully.
Thank you in advance

Managed to find the issue, it was in the docker file:
For some reason when copying "COPY" the files with .R extensions they need to be done in separate lines for each file unless they are with lower case .r file extension.
The files need to be copy in upper case file extension, this solve the issue.

No worries and thank you for your reply.
It was something I should have figure it out from the start so I am glad you didn't wasted time looking into this.
It is also very satisfying finding the mistake on my own.
Hope your new job is going great :)


rustup

@bors r+

:pushpin: Commit 37b1190defc78a8d2d4139bfcb4816a1a7faf253 has been approved by RalfJung

:hourglass: Testing commit 37b1190defc78a8d2d4139bfcb4816a1a7faf253 with merge 8355437d5d0e747b7e7239cd0a2af8a3825bd912...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 8355437d5d0e747b7e7239cd0a2af8a3825bd912 to master...


Can no longer reference sub environment variables from the base environment

Expected Behavior
Sub Environment variables used to work when referenced in the Base Environment.
Actual Behavior
The reference links are now broken and Insomnia cannot find the variables
Reproduction Steps

Create a Sub Environment and create a variable called var1
Go to Base Environment and create a new variable that references var1 as _.var1.

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.5.3
What operating system are you using?
macOS
Operating System Version
macOS Monterey 12.2.1 and Ventura 13.5
Installation method
downloaded from insomnia.rest
Last Known Working Insomnia version
2023.4.0

Bump on this. I'm thinking about moving from Postman to Insomnia and this is a blocker for me to move over IMO.


CUDA: Fix and deprecate inspect_ptx(), fix NVVM option setup for device functions

This fixes issues with device functions:

inspect_ptx was broken by PR #6735 (commit 11a7397). The device  function should use the code library to obtain the PTX instead of attempting to compile directly itself.
Optimization and debug options were not passed to NVVM when compiling device functions. These options are now set up and passed to compile_cuda when a device function is compiled.

This commit also deprecates the use of inspect_ptx - the preferred API for compiling Python to PTX is to use the compile_ptx function instead. The inspect_ptx() method had a couple of issues:

Allowing it to receive a dict of options for NVVM enabled it to produce different PTX to what might actually have been compiled so far, as highlighted by the fact that optimization and debug flags failed to be passed to NVVM for the compile() method, but not in the inspect_ptx() method.
The NVVM options dict kwarg was unsafely initialized anyway (nvvm_options={}) - See issue #5811.
It returned encoded bytes, which differs from similar APIs (e.g. inspect_llvm(), and the Dispatcher's inspect_asm(), which return str instead.

As there is no easy way to correctly and consistently pass NVVM options through inspect_ptx(), a warning is emitted stating that these are ignored if a user passes any options in.
Some tests are also added, to ensure that it works correctly, and warns the user appropriately.
Fixes #6950.

@gmarkall many thanks for the updates. Please could you resolve the conflict and then this can be run through the farm? Thanks again!

@gmarkall many thanks for the updates. Please could you resolve the conflict and then this can be run through the farm? Thanks again!

Thanks for the review - the conflicts are fixed but the tests fail due to master being broken for CUDA at the moment, e.g.:
======================================================================
ERROR: test_array_assign_all (numba.cuda.tests.cudadrv.test_cuda_array_slicing.CudaArraySetting)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/gmarkall/numbadev/numba/numba/cuda/tests/cudadrv/test_cuda_array_slicing.py", line 273, in test_array_assign_all
    darr[:] = _400
  File "/home/gmarkall/numbadev/numba/numba/cuda/cudadrv/devices.py", line 224, in _require_cuda_context
    return fn(*args, **kws)
  File "/home/gmarkall/numbadev/numba/numba/cuda/cudadrv/devicearray.py", line 570, in __setitem__
    return self._do_setitem(key, value)
  File "/home/gmarkall/numbadev/numba/numba/cuda/cudadrv/devicearray.py", line 628, in _do_setitem
    _assign_kernel(lhs.ndim).forall(n_elements, stream=stream)(lhs, rhs)
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 438, in __call__
    kernel = self.kernel.specialize(*args)
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 990, in specialize
    specialization = Dispatcher(self.py_func, [types.void(*argtypes)],
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 868, in __init__
    self.compile(sigs[0])
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 1055, in compile
    kernel = _Kernel(self.py_func, argtypes, link=self.link,
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 481, in __init__
    cres = compile_cuda(self.py_func, types.void, self.argtypes,
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/home/gmarkall/numbadev/numba/numba/cuda/compiler.py", line 157, in compile_cuda
    cres = compiler.compile_extra(typingctx=typingctx,
  File "/home/gmarkall/numbadev/numba/numba/core/compiler.py", line 675, in compile_extra
    return pipeline.compile_extra(func)
  File "/home/gmarkall/numbadev/numba/numba/core/compiler.py", line 419, in compile_extra
    return self._compile_bytecode()
  File "/home/gmarkall/numbadev/numba/numba/core/compiler.py", line 483, in _compile_bytecode
    return self._compile_core()
  File "/home/gmarkall/numbadev/numba/numba/core/compiler.py", line 462, in _compile_core
    raise e
  File "/home/gmarkall/numbadev/numba/numba/core/compiler.py", line 453, in _compile_core
    pm.run(self.state)
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_machinery.py", line 339, in run
    raise patched_exception
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_machinery.py", line 330, in run
    self._runPass(idx, pass_inst, state)
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_lock.py", line 35, in _acquire_compile_lock
    return func(*args, **kwargs)
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_machinery.py", line 289, in _runPass
    mutated |= check(pss.run_pass, internal_state)
  File "/home/gmarkall/numbadev/numba/numba/core/compiler_machinery.py", line 262, in check
    mangled = func(compiler_state)
  File "/home/gmarkall/numbadev/numba/numba/core/typed_passes.py", line 105, in run_pass
    typemap, return_type, calltypes, errs = type_inference_stage(
  File "/home/gmarkall/numbadev/numba/numba/core/typed_passes.py", line 83, in type_inference_stage
    errs = infer.propagate(raise_errors=raise_errors)
  File "/home/gmarkall/numbadev/numba/numba/core/typeinfer.py", line 1071, in propagate
    raise errors[0]
numba.core.errors.TypingError: Failed in cuda mode pipeline (step: nopython frontend)
No implementation of function Function(<intrinsic to_fixed_tuple>) found for signature:

 >>> to_fixed_tuple(array(int64, 1d, C), Literal[int](2))

There are 2 candidate implementations:
     - Of which 2 did not match due to:
     Intrinsic in function 'to_fixed_tuple': File: numba/np/unsafe/ndarray.py: Line 41.
       With argument(s): '(array(int64, 1d, C), int64)':
      Rejected as the implementation raised a specific error:
        KeyError: <class 'numba.core.extending_hardware.CUDA'>
  raised from /home/gmarkall/numbadev/numba/numba/core/registry.py:99

During: resolving callee type: Function(<intrinsic to_fixed_tuple>)
During: typing of call at /home/gmarkall/numbadev/numba/numba/cuda/cudadrv/devicearray.py (452)

File "numba/cuda/cudadrv/devicearray.py", line 452:
    def kernel(lhs, rhs):
        <source elided>

        lhs[to_fixed_tuple(idx[0], ndim)] = rhs[to_fixed_tuple(idx[1], ndim)]
        ^

@stuartarchibald Now that master is fixed, this PR is working locally for me again - I've merged in master too.


bug: Incorrect behavior when parsing versions with a hyphen

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.9.1
Operating system/version
Arch Linux
Describe the bug
Lazy.nvim seems to struggle to detect the latest version if the version string contains a hyphen. For example, take the following version strings: 1.2.3 and 1.2.3-1. Currently, Lazy.nvim thinks that 1.2.3-1 < 1.2.3 when it should actually be the other way around.
This is the plugin and the versions that are being problematic:

https://github.com/phpactor/phpactor/releases/tag/2023.06.17
https://github.com/phpactor/phpactor/releases/tag/2023.06.17-1
https://github.com/phpactor/phpactor/releases/tag/2023.06.17-2

Steps To Reproduce
(See above)
Expected Behavior
The version comparison in Lazy.nvim should come to the following conclusion: 2023.06.17 < 2023.06.17-1 < 2023.06.17-2 thus offer to update to the true latest instead of just 2023.06.17.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

This is incorrect. According to the semver spec, 1.2.3-1 is version 1.2.3 pre-release 1.
Version 1.2.3 is indeed higher than any pre-release version like 1.2.3-1

See the part of the spec here: https://semver.org/#spec-item-9

A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.--.


Updated coverage report guide to include parameter for ES6

This solves #235.
@zinserjan : This option works with require statement as well.

Codecov Report

Merging #241 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #241   +/-   ##
=======================================
  Coverage   96.99%   96.99%
=======================================
  Files          28       28
  Lines         765      765
=======================================
  Hits          742      742
  Misses         23       23

Continue to review full report at Codecov.

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


Launcher can get stuck flipping between two sets of Arcs tiles.

FYI @sjmiles perhaps not worth fixing until storage work is enabled but filing as FYI.
To repro:

Open an incognito tab and visit https://polymerlabs.github.io/arcs-live/shell/apps/web/
Wait until the launcher page loads and settles and tiles are visible
Click the gear icon in bottom popup, click the profile icon, choose 'Walt'
Don't click again (leave the popup open). Wait a bit. Eventually you should start seeing the tiles behind the partially opaque background start flipping between two sets. I saw this on both desktop and mobile.

It flips between a few different tile displays, and if you leave it long enough it appears to eventually settle on the correct end state. It can take a full minute or so. Several sample states attached.


Allow indirect calls to be added to a buffer (and be executed in batches, in intervals)

Indirect calls, discovered from syncing with the parent chain, should have the option to be executed in batches. Up until now, these calls are always being executed immediately. A new buffer trait will probably make sense (if not already introduced in #404 or #417), and the TOP pool will implement this trait.
This should be an option, in addition to executing the indirect calls immediately. Switching between these two options should be possible (what kind of switch exactly is tbd).
Blocked by #404 and #417
Discovered during discussions of #247

all TrustedCalls of one parentchain block should be scanned into a buffer and executed as a batch.
In the future, it should be possible to add the batch of TrusteCalls to the top pool, but for now, we execute then right when we sync the parentchain block
If added to the pool, the ordering of TrustedCalls must be strictly protected. No direct calls in between

Linking this issue to #616

Closed by #755


[Azure.Monitor.Ingestion] Rename Options for GA

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

https://apiview.dev/Assemblies/Review/fcac040265704824b91b26b947e72823

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Monitor.Ingestion

azp run net - Azure.Monitor.Ingestion - tests

./azp run net - Azure.Monitor.Ingestion - tests


[Web] Fix splash screen background color in HTML shell

Info
I would like to propose a small amendment to the new splash screen related to the background color. My first version used #38363A which came from the div #status-progress of the previous splash screen, but to be consistent with other exporters, the correct background color should be the same as the default application/boot_splash/bg_color from Project Settings, which is #242424.
main/main_builders.py
# Use a neutral gray color to better fit various kinds of projects.
g.write("static const Color boot_splash_bg_color = Color(0.14, 0.14, 0.14);\n")

Difference
Before:

After:

Notes
In the future, it may be possible to pass information to the HTML shell about user settings such as application/boot_splash/bg_color or application/boot_splash/show_image. For now, we can add information in the documentation that it is easy to modify the background color by typing CSS in the Head Include field:
<style>
#status { background: radial-gradient(circle, rgba(15,15,121,1) 0%, rgba(25,224,56,1) 100%); }
</style>

Similarly, you can hide the splash image by typing:
<style>
#status-splash { display: none; }
</style>

Thanks!


regions plugin: support max regions

I've been heavily using the regions plugin in a project i'm playing with.  One feature I definitely needed (for my UI's sanity) was to limit the number of regions a user could create (to 1, in my case).

documented

Coverage remained the same at 80.859% when pulling 89cbad319fbdcdc133dfc9471e42ea779f44f3a6 on osheroff:support_max_regions into 788ae67689783551a23b6882ec398e53342a1272 on katspaugh:master.


Java exception on first run with default options

When running tag 3.2.1 with the default options, I get the following error message:
(full log and error message: https://gist.github.com/MrFishFinger/3ac12a0c420cb1296395)
Any ideas what might cause this?
2015-12-22 16:45:29.595:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@1324409e{/idp,[file:///tmp/jetty-<IP_ADDRESS>-8443-webapp-_idp-any-7429767275020554732.dir/webinf/, file:///opt/shibboleth-identity-provider-3.2.1/webapp/],AVAILABLE}{/opt/shibboleth-idp/webapp/}
2015-12-22 16:45:29.687:INFO:oejs.ServerConnector:main: Started ServerConnector@74742430{HTTP/1.1,[http/1.1]}{<IP_ADDRESS>:8080}
Exception in thread "main" MultiException[java.io.IOException: keystore password was incorrect, java.lang.IllegalStateException: no valid keystore]
  at org.eclipse.jetty.server.Server.doStart(Server.java:347)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1510)
  at java.security.AccessController.doPrivileged(Native Method)
  at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
  Suppressed: java.lang.IllegalStateException: no valid keystore
    at org.eclipse.jetty.util.security.CertificateUtils.getKeyStore(CertificateUtils.java:48)
    at org.eclipse.jetty.util.ssl.SslContextFactory.loadKeyStore(SslContextFactory.java:1020)
    at org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:336)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
    at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
    at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
    at org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
    at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
    at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
    at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:260)
    at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
    at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
    at org.eclipse.jetty.server.Server.doStart(Server.java:384)
    ... 4 more
Caused by: java.io.IOException: keystore password was incorrect
  at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:2015)
  at java.security.KeyStore.load(KeyStore.java:1445)
  at org.eclipse.jetty.util.security.CertificateUtils.getKeyStore(CertificateUtils.java:52)
  at org.eclipse.jetty.util.ssl.SslContextFactory.loadKeyStore(SslContextFactory.java:1020)
  at org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:336)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
  at org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
  at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
  at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:260)
  at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
  at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
  at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
  at org.eclipse.jetty.server.Server.doStart(Server.java:384)
  ... 4 more

Yeah, go through the whole readme... You can't run it with only the default options unless your keys use the password of "changeme" or you include the passwords in idp-secrets.properties. You'll also need to generate a .p12 for the browser based TLS communications, if you haven't already.
Otherwise you'll need to update the various jetty-ssl .xml  files to use a jks file or remove crypto altogether.

ok my bad, i did not read that far into the document! :) - I will have another look at it tomorrow

Can't blame you, it's definitely a TLDR document.

Hi John,
Sorry to be a pain with this.  I had this running previously with the
credentials and passwords externalized like in the readme.  After getting
the latest image built and able to run I now get this error.
Exception in thread "main" MultiException[java.io.IOException: keystore
password was incorrect, java.io.IOException: keystore password was
incorrect]
at org.eclipse.jetty.server.Server.doStart(Server.java:347)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1510)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1435)
Suppressed: java.io.IOException: keystore password was incorrect
at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:2015)
at java.security.KeyStore.load(KeyStore.java:1445)
at
org.eclipse.jetty.util.security.CertificateUtils.getKeyStore(CertificateUtils.java:52)
at
org.eclipse.jetty.util.ssl.SslContextFactory.loadKeyStore(SslContextFactory.java:1020)
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:336)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:260)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:384)
... 4 more
Caused by: java.security.UnrecoverableKeyException: failed to decrypt safe
contents entry: javax.crypto.BadPaddingException: Given final block not
properly padded
... 21 more
Caused by: java.io.IOException: keystore password was incorrect
at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:2015)
at java.security.KeyStore.load(KeyStore.java:1445)
at
org.eclipse.jetty.util.security.CertificateUtils.getKeyStore(CertificateUtils.java:52)
at
org.eclipse.jetty.util.ssl.SslContextFactory.loadKeyStore(SslContextFactory.java:1020)
at
org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:336)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:64)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:260)
at
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
at
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:384)
... 4 more
Caused by: java.security.UnrecoverableKeyException: failed to decrypt safe
contents entry: javax.crypto.BadPaddingException: Given final block not
properly padded
... 21 more
Do I need to redo the init script to build credentials everytime the
underlying unicon/shibboleth-idp image changes?
Thanks
Travis
On Tue, Dec 22, 2015 at 8:57 AM MrFishFinger<EMAIL_ADDRESS>wrote:

ok my bad, i did not read that far into the document! :) - I will have
another look at it tomorrow
—
Reply to this email directly or view it on GitHub
https://github.com/Unicon/shibboleth-idp-dockerized/issues/10#issuecomment-166673028
.

Hi @tsschmi,
You should not and generally don't want to re-run that init script as you'll essentially be changing the identity of your IdP by creating new signing, encryption, and backchannel keys.
So what was the image tag/version this was working under? And just to confirm you are using the latest (as of this morning) 3.2.1?

@MrFishFinger and @tsschmi,
I'd recommend checking out https://github.com/UniconLabs/dockerized-idp-testbed, if you haven't already. It's a full working IDP, SP, and LDAP server that runs under docker-compose. I update the idp/Dockerfile with the version of the base image I want to test and then call docker-compose build and then docker-compose up and can watch everything spin up nicely. Browse to https://idptestbed/ (after setting up an etc/hosts file entry, and you can login with staff1 and password.  ctrl+c then docker-compose rm cleans everything up to try again.
I'd recommend cloning this and make sure you can get this to work. Then you can create your setup modeled after mine. You likely won't need the ldap image if you can just point at your organizations LDAP, but the rest will fit in well.

many thanks for the pointer to the testbed John, and many thanks for creating and maintaining this repo/docker image - it makes getting a test shibboleth environment setup much less painful!
i was eventually able to build a functioning testbed using docker-compose - although i ran into a docker AUFS bug when using an Ubuntu host to build the httpd-proxy image. Switching to a CentOS docker host to build the images got me around that.
Now the fun with attempting to get this to integrate with o365 for a PoC begins... urghh

You are very welcome! Please enjoy it. My Unicon IAM team and I just completed a code review and have just a few minor tweaks to make... just minor cosmetic things, but if you find any other problems or have suggestions, then please submit them. :)
As for O365, good luck. I've done it several times for clients and it really isn't that bad. If you get stuck, you might consider looking into a Shibboleth Open Source Support program subscription (https://unicon.net/opensource/shibboleth) from Unicon or just a general Shib consulting SOW.
(Thanks for listening to the sales pitch. The Shibboleth OSS program actually funds my work to produce this work.)

I think I have my bad keystore password issues figured out.   I think it
had to do with enabling root passwd yesterday so I could get docker-compose
to install on my machine(Still not sure why that was needed).  I did this
shortly before your upgrade was pushed.
The behavior I saw was that with root passwd on, I could setup external
idp-secrets.properties maybe once and it would work.  If i stopped and ran
again it would throw the bad password error.  If I renamed the mounted
volume from ext-conf -> my-conf, it would work once, and then stop.  After
disabling root passwd, this problem seems to have been resolved.
Thanks for the help.
Travis
On Tue, Dec 22, 2015 at 1:52 PM John Gasper<EMAIL_ADDRESS>wrote:

You are very welcome! Please enjoy it. My Unicon IAM team and I just
completed a code review and have just a few minor tweaks to make... just
minor cosmetic things, but if you find any other problems or have
suggestions, then please submit them. :)
As for O365, good luck. I've done it several times for clients and it
really isn't that bad. If you get stuck, you might consider looking into a
Shibboleth Open Source Support program subscription (
https://unicon.net/opensource/shibboleth) from Unicon or just a general
Shib consulting SOW.
(Thanks for listening to the sales pitch. The Shibboleth OSS program
actually funds my work to produce this work.)
—
Reply to this email directly or view it on GitHub
https://github.com/Unicon/shibboleth-idp-dockerized/issues/10#issuecomment-166740318
.

Excellent!
I'll close this out.

@jtgasper3
Thanks for the info John and its good to know that there are Shibboleth paid support options out there. If we end up implementing it in our environment, I will definitely speak to my manager about potentially getting a proper support arrangement.
However unfortunately Shibboleth may actually not be suitable for our requirements, as its support for o365 'Email-rich client logins' is quite limited - ie no Android or modern Outlook/Lync/SkypeForBusiness support. It seems like it would only work on clients that can handle a SAML login through a webpage. Sigh..

@MrFishFinger,
Those instructions are a bit dated, while the implementation process is technically accurate, it makes some broad statements that not necessarily true anymore. The ECP/PAOS profile supports Outlook and ActiveSync (iOS and Android) just fine. Older versions of Lync do have issues with Shib, but Microsoft is implementing "ADAL" which makes SAML support first class for its thick clients. I haven't implemented a Shibboleth/Office 365 integration for a client in a while, but depending upon your thick client environment, the Shib IdP could very well still be a viable solution.
Do some Googling on "ADAL" and "office 365".

For anyone wondering, here's an easy way to generate the idp-browser.p12, which is required to run the service for local use (of course, the browser complains about the self-signed cert):
openssl genrsa -out idp.key 2048
openssl req -new -x509 -nodes -sha1 -days 7305 -key idp.key -out idp.crt
openssl pkcs12 -export -in idp.crt -inkey idp.key -out idp-browser.p12

For me it was not obvious from the descriptions that idp-browser.p12 is mandatory to start the service and that I have to set a password and use JETTY_BROWSER_SSL_KEYSTORE_PASSWORD.
There is a typo in the Browser-based TLS Certificate and Key description: " mounted directials directory"
After some hours of wondering and trying I have a runnig server :)

Hi @jtgasper3 ,
You're welcome.
I was thinking to move the TLS Certificate generation up to the "mandatory" part, like https://github.com/Unicon/shibboleth-idp-dockerized/pull/54 .


Resolution procedure changes

NOTE: These rules are not set in stone so work cannot proceed. Specifically, we don't know how we want to respond to timing changes.

If an event is moved to a future date then its markets should resolve as No Contest. Have to check event time stability.
Only resolve an event if its scores are stable.
Resolve all events that should be resolved, not just those that finished in the past few days.

NOTE: This must include the resolution timestamp in a public method so the UI can get that information.

Depends on #818

@robert-e-davidson3 what's the status of this, should we move it to another column or close it

@namankumar We've only done the third subtask so there's still work to do here.


[HOLD for payment 2023-03-13] [$1500]  Clicking on the send icon on the compose box closes the Keyboard on mweb chrome, but doesn’t close the keyboard on android

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open Staging dot on Chrome on MWEB
Go to a chat
Click on Chatbox and donot write any message
A keyboard appears. Now, click on the send icon present on the right side of the emoji picker on chatbox
Result : It closes the keyboard. But, if I follow the same process on ANDROID, it doesn’t close the keyboard upon clicking the send icon. Thus, there isn’t consistency between MWEB CHROME & ANDROID

Expected Result:
Clicking on send icon on the chatbox that has no messages shouldn’t close the keyboard on MWEB Chrome. It should be consistent with android where clicking on send icon doesn’t close the keyboard.
Actual Result:
Clicking on send icon on the chatbox that has no messages closes the keyboard on MWEB Chrome
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

mWeb google chrome (Android & iPhone)

Version Number: 1.2.70-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/218237093-e6419485-42e0-4b25-8f2c-1e242d221cab.mp4
https://user-images.githubusercontent.com/43996225/218237101-4a5fc09e-a260-4cc3-911a-a9e8aabc1952.mp4
Expensify/Expensify Issue URL:
Issue reported by: @avi-shek-jha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1676004421814629
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~014ae1eefc051023c1
Upwork Job ID:<PHONE_NUMBER>673512960
Last Price Increase: 2023-03-16

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@michaelhaxhiu Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

Will prioritize today

@michaelhaxhiu Huh... This is 4 days overdue. Who can take care of this?

Sorry, got pulled into numerous ECX items and wasn't able to test yet. Not good. Tomorrow morning first thing!

This bug is valid and reproducible on iOS and Android. It's a small bug but could be polished.
If you tap send (and there's no message in the textbox to send), I am a tiny bit conflicted on whether the better behavior is to (A) collapse the keyboard like we do today or (B) do nothing. I think I lean toward do nothing to keep it consistent with other themes.

Job added to Upwork: https://www.upwork.com/jobs/~014ae1eefc051023c1

Current assignee @michaelhaxhiu is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

Triggered auto assignment to @nkuoch (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Clicking on the send icon on the compose box closes the Keyboard on mweb chrome, but doesn’t close the keyboard on native
What is the root cause of that problem?
So on mWeb the keyboard will close anytime you touch anywhere outside the keyboard as that takes the focus away from the composer which I think is what the expected behaviour should be because that's what users normally expect to dismiss a keyboard.
What changes do you think we should make in order to solve the problem?
We can prevent the default behaviour of taking the focus away from the composer only when send is clicked by the following:

Remove the disabled prop & just make the button appear as disabled by using the disabled styles as per the same condition used for disabled.
Intercept the presses in onPress event using the same condition as above & prevent the default press behaviour.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Clicking on send icon on the chatbox that has no messages closes the keyboard on Chrome MWeb
What is the root cause of that problem?
When the composer is empty, the Send button will be disabled and will not receive onMouseDown event. We already have a logic in onMouseDown to prevent the keyboard from being closed when clicking Send in https://github.com/Expensify/App/blob/f6c2172e7643c4b256711738eda60a0c7cd96859/src/pages/home/report/ReportActionCompose.js#L697
But this is not triggered when the Send button is disabled.
What changes do you think we should make in order to solve the problem?

We need to move that e.preventDefault logic inside the View that wraps the Send button instead so that it will preventDefault in all case (no matter whether the Send button is disabled or not). In here:
https://github.com/Expensify/App/blob/f6c2172e7643c4b256711738eda60a0c7cd96859/src/pages/home/report/ReportActionCompose.js#L686
What alternative solutions did you explore? (Optional)
NA

@nkuoch @michaelhaxhiu @mollfpr this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

Thank you guys for the proposals!
@priyeshshah11 Removing the disabled prop will make the button have the touch effect; I don't think we want that.

@nkuoch I think @tienifr proposal work well. Moving the onMouseDown to the view wrapper seems straightforward; the onMoseDown will be called even if the send button is disabled.
🎀 👀 🎀 C+ reviewed!

📣 @tienifr You have been assigned to this job by @nkuoch!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Regression Test Proposal
Bug: Screen is flashing when changing focus between edit input
Proposed Test Steps:

Open the app on mWeb
Go to a chat
Click on Chatbox (don't write anything)
Then the keyboard appears. Now, click on the send button on the chatbox
Verify that it doesn’t close the keyboard upon clicking the send icon.
Do 5 above steps again on Android and verify that it is consistent between MWEB CHROME & ANDROID

Do we :+1: or :-1:

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.2.78-0 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/15554

If no regressions arise, payment will be issued on 2023-03-13. :confetti_ball:
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

[ ] External issue reporter
[ ] Contributor that fixed the issue
[ ] Contributor+ that helped on the issue and/or PR

As a reminder, here are the bonuses/penalties that should be applied for any External issue:

Merged PR within 3 business days of assignment - 50% bonus
Merged PR more than 9 business days after assignment - 50% penalty

@nkuoch, @michaelhaxhiu, @mollfpr, @tienifr Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@mollfpr I invited you to the same upwork job

Appliedy, thank you!

Upwork job price has been updated to $2000

Please work on finishing the checklist  above so we can close this.
Payment:
@mollfpr = paid
@tienifr = not paid
@avi-shek-jha = not paid

@michaelhaxhiu I think the job should be $1500, including the bonus, not $2000.

Upwork job price has been updated to $1500

Oopsie, my mistake. Fixing.

@michaelhaxhiu the reporting bonus is I guess 250 dollars. Can you please confirm once? Thank you

📣 @avi-shek-jha! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

 Thank you for contributing to Expensify!

Please my upwork job invite. I have updated the price for you, so that we can do it all under 1 job.

@michaelhaxhiu accepted the offer. Thank you

@michaelhaxhiu I submitted the work for review.

@nkuoch @michaelhaxhiu I don't find any PR that introduces this issue. We find a similar issue https://github.com/Expensify/App/issues/7798. The PR is not introducing this issue, but the solution still needs to cover this issue. So this issue has been around for a long time.

@michaelhaxhiu I've applied, thanks!

Also @tienifr I just hired you in upwork this morning, and need you to confirm once more :)

@michaelhaxhiu accepted, thanks!

TY you are totally correct, I spaced on that. Updated 😄 .