Tabs with scrollButtons="on" in vertical orientation does not always show scrollbuttons

Tabs with scrollButtons="on" in vertical orientation does not always show scrollbuttons.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
scrollButtons="on" works exactly like scrollButtons="auto". I.e. button is hidden when you can not scroll anymore in that direction.
Expected Behavior 🤔
The buttons should always be present, regardless of scroll position. I guess the buttons should be disabled when you can not scroll anymore in that direction. Not hidden as they are currently.
Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-g4kng?file=/demo.tsx
Switch between scrollButtons="on" and scrollButtons="auto" and nothing changes.
Context 🔦
Horizontally aligning other content to vertical oriented tabs with sometimes hidden buttons is a mess.
Your Environment 🌎

Tech
Version

Material-UI
latest

React
latest

Browser
Chrome

TypeScript
latest

The buttons should always be present, regardless of scroll position.

@daniel-primea This is already the case:

You can provide a custom ScrollButtonComponent for this case:

However, I think that it would be interesting to allow even more customizations. What do you think about

Making TabScrollButton public
Adding a new ScrollButtonProps prop
Applying this diff so people can easily customize the disabled/invisible/inactive look

diff --git a/packages/material-ui/src/Tabs/TabScrollButton.js b/packages/material-ui/src/Tabs/TabScrollButton.js
index 552166546..5e25f4098 100644
--- a/packages/material-ui/src/Tabs/TabScrollButton.js
+++ b/packages/material-ui/src/Tabs/TabScrollButton.js
@@ -19,30 +19,25 @@ export const styles = {
       transform: 'rotate(90deg)',
     },
   },
+  disabled: {
+    opacity: 0,
+  },
 };

-/**
- * @ignore - internal component.
- */
 const TabScrollButton = React.forwardRef(function TabScrollButton(props, ref) {
   const { classes, className: classNameProp, direction, orientation, visible, ...other } = props;

-  const className = clsx(
-    classes.root,
-    {
-      [classes.vertical]: orientation === 'vertical',
-    },
-    classNameProp,
-  );
-
-  if (!visible) {
-    return <div className={className} />;
-  }
-
   return (
     <ButtonBase
       component="div"
-      className={className}
+      className={clsx(
+        classes.root,
+        {
+          [classes.vertical]: orientation === 'vertical',
+          [classes.disabled]: !visible,
+        },
+        classNameProp,
+      )}
       ref={ref}
       role={null}
       tabIndex={null}
@@ -81,4 +76,4 @@ TabScrollButton.propTypes = {
   visible: PropTypes.bool.isRequired,
 };

Yes that sounds like a reasonable enhancement.
Thank you @oliviertassinari

Great, if you wish to take the lead on it, we would be happy to review a pull request.

Can I take this?

@netochaves Sure :)


ciClean is always trying to _mkdir

This is creating a nativecommanderror every time this is run which is noisy and unnecessary
[ERROR] + .\lib\vendor\bin\phpqa --config .\lib\tests --buildDir .\ ...
[ERROR] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ERROR]     + CategoryInfo          : NotSpecified: ( [Filesystem\Cl...Lib\tests\build
[ERROR]    :String) [], RemoteException
[ERROR]     + FullyQualifiedErrorId : NativeCommandError
[ERROR]
[ERROR]  [Filesystem\FilesystemStack] mkdir [".\lib\tests\build"]
Simple fix only calls the mkdir command if the directory doesn't actually exist

mkdir from symfony/filesystem used in robo is skipping existing directory .
What is your OS? I never saw such error.
Anyway I don't understand why you are using current directory or parent directory --buildDir. It can delete some files you don't want to. I would use subdirectory

This is on Windows 10, and because of other tooling the directory needs to be both configurable and existing (even though it's empty) ... stupid TFS

@auroraeosrose: try to ask in symfony/filesystem. If it's not problem in symfony, then I'll reopen and merge your PR. But AFAIK _mkdir should not create a new directory, if already exists.


KAFKA-17110: Enable valid test case in KafkaConsumerTest for AsyncKafkaConsumer

Enable testResetToCommittedOffset, testResetUsingAutoResetPolicy, testCommitsFetchedDuringAssign, verifyPollTimesOutDuringMetadataUpdate, testFetchStableOffsetThrowInCommitted, testFetchStableOffsetThrowInPosition, testNoCommittedOffsets, testPollThrowsInterruptExceptionIfInterrupted, fetchResponseWithUnexpectedPartitionIsIgnored, testManualAssignmentChangeWithAutoCommitEnabled, testManualAssignmentChangeWithAutoCommitDisabled, testOffsetOfPausedPartitions, and testCloseShouldBeIdempotent for AsyncKafkaConsumer
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@FrankYang0529 please rebase code to trigger KafkaConsuemrTest

@FrankYang0529 please rebase code to trigger KafkaConsuemrTest

Rebased it. Thank you.

@FrankYang0529 Could we simplify this PR to enable the tests which work well even though we don't add any changes? We can have more discussion for other tests later

@FrankYang0529 Could we simplify this PR to enable the tests which work well even though we don't add any changes? We can have more discussion for other tests later

Agree, let address FindCoordinatorResponse issue in https://issues.apache.org/jira/browse/KAFKA-17129.


Get Code of Conduct for initial launch

Rolling into https://github.com/GoogleChrome/devsummit/issues/184


DongleSendSMSAction send only first line

Hello,
when i try to send multi-lines SMS by DongleSendSMSAction , it's send only first line and ignore other lines .
what i can do to solve this issue ?
$SMS = new DongleSendSMSAction("dongle1", "+10987654321","hello \n Test SMS") ;
Thanks

It seems you're not the only one having this issue with dongle. I suggest open them an issue.
Thanks!

Thank you marcelog
I can use dongle to send multi-lines sms by using "spool call file"
by put it as base64 value => base64_encode($Msg);
Setvar: SmsText=2KjYs9mFINin2YTZhNmHINin2YTYsdit2YXZhiDYp9mE2LHYrdmK2YUKCdmH2K/Zh9ivCgk=
And Use
exten => 101,1,DongleSendSMS(dongle1,${Destination},${BASE64_DECODE(${SmsText})},1440, yes)
my issue now is only , how to send it by php PAMI ?

Great!
You can manipulate call files with PAGI, See: http://marcelog.github.io/articles/pagi_tutorial_create_voip_telephony_application_for_asterisk_with_agi_and_php.html the seccion called "Spooling calls through call files".
Cheers!

Thanks marcelog


Invalid asset filename messsage

Information

Version 2.2.1
Mac
Build myself

Asset files in our app often contain locale specific characters. During development, we did not have any problem with that. But our ops team tried decoding apk to change version and version name and rebuilding again and they get error.
ApkTool obviously validates filenames in assets as well and should not do that.
Stacktrace/Logcat
W: /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/assets/pdf/education/directory/PdfFilenameéUnicodeChar.pdf: error: Invalid filename.  Unable to add.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [/var/folders/q_/t31gmn4j5g56jfqykyfhc0202sk4j9/T/brut_util_Jar_1904785156313027405.tmp, p, --forced-package-id, 127, --min-sdk-version, 14, --target-sdk-version, 22, --version-code, 10002013, --version-name, 1.0.2, -F, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/dist/App_1.0.2_13_10002013-prod-release.apk, -0, arsc, -0, arsc, -A, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/assets, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/build/apk]
	at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:439)
	at brut.androlib.Androlib.buildApk(Androlib.java:675)
	at brut.androlib.Androlib.build(Androlib.java:315)
	at brut.androlib.Androlib.build(Androlib.java:264)
	at brut.apktool.Main.cmdBuild(Main.java:227)
	at brut.apktool.Main.main(Main.java:84)
Caused by: brut.common.BrutException: could not exec (exit code = 1): [/var/folders/q_/t31gmn4j5g56jfqykyfhc0202sk4j9/T/brut_util_Jar_1904785156313027405.tmp, p, --forced-package-id, 127, --min-sdk-version, 14, --target-sdk-version, 22, --version-code, 10002013, --version-name, 1.0.2, -F, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/dist/App_1.0.2_13_10002013-prod-release.apk, -0, arsc, -0, arsc, -A, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/assets, /Users/user/Temp/apktool/App_1.0.2_13_10002013-prod-release/build/apk]
	at brut.util.OS.exec(OS.java:95)
	at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:433)

Steps to Reproduce

Create app with asset files using unicode characters as filenames
Decode
Build again

Frameworks
If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)
APK
Apk cannot be shared
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything? Yes i have, that is part of  steps to reproduce
Didnt come this far
Yes

I can see in the sources, that this is more likely aapt issue. Will try updating to newer aapt from build tools 25

Not working even with aapt form build-tools v25

This is another problem with aapt. I started work a few days on some aapt patches. We have too many patches in aapt at this point to make sense of them all, so trying to do this correctly this time around.
Working on tons of internal documentation for building apktool flavored aapt binaries, so the turn around time for building multiple platform binaries is much quicker. I assume OEMs and more get around this by patching the apk with some build scripts after the fact or simply use old aapt versions.
Nothing to report yet, but tons of these bugs are aapt's fault.

PR is open. Only have my laptop on me for this little holiday break so can't build the unix/windows binaries until back home but the upstream patch to our frameworks/base project here - https://github.com/iBotPeaches/platform_frameworks_base/commit/7cc18d918edf45c681692ecea948a0253b73a8a0
Seems to have worked for my re-enabled unit test for unicode asset filenames.


Cannot redefine property: File (nodejs 20.6.0 issue)

Describe the bug
I have nodejs specific issue that only gives problems with the latest release, in older versions it does work. I Couldn't find any other tickets with the issue.
npm create vite@latest
✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

cd vite-project
npm run build

><EMAIL_ADDRESS>build
> tsc && vite build

failed to load config from ~/Desktop/vite-project/vite.config.ts
error during build:
TypeError: Cannot redefine property: File
    at Function.defineProperty (<anonymous>)
    at Object.<anonymous> (~/Desktop/vite-project/node_modules/@babel/core/lib/index.js:7:8)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Module.require (node:internal/modules/cjs/loader:1115:19)
    at require (node:internal/modules/helpers:130:18)
    at Object.<anonymous> (~/Desktop/vite-project/node_modules/@babel/core/lib/config/helpers/config-api.js:16:14)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)

It does not work with: node v20.6.0, but it does work with 20.5.1
So It could also be a nodejs / npm specific issue.
Reproduction
see-discription
Steps to reproduce
npm create vite@latest
✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

cd vite-project
npm run build

><EMAIL_ADDRESS>build
> tsc && vite build

failed to load config from~/Desktop/vite-project/vite.config.ts
error during build:
TypeError: Cannot redefine property: File
    at Function.defineProperty (<anonymous>)
    at Object.<anonymous> (~/Desktop/vite-project/node_modules/@babel/core/lib/index.js:7:8)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
    at Module.load (node:internal/modules/cjs/loader:1091:32)
    at Module._load (node:internal/modules/cjs/loader:938:12)
    at Module.require (node:internal/modules/cjs/loader:1115:19)
    at require (node:internal/modules/helpers:130:18)
    at Object.<anonymous> (~/Desktop/vite-project/node_modules/@babel/core/lib/config/helpers/config-api.js:16:14)
    at Module._compile (node:internal/modules/cjs/loader:1241:14)

System Info
It does work on:

  System:
    OS: macOS 13.5.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 56.91 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.5.1 - ~/.nvm/versions/node/v20.5.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.8.0 - ~/.nvm/versions/node/v20.5.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 116.0.5845.179
    Safari: 16.6
  npmPackages:
    @vitejs/plugin-react: ^4.0.3 => 4.0.4
    vite: ^4.4.5 => 4.4.9

And it fails on:
    Node: 20.6.0 - ~/.nvm/versions/node/v20.6.0/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v20.6.0/bin/npm

Used Package Manager
npm
Logs
npm run build -- --debug

<EMAIL_ADDRESS>build
tsc && vite build --debug

failed to load config from ~/Desktop/vite-project/vite.config.ts
error during build:
TypeError: Cannot redefine property: File
at Function.defineProperty ()
at Object. (~/Desktop/vite-project/node_modules/@babel/core/lib/index.js:7:8)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Module.require (node:internal/modules/cjs/loader:1115:19)
at require (node:internal/modules/helpers:130:18)
at Object. (~/Desktop/vite-project/node_modules/@babel/core/lib/config/helpers/config-api.js:16:14)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Duplicate of https://github.com/vitejs/vite/issues/14299


remove owner from input message and message predicate

closes #179

lgtm, although maybe bump fuel-asm to v0.9.0 in this PR as well?

Seems ok to me


feature: step extension for REST DSL. First iteration. Not yet nice.

Thanks for contributing!
Purpose
Describe the problem or feature in addition to a link to the issues.
Is this a new step extension or an improvement for an existing one?
What is the step(s) that this extension covers?
Open Questions and Pre-Merge TODOs
Please ensure your pull request adheres to the following guidelines:

[ ] There are tests that cover at least 75% of the step extension code
[ ] All tests pass with yarn test
[x] There commands yarn clean, yarn install, yarn test, and yarn build finish without errors
[x] Improvements of existing step extensions should be backwards compatible unless specified otherwise.
[ ] There is a corresponding view definition in the catalog https://github.com/KaotoIO/kaoto-viewdefinition-catalog

Fixes https://github.com/KaotoIO/kaoto-ui/issues/1720

I am going to start adding tests.
But we can parallelize that with @KaotoIO/frontend telling me all the things I have done wrong on the implementation :innocent:


Unpublished Web Pages are not removed from the search index

Describe the bug
When a Content Editor unpublishes a web page, that web page is not removed from the search index.
Currently:

The web page remains in the search index through cache clears.
Explicitly rebuilding the search index properly removes the web page form the index (Development -> Search -> Rebuild).

From my testing I think the cause stems from Kentico:

Not listening to the WebPageEvents.Unpublish event.
Not looking for the WebPageEvents.Unpublish.Name to produce a LuceneTaskType.DELETE task (in screenshots).

To Reproduce
Steps to reproduce the behavior:

Go to any publishable page
Confirm the page is published
Click on the dropdown next to "EDIT PAGE"
Click on "Unpublish options"
Click on "Unpublish now"
Perform a content search
See the unpublished web page in the search results

Expected behavior
The unpublished web page does not appear in the search results.
Screenshots

Library Version
Kentico.Xperience.Lucene 7.0.0
Lucene.Net 4.8.0-beta00016
Desktop (please complete the following information):

N/A

Smartphone (please complete the following information):

N/A

Additional context
Our workaround was to listen to the WebPageEvents.Unpublish event and send the WebPageEvents.Delete.Name to DefaultLuceneTaskLogger.
Our project implements a custom indexing strategy, which inherits from DefaultLuceneIndexingStrategy, but the MapToLuceneDocumentOrNull is never called in the scenario above.
Our project only has a single index. I did not test for multiple indexes.

Hello, the issue has been fixed in the pull request #67


Minor change argument for ML similar search api

argument name changed yesterday

 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.

@bingjiez did you mean to close this??

Yes, the fix was merged with bingjiez commit here: https://github.com/iTwin/viewer-components-react/commit/a60dd40745db768a3f150bbff0c8da82e98d0888


How can I detect anomaly at pixel-level?

The paper describes using pixel-wise residuals between the input/ground truth and the reconstruction.

Do you mean the same as the image-level residual MSE(fake_img, real_img) because the function not cleat at the paper?

Yes, I think so. See item (4) in section 3.1 of the f-AnoGAN paper, as well as equation (5).

Thank you for your help.

@nickk124 I think the equation of,pixel_level anomaly detection is the loss L1 NOT MSE,  l1(fake_imgs, real_imgs) because in the paper A(x) =|x- G(E(x))|.
What do you think please, Thank you.


use minimum capabilities for collector container

Signed-off-by: Daxin Wang<EMAIL_ADDRESS>

Related to issue #54


[ENH] Improve responsive design

improve responsive design of a election banner
improve responsive design of converter tables (closes #211)

LGTM, thanks!


Filepath not allowing path to subdirectory

not specifying a filepath starts with the root directory, as expected.
specifying a full path to a notebook behaves as expected.

However, we cannot specify a path to a subdirectory (where the notebooks would typically be).

Hmmm - I just tried this URL:
https://mybinder.org/v2/gh/binder-examples/zero-to-binder/master?filepath=binder
and it did put me in the binder/ folder.
@SylvainCorlay can you share the link you're using that isn't working?

I think the problem is
https://mybinder.org/v2/gh/binder-examples/zero-to-binder/master?filepath=binder

vs
https://mybinder.org/v2/gh/binder-examples/zero-to-binder/master?filepath=binder/

(trailing slash). Should we sanitise that or just declare it illegal?

IMO we should sanitize something like that as it seems like a pretty reasonable assumption that users will make

@SylvainCorlay can you confirm that it works w/o the trailing slash?

I think this has now been fixed, #495 is closed as well. Please re-open if there is more to be done!


Selfie Flash UI test #79 #82

A UI test is added to Selfie Flash feature.

The Espresso Recorder had trouble generating code for shutter-involved actions. Your manual code provides the missing shutter functionality. Good job !

I actually learned it from your previous tests. Thanks !


create camera preview sample

@bbilodeau @hak @qchong @yinchiayeh PTAL

Hello, @ggfan thank you very much, the "read-image" sample, It's perfect to me. I use it and run perfect. Can you helpme with show the preview in the surface? Why I need it? I have this app run perfect in 4.4, 5.1 and 5.0 level api, With java and "Camera" Camera.PreviewCallback and sent the buffer to ndk. but in camera2 with onImageAvailable is not fast like Camera.PreviewCallback or Fail to Open camera2, For that, I want make everything in ndk (surfaceview and camera) to 6.0 and 7.0. Please helpme

Thanks for the comment: probably we could keep this conversation into issue: https://github.com/googlesamples/android-ndk/issues/349 for future reference.  First of all, personally I am a student for camera thing overall :-).  I like to show 3 supported ways to "see" the image from camera -- directly goes to NativeActivity's ANativeWindow, via ImageReader ( which I could see my pixel by adding my app between camera and display ), and via GLTexture ( which sends to GL engine as a texture, and render it to the render target ... ). GL engine will use hardware to stretch (or shrink ), and also does the color conversion ( I think ), which might give great performance boost.  With image-reader sample, I could not make the capture resolution too big -- CPU color conversion of a big resolution is just too slow, that is reason the resolution is "to pick the smallest supported resolution with the same aspect ratio as display device on THE camera mode list" and use it. You could change it to a big resolution in that function and see how slow it is.
with what you are saying, it might be a regression for camera2 API, might worth to file a bug for it so camera team could have a look?
Again, let's keep the conversation in issue: https://github.com/googlesamples/android-ndk/issues/349? thanks  :-)

My english it bad. Yes Keep the conversation in issue #349. Well I know I don't good developer and I thing the camera2 API it's good to use the camare directly in java doen't need more. But I need use the camera low level in android 7.0, I will need NDK. I have time in NDK I build my self lib to render img according the yuv work in all divices. You example It's perfect but I don't have any resouces from java (Layaout, text, views ...) only I need something like view. I read GLTexture in GL engine but I newcomer in C++ it so hard for me.

Are you going to help me? xD

the read-image sample does not have any Java UI: the only java code is to get camera run-time permission .( that you will need it for your apps too ). If you only have a view on java side,  that means you want your java side to create a surface and give to native to capture or view?  if that is the case, the cts code in android code might match your situation ( you need to look at the code, I do not have much experience in that directory):  https://android.googlesource.com/platform/cts/+/master/tests/camera/src/android/hardware/camera2/cts?autodive=0%2F%2F%2F%2F%2F%2F%2F%2F%2F
the matching jni code is:
https://android.googlesource.com/platform/cts/+/master/tests/camera/libctscamera2jni?autodive=0/
search for testCameraDeviceSimplePreviewNative or testJpegNative, to see how that test handles java side. Hope that could help some.

Hello I saw the example you sent me but it takes me to a box without a way out. I have never had the need to ask directly in a git forum or group and I did it because I did not get another way to achieve my development. I'm really thinking about leaving the project there are a lot of documentation problems and example. I have a lot of time in this (7 months), learning JNI, NDK and many other things, make my own library of render yuv for raw android and add the project to camera and c ++ and add camera2 of java to expand my users also agregge The latest transformations of yuv for android 7.0, but I really think it is very difficult to go deep into it, I always come to nothing or half make it work and at the end android hits me with some error in some device and I am wrong in my app thing that stops me Unfair and to make things according to what should be done but something is always missing, it will not always work. I'm sad that's why I think it would be better to walk the way of IOS since I know that it always works at the maximum expression of the device and there is no war between java and JNI c ++ Libs and also the errors for devices. Sorry if I refer badly on the subject with you, but there is no one with whom I can complain, I am a little disappointed with android I really believe in the project but its vertiginous changes that the promoters can never reach because they always change something. :(

personally I saw similar comments on stack overflow. When coming to application programming, as long as app need UI, it has to use Java side framework; I think that makes people in certain areas ( audio, video, graphics ) to be burdensome.  feel free to shoot questions to this forum or to any android-ndk public forums, normally they will get answered. I will come to this: just got dragged to another project.  The third way of retrieving images from camera is via: https://developer.android.com/reference/android/graphics/SurfaceTexture.html
from java side, create an object of it, get its ndk ANativeWindow, give it to camera2 ( so camera could push images into it: it is a queue ); then on GL side, every rendering cycle, get the latest image from this same surfaceTexture, use sampler to sample it and color could be automatically converted from YUV->RGB by sampler ( if not, use a matrix in fragment shader to map YUV to RGB ). that way your app does not have to CPU cycles to do it. Suppose to be very fast that way.  Number wise: camera output ~30 fps; display rendering side pull texture at 60fps. so you know display is camera is the slow producer and it will not starve.
On the size of the texture, make sure to create the size that is same aspect ration of your final display device resolution, this avoid image distortion.  The size as big as possible: as long as you could still do one GL frame within 16 ms (camera device might also having trouble to output huge frames at that rate ), you could increase captured frame size.  The downside ( I think ) is the memory movement ( the image goes from Camera -->CPU memory --> GPU memory ), you will hit memory bandwidth issue as you increase the texture size. But a balance spot will be found between picture quality and system throughput.
I need to look at the openGL couple of extensions and read through SurfaceTexture concept; then I could add code for it ( I was told I have to use java to set up SurfaceTexture, which makes me feel sad :-() will see.

Oh, for preview purpose ONLY, you do not have to do YUV to RGB conversion: directly let Camera talk to display (you might look at the "preview" sample in this Pull Request,  I hard coded the size to  640x480 for camera, which is not right, need to use the code to find the smallest + same aspect ration, and set to camera. The drawback is that application do NOT have chance to touch the pixels ( app is not in the loop )

I saw the "read-image" sample, It's perfect to me. But I need pass to preview to java Like surfaceview. Just that. If exist it any example to surfaceview to static image from bitmap I can make it.

is the read-image is enough for you? or you need more functionality as to connect to java side?

Only I need this example (read-image sample) with TextureView, ration camera does not matter.

yeah, tried with textureView, and Camera team told me how to use TextureView. what I tried at the moment is:

Create TextureView, set it  ContentView for the Activity
when SurfaceTexture of this TextureView is available, create a Surface from SurfaceTexture
(this is because there is no API to get ANativeWindow from SurfaceTexture )
sending down this SurfaceTexture to Native side via JNI, and get its nativeWindow, create camera.
Start preview, looks fine for preview: the preview is smooth.

what need to bring in:

create the camera with the right ratio and smaller size
manually get texture pixels from onSurfaceTextureUpdated(), add color conversion, and give to default Activity's view for display
The frame available function onSurfaceTextureUpdated() is on java side, so if want to do manual processing, I think I have to start there, pass to JNI to do real YUV --> RGB conversion

does this help your project?  I like avoid to add more things into ReadImage sample to keep it as read-image only

Men It's perfect this sample. Thank you very much

add the textureView code, not able to add the YUV to RGB conversion yet: display directly taking YUV and preview, no need to do YUV to RGB conversion, I think

I am having trouble to get the right rotation and aspect ratio for textureView preview: direct way seems to be difficult to get correct image.  will hack on it more

Nice demo. It would be nice to see how one can adjust the fetching frame rate - I think now it is capped at 30 FPS, correct?

yeah, that takes whatever the default from camera.  their standard would be 29.xxx ( sth like that ), you could see I am trying to be a video related person  :-) . will look into that frame rate thing.  thanks

I can not find the "read-image" sample，can you upload again?

it is inside this pull, the branch is
https://github.com/googlesamples/android-ndk/tree/camera-sample
No development yet

Oops, please let me know for any concerns: it is a typo fix this time.  thx

Hi @ggfan, great work. I am trying this on my Nexus 5X. The preview-read-image seems to work OK. However, if I try to run preview-native-activity -- the system is throwing the following exception. Looks like it couldn't find ANativeActivity_onCreate. Have you seen this before ?
I just imported the project on my Android Studio -- so not sure if this is an artifact of the build process.
06-18 09:05:22.215 19002-19002/com.sample.camera.readimage E/AndroidRuntime: FATAL EXCEPTION: main                                                                              Process: com.sample.camera.readimage, PID: 19002                                                                              java.lang.UnsatisfiedLinkError: Unable to load native library "/data/app/com.sample.camera.readimage-2/lib/arm64/libcamera_view.so": undefined symbol: ANativeActivity_onCreate                                                                                at android.app.NativeActivity.onCreate(NativeActivity.java:182)                                                                                at com.sample.camera.readimage.ReadImageActivity.onCreate(ReadImageActivity.java:38)                                                                                at android.app.Activity.performCreate(Activity.java:6679)                                                                                at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118)                                                                                at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2618)                                                                                at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)

you probably using NDK-r15?  try to attach the following to your own CMakeLists.txt for NativeActivity related sample
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -u ANativeActivity_onCreate")

closing this one down as it is merged into master


override websocket events on the client

is there a way to handle error/close ? i tried to use
myCableConsumer.connection.webSocket.onclose = function(){..}
and webSocket.onclose will always be null;

I don't recommend reaching into connection's webSocket like that. It gets reassigned when the connection is reopened so your onclose handler will be lost. Instead, add a disconnected callback to your subscriptions, which will be called when the connection is closed and on error:
cable = Cable.createConsumer "ws://cable.example.com"

cable.subscriptions.create "ExampleChannel",
  disconnected: ->
    ...


Add schema support to apache pulsar

Closes https://github.com/dapr/components-contrib/issues/2450.

Linter: Error: shadow: declaration of "schemaMetadata" shadows declaration at line 34 (govet)


Add user menu as a dropdown

Fixes #3888
Login button

on hover:

Staff logged in:

on hover:

On clicking on Staff button:

On hovering any item of these like 'Activity Feed' in this case:

Applicant or any other user logged in:

Test Steps

[ ] …

Worked well in testing! I think just a few stylistic changes and it should be ready to go. Nice addition!


[C-Api/Util] Add ML_NNFW_HW_NPU_SLSI case to converting function @open sesame 06/30 08:42

To support VD product, this patch adds the ML_NNFW_HW_NPU_SLSI case
to ml_nnfw_to_accl_hw() function.
Signed-off-by: Sangjung Woo<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #73. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @again4you, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/73-202106291806520.64839196205139-89cdabe43d3eec10f1b9622d675add2301429382/.

:octocat: cibot: @again4you, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nnstreamer-api/ci/repo-workers/pr-checker/73-202106300844320.14873099327087-89cdabe43d3eec10f1b9622d675add2301429382/.


Add cache management

Add a cache management to speed up github action

Found this documentation.
https://docs.github.com/en/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows

https://github.com/Xabibax/my-blog/commit/d76a8568e3652b53251a8cdd9415f7a7bcf1c2cf


How to do a hot reload?

I looked at the readme but its not immediately obvious how to do hot reloading?

https://github.com/humhei/FCSWatch#from-cli

dotnet tool install --global fcswatch-cli
fcswatch --project-file yourProjectFile
FcsWatch will load your project in autoReload mode by defalut

Does fcswatch --project-file yourProjectFile worked for you?

I mean how to get interpreted code to be reloaded?

Maybe you want
https://www.nuget.org/packages/fslive-cli-test/
It have not been documented....
Actually, When @dsyme think we should merge FcsWatch and FSharp.Compiler.PortaCode together
I abstract all the common codes to FcsWatch.Core
This means FSharp.Compiler.PortaCode can get benifit from cross-projects compiling and multiple target framework project(Though i doesn't test it, it may not get worked, As FcsWatch.Binary is all ok for me)

Thanks @humhei What I really wanted whether binary or interpreted was to keep the model between reloads, so the binary would be swapped but the model would remain the same.

IMHO.
Maybe implement akka.Persistance in your program side should be a good way?

@humhei So is there a webhook listener defined in this repo that I missed or is that only in fabulous?

For  interpreted code
It has the same effect when comparing to FSharp.Compiler.PortaCode
The watcher host will try to send serialized code check results AST to the program side
For  binary mode
The watcher host will only send a webhook (only contains dll file which was swapped #21 ) when we rerun program
It is only a notification but doesn't make more sense,
As rerun means taht it will try to stop program first,And then run it

Yeah I know this, the point I was trying to make is there is no example of client socket code to demonstrate the interpreted mode, you have to look in fabulous to find an example of that.

Examples of both parts you described above would be good especially the persistence of the model you described.
So on a binary web hook notification you get a notification when a dll is about to be swapped so you can persist the model?
On a rerun is there also a notification so you can load a model on startup?

In binary reload mode.
If you use the way i described above to persistent model to database,
You don't need to catch the webhook,
As akka.persistence will load (whether from snapshot or journal) your model from database after reload automatically
The only thing you should do is that after everytime model is changed
You should persistent them to database..
Also, I am worried about that if your model can be serializable or not

Sorry I didn't test it,
It's only just an idea

Theres also the issue of if you change the models shape in-between restarts.


Permissions required: only contributor

It states "1. As a user with the role Security admin or Subscription Contributor, from the toolbar on the alerts page, select Create sample alerts."
But in our tenant having the role Security Administrator is neither sufficient nor necessary. One must have the contributor role to the subscription for which sample alerts should be created.

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

ID: 5d9f5c7e-0c34-9b6d-53da-7353525aef8b
Version Independent ID: 223a6f7e-bb24-a09e-2a8a-7188d7710ab7
Content: Alert validation in Azure Security Center
Content Source: articles/security-center/security-center-alert-validation.md
Service: security-center
GitHub Login: @memildin
Microsoft Alias: memildin

Hello @andrePKI , thanks for taking time to share your valuable feedback! We are taking a look into this and will get back to you soon.

I was able to reproduce this, let me get back to you with an update.

I have made changes to the doc, please expect it to be live soon.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


REX lands not parsed

REX lands fall into the Verhey parser, but don't have a keywords object on their face[0].
Secondarily, this failure isn't bubbling up into the logs 🤔

Ah, it's because the REX lands don't even exist in the card dump we download.

The fix for j21 missing cards sort of opened the door to some glorious hackery. Let's lean in on that for the rex lands.


[Dashboard] List NFT to marketplace directly from token-page

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on enhancing the functionality of the marketplace by adding a ListMarketplaceButton, improving the listing creation process, and refining the NFT selection and contract handling.
Detailed summary

Updated type in CreateListingButtonProps to be required.
Added ListMarketplaceButton component with form and state management.
Integrated NFT selection and listing creation logic in CreateListingsForm.
Enhanced form validation and error handling for marketplace actions.
Implemented prefilled NFT info display in the listing form.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5442  👈 (View in Graphite)
main

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


No license file

Hi,
I really like your date picker and would like to use it - can you please add a license file?
https://help.github.com/articles/open-source-licensing/#what-happens-if-i-dont-choose-a-license
Thanks & best regards,
Compu

+1

Added MIT license. Thanks!


libguestfs: 1.38.4 -> 1.38.6

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libguestfs/versions.
meta.description for libguestfs is: '"Tools for accessing and modifying virtual machine disk images"'.

Checks done (click to expand)

built on NixOS
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/guestfish passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/guestmount passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/guestunmount passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/libguestfs-test-tool passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-alignment-scan passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-builder passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-builder-repository passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-cat passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-copy-in-wrapped had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-copy-in passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-copy-out-wrapped had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-copy-out passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-customize passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-df passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-dib passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-diff passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-edit passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-filesystems passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-format passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-get-kernel passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-index-validate passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-inspector passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-list-filesystems-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-list-filesystems had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-list-partitions-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-list-partitions had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-log passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-ls passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-make-fs passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-rescue passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-resize passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-sparsify passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-sysprep passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-tail passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-tar-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-tar had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-tar-in-wrapped had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-tar-in passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-tar-out-wrapped had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-tar-out passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-v2v passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-v2v-copy-to-local passed the binary check.
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-win-reg-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/virt-win-reg had a zero exit code or showed the expected version
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.guestfish-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.guestmount-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.guestunmount-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.libguestfs-test-tool-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-alignment-scan-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-builder-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-builder-repository-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-cat-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-customize-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-df-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-dib-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-diff-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-edit-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-filesystems-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-format-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-get-kernel-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-index-validate-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-inspector-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-log-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-ls-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-make-fs-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-rescue-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-resize-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-sparsify-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-sysprep-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-tail-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-v2v-wrapped passed the binary check.
/nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6/bin/.virt-v2v-copy-to-local-wrapped passed the binary check.
60 of 72 passed binary check by having a zero exit code.
24 of 72 passed binary check by having the new version present in output.
found 1.38.6 with grep in /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6
directory tree listing: https://gist.github.com/92b4bb76a646f1bf7e912dea7b4291db
du listing: https://gist.github.com/aa5a161a7a6350e9b705c8f2e3361f0a

Instructions to test this update (click to expand)

One-time optional setup to skip building using Cachix:

Install cachix from https://cachix.org/
Use r-ryantm's cache:cachix use r-ryantm

Test this update by entering a nix shell, seeing what is inside the
result, and if applicable, running some binaries:
nix-shell --pure -I nixpkgs=https://github.com/r-ryantm/nixpkgs/archive/6e58fb8309ed76ed7bc494400e4032a58e9b0f9a.tar.gz -p libguestfs
ls -la /nix/store/laayqaqqscg7wsx2ywra4by3bn5f2pzw-libguestfs-1.38.6

cc @offlinehacker for testing.

@GrahamcOfBorg build libguestfs

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: libguestfs
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: libguestfs
Partial log (click to expand)
shrinking /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6/lib/perl5/site_perl/5.28.0/x86_64-linux-thread-multi/auto/Sys/Guestfs/Guestfs.so
gzipping man pages under /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6/share/man/
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6/lib  /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6/bin
patching script interpreter paths in /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6
checking for references to /build in /nix/store/si5fsg9ix2g9912yx36ag7v3jvda5xmg-libguestfs-1.38.6...
running install tests
Formatting 'disk1.img', fmt=qcow2 size=10737418240 cluster_size=65536 lazy_refcounts=off refcount_bits=16
/dev/sda: unknown
/dev/sda1: ext2

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libguestfs
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


typescript: index through "export" statements [phab:D1673]

Created by evmar at 2017-05-25 18:22:40:
Fixes more TODOs.  It turns out we just needed to hand the statement
to the existing machinery.

fromberger accepted this revision at 2017-05-25 21:28:00

fromberger closed via commit 13d742be5e949eebc067028d1c29a7ee4690f8da at 2017-05-25 21:28:23


Manage google analytics UA ID in BgeeProperties

In GitLab by @fbastian on Sep 13, 2015, 03:53

Add the UA ID to the Bgeeproperties.

Modify org.bgee.view.html.HtmlParentDisplay#startDisplay(String) to not display the GA code if no UA ID defined.

This will notably allow to stop messing up the google analytics results with our development tests (there would be no UA ID defined in test resource properties).
Related to issue#39

In GitLab by @fbastian on Oct 14, 2015, 22:25
Assignee removed


performance improvement by about 30%

re-implement Utilities::parseNumber method to deprecate stringstreem operator>>
re-implement Utilities::split method to deprecate istrimgstream class
re-implement ObjectParser::parseLine method
use std::unordered_map instead of std::map for beter performance

Test inp file with about 50000+ nodes

@WaterDesk while I am OK with your changes 2 - 4, I am concerned with change 1. It seems to only work for floating point numbers and not integers plus I question if it is any faster than using the stringstream approach. Could you run your benchmark again with the original parseNumber code restored and compare run times. Another approach that is used in EPANET 2 is the following code which also seems to be very fast:
int getfloat(char *s, double *y)
/*
**-----------------------------------------------------------
**  Input:   *s = character string
**  Output:  *y = floating point number
**           returns 1 if conversion successful, 0 if not
**  Purpose: converts string to floating point number
**-----------------------------------------------------------
*/
{
  char *endptr;
  *y = (double)strtod(s, &endptr);
  if (*endptr > 0) return (0);
  return (1);
}

@LRossman There is a page which show the comparison between different methods to convert string to double. This native method is the fastest one. https://tinodidriksen.com/2011/05/cpp-convert-string-to-double-speed/
It is about 19 times faster than strtod in msvc, about 4-6 times faster than strtod in gcc and clang.
The template method parseNumber only supports double and float data now, not integers. In the project, all usage of parseNumber's parameter is double. So, not supporting integer is not a problem.

@WaterDesk thanks for the reference. Can you revise the new parseNumber method to accept numbers in scientific notation (e.g., 1.23e4) which the current method can do?

@WaterDesk thanks for the reference. Can you revise the new parseNumber method to accept numbers in scientific notation (e.g., 1.23e4) which the current method can do?

@LRossman You are right. The new parseNumber method doesn't accept numbers in scientific notation. I made the regression and create a new PR to fix it #47


Upgrade to Scalameta v3.7

Supersedes #84. I was struggling to debug why #84 was failing in manual tests, goto definition, find references didn't work. I went ahead and migrated from scratch and everything works now. I encountered an off-by-one bug in positions when manually testing the site, but otherwise everything worked out nicely.
One regression that I leave for a future PR is that signatures ("containerName") for "document symbol" no longer show result types

Metap does not expose an API to pretty print a single SymbolInformation.tpe.

Hmm 🤔
7.78s$ git submodule update --init --recursive
Submodule 'paiges' (https://github.com/typelevel/paiges.git) registered for path 'paiges'
Cloning into '/home/travis/build/scalameta/metadoc/paiges'...
error: Server does not allow request for unadvertised object 265d5186aca6d8584f7a859417f72b47dbeb12f0
Fetched in submodule path 'paiges', but it did not contain 265d5186aca6d8584f7a859417f72b47dbeb12f0. Direct fetching of that commit failed.

Any idea what caused this regression @jonas ?

It looks like someone force pushed into the repo.
I get a 404 when accessing https://github.com/typelevel/paiges/commit/265d5186aca6d8584f7a859417f72b47dbeb12f0

Whoop, CI is green! Forcing the submodule to a particular commit fixed the problem.

Hmmm
dpl.3
Deploying application
Publishing...
commit e294162f0504cfc30201286e217fa2e7a8884683
Merge: fdea3ce 69541fe
Author: Ólafur Páll Geirsson <[secure]>
Date:   Sun Apr 8 23:00:40 2018 +0200
    Merge pull request #90 from olafurpg/semanticdb3

    Upgrade to Scalameta v3.7
commit 69541fe4463e93c69661073242a0888f1593d111
Author: Ólafur Páll Geirsson <[secure]>
Date:   Sun Apr 8 22:49:04 2018 +0200
    Link to relevant ticket for Type pretty printing
commit 627f0a27ebec62398ce5f3e1a0fd77405f2e154d
Author: Ólafur Páll Geirsson <[secure]>
Date:   Sun Apr 8 22:42:08 2018 +0200
    Revert sloppy sed rename.
Already up to date!
HEAD detached at e294162
nothing to commit, working tree clean
Dropped refs/stash@{0} (a428b5697528ea83b4e343ae2b3a0aba9b667bac)
Script failed with status 141
failed to deploy

(wasn't meant to post that comment right away)
Deploy seemed to fail https://travis-ci.org/scalameta/metadoc/jobs/363871672#L4123
Any idea what went wrong @jonas ? Logs are quite cryptic

I will take a look.

The problem was the pipefail flag. Not sure why the gpg key import commands fail.


Unit | Component | sl date time: "title" property is an alias to "datetime" value

not ok 424 PhantomJS 1.9 - Unit | Component | sl date time: "title" property is an alias to "datetime" value
    ---
        actual: >
            null
        message: >
            Died on test #1     at test (http://localhost:7357/assets/test-support.js:3025)
                at testWrapper (http://localhost:7357/assets/test-support.js:6192)
                at test (http://localhost:7357/assets/test-support.js:6205)
                at http://localhost:7357/assets/tests.js:23236
                at http://localhost:7357/assets/vendor.js:152
                at tryFinally (http://localhost:7357/assets/vendor.js:33)
                at http://localhost:7357/assets/vendor.js:158
                at http://localhost:7357/assets/test-loader.js:60
                at http://localhost:7357/assets/test-loader.js:51
                at http://localhost:7357/assets/test-loader.js:82
                at http://localhost:7357/assets/test-support.js:6024: 'undefined' is not a function (evaluating 'validTimeZonesArray.includes(this.get('timezone'))')
        Log: |
    ...

Will likely be resolved by https://github.com/softlayer/sl-ember-components/issues/1503

Resolved by https://github.com/softlayer/sl-ember-components/issues/1503


WIP Adds v1beta1 EdgeConnect CRD

K8S-10077
Description
Adds v1beta1 EdgeConnect CRD.
How can this be tested?

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 25.39683% with 423 lines in your changes missing coverage. Please review.

Project coverage is 56.78%. Comparing base (c1e08d6) to head (72b6d52).

Files
Patch %
Lines

...g/api/v1beta1/edgeconnect/zz_generated.deepcopy.go
0.00%
155 Missing :warning:

pkg/api/v1beta3/dynakube/zz_generated.deepcopy.go
0.00%
127 Missing :warning:

pkg/api/v1beta1/edgeconnect/secret.go
0.00%
24 Missing :warning:

pkg/api/v1beta1/edgeconnect/proxy.go
0.00%
21 Missing :warning:

pkg/api/v1beta2/dynakube/zz_generated.deepcopy.go
0.00%
21 Missing :warning:

pkg/api/v1beta1/edgeconnect/properties.go
0.00%
20 Missing :warning:

pkg/api/v1beta1/edgeconnect/edgeconnect_types.go
38.09%
13 Missing :warning:

...g/api/v1beta1/edgeconnect/validation/validation.go
50.00%
12 Missing :warning:

pkg/api/v1beta1/edgeconnect/certs.go
0.00%
9 Missing :warning:

.../api/v1alpha1/edgeconnect/zz_generated.deepcopy.go
0.00%
8 Missing :warning:

... and 4 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3543      +/-   ##
==========================================
- Coverage   57.66%   56.78%   -0.88%
==========================================
  Files         379      395      +16
  Lines       20383    20948     +565
==========================================
+ Hits        11753    11896     +143
- Misses       7379     7799     +420
- Partials     1251     1253       +2

Flag
Coverage Δ

unittests
56.78% <25.39%> (-0.88%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Please put merging this PR on-hold until further notice.


Add tooltip component

Feature Request
Description

A tooltip that appears on hover. Disappears when hovering away. The tooltip should stay visible while over the popup area. Example of behavior I would expect - https://ant.design/components/tooltip/
Additional Context / Screenshots

We tried implementing this with popup - we were getting a lot of unexpected behavior.

Thank you @RusseII for your new component request and we welcome your input on suggestions.
Background:
Tooltips are a common request from Terra consumers, but is a challenging component for Terra to create, for a few reasons. You've heard the theme "mobile first design", in a similar way, Terra has been moving toward focusing on building web ui that is an "accessible first" design approach.
Traditionally, tooltips have been a common method for showing additional content like revealing truncated text, displaying the alternative text or caption for an image, clarifying the meaning of an icon/button/label/etc., showing full value of something shorthanded like a date/time or the url of a hyperlink, or providing additional details like helpful instructions.

What is needed:
Keeping a focus on accessibility and being device (and input method) agnostic, tooltips in their traditional fashion create a few problems in Terra:

they are primarily a desktop (mouse/pointer input) technique, and have no direct access for touch input users or non-pointer inputs, including keyboard-only users.
because of the limitations of input support, our UX requires that any content that is provide via a tooltip needs to also be available directly as faceup content. For example, if long text is truncated, a tooltip cannot be the only way the full contents are disclosed. Tooltips should be used a secondary and supplemental, only in addition after a primary disclosure flow exists to reveal the full content presented in the tooltip.
it is difficult, if not impossible, to make them WCAG2.1 accessible using the traditional hover interaction rules that users expect for a tooltip. Changing the behavior to make them accessible moves them closer into the realm of a popup, and questions the very intent or value of a tooltip with odd new behavior patterns.

What you can do:
However, given those constraints, Terra would love to keep investigating the creative opportunities that might exist to make a component that has features included to solve for the problems I have mentioned above. We would love to see someone take some time and see if there are some new ways with the React ecosystem to provide for an accessible-first tooltip that still matches a user's mental model of the behavior pattern.
This issue can serve as a tech design proposal for a new component and we can have the discussion below and experiment with drafting the best options for what a terra-tooltip component could be.

And you are correct, implementing a tooltip with the terra-popup may get you in the visual ballpark of a tooltip, but it's behavior patterns are unique for popups (click to open, not hover. focus trapping once it is open, no proper way to dismiss on hover out) and would not translate to adapting it directly as a tooltip.


FIX: show missing value columns

julia> georef((; x=[missing]), [(0, 0)])
1×2 GeoTable over 1 PointSet{2,Float64}
┌───────────┬────────────┐
│     x     │  geometry  │
│  Missing  │   Point2   │
│ [NoUnits] │            │
├───────────┼────────────┤
│  missing  │ (0.0, 0.0) │
└───────────┴────────────┘

closes #58

Codecov Report

Merging #59 (9e54e65) into master (3129671) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
+ Coverage   94.02%   94.09%   +0.06%
==========================================
  Files           6        6
  Lines         268      271       +3
==========================================
+ Hits          252      255       +3
  Misses         16       16

Files Changed
Coverage Δ

src/abstractgeotable.jl
99.01% <100.00%> (+0.01%)
:arrow_up:


Pluggable Components' "Define the component" has wrong information

Describe the issue
It reads:

Define your component using a component spec. Your component’s type is derived from the socket name, without the file extension.

But that is not really the case. Filename has a impact on the component name, not on its type.
URL of the docs
https://docs.dapr.io/operations/components/pluggable-components/pluggable-components-registration/#define-a-component
Expected content
TBD
Screenshots

Additional context

/assign

@tmacam let me know if you'd like me to help out with updating this doc

Hey @hhunter-ms . If you have the docs ready and could update that I would appreciate. Otherwise I will tackle this later this week.

@tmacam ok! I don't have anything ready, just offering support!


top_p argument is used like 1-top_p

For example, top_p=0.999 gives you nearly deterministic sampling, not nearly on-distribution sampling.

I was confused why I was getting much less diverse samples with top_p=0.95 than I got with top_p turned off.
I found the cause in these lines:
https://github.com/Aleph-Alpha/magma/blob/bfd5c8def6a290f98b7eae34da120756f708cd38/magma/sampling.py#L11-L14
threshold is set to top_p here:
https://github.com/Aleph-Alpha/magma/blob/bfd5c8def6a290f98b7eae34da120756f708cd38/magma/sampling.py#L101-L102
Suppose eg threshold is 0.95.  Then 1-threshold is 0.05.
So we remove all tokens where the cumulative probs are > 0.05, which is most of the tokens -- we are really doing top-p sampling with top_p=0.05 (in the usual convention), not the intended top_p=0.95.

Thanks for catching that, it is fixed now.


Use line number if position is not known.

If the position in a diff isn't known (like in local diff parsing)
a comment's key should be based on the line number. Using position
causes incorrect comment collapsing.

Codecov Report

Merging #320 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #320   +/-   ##
=======================================
  Coverage   91.07%   91.07%
=======================================
  Files          48       48
  Lines        3047     3048    +1
=======================================
+ Hits         2775     2776    +1
  Misses        272      272

Impacted Files
Coverage Δ

lintreview/review.py
96.92% <100.00%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Add Survey Form web page

I will add a survey form web page for the other participants to add their thoughts and ideas for this website and make it responsive

i would like to add survey from in webpeg
@iamrahulmahato  plz assign me this task under hacktomberfest2024

@iamrahulmahato please assign this task to me I would like to work on it...

I would like to add survey form in webpage .
@iamrahulmahato ,please assign this tak to me.


compilation errors after eject

Hello.
I'm using create-react-app for quite sometime, and recently needed to use eject to take advantage of webpack's extended functionality. For some reason, after ejecting the app "npm start" or "npm run build" fail (Seems not to understand jsx at all).
The compilation error:
Failed to compile.

./src/index.js
Syntax error: <mypath>: Unexpected token (27:2)

  25 |
  26 | ReactDOM.render(
> 27 |   <Provider store={Store}>
     |   ^
  28 |   <ConnectedRouter history={history}>
  29 |     <App />
  30 |   </ConnectedRouter>

.babelrc file after ejecting:
{
  "presets": ["es2015", "es2016"]
}

Thanks for any further help,
Orel.

React syntax is not part of es2015 or es2016.
You need to correctly configure babel to handle React; FYI we already support es2015, es2016, AND es2017 (if we didn't make this clear, please let us know) -- so you should not of ejected to configure babel as such.
I suggest you remove your .babelrc all together and see the pre-configured one in your package.json which was populated after ejecting.

Ok thanks, I see my confusion. Deleted .babelrc but it still doesn't work tho.
my pre-configured babel is:
"babel": {
    "presets": [
      "react-app"
    ]
  },

Error:
Compiling...
Failed to compile.

./src/index.js
  Line 22:  Parsing error: Unexpected token )

If I might add I lack knowledge in webpack, babel, gulp and everything related to the compilation process (Not a web developer originally) and thus using create-react-app.

I'd need a project reproducing this to help, things should be working fine.
May I asked why you ejected? You should probably not if you're new. 😄

Hi, Coders
I was also facing same issue but then i tried Yarn Install and then yarn start , instead of npm install and npm start


Toolpad is UI is slow and freezes when trying to add a filePicker component

Steps to reproduce
Link to live example: (required)
Steps:
1.Run the editor
2.Add FilePicker
3.App will freeze
Current behavior
Freezes whole page
Expected behavior
FilePicker added
Context
Add FilePicker component
Your environment

npx @mui/envinfo
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Search keywords: slow toolpad ui freezing

@Zenith201 I can't reproduce this. would you mind running npx @mui/envinfo and paste the output here?


ModuleNotFoundError when importing from working directory

Importing a package from the working directory gives me a ModuleNotFoundError.
I have checked os.getcwd() and it is correct.
I have tried the most recent version of this extension, that is 2649928e013d4a6a80fbf66485860692ee2d3d5d.
I guess that the error is due to sys.path not containing the working directory:
[
  '/working-directory/.venv/lib/python3.11/site-packages/sphinx_autorun',
  '/opt/homebrew/Caskroom/miniforge/base/envs/my-conda-env/lib/python311.zip',
  '/opt/homebrew/Caskroom/miniforge/base/envs/my-conda-env/lib/python3.11',
  '/opt/homebrew/Caskroom/miniforge/base/envs/my-conda-env/lib/python3.11/lib-dynload',
  '/working-directory/.venv/lib/python3.11/site-packages'
]

Python won't import modules from the current working directory.

Thanks for the response!
I mean, if you run python from the command line, of course it will import modules from the working directory. But maybe I'm confusing apples and oranges here. However, when writing documentation for a module, let's say, mymod, how am I supposed to make this work then?
.. runblock:: pycon

    >>> import mymod

I found the following solution. Add the following code to conf.py:
import os
os.environ['PYTHONPATH'] = os.path.abspath('../..') + ':' + os.environ.get('PYTHONPATH', '')

You probably want sys.path.append: https://stackoverflow.com/a/3108301/107510

When docs are built, the current directory typically changes. At least it does with the default Sphinx Makefile.


JSON formatted logs with truncated body are not valid JSON anymore

Description

By default the body of a request that is not authenticated is replaced with <skipped>. This is currently formatted in the logs as {..., "headers":{...},"body":<skipped>} which is not valid JSON.
This is an issue when you attempt to parse the lines as JSON in order to get structured details about the content.
Expected Behavior

The line with a skipped body should be formatted as {...,"body":"<skipped>"}.
Actual Behavior

See above.
Possible Fix

I had a look at JsonHttpLogFormatter's tryParseBodyAsJson. The issue seems to be that the string should be considered invalid JSON and the method should simply return the string as is. However, the compactJson method terminates early because isAlreadyCompacted only looks for the existence of new lines but not whether it is valid JSON at all. The string is then simply returned and later serialized as a raw value via JsonBody which foregoes adding the quotes.
I guess a fix could be to also check for valid JSON syntax in tryParseBodyAsJson or similar but I'm not sure what the best approach would be. Maybe the isAlreadyCompacted check can be removed; I don't know how much performance it saves. Parsing the content beforehand for syntactical validity might lead to duplicate parsing. Not sure.
Steps to Reproduce

configure application to use JsonHttpLogFormatter
send unauthenticated request with payload

Context

Your Environment

Version used: 1.8.0
Link to your project:

You're absolutely correct. I identified this issue during #267, but I didn't fully understand the impact or scope.

I guess a fix could be to also check for valid JSON syntax in tryParseBodyAsJson or similar but I'm not sure what the best approach would be. Maybe the isAlreadyCompacted check can be removed

That would be a quick fix that would work.

I don't know how much performance it saves.

Me neither, but from gut feeling I'd expect a lot, since we never produce pretty-printed JSON.

Parsing the content beforehand for syntactical validity might lead to duplicate parsing. Not sure.

Even parsing it once, just to compact it already feels too much.
Long term I feel like the most robust solution would be to allow request and response filters to specify whether they are destructive or not, i.e. whether they modify the body in a way that it no longer conforms to the media type or not.

@musiKk Thanks for the thorough analysis! :tada:

One other very simple idea (not taking the possible fix into account): There would also be the possibility of simply checking whether the body equals "" and if yes, just returning it. This sounds like a hack at first but that could be alleviated bei either making that specific token part of the specification or make it configurable and use that configured value in the comparison. The latter sounds a bit like overkill to me though and would only be necessary if users create their own strategies.

The replacement string is pretty dynamic. We have a set of pre-defined one, but users are free to use their own: https://github.com/zalando/logbook/blob/master/logbook-core/src/main/java/org/zalando/logbook/BodyReplacers.java#L46

@musiKk I release the fix as 1.8.1 to central. Should be available soon. Thanks for raising the issue!


oss-directory transformation that changes all EOA addresses to any_evm

What is it?
There's no reason to only track EOA addresses on a single network, if the network is evm compatible, we mind as well try to find all contracts from that address

https://github.com/opensource-observer/oss-directory/pull/315


Tracking issue for dropping the local revert of https://github.com/llvm/llvm-project/pull/116470

The change to add 1:N matchAndRewrite method seems to have caused few failures in IREE. This is the tracking issue.
First issue is related to iree-stream-conversion pass.
Repro :
module attributes {stream.affinity.default = #hal.device.affinity<@__device_0>} {
  util.global private @__device_0 = #hal.device.target<"local", [#hal.executable.target<"llvm-cpu", "static", {cpu = "generic", cpu_features = "", data_layout = "e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-\i128:128-f80:128-n8:16:32:64-S128", link_embedded = false, link_static = true, native_vector_size = 16 : i64, static_library_output = "simple_mul_c_module.o", target_triple = "x86_64-unknown-linux-gnu"}>]> : \!hal.device
  flow.executable private @simple_mul_dispatch_0 {
    flow.executable.export public @simple_mul_dispatch_0_elementwise_4_f32 workgroups() -> (index, index, index) {
      %x, %y, %z = flow.dispatch.workgroup_count_from_slice
      flow.return %x, %y, %z : index, index, index
    }
    builtin.module {
      func.func @simple_mul_dispatch_0_elementwise_4_f32(%arg0: !flow.dispatch.tensor<readonly:tensor<4xf32>>, %arg1: !flow.dispatch.tensor<readonly:tensor<4xf32>>, %arg2: !flow.dispatch.tensor<writeonly:tens\or<4xf32>>) {
        %0 = flow.dispatch.tensor.load %arg0, offsets = [0], sizes = [4], strides = [1] : !flow.dispatch.tensor<readonly:tensor<4xf32>> -> tensor<4xf32>
        %1 = flow.dispatch.tensor.load %arg1, offsets = [0], sizes = [4], strides = [1] : !flow.dispatch.tensor<readonly:tensor<4xf32>> -> tensor<4xf32>
        %2 = tensor.empty() : tensor<4xf32>
        %3 = linalg.generic {indexing_maps = [affine_map<(d0) -> (d0)>, affine_map<(d0) -> (d0)>, affine_map<(d0) -> (d0)>], iterator_types = ["parallel"]} ins(%0, %1 : tensor<4xf32>, tensor<4xf32>) outs(%2 :\ tensor<4xf32>) {
        ^bb0(%in: f32, %in_0: f32, %out: f32):
          %4 = arith.mulf %in, %in_0 : f32
          linalg.yield %4 : f32
        } -> tensor<4xf32>
        flow.dispatch.tensor.store %3, %arg2, offsets = [0], sizes = [4], strides = [1] : tensor<4xf32> -> !flow.dispatch.tensor<writeonly:tensor<4xf32>>
        return
      }
    }
  }
  util.func public @simple_mul(%arg0: !hal.buffer_view, %arg1: !hal.buffer_view) -> !hal.buffer_view attributes {iree.abi.stub, iree.reflection = {iree.abi.declaration = "sync func @simple_mul(%input0: tensor\<4xf32>, %input1: tensor<4xf32>) -> (%output0: tensor<4xf32>)"}} {
    %0 = hal.tensor.import %arg0 "input0" : !hal.buffer_view -> tensor<4xf32>
    %1 = hal.tensor.import %arg1 "input1" : !hal.buffer_view -> tensor<4xf32>
    %2 = flow.dispatch @simple_mul_dispatch_0::@simple_mul_dispatch_0_elementwise_4_f32(%0, %1) : (tensor<4xf32>, tensor<4xf32>) -> tensor<4xf32>
    %3 = hal.tensor.export %2 "output0" : tensor<4xf32> -> !hal.buffer_view
    util.return %3 : !hal.buffer_view
  }
}

Repro command
iree-opt --iree-stream-conversion repro.mlir

It throws the following error
Trying to match "mlir::iree_compiler::(anonymous namespace)::ConvertDispatchOp"
LLVM ERROR: pattern 'mlir::iree_compiler::(anonymous namespace)::ConvertDispatchOp' does not support 1:N conversion

The pattern pointed to here https://github.com/iree-org/iree/blob/7177c29f9b2d9e255b63987f5dfff174ec2afc2f/compiler/src/iree/compiler/Dialect/Stream/Conversion/FlowToStream/Patterns.cpp#L715
That error is confusion since this is seems like a 1-1 replacement. One op (with N results) is replaced with another op (with N results).
Recording from Discord steps from @matthias-springer  to fix issues
[12:23 AM]Matthias Springer: I would approach it as follows:

Look for does not support 1:N conversion in the test failures.
For each pattern that does not support 1:N, replace the OpAdaptor of the matchAndRewrite with OneToNOpAdaptor. That's how you update 1:1 patterns to 1:N. When you call functions of the adaptor, you will now get ValueRange instead of Value. From there you have to continue on a case-by-case basis:
Check if the ValueRange always contains a single Value. In that case you can probably put an assert and take the single value.
If the ValueRange has more than one value, dump the all values and try to understand what the pattern is supposed to do with these values. (It's probably similar to what the addArgumentMaterialization callback was doing, followed by the pattern logic.) Update the patterns accordingly.
The tests should now be passing.
Cleanup: Delete all addArgumentMaterialization. Look for UnrealizedConversionCast in your code base. Ideally they should all be gone. (If not, you may be able to delete them. With 1:N conversion support in place, explicit usage of UnrealizedConversionCastOp should no longer be necessary in most cases.)

Going to start doing this now.

Took a bit of debugging, couple of things to note. The Stream conversion has a mismatch between the type converter and the operand converters. The operations convert tensor<...> to stream.resource<*> while the type converted seems to convert tensor<...> to stream.resource<*>, index.
For example
util.func public @simple_mul(%arg0: !hal.buffer_view, %arg1: !hal.buffer_view) -> !hal.buffer_view attributes {iree.abi.stub, iree.reflection = {iree.abi.declaration = "sync func @simple_mul(%input0: tensor\<4xf32>, %input1: tensor<4xf32>) -> (%output0: tensor<4xf32>)"}} {
    %0 = hal.tensor.import %arg0 "input0" : !hal.buffer_view -> tensor<4xf32>
    %1 = hal.tensor.import %arg1 "input1" : !hal.buffer_view -> tensor<4xf32>
    %2 = flow.dispatch @simple_mul_dispatch_0::@simple_mul_dispatch_0_elementwise_4_f32(%0, %1) : (tensor<4xf32>, tensor<4xf32>) -> tensor<4xf32>
    %3 = hal.tensor.export %2 "output0" : tensor<4xf32> -> !hal.buffer_view
    util.return %3 : !hal.buffer_view
  }

with the new change gets converted to
util.func public @simple_mul(%arg0: !hal.buffer_view, %arg1: !hal.buffer_view) -> !hal.buffer_view attributes {iree.abi.stub, iree.reflection = {iree.abi.declaration = "sync func @simple_mul(%input0: tensor<4\xf32>, %input1: tensor<4xf32>) -> (%output0: tensor<4xf32>)"}} {
  %element_type_f32 = hal.element_type<f32> : i32
  %dense_row_major = hal.encoding_type<dense_row_major> : i32
  %c4 = arith.constant 4 : index
  hal.buffer_view.assert<%arg0 : !hal.buffer_view> message("input0") shape([%c4]) type(%element_type_f32) encoding(%dense_row_major)
  %0 = stream.tensor.sizeof on(#hal.device.affinity<@__device_0>) tensor<4xf32> : index
  %1 = stream.tensor.import on(#hal.device.affinity<@__device_0>) %arg0 : !hal.buffer_view -> tensor<4xf32> in !stream.resource<external>{%0}
  %2 = stream.async.transfer %1 : !stream.resource<external>{%0} from(#hal.device.affinity<@__device_0>) -> to(#hal.device.affinity<@__device_0>) !stream.resource<*>{%0}
  %3:2 = builtin.unrealized_conversion_cast %2 : !stream.resource<*> to !stream.resource<*>, index
  %4 = hal.tensor.import %arg0 "input0" : !hal.buffer_view -> tensor<4xf32>
  %element_type_f32_0 = hal.element_type<f32> : i32
  %dense_row_major_1 = hal.encoding_type<dense_row_major> : i32
  %c4_2 = arith.constant 4 : index
  hal.buffer_view.assert<%arg1 : !hal.buffer_view> message("input1") shape([%c4_2]) type(%element_type_f32_0) encoding(%dense_row_major_1)
  %5 = stream.tensor.sizeof on(#hal.device.affinity<@__device_0>) tensor<4xf32> : index
  %6 = stream.tensor.import on(#hal.device.affinity<@__device_0>) %arg1 : !hal.buffer_view -> tensor<4xf32> in !stream.resource<external>{%5}
  %7 = stream.async.transfer %6 : !stream.resource<external>{%5} from(#hal.device.affinity<@__device_0>) -> to(#hal.device.affinity<@__device_0>) !stream.resource<*>{%5}
  %8:2 = builtin.unrealized_conversion_cast %7 : !stream.resource<*> to !stream.resource<*>, index
  %9 = hal.tensor.import %arg1 "input1" : !hal.buffer_view -> tensor<4xf32>
  %c0 = arith.constant 0 : index
  %10 = stream.tensor.sizeof on(#hal.device.affinity<@__device_0>) tensor<4xf32> : index
  %11 = stream.async.dispatch on(#hal.device.affinity<@__device_0>) @simple_mul_dispatch_0::@simple_mul_dispatch_0_elementwise_4_f32(%2[%c0 to %0 for %0], %7[%c0 to %5 for %5]) : (!stream.resource<*>{%0}, !st\ream.resource<*>{%5}) -> !stream.resource<*>{%10}
  %12:2 = builtin.unrealized_conversion_cast %11 : !stream.resource<*> to !stream.resource<*>, index
  %13 = flow.dispatch @simple_mul_dispatch_0::@simple_mul_dispatch_0_elementwise_4_f32(%4, %9) : (tensor<4xf32>, tensor<4xf32>) -> tensor<4xf32>
  %14 = stream.resource.size %12#0 : !stream.resource<*>
  %15 = stream.async.transfer %12#0 : !stream.resource<*>{%14} from(#hal.device.affinity<@__device_0>) -> to(#hal.device.affinity<@__device_0>) !stream.resource<external>{%14}
  %16 = stream.tensor.export on(#hal.device.affinity<@__device_0>) %15 : tensor<4xf32> in !stream.resource<external>{%14} -> !hal.buffer_view
  %17 = hal.tensor.export %13 "output0" : tensor<4xf32> -> !hal.buffer_view
  util.return %17 : !hal.buffer_view
}

Notice the builtin.conversion_cast are being inserted to do what the TypeConverter sees as a mismatch. But in reality all the uses of the builint.conversion_cast dont want to use the 0-th result of the operation. Instead they want to use the operand of the operation. If I just extract the operand in the conversion pattern the pass works as expected.
Couple of strange things

The Stream conversion pattern and type converters need to agree. This is the reason for the mismatch
It is strange to me that the OneToNOpAdaptor is returning the results of the builtin.unrealized_conversion_cast instead of the operand directly, but maybe that makes sense.

cc @nithinsubbiah  and @matthias-springer

The result IR is the final IR and not the output of -debug, right?

But in reality all the uses of the builint.conversion_cast dont want to use the 0-th result of the operation. Instead they want to use the operand of the operation.

This could be the result of folding two unrealized_conversion_cast ops.
Can run the dialect conversion with ConversionConfig::buildMaterializations = false and kDumpMaterializationKind = true? This will skip materializations and instead put unrealized_conversion_cast ops with an attribute that indicates the type of materialization. (I would expect no argument materializations. These should all be gone.)


Trio as an alternative to asyncio

Trio is a third party async library similar to asyncio. According to their documentation

Trio was built from the ground up to take advantage of the latest Python features, and draws
inspiration from many sources, in particular Dave Beazley’s Curio. The resulting design is
radically simpler than older competitors like asyncio and Twisted, yet just as capable. Trio is
the Python I/O library I always wanted; I find it makes building I/O-oriented programs easier,
less error-prone, and just plain more fun. Perhaps you’ll find the same.

The main reason why I prelimiarily prefer it over asyncio is that all concurrency is explicit: Parents can spawn child tasks, but only inside a "nursery" context manager.  In particular, one cannot spawn tasks that just run somewhere in the void like with asyncio.ensure_future (whose exceptions may just get ignored if not handled explicitly).
As a result all tasks form an easy to overlook tree, enabling a second neat feature: Cancel scopes. Tasks can have (potentially nested) cancel scopes created with a context manager or inherited from their parent. This seems to fulfill the same functionality as our cancel tokens, but one doesn't have to pass them around explicitly (less clutter, less errors, and due to the task tree structure probably more clear).
The obvious concern is ecosystem adoption: The project is still young. It seems to be actively developed since 1 1/4 years, but mainly by a single developer (although in the last month there have been commits by 8 contributors). It doesn't seem like there are major projects already using it (I don't know of a good way to find them though). Requests is apparently experimenting with Trio for their version 3.0. There is a pytest plugin. A couple of projects are being ported here, including click and PyMySQL. There's also trio-asyncio which apparently allows using libraries written with asyncio support from trio.
On that topic, a relevant quote by the author:

If you need to ship something to production next week, then you should use asyncio (or Twisted or Tornado or gevent, which are even more mature). They have large ecosystems, other people have used them in production before you, and they're not going anywhere.
[...]
If you want to ship something to production a year from now... then I'm not sure what to tell you. Python concurrency is in flux. Trio has many advantages at the design level, but is that enough to overcome asyncio's head start? Will asyncio being in the standard library be an advantage, or a disadvantage? (Notice how these days everyone uses requests, even though the standard library has urllib.) How many of the new ideas in trio can be added to asyncio? No-one knows. I expect that there will be a lot of interesting discussions about this at PyCon this year :-).

References:

https://github.com/python-trio/trio
https://trio.readthedocs.io/en/latest/index.html
https://stackoverflow.com/a/49485603

(Note: I'm not necessarily advocating to switch to Trio, I just want to make sure that an active and informed decision is made.)

@jannikluhn I think you guys should look into using this when you implement the beacon node syncing.

@cburgdorf @lithp would lahja support non-asyncio interface as well, so we can experiment with trio in an isolated process? I think that's one of the few things that would currently lock an isolated plugin into using asyncio (but just a guess).

A short term solution might involve creating something like a an adapter that wraps a lahja Endpoint and maybe throws together some of these helpers to expose trio compatible APIs.

Can this be closed?..


More erganomic AnimationPlayer API

What problem does this solve or what need does it fill?
Right now there are very few methods on AnimationPlayer which makes it more difficult to use than it needs to be.
I commonly need to be able to know:

the current animation
if it the current animation is finished
if there is no current animation (I think this is the case right now it the current animation clip is the default handle)

What solution would you like?
Adding some basic methods like animation_clip() and is_finished().
Also a way of figuring out if there is actually an animation. This could be either a method or return an Option from animation_clip() or just documenting that animation_clip() could return the default handle and that means that there is no animation playing.
Also maybe the default AnimationPlayer (like the one added to an entity in a gltf scene) should have better defaults like being paused and/or finished.
What alternative(s) have you considered?
You can manually track the current animation clip using a separate component but it is really annoying because you have to query and update an extra component.
You can calculate if the animation is finished if you know the current AnimationClip and look it up in Assets<AnimationClip> to find the length and comparing that to the AnimationPlayer's elapsed time. Again super annoying and probably requires to tack the current animation.
Additional context
These are issues that I came across in developing my Bevy Jam 2 submission. You can see how I worked around this in the code.
I am willing to do the implementation on this.

+1
I also had to work around these API limitations in my crate.


implement procedure to create psuedo SQL statetment fragments from  Expr enums.

Implementing this so that we can add a definition/description column for the show indexes command.
For example, if we have the following expression;
Expr::BinaryOp {
                left: Box::new(Expr::Identifier("id".to_string())),
                op: BinaryOperator::Plus,
                right: Box::new(Expr::Identifier("num".to_string()))
 }

this would be converted to:
id + num

Codecov Report

Merging #554 (ad77579) into main (5bfd458) will decrease coverage by 0.03%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##             main     #554      +/-   ##
==========================================
- Coverage   93.17%   93.14%   -0.04%
==========================================
  Files         179      180       +1
  Lines       11750    11870     +120
==========================================
+ Hits        10948    11056     +108
- Misses        802      814      +12

Impacted Files
Coverage Δ

core/src/ast/operator.rs
100.00% <ø> (ø)

core/src/ast/expr_decoder.rs
90.00% <90.00%> (ø)

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 5bfd458...ad77579. Read the comment docs.

I am thinking about merging this PR with PR #551 since the decode function will primarily be used with the show indexes from table functionality.  Should I keep it as a separate PR, or merge with #551?

Will continue this PR once PR #551 is merged.  Changed status to draft until then..

Nice!
Here... could you split the PR into two?
Two independent tasks exist in the single PR.

provide sql representation to gluesql ast
add description column to show indexes from table command

OK.  Will do


Instagram checkpoint pls fix

I dunno why this is happening but I NEED to message somebody on Insta like rite now! I don't have time to spare!

How to fix:
1- desactive your Instagram account via browser or Instagram app.
2- Open your account via iGDM.
It works for me


Document Algorithm Comparison

Compare the evaluated algorithms and conclude

Document why we can't compare and how we decided to continue (D3)


Custom endpoint config

Looks good!
But making four requests every time seems inefficient.
I'd propose to either make those requests on the first method call and cache the fastest domain to use for all subsequent requests, or use one domain by default and add those four domains as an optional parameter. What do you think?

making four requests every time seems inefficient

Although it makes 4 requests, it only completes one of them and kills the other requests when the first response is received.

first method call and cache the fastest domain

Given the instability of piratebay, with proxies and the official site going up and down all the time, I dont think we should rely on the consistency of the endpoints. For example, if endpoint A returns the fastest response and we cache the endpoint as the fastest but then it goes down, we're at a loss. Another inconsistency would be the speed of the API's. There is generally never an endpoint that consistently returns faster than the other endpoints. I noticed this when running tests. For some of the tests, the domain would be validated as part of the tests. As you know, they failed.
Another reason why we cant depend on one endpoint is because of PirateBay's notorious 'Database down for maintenance' issue. The chance that a certain endpoint will return quickly for one request and return a 'Database Maintenance' error for another request is very high.

Solution: allow the user to limit the number of concurrent requests in an 'advanced configuration' setting.
Thoughts?

Sounds good! And I like the concurrent requests option idea

In the Parser.js file, there's already a maxConcurrentRequests. All we need to do is allow it to be configurable.

🚢 🚢 🚢


fix(openai): handle async streaming responses for openai v1 client

Thanks @najork! Looks like the tests aren't actually running since we're missing some pytest async plugin (see test run logs).
When they do run - you'll need to run them locally. Here's how to do that:

Set the environment variable OPENAI_API_KEY with an actual API key.
Comment out this line
Run poetry run pytest -v --record-mode=once so that we'll have a recording of the requests + responses for future tests. Don't worry, this does not log your API key in any way, just the response completion you got from OpenAI so that the test can be run without actually calling OpenAI.


Switch to TME test subscription

API change check
API changes are not detected in this pull request.

/azp run js - storage - tests

/azp run js - template - tests

/azp run js - service-bus - tests-weekly

/azp run js - event-hubs - tests-weekly

js - communications-chat - tests-weekly
js - storage-blob - tests-weekly


GeoLite2 不再提供开放式公共下载服务

https://github.com/teddysun/across/blob/d984be07cccf6ea918db28d598e88ce0cecc6d3b/docker/v2ray/Dockerfile#L27
Starting December 30, 2019, we will be requiring users of our GeoLite2 databases to register for a MaxMind account and obtain a license key in order to download GeoLite2 databases. We will continue to offer the GeoLite2 databases without charge, and with the ability to redistribute with proper attribution and in compliance with privacy regulations. In addition, we are introducing a new end-user license agreement to govern your use of the GeoLite2 databases. Previously, GeoLite2 databases were accessible for download to the public on our developer website and were licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
Starting December 30, 2019, downloads will no longer be served from our public GeoLite2 page, from geolite.maxmind.com/download/geoip/database/*, or from any other public URL. See the section below for steps on how to migrate to the new download mechanism.

还真是……
有替代方案么？

稍等，我写个pull request

稍等，我写个pull request

好的，有劳了

PR 已提交，请大佬惠存

https://github.com/teddysun/across/pull/54 里写的：

注册 maxmind的账号，并生成自己的license_key

这样太麻烦了，干脆写一个脚本自动下载到我自己的服务器上，然后将这个网址改为我的服务器地址好了

我自己注册了个帐号，生成了 License key，然后又写了个 cron 脚本，每周自动去下载最新版。
下载地址为：
https://dl.lamp.sh/files/GeoLite2-Country-CSV.zip

你的脚本你做主😂


prepare plugin does not work if you only switch textures in animatedSprite.textures

Take a look at this example: http://forwardingsolutions.club/issue/px5
On second click, there should be texture atlas already loaded in GPU, because this function is called on first click:
function loadNext() {
    if (firstRun) {
        infiniteLoader.add('jimages/2s.png.json');
        infiniteLoader.load(function (loader, resources) {
            next.textures = setupFrames("2_000"); // setupFrames just prepares textures

            app.renderer.plugins.prepare.upload(next, () => {
                canRunNext = true;
                $("body").css("background-color","green");
            });
        });
...
}

However, there is still significant delay between click and the start of animation. I am not sure if this is a bug or am I just too stupid to use prepare functionality correctly, so I'll just leave it here for you to decide :)
What I am trying to achieve is to load texture atlases dynamically and display them on click without any delay. At the same time the click happens, the previously loaded texture atlas gets played. Sounds a lot easier than it is, because a running texture atlas animation freezes for example when new sprite is added to canvas.

Please refer to the forum thread where I answered your questions:
http://www.html5gamedevs.com/topic/29700-unexpected-delay-when-loading-texture-atlases-dynamiclly/
JS is synchronous, you can only do 1 thing at a time. If a texture is uploading, you have to wait for it. Whether it is us doing it automatically for you, or if you put it into prepare; it still takes the same time to upload.


added annotations that are images and images that are not annotations categories

Related click-up ticket: https://app.clickup.com/t/8694jez2z
On top of that ticket, added annotations that are images and images that are not annotations


[ADD ME TO THE ORGANIZATION]

Name:
Location:
Interest:
Discord username(optional):-
Why do you want to join?

I want to join because

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@SkyCaptainess Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.