Update README.md

Update composer require argument to match packagist.org account name :)

Thanks!
I've forgotten to change the package name in Packagist. I will to remove the package and publish with the correct name because I want to maintain the same vendor name as my GitHub account.

Thanks for making this by the way! Saved me a tonne of time and sanity in trying to clean up the original token generation file.

Actually, the package can be installed using composer require matricali/akamai-auth-token.
I've created a release (tag:1.0.0) so you can use this as a Composer dependancy without changing the "minimum-stability" in your project's composer.json.
Feel free to send me another PR if you consider any change as an improvement.


Is there an "whenblockedusermessage" function?

Is there any one?

There isn't one at this moment in time.

Please add it


Research K8s Cluster Creation

Seems the quickest way to start a cluster with the fewest effort executing is via Terraform.
References

https://cloud.google.com/kubernetes-engine/docs/quickstarts/create-cluster-using-terraform
https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/container_cluster#example-usage---with-a-separately-managed-node-pool-recommended

Tasks

Access the above resource and summarize its contents

Will likely require individual Terraform modules for the Kubernetes resources in both GCP / AWS.


does "getElementsByTagName" work in backround

if not investigate iFrame version together with @BrueckmannM

Following https://developer.mozilla.org/en-US/Add-ons/WebExtensions/manifest.json/permissions this it will not be possible to apply our script unless we request permission for *.
> Host permissions

Host permissions are specified as match patterns, and each pattern identifies a group of URLs for which the extension is requesting extra privileges.
The extra privileges include:
XHR access to those origins
the ability to inject scripts programmatically (using tabs.executeScript) into pages served from those origins
the ability to receive events from the webRequest API for these hosts
the ability to access cookies for that host using the cookies API, as long as the "cookies" API permission is also included.

to be continued in #13 - needs to investigate if using an internal page in our tab with an iframe would be sufficient permission or whether we escalate our addon permissions and allow full access to all tabs.


perf(vote_mgr): retrieve votes from db on launch from separate thread

Purpose
Right now if a node has been stalled or partitioned for a while, upon restart it will block pbft manager consensus while vote manage retrieves votes from the db.   Instead we can asynchronously retrieve the votes and populate them into the vote manager.

prnet cleaned-up successfully


Update Index.js with optimized code.

Description :
Code cleaning and optimization.
Please ensure Checkmark the following :

[x] - Tested Localy
[x] - Checked in IE11 and Firefox
[x] - Checked in mobile
[ ] - Backend work
[x] - Frontend work
[ ] - Bug Fixes
[x] - Enhancements

@Ishaan28malik Thank you for your contribution. It seems that it is meaningless to use ternary operators instead, so close the issue.


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1655 ms

Resolved: Bofrost.lu performance has improved in d47a70b after 22 minutes.


localhost https out of the box

Describe the bug
It is not possible to use https when starting BaGet with the default localhost config (5000 -> http, 5001 -> https) and trying to push a package through https:
error:   The SSL connection could not be established, see inner exception.
error:   The remote certificate is invalid according to the validation procedure.
To Reproduce
Steps to reproduce the behavior:

Using this version of BaGet 'v0.3.0-preview2'
Run this code

dotnet BaGet.dll
dotnet nuget push -s https://localhost:5001/v3/index.json <trywithanypackage>.nupkg

With this config

{
  "ApiKey": "",
  "PackageDeletionBehavior": "Unlist",
  "AllowPackageOverwrites": false,

  "Database": {
    "Type": "Sqlite",
    "ConnectionString": "Data Source=baget.db"
  },

  "Storage": {
    "Type": "FileSystem",
    "Path": ""
  },

  "Search": {
    "Type": "Database"
  },

  "Mirror": {
    "Enabled": true,
    "PackageSource": "https://api.nuget.org/v3/index.json"
  },

  "Logging": {
    "IncludeScopes": false,
    "Debug": {
      "LogLevel": {
        "Default": "Warning"
      }
    },
    "Console": {
      "LogLevel": {
        "Microsoft.Hosting.Lifetime": "Information",
        "Default": "Warning"
      }
    }
  }
}

See error

error:   The SSL connection could not be established, see inner exception.
error:   The remote certificate is invalid according to the validation procedure.
The serviceindex could also not be loaded, this is the first output (I did not pasted it here, is in german language on my pc).
Expected behavior
1.) At least a localhost certificate should be there to get https working out of the box or 2.) a description how to add one / get https working (e.g. from a free certification site like https://letsencrypt.org or self-signed pfx with a local openssl. For sure, a domain name can't be there out of the box but for a development on the localhost pc this would be nice. ;-)
If (for security reasons for example) no localhost cert is provided, then 2nd option would be nice.

When starting there is printed that a development certificate is used. How to make Visual Studio and Browser make accept that?


[Bug]: PuppeteerNewTab automatically close tab

Version of the software
0.1.21
Operating system
Windows 10 x64
Browser
Chrome 92.0.4515.107 (Official Build) (64-bit)
What happened?
A bug happened! PuppeteerNewTab got problem, it automatically close my current tab and open a new page.
Relevant LoliCode if needed
No response

Can someone address this?

I am on vacation, I will try to check it out once I'm back

I am on vacation, I will try to check it out once I'm back

All good, enjoy your vacation Ruri :)


WIP - Setup visual regression testing

** This is still a work in progress pull request. Not ready yet for merge **
I've pushed what I have managed to do this month's slot on this topic, namely:

Setup PhantomCSS for visual regression tests
Configure it according to our needs
Write initial example tests for atoms and molecules
Add common utils to avoid repetition on test specs

To be done on next month's cycle:

Solve the problem with demo's left menu overlapping tested components on screenshots on mobile size viewport.

I tried both clicks on the toggle and removal of the related class in the HTML element but couldn't make it work yet.

Try to centralize some more common functionality regarding the CasperJS tests execution skeleton to avoid repetition.
Document how the setup works for other developers
Integrate --rebase option to NPM scripts to allow baseline images generation when a change is expected.
Ask other collaborator to write a couple of tests to try to find possible areas for improvement on the current setup

:-1:

I've made a big progress on this topic but I still have to finalise it in the next iteration.
Current setup is:
npm run test / yarn test triggers a runner (runner.js) script which forks two different processes which communicate with each other:

An express server (server.js) which serves all the pages under docs/demo/materials/03-atoms

[ ] Need to extend it to also add molecules here

When up and running a CasperJS job is started to run all tests (suites.js) and take screenshots.
Suites are automated and we should be able to cover basic tests for all components
Tests depending on actions like clicks, hovering and so on will have to be investigated further.

Feel free to take a look and leave your opinions @rbarilani @sambhav-gore
On the next iteration, I'll take care of doing some adjustments, document how to use it and squash all commits and hopefully finish this.

:-1:

👍 I think this is a great progress @dami-gg! awesome!

Closed in favor of #412


feat: include libraries when publishing

What I did
fixes: #43
Fixes: APE-324
Allows libraries when publishing.
Mostly just wanted to make sure https://github.com/ApeWorX/ape-solidity/pull/89 didn't break publishing.
I haven't really tested this yet so leaving it in draft until I have more time. Should work though....
Requires ape 0.6.3 and ape-solidity 0.6.1 though.
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

See https://github.com/ApeWorX/ape-etherscan/pull/74


Python: Support OpenAI Assistants

Motivation and Context
OpenAI released new functionality and APIs related to assistants. SK Python was lacking this functionality.

Description
This PR brings in the ability to create an OpenAI ChatCompletion assistant, specify the assistant's instructions and either simply call the API or additionally configure functions that run alongside the assistant.
This change will start out as a draft to allow the community to review/comment. There are some comments/todos:

As part of #4097, there is a large revamp to simplify/improve how the AI requests settings are configured. Once this PR goes in, it will simplify a bit of code related to transforming tools (previously called functions) when calling the assistants API. This PR also removes the method complete_chat_with_functions_async. This would need to be updated in this current code once that PR goes in.
Even if the user passes in one function to the assistants API, it may return multiple required tool calls. There were adjustments made to run the required function for the amount of tool calls that are required as the assistants API requires the same number of tool call outputs when re-submitting on the current run.
The assistants ChatCompletion returns a list of tuples of (Completion, FunctionCall). This is different than the complete_chat_async that only returns a Completion. We should align on how we want to support these return types.
There some new kernel examples showing how the assistant code works. I have yet to do a notebook.
Need to write some more integration tests that use specific tools to make sure we have code coverage.
Todo: support handling files with assistants

Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Closing this PR as this work will be re-introduced after we make it to a beta SK python version.


Osmosis Chain adapter to Parity w/ Cosmos for transfers

TX history and sends

@elmutt - can you comment of this ticket on the status?

closed in grooming as per @elmutt this is done


feat(use-presence): allow use-presence to be driven by arbitrary data

The purpose of this change is to solve another challenging problem with presence animations within the already available hook which, in my opinion, makes it even more useful!
With this change, usePresence can take an argument of arbitrary type, and it will manage a staggered state of that argument. This allows the hook to function as it always did with boolean values, but if it receives another type then it will manage the render state based upon if the value is truthy or not+1. However, if the state changes between two truthy values, then the added change will ensure that the original data continues to persist until the element has transitioned out, at which point the element will transition back in with the new data without ever unmounting.
Here is a StackBlitz example showing a simple use-case for the new version of the hook alongside the old behavior working as expected.

If you're interested in having this change, then just let me know and I'll add the new use-cases to the docs. If this is not a change you're interested in, I might just make a wrapper package around yours.
+1 I've also considered accepting a custom function which can evaluate truthiness in case you have a data type like number and you want 0 to be truthy. If you think this is important I can also add that.

Hey, thanks a lot for sharing your idea—I think that's certainly interesting!
The use case would be to have an array of items where only one of them is visible at a time, right? E.g. a tab navigation where the content is animated.
Maybe it would make sense to implement it as a wrapper hook indeed? We could still export it from this package if you like:
import {useItemPresence} from 'use-presence';

The intention here would be to keep the size of the original usePresence hook. There are very capable animation libraries for React (like framer-motion) and I think the sweet spot of use-presence are really the simple use cases where bundle size matters, therefore I'd like to keep optimizing for that. Also keeping the isVisible: boolean argument for documentation purposes is helpful IMO.
Out of curiosity: How did you learn about the use-presence package? 🙂

Hey @amannn, your assumption about the use case is exactly right! If you have an array/record/map where you want to be able to swap the data in & out arbitrarily and see the old data maintained while a component displaying it animates out and then update the data to whatever the latest is to animate a new piece of data back in.
I think there's a valid take that this would make more sense as a wrapper hook. That's how I originally implemented it in my use-case and it works well. Adding the lag-data state also forces a few more renders to fire. It's never been a problem in my use-cases, but I can see why you wouldn't want to make your users have to deal with that if they don't need it. I've updated the PR to create and export a separate hook. If you like this as it is, then just let me know and I'll write up the documentation!
And I found use-presence because it was exactly what I was looking for 🎉 I wanted AnimatePresence from framer-motion but without the weight of framer-motion. The savings from use-presence is substantial: use-presence & React bundles to a 2.89KB GZIP bundle, whereas just trying to grab AnimatePresence from framer-motion & React bundles to a 47.45KB GZIP bundle. That's a 94% size reduction for features that I never needed 😅

Little extra update: because the wrapper hook is using the type of the options from the base hook, I just separated out the types for each of their options argument. That way if the options type for usePresence changes in the future, the type for useUniqueDataPresence will be updated automatically.
I also exported both of these types. I did this because when I used this hook in my project, I had a transitionDuration that I used everywhere. So within my own project, I created my own wrapper hook that looked like this:
import usePresenceBase from "use-presence";

export const usePresence = (
  isVisible: boolean,
  options: Parameters<typeof usePresenceBase>[1] = { transitionDuration: 150 }
) => usePresence(isVisible, options);

But once the types are exported I can use UsePresenceOptions as opposed to Parameters<typeof usePresenceBase>[1]

Updated StackBlitz with latest code!

@amannn I've responded now to all inline comments. For everything that I went exactly along with, there's a 👍 and for the one comment that I went slightly off script there's a ℹ .
Let me know what you think at this point and if you like where the code has ended up and you feel that it's well tested then I will add some documentation for the new hook!

@amannn Responded to all comments in agreement (👍) and updated!
Added docs in the commit after, writing is not my strong suit so just let me know what you think!

Thanks a lot, looks great! 👏
Thanks also for drafting a section for the docs! Would you mind if I try to rephrase it a bit?

@amannn you absolutely may rephrase it. I don't know if you want to just to inline recommendations in the PR and I can commit it. Or if you want to commit it to my fork, I just added you as a contributor, and I have allowing edits from maintainers checked off.

Great, thanks! I've created a PR to propose my changes: https://github.com/EthanStandel/amannn-react-hooks/pull/1

@amannn  I left a couple comments on that, but did approve it for the record. You should be good to merge at any time. Once you do, then I assume you'll be ready to merge this PR. I'll leave this one as is unless I hear any other feedback from you 👍

Released in<EMAIL_ADDRESS>you so much for your work and the great collaboration! 👏


Can't find libunrar or the rar command on Linux

Running Arch Linux.  I run comictagger.py from the command line and it launches but says the rar support is disabled because it can't find libunrar.so.  I go into the preferences and confirm the path to libunrar.so and rar are set correctly.  Hit OK.  Quit out of the app and go back in, and it still tells me if can't find RAR.  Using latest source files for 1.1.30 rc.  I pulled down the Mac version, since MacOS is UNIX.

Nevermind.  Needed to install the unrar python module.
sudo pip install unrar
That fixed it.


Fixes to minideflate

Still not quite right for some reason.
Now minideflate it hangs forever during inflate.
Probably stuck in the loop instead of erroring out like before.

I wonder if I have to do while (d_stream.avail_in > 0);

Heh, good thing CI doesn't invoke that tool.

Uhm, it seems this is wrong actually.
According to documentation, windowbits should be:
-1 to -15 is raw deflate without header or trailer
0 to 15 is deflate wrapper (adler32)
16 to 31 is gzip wrapper (crc32c)
32 to 47 is wrapper auto-detect (but not raw deflate)
So, doesn't that mean that we were already doing deflate with adler32?
Also, perhaps minideflate should do decompress with 47 by default? (would need to be tested first of course)

@Dead2 it looks like you are correct about the window_bits. I've updated the help usage to reflect it. And for inflateInit by default it will auto-detect. That may have been the issue with the Z_BUF_ERROR that you were experiencing.
If you still get the Z_BUF_ERROR can you tell me which file you are testing against? I tried against silesia-small.tar and didn't get that error.

I see no reason why we shouldn't have -k parameter...

Yes I noticed there was no -k argument also, but that is because it doesn't automatically delete the input file.

I guess that should perhaps be made clear somehow then, because that differs from how minigzip and many other compression utils works :)

@nmoinvaz Did you do testing of the new features? If so, then LGTM.

I did test it while developing. I also tested that each extension was appended properly during compression and removed during decompression.


Unspecified descriptor mediatypes MUST be ignored

As per out discussions on the dev mailing list, this is the first step towards ensuring that storage and distribution of non-specified content can be experimented with while maintaining a standards-compliant registry.
cc @stevvooe

Rejected (for now -- see my proposed wording to see what my concerns are).

Rejected? Based on what? Your conclusion is weird.
Are you requesting changes or outright rejecting this?

I'm not a fan of MUST be ignored. They MUST be safe to ignore though

@cyphar Let's see a suggested wording that helps with the intent, rather than issuing a rejection. The interpretation of "unspecified" does include OCI. That is up to the interpreter. If someone has specified it elsewhere and they don't ignore it, then they are compliant. This is to prevent implementations from rejecting mediatypes from one vendor or another.
What if it was qualified like this:
An encountered `mediaType` that is unknown to the implementation but unspecified by OCI MUST be ignored.

I'm not a fan of MUST be ignored. They MUST be safe to ignore though

This is very odd language. How can we make a strong statement about safety?
We need strong language to ensure that future mediaTypes can be added without causing issues with backwards compatibility.

@stevvooe

An encountered mediaType that is unknown to the implementation but unspecified by OCI MUST be ignored.

That seems far more reasonable to me (and I agree with it).

Let's see a suggested wording that helps with the intent, rather than issuing a rejection.

I explained my concerns and provided suggested wording in this comment -- maybe you didn't see it?
The main objection I have is that the currently-proposed wording (at least to me) seems to disallow mediaTypes that are known to the implementation but are unspecified in the spec -- obviously this is not what any of us wants (which is why I'm against the patch). Of course, I do think that making out-of-spec mediaTypes no longer potentially subject to being broken is a good thing.
I would be fine with:

An encountered mediaType that is unknown to the implementation MUST be ignored.

or your suggested text.

I moved forward with Aleksa's final wording because I'd rather have the intentions clear than be technically correct.
PTAL

LGTM, thanks @jzelinskie. I'm not sure what's up with the CI failure.


fix: add test router.back & router.forward

what do you mean?

what do you mean?

Looking forward to participation and collaboration, but no clue what to write, so try

I'm sorry but I don't understand what you are trying to add 😓


[xxhash] Update to 0.8.1

Update the xxhash port from 0.8.0 to 0.8.1.
Changelog : https://github.com/Cyan4973/xxHash/releases/tag/v0.8.1

Thanks for both the update and the modernization!


Model run should be able to limit stages to run

Starting a model from a named stage needs to work.
Also have some "limit" on how many additional stages to run (see separate issue on stopping for error, however). This stop should be forced even if the stage runs correctly.
More work on limiting stages: #5

Working with fixes on issue #11


enable PROV_CERT in sidecar.env by default

to reduce manual work for users, let's set PROV_CERT=/etc/certs by default to make situations like https://github.com/istio/istio/issues/22665 more smooth.

@irisdingbj: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-local-tests_istio
c05d822fde1ec4990b1356ac97a593fabdab7e8b
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

This doesn't seem like the right fix. Is sidecar.env supposed to override
existing environment variables? It seems like if that is the case we are
putting this in the wrong space, but I would need to take a closer look at
the full flow - it just seems a bit off to me currently. We set defaults
for Discovery address as well and do not need this
On Thu, Apr 9, 2020, 7:09 PM Iris<EMAIL_ADDRESS>wrote:

@irisdingbj commented on this pull request.
In pkg/test/echo/docker/Dockerfile.app_sidecar
https://github.com/istio/istio/pull/22827#discussion_r406569344:

@@ -9,6 +9,7 @@ COPY certs/default/*                  /var/run/secrets/istio/

Install the sidecar components
COPY istio-sidecar.deb  /tmp/istio-sidecar.deb
RUN dpkg -i /tmp/istio-sidecar.deb && rm /tmp/istio-sidecar.deb
+RUN sed -i "s/PROV_CERT=/#PROV_CERT=/g" /var/lib/istio/envoy/sidecar.env
Because the setting in sidecar.env will override env var we set in
https://github.com/istio/istio/blob/master/pkg/test/framework/components/echo/docker/workload.go
.
So we need to make sure we do not specify PROV_CERT for local testing
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/22827#discussion_r406569344, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMRI5V7YUS3MXYO6J3RLZ5T3ANCNFSM4MEMGMMA
.

Why do we rotate the prov cert? I thought we want to just rotate the
returned workload certs which have a low ttl but the prov cert has a high
ttl
On Thu, Apr 9, 2020, 7:10 PM Iris<EMAIL_ADDRESS>wrote:

@irisdingbj commented on this pull request.
In tools/packaging/common/sidecar.env
https://github.com/istio/istio/pull/22827#discussion_r406569623:

@@ -85,7 +85,7 @@

Location of provisioning certificates. VM provisioning tools must generate a certificate with
the expected SAN. Istio-agent will use it to connect to istiod and get fresh certificates.
-#PROV_CERT=/var/run/secrets/istio
Now with #PROV_CERT=/var/run/secrets/istio , it means user must put
related certs
under '/var/run/secrets/istio` and the auto cert rotation will not happen
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/22827#discussion_r406569623, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXOZGXT4IYZUNRRNZW3RLZ5YFANCNFSM4MEMGMMA
.

@howardjohn
` If the value is different from PROV_CERTS the workload certs will be saved, but
the provisioning cert will remain under control of the VM provisioning tools.`
See comments from sidecar.env
We use certs from PROV_CERTS to create connection.
regarding the test changes , it is because we run echo-start.sh after we setting the env var in workload.go

Hi,
Just info on this, if you set PROV_CERTS=/etc/certs as well as OUTPUT_CERTS=/etc/certs the istiod service is still failing with the error mentioned in #22665. It seems more like a bug,  than a plain config  issue (or sidecar.env gets ignored or overridden)

Hi,
Just some info on this:
If you set PROV_CERTS=/etc/certs as well as OUTPUT_CERTS=/etc/certs the istiod service is still failing with the error mentioned in #22665. It seems more like a bug, than a plain config issue (or sidecar.env gets ignored or overridden). So this PR is maybe not addressing the root cause.

The problem in  #22665 is because the setting in current dep package will override your changes in sidecar.env.  THis is why want to change the default value.

@howardjohn PTAL, Thanks!

cc @sdake

@irisdingbj, are those the only changes regarding the issue?


PostProcessStage not work correctly

What happened?
I want to obtain the coverage of the viewing volume from a specific camera angle through the post-processing stage. For example, the shader code MainMAX is a transformation matrix from the screen coordinate system to the camera's 0-1 coordinate system
My code works normally in the old version, but there are problems after updating to the latest version
But this will not get the correct result, or it can only be shown in some angles
``
uniform float myNear;
uniform float myFar;
uniform float mylog2FarPlusOne;
uniform float z_offset;
uniform sampler2D colorTexture;
uniform sampler2D depthTexture;
uniform sampler2D CameraDepthTexture;
in vec2 v_textureCoordinates;
uniform sampler2D videoTexture;
uniform mat4 viewport_w;
uniform mat4 MainMAX;
float my_reverseLogDepth(float logZ)
{
    float near = myNear;
    float far = myFar;
    logZ = pow(2.0, logZ * mylog2FarPlusOne) - 1.0;
    logZ = far * (1.0 - near / logZ) / (far - near);
    return logZ;
}

void main() {
    vec2  MainDepth=vec2(gl_FragCoord.x/viewport_w[0][2],gl_FragCoord.y/viewport_w[0][3]);
    float MainDepth1=czm_unpackDepth(texture(depthTexture, MainDepth.xy));
    float MainDepth2= czm_reverseLogDepth(MainDepth1);
    vec4 MainInfo1=vec4(v_textureCoordinates.x*2.0-1.0,v_textureCoordinates.y*2.0-1.0,MainDepth2*2.0-1.0,1.0);
    vec4 MainInfo7=MainMAX*MainInfo1;
    vec4 BaseColor = texture(colorTexture,v_textureCoordinates);
    MainInfo7 = MainInfo7/MainInfo7.w;
    if(MainInfo7.w+0.0005>0.0&&MainInfo7.x+0.0005>= 0.0&&MainInfo7.x-0.005<=MainInfo7.w&&MainInfo7.y-0.005<=MainInfo7.w&&MainInfo7.y+0.005>=0.0&&MainInfo7.z+0.0001<=MainInfo7.w&&MainInfo7.z+0.005>=0.0){
        out_FragColor =vec4(1.0,1.0,1.0,1.0);
    }
    else{
        out_FragColor =BaseColor;
    }
}

But strangely, when I add an entity, it works normally again. Why is that?
addXYZ(videocamera)
{
      let position=new Cesium.Cartesian3();
      position.x=videocamera.CameraPos.x;
      position.y=videocamera.CameraPos.y;
      position.z=10000;
      let  hprRollZero = new Cesium.HeadingPitchRoll(); //不做欧拉角旋转
      let convert=Cesium.Transforms.eastNorthUpToFixedFrame;
      let modelmatrix=Cesium.Transforms.headingPitchRollToFixedFrame(position,hprRollZero,Cesium.Ellipsoid.WGS84, convert);
      let BiaoDingCoordinate=new Cesium.DebugModelMatrixPrimitive({

          modelMatrix : modelmatrix,
        //  length : 100.0,
          width : 0.000001
      });
      viewer.scene.primitives.add(BiaoDingCoordinate);
}

Reproduction steps

...
Sandcastle example
No response
Environment
Browser:
CesiumJS Version:1.115
Operating System:

Thanks for the report @Pure0319.

My code works normally in the old version, but there are problems after updating to the latest version

Can you please provide the specific version numbers this is working in and not working in?

Thanks for the report @Pure0319.

My code works normally in the old version, but there are problems after updating to the latest version

Can you please provide the specific version numbers this is working in and not working in?
The old version is 1.58 very old work in
but 1.115 not work

# @ggetz
The old version is 1.58 very old version but work
1.115 not work

@ggetz
The old version is 1.58 very old version but work
1.115 not work

I guess there is a problem in executeCopyDepth step ，so i can not get right depth in my shader

Thanks @Pure0319. This is likely related to https://github.com/CesiumGS/cesium/issues/11067.
I'm going to go ahead and close this issue in favor of #11067 to keep discussion in one place.


Create basic Dependabot configuration

What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain: Configure Dependabot so that you have a working dependency bot.
What changes did you make? (Give an overview)

Create a basic Dependabot config.

Which issue (if any) does this pull request address?
Closes #1550
Is there anything you'd like reviewers to focus on?
I'm marking this as a draft, because I still need some answers to configure this to your liking:

How often do you want Dependabot to check for updates? Each working day, each week, each month?
Do you want Dependabot to run at a certain time of day, at 8 o'clock in the morning your time for example?
Do you want Dependabot to assign somebody to the pull request?
Do you want Dependabot to request a review from somebody?
Do you want a specific commit message format?
Do you want Dependabot to use a specific label, like dependabot or dependencies for example?
What version strategy do you want to use? Increase the version requirements, or widening the range of versions? versioning strategy docs Dependabot.

References:
Official GitHub Dependabot configuration options documentation

Daily is fine
No specific time
Don't assign to anyone
Don't request a review
No particular commit format
You can apply the label dependency
The "increase" strategy looks good

And my question for you?

Is there a way to apply this configuration to the whole standard GitHub organization?

Is there a way to apply this configuration to the whole standard GitHub organization?
There is no setting in Dependabot, that I know of, to source a config file from a separate repository like dependabot-config-repository. I think you can use Git Submodules to cobble something together, but this would only work if the wanted config is exactly the same across repositories.
See ProGit2 book, chapter 7.11 Git Tools - Submodules to see how that would work. I don't think this is easier to use than just using a separate config for each repository though. I think a Git submodule adds more complexity for little benefit.
If this is something that you really want, I can help you with a Renovate config instead. With Renovate you can create a base config in a separate repo that other repositories then extend from.

@feross I answered your question, take a look at the post above this one. :wink:

@feross You might want to remove the stale branches that are left over from the old Greenkeeper bot: https://github.com/standard/standard/branches/stale

@HonkingGoose Thanks for the suggestion – fixed!

Cheers! :smile:


Missing d3d9.lib exports

As described here, d3d9.lib exports for Direct3DCreate9On12 and others are missing.
I can confirm this issue on windows version 19041.208 (insider slow ring) on a v140 project using the 10.0.19041.0 target SDK version.
The exports exist in the d3d9.dll however and calling those functions can be achieved with a hack - basically using GetProcAddress to retrieve the exported function and calling it.

(Sorry for not responding for so long...)
I don't see this. I see Direct3DCreate9On12 exported from d3d9.lib in the 10.0.19041.0 SDK, confirmed with link.exe /dump /headers "C:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x64\d3d9.lib":
  Version      : 0
  Machine      : 8664 (x64)
  TimeDateStamp: F5D00EF8
  SizeOfData   : 0000001D
  DLL name     : d3d9.dll
  Symbol name  : Direct3DCreate9On12
  Type         : code
  Name type    : ordinal
  Ordinal      : 20


Rename "suspended" state to "semi-expired"

"Suspended" is, in non-Namecoin contexts, sometimes associated with censorship by a 3rd party rather than failure to renew on time.  "Semi-expired" avoids the risk that users will incorrectly infer that their name has been censored.
The criteria for the new state name were:

Intuitively conveys that the state is temporary, i.e. it will transition to "expired" or "confirmed".
Intuitively conveys that the name is unresolvable, like "expired".
Single word (hyphenated is fine) so that it avoids problems when used in JSON-RPC API's.
Adjective form of a past-tense verb (allows us to conjugate in parallel to "expired").
Intuitively conveys urgency, so that users won't ignore it.
Cannot easily be misconstrued as a reference to censorship.

Thanks to (in lexicographic order) Arthur Edelstein, Cyberia Computer Club, Cypherpunks, Cyphrs, Diego Salazar, s7r, Somewhat, and Yanmaani for helping find a better name for this state.
This PR also adds better contextual feedback on the semi-expired state, as per a suggestion from Diego.  It also fixes some i18n bugs that I noticed while implementing this PR.

@yanmaani @somewhatnmc Feel free to review.

@JeremyRand remove all "suspension" what you added to Electrum NMC. Your renaming from suspension to semi-expired in this pull request doesn't change the fact that the domain names stop resolving before expiration!
You had a chance to read and address all issues raised in the comments under https://github.com/namecoin/electrum-nmc/pull/297 but you instead renamed suspension.
You have to remove all what you introduced with https://github.com/namecoin/electrum-nmc/pull/297 which is clearly censorship. No domain should stop resolving before the 36000th block! Period.

Received an ACK from @somewhatnmc on #namecoin.   I'll merge if @yanmani ACKs, or in circa 2 days if he doesn't reply.
@mrpeertopeer I see you're flattering yourself, Zoltan.  This PR wasn't a response to your invalid rant or in any way intended to address your bogus criticism, it was a response to a valid concern raised by yanmaani circa 1-2 months ago.
You were given a chance to make your criticism heard some months before suspensions were merged, and your criticism was widely regarded as meritless by everyone who heard it.  This decision has been made (with the full agreement of Daniel); you are the only person who's unhappy with it; the decision is not being reversed; I don't want to see any more of your comments about this topic cluttering our issue tracker.

@JeremyRand you have stolen from the Namecoin project a few million dollars already, and on top of that, you asked for money from the European Union and the NLNet Foundation. Since you are involved in the Namecoin project, not only me but many others have also been attacked and bullied on all public channels, including now on GitHub.

You are using namecoin.org and the Namecoin Twitter feed as a personal blog, even now on GitHub. You are clearly doxxing because you can't provide a single reasonable response to the questions I posted or the issues I raised.
Apart from that, I have tried to contribute to this project multiple times and every time I have been attacked the same way you are attacking me now.
You destroyed the Namecoin project with your hostile actions, which resulted in Namecoin's price collapsing multiple times to less than a dollar.
Neither you, Jeremy Rand nor Daniel Kraft spent a single dollar on Namecoin's promotion. No press release, nothing.
We can also see on Wikipedia that you bully people with copyright and trademark threats regarding the Namecoin logo, which is clearly in the public domain. You have no right to the Namecoin logo, nor do you have the right to threaten Doxx or in any way attack those who are working with Namecoin.
Even though you listed @rllola on Namecoin.org, who has contributed absolutely nothing to Namecoin, as well as Theymos, who is a well-known criminal, he stole more than 11,000 Bitcoin from the Bitcoin community.
 As a member and long-time user of Namecoin, I have all the right to demand changes both in the software and in any other public resources that belong to the Namecoin project.

You and @yanmaani threatened me for more than three weeks to make you the founder of the #namecoin channel on Libera Chat, and when I asked you to give me the #namecoin channel on Freenode, you attacked me and gave the channel to @luke-jr, who has nothing to do with Namecoin.
@luke-jr claimed that he was a contributor to Namecoin while he never submitted a single pull request to any Namecoin repository. His claims are totally outrageous since he claims that he has the right to run the #namecoin channel on Freenode because he is a contributor to Bitcoin which is Namecoin's upstream. According to this logic, all open-source projects are under a significant threat since upstream contributors can claim to run and own channels or any other public resources related to forks.
I am going to sue you and Daniel Kraft if you do not reverse your commits to Namecoin NMC and do not immediately show public addresses on the blockchain where the Namecoin project's funds are. You are either going to be held accountable for the millions of dollars you embezzled or you will be jailed. It is that simple.
I also find it outrageous and unacceptable that Daniel Kraft describes himself as a "Chief Namecoin Scientist" and you claim to be a "Lead Application Engineer & Community Organizer." You're a disaster who has indeed contributed to Namecoin's clients, but none of your contributions have been significant. What kind of "community organizer" are you when you freak out on a pull request and start doxxing me when I post legitimate criticism which you brand "bogus?" What kind of community are you leading, Jeremy Rand? The 14 people on Libera Chat? Wow, man, congratulations.
Your recent tweet about merging Taproot into Namecoin is another significant threat to Namecoin.
And just to make it very clear, after that, I made you the founder of the #namecoin channel on Libera Chat, you gave op to @yanmaani, and I have been banned from the channel, so even if I wanted to, I wouldn't be able to oppose your pull request merging suspensions of domain names into Electrum NMC.
Stop pretending you're some kind of victim because you're not, and again, stop treating this project as yours because it is not. I even knew and had a long discussion with David, who was the person who mined the very first .bit domains because, as he said, @vinced hasn't had enough GPU power to do so.
In my opinion, you are an extremely toxic "community organizer" just as @luke-jr deemed toxic to the Bitcoin project by @gavinandresen. You and he are like twins, and it would be better for the Namecoin project without you.

Wow, very intelligent discussion on this PR for sure.
utACK 9f0fb4f. Though I think semi_expired_in would be slightly cleaner than semi_expires_in.

Everyone who registers .bit domains or other data on the Namecoin block chain knows that they should renew the domain before the 36000th block, or approximately every 6 months.
This pull request, on the other hand, directly censors, bans, and stops resolving domains after only the fifth month, which means that the domain owner must pay three times a year, rather than two,.
This is a serious assault on domain owners just like myself. Don't even think that I'm going to sit back and accept censorship on my domains; and don't even think that Electrum NMC after this will be added to ZeroNet or any of its forks by @rllola; that's not going to happen.
All domains must keep resolving until they expire. Any action or attempt to censor the domains before expiration is unacceptable.
@yanmaani keep your imagination to yourself.

Censorship is stopping resolving domains before expiration.

According to whom? What problems does this cause?

Don't interfere with domain name resolutions by stopping resolving domain names before their expiration date. At this point, I do not even see any reason why warning users is necessary. This pull request is not a warning since it stops resolving domain names.

@JeremyRand It should be fine.  Xaya doesn't have expiration at all, so all that code is not there anyway.  It might cause conflicts because you are changing deleted code in some places, but those are easy to resolve then.

Merged, thanks everyone who helped get semi-expiration into Electrum-NMC.  This unblocks the 4.0.0b1 release, and also unblocks important sponsored work.  \o/


Issue: Can we limit the number of relevant documents returned by AzureCognitiveSearchRetriever?

I need to limit the number of documents that  AzureCognitiveSearchRetriever returns so that I can aggregate only the most relevant documents. Is there a way to do this with the current functionality or do we need to implement it?

Hey, I wrote AzureCognitiveSearchRetriever. 👋🏼
Can you post your full code where you would need it? Is retriever.get_relevant_documents("what is langchain")[:n] not sufficient for your use case?

@UmerHA Do you have a sample on using the retriever?  I have tried calling the retriever but getting connection errors.
Also, what is the conten_key parameter?
retriever = AzureCognitiveSearchRetriever(content_key="content")
Thanks,
Marcelo

@UmerHA I was able to figure it out the parameter content_Key, however, I wanted to know if there is anyway to return the whole result so I can get the keys I need.  I my case, each result has 5 different keys.
Thanks

@UmerHA Please ignore as I was able to figure it out.  Retriever is working great!!!  Thanks

@UmerHA Is slicing the appropriate way to handle limiting search results? can we not push this back to cognitive search to do a top N? I'm trying to use RetrievalQA, my retriever in this case "AzureCognitiveSearchRetriever" if I do a generic query it's going to return a ton of documents, is there no way to limit this on the Retriever instance?
qa = RetrievalQA.from_chain_type(
llm=open_ai,
chain_type="stuff",
retriever= AzureCognitiveSearchRetriever(xxxx),
chain_type_kwargs=chain_type_kwargs,
verbose=True,
)

@UmerHA Currently AzureCognitiveSearchRetriever retrieves all the documents, but in case I want to limit only 5 relevant documents and then use RetrievalQA, is it possible? As currently, I get token limit breach. Following is my code.
`from langchain.retrievers import AzureCognitiveSearchRetriever
from langchain.chains import RetrievalQA
retreiver = AzureCognitiveSearchRetriever(content_key="content", index_name=AZURE_SEARCH_INDEX, api_key=search_key, service_name=AZURE_SEARCH_SERVICE)
docs = retreiver.get_relevant_documents(user_input)
qa_chain = RetrievalQA.from_chain_type(
llm,
retriever=retreiver,
return_source_documents=True,
chain_type="refine"
)
result = qa_chain({"query": user_input})
`
I get the following error:
"This model's maximum context length is 4097 tokens, however you requested 6212 tokens"
Reason: Currently retriever tries to perform refine over all documents, but I want it to refine over only Top 5 relevant docuements, so that token limit is not crossed

@harryaultdev @reeshabh90 Added that option - see #7690. You can use a top_n parameter to set limit the number of documents returned
from langchain.retrievers import AzureCognitiveSearchRetriever
from langchain.chains import RetrievalQA

retreiver = AzureCognitiveSearchRetriever(content_key="content", index_name=AZURE_SEARCH_INDEX, api_key=search_key, service_name=AZURE_SEARCH_SERVICE, **top_n=10**)
docs = retreiver.get_relevant_documents(user_input)

qa_chain = RetrievalQA.from_chain_type(
    llm,
    retriever=retreiver,
    return_source_documents=True,
    chain_type="refine"
)
result = qa_chain({"query": user_input})

Hi @UmerHA
I also created a PR: 7692
Kindly review

Hey @UmerHA , Apologies, saw the PR you have already created. Awesome!

Hey @UmerHA , Apologies, saw the PR you have already created. Awesome!

No worries! Diving in and solving your problems yourself is exactly the right attitude. Keep it!

@baskaryan @UmerHA  Do we need to upgrade LangChain version via pip?

@baskaryan @UmerHA Do we need to upgrade LangChain version via pip?

Yes, pip install -U langchain, where the U stands for upgrade

I still get following error:
1 validation error for AzureCognitiveSearchRetriever
top_n
extra fields not permitted (type=value_error.extra)

I still get following error: 1 validation error for AzureCognitiveSearchRetriever top_n extra fields not permitted (type=value_error.extra)

Sry, its top_k now, not top_n, so it's retreiver = AzureCognitiveSearchRetriever(<all the other stuff>, top_k=10)

Okay, however, even after fresh installation of langchain, this does not show up in code.
Is the new change merged in main code?

Okay, however, even after fresh installation of langchain, this does not show up in code.
Is the new change merged in main code?

Just checked the master branch, that update is there. But it is not released, I think. Could be the reason that pip update doesn't serve our purposes.


Adds non-operational rewards withholding

Closes https://github.com/onflow/flow-core-contracts/issues/248
Some nodes do not upgrade quickly enough for sporks or other network upgrades
and some nodes spend a lot of time down
This PR introduces a mechanism for the staking admin to mark certain nodes as inactive and marks how much their rewards should be decreased by
Nodes that are marked as inactive will have their rewards decreased by the amount specified by the admin when rewards are calculated. The delegators to an inactive node will also have their rewards decreased.
The withheld rewards are then distributed among the rest of the non-offending nodes and delegators.
After rewards are calculated, the inactive nodes list is cleared so the node has the opportunity to fix their misbehavior before the next rewards payment.
This process will be controlled manually first, but is a small work towards future automated slashing in the future.

hi @joshuahannan , first of all this is a great idea.
I have a question about The delegators to an inactive node will also have their rewards decreased. part.  For delegator rewards, there is a fixed percentage fee node taking for staking on behalf of delegators, wouldn't be more fair to remove the penalty first from that bucket, then apply it to delegators? Otherwise it is a bit of unnecessary heat on node operators. ( If it will be really implemented with uptime in the future instead of admin involvement )

@bluesign Just to clarify, you are suggesting that if the amount of rewards withheld is somewhere greater than zero but less than 100%, we take it from the node's delegator cuts first before taking from the delegators? Or are you suggesting something else? I'm a little confused

@joshuahannan , sorry I could state more clear.
Now there is a 8% cut for code operator. 92% is going to the delegator. If there would be 2% amount to withheld. I think first this should go from cut, so node operator should get 6%, delegator should still get 92%.
So if it is 8% -> 8% withheld 0% cut 92% delegators.
Only after 8% of penalty, effecting delegators revenue can be beneficial to the ecosystem. Users don't have much effect about node operators uptime, also this allows node operators to be more motivated to keep uptime high.

clarify staking admin and service account relationship , looks great

I addressed all the important PR comments so this should be good to deploy. I'm gonna try to clean up some more things in the tests tomorrow morning before we merge though


📋 fix: Ensure Textarea Resizes in Clipboard Edge Case

Summary
In my testing prior to release, I wanted to tackle a bug I had noticed previously, which was introduced by recent textarea optimizations: https://github.com/danny-avila/LibreChat/pull/2058
Before this update, if you paste content expanding the textarea, submit the message, create a new chat, then paste any content expanding the textarea again, delete it, the expanded textarea remains
Before
https://github.com/danny-avila/LibreChat/assets/110412045/5de118c7-5237-4540-b1c2-3e2435c71da6
After
https://github.com/danny-avila/LibreChat/assets/110412045/2afb043e-4cec-4255-a2e6-0ad7c55effb9
Change Type

[x] Bug fix (non-breaking change which fixes an issue)

Testing
Try the reproduction shown in the video and explained in summary before this update, then try it after applying the PR.
Checklist

[x] My code adheres to this project's style guidelines
[x] I have performed a self-review of my own code
[x] I have commented in any complex areas of my code
[x] I have made pertinent documentation changes
[x] My changes do not introduce new warnings
[x] I have written tests demonstrating that my changes are effective or that my feature works
[x] Local unit tests pass with my changes
[x] Any changes dependent on mine have been merged and published in downstream modules.
[x] New documents have been locally validated with mkdocs

Thanks!


Removed module variable from global scope in angular-mocks.

Fixes issue https://github.com/borisyankov/DefinitelyTyped/issues/2072
@Bartvds

close the PR because this is too old.


RFC: Nullish Operator

RFC Is in PR #33
rendered
Please use this space to discuss the RFC.

closing in favor of discussing on PR directly


cleanup evaluation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Lights opened itself constantly

I see the issue ‘Bluetooth mesh does not get the status correctly #1335’. The conversation mentioned the adaptive-lighting integration.

I also use the adaptive-lighting integration. Here's my issue: During my trip, I found my mesh-group light (I got only one mesh group) opened itself constantly. I'm sure the open status is correct because I can see the light through the camera. And my mom asked me what happened to the 3 lights.

The mesh-group(筒灯) includes 3 lights, which is 筒灯1,筒灯2 and 筒灯3. All 4 entities are added to gateway3, and only 1 entity(the mesh group) is added to Homekit Bridge and adaptive-lighting.

By the way, the gateway3 version is 4.0.5.
home-assistant_xiaomi_gateway3_2024-05-04T15-05-19.456Z.log

Device information:
3 same lights
Mesh: YLTS02YL/YLTS04YL, yeelink.light.ml1

it happened again. Here's the log.
Is the issue caused by xiaomi_miot? My ha's Core version is 2024.5.0 currently (The latest is 5.1) .
日志: homeassistant.core
来源: core.py:2758
首次发生: 2024年5月3日 08:15:11 (136 全部发生)
上次记录: 02:28:36
Error executing service: <ServiceCall light.turn_on (c:01HX2DFWF0:al:5CD2:ntrv:H3): entity_id=['light.yeelink_ceil26_2404_light'], params=transition=45.0, brightness=3, color_temp=370, color_temp_kelvin=2702>
Error executing service: <ServiceCall light.turn_on (c:01HX2DJMV7:al:5CD2:ntrv:H4): entity_id=['light.yeelink_ceil26_2404_light'], params=transition=45.0, brightness=3, color_temp=370, color_temp_kelvin=2702>
Error executing service: <ServiceCall light.turn_on (c:01HX2DND7F:al:5CD2:ntrv:H5): entity_id=['light.yeelink_ceil26_2404_light'], params=transition=45.0, brightness=3, color_temp=370, color_temp_kelvin=2702>
Error executing service: <ServiceCall light.turn_on (c:01HX2DR5KM:al:5CD2:ntrv:H6): entity_id=['light.yeelink_ceil26_2404_light'], params=transition=45.0, brightness=3, color_temp=370, color_temp_kelvin=2702>
Error executing service: <ServiceCall light.turn_on (c:01HX2DTXZT:al:5CD2:ntrv:H8): entity_id=['light.yeelink_ceil26_2404_light'], params=transition=45.0, brightness=3, color_temp=370, color_temp_kelvin=2702>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 2758, in _run_service_call_catch_exceptions
await coro_or_task
File "/usr/src/homeassistant/homeassistant/core.py", line 2779, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 975, in entity_service_call
single_response = await _handle_entity_call(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1047, in _handle_entity_call
result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/light/init.py", line 627, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1680, in async_turn_on
await self.hass.async_add_executor_job(ft.partial(self.turn_on, **kwargs))
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_miot/light.py", line 187, in turn_on
ret = self.send_miio_command('set_bright', [val, 'smooth', trs])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_miot/init.py", line 1340, in send_miio_command
return super().send_miio_command(method, params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/xiaomi_miot/init.py", line 989, in send_miio_command
self.hass.bus.async_fire(f'{DOMAIN}.send_miio_command', {
File "/usr/src/homeassistant/homeassistant/core.py", line 1508, in async_fire
self._hass.verify_event_loop_thread("async_fire")
File "/usr/src/homeassistant/homeassistant/core.py", line 440, in verify_event_loop_thread
frame.report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 162, in report
_report_integration(what, integration_frame, level, error_if_integration)
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 203, in _report_integration
raise RuntimeError(
RuntimeError: Detected that custom integration 'xiaomi_miot' calls async_fire from a thread at custom_components/xiaomi_miot/init.py, line 989: self.hass.bus.async_fire(f'{DOMAIN}.send_miio_command', {. Please report it to the author of the 'xiaomi_miot' custom integration.
日志: homeassistant.helpers.frame
来源: helpers/frame.py:190
首次发生: 2024年5月3日 02:44:23 (143 全部发生)
上次记录: 02:28:36
Detected that custom integration 'xiaomi_miot' accesses hass.helpers.service. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from service directly at custom_components/xiaomi_miot/init.py, line 560: hass.helpers.service.async_register_admin_service(, please create a bug report at https://github.com/al-one/hass-xiaomi-miot/issues
Detected that custom integration 'hacs' accesses hass.helpers.event. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from event directly at custom_components/hacs/base.py, line 642: self.hass.helpers.event.async_track_time_interval(, please create a bug report at https://github.com/hacs/integration/issues
Detected that custom integration 'xiaomi_miot' calls async_fire from a thread at custom_components/xiaomi_miot/init.py, line 989: self.hass.bus.async_fire(f'{DOMAIN}.send_miio_command', {, please report it to the author of the 'xiaomi_miot' custom integration
Detected that custom integration 'adaptive_lighting' accesses hass.helpers.entity_component. This is deprecated and will stop working in Home Assistant 2024.11, it should be updated to import functions used from entity_component directly at custom_components/adaptive_lighting/switch.py, line 2471: await self.hass.helpers.entity_component.async_update_entity(light), please create a bug report at https://github.com/basnijholt/adaptive-lighting/issues
Detected that custom integration 'xiaomi_miot' calls async_write_ha_state from a thread at custom_components/xiaomi_miot/init.py, line 1906: self.async_write_ha_state(), please report it to the author of the 'xiaomi_miot' custom integration

There is nothing in your logs about this component
Your error about the component xiaomi_miot
Your screenshots are useless because I don't understand your language

My mesh-group (light1, light2 and light3) just turned on by itself. I screenshotted the log and translated it. I'm pretty sure the translation is correct (I checked it 3 times).It says 'triggered by service'. what service indeed? What service may it be?
I did not add this mesh-group (light1, light2 and light3) into xiaomi_miot. In my understanding, the issue can't be caused by xiaomi_miot.
And I only add the group into Gateway3. (I did not add light1, light2 or light3 into Gateway3)

I'm really confused.
home-assistant_adaptive_lighting_2024-05-05T15-57-19.654Z.log
home-assistant_xiaomi_gateway3_2024-05-05T15-59-21.613Z.log


Argument list too long: recursive header expansion failed

I get such error in Xcode "Argument list too long: recursive header expansion failed", version of react-native: 0.47.2,  "react-native-fcm": "^9.7.2"

get latest one.
The old repo scans the whole ios folder for header files.
If you cannot upgrade, move your Index folder to somewhere outside.


fix: improve GridFormInputGroup tests

Signed-off-by: Aaron Foster Breilyn<EMAIL_ADDRESS>Overview
Refactors test helper methods into a __fixtures__ directory. Also:

Changes the assertions in those helpers to be more canonical
Cleans up exports
Adds more specific typing

This is a response to comments made on https://github.com/Codecademy/client-modules/pull/863 after we'd merged.
PR Checklist

[x] Related to JIRA ticket: EN-117, EN-121
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-labs@1.7.36-alpha.69eb48.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f06281025fbebd31bc16882--codecademy-styleguide.netlify.appDeploy Logs

Ignored the codecov warning and merged because this is a refactor that does not remove test coverage.


Lint other projects with our rules

We have to check our code quality. If we check other projects with our linter rules we could see how our rules worked and how good the quality of the other projects is
Describe the solution you'd like
Lint some other projects of SWT

First of all we have to adjust our linter rules


polonium: 0.6.0 -> 1.0b1

Description of changes
Github release
Things done
i built it on my mashine (x86_64-linux with plasma6) and it builds successfully and works as intended
fixes #293409

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

this still builds it against plasma5 and building against plasma6 will fail as we need to invoke kpackagetool.
I have been using a local package here (just for reference):
{ lib
, fetchFromGitHub
, buildNpmPackage
, qtbase
, plasma5Packages ? null
, kdePackages ? null
}:

# how to update:
# 1. check out the tag for the version in question
# 2. run `prefetch-npm-deps package-lock.json`
# 3. update npmDepsHash with the output of the previous step

let
  isQt5 = (lib.versions.major qtbase.version) == "5";

in
buildNpmPackage {
  pname = "polonium-git";
  version = "1.0.0.beta1";

  src = fetchFromGitHub {
    owner = "zeroxoneafour";
    repo = "polonium";
    rev =
      if isQt5
      then "dbb86e5e829d8ae57caf78cd3ef0606fdc1fbca5"
      else "32b8af8a65242e2f213c268ac4be9101321b0130";
    hash =
      if isQt5
      then "sha256-MKG255AtybzXLHaxaBjk6HhcMbgGUMPiNn5tjQDaLMQ="
      else "sha256-2uthjNhQm+hkRCPXGQm2LZunTj+J0SUuUfZL0PeRd4s=";
  };

  npmDepsHash =
    if isQt5
    then "sha256-NBEkn4wNV34YWyADtjWdhnUXEfe/xomeCoiWAmin4+M="
    else "sha256-kaT3Uyq+/JkmebakG9xQuR4Kjo7vk6BzI1/LffOj/eo=";

  # the installer does a bunch of stuff that fails in our sandbox, so just build here and then we
  # manually do the install
  postPatch = ''
    substituteInPlace Makefile \
      --replace-fail "build install cleanall" "res src"
  '';

  nativeBuildInputs = [ (if isQt5 then plasma5Packages else kdePackages).kpackage ];

  dontNpmBuild = true;

  dontWrapQtApps = true;

  installPhase = ''
    runHook preInstall

    kpackagetool${if isQt5 then "5" else "6"} --install pkg --packageroot $out/share/kwin/scripts

    runHook postInstall
  '';

  env.LANG = "C.UTF-8";

  meta = with lib; {
    description = "Auto-tiler that uses KWin ${if isQt5 then "5.27" else "6"}+ tiling functionality";
    license = licenses.mit;
    maintainers = with maintainers; [ peterhoeg ];
    inherit (kdePackages.kpackage.meta) platforms;
  };
}

Pardon my poor choice of words - it's not that it's built against plasma6 as such (there are no direct dependencies other than the packaging tool) but the build will fail when the plasma5 build-infra is ripped out.

@peterhoeg Should this be merged, or you want your version of bump instead?

This version of polonium deprecates Plasma 5 support (and does nothing there) - is there a compromise? Could libsForQt5 be held back on 0.6.0 while kdePackages gets >1.0?

This version of polonium deprecates Plasma 5 support (and does nothing there) - is there a compromise? Could libsForQt5/plasma5Packages be held back on 0.6.0 while kdePackages gets >1.0?

I thought that release notes stated it is the last version to support plasma5

Update to Plasma 6. Plasma 5 is still available with this release, but the code quality is worse, it may have more (or fewer) bugs, and it is lacking shortcuts.

However, yeah, I do think that plasma5 package should also be present for backward compatibility

I thought that release notes stated it is the last version to support plasma5

Update to Plasma 6. Plasma 5 is still available with this release, but the code quality is worse, it may have more (or fewer) bugs, and it is lacking shortcuts.

"Support" in this case appears to mean "registers itself as a kwin script at all", but practically tiling functionality is lost - unsurprising as the internals were reworked for Plasma 6 in this release. Loss of shortcuts is pretty big for a tiling plugin too.

I do think that plasma5 package should also be present for backward compatibility
It appears v1.0 proper will deprecate Plasma 5 and push support for it off to a special branch, so preemptively splitting it into its own package seems worthwhile and congruent with the developer's intent: https://github.com/zeroxoneafour/polonium/issues/106

I would hope to see Plasma 5 support in general kept around for a while yet. Plasma 6 feels amazing but it seems even window management can cause fatal crashes at present - I get one with splitting out documents from OnlyOffice, and Polonium itself has some window dragging related crashes. It's a pretty far cry from P5 in terms of everyday stability.

I would hope to see Plasma 5 support in general kept around for a while yet. Plasma 6 feels amazing but it seems even window management can cause fatal crashes at present - I get one with splitting out documents from OnlyOffice, and Polonium itself has some window dragging related crashes. It's a pretty far cry from P5 in terms of everyday stability.

I did experience a lot of crashes with polonium beta on 6, yes
Can you please PR it? I can do that in the next 30-40 hours if you can't.

Can you please PR it? I can do that in the next 30-40 hours if you can't.

any ideas on how to structure it? it looks like it should go under pkgs/kde somewhere, but there's no 3rd party dir there, and the 3rdparty/addons dir in desktops/plasma-5 seems wrong as it's explicitly splitting away from p5.

I guess we need @NixOS/qt-kde for that)


Added nodejs and npm for chrome extension

This PR is to solve the issue when trying to develop for the chrome extension through sail.
Currently, when running sail run roberthmiller/sail, I am unable to use npm (getting the deps for the chrome extension). This PR is to fix that.
Edit:
Resolves #161

Note: This currently fails. I am working on a fix for this.

Ok, This is ready for review.

I will make some updates and you can squash and merge :smile:

If it is decided to change this to NVM, can we do this in a later PR?

I'd rather just use NVM in this PR and change it later if needed, as I'm pretty sure that's how Kyle will want it installed. Also, that'll remove the need to install software-properties-common.

Ok, will update that after I am done submitting this other PR.

@nathanpotter This PR should be good to go.

Good to go

:+1:


How to update the uniforms of an Effect

Hi,
I know how to update the uniforms of a custom Effect, but I'm not sure how to that with the included ones.
For instance, with a ChromaticAberrationEffect like this:
composer.addPass( new EffectPass( camera,
    new ChromaticAberrationEffect({
        offset: new THREE.Vector2(.005, 0)
    }),
));

How could I update the offset?
Thanks!

The offset uniform can be accessed via the uniforms field: effect.uniforms.get("offset").value.x = 0;. This effect also provides an offset getter which acts as a shortcut: effect.offset.value.x = -0.004;.

Excellent, thanks @vanruesc 🙏

FYI: the offset getter has been superseded by getOffset() and setOffset() in<EMAIL_ADDRESS>


[Input] Workaround for gamestudio input

PR Details
Changes how the workaround for raw input operates to fix #686
Again, still not exactly sure what's going on here but this work.
Related Issue
Fixes #686
Previous related PR #181 which 'fixed' issue #159
Motivation and Context
Fixes/workaround a bug.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

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


Fixed #32600 -- Fixed Geometry collections and Polygon segmentation fault on macOS ARM64.

https://code.djangoproject.com/ticket/32600
In GIS, when constructing Polygon, MultiPolygon, MultiLineString, or MultiPoint in a process running natively on Apple's M1 processor (arm64 architecture), the GEOS call reliably causes a segmentation fault; this occurs in production applications with various versions of GEOS and Django, as well as when running Django runtests with the latest supported versions of each.
I can confirm that this is indeed a Django bug, and I was able to replicate segfaults on Django's main branch, so it appears the GEOS 3.9 update in https://code.djangoproject.com/ticket/32544 did not fix this. It's also been replicated in e.g. https://github.com/libgeos/geos/issues/528.
It appears that in the current GEOS integration, argument signatures were omitted in favor of automatically casting arguments for a few polygon-related API calls. While this appears to have worked fine on x86 and x64, on macOS arm64 (for native M1 processors), it causes seemingly random data to be provided in place of arguments after the first, reliably causing segmentation faults whenever a Polygon, MultiPolygon, or MultiLineString is constructed. Underlying CFFI internals may be less lenient to unspecified arguments in Apple's implementation than on other platforms. Moving to explicit signatures works fine, and I see no reason having explicit signatures should cause problems on other platforms (though we should ensure CI passes).
All GIS tests now pass, and the changes are fully covered by test_geos. The deeper issue in testing is that CI does not run on Apple hardware, so it will be difficult to prevent regressions. However, the code changes are small and well-documented, and I'd suggest that Apple/arm64 CI will be important but not urgent.
For organizations using older versions of Django, I've also made a monkey-patch available at https://gist.github.com/bpartridge/26a11b28415d706bfb9993fc28767d68 which can be added in any initialization code (or even called from settings.py) before Polygon objects are created. When applied in test settings against the main branch, all GIS tests pass as well; functionality is identical to the PR above.

Awesome! Just a small linting about imports to fix. Thanks a lot.

Upon further reviewing this, does this apply as a crashing bug per https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions-policy ? If so, should I add a release note in preparation for backporting? Do maintainers handle the backporting process, or should I create separate backport PRs?

@bpartridge Thanks for updates :+1: Welcome aboard :boat:
I pushed edits to a release note.

buildbot, test on oracle.

@aapris @szunami @HorebParraud Can one of you confirm that this fixes the issue on M1?

It works perfectly!
> pip install -r requirements.txt
Obtaining Django from git+https://github.com/bpartridge/django.git@ticket_32600#egg=Django (from -r requirements.txt (line 3))
  Updating ./venv/src/django clone (to revision ticket_32600)
  Running command git fetch -q --tags
  Running command git reset --hard -q b2336516a8ac6ae754a254a8c1d872da0ca96dc2
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
...

> python manage.py shell
Python 3.9.9 (main, Nov 21 2021, 03:16:13)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.30.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: from django.contrib.gis.geos import MultiPolygon

In [2]: p = MultiPolygon()

In [3]: p
Out[3]: <MultiPolygon object at 0x150116088>

@HorebParraud Thanks :+1:

Works for me too! \ö/
Thanks!
% geos-config --version
3.10.1
% gdal-config --version
3.3.3
% python -V
Python 3.9.7
% pip freeze|grep -i django
Django @ git+https://github.com/bpartridge/django.git@b2336516a8ac6ae754a254a8c1d872da0ca96dc2

@aapris Thanks :+1:


add default postgres password environment to fix integration_tests ci…

…rcle job
Signed-off-by: Daniel Nurmi<EMAIL_ADDRESS>

@Btodhunter, @alfredodeza - from previous discussion, adding the default POSTGRES environment to allow intergration_tests job to execute


Mirror OBS signing key on owncloud.org

I'm absolutely not sure if that is the way to add static files and link to them, so feel free to make adjustments.
@MorrisJobke FYI

@tomneedham Please re-review :)

Super :+1:


Chess: Move F3 to F4

Please do not change the title. Just click "Submit new issue". You don't need to do anything else :D

@N-NeelPatel you cannot play two consecutive moves no matter how much you try. Once you play as either black or white, you have to wait until someone else plays as the opposite color.
Please, try not to spam with many invalid moves in such a short amount of time since many people are subscribed to this repo and they will get an e-mail every time someone opens an issue.
Many thanks 😄

Sorry my bad.


⚠ Bofrost.fr has degraded performance

In ec3792e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1173 ms

Resolved: Bofrost.fr performance has improved in 8ed351f after 26 minutes.


code refactor (merge similar code)

I wonder why you are working on this.  The code might be a bit nicer, but otherwise there is no advantage.
You cannot use "for (int i = 7", older C standards don't support it.  The code most follow ANSI C.

ok, now I see why you didn't put int i inside for(...).
The duplicated part (addrlen + 3 + (grplen * cols - 1)/octspergrp + p) is quite long and this refactor make the code easier to read and understand. When I read this code, I had to reread and compare 3 places where it appear to make sure there's no difference.
The performance gain is minimal, but it will be easier to change it later (instead of changing multiple places).


Deal gracefully with Websocket exceptions

We're getting an occasional ParseException "Failed reading: unknown opcode ..." and it appears to be coming from the Websocket library.
To wit:
$ ag ParseException
websockets-<IP_ADDRESS>/src/Network/WebSockets/Stream.hs
156:    go (Atto.Fail _ _ err) _ = throwIO (ParseException err)

websockets-<IP_ADDRESS>/src/Network/WebSockets/Types.hs
121:    | ParseException String

websockets-<IP_ADDRESS>/tests/haskell/Network/WebSockets/Server/Tests.hs
133:    handleClose _ (ParseException _) =
146:        handler (ParseException _) = error "Unexpected parse exception"

And also:
> matterhorn: <socket: 15>: hGetBuf: resource vanished (Connection reset by peer)
matterhorn: ConnectionClosed

This is now fixed in the API package.


Substructures: SMARTSQuery type is broken

The query graph contained in our SMARTSQuery type uses a SMILES-based type from MolecularGraph.jl, which is also incompatible with our current SMARTSQuery constructor.

Base.match for SMARTS matching is also broken.


Bulk export throughput is limited for large resource counts

When a bulk export job runs it processes a resource type (like Observation) serially using batches of 1000 resources.
The content for each batch is driven using a pagination pattern based on two queries: a count followed by an identity selection query:
SELECT COUNT(DISTINCT R.LOGICAL_RESOURCE_ID)  FROM Observation_LOGICAL_RESOURCES LR  JOIN ( SELECT * FROM Observation_RESOURCES IR WHERE (LAST_UPDATED >= ?)) R ON R.RESOURCE_ID = LR.CURRENT_RESOURCE_ID  AND R.IS_DELETED = 'N'
  searchArgs=[2021-01-05 08:56:07.131]
  count=224697 executionTime=528.458981ms
[1/12/21 16:14:05:585 UTC] 000000ae FHIRPersisten 1   searchResultCount = 224697
[1/12/21 16:14:08:379 UTC] 000000ae ResourceDAOIm 1   DB search for ids complete. SqlQueryData [queryString=SELECT R.RESOURCE_ID,MIN(S1.DATE_START)  FROM Observation_LOGICAL_RESOURCES LR  JOIN ( SELECT * FROM Observation_RESOURCES IR WHERE (LAST_UPDATED >= ?)) R ON R.RESOURCE_ID = LR.CURRENT_RESOURCE_ID  AND R.IS_DELETED = 'N'  LEFT OUTER JOIN Observation_DATE_VALUES S1 ON (S1.PARAMETER_NAME_ID=1003 AND S1.LOGICAL_RESOURCE_ID = R.LOGICAL_RESOURCE_ID)  GROUP BY R.RESOURCE_ID  ORDER BY MIN(S1.DATE_START) ASC NULLS LAST LIMIT 1000 OFFSET 215000, bindVariables=[2021-01-05 08:56:07.131]]

The second query must join/sort a dataset comprising 224697 records. This takes about 2.5 seconds each time the query is run. The time of these two queries represents the bulk of the time to process one batch. Because this processing happens serially, throughput is lower than it could be if a more efficient mechanism were used to drive the resource selection.
Investigate other options to break the export dataset into batches.

I think this is actually in progress.

I think this is actually in progress.


Test File

Verify CircleCI Build

@Dorcas-BD nice but circleci isn't initiating automatically, ensure circleci gets initiated automatically when a PR is sent from a forked repo!

Alright, thank you

@Dorcas-BD nice but circleci isn't initiating automatically, ensure circleci gets initiated automatically when a PR is sent from a forked repo!

Alright, thank you

I have adjusted the circleci setting for the project @Redeem-Grimm-Satoshi


Complete adding jsDoc comments to decorators, accessors and associated types

As part of generating reference documentation for emitters, add jsDoc comments to public accessors and associated types

est: 8

Completed in #1860.


Cannot Use SageMaker Studio Lab Due to Service Terms Restriction

Dear SageMaker Studio Lab Support Team,
I have been using SageMaker Studio Lab for approximately one year without any issues. Recently, when I attempt to use it, I receive the following message:
"You can't use the project runtime because your account is associated with activity that may have violated our Service Terms."
I am not aware of any activity that could have violated the Service Terms. Could you please help me resolve this issue?
Thank you for your support. I look forward to hearing from you.
Best regards,

Hi, can you please send me a private message here so I can capture your details securely?
thanks
Michele
https://pages.awscloud.com/GLOBAL_PM_PA_amazon-sagemaker_20211116_7014z000000rjq2-registration.html

Hi Michele,
Thank you for your response. I have submitted the requested details via the provided form. Please let me know if you need any additional information.
Best regards,


[Transaction] TransactionBuffer recover from log

Motivation
Currently, the TransactionBuffer can't be recovered.
Modifications
Read the TransactionBuffer log and recover related data.
Verifying this change
This change added tests and can be verified as follows:

org.apache.pulsar.broker.transaction.TransactionProduceTest#recoverFromLogTest

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

This transaction buffer design had been changed, I closed this PR.


RC0 issue

hey, thirst thanks for the super work. with the latest update ionic doesn't use gulp, what next?

Your'e totally right, I should figure it out.
Ill probably work on it tommorow!

okey thanks, just wainting for

Seems like upgrading to RC.0 requires more work than I though (since they also upgraded Angular), but look forward for my updates!

i'm waiting

I updated the plugin and the docs, enjoy!


Add README.md with initial structure

Pull Request

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

#15
#14
#13
#12  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 27, 2:37 PM EDT: A user started a stack merge that includes this pull request via Graphite.


Undoing what seems to be a faulty auto-merge in last weekly sync.

It seems to have re-introduced ROCm specific "skips" in the subtests within the test def_function_xla_jit_test.py. We had removed them a while back, but had not upstreamed that change. Somehow the old upstream code flowed back to us as part of weekly merge...not quite sure how/why that happened.

Can one of the admins verify this patch?

one failure in rocm and two in rocm-xla, neither are related to the change in this PR (which does not change any source code, only one test)
http://ml-ci.amd.com:21096/job/develop-upstream-unit-tests/job/tensorflow-upstream-unit-tests/2144/console
http://ml-ci.amd.com:21096/job/develop-upstream-unit-tests/job/tensorflow-upstream-unit-tests-rocm-xla/1498/console

jenkins : retest rocm-xla please

jenkins : retest rocm please

jenkins : retest rocm-xla please

jenkins : retest rocm please

Thanks Deven! This is the very wired case I encountered last time. Upstream was doing a revert on top of another revert which blow away some of downstream changes. Thanks for identifying and fixing it.


Add reminder for model card consistency

PR related to https://github.com/huggingface/hub-docs/pull/1186.
If any modelcard/datasetcard content is modified, let's post a warning on the PR to remind the author/reviewers to also check the equivalent files in hub-docs. More details on https://github.com/huggingface/hub-docs/pull/1186#issue-2076837057.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


PostgreSQL adapter not working

Latest version that introduced some real persistence (thanks for that, by the way!) doesn't seem to be fully working:
kong-ui-db_1  | ERROR:  relation "public.konga_users" does not exist at character 46
kong-ui-db_1  | STATEMENT:  SELECT COUNT(*) as count FROM (SELECT * FROM "public"."konga_users" ) AS "konga_users"
ui_1          | User had models, so no seed needed
ui_1          | A hook (`load-db`) failed to load!
ui_1          | Error (E_UNKNOWN) :: Encountered an unexpected error
ui_1          | error: relation "public.konga_users" does not exist
ui_1          |     at Connection.parseE (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:539:11)
ui_1          |     at Connection.parseMessage (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:366:17)
ui_1          |     at Socket.<anonymous> (/app/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:105:22)
ui_1          |     at emitOne (events.js:96:13)
ui_1          |     at Socket.emit (events.js:191:7)
ui_1          |     at readableAddChunk (_stream_readable.js:176:18)
ui_1          |     at Socket.Readable.push (_stream_readable.js:134:10)
ui_1          |     at TCP.onread (net.js:563:20)
ui_1          |
ui_1          | Details:  error: relation "public.konga_users" does not exist
ui_1          |

A quick docker-compose.yml that demonstrates this problem:
version: '2'
services:
  kong-ui-db:
    image: postgres:9.4
    environment:
      - POSTGRES_USER=kong-ui
      - POSTGRES_DB=kong-ui
      - POSTGRES_PASSWORD=testtest123
  ui:
    image: pantsel/konga:latest
    environment:
      - DB_ADAPTER=postgres
      - DB_HOST=db
      - DB_USER=kong-ui
      - DB_PASSWORD=testtest123
      - DB_DATABASE=kong-ui
    links:
      - kong-ui-db:db

Also, unrelated, but it would be great if you enabled tagging for docker hub builds so that we can revert back to older versions in case something breaks in the new release. Thanks so much for this project - its awesome!

Hello @smazurov,
Have you manually created the kong-ui database in your PGSQL server? Konga doesn't create the database, it just populates it (unless it's MongoDB).
I'm asking because i see: SELECT COUNT(*) as count FROM (SELECT * FROM "public"."konga_users" ) AS "konga_users".
Shouldn't it be: SELECT COUNT(*) as count FROM (SELECT * FROM "kong-ui"."konga_users" ) AS "konga_users"?
It seems to be working on my end...
Thanks for the feedback.

did you run docker-compose.yml i provided? It does create kong-ui db that I configured as DB_DATABASE in konga service.

It seems that Users where seeded in some database (maybe "public"?)

me too.
23/03/2017 01:23:34User had models, so no seed needed
23/03/2017 01:23:34A hook (load-db) failed to load!
23/03/2017 01:23:34Error (E_UNKNOWN) :: Encountered an unexpected error
23/03/2017 01:23:34: ER_NO_SUCH_TABLE: Table 'konga.konga_users' doesn't exist
23/03/2017 01:23:34    at Query.Sequence._packetToError (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/sequences/Sequence.js:48:14)
23/03/2017 01:23:34    at Query.ErrorPacket (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/sequences/Query.js:83:18)
23/03/2017 01:23:34    at Protocol._parsePacket (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Protocol.js:280:23)
23/03/2017 01:23:34    at Parser.write (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Parser.js:73:12)
23/03/2017 01:23:34    at Protocol.write (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Protocol.js:39:16)
23/03/2017 01:23:34    at Socket. (/app/node_modules/sails-mysql/node_modules/mysql/lib/Connection.js:96:28)
23/03/2017 01:23:34    at emitOne (events.js:96:13)
23/03/2017 01:23:34    at Socket.emit (events.js:191:7)
23/03/2017 01:23:34    at readableAddChunk (_stream_readable.js:176:18)
23/03/2017 01:23:34    at Socket.Readable.push (_stream_readable.js:134:10)
23/03/2017 01:23:34    at TCP.onread (net.js:563:20)
23/03/2017 01:23:34    --------------------
23/03/2017 01:23:34    at Protocol._enqueue (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Protocol.js:141:48)
23/03/2017 01:23:34    at PoolConnection.query (/app/node_modules/sails-mysql/node_modules/mysql/lib/Connection.js:201:25)
23/03/2017 01:23:34    at FIND (/app/node_modules/sails-mysql/lib/adapter.js:838:20)
23/03/2017 01:23:34    at afterwards (/app/node_modules/sails-mysql/lib/connections/spawn.js:84:5)
23/03/2017 01:23:34    at /app/node_modules/sails-mysql/lib/connections/spawn.js:40:7
23/03/2017 01:23:34    at Ping.onOperationComplete [as _callback] (/app/node_modules/sails-mysql/node_modules/mysql/lib/Pool.js:99:5)
23/03/2017 01:23:34    at Ping.Sequence.end (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/sequences/Sequence.js:96:24)
23/03/2017 01:23:34    at Ping.Sequence.OkPacket (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/sequences/Sequence.js:105:8)
23/03/2017 01:23:34    at Protocol._parsePacket (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Protocol.js:280:23)
23/03/2017 01:23:34    at Parser.write (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Parser.js:73:12)
23/03/2017 01:23:34    at Protocol.write (/app/node_modules/sails-mysql/node_modules/mysql/lib/protocol/Protocol.js:39:16)
23/03/2017 01:23:34    at Socket. (/app/node_modules/sails-mysql/node_modules/mysql/lib/Connection.js:96:28)
23/03/2017 01:23:34    at emitOne (events.js:96:13)
23/03/2017 01:23:34    at Socket.emit (events.js:191:7)
23/03/2017 01:23:34    at readableAddChunk (_stream_readable.js:176:18)
23/03/2017 01:23:34    at Socket.Readable.push (_stream_readable.js:134:10)
23/03/2017 01:23:34    at TCP.onread (net.js:563:20)
23/03/2017 01:23:34
23/03/2017 01:23:34Details:  Error: ER_NO_SUCH_TABLE: Table 'konga.konga_users' doesn't exist
23/03/2017 01:23:34

Hello @maltyxx,
Have you manually created a db named konga first?

Yes

Ok I just understand, it be not that I create the database the first time

As a refernce check out issue #40

Hi @pantsel ,
I am getting the same error in production mode.
It runs well in development mode but when I trying with production mode, it throws an error.
> node --harmony app.js --prod

No DB Adapter defined. Using localDB...
Hook:api_health_checks:process() called
Hook:health_checks:process() called
Hook:start-scheduled-snapshots:process() called
Hook:user_events_hook:process() called
Failed to seed User Error (E_UNKNOWN) :: Encountered an unexpected error
error: relation "public.konga_users" does not exist
    at Connection.parseE (/home/lcom58/Downloads/konga-0.10.4/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:539:11)
    at Connection.parseMessage (/home/lcom58/Downloads/konga-0.10.4/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:366:17)
    at Socket.<anonymous> (/home/lcom58/Downloads/konga-0.10.4/node_modules/sails-postgresql/node_modules/pg/lib/connection.js:105:22)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TCP.onread (net.js:548:20)

My settings in local.js
connections: {
    postgres: {
      adapter: 'sails-postgresql',
      host: process.env.DB_HOST || 'localhost',
      user: process.env.DB_USER || 'postgres',
      password: process.env.DB_PASSWORD || 'admin',
      port: process.env.DB_PORT || 5432,
      database: process.env.DB_DATABASE || 'konga',
      poolSize: process.env.DB_POOLSIZE || 10,
      ssl: process.env.DB_SSL || false
    }
  },

  models: {
    connection: process.env.DB_ADAPTER || 'postgres',
  },

@ldeveloperl1985 , that's the expected behaviour.
See https://github.com/pantsel/konga#note-
Tables are not created or altered in production mode.
Better be safe than sorry.

Ok thanks for info

be attention DB_URL variable in .env


[!] Unable to determine Swift version for the following pods:      - get_ip does not specify a Swift version and none of the targets (Runner) integrating it have the SWIFT_VERSION attribute set. Please contact the author or set the SWIFT_VERSION attribute in at least one of the targets that integrate this pod.

duplicated with #11

Hello,
Did you find a solution ?. I am getting the same error on iOS


Include build-essential in luarocks images

A very large fraction of luarocks modules are C modules that have to be compiled, which requires a functioning toolchain (build-essential on debian, alpine-sdk on alpine).
EDIT: actually I see you are installing and removing gcc, make etc. in the builds. maybe it would be enough to just skip this cleanup step for luarocks images?

@s-ol: I'd prefer to keep these images minimal, so that's why I didn't include the dependencies for building C modules. If you're only installing pure-Lua dependencies from LuaRocks, then you don't need those compilers or build tools, so that's why I had opted to remove them from the final images. There may also be dependencies beyond build-essential needed, depending on what specific packages you're trying to install, so that's why I thought it might be best to leave the installation of those dependencies up to the user.
But I can see how this might be a common issue, so thanks for filing the issue! I've attempted to clarify this in the README with additional instructions: https://github.com/GUI/lua-docker#installing-c-libraries But let me know if you have any other suggestions or feedback. Thanks!


#19 Add headers to the generated interaction body

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Deploying to azure?

When are you adding the tutorial on deploying to Azure?
In the meantime, is this how you would deploy?

Deploy the build folder of the react app as a static web app (per https://medium.com/@to_pe/deploying-create-react-app-on-microsoft-azure-c0f6686a4321). In this case using local git in the build folder only (as an example).
Deploy the express app as a separate web app. So at this point you have 2 web apps + the cosmos db.
configure CORS in the express web app to allow access from the react web app

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

ID: 79e0a0b9-d316-fea3-f92d-db9535ea3400
Version Independent ID: 215ec001-4569-072c-01fb-32edba90db40
Content: MongoDB, React, and Node.js tutorial for Azure
Content Source: articles/cosmos-db/tutorial-develop-mongodb-react.md
Service: cosmos-db
GitHub Login: @johnpapa
Microsoft Alias: jopapa

@richprze Thank you for your interest in Azure cloud services. Just to clarify your question, are you asking for this scenario to be added as a tutorial, in the form of written documentation, that is part of the MicrosoftDocs repository? You have the ability to contribute and can submit this content to the repository. Please see the following: Microsoft Docs contributor guide overview

I am assigning the issue to the content author to evaluate and update as appropriate.

@johnpapa Given that the tutorial is entirely in video format and dated September 2017, this tutorial could use an update.

I believe Burke Holland wrote this. GitHub on my phone won’t tag for some reason. But you can tag him here.

Yeah - I think so. What is the ask here exactly? What do we need to update in the video?

@burkeholland The customer is looking to clarify specific steps to deploy to Azure:

Deploy the build folder of the react app as a static web app (per https://medium.com/@to_pe/deploying-create-react-app-on-microsoft-azure-c0f6686a4321). In this case using local git in the build folder only (as an example).
Deploy the express app as a separate web app. So at this point you have 2 web apps + the cosmos db.
configure CORS in the express web app to allow access from the react web app

Is this not the scope of the videos?

No - the video deploys these things as one project and uses the express server to serve the React app as opposed to using IIS to do it.
Although the customer is right here in terms of having the right steps.

@richprze The steps you are wanting to be confirmed are correct. Is there anything additional you need to move forward?

@richprze We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

It is useful to have a ARM template to deploy it to Azure for real experience and customer can gradually leverage to Azure services for web hosting and further usages.
I see in some tutorials there is supported button with ARM template to deploy it like


Fix nested

Do it as browsers do:
if we are in , close tag.
if we are in , unset flag. If flag is already unset, close tag.

Merged, core/pull-requests/330


Error appears when trying to disconnect from db if any object from db is opened

System information:

Operating system (distribution) and version win 10 x64
DBeaver version EA 6.1.1

Connection specification:

Database name and version - doesn't matter

Describe the problem you're observing:
Error appears when trying to disconnect from db if any object from db is opened

Steps to reproduce, if exist:

Connect to db
Open any object for editing (F4)
Disconnect from DB

Include any warning/errors/backtraces from the logs
error_on_disconnect.log

This seems to be a side effect of #6108 (navigator tree became corrupted after incorrect object delete handling).

fixed. verified


The columns provided to material table are static, but contain functions which update on every render, resetting the table state. Provide a stable function or column reference or an row id to prevent state loss.

As soon as I'm using the render option in the columns object I'm getting following console message:

The columns provided to material table are static, but contain functions which update on every render, resetting the table state. Provide a stable function or column reference or an row id to prevent state loss.

Here is an example similar to my configuration:

import Reactfrom "react";
import MaterialTable from "@material-table/core";

const columns = [
  { title: "Id", field: "id", type: "numeric" },
  { title: "Email", field: "email" },
  { title: "First Name", field: "first_name", render: rowData => (<div>{rowData.companion1}</div> }
];

const App = () => {
  const [data, setData] = useState([]);

  return (
    <MaterialTable
      data={getData}
      columns={columns}
    />
  );
};

I'm using material-ui<EMAIL_ADDRESS>Any help welcome

Please see here.

@oze4 Thank you for pointing me into the right direction - and that so fast.

Cheers!


1.1.3: existential @var? doesn't check for undefined

This seems like a pretty minimal test case:
@a?

outputs:
this.a != null;

According to the documentation, "CoffeeScript's existential operator ? returns true unless a variable is null or undefined"
a?

correctly outputs:
typeof a !== "undefined" && a !== null;

See #1631

Whoops, didn't realise it was you. Here's a more complete explanation: X == null tests that X is either null or undefined, assuming it is in scope. If we can't make that assumption, we need to do a typeof test to avoid ReferenceErrors. Please search for old issues before posting. There has to be a dozen that are exact duplicates.

Apologies, I did search, but nothing came up that seemed relevant. There are so many closed issues now that searching through them is tiresome. Thanks for your patience.
It is disappointing that there doesn't seem to be a good solution for this issue. I was hoping to write some code that checked for null or undefined and there doesn't seem to be a good syntactic way to do that in CS.

@lookfirst: X? does check for null or undefined.
$ node
> a = null
null
> a == null
true
> a = void 0
> a == null
true
> a = 0
0
> a == null
false
>

What I'd like to do is write this:
	methodFoo:
		@saveGroup(@d.groupName.val().trim(), @key?)

	saveGroup: (groupName = '', existing = false) =>
		if existing

What I ended up having to write is this:
	methodFoo:
		keyExists = typeof @key != "undefined" && @key != null
		@saveGroup(@d.groupName.val().trim(), keyExists)

	saveGroup: (groupName = '', existing = false) =>
		if existing

Maybe I'm just not understanding things correctly.

@lookfirst: you're not understanding things correctly. @key? is fine, trust me. It produces true if the value of this.key is either undefined or null. Either one. Otherwise, it produces false. The equivalent javascript test that is being performed is this.key == null. Read up on the abstract equality comparison algorithm (section 11.9.3).

@lookfirst: Googling for site:github.com inurl:jashkenas/coffee-script/issues existential operator seems to find a lot of stuff.

Ok, thanks for the pointers. I'm understanding things a lot more clearly now. Again, thanks for your patience.

@alpha123: wow, I'm surprised how effective that is. Google's amazing. Thanks for the tip.

We should start a drinking game for every time this comes up ;)