Revoking a revoked token returns generic error message

The is the error I get back when I revoke an already revoked token.  It would be great if it gave a error to indicate the token has already been revoked.  Would be easier to handle that error.
Error: Response has an Error
at OAuthClient. (/Users/bilal/workspace/mydoma-studio-api/node_modules/intuit-oauth/src/OAuthClient.js:621:42)
at
at process._tickDomainCallback (internal/process/next_tick.js:229:7)

This is the response for revoking an already revoked error message.  Would be great if it mentioned that the token was already revoked.
Error: Response has an Error
at OAuthClient. (/Users/bilal/workspace/mydoma-studio-api/node_modules/intuit-oauth/src/OAuthClient.js:621:42)
at
at process._tickDomainCallback (internal/process/next_tick.js:229:7)

It's missing the error code in the response.

@belo32 : Is the token being revoked outside the scope of this client (is the token revoked outside your app ? )  If you are using this node client to revoke, the response should look like :
{
   "token":{
      "realmId":"realmID",
      "token_type":"bearer",
      "access_token":"revoked access_token",
      "refresh_token":"revoked refresh_token",
      "expires_in":12324255363668,
      "x_refresh_token_expires_in":12324255363668,
      "id_token":"revoked id_token",
      "latency":60000
   },
   "response":{
      "url":"https://developer.api.intuit.com/v2/oauth2/tokens/revoke",
      "headers":{
         "content-length":"0",
         "connection":"close",
         "server":"nginx",
         "date":"Mon, 15 Apr 2019 17:33:05 GMT",
         "strict-transport-security":"max-age=15552000",
         "intuit_tid":"3605978xxxxx-xxx-xxx-xxx2e89",
         "cache-control":"no-cache",
         "pragma":"no-cache",
         "expires":"-1"
      },
      "body":"",
      "status":200,
      "statusText":"OK"
   },
   "body":"",
   "json":null,
   "intuit_tid":"3605978xxxxx-xxx-xxx-xxx2e89"
}

For posterity, the client should be able to handle the error responses irrespectively.  Will handle this as part of the next release. Thanks.

Thank you,  the token was revoked during the scope of the client.  It's just the code did not handle the updating the state properly at the time and the response we were getting back from the OauthClient was not clear.

Fixed with Release 1.2.0


[Question] Generated preview image for equirectangular panoramic images.

I am looking for a tool or library that will allow me to generate a preview image for an equirectangular panoramic image.  The idea is to serve a lightweight preview images while the main image loads. I would like to have a small sized preview image that does not look warped. Does such a tool/library/script exist?
Thank you!

I'd recommend looking at Hugin. It includes an assortment of command line tools, such that you could write a script to generate preview images to your liking. There's also a GUI, if that's preferable.


Helm Release Values not being updated after initial load

When going to Releases in the Helm section to read the helm values, you are able to load the values one time, and every load after that displays the values from the initial load no matter what release you are trying to get the values from.

Open the application and go to the helm releases
Click on "A" -> Displays values of "A"
Click on "B" -> Displays values of "A", but changes the Resoureces to values of "B"
Click on "C" -> Displays values of "A", but changes the Resoureces to values of "C"

Note: Clicking upgrade shows the correct helm.
A:

B:

C:

Environment (please complete the following information):

Lens Version: Tried 6.2.1 to 6.2.5
OS: Win10

Similar to https://github.com/lensapp/lens/issues/6197


Flutter Metal support on iOS

Maybe it's a good idea to support Flutter/skia Metal renderer on iOS as it becomes popular. It may attracts new contributors if gfx-portability can provide a better avg performance than MoltenVK in some scenarios.

Thanks for filing the issue! Moved to an item in https://github.com/gfx-rs/portability/issues/125


Write Telemetry docs

Tracking issue for writing documentation about Telemetry added to YARP in #501 and its consumption (#571).

Triage: Covers E2E - incl. Runtime and ASP.NET relevant logging.


Support Docker 1.11.0

Docker 1.11.0 has been released.
I'm not sure how relevant this warning to RancherOS, but here is a note left to the 1.11.0 release:

IMPORTANT: With Docker 1.11, a Linux docker installation is now made of 4 binaries (docker, docker-containerd, docker-containerd-shim and docker-runc). If you have scripts relying on docker being a single static binaries, please make sure to update them. Interaction with the daemon stay the same otherwise, the usage of the other binaries should be transparent. A Windows docker installation remains a single binary, docker.exe.

Unfortunately it will take us maybe a month to support 1.11 in rancheros because of the various changes in 1.11.  Overall it's going to make RancherOS much better though.

I'm not in a hurry for 1.11.0. I have just noticed that it is there, and there was no place in Rancher mentioned the new release. Thus, I thought it would be good to let you know just in case you missed it.
Thank you, Rancher team, for this solid and nice-looking project which helps me to manage my small Docker cluster!

@frol the point is that get.docker.com is very aggressive in installing the always newest version and makes installing a older one not so easy. Made the experience today by trying to install the 1.10.3 mac toolbox and the first boot2docker run updates directly to 1.11. I think I don't really like this...

Yeah i wish there should be a documentation on how to install docker by version. Cos the only one most of know is running the script in get.docker.com

@lavvy: http://docs.rancher.com/os/configuration/custom-docker/

In v0.5.0, we support docker 1.11


macOS app fails to after renaming the flutter_created directory

On macOS: if I create an app with flutter create foo and then rename the foo directory, the app fails to run. Summary:
flutter create foo
(cd foo; flutter run --device-id macos) # all is well
mv foo button_examples
(cd button_examples; flutter run --device-id macos) # BUILD fails

See the transcript below for the details. I have a .tar file with the problem app if that's helpful. It's too big to attach to the issue.

```
hansmuller@hansmuller-macbookpro flutter % flutter create foo
Creating project foo...
Resolving dependencies in foo...
Got dependencies in foo.
Wrote 129 files.
All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev
In order to run your application, type:
$ cd foo
$ flutter run
Your application code is in foo/lib/main.dart.
hansmuller@hansmuller-macbookpro flutter % (cd foo; flutter run --device-id macos)
Resolving dependencies...
matcher 0.12.15 (0.12.16 available)
test_api 0.5.2 (0.6.0 available)
Got dependencies!
Launching lib/main.dart on macOS in debug mode...
2023-05-30 12:10:47.066 xcodebuild[41264:49145487] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006000-000018392121801E }
{ platform:macOS, arch:x86_64, id:00006000-000018392121801E }
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
Building macOS application...
Syncing files to device macOS...                                    58ms
Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).
A Dart VM Service on macOS is available at: http://<IP_ADDRESS>:59272/23tm4WQZX4Q=/
The Flutter DevTools debugger and profiler on macOS is available at:
http://<IP_ADDRESS>:9102?uri=http://<IP_ADDRESS>:59272/23tm4WQZX4Q=/
Application finished.
---- The app ran without any problems -----
hansmuller@hansmuller-macbookpro flutter % rm -rf button_examples;
hansmuller@hansmuller-macbookpro flutter % mv foo button_examples
hansmuller@hansmuller-macbookpro flutter % (cd button_examples; flutter run --device-id macos)
Launching lib/main.dart on macOS in debug mode...
2023-05-30 12:12:08.029 xcodebuild[41663:49147823] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006000-000018392121801E }
{ platform:macOS, arch:x86_64, id:00006000-000018392121801E }
/Users/hansmuller/flutter/foo/macos/Runner/Configs/Debug.xcconfig:1:1: error: unable to open configuration settings file
/Users/hansmuller/flutter/foo/macos/Runner/Configs/Debug.xcconfig:1:1: error: unable to open configuration settings file
/Users/hansmuller/flutter/foo/macos/Runner/Configs/AppInfo.xcconfig:1:1: error: unable to open configuration settings file
error: Unable to load contents of file list: '/Users/hansmuller/flutter/foo/macos/Flutter/ephemeral/FlutterInputs.xcfilelist' (in target 'Flutter Assemble' from project 'Runner')
error: Unable to load contents of file list: '/Users/hansmuller/flutter/foo/macos/Flutter/ephemeral/FlutterOutputs.xcfilelist' (in target 'Flutter Assemble' from project 'Runner')
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **
Building macOS application...
Exception: Build process failed
</details>

CC @cbracken


feat: update Merkle library to check height

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

14 of 14 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 90.22%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
1053

Relevant Lines:
1132

💛  - Coveralls


Aspect ratio instead of pixel amount

I have a bunch of 3:2 images that I'd like to crop at 16:9 while keeping as much of the original image as possible. I'd like to do this locally using smartcrop-cli.
Would this be possible using smartcrop.js? It would be a dream that comes true.
EDIT: Every picture has different pixel size, but the same 3:2 aspect ratio. If that's not possible with smartcrop.js native functionality, maybe with a shell script as a wrapper? 🤔🤔

It is, you can just pass in width: 300, height: 200, minScale: 1 and it should work the way you want to.

It's in the README:
  --faceDetection  perform faceDetection using opencv

Oh my...long day for me I guess. Thanks a lot.


Implement SSAO effect on renderer

Implements SSAO (screen-space ambient occlusion) effect

Beyond the effect itself (implemented in defered renderer.cpp/h), some other changes had to be made to the engine as well:

Add short/half-float texture formats (R16FLoat, RGB16Float, etc...)
Fix invalid enum constant GL_R (it should be GL_RED, source: https://stackoverflow.com/questions/41396731/in-opengl-whats-the-difference-between-the-gl-red-and-gl-r-color-formats)
Added function to pas a mat4x4 to a shader binding point
Fix overflow when reading certain cube models, leading to an infinite loop (grid.cpp)

PR ready for review :tada:


[Bug]: AC500 + 2XB300S: Battery1+2 percent and voltage are "unavailable" with Version 0.1.3

What happened?
Unfortunately, Version 0.1.1 doesn't solve the problem.
Very seldom there are values displayed for Battery1+2.
I am going back to 0.0.16, this was the last version where the voltage and percent for my 2 batteries were always shown properly.
What version of our software are you running?
0.1.1
What device are you seeing the problem on?
AC500 + 2XB300S:
What bluetooth connection are you using?
ESPHome bluetooth proxy
Have you changed the integration settings?
false
Integration settings (if you changed them)
No response
Relevant log output
There are no errors in the logs.

Still the same problem with 0.1.2.
Went back to 0.0.16

Unfortunately still the same Problem with 0.1.3.
Went back to 0.0.16

Problem solved with 0.1.4.
Thank you very much.


#367 comment out import of CacheMap for checkstyle

Comment out the currently unused import of CacheMap to stop checkstyle from failing the build

Checkstyle is now shut up, allowing  real tests to  break the  build :)

@sesuncedu Thanks. It's still in progress... ;-)

In progress is progress :) It seems like the index/indexer is getting much
more aggressive AND defensive.
On Sat, May 27, 2017, 4:10 PM Jakub Chrzanowski<EMAIL_ADDRESS>wrote:

Merged #368 https://github.com/hsz/idea-gitignore/pull/368.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hsz/idea-gitignore/pull/368#event-1099991752, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZIG1B9p-CL0UgdXrNkU445a9miH9ufks5r-IMngaJpZM4NoXPI
.


Final version???

When will we see the final npm package? The current package is 3 months old and was released before Angular 2 went final. My understanding was the final release was planned for about a month after the final release of Angular 2. What happened to that?

Are you looking at the wrong package? The current one can be found here: https://www.npmjs.com/package/devextreme-angular

Yes, apparently so. I missed that the package got renamed. I'm still using devextreme-angular2.

Are there any instructions for how to migrate from the old devextreme-angular2 package to the new devextreme-angular package. This is turning into a major pitta. Looks like the dependency are managed very different know. Our app is using jQuery as well, so we have it statically loaded as was previously required with the old package, but now it's managed as a module dependency, which is messing everything up for me. I'm trying to look at the updated examples and see what I have to remove and change etc.


The sample code on this page does not work

Even if you write the sample code according to the procedure on this page, an error occurs and it cannot be executed.
The error message is the following:
dbg_sample\calling-quickstart\app.js:1:1

1 | import { CallClient, CallAgent } from '@azure/communication-calling';
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 | import { AzureCommunicationTokenCredential } from '@azure/communication-common';
3 |

C:\Users\osamum\Documents\Job\Tech\Azure Communication Service\playGround\dbg_sample\calling-quickstart\index.html:34:5
33 |

34 |
|     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The environment was originally created here
35 |
36 |

💡 Add the type="module" attribute to the

@osamum Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@osamum You're very correct I will make some changes today. Thank you for the report.

I've made changes to the quickstarts to add the type="module" where it is needed.
I'll also be updating the samples repo with these changes soon


minimum set of changes for using internal vendor pip.

Thank you for contributing to Pipenv!
The issue
I noticed this through a number of issue reports that sometimes a user's local pip conflicts with pipenv's expected behavior.   To me, it does not make sense that we do not always use our patched vendored pip to install certain types of packages.   With this change it should be possible for a user to only install pipenv and not have pip installed at all.   There is nothing wrong with having both installed, but why have pipenv require it and rely on it when we go to the work to patch an vendor in the latest and greatest pip?
I will rename notpip to pip in a follow-up PR.

Declining in favor of branch based on this one that also had to vendor in pip 22.2 to get this last failing test passing:  https://github.com/pypa/pipenv/pull/5196


Use go 1.18 in tests

Signed-off-by: David Cassany<EMAIL_ADDRESS>

I am not entirely sure this is the best approach but seams to work. Essentially I could not find why in ginkgo and gomega docs they stick with the go get instead of go install. I could see some back and forth in their docs around the two recently due to some people having issues with go1.18, but I could not see any reasoning on why they still stick with go get for omega... 🤷🏽♂

I am not entirely sure this is the best approach but seams to work. Essentially I could not find why in ginkgo and gomega docs they stick with the go get instead of go install. I could see some back and forth in their docs around the two recently due to some people having issues with go1.18, but I could not see any reasoning on why they still stick with go get for omega... 🤷🏽♂

I think go install is meant to install binaries, while go get just downloads the given package.
So the main difference is that go install will look for a main module to compile it to binary while go get just ignores if there is a main module. Thus gomega which is just a matcher does not contain a main module so it can be installed by go install
Now, I dont understand why when you install ginkgo, gomega is not build as part of it if it has it as a dep, nor I want to understand go deps anymore. Its all just a mess. We should probably use the go run github.com/onsi/ginkgo/v2/ginkgo from the tests dir so it uses the versions in the go.mod, although Im not even sure that will fix it.

I think go install is meant to install binaries, while go get just downloads the given package.

Yes, understand this is the case for go1.18. Prior that I think go get also used to build binaries, starting from g1.18 go get is no longer building the binaries, this is what I understood. Probably we can drop the go install for gomega...

We should probably use the go run github.com/onsi/ginkgo/v2/ginkgo from the tests dir so it uses the versions in the go.mod, although Im not even sure that will fix it.

I think we are already doing that 🤔

I think I will run a separate PR to try to better fix it, if not we can just merge this as it seams to work for now and it is a simple change.

closing in favor of #1638

closing in favor of #1638


Added warning

Added warning about repo not being maintained
@horeaporutiu Can you approve this if it's correct?

@horeaporutiu OK. I see that you added a warning in the Watson Viz Rec area, so I'll close this.

@horeaporutiu OK. I see that you added a warning in the Watson Viz Rec area, so I'll close this.


Datagrid[EditableCells]: edit icon should not always be visible

What package(s) are you using?

[X] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description

Describe in detail the issue you're having.

Discussed during design review with Virginia, the edit icons should not always be visible. Instead, they should be visible on hover, focus, or if the cell is in an active state.

Is this issue related to a specific component?

Datagrid, useEditableCells

What did you expect to happen? What happened instead? What would you like to
see changed?

Expect icons to not always be visible, creates visual overload

What browser are you working in?

Chrome

What version of the @carbon/ibm-products (or @carbon/ibm-cloud-cognitive)
package are you using?

Latest

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

N/A
Steps to reproduce the issue

View current editable cell storybook example

Fixed in @carbon/ibm-products: 2.12.1


[CHALLENGE SUBMISSION] - Day 20

Please provide the following information for your submission:
What is your name? (First, Last)
Stuart Leaver
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/stuartleaver/25-days-of-serverless/tree/master/20-iot-with-cognitive-services
What Challenge is this for? (Challenge number between 1 and 25)
20
(Optional) Anything else we should know? e.g., language used, location, blog post?
HTML Webcam (HTML & JS), Azure Function (C#), Computer Vision Cognitive Service, Notification Hub, Android Mobile App (Xamarin)

The unthinkable has happened: after weeks of community members all over the globe chipping in to help solve people's problems with serverless technology, the evil grinch's heart is starting to soften! He's still not quite ready to give up his server-stealing plot, but our whole Azure Cloud Advocacy team is flying up to the grinch's lair to help convince him to change his ways.
As such, the team behind 25 Days of Serverless is OOF (Out Of Facility/Office) between Dec 24, 2019 and January 1, 2020. We'll not review Issues in this period of time, but encourage you to catch up on any challenges you haven't had the time to work on yet. 😄 Our Discord Server is a perfect place to reach out to for community support during this time. After our return, we'll add contributors who submitted a working solution as an Issue to CONTRIBUTORS.md file until January 15, 2020.


Reduce boilerplate

Summary
Previously each serverless function was mostly boilerplate, making them more difficult to work with and read. This also increased the friction for a developer adding new functions to the project.
Added two wrapper functions that take all of the boilerplate and move it to a single spot:

prepareStudioFunction - validates that required parameters are provided, sets up the response object with the appropriate headers, and provides an error handling function
prepareFlexFunction - the same as above, plus the Flex TokenValidator

These wrapper functions are used in the exact same way we typically used TokenValidator, wrapping the entire handler function. Now, functions behave exactly the same but are significantly easier to read and write. Here is an example, get-call-properties:
const { prepareFlexFunction } = require(Runtime.getFunctions()["common/helpers/prepare-function"].path);
const VoiceOperations = require(Runtime.getFunctions()[
  "common/twilio-wrappers/programmable-voice"
].path);

const requiredParameters = [
  { key: "callSid", purpose: "unique ID of call to fetch" },
];

exports.handler = prepareFlexFunction(requiredParameters, async (context, event, callback, response, handleError) => {
  try {
    const { callSid } = event;

    const result = await VoiceOperations.fetchProperties({
      context,
      callSid,
      attempts: 0,
    });

    const { success, callProperties, status } = result;

    response.setStatusCode(status);
    response.setBody({ success, callProperties });
    callback(null, response);
  } catch (error) {
    handleError(error);
  }
});

As part of the change, I decided to axe the scriptName parameter we were passing around in favor of context.PATH. This provides a few benefits:

context.PATH provides the function name and its path in the project structure
Fewer parameters to pass around to every Twilio wrapper function; we were already passing context around
Developers don't need to remember to name their handler function, which was easy to overlook

Checklist

[x] Tested changes end to end
[x] Added PR Label "ready-for-review"
[x] Requested one or more reviewers for the PR

One request, if you have not already done so, can you make sure the retry handling works correctly?

It looks like retry handling is working the same as it is in the main branch.

Tested without fix and observed the same issue on v1 (using dialpad-addon plugin) and v2 Flex. I did notice that if customer comes off hold after third participant is added, and then later drops, the conference remains - so there’s a degree of workaround in place already, albeit simplistic. But if customer drops while on hold, the conference does indeed end unceremoniously.
Having this additional level of workaround (and having it be opt-in) is another great value add to customers that might want it. And I’m sure anyone who sees the README and tests it will want to switch it on. Great addition.
npm ci is taking an age to run for me, so I'll test the new code and complete review tomorrow :)

Deleted my old comment which was for PR80 not 82 :)


fix Visual Studio/Visual Studio for Mac

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


image_types_ostree.bbclass: add fakeroot varflag to prepare_ostree_ro…

…otfs
Since the ostree rootfs is generated by fakeroot, we should make
prepare_ostree_rootfs run with fakeroot as well, or else we might run
into a pseudo abort issue when removing OSTREE_ROOTFS directory.
Reference:
https://wiki.yoctoproject.org/wiki/Pseudo_Abort
Signed-off-by: Ming Liu<EMAIL_ADDRESS>

I don't understand what's going on here. Where does fakeroot get involved with ostree, and if it is necessary to change this task, why wouldn't we need to change all the others, too?
@aodukha Please take a look and see what you think.

@pattivacek @aodukha I would like to explain some details here.
All the updater image tasks ostree/ostreecommit/ostreepush/garagesign run under fakeroot, this is done in https://github.com/openembedded/openembedded-core/blob/master/meta/classes/image.bbclass#L494
So we need let their prefuncs/posfuncs (currently only one: prepare_ostree_rootfs) also run under fakeroot, or else it may run into the problems described in https://wiki.yoctoproject.org/wiki/Pseudo_Abort
I have observed this issue when I added meta-security/meta-integrity, and have verified it could be fixed by this patch.


Stream stopped all of a sudden

What version of Music Assistant has the issue?
2.0.0b116
What version of the Home Assistant Integration have you got installed?
2024.3.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
After some time of flawless playing the stream stops on my hardware receiver. In MASS the stream is still playing.
How to reproduce
It happens from time to time but mostly after several minutes of playing an album. The below output was roughly after 20min of starting the album.
Music Providers
Tidal
Player Providers
AirPlay
Full log output
2024-03-19 22:32:14.785 WARNING (MainThread) [asyncio] child process pid 339 exit status already read:  will report returncode 255
2024-03-19 22:32:23.286 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)                                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data aiohttp.http_exceptions.InvalidURLError: 400, message:
  Invalid char in url query:
    b'GET /imageproxy?pa\x07 HTTP/1.0'

                    ^

Additional information
No response
What version of Home Assistant Core are your running
2024.3.1
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Linux

Please actually read the troubleshooting page inthe docs and resubmit this meeting the requirements


fix(presenter): restrict height of notes area

Resolves #1172

@antfu a simple fix to resolve a lot of notes impacting the presenter display area.


hhalignment.cpp:3539: MergeMasterSlave error

I have generated more than 20,000 structures with alphafold, now running alphafold 2.2.1, but have three particular protein sequences, Ashbya gossypii proteins AFL131W,  ADL346W, and AGR113W, where alphafold fails, and I get the following error message. This problem also occurred when running alphafold 2.1. While these proteins are on the large size, I have generated hundreds of structures for proteins larger than these.
The brief version of the error message is:
...
I0721 07:22:02.937924<PHONE_NUMBER>58240 run_docker.py:256] - 11:21:59.174 ERROR: Error in /tmp/hh-suite/src/hhalignment.cpp:3539: MergeMasterSlave:
I0721 07:22:02.937985<PHONE_NUMBER>58240 run_docker.py:256]
I0721 07:22:02.938046<PHONE_NUMBER>58240 run_docker.py:256] - 11:21:59.174 ERROR: 	did not find 243 match states in sequence 1 of SRR5579859_7281350. Sequence:
...
Two problems.

How to fix this problem.

Why is the term "MasterSlave" used in the code? I personally find the term offensive and inappropriate to use in the code at all, and particularly to use as an output message.

linked below is the more complete error message:
AGR113Wnohup.txt

Could you raise this issue with the authors of the HH Suite? HHAlign is part of HHBlits, which is a third party protein sequence search tool that we use within AlphaFold. This is also the reason the problematic term is used in the code - it is not in code that we produced.

Is it possible to re-open this issue? it seems to stem partially from the way alphafold launches hhalignment

Hi, I have tried to model different multimers but only on 1 a got an error. The AF2 multimer version is 2.3.1 and I got this error:
ERROR: Error in /opt/conda/conda-bld/hhsuite_1645696999782/work/src/hhalignment.cpp:3539: MergeMasterSlave:
ERROR:   did not find 240 match states in sequence 1 of SRR5262245_40669095.
Does anyone know how to solve this issue?

Hi, we are also having this same issue - I agree maybe worth reopening? In the HHsuite issue connected to this they say

The multi-database feature of HH-suite seems the be the problem. If you search against the Uniref30 and the BFD separately it works without crashing. Please do not use this feature.

is AlphaFold still using it?


Consider reusing grin dockerfile

https://github.com/mimblewimble/grin/blob/master/Dockerfile
Instead of maintaining your own.

Agreed, did it.


Add colorMode setting

Add colorMode setting in defaults / config.

'none': no change in behavior, default
'auto': ask platform to supply colorMode
'light': light mode
'dark': dark mode

The colors for light and dark mode are defined in defaults.colors['light'|'dark'].
Resolves #8658
Caveats:
The resolution order is not optimal, because it comes before all other defaults = before defaults.datasets.line for example.
TODO:

[ ] docs
[ ] types

Filename
Size
Change

dist/chart.esm.js
67.4 kB
+246 B (0%)

dist/chart.js
85.4 kB
+320 B (0%)

dist/chart.min.js
60.9 kB
+228 B (0%)

dist/chunks/helpers.segment.js
19.1 kB
+77 B (0%)

Maybe it would be better to just add couple of lines to the docs.

I think this should be documented instead. So I'll close this.


Delete Stale Branches

This repo has way to many stale branches, please remove them

DO you not wanna remove the useless branches?

they are just sitting there


separate-debug-symbols option only honored on the CLI but not in Cargo.toml metadata.deb table

The README documentation does claim the option can be used there and the code has a field in CargoDeb but when it is used in main.rs process() only the one from CliOptions is used.

That's unintentional. Could you make a PR with a fix?


removed fancy default for pan-y

There was built into the default touch-action: "pan-y" a special case to effectively turn it into touch-action: "none" when the modelviewer element was fullscreen. However, this doesn't work well at all for iframes and it's honestly a little confusing anyway. From now on, if you know your page doesn't need to scroll, you'll have to remember to set touch-action: "none" manually.

FYI @mqg734


Fix #412: Quote tweet content not translated

Fixes #412
Changes Summary

Add data-tweet-suffix
Automatically update tweet link after load.
Include script in homepage.

This pull request is ready for review.

This does not work on page first load, you have to refresh on the language for it to take effect. The bigger issue being that with the translated text, it will usually be greater than twitter's character count limit.
Also, it seems weird to be doing this client side instead of with php, but that's just opinion.

It works on first page load for me, I don't see any reason why it wouldn't unless your browser had just cached the page. I should probably truncate the quote right? or just tweet in english?
I don't want to do this in PHP because it means more fiddling with the DOM when translating, and that area is already a mess as it is. We have other scripts that modify links on page load.

Ready for another review.

I adjusted it a bit so '…' would be inside the quotes. LGTM for me

Awesome, can we approve each others bits?


Unknown flag: '-t' error on Arch

Installed tealder with cargo install tealder, but no matter what options I use it provides me the same output
Unknown flag: '-t'

Verified also on latest Manjaro with the same result and AUR version.

I cannot reproduce this issue. I suspect it has something to do with your shell completions.
What shell do you use, and if you installed the package through cargo, did you manually install any completions for it? Maybe completions for a different tldr client are installed?

@dbrgn Thaks for the help it was really my alias in bash to use specific color theme for NodeJS tldr client that I've used before.


Dosen't work as expected

First of all, thanks for writing this plugin. It is an excellent work.
I'm using Redux for managing states, so I wrote like this:
// .jsx
                <Editor
                  editorState={editor.editorState}
                  onChange={actions.onSaveEditorState}
                  plugins={editor.plugins}
                />

// reducer
const defaultState = {
  editorState: EditorState.createEmpty(),
  plugins: [createMarkdownPlugin()]
};

  if (type === UPDATE_EDITOR_STATE) {
    newState = {
      ...state,
      editorState: payload
    };
 else if (type === UPDATE_EDITOR_CONTENT) {
    const text = fs.readFileSync(payload, 'utf8');
    newState = {
      ...state,
      editorState: EditorState.createWithContent(
        ContentState.createFromText(text),
      ),
      plugins: [createMarkdownPlugin()],
      currentFile: payload
    };
  }

It dose not work at all. The editor.plugins properly contains draft-js-markdown-plugin plugin in .jsx but it does not work. What is wrong with my code?

You're re-creating the plugin on every render, I think that might be it? Try instantiating it once in a variable and then passing that in plugins

@mxstbr Well, I re-wrote like
const markdown = createMarkdownPlugin();
const defaultState = {
  editorState: EditorState.createEmpty(),
  plugins: [markdown]
};

But it's the same


Ticking Loop Server Crash

http://pastebin.com/QYfnVewR

Fixed in dev

so the new update should fix it

Yup 1.1.3

thank you so much for the help
On Fri, Jan 27, 2017 at 9:23 AM, Ollie Lansdell<EMAIL_ADDRESS>wrote:

Yup 1.1.3
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SonarSonic/Flux-Networks/issues/46#issuecomment-275690466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASlyxRLhOfa3agM3ZlT4gTnqIG3oE9r4ks5rWgvagaJpZM4Lvwrt
.


Initial structure for RLS

This change is

@haberman, can you advise as to the right way to do that? The upb header file isn't all that clear on how to detect an error:

You are correct, the encoder returns -1 on failure. This should definitely be better documented and we should have a named constant for this at least.


Complete the Alumni

Please expand this issue!

i will do this. but Also want details of  alumni page(new members).

@yohanym95 could you speak to @hasitha95 or Tharika. Either of them should be able to give you the details.
This issue comes with the JSON port as well. So all the information should stored as a JSON file!

@Piumal1999 and @jayasanka-sack still didnt get a complete one to this issue.

Thanks a lot! @yohanym95

I added changes to this on the Trello board @Piumal1999

@jeevanthask How much progress have we made?


Add rust-toolchain file

Proposed changes

Having a rust-toolchain file at the root of the project will ensure that any cargo commands executed will use that rust version. This is particularly useful for cargo clippy.
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Too many a times I run cargo clippy and see so many warnings and then realise my cargo clippy is 1.65.0
But this is useful not only for cargo clippy but also build, test, fmt, etc


FSLeyes integration - Change the way active overlays are determined

TODO : Check which overlays are "Displayed" (with the eye icon). Those will be the active images/masks.

With commit e3ae8dd9d82000b7ed6c3ef59d92e097c6b0065c , there is now an option to load existing segmentation masks. (I didn't reference the issue correctly in the commit message).
The active masks are those that are "Displayed" (eye icon). If a mask has "axon" in its name, the script recognizes it as an axon mask. If a mask has "myelin" or "Myelin" in its name, the script recognizes it as a myelin mask.
TODO: applying a prediction model should also use the currently visible histology image.

With commit 87f72ee , the active microscopy image is also determined by visibility status.
Note that the microscopy image must NOT have the following keywords in its name:
axon   myelin   Myelin   watershed   Watershed. Otherwise, it will be considered as a mask.


Enhancement Request: Customizable RestartPolicy for kpack Build Pods

Context
I am eager to propose an enhancement to the kpack open-source project that allows users to have control over the customization of the restartPolicy for kpack Build Pods. Presently, the restartPolicy is not adjustable and is fixed at Never, which may not always align with the diverse requirements of our open-source community.
The capability to customize the restartPolicy for Build Pods would significantly enhance flexibility and management control in different use cases. This enhancement would empower users to fine-tune the behavior of Build Pods according to their specific needs. By doing so, we can effectively address scenarios where Build Pods fail due to issues like image repository unavailability, thus improving error handling.
Example Scenario
In my own experience, I've been utilizing kpack in conjunction with the AWS ECR controller to initiate the creation of a repository on Amazon Elastic Container Registry (ECR) for images about to be built. Occasionally, there are timing discrepancies where the repository gets created slightly later than the Build Pod expects it to be available. This situation results in Build Pod failure at the prepare phase.
It would be highly beneficial, if the restartPolicy of the Build Pod could be customized or, at the very least, set to OnFailure as a default option. This customization or default setting adjustment would enable reiteration in case of failures, enhancing the robustness and adaptability of the kpack project for a broader range of use cases.

My main concern with this would be perpetual retries even for issues that should be terminal like compilation failures. We have been tossing around the idea of retrying particular steps of the build as opposed to the entire build. How would you feel about something like that.

Can we expect this support anytime soon in the coming release?

I think the next step would be an rfc proposing the change since this will be a pretty fundamental change. I am not sure exactly when we plan on doing it, but it is something we are actively thinking about prioritizing. We would also happily accept an rfc if this is something you'd be interested in


subscriptions-- add should default to upsert

since id is a UUID, when a subscriber calls add it should really first try and update, and then ad insert.
Or, maybe we provide an upsert handler?
And remove the current add/update handlers?
The question is-- will anyone ever want to have the same id twice in a series?
And I think the answer is no. Cashay doesn't allow it with pagination, it shouldn't allow it here.
Popular sites like facebook might show the same story twice, but I think that's them goofing up, it's not like they wanna do that.
i don't wanna see a facebook post of a cat trying to eat a wheel of cheese twice.

updated in v0.16.0


Tile name validation doesn't seem to be working in tilemap editor

You can assign tiles to have invalid names in the tilemap editor. Specifically, you can assign names of other tiles (which causes weird bugs) and you can add whitespace at the ends of the name making it impossible to use in your project.
Reported on the forum here: https://forum.makecode.com/t/heart-animation-not-working/6376
To reproduce one version of this:

Create a new project
Create a tilemap and a custom tile
Change the tile's name to end in a space
Try to use an "array of all [tile] locations" block with your custom tile selected
Refresh, the tileset editor turns into a grey block

Another version of the same bug:

Create a new project
Create a tilemap and two custom tiles
Change the second tile's name to be the same as the first
Try to use an "array of all [tile] locations" block with your second custom tile selected
Refresh, the tileset editor changes to the first tile

Fixed!


Fix typo

+1

+1

thank you @enriquez! thought we fixed that already with the last PR by @Pmant.
version 1.1.6 is available via npm :)


Coloredconsole not compiled regex by default

Added CompileRegex option, false by default. If false the Regex Cache is used.
Some small performance improvements

fixes https://github.com/NLog/NLog/issues/764

Current coverage is 73.41%

Merging #1171 into master will decrease coverage by -0.02% as of 0e43c9f

@@            master   #1171   diff @@
======================================
  Files          265     265
  Stmts        14977   14996    +19
  Branches      1643    1646     +3
  Methods          0       0
======================================
+ Hit          10998   11009    +11
- Partial        418     421     +3
- Missed        3561    3566     +5

Review entire Coverage Diff as of 0e43c9f

Uncovered Suggestions

+0.08% via ...nternal/AspHelper.cs#206...218
+0.08% via ...nternal/AspHelper.cs#188...200
+0.08% via ...nternal/AspHelper.cs#170...182
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Is someone would review this, that would be great :)

How about supplementing one of the tests to test with both true and false values for this property?

Thanks @bhaeussermann !

Review notes applied!

It looks good to me! Will you update the Wiki? Then I'll merge.

done https://github.com/NLog/NLog/wiki/ColoredConsole-target


(chore): de-dupe axum

0.6 is pulled by opentelemetry-otlp -> tonic

Can you rebase, there are fixes to address some of the current tests (rust 1.66 made clippy fail).
There will probably be more issues due to the version change.

Tests are fixed locally - let's see if CI agrees!


Upgrade controlplane to a more powerful node

/kind bug
Hi, I am asking myself, what would be the best way to upgrade the control plane server?
cx21 -> cx31
I've created a helm chart for this:
Before
control_plane_machine_count: 1
hcloud_control_plane_machine_type: cx21

After
control_plane_machine_count: 1
hcloud_control_plane_machine_type: cx31

But upgrade of the helm chart had not the intended effect of migrating everything to a cx31 server.
Environment:

cluster-api-provider-hetzner version: v1.0.0-alpha.11
Kubernetes version: (use kubectl version) 1.23.4
OS (e.g. from /etc/os-release): fedora-35

Please have a look on this helm chart: https://github.com/syself/charts/blob/main/charts/capi-cr/templates/controlplane.cluster.x-k8s.io/kubeadm_control_plane.yaml#L18
Here you will see that a new HcloudMachineTemplate is created and the reference is changed. In general more information on: https://cluster-api.sigs.k8s.io/tasks/upgrading-clusters.html#upgrading-the-control-plane-machines

@batistein Thanks for the quick answer.
I haven't picked your helm chart yet, because the templates are older than the templates from cluster-api generate.
Nice article, I'll try out and increment the KubeadmControlPlane spec version :+1:

@batistein Okay, I fetched the HCloudMachineTemplate from the cluster.
testcluster-control-plane.yaml
then I renamed the Object to name testcluster-control-plane2 and changed the image to type: cx31
I applied the resource to the cluster.
After that I changed KubeadmControlPlane to point with the infrastructureRef to the new HcloudMachineTemplate testcluster-control-plane2.
After that it worked!

Thank you very much for the feedback! I will close that issue then.


Add missing alias for xnor on bitop

While at it, does it make sense to also add aliases for andn1, andn2, orn1, and orn2?


theme-selector: Subclass AdwBin

One has to manually remove the child of a Widget subclass, Bin takes care of this for us.

Thanks.
I think ThemeSelector was a director port from the one in GTE - I wonder if it stills suffers from the same problem.

A simpler solution is to call gtk_widget_unparent on the child on dispose,but I have no clue how to do it on gsj.


[ingestion/clearlydefined] clearlydefined fails to run when the osv certifier has already run

Describe the bug
clearlydefined fails to run when the osv certifier has already run. This occurs because root package query checks if certifyVulns are already collected and skips the package. This should not happen when the clearly defined certifier is run.
Question is, should this check be removed? As we want the certifiers to run on OSV and clearlydefined on various intervals, re-adding new vulns or licenses as they are found. The check was only added to prevent the certifier from running again manually and adding duplicate vuln nodes. This, in the long term, is actually what we want to happen in GUAC as we know that the information is up-to-date.

Expected behavior
Add all the license information based on clearly defined.
GUAC version
v0.8.0

Removing the check seems like the right call. If it's preventing certifiers from running, that defeats the purposes of certifiers.

Removing the check seems like the right call. If it's preventing certifiers from running, that defeats the purposes of certifiers.

To add more context and looking back at the code, we need to keep the checks to determine when the last scan occurs so that the certifier can determine if a re-scan needs to happen again (based on the interval set by the user).
I need to think of a better approach for how we want to handle this.

After further thought, we can remove daysSinceLastScan as it is redundant with the certifier interval. This will also reduce the load on the DB as neighbors will not need to be called. Plus with the addition of:
# query vulnerability during ingestion
add-vuln-on-ingest: true

# query licenses during ingestion
add-license-on-ingest: true

This will keep the license and vulns up to date.


Cleanup, micro-refactor, add tests

Delete _AliasTable

RegressionTests is almost entirely clean with one presumed false positive.


Tractability heat map on target profile page not highlighting correct cells

Observed Behaviour
On the target profile page for VCP, the tractability heat map shows that the target hits the following buckets:

In the image, it looks like the target hits buckets 5, 6, and 8. However, according to the .TSV file from Chris and the API response, it should hit buckets 4, 5, 7, 8.
Expected Behaviour
The heat map should correctly render the data from the API response and in this case, highlight the PDB targets with ligands, Active compounds in ChEMBL, DrugEBIlity score 0 to 0.7, and Druggable Genome cells.

Hi Andrew, yes the bucket-column mapping there is incorrect.
This is fixed for the new release (i.e. v2 of prioritisation view + batch search) but I can cherry-pick the commits and push that with next mini-release:

Pushed mini-release with the fix.

I've come across another example of inconsistency between UI and API response for small molecules:
API response:

SM: 4, 5, 7, 8

UI rendering:

SM: 4, 5, 6, 8

It turned out this is not a bug. Thanks @andrewhercules for the explanation.
The correspondence between buckets and cells highlighted in purple in the UI is a weird one and confusing when compared to the API response.
The order of the cells in the table is
bucket 1
bucket 2
bucket 3
bucket 4
bucket 7
bucket 5
bucket 6
bucket 8
We will convey this into our docs/Chris' blog post as users may assume the order of the cells in the UI is bucket 1, 2, 3, 4, 5, 6, 7, 8.
It may be worth showing in the UI which cell corresponds to which bucket.
Also, buckets 9 and 10 from the original paper have been either dropped or are not shown.


[docs][base-ui] Stretched multiline input overflows the demo container

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
https://mui.com/base-ui/react-input/
https://github.com/mui/material-ui/assets/105445488/3ccbe443-688b-452c-be11-b23368facfdb
Current behavior 😯
No response
Expected behavior 🤔
No response
Context 🔦
The width should be under the range of parent div element.

  Output from `npx @mui/envinfo` goes here.

can i start working on this issue or it is fixed ?

@michaldudak @oliviertassinari I have updated follow your comment and fix this bug https://github.com/mui/material-ui/pull/39201#issuecomment-1741121092
Pls check my PR https://github.com/mui/material-ui/pull/39182


Maximize png compression for reference images

After this PR https://github.com/Mapsui/Mapsui/issues/2572 it made sense to also change our compression when saving reference images to disk. However, even when using the maximum png compression of skia the images are bigger than they were after the previous PR: A total size of on disk of 72.5 MB instead of 62.5 MB.  This is not a big problem. Over times, when we need to update reference images, the total size on disk will grow again. Also, when we copy an image over an optimized image the binary will not be the same anymore.

When I use WebP the total size on disk is 55.9 MB. That might be worth it. But the should rename the files to .webp too.

I agree with the webpage renaming the generated webpage images are lossless so no artefacts should be introduced

I am also thinking about not putting the images in the repository at all to reduce the data. One thing I am worried about is that if we checkout a branch we get all the diffs, also of the images, this means that over time if we keep updating the images the repository will grow even if we do not increase the number of images. I assume that is how git works, did not read up about it, and chatgpt agrees.
An alternative could be to write the reference images to a docker and in our code point to a specific version of that image. If we update the reference images we need to update the image. That way we won't have a history of image diffs in our repository.

You can make a shallow checkout on hit which will only fetch the files of the requested branch without history.
https://stackoverflow.com/questions/68933323/git-shallow-checkout-a-remote-branch

But that is what every person would have to do individually, right? Random people cloning the repo would not do this.


Create Wallet page

WIP - create wallet page (https://github.com/busyorg/busy/projects/6#card-5213698)

Can you put white background on these frames?

Looks like the icons Steem Power and Steem Dollar are reversed
Can we have the values in Saving on the same line like this:

1: Can you change the icon and background with the same color than Paresh design?
2: Can you put any amount aligned on the right? (include claim reward amounts)
3: For claim reward, can you hide the 0 amounts? And change VESTS to SP

Numbers should be a formatted number like 1,300.000 STEEM similar than others number in the interface

Also can you use 22px size for icons? Include balance icons, and change the icon for claim operation to success_fill icon?

@Sekhmet can you review when you have time? Thanks!

@Sekhmet Made updates based on your suggestions, whenever you got time could I get another review? Thanks!

@jm90m can you change the url for the wallet to /wallet instead of /@fabien/wallet?

Everything else looking good for me to merge, well done!

@bonustrack just updated it to use/wallet


Support overloading functions

Hi, I found that postgraphql doesn't support overloading functions，the minimal reproduce case is
create schema test_a;

create function test_a.overloading_function(text) returns integer as $$
  select 1 + 1
$$ language sql;

create function test_a.overloading_function(text, text) returns integer as $$
  select 1 + 2
$$ language sql

Please inform me if I  had missed that in document, or would you consider to put it on schedule?

An easy temporary workaround for this is to define aliases for these functions; e.g.
create function test_a.overloading_function__text(a text) returns integer as $$
  select test_a.overloading_function(a)
$$ language sql;

create function test_a.overloading_function__text__text(a text, b text) returns integer as $$
  select test_a.overloading_function(a, b)
$$ language sql;

My knowledge of GraphQL is still extremely superficial, but I think because of the type signatures in GraphQL (where each argument is named and typed) we can't represent overloaded functions that take different types as would be the case for generic overloaded functions. So if we were to support this internally we'd have to derive function names (like those in my example above) for the different overloadings. Then we'd have a challenge as to how to make these predictable, non-confusing and worst of all persistent. e.g. if we started with the two argument version test_a.overloading_function which we'd just call overloadingFunction when you add the second function which takes just one argument it would trigger the "overloading" logic and both functions would rename which would break backwards compatibility.
Do you have thoughts on how we might solve this @lcjnil?

@benjie Thanks for your reply!
Your workaround does a good idea, but still hard to use. More to say, I am trying to wrapper a function to support both jwt.claims.* as well as token which is used in token-based authtication (not jwt), perhaps overloading function is the easiest way to do that, or I need to write wrappers like you.
Though, my knowledge to graphql is quite naive, and I can't figure out a way to resolve it, but I do think your workaround should be placed in document.
Thanks again.

I’m going to re-open this, because I do feel like it’s a space we can explore. I haven’t looked into this too much, but I get the feeling that if we have named arguments we may be able to intelligently create a GraphQL field for overloaded functions. It’s not a high priority though, so aliases are probably your best bet for now like @benjie suggests :blush:

If I may , I have one more question .I am trying to use plv8 , to write
functions in Postgres , to be queried by Postgraphql .
When giving it complex arguments , as array of objects , it does not work
at all .
For example I get "message": "ReferenceError: sort_By is not defined", even
if I send him a sortBy parameter  .
I am trying actually to build function that replaces the default orderBy
because I need to have only one function that does search and order on the
server , to be used with a grid .
Can you kindly  tell me what am I doing wrong ?
Thank you ...
create or replace function sortAndOrder(start int, page int, filter_By
filter_By[], sort_By order_By[]) returns setof abc.relations as
$$
plv8.elog(NOTICE, sort_By);
if (typeof filter_By == "undefined") {
var sort = [{field: "naam"}];
if (typeof sort_By == "undefined") {
    var query = "select * from abc.relations ORDER BY naam DESC limit "

start + "OFFSET "+ page ;
var a = plv8.execute(query);
return a;}
}
$$
language plv8 stable;

create or replace function sortAndOrder(start int, page int, filter_By
filter_By[], sort_By order_By[]) returns setof abc.relations as
$$
plv8.elog(NOTICE, sort_By);
if (typeof filter_By == "undefined") {
var sort = [{field: "naam"}];
if (typeof sort_By != "undefined") {
    var query = "select * from abc.relations ORDER BY  ' +

sortBy[0].field +"  DESC limit  " + start + "OFFSET "+ page ;
var a = plv8.execute(query);
return a;}

}
$$
language plv8 stable
"message": "ReferenceError: sort_By is not defined",
On Mon, Jan 29, 2018 at 10:22 AM, Benjie Gillam<EMAIL_ADDRESS>wrote:

There has been no change on this front.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/postgraphql/postgraphql/issues/284#issuecomment-361171263,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgsnU8vkmamisYndYdq4_6RkjkXSBQ74ks5tPX_CgaJpZM4LQlWt
.

SQL is case insensitive, you've not wrapped your identifiers in quotes so when they come through to plv8 they will be seen as filter_by, not filter_By.
Please write further issues into GitHub directly and wrap your code snippets in triple backticks to make them more legible - reading the formatting from email is a nuisance.


Readme

Readme edited

Hey dev,
Please make your repo hacktoberfest accepted.
Thank you
Ruben Abraham Shibu
On Sat, 2 Oct 2021 at 16:09, HUMANORE @.***> wrote:

Merged #2
https://github.com/cg-humanore/STONE-PAPER-SCISSORS-GAME/pull/2 into
main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cg-humanore/STONE-PAPER-SCISSORS-GAME/pull/2#event-5398022249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDY6UG3QJS4BYHHN5QVZXTUE3OMXANCNFSM5FGIFT7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


delete_table shows result data as insert_table

In mission control, while previewing mutations, this is what is shown to us

I believe that the right hand side should also be delete_table.
I also think that this is due to this code in utils.js/generateQueries :
queries.delete.res = removeRegex(`{
      "data":{
        "insert_${colName}":{
          "status": 200
        }
       }
      }`, 1)

Thanks @ShubhankarKG. This is fixed in v0.19.0 plus many more exciting features to come inside that queries page in v0.19.0 like a play button 😀
Also spaceuptech/space-cloud is the repo where we create all issues now. Be it regarding mission control or docs or gateway


Feature Request: Mob Blacklist

Hello! Was wondering if it was possible to have a blacklist implemented.
Some some modded mobs don't behave as intended when they get boosted by the mod, simply removing the ability for them to get effects would solve this issue.

Added in latest update to 1.19!


UI Improvement

Is there an existing issue raised for this?

[X] I have searched the existing issues

Description:
Hey, some section text is not visible properly you can see below. Can you please assign this task to me under GSSOC'23?
Reason for Change:
Better user experience
Current Styling:

Also, there is a conflict between two-component

Proposed Styling:
It should look like this
![image](https://github.com/UBA-GCOEN/StichHub/assets/94003231/68588f26-5798-457d-bda2-99452eef8370
Screenshots or Design Mockups (optional):
No response
Tick the appropriate boxes as per your choice

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

Hey @SubhamB2003 Go ahead with it


[build-script] Use a single-threaded runner for the lldb tests

The multithreaded runner has been reported to issue "Connection refused"
failures for unclear reasons.
rdar://37173570

@swift-ci smoke test and merge

We.. appear to ignore --skip-category when --no-multiprocess is set? And also there are pexpect()-related issues.

The pexpect-reliant tests have either been removed from swift PR testing or rewritten using lit (rdar://36628021). This should no longer be an issue.


Code completion doesn't work for service resource annotation

Description:
See below

Closing this issue as this was due to error code before this line.


toolchain.info creation error on msvc14 with toolset LLVM-vs2014

When compiling with toolchain LLVM-vs2014 hunter throws an internal error
$ cmake -H. -B_build_llvm -G "Visual Studio 14 2015 Win64" -T "LLVM-vs2014"

hunter-compilation-error.txt
The interesting part of the Log
[hunter ** INTERNAL **] 'hunter_check_toolchain_definition' incorrect toolchain.info file,
[hunter ** INTERNAL **]  double definition of define '__amd64__'
[hunter ** INTERNAL **]  in file 'C:/Users/nw.HORN/.hunter/_Base/4629acb/18812f7/toolchain.info'.
[hunter ** INTERNAL **] [Directory:C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/projects/rdb]

------------------------------ WIKI -------------------------------
    https://github.com/ruslo/hunter/wiki/error.internal
-------------------------------------------------------------------

CMake Error at C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/modules/hunter_wiki.cmake:12 (message):
Call Stack (most recent call first):
  C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/modules/hunter_internal_error.cmake:13 (hunter_wiki)
  C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/modules/hunter_check_toolchain_definition.cmake:62 (hunter_internal_error)
  C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/projects/rdb/hunter.cmake:17 (hunter_check_toolchain_definition)
  C:/Users/nw.HORN/.hunter/_Base/Download/Hunter/18.10.1/4629acb/Unpacked/cmake/modules/hunter_add_package.cmake:62 (include)
  CMakeLists.txt:23 (hunter_add_package)

I've narrowed the problem down on how the file scripts/ShowPredefined.cpp is compiled and reported. I've modified scripts/create-toolchain-info to write the raw compilation output outresult to a file
https://github.com/ruslo/hunter/blob/master/scripts/create-toolchain-info.cmake#L76-L82
compiling with msvc14
cmake -Hexamples/Eigen -B_build_llvm -G "Visual Studio 14 2015 Win64" -T "LLVM-vs2014"

hunter_MSVC14.log
compiling with LLVM-vs2014
cmake -Hexamples/Eigen -B_build_llvm -G "Visual Studio 14 2015 Win64" -T "LLVM-vs2014"

hunter_LLVM-vs2014.log
Clang prints the #pragma message as warning. And MSVC creates a summary at the end of all warnings occurred during the compilation. Therefore the toolchain.info file has all defines two times
Note: rv18.10.1 is an internal version of Hunter based on v0.23.29 with some additional private packages. No changes on toolchain.info creation

I guess it's possible to add "remove duplicates" logic here:

https://github.com/ruslo/hunter/blob/master/scripts/create-toolchain-info.cmake

Or simply ignore this warning for MSVC + LLVM toolchain:

https://github.com/ruslo/hunter/blob/6078d6f80ab4f8b5cb11e68e95cdcb1821b9c072/cmake/modules/hunter_check_toolchain_definition.cmake#L61-L67

as the toolchain reiterates every warning to us, we could just remember the first flag and finish the parsing of the ShowPredefined.cpp file early when the first flag is found again.
Do you think we should add a warning just in case?

just remember the first flag and finish the parsing of the ShowPredefined.cpp file early

Well it's true for our case but it may not be true for another compiler. Just removing duplicates sounds like a reasonable option which doesn't rely on any compiler specific features.

Do you think we should add a warning just in case?

You mean warning instead of hunter_internal_error?
@NeroBurner Can you please try fix from branch issue-1589 ?

Maybe a bit late, but I thought of another solution
https://github.com/ruslo/hunter/blob/6078d6f80ab4f8b5cb11e68e95cdcb1821b9c072/cmake/modules/hunter_check_toolchain_definition.cmake#L61-L67
instead of always throwing an error we could throw the error only if the defines have different values?
will try your fix tomorrow. thanks!

The branch is working! Thanks!

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.43


Investigate PICS_SDK_CI_ONLY use in cert

Please follow the below template to file issues/concerns/feature enhancement against Test Scripts:
Summary Title:
Need to disallow PICS_SDK_CI_ONLY in cert.
Description:
It is possible to go to cert with PICS_SDK_CI_ONLY set, which means big pieces of some major tests are being skipped. We should disallow this, but it's actually hard to do since we DO want to allow this in the CI and we need it. Is this maybe something we can build into the TH? Maybe in the PICS tool?
See https://github.com/project-chip/matter-test-scripts/issues/206
@raju-apple WDYT?
Steps to reproduce:
Add this pics, go to cert, see bad things happen.
Logs:
Additional Info:

@raju-apple - what are your thoughts on this? We definitely had at least one device go to SVE with this PICS turned on.


Fix finalize_clip for GRAY clips

Fix #100

https://github.com/Jaded-Encoding-Thaumaturgy/vs-tools/commit/c129c1545fb48f05aaeb4c3b292ad695caec5592


Added residual smoothing to IDR method

This PR replaces #65, squashed with whitespace cleaned, and rebased on top of master. This new PR will trigger a new set of tests.

Current coverage is 86.97% (diff: 89.65%)

Merging #89 into master will increase coverage by 0.01%

@@             master        #89   diff @@
==========================================
  Files            17         17
  Lines          1096       1113    +17
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            953        968    +15
- Misses          143        145     +2
  Partials          0          0

Powered by Codecov. Last update e38feea...6f4df86


reimplement it using Qt control 2.0

You should implement this using the new qt control 2 mecanism
http://doc.qt.io/qt-5/qtquickcontrols2-styles.html
I can help ! Create a new repository and add me !

I just started to implement there : https://github.com/labsquare/FlatUI-QML

oooooohh! This is interesting. I forgot about the v2 of the controls. Thanks for the update.

I started my own repo.
You can work on mine if you are agree.
https://github.com/labsquare/FlatUI-QML?files=1
Just open projet.pro in qtcreator with Qt 5.7 minimum. And run it! Plugin
is compiled and demo start.
Le 18 sept. 2016 10:20, "Lee Lazarecky"<EMAIL_ADDRESS>a écrit :

oooooohh! This is interesting. I forgot about the v2 of the controls.
Thanks for the update.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Druage/FlatUI-Controls-QML/issues/1#issuecomment-247857165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0pF2Qng-NxH2-wZ3UF05VsRYcXC8HKks5qrWSzgaJpZM4J6o5I
.

Okay sounds good!


Refactor: validators

This is a proper refactoring of the most entangled solution in the project - the validators.
Now, we have only two validators types - the one with the data from current epoch (ValidatorEpochData) and another one extending it with external data - contact info, fee, telemetry etc (ValidatorFullData).
Glossary:

current epoch stake (CES) - stake of the validator in current epoch (epoch X);
next epoch stake (NES) - stake of the validator in the upcoming epoch (epoch X+1);
after next epoch stake (ANES) - stake of the validator that it proposed to the network, to be picked (or not picked) in the epoch after the next one (epoch X+2);
contract stake (CS) - stake of the validator that is fetched from contract pool function get_total_staked_balance, used to fetch balance for potentially-validating-nodes not currently participating in validating process.

I'll describe current scheme briefly for historical purposes:

We get data about current epoch validators, next epoch validators and proposal (after next epoch) validators from RPC call validators and remap it to the list of validators with corresponding props.
Additionally, we add all the accounts that end up with poolv1.near to the list for a user to pick a newcoming pool with not enough tokens to take a validator seat. For these we get CS.

The order of validators rendering is:

first by amount of CES tokens (if any)
second by amount of NES tokens (if any)
third by amount of ANES tokens (if any)
last by amount of CS tokens (if any)

We render those validators with amount of tokens:

on the main line we render one of the stakes, the priority is: CES, NES, ANES, CS.
on the secondary line we render stake diff ONLY if we have CES and one of the following: NES or ANES, the diff is either NES-CES or ANES-CES.

We render validators token status based on following rules:

if contract has CES and NES - we render it as active
if contract has CES but no NES - we render it as leaving
if contract has no CES but has NES - we render it as joining
if contract has no CES and no NES but has ANES - we render it as proposal
else we decide by validator seat price:

if CS has more tokens than the seat price - we render it as onHold
if CS has more tokens than 20% of the seat price - we render it as newcomer
if CS has less tokens than 20% of the seat price - we render it as idle

@shelegdmitriy Ready for review!

https://frontend-pr-955.onrender.com/nodes/validators
I am thinking about mixing those "joining" and "proposals" into the list of active nodes but without giving them an index number, and showing their stake in grey font color like it is commonly used to indicate "disabled" state. @shelegdmitriy I feel this used to be the case before, wasn't it? @reefoh Any objections? I don't want us to spend too much time on it, but since we are touching it anyway, we may as well do slight tuning.

On the second thought, I feel we can merge this PR as is, and then consider to have a separate PR addressing the topic I raised in the previous comment.


docs: Update README with badges, note callouts

Adds badges: https://shields.io
Format notes into callouts

Thanks Grant, this looks great.


Screenshot not available

The screenshot in the README is not available

In case anyones curious about what it looked like.
https://web.archive.org/web/20231024201237if_/https://camo.githubusercontent.com/b610261ef7a0d32842bcb4bbc6ea6b252573a991d2b68396b62fefd3329cc1ba/68747470733a2f2f662e6a7374616e6765722e6465762f6769746875622f69726f6e6261722f6261722e706e673f726177

In case anyones curious about what it looked like. web.archive.org/web/20231024201237if_/https://camo.githubusercontent.com/b610261ef7a0d32842bcb4bbc6ea6b252573a991d2b68396b62fefd3329cc1ba/68747470733a2f2f662e6a7374616e6765722e6465762f6769746875622f69726f6e6261722f6261722e706e673f726177

This screenshot is pretty old, maybe a new screenshot with newer functionality would be cool

Yeah, happy to provide some new ones once I'm up and running again. Of course, happy for anybody who has anything they'd like to show off to ]submit theirs](https://github.com/JakeStanger/ironbar/discussions/categories/show-and-tell) and I'll consider using that in the README/docs too :)

WD have shipped my drives at long last! I'll have screenshots back up likely mid next week.

900Mbps is a lot faster than I thought. Back up and I've updated the screenshot :)

Nevermind I'm getting drive errors with the replacements :/
Will try and sort out something temporary in the meantime.


FNF lag when computer configuration is very strong

the video I made is below but when switching characters the FPS drops drastically. Can anyone help me with this. my computer high configuration ram 24gb; Intel(R) Xeon(R) CPU E3-1230 v5 @ 3.40GHz 3.40 GHz, windows 10.
https://youtu.be/ChWoluTW4-U

See #1753.
The issue here is likely with how the mod is coded. This issue can occur if you load the character as you're switching to them. To prevent this lag, you need to load all the characters into memory at the start of the song, then switch between them. This will of course take a lot of RAM but you have 24GB of it.

@MasterEric  Thank you very much! I have never seen anyone with such a standard and enthusiastic guide as you! Thank you again :D how can I make friends with you?


Clarify documentation

I recently moved to vRP2, managed to create some extensions, but I’m having problems using vRP Client Extensions client-side. I’m trying to load my client.lua into vRP like this:
local Proxy = module("vrp", "lib/Proxy")

local vRP = Proxy.getInterface("vRP")

async(function()
    vRP.loadScript("tp_inventory", "client")
end)

Even though client.lua exists inside my “tp_inventory” resource I get this error:

"SCRIPT ERROR: @vrp/lib/utils.lua:51 resource file tp_inventory/client.lua not found"

Error image
Am I trying to load it the wrong way? Also, I think it would be nice if you could add how to do it correctly to the documentation instead of:

“The content of server_vrp.lua is now executed in the vRP context and can now use the API. The same thing should be done client-side.”

So that way people don’t get confused as I did.
Thank you, and you did an awesome job at vRP2!!

Did you added your client script to the client files of your resource ?
I'm afraid I can't clarify more, the behavior is symmetric by using the module function which uses the FiveM API about resource's files, as you can see: https://github.com/ImagicTheCat/vRP/blob/c33ed0d0a6228e4438fa53cdf90128379844380d/vrp/client/base.lua#L11

Well, maybe removing the specialized example will help. https://github.com/ImagicTheCat/vRP/commit/b1428ffbb3af0f7aa3d2533e29e6f9371581f43f

So, looking at the examples, when server.lua is loaded using loadscript it appears it does not need to be included at "server_scripts", but the client script does? Anyway, adding it to the client scripts solved the problem. Example of the __resource.lua for anyone who needs it:
server_scripts{
<EMAIL_ADDRESS>    "vRP.lua",
}

client_scripts {
<EMAIL_ADDRESS>    "vRPcli.lua",
    "client.lua"
}`

But when the client loads the script, some of the client modules break (image).
This is how I'm initializing the client script:
local Proxy = module("vrp", "lib/Proxy")
local Tunnel = module("lib/Tunnel")

local cvRP = module("vrp", "client/vRP")
vRP = cvRP()

local tpInventory = class("tpInventory", vRP.Extension)

function tpInventory:__construct()
    vRP.Extension.__construct(self);
end

Tried to initialize it like the server script, just declaring the extension class and constructing it, but it doesnt seem to be the right way to do it as vRP becomes undefined.
So, does it differ from the server-side logic or am I doing something stupid?
Thanks for attention.

This is more about FiveM than vRP. client_scripts and server_scripts are script loaders. Files loaded in the vRP context are just file, you don't execute them in your own resource. Files are always available server-side, but client-side files should be added to files (for downloading).
Check the FiveM documentation.

Got it, also that error was a silly mistake of mine. I forgot to register the extension. Thanks for the help @ImagicTheCat, hope to contribute to your project :)


Redis connection failed

Version: What node_redis and what redis version is the issue happening on?
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Platform: What platform / version? (For example Node.js 0.10 or Node.js 5.7.0 on Windows 7 / Ubuntu 15.10 / Azure)
NodeJS v8.12.0 on Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-135-generic x86_64)

Description: Description of your issue, stack traces from errors and code that reproduces the issue
Randomly get this error:
Redis connection to <IP_ADDRESS>:6379 failed - write EPIPE at WriteWrap.afterWrite [as oncomplete] (net.js:868:14) errno: 'EPIPE', code: 'EPIPE', syscall: 'write'

Any idea where to look for the issue?

This looks like it's a connection issue - double check all the ports are open and stuff.
-K

@stockholmux thanks, thanks, that much I figured, I was interested about the specifics of the cause ( if anything retraceable from the error message ). I guess is not possible though...

@xyboox Nope. That's an error generated by Node.js. Sorry.

The same error in Stackoverflow


Electron: backport DPI related Windows fix

Refs: https://github.com/electron/electron/issues/10862
Upstream: https://chromium-review.googlesource.com/c/chromium/src/+/4673217

Details

The upstream change will be available in Electron 27 with Chromium 117, so we can then do an exploration build to try it out.
https://chromiumdash.appspot.com/commits?commit=5bf7cfd44326bbaad9b85f9500151013b1d65c43&platform=Mac

Oh, turns out that there is Electron 27 alpha out. I created an exploration build: https://builds.code.visualstudio.com/builds/exploration?commit=fe65440775961556476b03a8c764b18971f48784

I tested the build on Windows and unfortunately I see no improvement around this hack:
https://github.com/microsoft/vscode/blob/bf1f6a2298fdfdd09060336417a5e892176200c7/src/vs/platform/windows/electron-main/windowImpl.ts#L354-L372
We still need it, otherwise the window opens with bad dimensions on a secondary monitor with 175% scaling.
I suggest to not pursue this with a backport but wait for the official release.


Add circle ci and travis setup

As detected in https://github.com/MyBitFoundation/MyBit-Network.tech/issues/197, we haven't setup Circle CI nor Travis on this project.

Seems we haven't even setup Github/Asana integration, nor DDF integration in this project. Beautiful. Closing this as this has to be done internally.


feat: Auto-height add reducers and actions

Description
Prep for the auto height feature.

[ ] Add a new action which updates specific canvasWidgets paths. This action doesn't trigger an eval.
[ ] Add a new reducer to store the canvas level maps. This is necessary for auto height computations
[ ] Add a new reducer to store the auto height layout tree. This is necessary for auto height computations.
[ ] Add new action functions for the new action types
[ ] Register new reducers

Fixes #12606
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual
Jest

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=86168c9

/ok-to-test sha=e95ba9e

/ok-to-test sha=0548288

/ok-to-test sha=3ea2224

/ok-to-test sha=017e0ed


Configure support tools

(Mostly) Python:

pre-commit
ruff
poetry
pytest
pytest-cov
codecov?
prettier
mkdocs

https://github.com/Argmaster/pygerber

I’ve created documentation that includes (previously selected) support tools and a set of information about environment that everyone should use during project development. This should make work easier, faster and help team members focus on more important issues related to the functionality of the program itself. Before implementing the support tools listed in this documentation, they should be checked whether they all work properly.

Installation
Decelopment
Build from source
Build documentation

I've checked and corrected the previous documentation. From now on, all support tools should work correctly in the environment of each team member. Additionally, I've updated the README.md file with key information about adding support tools to other team members' workspaces.


use aurelia-loader instead of aurelia-loader-default

In order to work correctly with both jspm and webpack, could you use aurelia-loader instead of aurelia-loader-default

I want to use this plug-in in my application, but can't due to this issue (we are using Webpack and ES2015).  Is there a work-around in the meantime of implementing this fix?

Hey guys,
In the meantime you can use this fork

@raiseandfall I'm somewhat new to a lot of the tooling in front end development.  How would I install and use that fork via npm?

@m-andrew-albright sure, makes more sense if I paste the dependency line in package.json:
"dependencies": {
  "aurelia-configuration": "https://github.com/learningmachine/Aurelia-Configuration/tarball/1.0.7"
}

@raiseandfall  When I try to run after adding this dependency, I'm getting this error:
Uncaught Error: Cannot find module "aurelia-http-client" -  aurelia-configuration/dist/commonjs/configure.js:13
I currently am only using the aurelia-fetch-client in my application; does this have a dependency on aurelia-http-client?  If so, what is it using that for?  Can I circumvent this somehow?

@m-andrew-albright I don't think that's related to this dependency (I don't have the issue). Did you try installing it?

This is fixed in the latest release. Sorry this took so long.


Relicense as MIT/Apache-2

Fixes #39
As discussed in #39, all current contributors (@KodrAus, @saresend and me) agree in relicensing this as MIT/Apache-2.

I'm just going to merge this without review. This is 99% copy-and-paste text anyway.


Can CreateEmbeddings support custom models?

Integrate with the third-party large models, their API is compatible with openai, but need to specify their model, so I hope to support custom model.

I believe this can now be closed due to #629


Temp File Issue

I'm getting a ton binaries showing up in the /tmp space. please help! k thx bye

sigh windows support, time to yank. we used to do ops on files which windows didn't like, got merged in #118 to be reverted.

sigh windows support, time to yank. we used to do ops on files which windows didn't like

Does this mean we’re no longer opening the file a second time and those changes should just be reversed, or is there more to it than that?


MINOR Always archive build scan

Change the CI workflow to unconditionally run with --no-scan to ensure we can capture and archive the build scan.
Change the CI Complete workflow to run on trunk as well as PRs.

Earlier today, ge.apache.org was down for a while which resulted in many missed build scans. I was able to manually upload several of them, but this is kind of a hassle. If we use the CI Complete workflow for uploading build scans from trunk, we will be able to simply rerun the workflow to re-attempt the publish. Since we already have the mechanism in place, it makes sense to use it.
Another option would be to modify CI Complete to be able to run on-demand. But making the trunk and PRs builds more consistent seems like a good idea.


Merge pull request #1 from gardener/master

Merge latest pull requests from gardener master
How to categorize this PR?

/area TODO
/kind TODO
/priority normal
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

 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.


feat(dao) re-introduce immutable field validator to DAO

Summary
This PR re-introduces the immutable field validator to the DAO, allowing Kong to prevent certain fields from being updated.
Full changelog

Add Unit Tests
schema/init.lua Introduced validate_immutable_fields schema method
schema/init.lua Expanded checks in process_auto_fields to include searching each field for immutable attribute
dao/init.lua Integrated new functionality into check_update
spec/01-unit/01-db/04-dao.lua Added Unit Tests

 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.

@james-callahan: The purpose of immutability in this case is to preserve important relationships that could otherwise be tampered with, not prevent a database item from having a particular field (so deleting and replacing a record isn't problematic or what this is trying to solve).


[feature request] runtime-manager cri-proxy

What would you like to be added:
Why is this needed:

/assign $ZYecho

/assign $honpey

/assign honpey

/area runtime

implement by #105


WIP: fix encoding for ISO output (#576)

Overview
This PR attempts to fix the encoding issue for ISO output.
Related Issue / Discussion
#576
Additional Information
NA
Contributions and Licensing
(as per https://github.com/geopython/pycsw/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x] I'd like to contribute [feature X|bugfix Y|docs|something else] to pycsw. I confirm that my contributions to pycsw will be compatible with the pycsw license guidelines at the time of contribution.
[x] I have already previously agreed to the pycsw Contributions and Licensing Guidelines

Kia ora,
We are upgrading Geonode to meet python3 compatibility and ran into this bug here. Geonode has a dependency on pycsw, we are getting TypeErrors caused by the differences between byte literals and strings in Python3. Can we please have an update on the progress/problems here? We would be happy to help.
Dingding

Hi @tomkralidis ,
As I mentioned before, our python3 upgrade of GeoNode is dependent on PyCSW, and this encoding problem is preventing us from passing tests under python3. Is a deadline/priority for this PR, again we are very keen on helping if necessary.
Kind Regards,
Dingding

Can you provide a sample metadata record and environment / workflow so I can reproduce? Does this PR work for you?

The latest change in this PR results in failure in Geonode's tests, however the commits that work with our upgradings are

8739d56c67c5a70975de371c50e978b20572cbe6 https://github.com/geopython/pycsw/blob/8739d56c67c5a70975de371c50e978b20572cbe6/pycsw/plugins/profiles/apiso/apiso.py#L389

9f151040a99c1b32dbe02ce9ceabe0d62ea3b146 https://github.com/geopython/pycsw/blob/9f151040a99c1b32dbe02ce9ceabe0d62ea3b146/pycsw/plugins/profiles/apiso/apiso.py#L389

Regarding on the tests that fail in Geonode:
This cataloging code is used in Geonode many times, especially when running integration test with TEST_RUN_INTERNAL_APPS=True python manage.py test geonode.geoserver.tests.test_server.SignalsTests.test_set_resources_links, the test fails on https://github.com/mtnorthcott/geonode/blob/py3/geonode/geoserver/tests) /test_server.py#L1141 with following messages:
File "geonode/geonode/geoserver/tests/test_server.py", line 1141, in test_set_resources_links
    self.assertTrue(count > 0, "No layers have got metadata")
AssertionError: False is not true : No layers have got metadata


Temporarily Disable Librarian Permissions Check

Until #146 is resolved, we're going to disable the check.

Closing. Actual fix found hiding in plain sight. 👓


Why can't Info level logs be uploaded to Exceptionless

The Exceptionless version I am using is v2.7.1. When I use Exceptionless.NLog of version 4.6.2, Info level logs cannot be uploaded to Exceptionless, but Warn and Error logs can be uploaded.

你参考下文档里的设置：https://exceptionless.com/docs/setting-log-levels/
不过按照文档中的设置之后，也会遇到这样的情况，我debug手动在代码中修改日志等级，然后就写进去了，有时候跟堵住了一样。


Handle overlap between input images

The main case of yokogawa parsing we've implemented so far was a grid without overlap. After that, given the progress with metadata parsing & ROI definitions, we want to support search-first data where the FOVs are not a grid, but any random positions (see https://github.com/fractal-analytics-platform/fractal/issues/23). As an initial implementation, we can focus on random positions, but without overlap between FOVs.
The step after that is handling overlap between FOVs. I don't know whether we have test data for search-first with overlap, but we certainly have grids with overlap (e.g. FOVs always overlap for about 10%). I'm not fully sure how we want to handle that in our current setup where a well is a single FOV.
We could consider a direction that only saves to Zarr once registration has been done, but that could get tricky memory-wise.
For grids, we could also save it initially as a non-overlap grid and then later have a registration/merging task that combines images.
This has the downside of having to actually merge (=edit) the raw data and save the modified data. That we probably have to live with if we want to go in this direction.
The other somewhat annoying downside is the question of how we handle metadata. Because the metadata from the microscope will already define an overlap between the FOVs, which is not how we'd want to save it initially, most likely.
Let's use this issue to discuss how we'll handle this. We may decide that this is not in scope for the search first milestone, but should start thinking about how we'll eventually tackle this.

Overview of the options for storage on disk in Zarr files of overlap
a) We never store overlap on disk (very limiting, would mean stitching only possible during parsing)
b) We shift FOVs to save it as a grid without overlap. If stitching is performed, it is baked into the image. Where do we save overlap positions? In a extended part of the ROI table (e.g. have position_x and raw_position_x)? Could then be used as an optional input to a stitching algorithm (initial position of all tiles)
c) We save it as a multi-FOVs Zarr file that contains the positional information for each FOV . Benefit: Could be visualized in any way the user desires (e.g. blending overlaps), maintains all raw data & positions. Downsides: Massive complexity. Much harder to process in our current infrastructure. Visualization doesn't scale at all, file numbers scale very badly.
I would go with b for the moment and declare c out of scope. It is potentially interesting to implement at a later point, but the complexity is fairly high. b takes a bit of additional parsing, but is doable.
Depends also a bit on what kind of downstream processing we need to enable, see the discussion on processing iii) here: https://github.com/fractal-analytics-platform/fractal/issues/137

Given the discussion in #137, we can stay with b here. If we do stitching, we do it early on and then just have the fused array.
Until the stitching, we can just save the shifted tiles, so let's keep things simple then :)


One off bug fixes

[x] appearance, delete css properties
[x]  overflow - allowed values: 'hidden' or 'none', overflowY and overflowX are not allowed
[x] whiteSpace - likely indicating the need for ellipsis
[x]  textOverflow - ^^

better to move forward and adjust 👍


Any other official way(not public in github issues) to report security bug of tensorflow?

Hi,
I have found a security issue in Tensorflow. An attacker can easily execute arbitary code on victim machine through this issue. I think it has severe secure impact on tensorflow users. So it is not proper to disclosure this issue on github issues publicly before it is fixed.
Is there any other official way to report security issue? I will explain the details.
Thanks.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Not a google developer, but how about this?
https://www.google.com/about/appsecurity/

@zhangbo5891001 Is it related with the saved model file? Maybe we could try to sign it if it is.


Data thats downloaded seems to be limited

For example, for the general election polls, downloading all the data only yields five or six polls where Trump and Clinton are > 0. Is there a reason for this?

Hi there! Please provide some example code, the result python-pollster gives, and a description of what's wrong with that result.

So, I looked at the chart:

And tried to download the corresponding polls:

But, the number of non-trivial results seem to be very limited:

In fact, for significant polls there are barely 60:

Just wanted to make sure that made sense

Leads to sparse maps:
https://github.com/bloomberg/bqplot/pull/303

Thanks ... but what's the code you wrote to populate data?

For getting the data I used:
raw_data = pollster.charts(topic='2016-president')

def get_candidate_data(question):
    clinton, trump, undecided, other = 0., 0., 0., 0.
    for candidate in question['subpopulations'][0]['responses']:
        if candidate['choice'] == 'Hillary Clinton':
            clinton = candidate['value']
        elif candidate['choice'] == 'Donald Trump':
            trump = candidate['value']
        elif candidate['choice'] == 'Undecided':
            undecided = candidate['value']
        else:
            other = candidate['value']
    return clinton, trump, other, undecided

def get_row(question, partisan='Nonpartisan', end_date='2016-06-21'):
    if question['topic'] != '2016-president':
        return
    hillary, donald, other, undecided = get_candidate_data(question)
    return [{'Name': question['name'], 'Partisan': partisan, 'State': question['state'],
             'Date': np.datetime64(end_date), 'Trump': donald, 'Clinton': hillary, 'Other': other,
             'Undecided': undecided}]

def analyze_polls(polls):
    global data
    for poll in polls:
        for question in poll.questions:
            resp = get_row(question, partisan=poll.partisan, end_date=poll.end_date)
            if resp is not None:
                data = data.append(resp)
    return

data = pd.DataFrame(columns=['Name', 'Partisan', 'State', 'Date', 'Trump', 'Clinton', 'Other',
                     'Undecided'])

for i in raw_data:
    analyze_polls(i.polls())

You're going poll-question by poll-question, but different poll questions have different response phrasings. For some polls, a choice might be u'Hillary Clinton'. For other polls, the choice could be u'Clinton'. Another would be u'Hillary Clinton, the Democratic Candidate'. Pollster doesn't control these: it just copy/pastes from the poll results. If there's a typo in the poll, there will be a typo in Pollster.
So here's a simple workaround: look for last_name of u'Trump' or u'Clinton'. That will work because last_name is a field that we at Pollster control.
We're totally on board with helping you use the API. But I don't consider this a bug in python-pollster, so I'll close this issue. I encourage you to join https://groups.google.com/forum/#!forum/pollster-users and discuss everything API-related.

That worked much better @adamhooper
Thanks! Just a quick question, whats the license on the data?

CC-by-nc-sa , as per http://elections.huffingtonpost.com/pollster/api.
IANAL, but my understanding is: "by" is easy (please cite and link to us) and "sa" is easy (please publish derived CSVs -- which is good form, anyway). As for NC: I believe AOL considers public-interest news reporting (like NYT or 538 predictions/stories) to be "non-commercial". I don't know where the boundaries are to that definition. To be safe, please double-check with<EMAIL_ADDRESS>