Switch up nox -s test_env and add nox -s dev_env

Closes https://github.com/ethyca/fides/issues/2385
Code Changes

[x] Refactors the original nox -s test_env session function so we can reuse most of its functionality for nox -s dev_env
[x] Add separate stage for running npm run export so that local-ui doesn't have to run this (time intensive) step when it's just trying to npm run dev

Steps to Confirm

[ ] Make sure you don't have anything in your local src/fides/ui-build/static/admin/ for the purpose of these confirmation steps
[ ] Run nox -s dev_env. Things should behave the same as the old nox -s test_env command. For example, try editing an endpoint (i.e. the health endpoint) and saving. Hot reload should kick in, and your endpoint will have your new edits in it. The local-ui image should also take less time to build. If you navigate to localhost:8080, you should see "Privacy is a Human Right!" since your local src/fides/ui-build/static/admin/ will have volume mounted over where the package is trying to serve the frontend
[ ] Run nox -s test_env. Navigate to localhost:8080. You should see the latest built frontend image, even though you have nothing in src/fides/ui-build/static/admin/ (this is because installing via the wheel has the built frontend within the package). Everything else should also come up without problem as well

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[x] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[x] Update CHANGELOG.md

Description Of Changes
Some considerations:

Perhaps nox -s test_env should not be building/running the admin ui at all, since then it will exist on both 8080 and 3000. To do this would involve modifying the base docker-compose file though, and I didn't want to make big changes here
Privacy center does not hot reload—its docker image always builds the UI and serves it. It would be nice of nox -s dev_env served up a development privacy center, but that seemed out of the scope of this PR

@allisonking I'm going through and testing and everything looks good, but my one nit (gotta have one, right? 😂 ) is the naming.
we already have nox -s dev which should be the dev environment right? So really dev_env is more like test_env but with hot reloading? (i know there are more fundamental differences, but that's what the docstring says)
My only ask here is that we flesh out better descriptions/potentially better names here so it is transparent to developers when to use which environment and for what

I went ahead and became the change I wanted to see in the world, lmk what your thoughts are 🙂

all of the tests that failed here were related to a git error, rerunning the tests to verify

we already have nox -s dev which should be the dev environment right? So really dev_env is more like test_env but with hot reloading? (i know there are more fundamental differences, but that's what the docstring says)

yup yup, I like the change you made to make it fides_env(dev) and fides_env(test).
I like the param change you made! but wondering if there's a way to make the nox command which lists out all commands a little more helpful here? or to say something different for each param? I know you have the param documented, but not sure where that shows up other than in the code
$ nox
...
- fides_env(dev) -> Spins up a full fides environment seeded with data.
- fides_env(test) -> Spins up a full fides environment seeded with data.
...

we already have nox -s dev which should be the dev environment right? So really dev_env is more like test_env but with hot reloading? (i know there are more fundamental differences, but that's what the docstring says)

yup yup, I like the change you made to make it fides_env(dev) and fides_env(test).
I like the param change you made! but wondering if there's a way to make the nox command which lists out all commands a little more helpful here? or to say something different for each param? I know you have the param documented, but not sure where that shows up other than in the code
$ nox
...
- fides_env(dev) -> Spins up a full fides environment seeded with data.
- fides_env(test) -> Spins up a full fides environment seeded with data.
...

This is totally my bad for not communicating this more! I added a nox command that prints out the full docstring to help with this (noxception?)
nox -s  usage -- fides_env will show the whole docstring

I'm going to merge the fix from https://github.com/ethyca/fides/pull/2441 in when its ready


Fixes #13

@saniales I'm fine giving it a try, but I'd please prefer to keep the two mods separate.
Would you mind keeping here the actions mod and keep in #12 the other mod?
Thanks

I'm on it


Regression with generating multipart requests

After migration from Spring Cloud contract 2.2.7.RELEASE to 3.0.3. Cloud contract tests which use multipart content-type started failing with 400 Bad Request reason. After the analyse of the generated contracts I have found that one line is missed into the new version of Spring Cloud contracts.
Example of the contract - contract wasn't changed between the versions
Contract.make {
    request {
        method POST()
        url '/attachments'
        headers {
            header 'Content-Type': value(client(regex('multipart/form-data; ?boundary=.+')), server('multipart/form-data;boundary=AaB03x'))
        }
        multipart(
            file: named(
                name: $(c(regex(nonEmpty())), p('filename.csv')),
                content: $(c(regex(nonEmpty())), p('file content'))
            )
        )
    }
    response {
        status CREATED()
    }
}

It is almost the same as example provided here - https://cloud.spring.io/spring-cloud-contract/reference/html/project-features.html#contract-dsl-multiple
The generated code in Spring Cloud contract version 2.2.7.RELEASE
def validate_shouldReturnCreatedForUploadAttachments() throws Exception {
   given:
      RequestSpecification request = given()
            .header("Content-Type", "multipart/form-data;boundary=AaB03x")
            .multiPart('file', 'filename.csv', 'file content'.bytes)
   when:
      Response response = given().spec(request)
            .post("/attachments")
   then:
      response.statusCode() == 201
}

The generated code in  Spring Cloud contract version 3.0.3
	def validate_shouldReturnCreatedForUploadAttachments() throws Exception {
		given:
			RequestSpecification request = given()
					.header("Content-Type", "multipart/form-data;boundary=AaB03x")

		when:
			Response response = given().spec(request)
					.post("/attachments")

		then:
			response.statusCode() == 201
	}

It is possible to spot that the following line is missed
.multiPart('file', 'filename.csv', 'file content'.bytes)
When I have added this line manual and run the test with the new version of Spring Cloud contracts it passed however I am not able to force proper generation of the contract with this line.

Hi, I tried to reproduce this bug, but couldn't reproduce it. Generated codes in both versions 2.2.7.RELEASE and 3.0.3 seem to contain .multiPart('file', 'filename.csv', 'file content'.bytes) correctly. Maybe need the steps to reproduce it.

I provided the example of the specification. What extra steps can I provide you?
I have re-written those tests to average integration tests so I can not check in my source code anymore. Which was a good idea as since I reported the issue passed almost 9 months.

What I know for sure compare to your use cases you test usually in maven but my code is in Gradle. In that moment it was version 6.x but which exactly version I don't remember.

I provided the example of the specification. What extra steps can I provide you?

Preferably a sample that reproduces the problem.
BTW as you can see this issue is marked as good first issue or gracehopperOSD so there are people who are interested in getting into open source and helping us out. That means that we should do our best to be as kind as possible to them (in general we should be doing this but here we should do even more ;) ).

Could you be more specific about what is required?
I tried to do my best. I think I prepared the sample. Provide steps to reproduce is not so specific question as step to reproduce is to run tests e.g. gw clean build
I am OK to help that's why I created this ticket.
Environment: Gradle 6.x, Groovy 2.5.x (I suppose 12). I suppose tests were run via JUnit 5 platform (but now I am not sure it was pretty far away).

Please push some code that is failing to a repo on github that reproduces the problem. That way we will be sure that we can easily replicate the issue.

I tried it again in the environment @aplotnikov provided, but still cannot reproduce it. Here is the repo I used for checking: https://github.com/igarash1/spring-cloud-contract-issue1667

His is the repo. You can find the generated test but the process itself doesn't work.
You can run clean build and generate test.
https://github.com/aplotnikov/cloud-contract-test

I have tried to create is ASAP so something can be cleaned up or so.

I have found a pattern already sounds like when testMode = 'Explicit' is removed it works properly.

With explicit
package com.example.cloudcontracttest

import com.example.cloudcontracttest.BaseContractSpec
import spock.lang.Specification
import io.restassured.module.mockmvc.specification.MockMvcRequestSpecification
import io.restassured.response.ResponseOptions

import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
import static io.restassured.module.mockmvc.RestAssuredMockMvc.*

@SuppressWarnings("rawtypes")
class ContractVerifierSpec extends BaseContractSpec {

	def validate_shouldTest() throws Exception {
		given:
			MockMvcRequestSpecification request = given()
					.header("Content-Type", "multipart/form-data;boundary=AaB03x")
					.multiPart('file', 'filename.csv', 'file content'.bytes)

		when:
			ResponseOptions response = given().spec(request)
					.post("/attachments")

		then:
			response.statusCode() == 201
	}

}

Without explicit
package com.example.cloudcontracttest

import com.example.cloudcontracttest.BaseContractSpec
import spock.lang.Specification
import io.restassured.specification.RequestSpecification
import io.restassured.response.Response

import static org.springframework.cloud.contract.verifier.assertion.SpringCloudContractAssertions.assertThat
import static org.springframework.cloud.contract.verifier.util.ContractVerifierUtil.*
import static io.restassured.RestAssured.*

@SuppressWarnings("rawtypes")
class ContractVerifierSpec extends BaseContractSpec {

	def validate_shouldTest() throws Exception {
		given:
			RequestSpecification request = given()
					.header("Content-Type", "multipart/form-data;boundary=AaB03x")

		when:
			Response response = given().spec(request)
					.post("/attachments")

		then:
			response.statusCode() == 201
	}

}

Path where the test is located build/generated-test-sources/contractTest/groovy/com/example/cloudcontracttest

So actually it works for EXPLICIT and doesn't for MOCKMVC ?

I don't know what you mean by works fine.
I think the issue is reproducible for EXPLICIT but for MOCKMVC works fine = no issues.

I made a mistake in my first message https://github.com/spring-cloud/spring-cloud-contract/issues/1667#issuecomment-1073910521
I correct it in this message https://github.com/spring-cloud/spring-cloud-contract/issues/1667#issuecomment-1073921643

Most likely we're missing sth around here https://github.com/spring-cloud/spring-cloud-contract/blob/e73d6526bfb3240f9dc33d6afcf2be17e5383f49/spring-cloud-contract-verifier/src/main/java/org/springframework/cloud/contract/verifier/builder/RestAssuredGiven.java#L46 . That means that for EXPLICIT we're NOT generating a line for multipart but we're generating one for MOCKMVC

I was able to reproduce it in 3.1.1, and I also found that even for WEBTESTCLIENT (=testMode) it's not generating multipart as well.
I think we can add a class(sth like SpockExplicitMultipartGiven) here to fix this case, but can we just combine  JavaMultipartGiven and  SpockMockMvcMultipartGiven into a single class? because it seems they do the same thing.

They differ by this line https://github.com/spring-cloud/spring-cloud-contract/blob/9949ebe4a98c419db5493d6385f1d6917230dd6a/spring-cloud-contract-verifier/src/main/java/org/springframework/cloud/contract/verifier/builder/SpockMockMvcMultipartGiven.java#L68 . Yeah something is wrong with multipart in general. Indeed we should add some code where you mentioned for webTestClient approach and explicit. The idea of the architecture that we created there is to prefer duplication but have clear separation between those configuration options (webtestclient, explicit, spock etc.), so let' leave those separated but let's add the missing implementations

I see. It makes sense. I will try to make PR for this. Thanks for helping me @aplotnikov @marcingrzejszczak


Publish distributable code

Changes in order to publish transpiled code to npm registry instead of the source code.
Also removed dependency on react-native, since girders-elements can be used in web applications.

Coverage increased (+0.1%) to 75.145% when pulling 0482eabbe628f5b5ee8099204970755b305704b1 on web into 15784daa36cfc43daac94374e947c9956e831ffc on master.


[FEATURE REQ] Migrate docs to MK docs for material

Please describe the feature.
MK docs for material is much modern framework for building docs/workshop like this. It has much better support for better UX out of the box, when documenting workshops like this especially if catering alot of docs and supporting multiple language runtimes etc.
https://squidfunk.github.io/mkdocs-material/

@tjoudeh @waelkdouh Will this be of interest to evaluate, I can try spinning up a POC when I have sometime. I dont expect alot of changes in existing markdowns. So initial migration could be a lot easy.

@pankajagrawal16 please feel free to submit a PR. We can evaluate it for sure if you think it would bring value.

Site has been migrated to mkdocs. Excellent work @pankajagrawal16 !


fabric no using TLS ! how to using caliper?

node benchmark/simple/main.js -c yourconfig.json -n yournetwork.json
report create-channel.js TLS path error~

... can you expand on the above issue please? What were you trying to achieve, what did you do, etc

@gantleman TLS is the way that fabric support ，you can refer to [https://hyperledger-fabric.readthedocs.io/en/release-1.4/enable_tls.html]，or you can use the default tls network config file or the defautl no tls network config file.

@gantleman Any progress on the issue? The network examples have been reworked, for both TLS and no-TLS.


Fix typo in directory watch event

https://github.com/valtech-sd/rule-harvester/blob/4600a37037d13c4cf46d6cb10330e7d54a8cc8e0/examples/src/providers/rule_input_file_watcher.js#L37

Should probably be 'change' event? @daniellmorris

This is being handled in https://github.com/valtech-sd/rule-harvester/pull/27


Query : How to invoke a non device function from a device function

In the below code we are trying to invoke a non-device function from device function.
/* host function */
int my_rand(void)
{
static thrust::default_random_engine rng;
static thrust::uniform_int_distribution dist(0, 9999);
return dist(rng);
}
int main(void)
{
// generate random data on the host
thrust::generate(h_vec.begin(), h_vec.end(), my_rand);   /* generate(device function) internally invokes my_rand(host function)*/
}
Called function is host function and has __  host  __ as qualifier
Calling function is device function and has  __  device  __as qualifier
Facing the below issue while compiling an application in Thrust/examples
./thrust/detail/function.h:52:31: error: call from AMP-restricted function to CPU-restricted function
We tried to compile by adding __ device __ keyword while declaring the m_f function variable but the issue persists
Steps to reproduce the above error:
Step 1: Clone thrust repository from https://github.com/ROCmSoftwarePlatform/Thrust.git
Step 2:In Thrust/thrust/detail/function.h line no:51
-#ifdef  __ HIP_PLATFORM_NVCC __
return static_cast(m_f(thrust::raw_reference_cast(x)));
-#endif
Step 3:In Thrust/examples/sum.cpp line:20(Uncomment that line)
+thrust::generate(h_vec.begin(), h_vec.end(), my_rand);
Step 4: Compile using the below command
$  cp sum.cu sum.cpp
$ /opt/rocm/hip/bin/hipcc sum.cpp -I ../ -o sum.cpp.out
full_log.txt

@sriharikarnam  considering that this is actively against the CUDA specification as I understand it, I am rather certain that is not what you want to do. In fact, the error that you are getting is EXACTLY expected behaviour, please read Appendix B from here: http://docs.nvidia.com/cuda/pdf/CUDA_C_Programming_Guide.pdf, specially B.1.3, which specifically states (paraphrasing) "a host function [...] is callable from the host only". What are you actually trying to achieve? Either the example is bad or you are asking about how to do something which is illegal, the answer to that inquiry being you do not do it.

Thanks Alex we rectified the issue earlier by guarding the host function to be called from host code .
We can close this issue.


Return code 412

This specific return code should be displayed longer as user needs to understand.
probably 5 sec and display the message returned by the issuer

Can you give me a test url that returns 412? @ThierryThevenet

That is too fast : at least 5sec and need to read the text returned


Files not uploading

I am using a PHP script that is working for CKE file uploading and have a second which is just a very simple upload.php found on line (which works) but I am not getting any file upload from this component and there are no errors in the console. I get all of the responses I expect: Preparing, Getting Upload Params, Uploading, headers_recieved, done, each with Files all data looks correct. Then I get an object (with an upload date and status removed) and then Removed and File
I changed to the auto_upload example and I am having the same issue. status === "headers_received"  is true toast(${meta.name} uploaded!) executes correctly but there is no file on my server. Permissions are correct and like I said other apps are able to drop files here using this script.

Looks like an issue with our php file not being coded for multi-file.  Helpful code here https://www.php.net/manual/en/features.file-upload.multiple.php


FATAL ERROR after updating? Fix here!

When updating to a new version, it may give a FATAL ERROR when you load NBS.
Like here:

To fix this, you can either:
1. Remove Note Block Studio completely and install it again
2. Delete the settings.onbs file located inside the Data folder.
In both cases, your settings will unfortunately be reset.

I tried both reinstalling and removing settings.onbs. Still getting this message. Note Block Studio no longer loads. 3.6.0

Can you send your error message?

It’s the same issue as the picture above.


[Documentation]: please keep a single source of truth for "Known Issues". Inconsistency found.

Description of errors
I hope there is only one team making the release of ROCm.
There is a section in https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-23-40-rocm-6-0-2
Known Issues

    Running PyTorch with iGPU enabled + Discrete GPU enabled may cause crashes. See the Limitations section within the How To Guide for details.
    GPU reset may occur when running multiple heavy Machine Learning workloads at same time over an extended period of time.
    Intermittent gpureset errors may be seen with Automatic 1111 webUI with IOMMU enabled. Please see https://community.amd.com/t5/knowledge-base/tkb-p/amd-rocm-tkb for suggested resolutions.
    RX 7900 GRE may exhibit a hang rather than Out Of Memory error on BERT FP32 training loads.
    Soft hang observed when running multi-queue workloads.

None of these were mentioned at https://github.com/ROCm/ROCm/blob/develop/CHANGELOG.md
Could you please improve the accuracy and consistency of info in release notes?
Attach any links, screenshots, or additional evidence you think will be helpful.
No response

@ye-luo, thank you for catching this error.  I will forward your info to the internal team.


Customizable Morale effect

Morale should be customizable in template

Several variables have been customizable in template but most only available in Init function of the component and need to be converted to template variables


feat(graphql): factory pattern vtl generator for model directive

PR for Model directive with VTL Generator factory pattern.

Codecov Report

Merging #1188 (5880c28) into feature/rds-support (0fe7de9) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@                   Coverage Diff                   @@
##           feature/rds-support    #1188      +/-   ##
=======================================================
- Coverage                63.32%   63.32%   -0.01%
=======================================================
  Files                      297      297
  Lines                    18861    18863       +2
  Branches                  4559     4561       +2
=======================================================
+ Hits                     11944    11945       +1
  Misses                    6303     6303
- Partials                   614      615       +1

Impacted Files
Coverage Δ

...api/src/graphql-transformer/transformer-factory.ts
28.44% <100.00%> (ø)

...fy-graphql-auth-transformer/src/resolvers/query.ts
89.74% <0.00%> (-0.70%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

General comment, and doubly important because this seems to be a change that introduces some structural and pattern changes to our code.

I'd love a more comprehensive description of the change (almost a lightweight version of your design doc explaining what the change is, why it's being made) both  for us, as well as for posterity when we go and look at the change itself.

It's a pretty large PR (in terms of lines changed), but I think I grok why it's this large. What would help my understand a bit more is a description of whether this could be released more incrementally, and the process you took to refactor towards a single factory. This might be addressed by point 1 as well.

Still going through the code, but wanted to drop that feedback earlier.

I have updated the description with more details about why we are making this change.
The change is minimal when compared to the current main branch. The differences shown on this PR are because of the previous split work (got merged to feature branch) done to separate out DynamoDB and RDS transformers into different packages. I reverted the files to how it is in main today and made the changes on top of it.


When I use okhttp, how to determine whether the data is completely downloaded, as well as to determine whether the request is terminated

When I use okhttp, how to determine whether the data is completely downloaded, as well as to determine whether the request is terminated

Duplicate of #1572m


remove redundant animation when swipe back

Right now the _goBack logic is redundant, after swiped back, we need to wait an extra ANIMATION_DURATION time before we can perform other interaction, actually the slide animation is already done in onNavigateBack ( navigation.goBack )

ping @satya164

ping @satya164 @grabbou

CardStackPanResponder is currently not used by CardStack, so this PR is a bit confusing. Could we just delete this file entirely?

@ericvicenti thanks for your feedback, seems CardStackPanResponder is used by Card, and I can confirm this PR solves my problem
https://github.com/react-community/react-navigation/blob/master/src/views/Card.js#L59
https://github.com/react-community/react-navigation/blob/master/src/views/CardStack.js#L571
https://github.com/react-community/react-navigation/blob/master/src/views/CardStackStyleInterpolator.js#L67 here we add extra 30px when interpolate so we don't notice the delay, but you can see that when using it in modal mode, and I'm using StackNavigator with custom transformation, and removed the extra 30px, then it's very easy to see the delay.
With this PR, the following workaround can be removed because the shadow disappears immediately after wipe back with this fix
// Add ~30px to the interpolated width screens width for horizontal movement. This allows
// the screen's shadow to go screen fully offscreen without abruptly dissapearing

If needed, I will send another PR to remove this workaround

@ericvicenti any chance to review this again?

I get it now, I'm working on beta.6 instead of master branch

since the remove has been done in https://github.com/react-community/react-navigation/commit/93976d358e27580e568ef016f820dc0253423aa7, I'll close this PR and create a new one to address the goBack animation stuff


Test the find method

It is just some sort of fuzzy find by endpoint or callback.

Nope. Will make private in #19


Add require entrypoint to follow bundler convention

By default, bundler will try to require the name of the rubygem. For
example, this gem is langchainrb, so it would try to
require "langchainrb".
That file doesn't exist, so when using bundler you'd need to explicitly
set require, ie:
gem "langchainrb", require: "langchain"

This adds lib/langchainrb.rb that only requires "langchain" so that
extra require: "langchain" isn't
necessary.

@technicalpickles Please run standardrb --fix and let's ship it! Thank you!

Fixed!


bulk insert

I would appreciate any hints how to perform a bulk/batch insert.
I ve been looking at the test suit and I could not figure out how.

Do you want to do a parameterized bulk insert?  Eg:
INSERT INTO foo (a,b,c) VALUES (?, ?, ?), (?, ?, ?), ...;

If this is the case, sqlx does not provide any helpers for this, although if you are using a db that uses $1, $2, ... bindvars instead of the ? bindvar, you can build it with ? (which will be easier) and then rebind it.

I'm actually using NamedExec, my insert look like this:
sqlQuery := "INSERT INTO mytable (field1, field2) VALUES (:field1, :field2)"
res, err = tx.NamedExec(sqlQuery, vmap)

Is there a way to exec a Dry run wtih NamedExec, in order to copy the SQL in a buffer and then Exec all the insert in one call?

NamedExec and BindNamed have to take the names and convert them into a []interface{} for execution with Query.  There's no way currently to do this in bulk, you have to call it each time.  This, for instance, is not handled:
type thing struct { f1, f2 string }
var things []thing{...}
Query(`INSERT INTO mytable (field1, field2) VALUES (:f1, :f2), (:f2, :f2)`, things)

Okey that's a pity. I will close the issue, feel free to reopen if needed.

I would love to see this work, especially since it can be done with DB.Exec from the stdlib sql/database package.

This would be a good improvement. I also need something like that.  I would appreciate one day have this feature at hand.

Would also like to see a helper for bulk inserts!

duplicate https://github.com/jmoiron/sqlx/issues/238
already fixed in https://github.com/hmgle/sqlx/commit/018bd2dc4495148c6bc575e693573ea68c9ad506
Could you pull these changes?

There's even an open PR to resolve this. #285.

There is a bug when there is on duplicate key update statement.
INSERT INTO `cloudx_wenjuan_luck`.`luckg_cross_sig`
(
`id`,
`survey_id`,
`bucket_key`,
`doc_count`,
`percent`,
`answer_total`,
`delete_at`)
VALUES (
        ?,
        ?,
        ?,
        ?,
        ?,
        ?,
        ?) ON DUPLICATE KEY
UPDATE
		`survey_id`=VALUES(survey_id),
		`bucket_key`=VALUES(bucket_key),
		`doc_count`=VALUES(doc_count),
		`percent`=VALUES(percent),
		`answer_total`=VALUES(answer_total),
		`delete_at`=VALUES(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at)

There is a bug when insert multiple rows on duplicate key update.
INSERT INTO `cloudx_wenjuan_luck`.`luckg_cross_sig`
(
`id`,
`survey_id`,
`bucket_key`,
`doc_count`,
`percent`,
`answer_total`,
`delete_at`)
VALUES (
        ?,
        ?,
        ?,
        ?,
        ?,
        ?,
        ?) ON DUPLICATE KEY
UPDATE
		`survey_id`=VALUES(survey_id),
		`bucket_key`=VALUES(bucket_key),
		`doc_count`=VALUES(doc_count),
		`percent`=VALUES(percent),
		`answer_total`=VALUES(answer_total),
		`delete_at`=VALUES(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at),(delete_at)

Does anyone know if there is a new ticket to address this bug for bulk upserts?


npm install and npm run dev fail in laravel homestead

Laravel Mix Version: #.#.# (npm list --depth=0)
This fails to run
Node Version (node -v):
v14.15.4
NPM Version (npm -v):
6.14.11
OS:
Ubuntu (laravel 8 homstead)

Description:
I tried updating my tailwindcss base in app.css and theme in tailwind.config.js and tried to run
npm run dev
and failed with
> mix

sh: 1: mix: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @ development: `mix`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the @ development script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the @ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/vagrant/.npm/_logs/2021-07-28T21_44_09_114Z-debug.log

So, I tried running
npm cache clear --force

rm -rf node_modules

npm install

and fails with
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/vagrant/code/project/node_modules/terser-webpack-plugin/node_modules/schema-utils/package.json.3096017829
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/vagrant/code/project/node_modules/terser-webpack-plugin/node_modules/schema-utils/package.json.3096017829'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!   Apparently mix just disapeared since the last time i used it.

I am having the same issue too but I'm using vagrant.
vagrant box: bento/ubuntu-20.10
laravel framework: 8.52
nodejs: 14.17.3
npm: 6.14.13

So, turns out its a windows issue with relative paths. The only thing ive gotten to work is to run all npm commands on the host machine instead of inside the vm.


Putting properties in the spec file is mandatory

Properties that are not in the spec file are not available in the template expansion, right?

@voelzmo @cppforlife
From the thread at https://groups.google.com/a/cloudfoundry.org/forum/#!msg/bosh-users/26pogGElU5s/KDFPkfibdUQJ I experienced that properties not declared in the Spec file were indeed available for template expansion, hence pr https://github.com/cloudfoundry/docs-bosh/pull/40
Has bosh changed this behavior lately, or did I misunderstood something ?

Is that just working because the templates are not using the p('some_property') notation? I noticed that the cf-services-contrib-release seems to be accessing the properties object directly. @cppforlife could you maybe clarify this?


Remove duplicate dependencies

Thank you for your great work!
I tried to use this engine with webpack, and found that there are some dependencies for development in package.json dependencies field, which is used for production environment. The same dependencies are already in devDependencies, so it seems to be safe to remove duplicate dependencies in dependencies field.

Awesome, thanks for this!

Merged this into dev instead of master. Will promote to master along with a few other bug fixes I'll start on today, too.
Thanks!


Add support for CPU AMP autocast

What does this PR do?
Adds PyTorch 1.10 support for CPU autocast. Requires installing 1.10 (and I noticed that for now till the release, we have to include a dev check to the availability for people using nightly or building from source).
Now in 1.10 this works:
Trainer(precision='bf16')

cc @ananthsub @anj-s @min-xu-ai I noticed that torch.cpu.autocast only has bf16 support which means it might not play well with fp16 mode for FSDP when using CPU offloading. Would be nice to have support for this out the box!
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

@SeanNaren I think this PR caused the following 5 tests to fail in our CI job (conda 3.7, 1.10)
FAILED tests/models/test_amp.py::test_amp_cpus[1-bf16-None]
FAILED tests/models/test_amp.py::test_amp_cpus[1-bf16-ddp_spawn]
FAILED tests/models/test_amp.py::test_amp_cpus[2-bf16-None]
FAILED tests/models/test_amp.py::test_amp_cpus[2-bf16-ddp_spawn]
FAILED tests/models/test_amp.py::test_cpu_model_with_amp

The issue tracking this is #9280
Stack traces for the failing tests can be found in this gist: https://gist.github.com/daniellepintz/3d5a13b6264a832fc745f73460d2fa23 (from https://github.com/PyTorchLightning/pytorch-lightning/runs/3483032531)
Do you know what might be causing these failures?


OLM doesn't revert modified deployment of operator

Bug Report
What did you do?

Subscribe an operator on operatorhub console

Scale down operator deployment

What did you expect to see?
Deployment be scaled up or rolled back soon.
What did you see instead? Under which circumstances?
The replicas of deployment keep 0 and CSV phase remains succeed
Environment

operator-lifecycle-manager version:
0e65642458a1e44e77bd5509dceee3a41da35b76

Kubernetes version information:
v1.19.1

Kubernetes cluster kind:
Kubernetes created with kind

Possible Solution
Additional context
Remove the deployment and it will be rebuild soon.

/kind bug

I found that OLM compares the hash set in label of existing deployment with calculated from CSV.spec.install.spec.deployments, but both of these hash values won't be updated when deployment is modified directly, which made them equled always.
https://github.com/operator-framework/operator-lifecycle-manager/blob/0e65642458a1e44e77bd5509dceee3a41da35b76/pkg/controller/install/deployment.go#L281
I'd like to solve this bug if my analysis is right 😃

Thank you for submitting this bug @zkyle95 - after reading your most recent comment, I believe that OLM is working as intended.
OLM uses the deploymentHash to ensure that the resources created by OLM match those defined in the CSV. This approach allows a user to edit the resources once they are installed and prevents OLM from entering an endless loop when a webhook is changing the resource before it is saved to the object store.
I am planning to close this issue as things are working as intended.


using datastore (+pubsub?) emulator requires credentials

There may be a way to do this that I'm not aware of, but from hunting around for documentation, consulting slack, and stepping through the code, it appears that this library requires live gcp credentials to use the emulator. This wouldn't be a problem, except that I can't think of a reason it would require the credentials, and if there's a problem using the emulator no notice is given, it simply falls back to using the live account.
I would like to configure my dev/test environments to not have access to a live account at all, and ideally I would like to be able to toggle 'force emulator use' on my dev machine just in case. Is this possible?

OS type and version
Win10/macOS Sierra
Python version and virtual environment information python --version
python 3.5.2
google-cloud-python version pip show google-cloud, pip show google-<service> or pip freeze
0.20.0

Thanks for filing. The connection can tell if it is in an emulator, but just uses the default credential checking behavior. In our system test, we manually pass in some do-nothing credentials.
Have you seen the tox -e pubsub-emulator environment or run_emulator.py?

Please any updates on this ? passing empty credentials didn't fix the problem ? please advice !

@nabilm can you give a code example of how you passed in the credentials?

@dhermes we used the same approach as you suggested to avoid that default credentials have to be set in emulator mode:

In our system test, we manually pass in some do-nothing credentials.

However, we recently updated to the version that contains this code which checks that the credentials are either None or an instance of google.auth.credentials.Credentials. Just passing in credentials=None (and also adding projects=<PROJECT_NAME> to avoid that it tries to derive the project name from the non-existing default credentials) seems to work.
I was wondering if there is a better approach? Also, is it possible that the test is not up to date anymore?

I also found it very inconvenient to pass in real credentials just to run unit tests on an emulator in my CI environment. That requires encrypting the credentials, managing secrets, etc. I tried editing the credential files to not include real keys, but it appears the creds need to actually load correctly to connect to the emulator.
In the end, this worked well. I subclassed Credentials and passed those in:
class DoNothingCreds(credentials.Credentials):
    def refresh(self, request):
        pass

client = google_datastore.Client('gitlawca', credentials=DoNothingCreds())

Hello! :-)
First, a mea culpa; I have not done as good of a job at keeping up with issues as I should have. If you are getting this (I admit it) cut and paste, it is likely because your issue sat for too long.
In this case, I have been in the process of making a radical update to the PubSub library (#3637) to add significant performance improvements and a new surface, which we hope to launch soon. As such, I am clearing out issues on the old library. It is my sincere goal to do a better job of being on top of issues in the future.
As the preceding paragraph implies, I am closing this issue. If the revamped library does not solve your issue, however, please feel free to reopen.
Thanks!


Add metadata to mediaconvert job for filtering, based on queue name

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

[x] Settings

[x] New settings are documented and present in app.json
[x] New settings have reasonable development defaults, if applicable
[x] Opened issue for DevOps regarding necessary configuration changes to deployed environments

What are the relevant tickets?
Part of #995
What's this PR do?
Adds a new setting VIDEO_TRANSCODE_QUEUE, to match the queues specified in ol-infrastructure, and updates the MediaConvert job definition to include it.

Related: https://github.com/mitodl/salt-ops/pull/1501

Adds a UserMetadata.filter key to the MediaConvert job definition, which will be used for SNS event rule filtering on AWS (this will require a change to the ol-infrastructure code).
How should this be manually tested?

Copy RC AWS_* settings to your .env file, and set VIDEO_TRANSCODE_QUEUE=ocw-studio-mediaconvert-queue-qa
Create a Video object in a shell and then start a mediaconvert job for it.  There should be no errors.from videos.api import *
video = Video.objects.create(website=<your_website>, source_key="gdrive_uploads/11-382-water-diplomacy-spring-2021/1RxRDvHiKFR-QZ99GgZam2PiXRFCLJTLM/jellie3local1.mp4")
create_media_convert_job(video)

If you change VIDEO_TRANSCODE_QUEUE=fake_queue, restart the shell, and run create_media_convert_job(video) again, you should get an error about an invalid queue.

Codecov Report

Merging #1018 (b249fa2) into master (a5a926f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1018   +/-   ##
=======================================
  Coverage   91.02%   91.03%
=======================================
  Files         194      194
  Lines        7413     7415    +2
  Branches     1297     1297
=======================================
+ Hits         6748     6750    +2
  Misses        583      583
  Partials       82       82

Impacted Files
Coverage Δ

main/settings.py
94.25% <100.00%> (+0.02%)
:arrow_up:

videos/api.py
95.65% <100.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Limit optimization leads to problematic join condition for composite PKs

The fix for https://github.com/Blazebit/blaze-persistence/issues/1810 causes some issues when trying to limit something that has a composite primary key, because the generated query looks like join CompositePkEntity e on e = (limit((select e2.pk1, e2.pk2 from CompositePkEntity e2 ...),1)) which Hibernate complains about.

Hello @beikov,
Is there any progress going on on this bug ?

Hi @haraleib, no, I'm not currently working on this. Is it critical for you? If so, what version of Hibernate ORM are you using?

As we want to move to an official BlazePersistenc Version, this bug is the last regression we have so far to do so.

Ok, but what version of Hibernate ORM are you using?


copy-paste bug: crypto\asn1\asn1_gen.c - (!strncmp(vstart, "BITLIST", 3))

V666 Consider inspecting third argument of the function 'strncmp'. It is possible that the value does not correspond with the length of a string which was passed with the second argument. asn1_gen.c 371
	case ASN1_GEN_FLAG_FORMAT:
	if (!strncmp(vstart, "ASCII", 5))
		arg->format = ASN1_GEN_FORMAT_ASCII;
	else if (!strncmp(vstart, "UTF8", 4))
		arg->format = ASN1_GEN_FORMAT_UTF8;
	else if (!strncmp(vstart, "HEX", 3))
		arg->format = ASN1_GEN_FORMAT_HEX;
	else if (!strncmp(vstart, "BITLIST", 3))
		arg->format = ASN1_GEN_FORMAT_BITLIST;

fix:
if (!strncmp(vstart, "BITLIST", 3)) -> if (!strncmp(vstart, "BITLIST", 7))

This was fixed in 0b142f022e2c5072295e00ebc11c5b707a726d74, so it can be closed.


Transforms

Copied transforms over to 'dev' and made the following changes there:

issue with “Aggregations” title appearing everywhere
name all transforms with unique name - transform: by
filter out transform[]… by regex at map function
added a few fields to 'filter'

:dancer: once that labelling comment is addressed

great 💃


Async Tool Support

It appears as though only synchronous functions for tools are supported. Is that correct?
In executor.py:
# We then call the tool on the tool input to get an observation
observation = tool.run(

However, I have several tools which have coroutines rather than func. For instance something like this:
async def _load_stuff():
    return await do_things()

 def _get_my_tool() -> Tool:
    return Tool(
        name="my tool name"
        func=lambda *args, **kwargs: print("***** NOT IMPLEMENTED*****"),
        coroutine=_load_stuff,
        description="a good description"
    )

I don't think this is supported though based on my reading of executor. Would it be possible to check if a coroutine is defined and if so then use arun instead?

+1
Similarly add support like
from crewai_tools import tool
@tool("Name of my tool")
async def my_tool(question: str) -> str:
    """Clear description for what this tool is useful for, you agent will need this information to use it."""
    # Function logic here
    return await do_things()

You can try something like this:
from gpt_researcher import GPTResearcher
from langchain.tools import tool

import asyncio

class ResearchTool():
    @tool("Perform research for crew members on the topic at hand when needed.")
    def perform_research(query):
        """Useful for conducting research on a given topic and return a report"""
        report_type = "research_report"

        print("Performing research on the topic at hand...")

        async def _async_research():
            researcher = GPTResearcher(query, report_type)
            await researcher.conduct_research()
            report = await researcher.write_report()
            return report

        # Create a new event loop
        loop = asyncio.new_event_loop()
        asyncio.set_event_loop(loop)

        # Run the coroutine using the event loop
        return loop.run_until_complete(_async_research())

Creating an event loop and calling your async function within the new event loop you've created is a workaround, but it would be nice to be able to define an async function for a tool.

This is still an issue, can confirm today in v0.51.1

You can try something like this:
from gpt_researcher import GPTResearcher
from langchain.tools import tool

import asyncio

class ResearchTool():
    @tool("Perform research for crew members on the topic at hand when needed.")
    def perform_research(query):
        """Useful for conducting research on a given topic and return a report"""
        report_type = "research_report"

        print("Performing research on the topic at hand...")

        async def _async_research():
            researcher = GPTResearcher(query, report_type)
            await researcher.conduct_research()
            report = await researcher.write_report()
            return report

        # Create a new event loop
        loop = asyncio.new_event_loop()
        asyncio.set_event_loop(loop)

        # Run the coroutine using the event loop
        return loop.run_until_complete(_async_research())

Creating an event loop and calling your async function within the new event loop you've created is a workaround, but it would be nice to be able to define an async function for a tool.

This solution unfortunately won't work in a Jupyter notebook.

Please reopen

need more information from crewai team


Feature report event

Codecov Report

Merging #4 (8554e95) into master (202b549) will increase coverage by 0.58%.
The diff coverage is 96.42%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
+ Coverage   95.16%   95.74%   +0.58%
==========================================
  Files           4        4
  Lines         124      141      +17
==========================================
+ Hits          118      135      +17
  Misses          6        6

Impacted Files
Coverage Δ

bk_monitor_report/reporter.py
90.00% <93.33%> (+0.71%)
:arrow_up:

tests/test_reporter.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Shooter Game

Fixes #421

@TusharAMD this PR was made before the announcement so please merge this one, also u have merged 7 after the announcement so please at least merge the ones yesterday

https://gist.github.com/awatekiran/5885598


Suggestion to Make Website Fully Responsive

The website's grid card layout is not fully responsive across different screen sizes and devices. This issue impacts the user experience as the cards may not display correctly on smaller screens or in other orientations.
Suggestion:

Improve the responsiveness of the grid card layout to ensure it adapts well to various screen sizes and orientations.
Assign this task to me, and I will work on implementing the necessary changes to make the website fully responsive.

Hi @sahilatahar, I am currently looking into migrating into a design framework to keep everything consistent. This will help in making it more responsive.


Conflict with another package

There is a conflict with package latex-completions (it works only when atom-ide-purescript is disabled). Since purescript now supports unicode, it would be nice to have some kind of autocompletion for it. Ideally as a part of atom-ide-purescript.

A question of priority & exclusion of completion provider. This should be fixed as part of the linked PR - whenever that package is next released.


'jsdom' breaks on npm install on 3.5.x version

I cloned the master repo which seems to be on '3.5.6' version, when I tried installing node dependencies using npm install it is failing throwing this error: npm install console log.
But if I install jsdom manually using npm install jsdom@latest it's getting installed properly. So if there are no restriction of using the specific jsdom can we upgrade to jsdom's latest version or as you mentioned on other issues can remove jsdom dependency completely but for time being if upgrading to latest version is possible can we just update package.json file accordingly?

It looks like you’re trying to install an older version of D3, specifically, 3.4.1.
In the latest version, JSDOM has been demoted to a devDependency rather than a dependency, which typically means you don’t have to install JSDOM and all its dependencies (the most error-prone of which is Contextify, since it requires compiling native code) if you only depend on D3.
The install should look like this:
$ npm install d3
<EMAIL_ADDRESS>node_modules/d3
$

The JSDOM dependency is declared as "3", which means we depend on the latest version of JSDOM that has the major version 3. Incrementing the major version is not backwards-compatible, so that’s the most aggressive we should be about using the latest version of JSDOM.
We could upgrade to a more recent version of JSDOM, but that would require everyone to use a newer version of Node (4+). I’m not sure that’s a good idea.
But at any rate, the issue here appears to be you are installing an old version of D3, and assuming you switch to a more recent version, you shouldn’t need to install any version of JSDOM.

@mbostock As I mentioned in my last comment I'm not installing D3 using any package manager either npm or bower, all I did was cloned master branch of D3 repo, which seems to be on 3.5.6 version precisely according to package.json file, and as you said yes the JSDOM is under the devDependency in package.json file, but when I do npm install it throws the error provided in my last comment.
PS: I'm using Node's latest version viz v4.1.2 on my Mac which is running OS X El Capitan (10.11)

Okay, sure, if you’re cloning the repo and running npm install then yes you still need JSDOM because it’s a development dependency.

So is there anything we can do? or is this all depends on JSDOM module to fix the Contextify issue?


Bump Alpine

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/hold


Auth token step

The token I get from running the step to get the auth token produces a token with claim https://management.core.windows.net/.
Then when running commands on databricks cli I get the error:
% databricks workspace ls

Error: b'\n\n<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>\n<title>Error 400 io.jsonwebtoken.IncorrectClaimException: Expected aud claim to be: 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d, but was: https://management.core.windows.net/.</title>\n\n
HTTP ERROR 400
\n
Problem accessing /api/2.0/workspace/list. Reason:\n
    io.jsonwebtoken.IncorrectClaimException: Expected aud claim to be: 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d, but was: https://management.core.windows.net/.

\n\n\n'

If I specify the resource id then works ok:
export DATABRICKS_AAD_TOKEN=$(az account get-access-token --resource 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d| jq .accessToken --raw-output)

wsUrl=$(az databricks workspace list -g $rg --query "[0].workspaceUrl" -o tsv)
databricks configure --aad-token --host https://$wsUrl

% databricks workspace ls
Users
Shared
Repos

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

ID: 47bb00ae-8ec1-0000-4972-5dfd22983982
Version Independent ID: 8a8a2723-9a42-1f24-80c4-9c44b59372e2
Content: Databricks CLI - Azure Databricks
Content Source: databricks/dev-tools/cli/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@andrew-twigg  Since this issue is not related directly to the doc, I would recommend you to create a thread on the forums - Microsoft Q&A or Stack Overflow
Once you post your issue on forums, it will have visibility across the community which is a better suited audience for such types of issues.

@andrew-twigg Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

I am facing the same issue and do not think it is a documentation issue. When I tried to generate token with requested audience from the exception some features work, but some still fail. In my case I was trying to create Key Vault backed secret scope.
Seems like token for 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d is required to access Databricks API, but to perform actions like creating secret scope management token is required.

To my understanding this is indeed a bug in documentation. The example on https://docs.microsoft.com/en-us/azure/databricks/dev-tools/cli/ just does not work.
One has to add an  --resource 2ff814a6-3304-4ab8-85cb-cd0e6f879c1d to it and then everything is fine.

Hi Everyone, does anyone know what is this resource "2ff814a6-3304-4ab8-85cb-cd0e6f879c1d" "

Can confirm, docs are wrong.  Frustrating and time wasting.  Hope its corrected soon.  @fmms thanks for providing the solution.

How can I make this work using the python msal library? The docs are still wrong and it is really frustrating trying to work this out on my own.

Still not possible to do this with python msal lib ?

Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue and apologize for the delayed response. The requested updates have not yet been made. The timeline for resolution varies based on resourcing. We've created an internal work item (DOC-7024) to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close

#please-close


code --install-extension Prisma.prisma-insider@[version] returns Server returned 503

We are seeing many Server returned 503 errors from this command in our CI (GitHub Actions):
/workspaces/language-tools/.vscode-test/vscode-linux-x64-1.66.2/VSCode-linux-x64/bin/code --install-extension<EMAIL_ADDRESS>
This command is called for each new version (with the corresponding version)
The full source code is located at https://github.com/prisma/language-tools/blob/main/scripts/e2eTestsOnVsix/install_extension.js
The GitHub Action workflow runs:
https://github.com/prisma/language-tools/actions/workflows/e2e_published_vsix.yml
Error log example: https://github.com/prisma/language-tools/runs/6075977680?check_suite_focus=true#step:5:31
{
  status: 1,
  signal: null,
  output: [ null, 'Installing extensions...\n', 'Server returned 503\n' ],
  pid: 1875,
  stdout: 'Installing extensions...\n',
  stderr: 'Server returned 503\n'
}

Do you have an idea about what this error is and how to avoid it?

I could not reproduce locally, and the CI indicates that this might be flaky, though it happened a lot in the last few hours (see screenshot)

Marketplace service is facing service issues the last couple of days. We are aware of this and we are looking into it.
Soon there should be an issue with more details in the https://github.com/microsoft/vsmarketplace repository
Thank you for your understanding

@isidorn @connor4312 Ok makes sense now.
Could the error message be improved, maybe?
Because it's not saying much about what it is (just a "Server" and a "503" but nothing else that could help, like the URL of the server that triggered that error.)

After a random Google search, I found the status page at https://vsstatus.visualstudio.com/ and everything is green there 🤔

https://status.dev.azure.com/_event/302592133
This should have more details. I do not know why those two status pages are not in sync though - sorry!


quick fix: ensure drop loading state can be cleared

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Needs QA check

@kodadot/qa-guild please review

The reason for the issue is: In the sketch code of old drop, kodahash/render/completed event might not exist.
Context

[x] Closes #9585
[ ] Requires deployment <snek/rubick/worker>

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Screenshot 📸

[ ] My fix has changed UI

@prury good to go?

yup

Thanks!
pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 8.46 USD/DOT ~ 3.546 $DOT
🧗 1CAv6Zq3yVxL3eKhC94GWTWVwp1w4jZbqeZ6wXx1rPAhrce
🔗 0xb8cc711595b89dcf88918c70800f4f6db73b11e018002005cfa1c00576b61538
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Lighter text color for 'Forwarded' title

When forwarding messages, the little italic text up on the message box 'Forwarded' doesn't have a good contrast. Just adding this:
._15aTv{     color: var(--lighter); }
will solve it.

Sorry for a bit late reply, life kinda got in the way. I've added it in the newest update, thanks! :smiley:


BiomartGeneRegionTrack and depreciated dplyr functions

Hello,
I am having a problem when I run BiomartGeneRegionTrack(). When I try to run the command, I have an error that reads,

select_() was deprecated in dplyr 0.7.0.
Please use select() instead.filter_() was deprecated in dplyr 0.7.0.
Please use filter() instead.
See vignette('programming') for more helpError in UseMethod("filter_") :
no applicable method for 'filter_' applied to an object of class "c('tbl_SQLiteConnection', 'tbl_dbi', 'tbl_sql', 'tbl_lazy', 'tbl')"

Is there any way to fix this problem?
Thank you so much!

Hi @14stutzmanav,
There is not a lot information in your post (missing sessionInfo()and reproducible piece of code leading to the error).
However I would expect that there is a conflict between tidyverse and Bioc worlds.
I would recommend you, that you load first dplyr (or tidyverse) and only afterwards load Bioc libraries (like Gviz).
Hope that helps, best, Robert

Hi,
I can confirm this problem. select_ and filter_ are deprecated and are going to show warnings/errors with "older" versions.
However loading FIRST dplyr/tidyverse and later on Gviz is going to work.
I had the chance to test it on  a fresh installed R + packages. Warning/Error is not showing any more.
session.txt
best


Example code in README.md might benefit from clarification that GmfFloat/GmfDouble is returned from GmfOpenMesh

The example code in the README.md runs successfully only if Coords is an array of doubles, not floats (and there are some small typos).
EDIT: ok, just saw that GmfOpenMesh returns GmfFloat or GmfDouble in its third argument .... maybe that should be clear from the example, it's easy to assume that it will always paste sizeof(float) into the arguments of GmfSetLin.

The example code in the README.md runs successfully only if Coords is an array of doubles, not floats (and there are some small typos).

Hi Mathias,
thanks for pointing that out.
I corrected the typos to make the code compiling.
I specified that the "triangles.mesb" file should be written with single precision numbers.
Regards,
Loïc


"Disable WDAC Policies": Cleanup formatting

This PR performs a few list/callout-related changes to the article "Disable Windows Defender Application Control Policies":

Move list of WDAC policy locations into "Note" callout referencing them
Replace boldface "Note"  with DFM [!NOTE] tags

@JohanFreelancer9, is there any specific requirement in the style guide that lists must be enclosed in quote-blocks like that? The only reason I did that for the list around L45 is because the previous statement contextualizing/referring to said list was already in a [!NOTE] quote-block:

Good question. I was wondering the same, because I have not seen this formatting style yet, unless it is to include it as a part of a [!NOTE] blob.

@sewillia-msft, you are absolutely correct. Sorry about that, it is totally my mistake, and thank you for pointing it out. There certainly is no such requirement and I have deleted my suggested changes. Thanks again.


Build fixes for WinRT

C++ Native mode support coming back and C++/CX support fixed in core and made more flexible in videoio.  Next tasks to fully support Windows 10 Universal Apps and Visual Studio 2015 and resurrect some native C++ code that ended up deprecated due to conflicts.

:+1:


add NaN js question

Checklist:

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Changes added, it's my first contribution thank you very much!


Use my RPC node

I still need to test this end to end, but it looks possible to your my private RPC instead of the public one.

LGTM.


Link failure with GraalVM 21.1.0 for Java 16

I tested building my application with the client-maven-plugin on a Mac with the new GraalVM 21.1.0 for Java 16. It failed at the end with a link error.
[Do. Apr. 22 16:46:11 MESZ 2021][INFO] [SUB] ld: library not found for -lsunec

The exact same setup worked without problem with the same GraalVM version for Java 11. I used client-maven-plugin version 0.1.39, JavaFX 17-ea+7. The configuration was all created by running the agent.

Same here.

I am build on Windows with same GraalVM and Java version, and have same error:
 [週一 7月 12 17:34:29 TST 2021][INFO] [SUB] LINK : fatal error LNK1181: 無法開啟輸入檔 'sunec.lib'
This solve my problem:
1.Copy link command on error log
2.Remove 'sunec.lib' in command
3.Run new command again

I experienced the same issue today on MacOS 10.15.7 graalvm-ce-java16-21.2.0 using both gluonfx-maven-plugin 1.0.4 and 1.0.5-SNAPSHOT built from 9ff71e7

I resolve it on Ubuntu. It's not a Mac, but it might help you

first : find already existed libsunec.a

locate libsunec | grep libsunec.a
# /home/tcsnzh/桌面/packages/graalvm-ce-java11-linux-amd64-21.2.0/graalvm-ce-java11-21.2.0/lib/static/linux-amd64/glibc/libsunec.a
# /home/tcsnzh/桌面/packages/graalvm-ce-java11-linux-amd64-21.2.0/graalvm-ce-java11-21.2.0/lib/static/linux-amd64/musl/libsunec.a
# /home/tcsnzh/桌面/packages/graalvm-ce-java8-linux-amd64-21.2.0/graalvm-ce-java8-21.2.0/jre/lib/libsunec.a

than , link it to system static lib path.

sudo ln -s /home/tcsnzh/桌面/packages/graalvm-ce-java11-linux-amd64-21.2.0/graalvm-ce-java11-21.2.0/lib/static/linux-amd64/musl/libsunec.a /usr/lib/libsunec.a

sunec library has been removed from JDK 16+. The plugin (1.0.10) already checks if you are running on JDK 11 (keeps the library) or greater (removes the library).

@jperedadnr thank you for the update, I can confirm that it works with 1.0.10 – at least on macOS and Windows. On Linux, I still get [INFO] [SUB] /usr/bin/ld: cannot find -l:libsunec.a. But this could also be an issue with my workflow, will dig a little deeper.
Side note: 1.0.1 is still the latest release on GitHub, which might be confusing to some users.

There was a small issue with sunec on Linux, it has been fixed with 1.0.11-SNAPSHOT
(Include this repo:)
<pluginRepositories>
        <pluginRepository>
            <id>Snapshots</id>
            <url>http://oss.sonatype.org/content/repositories/snapshots/</url>
        </pluginRepository>
    </pluginRepositories>

Yes, releases are done via Github actions, and they don't show as releases, but Maven badge shows 1.0.10

There was a small issue with sunec on Linux, it has been fixed with 1.0.11-SNAPSHOT (Include this repo:)
<pluginRepositories>
        <pluginRepository>
            <id>Snapshots</id>
            <url>http://oss.sonatype.org/content/repositories/snapshots/</url>
        </pluginRepository>
    </pluginRepositories>

Yes, releases are done via Github actions, and they don't show as releases, but Maven badge shows 1.0.10

It require https default . so :
<pluginRepositories>
        <pluginRepository>
        <id>Snapshots</id>
        <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>


I think we should merge this after the v0.83.0 release cycle is completed. cc @djaglowski for that as release manager


[FLINK-36210] Optimize the logic for fetching topic metadata in the TopicPatternSubscriber mode

What is the purpose of the change
In TopicPatternSubscriber mode, our current logic for fetch topic metadata for all topics and then filtering it. We can optimize this by first filtering the topic names and then fetch metadata only for the filtered topics.
Brief change log
Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? no)
If yes, how is the feature documented? (not applicable)

Friendly ping, do you have time to take a look @AHeise 🙏 ?

Don't forget to run spotless.

LGTM. I'll approve and merge once CI passes.
Have you seen any performance improvements with this change? Could you add that to the description? I'm assuming you are submitting the change because the old code took too long to recover.

Thank you for your careful review.

Don't forget to run spotless.

Thanks for the reminder! I'll make sure to run spotless before finalizing the changes.

Don't forget to run spotless.

Thanks for the reminder!

run spotless

done.

Merged, thank you for your contribution :)


Automated System Certificate Rotation

Problem
Rotating the NATS and blobstore CAs through all of the director and deployed VMs takes an immense amount of time, due to the need for deployed VMs to be recreated to update the certificates.
The certificates have essentially no meaning to operators, as they're created during create-env and distributed as VMs are deployed.
The only way to transfer new NATS/Blobstore CAs/certs to VMs is via a recreate of the entire VM.
This is an optimization that can be performed when needing to rotate the CAs. The three-legged deploy should still be performed if operators are concerned about leaked certificates.
Proposal
Given a healthy director, an operator can execute some CLI command that executes a task that will update director and deployed VM NATS/blobstore certificates without the operator recreating all deployed VM or the director VM.
Director
Given a director, execute a bosh cli command that:

Starts a task that can be tracked
Shows each instance being updated during task execution
Handles failing VMs gracefully, allowing idempotent retries
Distributes the new CA and leaves to deployed VMs
Accepts the --vars-store option in order to update the creds.yml file after completion
Director reloads gnatsd when appropriate

Agents
A deployed VM, with an agent that has successfully checked in recently will:

Receive a message over NATS to begin the process
Accept a new NATS CA and leaf certificate via message from director
Install the new CA, concatenated with the old CA
Respond to ping over NATS using the new leaf certificate
Clean up unused artifacts from the process

Problems

Security of transferring new credentials over a potentially compromised channel
A VM may fail to respond to a ping with the new leaf certificate, for reasons other than TLS
The task could be cancelled by operator(s)
There could be other tasks going on at once that use NATS (everything)
Locking the entire director and deployed VMs may be unreasonable

Potential Solutions to above

An agent could generate a keypair, and send the public key to the director to encrypt the new CA and generated leaf. If an attacker can respond as the director with a compromised CA, then using the public key could send a replacement certificate to an agent. Operators should default to the recreation-based approach in the event of a compromised NATS CA.
Process should be idempotent, and write enough state so the process can be resumed at any time. Old and new CAs are concatenated as the certificate authority. Retry a couple times quickly.
If the task is cancelled, then if the process is idempotent in all steps, then the task could be resumed. VMs should still be able to health check.
Deployment locks, work on one deployment at a time.
Director may need to have a manual 'start' and 'finish' command in order for operators to update deployments at their leisure. Expecting all deployments to be rotated at once is unreasonable.

Security/Risks

What if the NATS CA is compromised? The DH key exchange would help here, but if the attacker has access to the director VM, they could also generate the keypair.
At the moment, the recreate is helpful as the channel for credentials is the cloud provider's metadata service. This isn't necessarily secure at all, but at least doesn't use the same channel for its own credential update. Operators concerned about the proposed optimization can still perform the three-step approach.
Health monitor and updating the VMs may cause some chaos, if the check intervals and updates are timed in a certain way.
The time it takes for gnatsd on the director to reload, and the reload/re-establish connection to NATS server from a VM could result in timeouts and necessitate more retries.

Performance
Clearly there will be a gain in performance as operators are not required to recreate VMs, and not reinstall/start jobs back up again. Any downtime should also be eradicated. The key exchange shouldn't be that intensive. Concurrency rules like max_in_flight can still be honoured. Waiting for gnatsd on the director to reload and agent reconnects could take some time, but much less than a whole recreate would.
Accompanying Picture

An old slack discussion around this topic, which could be helpful: https://cloudfoundry.slack.com/archives/C02HPPYQ2/p1553631617308300

+1000 this would be tremendously helpful to have.
Thanks for the work that went into this, @h4xnoodle!

Forgive this useless comment, I can delete it, but as someone whose currently rotating natsCA for all our environments prior to expiration, boy howdy having this as a more "intentional" and specific workflow that could be more easily reasoned about (which VMs have the new concatenated CA? which still need to be re-deploy/created? etc.) and performed more regularly would be nice. Thanks for all you all do 👍


Get GPU metrics into wandb

Maybe wandb will take care of this for us? I opened a ticket with them.

Marking the items prior to Feb 29th as "closed".


For sys_template the columns sys_created_by, sys_created_on, sys_updated_by and sys_updated_on are not created

These columns are not included when the table is created. However, if they are added manually (via alter table) then they will be populated.

This issue has been traced to a defect in the method TableSchema.determineParentname(). If the table name begins with "sys_", then columns from the parent table are not included in the schema. This will be fixed in the next release.

Fixed in 3.1.2


Actions and action creators

As defined here, we are going to define the actions/actions-creators.

Tied to ##11


fix tape: test emitter in async function

Would be amazing if Promise not marked end of the test because it breaks such codeб calling end twice:
const {EventEmitter} = require('events');
const test = require('../../');

test('async6: double end', async function myTest(t) {
    const events = new EventEmitter();

    events.once('change', () => {
        t.pass('good');
        t.end();
    });

    setTimeout(() => {
        events.emit('change');
    });
});

Using subscription to events is a very common situation for end to end tests :).
Anyways I want to thank you for a v5.0.0 and for a fix of rejected promises, I used try-to-tape to fix this behavior :).

Auto calling "end" is a nice feature but breaks tests mixing promises and callbacks.
Honestly, mixing promises and callbacks is bad.
You should try writing tests like
test('async6: double end', async function myTest(t) {
    const events = new EventEmitter();

    setTimeout(() => {
        events.emit('change');
    });

   await new Promise((resolve) => {
       events.once('change', () => {
            t.pass('good');
            resolve();
        });
    })
});

Auto calling "end" is a nice feature but breaks tests mixing promises and callbacks.

Actually, if I want this feature I would take any other test runner 😄 :

zora
jest
ava
mocha

All of them gives ability of auto calling "end".
One of the things I like in tape is ability to explicitly set ending of a test.

Honestly, mixing promises and callbacks is bad.

Could you please describe in more details why it's bad? My code is shorter, and I test this way a lot modules, and everything works good: working well tested simple to support code.
Also that was illustrative example of course I would rather choose such way of code:
import EventEmitter, {once} from 'events';
import holdUp from '@iocmd/hold-up';
import test from 'tape';

test('async6: double end', async (t) => {
     const emitter = new EventEmitter();
     const emitChange = emitter.emit.bind(emitter, 'change');

     await Promise.all([
         once(emitter, 'change'),
         holdUp(emitChange),
     ]);

     t.pass('good');
     t.end();
});

Using once and hold-up, but I can't change all my codebase in a moment :), but I would like to use latest version of tape with rejects fixed, for example :)
And also this is details of realization tape, it's leaking abstraction, and all this just to have ability not write end :)?

This was discussed in the PR that added async function support ( https://github.com/substack/tape/pull/472#issuecomment-505484503 ).
Specifically https://github.com/substack/tape/pull/472#issuecomment-506275358
As a work around you can add
test('foo', async function t(assert) => {

  await new Promise((resolve) => {
    assert.once('end', resolve)
  })
})

Basically for any test where you do not want auto end behavior add an await on the end event at the bottom of the test.

OK, I understood that it is a well designed feature to use one promise for a full test lifecycle. Anyways it makes test harder to write and maintain, and breaks existing well-working tests. As a workaround supertape can be used, it is already extends tapes features list.

If you want to make tests easier to write and maintain then dont use async/await in a callback driven test.
Aka
const {EventEmitter} = require('events');
const test = require('../../');

// Use vanilla function without async / await for testing callbacks.
test('async6: double end', function myTest(t) {
    const events = new EventEmitter();

    events.once('change', () => {
        t.pass('good');
        t.end();
    });

    setTimeout(() => {
        events.emit('change');
    });
});

Indeed; these were all explicit decisions made.
If your test is an async function, the nature of async function is that it returns a promise, and so your entire test ends when that promise fulfills - which is how all other popular test runners work when receiving a promise.
I'm going to close this, since all the removed tests were added for a reason :-)

This is a good example of breaking people's existing tests on tape @ 4 in the wild.
Adding a section to the README about migrating to v5 and end() already called might be useful.

@ljharb that's an interesting api change and it has sense. Would be great if you write about such changes in release notes, so consumers can read about what changes is waiting for them, and why :). Also message end is already called is not not intuitive :), message describing promise behavior with a link to issue would be much better (and deprecation notice in v4, so people can upgrade more smoothly).

@coderaiser https://github.com/substack/tape/releases/tag/v5.0.0 is the release notes; the amount of prose that would be necessary to avoid all misunderstandings in any project is potentially very massive, and it's not imo reasonable to expect that :-)
Separately, v4 is NOT deprecated - deprecation messages are not simply to encourage updates. v4 will work fine likely forever, and there's no reason anybody needs to upgrade.

Separately, v4 is NOT deprecated - deprecation messages are not simply to encourage updates. v4 will work fine likely forever, and there's no reason anybody needs to upgrade.

@ljharb I didn't say that v4 is deprecated, I say that ability to work with async code, the old behavior is deprecated :).

the amount of prose that would be necessary to avoid all misunderstandings in any project is potentially very massive, and it's not imo reasonable to expect that :-)

Here is an example of release notes with well defined breaking changes :), I also have a lot packages, but that doesn't mean that breaking change I make should be invisible, if you have new vision on the way how library should be used, it's a good practice to describe this vision in some convenient way (I admit that our dialog can be this way, I'm OK with it, but that's no scaled).
Anyways I appreciate new knowledge I received today, and now my tests looks this way :).

The ability to mix a Promise-returning test callback, with non-Promise code, has always been deprecated from a community best practices sense ¯\_(ツ)_/¯

Just created codemod to simplify transition to tape v5.0.0: convert-emitter-to-promise. It can help to refactor mixed callbacks with promises :).


add update user password to api

Coverage increased (+1.1%) to 70.143% when pulling 90547ec7b6f6a9109ff5b2564f11a0c1ca15ca33 on update_user into 3a57e3cd17f7b22a6700f79463c95118165a3721 on master.

Coverage increased (+1.2%) to 70.226% when pulling ae39ac1a3743d80b7ee0282b5cb3d0100848c475 on update_user into 3a57e3cd17f7b22a6700f79463c95118165a3721 on master.

Coverage increased (+1.2%) to 70.226% when pulling ae39ac1a3743d80b7ee0282b5cb3d0100848c475 on update_user into 3a57e3cd17f7b22a6700f79463c95118165a3721 on master.

Coverage increased (+2.03%) to 71.042% when pulling 5ae919fbb5751152b210d81136779a4d84987e1d on update_user into 3a57e3cd17f7b22a6700f79463c95118165a3721 on master.

Coverage increased (+2.03%) to 71.042% when pulling 5ae919fbb5751152b210d81136779a4d84987e1d on update_user into 3a57e3cd17f7b22a6700f79463c95118165a3721 on master.


Installing onto OpenShift leads to not working Pod

Expected Behavior
Should work after installing.
Actual Behavior
Seems to create all objects. But tekton-pipelines-webhook creates Pods, that don't work.
Steps to Reproduce the Problem

kubectl apply --filename https://storage.googleapis.com/knative-releases/build-pipeline/latest/release.yaml

Additional Info
Pod log is e.g.:
{"level":"info","caller":"logging/config.go:96","msg":"Successfully created the logger.","knative.dev/jsonconfig":"{\n  \"level\": \"info\",\n  \"development\": false,\n  \"sampling\": {\n    \"initial\": 100,\n    \"thereafter\": 100\n  },\n  \"outputPaths\": [\"stdout\"],\n  \"errorOutputPaths\": [\"stderr\"],\n  \"encoding\": \"json\",\n  \"encoderConfig\": {\n    \"timeKey\": \"\",\n    \"levelKey\": \"level\",\n    \"nameKey\": \"logger\",\n    \"callerKey\": \"caller\",\n    \"messageKey\": \"msg\",\n    \"stacktraceKey\": \"stacktrace\",\n    \"lineEnding\": \"\",\n    \"levelEncoder\": \"\",\n    \"timeEncoder\": \"\",\n    \"durationEncoder\": \"\",\n    \"callerEncoder\": \"\"\n  }\n}\n"}
{"level":"info","caller":"logging/config.go:97","msg":"Logging level set to info"}
{"level":"warn","caller":"logging/config.go:65","msg":"Fetch GitHub commit ID from kodata failed: open /var/run/ko/HEAD: permission denied"}
{"level":"info","logger":"webhook","caller":"webhook/main.go:52","msg":"Starting the Configuration Webhook","knative.dev/controller":"webhook"}
{"level":"info","logger":"webhook","caller":"webhook/webhook.go:301","msg":"Found certificates for webhook...","knative.dev/controller":"webhook"}
{"level":"error","logger":"webhook","caller":"webhook/webhook.go:310","msg":"failed to register webhook","knative.dev/controller":"webhook","error":"failed to create a webhook: mutatingwebhookconfigurations.admissionregistration.k8s.io \"webhook.tekton.dev\" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: User \"system:serviceaccount:tekton-pipelines:tekton-pipelines-controller\" cannot update deployments/finalizers.extensions at the cluster scope, <nil>","stacktrace":"github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook.(*AdmissionController).Run\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook/webhook.go:310\nmain.main\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/cmd/webhook/main.go:97\nruntime.main\n\t/usr/lib/google-golang/src/runtime/proc.go:200"}
{"level":"fatal","logger":"webhook","caller":"webhook/main.go:98","msg":"Error running admission controller{error 25 0  failed to create a webhook: mutatingwebhookconfigurations.admissionregistration.k8s.io \"webhook.tekton.dev\" is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to a resource you can't set finalizers on: User \"system:serviceaccount:tekton-pipelines:tekton-pipelines-controller\" cannot update deployments/finalizers.extensions at the cluster scope, <nil>}","knative.dev/controller":"webhook","stacktrace":"main.main\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/cmd/webhook/main.go:98\nruntime.main\n\t/usr/lib/google-golang/src/runtime/proc.go:200"}

Hi @abergmeier
Thanks! for reporting an issue. Recently we have fixed this issue. It would be available in the next release.
However, to get fix this issue, for the time being, you could add permissions to tekton-admin role according to patch.

However, to get fix this issue, for the time being, you could add permissions to tekton-admin role according to patch.

That seems to bring me further:
{"level":"info","caller":"logging/config.go:96","msg":"Successfully created the logger.","knative.dev/jsonconfig":"{\n  \"level\": \"info\",\n  \"development\": false,\n  \"sampling\": {\n    \"initial\": 100,\n    \"thereafter\": 100\n  },\n  \"outputPaths\": [\"stdout\"],\n  \"errorOutputPaths\": [\"stderr\"],\n  \"encoding\": \"json\",\n  \"encoderConfig\": {\n    \"timeKey\": \"\",\n    \"levelKey\": \"level\",\n    \"nameKey\": \"logger\",\n    \"callerKey\": \"caller\",\n    \"messageKey\": \"msg\",\n    \"stacktraceKey\": \"stacktrace\",\n    \"lineEnding\": \"\",\n    \"levelEncoder\": \"\",\n    \"timeEncoder\": \"\",\n    \"durationEncoder\": \"\",\n    \"callerEncoder\": \"\"\n  }\n}\n"}
{"level":"info","caller":"logging/config.go:97","msg":"Logging level set to info"}
{"level":"warn","caller":"logging/config.go:65","msg":"Fetch GitHub commit ID from kodata failed: open /var/run/ko/HEAD: permission denied"}
{"level":"info","logger":"webhook","caller":"webhook/main.go:52","msg":"Starting the Configuration Webhook","knative.dev/controller":"webhook"}
{"level":"info","logger":"webhook","caller":"webhook/webhook.go:301","msg":"Found certificates for webhook...","knative.dev/controller":"webhook"}
{"level":"info","logger":"webhook","caller":"webhook/webhook.go:402","msg":"Webhook already exists","knative.dev/controller":"webhook"}
{"level":"info","logger":"webhook","caller":"webhook/webhook.go:410","msg":"Updating webhook","knative.dev/controller":"webhook"}
{"level":"info","logger":"webhook","caller":"webhook/webhook.go:313","msg":"Successfully registered webhook","knative.dev/controller":"webhook"}
{"level":"error","logger":"webhook","caller":"webhook/webhook.go:321","msg":"ListenAndServeTLS for admission webhook returned error","knative.dev/controller":"webhook","error":"listen tcp :443: bind: permission denied","stacktrace":"github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook.(*AdmissionController).Run.func1\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook/webhook.go:321"}
{"level":"fatal","logger":"webhook","caller":"webhook/main.go:98","msg":"Error running admission controller{error 25 0  webhook server bootstrap failed}","knative.dev/controller":"webhook","stacktrace":"main.main\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/cmd/webhook/main.go:98\nruntime.main\n\t/usr/lib/google-golang/src/runtime/proc.go:200"}

That's true, this would solve the problem
oc adm policy add-scc-to-user anyuid system:serviceaccount:tekton-pipelines:tekton-pipelines-controller

Or if you are running minishift, you can enable minishift addon
minishift addon enable anyuid

@hrishin it may be good to have a document documenting all those gotchas (or limitations) somewhere,

copied @chmouel  :+1: .

/good-first-issue
/mostly-docs

And it seems we also need a hack oc adm policy add-cluster-role-to-user cluster-admin -z tekton-pipelines-controller -n tekton-pipelines for the pipelines-controller to work

@sthaha is it on 3.x or 4.x ? On os4.x with 0.2 release, webcontroller does not even start for me :
{"level":"error","logger":"webhook","caller":"webhook/webhook.go:321","msg":"ListenAndServeTLS for admission webhook returned error","knative.dev/controller":"webhook","error":"listen tcp :443: bind: permission denied","stacktrace":"github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook.(*AdmissionController).Run.func1\n\t/usr/local/google/home/jasonhall/go/src/github.com/knative/build-pipeline/vendor/github.com/knative/pkg/webhook/webhook.go:321"}

I'll start a new issue for this (i have tested the fix to bind it to another port and it will run)

Closing, looks like the documentation was added above.


add libunibreak line breaking package

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/jhs67/hunter/build/1.0.7
https://travis-ci.com/jhs67/hunter/builds/73760572

I have submitted CI configs to https://github.com/ingenue/hunter targeting pkg.template branch,
see this merged pull request https://github.com/ingenue/hunter/pull/253

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3972
https://travis-ci.org/ingenue/hunter/builds/380747212?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3973
https://travis-ci.org/ingenue/hunter/builds/380754781?utm_source=github_status&utm_medium=notification

Uploading

Failed, example: https://travis-ci.org/ingenue/hunter/jobs/380754786
The reason is because symbolic link contains full path:
> wget https://github.com/ingenue/hunter-cache-2/releases/download/cache-fbeef0c/fbeef0c0049a5135222b4afb7f8f4d309b8614ac.tar.bz2
> tar xf fbeef0c0049a5135222b4afb7f8f4d309b8614ac.tar.bz2
> ls -l lib/liblinebreak.a
... lib/liblinebreak.a -> //Users/travis/build/ingenue/hunter/_testing/Hunter/_Base/518f00b/5c58b6b/bfcd001/Build/libunibreak/Install/lib/libunibreak.a

hunter_cacheable removed: https://github.com/ruslo/hunter/commit/c9f82e4cab290f26ac39d9c1945d8a6967ce6d00
Released: https://github.com/ruslo/hunter/releases/tag/v0.21.6


Responses to out-of-MW-SDN-domain software have x-correlator header

x-correlator header should not be sent on the interface towards the out-of-MW-SDN-domain software.
The following paths are affected:

/v1/provide-list-of-connected-devices
/v1/provide-list-of-device-interfaces
/v1/provide-list-of-actual-device-equipment
...
/core-model-1-4:network-control-domain=cache/control-construct={mountName}

Fixed in tag "v1.0.0_impl-fix-6".

Fixed.


Ability to transfer organisations to other parents

At the moment an existing organisation can not be transferred to a new created parent organisation.

What is the ETA of this future request?

TODO:

[x] Implement backend
[ ] Expose in web UI
[ ] Update raml (possibly documentation)
[ ] Extensive verification ( since this probably has a large impact )

Reverted in cb804a7c7c8b8463294b4c62bbe7eeac5da03c5a
This was intended to be stashed to be able to work on more other things, as this is nowhere near completion ( see TODO list above). Unfortunately it seems I somehow committed this instead :(.

Moved this to the roadmap for now as it is not required for anything/anyone and is more of a quality of life thing


Update base.html

Hey this is a new PR

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview adb926d4-093e-406f-8710-67d7187aafd4
john-env

/qovery  preview 690075b1-3645-4e11-bc1d-549b5558a085
chris-env

/qovery  preview 07d2ddeb-ac9b-4055-9cab-3ac0de039e57
blueprint

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

Write comments that add new information that doesn’t exist in the code

/qovery preview 07d2ddeb-ac9b-4055-9cab-3ac0de039e57

/qovery preview 07d2ddeb-ac9b-4055-9cab-3ac0de039e57

A preview environment was automatically created via Qovery.
Click on the link below to follow its deployment and use it.
:point_right: [PR] blueprint - Update base.html - 2023-07-20T15:03:44Z
Another comment will be posted when deployments are terminated


[Dropdown] Set exactly fires an empty string

Using "set exactly" to set the value of a dropdown, fires off an empty string in onChange.
http://jsfiddle.net/91rp1v0L/2/

Watch the console output
Click "Set Value"

Expected:
I would expect that onChange only would occure once, when the actual value is set.
Actual:
onChange happens two times, first with an empty value, the second time with the actual value.

Yeah, if there are multiple elements in that array, it'll fire multiple times, each time single element change ! I also don't know why it is firing first value as empty.
Is there anyway complete array is selected at once instead of element by element ?
I'm also expecting a solution !

As set exactly triggers onChange after each individual change as stated in #4913, it obviously also fires after initially clearing the dropdown of all existing values. If #4913 is considered a bug, this should be considered a duplicate of it. If it isn't, this should be closed.

@philrykoff Thanks, you’re right, this one can probably be closed.


/plugins structure not working properly

Im using TYPE: PAPER in the docker-compose.
As described in the docs I mounted the /plugins folder.
Inserted there my GeyserMC.jar and Floodgate.jar.
But those have not been used in any way.
As well, I noticed the owner of the plugins folder is not 1000:1000 minecraft it is root.
From the host system, I'm manually copied the files to /data/plugins.
But unfortunately, then I ran in to the owner issue again as, the files are owned by root instead of minecraft.
So I manually need to change the ownership.
Greats

Can you also provide the container logs?

It found the mods, but both are invalid id you look at your logs
[22:45:53] [Server thread/ERROR]: Could not load 'plugins/floodgate-spigot.jar' in folder 'plugins'
org.bukkit.plugin.InvalidDescriptionException: Invalid plugin.yml

[22:45:53] [Server thread/ERROR]: Could not load 'plugins/Geyser-Spigot.jar' in folder 'plugins'
org.bukkit.plugin.InvalidDescriptionException: Invalid plugin.yml

This is something you need to fix. It's not a problem with the image.

Hi,
I got your point, but the root cause seems to be, for me, this line:
Caused by: java.io.FileNotFoundException: plugins/floodgate-spigot.jar (Permission denied)
As it hadn't the correct owner group, the parsing has failed.
After I changed manually the ownership, everything worked.
This printout was possible after I moved the file manually to /data/plugins.
If I understood the documentation correctly usually the files from the folder /plugins should be imported automatically.
But this didn't worked either.

Yes, /plugins gets synchronized to /data/plugins but if you have permission problems on your host side there's only so much the image fix.
You haven't yet provided your compose file. I can't help make without that.
Have you tried moving away the data path to let the container set it up properly?

No it is the permission inside the container not on the host site.
The container needs to align the permissions inside from it.
services:   minecraft-server:     image: itzg/minecraft-server     container_name: minecraft-server-java     environment:       EULA: "TRUE"       TYPE: PAPER       UID: $PUID       GID: $PGID       TZ: $TZ       GAMEMODE: survival       DIFFICULTY: normal       SERVER_NAME: MC Mad-Max       DEFAULT_PLAYER_PERMISSION_LEVEL: "member" # Options: visitor, member, operator       MEMORY: 6G       LEVEL_NAME: The Gloriuos World       VIEW_DISTANCE: "8"       TICK_DISTANCE: "4"       MAX_THREADS: "8"       #DISABLE_HEALTHCHECK: "true"     ports:       - 19132:19132/udp       - 25565:25565     volumes:       - $DOCKERDIR/Minecraft-Server-Java/data:/data     stdin_open: true     tty: true

Thanks, that helps.

Can you provide output from ls -ld $DOCKERDIR/Minecraft-Server-Java/data from the host side?
Can you provide ls -l $DOCKERDIR/Minecraft-Server-Java/data/plugins?
I don't see a volumes entry for /plugins. If you were trying that before, can you do the same ls -l for that host path?

Ah sorry for the missing volume at plugins.
I removed it as it didn't worked out and thought maybe this is part of the issue..
[/share/Container/Minecraft-Server-Java] # ls -ld data
drwxrwxr-x 8 Michael 1000 4096 2021-09-14 21:42 data/
[/share/Container/Minecraft-Server-Java] # ls -ld data/plugins
drwxr-xr-x 5 Michael 1000 4096 2021-09-14 00:53 data/plugins/
[/share/Container/Minecraft-Server-Java] # ls -l plugins
total 0
[/share/Container/Minecraft-Server-Java] #


Typo in docs => Azure Container Service (AKS)

Typo in:
https://docs.microsoft.com/en-us/rest/api/containerregistry/
Is:
Azure Container Service (AKS) - Deploy and manage containerized applications in a hosted Kubernetes environment.
Should be:
Azure Kubernetes Service (AKS) - Deploy and manage containerized applications in a hosted Kubernetes environment.

@geirivarjerstad - thank you for your feedback. I have transferred the issue to  source repo where this topic was written and notified the writers.


Fix glide

People have been modifying vendor and glide.lock not using the glide tool, leaving it in a weird state. This adds a new make target verify-glide, that just runs glide list and checks if there are any errors emitted. Making it a prerequisite of test means we'll get CI to run it on new PRs.
The only meaningful change here is to bump github.com/rakelkar/gonetsh to https://github.com/rakelkar/gonetsh/commit/501daadcadf88660f61cc3352bdcb26b5f8ba4ce. This looks like it was improperly done in #1161, instead of bumping gonetsh the vendored code was just modified directly.
Should mean #1194 can be much more straightforward once this is through :smile:

/lgtm
@arasananbu  Can you give it a quick glance?

Is there a reason that flannel cannot move to go modules instead?

I think we should, I just wanted to get Glide fixed first so we could bump a single dependency. When I explored switching to gomod it resulted in even more massive amounts of dependency changes.


Contributing

Very cool project, I was thinking of working on a 3 band EQ, but it may be a bit over my head as I'm rather new to javascript. I'd still love to contribute, is there anything a little simpler you have for me that could get me started? Docs, tests, whatever.
Thanks

A 3 band EQ would be awesome. Tests would be cool too, using web-audio-mock and mocha, sinon and chai. Any doc updates would be appreciated if you see opportunity for clarity

Sounds good ill do by best


Int matrix multiplication

Doing this well is actually really involved.
https://marek.ai/matrix-multiplication-on-cpu.html
https://github.com/flame/how-to-optimize-gemm
https://siboehm.com/articles/22/Fast-MMM-on-CPU


yield tuple of (ref, object) from canonical_stream

Changes canonical_stream to yield a tuple of (canonical_ref, canonical)
This will let the indexer know about the canonical ref of the objects in the stream.  Yields the base58 string form of the canonical ref.

We aren't really doing proper semantic versioning at this point but I think that's OK for rapid iteration