cellRenderer with ng-click not firing

Hi.
I'm wondering if you can help me. I've got a cellRenderer function that creates a hyperlink. I need to fire a ng-click action on the hyperlink. The function for my click is in my controller.
ng-click="groupClick('test')" or ng-click="search.groupClick('test')" ----  doesn't fire
Any help appreciated.
Vinny

do you have 'angularCompileRows=true' set in the gridOptions?

Yes I did.
However I forgot to add the function the the scope of the cell.
Like this
params.$scope.groupClick = vm.groupClick;
So in the end it was user error :-)
Thanks for the reply.

Great you got it sorted!! To be honest, I had very little to go on with the above!

I wonder if it is worth adding in detection for when a user returns markup that uses obvious Angular directives (e.g. ng-click, ng-repeat and so on) without having the correct option enabled.
If you do detect it, you could log something to the console to warn the developer of their likely mistake.
You'd probably need a way to disable that warning via code, though, in case you did it deliberately. Perhaps a provider method or property?
It might make it more user friendly for new developers and cause you to spend less time dealing with GitHub issues like this one. :-)

On 22 Apr 2015, at 6:12 pm, Niall Crosby<EMAIL_ADDRESS>wrote:
Great you got it sorted!! To be honest, I had very little to go on with the above!
—
Reply to this email directly or view it on GitHub.

interesting idea. as more people use, am sure more people will be asking the same newbie questions. i was thinking of having the angularCompile the other way around - have it on by default, and property to turn it off. or just provide a FAQ section, that would be the top question in the FAQ!!

Personally I like the fact that it's off by default. It's stops unnecessary bloat being loaded. Specially if like me some of the grids are preloaded with data and don't need any interaction.In short if I want to use angular I'll switch the flag on.
The unclear bit was not realizing how important the params.$scope was. Because from the grid cell you don't have access to the controller scope unless you inject it into the params.$scope part.
Again what's nice is that I'm only injecting what I need. No unnecessary bloat.
I'm really impressed by how you're approaching the development of this module.Well done and I look forward to all the features coming.

Hadn't really thought about the impact of the grid using an isolated scope.
I can appreciate people would want it non-isolated. Or maybe have that as
an option. Especially given Angular Grid doesn't put anything into the
scope, so won't dirty it.
What does ng-grid do?
On 22 April 2015 at 12:50, vinnytheviking<EMAIL_ADDRESS>wrote:

Personally I like the fact that it's off by default. It's stops
unnecessary bloat being loaded. Specially if like me some of the grids are
preloaded with data and don't need any interaction.In short if I want to
use angular I'll switch the flag on.
The unclear bit was not realizing how important the params.$scope was.
Because from the grid cell you don't have access to the controller scope
unless you inject it into the params.$scope part.
Again what's nice is that I'm only injecting what I need. No unnecessary
bloat.
I'm really impressed by how you're approaching the development of this
module.Well done and I look forward to all the features coming.
—
Reply to this email directly or view it on GitHub
https://github.com/ceolter/angular-grid/issues/85#issuecomment-95147573.

--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Statements and opinions expressed in this e-mail may not
represent those of the sender. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender immediately and delete
the material from any computer.

ng-click is working fine.i need to pass another field value in one column.my code is
{
headerName: "Claim No.", field: "claimNumber", width: 100,enableRowGroup: true,filter: 'number',
cellRenderer: function (params) {
if (params.value != undefined) {
return '' + params.value + '';
}
else {
return "";
}
}
},
initially it is working fine. suppose if iam doing grouping, it shows error like ClaimID is undefined or null reference. i dont know why it is coming.

Hi All,
Can anyone help here, this click on callrenderer is not working for me... I am using ag-agrid. please help
this.myImageCellRenderer = function(rowEntity) {
return '✉';


Pytorch CrossEntropy function contains softmax

Hi, thanks for your nice code.
However, I find that your code has a bug: you apply CrossEntropy function after softmax activation. But actually pytorch CrossEntropy function itself takes logit as its input.
After removing the softmax activation, I'm able to improve the MLP from 90% to 95%.

Then by changing the network architecture to the MLP (784 -> 200 -> 200 -> 10), the accuracy is increased to 97% :)

Thx again! fixed.


Editing project description removes existing tags

[OSF-5802]

@kch8qx Since this is a bug and the fix is straight forward, can you promote this to a hotfix please? To do that, just create a new hotfix branch off of master and commit your change there.

Also, please add a regression test. A new view test in this class should do the trick: https://github.com/CenterForOpenScience/osf.io/blob/debe8122162851c8817fd265ea3e8ad698b0cecc/api_tests/nodes/views/test_node_detail.py#L236


docs: add C++/Nginx Plus

 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.


Material rendered black on non-instanced object, correct if object is instanced

Reported by Max from Insertcoin.tv.
LuxCore version: v2.3beta1
Scene: black_material.zip
Steps to reproduce:

Start a viewport render. The object will be instanced by BlendLuxCore and everything works fine
Start a final render. The object will not be instanced anymore and appear black

I have a feeling there might be NaNs involved here, possibly caused by some of these factors:

The object has a negative scale of -0.385706 along the Z axis (when the scale is applied in Blender, the problem vanishes)
A bump map is used on the object (when the bump map is removed, the problem vanishes)

Viewport render, object instanced:

Final render, object not instanced:

The problem may be in BlendLuxCore (or in the LuxCore export process). Try to do this test:

use FILESAVER to export the scene with +Z scale

use FILESAVER to export the scene with -Z scale

now import the 2 mesh .ply files inside Blender and check the normals: they point in the same direction (while they should be flipped in one case).

So the problem may be in the process of exporting normals when Z scale is negative (?)

You mean somewhere in here? https://github.com/LuxCoreRender/LuxCore/blob/ab1c6c65f7483f7aad50f020b6a4eb1c233da6cd/src/luxcore/pyluxcoreforblender.cpp#L673
Or maybe in https://github.com/LuxCoreRender/LuxCore/blob/09fc1058f148a946248c5f8ce2ce994ab5cc238c/src/luxrays/core/exttrianglemesh.cpp#L249
However, even with normals pointing to the wrong side, why would the mesh be black? Wouldn't that be like looking at it from the other side?

I should have fixed the problem: the transformation was swapping the handiness of reference system.

Confirmed, thanks!


Resizing game window with an enum selection widget open breaks layout

As title; sometimes the selection widget is not visible, other times it'll completely break the UI

Resolved in 1.21 - unsure if this is an issue in 1.20.1, but I don't recall anyone reporting it, so closing.


TS-4976: Regularize example plugins - blacklist

Incremental work on #1114.

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/10/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/23/

FreeBSD11 build failed! https://ci.trafficserver.apache.org/job/freebsd-github/1705/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/9/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1600/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/136/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/268/

[approve ci]

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/11/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/24/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1706/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/10/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1601/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/137/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/269/

[approve ci]

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/13/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/26/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1708/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/12/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1603/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/139/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/271/

[approve ci]

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/14/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/27/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1709/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/13/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/140/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1604/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/272/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/15/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/28/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/14/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1710/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1605/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/141/

clang-analyzer build successful! https://ci.trafficserver.apache.org/job/clang-analyzer-github/273/


zoro.to domain change

Source information and language
zoro.to (experimental) 13.29
Source new URL
https://aniwatch.to/
Other details
sanji.to no longer works, and all previous domains are redirected to the aforementioned url
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated all installed extensions.
[X] I have checked if the source URL is not already updated by opening WebView.
[X] I will fill out all of the requested information in this form.

#1832


Custom font doesn't remain applied to Entry

Whenever clicking on the floatLabel then click away without entering text,
the font of the placeholder is set back to the default font.

Due to changing placeholder text whenever focus is gained/lost.
Seems to be IOS bug.
Workaround:
Font should be reset to default then back to desired font whenever placeholder text is changed.


Update flatbuffers to 23.1.21

Would you mind explaining why you rejected this PR @chippers?

@gollth  yeah sorry I ended up directly releasing 23.5.8, and I'm tracking being able to update the next release but the build is a bit broken #7


antd

https://codesandbox.io/s/silly-blackwell-nm3qe?file=/index.html
if i use bundle antd and react to do a simple demo, react will throw an error
error:

https://reactjs.org/docs/error-decoder.html/?invariant=321

help!

@ije @asafamr @zhoukekestar @MarkTiedemann

Hello @fakership.
Please don't tag random contributors in your issue. In general, people can voluntarily subscribe to the issues of a repository and will then receive a notification if a new issue is opened. I, for one, am not subscribed to this repository's issues - and just because I contributed to this repository once, I don't want to be notified about your issue. Again, in future, please don't tag random contributors.
Also, please don't scream for help 1h after opening an issue. I know coding can be frustrating, we've all had that experience before. But please understand that most people on GitHub contribute in their freetime, for fun. Putting pressure on random, well-meaning people on the internet so that they quickly help you with your issue is not a nice gesture.
Regarding your issue, I'd suggest adding the example code as well as the error message that you encountered in the description of this issue so that it is easier for anyone looking at this issue to understand your problem. At the same time, this may be helpful to other people in the future who encounter the same error message.
Have a good one! Hope your isssue is gonna be fixed soon.

I am so sorry for my incorrect tag

@fakership Here's a minimal example of using antd via esm.sh. It works just fine, there's no issue.
<!DOCTYPE html>
<style>
	@import<EMAIL_ADDRESS></style>
<script type="module">
	import React from<EMAIL_ADDRESS>	import ReactDOM from<EMAIL_ADDRESS>	import { Button } from<EMAIL_ADDRESS>
	ReactDOM.render(
		React.createElement(Button, { type: "primary" }, "Click me"),
		document.body
	);
</script>

thank you very much, the difference is i use the bundle antd,  which will bundle react in antd, which has conflict the outer react

Okay. But that's not an issue with esm.sh, but an issue with antd/react, right?
PS: There should be a "Close" button that you can use to close this issue, if it's fixed in your opinion.

done


Implement Jest testing in bc-wallet-mobile

The majority of the scaffolding is done (the single test added is passing) but there is an issue with Jest not liking tests of components that import from bifold that was taking me too long to sort out. Possibly solvable by editing jest.config.js. Mocking bifold seems to make these tests pass but I don't think that's a valid solution.

I'm new to this project but maybe mocking bifold is a valid strategy? The tests in this project shouldn't be testing bifold. I should be assuming bifold is tested within bifold. There is still a lot of valuable testing that could be done with a mocked bifold in this project.

@jamshale just seeing this. I think I wasn't very clear, sorry about that. What I mean is that if a screen in BC Wallet uses a button imported from Bifold the tests won't run until I use a mock the button component in it's entirety. So it's essentially not testing the real thing unless I have a copy of Bifold in the mocks folder. There should be some configuration way around this issue but I haven't been able to find it. I think it's due to the fact that Bifold is a submodule and not a regular dependency.


Migrate all deprecated components and tools to the latest in Flutter 3.10.x

Why
Upgrading Flutter and Dart SDK to the latest versions, there are some deprecated components and tools that MUST be migrated, such as using the new dart format command (has been migrated here), dart run command, etc.
All necessary changes & guides are listed here https://docs.flutter.dev/release/breaking-changes. We should visit all necessary changes until the latest Flutter 3.10.x for the migration.
Who Benefits?
Developers

@thiennguyen0196 Could you please update this 1 more deprecated stuff?

Update using AsyncNotifier instead of deprecated StateNotifier https://github.com/nimblehq/flutter-templates/pull/244#discussion_r1274567520


podman: support to specify the namespace to join using the ns:/PATH notation

add a prefix --net ns:/PATH/TO/THE/NAMESPACE that can be used to specify what namespace must be joined.
We probably want to do the same thing for other namespaces

@mheon I might have misunderstood your previous comment about it and how to take rid of it, but I still think we want the extra configuration in libpod/container.go so that it can be used when the container is restarted.

LGTM

Why do we need to store the information separately when it's in the OCI
spec? All the namespaces and their paths are stored in there, and we'll use
the same base spec every time the container restarts. I don't think we need
to retain the namespace information twice, we just need to make sure that
none of the options that would replace the network namespace with one
podman sets up are set.
On Tue, Jul 24, 2018, 07:24 Tom Sweeney<EMAIL_ADDRESS>wrote:

LGTM
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectatomic/libpod/pull/1145#issuecomment-407371986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHYHCInvmlCgC8VlvuFUGG3xZsp9vzxEks5uJwPTgaJpZM4VcdVE
.

@mheon I've pushed a new version where that information is stored only in the OCI specs.  If this pattern looks good, I am going to add the same feature to other namespaces

BTW This was a heavily requested feature of Docker that was always rejected. Nice work @giuseppe

LGTM

@rh-atomic-bot r+


Handled an index out of bounds case when removing a valid element fro…

Handled an index out of bounds case when removing a valid element from a non empty customArrayList.
Refer to the issue https://github.com/deepak-malik/Data-Structures-In-Java/issues/2.
Added a boundary check when removing the elements.

Added set method in the ADT which sets an element in the index to a new value.


Moved our regression vault module to development/tests/regression

We decided to move the regression_vault.py module to our development section. This should increase our code coverage ratio "dramatically".

Codecov Report

Merging #16 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   83.71%   83.71%
=======================================
  Files          17       17
  Lines         522      522
=======================================
  Hits          437      437
  Misses         85       85

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 bf3ad91...e36d9b0. Read the comment docs.


Add Android Go VM to UTM Gallery

Can we use android go version for android on iPadOS?
Or some custom rom like lineages os ? That require less than 2gb ram as that the max ram we can allot to android vm running on iPadOS.
Kindly add support images for
Android Go
Lineage OS
As android 9 images is currently stuck on bootloop
Also some useful links:
https://www.androidpolice.com/2020/07/22/new-devices-with-2gb-of-ram-or-less-must-run-android-go-according-to-leaked-documents/amp/
https://www.android-x86.org

Since release of Swift Playground 4, would it be possible to launch UTM from there and still use JIT?

I believe your questions are:

Can we use Android Go in UTM on iPadOS?
Can we use LineageOS in UTM on iPadOS?

I believe that it requires a custom boot loader and firmware image to be supplied, then maybe the ARM version of Android (or LineageOS) could run in UTM (slowly due to emulation). Androidx86 should work in UTM, however on iPad it will also be slow.
I will close this as "wont fix" because the topic has come up many times and no-one has been able to get an ARM version of Android working.

I believe your questions are:

Can we use Android Go in UTM on iPadOS?
Can we use LineageOS in UTM on iPadOS?

I believe that it requires a custom boot loader and firmware image to be supplied, then maybe the ARM version of Android (or LineageOS) could run in UTM (slowly due to emulation). Androidx86 should work in UTM, however on iPad it will also be slow.

> I will close this as "wont fix" because the topic has come up many times and no-one has been able to get an ARM version of Android working.
And that's exactly why he referenced the Android-X86 Project at the end. He means support for any custom light roms, which there are tons.

It’s been tried and nobody got it working well. Android (even x86 android) depends heavily on gpu acceleration.

The Android ARM image in the Android developer app runs great on Apple M1 machines, and uses qemu to do it. I could be wrong, but it might not take much reverse-engineering to duplicate whatever qemu config is being used there.

Indeed. 🤔 (this is running the "Android Emulator" binary with the name of a specific device passed.
Emulator path: ~/Library/Android/sdk/emulator/emulator
Data path: ~/.android/avd/<Virtual Device Name>.avd/

Did some digging. The QEMU used in my copy of the Android Emulator (might be some months old) reports itself as 2.12.0 from 2018. This can be verified by running:
~/Library/Android/sdk/emulator/emulator -qemu -h
Generally you supposedly can pass the -qemu parameter to the emulator and everything after that will be passed along to the QEMU it launches. I tried to pass the -qemu -D ~/Desktop/avd.txt parameter to enable QEMU log but it does not create the log file. I believe the emulator program only accepts overriding QEMU parameters it uses itself (like -kernel).
Interestingly, this seems to be added to the QEMU help output:
-android-ports <consoleport>,<adbport> TCP ports used for the emulator instance and adb bridge
-android-wifi-client-port <client port> TCP port used to connect to another emulator running as a WiFi server.
 This allows WiFi traffic to pass between two emulators, one acting as a
 client and one as a server. The decision which is the server and which
 is the client does not affect WiFi functionality
-android-wifi-server-port <server port> TCP port to listen on that another emulator can connect to as a WiFi
 client. This allows WiFi traffic to pass between two emulators, one
 acting as a client and one as a server. The decision which is the
 server and which is the client does not affect WiFi functionality
-android-report-console <socket> report console port to remote socket
-dns-server <servers> use this DNS server(s) in the emulated system
-android-hw <file>
                specify the hw config ini file location
-skip-adb-auth  skip adb authentication dialogue
-timezone <timezone> use this timezone instead of host's default
-net-tap <tap interface> use the provided TAP interface for networking
-net-tap-script-up <script> script to run when TAP interface goes up
-net-tap-script-down <script> script to run when TAP interface goes down
-mem-file-shared (use with -mem-path) initializes RAM backing file (specified in -mem-path) as a shared mapping
-read-only mark the session as read-only and abandon all snapshot or any disk changes at exit.
-fuchsia Fuchsia kernel/image run. Only standard QEMU options are allowed after, and emulator does not start Android virtual devices automatically.-allow-host-audio Allows sending of audio from audio input devices. Otherwise, zeroes out audio.-restart-when-stalled Allows restarting guest when it is stalled.-perf-stat <file> Run periodic perf stat reporter in the background and write output to specified file.-multidisplay config a number of (MAX 3) multidisplays-google-maps-key Provide an API key to use with Google maps GUI-no-location-ui Disables the location UI in the extended window-record-session Screen record the emulator session-legacy-fake-camera emulates fake camera by legacy camera HAL-crostini Turn on optimizations for running in a VM on Chrome OS-wear-auto-forward automatically forward tcp:5601 on the host to tcp:5601 on a connected phone if a connected virtual watch is detected.
During emulation, the following keys are useful:
ctrl-alt-f      toggle full screen
ctrl-alt-n      switch to virtual console 'n'
ctrl-alt        toggle mouse and keyboard grab

From looking at the open source licenses, it appears both MoltenVK and/or SwiftShader are used to enable 3D graphics.
And the following is found in the emulator binary, probably from the disk images help page:
  The emulator needs several key image files to run appropriately.
  Their exact location depends on whether you're using the emulator
  from the Android SDK, or not (more details below).
  The minimal required image files are the following:
    kernel-qemu      the emulator-specific Linux kernel image
    ramdisk.img      the ramdisk image used to boot the system
    system.img       the *initial* system image
    vendor.img       the *initial* vendor image
    userdata.img     the *initial* data partition image
  It will also use the following writable image files:
    userdata-qemu.img  the persistent data partition image
    system-qemu.img    an *optional* persistent system image
    vendor-qemu.img    an *optional* persistent vendor image
    cache.img          an *optional* cache partition image
    sdcard.img         an *optional* SD Card partition image
    snapshots.img      an *optional* state snapshots image
  If you use a virtual device, its content directory should store
  all writable images, and read-only ones will be found from the
  corresponding platform/add-on directories. See -help-sdk-images
  for more details.

Further down the strings, I found this series of what looks like it might be QEMU parameters.
autoconfig: -sysdir %s
-image
autoconfig: -system %s
-vendor
autoconfig: -vendor %s
-kernel
autoconfig: -kernel %s
-ramdisk
autoconfig: -ramdisk %s
autoconfig: -datadir %s
%s/userdata-qemu.img

Shortly after, some CPU models (but they are 32 bit):
qemu32
Auto-config: -qemu -cpu %s
cortex-a8
mips32r6-generic
P5600

Finally, there are references in the strings to "Mac Camera capture" but I did not find such feature in the actual running emulator or its settings. The module name might be com.google.goldfish.mac.camera.capture.
Unfortunately, my reverse engineering skills don't go further than strings. I wasn't able to use UTM to boot the Android Emulator files (~/Library/Android/sdk/system-images/android-32/google_apis/arm64-v8a/). I've attached the output of a "get open files and ports" from Activity Monitor as well as the strings run on the emulator binary:
emulator-avd-strings.txt
emulator-avd-open-files-and-ports.txt

I'm running Android Studio 2021.1 on an M1 MacBook Pro. I've set up a Pixel 2 API 31 virtual device, Android 12.0, arm64, with Google Play. I'd be happy to provide whatever image files would be useful out of this setup.
Contents of the hardware-qemu.ini file:
hw.cpu.arch = arm64 hw.cpu.ncore = 4 hw.ramSize = 2048 hw.screen = multi-touch hw.mainKeys = false hw.trackBall = false hw.keyboard = true hw.keyboard.lid = false hw.keyboard.charmap = qwerty2 hw.dPad = false hw.rotaryInput = false hw.gsmModem = true hw.gps = true hw.battery = true hw.accelerometer = true hw.gyroscope = true hw.audioInput = true hw.audioOutput = true hw.sdCard = true disk.cachePartition = true disk.cachePartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/cache.img disk.cachePartition.size = 66m test.quitAfterBootTimeOut = -1 test.delayAdbTillBootComplete = 0 test.monitorAdb = 0 hw.lcd.width = 1080 hw.lcd.height = 1920 hw.lcd.depth = 16 hw.lcd.density = 420 hw.lcd.backlight = true hw.lcd.vsync = 60 hw.gltransport = pipe hw.gltransport.asg.writeBufferSize = 1048576 hw.gltransport.asg.writeStepSize = 4096 hw.gltransport.asg.dataRingSize = 32768 hw.gltransport.drawFlushInterval = 800 hw.displayRegion.0.1.xOffset = -1 hw.displayRegion.0.1.yOffset = -1 hw.displayRegion.0.1.width = 0 hw.displayRegion.0.1.height = 0 hw.displayRegion.0.2.xOffset = -1 hw.displayRegion.0.2.yOffset = -1 hw.displayRegion.0.2.width = 0 hw.displayRegion.0.2.height = 0 hw.displayRegion.0.3.xOffset = -1 hw.displayRegion.0.3.yOffset = -1 hw.displayRegion.0.3.width = 0 hw.displayRegion.0.3.height = 0 hw.display1.width = 0 hw.display1.height = 0 hw.display1.density = 0 hw.display1.xOffset = -1 hw.display1.yOffset = -1 hw.display1.flag = 0 hw.display2.width = 0 hw.display2.height = 0 hw.display2.density = 0 hw.display2.xOffset = -1 hw.display2.yOffset = -1 hw.display2.flag = 0 hw.display3.width = 0 hw.display3.height = 0 hw.display3.density = 0 hw.display3.xOffset = -1 hw.display3.yOffset = -1 hw.display3.flag = 0 hw.gpu.enabled = true hw.gpu.mode = host hw.initialOrientation = Portrait hw.camera.back = virtualscene hw.camera.front = emulated vm.heapSize = 512 hw.sensors.light = true hw.sensors.pressure = true hw.sensors.humidity = true hw.sensors.proximity = true hw.sensors.magnetic_field = true hw.sensors.magnetic_field_uncalibrated = true hw.sensors.gyroscope_uncalibrated = true hw.sensors.orientation = true hw.sensors.temperature = true hw.sensor.hinge = true hw.sensor.hinge.count = 0 hw.sensor.hinge.type = 0 hw.sensor.hinge.sub_type = 0 hw.sensor.hinge.fold_to_displayRegion.0.1_at_posture = 1 hw.sensor.roll = false hw.sensor.roll.count = 0 hw.sensor.roll.resize_to_displayRegion.0.1_at_posture = 6 hw.sensor.roll.resize_to_displayRegion.0.2_at_posture = 6 hw.sensor.roll.resize_to_displayRegion.0.3_at_posture = 6 hw.sensors.heart_rate = false hw.useext4 = true hw.arc = false hw.arc.autologin = false kernel.path = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//kernel-ranchu kernel.newDeviceNaming = yes kernel.supportsYaffs2 = no disk.ramdisk.path = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//ramdisk.img disk.systemPartition.initPath = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//system.img disk.systemPartition.size = 2619m disk.vendorPartition.initPath = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//vendor.img disk.vendorPartition.size = 800m disk.dataPartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/userdata-qemu.img disk.dataPartition.size = 6g disk.encryptionKeyPartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/encryptionkey.img PlayStore.enabled = true avd.name = Pixel_2_API_31 avd.id = Pixel_2_API_31 fastboot.forceColdBoot = false android.sdk.root = /Users/jon/Library/Android/sdk android.avd.home = /Users/jon/.android/avd
Directory listing of the AVD subdirectory:
% ls -sla total 13780152        0 drwxr-xr-x  23 jon  staff         736 Apr 11 10:58 .        0 drwxr-xr-x   5 jon  staff         160 Dec 21 13:46 ..        8 -rw-r--r--   1 jon  staff         146 Apr 11 10:58 AVD.conf    10432 -rw-r--r--   1 jon  staff    69206016 Dec 21 13:45 cache.img      648 -rw-r--r--   1 jon  staff      327749 Mar 26 11:03 cache.img.qcow2        8 -rw-r--r--   1 jon  staff        1255 Dec 21 13:45 config.ini        0 drwxr-xr-x   3 jon  staff          96 Feb 11 19:22 data        8 -rw-r--r--   1 jon  staff         140 Apr 11 10:57 emu-launch-params.txt        8 -rw-r--r--   1 jon  staff          50 Apr 11 10:58 emulator-user.ini    36864 -rw-r--r--   1 jon  staff    18874368 Dec 21 13:45 encryptionkey.img   415744 -rw-r--r--   1 jon  staff   212860928 Apr 11 10:57 encryptionkey.img.qcow2        8 -rw-r--r--@  1 jon  staff        3672 Apr 11 10:57 hardware-qemu.ini     8320 -rw-r--r--   1 jon  staff     4018924 Apr 11 10:57 initrd        0 drwxr-xr-x   6 jon  staff         192 Dec 21 13:46 modem_simulator        0 -rw-r--r--   1 jon  staff           0 Apr 11 10:57 multiinstance.lock        0 -rw-r--r--   1 jon  staff           0 Apr 11 10:57 read-snapshot.txt  1048576 -rw-r--r--   1 jon  staff   536870912 Dec 21 13:45 sdcard.img        0 drwxr-xr-x   2 jon  staff          64 Mar 26 11:03 snapshots        0 drwxr-xr-x   7 jon  staff         224 Apr 11 10:58 tmpAdbCmds   205760 -rw-r--r--   1 jon  staff<PHONE_NUMBER> Dec 21 13:45 userdata-qemu.img 12051712 -rw-r--r--   1 jon  staff<PHONE_NUMBER> Apr 11 10:58 userdata-qemu.img.qcow2     2048 -rw-r--r--   1 jon  staff     1048576 Dec  9 15:10 userdata.img        8 -rw-r--r--   1 jon  staff           8 Dec 21 13:45 version_num.cache

hate to necropost but @jlg89 the android developer website says that the qemu version they use is downstream with a couple of modifications so i dont know if it's possible to actually boot into that image without said modifications

I'm running Android Studio 2021.1 on an M1 MacBook Pro. I've set up a Pixel 2 API 31 virtual device, Android 12.0, arm64, with Google Play. Looks like it's using qemu 2.25202.12.0. I'd be happy to provide whatever image files would be useful out of this setup.
Contents of the hardware-qemu.ini file:
hw.cpu.arch = arm64
hw.cpu.ncore = 4
hw.ramSize = 2048
hw.screen = multi-touch
hw.mainKeys = false
hw.trackBall = false
hw.keyboard = true
hw.keyboard.lid = false
hw.keyboard.charmap = qwerty2
hw.dPad = false
hw.rotaryInput = false
hw.gsmModem = true
hw.gps = true
hw.battery = true
hw.accelerometer = true
hw.gyroscope = true
hw.audioInput = true
hw.audioOutput = true
hw.sdCard = true
disk.cachePartition = true
disk.cachePartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/cache.img
disk.cachePartition.size = 66m
test.quitAfterBootTimeOut = -1
test.delayAdbTillBootComplete = 0
test.monitorAdb = 0
hw.lcd.width = 1080
hw.lcd.height = 1920
hw.lcd.depth = 16
hw.lcd.density = 420
hw.lcd.backlight = true
hw.lcd.vsync = 60
hw.gltransport = pipe
hw.gltransport.asg.writeBufferSize = 1048576
hw.gltransport.asg.writeStepSize = 4096
hw.gltransport.asg.dataRingSize = 32768
hw.gltransport.drawFlushInterval = 800
hw.displayRegion.0.1.xOffset = -1
hw.displayRegion.0.1.yOffset = -1
hw.displayRegion.0.1.width = 0
hw.displayRegion.0.1.height = 0
hw.displayRegion.0.2.xOffset = -1
hw.displayRegion.0.2.yOffset = -1
hw.displayRegion.0.2.width = 0
hw.displayRegion.0.2.height = 0
hw.displayRegion.0.3.xOffset = -1
hw.displayRegion.0.3.yOffset = -1
hw.displayRegion.0.3.width = 0
hw.displayRegion.0.3.height = 0
hw.display1.width = 0
hw.display1.height = 0
hw.display1.density = 0
hw.display1.xOffset = -1
hw.display1.yOffset = -1
hw.display1.flag = 0
hw.display2.width = 0
hw.display2.height = 0
hw.display2.density = 0
hw.display2.xOffset = -1
hw.display2.yOffset = -1
hw.display2.flag = 0
hw.display3.width = 0
hw.display3.height = 0
hw.display3.density = 0
hw.display3.xOffset = -1
hw.display3.yOffset = -1
hw.display3.flag = 0
hw.gpu.enabled = true
hw.gpu.mode = host
hw.initialOrientation = Portrait
hw.camera.back = virtualscene
hw.camera.front = emulated
vm.heapSize = 512
hw.sensors.light = true
hw.sensors.pressure = true
hw.sensors.humidity = true
hw.sensors.proximity = true
hw.sensors.magnetic_field = true
hw.sensors.magnetic_field_uncalibrated = true
hw.sensors.gyroscope_uncalibrated = true
hw.sensors.orientation = true
hw.sensors.temperature = true
hw.sensor.hinge = true
hw.sensor.hinge.count = 0
hw.sensor.hinge.type = 0
hw.sensor.hinge.sub_type = 0
hw.sensor.hinge.fold_to_displayRegion.0.1_at_posture = 1
hw.sensor.roll = false
hw.sensor.roll.count = 0
hw.sensor.roll.resize_to_displayRegion.0.1_at_posture = 6
hw.sensor.roll.resize_to_displayRegion.0.2_at_posture = 6
hw.sensor.roll.resize_to_displayRegion.0.3_at_posture = 6
hw.sensors.heart_rate = false
hw.useext4 = true
hw.arc = false
hw.arc.autologin = false
kernel.path = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//kernel-ranchu
kernel.newDeviceNaming = yes
kernel.supportsYaffs2 = no
disk.ramdisk.path = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//ramdisk.img
disk.systemPartition.initPath = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//system.img
disk.systemPartition.size = 2619m
disk.vendorPartition.initPath = /Users/jon/Library/Android/sdk/system-images/android-31/google_apis_playstore/arm64-v8a//vendor.img
disk.vendorPartition.size = 800m
disk.dataPartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/userdata-qemu.img
disk.dataPartition.size = 6g
disk.encryptionKeyPartition.path = /Users/jon/.android/avd/Pixel_2_API_31.avd/encryptionkey.img
PlayStore.enabled = true
avd.name = Pixel_2_API_31
avd.id = Pixel_2_API_31
fastboot.forceColdBoot = false
android.sdk.root = /Users/jon/Library/Android/sdk
android.avd.home = /Users/jon/.android/avd

Directory listing of the AVD subdirectory:
% ls -sla
total 13780152
       0 drwxr-xr-x  23 jon  staff         736 Apr 11 10:58 .
       0 drwxr-xr-x   5 jon  staff         160 Dec 21 13:46 ..
       8 -rw-r--r--   1 jon  staff         146 Apr 11 10:58 AVD.conf
   10432 -rw-r--r--   1 jon  staff    69206016 Dec 21 13:45 cache.img
     648 -rw-r--r--   1 jon  staff      327749 Mar 26 11:03 cache.img.qcow2
       8 -rw-r--r--   1 jon  staff        1255 Dec 21 13:45 config.ini
       0 drwxr-xr-x   3 jon  staff          96 Feb 11 19:22 data
       8 -rw-r--r--   1 jon  staff         140 Apr 11 10:57 emu-launch-params.txt
       8 -rw-r--r--   1 jon  staff          50 Apr 11 10:58 emulator-user.ini
   36864 -rw-r--r--   1 jon  staff    18874368 Dec 21 13:45 encryptionkey.img
  415744 -rw-r--r--   1 jon  staff   212860928 Apr 11 10:57 encryptionkey.img.qcow2
       8 -rw-r--r--@  1 jon  staff        3672 Apr 11 10:57 hardware-qemu.ini
    8320 -rw-r--r--   1 jon  staff     4018924 Apr 11 10:57 initrd
       0 drwxr-xr-x   6 jon  staff         192 Dec 21 13:46 modem_simulator
       0 -rw-r--r--   1 jon  staff           0 Apr 11 10:57 multiinstance.lock
       0 -rw-r--r--   1 jon  staff           0 Apr 11 10:57 read-snapshot.txt
 1048576 -rw-r--r--   1 jon  staff   536870912 Dec 21 13:45 sdcard.img
       0 drwxr-xr-x   2 jon  staff          64 Mar 26 11:03 snapshots
       0 drwxr-xr-x   7 jon  staff         224 Apr 11 10:58 tmpAdbCmds
  205760 -rw-r--r--   1 jon  staff<PHONE_NUMBER> Dec 21 13:45 userdata-qemu.img
12051712 -rw-r--r--   1 jon  staff<PHONE_NUMBER> Apr 11 10:58 userdata-qemu.img.qcow2
    2048 -rw-r--r--   1 jon  staff     1048576 Dec  9 15:10 userdata.img
       8 -rw-r--r--   1 jon  staff           8 Dec 21 13:45 version_num.cache

Is there also Android Go images? Because the regular android has the limitation of requiring at least 2GB of RAM, thus cannot run on iOS where apps cannot allocate so much memory (from my understanding).


Create subscription module

According to the architecture explained in this article, subscriptions are important means of accessing music on Muzikie which introduce several benefits to the system:

Eliminate the need of storing tokens on the account for an extended period of time, making the accounts less attractive for attacks.
Enable users to purchase bigger packages and share with family members, essentially reducing the price they pay.
Make system more sustainable.

Architecture
With the revised architecture, subscriptions play the role of middlemen, holding the value paid by the user, and distributing it among the audio NFT tokens which are streamed using a subscription.

Substores
Similar to other modules, the data of the subscription module are stored in different substores.
Account substore
The account substore is reserved for storing the accounts who have purchased subscriptions. Each entry has one subscriptionID, which represents the subscription in use. More on this in #56
Subscription substore
The subscription substore is reserved for storing the subscription NFT tokens. The details of the subscriptions are explained in #57.
Subscription NFT tokens
Muzikie subscriptions are NFT tokens created only by the development account, which are freely purchasable by any other account.
Create command
This command creates a Subscription NFT token. The token by default belongs to the development account. Other accounts may freely purchase subscriptions by paying the price. More details about this command is explained In #54.
Purchase command
User may submit this command to purchase a subscription token, e.g transfer the ownership of a subscription NFT token from the development account to the transaction sender. Purchasing a subscription will

Debit the price of the NFT token from sender account.
Credit 20% of the NFT token price to the development account.
Credit the 80% of the price of the NFT token as consumable to the NFT token.
Subscriptions are not transferable. Therefore this command is available to any account, as long as the owner of the subscription token is the treasury account. More details about this command is #55.

UpdateMembers command
The owner of the subscription token may update the list of members at any time before the subscription is exhausted. More on this command in #61.
Audio module changes
Considering the new revision of the subscription module, we need to apply changes to the Audio module.
Updated Audio substore
The audio substore should add (loyalty) owners as
[
  {
     address: /* Account address */,
     share: /* A number from 1 - 100 */
  }
]

More on this change in #62.
Stream command
The stream command is used to pay the artists for their artists work using the value stored in the subscription token. Muzikie handles the stream API requests via the streamer application. Although the streamer application responds the requests based on the corresponding account info in the subscription module. More on this transaction in #53.
Create command
Following the changes above, the create command should define an additional owners list. More on this in #65 .
Destroy command
With the new owners property, we should change the destroy command so that only the owner who has the entire loyalty (100%) right is able to destroy the NFT audio. More on this transaction in #63.
Transfer command
Following the changes above, the transfer command should transfer loyalty rights of the token, instead of the ownerAddress. More on this in #64 .
Reclaim
Users can freely submit reclaim transactions, provided they own audios or playlists which have a non-reclaimed stream count.
The reclaim command removes the stream income for all the audio and playlist NFT tokens that belong to the sender.
We'll explain this transaction further in #60.
Endpoints and methods
The external communications of a module in Lisk ecosystem are handled by the endpoints and the cross-module communications are handled via methods. The subscription module is no exception. The following are the required methods and endpoints:
getSubscription
Retrieves an subscription corresponding the given subscriptionID.  #71
getAccount
Retrieves an account corresponding the given address. #72

There's also issue number #82 which fixes some issues.


tests: x86/pagetables: skip table dumping if large memory

For boards with (relatively) large memory, the test which dumps
page tables takes a long time to finish. The default timeout of
sanitycheck is not enough for those boards.  So limits to pagetable dumping to boards with
less than 32MB.
Fixes #28548
Signed-off-by: Daniel Leung<EMAIL_ADDRESS>

I'd like to solve this a different way. Can we #ifdef the body test_dump_ptables such that it calls ztest_test_skip() if CONFIG_SRAM_SIZE is larger than 16 megabytes or something like that?

I'd like to solve this a different way. Can we #ifdef the body test_dump_ptables such that it calls ztest_test_skip() if CONFIG_SRAM_SIZE is larger than 16 megabytes or something like that?

Yeah, it should be easy to do. Though are you fine with it not testing the page table dumping?

I'd like to solve this a different way. Can we #ifdef the body test_dump_ptables such that it calls ztest_test_skip() if CONFIG_SRAM_SIZE is larger than 16 megabytes or something like that?

Yeah, it should be easy to do. Though are you fine with it not testing the page table dumping?

Yeah that's fine with me, it doesn't actually "test" anything (other than the function doesn't crash) and I mostly put it there as a convenient way to get a page table dump.


Train everyone on Git workflows

We've started this process, but we still need to make sure everyone knows about
@kayladavis

[ ] Pull
[ ] Push
[ ] Rebase
[ ] Fast forward merge
[ ] Merge conflicts
[ ] Hard reset
[ ] Squash commits
[ ] Feature branches
[ ] It doesn't exist until it's pushed
[ ] Pull requests
[ ] Traceability to github

@kbaumzie

[x] Pull
[x] Push
[x] Rebase
[ ] Fast forward merge
[x] Merge conflicts
[ ] Hard reset
[ ] Squash commits
[x] Feature branches
[ ] It doesn't exist until it's pushed
[ ] Pull requests
[ ] Traceability to github

@elibosley

[x] Pull
[x] Push
[ ] Rebase
[ ] Fast forward merge
[x] Merge conflicts
[x] Hard reset
[ ] Squash commits
[ ] Feature branches
[x] It doesn't exist until it's pushed
[x] Pull requests
[ ] Traceability to github

@mesternefeld

[x] Pull
[x] Push
[ ] Rebase
[ ] Fast forward merge
[ ] Merge conflicts
[ ] Hard reset
[ ] Squash commits
[ ] Feature branches
[ ] It doesn't exist until it's pushed
[ ] Pull requests
[ ] Traceability to github

Go ahead and check the box when you've gotten a lesson on this from me.

Gonna close this since we're doing it differently now.


How to download the Roxford5k and rparis6k dataset

Hello, I want to know how to download the oxford5k and the rparis6k dataset, which contain the images and labels.

@Cindy-zhangtong  check this out: https://www.kaggle.com/datasets/qiubit/roxfordparis


Cleanup

See commit messages.

Thanks for contribute.

But, this branch has conflicts that must be resolved...
https://github.com/beucismis/awesome-fetch/pull/77/conflicts

Fixed. Please check again, thanks.

Thanks.


Updated Typescript example and config files

I added props and state to the example the way Typescript recommends
https://www.typescriptlang.org/docs/handbook/react-&-webpack.html
I updated tsconfig so the compiled code becomes what Zeit suggest at (e.g. async await)
https://zeit.co/blog/next
This way Typescript does it thing (intellisense, warnings at compiletime and removes declarations) and Zeit does the rest. (in the old example Typescript compiled to js and not jsx)
Advantages:

Removable - Typescript is just a layer.
Stackoverflow - you can post the JS code (which now looks good)
Issues - if you have an issue you need to post here on GH you would either have to post Typescript code or ugly JS code (compiled) Helpers could (rightly) say perhaps it is the Typescript to JS compilation that goes wrong.
Better use of Zeit servers capabilites. If they support async await why would we want Typescript to polyfill them. Therefore the goal should be to compile to es2017 and let Zeit do their thing.

The updates to the tsconfig are all necessary to achieve this.

To use options in the config to be able to get a readable output to be able to post on SO makes absolutely no sense to me. It doesn't take longer to remove the TS syntax sugar than making the code postable (making the code more generic, remove irrelevant stuff, remove customer specific stuff etc). If you post the output then you might end up with code that works and can be readable but still makes no sense to a human in the way it's being written. And if you want to implement an answer you get you will have to do some reverse engineering and figure out how tsc transpiles the code and how you should implement it in TS to get the same output as the answer. This feels like one of those "It works, but..."-tings.

I think the question is why would you want Typescript to compile it in the first place?
' The preserve mode will keep the JSX as part of the output to be further consumed by another transform step (e.g. Babel)' from https://www.typescriptlang.org/docs/handbook/jsx.html
Which is the case here.
Why rely on Typescript to do this? (It is not what they're "good at")
The best selling point is :
Better use of Zeit servers capabilites. If they support async await why would we want Typescript to polyfill them. Therefore the goal should be to compile to es2017 and let Zeit do their thing.

I agree but three out of four of the Advantages listed in the PR is about posting code on SO and Issues and being able to actually use the output instead of the TS files.

@OskarKlintrot  isn't it 2/4?
But you do agree, so if I fix the other things (spaces and casing) you would back this pull request?

To be honest, I appreciate the fix to get the example up and running but I don't really see the point of everything else (except maybe preserve). I still think what @giladgray wrote in the other PR should be the main focus of this example: "this seems like an ideal minimal typescript example: it provides a clean solution for the single problem of typescript compilation". But in the end I'm just a residue from the old PR and not part of Next.js.
Something that I personally think would contribute to the project is a "production ready"-example with proper setup of TS and handling of assets, the build in a separate folder (not the root) etc. Something to actually build upon to get something that can be delivered to a customer but still providing great DX. Basically having to examples:

examples/with-typescript-minimal-setup (the current example)
examples/with-typescript (a new example ready to build upon)

As I said I'm not part of Next.js and I'm currently using dotnet core for SSR and TS so don't take my words too serious, but... I think it can be a good idea to open up a new issue to either a) discuss rewriting the example (as you have done here) if you really really want that or b) discuss adding a new example (as I written above). See what the members and community of Next.js think and go from there. I understand that it must be frustrating to code stuff that just gets criticized and rejected so having a clear picture of what the project wants and needs is probably a good way forward. As I have written before, we discussed the current example for three weeks before everyone was satisfied and that's not a lot code and very unopinionated!

Ping @giacomorebonato who wrote the current example.

It is getting a bit frustrating when this (old setup)

keeps being preferred over this (PR):

When clearly the ladder is an ideal minimal typescript example.
The previous minimal setup actually did too much compiling, but was minimal in form of showing an actual typescript example.

Yeah but that's like updating package.json and changing two lines in tsconfig.json. You have rewritten much more than that so the example in this PR is a different one than the current example. If you just would have fixed the bug and updated the tsconfig.json with good arguments (letting Next.js do the build is a good argument, being able to post the output on SO is not IMHO) I don't think anyone would see a reason why not to just merge it but that is not what you have done here. This PR is not about fixing something, this is about throwing out something that has three weeks of discussions behind it and replace it with something new. So I think a good approach from here is:

Open a new issue about the bug in the current example (not running at all due to missing packages if I understand it correct). <-- Maybe a bit overkill since you already know how to fix it, some OS projects wants this anyway but not all, I don't know about Next.js
Open a PR fixing that issue. <-- This should be able to be merged without any discussions
Open a PR about the minimal changes in tsconfig.json, don't change stuff like es2015 to es6, it's just polluting the history. <-- I guess this would maybe end up in some questions about why if it's not backed by good enough arguments, I would definitely back this one if it looks good and only have the minimal changes to it
Open a new issue about adding a more complete example, see if people want it and if they do, what they actually want
When you have got a good picture about what the community wants from nr 4, open a new PR with that implemented

Again, I'm not part of Next.js and don't talk for them. This is just a common way of contributing to OS projects.

Keystonejs is an awesome project with some really solid guidelines for contributing that might be worth looking at. Their workflow is pretty much what I have described above.

'Yeah but that's like updating package.json and changing two lines in tsconfig.json.' +3
Every change in tsconfig is necessary and found trial and error :-/
That time could be saved by others trying to get Typescript setup.
It is actually the minimal changes to get the proper output (that is output like examples written by Zeit)
Thank you very much for the guide and feedback.
4+5 ok - but I would claim that I didn't make a more complete example - more like a minimal example (like they have in the other examples in the example folder)

I start to feel like I'm repeating myself but... I know that you haven't done a more complete example but you still have rewritten the example that we spent three weeks working on and that is where my problem is with this approach. I'm not complaining about necessary changes in tsconfig, I'm complaining about changes from es2015 to es6 (which was done in the previous PR). That means the same thing and is just polluting the history.
To sum up my thoughts on this:

Bug fixes are great
Leveraging Next.js instead of tsc is great
Unnecessary changing of options is not great
Rewriting an example with a lot of work behind is also not great unless discussed properly with the community and ultimately the members of the project
If you want to write something bigger than the current example code base-wise, feel free to open an issue for discussing it, I'm sure people will like the idea (at least I would love it)

Again, just MHO's.

You and me both (about the repeating ;-) But I think we are on the same page (or close)
No es6 in this PR :) so zero 'unnecessary changing of options'
'Rewriting an example with a lot of work behind' That was literally 12 lines of code and no Typescript.
My example was filled with convention errors and I am grateful for the corrections.
I have some work now - I hope others will try my version and comment. I am learning from this :)

Work was maybe the wrong word, discussion is what I meant but you get the point.

I like the "jsx": "react-native" settings, so .tsx compile to .js.
For the rest I like to compile TypeScript to ES6 so I can use latest language feature and then I don't mind to compile it again to ES5 with Babel.
But it is my humble and fast opinion. I will keep thinking about it.

@giacomorebonato '..to ES6 so I can use latest language feature..' I think you can do that regardless.
My point is that we shouldn't make Typescript rewrite/polyfill features supported by next.js.
IMO typescript should just strip the code for declarations and the rest should be done by next.js

vs

Some may (rightfully) care about lock in and bloating the code.

@giacomorebonato Any thoughts on "preserve" vs "react-native"?

If I target ES5 with TypeScript^2.2.2, I can't use even the Promise keyword. @bestwestern  Do you confirm?
@OskarKlintrot "preserve" would be semantically more correct, but the problem when I made the PR was that it compiled to .jsx and next was looking only for .js files.

Thanks for the explanation @giacomorebonato! 👍

I am receiving a lot of `Cannot use JSX unless '--jsx' flag is enabled' and alias doesn't work with this configuration.

@leesiongchan are you writing JSX in .tsx files? The configuration should work then.

I'm going to close this in favor of https://github.com/zeit/next.js/issues/2391


[HOLD for payment 2021-11-04] Chat - No results found message displayed even when results are found

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to https://staging.new.expensify.com
Log in with any account.
Tap + green fab and select "New chat" option
On the search box, search any user you have access to

Expected Result:
If a user is found the message ''No result found" hould not be displayed
Actual Result:
No results found message displayed even when results are found for searched user
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
1.91-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/131736762-bb64f633-48fd-40c8-a228-2b6f46903392.mp4

Expensify/Expensify Issue URL:
View all open jobs on GitHub

Sure, I will refactor it.

I was actually wondering if it's the case that we should be seeing both "Recents" and "Chats" in this view. I recall that when it was designed we only wanted personal details.
Looks like this changed here - but we didn't update this part of the code.
Might be something to keep in mind when deciding how to approach a refactor.

Issue reproducible during KI retests

Triggered auto assignment to @NikkiWines (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Based on Rory's comment here seems like we should have already hired @parasharrajat for this one? If we haven't yet, @MitchExpensify can you hire him now?

I am on vacation. back on 8.

Hired!

@roryabraham I am picking this up now. What kind of refactor are you asking here?

UI|JSX.
methods logic.
Or Both. Overall sight says that A common component can be made which can be adjusted based on props.
for example, a prop for choosing option method getNewChatOptions | getNewGroupOptions etc.

Looking for a direction. Thank you.

@parasharrajat Both UI/JSX and methods could be DRY'd up. I would just take an iterative approach – I think you'll find that there's a ton that could be easily cleaned up. To get you started:

personalDetailsPropTypes should be extracted to its own file
There are some seemingly unnecessary JSX differences
The only difference between getNewChatOptions and getNewGroupOptions is that getNewGroupOptions takes an optional selectedOptions array. selectedOption is then passed directly to getOptions, which has a default value of [] for that parameter anyways. The only other difference is that getNewGroupOptions passes includeMultipleParticipantReports: false to getOptions. We could pretty easily combine these two functions into just a single getNewChatOptions.
NewChatPage can basically be seen as nearly identical to NewGroupPage, except that the maximum number of report participants is 2 instead of CONST.REPORT.MAXIMUM_PARTICIPANTS, and that it should immediately create the chat when the other participant is selected, instead of allowing the user to select multiple participants.

Thanks for the details. I got it.

Issue reproducible during KI retests.

@parasharrajat Whoops! This issue is 2 days overdue. Let's get this updated quick!

PR is in draft as low priority

Hi @parasharrajat, I've placed this issue on hold as per this update, as we are prioritising issues related to a feature release scheduled for 9/24. As an apology for the delay, we will add a $100 bonus as a thank you for waiting.

Issue reproducible during KI retests.

@parasharrajat Whoops! This issue is 2 days overdue. Let's get this updated quick!

Issue reproducible during KI retests.

@parasharrajat 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@parasharrajat 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

On hold

@parasharrajat 10 days overdue. I'm getting more depressed than Marvin.

On hold, not overdue

Issue reproducible during KI retests

Please refer to this post for updated information on the n6 hold, we've raised the bonus to $250 for all issues where a PR is created before the N6 hold is lifted.

Issue not reproducible during KI retests. (Third week)

@MitchExpensify just bringing to your attention that I have done extra work on the PR for this issue based on this https://github.com/Expensify/App/issues/4993#issuecomment-910837371 request.

@parasharrajat Tangentially related, but IMO there is too much-duplicated code between NewChatPage and NewGroupPage, and also partially SearchPage. I would be willing to pay a small bonus if you spend some time DRYing up that code. Up to you!

According to this, this job should be paid with a bonus for that work which is exclusive of N6-bonus. Thank you.

Thanks for the heads up @parasharrajat !

Ping for

Sorry for all these extra actions due to the N6 hold causing old jobs to close in Upwork @parasharrajat . I think this is the last one on my end. Please apply for the new posting here, thanks!

There can be the following reasons:
1- The check is just put on the base of contacts not also on the recent basis.
2- The check put on both the contact and recent basis but not handle in case of recent single base.
This can be resolve with 5 hours.

Responding to upwork job: https://www.upwork.com/jobs/~0197df495d5d91b0d5
For this issue, my first guess would be that the response from the API is perhaps formatted differently, and the UI isn't displaying anything, because it's unable to parse the response properly?

@ALIHASSAN65 and @opal6502 this job is completed and awaiting payment. To view open jobs check here https://github.com/Expensify/App/issues?q=is%3Aopen+is%3Aissue+label%3A"Help+Wanted"

Ping for

Issue not reproducible during KI retests. (Fourth week)
@roryabraham Let us know if you want us to keep checking it in KI retests

Paid @parasharrajat inc. the n6-hold bonus

@mallenexpensify I think you missed this https://github.com/Expensify/App/issues/4993#issuecomment-958655633 comment here.

Thanks Rajat, 100% missed that.  Since the amount was confirmed and Rory referenced small bonus, I'm going to add another bonus of $250.  Let me know if you don't think that's fair.

Sounds good. Something is better than nothing. :1st_place_medal:

Done. Thanks for the help Rajat!


Create settings.py having Settings class for changing web WhatsApp's settings

Add the following automation

notifications(is_sounds, is_desktop_alerts, is_show_previews, is_turn_off_desktop_notifications): taking boolean values to set followings

theme(theme): Taking constant values from contants.py i.e add new class STRINGS having sub-class SETTINGS having contants like THEME_LIGHT='Light' so that we can use theme(STRINGS.SETTINGS.THEME_LIGHT)

block_contacts(contacts): takes a list of contacts to add in the blocklist

Hey, I would like to try this issue

Hey, I would like to try this issue

@beatorizu You are most welcome. 😊

@beatorizu
I want to suggest something that will help alot
https://github.com/Tithibots/tithiwa/pull/30#issuecomment-707633120 and https://github.com/Tithibots/tithiwa/pull/30#issuecomment-707644654

@beatorizu you can ask me if you are facing any problems while doing it.

Thank you, guys 😊

How do I start a session? Do I need to use my personal number?

How do I start a session? Do I need to use my personal number?

You can use it, but as i know it a bad idea to use my personal number as i was experimenting things like exiting groups.. Etc so i cloned my whatsapp and created a new whatsapp with my other number for that purpose.

How do I start a session? Do I need to use my personal number?

You can use it, but as I know it is a bad idea to use my personal number as I was experimenting with things like exiting groups. Etc so I cloned my WhatsApp app on my mobile and created a new WhatsApp account with my other mobile number for that purpose.

How do I start a session? Do I need to use my personal number?

You can use it, but as I know it is a bad idea to use my personal number as I was experimenting with things like exiting groups. Etc so I cloned my WhatsApp app on my mobile and created a new WhatsApp account with my other mobile number for that purpose.

As I am changing things related to settings I believe that it is fine to use my own phone number :thinking:

As I am changing things related to settings I believe that it is fine to use my own phone number 🤔
Yes.


Upgrade to Swift 3.0

Thanks for your PR! I merged it into a new branch where I will be overhaul the internal names (to better fit Swift 3) before merging it into master.


Update CHANGELOG.md

Version 4.1.2: Correct border in the full scope of elements with border-box

@jonathantneal, as you closed #598, this can be closed too.


Remove?

Do we still need this, now we test in the compiler travis build?

No, I don't think so. We could break this up over the various test directories in the core repos.

I'll archive and move to purescript-deprecated then.


chore: add cnpg plugin for kubectl

Add the cnpg plugin for kubectl to be used with CloudNativePG operator

Description
This PR aims to add the cnpg pluging for kubectl to be used with CloudNativePG operator, in a future
PR we hope to provide also a way to install this operator using arkade
Motivation and Context
The cnpg plugin can make use of Arkade to distribute the plugin
Issue  https://github.com/alexellis/arkade/issues/852
How Has This Been Tested?
Local laptop using amd64 and RaspberryPi B4 both to install the plugin both with Linux
Local laptop using amd64 with macOS
Are you a GitHub Sponsor yet (Yes/No?)

[X] Yes
[ ] No

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Documentation

[X] I have updated the list of tools in README.md if (required) with ./arkade get -o markdown
[ ] I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

[x] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I've read the CONTRIBUTION guide
[X] I have signed-off my commits with git commit -s

[x] I have tested this on arm, or have added code to prevent deployment

@Jasstkn could you help out here with explaining how to do the checker script that shows the arch for each binary? The one we have in the contributing guide.

@sxd Hi! thanks for the contribution. Please, check our contribution guide to see how the code should be properly tested.
One of the mentioned ways is to use our test script. You can run it by executing the following:
./hack/test-tool.sh <tool_name>

The output of this should be added to the PR's description. It will speed up the review process 🚀

@alexellis @Jasstkn working on it! thank you!!! and sorry for wasting your time I thought that I followed all the contribution guide but clearly I didn't, my bad! fixing!

@Jasstkn here is the output:
./hack/test-tool.sh kubectl-cnpg
+ ./arkade get kubectl-cnpg --arch arm64 --os darwin --quiet
+ file /home/zeus/.arkade/bin/kubectl-cnpg
/home/zeus/.arkade/bin/kubectl-cnpg: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>
+ rm /home/zeus/.arkade/bin/kubectl-cnpg
+ echo

+ ./arkade get kubectl-cnpg --arch x86_64 --os darwin --quiet
+ file /home/zeus/.arkade/bin/kubectl-cnpg
/home/zeus/.arkade/bin/kubectl-cnpg: Mach-O 64-bit x86_64 executable
+ rm /home/zeus/.arkade/bin/kubectl-cnpg
+ echo

+ ./arkade get kubectl-cnpg --arch x86_64 --os linux --quiet
+ file /home/zeus/.arkade/bin/kubectl-cnpg
/home/zeus/.arkade/bin/kubectl-cnpg: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=c8EnbaDLyYSH5tuhAN-I/0Xl4aey1cq1x8eY1BR2z/AT7ShFvoaMOD48e969WV/tIKr3LQQwdHlqO9VFZ0h, stripped
+ rm /home/zeus/.arkade/bin/kubectl-cnpg
+ echo

+ ./arkade get kubectl-cnpg --arch arm64 --os linux --quiet
+ file /home/zeus/.arkade/bin/kubectl-cnpg
/home/zeus/.arkade/bin/kubectl-cnpg: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=leVwSvJ3d-6YzsMXcO1B/xnofTK4v6MCNdYr9wwHt/tPTd9mv1MB_orY3ZalS3/yknIaaHoN4vYgohfdfV5, stripped
+ rm /home/zeus/.arkade/bin/kubectl-cnpg
+ echo

+ ./arkade get kubectl-cnpg --arch x86_64 --os ming --quiet
+ file /home/zeus/.arkade/bin/kubectl-cnpg
/home/zeus/.arkade/bin/kubectl-cnpg: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, Go BuildID=leVwSvJ3d-6YzsMXcO1B/xnofTK4v6MCNdYr9wwHt/tPTd9mv1MB_orY3ZalS3/yknIaaHoN4vYgohfdfV5, stripped
+ rm /home/zeus/.arkade/bin/kubectl-cnpg
+ echo

I ran make e2e and I got an error:
    --- FAIL: Test_CheckTools/Download_of_kubeseal (0.47s)

I think it's not related but it's looking for a file that doesn't exists here:
=== NAME  Test_CheckTools/Download_of_kubeseal
    url_checker_test.go:51: Error with HTTP HEAD for kubeseal, https://github.com/bitnami-labs/sealed-secrets/releases/download/helm-v2.7.6/kubeseal-helm-v2.7.6-linux-amd64.tar.gz: status code: 404, body:

The e2e tests were failing but are now fixed in the master branch.
@Jasstkn can you give a review when you have time?

I just rebased the PR on master branch so now it shouldn't fail

We just missed the update to the README which is part of the PR template.
You checked it but I don't think you added the file?

I have updated the list of tools in README.md if (required) with ./arkade get -o markdown

I'll sort out the README for you.
Thanks for contributing to arkade and for being a sponsor too.


trigger: true for version on rc step

Good afternoon,
I've been testing the go pipeline and I witnessed a strange behaviour that seems to be caused by the trigger: true for the version resource on the RC step.
Basically for every git commit the test step runs, that eventually triggers the rc step and because rc bumps the version it seems like it runs twice. Later down the road when the bump-patch runs it looks like another rc is run again.
Is there something that I am doing wrong?

Hey @marccardinal, which pipeline folder are you using?

Hi @drnic , I have seen that behaviour with the go pipeline but I could see it happen with other ones too since the version -> rc -> version followed by shipit -> patch bump -> version pattern also exists elsewhere. Is it something you have seen?


on windows can't open line with absolute path on windows

VSCode Version: Code 1.5.3 (5be4091987a98e3870d89d630eb87be6d9bafd27, 2016-09-22T08:50:42.185Z)
OS Version: Windows_NT ia32 10.0.14393

Steps to Reproduce:
as you can see when i use -g option with absolute path, i got error.
"Arguments in --goto mode should be in the format of FILE(:LINE(:COLUMN))."

Can you show how the command you run looks like exactly?

@kefengwei @joaomoreno I think we fixed this in our insider release, I got a related bug some time ago.
Can you try with insiders please?
You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

@bpasero I try with insiders, the problem got solved.thanks.

Absolute path in Windows would have the drive letter making this duplicate of #11731


To do list project for review

This pull request is created by me for my coding partner to review my JavaScript practices.

Hello @Sajeelzafar 👋🏽
Your work is completed! You did a remarkable job at it. 💯
It's time to merge it.
Congratulations. 🥳
Cheers and Happy coding!👏👏👏


cog build -t X fails with "Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory)" on podman system

Hi.  Running into an issue while building an image with PODMAN.  I know it's not a first tier platform, but it looks like there's maybe a bad image resolving early on and there doesn't seem to be a way to change it.  I've tried with many permutations of cuda and python version (CUDA 11.3 / Python 3.9, etc), but the determining factor seems to be just that running with podman doesn't grab a correct base image.  This could be a podman issue, but again, without a way to change what image Cog is using it's hard to tell.
Cog Version: 0.4.4 (built 2022-09-23T19:52:35Z)
Operation System: MacOS Monterey 12.6
Steps to Reproduce:

Create a new directory (mkdir example)
Create a cog.yaml file with the following contents:

build:
  gpu: true
  cuda: "11.6.2"
  python_version: "3.10"
predict: "predict.py:Predictor"

Create a minimal predict.py placeholder.  One is provided below.

from cog import BasePredictor, Path

class Predictor(BasePredictor):
    def setup(self):
        self.test = "foo"
    def predict(self,) -> Path:
        with open("/tmp/asdf.txt", 'wt') as fout:
            fout.write("asdf")
        return Path(f"/tmp/asdf.txt")

Run cog build -t test

Expected Behavior:
Image with name 'test' should build.
Output (Docker):
Building Docker image from environment in cog.yaml as test...
[+] Building 246.2s (17/17) FINISHED
 => [internal] load .dockerignore
 => => transferring context: 2B
 => [internal] load build definition from Dockerfile
 => => transferring dockerfile: 1.50kB
 => resolve image config for docker.io/docker/dockerfile:1.2
 => docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc
 => => resolve docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc
 => => sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc 1.69kB / 1.69kB
 => => sha256:e3ee2e6b536452d876b1c5aa12db9bca51b8f52b2505178cae6d13e33daeed2b 528B / 528B
 => => sha256:86e43bba076d67c1a890cbc07813806b11eca53843dc643202d939b986c8c332 1.21kB / 1.21kB
 => => sha256:3cc8e449ce9f6e0752ede8f50a7334bf0c7b2d24d76da2ffae7aa6a729dd1da4 9.64MB / 9.64MB
 => => extracting sha256:3cc8e449ce9f6e0752ede8f50a7334bf0c7b2d24d76da2ffae7aa6a729dd1da4
 => [internal] load build definition from Dockerfile
 => => transferring dockerfile: 1.50kB
 => [internal] load metadata for docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04
 => [internal] load build context
 => => transferring context: 63.64kB
 => [stage-0 1/8] FROM docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04@sha256:55211df43bf393d3393559d5ab53283d4ebc3943d802b04546a24f3345825bd9
 => => resolve docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04@sha256:55211df43bf393d3393559d5ab53283d4ebc3943d802b04546a24f3345825bd9
 => => sha256:f7fc13e0aab50148a520cd621e5ca618499c89841b04a3b042313c502fc85a70 2.43kB / 2.43kB
 => => sha256:c433df359e8b6ab825294348ea7686b6b9f559e3b819ad9963a904015778b43b 15.72kB / 15.72kB
 => => sha256:d7c6ec6e132736acf58653941565cac6853e607de890402319cacaeaf6842c78 7.93MB / 7.93MB
 => => sha256:943d01f4776a586a39e2e8686e607b319054734758f83695bc4d26812ff90e29 23.56MB / 23.56MB
 => => sha256:55211df43bf393d3393559d5ab53283d4ebc3943d802b04546a24f3345825bd9 743B / 743B
 => => sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0 28.57MB / 28.57MB
 => => sha256:23025e0ea7d2d4d8fb89bf49dbb5c4a0b2c9cef36933b7340b3dde1d1ba25c2a 185B / 185B
 => => sha256:8acc1c2b01b060fe5e76a5a2cd51a8bb5933c95c37d555177b8389cad5fe075c 6.43kB / 6.43kB
 => => sha256:894d0771aab577d61591f298845419ffdc8cb447edfc4e4b1954e32f1ea2ac18 1.12GB / 1.12GB
 => => sha256:8451e5a9bff2cba28ca62a5fac2d5eeadb80e1fefb493a0c8226ae9872690d0f 62.77kB / 62.77kB
 => => sha256:a6b5bd0a44ab412914eb46718eec8ba90e455e87dc8a13770d8d792095dcd691 1.44GB / 1.44GB
 => => sha256:364573d3ec9893e492751572bc8e887636634153c117a2c546be2044abf341bb 85.72kB / 85.72kB
 => => extracting sha256:d5fd17ec1767521cf97f61568096bfc9a7cd9c2d149576a7b43930c5a97062b0
 => => sha256:75b4e35cee13d4ba9da6d6e1a415d7d3618ceb4da44f970dacb94ef207c6fd0b 1.48GB / 1.48GB
 => => extracting sha256:d7c6ec6e132736acf58653941565cac6853e607de890402319cacaeaf6842c78
 => => extracting sha256:943d01f4776a586a39e2e8686e607b319054734758f83695bc4d26812ff90e29
 => => extracting sha256:23025e0ea7d2d4d8fb89bf49dbb5c4a0b2c9cef36933b7340b3dde1d1ba25c2a
 => => extracting sha256:8acc1c2b01b060fe5e76a5a2cd51a8bb5933c95c37d555177b8389cad5fe075c
 => => extracting sha256:894d0771aab577d61591f298845419ffdc8cb447edfc4e4b1954e32f1ea2ac18
 => => extracting sha256:8451e5a9bff2cba28ca62a5fac2d5eeadb80e1fefb493a0c8226ae9872690d0f
 => => extracting sha256:a6b5bd0a44ab412914eb46718eec8ba90e455e87dc8a13770d8d792095dcd691
 => => extracting sha256:364573d3ec9893e492751572bc8e887636634153c117a2c546be2044abf341bb
 => => extracting sha256:75b4e35cee13d4ba9da6d6e1a415d7d3618ceb4da44f970dacb94ef207c6fd0b
 => [stage-0 2/8] RUN rm -f /etc/apt/sources.list.d/cuda.list &&     rm -f /etc/apt/sources.list.d/nvidia-ml.list &&     apt-key del 7fa2af80
 => [stage-0 3/8] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends  make  build-essential  libssl-d
 => [stage-0 4/8] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash &&  git clone https://github.com/mo
 => [stage-0 5/8] COPY .cog/tmp/build1946552261/cog-0.0.1.dev-py3-none-any.whl /tmp/cog-0.0.1.dev-py3-none-any.whl
 => [stage-0 6/8] RUN --mount=type=cache,target=/root/.cache/pip pip install /tmp/cog-0.0.1.dev-py3-none-any.whl
 => [stage-0 7/8] WORKDIR /src
 => [stage-0 8/8] COPY . /src
 => exporting to image
 => => exporting layers
 => => writing image sha256:a43d2dbaee9dea0378d6d82b2aa599295f964f2201019fb8d8e1dfa195bb844f
 => => naming to docker.io/library/test
 => exporting cache
 => => preparing build cache for export
 Adding labels to image...

Observed Behavior:
Image fails to build on step 7 of 14.
Output (Podman):
Building Docker image from environment in cog.yaml as test...
STEP 1/14: FROM nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04
STEP 2/14: ENV DEBIAN_FRONTEND=noninteractive
--> Using cache eab19441a2d4cd95cc652472f3f3cfdc4b87e45883aba512ed861b7919a39068
--> eab19441a2d
STEP 3/14: ENV PYTHONUNBUFFERED=1
--> Using cache d59852caafbcc5d0f28844e18988cb28f6b69403bd09d44c94acee854426b097
--> d59852caafb
STEP 4/14: ENV LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/x86_64-linux-gnu:/usr/local/nvidia/lib64:/usr/local/nvidia/bin
--> Using cache 7f4c6ed0959359dad0031fa8da071153a3c17f93f227cb7bcd875e1b444688f4
--> 7f4c6ed0959
STEP 5/14: RUN rm -f /etc/apt/sources.list.d/cuda.list &&     rm -f /etc/apt/sources.list.d/nvidia-ml.list &&     apt-key del 7fa2af80
--> Using cache ff376225f38a783739b72148a68e3e5e046de4c27e2307320235ed3de7920515
--> ff376225f38
STEP 6/14: ENV PATH="/root/.pyenv/shims:/root/.pyenv/bin:$PATH"
--> Using cache 72a9604c400e28e66e3cec9347578c86afafbc21b9174d33b644847b8354c38d
--> 72a9604c400
STEP 7/14: RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends      make    build-essential         libssl-dev        zlib1g-dev      libbz2-dev      libreadline-dev         libsqlite3-dev  wget    curl    llvm    libncurses5-dev         libncursesw5-dev        xz-utils        tk-dev    libffi-dev      liblzma-dev     python-openssl  git     ca-certificates         && rm -rf /var/lib/apt/lists/*
E: Archives directory /var/cache/apt/archives/partial is missing. - Acquire (2: No such file or directory)
Error: error building at STEP "RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends  make    build-essential  libssl-dev       zlib1g-dev      libbz2-dev      libreadline-dev         libsqlite3-dev  wget    curl    llvm    libncurses5-dev         libncursesw5-dev        xz-utils tk-dev   libffi-dev      liblzma-dev     python-openssl  git     ca-certificates         && rm -rf /var/lib/apt/lists/*": error while running runtime: exit status 100

ⅹ Failed to build Docker image: exit status 100

EDIT: Fixed copy/paste error for sample predict.py.
EDIT 2: In adding the stack trace for the good docker build, I noticed the one that works is using a cached nvidia image.  If it turns out that the cached version fails then this is an issue with nVidia breaking their container and I'll close the issue.
EDIT 3: After clearning the cache and rebuilding, can confirm it's NOT an issue with the nVidia image.

I think I have this narrowed down to an issue with --mount=type=cache,target=/var/cache/apt in Docker vs Podman.  I'm calling it a day for now but that's still beyond my control.

If the issue persists after cleaning the cache and rebuilding, it is might be due to a misconfiguration in the cog.yaml file. Consider checking the syntax of the cog.yaml and ensuring the specified packages are available in the environment. Additionally, you can try to explicitly install the missing packages as part of the build step.
You can install the missing podman package using the '--install' flag. For example, to install the podman package, you can use the following command: apt-get install --install podman.
Let me know if that helps!
Got this from Clerkie (ai code debugger bot) - https://sinfulvibrantexponents.krrishdholakia.repl.co/

Hi @krrishdholakia.  While I appreciate the attempt, I think this may be a teachable moment and while this is a criticism of the reply, it's not intended with malice and I laude the willingness to help.  There's nothing inherently wrong with using an AI code debugger, but it should be a starting point for our investigation and not the end.  If we find ourselves applying AI debuggers to tickets, we must be wary of their relevance.  For example,

You can install the missing podman package using the '--install' flag. For example, to install the podman package, you can use the following command: apt-get install --install podman.

First, podman is installed, as should be apparent from the first message.  The statement is vacuous.  Second, even if it weren't, the system in question is not a Linux machine, as mentioned.

it is might be due to a misconfiguration in the cog.yaml file. Consider checking the syntax of the cog.yaml and ensuring the specified packages are available in the environment.

The cog.yaml is provided in the first message, too, but if there's a misconfiguration it's not obvious.  I would liken this to "I think there is a bug in my code," being replied to with, "this can be caused by a bug in the code."  On the surface, it's possibly correct.  The cog.yaml passes parsing, but if there are parameters which disagree it's not clear what, and that's where I'd hope to gain insight.
StackOverflow has banned AI-generated answers for similar reasons: they have a high rate of being incorrect and irrelevant.  There's already a lot of noise on the internet and if we add content that's even harder to distinguish from signal then it can make for a worse experience for all of us.
Please don't let this discourage you from volunteering answers in the future.  I respect and appreciate the desire to help, but perhaps it's worth keeping Clerkie to personal projects?

And, for what it's worth, this is still an issue, though it looks like ~16 hours from now the release file for focal-securities will be valid and the command may work?
$ cog build -t test
Building Docker image from environment in cog.yaml as test...
STEP 1/14: FROM nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04
Resolving "nvidia/cuda" using unqualified-search registries (/etc/containers/registries.conf.d/999-podman-machine.conf)
Trying to pull docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04...
Getting image source signatures
Copying blob sha256:9ce4eceb346b57d4be964a3a57551204b7435b2eae1d8c3154ef672661d710e4
Copying blob sha256:eaead16dc43bb8811d4ff450935d607f9ba4baffda4fc110cc402fa43f601d83
Copying blob sha256:cb69caf25724810d45aec6392c11de6f67c2efde38da9d46402857dedb68aefb
Copying blob sha256:3a665e4036160d33fc32ce19c889271febc4fe4cdb82637cdd8c9ef10ca9541c
Copying blob sha256:bcf9a52c75ac54dc66b5b683fc8dc2bb8a1cc8eef9340433a3efbfe8d6fa3006
Copying blob sha256:8941157b58ada869bd12299ba8a56cdc5317923a5ce7df8158c5a3b44ff2fb67
Copying blob sha256:b1c91cec61e689319fc5354207f545dc4d065599ae530f8aae92bded993c72e3
Copying blob sha256:01035e520ac2fd77f181410687ecc81e9df074e738f8a4dfea4589572c663bd8
Copying blob sha256:246ba1b32462cea77206e04797df75780a0bdebd112b020b9bf11a7c6694eaa1
Copying blob sha256:dc3b3af10cf618c7b3038ca70bbcc422701fa0bf6cb9afae277406df7140445a
Copying config sha256:624cfe37262e44c78cd50ec7bc8a98e417be3b81bb215eed099bf7da343b1a63
Writing manifest to image destination
Storing signatures
STEP 2/14: ENV DEBIAN_FRONTEND=noninteractive
--> 1c3717268f9
STEP 3/14: ENV PYTHONUNBUFFERED=1
--> 94f1ecff3fe
STEP 4/14: ENV LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/x86_64-linux-gnu:/usr/local/nvidia/lib64:/usr/local/nvidia/bin
--> d2b5903033d
STEP 5/14: RUN rm -f /etc/apt/sources.list.d/cuda.list &&     rm -f /etc/apt/sources.list.d/nvidia-ml.list &&     apt-key del 7fa2af80
OK
--> f9d50c86fbb
STEP 6/14: ENV PATH="/root/.pyenv/shims:/root/.pyenv/bin:$PATH"
--> c3a91f44b23
STEP 7/14: RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends      make    build-essential         libssl-dev      zlib1g-dev      libbz2-dev      libreadline-dev         libsqlite3-dev  wget    curl    llvm    libncurses5-dev         libncursesw5-dev        xz-utils        tk-dev  libffi-dev      liblzma-dev     python-openssl  git     ca-certificates        && rm -rf /var/lib/apt/lists/*
E: Release file for http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease is not valid yet (invalid for another 14h 51min 11s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease is not valid yet (invalid for another 15h 52min 46s). Updates for this repository will not be applied.
E: Release file for http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease is not valid yet (invalid for another 14h 53min 59s). Updates for this repository will not be applied.
Error: building at STEP "RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends        make    build-essential         libssl-dev      zlib1g-dev      libbz2-dev      libreadline-dev         libsqlite3-dev  wget    curl    llvm    libncurses5-dev         libncursesw5-dev        xz-utils        tk-dev  libffi-dev      liblzma-dev     python-openssl git     ca-certificates         && rm -rf /var/lib/apt/lists/*": while running runtime: exit status 100

ⅹ Failed to build Docker image: exit status 100


Enter in Formatted Text fields causes Save

For example, on the General tab in Edit Event Type.
Reported by Blockus 10/7

Done 10/13/15


R base version isn't pinned in environments

I thought that R itself is pinned in the conda environments, but it is not. I guess whatever R version is installed on user's computers is what gets used. This will lead to problems if users have a newer R version that doesn't work well with our pinned older packages defined in the env yamls.

Hmmm but the R interpreter that gets used is determined by conda right? I'm pretty sure the version of r for example on the gh action runner wasn't changing

You're right, it's determined by conda and it must get downloaded into the snakemake-created environments as a dependency of one (probably more) of the r packages we have in the yaml. The R version in my base environment is 4.4.1, but the version in my persistant R-DOAF_reports environment (downloaded a few months ago) is 4.2.3. I just installed the environment again and it's still version 4.2.3 . So maybe this isn't an issue at all.

It might not be a bad idea to at least define the version, for reproducibility reasons though


Something has happened to Nightscout Authentication between mid November and early April that breaks this deployment

I had built my original autotune docker using a Nightscout build of the Master branch in November 15th 2020; following an update of the Master branch and re-deployment on April 8th 2021 - Autotune stopped working. Is there something in your build that needs changing - it tends to fail with this sort of failure
TypeError: opts.glucose.map is not a function
Stepping through the shell file manually made no difference

I will need to look in to this.
On Mon, 26 Apr 2021, 19:57 alternateal, @.***> wrote:

I had built my original autotune docker using a Nightscout build of the
Master branch in November 15th 2020; following an update of the Master
branch and re-deployment on April 8th 2021 - Autotune stopped working. Is
there something in your build that needs changing - it tends to fail with
this sort of failure
TypeError: opts.glucose.map is not a function
Stepping through the shell file manually made no difference
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joeyede/AutorunAutotune/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3WAZCXIGWF3FCOO6ETOP3TKWZS7ANCNFSM43TOXZBQ
.

I had built my original autotune docker using a Nightscout build of the Master branch in November 15th 2020; following an update of the Master branch and re-deployment on April 8th 2021 - Autotune stopped working. Is there something in your build that needs changing - it tends to fail with this sort of failure
TypeError: opts.glucose.map is not a function
Stepping through the shell file manually made no difference

@alternateal Did you resolve this issue?

Honestly not had a chance to sit down and look at it logically - I am still using an old build of Nightscout to make it work. I suspect it is something in the Nightscout authentication, but again not spent enough time looking.

Honestly not had a chance to sit down and look at it logically - I am still using an old build of Nightscout to make it work. I suspect it is something in the Nightscout authentication, but again not spent enough time looking.

What version of NS are you on?

I belive I found this issue.
At some point authentication using the apikey stoped working and you must use the sha1 hash of your apikey so for e.g. if you currently have in Dockerfile:
ENV API_SECRET IloveAutoAutotune
replace it with:
ENV API_SECRET 7499FB74EE6A4FB035AD0A45848335CCEFDB90B6
One way to get the sha1 has would be to use: https://passwordsgenerator.net/sha1-hash-generator/

tuned out this broke trigger profile which was expecting unhashed key.  Fixed script to hash it so you can continue to use unhashed key in Dockerfile if you update to lates version of these scripts


Fix homepage tile lazy loading when Finder is disabled

The Finder logic (including "blank slate" image lazy loading) is triggered on existence of the .js-campaign-finder div. We need lazy loading to run on existence of the blank slate div whether or not the Finder is enabled.
References #2251.

This was fixed a long time ago. Closing!


💬 [Question] Klicktipp Usage as part of the AGBs

💬 Question

We need to inform the user about our usage of the 3rd party association with Klicktipp and our datatransfere to that company(email, name etc), or is this already covered by our dataprotection/agbs?

Hi @clauspeterhuebner, @BerndHueckstaedt,
We would need a lawyer to writte an AGB or what should be the Prozess for this?

brexit?


[url_launcher]: The plugin url_launcher_android uses a deprecated version of the Android embedding

The plugin url_launcher_android uses a deprecated version of the Android embedding.

Steps to Reproduce

Update android studio and tools to latest.
Add and import url_launcher in your flutter application.
Try to build and run...

Expected results: Application should build and run
Actual results: Deprecation Note and exits
Complete Log
The plugin `url_launcher_android` uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.

Hi @New-dev0, Thanks for filing the issue. I am unable to reproduce those warning when depending on url_launcher  or url_launcher_android when running on Xiaomi k20 pro (Android 11)
Launching lib/main.dart on Redmi K20 Pro in debug mode...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Connecting to VM Service at ws://<IP_ADDRESS>:55257/P4wdNcAMXr4=/ws
I/.example.newap(11950): ProcessProfilingInfo new_methods=977 is saved saved_to_disk=1 resolve_classes_delay=8000

Please share the output of flutter doctor -v

flutter doctor -v (mac)
[✓] Flutter (Channel stable, 3.0.0, on macOS 12.3 21E230 darwin-arm, locale en-IN)
    • Flutter version 3.0.0 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ee4e09cce0 (6 days ago), 2022-05-09 16:45:18 -0700
    • Engine revision d1b9a6938a
    • Dart version 2.17.0
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-32, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! CocoaPods 1.10.2 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your
        plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.3 21E230 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Thanks for reply


Error rate fluctuation

Hello,
Sometimes, I notice that between trainings, it is possible to observe fluctuations in the results. Here is an example :
{ error: 0.004999279467972932, iterations: 6500 }
{ Win: 0.48747244477272034, Loss: 0.5125441551208496 }

{ error: 0.00499901753758613, iterations: 6348 }
{ Win: 0.4875994622707367, Loss: 0.5123955607414246 }

{ error: 0.004998189792153667, iterations: 8187 }
{ Win: 0.4831335246562958, Loss: 0.516595721244812 }

{ error: 0.07775032963693915, iterations: 20000 }
{ Win: 0.6663448214530945, Loss: 0.33365845680236816 }

It's the same data set. So, my question is : is it normal to have, sometimes, an error above the error threshold ?
Thank you for advice !

This is normal, and in fact one of the coolest things about machine learning.  What is happening is that brain is learning to compartmentalize or segregate a set of logic into a simpler subset, and when it does there is a large efficiency increase.
Picture like something in the real world, bubbles.  it like two bubble

Thank you for your response ! Because I have to do a professional presentation on neural networks, and I wasn't sure about how to present the thing.

Very cool, and let me know how it goes!  Also, if you have any more questions, feel free to ask.

Also feel free to include a link to your presentation.


Camera pressure - small object ignored

This PR is about camera pressure.
Now we are ignoring small objects that don't interfere with view.
Example is shown here:
https://user-images.githubusercontent.com/4487857/142434816-607f2eb8-25cc-4e52-8b28-85ec418b0237.mp4

Tree branches was intercepting rays from player to camera, and that was causing camera to jump in front of tree branch.
Now we are ignoring small objects that intercept rays so camera is more stable in its position.

This is the issue in question https://github.com/webaverse/app/issues/1814

1-The Camera View has improved a lot, but the transition of camera from far to near when an object gets in the way is not smooth and appears very fast and sometimes disruptive.(I will post the video tomorrow due to an issue.)
Else is fine, the ignoring of small objects has made the view much more detailed.

Looks fine to me. @amnaarshed4224 Please post the video for reference.

The camera view and transitions are working fine But there is one issue that needs to be addressed still
1-In congested places that are crowded with objects The camera view stirs. Kindly check it if it should be fixed i the current PR or a separate PR.
https://user-images.githubusercontent.com/35926530/143908722-b11e2716-ad2f-49c9-b13b-ada0c0d71f97.mp4

Last commit is about elimination of jitter when there is no camera movement.
https://user-images.githubusercontent.com/4487857/143954843-0cf74560-ecf2-42d9-be3d-cb491c10f188.mp4

The jitter is gone while there's no camera movement.
While passing through the back of objects it still stirs but I guess that is something that can be ignored for now
https://user-images.githubusercontent.com/35926530/144077711-24fcedb8-57d8-417d-b2ec-243d3259e93d.mp4
.


non blocking da v3: altdasend -> txsend pipeline

This version, as opposed to v2 (#6) which wraps eth tx submitter inside altda submitter, keeps the altda submitter and eth tx submitters as separate entities.
We thus get a pipeline mainloop -> altda submitter -> eth tx submitter

Closing as no longer needed. #7 is the approach we are currently going for.


Added open-cobol to linux builds

Description
New tool,
Added open-cobol to your linux hosts, both Ubuntu 16.04 and 18.04
For new tools, please provide total size and installation time.
~5 seconds, is very lightweight
Related issue:
Check list

[x] Related issue / work item is attached
[x] Tests are written (if applicable)
[x] Documentation is updated (if applicable)
[x] Changes are tested and related VM images are successfully generated

/azp run ubuntu1604, ubuntu1804

@LuisEnMarroquin, thank you for contribution!
Your changes look good and checks passed successfully. But we can't merge the pull-request right now.
We have an active incident with disk space on Ubuntu images so we have to wait a bit until it is resolved.

Hi @LuisEnMarroquin! As @maxim-lobanov mentioned we've been having disk space issues in the ubuntu environments so at this time we rather not add tools that are not essential for a large number of workflows. Thanks a lot for your contribution. I'll close the PR but we can reopen in the future if the situation changes.