Visual Studio 2010 - Link problem: error LNK2019: unresolved external symbol __imp__timeGetTime

I have run into this myself occasionally. I remember that it could be solved somehow by choosing the right compiler options. However, I find it strange that this error should occur at all. Any insights, perhaps, @Andne?

Off the top of my head, it sounds like the project is being configured to link against the DLL version of a library (the imp tells me that), but for some reason the import library isn't being passed to the linker.  That function is part of winmm.lib, so is that not being passed to the linker for some reason? Not sure what would have happened to break that on the main projects though, it was working so it should keep working I'd think.

Fixed yet?

I think it is. At least I remember that @Andne and I put in quite a bit of effort getting all those nitty-britty VS-issues fixed. I think this one came up on Google Groups. I also think Appveyor should show it, if there were still a (general) problem.

FYI I ran across this issue just today on a fresh checkout of the repository.  There is a relevant Stack Overflow discussion/solution here.
To resolve the issue I had to add Winmm.lib to the additional linker dependencies in the project properties MyCppUTestProject>Properties>Linker>Input>Additional Dependencies


IE 8 error - null is null or not an object

Hi,
Please find the code i am using to invoke mediaelement, this works fine in Chrome, but on IE 8 we get this "null is null or an object error" when the code tries to load/play the player. i tried with commenting the load/play line yet it throws the same error.
i have tried this with jQuery 1.7.2 too but futile. Note, i am able to stream the videos despite the error. but since the frequency of the error thrown is very often, i fear at some point of time browser could become unresponsive.
Let me know if i'm doing something incorrectly.
JS
$("#videoPlayer").empty().show();
var vid = '';
$("#videoPlayer").append(vid);
var source = jQuery.validator.format(streamingUrl, g_Video.DocID); //this line of code constructs streaming url
$("#video").attr('src', source);
var player = new MediaElementPlayer('#video');
player.load();
player.play();
Html
div id="videoPlayer" style="display: none"
video id="video" src="" width="560" height="360" controls="controls" preload="none" /video
/div
i have included the related css and js files in the header
Thanks,
Raghavan

@raghavan-mk You are basically removing the the video tag with this line:
$("#videoPlayer").empty().show(); var vid = ''; $("#videoPlayer").append(vid); that's why you get that.  You should avoid using empty(). If that solves your issue, can you close this please?


feat: Add macOS support for progress-view

Summary
This change adds a macOS implementation of RNCProgressView. The Objective-C implementation was copied over from the current implementation under React/Views/RCTProgressView* in Microsoft's react-native-macos repo, plus some simple refactoring to change the RCT prefix to RNC as needed.

Test Plan
Basic functionality was tested using a simple test app under example/macos. The implementation is similar to that of the already existing test app for Android and iOS, but due to differences between which version of React Native we pull, we have to create a separate test project for macOS. This test project has been slimmed down to only include the macOS implementation.

Compatibility

OS
Implemented

macOS
✅

iOS
✅

Android
✅

Checklist

[X] I have tested this on a device and a simulator
[X] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md*
[ ] I updated the typed files (TS and Flow)*
[X] I added a sample use of the API in the example project (example/App.js)

*Not applicable.

Related https://github.com/microsoft/react-native-macos/issues/391

Don't we want it to be a native progress bar (NSProgressIndicator)? https://developer.apple.com/design/human-interface-guidelines/macos/indicators/progress-indicators/

Don't we want it to be a native progress bar (NSProgressIndicator)? https://developer.apple.com/design/human-interface-guidelines/macos/indicators/progress-indicators/

The main goal of this PR is to bring react-native-macos's implementation into react-native-community, and this is how ProgressView is currently implemented for macOS. That being said, this is something that can be revisited in a later PR, although I'm open to discussion about whether making sure we're using an actual NSProgressIndicator would take precedence over getting react-native-community up to speed.

@Naturalclar do you think you'd be able to get this merged & publish a new version?

@kelset thanks for the ping, I'll take a look at it today and merge/publish if there's no problem :+1:


logic behind large election ID

It looks like election ID is 128 bits which is huge for this purpose. I don't think election ID is going to change frequently that requires this huge number. Even if we want to be conservative uint64 is more than enough. What is the logic behind it?

@adibrastegarnia That's a good question. It's been a while since we took that decision and I think it came from Google so I imagine that they have a leader election mechanism internally that may produce 128-bit ids.
I am not an expert on consensus protocols, but I imagine that using 128 bits lets us have a 64-bit term id (or round id) plus a 64-bit node id. Note that if your consensus protocol only requires 64-bit of space, you should feel free to always set the high 64 bits to 0. A P4Runtime server implementation should not care about how you generate these ids. It only cares about their numerical value and their ordering. So if you only need 64 bits of space total, you can organize the ids as you want:
<32bits of 0s><32bits of term id><32bits of 0s><32bits of node id>
<64bits of 0s><32bits of term id><32bits of node id>
<64bits of 0s><64bits of id>
<64bits of id><64bits of 0s>
The added complexity on the client side and server side, that comes from using 2 uint64 values, is quite small IMO. It's not like the election id value needs to traverse the stack. It really should be handled locally on the Southbound of the client and the Northbound of the server. In this server implementation for example, the election id is only used in that one file, to enforce arbitration.

Yeah this makes sense to me. I suspect something like Google's Chubby lock service could generate very large epochs like this since it's so widely used and may not be isolated to a single controller.


FaceMesh Visualization using React not working

Please make sure that this is a solution issue.
System information (Please provide as much relevant information as possible)

Have I written custom code (as opposed to using a stock example script provided in Mediapipe):
I mostly copied a "working" solution from #2261 and replaced relevant parts with the FaceMesh JS sample code
OS Platform and Distribution (e.g., Linux Ubuntu 16.04, Android 11, iOS 14.4):
macOS 12.3.1 (Intel i7), Chrome Version 102.0.5005.61 (Official Build) (x86_64)
MediaPipe version:
"@mediapipe/camera_utils": "^0.3.1640029074"
"@mediapipe/drawing_utils": "^0.3.1620248257"
"@mediapipe/face_mesh": "^0.4.1633559619"
Bazel version:
NA
Solution (e.g. FaceMesh, Pose, Holistic):
FaceMesh
Programming Language and version ( e.g. C++, Python, Java):
JavaScript / React

Describe the expected behavior:
Upon loading of the webpage at localhost:3000 and initialization of the mediapipe solution and the webcam (permission has to be granted), the face mesh is vizualized as in the example mentioned above.
Standalone code you may have used to try to get what you need :
The example code from here works without fail. The problem is visualization using React.
If there is a problem, provide a reproducible test case that is the bare minimum necessary to generate the problem. If possible, please share a link to Colab/repo link /any notebook:
Below is the code I used:
npx create-react-app app
cd app
npm i react-webcam @mediapipe/face_mesh @mediapipe/drawing_utils @mediapipe/camera_utils

Replace the content in App.js with the following and run npm start:
// App.js
import { useRef, useEffect } from "react";
import * as cam from '@mediapipe/camera_utils';
import Webcam from 'react-webcam';
import * as mediapipeUtils from '@mediapipe/drawing_utils';
import { FaceMesh } from '@mediapipe/face_mesh';

function App() {
  const webcamRef = useRef(0)
  const canvasRef = useRef(0)
  var camera = null

    function onFaceMeshResults(results) {
        // Define the canvas elements
        canvasRef.current.width = webcamRef.current.video.videoWidth
        canvasRef.current.height = webcamRef.current.video.videoHeight
        // Check for useing the front camera
        const canvasElement = canvasRef.current;
        const canvasCtx = canvasElement.getContext("2d")
        canvasCtx.save();
        canvasCtx.clearRect(0, 0, canvasElement.width, canvasElement.height);
        canvasCtx.drawImage(
            results.image, 0, 0, canvasElement.width, canvasElement.height
        )
        if (results.multiFaceLandmarks.size > 0) {
            for (const landmarks of results.multiFaceLandmarks) {
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_TESSELATION,
                    {color: '#C0C0C070', lineWidth: 1}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_RIGHT_EYE,
                    {color: '#FF3030'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_RIGHT_EYEBROW,
                    {color: '#FF3030'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_RIGHT_IRIS,
                    {color: '#FF3030'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_LEFT_EYE,
                    {color: '#30FF30'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_LEFT_EYEBROW,
                    {color: '#30FF30'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_LEFT_IRIS,
                    {color: '#30FF30'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_FACE_OVAL,
                    {color: '#E0E0E0'}
                );
                mediapipeUtils.drawConnectors(
                    canvasCtx, landmarks,
                    mediapipeUtils.FACEMESH_LIPS,
                    {color: '#E0E0E0'}
                );
            }
        }
        canvasCtx.restore();
    }

  useEffect(() => {

    /* CREATE POSE PIPE */
    // const pose = new Pose({
    //   locateFile: (file) => {
    //     return `https://cdn.jsdelivr.net/npm/@mediapipe/pose/${file}`;
    //   }
    // });
    // pose.setOptions({
    //   modelComplexity: 1,
    //   smoothLandmarks: true,
    //   minDetectionConfidence: 0.5,
    //   minTrackingConfidence: 0.5
    // });
    // pose.onResults(onPoseResults)

    /* CREATE FACE_MESH PIPE */
    const faceMesh = new FaceMesh({
        locateFile: (file) => {
            console.log(file);
            return `https://cdn.jsdelivr.net/npm/@mediapipe/face_mesh/${file}`;
        },
    });
    faceMesh.initialize();
    faceMesh.setOptions({
        maxNumFaces: 1,
        refineLandmarks: true,
        minDetectionConfidence: 0.5,
        minTrackingConfidence: 0.5
    });
    faceMesh.onResults(onFaceMeshResults);

    /* CREATE WEB CAMERA */
    if (typeof webcamRef.current !== "undefined" && webcamRef.current !== null) {
      camera = new cam.Camera(webcamRef.current.video, {
        onFrame: async () => {
          await faceMesh.send({ image: webcamRef.current.video })
        },
        width: 320,
        height: 240
      });
      camera.start()
    }
  })
  return (
    <div className="App">
      <Webcam
        ref={webcamRef}
        style={{
          position: "absolute",
          marginLeft: "0px",
          marginRight: "0px",
          left: 0,
          right: 0,
          textAlign: "center",
          zindex: 9,
          width: 320,
          height: 240,
          marginBottom: "0px",
        }} />
      <canvas
        ref={canvasRef}
        style={{
          position: "absolute",
          marginLeft: "0px",
          marginRight: "0px",
          left: 0,
          right: 0,
          textAlign: "center",
          zindex: 9,
          width: 320,
          height: 240,
          marginBottom: "0px"
        }}>
      </canvas>
    </div>
  );
}
export default App;

Other info / Complete Logs :
Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached:

Hi @felixdollack ,
Could you please check whether the imports are loaded appropriately. Thanks!

Don't have to replace the jsdelivr, that piece of code is fine; also I think you need to reorder your code a little bit:
2.Should put the faceMesh initialization inside the useEffect, with [] as parameter; therefore, the algorithm will start when the page is rendered for the first time
3.Also, you don't need to get videoElement and canvasElement with doc.*, because you already have some refs defined

Sorry for the delayed response.
Thank you for your suggestions @sureshdagooglecom.
I added some of them, but the example you gave is for face_detection.
I am trying to use face_mesh.

Hi @felixdollack .
Could you please check whether the imports are loaded appropriately. Thanks!

am experiencing similar 'abort facemesh' issue with React and Facemesh. I'm using Camera vs webcam, and have my facemesh initialization inside the initial useEffect hook.

the only way I found around this is to use Holistic instead

Hey @cindyloo, thank you for the tip I will give it a try 👍🏼

So I don't know if I am still doing something wrong, or if the drawing utils for the face mesh are the problem.
I can confirm that I get mesh data in react when using the mediapipe/holistic solution.
However, I still can not draw the mesh as such, but only the connection points without connections.

I imported both drawing utils and the holistic solution,
import * as mediapipeUtils from '@mediapipe/drawing_utils';
import { Holistic } from '@mediapipe/holistic';

...

function onHolisticResults(results) {
        const canvasElement = canvasRef.current;
        const canvasCtx = canvasElement.getContext("2d")
        canvasCtx.save();
        // does work:
        mediapipeUtils.drawLandmarks(
            canvasCtx, results.faceLandmarks, Holistic.FACEMESH_TESSELATION,
            {color: '#FF0000'}
        );
        // does not work:
        mediapipeUtils.drawConnectors(
            canvasCtx, results.faceLandmarks, Holistic.FACEMESH_TESSELATION,
            {color: '#C0C0C0', lineWidth: 1}
        );
        canvasCtx.restore();
}

Hi @felixdollack ,
Could you please provide your complet code changes to investigate further on this issue.

please would you look at the code with my similar bug @sureshdagooglecom ? https://github.com/google/mediapipe/issues/2963

Hi @felixdollack ,
Could you please provide your complet code changes to investigate further on this issue.

Hi @sureshdagooglecom , no problem.
I uploaded my code in this project: face_mesh_issue_3430
It contains files for pose, holistic and face_mesh.
You can swap between them uncommenting the import and usage in src/App.js
I hope this helps with finding the underlying issue.

Facing issue on Samsung devices while using this library for open stream it says getUserMedia  got deprecated and it takes lotes of time to load the model any one please suggest

Hi @felixdollack ,
can you close this issue if resolved?

The underlying issue seems not resolved, as you can see by running the code mentioned here.
However, I have shifted to use the holistic solution, because that works for me.

Hi, is there any news on this? Has anyone managed to use the FaceMesh solution

Hey @dodorian92,
you can swap from FaceMesh (only) to the Holistic model (including FaceMesh).
Small example was posted earlier

i managed to use the faceMesh model
change your onFaceMeshResults. And it should go
`function onFaceMeshResults(results) {
// Define the canvas elements
canvasRef.current.width = webcamRef.current.video.videoWidth
canvasRef.current.height = webcamRef.current.video.videoHeight
// Check for useing the front camera
const canvasElement = canvasRef.current;
const canvasCtx = canvasElement.getContext("2d")
canvasCtx.save();
canvasCtx.clearRect(0, 0, canvasElement.width, canvasElement.height);
canvasCtx.drawImage(
results.image, 0, 0, canvasElement.width, canvasElement.height
)
if (results.multiFaceLandmarks != 0) {
  for (const landmarks of results.multiFaceLandmarks) {
      console.log(landmarks);
      mediapipeUtils.drawLandmarks(
          canvasCtx, landmarks,
          FaceMesh.FACEMESH_TESSELATION,
          {color: '#FF0000', lineWidth: 0.5}
      );

}}
canvasCtx.restore();

}`
ow i would like to try using three js in react for loading a 3d model on the face. Some idea?


[WIP] runtime_img: search registries: right trim slashes

Right trim slashes of search registries to avoid double slashes when
looking up images.  Otherwise, registries set to ["foo.com/bar/"] will
ultimately lead to an invalid "foo.com/bar//" reference.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

@vrothberg Now that container/image has been merged can we move forward with this?

@vrothberg Now that container/image has been merged can we move forward with this?

If I’m not mistaken, libpod just needs to update its containers/image version, and no code change should happen here.

That’s correct. Updating the vendored image lib will suffice. Feel free to
close this PR then. I’m on the phone and hope the reply reaches you.
On Fri 16. Mar 2018 at 17:06, Miloslav Trmač<EMAIL_ADDRESS>wrote:

@vrothberg https://github.com/vrothberg Now that container/image has
been merged can we move forward with this?
If I’m not mistaken, libpod just needs to update its containers/image
version, and no code change should happen here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/libpod/pull/452#issuecomment-373762018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALI4g_kkItJ77L5Ee2CAYVj7dD_XGlJdks5te-MVgaJpZM4SetcT
.

Closing, given we just bumped c/image


Question: How to setup aggregate in order to not interfere in files from modules not in reactor ?

I'm trying to set a parent POM in order to do a check for file's license header on all modules include in that root POM.
My problem is that the plugin is processing files that in my vision it not supposed to do.
Initially I did the following:
                 <plugin>
                        <groupId>com.mycila</groupId>
                        <artifactId>license-maven-plugin</artifactId>
                        <inherited>true</inherited>
                        <executions>
                            <execution>
                                <id>check-header-root-project</id>
                                <goals>
                                    <goal>check</goal>
                                </goals>
                                <phase>process-test-classes</phase>
		                        <configuration>
		                        	<detail>true</detail>
		                        	<aggregate>true</aggregate>
		                        	<useDefaultExcludes>true</useDefaultExcludes>
			                        <includes>
			                            <include>pom.xml</include>
			                            <include>src/main/java/**</include>
			                            <include>src/test/java/**</include>
			                        </includes>
		                        </configuration>
                            </execution>
                        </executions>
                    </plugin>

But some how it is not finding any problem in any children module's POM.
If I change the config to <include>*\pom.xml</include> it will take all directories including those that are not part of the root reactor.
am I missing something here ?

you cannot used aggregate>true</aggregate> with <inherited>true</inherited> : even if technically this is allowed, logically it does not make any sense since al sub modules would try to run the license check again with all their sub modules again.
aggregate treats the root project as 1 module. All the files within it will be checked (subject to include/exclude rules)


ft: ZENKO-270 add data upload limit

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

PR has been updated. Reviewers, please be cautious.

CONFLICT (add/add): Merge conflict in tests/unit/testConfigs/locConstraintAssert.js
CONFLICT (add/add): Merge conflict in tests/unit/multipleBackend/locationConstraintCheck.js
CONFLICT (add/add): Merge conflict in tests/unit/multipleBackend/locConstraintParse.js
CONFLICT (add/add): Merge conflict in tests/unit/metadataswitch.js
CONFLICT (add/add): Merge conflict in tests/unit/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in tests/unit/metadata/bucketclient/backend.js
CONFLICT (add/add): Merge conflict in tests/unit/helpers.js
CONFLICT (add/add): Merge conflict in tests/unit/bucket/bucket_mem_api.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectReplicationMD.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/objectCopyPart.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/unit/api/multiObjectDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/api/listParts.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketPutReplication.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketGet.js
CONFLICT (add/add): Merge conflict in tests/unit/api/bucketDelete.js
CONFLICT (add/add): Merge conflict in tests/unit/Config.js
CONFLICT (add/add): Merge conflict in tests/multipleBackend/objectPutPart.js
CONFLICT (add/add): Merge conflict in tests/multipleBackend/objectPutCopyPart.js
CONFLICT (add/add): Merge conflict in tests/multipleBackend/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/multipleBackend/multipartUpload.js
CONFLICT (add/add): Merge conflict in tests/locationConfig/locationConfigTests.json
CONFLICT (add/add): Merge conflict in tests/locationConfig/locationConfigLegacy.json
CONFLICT (add/add): Merge conflict in tests/functional/report/checkRoutes.js
CONFLICT (add/add): Merge conflict in tests/functional/raw-node/utils/gcpUtils.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/versioning/versioningGeneral2.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/versioning/versioningGeneral1.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/support/awsConfig.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/utils.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/put/put.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectTagging/taggingAwsVersioning-putget.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectTagging/taggingAwsVersioning-delete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectTagging/objectTagging.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectPutCopyPart/objectPutCopyPartAzure.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectCopy/objectCopyAwsVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectCopy/objectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/objectCopy/azureObjectCopy.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/mpuComplete/mpuAwsVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/mpuComplete/azureCompleteMPU.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/listParts/azureListParts.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/initMPU/initMPUAzure.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/get/getAwsVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/get/get.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/delete/deleteAwsVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/delete/delete.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/multipleBackend/acl/aclAwsVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/testBucketVersioning.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/putBucketReplication.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/test/bucket/getLocation.js
CONFLICT (add/add): Merge conflict in tests/functional/aws-node-sdk/lib/json/mem_credentials.json
CONFLICT (add/add): Merge conflict in tests.bash
CONFLICT (add/add): Merge conflict in package.json
CONFLICT (add/add): Merge conflict in mdserver.js
CONFLICT (add/add): Merge conflict in lib/utilities/reportHandler.js
CONFLICT (add/add): Merge conflict in lib/utilities/internalHandlers.js
CONFLICT (add/add): Merge conflict in lib/utapi/utilities.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapiReplay.js
CONFLICT (add/add): Merge conflict in lib/utapi/utapi.js
CONFLICT (add/add): Merge conflict in lib/services.js
CONFLICT (add/add): Merge conflict in lib/server.js
CONFLICT (add/add): Merge conflict in lib/routes/routeBackbeat.js
CONFLICT (add/add): Merge conflict in lib/metadata/wrapper.js
CONFLICT (add/add): Merge conflict in lib/metadata/metadataUtils.js
CONFLICT (add/add): Merge conflict in lib/metadata/bucketfile/backend.js
CONFLICT (add/add): Merge conflict in lib/metadata/ModelVersion.md
CONFLICT (add/add): Merge conflict in lib/data/wrapper.js
CONFLICT (add/add): Merge conflict in lib/data/multipleBackendGateway.js
CONFLICT (add/add): Merge conflict in lib/data/locationConstraintParser.js
CONFLICT (add/add): Merge conflict in lib/data/external/utils.js
CONFLICT (add/add): Merge conflict in lib/data/external/GcpClient.js
CONFLICT (add/add): Merge conflict in lib/data/external/GCP/gcp-2017-11-01.api.json
CONFLICT (add/add): Merge conflict in lib/data/external/GCP/GcpUtils.js
CONFLICT (add/add): Merge conflict in lib/data/external/GCP/GcpService.js
CONFLICT (add/add): Merge conflict in lib/data/external/AzureClient.js
CONFLICT (add/add): Merge conflict in lib/data/external/AwsClient.js
CONFLICT (add/add): Merge conflict in lib/auth/in_memory/builder.js
CONFLICT (add/add): Merge conflict in lib/api/objectPutPart.js
CONFLICT (add/add): Merge conflict in lib/api/objectGet.js
CONFLICT (add/add): Merge conflict in lib/api/objectDelete.js
CONFLICT (add/add): Merge conflict in lib/api/objectCopy.js
CONFLICT (add/add): Merge conflict in lib/api/initiateMultipartUpload.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutVersioning.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPutReplication.js
CONFLICT (add/add): Merge conflict in lib/api/bucketPut.js
CONFLICT (add/add): Merge conflict in lib/api/bucketGet.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/processMpuParts.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/getReplicationInfo.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/object/createAndStoreObject.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/bucket/bucketCreation.js
CONFLICT (add/add): Merge conflict in lib/api/apiUtils/authorization/aclChecks.js
CONFLICT (add/add): Merge conflict in lib/Config.js
CONFLICT (add/add): Merge conflict in docs/mkdocs.yml
CONFLICT (add/add): Merge conflict in docs/USING_PUBLIC_CLOUDS.rst
CONFLICT (add/add): Merge conflict in docker-entrypoint.sh
CONFLICT (add/add): Merge conflict in dataserver.js
CONFLICT (add/add): Merge conflict in constants.js
CONFLICT (add/add): Merge conflict in config.json
CONFLICT (add/add): Merge conflict in conf/authdata.json
CONFLICT (add/add): Merge conflict in circle.yml
CONFLICT (add/add): Merge conflict in README.md
CONFLICT (add/add): Merge conflict in .github/ISSUE_TEMPLATE.md

closed in favor of #1282


Is there a less boilerplate way to handle mutations?

It would be nice to have some sort of helper function to handle the update() and optimistic UI code.
update: (store, { data: { createTask } }) => {
  // Add to All tasks list
  const data = store.readQuery({ query: TASKS_ALL })
  data.allTasks.push(createTask)
  store.writeQuery({ query: TASKS_ALL, data })
  // Add to Todo tasks list
  const todoQuery = {
    query: TASKS_ALL,
    variables: { filter: { done: false } },
  }
  const todoData = store.readQuery(todoQuery)
  todoData.allTasks.push(createTask)
  store.writeQuery({ ...todoQuery, data: todoData })
},
optimisticResponse: {
  __typename: 'Mutation',
  createTask: {
    __typename: 'Task',
    id: null,
    done: false,
    label,
  },
},

Aside from the query and variables, I imagine this is typically going to be the same code over and over throughout every mutation. This is not very DRY.

I think this is outside of the scoped of vue-apollo.

Devs could easily write their own properties/methods to condense this and make it more reusable. Just saying, it would be handy for vue-apollo to include helper functions.
Would you consider a PR?

I think this would be cluttering vue-apollo a bit too much. Maybe in another new package?


Feature/game/declarative

I'd rather the consumers not need to decide how to retrieve the renderer and window singletons during onGameInitialize and onGameUpdate handlers. By doing this, I can avoid having to add even more API methods than I'm comfortable with.

Fixes: https://github.com/KajiTetsushi/Pong/pull/8#discussion_r974579867


Unify coding style

At the minimum, we should determine a standard indentation style, and make all files adhere to it.

I'm in favor of indenting by two spaces.

I'm down for 2 spaces. It's a simple thing to edit in the editor.

Yea two spaces sounds fine

We could use ESLint to check style automatically. It can also integrate with Atom, Sublime, etc. so it's super easy to use.


store return value from webhook/api call into database

Really excited about saltcorn, working from a local docker image for now.
Any pointers on how would I go about calling a webhook/api and getting the return value into a table field?
I create the action element but I can't see a way to retrieve/store the response.
Thank you in advance.

you can use https://url/api/tablename?access_token=""&otherfieldname="value"

Thank you


Update Welcome screens

At the moment the 3 welcome screens state wrong information. Please make it congruent with figma

Will be fixed with merging #801


A new enhancement integrated into the Oracle Cloud platform. - NEW FEATURE

Greetings! Firstly, I would like to express my appreciation for the excellent code, as it has proven to be highly efficient and beneficial on both the GCP and Azure platforms, which we are already adept at utilizing.
Now, I would like to inquire about the feasibility of incorporating versioning functionality specifically for OCI (Oracle Cloud Platform). While we have attempted to adapt the code, it is not functioning in the same manner as it does on GCP and Azure.
thank you so much

Hi, thanks.  This extension just calls terraform commands in Azure Devops pipelines, it doesn't have any Azure or GCP specific code.  What is not working?

@mgalvao-git did you see the question above?

Appears this is not related to this extension.  Please comment if this is not the case and we can re-open.


City Production Panel doesn't open

 Issue by Endeavour79
Saturday Sep 09, 2017 at 10:15 GMT
Originally opened as https://github.com/CQUI-Org/cqui/issues/614

New game, can select city production. Right side panel doesn't open.
Summer 2017

 Comment by JCron245
Saturday Sep 09, 2017 at 20:07 GMT

I believe this is a known issue with the summer patch. You should check out the thread dedicated to the patch and the work being done to make CQUI compatible with it https://github.com/CQUI-Org/cqui/issues/591
There are some work-arounds people have found to getting a good amount of the CQUI features working. If your problem hasn't been posted yet you should report it there as well.

 Comment by sparrow8332
Friday Sep 22, 2017 at 03:53 GMT

Kamino cloned this issue to sparrow8332/cquiissues


Changing a stub workflow from CWL to WDL does not rename the Workflow path to /Dockstore.wdl

I think this was dealt with before, but has since been deleted accidentally.

Functional on staging with API 1.5.0-alpha.4, UI 2.2.0-alpha.3


Could this code be used for the evaluation of Davis-2016?

if i modify this code a little, like changing the val.txt and annotations format to Davis2016, could i use this code directly for the evaluation of davis 2016?  I just want to know if  the implementation details of J/F are exactly the same with 2016 version.
Thx

Hello,
The implementation details for J and F are the same that the ones used for DAVIS 2016. However, I would strongly recommend that you double check your final result using the Matlab or Python versions released for DAVIS 2016 to verify that your modifications are correct.


Update Generic Pages “our-principles”

Automatically generated by Netlify CMS

👷 Deploy Preview for tech-works-for-us processing.

Name
Link

🔨 Latest commit
1de93c4d6e5c0947c59846fce13af872f9e1a9c3

🔍 Latest deploy log
https://app.netlify.com/sites/tech-works-for-us/deploys/63879ef4bd838c00099dd143


Grey screen few seconds after transfer started

When I initiate a transfer between my Macbook M1 Max and the my Xiaomi F2 Pro the transfer starts but the window goes grey after a few seconds. I have read in the issues that this happened to other users upon transferring large files but in my case the files transferred are not large. They are photos with size between 5MB and 45MB.

I'm actively working on this issue. Here is the pr, do watch it for further updates. https://github.com/ganeshrvel/openmtp/pull/303

Same issue on macOS Ventura

Hey @Sameerkash , this should probably get fixed by this weekend

@ganeshrvel I'm experiencing the same issue on OpenMTP Version 3.2.0 (<IP_ADDRESS>), but for me it stays green and transfer process seems is frozen. My Mac is running Ventura 13.1.

The fixes were pushed to the latest GitHub branche.
I'm working with cicd provider to make the release happen.

HI.  Just wondering if the fix for this made it into OpenMTP 3.2.0 ?  It's still happening for me on 3.2.0 / macOS 13.0.1 , Android 13 on a OnePlus 7T Pro (LineageOS)
Thanks
https://user-images.githubusercontent.com/12557929/214560396-f0ac7f93-d134-4f96-bf81-833c7cb2507c.mp4

OpenMTP v3.2.10-beta.1 is now rolling out.
Features

Fixes - the app crash on older versions of macOS
Fixes - the app crash caused while transferring files a large number of files.

If you are on an older version of OpenMTP and have frozen the auto-app update option for the sake of preventing the app crash, you may re-enable it from Settings > Updates > Automatically Check for Updates
Note: We have now officially retired the support for Kalam Kernel on macOS 10.13 (OS X El High Sierra) and lower. Though the "Legacy" MTP mode will continue working on these outdated machines.
Read more: https://github.com/ganeshrvel/openmtp/tree/release/3.2.10-beta.1#system-requirements-and-support
Download:

Apple Silicon (mac M1/M2): openmtp-3.2.10-beta.1-mac-arm64.dmg
Intel Silicon (Older mac): openmtp-3.2.10-beta.1-mac-x64.dmg

Hi,
Thanks for the response.
WIth 3.2.10-beta1 (Intel) I was able to successfully copy videos from Mac > Android.  Next I needed to copy some files from Android > Mac and instantly had the same "screen goes blank" issue when I started the transfer.
Environment is per my previous post.
Steve

Same for me. Mac to Android works, other direction not yet.

Certainly looking good on Mac > Android though.  I've just moved several GB / hundreds of files without issue.

A fix for this issue will be rolling out in 20 mins!

OpenMTP v3.2.10-beta.2 is now rolling out.
Note: This a pre-release version and it might be unstable. ⚠
Features

Fixes - the app crash while downloading files
Fixes - the app crash on older versions of macOS
Fixes - the app crash caused while transferring files a large number of files.

If you are on an older version of OpenMTP and have frozen the auto-app update option for the sake of preventing the app crash, you may re-enable it from Settings > Updates > Automatically Check for Updates
Note: We have now officially retired the support for Kalam Kernel on macOS 10.13 (OS X El High Sierra) and lower. Though the "Legacy" MTP mode will continue working on these outdated machines.
Read more: https://github.com/ganeshrvel/openmtp/tree/release/3.2.10-beta.1#system-requirements-and-support
Download:

Apple Silicon (mac M1/M2): openmtp-3.2.10-beta.2-mac-arm64.dmg
Intel Silicon (Older mac): openmtp-3.2.10-beta.2-mac-x64.dmg

Fixed the issue in https://github.com/ganeshrvel/openmtp/pull/314. Closing


Release 📦

📦 Release Pull Request
📝 Release Notes

Released focused on some hot fixes for the first release and then a falling pipeline.
🚧 Pre-Release Checklist

[ ]  ~All tests passed successfully.~
[x]  Code follows coding standards.
[x]  Documentation is up-to-date.
[x]  Dependencies are correctly updated.
[ ]  ~Continuous Integration (CI) pipelines passed.~

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


react-grid-layout "drag from outside" not working in mobile view

Describe the bug
Hello,
The react-grid-layout "drag from outside" is not working in mobile resolution. I have also attached the code sandbox link below for the reference.
I request to please look into the issue or please suggest if there is any solution to make it work in mobile view.
Thanks!
Your Example Website or App
https://codesandbox.io/s/react-grid-layout-nested-grids-drag-from-outside-forked-hs06sm?file=/dragFromOutside.js
Steps to Reproduce the Bug or Issue

Go to code sandbox link provided above.
Open the console.
Click on the "Toggle Device Toolbar" (for the mobile view).
The "drag drop from outside" is not working in mobile resolution.

Expected behavior
The "drag from outside" example is working in normal laptop screens but its not working in mobile resolution.
react-grid-layout library version
1.3.4
Operating System Version
Windows
Browser
Chrome
Additional context
No response
Screenshots or Videos
No response

import React, { useState } from "react";
import GridLayout from "react-grid-layout";
import "./styles.css";
import { WidthProvider } from "react-grid-layout";

const ResponsiveGridLayout = WidthProvider(GridLayout);

const dragFromOutsideItem = {
  w: 2,
  h: 2,
  x: 0,
  y: 0,
  i: "new-item"
};

export default function DragFromOutside() {
  const [layout, setLayout] = useState([]);

  const onDrop = (layout, item, e) => {
    setLayout([...layout, { ...dragFromOutsideItem, i: `new-item-${layout.length}` }]);
  };

  return (

 {
          // Manually start drag on touch start
          e.dataTransfer = new DataTransfer();
          e.dataTransfer.setData("text/plain", "");
        }}
        draggable
      >
        Drag me

      <ResponsiveGridLayout
        className="layout"
        layout={layout}
        cols={12}
        rowHeight={30}
        width={1200}
        isDroppable={true}
        onDrop={onDrop}
        measureBeforeMount={false}
        compactType={null}
        preventCollision={true}
      >
        {layout.map((item) => (

            {item.i}

        ))}
      </ResponsiveGridLayout>

  );
}


Add name safety to default exports

Suggestion
When using TypeScript, I tend to avoid default imports/exports because they can be named anything by default.
It would be nice if TypeScript enabled a method to annotate a default export to ensure it's imported with the expected name
// @ts:defaultExportName="myDefault"
export default 'foo'

Where consumers would be required to use the annotated default
import myDefault from './my-default'

Where this would result in an error or warning
import myDefaultt from './my-default'

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Where consumers would be required to use the annotated default
import myDefault from './my-default'

Where this would result in an error or warning
import myDefaultt from './my-default'

Why force the user to use a specific name? What would you as the library author actually gain from it? And what if the user already has a myDefault name in the scope?
It sounds more like you want a linter for your own source code that enforces a specific pattern.

Enforcing naming conventions is the job of a linter


main.dart in /bin vs project root?

Is there an intentional reason that main.dart lives in a bin/ sub-directory? This may send a mixed message to some users, as .dart files are not executable binaries.
Would it be reasonable to move main.dart to the project root, and reserve a bin directory for executable binaries (like tailwindcss)?

The standard location in a Dart package for executable files (not binary, just executable), is the /bin directory.
Please see Dart's official project structure docs: https://dart.dev/tools/pub/package-layout#command-line-apps

Ah. Okay. Fair enough. Thanks for sharing. Will close this issue.


Unable to get ImmutableGrowthData as mutable

Apparently this is a known issue, creating ticket for tracking.
java.lang.IllegalArgumentException: Applicable constructor not found for class: org.spongepowered.common.data.manipulator.mutable.block.SpongeGrowthData with args: [2, 0, 7, 0] ...
Full stack trace also available here, as GH issues seems to mangle the readability. https://gist.github.com/Zbob750/ae1899f632a58e556d67

@Zbob750: Is this still an issue?

IRC bump
<Z750> I have not tested to see if it is still an issue since the initial report
<Aaron1011> oh, that's a username :P
<Aaron1011> didn't realize you were in this channel
<Aaron1011> hello :)
<Z750> the stack trace linked in the issue has the code used at the bottom
<Z750> hi :)
<kashike> https://github.com/SpongePowered/SpongeCommon/blob/master/src/main/java/org/spongepowered/common/data/manipulator/mutable/block/SpongeGrowthData.java
<kashike> 3 arg ctor, no 4 arg
<Aaron1011> ooh, right
<Z750> ^ that was the original issue yes

https://github.com/SpongePowered/SpongeCommon/blob/master/src/main/java/org/spongepowered/common/data/manipulator/mutable/block/SpongeGrowthData.java


test

Product Description

Technical Summary

Safety Assurance
Safety story

Automated test coverage

QA Plan

Special deploy instructions

[ ] This PR can be deployed after merge with no further considerations.

Rollback instructions

[ ] This PR can be reverted after deploy with no further considerations.

Review

[ ] The set of people pinged as reviewers is appropriate for the level of risk of the change.

test

test

test

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this

@dimagotchi duplicate this


Added benchmark to compare grok and grokky

Result:
BenchmarkGrokkyVsGrokApacheLog/grokky-8         	    3000	    575750 ns/op
BenchmarkGrokkyVsGrokApacheLog/grok-8           	    3000	    567022 ns/op

Grokky looks OK but around 1% slower

Coverage remained the same at 100.0% when pulling a4aedc06fbcaad0d41e6234fc0bc9bc7693a1093 on nanjj:master into 24c9a8672290adc783b4d61d1ae78f64b9edb873 on logrusorgru:master.

Coverage remained the same at 100.0% when pulling a4aedc06fbcaad0d41e6234fc0bc9bc7693a1093 on nanjj:master into 24c9a8672290adc783b4d61d1ae78f64b9edb873 on logrusorgru:master.

Actually, RE2 is deterministic, Oniguruma is not.
// Intel Core i5-6200U
// DDR4 8G 2133 MHz
// Linux Ubuntu 17.04 4.12.4-041204-generic
//
// go test -bench . -benchtime=1m
//
// Benchmark_logrusorgru_grokky_rfc3339-4    30000000    3201 ns/op  1297 B/op  5 allocs/op
// Benchmark_vjeantet_grok_rfc3339-4         30000000    2967 ns/op  1329 B/op  5 allocs/op
// Benchmark_grokkyVsGrokApacheLog/grokky-4    200000  447480 ns/op  5098 B/op  6 allocs/op
// Benchmark_grokkyVsGrokApacheLog/grok-4      200000  473763 ns/op  5609 B/op  6 allocs/op
// PASS
// ok      github.com/logrusorgru/grokky   385.076s

Look at your benchmark result: 3201 > 2967.
So we can say grokky a little faster, but not really fast :-)

@nanjj , I think it may be slower then original C Oniguruma. Core of the grokky is very close to core of the grok. It's just golang regexp.

Look the benchmark:
BenchmarkGrokkyVsGrokApacheLog/grokky-8            3000     553254 ns/op

It means I can only handle 1.8 K nginx access log per second. It's too
slow. 20 K/s is an acceptable speed.
Another thing, I suggest you to change your license to a usual one, say
apache or BSD. Current license may prevent some potential users even
developers.
Thanks
On Sun, Aug 13, 2017 at 2:46 AM, Konstantin Ivanov<EMAIL_ADDRESS>
wrote:

@nanjj https://github.com/nanjj , I think it may be slower then
original C Oniguruma. Core of the grokky is very close to core of the grok.
It's just golang regexp.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/logrusorgru/grokky/pull/2#issuecomment-321998906, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnG6jffjMtn8VEKyk1FKD9NUeYCniyaks5sXfMegaJpZM4OxkE5
.

--
Cheers
Jun Jie Nan
∧ ∧︵
ミ^ō^ミ灬)～

Just simplify regexps. No-one need so strict regular expressions to parse logs. Take a look benchmark I have added. It's about 113 K/s for nginx access log (combined format).
About license. I don't want to complicate the world. Everyone can fork the grokky and redistribute it under MIT, BSD, CC0 or any other license he want. The WTFPL is best for users, who do not want to mess with rights, legals, etc. Users who know what license is, know how to redistribute the product. I don't want to force users to copy-paste copyright note or care about it more than a second.

Strict regular expressions are overkill.

It's great! Thanks!
On Fri, Aug 18, 2017 at 4:39 PM, Konstantin Ivanov<EMAIL_ADDRESS>
wrote:

Strict regular expressions are overkill.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/logrusorgru/grokky/pull/2#issuecomment-323295636, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnG6lT2QYn6Rtrjh5Q7pOvO6pcwZGxMks5sZU2tgaJpZM4OxkE5
.

--
Cheers
Jun Jie Nan
∧ ∧︵
ミ^ō^ミ灬)～

Also, check out More performance paragraph. The Parse method creates map[string]string every time, that may not be necessary in some cases.


[DOCFIX] Fix Language dropdown bug in new layout in os and add pr check

Fix Language dropdown in new docs layout shows English twice

alluxio-bot, merge this please


chore(deps): update github.com/openshift/api digest to 188620a (master)

This PR contains the following updates:

Package
Type
Update
Change

github.com/openshift/api
require
digest
611114d -> 188620a

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:Y0RJ/Y5g5wJpkTisOtqwDSo4HwhGmLB4VQSw2sQJLHk=
	go.sum:     h1:fB45yRUv8NstnjriLhBQLuOUt+WW4BsoGhij/e3PBqk=

SECURITY ERROR
This download does NOT match an earlier download recorded in go.sum.
The bits may have been replaced on the origin server, or an attacker may
have intercepted the download attempt.

For more information, see 'go help module-auth'.


Implement send method

I believe this plug in is for client-side of messaging.
Send is a server side function. I'm not sure this is a valid issue.

@quintonn https://firebase.google.com/docs/cloud-messaging/android/upstream

I also think this is a valid request. We need to use it with the XMPP server implementation.


[LOOP-3486] Restore title to therapy settings preview and review views

https://tidepool.atlassian.net/browse/LOOP-3486
Remove duplicate titles in therapy settings during onboarding

LW PR for build: https://github.com/tidepool-org/LoopWorkspace/pull/545


Question: Using SHAP with GPT-4 via API

Good evening,
I'm trying to use SHAP for my graduation thesis with various LLM, as Falcon, Mistral and GPT 4 and Llama, and i'm trying to follow the instruction with GPT-2 as in documentation but it's not possible to apply it to GPT-4, is there any solution to obtain Shapley Values with GPT-4 using SHAP?
I put an example of my code
import json
from langchain.chat_models import ChatOpenAI
import shap
with open('path/to/apikey.json', 'r') as file_json:
dati_json = json.load(file_json)
openai.api_key = dati_json['OPENAI_API_KEY']
chat = ChatOpenAI(temperature=0.0, openai_api_key =dati_json["OPENAI_API_KEY"] )
review_template = ["I enjoy walking with my cute dog"]
explainer = shap.Explainer(chat)
shap_values = explainer(t)
Thanks in advance!

No, there is no possibility to extract shap values from models that are extracted through APIs since one typically just gets the model outputs (and not even the tokenization or something) from these models.

Seems like no discussion is getting on here and as already said, this cannot be implemented.

Is there a way to leverage the existing SHAP API/examples?
The OpenAI models do return the log_probs for the top 20 tokens at each generation.
completion = client.chat.completions.create(
  model="gpt-4o",
  messages=[
    {"role": "user", "content": "Hello world!"}
  ],
  logprobs=True,
  top_logprobs=20
)

mark


Complete initial goals

The first is obviously extracting the text from the PDF.

Then we should have a step for Unicode normalization, based on the mapping in this file:
https://github.com/clulab/processors/blob/master/main/src/main/resources/org/clulab/processors/bionlp/unicode_to_ascii.tsv
This is needed to avoid the weird hyphen issue we ran into. There are other Unicode chars that are similar.

Add implicit end-of-sentence punctuation. That is, the generated text often include 2+ new lines to indicate different paragraphs. For example:

This is a Title
This is where the first paragraph begins...
Because sometimes lines that end a paragraph do not include end-of-sentence periods, processors thinks that the whole thing is a single sentence, which is wrong. I propose the following heuristic: if text is separated by 2+ new lines, and the line on top does not end with end-of-sentence punctuation, and " ." to it. That is, the text above becomes:
This is a Title .
This is where the first paragraph begins...

Merge broken words ("-" followed by 1 white space). That is, some words are separated into two fragments due to end of lines. In the generated text, they will show up separated by a dash followed by a white space, e.g.: "dis- close". These should be merged.

Merge broken words using language models. Similarly, some words are broken without the dash. In this case, we should probabilistically merge them using a language model (LM). For example, take the sentence:

"They decided to dis close something"
Using a language model, we should check if P("dis"|"They decided to") is larger than P("disclose"|"They decided to"). If not, then the two tokens should be merged into one. Masha and Mithun can help populating an API that computes P(text|text_that_precedes_it).

Thanks @kwalcock !


[settings] in single folder setting, both workspaceValue and workspaceFolderValue are set

open VSCode on a folder
have a workspace setting, e.g.

{
        "json.schemas": [{
            "fileMatch": ["view.json"],
            "url": "http://json.schemastore.org/bower"
        }]
}

in the extension host access the settings:

	let folders = workspace.workspaceFolders;
	if (folders) {
		folders.forEach(folder => {
			let jsonConfig = workspace.getConfiguration('json', folder.uri);
			let schemaConfigInfo = jsonConfig.inspect<JSONSchemaSettings[]>('schemas');

Observe that in schemaConfigInfo both workspaceValue and workspaceFolderValue are set. That looks wrong as in reality only one level of setting exists and there's no overwriting happing.
Depending on philosophy, either workspaceFolderValue should be undefined and workspaceValue set or the other way around.
I need this to find out if there are actually folder specific settings, or if it is enough to transmit just the global settings.

@aeschli I see your concern. Ideally in this case, workspaceValue should be undefined but this will break the API. Marking workspaceFolderValue as undefined looks wrong to me.
Happy to have suggestions.

Yes, I guess If you want to be backward compatible, then having workspaceFolderValue undefined is the right thing to do for the case that VSCode was opened on a folder. If VSCode was opened on a workspace with one folder, then 'workspaceFolderValue' should be set and 'workspaceValue' undefined.

The issue is still there but I've worked around it.


[x64] Add i64x2.all_true and i64x2.bitmask

These instructions already had CLIF implementations but were only recently approved in the Wasm SIMD working group. Additionally, this re-enables the simd_lane.wast spec tests (probably disabled waiting on wasm-tools?).

The latest push only enables simd_boolean.wast for x64 and aarch64; the old backend would need work and, since it already behind the other two and slated to be replaced, I was not planning on fixing it up.


Support for coolermaster's masterkeys pro models

Hi, I'm trying to add support for these models and I figured you guys could help me get past some issues. This is my first RE project, so feel free to point at any bizarre thing I'm doing.
Ok, so here's what I've got so far

Reversed part of the fw updater software. Basically, I've traced fread calls to figure out where the fw is inside the executable. This also led me to a de-mangling  function that partially "decrypts" the firmware. A funny thing that I've noticed is that it reads both the fw version string and the actual fw twice, from different locations. Maybe they're trying to "protect" patching?

As expected, the extracted binary is still "encrypted". I brute forced a 52 byte XOR key and it worked partially, some readable strings appeared and the vector table at the top took some shape.

At this point, I began looking for similar firmwares so I could fix the rest of the XOR key, turns out that my firmware is really similar to the one used by cypher model. I managed to fix the rest of key and now I may have a working dump.

Fiddled a bit with pok3rtool to add the right HID's for my model and both info and version commands worked. The offsets looks the same as cypher model(got it from the vector table) and the commands working point to that too, but I'm not sure.

The thing that broke my legs, is that I can't run the official update to capture the protocol. My model is already at the last version and It seems they never released a update for an ISO model. This means that I basically have two alternatives

Patching the fw updater to bypass all layout and version checks
Use this tool to upload my dump, but I'm not sure if the offsets and protocol are the same as cypher

Both alternatives seems kinda dangerous, since I'm not sure what happens if a different layout is used. Any pointers?
Oh, and I also could use some help understanding the boot model for these devices. From the data sheets, I thought that vector table was loaded from 0x0, but all of the firmwares start at an offset in the flash and they also have a vector table. If there was a builtin fw at 0x0, why the uploaded fw also needs a vector table?
Any help is really appreciated, so thanks in advance. This project was a great source of information

I'm don't know which keyboard you are looking at, but I found a firmware updater for the CM Masterkeys Pro L White on CM's website. I was able to extract and decrypt the firmware with my existing program. See updatepackage.cpp. I just added the following to the packages array:
// Cooler Master Masterkeys Pro L
{ 0x38cc849b2e54b6df,   MAAV102 },

And ran it as:
pok3rtool decode masterkeys-pro-l-white-v1.08.exe v108.bin

You will notice in the output there are six "sections". There are actually three firmware images with different layouts: US, EU, and KR(?). For each there is a firmware section, and a version info section. That is why you see the code reading from multiple locations. You'll have to hack updatepackage.cpp to dump the correct firmware section.
I broke the XOR key for one firmware updater a long time ago, and it keeps working. You can compare the XOR key you found to the one at the bottom of proto_cykb.cpp.
I suspect pok3rtool will work as-is for uploading firmware to this keyboard. You can try some of the more harmless commands before trying to flash firmware. The bootloader command will reset the keyboard to the bootloader. You can confirm it is in the bootloader with the version command. The setversion command will write the version string.
I assume your goal is to extract the bootloader?  My method is to disassemble and patch the application to allow me to read flash unrestricted using the update protocol. Look at https://github.com/pok3r-custom/pok3r_re_firmware/blob/master/disassemble/core/v104/patch_v104.txt for an idea of what these patches look like.

I'll try to explain how the boot process works.
There is a builtin bootloader firmware at 0x0 in flash. The bootloader will look for the main application firmware at a specific address. It looks like the firmware is loaded at 0x3000 (it should be a multiple of 0x400 to align to the flash page size). Different keyboards place the firmware at slightly different locations, depending on the size of the bootloader. The flash page before the application (e.g. 0x2c00) contains some information about the firmware, including the version string. The bootloader does a couple of things before jumping to the main firmware:

Check the initial SP and Reset vectors at 0x3000 are not erased
Check the version string at 0x2c00 is not erased
Check for a specific "key" in the application firmware at (e.g.) 0x3bf8 (older versions of the firmware, like on the POK3R, don't do this). This is to prevent booting the wrong firmware for that specific keyboard.

If any of these tests fail, the bootloader works as a simple keyboard. The firmware download function can also be used when the bootloader is running.
If all the checks pass, the bootloader jumps to the application firmware. The reason the application has its own vector table is so that different interrupt handlers an be used in the application. The VTOR register (vector table offset) can be used to specify the base of the vector table, for exactly this use case.

I don't know which keyboard you are looking at

My model is the masterkeys pro m white model.  I'll run your tool and compare the output against my own version.

I assume your goal is to extract the bootloader?

Yeah. Thanks a lot for the info. The boot process makes a lot more sense now, and I'll try to patch the firmware in a similar way to your example. I'm also guessing that flashing a non matching layout won't break the usb protocol, so I could eventually fix it on my own if some keys stop working. Have you ever flashed a mismatched layout?

It worked, got a full firmware dump and the patch is pretty much the same as your example
FW offset is 3200

        00006388 ff 28           cmp        r0,#0xff
        0000638a 05 d1           bne        LAB_00006398
        0000638c 68 68           ldr        r0,[r5,#0x4]
        0000638e 3c 21           mov        r1,#0x3c
        00006390 30 e0           b          LAB_000063f4
        00006392 00 bf           nop
        00006394 00 bf           nop
        00006396 00 bf           nop

If you are interested, I could PR the changes. It's only a few changes adding the correct device ids and mappings.

I am interested in this effort! I started working on support for Pro S RGB, but ran into issues along the way.
From my testing poking around USB with python scripts (and looking at disassembly), I found Pro S RGB had a lot in common with both POK3R and CYKB protocols (documented partially https://github.com/m-radomski/re-masterkeys/issues/1). With my findings, I started working on my own fork to better support my device (and other cooler master keyboards): https://github.com/hansemro/pok3rtool/tree/cooler-master-dev.
Unfortunately, I ended up bricking my keyboard by erasing firmware region (@0x3400) in my attempt to write stock firmware with pok3rtool. This result is leading me to believe that something is wrong with the write command (which works fine for setting version). @ChaoticEnigma  if you have time, can you help identify the cause of the issue? I have packet captures of firmware upgrade via OEM software and my failed attempt with custom pok3rtool.
pok3rtool attempt:
pok3rtool_fw_flash_attempt_with_erase.zip
OEM:
fw-upgrade.zip

@hansemro did you make any progress on the Pro S RGB? I have one here if I can create any dumps for you.

@ciarancoffey No further progress on fixing USB writes with Pro S RGB as I did not get a replacement keyboard.

@ciarancoffey Picked up one Pro S RGB and one Pro L RGB for cheap. I am going to learn my mistake and avoid directly wiping my board before I figure out how to write to an arbitrary address.

Managed to dump Pro L White bootloader and firmware without much difficulty.
Documented here: https://github.com/mateuszradomski/re-masterkeys/issues/3.
FW Patch + dump can be found here: https://github.com/hansemro/re-masterkeys/tree/Pro_L_White/binaries/Pro_L_White
pok3rtool with this patch should be sufficient: https://github.com/hansemro/re-masterkeys/blob/Pro_L_White/patches/pok3rtool/ProLWhite.patch

The glaring difference between my failed pok3rtool flash attempt and OEM software is that I did not encode firmware before writing.  Relevant commit: https://github.com/hansemro/re-masterkeys/commit/d5290eea057872d1318e6a2c73e9d700c03f3d1f
Now I just need to flash my new Pro S RGB with stock bootloader (although it is on 1.1.5 firmware that cannot be recovered).

Yup. Fixed USB writes with https://github.com/hansemro/pok3rtool/commit/11b822daccf6230801e9e4c1574e27bc54f884a1. Did a firmware upgrade from 1.1.5 to 1.2.2.

@ciarancoffey We should be good now :)  https://github.com/hansemro/re-masterkeys/blob/Pro_S_RGB/binaries/Pro_S_RGB/flash.dump
Time for me to recover my other board.

@ChaoticEnigma Got QMK up on the Pro S RGB and wrote (3-cascade) fully working MBIA043 RGB matrix driver. This should hopefully be useful for Vortex boards with the same LED driver (although it is unclear to me how RGB is achieved with 2-cascade configuration).
Note: I only flashed on board with security bits set, so I am not sure if I will run into hardfaults if I try flashing on a spare board with those bits set.
MBIA043 info: https://github.com/mateuszradomski/re-masterkeys/issues/1#issuecomment-1274826627
MBIA043 driver: https://github.com/hansemro/qmk_firmware/blob/prosrgb_mbia043_dev/keyboards/masterkeys/prosrgb/mbia043.c

On GK68XS, RGB is not separated by IC but by the individual channels on the ICs. This is likely what is being done for keyboards with just 2 LED drivers.

@hansemro That's awesome work, very cool! I was out of town last week, best I could do at the time was an emote!
It looks like I'll have to get back on the Vortex boards soon. I'll be stealing your MBIA043 driver!
I believe I did trace out the POK3R RGB LED rows/columns, and I think it's exactly as you say for the GK68XS.

@ChaoticEnigma It is only fair since pok3rtool and your firmware disassembly annotations were incredibly useful.

Here is Pro L White QMK port with MBI5042 LED driver support: https://github.com/hansemro/qmk_firmware/tree/prolwhite_mbi5042_test/keyboards/masterkeys/prolwhite
MBI5042 driver: https://github.com/hansemro/qmk_firmware/blob/prolwhite_mbi5042_test/keyboards/masterkeys/prolwhite/mbi5042.c
One thing to note here is that you may need additional "LED matrix to LED index" look-up-matrix if LED matrix and Key matrix do not map to the same keys (like on Pro L White). On Pro S RGB, LED and Key matrices mapped to the same keys so I did not have to define this extra mapping.
@ChaoticEnigma Let me know if you have questions or improvements.


Bug report: script sample for teams active users fails

Priority
(Medium) I'm annoyed but I'll live
Description
The script sample executes all steps but fails on sending a correct card. It sends an empty card and throws an error in the script.
Error: true is not a valid GUID
Run 'm365 entra user get -h' for help.
Error: true is not a valid GUID
Run 'm365 entra user get -h' for help.

And then an empty card being send
Steps to reproduce
Copy paste script from: https://pnp.github.io/cli-microsoft365/sample-scripts/teams/recognize-most-active-users-specific-team/ and run with parameters results in an error:
Expected results
A working card containing user score
Actual results
An empty card and errors in the terminal
Diagnostics
N/a
CLI for Microsoft 365 version
tested on v8, v9 and current beta
nodejs version
v18.19.0
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
No response
Additional Info
No response

Can be solved by adding changing the following line:
https://github.com/pnp/cli-microsoft365/blob/4ee36d4e4fe56d9747d57b52d8af159c07b535e2/docs/docs/sample-scripts/teams/recognize-most-active-users-specific-team/index.mdx?plain=1#L92
To $user = m365 entra user get --id $teamsUser.Name --output json | ConvertFrom-Json
The userId does not exists, we need the Name property as that is the name of the group:


⚠ Secret Website 2 has degraded performance

In 8d06317, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 7297 ms

Resolved: Secret Website 2 performance has improved in 1f0cce1.


Feature: Support servicePrincipals appRoleAssignments

We would like support for CRUD of service principals app role assignments.
https://docs.microsoft.com/en-us/graph/api/resources/approleassignment?view=graph-rest-1.0
This can then eventually be incorporated into the Terraform AzureAD provider to alleviate workarounds such as this.

@manicminer I will look into this issue. Feel free to assign it to me.

Good day, upon looking at the PR #39 i noticed the addition of (List/Remove/Assign)AppRoleAssignments in service principal which is awesome. Upon reading the graph documentation I noticed the Microsoft suggests best practice for app role assignments is to use AppRoleAssignedTo. Is there a plan to add these 3 endpoints?
Using the existing code i extended the serviceprincipal struct for my current solution to add those 3 functionalities but I do not want to step on anyone's toes, here is what i user if it helps as a starting point:
// ListAppRoleAsssignedTo retrieves a list of appRoleAssignment that users, groups,
// or client service principals have been granted for the given resource service principal.
func (c *ServicePrincipalsClient) ListAppRoleAsssignedTo(ctx context.Context, id string) (*[]AppRoleAssignment, int, error) {
	resp, status, _, err := c.BaseClient.Get(ctx, GetHttpRequestInput{
		ValidStatusCodes: []int{http.StatusOK},
		Uri: Uri{
			Entity:      fmt.Sprintf("/servicePrincipals/%s/appRoleAssignedTo", id),
			Params:      url.Values{"$select": []string{"id"}},
			HasTenantId: true,
		},
	})
	if err != nil {
		return nil, status, fmt.Errorf("ServicePrincipalsClient.BaseClient.Get(): %v", err)
	}
	defer resp.Body.Close()
	respBody, err := ioutil.ReadAll(resp.Body)
	if err != nil {
		return nil, status, fmt.Errorf("ioutil.ReadAll(): %v", err)
	}
	var data struct {
		AppRoleAssignments []AppRoleAssignment `json:"value"`
	}
	if err := json.Unmarshal(respBody, &data); err != nil {
		return nil, status, fmt.Errorf("json.Unmarshal(): %v", err)
	}
	return &data.AppRoleAssignments, status, nil
}

// AddAppRoleAssignedTo assigns an app role for a resource service principal, to a user, group, or client service principal.
func (c *ServicePrincipalsClient) AddAppRoleAssignedTo(ctx context.Context, servicePrincipalID, principalID, resourceID, appRoleID string) (*AppRoleAssignment, int, error) {
	var status int
	data := struct {
		PrincipalID string `json:"principalID"`
		ResourceID  string `json:"resourceID"`
		AppRoleID   string `json:"appRoleID"`
	}{
		PrincipalID: principalID,
		ResourceID:  resourceID,
		AppRoleID:   appRoleID,
	}

	body, err := json.Marshal(data)
	if err != nil {
		return nil, status, fmt.Errorf("json.Marshal(): %v", err)
	}
	resp, status, _, err := c.BaseClient.Post(ctx, PostHttpRequestInput{
		Body:             body,
		ValidStatusCodes: []int{http.StatusCreated},
		Uri: Uri{
			Entity:      fmt.Sprintf("/servicePrincipals/%s/appRoleAssignedTo", servicePrincipalID),
			HasTenantId: true,
		},
	})
	if err != nil {
		return nil, status, fmt.Errorf("ServicePrincipalsClient.BaseClient.Post(): %v", err)
	}
	defer resp.Body.Close()
	respBody, err := ioutil.ReadAll(resp.Body)
	if err != nil {
		return nil, status, fmt.Errorf("ioutil.ReadAll(): %v", err)
	}
	var appRoleAssignment AppRoleAssignment
	if err := json.Unmarshal(respBody, &appRoleAssignment); err != nil {
		return nil, status, fmt.Errorf("json.Unmarshal(): %v", err)
	}
	return &appRoleAssignment, status, nil
}

// DeleteAppRoleAssignedTo deletes an appRoleAssignment that a user, group, or client service principal has been granted for a resource service principal.
func (c *ServicePrincipalsClient) DeleteAppRoleAssignedTo(ctx context.Context, servicePrincipalID, appRoleAssignmentID string) (int, error) {
	_, status, _, err := c.BaseClient.Delete(ctx, DeleteHttpRequestInput{
		ValidStatusCodes: []int{http.StatusNoContent},
		Uri: Uri{
			Entity:      fmt.Sprintf("/servicePrincipals/%s/appRoleAssignedTo/%s", servicePrincipalID, appRoleAssignmentID),
			HasTenantId: true,
		},
	})
	if err != nil {
		return status, fmt.Errorf("ServicePrincipalsClient.BaseClient.Delete(): %v", err)
	}
	return status, nil
}

Hi @zbergus,
thank you for your comment and contribution. You are right about using the appRoleAssignedTo method as best practice.
It is already part of the existing PR, listing the relevant functions here below:

func (c *ServicePrincipalsClient) ListAppRoleAssignments(){}
func (c *ServicePrincipalsClient) AssignAppRoleForResource(){}
func (c *ServicePrincipalsClient) RemoveAppRoleAssignment(){}

hi @michaljirman I apologize!
I should have taken a look a bit more at the endpoint being used, I assumed from the method names that the other endpoints for the service principal were being used /appRoleAssignments
Very glad to find out it is the /appRoleAssignedTo endpoint being used!

no worries @zbergus!
Maybe just my choice of the method names is not clear enough.

This was added in #39


ValueError: The condensed distance matrix must contain only finite values

using python 3.8, just installed panoview yesterday and got this error:
>>> C56.RunSearching()
Percentage of cells being analyzed: 26%
Percentage of cells being analyzed: 27%
Percentage of cells being analyzed: 30%
Percentage of cells being analyzed: 31%
Percentage of cells being analyzed: 37%
Percentage of cells being analyzed: 45%
Percentage of cells being analyzed: 51%
Percentage of cells being analyzed: 54%
Percentage of cells being analyzed: 58%
Percentage of cells being analyzed: 61%
Percentage of cells being analyzed: 62%
Percentage of cells being analyzed: 67%
Percentage of cells being analyzed: 97%
Percentage of cells being analyzed: 98%
Percentage of cells being analyzed: 99%
Clusters generated
>>> C56.OutputResult()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/gpfs/gsfs12/users/CSD/zfext/env2/lib/python3.8/site-packages/PanoramicView/scPanoView.py", line 509, in OutputResult
    linkage_matrix = linkage(sim_mat,method="ward")
  File "/gpfs/gsfs12/users/CSD/zfext/env2/lib/python3.8/site-packages/scipy/cluster/hierarchy.py", line 1057, in linkage
    raise ValueError("The condensed distance matrix must contain only "
ValueError: The condensed distance matrix must contain only finite values.

Thank you.

The above error happened when I provided the raw counts csv as an input. It is not clear what the input should be so I looked at the example PollenRaw.csv file and there the samples (columns) are normalized to sum to 1e6 (there seems to be no log-transform and no centering; all values are >=0). When I did such a normalization to my counts I did not see the error above and OutputResult() worked. Not sure though why counts matrix would behave differently ...


Option to disable thread exit logging in launch.json

Desired Behavior:
I'd like the ability to disable thread exit messages in the Debug Console. Options already exist for other types of messages such as module loads (under logging.moduleLoad), so this would simply be another one added to the list.

VSCode Version: Code - Insiders 1.17.0-insider (ac167c41bababe6c47180012723fa2bc52610ff4, 2017-09-07T05:24:04.020Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

python
don
0.7.0

Lua
key
0.0.9

cpptools
ms-
0.12.3

code-settings-sync
Sha
2.8.3

Steps to Reproduce:

Launch a C++ program under the debugger
Notice "The thread #### has exited with code 0 (0x0)" messages in the Debug Console

This issue was moved to Microsoft/vscode-cpptools#1017


Allow closing stdin pipe

Hello,
The current implementation seems solid (I really like that Amp ecosystem!), but the API is somewhat closed and limited.
I personally need to close the stdin pipe after having sent the data to the spawned process, that waits for stdin to be closed before processing.
I've made a rapid and "dirty" patch to the library to add Process#closeStdin() because I need it right now.
Feel free to comment, merge, ask for more commits, cleaner implementation or simply close the PR without explanation :)
Example :
Amp\run(function() {
    $process = new Amp\Process('cat');
    $execution = $process->exec();

    yield $process->write("Hi!\n");

    $process->closeStdin(); // `cat` waits indefinitely without that

    yield $execution;
});

@trowski I've only now realized here's a PR pending (sorry @toverux for the long wait) .
I see no issue with the concept, do you? If not, I'll check implementation tomorrow and merging. (going to bed soon.)

I saw the PR, thought it'd be already merged, oops. Sorry for the delay, @toverux.

@bwoebi This one fell under my radar as it's targeted at Amp v1. I see no issues with this. The refactor for Amp v2 already made this possible.

Thanks for the sudden attention :D
Yes it's targeting Amp v.1 so don't bother yourself too much with it since it's not in your current priorities. I didn't wait at the time and told Composer to install it from my fork, and I don't use it anymore.


parser: support cast as double

What problem does this PR solve?
Related TiDB PR: https://github.com/pingcap/tidb/pull/11443
Support cast(xxx as double).
Mysql support the parser in 8.0.17.
https://dev.mysql.com/doc/refman/8.0/en/cast-functions.html

 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.

Please include a test case showing that CAST(x AS DOUBLE) is now a valid expression.
Rest LGTM.
CAST(x AS FLOAT), CAST(x AS FLOAT(p)) and CAST(x AS REAL) are also added in 8.0.17, would you mind at least supporting CAST(x AS FLOAT) in this or a future PR? Thanks.

UPDATE. PTAL @kennytm
And I will try to support CAST(x AS FLOAT) in next PR.


Create TODO Application.md

📝 Description
Created a TODO application using ILLA Builder.
Navigate your tasks effortlessly with this application - your ultimate to-do companion.
💣 Is this a breaking change (Yes/No):

[ ] Yes
[x] No

🚧 How to migrate?
Don't need.
📝 Additional Information

The second badge plz @holopin-bot @NewtonFernandis


Update awssdk:auth, awssdk:core, ... to 2.17.129

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:core
software.amazon.awssdk:regions

from 2.17.126 to 2.17.129.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #31.


pre-commit issue with types-pkg-resources

I can't get pre-commit working on my computer. This seems to be because the dependency types-all requires types-pkg-resources which has been yanked from PyPI - https://pypi.org/project/types-pkg-resources/#history. So types-all fails to install

Yes, I hit this a week or two ago. Thanks for reporting! I added types-all as a stop-gap to be lazy and not track down individual typing packages, but we can definitely just do that.


please add tag for 1.7.0 release

we use github tarballs in debian (to make sure we always build from source).

Thanks for pointing that out. I had followed the usual process and made the tag, not sure why it didn't get pushed at the time.


Can not find the Auther?

hi. I want to know how to bulid The SourceCode Zip from the Code.?
i download the  code from git that Selenium of the offical site.but cann't export SourceCode Zip can linked!
Best Regards

@iqpkeq not really sure what you're asking for here...? Are you asking about building Selenium itself from source? If so, you'd need to go to their repository. This is just a library to pull the JAR into a Composer package...

@asgrim i'm meaning that i got  selenium-server-standalone.jar ;But i cann't find selenium-server-standalone-source.jar (maybe different name?) on the Office site.

@iqpkeq Sorry, but this is not the repo for the actual code for selenium-server-standalone. You'd need to check on https://www.seleniumhq.org/ for where that is located. As I said, this library just redistributes the JAR in a Composer package for PHP users, we don't have any source code for it here.


Any idea to port to mono?

Have you ever considered porting Wox to mono so that Linux users can also benefit from it? kupfer is super, but not the alfred way; unfortunately I have not found other launchers as powerful and neutral as that.

WPF is not available on Mono...

Sorry about that :disappointed:


Recommended changes resulting from automated audit

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.
We encourage you to make the following modifications:

[ ] You are currently referencing Cake.Core 0.26.0. Please upgrade to 0.28.0
[ ] You are currently referencing Cake.Common 0.26.0. Please upgrade to 0.28.0
[ ] The Cake.Core reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Core" Version="0.28.0" PrivateAssets="All" />
[ ] The Cake.Common reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Common" Version="0.28.0" PrivateAssets="All" />
[ ] The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.rawgit.com/cake-contrib/graphics/a5cf0f881c390650144b2243ae551d5b9f836196/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.org and in the project on github.

@Jericho Thanks for the heads up. Am I correct in assuming these are the best-practices you are talking about?

Yes it is. Although, to be honest with you, I don't think the page is fully up to date. For instance, it's still talks about 0.22.0 being the most recent version of Cake and it also talks about IL merging your dependencies which is no longer necessary.


rename platform to system_info

There is a system module named platform, which can conflict with Platform

LGTM

merged as part of https://github.com/lbryio/lbry/pull/339


release.create-github-release: Use current version not next one

What does this PR do?

[!NOTE]
You should review the 2 commits distinctly.

This task used the next tag but should use the latest one instead.
Moved version helpers within the proper module.
Motivation
Describe how you validated your changes

Possible Drawbacks / Trade-offs
Additional Notes

/merge


When showing the sidebar, keep focus in the editor

If I'm editing in an editor on a file, and I show the sidebar with Cmd+B, then focus is lost from the editor, so I can't continue typing code until I close the sidebar again.
Please instead keep focus on the editor, or add an option to do so.

Duplicate of #46092


Refactor/no-server-model

Simplify the extension by removing server-client model between background and panel. It was getting too complicated. See branch feat/chrome-debugger-connection to understand.

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


Fix typo in replay engine

Fixed typo: "Replay doens't have actions" → "Replay doesn't have actions"

uh


scheduler: Include restarted jobs when counting host jobs

job.restartTimer is non-nil for any job that was a restart of another job, even when that job is running. This means that checking for a nil job.restartTimer causes GetHostJobCounts to ignore jobs which are restarts of others, regardless of whether those jobs are running or not, and thus can lead to too many jobs running on a single host.
This caused errors in a user's cluster because omni jobs were being placed unevenly, leading to the surplusOmniJobs routine stopping them, but then anti-entropy then placing the job unevenly again, leading to the omni job flapping indefinitely.
Fixes #2757.

LGTM


KYLIN-4163 have yarn app url when creating flat hive table job running

Can one of the admins verify this patch?

Codecov Report

Merging #856 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master    #856      +/-   ##
===========================================
- Coverage     25.61%   25.6%   -0.01%
  Complexity     6068    6068
===========================================
  Files          1399    1399
  Lines         83654   83666      +12
  Branches      11722   11724       +2
===========================================
- Hits          21431   21426       -5
- Misses        60165   60181      +16
- Partials       2058    2059       +1

Impacted Files
Coverage Δ
Complexity Δ

...a/org/apache/kylin/job/common/PatternedLogger.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...lin/source/hive/CreateFlatHiveTableByLivyStep.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...che/kylin/source/hive/CreateFlatHiveTableStep.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...he/kylin/job/impl/threadpool/DefaultScheduler.java
74.41% <0%> (-2.33%)
12% <0%> (ø)

.../apache/kylin/cube/cuboid/TreeCuboidScheduler.java
63.84% <0%> (-2.31%)
0% <0%> (ø)

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build 5048

0 of 12 (0.0%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.005%) to 28.074%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-job/src/main/java/org/apache/kylin/job/common/PatternedLogger.java
0
2
0.0%

source-hive/src/main/java/org/apache/kylin/source/hive/CreateFlatHiveTableByLivyStep.java
0
5
0.0%

source-hive/src/main/java/org/apache/kylin/source/hive/CreateFlatHiveTableStep.java
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

source-hive/src/main/java/org/apache/kylin/source/hive/CreateFlatHiveTableByLivyStep.java
1
0.0%

source-hive/src/main/java/org/apache/kylin/source/hive/CreateFlatHiveTableStep.java
1
0.0%

core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java
2
80.23%

Totals

Change from base Build 5041:
-0.005%

Covered Lines:
23488

Relevant Lines:
83666

💛  - Coveralls


Behaviour of yf download when certain symbols fail to download (no error bug!)

If yf download fails to download certain symbols, it should continue and go to the next symbol without generating a bug.
The pre-release version yfinance-0.2.19b3 generates a bug when there is a symbol that could not be downloaded:
https://github.com/ranaroussi/yfinance/issues/1526#issuecomment-1559588523
However, the release-version 0.2.18 simply says that the download failed but continues to download the next symbols WITHOUT generating an error bug:
https://github.com/ranaroussi/yfinance/issues/1526#issuecomment-1559707072
Describe the solution
When the user gives a long list of tickers to yf.download, chances are that some tickers can not be downloaded. If this is the case, yf-download should simply continue with the next symbol without generating a bug. It should simply continue to behave like up to version 0.2.18.
Additional context

generates a bug

Then please use the 'Bug report' template not 'Feature request'


Do keys still make sense at the current granular level?

We will add Network queries to Weaviate.

How will we handle keys in there?
Are keys still aligned with the current vision of what Weaviate should be?

We aligned on this IRL this morning; we don't know yet for the Network; for GraphQL, we'll for now require that the user has a Root Key (and therefore is allowed to access all data).


Fallback for accessing properties on symbols of proxy types

Looks like the crash can only happen with case vals, so a simple fallback will work. (Those types don't have any params either way)

Awesome, thanks! :)

This closes #413


typo: indiate -> indicate

@nschonni, there's more wrong here than the misspelling, so I'll mark it as awaiting feedback.
@HongGit, the text "failure, however it is unsure of the transaction outcome and request its status." is problematic; I think it should read "failure; however, it is unsure of the transaction outcome and requests its status." Is that OK?

@rpetrusha, I agree with your change. I also approved the change from indicate -> indicate.
Thanks!


[FEA]: The "More" option in category section should redirect to there respective youtube videos.

Category

[x] Resource Addition
[x] User Interface
[x] Feature Request

Description
In the category section, the "More" button in the boxes should redirect the user to their respective youtube videos.

Hey @Ashutosh104, these links should actually link to their respective pages in the domain. But the pages are not made yet, so the links will not work for now and hence, we're closing this one.


fix(tegel): remove base value and use px instead of rem

Describe pull-request
Refactored tegel to not import reboot.scss. This removes the font-size: 4px on on the html tags. Removed the use of rem is all components/stories. Refactored all use of rem to px in theme/core. Refactored all use of rem to px in spacing and typography.
Solving issue
Fixes: AB#2522
How to test

Checkout branch and run npm build on root level.
Cd into tegel and run npm run tegel
Check in Foundations -> Grid/Spacing/Typography and make sure the stories look good.
A couple of random components and make sure the are using the correct px instead of any rem values.

Screenshots
Additional context

Although i now see the vertical spacing in the migration document got substantially bigger

LGTM

Nice, since it's a pretty big change I'll hold off on merging it until we have had some more reviews ✌🏻

Please remove "@scania/typography": "^1.2.1" from Tegel's package.json file, drop node_modules and run the installation again. Let's see how Tegel behaves without it. I would like the Tegel package consumes "raw" typography SCSS and let Stencil compiles it so we can see immediate changes - same as we did for spacing, colors etc... I think it might be cleaner and won't give us false positives or false negatives.
PS: Typography stories will brake, but it gives a good hint about which "raw" typography files we have to include in globals.scss  .

Good idea! I have removed it now and it seems like the only thing affected is the typography story 😄


convert the text columns to libsvm format using feature hasher from scikit learn ?

https://github.com/zygmuntz/phraug/blob/master/csv2libsvm.py links to a code which only works for numeric data , but I have CSV file for machine learning which has mostly text data and most columns have a large cardinality , eg: a column with name of a person. Ideally would like to use the scikit learn's feature hasher or a vectorizer to generate the file in libsvm format hashing the text feature values to appropriate numeric values.
Note:
The graphlab ML library takes inputs with non numeric values in its Sframe and the Sframe is used in the classifiers like xgboost. So it is already doing what I require but it is not opensource and we dont get the numeric table output from the sframe. Most likely graphlab is using some featurehasher internally to keep track of the mappings between the text values and numeric values.
So how to convert the text columns to libsvm format using feature hasher from scikit learn ?

closing this for now as this seems goes beyond scope of the classifier but more of feature scripting question


Duckduckgo browser crashed on Windows 10 x64

See attached events from Windows log
DuckDuckGo-crash-event.zip

one more crash, see

DuckDuckGo-crash-event2.zip

Hi - I will pass this on to the Windows team, but this repo is for Apple related code.  Thanks for using DuckDuckGo!


Add additional reveal options

Add options to the reveal menu to show specific roll details for individual rolls. This will allow GMs to reveal e.g. only dice rolls, or only totals, for individual hidden GM rolls.

+1 for this.  Specifically, I'd like to be able to reveal the description under certain circumstances.

+1 from me for this, too. Specifically, it'd be awesome if we can show damage totals without the formula behind it. For example, if a weapon does 1d8 bludgeoning and 2d6 fire damage, the chat card shows the total damage, as well as the results for each damage type (marked in green), but not the formulae behind the total (marked in red).

No idea if that is even possible, but for the way players need to access info about damage types with regard to resistances, it would be very useful to have this kind of "light" sanitization.


Add Readarr integration

Details
Describe the solution you'd like:
Integrate Readarr since its part of the "arr" apps but for reading.
Anything else you would like to add:
No API documentation but the API is very similar to Lidarr, see https://github.com/Readarr/Readarr/tree/develop/src/Readarr.Api.V1
Additional Information:

https://readarr.com/

Can work on this now if you're okay with the integration @onedr0p

Absolutely, I would just make sure we label this as "alpha" in the docs because Readarr doesn't have a "stable" or even "beta" release yet

Sounds good!

API docs exist here, now:
https://readarr.com/docs/api/

ghcr.io/onedr0p/exportarr:master has the latest bits for readarr, I would love for people to try it out and report back if there are any problems. If I don't hear anything I'll go ahead and make a release.


Add Nuget .nuspec file to source and a way of building the package

I've already added Exception Reporter as a NuGet library but it needs updating and to be added to the source tree

I've added the .nuspec file in "packaging" folder. Now just need to setup something that builds a nuget package automatically

More recent versions of Visual Studio handle nuget packaging within the project, so I'm doing this


Add LICENSE

Project states MIT license but lacks the explicit terms. The this is unnecessarily ambiguous and as such creates a potential legal liability for users.
This PR simply adds the MIT license from https://choosealicense.com/, with the current year and the author's name (grabbed from Twitter - please correct this prior to merging if it is not accurate) filled in.
Please let me know if you have any questions or concerns.

Thanks @Nolij !


update

Codecov Report

Merging #16 into master will increase coverage by 8.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
+ Coverage   78.84%   86.95%   +8.11%
==========================================
  Files          13        4       -9
  Lines         104       69      -35
  Branches        8        3       -5
==========================================
- Hits           82       60      -22
+ Misses         21        8      -13
  Partials        1        1

Impacted Files
Coverage Δ

angular/src/app/app.component.ts

angular/src/app/navpages/home/home.component.ts

angular/src/app/firebase/data/data.component.ts

angular/src/app/navpages/page1/page1.component.ts

angular/src/app/navpages/page0/page0.component.ts

angular/src/app/navpages/main/main.component.ts

angular/src/app/navpages/auth/auth.component.ts

angular/src/app/navbars/navbar/navbar.component.ts

angular/src/test.ts

Continue to review full report at Codecov.

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


Remove some unnecessary closures

clippy nightly started warning about this use of ok_or_else() and
suggests to use ok_or() instead. I agree that this makes sense.
Signed-off-by: Uli Schlachter<EMAIL_ADDRESS>

Just remember how my code looked like before clippy and rustfmt ;-)


Let's ship 0.8.0

Since we've bumped libsass to 3.2 let's release!

lmk if you need any assistance with the rollout :D

err actually let's pick up the bugfixes in 3.2.1 and 3.2.2

It’d better to include 3.2.1 and 3.2.2 as well.  Thank you for #64.


sort imports according to PEP8 for components starting with "X"

Description:
I have sorted the imports for the components that start with the letter "x" according to PEP8 using isort.
I think it would be good if in the future we can add isort to the .pre-commit-config.yaml.
To do that I will first fix all sorting issues per component.
This PR affects:

homeassistant/components/x10/light.py
homeassistant/components/xbox_live/sensor.py
homeassistant/components/xeoma/camera.py
homeassistant/components/xfinity/device_tracker.py
homeassistant/components/xiaomi_tv/media_player.py
homeassistant/components/xmpp/notify.py
homeassistant/components/xs1/climate.py
tests/components/xiaomi/test_device_tracker.py

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Please name the PRs with capital letter in the first word of the title.

@MartinHjelmare, done!

I meant to change "sort" to "Sort".

Don't worry, I'll pick them up during the merge.