Five mins

Issue Addressed
https://github.com/CityofToronto/bdit_flashcrow/pull/1226 didn't work in dev... so I am just changing the time to 5 mins. We'll need to remember to change this back after!
Description
I am just changing the time to 5 mins. We'll need to remember to change this back after!
Tests
Everything still passes

This had other things it shouldn't have... oops.


Error msg with IE9

Hi,
I get this error message with IE9 (probably because it's html4): History.js does not support states with fragement-identifiers (hashes/anchors)
What does this error msg mean? In which cases it pops? Any ideas of how can it be fixed?

I'm seeing this error too with the latest version from github.

I ended up duck-punching pushState and replaceState so that they cull fragment identifiers (the hash and everything after it) from states before doing what they normally do. This seems to be working well enough for me, but I'd really rather not have to do something so cheesy. :P
My project will eventually move to jQuery Mobile, so I expect I'll have to deal with whatever issues their implementation of HTML5 History introduces too. Or do they use this library too?

I tracked my issues down to the fact that I was passing "" as the state url for the root page. This turns into "./" inside History.js which causes all sorts of issues. Using "/" doesn't cause these problems, although I am actually using some form of "?state=1", as in the examples.
Ron, I noticed that you are not starting your state urls with "?". Maybe this is causing your problems. History.js tries to make the URL relative (hence "" becomes "./") and so starting with "/" might be causing your problems. Although, my understanding of this is still shakey.

It merits further investigation. However, all of the URLs that I pass into History.JS already have slashes in them. I would hope that History.JS sees sufficient slashing and doesn't attempt any further mangling.
I would consider it a bug if the presence of a question-mark (?) was either mandatory or not allowed. ?s are to help the server parse a request, the only thing a browser should care about is the hash (#) an what comes before and after it.

I recently bumped into this issue, my urls look something like this: http://site.com/view.aspx?Id=365 and I was using pushState({ obj }, null, null); which works fine in "html5-mode". In html4 it modified the url to behttp://site.com/view.aspx?Id=365#view.aspx?Id=365&_suid=12345678901234567. After I changed to using pushState({ obj }, null, "/"); the urls are now: http://site.com/view.aspx?Id=365#/?&_suid=12345678901234567 and work fine.


Qingying

Modify the acquisition of DVH in re-opt
Modify the way of creating the file path
Add a tutorial for BOPlanner
Update README

tutorial update


error message "Generate nginx file failed"

Congratulations for the effort to develop this nice mod!
After starting the run.bat file as administrator, I click "run", and receive the error message "Generate nginx file failed". It seems the mod is not loading Google Maps images.
Also, I'm getting another error message in the run.dat output "dns.exeption.Timeout: The DNS operation timed out after 5.4 seconds".
Any suggestions?
Thanks!

Seems it has issue finding DNS resolve. Do you have issue access <IP_ADDRESS> or <IP_ADDRESS>

I'm sorry, I did not understand your answer. Should I search for access <IP_ADDRESS> or <IP_ADDRESS>?

Sorry, I mean you may have access issue for <IP_ADDRESS> or <IP_ADDRESS> so that the DNS can't be resolved.
I will more common servers and please stay tunned for latest version

Please try this version, I added more DNS server, may solve this problem.
https://github.com/derekhe/msfs2020-google-map/releases/tag/2.2.4

I've updated the version to 2.2.4 and got this new error message:
error.pdf

Thanks, I think it is a DNS issue, I'm trying to find out.

Please try this version: https://github.com/derekhe/msfs2020-google-map/releases/tag/2.2.5

@viniciusbrei any fix?

Also ,please try: https://github.com/derekhe/msfs2020-google-map/releases/tag/2.2.6

@viniciusbrei did it fix?

Unfortunately, it's not working. The mod is not crashing anymore, but I does not load Google Maps in MSFS 2020.

Please try latest version

@viniciusbrei fixed?

Please try latest version: https://github.com/derekhe/msfs2020-google-map/releases/tag/2.3.2


Multiprocessing

Support for multiprocessing for optimizations.
Extensive changes were made to facilitate this that include the following:
OptPol notably accepts a FLAT and returns either 0 if the optimization does not complete or the optimized Mol.
OptPol also works on exactly one conformation at a time, instead of generating nConfs conformers and optimizing all of them. This means all the required OptPol jobs can be managed by the ProcessPoolExecutor.
The Polymer objects are populated with lists of Mol objects with 1 optimized conformation. This means the need for SDF temporary files is removed, which obviates the workaround on Windows platforms that results in a buildup of temporary files that could not be deleted at runtime.
Unscientific performance tests show ~50% runtime reduction for 1-7 units of Styrene and a ~66% reduction for 1-14 units.
The progress bars are now drawn by the rich  module instead of tqdm, which takes up less screen real estate and looks better.

Eliminating the need for the temporary files will be convenient. I'll compare run times with previous optimizations.


Schema 'warren.cineast' does not exist

This seems to be a regression of #255.
To reproduce clone https://github.com/akohlbecker/vitrivr-docker-compose
and start the vitrivr stack with docker compose:
docker compose up --build

conttontaildb startup fails with:
cineast     | 2024-04-17 16:08:41.046 [main] DEBUG o.v.c.c.d.c.CottontailWrapper - Starting to connect to Cottontail DB at cottontail:1865
cottontail  | Cottontail DB server is up and running at port 1865! Hop along... (catalogue: V3_1, pid: 7)
cineast     | 2024-04-17 16:08:41.199 [main] INFO o.v.c.c.d.c.CottontailWrapper - Connected to Cottontail DB in 153 ms at cottontail:1865
cottontail  | 2024-04-17 16:08:41 [DefaultDispatcher-worker-1] DEBUG TransactionalGrpcService:135 - [1, c1068fd9-5dd0-4cea-b725-8082c3c98efd] Preparation of AboutEntity completed successfully in 35.994953ms.
cottontail  | 2024-04-17 16:08:41 [DefaultDispatcher-worker-1] ERROR TransactionalGrpcService:225 - [1, c1068fd9-5dd0-4cea-b725-8082c3c98efd] Execution of AboutEntity query failed: Schema 'warren.cineast' does not exist!
cottontail  | 2024-04-17 16:08:41 [DefaultDispatcher-worker-1] ERROR TransactionalGrpcService:226 - org.vitrivr.cottontail.dbms.exceptions.DatabaseException$SchemaDoesNotExistException: Schema 'warren.cineast' does not exist!

I'm not sure what behavior you are expecting here. I had a quick look at your docker comose and could not find a database initialization step anywhere. Just based on the log snippet, it's also not quite clear if you interacted with cineast in any way that would cause it to query an uninitialized database. Could you elaborate on what you were trying to do?

In the wiki (https://github.com/vitrivr/cineast/wiki/Environment-Setup & https://github.com/vitrivr/cottontaildb/wiki ) I did not find anything on initializing a db, therefore I was assuming that cineast has a default configuration that allow it to connect cottontaildb in order to initialize a DB in case it is missing.

Well, the features based on which retrieval is performed need to come from somewhere. Generally, cineast extracts them and stores them in cottontaildb. Since the features to be used are configurable, the relevant database initialization happens only when the features are used for extraction. See https://github.com/vitrivr/cineast/wiki/Extracting-Features#extracting-directly-to-cottontail-db.

Thanks a lot! That answers two of the questions I scratch my head about.

Ok great. If you have any further questions, please don't hesitate to reach out through the Discussions tab.


IO bakend statistics brokes browser node

Looks like this commit https://github.com/paritytech/substrate/commit/eae576ffbcd0ae62020f2e9f865e3c7b8db00213 brokes browser node.
panicked at 'time not implemented on wasm32-unknown-unknown', src/libstd/sys/wasm/time.rs:13:9

Stack:

Error
    at imports.wbg.__wbg_new_59cb74e423758ede (http://localhost:8000/pkg/node_cli.js:311:19)
    at console_error_panic_hook::hook::h5edd888a68f66635 (wasm-function[3588]:0x634d30)
    at core::ops::function::Fn::call::h707890c35947098d (wasm-function[14479]:0x854e2b)
    at std::panicking::rust_panic_with_hook::hea54eab3988c00c4 (wasm-function[7183]:0x7a4778)
    at std::panicking::begin_panic::h95e5c5c9babf5826 (wasm-function[11739]:0x845a9c)
    at std::sys::wasm::time::Instant::now::h9bdc09727261d0c0 (wasm-function[13610]:0x85260e)
    at std::time::Instant::now::h86092932a009d41c (wasm-function[14628]:0x85528b)
    at kvdb::io_stats::IoStats::empty::hd9e4130d7fd84c26 (wasm-function[9442]:0x813741)
    at sc_client_db::light::LightStorage<Block>::new::h6e1f24ea320f84fb (wasm-function[601]:0x2d382e)
    at node_cli::service::new_light::hdcbcad0d1fd2cb1e (wasm-function[150]:0xbe7e5)

Whats about to make it optionally?

I thought @expenses added optionality there?

Ok seems that timer panics fixing is still in progress:
https://github.com/paritytech/substrate/pull/4561
But I can add separate patch just for that meanwhile

^^^ I am not sure if my pr will close the issue compelely, it might be not only one that prevents it from working


Write caching logic(useSwr hook)

Problem statement
Right now codingspace doesn't have a way to cache data to load things faster.
Describe the solution you'd like
I want to add a useSwr hook to cache the data to make the website load faster.
Success criteria
The criteria must be met in order to consider this feature a success.

Load times reduced at least 20%, ideally more

User stories
How the product should work for various user types.
As a user

I want my search queries to return results quickly
So I can get my work done faster

As a front end engineer

I expect my queries to be cached on the back end
So the front end can be as fast as possible

If anyone wants to work on this issue, please let me know in the comment section.

do you refer this swr ?

do you refer this swr ?

Yes

Hey, I want to work on this. But First I need to learn this. So it takes some time.

Take your time.
Assigned to you
On Tue 5 Oct, 2021, 11:13 AM BivasBiswas, @.***> wrote:

Hey, I want to work on this. But First I need to learn this. So it takes
some time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rishipurwar1/coding-space/issues/27#issuecomment-934085178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANTEVECFCP3E7ZBUHPQHHNTUFKGBHANCNFSM5EJBYW4Q
.

oke

how I see the login page in my system ?

There is no login page on the website.

I also wants to work on this issue.

@Bivas-Biswas are you working on this one?

Hey @rishipurwar1, kindly assign this to me

@imps1001 you can work on this with @Bivas-Biswas


[BUG] AWSV4SignerAuth does not accept "aos"

What is the bug?
When users are using OSB to test a SigV4 authenticated opensearch cluster, they set the environment variable to aos or aoss. However, AWSSigV4Auth class takes es instead of aos. This could be misleading to new OpenSearch users.
Are there any plans to support aos on top of es and aoss?
How can one reproduce the bug?

Create an AOS domain that uses an authenticated IAM user for security
Set OSB environment variables as described here

OSB_AWS_ACCESS_KEY_ID=<IAM USER AWS ACCESS KEY ID>
OSB_AWS_SECRET_ACCESS_KEY=<IAM USER AWS SECRET ACCESS KEY>
OSB_REGION=<YOUR REGION>
OSB_SERVICE=aos

Run a test like the following command:

opensearch-benchmark execute-test \
--target-hosts=<CLUSTER ENDPOINT> \
--pipeline=benchmark-only \
--workload=geonames \
--client-options=timeout:120,amazon_aws_log_in:environment \

Error encountered:
"Service for aws log in should be one of 'es' or 'aoss'"

What is the expected behavior?
opensearch-py should accept aos as well on top of es and aoss.
What is your host/environment?
Occurs on MacOS, Linux and with Amazon Managed-Service Clusters
Do you have any screenshots?
N/A
Do you have any additional context?
N/A

This feels like an OSB problem because the AWS service is definitely es and aoss, not aos, no?

I was thinking it was on the opensearch-py side since OSB leverages OpenSearch-py to communicate with clusters
https://github.com/opensearch-project/opensearch-py/blob/84ac172ddc54b3e6c975d36221d16ec3e78a2fe9/opensearchpy/helpers/signer.py#L51

@IanHoang That default is correct, the service code is "es". Service codes are used to scope service credentials. Do you not agree?

@dblock You're right, thanks for calling this out! opensearch-py uses botocore, which still uses es. Closing this issue


"./cluster/kubectl.sh get vms" after cluster-sync claims "vms" resource is not supported

This happens once after cluster-sync; the second call to the same command always returns the correct result (no resources found).
[ihar@ws kubevirt]$ ./cluster/kubectl.sh get vms
the server doesn't have a resource type "vms"
[ihar@ws kubevirt]$ ./cluster/kubectl.sh get vms
No resources found.

Could this be a timing issue?
I.e. does it also happen with a sleep or manual (human) sleep between the
two calls?

fabian

On Fri, May 4, 2018 at 10:05 PM, Ihar Hrachyshka<EMAIL_ADDRESS>wrote:

This happens once after cluster-sync; the second call to the same command
always returns the correct result (no resources found).
[ihar@ws kubevirt]$ ./cluster/kubectl.sh get vms
the server doesn't have a resource type "vms"
[ihar@ws kubevirt]$ ./cluster/kubectl.sh get vms
No resources found.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubevirt/kubevirt/issues/994, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFGAL4zuTlDQU-OGPxtQCtlvHkZaEo1ks5tvLSGgaJpZM4TzMvX
.

That is expected. It can take a few seconds until the kubernetes api server makes newly posted custom resource definitions available on the api. We could move our cluster-readiness check  from automation/tests.sh to cluste/sync.sh, to make it easier on the dev-side to see when everything is ready. @booxter would that help?

@rmohr I don't think that's a bootstrapping timing issue. I just put 5 minutes sleep between cluster-sync and kubectl commands, and the issue remains.

interesting. And it is always the first call, right?

Yes, always the very first call only, and it's specific to kubevirt resources.

The issue seems to be related to short name (vms) used. If I instead call 'get virtualmachines', it works fine the first time and all consequent times regardless of whether I later use the shortened version.

It seems to be a general caching issue in kubectl. Maybe worth filing a bug in kubernetes, if it does not already exist.

@booxter could you please file a bug and crossreference this issue?

The issue is reported upstream at: https://github.com/kubernetes/kubernetes/issues/65517

:+1:

The issue still exists.
/remove-lifecycle stale


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_06d4321d-f2ce-477a-b3bb-113fd11c7dec/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_06d4321d-f2ce-477a-b3bb-113fd11c7dec.git

Docs Build status updates of commit 784d414:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Use lowercase key name in code sample for k8s provider

Proposed changes
Fixes typo in code sample to match ProviderArgs lowercase key for kubeconfig.

Thanks for the PR, @ajaegle!


Always downloading Playwright driver

I noticed that in the current master branch it was always downloading the driver. I found the issue, in PlaywrightDriver.isUpToDateDriver  It's checking the output of PW, for example:
/Users/sam/Library/Caches/ms-playwright-go/1.16.0-next-1634703014000/playwright.sh --version
Version 1.16.0-next

With the constant:
const playwrightCliVersion = "1.16.0-next-1634703014000"

Using:
	if bytes.Contains(output, []byte(d.Version)) {
		return true, nil
	}

The extra -1634703014000 on the constant is the issue.
I've fixed it locally by adding this to the end of isUpToDateDriver:
	if strings.HasPrefix(string(output), "Version ") {
		// Get rid of trailing new line
		outputStr := strings.TrimSpace(string(output))
		if len(outputStr) > 8 && strings.Contains(d.Version, outputStr[8:]) {
			return true, nil
		}
	}

I'll submit a PR with the change.
If you have any suggestions for changes I'm happy to change.

This looks more like a bug upstream caused by the recent monorepo migration. Let me fix it there instead.

Sure thing, I'll close the PR. Thanks for your time.

This should get fixed with the next roll.

I have the same issue with the latest master branch. Every time I run the program, the driver will be downloaded again.
2022/01/12 09:06:00 report date is: 2022-01-11
2022/01/12 09:06:06 Downloading driver to C:\Users\caguoa00\AppData\Local\ms-playwright-go\1.16.3-1635814179000
2022/01/12 09:06:16 Downloaded driver successfully

go.mod
go 1.17

require github.com/mxschmitt/playwright-go v0.1400.1-0.20211124164553-ce64d8145ec8

This should be fixed in v1.20.0


withWidth util not working inside componentWillMount

Problem description
The width property is not properly set when used inside componentWillMount. The value is set to 1 -equivalent to small screens <768px-. However, that is not true.
Steps to reproduce
Add the following code inside the component that uses the width:
	componentWillMount() {
		const {width} = this.props;
                  console.log(width)
                //Other logic
	}

Versions

Material-UI: 0.15.4
React: 15.3.1
Browser: Chrome

This one, https://www.npmjs.com/package/react-dimensions, delivers correct values.

We are using the componentDidMount hook in the withWidth HOC as the componentWillMount hook is also called when rendering on the server-side.
Why using the componentWillMount instead of the componentDidMount on your side?
Isn't it better to wait for the component to be mounted perform doing a measurement?

I am using componentWillMount because I want to change the state - I am using redux -, before the first render. Right now I am using to control a Nav Drawer and I control the initial state of the Nav Drawer depending on the width and the current page.
I moved the logic from render to componentWillMount. Dispatching reducers from render throws a warning as it is not recommended.
Do you any problem using componentWillMount instead of componentDidMount? May be with server side rendering?

I think that you are right, we should move the logic inside the constructor / the componentWillMount method.
We have added the logic under the componentDidMount to save from checking if we were in a node environment.
Do you want to work on it? Adding some unit tests would be great too.
I have two side notes:

The componentWillMount() hook could be deprecated in the future: https://github.com/facebook/react/issues/7671. We would have to move the logic under a different function if that goes forward
This HOC would probably no longer be needed in the next branch as we are moving away from the inline-style approach. I could move it under a different project. The range of problem solved is close to react-dimensions but I don't think are fully the same ones.

@oliviertassinari great and quick work! Sorry I couldn't help. I have been quite busy these last 2 days.
Will these changes we added to the next release?


Wrap feature possible issue

In line 293 of ocfnet.py， I think the transformed_grid.shape[1]=4, which may indicate you only wrap 4 voxel grid feature to the wraped_x from x. I don't know if I understand right, I think the for loop should be the number of voxels. May you check again this part?

@synsin0 thanks for your reminder! we fixed it in the latest version.


Nested Template Literals

Currently, when nesting temp literals, the resulting highlighting is janky.
`<tag attr=${exp}>${exp}</tag>`
`${`<tag attr=${exp}>${exp}</tag>`}`

Ideally the top highlighting should be identical to the bottom when placed inside the expression.
What I assume is happening is the first ` gets matched to the second `, when it should skip it (and match to the fourth `) because it is inside the expression.
What it should look like would be similar to:

This is fixed now.


False positive on org.eclipse.jetty.alpn

False positive on https://mvnrepository.com/artifact/org.eclipse.jetty.alpn/alpn-api
Identifiers

cpe: cpe:/a:jetty:jetty:1.1.3.v20160715  Confidence:Low  suppress
maven: org.eclipse.jetty.alpn:alpn-api:1.1.3.v20160715  Confidence:Highest
cpe: cpe:/a:eclipse:jetty:1.1.3.v20160715  Confidence:Low

See comment from the author:
https://github.com/http4s/blaze/issues/235#issuecomment-426927348
Workaround suppression:
   <suppress>
       <notes>False-positive: it's about the implementation not the api</notes>
       <cve>CVE-2017-14798</cve>
       <cpe>cpe:/a:eclipse:jetty</cpe>
   </suppress>

@jeremylong
I updated the workaround to something more specific.
Could you update the suppression? Because it's too much of a wildcard I think.
Thanks

@joan38 I actually don't think the suppression is too broad. It is very specific to the alpn-api which is not Jetty.

Suppressing the CVE will suppress this single entry.  Suppressing by CPE will prevent future CVEs from being reported against alpn-api - which will reduce the number of FP in the output. If someone is using alpn-api in addition to, for instance, embedded jetty - the embedded version of jetty would still get flagged.

Great!
Should we close this now? Or we are waiting for the release?


chore(main): release rhtap-ui 0.5.0

:robot: I have created a release beep boop
0.5.0 (2024-06-03)
Features

Component-relationship: add modal to define component relationship (#898) (4726d85)
docs: update learn more links to use Konflux docs (d71880f)
ImportForm: add base form including the source and component section (7165f52)
plr: add test suites (1934ae5)
plr: add to hook (fbaf249)
plr: fix test (6173a44)
releases: add release plan form (7974d6c)
release: trigger release form (#911) (cc55262)
secret: add css to make field widths consistent (4af54fd)
secret: add linking secret to service account (c14ebb6)
secrets: add k8sSecrets instead of remote secrets (aecb9e8)
secrets: add scm host metadata (f8e18dd)
secrets: fix review comments (ae961df)
secrets: remove deployments from add secrets form (9d775a5)
STONEINTG-837: update url of redhat-appstudio/integration-examples (#924) (dac1cfd)
STONEINTG-877: add Fixable to vulnerabilities titles (251ed64)
taskRun: failed taskRun should show log page initially (9efb95f)
theme: retheme UI for Konflux (993415d)

Bug Fixes

Application: add application thumbnail check on resource metadata (b04793b)
app: update text content through out app (e9f7261)
ComponentRelation: fix visualization on details page (dd171f7)
ComponentRelation: use component from all applications (7c69142)
Component: remove sha hash from container image url (574814f)
components: add unit test for useAllComponents (a58d847)
content: update overview page content based on Konflux website (7a3090e)
docker: update .dockerignore (10244c7)
e2e: avoid getting stuck waiting for spinner (bbd6652)
e2e: force render the table on new data changes (9605e76)
e2e: remove check of target in secrets tab (e260d71)
e2e: replace github import API with template generation (630d545)
e2eTests: fix advance happy path and environment page tests (de5be43)
e2eTests: fix e2e tests to work without deployments and environments (72058f9)
EnterpriseContract: show ec results under security tab from tkn (115ac10)
Environment/Deployments: remove deprecated code for environments and deployments (88647a6)
Environment/Deployments: remove environments and deployments refrences from UI (88fc539)
environments: fix unit tests and remove mention of deployments (f2569a9)
github-app: change github app url and name (ed46215)
GithubApp: fix github app urls for internal instance (095a8e6)
GithubRedirect: add redirects for url from github checks (add8fa1)
GithubRedirect: use task name instead of task run (32a46ad)
ImageRepository: use ImageRespository cr instead of component annotation (158e171)
ImportForm: add build secret section (2be13bd)
ImportForm: add ImageRepository support (5de16c2)
ImportForm: add pipeline section and fetch pipeline template from config map (402e2ac)
ImportForm: add submit-utils to create application and components (7b466b5)
ImportForm: add unit tests and cleanup redundant code (c6a2019)
logs: update fetch method for tekton-results pipelinerun logs (537cd9d)
overview: change slack channel name and typo fix (c79053c)
pipeline-modal: fix table row width for pipeline modal (493edf0)
pipeline: fix pipeline rerun actions to run pac build (7415588)
PipelineSection: select default pipeline and remove community pipeline (6e6cd66)
plr: remove hidden property from rerun action (746eace)
PrivateAuth: remove feature flag from auth flow (5b13d3b)
release-plan: update release plan form, add status and release plan addmision column (2062fa6)
release: remove name check (a45d06b)
releases: add links for snapshot in release details and list view (542c47b)
release: trigger release preselection (e9e55b3)
release: update release links (c75594f)
results-api: avoid refetching of API in case of errors and add error states (98a2623)
results-api: enable caching in the tekton results vulnerabilities API call (0b28aeb)
Secret: add namespace as target to Remote secret creation (e330c27)
secrets: address review comments (94eb084)
testpipeline: remove commits from filter (f3569f5)
test: remove menu item Learning resources (283d2f7)
test: stabilise vulnerabilities by refreshing the page during advanced happy path (a14b600)
UserAccess: change minimum character limit for username (e82a41c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/openshift/hac-dev/releases/tag/rhtap-ui-v0.5.0 :sunflower:


Exam Scoreboard with Barchart

Refer to: https://www.figma.com/file/EBXAMSH5BVf7xLt7bqVUKa/Exam?node-id=45%3A1793
The library mentioned in the sprint: https://www.chartjs.org/

Should make sure about whether we really need dim colors:


Option to allow failure

Is your feature request related to a problem? Please describe.
Sometimes a command's success is optional. It would be nice to mark it as "allow failure".
Describe the solution you'd like
An option to tell the command can fail but still return a 0 exit code, with a yellow cross instead of a green check mark.

Done, option -z, --zero, --nofail, nofail in API.


Error parsing undocumented API response

Starting the add-on gets error parsing undocumented API response 1: unknown field dspVersionSoft and quits.
I am running HAOS and followed the instructions to install this add-on.
Logs below.
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
GOVEE_API_KEY=XXXX
GOVEE_MQTT_HOST=core-mosquitto
GOVEE_EMAIL=XXXX
GOVEE_MQTT_USER=addons
GOVEE_MQTT_PORT=1883
++ cd /app
++ exec /app/govee serve
[2024-01-04T08:22:42 INFO  govee::commands::serve] Starting service. version 2024.01.03-63439388
[2024-01-04T08:22:42 INFO  govee::commands::serve] Querying platform API for device list
[2024-01-04T08:22:43 INFO  govee::commands::serve] Querying undocumented API for device + room list
Error: request status 200: OK

Caused by:
    0: parsing response as json: {"devices":[{"groupId":0,"device":"2A:64:F8:4F:C0:2E:56:AA","sku":"H706A","spec":"","versionHard":"3.04.01","versionSoft":"1.00.14","deviceName":"Permanent Lights Pro","deviceExt":{"deviceSettings":"{\"wifiName\":\"XXXX\",\"address\":\"F8:4F:C0:2E:56:AA\",\"bleName\":\"Govee_H706A_56AA\",\"topic\":\"GD/9b546caecc80eef27478fd5839453d27\",\"wifiMac\":\"60:74:F4:85:45:D4\",\"pactType\":1,\"pactCode\":1,\"wifiSoftVersion\":\"1.01.17\",\"wifiHardVersion\":\"1.04.01\",\"ic\":55,\"secretCode\":\"XXXX=\",\"boilWaterCompletedNotiOnOff\":1,\"completionNotiOnOff\":1,\"autoShutDownOnOff\":1,\"dspVersionSoft\":\"13\",\"supportBleBroadV3\":false,\"segmentCount\":11,\"sku\":\"H706A\",\"device\":\"2A:64:F8:4F:C0:2E:56:AA\",\"deviceName\":\"Permanent Lights Pro\",\"versionHard\":\"3.04.01\",\"versionSoft\":\"1.00.14\",\"playState\":false}","lastDeviceData":"{\"online\":false}","extResources":"{\"skuUrl\":\"https://d1f2504ijhdyjw.cloudfront.net/sku-img/110c816f749f75640260511c333a1065-add_list_type_device_706a.png\",\"headOnImg\":\"https://d1f2504ijhdyjw.cloudfront.net/sku-img/8e57eab8d1c8c6d9f280be7e4460b0d2-706a_light_title_on.png\",\"headOnImgNew\":\"\",\"headOffImg\":\"https://d1f2504ijhdyjw.cloudfront.net/sku-img/a4e9d925c3c788fc25adde52e44349a8-706a_light_title_off.png\",\"headOffImgNew\":\"\",\"ext\":\"\",\"ic\":120}"},"pactType":1,"pactCode":1,"share":0,"deviceId":17753321,"goodsType":180,"attributesId":49,"supportScene":0}],"groups":[{"groupId":16153650,"groupName":"Bedroom"},{"groupId":16153651,"groupName":"Living Room"}],"sort":[],"sortTime":0,"message":"","status":200}
    1: unknown field `dspVersionSoft`, expected one of `wifiName`, `address`, `bleName`, `topic`, `wifiMac`, `pactType`, `pactCode`, `wifiSoftVersion`, `wifiHardVersion`, `ic`, `ic_sub_1`, `ic_sub_2`, `secretCode`, `boilWaterCompletedNotiOnOff`, `completionNotiOnOff`, `autoShutDownOnOff`, `sku`, `device`, `deviceName`, `versionHard`, `versionSoft`, `playState` at line 1 column 371

Stack backtrace:
   0: anyhow::context::<impl anyhow::Context<T,E> for core::result::Result<T,E>>::with_context
   1: govee::undoc_api::GoveeUndocumentedApi::get_device_list::{{closure}}
   2: govee::commands::serve::ServeCommand::run::{{closure}}
   3: govee::Args::run::{{closure}}
   4: tokio::runtime::park::CachedParkThread::block_on
   5: tokio::runtime::context::runtime::enter_runtime
   6: govee::main
   7: std::sys_common::backtrace::__rust_begin_short_backtrace
   8: std::rt::lang_start::{{closure}}
   9: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/ops/function.rs:284:13
  10: std::panicking::try::do_call
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:552:40
  11: std::panicking::try
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:516:19
  12: std::panic::catch_unwind
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panic.rs:142:14
  13: std::rt::lang_start_internal::{{closure}}
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/rt.rs:148:48
  14: std::panicking::try::do_call
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:552:40
  15: std::panicking::try
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:516:19
  16: std::panic::catch_unwind
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panic.rs:142:14
  17: std::rt::lang_start_internal
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/rt.rs:148:20
  18: std::rt::lang_start
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Thanks for sharing this. I think this should be generally resolved by ea42fcc284448bbb73ab0488c36cfb619f86d901
If you update the addon it should hopefully work!

Thanks. Now it is working.


⚠ Bofrost.lu has degraded performance

In 5c3b9c6, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1394 ms

Resolved: Bofrost.lu performance has improved in 5fe3076 after 28 minutes.


Licensing?

Love the art!
I'm considering doing some ascii tarot-ish art in a project. What kind of derivation would you allow?

Please add a license for this!

License is stated as MIT in the package.json file

Clarified MIT License in LICENSE.txt and Readme


TTL is not working

Hi.
I'm testing this lib but I have error. I set key with expire after 10 seconds. But It not removed after this time.
Code:
func testTTLMAP() {
expirationCallback := func(key string, value interface{}) {
fmt.Printf("This key(%s) has expired\n", key)
}
cache := ttlcache.NewCache()
defer cache.Close()
cache.SetWithTTL("keyWithTTL", "value 123", 10 * time.Second)
cache.SetExpirationCallback(expirationCallback)
for {
	log.Println(cache.Get("keyWithTTL"))
	time.Sleep(1 * time.Second)
}

}
Result:

2019/10/29 16:18:13 value 123 true
2019/10/29 16:18:14 value 123 true
2019/10/29 16:18:15 value 123 true
2019/10/29 16:18:16 value 123 true
2019/10/29 16:18:17 value 123 true
2019/10/29 16:18:18 value 123 true
2019/10/29 16:18:19 value 123 true
2019/10/29 16:18:20 value 123 true
2019/10/29 16:18:21 value 123 true
2019/10/29 16:18:22 value 123 true
2019/10/29 16:18:23 value 123 true
2019/10/29 16:18:24 value 123 true
2019/10/29 16:18:25 value 123 true

I resolved the problem by adding function cache.SkipTtlExtensionOnHit(true)

Ok, not a bug then

this kind of is a bug, had the same issue.
The library doesnt work as expected in the examples.
Without
cache.SkipTtlExtensionOnHit(true)

ttl doesnt work as expected (10 second ttl will not expire after 10 seconds. It takes quite a bit longer for some reason? Unknown)
Anyways, thanks @minhdv118 for the solution :)


Complain about LANGUAGE pragmas

We're not going to implement any nontrivial GHC extensions for the foreseeable future, so I think the compiler should check for unsupported LANGUAGE pragmas and die with an error, rather than attempt to soldier on and inevitably fail.
Sure, pragmas are technically comments, so we're breaking standards compliance in this specific case, but I think it's worth it for the sake of better error messages.

The parser (#8) can handle them specially, whilst stripping out regular comments.


Typo-fix-on-how-it-works-section

Accessibility Spelling Corrected..
BTW awesome work...⭐⭐⭐⭐⭐

Thank you so much 👍


chore: formatting changes

This PR was generated using Autosynth. :rainbow:
Log from Synthtool
synthtool > Executing /tmpfs/src/git/autosynth/working_repo/synth.py.
synthtool > Ensuring dependencies.
synthtool > Pulling artman image.
latest: Pulling from googleapis/artman
Digest: sha256:545c758c76c3f779037aa259023ec3d1ef2d57d2c8cd00a222cb187d63ceac5e
Status: Image is up to date for googleapis/artman:latest
synthtool > Cloning googleapis.
synthtool > Running generator for google/logging/artman_logging.yaml.
synthtool > Generated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/js/logging-v2.
synthtool > Replaced '../../package.json' in src/v2/config_service_v2_client.js.
synthtool > Replaced '../../package.json' in src/v2/logging_service_v2_client.js.
synthtool > Replaced '../../package.json' in src/v2/metrics_service_v2_client.js.
.eslintignore
.eslintrc.yml
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.jsdoc.js
.kokoro/common.cfg
.kokoro/continuous/node10/common.cfg
.kokoro/continuous/node10/docs.cfg
.kokoro/continuous/node10/lint.cfg
.kokoro/continuous/node10/samples-test.cfg
.kokoro/continuous/node10/system-test.cfg
.kokoro/continuous/node10/test.cfg
.kokoro/continuous/node12/common.cfg
.kokoro/continuous/node12/test.cfg
.kokoro/continuous/node8/common.cfg
.kokoro/continuous/node8/test.cfg
.kokoro/docs.sh
.kokoro/lint.sh
.kokoro/presubmit/node10/common.cfg
.kokoro/presubmit/node10/docs.cfg
.kokoro/presubmit/node10/lint.cfg
.kokoro/presubmit/node10/samples-test.cfg
.kokoro/presubmit/node10/system-test.cfg
.kokoro/presubmit/node10/test.cfg
.kokoro/presubmit/node12/common.cfg
.kokoro/presubmit/node12/test.cfg
.kokoro/presubmit/node8/common.cfg
.kokoro/presubmit/node8/test.cfg
.kokoro/presubmit/windows/common.cfg
.kokoro/presubmit/windows/test.cfg
.kokoro/publish.sh
.kokoro/release/docs.cfg
.kokoro/release/docs.sh
.kokoro/release/publish.cfg
.kokoro/samples-test.sh
.kokoro/system-test.sh
.kokoro/test.bat
.kokoro/test.sh
.kokoro/trampoline.sh
.nycrc
.prettierignore
.prettierrc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
codecov.yaml
renovate.json
samples/README.md
synthtool > Replaced 'https:\\/\\/cloud\\.google\\.com[\\s\\*]*http:\\/\\/(.*)[\\s\\*]*\\)' in src/v2/doc/google/protobuf/doc_timestamp.js.
synthtool > No replacements made in **/doc/google/protobuf/doc_timestamp.js for pattern toISOString\], maybe replacement is not longer needed?
synthtool > Replaced 'Sum\\[i=1\\.\\.n\\]\\(https:\\/\\/cloud\\.google\\.com\\(x_i - mean\\)\\^2\\)' in src/v2/doc/google/api/doc_distribution.js.
npm WARN npm npm does not support Node.js v12.13.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.
npm WARN npm You can find the latest version at https://nodejs.org/

><EMAIL_ADDRESS>postinstall /tmpfs/src/git/autosynth/working_repo/node_modules/core-js
> node postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
> https://opencollective.com/core-js
> https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

><EMAIL_ADDRESS>postinstall /tmpfs/src/git/autosynth/working_repo/node_modules/protobufjs
> node scripts/postinstall

><EMAIL_ADDRESS>prepare /tmpfs/src/git/autosynth/working_repo
> npm run compile

npm WARN npm npm does not support Node.js v12.13.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.
npm WARN npm You can find the latest version at https://nodejs.org/

><EMAIL_ADDRESS>compile /tmpfs/src/git/autosynth/working_repo
> tsc -p . && cp -r src/v2 build/src/v2 && cp -r protos build && cp -r proto build && cp test/*.js build/test

npm notice created a lockfile as package-lock.json. You should commit this file.
added 766 packages from 1287 contributors and audited 3066 packages in 20.668s
found 0 vulnerabilities

npm WARN npm npm does not support Node.js v12.13.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.
npm WARN npm You can find the latest version at https://nodejs.org/

><EMAIL_ADDRESS>fix /tmpfs/src/git/autosynth/working_repo
> gts fix && eslint --fix '**/*.js'

synthtool > Cleaned up 2 temporary directories.
synthtool > Wrote metadata to synth.metadata.

Seems like some formatting fixes. Incompatible gts / prettier?  (closing for now, we'll see what happens next)


Vagrantfile: Fail testsuite if go tests fails

Signed-off-by: Thomas Graf<EMAIL_ADDRESS>

Thanks for the review @scanf


Investigation about tracing, logging, and metrics support.

As a library for production usage, it would be useful to add logging, metrics, and tracing support. We need to do some investigation about to fit into rust ecosystem as much as possible.

I will suggestion the following set:

logging: log
metrics: prometheus_client
tracing: fastrace

Why not tracing?
Tracing is widely used, but it often confuses the scope of logging and tracing.
From a tracing perspective, it's 100 times slower than fastrace.
Meanwhile, log offers the most compatible solution for all logging systems, making integration easier for users.
Why not prometheus?
prometheus project maintained by tikv community is almost dead.
Why not metrics?
It makes sense to introduce an abstraction based on metrics tailored to my own usage. However, its abstraction does not effectively support prometheus, which is the most widely used metrics collector.
I suggest we first integrate directly with Prometheus and consider metrics, while also accommodating requests for support of other metrics tools like tcp.

Personally I'd support tracing crate over logging. Adoption of tracing has supplanted that of logging over the past few years. It is more capable and flexible than logging. I disagree with the sentiment that it confuses things.

Adoption of tracing has supplanted that of logging over the past few years.

Users who rely on tracing can still integrate with our log, as tracing has native integration. However, if we adopt tracing, then log users will not be able to integrate with us. Therefore, I believe libraries like Iceberg should use log instead of tracing. Nonetheless, I'm open to using tracing_subscriber in our tests for a better user experience.
Here is a decision matrix:

Does it works?
iceberg use log
iceberg use tracing

user use env_logger (log ecosystem)
YES
YES

user use tracing_subscriber(tracing ecosystem)
YES
NO

Hi all,
I agree with @sdd and suggest to stick with tracing. It is the default choice for logging in async applications and has the most wide-spread adoption.
Regarding performance arguments, I doubt that this matters in any real world benchmark of this crate, any tracing incurred overhead will be dwarfed by the network latencies of whatever storage cloud service serves the data files / roundtrips to DB catalog / API calls to a Rest catalog. I'm strongly in favor with sticking with a tried and tested implementation and put some real world benchmarks in place and only if those show tracing to be a bottleneck consider choosing a less active alternative.
I also do not agree with the sentiment that it is a problem to address tracing & logging in the same crate. It rather provides very useful debugging utilities, e.g. when used in a server, some middleware can create a span containing a request id, now every (tracing-)log statement within that span will have the request id attached to it so your favorite log aggregator can filter by this request id to get all logs pertaining to it which is incredibly helpful when dealing with production issues.
Regarding metrics, I'm not sure I understand the issue, there exists https://crates.io/crates/metrics-prometheus which provides integration of prometheus with metrics.rs.

Thank you all for joining the discussion. It seems most people prefer using tracing for trace and log. I'm willing to accept this since it's more important for us to move forward.
So the left part is metrics.
What do you think about prometheus_client and metrics?

Some additional context. Renjie mentioned:

Cons:
It's mixing logging with tracing. If we use tracing for logging, our logging compability will not be compatible with logger system.

This is not quite right. You can use the  tracing_log crate to redirect any other crates logs that went to log to tracing:
use tracing_log::LogTracer;

// redirects all output sent to log:* to their tracing::* equivalent
LogTracer::init().expect("Failed to set logger");

Regarding metrics, my preference would be either metrics or opentelemetry. Both are vendor-agnostic with pluggable exporters. My first choice would be opentelemetry as it seems to have better cross-language recognition and a bit more active / vibrant community (I'm basing this on github stars, watchers, number of contributors and commit / merge frequency)

It sounds like tracing is the preferred option for tracing and logging. I'm happy to raise a PR to add this if we are all in agreement.
Regarding telemetry, does anyone have objections to the choice of opentelemetry?

It sounds like tracing is the preferred option for tracing and logging. I'm happy to raise a PR to add this if we are all in agreement.

I'm fine with this. Also cc @liurenjie1024 for ideas.

Regarding telemetry, does anyone have objections to the choice of opentelemetry?

opentelemetry's metrics support is currently in the Alpha stage. I believe most people primarily use it for trace. See: https://opentelemetry.io/docs/languages/rust/
I will support to use metrics instead if we don't want to depends on lib like prometheus_client directly.

Some additional context. Renjie mentioned:

Cons:
It's mixing logging with tracing. If we use tracing for logging, our logging compability will not be compatible with logger system.

This is not quite right. You can use the tracing_log crate to redirect any other crates logs that went to log to tracing:
use tracing_log::LogTracer;

// redirects all output sent to log:* to their tracing::* equivalent
LogTracer::init().expect("Failed to set logger");

Regarding metrics, my preference would be either metrics or opentelemetry. Both are vendor-agnostic with pluggable exporters. My first choice would be opentelemetry as it seems to have better cross-language recognition and a bit more active / vibrant community (I'm basing this on github stars, watchers, number of contributors and commit / merge frequency)

I have a question: the LogTracer in tracing_log is used to convert the log record into a trace event. Does this mean that if the user uses log originally and after they introduce iceberg-rust, they have two choices:

maintain trace and log separately
use trace and redirect all original log records into trace events.
For users, is it a more ideal behavior to redirect the trace to the original log? 🤔


Fix odd multi-file error that duplicates current doc into preview window

Presently with multi-files, if we create another file, then return to index.html any keys pressed within brackets will duplicate whatever is in the preview window, presented below in a screen shot and video:

https://www.youtube.com/watch?v=oowVRR8IDZI&feature=youtu.be

@KeniMorri I'm working on this, it's related to this [issue] (https://github.com/humphd/brackets-browser-livedev/pull/28)

@KeniMorri upon further investigation, it appears that the [copy/paste] (https://github.com/adobe/brackets/pull/10653) patch fixes this issue.

Fixed with copy/paste patch


Add introductory hello-world exercise

This addresses exercism/rossconf#2 towards goal #12.
The hello-world exercise has three test cases, one for no name given, one for the name 'Alice' given and one for the name 'Bob' given. This is to avoid the hardcoding of a name into the solution.

This looks great. I'm going to hold off on merging it until we have the code in place to ignore hello-world in the nitpicking list, and to submit an encouraging comment by rikki-.
Would you submit a separate PR with the SETUP.md? That would be useful to have even before hello world goes live.

Thanks for the feedback! I've removed the SETUP.md commit.

:heart: here we go!

Wahey! Awesome, still getting you that Obj-C version. :smile:

Niiiice!


Bug Report: when I pass the first song of week 3 the game closes

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
What version of the game are you using? Look in the bottom left corner of the main menu.
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Please describe your issue. Provide extensive detail and images if possible.

this is a confirmed bug , and still in the fixing


Video name

What are you trying to achieve?
Having a video for a failed test with the scenario name, as for screenshots.
What do you get instead?
File names with ids similar to "2f6507fa202d0d3e5d8cc2a55850a285.webm"
Details

CodeceptJS version: 3.3.5
NodeJS Version: 16.10.0
Operating System: Win 10 Pro
playwright
Configuration file:

require('ts-node/register')
const { setHeadlessWhen } = require('@codeceptjs/configure')

// turn on headless mode when running with HEADLESS=true environment variable
// HEADLESS=true npx codecept run
setHeadlessWhen(process.env.TEST_HEADLESS === 'true')

exports.config = {
	tests: './tests/*/**_test.ts',
	output: './tests/output',
	timeout: 240, // limit all tests in all suites to 240 secs
	helpers: {
		Playwright: {
			browser: 'chromium',
			show: true,
			url:'http://localhost:3030',
			video: true,
			trace: false,
			// keepTraceForPassedTests: true,
			waitForAction: 2000,
			waitForTimeout: 30000,
			windowSize: '1800x920',
		},
	},
	bootstrapAll: require('./presettings.ts').bootstrapAll,
	bootstrap: require('./presettings.ts').bootstrap,
	teardownAll: require('./presettings').teardownAll,
	teardown: require('./presettings').teardown,
	plugins: {
		subtitles: {
			enabled: true
		},
		pauseOnFail: {},
		retryFailedStep: {
			enabled: true,
		},
		tryTo: {
			enabled: true,
		},
		screenshotOnFail: {
			enabled: true,
		},
		// coverage: {
		// 	enabled: true,
		// },
	},
}

Hello,
Any news?
BR
Nicolas

I suspect that name is from Playwright.

Hello @nicostubi not any configuration is needed.


API Tests seem to be failing

CurrentApiServiceTest and HourlyApiServiceTest seem to fail.
Logs: https://gist.github.com/iamutkarshtiwari/cbb6c382f07d20584a19ab45f2c00d52

It should be fixed now. Seems like I modified the models but didn't update the tests.

Thank you! 🙏 I am learning a lot from your project.

Thanks you too for pointing it out.


add innounp

I'd like to suggest that innounp, the Inno Setup Unpacker, be added to flare-vm. Its available here: http://innounp.sourceforge.net/

also: http://constexpr.org/innoextract/

Both are added! I also added UniExtract2 which can extract many different file types.


Blazor Security/Authorisation

Please consider a claim/policy based client-side authorisation framework where user claims/cookies can be evaluated with in the blazor runtime, to enable/disable application functionality/ui features based on user claims/policy evaluation.

I'm sorry, but doesn't this strike anyone else as inherently insecure and unsafe?  The client runs in the user's browser.  They can change anything.  Put authorisation/authentication in the data source, not on the client.
It might be nice to have for convenience but it would only encourage developers to rely on it when they absolutely shouldn't.
And we can already do this.  System.Net.HttpClient can handle the a bearer authentication token without issue.

@richbryant I think your misunderstanding this topic; a claims based policy systems that has nothing to do with authentication; claims would be issued by a claims server/service and digitally secured so that these can't be modified; complied blazor code running in the browser would determine if a claims token has been issued that fulfils the policy required to perform an action.  claims tokens are ready in use by any number of browser application in the form of JWT/access token and stored in cookies for Facebook, Twitter, etc.  however I would defer to @blowdart the security expert for comment if he thinks this would weaken/create security issues?

I'm afraid I'm going to lean towards nope, unless the token itself is kept on the client side, and meant for a client app ID (for example using Facebook's javascript SDK so a server is never involved). At which point generally everyone has SDKs for their own tokens, or you parse and validate the JWT yourself. Server side, well, if you start asking a server "Show/Hide X" and you can just use fiddler or dev tools to influence the result then obviously that's not something we should depend on.
Now I take your point that no, this isn't really security, it's UI, but would all our users be that informed? Would they suddenly see claims and think "Hey this is security". I think that from an API design perspective this one will confuse people and ultimately lead to sadness when the confusion happens.
But as Blazor's a preview we haven't undergone any formal security reviews as yet.

Let's assume we have a Customers module with a few fields: name, address, credit limit. To edit credit limit field, users have to have special claims. Without special claims credit limit field is displayed as read-only. This is good user experience. Of course malicious user can try to use other tools (for example Postman) to post some data to the server. If you want to create secure application you have to check the same business rules on the server. The same is true in every application type. Here you can read about ASP.NET Core:
https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/validation?view=aspnetcore-2.1#how-validation-works
In Angular you can use route guards (https://angular.io/guide/router#guards) to hide some parts of the application from unauthorized users, for example you can disable link to example.com/customers. Probably you also have WebAPI endpoint: example.com/api/customers. Of course to make application secure you have to authorize all WebAPI requests.
In summary:

you can implement business rules on the client to create good user experience
you have to implement the same business rules on the server to create secure application

There have been ways for years for a dev to place "claims" browser side (see Forms Auth Cookies). These cookies could carry auth info as well as roles/claims. Now these cookies were posted to the server and read server-side but a cookie was exposed to the client with that info (of course encrypted). I guess just saying there is precedence for storing roles/claims browser-side.
Maybe a special type of "read-only" cookie/token with a signature that needs to be validated server-side prior to accessing? IDK I could see this implemented various ways to give the client-side a way to make presentation based decisions? Bottom-line is that whatever checks for allowed features, for example, are placed on the browser-side should be enforced server-side. If there were the shared claims/policy mechanism it would be nice to share it across browser/server side for consistent enforcement.... Sorry for the rambling...

@chassq I don't agree with "If you want to create secure application you have to check the same business rules on the serve", no you always have to do it on server side, if you want to improve UX you can do it on client side as well but it's not mandatory (just like form validation).
What you need is just an endpoint on your server that send the claims available serialized for the authenticated user, so the cookie reading will only happen on server side.

@remibou don't think I said what was in your quotes... I do agree all checks should be server side.. My point is only it would be nice to share the same claim policy framework to the point it makes passing and checking the claims seamless and consistent between client and server...

I'm sorry your avatar looks like the one on the comment before yours, I edited.

Something like the following?
[Authorize("myPolicy")]
@ page "customers"

So I'm working on an authentication system that will be able to handle the various providers. It works completely client-side, uses ClaimsPrincipal, and doesn't expose any secret keys or anything like that.
Now, my question is this: I'm working on the token refresh mechanism, and I need to know: does the HttpClient instance reuses the browser's CookieContainer when it makes requests? I'm hoping it does, because I need to be able to make a GET request to a location I previously redirected to, and I'll need the previous cookie from the Redirect to be available.
Thanks!

@robertmclaws The HttpClient uses JS interop to call into the fetch API (BrowserHttpMessageHandler). We don't introduce a new cookie container.

At a high level, how does this ticket relate to server-side rendered blazor components?
Isn't that going to require a full authorisation framework to invoke server side code, because it will not happen via the fetch api?

@shadowmint I don't follow? AFAIA the cookie that is supplied to the server-side rendered blazor components would be the claims cookie that was given to the user at sign-in just like and use the standard roles/claims a standard .net core web application?

@grahamehorner yes, but normally an authorisation policy would be applied, eg. in MVC, at the controller; I don't understand where this would be done in this case?
Or would the component be required to authenticate the user request manually based on the claims? ...in which case, doesn't the client-only blazor need to know about claims?
Perhaps I haven't understood how this is supposed to work; are there any examples of applying an authentication policy using server-side blazor?

So this is going to be interesting to work out.
I'm working on a framework that allows client-side Blazor to authenticate with 3rd party systems like Auth0 through regular C#, not importing JS libraries. It's wired up in Startup.cs, and should feel very familiar to OWIN and ASP.NET Core developers.
I'm working on a blog post about this, but here's the gist of it:

The first Action returns a redirect URL so the user can be redirected to the auth page. The second Func processes the return payload into a ClaimsPrincipal. Gluing it all together is a Blazor page that pulls the payload out of the URL and marshalls it back to AppStateBase.

So then you can modify MainLayout.cshtml to have login controls, like this:

The beauty of this system is that everything responds in real-time, the AppStateBase tracks authentication, but you can easily inherit from that to track other state data that is not specific to your ViewModels.
I'm working now to try to figure out the best way to handle refreshing your tokens, and if it's possible to have an @authorize declaration (or an equivalent) and what happens when you're not authorized. If you have any ideas, please post here, or in the related BlazorEssentials issue.
So that was long-winded, but the interesting part will be how well all this works in Server-Side Blazor. I haven't had a chance to set that up yet and see if what I have now will need to be changed.
Feedback welcome :).

It would be nice to have an @authorize directive which would turn into an [Authorize] attribute on the Component class. Then making it possible to hook into the authorization logic into the Router like a middleware.
@authorize
@authorize "Operator", "Partner"

@robertmclaws is this sample in github?

@xrkolovos Yep, it should be in there. https://github.com/CloudNimble/BlazorEssentials/tree/master/src/CloudNimble.BlazorEssentials.TestApp

Authorization is a real headache especially for beginners like me. It would be really nice if there was a @Authorize that would be the same as [authorize].


Use TestingT & TestingFT interfaces instead of *testing.T

formatError reworked to use Fprint (or Fprintf if a format is
detected).
Add "args..." documentation in each function using it.
tools/gen_funcs.pl checks this comment is consistent everywhere.
Signed-off-by: Maxime Soulé<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 72

99 of 99 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 98.963%

Totals

Change from base Build 69:
0.002%

Covered Lines:
3339

Relevant Lines:
3374

💛  - Coveralls

Pull Request Test Coverage Report for Build 72

99 of 99 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 98.963%

Totals

Change from base Build 69:
0.002%

Covered Lines:
3339

Relevant Lines:
3374

💛  - Coveralls


Add Profit Margin Calculator

This  calculator allows the user to input the revenue, costs, and type of costs (fixed or percentage of revenue), and calculates the profit margin in real-time as the user types.
@Srijita-Mandal , I would like to work on this issue under jwoc.

@Laxmankohar Yes. Go for it.


Add documentation about how to deploy with Vercel

Update README.md file to include documentation about how to deploy the website with vercel

https://github.com/abbyfischler/css-starter/pull/1

Vercel has a neat button to make this really easy!

[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fhackclub%2Fcss-starter)

and a Netlify one:

[![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg)](https://app.netlify.com/start/deploy?repository=https://github.com/hackclub/css-starter)

https://github.com/hackclub/css-starter/pull/5

Thanks @abbyfischler!


Add two date elements start and end date

Hi @zverbatim / @asimonok / @mikhail-vl / @githubDante / @maleksan (sorry for tagging you all didnt know whome to tag).  First of all thank you for the plugin which is continuoysly improving with features and works flawlessly.
I have added two elements(example start and end date)of type date. It also works if start date is > end date. How can i implement it ? I want user to select proper dates and then only the button should be enabled.
Also when i am trying to send the values over API. The time is not properly inserted, it always have the difference of 5 hours.
Also can the date time format can be changed  as per my wish ?

@vanimesh Regarding two elements, there was another requests to implement dependency of the elements. I am think how to implement it in the future releases, for now it's not supported.
Date elements works with the browser time, but the request will be sent in UTC. So your API should expect UTC time, not the local user's time.
dateTime: "2023-07-26T19:22:55.000Z"

You can update the data time format using Custom Update Request, instead of predefined, and update any values as you wish: https://volkovlabs.io/plugins/volkovlabs-form-panel/request/
I will think of implementing the Custom Code for the updated request before the request, which can help with your request.

So can we send the browser timezone as a parameter? To our api? Also really waiting for dependency elements.

@vanimesh If you need the browser timezone, add it to the custom code for the initial request.
You can have a hidden String element and update its value following documentation to the browser timezone: https://volkovlabs.io/plugins/volkovlabs-form-panel/code/

Dependency for elements will be implemented in the upcoming version https://github.com/VolkovLabs/volkovlabs-form-panel/issues/198

@vanimesh Please try to stick to one question per issue. I will keep this issue for adding additional custom code to execute before the update request.


Add basic support for Unmarshall's case insensitive key finding

Addressing #84
Work in progress:

[x] non bytes.EqualFold case insensitive compare functions. (maybe added to fflib)
[ ] optimizations to avoid N comparisons for keys that we aren't Unmarshalling (consider a lower cased switch or other ideas)

Going to skip optimizations of this for right now, seems to have minimal affects on my benchmarks.


Does ContentTools have a non-inline setting?

I want to use ContentTools in a form that I'm making, it's for adding news articles.
I want to have normal inputs for the Title and Date of the news, but have a ContentTools container for the news content/body input.
Does ContentTools have a non-inline setting that can be enabled?

Hi @shockdot. Looks like you want the same as #118.

Hi @shockdot as @shvetsovdm commented this isn't a feature of ContentTools currently but has been discussed. I can't see it being a short term goal for the library unless it's taken up by others but I'd have no objection to this becoming a feature.


[BUG] .NET 5 keeps increasing the memory usage when using razor files

Rendering the razor file keeps adding to the memory. For the example I use a file that generates an output of 10MB so you see the change in memory. When returning a View() there isn't a problem but when we use the RazorTemplateEngine it keeps adding to the memory. I tried to find the problem myself but I cannot find the issue.
Test1
When using Test1() the memory increases but is stable afterwards. Same for every other view rendered by .NET

Test2
When using Test2() the memory keeps increasing. Every snapshot is taken a after calling the test again.

and the diff of snapshot #7:

Startup.cs
public void ConfigureServices([NotNull] IServiceCollection services)
  {
    // Some code

    services.AddRazorTemplating();
  }

Test.cshtml
@{
    Layout = null;
    var array = Enumerable.Repeat("A", 10000000); // 10MB string, we need to see it in memory
}

<div>
    @string.Concat(array)
</div>

TestController.cs
public class TestController : Controller {
    public async Task<IActionResult> Test1()
    {
        return View("~/Views/Shared/Test.cshtml");
    }

    public async Task<IActionResult> Test2()
    {
        var html = await RazorTemplateEngine.RenderAsync("~/Views/Shared/Test.cshtml");

        return Ok("Done");
    }
}

Interesting! I'll try to replicate & fix the issue.
Thanks for taking your time to debug & give detailed information.

Hi @Benexx , I've fixed the issue. If possible you can checkout the latest master & test. Otherwise, I'll be releasing a preview version this weekend anyway. You can test using that. Thanks

A thanks! I'll test it maybe this weekend or else on Monday! Thanks for the quick response!

I have tested the memory usage and the problem seems to be solved! Thanks again for the quick response!

That's good to know! I'll make a release for this fix

Update:
New version v1.5.0 with the fix has been released
A much thanks to @Benexx for spotting this issue 💯🥇


ErrorInvalidRegion when uploading images to CustomVision.ai

Hi,
I'm trying to build ObjectDetector model using customvision.ai. As we know web UI does not provide any option to zoom in or out functionality. I'm dealing with large-sized images and need to zoom in to annotate the objects properly. So instead of web UI now I'm using LabelImg tool to annotate the images and Azure python SDK to tag and upload images on customvision.ai.
I'm aware that the custom vision needs coordinates in normalized format and LabelImg provides those coordinates I believe. If you go through the below dict you will notice few images have a single object and a few might have multiple objects. I'm interpreting below coordinates as x, y, w, h.
{'1-A223': [ [0.088942, 0.126316, 0.168269, 0.168421],
[0.592147, 0.131579, 0.254808, 0.178947],
[0.774038, 0.136842, 0.073718, 0.168421],
[0.865385, 0.131579, 0.073718, 0.178947],
[0.956731, 0.136842, 0.073718, 0.189474],
[0.228365, 0.489474, 0.075321, 0.852632],
[0.31891, 0.468421, 0.076923, 0.852632],
[0.409455, 0.263158, 0.075321, 0.442105] ],
'1-A312': [ [0.495033, 0.47191, 0.963576, 0.876404] ],
'2-A223A': [ [0.091346, 0.457143, 0.173077, 0.857143],
[0.295673, 0.457143, 0.171474, 0.8],
[0.498397, 0.442857, 0.173077, 0.771429],
[0.701923, 0.471429, 0.169872, 0.771429],
[0.907853, 0.5, 0.171474, 0.828571] ],
'2-A223B': [ [0.233974, 0.465909, 0.464744, 0.840909],
[0.746795, 0.488636, 0.490385, 0.886364] ] }
Sample Code Screenshot
For the above coordinates, it's showing ErrorInvalidRegion. I'm not sure if is it because of the SDK issue or if something is wrong with the coordinates. I used the above coordinates to draw a rectangle on it I multiplied w with the actual width of the image and h with the actual height of the image.
Sample Code to draw a rectangle on image

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

ID: 0b47b105-296c-139f-7e2c-d4d143aa1ccd
Version Independent ID: 7c55bf3c-739f-8e7d-6dee-40409ffbe548
Content: Quickstart: Object detection with Custom Vision client library - Azure Cognitive Services
Content Source: articles/cognitive-services/Custom-Vision-Service/quickstarts/object-detection.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

Thanks for the feedback! We are currently investigating and will update you shortly.

Hello @shubhamjante, I am sorry this issue seems out of scope for this forum, I will highly suggest you to raise a support ticket for this issue or post it to Microsoft Q&A platform.
Please let me know if you have no support plan and I am willing to enable you one, forwarded this issue to product team for checking if this is a SDK issue as well.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

Was that solved? If yes, where can I find the solution? I'm facing the same issue.


Support for sphinx 7 and onwards

Closes #130

Actually all tests are passing on my fork :tada: https://github.com/LecrisUT/sphinx-design/pull/1

@choldgraf in case you missed it and sorry for the ping if you are not the one I should have pinged :)

Hello, hello! Any update on this?

@chrisjsewell -- sorry for the ping, would it be possible to look at this PR to support Sphinx 7 in sphinx-design please? From my perspective all seems fine, but I'm not sure who has permissions to do a release on the executable books team.
Thanks,
Adam

superceded by #148


Added basic erc20 test contract.

Stack:

#1866
#1864
#1863
#1862
#1860
#1857
#1855
#1854
#1853 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

crates/cairo-lang-starknet/src/plugin_test_data/hello_starknet line 91 at r1 (raw file):

                    let mut err_data = array_new();
                    array_append(ref err_data, 'Out of gas');
                    panic(err_data);

both options compile?
Code quote:
 panic(err_data);

crates/cairo-lang-starknet/test_data/erc20.cairo line 7 at r1 (raw file):

    total_supply: u256,
    balances: Map::<felt, u256>,
    allowances: Map::<(felt, felt), u256>,

is it hard to fix the formatting?
Code quote:
    struct Storage { name: felt, symbol: felt, // TODO(orizi): Move to u8.
    decimals: felt,
    total_supply: u256,
    balances: Map::<felt, u256>,
    allowances: Map::<(felt, felt), u256>,
    }

crates/cairo-lang-starknet/test_data/erc20.cairo line 106 at r1 (raw file):

        let current_allowance = allowances::read((owner, spender));
        let ONES_MASK = 0xffffffffffffffffffffffffffffffff_u128;
        if current_allowance.low != ONES_MASK | current_allowance.high != ONES_MASK {

can you move this to
is_unlimited_allowence()?
Code quote:
 if current_allowance.low != ONES_MASK | current_allowance.high != ONES_MASK

crates/cairo-lang-starknet/test_data/erc20.cairo line 21 at r1 (raw file):
Previously, orizi wrote…
https://github.com/OpenZeppelin/cairo-contracts/blob/ad399728e6fcd5956a4ed347fb5e8ee731d37ec4/src/openzeppelin/token/erc20/library.cairo#L228

but the constructor does not call mint.

crates/cairo-lang-starknet/test_data/erc20.cairo line 107 at r2 (raw file):
Previously, orizi wrote…
Done.

I don't see it

crates/cairo-lang-starknet/test_data/erc20.cairo line 107 at r2 (raw file):
Previously, orizi wrote…
look again

don't you want to change the allowance only if it is not unlimited ?

crates/cairo-lang-starknet/test_data/erc20.cairo line 107 at r2 (raw file):
Previously, orizi wrote…
right - fixing

I misspelled allowance
Suggestion:
allowance


Support to configure logging levels for sqltools services

Adding support for configuring SqlTools log levels from user configuration. This also adds changes to see the tail of the sqltools log file in the newly created 'Output->Log (SqlTools)' channel

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


Update bicep-import.md to remove experimental notices

Removing "experimental" notes as compileTimeImports and userDefinedFunctions are now no longer experimental.

@mumian
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


ng serve doesn't work in FAT32 driver of windows

OS: Windows 7 x64

angular-cli: 1.0.0-beta.5
node: 4.4.5
os: win32 x64

ng new project
cd project
ng serve

The Broccoli Plugin: [Funnel] failed with: Error: EISDIR: illegal operation on a directory, symlink '...\src' -> '...\tmp\funnel-input_base_path-CWcRWSHb.tmp\0'

It looks like that angular-cli's serve command doesn't support FAT.When I change the project directory from a FAT32 driver into a NTFS driver,it works perfect!

another error same as mine in this post:  [http://stackoverflow.com/questions/36752014/ember-js-error-eisdir-illegal-operation-on-a-directory/37588472#37588472]

forgive for my poor English

beta.5 on windows still requires admin privileges for ng serve to work. Were you running it in an admin prompt?
beta.6 won't require admin privileges though.

@filipesilva  yes,i run ng serve with runas /user:administrator in cmd.it has no effect on this issue.I also try to change the privileges of project,useless too.I am working with beta 5 in a NTFS driver now,so I believe that is the reason.
Maybe i can try beta6 in FAT32 driver in my free time,i will give feedback then.

Issue made obsolete by #1455.


Styling broken on the PIN entry screen for Windows Phone

All of the number buttons are not aligned correctly on Windows Phone.
This has to due with the custom class that is used to vertically center the buttons; once removed the buttons align properly.

Since this only affects Windows Phone 8 and not the newer Windows 10/UWP runtime, I'm going to close this as wontfix.
This can be worked around by removing the content-vertical-center class.


Move commons code to acitvemix

Hi guys
Just a quick update I am working on the erp  poc installing some dockers on
my mavhine trying to run it.  Will keep u in track this week.
On Mon, May 24, 2021, 8:28 PM Hadrian Zbarcea @.***>
wrote:

Merged #51 https://github.com/apifocal/activemix/pull/51 into master.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apifocal/activemix/pull/51#event-4787913314, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATI44B6YNY4YIC74POBL5K3TPKEC5ANCNFSM45MQBXXQ
.


Georeference UI Admin Regions: 2nd Question is Irrelevant with Country Data

Context
When geocoding based on country names, the second question in the UI is irrelevant ("Select Your Country Data"). If the user inputs their country column in answer to that 2nd question in the form, the georeferencing will fail. By leaving that 2nd question blank, the georeferencing succeeds.
Process
Import a dataset with a column of country names that need to be georeferenced
Choose the "Admin Regions" georeferencing option in the UI
Select the country column for both form questions ("Select Your Region Name" and "Select Your Country Data")
The georeferencing will fail
If you have country names, you only need to input your column in answer to the second question "Select Your Region Name" otherwise the georeferencing will fail.

S/B 9099020
Client only has 'country' column and is trying to georef by admin region - if you only choose second pulldown the 'Continue' button is inactive:

To apply on the analysis UI.
Also, we should rethink the labels on the fields. Right now they are hard to understand.

Dupe!


error onboarding the user at the auth keyserver

Running through the "new bank account use case" flow, after login to the OIDC provider, there's an onboarding error that blocks the flow:
{"errMessage":"failed to onboard the user: create operational keystore : create authz keystore : http request: failed to read resp body 400 : unexpected EOF"}

nginx.1    | 2020/12/01 20:56:38 [error] 121#121: *229 recv() failed (104: Connection reset by peer) while reading upstream, client: <IP_ADDRESS>, server: auth-rest-hydra.trustbloc.local, request: "POST /kms/ke
ystores HTTP/1.1", upstream: "http://<IP_ADDRESS>:11201/kms/keystores", host: "ops-kms.trustbloc.local"
nginx.1    | ops-kms.trustbloc.local <IP_ADDRESS> - - [01/Dec/2020:20:56:38 +0000] "POST /kms/keystores HTTP/1.1" 400 54 "-" "Go-http-client/1.1"

nginx.1    | authz-kms.trustbloc.local <IP_ADDRESS> - - [01/Dec/2020:20:56:37 +0000] "POST /kms/keystores HTTP/1.1" 201 0 "-" "Go-http-client/1.1"
nginx.1    | authz-kms.trustbloc.local <IP_ADDRESS> - - [01/Dec/2020:20:56:37 +0000] "POST /kms/keystores/bv3as15bpp2i7bda52o0/keys HTTP/1.1" 201 0 "-" "Go-http-client/1.1"
nginx.1    | authz-kms.trustbloc.local <IP_ADDRESS> - - [01/Dec/2020:20:56:37 +0000] "GET /kms/keystores/bv3as15bpp2i7bda52o0/keys/eXx4IBgQUvdNXONnWHd0Wgyewybdy7KimueG2BYgP78/export HTTP/1.1" 200 61 "-" "Go-http-client/1.1"

This error doesn't occur all the time; restarting the docker containers usually solves it.


move feature selection up?

 I think it should be together with the supervised learning.

Haha, sorry for all my counter-arguments in the last 5 minutes ... :P. I actually think that having a separate feature selection notebook may be useful rather ... for clarity and also as a future reference for the attendees. E.g., "How do I do feature selection again, ahja wait, we had this notebook here ... "

I didn't mean remove the notebook. I meant reorganize the toc. I think it would make more sense after 24 rather than after 26

Oh okay, with that I agree! :) I thought you meant merging the content of the notebook into the other one ... Okay, then let me merge your pull requests first ...

done in 2d83abbeaf89a9540540ef71e2ecf6bef5adb982


Sunstone truncates supported advanced disk options when HYPERVISOR=LXC

Description
When the VM Template has HYPERVISOR=LXC it hides advanced options under the IMAGE section which are currently supported.  Cache and size on instantiate are implemented features on the driver.
There are also other sections whose contents are hidden but the sections are shown anyways.

To Reproduce

Select LXC hypervisor on VM Template
Click Advanced options on the disk section

Expected behavior
Features supported by the driver should not be hidden.

cache
size on instantiate

Truncated sections should hide the heading of the section as well.
Details

Version: 6.0, 6.2, master

Progress Status

[x] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

@tinova PRs to be approved:

Code: https://github.com/OpenNebula/one-ee/pull/1709
Docs: https://github.com/OpenNebula/docs/pull/2116


Access HTTP Headers from Event Handlers

Description
I am hosting Bolt on a serverless option from GCP which has a slow VM start time. As a result, on the first request to a VM, the response is delayed and so the Slack Events API interprets this as an error, and sends a second (and sometimes a third request). However, the slow Bolt server does eventually load and processes the first, second (and sometimes third) request, resulting in duplicate responses. This is a bad time.
I am aware of the presence of the Slack header which indicates the retry number, which could be used to ameliorate the issue described above. However, - at least in the case of the ExpressReceiver - it appears that the event data which is passed to the bolt handler only contains the request body.
I am proposing that headers be included in the the event data passed to Bolt handler functions. This allows handlers to be sensitive to Slack Retry information (& any other information also carried in the HTTP Headers). In other words alter the definition of ReceiverEvent & its usages:
  export interface ReceiverEvent {
    body: StringIndexed;
    headers: StringIndexed; // new field
    ack: AckFn<any>;
  }

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[X] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Hey @kaifresh, thanks for suggesting the HTTP Header enhancement and discussing your implementation details. We're also grateful to hear how you're hosting your Bolt app - hearing these details helps us make better decisions! 🙏🏻
(Also, thank you to everyone who's +1 this issue, please keep those coming!)
Access to HTTP headers has been requested before and we originally planned to include it in the Bolt 3.0 release (see #670). Unfortunately, it didn't make the major release but we want to follow up with a minor update to include it.
I think we'll start to use this issue as the place to track that work. I've labeled it as an enhancement but we may switch it to a discussion if we need to work out more details.

Hey @kaifresh, thanks for suggesting the HTTP Header enhancement and discussing your implementation details. We're also grateful to hear how you're hosting your Bolt app - hearing these details helps us make better decisions! 🙏🏻
(Also, thank you to everyone who's +1 this issue, please keep those coming!)
Access to HTTP headers has been requested before and we originally planned to include it in the Bolt 3.0 release (see #670). Unfortunately, it didn't make the major release but we want to follow up with a minor update to include it.
I think we'll start to use this issue as the place to track that work. I've labeled it as an enhancement but we may switch it to a discussion if we need to work out more details.

Hi,
I was just about to open a similar request. We're experiencing the same issues running on Firebase Cloud Functions. Almost everything is working well, but our biggest issue right now are the cold starts of our functions which generates retries which generates duplicate requests. I've tried different ways to stop this, but the easiest way by far would be to use the Slack Event API header which shows retry number, but I'm right now unable to access it. Would love to get access to this. Would that be possible?
Thanks!

Hi,
I was just about to open a similar request. We're experiencing the same issues running on Firebase Cloud Functions. Almost everything is working well, but our biggest issue right now are the cold starts of our functions which generates retries which generates duplicate requests. I've tried different ways to stop this, but the easiest way by far would be to use the Slack Event API header which shows retry number, but I'm right now unable to access it. Would love to get access to this. Would that be possible?
Thanks!

Thanks for the +1 @GuineaPigApp!
The cold start is a frustrating issue with FaaS hosting. Just to make sure, are you also using the processBeforeResponse options. It won't solve the cold start issue, but it can solve some race conditions that happen with Lambda (not sure if the same issue exists on Firebase/Google Cloud).

Thanks for the +1 @GuineaPigApp!
The cold start is a frustrating issue with FaaS hosting. Just to make sure, are you also using the processBeforeResponse options. It won't solve the cold start issue, but it can solve some race conditions that happen with Lambda (not sure if the same issue exists on Firebase/Google Cloud).

Hi @mwbrooks,
Yes! Here's how we're doing it right now:
const app = new App({     receiver: expressReceiver,     authorize: authorizeFn,     processBeforeResponse: true });
I just tried to set up a http function that'd first check the headers from Slack and then push it to the functions.https.onRequest(expressReceiver.app), but I forgot that I'd get this error so it didn't end up working: Request verification failed (code: slack_bolt_receiver_authenticity_error, message: Slack request signing verification failed. Signature mismatch.).
Is there any quick workaround that you could suggest to access the request headers or somehow avoid getting these retries due to cold starts? As a follow up to that: Do retries have any of the same data, such as trigger_id or event_id? If so, maybe I could try to store these in a database when I get a new request and remove it when the function is done, checking at the start of every function if this trigger_id or event_id is already there? If the ids are not the same, I don't know how else I could check if it's a retry without the request headers. Really appreciate the help, thanks!

Hi @mwbrooks,
Yes! Here's how we're doing it right now:
const app = new App({     receiver: expressReceiver,     authorize: authorizeFn,     processBeforeResponse: true });
I just tried to set up a http function that'd first check the headers from Slack and then push it to the functions.https.onRequest(expressReceiver.app), but I forgot that I'd get this error so it didn't end up working: Request verification failed (code: slack_bolt_receiver_authenticity_error, message: Slack request signing verification failed. Signature mismatch.).
Is there any quick workaround that you could suggest to access the request headers or somehow avoid getting these retries due to cold starts? As a follow up to that: Do retries have any of the same data, such as trigger_id or event_id? If so, maybe I could try to store these in a database when I get a new request and remove it when the function is done, checking at the start of every function if this trigger_id or event_id is already there? If the ids are not the same, I don't know how else I could check if it's a retry without the request headers. Really appreciate the help, thanks!


qubes-core-vchan-xen: init at 4.1.0

Motivation for this change
Adding core QubesOS services for better integration.
During CCCamp19 we (@erictapen, +others) sat down with @marmarek and talked about NixOS Integration in QubesOS.
This package is a dependency for qubes-core-qrexec.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option 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 nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

I haven't uploaded my WIP version yet (I've got half into qrexec packaging), but I did improved makefile in qubes-core-vchan-xen upstream. On camp we've hit various issues about library paths (pkgconfig file, include etc). Now it's possible to put them in /lib /include etc, instead of /usr, with a PREFIX=/.

And thanks for pushing it here!

So this just seem to be some header files and nothing else? so not much to review then I guess

There should be a library (.so) too.

/nix/store/nwjvmbqp3ldzy9hhbcd363sldimhg3s3-qubes-core-vchan-xen-4.1.2
├── include
│   ├── u2mfn-kernel.h
│   ├── u2mfnlib.h
│   └── vchan-xen
│       └── libvchan.h
└── lib
    ├── libu2mfn.so
    ├── libvchan-xen.so
    └── pkgconfig
        └── vchan-xen.pc

4 directories, 6 files


set white of first column in jstree to normal (#6856)

backport #6856

Coverage remained the same at 78.215% when pulling 10eb9eb5ed02bb76094324d0df8cd9eb35473003 on FinalAngel:release/3.7.x into 5027a5e27efbbb29f9586ac0f751ec444f593b92 on divio:release/3.7.x.


[Menu Entry Swapper] Add a shift click option for House Portals

Being able to configure a secondary option like build mode or friends house as shift click option for house portals would come in super handy!
Cheers

Duplicate of #14813

Hi there, not sure if this still counts as duplicate or not, but i was referring to a shift click object swap on house portals, opposed to a UI swap for the house teleport spell as the other thread suggested.


test: Delete hubble-ca-secret when cleaning up

Remove hubble-ca-secret when cleaning up Cilium components. Otherwise
tests can fail installing Cilium with this error message:
Error: rendered manifests contain a resource that already
exists. Unable to continue with install: existing resource conflict:
kind: Secret, namespace: kube-system, name: hubble-ca-secret
Add a clean up call to the Cilium install code to clean up any
resources that may be left behind after kubectl delete on the cilium
yaml.
Signed-off-by: Jarno Rajahalme<EMAIL_ADDRESS>

@jrajahalme I assume we can close #17525?

I had forgotten about that. It has more reviews and still does not need to be rebased, so I'll close this one instead.

Oops, there are a number of CI flakes on #17525, so I'll reopen this and close that as some of them might have been resolved in the meanwhile.


EMA model lagging behind

Thanks so much for awesome work!
After around 1 Million images my model samples already look pretty good, but the ema samples are still very noisy (FID of 450 vs. 76). Does this make sense?
I thought in general the ema model is supposed to have better and more stable results.

It makes sense. One million images are only ~8000 iterations with 128 batch size. This still leaves traces of initial weights on the EMA model, not long enough for it to reach a sensible region of weights.

Is this because the ema decay factor is too small for fp16 precision? when doing ema the target model precision is also fp16 and the default ema decay factor is 0.9999

could this be related to fp16 precision training?


Improve test & code clarity around requirements generation

Test now checks for dev dependency "pytest==3.1.1" rather than the
characters of the string
Test verifies that dev dependencies are excluded by default
Corrected intent of returned variables from merge_deps call in cli.py

@idoru thanks for the first time contribution.  This actually looks really good.  I thought I had concerns but upon more careful consideration I think this is good to go.
@nateprewitt this doesn't alter any behavior but does provide some cleanup

✨🍰✨


Gitea panic

Gitea version (or commit ref): v1.11.1
Git version: v2.11.0
Operating system: Debian Stretch
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

https://gist.github.com/rvillablanca/565f1d13615cd02191e44d38a44011a1
Description
This just happened when merging a PR

I've reported some others bugs related with panics in gitea and I have the impression there is no middleware catching unhandled panics, I have to check in the source code for this.

Closing because it was fixed by #10408


"Recommend a friend" for alerts?

Should we have a "recommend a friend" option for alerts?
I.e. you can put someone else's email address, who will then receive the latest alert for that practice/CCG, saying who it was that recommended it, and how to sign up. (Of course you can already sign someone else up.. but it would probably require you to also email them to explain what it is and why you've done it.)
I was thinking maybe that CCG meds op people for example may want to recommend it to some of their GPs.
@brianmackenna said:

Sounds like a nice things for GPs who are prescribing leads in practices especially.

Safeguards:

Restrict to once ever per recipient
Once the sender has entered their email address, run a check to make sure we are sending them an alert. If not, prevent sending to any friends and say "Looks like you're not signed up for any alerts. Please sign yourself up before recommending a friend"
Or could require 2-step confirmation process, i.e. recommender must confirm they have a valid email address first so people can't create unwanted spam anonymously.

Issues

For NHS people the email may be likely to go to spam box and not be seen anyway. As an alternative we could have a prewritten email for people to send to their friends
I think this could be a good feature and encourage people to get others to sign up... but we should consider how much we think it would be used. Twitter poll maybe??

Re spam and sign up from two step confirmation. I registered about 10 GPs (they all consented) on their behalf to the alert for Islington Central Medical Centre (F83010) in in the last year. To inform our decision could we check that practice to see what their confirmation rate was?


Support automatically download ARM template for given resource

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Extension name (the extension in question)
cli-translator
Description of issue (in as much detail as possible)
Currently user has to download resource template manually from portal and then use cli-translator command to translate it to executable CLI commands, which is not convenient.
It will be better to support download template automatically so that user can only specify the resource name/id.

cli translator

cli-translator

https://docs.microsoft.com/en-us/rest/api/resources/resourcegroups/exporttemplate


[SPARK-44925][K8S] K8s default service token file should not be materialized into token

What changes were proposed in this pull request?
This PR aims to stop materializing OAuth token from the default service token file, /var/run/secrets/kubernetes.io/serviceaccount/token, because the content of volumes varies which means being renewed or expired by K8s control plane. We need to read the content in a on-demand manner to be in the up-to-date status.
Note the followings:

Since we use autoConfigure for K8s client, K8s client still uses the default service tokens if exists and needed.

https://github.com/apache/spark/blob/13588c10cbc380ecba1231223425eaad2eb9ec80/resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/SparkKubernetesClientFactory.scala#L91

This PR doesn't change Spark's behavior for the user-provided token file location. Spark will load the content of the user-provided token file locations to get OAuth token because Spark cannot assume that the files of that locations are refreshed or not in the future.

Why are the changes needed?
BoundServiceAccountTokenVolume became Stable at K8s 1.22.

KEP-1205 Bound Service Account Tokens : BoundServiceAccountTokenVolume

Alpha
Beta
GA

1.13
1.21
1.22

EKS Service Account with 90 Days Expiration

For Amazon EKS clusters, the extended expiry period is 90 days. Your Amazon EKS cluster's Kubernetes API server rejects requests with tokens that are greater than 90 days old.

As of today, all supported EKS clusters are from 1.23 to 1.27 which means we always use BoundServiceAccountTokenVolume.

Does this PR introduce any user-facing change?
No. This fixes only the bugs caused by some outdated tokens where K8s control plane denies Spark's K8s API invocation.
How was this patch tested?
Pass the CIs with the all existing unit tests and integration tests.
Was this patch authored or co-authored using generative AI tooling?
No.

Thank you so much, @yaooqinn !

Merged to master/3.5/3.4/3.3.