Addi : Inside JS : 4 weeks

my fork of module repository

Learning Objectives
0. Asserting

Skills:

[x]  Predicting Execution: You can use the browser's debugger to step
through your code. Before each step you can make a prediction about what
will happen, after each step you can check your prediction.
[x]  Assertion Testing: You can write assertion tests to predict what
values will be in your program at a specific step of execution.

Language Features

[x]  Comments: You can write clear, helpful comments and can explain
different ways comments can be used in a program.
[x]  Strings: You can write and read string values in a program.
[x]  let vs. const: You can explain the differences between let
and const including: uninitialized declarations and reassignment.
You can determine when a variable can be assigned with const in a
program.
[x]  Strict Comparison: You can explain how the === and !==
operators compare strings, and can predict the result of any string
comparison.
[x]  console.log: You can use console.log to create program traces
in the console, and to print other helpful info for developers.
[x]  console.assert: You can use the console.assert for assertion
testing, and can write a helpful message assertion message.

1. Primitives and Operators

Skills:

[x]  Predicting Truthiness: You can predict the truthiness of any
primitive value.
[x] Tracing Operators: You can use an operators trace table to
evaluate expressions with more than one operator, and you can check your
work with the [trace] button.

Language Features

[x]  Primitive Types: You can explain the difference between the 5
main primitive types (string, number, boolean, null,
undefined) and what they are used for in a program.
[x]  typeof: You can predict the typeof operator's output for
values from any of the 5 main primitive types.
[x]  Explicit Coercion: You can predict & check the outputs when using
Boolean(), String() and Number() to convert between primitive
types.
[ ]  Truthiness Operators: You can explain how truthiness is used
when evaluating &&, ||, ! and ? :.
[ ]  Short-Circuiting: You can write an example that demonstrates how
short-circuiting works with && and ||.
Implicit Coercion:

[ ]  You can explain what implicit coercion is and how it can cause
problems in your programs.
[ ]  You can explain the rules for implicit coercion in common operators
such as +, ! and >.

[x]  Comparisons: You can predict and check the result of any
primitive comparison.
[ ]  Template Literals: You can read and trace multi-line template
literal strings.
[ ]  Statements vs. Expressions: You can identify if a piece of code
is a statement or an expression.
[ ]  Arithmetic: You can use JavaScript to do math, and can explain or
debug your expressions when they evaluate to something unexpected.

2. Control Flow

Skills:

[ ]  Imperative Programming: You can define the imperative
programming paradigm and can explain how you know the programs in this
chapter are imperative.
Writing Interactive Programs: For programs that take a string from
users:

[x]  Blanks: You can complete a program by filling in the blanks.
[x]  Bugs: You can fix bugs in an otherwise complete program.
[ ]  Goals: You can write the missing portion of a program.
[ ]  Empty Page: You can develop a program with specific behavior
starting from an empty page.

[ ]  User Numbers: You can complete, debug and write programs that
cast user input from string to number.
Stateful Programs: You can step through, debug and complete
programs with an HTML/CSS interface that store user data in a variable
between interactions.
Refactoring Control Flow:

[ ]  Conditionals: You can refactor between truthiness operators and
if/else statements.
[ ]  Loops: You can either refactor between all loop types, or
explain when it is not possible (or a good idea).

Language Features: You are comfortable reading and tracing programs that
use ...

[ ]  Block Scope: You can show how block scope works using code
snippets and your browser's debugger.
[x]  Conditionals: You can predict and trace a program's path through
conditional statements.
[x]  While Loops: You can predict and trace simple programs that use
while loops.
[x]  for-of Strings: You can predict and trace simple programs that
iterate through the characters of a string using for-of.
[ ]  For Loops: You can explain how a for loops works by refactoring
simple for loops into while loops.
[ ]  Break: You can predict and trace simple programs that use
break.
[ ]  Continue: You can predict and trace simple programs that use
continue.

3. Functions

Skills:

[x]  Tracing: You can use the debugger to predict and check the
execution of small programs that use functions. This includes:
[x]  Test Cases: You can explain a simple function's behavior using
inputs & outputs.
[x]  Documenting Functions: You can write a JS Doc comment to describe
a function's behavior, inputs and outputs.

Language Features:

[ ]  ES6 Arrow Functions:

Defining a Function: You can show where a function is defined in a
program.
Parameters: You can find a function's parameters in it's definition
Return Statement: You can find the return statements in a function's
definition.
Calling a Function: You can show where a function called in a
program
Arguments: You can show the arguments passed to a function call.
Return Value: You can show how a function's return value is used
after the function call.

[ ]  Default Parameters: You can explain how default parameters work,
and how they help a developer read/understand a function definition.
[ ]  The Callstack: You can explain and inspect the callstack using
the browser's debugger.
[ ]  Variables in Functions: You can explain three different ways a
variable in a function can be declared/assigned, and can show this in
the debugger:

Parameters: A parameter is assigned it's value when a function is
called with arguments.
Local Variables: A variable declared in the function's curly braces.
Parent Scope Variables: A variable that was declared outside of the
function but used inside the function (avoid this for now.)

5. Unit Testing

Skills:

[ ]  Testing Environments: You understand that the conventional
describe/it/expect.toEqual functions are defined by a testing
library and made available as global variables in a testing
environment. They are not part of JavaScript!
[ ]  File Sub-Extensions: You can identify how a file is used by it
sub-extension: file.__.js. Sub-extensions are a convention for
developers and development tools. They do not change how JavaScript
inside the file works.
[ ]  Reading Tests: You can read unit tests to understand what a
function is supposed to do.
[ ]  Stepping Through Tests: You can step through unit tests in the
debugger, stepping over the global testing functions and into the
function you are testing.
[ ]  Writing Tests: Given a working function, you can write passing
unit tests to describe it's behavior.
[ ]  Debugging Functions: Given working tests and a function with
small mistakes, you can use the tests as a guide while debugging the
function.
[ ]  Passing Tests: Given working unit tests and an empty function,
you can write code to pass the tests.

Language Features:

nothing new here!

6. ES Modules

Skills:

[ ]  Spec Files: You can work with functions and unit tests separated
into two files.
[ ]  Visualizing Dependencies: You can use the
VSCode Dependency Cruiser extension
and the ?deps lens to visualize the dependencies in a folder.
[ ]  Refactoring Tests: You can refactor a function and unit tests
from one file to two files: one with the function, one with the unit
tests.

Language Features:

[ ]  Module Files: Are always in strict mode by default, no more
'use strict'!
[ ]  Named Exports: You can export a variable and it's value using
export const _ = () => {};
[ ]  Named Imports: You can import a variable and it's value from
another file using import { _ } from './path/to/file.js';
[ ]  Module Life-Cycle: You understand that ES Modules are static,
and are evaluated at creation phase.

6. Using Functions

Skills:

[ ]  Procedural Programming: You can define the procedural
programming paradigm and can explain how you know the programs in this
chapter are procedural.
[ ]  Using Functions: You can use a pre-written functions in a
program.
[ ]  Writing Functions: You can write functions that are used in a
program.
[ ]  Refactoring Functions: You can refactor a function out of a
program and test the function separately.
[ ]  Reverse-Engineering: You can reverse-engineer an example program
and refactor parts of your program into separate functions.

Language Features:

Nothing new here!

7. Arrays

Skills:

[ ]  Reference vs. Value: You can explain how arrays are stored in
memory and can demonstrate using examples run in JS Tutor.
[ ]  Deep vs. Shallow Comparison: You can explain use the concept of
reference vs. value to explain how a deep comparison is different than a
shallow comparison.
Side-Effects: You can ...

[ ]  Explain what side-effects are with an example.
[ ]  Avoid side effects when writing your own functions.
[ ]  Write tests to check if a function has side-effects.
[ ]  Fix side-effects in buggy functions.

Integrating Arrays: You can work with programs that use arrays to store
user data:

[ ]  Call: You can call pre-written functions in a program:
[ ]  Write: You can write functions that are used in a pre-written
program.
[ ]  Refactor: You can refactor logic from a program into a separate
function. You can avoid side-effects and test your function.
[ ]  Reverse-Engineer: You can reverse-engineer a program,
refactoring logic to a separate function if necessary.

Stateful Programs: You can step through, debug and complete
programs with an HTML/CSS interface that store user data in an array between
interactions.

Language Features: You are comfortable reading and tracing programs that
use ...

[ ]  Array Literals: You can create a new array in your program with
initial values using the array literal syntax:
const arr = ['items'];
Adding and Removing Items: You can use these methods to add and
remove items in an array:
[ ] arr.push(): Adds a new item to the end of an array.
[ ] arr.pop(): Removes the last item in an array.
[ ] arr.shift(): Adds a new item to the front of an array.
[ ] arr.unshift(): Removes the first item in an array.
Reading Items: You can read items in an array using:
[ ] arr[i]: Access a specific item in an array using square brackets a
positive index.
[ ] arr.at(i): Access a specific item in an array using .at() and a
positive or negative index.
[ ]  Updating Items: You can update any item in an array using it's
index, square brackets and assignments: arr[4] = 'hello'.
Iterating Over Arrays:
[ ] for (const item of arr): You use for-of loops to iterate
forwards through an array.
[ ] for (let i = ...): You can use for loops to iterate forwards and
backwards through an array.
[ ]  Array.isArray(): You can use Array.isArray() to check if
something is an array: Array.isArray(something)
[ ]  Spread Syntax: you can use spread syntax to create a shallow
copy of an array: const shallowCopy = [...arr];

8. Functional Array Methods

Skills:

[ ]  Declarative Programming: You can define the declarative
programming paradigm and can explain how you know that code using
functional array methods is declarative.
Array Strategies: You can explain these array strategies using a
diagram or drawing:
[ ] Mapping: Modifying each item in an array and putting the results
in a new array.
[ ] Filtering: Creating a new array with only the items from the old
array that match some criteria.
[ ] Every Item: Checking if every item in an array matches some
criteria.
[ ] Some Items: Checking if at least one item in an array matches some
criteria.
[ ] Finding: Finding the first item in an array that matches some
criteria.
[ ] Reducing: Combining all the items in an array to create a single
result.
Using Callbacks: You can explain what a callback is, and can ...
[ ] Pass a callback into a higher-order function that consumes it.
[ ] Write a callback for a higher-order function to consume.
[ ] Consume callbacks in a higher-order function that you write.
[ ] Decide when to declare callbacks inline, and when to declare them
separately.
[ ]  Debugging Functional Array Methods: You can step through code
that uses functional array methods in your debugger, and can use the
scopes panel to explain what is happening behind the scenes.

Language Features:

Array Methods: You can read and trace code that uses these array
methods, you can also use them to solve simple coding challenges:

[ ] 🥚 [].every
[ ] 🥚 [].some
[ ] 🐣 [].map
[ ] 🐣 [].filter
[ ] 🐣 [].find
[ ] 🐥 [].reduce

[ ] 🐣 Higher-Order Functions: You can explain what a higher order
function is using a simple example.
[ ] 🐥 Implicit Returns: You understand when a function can be written
with an implicit return and can decide if it makes your code more or
less readable.

9. Multiple Interactions

Skills:

[ ] 🥚 Avoiding Side Effects: You can read, debug and write functions
that use objects as arguments, without creating side-effects.
🐣 Stateful Programs: You can step through, debug and complete
programs with an HTML/CSS interface that store user data in an object
between interactions.

Language Features:

[ ] 🥚 Object Literals: You can declare a new object with initial
key/value pairs using object literal syntax:
const obj = { a: 1, b: 2 };.
[ ] 🐣 Dots vs. Brackets: You can explain the difference between dot
and bracket access in an object and can decide which one is best in
your code.
[ ] 🐣 Reference vs. Values: You can show that objects are stored by
reference with an example that modifies one object from two variables.

Week 1
I Need Help With
Nothing right now.
What went well?
Everything is ok!
What went less well?
all good for now
Lessons Learned

@AddiAlomoush where is your check-in for week 2?


For loop list a conflicting values

What version of CUE are you using (cue version)?

$ cue version
cuelang.org/go v0.4.3

Does this issue reproduce with the latest release?
What did you do?

params: #input
uiSchema: {}
#input: {
	name: string
	appName: string
	appEnv: string
	namespace: *"system" | string
	workspace: params.appName + params.appEnv | string
	triggers: {
		...
	}
	stages: [...{
		name: string
		customParams: {
			...
		}
		jobs: [...{
			id?: int
			created_at: string
			updated_at: string
			name: string
			stepType: string
			params: {
				...
			}
			image: string
		}]
	}]

}
output: {
	apiVersion: "tekton.dev/v1beta1"
	kind:       "Pipeline"
	metadata: {
		name:      params.appName + params.appEnv
		namespace: params.namespace
	}
	spec: {
		workspaces: [{
//			name: "git-credentials"
//			description: "ssh credentials"
			name: "healthtest"
			description: "This workspace contains the cloned repo files, so they can be read by the next task"
		}]
		"params": [
			for stage in params.stages {
				if stage.customParams != _|_ {
				  for key, value in stage.customParams {
						{
							name: key
							default: value
						}
					}
				}
			}
		]
		tasks: [
			{
					name: "fetch-source"
					taskRef:
						name: "git-clone"
					workspaces: [{
						name: "output"
						workspace: "healthtest"
		//      	name: "ssh-directory"
		//      	workspace: "git-credentials"
					}]
					"params": [
					 for stage in params.stages {
							for key, value in stage.customParams {
								{
									name: key
									value: "$(params." + key + ")"
								}
							}
					 }
					]
			},
			for i, stage in params.stages {
			  if i == 0 {
					for job in stage.jobs {
						{
							name: job.name
							runAfter: ["fetch-source"]
							taskRef:
								name: job.name
							workspaces: [{
								name: "output"
								workspace: "healthtest"
		//								name: "ssh-directory"
		//								workspace: "git-credentials"
							}]
							"params": [
								for key, value in stage.customParams {
									{
										name: key
										value: "$(params." + key + ")"
									}
								}]
						},
					}
				}
			  if i > 0 {
					for job in stage.jobs {
						{
							name: job.name
							runAfter: [
									for job in params.stages[i-1].jobs {
										job.name
									}
							]
							taskRef:
								name: job.name
							workspaces: [{
								name: "output"
								workspace: "healthtest"
		//								name: "ssh-directory"
		//								workspace: "git-credentials"
							}]
							"params": [
								for key, value in stage.customParams {
									{
										name: key
										value: "$(params." + key + ")"
									}
								}
							]
					  }
					}
			  }
			}
		]
	}
}

json
{
	"stages": [{
		"name": "test-1",
		"customParams": {
			"t": "2"
		},
		"jobs": [{
			"name": "make-code-1",
			"stepType": "execute_shell",
			"params": {
				"scriptType": "bash",
				"scriptContent": "#!/bin/bash \n ls -l /root\n pwd"
			},
			"image": "alpine:latest"
		}, {
			"name": "make",
			"stepType": "execute_shell",
			"params": {
				"scriptType": "bash",
				"scriptContent": "#!/bin/bash \n ls -l /root\n pwd"
			},
			"image": "alpine:latest"
		}]
	}, {
		"name": "test-2",
		"customParams": {
			"t3": "3"
		},
		"jobs": [{
			"name": "upload-oss-1",
			"stepType": "execute_shell",
			"params": {
				"scriptType": "bash",
				"scriptContent": "#!/bin/bash \n ls -l /root\n pwd"
			},
			"image": "alpine:latest"
		}, {
			"name": "upload-oss-2",
			"stepType": "execute_shell",
			"params": {
				"scriptType": "bash",
				"scriptContent": "#!/bin/bash \n ls -l /root\n pwd"
			},
			"image": "alpine:latest"
		}]
	}, {
		"name": "test-3",
		"customParams": {
			"a": "<IP_ADDRESS>"
		},
		"jobs": [{
			"name": "deploy",
			"stepType": "execute_shell",
			"params": {
				"scriptType": "bash",
				"scriptContent": "#!/bin/bash \n ls -l /root\n pwd"
			},
			"image": "alpine:latest"
		}]
	}],
	"name": "health-dev-flow",
    "appName": "health",
    "appEnv": "dev",
	"triggers": {
		"gitUrl": "1",
		"gitBranch": "1",
		"secretType": "pass",
		"secret": "jack"
	}
}

What did you expect to see?
  tasks:
  - name: show-readme
    runAfter: ["fetch-source"]
    taskRef:
      name: make-code-1
    workspaces:
    - name: source
      workspace: shared-data
    params:
    - name: t
      value: $(params.t)
    - name: t3
      value: $(params.t3)
    - name: a
      (value: $(params.a))

  - name: make
    runAfter: ["make-code-1"]
    taskRef:
      name: make
    workspaces:
    - name: source
      workspace: shared-data
    params:
    - name: t
      value: $(params.t)
    - name: t3
      value: $(params.t3)
    - name: a
      (value: $(params.a))

What did you see instead?
"err":"output.spec.tasks.1.name: conflicting values \"make\" and \"make-code-1\""}

I think breaking this down to something more simple would help you and other people trying to help.
So let's go with:
_stages: [{
    name: "s1"
    jobs: [
        { name: "j1" },
    ]
}, {
    name: "s2"
    jobs: [
        { name: "j2" },
    ]
}, {
    name: "s3"
    jobs: [
        { name: "j3"},
        // { name: "j4" }
    ]
}]

And a list populated by a comprehension:
tasks: [for stage in _stages {
    for job in stage.jobs {
        name: job.name
    }
}]

So far so good:
tasks:
  - name: j1
  - name: j2
  - name: j3

However, when uncommenting j4, the same error occurs:
tasks.2.name: conflicting values "j4" and "j3":

This is because of how the comprehension is written.
It's attempting to merge the values of _stages[2][0] and _stages[2][1] into tasks[2]; it is not creating a new element for each job at _stages[2]. Therefore, a conflict error occurs, as the names do not match.
Writing it like so works:
tasks: [for stage in _stages for job in stage.jobs {
        name: job.name
}]

tasks:
  - name: j1
  - name: j2
  - name: j3
  - name: j4

And finally with the conditionals:
tasks: [for i, stage in _stages for job in stage.jobs {
        name: job.name
        if i > 0 {
            runAfter: _stages[i-1].jobs
        }
}]

tasks:
  - name: j1
  - name: j2
    runAfter:
      - name: j1
  - name: j3
    runAfter:
      - name: j2
  - name: j4
    runAfter:
      - name: j2


HUE Problems with filters in Job Browser

i have some problems with filters in Job Browser.
For example, when i select all jobs in the last 1 day, i see, for example job id# 1000 and job id#1001, but when i change filter to select all jobs in the last 3 days I see no jobs.
Same behavior when i filter running jobs + last 1 day - All is OK, when i change to last 2..3....5...10...etc days nothing displays.

@demydovb I cannot reproduce this issue. Can you add a few screenshots that would show the issue?


Write design document for the Fission Server

The design document should be a blueprint that explains in details what the Fission Server is, and how we will build it.
It needs to capture and reflect the agreements and decisions coming from discussions that in Talk.
We can add a glossary as well to make sure everyone knows what we mean when using specific terms.
If you're ok with it, add it in this repository so that it lives in the same place as the code.

Merge or add a link to the open API spec

Some work on this by @expede: https://github.com/fission-codes/fission-server/blob/design-doc/design/README.md

We can add a glossary as well to make sure everyone knows what we mean when using specific terms.

I broke out a table at one point, but the main design/README.md is kind of like an expanded version of that, so cut it.

Merge or add a link to the open API spec

Has to wait for the code to be done. I'd suggest breaking this out as a separate Issue to keep things flowing. Arguably it's conceptually a separate step: prescriptive (pre hoc) vs descriptive (post hoc)


Fix Tough Claws

It gives a 30% boost, not 33%.

Putting this on hold. Marty is double-checking the calcs.

Marty confirmed the info, so I updated it to use the literal hex values he gave. They're the exact same as Aerilate's!

Should probably have the Auras use literal hex values as well.

Yay, Zard-X nerfed \o/


add workflows ci build and test

looks like the CI tests are filing because it isn't loading the libgodotgo-test-linux-amd64.so lib for some reason.... strange


[FEATURE] Do continuous docker image build on docker hub

Need to set up permissions with an automated bot account.

Done.


"Add choice" option on choice end

Like the add else and add elif, there could be an "Add Choice" button on the end of choices. That could be useful for quickly adding multiple choices on a question (usually you want more then 1)

I can take a look at trying to implement this once that problem I am having with the "Add Else" "Add Elif" buttons is solved.


Document using default OS account with WAM

Document changes introduced in https://github.com/Azure/azure-sdk-for-net/pull/39607. I cleaned up the README while I was in there too.

API change check
API changes are not detected in this pull request.


Can we add light version of video or a loading like animation in light property?

Can we add light version of video or a loading like animation in light property?

Check out https://github.com/cookpete/react-player/pull/1405


Support for function 43 / 14 Read Device Identification

@psztoch Would you mind to implement this?

I can try it. I'm learning rust, using modbus professionally and probably will implement that function in my c and c# modbus libs. I think that it will be good exercise.
Any hints where should i start?

I can try it.

awesome!

Any hints where should i start?

You can find an example described on page 43 in the Modbus Application Protocol Specification (PDF).

So here are some possible steps to implement it:

Define the Request & Response
Write test(s) with the given example
Implement the processing algorithm
Extend the public API

Hi.
Any chance to merge the read device identification function to the code?
Its stall since 2020.


Request for library removal

The library author has requested the following library to be removed, as it's been renamed quickly afterwards
https://lib.haxe.org/p/jStreamAPI-extern/

done


Error: "Invalid state" After successful login.

Description
As suggested here https://github.com/auth0/auth0-react/issues/49#issuecomment-651254746) I ran the basic sample app with my domain and clientId.
My management logs show Success Login and Success Exchange. Though in the webapp I'm not logged in. Error message there is Error: Invalid state
Full Error stack:
Inline Babel script:24 Error: Invalid state
    at e.<anonymous> (auth0-spa-js.production.esm.js:15)
    at auth0-spa-js.production.esm.js:15
    at Object.next (auth0-spa-js.production.esm.js:15)
    at auth0-spa-js.production.esm.js:15
    at new Promise (<anonymous>)
    at o (auth0-spa-js.production.esm.js:15)
    at e.handleRedirectCallback (auth0-spa-js.production.esm.js:15)
    at auth0-provider.tsx:196
    at step (auth0-react.js:95)
    at Object.next (auth0-react.js:76)
App @ Inline Babel script:24
renderWithHooks @ react-dom.development.js:14938
updateFunctionComponent @ react-dom.development.js:17169
beginWork @ react-dom.development.js:18745
beginWork$1 @ react-dom.development.js:23314
performUnitOfWork @ react-dom.development.js:22289
workLoopSync @ react-dom.development.js:22265
performSyncWorkOnRoot @ react-dom.development.js:21891
(anonymous) @ react-dom.development.js:11224
unstable_runWithPriority @ react.development.js:2685
runWithPriority$1 @ react-dom.development.js:11174
flushSyncCallbackQueueImpl @ react-dom.development.js:11219
flushSyncCallbackQueue @ react-dom.development.js:11207
scheduleUpdateOnFiber @ react-dom.development.js:21334
dispatchAction @ react-dom.development.js:15795
(anonymous) @ auth0-provider.tsx:203
step @ auth0-react.js:95
(anonymous) @ auth0-react.js:76
rejected @ auth0-react.js:67
Promise.then (async)
step @ auth0-react.js:68
(anonymous) @ auth0-react.js:69
__awaiter @ auth0-react.js:65
(anonymous) @ auth0-provider.tsx:192
(anonymous) @ auth0-provider.tsx:205
commitHookEffectListMount @ react-dom.development.js:19866
commitPassiveHookEffects @ react-dom.development.js:19904
callCallback @ react-dom.development.js:182
invokeGuardedCallbackDev @ react-dom.development.js:231
invokeGuardedCallback @ react-dom.development.js:286
flushPassiveEffectsImpl @ react-dom.development.js:22988
unstable_runWithPriority @ react.development.js:2685
runWithPriority$1 @ react-dom.development.js:11174
flushPassiveEffects @ react-dom.development.js:22955
(anonymous) @ react-dom.development.js:22834
workLoop @ react.development.js:2629
flushWork @ react.development.js:2584
performWorkUntilDeadline @ react.development.js:2196

Reproduction
I changed index.html to following:
<!DOCTYPE html>

    <meta charset="UTF-8" />
    <meta
      name="viewport"
      content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0"
    />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Auth0 React</title>

Hi @puengel
Even though we're sending openid as a scope to /authorize - I'm not seeing an id_token in the response.
Dp you perhaps have a custom rule in your tenant? One that might change the requested scope?

Hi @adamjmcgrath ,
I really had some rule which was causing this issue.

Closing this issue. Thanks for your help.

I'm having this same issue over the last two days. Same behavior as mentioned above: the user is directed to the lock login page, redirected back to the app, user authentication is never returned.  There are no rules in our app so the above solution does not apply.

{
"date": "2020-07-05T03:13:29.663Z",
"type": "s",
"connection_id": "",
"client_id": "7o21rTYAsoK0xKec9UxK2olZppzy7j56",
"client_name": "",
"ip": "<IP_ADDRESS>",
"user_agent": "Chrome 83.0.4103 / Windows 10.0.0",
"details": {
"prompts": [],
"completedAt":<PHONE_NUMBER>662,
"elapsedTime": null,
"session_id": "X6LOaGTzDP35GD7I9HjGm57iH5wqhLtz"
},
"hostname": "",
"user_id": "auth0|5efce1eda15b7b001361c588",
"user_name": "",
"auth0_client": {
"name": "auth0-react",
"version": "1.0.0"
},
"log_id": "90020200705031335800043426049758653529361151510378971138",
"_id": "90020200705031335800043426049758653529361151510378971138",
"isMobile": false,
"description": "Successful login"
}
"prompts": [],
"completedAt":<PHONE_NUMBER>662,
"elapsedTime": null,
"session_id": "X6LOaGTzDP35GD7I9HjGm57iH5wqhLtz"
}
This has been a very disappointing way of spending the holiday weekend. :(

Have you guys figured this out?


python310Packages.poetry-plugin-export: 1.3.0 -> 1.3.1

https://github.com/python-poetry/poetry-plugin-export/blob/refs/tags/1.3.1/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 227887 run on x86_64-linux 1

10 packages built:

poetry
poetry.dist
poetryPlugins.poetry-audit-plugin
poetryPlugins.poetry-audit-plugin.dist
poetryPlugins.poetry-plugin-up
poetryPlugins.poetry-plugin-up.dist
python310Packages.poetry-plugin-export
python310Packages.poetry-plugin-export.dist
python311Packages.poetry-plugin-export
python311Packages.poetry-plugin-export.dist


multiple bug fixes and stability fixes

SUMMARY
this PR is solving a variety of issues

incorrect workshop type being reported (would say Linux for everything, even if f5 or networking)
f5 lab bugs, wouldn't configure hosts correctly
unnecessarily gathering facts on ansible control nodes
SSL intermediate cert issues
if you already SSL certed your tower instances, it will skip that section on subsequent runs

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
multiple, see file diff
ADDITIONAL INFORMATION
N/A
linking to https://github.com/network-automation/linklight/pull/177, this "should" fix this, but if it doesn't i will accept both since it won't hurt anything

@kyleabenson @termlen0 @gdykeman
anyone got any problems with this merge?  only 9 miles, main fix is for SSL cert, we need something called an intermediate cert so that all browsers and api requests to tower will think it is legit, this should solve the tower_verify_ssl issues... although it might make sense to merge that PR regardless

@IPvSean these changes look good to me but I haven't tested them. Will spin up a lab today and see if it looks good.

from @gdykeman
TASK [Print Summary Information] ***********************************************
ok: [localhost] =>
  msg: |-
    PROVISIONER SUMMARY
    *******************
    - Workshop name is certcheck
    - Instructor inventory is located at  /home/ec2-user/linklight/provisioner/certcheck/instructor_inventory.txt
    - Private key is located at /home/ec2-user/linklight/provisioner/certcheck/certcheck.pem
    - Website created at http://certcheck.redhatgov.io

    FAILURES
    *******************
    No errors with DNS


[Leduc Holdem] Fix a bug when folding in the first round

fix #925
import jax
import jax.numpy as jnp
import pgx

env = pgx.make("leduc_holdem")

init_fn = jax.jit(env.init)
step_fn = jax.jit(env.step)

CALL = jnp.int32(0)
RAISE = jnp.int32(1)
FOLD = jnp.int32(2)

key = jax.random.PRNGKey(1)

state = init_fn(key)
state = step_fn(state, RAISE)
assert not state.terminated

state = step_fn(state, FOLD)
assert state.terminated  # OK

LGTM :)
@OkanoShinri Please merge it after CI


Add docstring for Instruction.flag_update

I found out about this usage through experimentation. I don't know a lot about OpenGL.

Maintainer merge checklist

[x] Title is descriptive/clear for inclusion in release notes.
[x] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[ ] Applied the release-highlight label to be highlighted in release notes.
[x] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[ ] Properly documented, including versionadded, versionchanged as needed.

@m1sl6 At runtime I'm seeing this error:
\kivy\kivy\graphics\__init__.py", line 83, in <module>
     from kivy.graphics.instructions import Callback, Canvas, CanvasBase, \
   File "kivy\graphics\instructions.pyx", line 83, in init kivy.graphics.instructions
     flag_update.__doc__ = """Indicate that the instruction needs to be redrawn on the next frame.
 AttributeError: attribute '__doc__' of 'method_descriptor' objects is not writable

@DexerBR Ah, sorry about that. Try #8958


React.createClass warning after upgrading to React 15.5

After upgrading to React 15.5, I'm seeing this warning:
Warning: A Component: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.

Can this be updated to be a JavaScript class?

PRs welcome 😉
When I have time I'll move it over to React.Component. This won't be an issue until react 16 anyhow.

#4

Fixed in https://github.com/iest/react-body-classname/commit/f603bed111f0d98b5eb85ce5b843a6ce516f3b99 thanks to @batusai513


⚠ Secret Website 3 has degraded performance

In 88203b8, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2408 ms

Resolved: Secret Website 3 performance has improved in 2629ca2.


Unit Testing & Test Coverage

At present there are no unit tests and no test coverage reporting. Unit tests need to be added to ensure there are no regression bugs as additional features are added, or functionality changed.

Unit testing completed


loader cause PostcssPlugins doesn't work

I recently user 'style-resources-loader' cause some plugins not work.
I'm not sure where problem it is.
addPostcssPlugins([
    require('postcss-px-to-viewport')({
      ...
    })
  ]),
  addWebpackModuleRule(
    {
      test: /\.less$/,
      use: ['style-loader', 'css-loader', 'less-loader', {
        loader: 'style-resources-loader',
        options: {
            patterns: [
                './src/global/*.less'
            ]
        }
      }]
    }
  ),

or you can use 'postcss-px2rem', it also doesn't work.

I am sorry here again,I test them in another project in vue-cli.
'postcss-px-to-viewport' and 'style-resources-loader' can work together.

Did you find mthods？

Did you find methods？

No,I run eject finally,or you can try another solution craco recommended by antd;

This is my solution：
const { override, addLessLoader, addPostcssPlugins} = require('customize-cra')
module.exports = {
  webpack: override(
    addLessLoader({
      lessOptions: {
        javascriptEnabled: true,
        modifyVars: {
          'hack': `true; @import "~@/assets/less/var.less";`
        }
      }
    }),
    addPostcssPlugins([
      require('postcss-px-to-viewport')({
        viewportWidth: 375
      })
    ])
  )
}

Attention, if addLessLoader behind addPostcssPlugins, it won't be work

I update version to 'v1.0.0', it's work!
  addLessLoader({
            javascriptEnabled: true,
            modifyVars: {
                hack: `true; @import "~@/assets/styles/mixin.less";`,
            },
            cssLoaderOptions: {}, // .less file used css-loader option, not all CSS file.
            localIdentName: '[local]_[hash:base64:5]',
            cssModules: true,
        }),

Did you find methods？


AuthorizationError: not authorized

Hello,
I tried the example provider and consumer, but I get the following error.
Who can explain me why will this occurs?
Express
500 AuthorizationError: not authorized
at validated (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/middleware/authorization.js:131:36)
at /home/kevin/oauth2orize/examples/all-grants/oauth2.js:180:14
at Object.exports.findByClientId (/home/kevin/oauth2orize/examples/all-grants/db/clients.js:24:10)
at exports.authorization.res.render.transactionID (/home/kevin/oauth2orize/examples/all-grants/oauth2.js:174:16)
at /home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/middleware/authorization.js:167:9
at pass (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/server.js:262:26)
at pass (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/server.js:280:9)
at pass (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/server.js:271:11)
at Server._parse (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/server.js:285:5)
at authorization (/home/kevin/oauth2orize/examples/all-grants/node_modules/oauth2orize/lib/middleware/authorization.js:118:12)
Best regards,
Kevin

@trevorallred I added an answer to your StackOverflow question. I ran into the same problem as well, hope it fixes your problem.