[18-10-2022] Password Reset Feature

Summary

Fixes #42
Fixes the password reset functionality
List of changes proposed in this PR (pull-request)

Added New Schema Methods To Handle The Generation Of Reset Tokens
Created New Route For Forgot Password
Send Reset Token To User Email (I Used Mailtrap.io for testing)
Created New Route To Handle The Reset Of Password
Handle and Make Patch Request To The API To Update The Password.

What should a reviewer concentrate their feedback on?

Authentication Feature: Password Reset
Parent Issue : #5
Sub Issue: #42

@BatoolMM please merge

@BatoolMM please merge

Thanks, @RealRichi3
I was about to mention you.

You're welcome

Can you resolve conflicts, please?

@all-contributors please add @anslemkelechi for infra

https://github.com/all-contributors please add @RealRichi3 for review

@anslemkelechi
I'm trying to create the unit test for the password reset feature. I can only get the reset token from the message sent to my email. But i don't want to make calls to any gmail API to read the last email and get the reset token.
What i had in mind was to get the saved hash from the db and reverse the hash to get the reset token, then use it to run the test for the endpoint. But i don't know how to reverse the hash using the crypto module.
Is there a way to get the original resetToken by reversing the hash, if there is a way, how can i do it?
https://github.com/Open-Science-Community-Saudi-Arabia/MOOCs/blob/63b05b771baa60601650e74e9a8e91aa86bc34d0/backend_API/src/models/user.models.js#L90-L98

Hi @RealRichi3, sorry for the late response, you would not be able to reverse the hash, because it wasn't encrypted rather it was hashed, the only two solutions to this could be

We can use encryption instead of hashing you can use this link to see how it's done

We save the resettoken it self to the db.

@anslemkelechi thanks

I'm thinking of creating a separate collection to store the unhashed token, then use this collection strictly for tests


miniflux: 2.1.0 -> 2.1.1

Description of changes
Version 2.1.1 requires at least go 1.22 to build.
As such, this and future releases can no longer be backported to nixos-23.11.
https://github.com/miniflux/v2/releases/tag/2.1.1
diff: https://github.com/miniflux/v2/compare/2.1.0...2.1.1
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.


Provide additional color themes

It'd be nice to include at least an additional dark theme with markserv, just for the eye, and expose that via a command line switch.

I've already done this for my local version of MarkServ, @F1LT3R you accepting a PR for this?

@zeue - yes!

Apologies for the delay, PR is open here #100

eyes hurty!


[GLUTEN-5341] fix fail 3.5 ut of  VeloxParquetWriteSuite

What changes were proposed in this pull request?
fix test write parquet with compression codec ut of VeloxParquetWriteSuite
(Fixes: #5341)
How was this patch tested?
manually run
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@yma11 / @zhouyuan for help sign

CC @JkSelf

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_5463_time.csv
log/native_master_04_21_2024_b08258e51_time.csv
difference
percentage

q1
36.30
34.90
-1.401
96.14%

q2
23.90
24.06
0.160
100.67%

q3
37.80
36.70
-1.104
97.08%

q4
39.18
40.96
1.782
104.55%

q5
71.82
69.60
-2.222
96.91%

q6
7.01
7.44
0.436
106.22%

q7
83.42
85.59
2.167
102.60%

q8
85.81
85.37
-0.436
99.49%

q9
121.92
125.78
3.863
103.17%

q10
47.42
43.35
-4.067
91.42%

q11
20.77
19.84
-0.928
95.53%

q12
27.28
25.80
-1.476
94.59%

q13
55.81
54.10
-1.706
96.94%

q14
17.79
21.91
4.123
123.17%

q15
29.52
29.24
-0.277
99.06%

q16
14.54
14.28
-0.254
98.26%

q17
102.46
101.35
-1.112
98.91%

q18
141.93
145.10
3.163
102.23%

q19
15.68
13.61
-2.069
86.80%

q20
27.83
28.46
0.627
102.25%

q21
296.18
287.28
-8.901
96.99%

q22
16.20
14.78
-1.420
91.24%

total
1320.57
1309.52
-11.051
99.16%


Using cf create-service with v8 CLI does not consider current targeted space

Please fill out the issue checklist below and provide ALL the requested information.

[x] I reviewed open and closed github issues that may be related to my problem.
[x] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[x] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[x] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
Running the following command using v8 CLI:
cf create-service cloud-service-account space-deployer my-service-account

Results in the following failure:
Creating service instance my-service-account in org my-org / space dev as<EMAIL_ADDRESS>
Service offering 'cloud-service-account' is provided by multiple service brokers. Specify a broker name by using the '-b' flag.

FAILED

When specifying -b flag, the command still fails:
cf create-service cloud-service-account space-deployer my-service-account -b uaa-credentials-broker

Creating service instance my-service-account in org my-org / space dev as<EMAIL_ADDRESS>
Service offering 'cloud-service-account' is provided by multiple service brokers. Specify a broker name by using the '-b' flag.

FAILED

What happened
It appears that when the v8 CLI makes the call using v3 API it's not considering the current targeted space like the v7 client does with the v2 API queries. This causes the create-service command to fail.
When inspecting the underlying API calls, CF CLI v7 makes these requests:

/v2/spaces//services?q=label%3Acloud-service-account
/v2/service_plans?q=service_guid:

So notably it's using the V2 of the cloud controller API, not V3
When using CF CLI v8 to make this request to the CC API V3:

/v3/service_plans?names=space-deployer&page=1&per_page=50&service_offering_names=cloud-service-account

Which as a non-admin user is returning 3 results for the space-deployer plan, but CF CLI v7 is making this request to CC API V2:

/v2/service_plans?q=service_guid:

Which only shows one instance of the space-deployer plan
Expected behavior
When using either the v7 or v8 CLI, running create-service should consider the currently targeted space.
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

1 broker with 2 plans - both plans are org scoped and not in all orgs
User is in 2 or more orgs and v8cli using v3 queries returns dup results x the number of orgs the user is a member of where the plan is scoped
Adding a space_guids of the current targeted space results in a single result

Run cf create-service cloud-service-account space-deployer my-service-account
See error

Provide more context

Mac OS X Terminal Version 2.13
cf version 8.7.7+583a09a.2023-12-26
version of the CC API Release you are on

Possibly related: https://github.com/cloudfoundry/cli/issues/2269

This issue is fixed with https://github.com/cloudfoundry/cloud_controller_ng/pull/3648 which is part of CAPI 1.173.0.


fix: default wait

What does this PR do?
use defaultValue on Duration flags
What issues does this PR fix or reference?
https://salesforce-internal.slack.com/archives/G02K6C90RBJ/p1701888844122029
@W-14625639@
QA:
if you want to link the plugin or use bin/run, you need to run yarn oclif manfiest first to get the manifest, which is where you could see the problem before this fix

QA
🟢 wait flag shows expected value in help when manifest is present
🟢 wait flag shows expected value in help when manifest is not present


Tolino page support

Hi!
thank you for your work, I was able to boot the image on my tolino page. The adb access does work and I was able to root the device using "twrp install" on command line.
Unfortunately the touch display does not work as expected.  I got streaked screen and I have no idea how to solve it. The "page" does have resolution 600x800 only
# cat /sys/devices/platform/mxc_epdc_fb/graphics/fb0/modes
U:600x800p-46
U:800x600p-47

So I grab the sources and recompiled the image playing around with BoardConfig parameters, but without look. Any hint how I can try to get the screen working?
Do you need additional informations about the device to add the support "official" to this repo?

Hi.
Could you please post:

output from: cat /proc/partitions
output from: getprop

Also, when you booted recovery - picture on screen displayed correctly (except crop)  or it was garbled?

$ cat /proc/partitions
major minor  #blocks  name

 179        0    3872256 mmcblk0
 179        1       6112 mmcblk0p1
 179        2      32768 mmcblk0p2
 179        3          1 mmcblk0p3
 179        4    2212387 mmcblk0p4
 179        5     393208 mmcblk0p5
 179        6     393208 mmcblk0p6
 179        7     524280 mmcblk0p7
 179        8       8184 mmcblk0p8
 179        9       4088 mmcblk0p9
 179       10     262144 mmcblk0p10

$ getprop
[config.disable_bluetooth]: [true]
[config.disable_telephony]: [true]
[dalvik.vm.dexopt-flags]: [m=y]
[dalvik.vm.heapgrowthlimit]: [128m]
[dalvik.vm.heapmaxfree]: [48m]
[dalvik.vm.heapminfree]: [512k]
[dalvik.vm.heapsize]: [384m]
[dalvik.vm.heapstartsize]: [48m]
[dalvik.vm.heaptargetutilization]: [0.75]
[dalvik.vm.jniopts]: [warnonly]
[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]
[debug.egl.hw]: [0]
[debug.force_rtl]: [0]
[debug.sf.enable_hgl]: [1]
[debug.sf.showfps]: [0]
[dev.bootcomplete]: [1]
[dhcp.wlan0.dns1]: [<IP_ADDRESS>]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[dhcp.wlan0.domain]: []
[dhcp.wlan0.gateway]: [<IP_ADDRESS>]
[dhcp.wlan0.ipaddress]: [<IP_ADDRESS>]
[dhcp.wlan0.leasetime]: [86400]
[dhcp.wlan0.mask]: [<IP_ADDRESS>]
[dhcp.wlan0.mtu]: []
[dhcp.wlan0.pid]: [2693]
[dhcp.wlan0.reason]: [REBOOT]
[dhcp.wlan0.result]: [failed]
[dhcp.wlan0.server]: [<IP_ADDRESS>]
[dhcp.wlan0.vendorInfo]: []
[gsm.ril.delay]: [15]
[hw.CTM.dev]: [lm3630a_led]
[hw.backlight.dev]: [mxc_msp430_fl.0]
[hwc.enable_dither]: [1]
[hwc.stretch.filter]: [1]
[init.svc.adbd]: [running]
[init.svc.bootanim]: [stopped]
[init.svc.console]: [running]
[init.svc.debuggerd]: [running]
[init.svc.dhcpcd_wlan0]: [stopped]
[init.svc.drm]: [running]
[init.svc.flash_recovery]: [stopped]
[init.svc.healthd]: [running]
[init.svc.hide_folders]: [stopped]
[init.svc.hw_check]: [stopped]
[init.svc.installd]: [running]
[init.svc.keystore]: [running]
[init.svc.media]: [running]
[init.svc.netd]: [running]
[init.svc.p2p_supplicant]: [stopped]
[init.svc.servicemanager]: [running]
[init.svc.surfaceflinger]: [running]
[init.svc.ueventd]: [running]
[init.svc.upgrade_check]: [stopped]
[init.svc.vold]: [running]
[init.svc.watchdogd]: [running]
[init.svc.wifi_mac]: [stopped]
[init.svc.zygote]: [running]
[net.bt.name]: [Android]
[net.change]: [net.dns1]
[net.dns1]: [<IP_ADDRESS>]
[net.hostname]: [android-8dfe3120c5310744]
[net.qtaguid_enabled]: [1]
[net.tcp.buffersize.default]: [4096,87380,110208,4096,16384,110208]
[net.tcp.buffersize.wifi]: [524288,1048576,2097152,262144,524288,1048576]
[persist.sampling_profiler]: [1]
[persist.sys.country]: [DE]
[persist.sys.dalvik.vm.lib]: [libdvm.so]
[persist.sys.language]: [de]
[persist.sys.localevar]: []
[persist.sys.profiler_ms]: [0]
[persist.sys.strictmode.disable]: [1]
[persist.sys.strictmode.visual]: [0]
[persist.sys.timezone]: [Europe/Amsterdam]
[persist.sys.usb.config]: [mass_storage,adb]
[qemu.hw.mainkeys]: [0]
[ro.adb.secure]: [1]
[ro.allow.mock.location]: [0]
[ro.baseband]: [unknown]
[ro.board.platform]: [imx6]
[ro.boot.console]: [ttymxc0]
[ro.boot.hardware]: [E60QJ0]
[ro.boot.serialno]: [80041040,ec22696e94dd4735bd49a79031fdae6e]
[ro.bootloader]: [unknown]
[ro.bootmode]: [unknown]
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1529945274]
[ro.build.date]: [Mon Jun 25 18:47:54 CEST 2018]
[ro.build.description]: [ntx_6sl-user 4.4.2 KOT49H 89 ee3fb1835172d6184eb374e4ed33b903eae4dbf6,release-keys]
[ro.build.display.id]: [KOT49H.89.ee3fb18]
[ro.build.host]: [build03]
[ro.build.id]: [KOT49H]
[ro.build.product]: [ntx_6sl]
[ro.build.tags]: [ee3fb1835172d6184eb374e4ed33b903eae4dbf6,release-keys]
[ro.build.type]: [user]
[ro.build.user]: [jenkins]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [89]
[ro.build.version.release]: [4.4.2]
[ro.build.version.sdk]: [19]
[ro.carrier]: [unknown]
[ro.config.alarm_alert]: [Alarm_Classic.ogg]
[ro.config.low_ram]: [true]
[ro.config.notification_sound]: [OnTheHunt.ogg]
[ro.crypto.fuse_sdcard]: [true]
[ro.crypto.state]: [unencrypted]
[ro.debuggable]: [1]
[ro.factorytest]: [0]
[ro.hardware]: [E60QJ0]
[ro.hw.ctm]: [no]
[ro.hw.epd_resolution]: [800x600]
[ro.hw.epd_vcom]: [2070]
[ro.hw.epd_waveform]: [320_G120_AD1F01_ED060SCTT1_TC]
[ro.hw.frontlight]: [no]
[ro.hw.gyro_app_ver]: []
[ro.hw.gyro_loader_ver]: []
[ro.hw.pcb_name]: [E60QJ0]
[ro.hw.touch_id]: [----]
[ro.hw.touch_ver]: [----]
[ro.hw.wifi_drv_ver]: [<IP_ADDRESS> (r420671)]
[ro.hw.wifi_fw_ver]: [<IP_ADDRESS>.23]
[ro.lockscreen.disable.default]: [true]
[ro.product.board]: [EVK]
[ro.product.brand]: [RakutenKobo]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [ntx_6sl]
[ro.product.display]: [eink]
[ro.product.hardwareType]: [E60QJ0]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [Rakuten Kobo Inc.]
[ro.product.model]: [tolino]
[ro.product.name]: [ntx_6sl]
[ro.revision]: [393728]
[ro.ril.wake_lock_timeout]: [300]
[ro.runtime.firstboot]: [1533749512121]
[ro.secure]: [0]
[ro.serialno]: [80041040,ec22696e94dd4735bd49a79031fdae6e]
[ro.sf.hwrotation]: [270]
[ro.sf.lcd_density]: [167]
[ro.tether.denied]: [true]
[ro.wifi.channels]: []
[ro.zygote.disable_gl_preload]: [true]
[service.bootanim.exit]: [1]
[supolicy.loaded]: [1]
[sys.2step.sleep_reason]: [3]
[sys.boot_completed]: [1]
[sys.interactive]: [active]
[sys.settings_global_version]: [1]
[sys.settings_system_version]: [3]
[sys.sysctl.extra_free_kbytes]: [5625]
[sys.usb.config]: [mass_storage,adb]
[sys.usb.state]: [mass_storage,adb]
[system_init.startsurfaceflinger]: [0]
[tolino.wifi_timeout]: [180]
[vold.post_fs_data_done]: [1]
[wifi.ap.interface]: [wlan0]
[wifi.interface]: [wlan0]
[wlan.driver.status]: [unloaded]
[wlan.interface]: [wlan0]

The screen looks

Thank you.
Please try this recovery: https://1drv.ms/u/s!AlBgZahcgzeIkQCv9_N2E-6YdAFg

The build does work for me now, thank you!
I am able to start using fastboot boot twrp.img but the image does not start if flshed to recovery partiiton.
I tried fastboot flash recovery twrp.img and dd if=/tmp/twrp.img of=/dev/block/mmcblk0p2 both with the same result: The device does power off after ~8 seconds without booting twrp :-(
Any further idea? The previous build I tested without flashing only too. I was able to start "original recovery" before so I know the key grip

By the way, you tried to boot with your book connected to pc?
As far as I see it won't boot into twrp while book is not connected to pc.

You are right.
Connected to PC and restarted using "Simple reboot" => TWRP started,
Restarted again from TWRP => TWRP started
Disconnected and restarted from TWRP => is hanging in TWRP splash image
So I this issue can be closed, since Page is supported more or less same way as other devices ;-)


Avatar equip does not set avatar

It only sets it locally -- it should also write it to the chain.

Should be set on the chain now.


update http gem to 3.0+

Only breaking change is drop of support for ruby 2.0 and 2.1 which we don't care. Fixes #320
twitter gem already moved to http 3.0 and this will help in debian packaging. We prefer to maintain only a single version of http.

Tests for ruby 2.2 passed, but failed for 2.3, 24 and 2.5 :(

possibly related: https://github.com/vcr/vcr/issues/695 (similar error, with http gem).

also sounds like this was supposed to be fixed in http 3.2.1 by https://github.com/httprb/http/pull/468?
however Travis failed with "Installing http 3.3.0".

Close-cycling to rerun Travis in vague hope failures would go away (?) :)
It does pass locally on 2.4.1.

Whoah, this is sporadic, depends on test order!
env TESTOPTS='--seed=10834' bundle exec rake fails.
env TESTOPTS='--seed=56466' bundle exec rake passes.
(at your commit 33fcfefa.  travis runs would-be-merge-to-master, which has new test cases so seeds may differ)

Can you also relax webmock to '~> 3.0'?  With latest Webmock 3.4.2 seems to fix sporadic errors (though it'd be great to debug why exactly those were happening)

@cben relaxed webmock as well and now tests are passing.

Thanks!  Have you by chance done any real-life testing of watching with http 3?
[P.S. My response speed is not good lately.  And Mooli switched to a new job and like won't have time for kubeclient.  I'd be happy if anyone wants to join as maintainer.]

Tested watching manually, seems fine.  Merging.
(Should we also allow http 2.y?  3.y exists for over a year, so I feel OK dropping 2.y — if someone needs it let us know, it's not impossible)


.createServerImage() errors with "Invalid format (output) missing from remote call"

When issuing a .createServerImage() command, the response returns the following error in the callback:
{ Error: Invalid format (output) missing from remote call
    at _getRequestError (/home/test/node_modules/openstack-wrapper/lib/os-request.js:219:20)
    at Request._callback (/home/test/node_modules/openstack-wrapper/lib/os-request.js:316:15)
    at Request.self.callback (/home/test/node_modules/request/request.js:186:22)
    at Request.emit (events.js:182:13)
    at Request.<anonymous> (/home/test/node_modules/request/request.js:1163:10)
    at Request.emit (events.js:182:13)
    at IncomingMessage.<anonymous> (/home/test/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:273:13)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1086:12)
  code: 'REMOTEERROR',
  detail:
   { remoteMethod: 'POST',
     remoteURI: '~~~remoteURI~~~',
     remoteStatusCode: 202,
     remoteMessage: '',
     remoteCode: '',
     remoteDetail: '',
     responseTime: 0.975 } }

The issued command looks something like this:
    await  nova.createServerImage(serverId, {
        "name" :   `image ${dateformat(new Date(), "dd/mm/yyyy HH:MM")}`,
        "metadata": {
            "test_var": "test_val"
        }
    }, (error, result) => {
        if (error) {
            console.log(error); // will output the earlier error
        }
        console.log(result);  // will be undefined
    });

even though the image is created fine, also seen by the remoteStatusCode 202.
I want to know if this is a problem with the cloud provider (OVH) because there is no body in their response.

Sorry for the slow response here - your provider (OVH) is probably doing this the right way.  Nova has simply changed the output format recently and the library wasn't supporting the older format.
Just published a new version (2.2.0) that should support both new and old formats on that call and should fix your issue.
You can see more info about the problem here if you are interested:
https://developer.openstack.org/api-ref/compute/?expanded=create-image-createimage-action-detail#create-image-createimage-action


in-place transformation for refmt

Some switch that allows the transformation of a file in-place, since cat foo.re | refmt ... > foo.re doesn't work because of how unix pipes work.

A workaround for now could be something like echo "$(cat foo.re | refmt ...)" > foo.re or even echo "$(refmt ... foo.re)" > foo.re.

@tekknolagi The workaround should work. In the meantime I think we should still have a -in-place option (or -i). Are you still working on this?

@yunxing Yep!

Would it make more sense to add --output/-o and have --in-place be a special case of that?

@tekknolagi Looks like the best solution so far given that "-i" is taken for "--intf"


EXP-2337 add getCurrent ( Device, Location, Experience, Zone), update…

… readme file

should we ok now 👍

:+1:


Issue 2388: Added TSVConnArgs support

Based on previous PR: https://github.com/apache/trafficserver/pull/2783 and discussions in Issue: https://github.com/apache/trafficserver/issues/2388
Added VConn args support
Changed TS_VCONN_PRE_ACCEPT to TS_VCONN_START
Added TS_VCONN_CLOSE hooks
Fixed docs for TS_VCONN_PRE_ACCEPT renaming to TS_VCONN_START and added docs for TSVconnArgs
Added an example plugin vconn_args to test

[approve ci]
[approve ci docs]

[approve ci]
[add to whitelist]

[approve ci]
[add to whitelist]

[approve ci ubuntu]

[approve ci autest]


feat(app)  desktop: robot update flow rework

closes RAUT-501 and RQA-1430

Overview

This PR adds desktop robot update flows in line with the new designs found here.
Note: The markdown does not match the proposed format. This discussion is in the ticket. It will be implemented at a later time.

Test Plan

Verified installation progress via Zip file upload to physical ODD.
Verified download/install flow.

Changelog

Refactored existing desktop update flows
Fixed a couple unrelated test failures
Added new translation text.

Risk assessment

medium

Just to update - all parts of the flow have been tested. They work as intended, but I'll monitor closely when this hits QA.

Left some comments but the changes look good to me! 🆙

Thank you for looking at this!


FFI build/runtime issues

FYI @johnmccutchan

Encountered this over the weekend. This error occurs at runtime while creating a rigid body:

[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Unsupported operation: The body is inlined in the frontend.
#0      DynamicLibraryExtension.lookupFunction (dart:ffi-patch/ffi_dynamic_library_patch.dart:67:7)
#1      new Body._ (package:cabal/physics/src/body.dart:76:46)
#2      new RigidBody._ (package:cabal/physics/src/body.dart:185:15)
#3      World.createRigidBody (package:cabal/physics/src/world.dart:52:22)
#4      CabalGame.startECS (package:cabal/game/cabal_game.dart:140:36)
#5      ECSGame.start (package:cabal/base/ecs_game.dart:39:5)
#6      GameRenderBox.attach.<anonymous closure> (package:cabal/base/game_render_box.dart:45:12)
#7      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:847:45)
#8      Future._propagateToListeners (dart:async/future_impl.dart:876:13)
#9      Future._completeWithValue (dart:async/future_impl.dart:652:5)
#10     Future._asyncCompleteWithValue.<anonymous closure> (dart:async/future_impl.dart:722:7)
#11     _microtaskLoop (dart:async/schedule_microtask.dart:40:21)
#12     _startMicrotaskLoop (dart:async/schedule_microtask.dart:49:5)

Also, around half the the time when I try to run cabal, the following error happens. However, rerunning always clears it up:

flutter run --debug --local-engine-src-path ~/projects/flutter/engine/src --local-engine=host_debug_unopt_arm64 --local-engine-host=host_debug_unopt_arm64 -d macos --enable-impeller
Launching lib/main.dart on macOS in debug mode...
lib/physics/src/body.dart:76:46: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  final unwrappedPositionSetter = jolt.dylib.lookupFunction<
                                             ^
lib/physics/src/body.dart:85:53: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedPositionGetter = jolt.dylib.lookupFunction<
                                                    ^
lib/physics/src/body.dart:96:53: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedRotationSetter = jolt.dylib.lookupFunction<
                                                    ^
lib/physics/src/body.dart:105:53: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedRotationGetter = jolt.dylib.lookupFunction<
                                                    ^
lib/physics/src/body.dart:116:59: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedWorldTransformGetter = jolt.dylib.lookupFunction<
                                                          ^
lib/physics/src/body.dart:127:66: Error: Expected type 'void Function(Pointer<WorldBody>, Float32List)' to be 'void Function(Pointer<WorldBody>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<WorldBody>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'WorldBody' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrapperCenterOfMassTransformGetter = jolt.dylib.lookupFunction<
                                                                 ^
lib/physics/src/shape.dart:22:54: Error: Expected type 'void Function(Pointer<CollisionShape>, Float32List)' to be 'void Function(Pointer<CollisionShape>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<CollisionShape>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'CollisionShape' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedGetCenterOfMass = jolt.dylib.lookupFunction<
                                                     ^
lib/physics/src/shape.dart:34:53: Error: Expected type 'void Function(Pointer<CollisionShape>, Float32List, Float32List)' to be 'void Function(Pointer<CollisionShape>, Pointer<Float>, Pointer<Float>)', which is the Dart type corresponding to 'NativeFunction<Void Function(Pointer<CollisionShape>, Pointer<Float>, Pointer<Float>)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'CollisionShape' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Void' is from 'dart:ffi'.
  static final unwrappedGetLocalBounds = jolt.dylib.lookupFunction<
                                                    ^
lib/physics/src/shape.dart:180:56: Error: Expected type 'Pointer<CollisionShape> Function(Pointer<ConvexShapeConfig>, Float32List, int)' to be 'Pointer<CollisionShape> Function(Pointer<ConvexShapeConfig>, Pointer<Float>, int)', which is the Dart type corresponding to 'NativeFunction<Pointer<CollisionShape> Function(Pointer<ConvexShapeConfig>, Pointer<Float>, Int)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'CollisionShape' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'ConvexShapeConfig' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Int' is from 'dart:ffi'.
  static final unwrappedCreateConvexShape = jolt.dylib.lookupFunction<
                                                       ^
lib/physics/src/shape.dart:269:54: Error: Expected type 'Pointer<CollisionShape> Function(Float32List, int, Uint32List, int)' to be 'Pointer<CollisionShape> Function(Pointer<Float>, int, Pointer<Uint32>, int)', which is the Dart type corresponding to 'NativeFunction<Pointer<CollisionShape> Function(Pointer<Float>, Int, Pointer<Uint32>, Int)>'.
 - 'Pointer' is from 'dart:ffi'.
 - 'CollisionShape' is from 'package:cabal/physics/src/jolt_ffi_generated.dart' ('lib/physics/src/jolt_ffi_generated.dart').
 - 'Float32List' is from 'dart:typed_data'.
 - 'Uint32List' is from 'dart:typed_data'.
 - 'Float' is from 'dart:ffi'.
 - 'Uint32' is from 'dart:ffi'.
 - 'NativeFunction' is from 'dart:ffi'.
 - 'Int' is from 'dart:ffi'.
  static final unwrappedCreateMeshShape = jolt.dylib.lookupFunction<
                                                     ^
Target kernel_snapshot failed: Exception

Command PhaseScriptExecution failed with a nonzero exit code
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **

Building macOS application...
Error: Build process failed

Okay, so I blew out everything and re-setup Cabal against engine ToT. Problem 2 seems to have gone away, but I'm still encountering problem 1.

Ah nvm, it turns out problem 2 is still afoot, the tool is just silently crashing right after launching the app, but --verbose reveals the errors.

FYI @dcharkes -- would you happen to know why the DynamicLibrary.lookupFunction extension no longer accepts mapping Float32List to ffi.Pointer<ffi.Float>?
Here's an example of the invocation:
  final unwrappedPositionSetter = jolt.dylib.lookupFunction<
      ffi.Void Function(ffi.Pointer<jolt.WorldBody>, ffi.Pointer<ffi.Float>),
      void Function(ffi.Pointer<jolt.WorldBody>,
          Float32List)>('body_set_position', isLeaf: true);

We realized that there were some issues with the way we introduced the API, so we reverted the API in https://dart-review.googlesource.com/c/sdk/+/349340. We're working on relanding it with a new API https://github.com/dart-lang/sdk/issues/44589.

What API guarantees does dart:ffi provide?

What API guarantees does dart:ffi provide?

APIs that made it into Dart stable that are not marked experimental are unlikely to be broken. (To my knowledge this API never was available in Dart stable, only in dev/beta releases. We cherry picked the revert to the stable release to prevent releasing an API that we realized had problems.)

The API was available for months and we were big users of it.

That is rather unfortunate.
I'm not sure how it was available for months for you? It landed December 12 (https://dart-review.googlesource.com/c/sdk/+/338620) and was reverted January 31 (https://dart-review.googlesource.com/c/sdk/+/349340). I'm a bit confused as how this project would have been able to use it after January 31st on tip of tree, or how it would have been using it on stable? Why did it only break now? Or did we somehow release a stable version with this API?

This has completely broken our project and it makes me worried about being broken again in the future.

I can understand that, that's why we have a breaking change policy.

Where are these breaking changes communicated?

Breaking changes to stable releases are communicated as per the Dart breaking change policy.
Breaking changes to dev/beta release are not.
Is this project running on tip of tree always? For that we don't have a good process I think, we generally don't promise anything tip of tree.

When is the replacement API going to be available?

I have a WIP, I can take a look next week to land it.
I believe for now the workaround would be to copy the data into C memory before an FFI call and free it immediately after. (Of course this costs performance, which is why we want to support this feature in the first place.)
Once again, I'm sorry for the inconvenience.
(And I'm confused as of why the problem surfaced in March on tip of tree instead of January 31st. Any insights here?)

Breaking changes to stable releases are communicated as per the Dart breaking change policy.

Breaking changes to dev/beta release are not.

This policy for beta releases seems hostile to our developers. If we think something is good enough to be in a beta release a developer should feel confident that they can use it and that if we take it away before the official release we will provide guidance. Ideally we do not remove APIs that were released in betas though.

Is this project running on tip of tree always? For that we don't have a good process I think, we generally don't promise anything tip of tree.

Given the timeline, I think we adopted this API right away. But, then, we stopped working on the project in February to focus on other things. We recently started working on this again and noticed all these strange breakages.
We now have a bunch of "churn" work to do to make our project functional and performance will be worse because we will be unnecessarily allocating/freeing all the time.

I have a WIP, I can take a look next week to land it.

This is great to hear but it doesn't give me confidence that porting cabal to this freshly landed API will be safe in the future. What guarantees are we getting? I do not want to have to rip out a bunch of code again in a month.

Thanks for the clarification @dcharkes!

I believe for now the workaround would be to copy the data into C memory before an FFI call and free it immediately after

Yeah, this is how I ended up working around it in the meantime.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis.


Edward Chong Lee

What is the current behavior?

What changes are you suggesting?

Additional information

Hey there @deltachonglee81!
Thanks for opening an issue. Could you please fill out the issue template so the team can know what the problem is?

Please note that I am not affiliated with the GitHub docs team.


feat!: language service plugin

BREAKING CHANGE: Utilize TypeScript LSP instead of ts-morph

@LukeAbby Referenced your PR, as well as the codebase of TypeScript Explorer to get to this release candidate. I would love your feedback if you have any 🙏


feature(*): change ticket content from calling object

Makes it possible to change the content of the ticket (subject & body) from the object calling the popup.
Example:
OtrsPopupService.changeTicket({
    subject: "The subject",
    body: "The body"
});

@Apollidore Could you please resolve conflict? Re-run a make build.

@antleblanc this is fixed

@FredericEspiau This pull request has now some conflicts.


Revise ws build warning/error messages

Right now, one can easily get confused with the following:
> C:\testing\wsclientside>dotnet ws build
Cache file for downloaded nuget packages is not found. Try the following:

- Add WebSharper.FSharp nuget to the current project (for example "> dotnet add package WebSharper.FSharp")
- Build prior running "dotnet ws build". Build will run in a moment.

This is confusing, because in reality if we don't find the NuGet cache file we just start msbuild, which immediately calls into the Booster if it's running already. I guess we could just leave a comment about this, something like:
Cache file for downloaded nuget packages is not found. Starting an msbuild now.

This could help the user remember that the project is compiled fresh with no obj folder yet, so either on a first run or after a clean.

Last I checked, the code still had the above error message.


Fix bug with new members subscription DS Master Campaign on MobileCommons

What's this PR do?

Fixes nasty bug with new members subscription DS Master Campaign on MobileCommons

How should this be reviewed?

Go to https://www.dosomething.org/user/register
Use phone number not registered with us
Search for this number on https://secure.mcommons.com/profiles
Ensure this number is subscribed to "Do Something Master Campaign"

Relevant tickets
Fixes #7000
cc @angaither

✔


Requirements for CONTRIBUTING.md

This issue will be used to track the ideas for what we should require from pull requests/issues. Current ideas include:

Restrict to Unity 5.5 and above
Stick to our issue template and a C# code style

Do you have a code style manual?.
The style of the variable names, function names, design patterns to use, etc.
Perhaps is a good idea to create one and accept only the pull request that use this guide.

I've made a change to the PokemonDatabase class to optimize a lot the access to it.
How could I make a pull request for that change?

@joseka1234 answer @superusercode, he will help you ^^

Thank you @cataclys but, how can I ask him?
I'm a bit useless using the GitHub web.

pm him on Discord superusercode#3623

Thanks!

@joseka1234 We have no code style guide at the moment, but I usually go back and lint the code after a pull request goes through.

I see there's some documentation written for users of the framework, but none for the developpers (i.e. internal functioning, class diagrams and relations...).
Is there any document hanging around that I haven't seen that describes a general picture of how all the scripts work with each other or something? Just to grab the big picture of the framework and get a hold of it, to make it easier (and faster) to start developing for it.

Here is a screen shot in my game page.
On Fri, Jul 26, 2019, 1:14 AM GMR<EMAIL_ADDRESS>wrote:

Closed #10 https://github.com/PokemonUnity/PokemonUnity/issues/10.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PokemonUnity/PokemonUnity/issues/10?email_source=notifications&email_token=AFFQYHG2DOMQ2QTLASXRVKLQBKP6BA5CNFSM4DBXW4S2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSW2TPEI#event-2511681425,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFFQYHCKUYKTKBUHAOPJWB3QBKP6BANCNFSM4DBXW4SQ
.


Is it possible for kube prod to dump the YAML it has generated?

I would like to apply the various components selectively or with modifications of my own.

You can tweak the file kubeprod-manifest.jsonnet to include or mute all stuff wanted. See https://github.com/bitnami/kube-prod-runtime/blob/master/docs/components.md
It's also possible to dump raw manifest. Take a look at:
$ kubeprod  install {cloud-provider}  --only-generate

But personally I would recommend:
$ kubecfg  -J ./lib show /path/to/kubeprod-manifest.jsonnet

What jbianquetti said :)
BKPR is designed to be highly customisable, by adding your desired modifications to kubeprod-manifest.jsonnet.
See https://github.com/bitnami/kube-prod-runtime/issues/320#issuecomment-459228512 for an example of the sorts of things you can do.  If you are new to jsonnet, I recommend you skim over the short/easy tutorial before diving in.
Also as recommended above, I suggest using kubecfg rather than running the kubeprod install command repeatedly.  The latter will work, but kubecfg offers additional features to help you debug the jsonnet you are developing (like kubecfg show, kubecfg diff, etc).
Please reopen if you have further questions.


My first feature branch

Add index.html

Add styles
Edit README file.

Good day.
I noticed my projects are showing no project submitted.
Please help rectify it to show I did a project.
On Thu, Sep 22, 2022, 11:13 PM Mamadou Abdoulaye Livouwane Diallo <
@.***> wrote:

@.**** approved this pull request.
STATUS: APPROVED 🟢 Hi @Eugeneiyukhun https://github.com/Eugeneiyukhun ,
[image: Congratulations!GIF]
https://user-images.githubusercontent.com/55918904/191301390-43d62dfa-bfdc-49c5-943b-4d72f4ea5bb8.gif
Your project is complete! There is nothing else to say other than... it's
time to merge it [image: :shipit:]
Congratulations! 🎉
(Highlights) Good Points: 👍

You documented your work professionally. ✔
GitHub flow is used correctly. ✔
All linters checks are ok. ✔

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this
PR. However, I strongly recommend you to take them into account as they can
make your code better. Some of them were simply missed by the previous
reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification.
As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have a
limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form https://airtable.com/shrQAqnBwek5a0O0s.
—
Reply to this email directly, view it on GitHub
https://github.com/Eugeneiyukhun/Hello-Microverse/pull/1#pullrequestreview-1117739969,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZOZO62364VQUWZM3TLFZQDV7TKZLANCNFSM6AAAAAAQSEG2FQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Error Handling and Multiple Search Terms for /tasks Endpoint

Description:
We have identified an issue with the "/tasks" endpoint, specifically when users provide an incorrect assignee that does not exist in the database. Additionally, we need to enhance this endpoint to support multiple search terms, such as "assignee," to provide more flexible querying of tasks.
Issue Details:
1. Incorrect Assignee Handling:

Route: https://api.realdevsquad.com/tasks?status=IN_PROGRESS&dev=true&assignee=sunny-s
Issue: When the provided assignee does not exist in the database, the endpoint should handle this case gracefully.
Desired Behavior: Instead of returning an error, the endpoint should return a response indicating that no tasks were found for the given assignee, similar to how the "/tasks" route behaves.

2. Supporting Multiple Assignees:

Route: https://api.realdevsquad.com/tasks?status=IN_PROGRESS&dev=true&assignees=sunny-s,john-d
Requirement: Enhance the "/tasks" endpoint to support multiple assignees in the query parameters.
Desired Behavior: When multiple assignees are provided, return the tasks assigned to any of the specified assignees. Ensure that the endpoint can handle multiple comma-separated assignee values.

Proposed Solutions:
1. Incorrect Assignee Handling:

Modify the "/tasks" endpoint to check if the provided assignee exists in the database.
If the assignee exists, return the tasks assigned to that user as usual.
If the assignee does not exist, return a response stating, "No tasks found for the given assignee."

2. Supporting Multiple Assignees:

Enhance the "/tasks" endpoint to parse and handle multiple assignee values when provided as comma-separated values in the query parameters.
Return the tasks assigned to any of the specified assignees.

Additionally, please ensure that appropriate error handling is in place to handle any other potential issues that may arise during the execution of this endpoint.

I will do this task.
ETA: 14th September

Hey is this issue still un-assigned?
Would love to work on it.
ETA:  18th September
As this is my first issue my ETA may vary.


FINERACT-1101 Swagger Codegen build using Gradle

Description
This PR addresses FINERACT-1101 issue. Following were the problems earlier:

Library generated by ./gradlew generateSwaggerCode was required to be build using mvn package only. If a user executed ./gradlew build, the build used to fail saying Could not determine java version from '11.0.8'. The issue was with the gradle-wrapper of the project. This is resolved by adding the Mustache Template for the gradle-wrapper.properties file.

Moreover, mvn package also failed due to an error in maven-javadoc-plugin. It was using the version 2.10.4 and was failing because of that. Version 3.2.0 worked correctly. This is resolved by adding the Mustache template for the pom.xml file

To be able to use Mustache Templates, we needed swagger-codegen-cli version 3.0.21. But if we used version 3.0.21 to generate swagger code, it would fail throwing an error Missing OpenAPI File. This was because the generated OpenAPI file was invalid. This was preventing to use the Mustache Templates. This is resolved in this PR.

Updated the client.md file with necessary documentation
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[x] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[x] API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm has been updated with details of any API changes.

[x] Integration tests have been created/updated for verifying the changes made.

[x] All Integrations tests are passing with the new commits.

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

An Apache RAT test is failing. Make sure you run this branch on your local machine and all builds and tests are passing. https://travis-ci.org/github/apache/fineract/builds/720575703

Hi @awasum  I checked the error. It is saying
Unapproved Licenses:
fineract-provider/config/swagger/templates/gradle-wrapper.properties.mustache
fineract-provider/config/swagger/templates/pom.mustache

Can you help me resolve this?

Ignore the file from rat checks as seen in the build.gradle file.

@awasum Thanks for the solution. It worked! I'll update the PR.


Invalid config searchCadence must be at least 1 day

Have you checked for any existing open/closed tickets that are the same or similar to your issue?

[X] I've searched far and wide!

I have gone to the Discord server for support and/or acknowledge that this is a bug and not a support issue

[X] I've tried to solve this already

What's happening surrounding the bug? (context)
I upgraded to v6.0.0-24 from v6.0.0-10 and my config is now showing as invalid.
According to the docs

There is a minimum of 1 day unless excludeRecentSearch has been set.
https://www.cross-seed.org/docs/basics/options#searchcadence

However I have have excludeRecentSearch: "30d" but it's still showing an error:
2024-07-19 20:32:15 error: Option: searchCadence
				searchCadence must be at least 1 day.
				(https://www.cross-seed.org/docs/basics/options#searchcadence)

"https://www.cross-seed.org/docs/basics/options#searchcadence"
Reproducing the bug
excludeRecentSearch: "30d",
searchCadence: "6h"

What should be happening?
Config should be accepted.
Feel free to show a warning if you consider it not an ideal setup but it's a misuse of error as it's a valid use case.
Your setup
- OS: Ubuntu
- Prowlarr/Jackett: N/A
- Docker: Yes
- Misc:

config.js (REDACT SENSITIVE INFORMATION)
excludeRecentSearch: "30d",
searchCadence: "6h"

verbose logs
cross-seed  | 2024-07-19 21:13:28 info: cross-seed v6.0.0-24
cross-seed  | 2024-07-19 21:13:28 info: Validating your configuration...
cross-seed  | 2024-07-19 21:13:28 warn: includeSingleEpisodes is not recommended when using rss or announce, please read: https://www.cross-seed.org/docs/v6-migration#updated-includesingleepisodes-behavior
cross-seed  | 2024-07-19 21:13:29 error: Option: searchCadence
cross-seed  | 				searchCadence must be at least 1 day.
cross-seed  | 				(https://www.cross-seed.org/docs/basics/options#searchcadence)
cross-seed  |
cross-seed  | 2024-07-19 21:13:29 error: Configuration:
cross-seed  | 				excludeOlder and excludeRecentSearch must be defined for searching. excludeOlder must be 2-5x excludeRecentSearch.
cross-seed  | 				(https://www.cross-seed.org/docs/basics/options)
cross-seed  |
cross-seed  | 2024-07-19 21:13:29 error: Your configuration is invalid, please see the errors above for details.
cross-seed exited with code 1

Failure or refusal to provide the information we require to address bugs will result in potential closure of the issue.

[X] I acknowledge that i have searched existing issues, read the documentation and faq, read the logs to see if the answer was provided in error messaging, and attempted to get support via the Discord prior to submitting this issue.

So you came to the discord, and read the docs? You acknowledged that you did this, yet I don't see you having asked anything there.
Read the note in the doc's for the migration guide.
https://www.cross-seed.org/docs/v6-migration#stricter-configjs-validation

Why do you need 6h instead of 1d?

For pre-release of v6, the regular docs are not the primary source. The entire page for v6 migration is.

We ask this for a reason, please do not ignore this in the future and check this box if you have not done this.

If you have some valid use case for 6h, feel free to let us know and we may consider it, as the note on the documentation suggests you do.

If you encounter problems with these restrictions which you feel are invalid, please reach out to us on Discord to discuss this further.

Otherwise, you will need to adjust your workflow and configuration.

We try to keep issues to actual bugs and feature requests and the like, breaking changes are to be expected with pre-release process, however what we are asking is more or less what necessitates such an aggressive and frequent searchCadence.
The reason I ask is because we can't always consider every single setup, but in almost every case what has ended up happening is that the user can achieve the same or better manner with a more reasonable configuration.
Feel free to have a conversation with us here, if you'd like. This was introduced in -24 - so you don't have to strictly stick to -10, -23 would work, and there are a variety of other features you'd be missing out on going to -10.
Are you not using rssCadence or anything?

What is your goal here? How do you still see this as a "validation error"?
You have not given a reason why you need 6h. We actually discussed this as the minimum before release but couldn't find any benefits over 1d. But you seem to have a very strong one enough to ignore critical updates?

I know it's considered a pre-release version but I'm confident in its stability, therefore I don't anticipate there being any critical updates.

There have been a dozen releases since -11, we aren't just making random releases for no reason - just so you know.

My interpretation of the question was it was an or statement:

A deliberate error stating that there is a problem that explicitly stated requirements for configuration have changed and, honestly, that is kind of a stretch to really be deemed a bug. We made a conscious decision, hence the error stating as much.

I'm then informed that the documentation I referred to isn't relevant and instead I should have full knowledge of the 3500 word article on migrating to v6.

Yes, the v6 migration guide is the relevant v6 documentation. It is not "released" - and therefore the remainder of the documentation is not updated in its entirety to reflect all the changes yet. Most of our userbase is still on v5.

I'm then informed that this isn't a bug, that I should have known this wasn't a bug and therefore it's a support request which should have been filed on discord.

Deliberate messaging and errors are all consistently showing that this was a conscious decision, as I stated before.
I've updated the issue template.
You could have also put support requests in "Discussions" in Q&A if you wanted. It's not a bug. It's a development decision you did not like, and while I understand your desire to "do what you want" - we are also making decisions to do what we think is best overall. If you intend to try and convince us that your preference is valid and "better" for you, we want to know why. Since you refused to give context for why you need those settings, it was kind of a non-starter.

I'm again informed I should have gone to Discord. Or I should just accept that decisions the maintainers have made, adapt my setup to follow their and not dare question it. [slightly overdramatised but that was my interpretation at the time]

Jesus.

The question "I have gone to the Discord server for support and/or acknowledge that this is a bug and not a support issue" should be rewritten or removed. When creating an issue I already identified I considered this a bug, so this check box is unnecessary.

It's been rewritten, but the ability for you to "interpret" things you don't agree with as a bug when it's pretty clearly a decision - that's not something that language can fix.

Consider redirecting users for support to GitHub discussions https://github.com/cross-seed/cross-seed/discussions in addition to Discord. This is very much personal opinion but I don't find Discord productive, whereas GitHub discussion seems to be setup for this exact use case (separating bug reports from support).

Already done, as I said.

Since you seem to have an issue with me, I'll bow out and you can continue this conversation without me.

I don't really follow why I need to justify how I use open source software on my own machine, connecting to my own accounts?

Of course you are free to pin versions or fork and make changes, that's perfectly acceptable. We would just prefer hearing the reasons first so we can decide if we will address it. We only restrict users when there is no value to gain by deviating while possible causing harm.

I'm confident in its stability, therefore I don't anticipate there being any critical updates

I'm not saying there could be a critical update, I'm saying that v6.0.0-24 is. The new caching behavior is one of the biggest improvements of v6. I was simply confused how you had such a strong reason skip it yet refused to state it.

What is wrong with having a searchCadence of 6h instead of 24h?

When searches are started, it can be very intensive on your disk, even if nothing will be searched. This is because it needs to index everything and perform tons of checks and validation on every torrent file or data file. So we limit to 1d to minimize this small but unnecessary added stress on your drives. It also creates tons of logging which makes the log files extremely bloated.
All this could be ignored if there was value to going less than 1d, which brings me to:

I have quite a few trackers configured and they aren't all particularly reliable so often connections fail. By running the search four times per day it means a search that failed to connect earlier is re-run

Search is not for getting cross seeds as fast as possible, that is for rss/announce/webhook which is far less strenuous on your system and trackers. This is a temporary problem you are having, everything will get searched eventually. Long term 1d will be sufficient which is what it's designed for.

I really don't follow how excludeRecentSearch and excludeOlder are linked at all? How can age have a MAX value?! Why is excludeOlder required at all?

This is so that searches are only performed a set number of times, a maximum of 6x. In reality, searches only need to happen once for the lifetime of cross-seed, rss/announce will catch all future releases. RSS pagination will be added soon so cross-seed downtime will not miss any releases.

I'm using cross-seed because I want to cross seed as much as possible, I don't follow why you'd only want to cross-seed new content?

This is exactly why these restrictions were added. You do not fully grasp how the entire application functions together and are likely to have harmful configurations. As I said earlier, we would have not restricted it if it brought any value. Of course we would make changes though if a user brought valid use case we haven't considered.

The complexity of the constraint is a strong sign it's too complex

These constraints ensures this only happens in daemon mode, this "complexity" gives you flexibility. You can bypass these restrictions as the PR says.
I also disagree with your assessment of the responses, they were appropriate as zakary noted above.

It's understandable that you interpreted this as a bug. When the program and the documentation it links to don't agree, something has a bug. In this case, v6 is on prerelease, so these links aren't accurate any more. We could consider versioned documentation, but I'd also like to get us out of prerelease soon. (We've been on prerelease for longer than I anticipated, which has made this problem worse.)
It sounds like we've already captured an action item out of this conversation, which is to offer GitHub Discussions as an alternative to Discord. Thank you for continuing to engage with us and keeping the conversation productive.

I don't really follow why I need to justify how I use open source software on my own machine, connecting to my own accounts?

Yes—as the account holder on your trackers, you are responsible for how you use cross-seed, and you are also free to fork or modify the code in any way. However, as cross-seed's user base has grown, every change or decision we make as developers has a larger impact than in the past, and we have to take some responsibility too.
To that end, cross-seed v6 has become much more opinionated about users' configurations, and some of them are no longer valid. In hindsight, it would have been good to do this from the beginning, but we were able to benefit from an experimentation period where users were able to figure out the "good" settings.
Remember, we want to find all the cross-seeds too—we believe in the efficacy of v6, regardless of the new restrictions on configuration. If you want to find old cross-seeds, you can set excludeRecentSearch and excludeOlder to high numbers - 1 year and 5 years is what I'm using.


Delete pricetable section from the homepage

pls delete pricetable section
Pricetable
-5%
Early Bird
350 UAH
Lorem ipsum is simply
Dummy text of the printing
Typesetting industry
Buy Now
-20%
Last Chance
450 UAH
Lorem ipsum is simply
Dummy text of the printing
Typesetting industry
Ticket sales will begin on 1 October 2014 00:00
Student
200 UAH
Lorem ipsum is simply
Dummy text of the printing
Typesetting industry
Sold Out

done!


Prototype of buffer reuse

This helps performance but not all performance issues have been resolved. Nontrivial CPU goes into write_buffer, and it's also possible that there isn't enough overlapping between CPU and GPU work.

Thanks for the review! I'll merge this soon but in this particular case would appreciate a glance from @dfrg, as I know he's spent some time thinking the problem.


Repetition of Model name in fitmaker.py

Hi,
I found that the PLSuperExpCutoff model to be repeated in the file, fitmaker.py. This occurs along the lines, 101-106. Should one of them be a logParabola or some other model, perhaps?
Thank you,
Venkatessh

thank a lot.
david


Stable

Doneness:

[X] Build is okay - I made sure that this change is building successfully.
[X] No Bugs - I made sure that this change is working properly as expected. It doesn't have any bugs that you are aware of.
[X] Branching - If this is not a hotfix, I am making this request against develop branch

:white_check_mark: Build Titanium-Web-Proxy 3.0.212 completed (commit https://github.com/justcoding121/Titanium-Web-Proxy/commit/5b7a8f43c5 by @honfika)


KAFKA-10069 The user-defined "predicate" and "negate" are not removed…

There are official configDef for both "predicate" and "negate" so we should remove user-defined configDef. However, current behavior does incorrect comparison so the duplicate key will destroy the following embed configDef.
https://issues.apache.org/jira/browse/KAFKA-10069
Committer Checklist (excluded from commit message)

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

@tombentley Could you take a look?

Yes, thanks, that was a goot spot @chia7712!


feat: Add a plugin framework to allow executing custom access request logic

@ashutosh16 I'll add sample plugin and docs in a future PR. 👍🏻


CommonJS Changes

Obviously you don't want this PR as-is (since the README is changed), but let me know what you think about the vars.js -> createClass.js changes, since that was really the area that wasn't working for me.

I think these changes are going in the right direction.
The name change is fine - I had it with that name because it was where the react instance was set previously
I'm find with referencing the modules through a central entry point rather than the sub modules directly
I do not want to remove support for AMD though - think you can get that straight?

Yeah, let me look into that.
Sent from my iPhone

On Jan 29, 2015, at 5:36 AM, Joe Hudson<EMAIL_ADDRESS>wrote:
I think these changes are going in the right direction.
The name change is fine - I had it with that name because it was where the react instance was set previously
I'm find with referencing the modules through a central entry point rather than the sub modules directly
I do not want to remove support for AMD though - think you can get that straight?
—
Reply to this email directly or view it on GitHub.

depending on the difficulty, I'm not opposed to just supporting CommonJS - but it would be ideal to support all.

Haven't been able to look at this yet, but might have a chance today or tomorrow.

see comments on https://github.com/jhudson8/react-chartjs/issues/4


Does SnarkyJS still need to be a peer dep?

iirc we switched to using a peer dep b/c the CLI needed SnarkyJS for deployment and this confilcted with the user's SnarkyJS.
But we now use the user's SnarkyJS for deployment. If we can switch back to a regular dep inside the project-ts project template, then zk system would be able to show SnarkyJS' version. But envinfo, which we use for zksystem, cannot list a peer dependency's version.
The todo here is to test create a project, switch SnarkyJS to a regular dep, npm install, and try to deploy it. If it works, we can switch back to a regular dependency.

No, unfortunately we switched to peer dep for a different reason. We did it so that UI (or other) projects can import both snarkyjs and the smart contract, without creating a situation where there are two versions of snarkyjs around (it deeply breaks snarkyjs if it's imported twice, bc it has a lot of global state, which is very much core to the imperative API we have for building circuits / transactions).
I think we could identify the need to update snarkyjs with a homegrown solution.
For classical projects (no ui / monorepo) we could take the "version range" in package.json as a hint and ask the user to update to a newer version range. Example: if we see that the project version is "^0.6.0" we could suggest a command to the user which would update that to "^0.7.2".
For monorepo projects, we could set it up so that snarkyjs is already installed as a normal dep in the ui project, and find out the exact version (like, by checking package-lock.json or node_modules/snarkyjs/package.json) in that project.


Silently cancel save from event handler

I read in the documentation that a save can be cancelled by throwing an exception in the saving event, but I would like to cancel the save operation without getting the exception (that would mean changing too much code for this case).
Is there any way I can cancel a save operation and then silently drop the exception?

Maybe using triggerThen?
I don't know if the following would work:
this.on('saving', (model, attrs, options) => {
  if (options.patch && _.isEmpty(attrs)) {
    trigger('saved');
  }
});

Does that skip the saving?

@chamini2 All the events magic lies in model.js#L971-L1034. And if you take look in events.js#L98-L105 then you can see that these are just promise chains. Promise chains currently can only be breaked by throwing an exception.
You could work out a workaround by implementing your own error and then catching it.
Promise.resolve()
.then(function() {
  return Promise.resolve('x')
  .tap(function(x) {
    throw new CustomError();
  });
}).then(function(y) {
  // never reaches here
}).catch(CustomError, function(){
  // all ok. just pass
}).then(
. . . .

@vellotis, I'm sorry, but I don't understand where I should put the catch part?

Take it as GOTO behaviour. As you know Promise is a tool to handle callback hell. If you use Node style then you pass Error to callback as long some callback handles it. So Promise is a callback chain. If you throw an Error then it is a "GOTO statement". If catch it, it is the "destination" of GOTO.

@vellotis, thanks for the recommendation, although I do understand the concept of using it as a GOTO, I didn't see the way to use it here. I ended making a hack to do a meaningless patch (setting id to it's current value), but I guess we could close this as I no longer have the problem.

@chamini2 You could try something like this:
const proto = bookshelf.Model.prototype;
const MyModel = bookshelf.Model.extend({
  save(...args) {
    return this.triggerThen('shouldSave', /* whatever arguments */)
      .catch(() => {})
      .then(() => proto.save.apply(this, args));
  }
});

But this sounds like a bad pattern IMO.

@chamini2 mind sharing your solution? Ran into this myself.

Sure, @jamesdixon:
    this.on('saving', (model, attrs, options) =>
      Promise.map(description, (modelDescr, name) =>
        saveModel(name, modelDescr, model, attrs, options)
      )
      .then(() => {
        // To avoid 'NoRowsUpdated' Bookshelf error
        if (options.patch && _.isEmpty(this.format(attrs))) {
          attrs.id = model.id;
        }
      })
    );


Update README.md

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview 13a77fc7-ab42-4472-b9a2-15ee0346f6f0
blueprint

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

There are two hard problems in computer science: naming things, cache invalidation and off-by-1 errors

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command
Blueprint environment

/qovery  preview 13a77fc7-ab42-4472-b9a2-15ee0346f6f0
blueprint

/qovery  preview {all|UUID1,UUID2,...}
To preview multiple environments

This comment has been generated from Qovery AI :robot:.
Below, a word from its wisdom :

Write comments that add new information that doesn’t exist in the code


Update documentation for "noselect"

In particular, make the distinction and interaction between "noinsert"
and "noselect" clearer as it was very confusing before.

thanks


StoqConfigParser class is not part of stoq.helpers when using pip3 install stoq-framework to install stoq.  To reproduce, follow the installation instructions in the documentation, install a plugin through the 'from directory' option and attempt to run stoq scan .  The code in the master branch is correct but not when installed using  pip3.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Client (please complete the following information):

OS: [e.g. Ubuntu]
stoQ Version [e.g. v2.0.0]

Exception
If applicable, the full exception traceback
Additional context
Add any other context about the problem here.

I'm not sure I follow. Are you saying that StoqConfigParser is not in stoq.helpers when you install with pip3 install stoq-framework? What version of stoQ are you installing? What operating system are you on?

Hey Marcus,
Good morning sir.  Hope you’re doing well and thanks for reaching out.  So yes, the StoqConfigParser class is not in stoq.helpers when i install with pip3 install stoq-framework.  I am installing version 3 of the stoq framework and I’m on an Ubuntu server 18.04 OS.  I ended up copying the source to disk and installing that way.  The pip3 installation method just wasn’t working for me.  Figured others were probably running into the same issue and that it might turn them off from using the framework (which I don’t want to see happen).  Please let me know if you have any more questions and I’ll be happy to answer them.  Anything to help sir!
Best Regards,
-Joseph Silva

On Jul 6, 2020, at 10:14 AM, Marcus LaFerrera<EMAIL_ADDRESS>wrote:
I'm not sure I follow. Are you saying that StoqConfigParser is not in stoq.helpers when you install with pip3 install stoq-framework? What version of stoQ are you installing? What operating system are you on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/PUNCH-Cyber/stoq/issues/154#issuecomment-654299055, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIQO2U65AYNSAS7NFB5HBYTR2HS37ANCNFSM4OIVNAGA.

Hi @deadh4nd - Unfortunately I am unable to replicate this. Can you try running pip3 install --upgrade stoq-framework or pip3 install stoq-framework==3.0.0 and see if that works for you? It sounds like there may be some conflicts from a older version of stoQ that are causing some issues.

Hey Marcus,
Sure.  I’ll have to create a new VM to test this on (since I already have a working copy on my current server), but I should be able to get back to you later today if that’s cool.
-Joseph

On Jul 6, 2020, at 10:29 AM, Marcus LaFerrera<EMAIL_ADDRESS>wrote:
Hi @deadh4nd https://github.com/deadh4nd - Unfortunately I am unable to replicate this. Can you try running pip3 install --upgrade stoq-framework or pip3 install stoq-framework==3.0.0 and see if that works for you? It sounds like there may be some conflicts from a older version of stoQ that are causing some issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PUNCH-Cyber/stoq/issues/154#issuecomment-654307602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIQO2U44EKKGB53FY6CUOA3R2HUUHANCNFSM4OIVNAGA.

Hey Marcus,
Work is getting in the way at the moment.  But as soon as I have some time I’ll give it a shot.  Sorry for the delay sir.
-Joseph

On Jul 6, 2020, at 10:43 AM, Joseph Silva<EMAIL_ADDRESS>wrote:
Hey Marcus,
Sure.  I’ll have to create a new VM to test this on (since I already have a working copy on my current server), but I should be able to get back to you later today if that’s cool.
-Joseph

On Jul 6, 2020, at 10:29 AM, Marcus LaFerrera<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi @deadh4nd https://github.com/deadh4nd - Unfortunately I am unable to replicate this. Can you try running pip3 install --upgrade stoq-framework or pip3 install stoq-framework==3.0.0 and see if that works for you? It sounds like there may be some conflicts from a older version of stoQ that are causing some issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PUNCH-Cyber/stoq/issues/154#issuecomment-654307602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIQO2U44EKKGB53FY6CUOA3R2HUUHANCNFSM4OIVNAGA.

Hi Marcus,
So I tried both of the pip3 installation methods you described and got the same error both times: “Could not find a version that satisfies the requirement stoq-framework (from versions: )  No matching distribution found for stoq-framework.”  That being said I’m also testing in my lab environment, so let me try on a system in a different environment and see if that fixes things.  I’ll get back to you with the results of that test tomorrow.  Thanks for taking the time to help me with this issue.
Best Regards,
-Joseph

On Jul 7, 2020, at 10:36 AM, Joseph Silva<EMAIL_ADDRESS>wrote:
Hey Marcus,
Work is getting in the way at the moment.  But as soon as I have some time I’ll give it a shot.  Sorry for the delay sir.
-Joseph

On Jul 6, 2020, at 10:43 AM, Joseph Silva<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hey Marcus,
Sure.  I’ll have to create a new VM to test this on (since I already have a working copy on my current server), but I should be able to get back to you later today if that’s cool.
-Joseph

On Jul 6, 2020, at 10:29 AM, Marcus LaFerrera<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi @deadh4nd https://github.com/deadh4nd - Unfortunately I am unable to replicate this. Can you try running pip3 install --upgrade stoq-framework or pip3 install stoq-framework==3.0.0 and see if that works for you? It sounds like there may be some conflicts from a older version of stoQ that are causing some issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PUNCH-Cyber/stoq/issues/154#issuecomment-654307602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIQO2U44EKKGB53FY6CUOA3R2HUUHANCNFSM4OIVNAGA.

Hey Marcus,
Good morning sir.  You can close this out.  I’m sorry for the inconvenience.  Looks like there is something going on in my lab.  Once I’m on a system outside of it, the installation works as expected.  Now to hound down what’s going wrong on my end.
Also, just switched to V3 and damn sir.  I am LOVING the fact that I can now chain workers together in a specific order.  That was something that I was struggling with in V2 and it makes a huge improvement to workflows.
Best Regards,
-Joseph

On Jul 8, 2020, at 5:37 PM, Joseph Silva<EMAIL_ADDRESS>wrote:
Hi Marcus,
So I tried both of the pip3 installation methods you described and got the same error both times: “Could not find a version that satisfies the requirement stoq-framework (from versions: )  No matching distribution found for stoq-framework.”  That being said I’m also testing in my lab environment, so let me try on a system in a different environment and see if that fixes things.  I’ll get back to you with the results of that test tomorrow.  Thanks for taking the time to help me with this issue.
Best Regards,
-Joseph

On Jul 7, 2020, at 10:36 AM, Joseph Silva<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hey Marcus,
Work is getting in the way at the moment.  But as soon as I have some time I’ll give it a shot.  Sorry for the delay sir.
-Joseph

On Jul 6, 2020, at 10:43 AM, Joseph Silva<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hey Marcus,
Sure.  I’ll have to create a new VM to test this on (since I already have a working copy on my current server), but I should be able to get back to you later today if that’s cool.
-Joseph

On Jul 6, 2020, at 10:29 AM, Marcus LaFerrera<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Hi @deadh4nd https://github.com/deadh4nd - Unfortunately I am unable to replicate this. Can you try running pip3 install --upgrade stoq-framework or pip3 install stoq-framework==3.0.0 and see if that works for you? It sounds like there may be some conflicts from a older version of stoQ that are causing some issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/PUNCH-Cyber/stoq/issues/154#issuecomment-654307602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIQO2U44EKKGB53FY6CUOA3R2HUUHANCNFSM4OIVNAGA.

Awesome! Great to hear v3 is benefiting your workflow. Let us know if you run into any other issues.


Revert "lib.getExe: Do not make assumptions about the main program"

A possible resolution to https://github.com/NixOS/nixpkgs/pull/247115

PRs to add meta.mainProgram to many packages have already been merged, they will hit the unstable channel soon.
The whole idea of the warning (and maybe at some point error) is to have people add meta.mainProgram immediately in the future. So I don't really see the point of this PR.

PRs to add meta.mainProgram to many packages have already been merged, they will hit the unstable channel soon.

May I have a link to this PR? I see only a few PRs where this was addedhttps://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+mainProgram+is%3Aclosed
I upgraded nixpkgs to master and got 6 warnings of lib.getExe being used, lib.getExe in this evaluation was used 7 times. Somehow I got a feeling that this is going to be the same ratio in other projects of mine

Strange error messages tend to be caused by assumptions in generic code. This is one of them. Removing the assumption improved the predictability of the code and the quality of error messages at the temporary cost of some inconvenience.

As long as this is implemented more or less everywhere. I am more than happy to see this patch

https://github.com/NixOS/nixpkgs/pull/248895


Edit ISSUE_TEMPLATE for use in new project #3

Purpose

The current Issue Template doesn't serve the purposes of this forked workstream well. The edits simplify and generalize for feature additions rather than a bug-forward issue template.
Solves for #3
Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[x ] Other... Please describe: Issue Template edit

How to Test

Go to "Issues" tab in GitHub UI
Select "New Issue"

Issue template should be the new format (see file changes)

What to Check
Verify that the following are valid

New issue template is default

Other Information

@bdleavitt - I am merging this one myself but if you have any questions/issues (no pun intended), lmk


Can't register gateway on TTNv3

Hi,
I am trying to send data with a nucleo-wl55 to an ESP 1ch gateway. I see some packages arriving to the gateway, but can't make the gateway to show up on things network. (Yesterday the nucleo connected to some nearby gateway and the packages showed up on ttn)
Can someone confirm if this project is still working with ttn? It is very possible that I messed up something, but I even tried a fork claiming that fixes ttnv3 connection.
If this project is not compatible with ttn anymore, could you recommend me some cheap ttnv3 compatible device/project?

Can try with ChirpStack instead?

Hi,
unfortunately I also failed to register the gateway with TTNv3. Has anyone managed to register the gateway with TTNv3?
Apart from connecting to TTNv3 thanks for great project!
Simon

Same issue; my device sends data to singlechan gateway which is reg'd with ttn3 and it shows there but never gets to ttn3 app console. This was all working fine with ttnv2, and the 3 nodes i have not started trying to migrate to ttnv3 are still receiving data via this gateway and into the v2 console - for another 2 weeks anyway. I brought up a multitech gateway and the node sends through to ttnv3 fine.
just today i've started playing with chirpstack and I see this notification in the gateway bridge related to this gateway:
Nov 10 21:30:08 Hennessy chirpstack-gateway-bridge[20358]: time="2021-11-10T21:30:08.819160443Z" level=debug msg="backend/semtechudp: sending udp packet to gateway" addr="<IP_ADDRESS>:1700" protocol_version=2 type=PullACK
Nov 10 21:30:08 Hennessy chirpstack-gateway-bridge[20358]: time="2021-11-10T21:30:08.819187591Z" level=debug msg="integration/mqtt: set gateway subscription" gateway_id=600194ffff499b2c subscribe=true
Nov 10 21:30:08 Hennessy chirpstack-gateway-bridge[20358]: time="2021-11-10T21:30:08.824857796Z" level=error msg="backend/semtechudp: could not handle packet" addr="<IP_ADDRESS>:1700" data_base64= error="gateway: at least 4 bytes of data are expected"

which is where i'm currently trying to investigate

What can we do when V2 will be closed?

As long as there is no fix for this, I went back to the original version. This works with TTN V3: https://github.com/itsygithub/ESP-1ch-Gateway

Hi
i just made it work with V3. I use ESP32+RFM95 and it works well.
Nothing changed regarding UDP packet forwarder message format.just  pay attention to few things i think.
1)It seems only 3 cloud server address available. If you don't find your country specific pls choose the nearest. I live in singapore so i choose Australia. (au1.cloud.thingsnetwork.)

Use the serial monitor to watch the message. if you get keep scrolling probably due to mistake  of mismatching configuration like PIN out & server address etc and you can fix any mismatch configuration.

goodluck.

You are mistaken; there can be no software solution to the actual problem, because the hardware is simply not capable of doing the job of a gateway.  LoRaWAN requires that a gateway simultaneously monitor 42 frequency and spreading factor combinations, but this device can only monitor one.  When you try to use this, you create a misleading situation where a gateway exists for only one combination, but does not exist for any of the other combinations that a proper LoRaWAN node is not just allowed, but actually required to make use of.
This completely screws up the ADR algorithm for settings spreading factor, and the fair channel selection algorithm required not only by the LoRaWAN spec, but actually by law.
Worse, when you do this on a public network, your mess things up for other people's nodes, even if you're not noticing the problem on you own nodes that you may have rigged to violate the LoRaWAN spec and radio laws, but only using a single frequency and spreading factor.
TTN absolutely prohibits connection of these non-compliant devices pretending to be gateways, because there is no possible software fix which can ever make them behave correctly as gateways.

You are mistaken; there can be no software solution to the actual problem, because the hardware is simply not capable of doing the job of a gateway. LoRaWAN requires that a gateway simultaneously monitor 42 frequency and spreading factor combinations, but this device can only monitor one. When you try to use this, you create a misleading situation where a gateway exists for only one combination, but does not exist for any of the other combinations that a proper LoRaWAN node is not just allowed, but actually required to make use of.
This completely screws up the ADR algorithm for settings spreading factor, and the fair channel selection algorithm required not only by the LoRaWAN spec, but actually by law.
Worse, when you do this on a public network, your mess things up for other people's nodes, even if you're not noticing the problem on you own nodes that you may have rigged to violate the LoRaWAN spec and radio laws, but only using a single frequency and spreading factor.
TTN absolutely prohibits connection of these non-compliant devices pretending to be gateways, because there is no possible software fix which can ever make them behave correctly as gateways.

ok by the way, can i use this solution in my private network base on https://github.com/TheThingsNetwork/lorawan-stack or chirp, installed localy?

I'm wondering the same. Since it's not supposed to be used with public TTN, then what are the private options?


Switch over to new exceptions

After this PR, mercantile raises only its own exceptions. If a user gets a MercantileError, they are using mercantile wrongly (or there is a mercantile bug). If a user gets a builtin exception, it's definitely a mercantile bug.

Coverage remained the same at 100.0% when pulling cfa192270ca34095f8cf13a5ff806f16bc370be2 on exceptions into e1faf21aa716d76d23c94cbe93d41c90a5e25d47 on master.

Coverage remained the same at 100.0% when pulling cfa192270ca34095f8cf13a5ff806f16bc370be2 on exceptions into e1faf21aa716d76d23c94cbe93d41c90a5e25d47 on master.

Coverage remained the same at 100.0% when pulling cfa192270ca34095f8cf13a5ff806f16bc370be2 on exceptions into e1faf21aa716d76d23c94cbe93d41c90a5e25d47 on master.

Coverage remained the same at 100.0% when pulling cfa192270ca34095f8cf13a5ff806f16bc370be2 on exceptions into e1faf21aa716d76d23c94cbe93d41c90a5e25d47 on master.

Coverage remained the same at 100.0% when pulling cfa192270ca34095f8cf13a5ff806f16bc370be2 on exceptions into e1faf21aa716d76d23c94cbe93d41c90a5e25d47 on master.

@rohits2 :wave: I'd like to have mercantile raise only its own exceptions for the reason expressed in the top comment :point_up: and would like to alter the exception messages a bit. Are you okay with that? I'd also love a double-check of the description of simplify() that I put in the change log.

This looks great! Your description of simplify is perfect as well.
The one thing I'd like to suggest is a little bit of a more descriptive error message for the InvalidTileError exception.  It's almost always caused by not using the zoom keyword argument, but right now the name makes it seem like the tile was out-of-bounds.  Maybe call it InvalidTileArgumentError or something that shows that it's a formatting/length problem?


Extract section from JSON of parsed books

Purpose of the script
The purpose of the script developed to return a section from a JSON file is to extract specific information from a book that has been parsed. The JSON file contains structured data from the book, and the script is designed to locate and return a particular section of the book, based on the information provided. This script can be used to extract information from multiple books, and the extracted data can be used for various purposes such as analysis, research, etc.
Useful Information
In the case of the JSON structures provided, one (Algebra.json) has a nested structure with a list of items, while the others (Chemistry 2e.json, College Physics 2e.json) have a flat structure with each item as a direct child. Therefore, it is important to handle both structures differently to ensure that all data is captured correctly. By using two different blocks of code within the json_to_section function, toggled by the value of nested_list argument, and each tailored to handle a specific structure, we can ensure that all data is captured regardless of the JSON file's format. This ensures that we do not miss any important information and can process the data accurately and efficiently.
Function
The main.py file accepts a path to json files of parsed books. These files contain portions called sections. The file then returns all sections alongside their page numbers in a csv file format; a csv file for each json file.
Test Results
JSON of parsed books

CSV of results

Intructions

Open the PATH.json file
Replace the ./parsed_books/ value with the absolute path location of the json files
Run the main.py file

Reviewers
@wsedor @quaku21

@PyJim since the previous PR is closed please ensure all the outstanding comments from there were addressed here as well so as to not redo the reviews

Yes. I made sure to rectify them before closing the PR.

Yes. I made sure to rectify them before closing the PR.
@PyJim okay. I don't see a usage function in the new PR hence the comment. It was a review item on the previous PR https://github.com/nsmq-ai/nsmqai/pull/57#discussion_r1278313408

I will add the usage function by close of day.


Error during the Synthesis Step

I have tried using the OpenLane flow for the aardonyx SoC developed at IIT Madras, India. An error is encountered during the synthesis step using Yosys and ABC.
.
The error message reads as below:
67.1. Executing OPT_EXPR pass (perform const folding).
terminate called after throwing an instance of 'std::out_of_range'
what():  Cell::getParam()
[ERROR]: during executing: "yosys -c /openLANE_flow/scripts//synth.tcl -l /openLANE_flow/designs/aardonyx/runs/28-07_19-08//logs/synthesis/yosys.log |& tee >&@stdout"
[ERROR]: Last 10 lines:
child killed: SIGABRT
error.log
yosys.log

The verilog source folder for the SoC is:
soc.tar.gz
I kindly request you to look into the error.

Hello @harikumar27399,
I could replicate the yosys crash you're getting. Is there a way to configure the amount of memory in the SoC? If so, could you try reducing it and test again? Currently it has more than 4 KBytes of memory.
Thanks.

Thanks a lot @ax3ghazy. Configuring the memory helped cross the OPT_EXPR pass. However, now I am facing an issue in the later part of the synthesis. There is a particular cell 'DLATCH_P' whose area remains unknown as it doesn't get assigned to any of the sky_pdk lib cells.
Due to this, the synthesis fails and the TCL interpreter exits with the following message:
ERROR: synthesis failed.
Exiting...
I feel this is also the reason behind slack violations pointed out by OpenSTA.
Updated verilog source directory:
aardonyx_src.tar.gz
opensta.log
yosys.log

@harikumar27399  As far as I understand, this means that the design contains latches and is not synthesizable by our version of Yosys. You should modify the design to remove those 6 latches. For example, this is a snippet of the Yosys log you attached reporting a latch in reg current_gate:
Latch inferred for signal `$paramod\MakeClock\initVal=1'0\initGate=1'1.\current_gate' from process `$paramod\MakeClock\initVal=1'0\initGate=1'1.$proc$/openLANE_flow/designs/aardonyx/src/MakeClock.v:99$25234': $auto$proc_dlatch.cc:450:proc_dlatch$30639

Thanks for the info @agorararmard. I removed those latches from the design and the synthesis passed successfully. However, there are timing violations (negative slack) reported after synthesis by OpenSTA.
The libraries used for min. and max. STA calculations are:
LIB_MIN: sky130_fd_sc_hd__ss_100C_1v60.lib
LIB_MAX: sky130_fd_sc_hd__ff_100C_1v95.lib
OpenSTA report: wns = -0.52, tns = -1.62
The synthesis passes in spite of these violations. So, I would like to know whether I can proceed with the floorplan step by ignoring these violations. If not, is there a way to fix the negative slack by configuring the toolchain differently or by using a specific library for STA calculations?
opensta.log

@harikumar27399 I'm afraid you're using the wrong corners for LIB_MIN and LIB_MAX, they should be:
::env(LIB_MIN) sky130_fd_sc_hd__ff_n40C_1v95.lib
::env(LIB_MAX) sky130_fd_sc_hd__ss_100C_1v60.lib

However, having a negative wns will not stop the flow, and it will proceed up to the GDS normally. We will be integrating some tools to enhance the wns as an optimization in the coming releases, however, for now, what you should do is increase the value of the environment variable CLOCK_PERIOD set inside config.tcl under your design until you no longer have a negative wns

@agorararmard I've solved the negative wns issue by increasing the clock period by one ns for the time being. I'm looking forward to the tools that will enhance the wns as an optimization in the coming releases.
Thank you.


Moment parse issue

When using the control to format input using HH:mm I am getting the wrong date.  The date depending on the input is consistent, but wrong.  An example would be 1503 parses to 12/31/02 19:00.  I have tested the parsing functionality of moment and it parses as expected.  Here is a fiddler that has the moment examples.
https://jsfiddle.net/lfolinowjb/spoqfd7y/2/

Are you using strict parsing? (the default)  From the example, it looks like you are not using strict mode.  (i.e. 1503 does not match HH:mm!)  Non-strict parsing has very strange behaviors that I am not able to predict.
Also, it seems to me that the input formats are incomplete  - I did not look in detail but I think you need at least these input formats ["hh:mm", "hhmm", "h"]
Closing because this does not seem to be related to this directive, it is a moment issue.


ci: amend commits instead of creating new ones

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Hey @krshdev not sure if this will mess up the commit history?

Maybe you could clarify the things you want to achieve there?
Nearly +60.000 Lines of code looking little bit suspicious to me :D


authorization on push

Is it possible to add login and password to push url?
I.e. to make something like:
application app00 {
live on;
push rtmp://user:pass@server:port/app/;
}

Hello friend, you can use the HTTP callbacks, using the on_publish notify, you just need to stripe the arguments you pass on the connection string and validate them against a PHP

No, i need to authorize on remote rtmp server when doing push

Did you try solution you wrote in question? It should work with auth data
in rtmp url.
2015-09-21 21:11 GMT+02:00 ugenk<EMAIL_ADDRESS>
No, i need to authorize on remote rtmp server when doing push
—
Reply to this email directly or view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/688#issuecomment-142081196
.

root@gate:~# /usr/local/nginx/sbin/nginx -s reload
nginx: [emerg] invalid port in url "user:pass@<IP_ADDRESS>:1935/live/" in /usr/local/nginx/conf/nginx.conf:26
part from config:
push rtmp://user:pass@<IP_ADDRESS>:1935/live/;

You can view: http://nginx-rtmp.blogspot.jp/2013/06/secure-links-in-nginx-rtmp.html

rtmp://user:pass@<IP_ADDRESS>:1935/live/

That syntax would be perfect, @arut any news?

@arut as @sgdc3  mentions people needing to leverage push rtmp://user:pass@<IP_ADDRESS>:1935/live/; to external services that use authenticated rtmp, nginx-rtmp does not work. Can you help shed some light on how to accomplish rtmp://user:pass@<IP_ADDRESS>:1935/live/ with out getting the "invalid port in url" error?
Thanks in Advance!

+1 We also need it to push to Wowza

+1 That would be really helpful.

I tried ffmpeg and it worked like a charm (in config file):
exec ffmpeg -i rtmp://<IP_ADDRESS>/live/test -threads 1 -vcodec copy -acodec copy -f flv<EMAIL_ADDRESS>

@shahab1363 nice! thank you for sharing

+1. This  would be really helpful.