Layout is very confusing

Could make the https://social.technet.microsoft.com/Forums/ a little less confusing to use. Making the accepted answer appear immediately after the question doesn't help because I don't have the context of why the guy who posted the accepted is saying what he/she is saying on that answer. This question even got multiple accepted answers. Look at StackOverflow, their page looks and feels better than what you currently have.

@saldana Can you please take a look at this?

@rickyManalo I really appreciate your input. At this point we are not investing in changing the UI for the current forums. While we understand that having the answer on top next to the answer, I also see that Stack Overflow is doing the same and that is very common on a Q&A/forums platform. You can always scroll down to see the answers in context.
I understand you like better Stack Overflow UI than MSDN Forums user experience. That said, we are looking at copying the UI than Stack Overflow has.

Hi,
Not investing on the UI change huh. At least, SO doesn't display multiple
copies of the single accepted answer unlike the way you are currently
emphasizing the multiple accepted answers in your website. And no one is
even using the point increment/decrement thing on your page. That was the
only way you can punish those very needy people who just want the whole
code without even showing or telling what they've already done and/or tried.
Well, you've already said that you're not investing on changing the UI
while SO kept on looking for the best way to make asking, answering and
displaying a question easier and cleaner than what other Q&A forums
currently have.
Regards,
Ricky
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Fri, May 31, 2019 at 5:43 AM Sandra Aldana<EMAIL_ADDRESS>wrote:

@rickyManalo https://github.com/rickyManalo I really appreciate your
input. At this point we are not investing in changing the UI for the
current forums. While we understand that having the answer on top next to
the answer, I also see that Stack Overflow is doing the same and that is
very common on a Q&A/forums platform. You can always scroll down to see the
answers in context.
I understand you like better Stack Overflow UI than MSDN Forums user
experience. That said, we are looking at copying the UI than Stack Overflow
has.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/feedback/issues/1554?email_source=notifications&email_token=AKSOI6EAMFOR2WHQZMBXCF3PYBC65A5CNFSM4HQAO4EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWTTFEQ#issuecomment-497496722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKSOI6DV3QK5TIG6YRWIMTDPYBC65ANCNFSM4HQAO4EA
.

Thank you @rickyManalo while we do not have immediate plans to update the UI, we are considering your feedback for the future. I appreciate you taking the time to let us know your experience and recommendation.
Best,
Sandra

You're welcome.
Regards,
Ricky
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Jun 4, 2019 at 12:17 AM Sandra Aldana<EMAIL_ADDRESS>wrote:

Thank you @rickyManalo https://github.com/rickyManalo while we do not
have immediate plans to update the UI, we are considering your feedback for
the future. I appreciate you taking the time to let us know your experience
and recommendation.
Best,
Sandra
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/feedback/issues/1554?email_source=notifications&email_token=AKSOI6D34GWXXZ62G5ZRWNTPYU7YLA5CNFSM4HQAO4EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWZ5NYQ#issuecomment-498325218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKSOI6EXI4AGXB7MWFHUIUDPYU7YLANCNFSM4HQAO4EA
.


Handle error: No handware node for cluster instance

The following changes are included:

Return an error if no handware node is found for the cluster instance.
Update the unit tests to ensure the expected hardware node is created.

/hold

/hold cancel

/approve


seek() jump inaccurate

example:
when input seek(125),The player will play at random a few seconds ahead of schedule,such as  from 123 seconds.
I don't know if it's a video source problem

@ChenPrince Hi did you fix this error?


Fixes for the Element Selector dialog and link creation in HTML editor

Resolves #882
Overview
Fixed the element selector dialog when using the HTML editor, triggered by this button:

All element types can now expand the model trees so that versioned folders are included:

I've updated the Terms selection to work without loading every Terminology in the catalogue, restrict to a context:

And I've updated the creation of the hyperlink when added to the HTML editor to remove the branch name from the path in the link. This is because all links should be considered local to the branch they are directly under, other link rewriting code will automatically fill in a branch so the links work correctly, but they must be saved to Mauro without branches in them.
Testing

Test the Element Selector - make sure that you can create a link of every type
Test that the links created in the HTML editor work and are constrained to the branch they are under, even if you select an element from another versioned folder branch.

small update, same error as term seems to happen on data model as well

@OButlerOcc I tried fixing the error you found but can't make a nice fix for it. The problem is that the cursor may not be directly inside the editing area as you insert a link. For example:

Edit a description of an item, like the class "ACCOMMODATION".
Do not click inside the text area yet! ... but click on the element selector toolbar button (looks like two interlocked links)
Select any item to insert as a link
The error will happen because the edit text area does not have focus.
Now click in the editor text area to mark a selection for the Jodit editor and repeat the steps.
Now the link will be inserted correctly.

I've tried to capture the exception thrown and show a nicer warning, but the warning appears too often even when it does work. I think we just have to accept this bug for now.
As for the links and paths, the links inserted will not work inside the editor as designed because they are Mauro paths and not valid URLs. When you save them and view the read-only view of the content again, then the links work because an automatic parsing function is called to convert the Mauro paths in anchor tags into valid URLs. This is how it is intended to work.
I think if there is nothing else then this sounds ready to be accepted.


Why is this code installed on my computer?

I did NOT follow the installation instructions, and yet I found this nocode thing sitting on my computer. It is apparently installed in /dev/null, in fact there is a full copy of the entire source code there. How to I uninstall it? It is taking too much of my hard disk space. Please add clear uninstall instructions.

OK, figured it out on my own!
After studying again the readme file, I found that by NOT following the installation instructions I actually DID follow the installation instructions. This is why the code is installed on my computer.
To remove it, I had to do this:

Then, everything went back to normal:

Thanks for sharing, had the same issue, just wanted to clean up my pc.


Refactor server side pages to use react context instead of passing props all over the place

https://medium.com/@skwee357/the-land-of-undocumented-react-js-the-context-99b3f931ff73

Contexts not ready as a stable React feature.


NamedQueryContext does not support IN clause with array

Assume a simple query:
query := SELECT * FROM places WHERE id IN (:placeIDs)
where placeIDs is []uuid.UUID and queryArgs is map[string]interface{}
To execute this one would need to:
func executeInClauseSupport(ctx context.Context, db *sqlx.DB, query string, queryArgs map[string]interface{}) (*sql.Rows, error) {
	q, args, err := sqlx.Named(query, queryArgs)
	if err != nil {
		return nil, err
	}
	q, args, err = sqlx.In(q, args...)
	if err != nil {
		return nil, err
	}
	q = db.Rebind(q)
	return db.QueryContext(ctx, q, args...)
}

because an error is thrown when trying to execute:
rowsCount, errCount := d.db.NamedQueryContext(ctx, queryCount.String(), queryArgs)

I commented on #623, agreed it fixes this but I feel like it causes too many other issues.  I feel like sqlx.In, sqlx.Rebind and the Named query stuff could all be implemented in a cleaner way, but not without sacrificing backwards incompatibility.  As they are, they are built organically on top of each other over the course of several years;  I think the answer here is to create a helper function for your desired combination of In and NamedQuery;  I don't like the idea of In happening without people knowing that it's happening (or people "paying" for it unknowingly).


JsonLd validation of nested Objects is not working correctly

Hello, I think the json-ld validation is not working correctly for nested Objects.
Tested with bcgovimages/aries-cloudagent:py36-1.16-1_0.7.4 And bcgovimages/aries-cloudagent:py36-1.16-1_0.7.5
Steps to reproduce :

Start Acapy without AdminKey at port 11000
Create a DID of type SOV
Run the following curl command after replacing the issuer and verkey
NOTICE the nested object vaccine has an extra wrong property **testMeWrong**. This property is not part of the schema in  "https://w3id.org/vaccination/v1"

curl -X 'POST' \
  'http://localhost:11000/jsonld/sign' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "doc": {
    "credential": {
      "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/vaccination/v1"
      ],
      "type": [
        "VerifiableCredential",
        "VaccinationCertificate"
      ],
      "id": "urn:uvci:af5vshde843jf831j128fj",
      "name": "COVID-19 Vaccination Certificate",
      "description": "COVID-19 Vaccination Certificate",
      "issuanceDate": "2019-12-03T12:19:52Z",
      "expirationDate": "2029-12-03T12:19:52Z",
      "issuer": "<replace-issuer-sov-did>",
      "credentialSubject": {
        "type": "VaccinationEvent",
        "batchNumber": "1183738569",
        "administeringCentre": "MoH",
        "healthProfessional": "MoH",
        "countryOfVaccination": "NZ",
        "recipient": {
          "type": "VaccineRecipient",
          "givenName": "JOHN",
          "familyName": "SMITH",
          "gender": "Male",
          "birthDate": "1958-07-17"
        },
        "vaccine": {
          "type": "Vaccine",
          "testMeWrong": "WRONG",
          "disease": "COVID-19",
          "atcCode": "J07BX03",
          "medicinalProductName": "COVID-19 Vaccine Moderna",
          "marketingAuthorizationHolder": "Moderna Biotech"
        }
      }
    },
    "options": {
      "proofPurpose": "assertionMethod",
      "type": "Ed25519Signature2018",
      "verificationMethod": "did:sov:7rB93fLvW5kgujZ4E57ZxL#key-1"
    }
  },
  "verkey": "<replace-verkey>"
}'

The expected result is an Error
The actual result is a signed doc (I think it is also the case for issue json-ld credentials flows)

Update:
"testMeWrong": "WRONG" is included in the returned signed_doc from /jsonld/sign but I think it is not a part of the signature 😱 Because calling /jsonld/verify returns valid even if I change its value from "WRONG" to "WRONGXOX"

I think this is working correclty for using the JSON-LD exchange protocols, but not for the JSON-LD sign / verify endpoints. There is a get_properties_without_context in ACA-Py but it's not used for the jsonl-ld sign/verify endpoints.
The best route would probably be to update the jsonld sing/verify to use the new jsonld signeatures support in ACa-Py, but this method could be quick fix

I think this is working correclty for using the JSON-LD exchange protocols, but not for the JSON-LD sign / verify endpoints. There is a get_properties_without_context in ACA-Py but it's not used for the jsonl-ld sign/verify endpoints.
The best route would probably be to update the jsonld sing/verify to use the new jsonld signeatures support in ACa-Py, but this method could be quick fix

Thank you. Could you please add it to a todo list or at least add a warning until this is fixed :) I have been using this method for a while and probably others doing it too without knowing about this critical issue :)


Resume game does not work?

Hi, i am new to vim, but how can i resume a game? When i open an sqt file i saved earlier, vim just opens it as a text file, it does not ask to resume the game...
Any idea how to solve that?
Cheers and thanks!

The plugin tries to automatically load flies with the .sgf extension, because that's the extension I saw in gnugo examples, I think. It's a bit hidden in terms of functionality, though, I was even trying to figure it out recently myself :+1:
I've just added a new command, :GnugoLoad that you can use to load a savegame file. So, if you open vim and run :GnugoLoad <filename>, it should resume the game. Could you try it out and let me know if it works.

years later ;)

I've just added a new command, :GnugoLoad that you can use to load a savegame file. So, if you open vim and run :GnugoLoad <filename>, it should resume the game. Could you try it out and let me know if it works.

works ;)

Hey, better late than never :) :+1:


Search request threw an error

Undiscord Version
5.2.3
Browser
130.0.1-1
Extension
ViolentMonkey
Reproduction steps
Follow regular steps.
Actual results
Search request threw an error:	{"fileName":"","lineNumber":0,"columnNumber":1,"message":"NetworkError when attempting to fetch resource."}
CoreException	{"fileName":"","lineNumber":0,"columnNumber":1,"message":"NetworkError when attempting to fetch resource."}

Expected results
Not an error.
Bug affects

[X] DMs
[X] DMs (group)
[X] Channels
[X] Channel (NSFW)

Additional information & file uploads

I tried manually entering the authorization token, that didn't help either.
Edit: yes I tried disabling any other addons before creating this issue.

no idea what that was but I am unable to reproduce this anymore. closing.


Added icon in the titlebar for Feedback page

What does this PR do?
Added icon in the titlebar
Fixes #424

Type of change

Bug fix (non-breaking change which fixes an issue)
Breaking change (fix or feature that would cause existing functionality to not work as expected)

How should this be tested?

[x] Test A: Verified that the dropdown menu opens and closes correctly after the fix.
[x] Test B: Ran all unit tests related to the dropdown functionality, and they passed without issues.

Mandatory Tasks

[x] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.

@YadavAkhileshh , didnt added label sir ???


android camera crash report starting 3.8.1

https://play.google.com/console/u/0/developers/5847528771323009147/app/4972382363216562931/vitals/crashes/d5acd1c1/details?installedFrom=PLAY_STORE&days=60

this bug is impacting android 9 only and about 470 users. closing as won't fix. it seems to have stabilized.


Using $var to distinguish between vars?

Nice package idea, @joshday ! I was playing with a similar concept not too long ago and thought about how to cleanly separate "property" variables from "external" ones.
Just an idea: What do you think about using something like
z = 3
result = @with (x = 1, y = 2) begin
    $x + $y + z
end

A bit less concise, but it wouldn't need hasproperty, which may become a source of type instability with types that specialize propertynames. Or maybe a second macro in addition to with that used $var?

I like the idea of using the string interpolation syntax, especially for more complicated code blocks.  However, I also like how super-simple the current macro is.
I think a second macro/using dispatch would be a good idea.

@with_interp?
Choose your own interpolation identifier through dispatch?:

z = 3
result = @with :$ (x = 1, y = 2) begin
    $x + $y + z
end
result = @with :(:) (x = 1, y = 2) begin
    :x + :y + z
end

I also have an implementation of a macro that does broadcasting on properties (for easy column-wise ops on tables, etc.). I've been thinking of creating a small package for it, but maybe it would fit into PropertyUtils?

It's a simple macro called @bfp ("broadcast function over properties", wanted something short, maybe not the best name). Given something with vector/column-like properties a, b, c it allows you to do this
data[@bfp $a * $b + $c < 0.25]

As an equivalent for this
data[data.a .* data.b .+ data.c .< 0.25]

Very quick to write, but a lot faster than Query.jl, etc., esp. if only some of the columns of data are accessed.

If you think broadcasted property access would fit in here, I could put together a WIP PR, and we could see where it might lead. But I can also make a separate package if you'd like to keep PropertyUtils more lightweight.

Also I just tried this and it works out of the box:
@. @with df df[a * b * c < .25, :]

@with df @. df[a * b * c < .25, :]

Would your macro provide a benefit above composing @with with @.?  There did seem to be a lot of JIT overhead on the first run

Hm, maybe. But the way this works is actually a bit different: @bfp $a * $b + $c < 0.25 creates a function that will take some data, and then run the broadcast. And I specialize a few operations like getindex, filter, etc., to make things more concise. So
data[@bfp $a * $b + $c < 0.25] is actually a shortcut for data[(@bfp $a * $b + $c < 0.25)(data)].
Regarding code-gen, I guess what I currently do will be more lightweight, because the broadcast directly gets a ready-made single function.
A bit difference is that with @bfp, the function is only broadcast over the properties, so external variables don't have to be wrapped in a Ref, and in fact can't be broadcast over (by design). I guess this is really something where only a variant that has the vars prefixed with $ makes sense, otherwise the behavior would be unpredictable for somebody reading the code.

Another difference is that @with df @. a * b * c < .25 will usually instantiate the NamedTuple for each full row of df (I think I've seen the compiler elide it with TypedTables in very simple cases, but often, it can't).
(@bfp $a * $b + $c < .25)(df) on the other hand, build's a a function f(a, b, c) and broadcasts over df.a, df.b and df.c and never touches any other columns of df - so that memory is never accessed. That can make a big difference, cache- and bandwidth-wise sometimes.

There could, of course, also be a non-broadcast version of @bfp - say, @propfunc. So I guess one could have

@with obj expr that takes an object and expression - since the object is available, it's properties are known and prop-access in expr doesn't need to be $-prefixed. Having a broadcasted variant might be useful (to optimize mem-access, etc.).

(@propfunc expr)(obj) that takes an expression and builds a function that can then be applied to any object (that has the right properties). Since the obj isn't known yet, prop-access in expr needs to be $-prefixed, to mark which vars should access properties (otherwise, behaviour would seem unpredictable). But the result of (@propfunc expr) can be passed around, etc. @bfp (or similar) would the variant that creates a function that broadcasts over the data.

I think both approaches could be very useful at times. Question is just if they should live in the same package. :-) But maybe it would be nice to have central package to deal with such issues. We have bit and pieces like this scattered across the ecosystem I think, we could (humbly try to) establish some kind of standard set of operations to provide convenient prop-access.

Another difference is that @with df @. a * b * c < .25 will usually instantiate the NamedTuple for each full row of df

I don't think that's correct, since we are operating on columns instead of rows: @. gives the functions dots and then @with pulls out the 3 columns needed.

My gut intuition is that @bfp is too "magical", but if it does indeed provide a benefit over composing @. and @with, it would be nice to have here.

@. gives the functions dots and then @with pulls out the 3 columns needed.

Ah, you're, right of course! Maybe something like @bfp will still be convenient for filterby, etc. (esp. for quick interactive use), but I probably should flesh this out a bit more.

@oschulz For what it's worth, I kinda like (@propfunc expr) idea.  Copying the data isn't great, it'd be better to have a function that can be broadcasted.

@oschulz For what it's worth, I kinda like (@propfunc expr) idea.  Copying the data isn't great, it'd be better to have a function that can be broadcasted.

Hey @joshday , just came back to this (after a long time :-) ) - nowadays (PropertyUtils v1.3, Julia v1.9), this still works
julia> df = @inferred StructArray(
    a = rand(100), b = rand(100),
    c = rand(100), d = rand(100),
    e = rand(100), f = rand(100)
)

julia> @. @with df df[a * c * d < .25, :]

But this one doesn't anymore
julia> @with df @. df[a * c * d < .25, :]
ERROR: UndefVarError: `##337` not defined
Stacktrace:
 [1] top-level scope
   @ REPL[36]:1

Any idea why? The second version is the one that avoids reading/instantiating the whole NamedTuple{(:a, :b, :c, :d, :e, :f)} entries, right?

For future reference, I've created PropertyFunctions.jl to explore the concept of $var referencing properties.


Error of building, syntax error, unexpected 'array'

I run a code from example and it works on my local server. When I run same code on the google cloud server, I see this in logs:
PHP Parse error:  syntax error, unexpected 'array' (T_ARRAY), expecting function (T_FUNCTION) or const (T_CONST) in /var/www/html/zxc/vendor/endroid/qr-code/src/Builder/Builder.php on line 53
I have the same error with just this:
<?php

use Endroid\QrCode\Builder\Builder;

class QR
{
    public function generate(string $data, int $size = 300, int $margin = 10): string
    {
        var_dump(Builder::create());exit;

    }
}

53 line:
private array $options;
PHP 7.4.27 (cli) (built: Dec 20 2021 21:27:56) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.27, Copyright (c), by Zend Technologies
And same PHP version on the google cloud server.

Hi @sevaske typing a property as an array is compliant with any PHP version >= 7.4.0 so you are either running an older PHP version or something else is wrong on your server. Please note that your PHP CLI version is not necessarily the same as your FPM version. Good luck debugging ;)

Hi @sevaske typing a property as an array is compliant with any PHP version >= 7.4.0 so you are either running an older PHP version or something else is wrong on your server. Please note that your PHP CLI version is not necessarily the same as your FPM version. Good luck debugging ;)

Oh, you are right. We had the same PHP version FPM and CLI. Apparently someone changed the version. I should have checked it first, I'm sorry.


Update CBA enablement based on current UI

Update the correct sequence to enable CBD and explaining the existent screenshot supporting this explanation

Learn Build status updates of commit 9727ad7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/active-directory/authentication/how-to-certificate-based-authentication.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@Justinha @vimrang - Can you review these changes?

@miguel-s-ferreira Thanks so much and sorry for delay. To work around the branch conflict, I submitted the fix in a separate internal pull request. #please-close


InvalidBucketName while deploy

I am getting InvalidBucketName, I configured AWS with 'aws configure' but still getting invalid bucket name.

Weird, haven't seen this one before. A few questions:

What's the contents of the deploy script that yarn is running?

After the deploy script started, does it say anything before the error?

Can you please try running aws s3api get-bucket-location --bucket mkumaran.net with AWS CLI?

hi @JoshuaWalsh

content of the deploy script

file: package.json
"scripts": {
   "dev": "gatsby develop",
   "lint": "eslint --ext .js,.jsx --ignore-pattern public .",
   "test": "echo \"Write tests! -> https://gatsby.app/unit-testing\"",
   "format": "prettier --trailing-comma es5 --no-semi --single-quote --write 'src/**/*.js' 'src/**/*.md'",
   "develop": "gatsby develop",
   "start": "npm run develop",
   "build": "gatsby build",
   "deploy": "gatsby-plugin-s3 deploy",
   "fix-semi": "eslint --quiet --ignore-pattern node_modules --ignore-pattern public --parser babel-eslint --no-eslintrc --rule '{\"semi\": [2, \"never\"], \"no-extra-semi\": [2]}' --fix gatsby-node.js"
 }

after the script started

get-bucket-location command using AWS CLI

Just to make sure there's no Unicode weirdness going on, could you please delete `mkumaran.net` from your bucketName and copy/paste 'mkumaran.net' in its place?
Otherwise I'm pretty stumped, since you get the error before it says "Please review the following:" it means our call to s3.getBucketLocation is throwing this. I can't think what would cause that.

got it, working now. It's because of the cache folder.
I deleted the below files from ".cache" folder and rebuilt then deploy.

Did you try rebuilding without deleting those files? I'm wondering if just rebuilding was enough to fix it or if you had to delete those files. If it's the latter it's still a bug.

I didn't try that @JoshuaWalsh
first I deleted those files then rebuild.
I think, rebuild would have solved the issue.

I did a mistake here, I didn't build after changed my bucket name :(
without building I tried to deploy and couldn't recognize which bucket name was invalid from the error message.
One small suggestion:-
while displaying the invalid bucket name error, please display the bucket name also.

It's a bit tricky because the InvalidBucketName error is not returned by us, it comes from Amazon. I'm wondering if we can somehow detect if our cached settings are stale and a rebuild is required. Or maybe we should just log all the deployment settings immediately (instead of before we try to infer the region) and then users would notice that the settings being used are different from the ones they specified.


Is it possible to avoid network_mode: host (docker)

First off, thank you for putting this repo together. This seems like a really viable solution to get away from using LIFX Cloud.
I'm trying to do two things:

Move away from using cloud services.
Move away from network_mode: host in docker.

It seems as though network_mode: host should be unnecessary. When I google around for a solution network_mode: host seems to be the accepted answer and the rest is dismissed. Do you happen to know why this is needed?

I hope to have a docker-compose similar to below. Initially I will just set up a switch using a rest call in Home Assistant to turn my LIFX bulbs on/off. The equivalent of:
curl -XPUT http://photons:6100/v1/lifx/command -H Content-Type:application/json -d '{"command": "transform", "args": {"transform": {"power": "on"}}}'

Currently the call from the home-assistant container to the photons container works fine. The logs show:
photons_1         | 2020-09-17 11:42:55,263 INFO    tornado.access  200 PUT /v1/lifx/command (<IP_ADDRESS>) 6.46ms

However, the bulb's state does not change. I think this because some sort of communication needs made to the bulbs from inside the photons container; I'm not sure what this communication is, but that communication not being made seems to be the issue.
version: '3.8'

services:
  home-assistant:
    image: homeassistant/home-assistant
    restart: unless-stopped
    ports:
    - 8123:8123
    volumes:
    - ~/home-assistant:/config

  photons:
    image: delfick/lifx-photons-interactor
    restart: unless-stopped
    environment:
    - TZ=America/Chicago
    volumes:
    - ~/photons/configdir:/project/config

It also may be worth mentioning that I manually set my discovery settings:
interactor:
  host: photons
  port: 6100
  discovery_options:
    hardcoded_discovery:
      [redacted]: "[redacted]"
      [redacted]: "[redacted]"

I think I may have just realized the issue. It seems like the LIFX bulbs are not accessible from these containers because of how docker networks work. I'm now wondering if I can do some equivalent of port mapping with the IP's of my LIFX bulbs or something 🤷 .

I'm now thinking maybe the issue is related to photons discovering the LIFX bulbs.

You may want to try hardcoding the discovery of your bulbs: https://photons.delfick.com/configuration/discovery_options.html
However, I'm not sure why you're using both Home Assistant and Photons, as Home Assistant has full support for LIFX built-in: https://www.home-assistant.io/integrations/lifx/ which doesn't use the LIFX Cloud either.

@Djelibeybi I didn't realize that Home Assistant wasn't using the cloud. I've also tried hardcoding the discovery of the bulbs. Seems to me like that should have worked.

Docker's networking is ... interesting. Photons (and the LIFX app) use a UDP broadcast to discover bulbs and this is not something that Docker supports across its standard NAT network. If you don't want to share the same IP as your host via ``--network=host, you can also use macvlan` networking to give the container a real IP address on your network.

@Djelibeybi I was able to use the Advanced Configuration here: https://www.home-assistant.io/integrations/lifx/#advanced-configuration
It was able to discover one bulb, but not the other 🤷 .
lifx:
  light:
    - server: home-assistant
      port: 56700
      broadcast: [my fixed ip address for one bulb]
    - server: home-assistant
      port: 56700
      broadcast: [my fixed ip address for the other bulb]

I'm going to go ahead and close this since it's something I can solve using Home Assistant. Seems like if I mess with it some more the second bulb will be discovered.

FYI, the broadcast setting needs to be the broadcast address, not a specific address. If your network is <IP_ADDRESS>/24 then the broadcast address is <IP_ADDRESS>.

Yeah, the way LIFX does discovery is by a UDP broadcast on the network which the lights then respond to. Without access to the host network we can't do that, so you have to tell Photons where they are to prevent it needing it to do broadcast discovery. In the future I'll probably add the option to use mdns discovery. All our devices that support homekit provide mdns and so if you don't have older devices that discovery would work.
The reason your config in the original post doesn't work is because discovery options is under the root of the config rather than under interactor options.
So you want
---

interactor:
  host: photons
  port: 6100

discovery_options:
  hardcoded_discovery:
    [redacted]: "[redacted]"
    [redacted]: "[redacted]"

The alternative is to create a systemd service that runs the interactor. So something under /etc/systemd/system/interactor.service like
[Unit]
Description=The LIFX onboarder
After=network.target

[Service]
ExecStart=/path/to/photonsvenv/bin/lifx lan:interactor
Environment=LIFX_CONFIG=/path/to/my/lifx.yml
KillMode=process
Restart=on-failure

[Install]
WantedBy=multi-user.target

First off, thank you for putting this repo together. This seems like a really viable solution to get away from using LIFX Cloud

Thanks :)


Deploy signet explorer

The signet explorer graciously hosted at ordinals.com is out of date. Any chance we can get some of the slick new features available on there? Much appreciated!

https://signet.ordinals.com and https://itestnet.ordinals.com now up and running :)

legend, thank you!

@raphjaph sorry sir the json api didn't get turned out 😕 can I bother you for that?

we haven't enabled the json api anywhere, still considering if to do it.
But ord on signet is really easy to run! And then you can just enable the json api locally :)

Yep all good, that's what I've done. I need 2 indexes as mentioned in https://github.com/ordinals/ord/issues/2736 which I am doing on main net as well which isn't fun 😅


Image sync for joined node

Sync all available images to the new node after it's joined
Add a daily task that is launched only by the leader node to do image synchronization if an image doesn't get synced successfully across the nodes in the past
Minor improvement on image sync between the nodes

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Hey, you need to sign-off your commits. :) Should be as easy as git commit -s. :)

Ah, yes, I forget to sign-off my last commit. Thanks for the reminder.

Updated. Please take another look.
Thanks.

@jenkins: test this please

@adglkh there are Go lint failures, see the test run here https://jenkins.linuxcontainers.org/job/lxd-github-pull-test/5478/arch=amd64,backend=dir,compiler=golang-1.11,restrict=lxd-priv/console#console-section-3.
==> TEST BEGIN: static analysis
# github.com/lxc/lxd/lxd
lxd/api_cluster.go:562: loop variable fingerprint captured by func literal
lxd/api_cluster.go:564: loop variable fingerprint captured by func literal

PR is force pushed by resolving the following issue
loop variable fingerprint captured by func literal
Thanks

jenkins: test this please

Sorry I didn't get to review this earlier, just did now and got 2-3 things that need to get fixed.
Thanks!

Thanks for pointing this out.
As it's merged,  so can I create another PR to address the above issues that @stgraber mentioned?
Thanks.

@adglkh yep, just send another pull request

@adglkh any update on this? We're releasing next week and will need this fixed by then.

Sorry for the late, I've been focusing on a couple of high priority tasks in Anbox project.
The follow-up PR can be found here https://github.com/lxc/lxd/pull/5537
Thanks.


Eliminate self-invented shared_ptr-like classes

Fixes #1739

Absolutely agree with @dmitry-gurulev and @dvrogozh

@mgonchar, @dvrogozh, @dgurulev
I completely redid this commit, no longer using the std::shared_ptr<std::shared_ptr> construction, and only use shared pointers where it affects the frame lifetime.
At the moment, I have changed only H265DecoderFrame class, and I want to know your opinion on the design, whether it is worth changing the rest of the classes this way.


MWPW-156612 fragment merch-card variant layouts

move from merch-card.js code each layout code related to a given variant under variants/variant class
move from global.css.js css related to a given variant under variants/variant.css.js
move from merch-card.css.js wc css related to a given variant under variants/variant.variantStyle
uses variants/variants as an index to get related class from related variant, and wc style too,
uses variants/VariantLayout, superclass of all variants, to insert css if card is used, and hold common code

Resolves: https://jira.corp.adobe.com/browse/MWPW-156612
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off

After: https://MWPW-156612--milo--npeltier.hlx.page/?martech=off

Before: https://main--milo--adobecom.hlx.live/docs/library/kitchen-sink/merch-card?martech=off&georouting=off

After: https://MWPW-156612--milo--npeltier.hlx.live/docs/library/kitchen-sink/merch-card?martech=off&georouting=off

tested kitchen sink with consolidated style in one tag done before first card is even parsed https://test-consolidate--milo--npeltier.hlx.live/docs/library/kitchen-sink/merch-card?martech=off&georouting=off but does not look like it greatly improves TBT

will probably need to wait for https://github.com/adobecom/milo/pull/2798 but reviews can start

(i also need to check why TBT is increased)

@npeltier the style of merch-card with background opacity has changed. Was that intentional?
your branch:

actual:

@npeltier Seeing also differences in width on mobile for special offers cards:
your branch:

act

ual:

@afmicka background image, special offers, and bacom page should be fixed now. The width issue on kitchen sink is due to style ordering in case of multiple type of cards inserted in the same section. i'm not sure what we want here & started to discuss this internally.

issues seem fixed. Will mark it verified.
@Roycethan could you please also have a look just in case? If all good on your end, please add Ready for stage.

@afmicka postponed heavy styling changes to later PR (cc @yesil ) so no additional testing on your hand is needed :)
it's all in the hands of @Roycethan now :)


Paginator Order Context

To build paginators that rely on sort order (e.g. cursor pagination) the
sort order requested must be known when applying pagination. This adds
an additional argument to Paginator#apply to supply the current sort
order and hooks it in through the resource finders.

:+1:


Universal link failed if App removed from task stack

When the App is removed fromt the task stack, a press on a room universal link does not launch Vecto on the correspnding room. Only "Messages" UI is displayed.

Issue steps:

Start Vector App anget logged ot a valid user
On the device display the task stack (ex: Home button long press)
Remove the Vector form the stack
Go to the mailer to click on an universal link (ex: https://vector.im/develop/#/room/#RennesConnection:matrix.org)
Vector App stars but kept stuck in the "Messages" UI, the target room is not displayed

Expected result: In step 5 the target Room should be displayed.
Note: if the Vector App is not removed from the stack, there i no issue
Version: master#13 03-Jun-2016 08:07

The same issue is raised with the PermaLinks instead of the universla link.. likely a common root issue.

https://github.com/vector-im/vector-android/commit/74b4755f76008446b994d1bdb9de192455f66991


Comments are not appearing

Task
Comments aren't appearing inside of objects and arrays in the HAL browser. (see screenshot)
They are appearing for 'primary' properties, but not for 'secondary'.

Interesting screenshot choice, but bug makes sense!


Introduce some way to allow the user to customize what the clients can see or do

This could maybe be done by checking for a config file, for exampe config.json in which the user can specify how the server acts.

no


Remove support for consuming compressed signatures

Signatures are indistinguishable from randomness, so there is no point in compressing them.
Hence it is obvious that the only use for compressed signatures is exploitation of weaknesses in compression algorithms.
Therefore we should remove support for compressed data packets when reading signatures in SignatureUtils.readSignatures().

Thanks to @DemiMarie for pointing this out.


Bump version to 0.11.2

I'd like to make the recent 'is_key_released' feature available in the crate on crates.io, and a version bump  seems necessary.
Is this also sufficient, or is there something else that has to be done to get the new version on crates.io?

Thanks!


Enforce sleeping at least acceptedConnectionsDelay at hard limit

Previous logic was switched which could cause the accept thread to sleep
too long.
Thanks to @gufmar for helping with tracking down this issue.

bors r+


Update site-recovery-runbook-automation.md

The Powershell code was missing an important part where you need to have a parameter to allow passing in the RecoveryPlanContext object. If this not present the next line 5 will fail with during the "Get-Member"

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

#sign-off


[BUG]OpenSearch Javascript Client No or Bad response

Describe the bug
I am trying to integrate OpenSearch Javascript Client with Serverless Node application.
I have setup the client as follows
const client = new Client({
    ...AwsSigv4Signer({
        region: AWS_REGION,
        service: 'es',
        // Example with AWS SDK V2:
        getCredentials: () =>
            new Promise((resolve, reject) => {
                // Any other method to acquire a new Credentials object can be used.
                AWS.config.getCredentials((err, credentials) => {
                    if (err) {
                        reject(err);
                    } else {
                        logger.info('credentials', credentials);
                    }
                });
            }),
    }),
    node: 'mydomain.url', // OpenSearch domain URL
});

And used as
export async function search(): Promise<any> {
    logger.info(`open search connection => ${client.transport.connectionPool.getConnection()?.status}`);
    let result;
    try {
        result = await client.search({ index: 'opensearch_dashboards_sample_data_ecommerce'});
        logger.info(`search response ${JSON.stringify(result.body).slice(0, 200)}`);
        return result.body;
    } catch (error: any) {
        logger.error('open search client error', error);
    }
    return result?.body;
}

However I am not getting logs after the await search call. open search connection logs as alive
Also when I try to connect to local OpenSearch Cluster using docker.
const client = new Client({
node: http://admin:admin@localhost:5601,
})
above same function returns error
{"body":"","statusCode":302,"headers":{"location":"/app/home","osd-name":"d2bf50a79df9","cache-control":"private, no-cache, no-store, must-revalidate","set-cookie":["security_authentication=Fe26.2**a7a9f2cd499adba847e8b7b4712a2b304ecc5f0783628c90c1394141a8cc805d*-rKqsQ7n_BAVWq0t01RLFQ*ArbJO8TFB1m_ZKSYOKKo02SgOzuC7mKz0XmfOLmiOdJ217Y1I2QGMeXBL0pcFzBcKLwn-3i-3vfomGQdewyrYS2EqN8d69oL5qBLcUSwVaLkOUGFiU5LMe_aLBcQoObQNK-GcBH4qH-mwUe4uDBYtqGtjv1VVFY6AjeNI5sCoIXxLhylIZRqw5csO4KHwMeu9tXPGlSxm-xpI9gz_Pc0Yg**67d8efb5627180bd7631dc9b1dc6d235ed4c19949c2cde277a0926bdabd12856*HbvmzN14lC8SMcTfI1R6-KVvsg3df_d9_eJs3YEB6Mo; HttpOnly; Path=/"],"content-length":"0","date":"Fri, 20 Oct 2023 07:35:16 GMT","connection":"keep-alive","keep-alive":"timeout=120"},"meta":{"context":null,"request":{"params":{"method":"GET","path":"/","body":null,"querystring":"","headers":{"user-agent":"opensearch-js/2.4.0 (darwin 21.6.0-arm64; Node.js v16.19.1)"},"timeout":30000},"options":{},"id":3},"name":"opensearch-js","connection":{"url":"http://localhost:5601/","id":"http://localhost:5601/","headers":{},"deadCount":0,"resurrectTimeout":0,"_openRequests":0,"status":"alive","roles":{"data":true,"ingest":true}},"attempts":0,"aborted":false}}
2020-08-21 02:20:15: [error] - open search client error Response Error {"name":"**rror","meta":{"body":{"statusCode":"**04","error":"**ound","message":"**ound"},"statusCode":"**04","headers":{"osd-name":"**9df9","content-type":"**tf-8","cache-control":"**date","set-cookie":["**th=/"],"content-length":"**60","date":"** GMT","connection":"**live","keep-alive":"**=120"},"meta":{"request":{"params":{"method":"**ET","path":"**dZGN","headers":{"user-agent":"**9.1)"},"timeout":"**0000"},"id":"**4"},"name":"**h-js","connection":{"url":{"href":"**601/","origin":"**5601","protocol":"**ttp:","username":"**dmin","password":"**dmin","host":"**5601","hostname":"**host","port":"**01","pathname":"**/"},"id":"**601/","headers":{"authorization":"**aW4="},"_status":"**live","roles":{"data":"**ue","ingest":"**ue"},"agent":{"_eventsCount":"**2","defaultPort":"**80","protocol":"**ttp:","options":{"keepAlive":"**ue","keepAliveMsecs":"**00","maxSockets":"**56","maxFreeSockets":"**56","scheduling":"**fo"},"freeSockets":{"localhost":[null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null[{"_host":"**host","_readableState":{"highWaterMark":"**6384","flowing":"**ue","reading":"**ue","constructed":"**ue","needReadable":"**ue","autoDestroy":"**ue","defaultEncoding":"**f8","dataEmitted":"**ue"},"_eventsCount":"**6","_writableState":{"highWaterMark":"**6384","defaultEncoding":"**f8","allBuffers":"**ue","allNoop":"**ue","constructed":"**ue","autoDestroy":"**ue"},"_sockname":{"address":"**.0.1","family":"**v4","port":"**5189"},"_peername":{"address":"**.0.1","family":"**v4","port":"**01"},"bytesRead":"**18","remoteAddress":"**.0.1","remoteFamily":"**v4","remotePort":"**01","localAddress":"**.0.1","localPort":"**5189","localFamily":"**v4","_bytesDispatched":"**42","bytesWritten":"**42"}]]},"keepAliveMsecs":"**00","keepAlive":"**ue","maxSockets":"**56","maxFreeSockets":"**56","scheduling":"**fo","maxTotalSockets":"**nity","totalSocketCount":"**1"}}}},"stack":"ResponseError: Response Error\n  at onBody (/Users/abhimanyupatil/Desktop/repos/portal-backend/node_modules/@opensearch-project/opensearch/lib/Transport.js:425:23)\n  at IncomingMessage.onEnd (/Users/abhimanyupatil/Desktop/repos/portal-backend/node_modules/@opensearch-project/opensearch/lib/Transport.js:340:11)\n  at IncomingMessage.emit (node:events:525:35)\n  at IncomingMessage.emit (node:domain:489:12)\n  at endReadableNT (node:internal/streams/readable:1358:12)\n  at processTicksAndRejections (node:internal/process/task_queues:83:21)"}

Related component
Clients
To Reproduce
const client = new Client({
node: http://admin:admin@localhost:5601,
})
Expected behavior
no error
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

There are 2 problems here it seems, one with serverless and another with local.
I would start with local. Make sure your server is up curl -k -v -u username:password https://localhost:9200 and then try running https://github.com/opensearch-project/opensearch-js/blob/main/samples/search.js.
For serverless, the service name is aoss, not es. I don't know what the logging problem is, but I do have a tested end-to-end working sample in https://github.com/dblock/opensearch-node-client-demo that you might want to compare your code with.
I'm going to close this here but feel free to ask more questions. A better place to get help is the public slack #clients channel. If you/we find any bugs we can definitely open them here.


CRUD for work orders

need an endpoint to hit to add, get, edit and delete work orders 🗡

 Add Master Branch

Added CRUD on last release.


Folder Structuring

Hey @mrbhatt2348 , I have resolved issue #150 under JWOC. Kindly review😀

Thank you!

@mrbhatt2348 i have a query, have texted you on discord, please check


checkinTime does not work

I tried this https://ocellus.info/?page=3&size=30&resource=images&checkinTime=since(06-06-2023)
and this this

you might also want to write

see https://github.com/punkish/ocellus/issues/43#issuecomment-1587948445


Set 0 to pyarrow.fs.HadoopFileSystem port in v2 API to make it consistent to the v1 API behavior

With the v2 API, it fails to connect to HDFS whereas v1 (legacy API) is fine.
>>> pfio.v2.from_url('hdfs:///')
...
Traceback (most recent call last):
  File "<string>", line 2, in <module>
  File "/usr/local/lib/python3.8/contextlib.py", line 113, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.8/site-packages/pfio/v2/fs.py", line 285, in open_url
    with from_url(dirname) as fs:
  File "/usr/local/lib/python3.8/site-packages/pfio/v2/fs.py", line 314, in from_url
    fs = Hdfs(dirname, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/pfio/v2/hdfs.py", line 185, in __init__
    self._fs = _create_fs()
  File "/usr/local/lib/python3.8/site-packages/pfio/v2/hdfs.py", line 167, in _create_fs
    return HadoopFileSystem(nameservice)
  File "pyarrow/_hdfs.pyx", line 83, in pyarrow._hdfs.HadoopFileSystem.__init__
  File "pyarrow/error.pxi", line 141, in pyarrow.lib.pyarrow_internal_check_status
  File "pyarrow/error.pxi", line 112, in pyarrow.lib.check_status
OSError: HDFS connection failed

The v1 API uses the pyarrow deprecated function pyarrow.hdfs.connect, while v2 uses the new recommended one pyarrow.fs.HadoopFileSystem.
In both API, pfio doesn't explicitly specify port number, however hdfs.connect uses 0 for the default port, but fs.HadoopFileSystem sets 8020. I found that this mismatch causes the issue where pfio+HDFS works with v1 but doesn't work with v2.
If I modify the v2 API to explicitly specfy 0 to the port argument when instantiating pyarrow.fs.HadoopFileSystem, it seems to work as expected.
This PR proposes to introduce this change.
I guess this change should be related to how the storage environment is set up, so if there's a better way to configure port, please let me know.

/test


Segmentation fault core dumped on Godot 4.0.3-stable (Request feature)

Godot version
v4.0.1.stable.official [cacf49999]
EDIT: v4.0.3.stable.official [5222a99f5] (I tested this error on 4.0.3, 4.0.2, and 4.0.1)
System information
Linux 20.04 intel i7, Mac intel i7, Mac M1 (Compatibility and GLES2)
Issue description
I can't find a way to request the feature. I'd like to request the feature to display the detail error. I'm using gdscript and I don't even know how to use C at all.
The error is only able to display the error using command line. It doesn't show on the godot editor. See the video here:
https://github.com/godotengine/godot/assets/65916520/34b5cd24-6dad-4636-88f5-66dc886911ff
I'm able to see the error below:

javascript ip: <null> port: <null> full: <null>
connecting to: ws://<IP_ADDRESS>:9050
CORE FEAGI ROOTADDRESS: <IP_ADDRESS>:8000
ERROR: Viewport Texture must be set to use it.
   at: get_size (scene/main/viewport.cpp:126)

Those are print from me plus the last error is known for so long time. It's been there since 3.1. It'snot the error I want to focus on.
The actual error is here:
Segmentation fault (core dumped)
I want to find the root of cause. I can't do that unless I go to C for that which I'm not quite familiar with C. I don't even know where to start.
So, I tried the log. See here:
bwuk@robots:~/ko/feagi/third_party/godot/godot_source$ cat .here.log
{
	"core": 0.01215,
	"servers": 0.386833,
	"scene": 0.114149,
	"load_autoloads": 0.009495,
	"game_load": 0.461491,
	"total_time": 0.984909

Which doesn't tell me anything.
My request is to be able to provide more details than just this error.
Steps to reproduce
Unfortunately, this occurs on my own code only. I was not able to re-produce the error on a new and simple project.
Minimal reproduction project
If you really need this as this code is only from my project: https://github.com/feagi/feagi/tree/feature-update-new-menu/third_party/godot/godot_source
Branch: feature-update-new-menu
It won't happen to others project, I doubt. I think this is not belong to request feature. Let me know if you are still wanting to use this godot project, I can give you a short list to make it running.

Forgot to add this part, I ran --verbose as well.
bwuk@robots:~/ko/feagi/third_party/godot/godot_source$ ./Godot_v4.0.3-stable_linux.x86_64 --verbose
Godot Engine v4.0.3.stable.official.5222a99f5 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
/lib/x86_64-linux-gnu/libxkbcommon.so.0: undefined symbol: xkb_utf32_to_keysym
/lib/x86_64-linux-gnu/libxkbcommon.so.0: undefined symbol: xkb_keymap_key_get_mods_for_level
XInput: Refreshing devices.
XInput: No touch devices found.
Detecting GPUs, set DRI_PRIME in the environment to override GPU detection logic.
Text-to-Speech: Speech Dispatcher initialized.
Found renderers:
Renderer 0: Mesa Intel(R) HD Graphics 530 (SKL GT2) with priority: 20
Renderer 1: NV117 with priority: 10
Using renderer: Mesa Intel(R) HD Graphics 530 (SKL GT2)
Using "default" pen tablet driver...
OpenGL API 4.6 (Core Profile) Mesa 21.2.6 - Compatibility - Using Device: Intel - Mesa Intel(R) HD Graphics 530 (SKL GT2)
JoypadLinux: udev enabled and loaded successfully.
PulseAudio: context other
PulseAudio: context other
PulseAudio: context other
PulseAudio: context ready
PulseAudio: Detecting channels for device: alsa_output.pci-0000_00_1f.3.analog-stereo
PulseAudio: detected 2 output channels
PulseAudio: audio buffer frames: 512 calculated output latency: 11ms

TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH:<PHONE_NUMBER>
Loaded builtin certs
Loading resource: res://Network/SimpleNetworkWorker.tscn
Loading resource: res://UI/Units/unit.tscn
Loading resource: res://UI/Units/Components/Field/field.tscn
Loading resource: res://UI/Units/Components/Counter/counter.tscn
Loading resource: res://UI/Units/Components/Toggle/Toggle.tscn
Loading resource: res://UI/Units/Components/DropDown/DropDown.tscn
Loading resource: res://UI/Units/Components/Header/header.tscn
Loading resource: res://UI/Units/Components/Button/button.tscn
Loading resource: res://UI/Units/Components/Fill/fill.tscn
Loading resource: res://UI/UnitGraph/UnitNodes/cortexNode.tscn
javascript ip: <null> port: <null> full: <null>
connecting to: ws://<IP_ADDRESS>:9050
CORE FEAGI ROOTADDRESS: <IP_ADDRESS>:8000
ERROR: Viewport Texture must be set to use it.
   at: get_size (scene/main/viewport.cpp:126)
Segmentation fault (core dumped)
bwuk@robots:~/ko/feagi/third_party/godot/godot_source$

@Kakcalu13 Would help immensely If you could debug the GDScript code and find the exact call resulting in Segmentation fault (core dumped).

I agree! This is why I ask for feature so I can debug it easily. Right now, I don't have a way to do it with over 10k lines in gdscript with at least 10 different scripts. This error doesn't return anything helpful or useful information. I was hoping if there's existing feature or something :sweat_smile:

To get information on a segmentation fault you actually need to compile Godot from source with debug symbols enabled (scons debug_symbols=yes). Then you should get a stacktrace when it crashes (if not, run it through gdb and it should work).

Thanks! My apologies, but is this the correct one?
https://docs.godotengine.org/en/stable/contributing/development/compiling/getting_source.html
I have never done this before with scons or gdb.
As we are typing, I'm already git cloning it

Unfortunately, error occured and got it killed.
Error:
[Initial build] Compiling platform/uwp/export/app_packager.cpp ...
[Initial build] Compiling platform/uwp/export/export.cpp ...
[Initial build] Compiling platform/uwp/export/export_plugin.cpp ...
{standard input}: Assembler messages:
{standard input}:229548: Warning: end of file not at end of a line; newline inserted
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
scons: *** [modules/text_server_adv/text_server_adv.linuxbsd.editor.x86_64.o] Error 1
scons: building terminated because of errors.
[Time elapsed: 00:12:44.839]
bwuk@robots:~/godot$

Last command:
scons platform=linuxbsd debug_symbols=yes
git status:
bwuk@robots:~/godot$ git show .
commit 2e273f0e35800f2bcc7c05db54100caa97928f69 (HEAD -> master, origin/master, origin/HEAD)
Merge: 42775ff75b 8c288918a0
Author: Rémi Verschelde<EMAIL_ADDRESS>Date:   Thu Jun 1 15:52:16 2023 +0200

    Merge pull request #77724 from RandomShaper/remove_red_th_cond

    Remove redundant check from thread guards

bwuk@robots:~/godot$

We believe we identified the issue. Although I'm unsure how to phrase it clearly, I will do my best.
The good news is that this problem is related to the graphedit node, which from my understanding is set to be rewritten anyways.
I still hope for a feature that can assist us in promptly debugging such as this feature, but we may be abletowrite our algorithm instead in the meanwhile
The problem lies within the algorithms. I will let him explain the specific details of the issue.

To give some more context to the issue, this was caused by " arrange_nodes() " in a graph edit inheriting script.
Its difficult to give an example since our code is constructing nodes given data being pulled from some internal servers of ours. However, we noticed the issue would occur when pulling larger / more complex data sets. We found that commenting out "arrange_nodes()" would solely stop the crash from occurring.
I believe the data set being loaded has some ~38 nodes, but with some complicated / recursive connections. While we cannot share this data set itself, if you are interested in looking into this issue, we can create a seperate dummy project that causes the same problem.
That being said since graph edit is being redone anyways, its understandable if you have other priorities instead.
Thanks!

@felaugmar
I am unable to build from the source. See my previous message regarding the source build, unless am I doing something wrong with debug_symbols=yes?
I am still very much interested in providing all the information you need. I sincerely hope to avoid encountering this issue again or for anyone else to experience a similar problem.

Segmentation faults are not going to give you any more error messages. The program is dead at that point. It can't give you any more information. Your options are either "print k" debugging, where you print information at progress points along the way, or you use a debugger. You can use print k plus the gdscript debugger to help identify where in your code the segmentation fault is being triggered.
Or you compile the engine and use a C++ debugger as others stated. There are hundreds of people who build the engine daily, so if you're not able to build the engine it is because of one of these factors:

You're building the master branch and it's temporarily broken. This is rare though. Switch to the stable 4.0 branch or 4.0.3 tag and build that.
Your build environment is not set up properly. Most likely.
 You can use the -j switch to reduce the number of threads in the build chain. It defaults to # of logical cores - 1. You can go all the way down to 1.

@Kakcalu13 It sounds like your CPU has issues, such as not being given enough voltage (which causes sporadic failures of this kind). How old is your laptop? You could also try building with fewer CPU cores using the -j2 or -j1 SCons option.

Thanks! The culprit could either be a CPU issue or an environment build issue. I wouldn't be surprised if it's a CPU issue, considering I have PyCharm full edition, two Godot editors, and multiple terminals/chrome windows (with at least 10 tabs) running concurrently. I sincerely apologize for the delayed response, and I will provide you with the output as soon as possible. I'll share the output from my M1 Mac.
This laptop was released in 2014, and it uses an Intel i7 processor. The specific model is the Dell Inspiron 15.6" Full HD Laptop, equipped with an Intel Core i7-6700HQ. It is currently running on Ubuntu 20.04 Linux.

@Calinou I also exprienced this crash. You can reproduce this in floating window mode.
This is my cpu: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz (6 Threads)

@younggam Could you share the shader that this happens with? If there is a legitimate issue in the arranger, it would be hard to reproduce without the specific configuration that causes the crash. Also, which version of Godot are you on? Have you tried the latest master, if you can?

sry I can't reproduce it anymore even reverted changes by git. I'm in v4.1.1.
However, whole godot editor shutdowned repeatedly in that state.
+
Press Window mode button After pressing Arrange nodes button randomely crashes.
I guess there's some relation between window mode and arrange nodes


feat(ru-KZ): autogenerated locale ru-KZ. Closes #108

Proposes initial auto translation for ru-KZ with @yenbekbay as maintainer

Thank you for your review, @yenbekbay!


Update sdxl rocm flags to match branch performance

With these additions we get to ~70ms on MI300, which reaches parity with the sdxl branch bar tunings.

@saienduri is there a CI flag I can add to run this or does it happen automatically?

@saienduri is there a CI flag I can add to run this or does it happen automatically?

It ran: https://github.com/iree-org/iree/actions/runs/8897947826/job/24434436488?pr=17232. That file is currently controlling test flags. We should also have an in-tree version of https://github.com/nod-ai/SHARK-TestSuite/blob/main/iree_tests/benchmarks/benchmark_sdxl_rocm.sh for benchmark flags.

@saienduri is there a CI flag I can add to run this or does it happen automatically?

It ran: https://github.com/iree-org/iree/actions/runs/8897947826/job/24434436488?pr=17232. That file is currently controlling test flags. We should also have an in-tree version of https://github.com/nod-ai/SHARK-TestSuite/blob/main/iree_tests/benchmarks/benchmark_sdxl_rocm.sh for benchmark flags.

ah ok so looks like we should probably update the flags for that script also.

Yeah. Though I'd want to pull the script into this repo so we don't need to cross repos to change flags and test performance changes.

Nice! I can take care of updating the flags on the SHARK-TestSuite side of things. So, these flags will only help for scheduled unet? (not prompt encoder or vae decode). Also, the benchmark script is using vmfbs generated by the model tests, so we don't have to worry about changing flags for that script (it's all connected).

Nice! I can take care of updating the flags on the SHARK-TestSuite side of things. So, these flags will only help for scheduled unet? (not prompt encoder or vae decode). Also, the benchmark script is using vmfbs generated by the model tests, so we don't have to worry about changing flags for that script (it's all connected).

yeah it might help on the others but I haven't tested. Unet is the main one for now anyway.


[feature request] Docker Support

What
Docker Support for private deployment
Details
Maybe we could build a docker image to docker hub that can help us deploy this service more easier.

It is not official, but you can try this.
https://github.com/3YOURMIND/js-polyfill-docker
I'm using it in my environment and till now it's working very good.

Hi @LeuisKen and @teawithfruit, we won't be publishing images to Docker Hub as we do not use Docker ourselves and it would be an extra piece of maintenance that we would have to take on to keep it up-to-date with any security patches and/or updates.


4.2: remove crosshair feature after the map was moved

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

5 of 5 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.66%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
12541

Relevant Lines:
12542

💛  - Coveralls


feat:  add drag and drop functionality [FTL-7664]

does it make sens to have a video recording of the (fixed?) bug ?

:tada: This PR is included in version 1.13.0 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Update basnet_test.py

Description
When python basnet_test.py was executed, the subprocesses were created recursively and execution was failed with an error. The solution to this problem is to wrap the code in if __name__ == '__main__':
Stacktrace:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 125, in _main
    prepare(preparation_data)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 236, in prepare
    _fixup_main_from_path(data['init_main_from_path'])
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 287, in _fixup_main_from_path
    main_content = runpy.run_path(main_path,
  File "/Users/proshore/opt/anaconda3/lib/python3.8/runpy.py", line 265, in run_path
    return _run_module_code(code, init_globals, run_name,
  File "/Users/proshore/opt/anaconda3/lib/python3.8/runpy.py", line 97, in _run_module_code
    _run_code(code, mod_globals, init_globals,
  File "/Users/proshore/opt/anaconda3/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/Users/proshore/Documents/work/python/ai/BASNet/basnet_test.py", line 75, in <module>
    for i_test, data_test in enumerate(test_salobj_dataloader):
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 352, in __iter__
    return self._get_iterator()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 294, in _get_iterator
    return _MultiProcessingDataLoaderIter(self)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 801, in __init__
    w.start()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/context.py", line 283, in _Popen
    return Popen(process_obj)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/popen_spawn_posix.py", line 42, in _launch
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 154, in get_preparation_data
    _check_not_importing_main()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/spawn.py", line 134, in _check_not_importing_main
    raise RuntimeError('''
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.
Traceback (most recent call last):
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 872, in _try_get_data
    data = self._data_queue.get(timeout=timeout)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/queues.py", line 107, in get
    if not self._poll(timeout):
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/connection.py", line 257, in poll
    return self._poll(timeout)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/connection.py", line 424, in _poll
    r = wait([self], timeout)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/multiprocessing/connection.py", line 931, in wait
    ready = selector.select(timeout)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/selectors.py", line 415, in select
    fd_event_list = self._selector.poll(timeout)
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/_utils/signal_handling.py", line 66, in handler
    _error_if_any_worker_fails()
RuntimeError: DataLoader worker (pid 73291) exited unexpectedly with exit code 1. Details are lost due to multiprocessing. Rerunning with num_workers=0 may give better error trace.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "basnet_test.py", line 75, in <module>
    for i_test, data_test in enumerate(test_salobj_dataloader):
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 435, in __next__
    data = self._next_data()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1068, in _next_data
    idx, data = self._get_data()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1034, in _get_data
    success, data = self._try_get_data()
  File "/Users/proshore/opt/anaconda3/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 885, in _try_get_data
    raise RuntimeError('DataLoader worker (pid(s) {}) exited unexpectedly'.format(pids_str)) from e
RuntimeError: DataLoader worker (pid(s) 73291) exited unexpectedly

@xuebinqin May you please review this?


UI Refactor

Changes

split nota api and web into separate folders
added seed script npm run seed for api
added docker (optional)

Closing due to: https://github.com/Adaptech/nota/pull/12


spec: replace nullable value with null type

Description

replace all nullable values with type null
replace anyOf and oneOf with type string, null

Issues Resolved
Closes https://github.com/opensearch-project/opensearch-api-specification/issues/366
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

I am wondering. Do we need this:
oneOf:
    - type: number
    - type:
        - 'null'
        - string

or would following also work:
oneOf:
    - type:
        - 'null'
        - number

I am wondering. Do we need this:
oneOf:
    - type: number
    - type:
        - 'null'
        - string

or would following also work:
oneOf:
    - type:
        - 'null'
        - number

I think oneOf here is not required.

The quoted 'null' feels a little awkward, does it get treaded differently from a null (without quotes)?

The quoted 'null' feels a little awkward, does it get treaded differently from a null (without quotes)?

Yes, otherwise it get interpreted by yaml.

The quoted 'null' feels a little awkward, does it get treaded differently from a null (without quotes)?

Yes, otherwise it get interpreted by yaml.

So, can we introduce a NullableString so that we don't accidentally confuse the two?


feathers generate authentication failed!

Steps to reproduce
(First please check that this issue is not already solved as described
here)

[ ] Tell us what broke. The more detailed the better.
[ ] If you can, please create a simple example that reproduces the issue and link to a gist, jsbin, repo, etc.

Expected behavior
Tell us what should happen
Actual behavior
I want to generate an authentication, so I run feathers generate authentication. But it stop here

I can do nothing. press any key is not working.
System configuration
Tell us about the applicable parts of your setup.
Module versions (especially the part that's not working):
NodeJS version: 8.1.0
Operating System: macOS
Browser Version:
React Native Version:
Module Loader:

Can reproduce the problem with:

Windows 10 Pro 64bit
Node 8.1.0
Latest feathers-cli

Tried on Windows Cmd, PowerShell, babun (zsh). Each with and without administrative rights.

@eddyystop Can you reproduce this on your Windows machine?

I run a Ubuntu VM. I'll set up a Windows environment tomorrow.

I can also confirm that this is also happening on Node 8.1.0 on Mac OS.

This was caused by an issue in Node 8.1.0 (https://github.com/nodejs/node/issues/13557). I just verified that it has been fixed in the latest version.
If you are encountering this problem, please upgrade to 8.1.1 or later.


Redirect legacy DNS names to current name

Guarded by feature flag, per application.
@hakonhall: Please review the feature flag part.

Allows us to throw away one NameService implementation.


test(pkg/envoy/eds): improve test coverage for clusterLoadAssignment

Description:
This pr improves test coverage for the method newClusterLoadAssignment
and converts the test to use go library
Fixes #3410
Signed-off-by: Sneha Chhabria<EMAIL_ADDRESS>Affected area:

Functional Area

Tests
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Did you notify the maintainers and provide attribution?

Is this a breaking change? no

Codecov Report

Merging #3472 (7233447) into main (8c812c8) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 7233447 differs from pull request most recent head 6b449b1. Consider uploading reports for the commit 6b449b1 to get more accurate results

@@           Coverage Diff           @@
##             main    #3472   +/-   ##
=======================================
  Coverage   65.82%   65.82%
=======================================
  Files         169      169
  Lines        7886     7886
=======================================
  Hits         5191     5191
  Misses       2664     2664
  Partials       31       31

Flag
Coverage Δ

unittests
65.82% <ø> (ø)

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

Impacted Files
Coverage Δ

pkg/kubernetes/announcement_handlers.go
71.42% <0.00%> (-5.72%)
:arrow_down:

pkg/endpoint/providers/kube/client.go
79.20% <0.00%> (+0.99%)
:arrow_up:

pkg/envoy/eds/cluster_load_assignment.go
100.00% <0.00%> (+4.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Memory leak when running GraphQL codegen for iOS

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.15.1
Amplify CLI Version
7.5.4
What operating system are you using?
mac
Amplify Categories
api
Amplify Commands
codegen
Describe the bug
I've got a large app that leaks a small amount of memory on every query. It's almost identical to this issue described in the apollo-ios client, which was fixed in version 0.29.0, by changing how the API.swift file is generated:
https://github.com/apollographql/apollo-ios/issues/230
I'm thinking this has to do with AWSAppSyncClient using an outdated version of the Apollo client. Is there a way to verify exactly what version of Apollo AppSync uses?
Expected behavior
I would expect the generated code to not cause any memory leaks.
Reproduction steps
I will be adding a minimum reproducible project later this week.
GraphQL schema(s)
No response
Log output
No response
Additional information
No response

Thank you for filing this issue @fkunecke, when you've had a chance to create your repro project, please remove the 'pending-response' label, and we'll take a look.

Closing due to inactivity. Please reopen if issue still exists. Thanks.


commitCommentEvent Model needs to be handled

closed via https://github.com/sedouard/gittrack/pull/60

Actually closed via https://github.com/sedouard/gittrack/commit/d9156e35ffa9cf836960ae4fe50018b88e06dec1


Cannot read property 'scrollTop' of undefined when using jQuery

When using jQuery in a project the following line gives the error in the title:
var scrollTop = e.detail.scrollTop;
It has to be replaced with this line to work:
var scrollTop = e.originalEvent.detail.scrollTop;
An if statement has to be used to detect if jQuery is used but I don't know how to do that.
Update
This fix seems to work in iOS but not in Android. This can be seen in both chrome developer tools device mode and the actual devices.

I have the same issue.

its work for me---
document.getElementById('scrollT').onscroll = function(evt) {
if (navigator.userAgent.match(/Android/i) || navigator.userAgent.match(/webOS/i) || navigator.userAgent.match(/iPhone/i) || navigator.userAgent.match(/iPad/i) || navigator.userAgent.match(/iPod/i) || navigator.userAgent.match(/BlackBerry/i) || navigator.userAgent.match(/Windows Phone/i)) {
console.log('app', evt.target.scrollTop);
if (evt.target.scrollTop > 250) {
$ionicNavBarDelegate.title($scope.food.name);
} else {
$ionicNavBarDelegate.title('');
}
} else {
console.log('web', evt.detail.scrollTop);
if (evt.detail.scrollTop > 260) {
$ionicNavBarDelegate.title($scope.food.name);
} else {
$ionicNavBarDelegate.title('');
}
}
        }

Hi guys,
I landed here by looking for a way to hide my sub-header on scroll and found this codepen:
http://codepen.io/anon/pen/rOXLzY
It didn't work for me by failing at a similar line to where you guys are having the problem:
        $rootScope.slideHeader = false;```

I wasn't using jQuery though. It worked for me by changing ```e.detail.scrollTop``` with ```e.target.scrollTop``` now I'm not getting errors.

I have the same issue.

This error is because of disabling jsscrolling -
$ionicConfigProvider.scrolling.jsScrolling(false);


Attract Mode

I'm using a pi3 B+ and the Retroflag Superpi Case.The case and  script works perfect if I'm using emulation station but if I switch to Attract Mode the on/off and reset button do not work so I have to shut it down through the menu.  Is there a script that works with Attract Mode?

I have the same issue.  It does not send the command in Attract Mode.

I ran sudo nano /opt/RetroFlag/SafeShutdown.py and changed wherever it said emulatationstation  to attract and that seemed to work. Both the power button and reset work and saves metadata.

@faustable can you describe wich lines i have to edit in the script? i read it and it calls functions on the other script (Multiswitch) thanks!


Update IndexOption to Index

The first IndexOption reference in the article is changed to Index. The second reference stays intact and is correct.
Fixes #7309

Thank you for the help, @daveabrock!


Add MrManager's file

created a branch, created a file and made a commit, and opened a pull request


Make the .jl remote suffix optional

Had a nice conversation with @aminya who is looking at PkgTemplates for non-Julia stuff. All the Julia-specific plugins can be disabled easily, but Git only requires this small change to be language-agnostic.

Thank you for making this ❤.


HHH-16119 Named native queries do not work with jakarta.persistence.Tuple result class

https://hibernate.atlassian.net/browse/HHH-15999

Nice!


Corrupted(lost packet, invalid sequence)

Prerequisites
Please check the FAQ, and search existing issues for similar questions before creating a new issue.YOU MAY DELETE THIS PREREQUISITES SECTION.
collector:1.8.1
web.18.1
agent:1.7.2

question
I found  the error :Corrupted(lost packet, invalid sequence)  from calltree.
From the issue #5600 , i check the following info:
collector.receiver.span.worker.queueSize in pinpoint-collector.properties is 4096.
stat.log is as following.

Need to increase the worker queueSize?
Thank you.

stat.log
2019-09-19 09:47:33 INFO
type=GAUGE, name=spanReceiverExecutor.completed, value=30073924564
2019-09-19 09:47:33 INFO
type=GAUGE, name=spanReceiverExecutor.running, value=1
2019-09-19 09:47:33 INFO
type=GAUGE, name=statReceiverExecutor.completed, value=31669869
2019-09-19 09:47:33 INFO
type=GAUGE, name=statReceiverExecutor.running, value=0
2019-09-19 09:47:33 INFO
type=METER, name=baseDataReceiverWorker.rejected, count=42321,
mean_rate=0.00435581412757024, m1=2.976463198511169E-296,
m5=9.370859266954124E-60, m15=1.0654063518313215E-20,
rate_unit=events/second
2019-09-19 09:47:33 INFO
type=METER, name=baseDataReceiverWorker.submitted, count=11221601,
mean_rate=1.15496345024355, m1=2.3776013086568084, m5=2.542931646440672,
m15=2.7470087189167187, rate_unit=events/second
2019-09-19 09:47:33 INFO
type=METER, name=spanReceiverExecutor.rejected, count=2930904,
mean_rate=0.30165811563634404, m1=2.964393875E-314,
m5=1.9992100035748813E-96, m15=2.1673772847022338E-32,
rate_unit=events/second
2019-09-19 09:47:33 INFO
type=METER, name=spanReceiverExecutor.submitted, count=30076855472,
mean_rate=3095.607207180676, m1=7839.423560305877, m5=7830.869193546291,
m15=7748.639417002164, rate_unit=events/second
2019-09-19 09:47:33 INFO
type=METER, name=statReceiverExecutor.rejected, count=0, mean_rate=0.0,
m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second
2019-09-19 09:47:33 INFO
type=METER, name=statReceiverExecutor.submitted, count=31669869,
mean_rate=3.259565351245565, m1=3.6904650538019395, m5=3.69895171446854,
m15=3.6991573875655623, rate_unit=events/second
2019-09-19 09:47:33 INFO
type=TIMER, name=baseDataReceiverWorker.dispatchDuration, count=11179280,
min=0.009679, max=0.735414, mean=0.02416030195164621,
stddev=0.020356990714111612, median=0.018625, p75=0.025426999999999998,
p95=0.048561, p98=0.094165, p99=0.110413, p999=0.258808,
mean_rate=1.1506076363586757, m1=2.377601098787431, m5=2.542909892350519,
m15=2.7469950118916584, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:47:33 INFO
type=TIMER, name=baseDataReceiverWorker.duration, count=11179280,
min=0.795057, max=1268.4895549999999, mean=20.717214700421867,
stddev=73.20644415944214, median=1.5182, p75=2.286883, p95=152.151525,
p98=289.552353, p99=385.096031, p999=718.4056469999999,
mean_rate=1.1506076363159354, m1=2.37778810486036, m5=2.5431092624912064,
m15=2.747084867245342, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:47:33 INFO
type=TIMER, name=spanReceiverExecutor.dispatchDuration, count=30073924572,
min=0.0015019999999999999, max=12.197218999999999, mean=0.2626153562514069,
stddev=0.8546814749398955, median=0.026806999999999997,
p75=0.11270799999999999, p95=1.251806, p98=2.817868, p99=3.744869,
p999=12.197218999999999, mean_rate=3095.305548984131, m1=7839.441796719689,
m5=7830.873155603057, m15=7748.641163355057, rate_unit=events/second,
duration_unit=milliseconds
2019-09-19 09:47:33 INFO
type=TIMER, name=spanReceiverExecutor.duration, count=30073924573,
min=0.021515, max=12.182765, mean=0.17769032691342937,
stddev=0.24723531294268158, median=0.08363899999999999,
p75=0.29773099999999997, p95=0.527272, p98=0.613831, p99=0.778117,
p999=1.0347309999999998, mean_rate=3095.305548949893, m1=7839.452884920552,
m5=7830.874550500013, m15=7748.640583594111, rate_unit=events/second,
duration_unit=milliseconds
2019-09-19 09:47:33 INFO
type=TIMER, name=statReceiverExecutor.dispatchDuration, count=31669869,
min=0.012031, max=1.140163, mean=0.04055246837494057,
stddev=0.08519580378081307, median=0.022067999999999997, p75=0.030428,
p95=0.092066, p98=0.22883399999999998, p99=0.521057, p999=0.754002,
mean_rate=3.2595653504228284, m1=3.6904650538019395, m5=3.69895171446854,
m15=3.6991573875655623, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:47:33 INFO
type=TIMER, name=statReceiverExecutor.duration, count=31669869,
min=0.420214, max=36.579302, mean=0.9946613991580979,
stddev=0.46631819400778773, median=0.875382, p75=1.1311579999999999,
p95=1.708048, p98=2.8960079999999997, p99=3.112419, p999=3.65469,
mean_rate=3.2595653502922617, m1=3.6904650538019395, m5=3.69895171446854,
m15=3.6991573875655623, rate_unit=events/second, duration_unit=milliseconds

2019-09-19 09:48:33 INFO
type=GAUGE, name=spanReceiverExecutor.running, value=1
2019-09-19 09:48:33 INFO
type=GAUGE, name=statReceiverExecutor.completed, value=31670091
2019-09-19 09:48:33 INFO
type=GAUGE, name=statReceiverExecutor.running, value=0
2019-09-19 09:48:33 INFO
type=METER, name=baseDataReceiverWorker.rejected, count=42321,
mean_rate=0.004355787214947416, m1=1.0949796181356535E-296,
m5=7.672210664621135E-60, m15=9.966950840352542E-21,
rate_unit=events/second
2019-09-19 09:48:33 INFO
type=METER, name=baseDataReceiverWorker.submitted, count=11221761,
mean_rate=1.1549727818558366, m1=2.594051586089391, m5=2.57738637145221,
m15=2.7461283882545757, rate_unit=events/second
2019-09-19 09:48:33 INFO
type=METER, name=spanReceiverExecutor.rejected, count=2930904,
mean_rate=0.30165625182541517, m1=2.964393875E-314,
m5=1.6368147117878973E-96, m15=2.0275965890378007E-32,
rate_unit=events/second
2019-09-19 09:48:33 INFO
type=METER, name=spanReceiverExecutor.submitted, count=30077338325,
mean_rate=3095.637777271001, m1=8006.179658721837, m5=7875.066542079965,
m15=7769.37552158343, rate_unit=events/second
2019-09-19 09:48:33 INFO
type=METER, name=statReceiverExecutor.rejected, count=0, mean_rate=0.0,
m1=0.0, m5=0.0, m15=0.0, rate_unit=events/second
2019-09-19 09:48:33 INFO
type=METER, name=statReceiverExecutor.submitted, count=31670091,
mean_rate=3.2595680606303863, m1=3.6911785458910784, m5=3.699000586111253,
m15=3.6991981923378674, rate_unit=events/second
2019-09-19 09:48:33 INFO
type=TIMER, name=baseDataReceiverWorker.dispatchDuration, count=11179440,
min=0.009679, max=0.735414, mean=0.029309764689053004,
stddev=0.03089054751338058, median=0.020787, p75=0.030549999999999997,
p95=0.057801, p98=0.119223, p99=0.180855, p999=0.30771499999999996,
mean_rate=1.1506169948205367, m1=2.594051508882762, m5=2.577368560709597,
m15=2.746115565236887, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:48:33 INFO
type=TIMER, name=baseDataReceiverWorker.duration, count=11179440,
min=0.795057, max=1268.4895549999999, mean=14.034306472270499,
stddev=56.96738982906958, median=1.6058839999999999, p75=2.189288,
p95=88.80629499999999, p98=209.443017, p99=312.462465,
p999=481.61555899999996, mean_rate=1.1506169947219056,
m1=2.594120304572367, m5=2.577531791175023, m15=2.7461996255479004,
rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:48:33 INFO
type=TIMER, name=spanReceiverExecutor.dispatchDuration, count=30074407452,
min=0.001175, max=6.924989999999999, mean=0.31293937725585746,
stddev=0.690692505270765, median=0.035649, p75=0.222432, p95=1.799928,
p98=3.0320929999999997, p99=3.5828819999999997, p999=4.918788999999999,
mean_rate=3095.336123345034, m1=8006.297740147163, m5=7875.075227607255,
m15=7769.37778053855, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:48:33 INFO
type=TIMER, name=spanReceiverExecutor.duration, count=30074407453,
min=0.021515, max=12.182765, mean=0.19469674355824393,
stddev=0.3082009506170936, median=0.083687, p75=0.287884, p95=0.604285,
p98=0.83734, p99=0.9434899999999999, p999=4.7342249999999995,
mean_rate=3095.3361231613458, m1=8006.312792655105, m5=7875.076980969128,
m15=7769.377310119569, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:48:33 INFO
type=TIMER, name=statReceiverExecutor.dispatchDuration, count=31670091,
min=0.011482, max=2.117073, mean=0.044241834458307386,
stddev=0.1388009204437695, median=0.024409999999999998, p75=0.034536,
p95=0.072575, p98=0.130912, p99=0.7516459999999999, p999=2.117073,
mean_rate=3.25956805912516, m1=3.6911785458910784, m5=3.699000586111253,
m15=3.6991981923378674, rate_unit=events/second, duration_unit=milliseconds
2019-09-19 09:48:33 INFO
type=TIMER, name=statReceiverExecutor.duration, count=31670091,
min=0.392704, max=36.579302, mean=1.1144871542766415,
stddev=1.4516553870700837, median=0.92679, p75=1.153092, p95=1.740113,
p98=2.8960079999999997, p99=3.333814, p999=22.414369999999998,
mean_rate=3.2595680588786866, m1=3.6911785458910784, m5=3.699000586111253,
m15=3.6991981923378674, rate_unit=events/second, duration_unit=milliseconds

collector rejected
in stat.log
name=spanReceiverExecutor.rejected, count=2930904,

collector rejected
in stat.log
name=spanReceiverExecutor.rejected, count=2930904,
Thank you for your answer.
Whether it indicates that collector.receiver.span.worker.queueSize need to be adjusted?
need to refer to the CPU and memory for parameter adjustment?

Every collectors's stat.log shows spanReceiverExecutor.rejected. If I increase the worker queuesize, whether the loader of hbase also be increased? @xunchangguo
Thanks.

Every collectors's stat.log shows spanReceiverExecutor.rejected. If I increase the worker queuesize, whether the loader of hbase also be increased?


Cant apt-get update and upgrade

I tried to install cups and update the whole system. Everytime it says the command failed because it does not have enough memory. I am using a 32 gb sd card (class 10) with a rpi 3b+ and there is literally nothing on it except the chillipi kiosk. What could be the issue here? and how to solve it?
please help !!!

Apparently, this problem goes away when you expand the filesystem using raspi-config. It needs to alocate more space to root.


Remove version: AppFlowy.AppFlowy version 0.6.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/AppFlowy-IO/AppFlowy/releases/download/v0.6.1/AppFlowy-0.6.1-windows-x86_64.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 910)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 886.)

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

Maybe this PR should be blocked by #159429? Since the issue can be resolved by correcting InstallerUrl instead of just removing it.

Close with reason: Duplicate of #159429;


📝🚧 Publish pre-release IG

This PR publishes a pre-release IG on https://ncpi-fhir.github.io/ncpi-fhir-ig/. This PR closes #19.

@bwalsh thanks for the feedback. Yes, I agree that checking in all of the generated outputs in the main branch wouldn't be ideal. This PR is an interim solution putting the IG under main's /docs. Once we get ready to deploy official releases, all the generated files will be put to a gh-pages branch.


Anass Abbar: UX/PUI, 2 weeks

I Need Help With:
How to fork but still working on it
What went well?
All good
What went less well?
Kind of hard to understand some stuff
Lessons Learned
What is UX and UI
Sunday Prep Work
Still in Progress

UX/UI DESING
WEEK2
I Need Help With:
Ideas because I'm bad at design
What went well?
I can not naswer because i was busy and did not have any progress yet
What went less well?
using figma
Lessons Learned
Figma


error: target not found

phyOS-repo is up to date
error: target not found: phyOS-dwm
error: target not found: phyOS-dunst
error: target not found: phyOS-dwmblocks
error: target not found: phyOS-st
error: target not found: phyOS-fonts
error: target not found: phyOS-dmenu
error: target not found: phyOS-xmenu
error: target not found: lf

Database is online and running. Can you try again? Also it is only available in pacman.


Allow update of CP4D license

After an installation of CP4D 4.6.4 using the deployer, we found that the License Service was reporting usage of "IBM Cloud Pak for Data", whereas the customer has purchased "IBM Cloud Pak for Data Enterprise Edition."
To correct this, we used the following command to update the license:
cpd-cli manage apply-entitlement \
--cpd_instance_ns=${PROJECT_CPD_INSTANCE} \
--entitlement=cpd-enterprise \
--production=false

This command is documented here: https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=manage-apply-entitlement
The CPFS License Service is documented here: https://www.ibm.com/docs/en/cpfs?topic=license-service
After this command was run, the License Server output started to correctly show usage of "IBM Cloud Pak for Data Enterprise Edition."
The request is that cp-deployer allow us to set the type of license (cpd-enterprise or cpd-standard) and whether it's a production license (true or false).
The alternative is to run the cpd-cli command after cp-deployer has completed, in order to update the license.

Implemented change. License status page now shows:


Fix test cases

Describe your changes
Typo in test cases
Issue ticket number and link
closes #109
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
see 1 file with indirect coverage changes


Adopt Terms to IEC63278-1:2023 + bugfix DeleteBulk etc.

Adoption of Terms and Definitions to IEC63278-1:2023. See changelog for changed terms.
Minor changes w.r.t. abbreviations.
Bugfix DeleteBulk Operation
Change Log structured and content added
fixed mentioning of V3.0 with V3.1
Profiles: AAS Bulk Operation (title and names fixed)
updated Annex UML Tables (same as in Part 1)
Formatting issues in profile and parameter files fixed.
Editorial changes

@BirgitBoss please have a look at my suggested change above. Rest looks fine.


Unable to build under windows - error at test:bin task

Cloned handlebars.js repository under windows 10 64bit, node 4.2.1
Installed dependencies npm install
Ran grunt. Initially there was an error in jison. After changing the eol of handlebars.I to unix it worked.
Again ran grunt
Got the following error:
Running "test:bin" task
Fatal error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "./bin/handlebars -a spec/artifacts/empty.handlebars"
To run ./bin/handlebars file under windows is necessary to execute node ./bin/handlebars

I don't have a windows box to test on, but if you submit a PR that fixes that issue, glad to accept.

Test with AppVeyor CI.

Done in https://github.com/wycats/handlebars.js/pull/1244
There still a issue with istanbul i could not find how to fix

#1346 should fix this

Hi updated and still getting an error:
Running "test:cov" task
D:\repositories\handlebars.js\node_modules\.bin\istanbul:2
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")
          ^^^^^^^
SyntaxError: missing ) after argument list
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3
Fatal error: 1 tests failed

There's a istanbul.cmd file in .bin folder but is executing the istanbul bash script instead file.
I change to call istanbul.cmd but gives another error:
D:\repositories\handlebars.js\node_modules\.bin\istanbul.cmd:1
(function (exports, require, module, __filename, __dirname) { @IF EXIST "%~dp0\n
ode.exe" (

Since fork is for a node.js module i tried spawn also without luck
Using node 6.9.1, windows 10

Have you tried what you wrote and then notice that the PR was not merged yet? Or did the PR-commit not work either?
I have merged the PR now, so maybe you could try again.

The mentioned issues were before merging. I tried the PR but got eslint errors. Will try after the merge

I manually applied the changes to master branch and worked fine. I can do a PR if necessary.
The 4.x build failed with an error in jison but this is another issue

I thought I pushed the merge to master already. No need to do a PR. I regularly merge from 4.x to master.
Is the jison error related to line endings? May there need to be more entries in .gitattributes
Am 14. Mai 2017 17:41:16 MESZ schrieb "Luiz Américo"<EMAIL_ADDRESS>
I manually applied the changes to master branch and worked fine. I can
do a PR if necessary.
The 4.x build failed with an error in jison but this is another issue
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/wycats/handlebars.js/issues/1233#issuecomment-301320948

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Is the jison error related to line endings?

No:
Running "parser" task
D:\repositories\handlebars.js\node_modules\jison\lib\jison\util\lex-parser.js:13
3
    throw new Error(str);
    ^

Error: Parse error on line 2:
function strip(raw
---------------------^
Expecting '%%', 'ACTION', 'NAME', 'START_INC', 'START_EXC', 'START_COND', got '{
'

@blikblum After changing the eol of handlebars.I to unix it worked. (That is what you found out about a year ago. A year can be a very long time, I know that.)
I have added a .gitattributes-entry to fix that on Windows. Deletion and `git reset --hard' may be necessary to apply the changed line-endings.

About the original issue: It still exists, but I'll integrate your suggestion, maybe slightly different, because on Linux it would still be good to call the script without the "node "-prefix

I have created b

Released in 4.0.11