Implement exercise collatz-conjecture

porting exercise

I believe that everything should be correct, I look forward to reviews

Squashed the commits to a single one

Thanks for your time, effort, and enthusiasm!
To collect all my scattered thoughts above, I'd suggest something more along the lines of the following.
#lang racket

(provide collatz)

(define (collatz-length n [acc 0])
  (if (= n 1)
      acc
      (collatz-length (if (even? n)
                          (/ n 2)
                          (add1 (* 3 n)))
                      (add1 acc))))

(define (collatz n)
  (if (nand (exact-integer? n)
            (positive? n))
      (error "number must be a positive integer")
      (collatz-length n)))

Thanks @yurrriq  Great suggestions! I will work on this and commit soon.

OK, I've committed changes that I believe fix the issues you found @yurrriq.  Thanks for the review

The tests look great, but I still think it’d be good to make collatz tail recursive. What do you think?

I could also get on board with the SICP convention of defining a tail recursive helper function (with an accumulator) and having collatz simply call that.

Hi @yurrriq, I agree, I updated the example to use the code you provided, thanks.

Awesome! Thanks for all your work on this and for taking the initiative to revamp the Racket track.

Hi @yurrriq, I tried to fetch this exercise, but I get an error:
joe ~/exercism/racket $ exercism fetch racket collatz-conjecture
2017/10/19 14:35:12 unable to fetch problems (HTTP: 404) - No implementation of 'collatz-conjecture' in track 'racket'

I'm not sure what's gone wrong here.. @kytrinyx ?

It's in the config. If the problem was fetching it, that's because I have to manually deploy, and with my current work-load, that isn't happening every day. I deployed a couple of hours ago, s

It's present in the config on master:
https://github.com/exercism/racket/blob/master/config.json#L76-L85

Sorry @kytrinyx, I didn't realize there was a manual deploy step.  Thanks for your help.  It is working fine now.  Also thanks to @yurrriq for his good suggestions.


allow  using fetchEvent for<EMAIL_ADDRESS>optionally

This PR adds the ability to use the fetchEvent from StarlingMonkey to handle incoming HTTP requests. This needs the http feature to be enabled explicitly.

I tested this only with the incomingHandler annotation but the above is a good catch. Let me go do some more testing/digging and report back.

It might be that name is just the interface name and so that the check should be using name_world_key against the interface world key for the full<EMAIL_ADDRESS>case.

Ahh, name is shadowing the outer name, so it should be renamed to Some(iface_name) =  I think.

To confirm my understanding the allowed exports are  incomingHandler and<EMAIL_ADDRESS>correct? or is the explicit notation supposed to be wasiHttpIncomingHandler020 ?

Yes exactly, so checking iface_name.toCamelCase() and name which are separate originating values.

I believe we are already doing both the checks on line 388 (fully qualified name) and line 392 (sugared name) unless I am missing something.

@guybedford let me know if there is anything else to address for this PR.

@guybedford would it be possible to get a release with this PR? Thanks!

Sure, I've published a 0.10.1.


Access token remains in URL after logging out and can cause automatic login

I'm using Supabase for authentication in my single-page application and have an issue with third-party OAuth logins. When a user logs in with GitHub or Google, their access token is stored in the URL. However, the access token remains in the URL after the user logs out. If the user then presses the back button or refreshes the page, they are automatically logged in again without having to re-enter their credentials.
This behavior is a serious security issue, as it allows unauthorized access to user accounts. I've tried using history.replaceState to remove the access token from the URL after logging out, but it doesn't seem to be working.
Can anyone suggest a solution to this problem? Is there a way to ensure that the access token is completely removed from the URL after logging out, and that the user is not automatically logged in if they navigate back to the page?

Fixed OAuth access token persistence issue and resolved automatic login on page refresh
The problem was resolved by adopting React Router for navigation within the single-page application, which ensures the removal of the access token from the URL and prevents unauthorized access. The issue has been successfully resolved, and the commit implements the necessary changes to fix the problem.


how to generate _tiktoken_bg.wasm?

hi! I wonder how to generate or download _tiktken_bg.wasm? Since i always encounter errors like "chatgpt activate error, not found _tiktken_bg.wasm" while debugging a vscode extension about chatgpt. Looking forward to your reply.

This repository does not currently ship WASM bindings. I'd ask the author of whatever unofficial extension you're using


feat(stepper): webcomponent version of stepper

NEEDS UPDATED Z-INDEX
Describe pull-request
Created a webcomponent version for stepper.
Solving issue
Fixes: AB#2699
How to test

Go to storybook link below.
Check in Components -> Stepper -> Webcomponent

Screenshots
Additional context

One thing, that I'm not sure about, is if we should have stepper items in this way. Could be that it's easier for the user just to have a numberOfSteps prop or something and not have to write out all the steps. But that might make it harder with labeling and status.

That might hinder the user from adding event to the stepper-items, so I would suggest we keep them as a parent and child items 👍🏻

Sorry about all my comments 😄 I don't want to slow the web component conversion down, but I also see this as our shot to make the components extra premium 😉

No worries! It's great that we are thorough in the PRs and ask questions, raise concerns and purpose improvements 👍🏻

Hiding the label seems to be dependent on removing text from the label prop it self. I wonder if we should have prop hideLabel as boolean - just thinking of case where user might want to hide label on one screen size and show it on another one? If so, should it be a prop on the parent wrapper then? What do you think?

If you hide label now but you toggle text position component gets some more space between the circles - not a big issue, but would be nice to resolve it.

Hiding the label seems to be dependent on removing text from the label prop it self. I wonder if we should have prop hideLabel as boolean - just thinking of case where user might want to hide label on one screen size and show it on another one? If so, should it be a prop on the parent wrapper then? What do you think?

If you hide label now but you toggle text position component gets some more space between the circles - not a big issue, but would be nice to resolve it.

I'll do some refactoring on this one so I'll close the PR and then create a new one when it's ready :)


org.springframework.cloud.bootstrap.BootstrapConfiguration deprecated ?

Hi,
as bootstrap mechanism has been deprecated, and config data encouraged instead,
how to migrate a class
public class VaultPropertySourceInitializer implements ApplicationContextInitializer, BeanFactoryAware, Ordered
declared in spring.factories in org.springframework.cloud.bootstrap.BootstrapConfiguration property ?
Thanks in advance for your help.
Ludo

You can apply customizations through a Spring Boot Bootstrapper:
SpringApplication application = …;

application.addBootstrapper(VaultBootstrapper.fromConfigurer(configurer -> configurer.add("secret/customized")));

Maybe it would be easier if I explain the feature I've implemented.
via a file vault.yml :
paths:

path: pathA/subpathA
prefix: prefixA
path: pathB/subpathB
prefix: prefixB

secrets declared in each path are loaded in Spring Context with prefixed bean (ex.: prefixA.mysecret, prefixB.mysecret).
We have implemented this to avoid key collision.
Maybe you have a simplest approach to achieve it.
Thanks for your help
Ludo

In that case, you can use the Config import feature to remove the need for a customizer altogether. You can import individual config locations by adding these to the spring.config.import property, e.g.: spring.config.import=vault:pathA/subpathA?prefix=prefixA,vault:pathA/subpathB?prefix=prefixB

Thanks a lot, it works like a charm !
On Mon, Jan 3, 2022 at 10:54 AM Mark Paluch @.***>
wrote:

In that case, you can use the Config import feature to remove the need for
a customizer altogether. You can import individual config locations by
adding these to the spring.config.import property, e.g.:
spring.config.import=vault:pathA/subpathA?prefix=prefixA,vault:pathA/subpathB?prefix=prefixB
—
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-vault/issues/627#issuecomment-1003978292,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD76MMTRMBMEA6ZH5YVQNDUUFW6FANCNFSM5LEXPTWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


empty stripe at the bottom of cards with only an image element

As shown in the following pic, there's a small stripe at the bottom of the card. I assume when the image is used as the only element of a card, it should fill the card and the bottom stripes should not exist.

                        Montreal

Fixed in aa1b00640ddefdf4c74c190c004fa406cf6ac82f


[K8S][HELM] Move helm chart to dedicated directory

Why are the changes needed?
The changes are needed to be compliant with Helm recommendations:

https://helm.sh/docs/topics/charts/#the-chart-file-structure

The directory name is the name of the chart (without versioning information).
Thus, a chart describing WordPress would be stored in a wordpress/ directory.

https://helm.sh/docs/howto/chart_releaser_action/#repository-changes

The charts should be placed under /charts directory at the top-level of the directory tree.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

retest

thanks, merging to master


534-update-env-example-v1

#534 This PR updates the latest information to .env.example file.

Removed info about Civic API key
Added info about Cicero API key

Thanks Param for helping me with this issue and the PR.


Add forwardRef to DrawerBody

Need to pass a ref to this component to not show google places autocomplete when scrolling; rough idea in this PR https://github.com/user-interviews/rails-server/pull/24206

This feels like we're exposing the internals of the DS (which is generally best to avoid) in order to handle a pretty unique edge case in rails server. Can you elaborate a bit on the problem this is solving?

This aims to to fix this behavior when scrolling
https://github.com/user-interviews/ui-design-system/assets/54962889/bada8ff9-c573-4a50-90b3-41358c5d65d4
with this PR https://github.com/user-interviews/rails-server/pull/24206/files you now have this
https://github.com/user-interviews/ui-design-system/assets/54962889/ed4cb953-5442-47be-aa73-10381ed53138
I need to listed to a DrawerBody scrolling event since that's where the scrolling happens for a drawer per our css https://github.com/user-interviews/ui-design-system/blob/develop/src/Drawer/DrawerBody.scss#L3
Happy to fix it in some other way if there are other better ideas!

I guess I just feel like forwardRef gives something to this library's consumers that points to a very mutable internal of this component (the dom node itself, on which any number of actions can be taken that we may or may not want to be possible).  To me, it's similar to the question of providing a className property vs supporting variants.  The second of these two yields a stricter interface.
In this case, would it be possible (and maybe preferred) to add an onScroll property to this component instead?

I'm generally of the opinion that we shouldn't be forwarding refs within DS components. Doing so is kind of creating a contract saying "you can expect this element to exist and do whatever you want with it" and that's really not a promise we want to make since individual elements within the component are implementation details that could change. In this case I think its unlikely to change since this component is pretty much a wrapper for styling but its still not a great pattern.
Given we're already doing that elsewhere its not the worst thing in the world to allow it here now but I'd prefer if we stopped forwarding refs when we hit 3.0 since its a breaking change to remove them.

In this case, would it be possible (and maybe preferred) to add an onScroll property to this component instead?

That's what I would prefer. Providing onScroll doesn't tie it directly to a specific DOM element. If the internals change later you can move the listener to the DOM element that is now relevant and not break the contract with the components using the DS component and the onScroll prop.

Yeah that does sound annoying. The root issue is with with GooglePlacesAutocompleteField not displaying correctly though. Using the ref (or even onScroll) to hide the autocomplete makes the issue less apparent but really the autocomplete should stay put on its own.
Given GooglePlacesAutocompleteField is a deprecated component the long-term solution is probably to create a Google Places autocomplete field that displays correctly and we actively maintain. I get why that would be out of scope of fixing this bug, but we should generally avoid refs wherever possible. They're more of an escape hatch than a tool you want to use often.

After saying that I referred to the React docs for when they recommend using refs and was reminded that they are actually documented in a section called Escape Hatches.

Yeah that does sound annoying. The root issue is with with GooglePlacesAutocompleteField not displaying correctly though. Using the ref (or even onScroll) to hide the autocomplete makes the issue less apparent but really the autocomplete should stay put on its own.

Given GooglePlacesAutocompleteField is a deprecated component the long-term solution is probably to create a Google Places autocomplete field that displays correctly and we actively maintain. I get why that would be out of scope of fixing this bug, but we should generally avoid refs wherever possible. They're more of an escape hatch than a tool you want to use often.
100%. We could create our own DS component where we fully control the css with google Autocomplete API to get the data
https://developers.google.com/maps/documentation/places/web-service/autocomplete


Upgrade black and add config

Summary
I noticed that there is no setting for black. I have set it to the same setting as Terra, but if that was your intention, please close this PR.
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

61 of 82 (74.39%)  changed or added relevant lines in 27 files are covered.
9 unchanged lines in 6 files lost coverage.
Overall coverage increased (+0.1%) to 72.814%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/api/clients/base.py
2
3
66.67%

qiskit_ibm_runtime/api/rest/backend.py
0
1
0.0%

qiskit_ibm_runtime/api/rest/utils/data_mapper.py
0
1
0.0%

qiskit_ibm_runtime/qiskit_runtime_service.py
20
21
95.24%

qiskit_ibm_runtime/runtime_job.py
5
6
83.33%

qiskit_ibm_runtime/runtime_options.py
1
2
50.0%

qiskit_ibm_runtime/runtime_program.py
3
4
75.0%

qiskit_ibm_runtime/utils/runner_result.py
0
1
0.0%

qiskit_ibm_runtime/utils/sampler_result_decoder.py
0
1
0.0%

qiskit_ibm_runtime/utils/utils.py
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/qiskit_runtime_service.py
1
81.21%

qiskit_ibm_runtime/runtime_job.py
1
77.56%

qiskit_ibm_runtime/runtime_options.py
1
91.67%

qiskit_ibm_runtime/runtime_program.py
1
88.2%

qiskit_ibm_runtime/utils/sampler_result_decoder.py
1
55.56%

qiskit_ibm_runtime/ibm_backend.py
4
54.86%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2590

Relevant Lines:
3557

💛  - Coveralls

Having the same black settings as terra works for me, it keeps the code bases more consistent

@kt474 Thank you very much. If you encounter any problems related to ddt in the future, please assign me.


Updated packages to fix 4719 vulnerabilities

I ran npm audit fix to find and update out-of-date packages with known vulnerabilities. 4719 vulnerabilities were found and patched. No breaking changes were made.

wow


NOT AN ISSUE!!

Amazing UX. I am curious frm where did you get the idea and inspiration to do this ? :)

Thanks @theapache64. This was originally made in 2012. I unfortunately do not recollect the thought process behind it :)


bitfield optimization of phase2

This avoids some sort-on-disk in phase2 (back-propagation) by recording which entries in table_index are used by table_index + 1. Phase 2 now looks like this:

loop from table 7..1:

scan current table:

if table < 7, skip any entries not set in current_bitfield
record the indices we find in the the current table by setting the corresponding bit in previous_bitfield

if table < 7: scan current table (again):

compact table by skipping fields whose bit is not set in current_bitfield
write back each pos and offset with an adjusted position, based on the new (compacted) locations in previous_bitfield.

current_bitfield = previous_bitfield
clear all bits in previous_bitfield

In order to hand over the tables in the correct order, sorted as the current phase 2 does, the "write-back" step is really done into a SortManager object. This object is then passed on to phase 3, as if it was a Disk.
Enabling a SortManager to implement the Disk interface required a few changes. The Disk interface now returns a pointer to the entry, when reading from it. This is how SortManager returns data, and I envision it is how we will actually return data if we transition to memory mapped files too.
To allow passing a SortManager from one phase to the next, they now heap allocate their memory, rather than relying in being passed a buffer that is later reused.
Another optimization of the algorithm described above is that the last table, table 1, isn't sorted, it just need to be compacted. Instead of running a read and write-back pass over table 1, there's yet another abstraction implementing the Disk interface; FilteredDisk. It wraps a normal file along with a bitfield and provides an object that appears to be a compacted file. i.e. all the entries not set in the bitfield are skipped when reading from the file. This saves another read and write pass over table 1.
The last change that was necessary to unify the interfaces of SortManager and Disk was to provide a BufferedDisk. It wraps a plain file on disk but implements a read and write cache. This simplifies the loops in phase 2 and phase 3, where they no longer need to do their own read caching. Similarly, the SortManager no longer needs to do its own write caching when writing to buckets.
The intention of this patch is to reduce disk I/O. Enabling disk I/O logging and testing:
./ProofOfSpace create -k 24 -s 8192

Yields this result:
total-read:<PHONE_NUMBER>
total-write:<PHONE_NUMBER>

This can be compared to the current master I/O, with the same command:
total-read:<PHONE_NUMBER>
total-write:<PHONE_NUMBER>

That's a reduction of writes by 12,07% and an increase of reads by 2.63%.
When the full working set fits in RAM (i.e. no actual disk I/O is performed) this patch runs slower. This is most likely because the sorting of the buckets in phase3 is done twice, since phase 3 performs two read passes over the tables. It's expected that it will be faster when running against an a disk, plotting a file much larger than available RAM.

@aqk I had a few typos in my additional unit test that catch (for some reason) didn't report so I didn't notice until CI ran and it detected a non-zero return code.
I've fixed that now. I want to squash all the fixup commits to their respective change they belong to, but to make it easier to review my changes, I left them in as new commits on top for now. Please take a look then I'll squash.

I ran some large benchmarks overnight (probably a lot larger than they had to be).
This is on MacOS, a fairly powerful laptop against a slow spinning disk connected over USB. So, this was most definitely I/O bound. I wanted to avoid running a test so small that it would fit in RAM, and I don't have all that much free space on the internal SSD. But it might be nice to get an idea of what the numbers look like on a more reasonable setup with a large SSD as the plotting target.
I timed these runs with time, but I also piped the output to tee to log it, along with 2>&1. I think this messed up the output from time and I lost the real time (I got the user and system CPU time as well as the total time).
total time with current master: 9:17:47.59
total time with this patch: 9:11:14.91
6 minutes and 33 seconds faster. Not a whole lot given a > 9 hour runtime.
This is the timing output from the runs, master first:
Time for phase 1 = 10833.506 seconds. CPU (116.590%) Fri Nov  6 03:50:20 2020
Time for phase 2 = 7490.284 seconds. CPU (36.240%) Fri Nov  6 05:55:10 2020
Time for phase 3 = 14189.635 seconds. CPU (44.280%) Fri Nov  6 09:51:39 2020
Time for phase 4 = 949.447 seconds. CPU (57.620%) Fri Nov  6 10:07:29 2020
Total time = 33462.874 seconds. CPU (66.270%) Fri Nov  6 10:07:29 2020

Now, for this patch:
Time for phase 1 = 9960.252 seconds. CPU (127.730%) Thu Nov  5 17:42:43 2020
Time for phase 2 = 6451.230 seconds. CPU (53.280%) Thu Nov  5 19:30:14 2020
Time for phase 3 = 15829.239 seconds. CPU (56.150%) Thu Nov  5 23:54:03 2020
Time for phase 4 = 826.582 seconds. CPU (66.470%) Fri Nov  6 00:07:49 2020
Total time = 33067.307 seconds. CPU (77.410%) Fri Nov  6 00:07:49 2020

That's only a 1.18 % reduction in runtime. Given that it's still performing 12% fewer writes (at the expense of 2% more reads) and it's not making things slower (at least not dramatically), I think it's still a viable change.
I suspect that one reason it's not improving runtime all that much on a spinning disk is that it (probably) increases seek times since phase 3 now reads from two separate sort managers, meaning it will keep two read cursors on disk that it will have to alternate between.
Right now I set the disk read-ahead (and write) buffers to 4 MiB, as that's the minimum extent size on ext4 (iirc). I'll experiment with making that larger, say, 8 or 16 MiB.

I ran another test of this patch with a 16 MiB read- and write cache. It almost took 1 hour longer than the two previous tests. I'm thinking that there's probably a lot of noise in the way I'm testing this. Most likely introduced by the spinning disk.
Interestingly, almost all of the additional time happened in phase1, which should be unaffected by my patch anyway. There may be some opportunity for improvements in phase 1 on spinning disks.

squashed fixups


How to enable Bytecode instrumentation (Automatic/Manual) in pinpoint?

Looks like i could see only exec(ms) column in Call stack visibility
How to get the dynamic instrumentation enabled like invocation count, CPU%, CPU Time spent in each method
I dont see any option of Bytcode Instrumentation feature in pinpoint dashboard
Please do let me know If I am missing something here

Hi @dinesh4747
The bytecode instrumentation is already enabled, that's how you're seeing the callstack (including exec(ms) etc).
The reason why you're not seeing CPU%, CPU time spent on each method is because we don't collect those statistics (yet?).
Invocation count is something we're working on currently.

Hi @Xylus
If i understand in right way that byte code instrumentation would give only the below

Call Stack
Exec time (ms)

But Instrumentation would give you the following as well if I am right as below:
a) Sync/Aysnc time
b) I/O Wait
c) N/w Wait
d) CPU Time
c) CPU % (Method level probing)
I feel that when we do byte code level automatic profiling we should be getting the above key insights as well
Kindly let me know If I have misinterpreted anything here

I think we're getting some terminologies mixed up here.
Bytecode instrumentation is a feature that enables you to modify bytecode during runtime (class load time to be exact). Simply using bytecode instrumentation doesn't give you anything except the ability to change bytecode.
We use bytecode instrumentation to modify various classes/methods in order to collect data needed to generate everything you see in the call stack (including execution time etc).
However, in order to also profile everything you've mentioned (I/O Wait, CPU Time, etc), we'll need to add/implement code to collect those data. Simply enabling instrumentation doesn't give you these data automatically.
If you're suggesting that it would be better if Pinpoint also collects the metrics you've mentioned, then yeh, I agree with you to an extent :)

Hi @Xylus
Yes - Agreed
Even I am just looking for the same sort of data


🍒 Cherry pick PR #8906 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/8906 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.57-9 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.


Area2D causes huge frame spikes and stutter, attributed to "setup/solve constraints"

Tested versions
Reproduced in 4.3 stable, 4.2.2. stable (haven't tested other versions)
System information
macOS, Windows
Issue description
We noticed our game having serious intermittent stutters in Godot 4.3. They were seemingly random, and checking the profiler I saw large spikes usually in Physics2D category "setup constraints" and occasionally in "solve constraints". I reproduced the issue in a small project consisting of just one Area2D moving around a bunch of other Area2Ds. "run on separate thread" is disabled for physics.
https://github.com/user-attachments/assets/02d3a9b7-70d3-4aa5-a5bb-b0a18828192b
and here's one of the biggest spikes I've seen (this time in Godot 4.2.2)

Steps to reproduce
run MRP, start profiler and check "Physics2D" to see the graph. Within a few minutes you should see some large frame spikes that coincide with the FPS dropping.
Minimal reproduction project (MRP)
physics-2d-stutter.zip

I don't manage to reproduce this on Linux (Ubuntu 24.04.1) on my machine:

Do you have any program(s) running in the background that could be causing this?
Can you test other machines and/or a Linux (live) distribution?

Not getting spikes, either with or without vsync
Godot v4.3.stable - macOS 14.5.0 - GLES3 (Compatibility) - Apple M1 Max - Apple M1 Max (10 Threads)

also no spikes on my windows pc

Well I'm not sure what was causing it exactly, but after a machine restart the issue seems to be gone. (could've sworn I tried that already). Apologies for the trouble and thanks all for testing!


require 'watir-rspec' cause circular reference on driver init

In my project which already running with selenium-webdriver I decide to try watir w/ watir-rspec gems.
I create driver instance via: @driver = Watir::Browser.new :firefox and if watir-spec is required - I got 'SystemStackError: stack level too deep' error
I've tried to debug it w/ and w/out requiring gem:

when it required - Watir::Browser.new cause to run ../watir-5.0.0/.../watir/loader.rb
when it's not - ../watir-webdriver-0.7.0/.../browser.rb

in first case it cause circular reference in initialize method which cause such exception.
Ask me for any additional info - would be happy to share.

What watir/selenium gems do you have in your Gemfile and how do you require those dependencies?

my Gemfile:
# watir related
gem 'watir-webdriver'
gem 'watir-rspec'

and my spec_helper:
require 'watir-webdriver'
require 'watir/rspec'

So I using latest 0.7.0 watir-webdriver and 2.0.3 watir-rspec on ruby 2.2.0

Do like this instead:
# Gemfile
group :test do
  gem "watir-rspec"
end

and in spec_helper.rb do not require any watir-related gems because Bundler already requires watir-rspec, which in turn loads everything needed in correct order.

When I removing require 'watir/rspec' from spec_helper.rb I got uninitialized constant Watir::RSpec (NameError). I using watir for black box test automation (no Rails or similar)

Did you use bundler to run your specs? It seems as you did execute rspec directly without bundler exec rspec.

Yup, thats true. I use RubyMine's run command - thats handy to run single example

If i'm not mistaken then Rubymine should have full Bundler support in it as
well so even if you'd run single example it still use Bundler. But that's a
completely different problem which you should fix as well :) However, until
then, just add that watir-rspec require back to your spec_helper then.
On Tue, May 26, 2015 at 11:31 AM, Iaroslav Kukharuk <
<EMAIL_ADDRESS>wrote:

Yup, thats true. I use RubyMine's run command - thats handy to run single
example
—
Reply to this email directly or view it on GitHub
https://github.com/watir/watir-rspec/issues/13#issuecomment-105444841.

OK, I found what cause such issue - page-object gem.
Check this code:
require 'page-object'
require 'watir/rspec'

RSpec.configure do |config|

  config.before(:all) do
    browser = Watir::Browser.new :firefox
  end
  config.include Watir::RSpec::Helper

end

describe 'test valid' do
  it 'test test', :smoke do
    browser.goto("http://www.google.com")
    sleep 5
    browser.close
  end
end

How can you be sure that page-object gem is to blame with that code?
On Tue, May 26, 2015 at 1:12 PM, Iaroslav Kukharuk<EMAIL_ADDRESS>
wrote:

OK, I found what cause such issue - page-object gem.
Check this code:
require 'page-object'
require 'watir/rspec'
RSpec.configure do |config|
config.before(:all) do
browser = Watir::Browser.new :firefox
end
config.include Watir::RSpec::Helper
end
describe 'test valid' do
it 'test test', :smoke do
browser.goto("http://www.google.com")
sleep 5
browser.close
end
end
—
Reply to this email directly or view it on GitHub
https://github.com/watir/watir-rspec/issues/13#issuecomment-105477094.

I've create test_spec.rb with code bellow, and run it as rspec test_spec.rb from command line(make sure p-o is before watir)
run it and ged:
 1) test google.com
     Failure/Error: @browser = Watir::Browser.new :firefox
     SystemStackError:
       stack level too deep
     # ./test_spec.rb:7:in `new'
     # ./test_spec.rb:7:in `block (2 levels) in <top (required)>'

than I run same code but with commented require 'page-object' and test passed.
what is interesting:
require 'watir/rspec'
require 'page-object'

...

not cause such error

I don't know inner workings of page-object gem, but maybe it does something
to trigger that error.
Try like this:
require "watir/rspec"
browser = Watir::Browser.new :firefox
require "page-object"
browser.goto("http://www.google.com")
J.
On Wed, May 27, 2015 at 4:15 PM, Iaroslav Kukharuk<EMAIL_ADDRESS>
wrote:

I've create test_spec.rb with code bellow, and run it as rspec
test_spec.rb from command line(make sure p-o is before watir)
run it and ged:

test google.com
Failure/Error: @browser = Watir::Browser.new :firefox
SystemStackError:
stack level too deep
./test_spec.rb:7:in `new'
./test_spec.rb:7:in `block (2 levels) in <top (required)>'

than I run same code but with commented require 'page-object' and test
passed.
what is interesting:
require 'watir/rspec'
require 'page-object'
...
not cause such error
—
Reply to this email directly or view it on GitHub
https://github.com/watir/watir-rspec/issues/13#issuecomment-105903193.

Closing this due to inactivity.


Buttons of mobile navbar are smaller than "clickable" area

lol not again...
I'll look into this, however, I don't think this is much of an issue as this does not occur on real mobile devices (since you got no hover-style there).

lol not again...
I'll look into this, however, I don't think this is much of an issue as this does not occur on real mobile devices (since you got no hover-style there).

I'm sorry :( I tagged it with low prio, just stumbled over it randomly when adding the logo

I disagree. This is indead a problem. You HAVE to click on the text for anything to happen. If you click on the whole width of the element (which I think is very reasonable, if the text is left aligned and my thumb has difficulties reaching the text, but not reaching the whole button width), you even see the hover styling but nothing happens.

I disagree. This is indead a problem. You HAVE to click on the text for anything to happen. If you click on the whole width of the element (which I think is very reasonable, if the text is left aligned and my thumb has difficulties reaching the text, but not reaching the whole button width), you even see the hover styling but nothing happens.

That is simply NOT true on real mobile devices (at least on the ones I own). Clicking inside the div and not on the text is sufficient to trigger the navigation.

I tried it with a local jwt branch build. You are right, it works on the deployed version. We should check again, when jwt is merged.


Migration dependencies

Add a decorator to endpoints that defines what migration it requires having in the database to be able to run.
This way, when we upgrade to Kubernetes, we could wait 5 minutes for more pods to switch over to the newest version, then migrate.
In the meantime the server can keep serving requests, just not those that require the newest migration. These will, when a request is made to them, return a JSON stating that the server is currently updating and to try again in x amount of minutes.

It could also try redirecting to a pod that is still on an older version, maybe? Then if that fails give the updating and try again result.


[QoL] Visualizer Font dimensions are too restricting

This is how the packed Lode Runner sprites should be visible inside the visualizer.

Unfortunately this is not currently possible due to incomplete / restrictive visualizer settings.  See #74 for details.

Font options also missing:

[x] Color
[x] High bit -- see #76


[jsoncons] Update to v0.146.0

Describe the pull request

What does your PR fix? Fixes issue #

#213, #214

Which triplets are supported/not supported? Have you updated the CI baseline?

All. Yes.

Does your PR follow the maintainer guide?

Yes

Thank you @danielaparker :)


refactor(utils): throw ArgumentError instead of assert

Coverage remained the same at 94.118% when pulling 1291f4273c3f92e67fe17458547c502c74cbbc65 on refactor/throw-argument-error-instead-of-assert into df586aa80fbc34a781086fb294f6dfed2b01e11a on main.


feat(backend): report alarm errors in actors

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#527  👈
#525
main

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

Join @NathanFlurry and the rest of your teammates on  Graphite


load keypair with passphrase

Processing key pair with a passphrase.
Please let me know if you like my proposal for this function. If we like this function I will also work on the test code.

@marco10507 Thank you for the PR. The original goal of this repo is to add the missing encryption/decryption capability to pkcs8. We tried to make it small and leave the usage to the application implementation. I feel that loading TLS certificates with encrypted keys falls more logically into the tls package instead of pkcs8. But feel free to branch off or extend tls package to add the functionalities.


Docs for /api/1.1/deliveryserviceserver are wrong

Current docs describe an API that is URL form encoded, but the implementation expects JSON.

piggy backing onto this issue. This endpoint is not deprecated: https://traffic-control-cdn.readthedocs.io/en/latest/api/deliveryservices_id_servers.html

1.x will soon be removed. closing.

1.x will soon be removed. closing.


Add abseil-cpp dependency for cmake to fix windows build failure

Creating a tentative pull request to test this on a windows machine

abseil-cpp has a dependency on cctz, so the build still fails with the error cctz not found.
CMake Error at CMake/AbseilHelpers.cmake:153 (message):
ABSL: compiling absl requires a cctz CMake target in your project,
                see CMake/README.md for more details

I tried to add cctz package in CMakeLists.txt as another external project. Though cctz compiled successfully, find_package in abseil-cpp still fails to find cctz package with the error above.

Thanks for looking into this. yes, you are right about the cctz package dependency. I also ran into the same issue but found that abseil-cpp does not use find_package making it unfeasible to use ExternalProject in CMake. See discussion in https://github.com/abseil/abseil-cpp/issues/80
I will close this PR and will wait for that issue to get resolved. For now, I have removed the dependency on absl in this commit. https://github.com/tensorflow/tensorflow/commit/e7ad6ec4267f1f79ee7d9f558c8a008746682959.


doc structure is illogical

The top level doc structure is illogical, and contains a few other niggles. Here it is
    Introducing Weave Net
    Weave Features
    Installing Weave Net
    Operational Guide
    Using Weave Net – Example
    IP Addresses, Routes and Networks
    Setting Up The Weave Net Docker API Proxy
    Using Fast Datapath
    Using the Weave Net Docker Network Plugin
    Encryption and Weave Net
    How Weave Net Works
    Address Allocation with IP Address Management (IPAM)
    Using WeaveDNS
    Using Weave with Systemd
    Weave Net FAQ
    Troubleshooting Weave Net
    Building Weave Net

Issues:

Introducing Weave Net should just be Introduction
Weave Features should just be Features
Installing Weave Net should just be Installation
Operational Guide should be Operation
Using Weave Net - Example should be just Using Weave Net
IP Addresses, Routes and Networks does not belong at the top level; not sure where it should go; perhaps the Ops Guide or How It Works
Using Fast Datapath should not be at the top level; not sure where it should go; perhaps the Ops Guide
Setting Up the Weave Net Docker API Proxy should just be Docker API Proxy
Using the Weave net Docker Nework Plugin should just be Docker Network Plugin
Encryption and Weave Net should just be Encryption and it should not be at the top level; not sure where it should go; perhaps the Ops Guide
How Weave Net Works should come later
Address Allocation with IP Address Management (IPAM) should just be IP Address Allocation
Using WeaveDNS should be Naming and Discovery
Using Weave with Systemd does not belong at the top level; Ops Guide is probably the right place for it
Weave Net FAQ should just be FAQ
Troubleshooting Weave Net should just be Troubleshooting

So, with all the above changes applied, here's how the top level would look like
    Introduction
    Features
    Installation
    Operation
    Using Weave Net
    Docker API Proxy
    Docker Network Plugin
    IP Address Allocation
    Naming and Discovery
    How Weave Net Works
    FAQ
    Troubleshooting
    Building Weave Net

Convention for titles is to be action orientated, hence the change:
http://writers.stackexchange.com/questions/1545/verb-tense-for-technical-document-titles

Convention for titles is to be action orientated

Ok, but a) 7 of the 17 titles weren't like that, and b) it looks really clumsy to have a whole bunch of "Using ..." titles.

This is a bit late to be talking about this now, i.e. two days before the release.  Change it, then.

Is this a mis-match between what the menu should say and what the doc titles should say?
When you're looking at a "Weave Net" page, it's obvious what the "FAQ" is about, but once you navigate to that page you need the full context.

The pages still have the Menu at the left, so I think context is fairly obvious. Though I've just noticed that it says "Net 1.5 Documentation" instead of "Weave Net 1.5 Documentation".

This is all fine, but I wished you had looked at that extensive planning document that I did about four months ago when I began this, and commented on that before we started re-jigging the entire structure  two days before a release.

Action-oriented titles for all but one...
    Introducing Weave Net
    Exploring Weave Net Features
    Installing Weave Net
    Operating Weave Net
    Using Weave Net
    Integrating with Docker through the Docker API Proxy
    Integrating with Docker through the Docker Network Plugin
    Allocating IP Addresses
    Naming and Discovering Containers and Services
    Understanding how Weave Net Works
    FAQ
    Troubleshooting Weave Net
    Building Weave Net

(far too many Weave Nets in that for my liking, but at least there is only one "Using")

That looks good.  I think you have a long technical writing career ahead of you   :+1:
(Agree there are too many 'Using'.)   I think those Integrating titles might be a bit long, and won't look great in the menu, so perhaps we could shorten those a bit.  Keep in mind that changing the titles will change URLs, so we'll have to fix the links again.

(Agree there are too many 'Using'.)

I think you mean 'Weave Net', of which, sadly, there are eight; there is only one 'Using' left.

those Integrating titles might be a bit long, and won't look great in the menu, so perhaps we could shorten those a bit.

Done

Keep in mind that changing the titles will change URLs, so we'll have to fix the links again.

That is not the case. URLs are based on the file/directory names, not the titles.

For SEO reasons, it's good to have the product name in your titles, but I see your point.
In Wordpress, the urls are based on the titles of the doc, but yes, we're doing it differently with the plugin by transforming .md file names to a URL.
And personally I'm not sure that "naming and discovery" is something a user is going to search on with regards to Weave.
They will search for 'WeaveDNS' or "weave and DNS", so what's the problem with calling the feature what it is? That was one of the things I was trying to achieve. Same with IPAM, it's a thing that people know and understand, so I don't understand the rationale in shrouding it in an euphemism.

They will search for 'WeaveDNS' or "weave and DNS"

They will only do that if they know something about Weave already. DNS is just one of many ways to do service discovery. So "naming and discovery" is what you want to do, and "weaveDNS" is the component in weave that deals with it, but there is no for you to know that unless you already know about weaveDNS.

Same with IPAM, it's a thing that people know and understand

It's a very obscure term, actually.
We could have something like
    Allocating IP Addresses with IPAM
    Naming and Discovering Containers and Services with weaveDNS

but a) that is rather long, and b) IMO it just adds jargon that will confuse novices.

How about "Naming and Discovery with WeaveDNS"?  It's implied that we are talking about containers and services.
And then, "Address allocation with IP Address Management (IPAM)"  <--- this is still an active sentence which is what we're going for here.

They will only do that if they know something about Weave already. DNS is just one of many ways to       do service discovery.

What other methods are there besides DNS to discover services?

How about "Naming and Discovery with WeaveDNS"? It's implied that we are talking about containers and services.

No, it is not implied. We could be talking about peers, for example.
Also, the above is not "active".

"Address allocation with IP Address Management (IPAM)" <--- this is still an active sentence which is what we're going for here.

I don't see how that is "active", based on the definition you linked to earlier. And the duplication of "Address" is awkward.
As I said, "IPAM" is jargon. So much so that went out of our way to not mention it in commands/options (e.g. we have --ipalloc-init not --ipam-init). I see no benefit in referring to it in the heading. In fact I would be happy if none of our docs mentioned it.

I don't think it's entirely necessary to say, "Exploring Weave Net Features", since there isn't anything that the user needs to do

True. That is also the case for "Introducing Weave Net" - it is not the reader that is doing the introducing.

"Feature Overview" is ok in this instance.

That is not active. Anyway...
    Introducing Weave Net
    Feature Overview
    Installing Weave Net
    Operating Weave Net
    Using Weave Net
    Integrating Docker via the API Proxy
    Integrating Docker via the Network Plugin
    Allocating IP Addresses
    Naming and Discovering Containers and Services
    Understanding how Weave Net Works
    FAQ
    Troubleshooting Weave Net
    Building Weave Net

What other methods are there besides DNS to discover services?

Links and injecting environment variables; which is what Docker used to do.
Service registries based on the likes of etcd or consul; there are plenty of articles extolling the virtues of that.


Addresses for entrances

Add a switch that enables an address form for an entrance.

Duplicate.

Maybe it's worth pinning a few of the most duplicated issues?


Fixed recent order time calculation

All relative time for recent order use round to ceil before, which introduce a error that time from recent order always goes faster by 1 minutes/hours/days/months. We should use around to floor which makes more sense.
Fixed: #265

:tada: This PR is included in version 2.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Hugo's personal page

Description
Hugo's Personal page

Additional Information

[x] I have read the contributing docs (if this is your first contribution)
[x] This is not a duplicate of any existing pull request

Related Issues
Closes #{issue number}
Note: If your changes are small and straightforward, you may skip the creation of an issue beforehand and remove this section. However, for medium-to-large changes, it is recommended to have an open issue for discussion and approval prior to submitting a pull request.
Your ENS/address:

Hi @hdevelopergit! It's nice to meet you and learn about you from your personal page. Here are a few small suggestions to make it even cleaner 🦾

I recommend including a screenshot of your personal page (and other UI changes you make in the future). It's much faster for a reviewer to see your changes in the body of your PR message than to have to clone your branch, yarn install, yarn start, open the page, etc. A reviewer will usually do all of that anyway to check other things, but it's a good habit to get into.

Please add a screenshot of your personal page to the PR message. Update it there and/or in future comments if you make additional commits that change the UI.

I love the way you use divs to separate your github, linkedin, and twitter. Clean look! I also appreciate the use of max-w-xl in your bio section.

In my opinion, you could go further to style the top section so it feels more "contained" (just like the social "cards" you made at the bottom) instead of text floating in a big background. Totally up to you, just an idea :)

Since you reuse the social media cards three times, you might consider refactoring the styling out as a single component that you invoke three times.

I think it's a good habit to practice, but again I'll leave it up to you if you're interested in the exercise.

I look forward to seeing what you buidl!

Hi @hdevelopergit! It's nice to meet you and learn about you from your personal page. Here are a few small suggestions to make it even cleaner 🦾

I recommend including a screenshot of your personal page (and other UI changes you make in the future). It's much faster for a reviewer to see your changes in the body of your PR message than to have to clone your branch, yarn install, yarn start, open the page, etc. A reviewer will usually do all of that anyway to check other things, but it's a good habit to get into.

Please add a screenshot of your personal page to the PR message. Update it there and/or in future comments if you make additional commits that change the UI.

I love the way you use divs to separate your github, linkedin, and twitter. Clean look! I also appreciate the use of max-w-xl in your bio section.

In my opinion, you could go further to style the top section so it feels more "contained" (just like the social "cards" you made at the bottom) instead of text floating in a big background. Totally up to you, just an idea :)

Since you reuse the social media cards three times, you might consider refactoring the styling out as a single component that you invoke three times.

I think it's a good habit to practice, but again I'll leave it up to you if you're interested in the exercise.

Was it intentional that you tag #20 in your PR? Your description doesn't explain what your personal page has to do with Mayowa's, so maybe that was an accident.

If so, please delete #20 from your PR message.

I look forward to seeing what you buidl!

Hi @derrekcoleman ! Nice too meet you. I will take into account what you say. To update the personal page I have to do a new pull request or I can update this one? Thanks!

@hdevelopergit all you have to do it push your next commit(s) to this same branch "hdevelopergit:2-PersonalPage". Those will automatically get added to this pull request and show up in this thread.

Hello @hdevelopergit! Nice to meet you
I was going through your socials and noticed that the LinkedIn link is broken. It is fixed if you add https:// at the beginning
hugoHomePageBug.mp4

Thanks Wilman. I've modified.

@hdevelopergit all you have to do it push your next commit(s) to this same branch "hdevelopergit:2-PersonalPage". Those will automatically get added to this pull request and show up in this thread.

Thanks @derrekcoleman I've done some modifications and pushed. Also I've added the image to the PR. Looking forward your approval. 😊

Thanks for adding the screenshot and trying out the refactor! Also shout out to @wildanvin for your well-documented support on this PR.
@carletex or @technophile-04, please merge when you get a chance (and/or give me write access to this repo 🙏)

Hey thanks @hdevelopergit, this is nice !! also thanks all for nice suggestions / discussion just added a couple of comments

Thanks for the great feedback, @technophile-04!
@hdevelopergit, as someone who is "not a web developer," I admire the way you're taking all of our feedback as a chance to learn new things and level up your skills. Try out Shiv's ideas and let us know how it goes!

Hey thanks @hdevelopergit, this is nice !! also thanks all for nice suggestions / discussion just added a couple of comments

thanks you 😊

Thanks for the great feedback, @technophile-04!
@hdevelopergit, as someone who is "not a web developer," I admire the way you're taking all of our feedback as a chance to learn new things and level up your skills. Try out Shiv's ideas and let us know how it goes!

thanks @derrekcoleman for your words 😊 Well, I want to learn. And challenges are a funny way to learn! Altough I must admit I'm a bit anxius to get my personal page approved. 🥺🤣

Nice and clean!! Thanks @hdevelopergit ! and also others for great suggestions !

Thanks @technophile-04 ! I'm happy with my first merge 🥳
Now I can delete the branch correct? The fork I guess should continue open for next branches.
Thanks also @derrekcoleman and @wildanvin for help and suggestions!


Given...

\answer needs to do
\notgiven after given
here

The bad behavior is:
[
\answer[given]{2} \qquad \answer{2}
]
Will present both (and all following) as given, as opposed to just the first, which is the correct behavior.

Would it be better to make the "given" a key-value pair with default to "given=false" so that it must be over-ridden with "given=true" in order to actually have the "given" flag apply?


Don't call onCompleted() for the asRows observable when it is unsubscribed

Thanks! In the future, be sure to submit commits as separate PRs using branches.


Error 'numpy' has no attribute 'float'

Hello there, I just tried out your example workflows and ran into this error:

Error occurred when executing UVR5Node:
module 'numpy' has no attribute 'float'.
np.float was a deprecated alias for the builtin float. To avoid this error in existing code, use float by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use np.float64 here.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
File "D:\VER_13_AI\ComfyUI\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "D:\VER_13_AI\ComfyUI\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "D:\VER_13_AI\ComfyUI\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\custom_nodes\uvr.py", line 80, in split
vocals, instrumental, input_audio = model.run_inference(audio_path,format=kwargs.get("format"))
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\uvr5_cli.py", line 53, in run_inference
return_dict = self.model.run_inference(audio_path)
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\lib\separators.py", line 244, in run_inference
return_dict = self.process_audio(y_spec_m,v_spec_m,input_high_end,input_high_end_h)
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\lib\separators.py", line 181, in process_audio
pool.apply(self.process_vocals, args=(v_spec_m,input_high_end,input_high_end_h,return_dict))
File "multiprocessing\pool.py", line 360, in apply
File "multiprocessing\pool.py", line 774, in get
File "multiprocessing\pool.py", line 125, in worker
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\lib\separators.py", line 152, in process_vocals
wav_vocals = spec_utils.cmb_spectrogram_to_wave(
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\lib\uvr5_pack\spec_utils.py", line 330, in cmb_spectrogram_to_wave
wave = librosa.resample(spectrogram_to_wave(spec_s, bp['hl'], mp.param['mid_side'],mp.param['mid_side_b2'], mp.param['reverse']), orig_sr=bp['sr'], target_sr=sr, res_type=wav_resolution)
File "D:\VER_13_AI\ComfyUI\ComfyUI\custom_nodes\Comfy-RVC\lib\uvr5_pack\spec_utils.py", line 269, in spectrogram_to_wave
wave_left = librosa.istft(spec_left, hop_length=hop_length)
File "D:\VER_13_AI\ComfyUI\python_embeded\lib\site-packages\librosa\util\decorators.py", line 88, in inner_f
return f(*args, **kwargs)
File "D:\VER_13_AI\ComfyUI\python_embeded\lib\site-packages\librosa\core\spectrum.py", line 394, in istft
dtype = util.dtype_c2r(stft_matrix.dtype)
File "D:\VER_13_AI\ComfyUI\python_embeded\lib\site-packages\librosa\util\decorators.py", line 88, in inner_f
return f(*args, **kwargs)
File "D:\VER_13_AI\ComfyUI\python_embeded\lib\site-packages\librosa\util\utils.py", line 2185, in dtype_c2r
np.dtype(complex): np.dtype(np.float).type,
File "D:\VER_13_AI\ComfyUI\python_embeded\lib\site-packages\numpy_init_.py", line 338, in getattr
raise AttributeError(former_attrs[attr])

I've installed through the comfyui manager and after I got this error I manually went to the custom node location and installed its requirements with:
pip install -r requirements.txt
which results in another error, because of using python 3.12

ERROR: Failed building wheel for faiss-cpu

So I've done this instead:
py -3.10 -m pip install -r requirements.txt
and it installed without issues.
After successfully installing the requirements it still results in the same numpy error when running the workflow. All nodes and the manager are up to date of course.
Thank you very much in advance and for implementing RVC in comfy!

Looks like the error is due to this: https://github.com/Anjok07/ultimatevocalremovergui/issues/1016#issuecomment-1868489252
Try downgrading numpy to <1.24 and let me know if that works.

I've tried manually downgrading to 1.23, but it ran into the same error. But then I installed your new updated version and it didn't throw the float error anymore. So thanks for the fix!


Start to use GetURL on Addressable instead of assuming Hostname.

Fixes #475
Proposed Changes

Use Addressable's GetURL method, rather than assuming hostname.

This is a port of knative/eventing#1296.

Release Note

Knative Serving 0.7 Services work as importer sinks.

generally wondering, what best to avoid some of this code duplications, here and eventing (core)

@Harwayne in 477, I had to (similar to Matt) also fix some of the URI expectations, on the tests

In v1beta1 GetURL goes away.
On Fri, Jun 28, 2019, 4:09 AM Matthias Wessendorf<EMAIL_ADDRESS>wrote:

@Harwayne https://github.com/Harwayne in 477, I had to (similar to
Matt) also fix some of the URI expectations, on the tests
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/knative/eventing-contrib/pull/476?email_source=notifications&email_token=AHWPD4EUXBLMO3JY2TAAZMDP4XWPDA5CNFSM4H4BAQSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYZZHEI#issuecomment-506696593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHWPD4ETK2YC3RTHTBEQEMDP4XWPDANCNFSM4H4BAQSA
.


Search button on sites page ignores language setting

Description:
When setting the language to french, and then back to English, the search button on the program sites page does not get set back to English.
Please see attached image.
Steps to Reproduce:

Login to Tola-Activity
Click Settings, change to french
Select Tola-Data Test program
Click View Program Sites on left hand side of the page
View search button above map, confirm in french
Click settings, change back to English
Return to program site page

Results:
Search button does not return to English, remains in french
Expected Results:
All displayed language is in English, as set by the user.
Attachments:

QA Verified:

Issue no longer persists as written.
Media:

QA Verified:

Issue no longer persists as written


missing jira tickets user-actions

see the following:
previously we got the following events(see screenshot), after changing the events to use the user-action we don't get them any more, its is used by some dashboard

Closed as not reproduced


Verify the backfilled account metadata is the same the it's in znode.

This is a cli tool to verify that the backfilled account metadata (one machine is configured to push all the new versions of account service to ambry server).

Codecov Report

Merging #1263 into master will decrease coverage by 0.26%.
The diff coverage is 5.62%.

@@             Coverage Diff              @@
##             master    #1263      +/-   ##
============================================
- Coverage     72.35%   72.08%   -0.27%
+ Complexity     6160     6157       -3
============================================
  Files           444      445       +1
  Lines         35364    35518     +154
  Branches       4491     4504      +13
============================================
+ Hits          25586    25602      +16
- Misses         8602     8741     +139
+ Partials       1176     1175       -1

Impacted Files
Coverage Δ
Complexity Δ

...ry/account/AccountServiceTransitionVerifyTool.java
0% <0%> (ø)
0 <0> (?)

...m.github.ambry.clustermap/HelixClusterManager.java
86.35% <100%> (+0.1%)
42 <0> (ø)
:arrow_down:

....github.ambry/config/HelixPropertyStoreConfig.java
100% <100%> (ø)
1 <0> (ø)
:arrow_down:

...va/com.github.ambry/account/AccountUpdateTool.java
23.27% <100%> (ø)
6 <0> (ø)
:arrow_down:

.../main/java/com.github.ambry.store/ScanResults.java
81.25% <0%> (-1.57%)
16% <0%> (-1%)

...ava/com.github.ambry.router/NonBlockingRouter.java
77.26% <0%> (-0.52%)
51% <0%> (-1%)

...rc/main/java/com.github.ambry.store/BlobStore.java
89.53% <0%> (-0.47%)
94% <0%> (-2%)

...src/main/java/com.github.ambry.commons/BlobId.java
93.52% <0%> (-0.36%)
71% <0%> (-1%)

...in/java/com.github.ambry.network/SocketServer.java
84.29% <0%> (+0.41%)
15% <0%> (ø)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Update playsample.js

this change updates playsample.js to allow the two samples to work independently. Now, they have independent functionalities and one won't stop the other on clicking.

@kasaby can you include #33 here ?

Done.

Changes were deployed: https://speech-to-text-demo.mybluemix.net/
@kasaby make sure you follow this style guide when writing javascript.

fixes #32


nomacs cannot drag

Hyprland Version
Hyprland, built from branch main at commit 0dbd9970031940b50f9cce4c88989c2830d2a15f dirty (input: Various constraint handling fixes (3381)). Tag: v0.29.1-95-g0dbd9970
Bug or Regression?
Bug
Description
I'm using nomacs and I just realized I cannot correctly crop images with Hyprland. The dragging of the cropping box is interupted.
This does not happen on sway, where the dragging of the zone works fine.


Documentation does not specify if rules are enabled by default

I cannot find any information about whether rules are enabled by default or not. It would be good to clarify.

Hi! We have in our README: This repo doesn't exports a "recommended" set of rules - feel free to recommend us!
(https://github.com/dotansimha/graphql-eslint#available-rules)
But I'll update it to be more clear. Thanks @therealgilles !


obs audio

guys hope you can help, im picking the streamwall audio upvia desktop audio in obs, is there anyway streamwall can get its own audio so obs can pick it up seperatly?? i can now not talk in discord as the disocrd audio goes out to my twitch streams
when i was using only obs to manage the streams, i could talk in disocrd without the audio going out to the stream, have i missed something or does this need a fix?
also sent you money for a coffee, would love a soloution for sound fix, so if poss for obs to detect the streamwalls audio seperatly and notthourgh desktop audio??

I got around this in windows by selecting a virtual audio device in windows for the output of Streamwall. Then I just pick up that audio in OBS.

you are right, virtual audio device should cure that issue, thank you!


Crashing with Index out of bounds or range out of range for slice of length

This is a very cool product!
I setup a local test and when I do searches I randomly get index out of bounds error such as this:
thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-main 3/src/seekstorm/intersection.rs:936:38:
index out of bounds: the len is 521 but the index is 521
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::panicking::panic_bounds_check
3: seekstorm::intersection::intersection_docid::{{closure}}.4929
4: seekstorm::intersection::intersection_blockid::{{closure}}.4926
5: <alloc::sync::Arc<tokio::sync::rwlock::RwLockseekstorm::index::Index> as seekstorm::search::Search>::search::{{closure}}.4905
6: seekstorm_server::api_endpoints::query_index_api::{{closure}}.4893
7: seekstorm_server::http_server::http_request_handler::{{closure}}.4853
8: <hyper::server::conn::upgrades::UpgradeableConnection as core::future::future::Future>::poll
9: <hyper::server::server::new_svc::NewSvcTask as core::future::future::Future>::poll
10: tokio::runtime::task::core::Core<T,S>::poll
11: tokio::runtime::task::raw::poll
12: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
13: tokio::runtime::task::raw::poll
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
zsh: abort      RUST_BACKTRACE=1 ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020
or range end index out of range errors.
thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-main 3/src/seekstorm/utils.rs:103:28:
range end index 5970246 out of range for slice of length 2604
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::slice::index::slice_end_index_len_fail
3: seekstorm::intersection::intersection_docid::{{closure}}.4929
4: seekstorm::intersection::intersection_blockid::{{closure}}.4926
5: <alloc::sync::Arc<tokio::sync::rwlock::RwLockseekstorm::index::Index> as seekstorm::search::Search>::search::{{closure}}.4905
6: seekstorm_server::api_endpoints::query_index_api::{{closure}}.4893
7: seekstorm_server::http_server::http_request_handler::{{closure}}.4853
8: <hyper::server::conn::upgrades::UpgradeableConnection as core::future::future::Future>::poll
9: <hyper::server::server::new_svc::NewSvcTask as core::future::future::Future>::poll
10: tokio::runtime::task::core::Core<T,S>::poll
11: tokio::runtime::task::raw::poll
12: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
13: tokio::runtime::task::raw::poll
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
zsh: abort      RUST_BACKTRACE=1 ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020
Format of my data is like this:
{"address": "123 N 4TH ST, DUPO, IL", "postcode": "61234"}
{"address": "456 N 2ND ST, DUPO, IL", "postcode": "12345"}
{"address": "789 N 5TH ST, DUPO, IL", "postcode": "12345"}
I am new to Rust so I am having a bit of trouble figuring out the errors.  Thank you for your help I really appreciate it.

Thank you very much for the report.
It seems you were using the seekstorm server. Please help me to replicate the problem.
What parameters and schema did you use for the create_index API? What data did you index? What queries/parameters did you send to the server via the query_index API?
Having all the API requests in cURL/JSON format sent to the server before the exception would help to replicate and fix.
Thank you

Thank you for the quick reply.
Here are the steps I took.

I edited the ingest match in server.rs to change the schema to address and postcode.:

 "ingest" =>
                    {

                        let apikey_quota_object=ApikeyQuotaObject {..Default::default()};

                        let mut apikey_list_mut = apikey_list_clone.write().await;
                        let apikey_object=create_apikey_api(
                            &index_path,
                            apikey_quota_object,
                            &demo_api_key,
                            &mut apikey_list_mut,
                        );

                        let wikipedia_schema_json = r#"
                        [{"field":"address","field_type":"Text","stored":true,"indexed":true,"boost":10.0},
                        {"field":"postcode","field_type":"Text","stored":true,"indexed":true}]"#;
                        let schema = serde_json::from_str(wikipedia_schema_json).unwrap();

                        let index_id = create_index_api(
                            &index_path,
                            "wikipedia".to_string(),
                            schema,
                            SimilarityType::Bm25fProximity,
                            TokenizerType::UnicodeAlphanumeric,
                            apikey_object,
                        );

                        let apikey_hash = calculate_hash(&demo_api_key) as u128;
                        let apikey_object=apikey_list_mut.get(&apikey_hash).unwrap();
                        let index_arc=apikey_object.index_list.get(&index_id).unwrap();
                        let index_arc_clone=index_arc.clone();

                        drop(apikey_list_mut);

                        let data_path=if parameter.len()>1 {parameter[1]} else {"addresses.json"};
                        ingest_ndjson(index_arc_clone,data_path).await;

                        println!("Set the 'individual API key' in test_api.rest to '{}' when testing the REST API endpoints",demo_api_key_base64);
                    },

Then I ran cargo build --release

Next I ran ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020

Next I ran "ingest" , the import was successful.

as soon as I start typing in "123 Main St" It crashes at "123 Main S"  - when crashes it would give me this error:

thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-main 3/src/seekstorm/utils.rs:103:28:
range end index 1971674 out of range for slice of length 33632

this query "1234 maple ave chicago" would give me this error:

thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-main 3/src/seekstorm/intersection.rs:936:38:
index out of bounds: the len is 183 but the index is 183

Thank you very much for your help. The data is US addresses, I have emailed the link with the full dataset and my SeekStorm directory with the index data as well.

Thank you for all the information.
The UI is hard-wired for the Wikipedia demo schema (which you have changed).
To display fields from a modified schema you need to edit /src/seekstorm_server/web/js/master.js (and possibly   /src/seekstorm_server/web/index.html  ) before building as well.
I should have mentioned this in the readme or made the UI universal for any schema.
line 92
$.ajax({
    url: QUERY_URL,
    data: JSON.stringify({
       query: query,
       offset: (page - 1) * 10,
       length: 10,
       realtime: true,
       highlights: [
        { field: "address", fragment_number: 0, fragment_size: 1000, highlight_markup: true},
        { field: "postcode", fragment_number: 2, fragment_size: 160, highlight_markup: true},
        { field: "postcode", name: "body2", fragment_number: 0, fragment_size: 4000, highlight_markup: true}]
    }),

line 131

			${element.address}

${element.postcode}

${element.url}

line 143
      newEntry.hover(() => {
        moveSplitter(newEntry[0].getBoundingClientRect().y);
        prevUrl.html(element.url);
        prevTitle.html(element.address);
		    prevText.html(element.body2.replace(new RegExp("\r", "gi"), "
"));
      });

This fixes the UI problem.

I will continue to investigate the crash

Thank you for the UI tips, I edited and it looks great now. Looking forward for the crash fix.

Before the next public release I need to do some more testing.
But as a quick fix you can apply the following changes:
Change in src/seekstorm/intersection.rs line 234
from
query_list_item_mut.p_run_sum =
    if query_list_item_mut.compression_type == CompressionType::Rle {
        read_u16(
            query_list_item_mut.byte_array,
            query_list_item_mut.compressed_doc_id_range + 4,
        )
        .into()
    } else {
        0
    };

to
query_list_item_mut.p_run_sum =
    if query_list_item_mut.compression_type == CompressionType::Rle {

  query_list_item_mut.p_run_count = read_u16(
            query_list_item_mut.byte_array,
            query_list_item_mut.compressed_doc_id_range,
        ) as i32;

        read_u16(
            query_list_item_mut.byte_array,
            query_list_item_mut.compressed_doc_id_range + 4,
        )
        .into()
    } else {
        0
    };

and change in src/seekstorm/intersection.rs line 1347
from
continue 'start;

to
continue 'restart;

Thank you!!! It works perfectly now.

Update: I get index out of bounds for some queries. Will do further testing and report back with the details. Thanks.

Commit ade2041 fixed the issue

Update: I get index out of bounds for some queries. Will do further testing and report back with the details. Thanks.

Yes, there is an exception when searching a term with 65.536 postings per block, e.g. when searching 'oh' in your test index.
But that is an unrelated problem I will fix in an separate commit.
Please let me know your findings.

The following change in src/seekstorm/index_posting.rs line 146
from
let mut posting_pointer_size = if value.size_compressed_positions_key < 32_768 {
    value.pointer_pivot_p_docid = value.posting_count as u16 + 1;
    2u8
} else {
    3u8
};

to
let mut posting_pointer_size = if value.size_compressed_positions_key < 32_768 && value.posting_count<65_535 {
    value.pointer_pivot_p_docid = value.posting_count as u16 + 1;
    2u8
} else {
    3u8
};

should fix the out of bounds. Unfortunately this is a breaking change that requires reindexing!
Please let me know if the fix works for you. Thanks.

Thank you for the updated code, it has fixed the issue for some queries. I still have two diffrent errors I encountered for the following queries. I did delete and reindex the data before running the queries.
Query 1: 123 Main St
Query  CURL: curl --location 'http://<IP_ADDRESS>:8020/api/v1/index/0/query?query=123%20Main%20St&offset=0&length=10' \ --header 'Content-Type: application/json' \ --header 'apikey: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA='
Query 1 Error: `andy@Andys-iMac release % RUST_BACKTRACE=full ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020
SeekStorm server v0.6.1 starting ...
Hit CTRL-C or enter 'quit' to shutdown server
opening index ...
index.bin name wikipedia id 0 version 3.2 3.2 level 1999 fields 2 2 facets 0 docs 130,987,896 deleted 0 segments 2048 time 0 s
Listening on: <IP_ADDRESS> 8020 index dir /Users/andy/Downloads/SeekStorm-0.6.1/target/release/seekstorm_index master key XXXXXXXXXXXXXXXX=
thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-0.6.1/src/seekstorm/add_result.rs:1847:15:
index out of bounds: the len is 5638 but the index is<PHONE_NUMBER>3702146056
stack backtrace:
0:        0x10e7f425b - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::haf41a54e7ed5fe07
1:        0x10e22099b - core::fmt::write::h526161fad96c5ad5
2:        0x10e7c871e - std::io::Write::write_fmt::h4de0398536c8b0e4
3:        0x10e7f859a - std::panicking::default_hook::{{closure}}::hffeef89117b5d267
4:        0x10e7f80af - std::panicking::default_hook::h2f20b53f3264c5d5
5:        0x10e7f9e21 - std::panicking::rust_panic_with_hook::h7919e8c602131afa
6:        0x10e7f8f85 - std::panicking::begin_panic_handler::{{closure}}::h7bd628128f542977
7:        0x10e7f8ee9 - std::sys::backtrace::__rust_end_short_backtrace::ha2fdb908654ed930
8:        0x10e7f8ed3 - _rust_begin_unwind
9:        0x10e8ca2d1 - core::panicking::panic_fmt::h292eaa4d42e451fa
10:        0x10e8ca3b6 - core::panicking::panic_bounds_check::h1d1822a2cd031b6c
11:        0x10e48acf6 - seekstorm::intersection::intersection_docid::{{closure}}::h7d84a1dff17a2fcd.4858
12:        0x10e43b148 - seekstorm::intersection::intersection_blockid::{{closure}}::h439a6ccfcecdff2e.4855
13:        0x10e432979 - <alloc::sync::Arc<tokio::sync::rwlock::RwLockseekstorm::index::Index> as seekstorm::search::Search>::search::{{closure}}::h08e48db7c8a2f510.4834
14:        0x10e427c47 - seekstorm_server::api_endpoints::query_index_api::{{closure}}::h53d60e8d6a7c0511.4822
15:        0x10e418dc4 - seekstorm_server::http_server::http_request_handler::{{closure}}::he141cfb8d0bf4d8f.4782
16:        0x10e79d910 - <hyper::server::conn::upgrades::UpgradeableConnection as core::future::future::Future>::poll::hab84192b8917d816
17:        0x10e1d3133 - <hyper::server::server::new_svc::NewSvcTask as core::future::future::Future>::poll::h6f113da6cc42bdf1
18:        0x10e569643 - tokio::runtime::task::core::Core<T,S>::poll::h666dfe94ceba2153
19:        0x10e1e0078 - tokio::runtime::task::raw::poll::h6be3611534d88a22
20:        0x10e7fbe8d - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::h18a54404c6f874bd
21:        0x10e802902 - tokio::runtime::task::raw::poll::hc78e731e5702ed1f
22:        0x10e801164 - std::sys::backtrace::__rust_begin_short_backtrace::hb47b7926120e2886
23:        0x10e800fa4 - core::ops::function::FnOnce::call_once{{vtable.shim}}::ha71ab310b607c26d
24:        0x10e7fb03b - std::sys::pal::unix::thread::Thread::new::thread_start::hcd19cc58b6db093a
25:     0x7ff80450a18b - __pthread_start
zsh: abort      RUST_BACKTRACE=full ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020`
Query 2: 1443 maple a
CURL for query 2: curl --location 'http://<IP_ADDRESS>:8020/api/v1/index/0/query?query=1443%20maple%20a&offset=0&length=10' \ --header 'Content-Type: application/json' \ --header 'apikey: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA='
Error for Query 2: `andy@Andys-iMac release % RUST_BACKTRACE=full ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020
SeekStorm server v0.6.1 starting ...
Hit CTRL-C or enter 'quit' to shutdown server
opening index ...
index.bin name wikipedia id 0 version 3.2 3.2 level 1999 fields 2 2 facets 0 docs 130,987,896 deleted 0 segments 2048 time 0 s
Listening on: <IP_ADDRESS> 8020 index dir /Users/andy/Downloads/SeekStorm-0.6.1/target/release/seekstorm_index master key XXXXXXXXXXXXXX=
thread 'tokio-runtime-worker' panicked at /Users/andy/Downloads/SeekStorm-0.6.1/src/seekstorm/intersection.rs:1683:37:
index out of bounds: the len is 704 but the index is 1023
stack backtrace:
0:        0x102a5825b - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::haf41a54e7ed5fe07
1:        0x10248499b - core::fmt::write::h526161fad96c5ad5
2:        0x102a2c71e - std::io::Write::write_fmt::h4de0398536c8b0e4
3:        0x102a5c59a - std::panicking::default_hook::{{closure}}::hffeef89117b5d267
4:        0x102a5c0af - std::panicking::default_hook::h2f20b53f3264c5d5
5:        0x102a5de21 - std::panicking::rust_panic_with_hook::h7919e8c602131afa
6:        0x102a5cf85 - std::panicking::begin_panic_handler::{{closure}}::h7bd628128f542977
7:        0x102a5cee9 - std::sys::backtrace::__rust_end_short_backtrace::ha2fdb908654ed930
8:        0x102a5ced3 - _rust_begin_unwind
9:        0x102b2e2d1 - core::panicking::panic_fmt::h292eaa4d42e451fa
10:        0x102b2e3b6 - core::panicking::panic_bounds_check::h1d1822a2cd031b6c
11:        0x1026ec4cb - seekstorm::intersection::intersection_docid::{{closure}}::h7d84a1dff17a2fcd.4858
12:        0x10269f148 - seekstorm::intersection::intersection_blockid::{{closure}}::h439a6ccfcecdff2e.4855
13:        0x102696979 - <alloc::sync::Arc<tokio::sync::rwlock::RwLockseekstorm::index::Index> as seekstorm::search::Search>::search::{{closure}}::h08e48db7c8a2f510.4834
14:        0x10268bc47 - seekstorm_server::api_endpoints::query_index_api::{{closure}}::h53d60e8d6a7c0511.4822
15:        0x10267cdc4 - seekstorm_server::http_server::http_request_handler::{{closure}}::he141cfb8d0bf4d8f.4782
16:        0x102a01910 - <hyper::server::conn::upgrades::UpgradeableConnection as core::future::future::Future>::poll::hab84192b8917d816
17:        0x102437133 - <hyper::server::server::new_svc::NewSvcTask as core::future::future::Future>::poll::h6f113da6cc42bdf1
18:        0x1027cd643 - tokio::runtime::task::core::Core<T,S>::poll::h666dfe94ceba2153
19:        0x102444078 - tokio::runtime::task::raw::poll::h6be3611534d88a22
20:        0x102a5fe8d - tokio::runtime::scheduler::multi_thread::worker::Context::run_task::h18a54404c6f874bd
21:        0x102a66902 - tokio::runtime::task::raw::poll::hc78e731e5702ed1f
22:        0x102a65164 - std::sys::backtrace::__rust_begin_short_backtrace::hb47b7926120e2886
23:        0x102a64fa4 - core::ops::function::FnOnce::call_once{{vtable.shim}}::ha71ab310b607c26d
24:        0x102a5f03b - std::sys::pal::unix::thread::Thread::new::thread_start::hcd19cc58b6db093a
25:     0x7ff80450a18b - __pthread_start
zsh: abort      RUST_BACKTRACE=full ./seekstorm_server local_ip="<IP_ADDRESS>" local_port=8020
`
What is interesting is if I add or remove characters from search query, there is no problems. Example "1443 maple av" and "1443 maple" queries work with no problem but "1443 maple a" crashes. Same with "123 main" and "123 main st chicago" works but crashes on "123 main st" .

Exceptions should be fixed with commit afd2e8f (all relevant changes are within intersection.rs).
Please let me know if the fix works for you. Thanks.

Thank you very much! This has resolved the crashes. It works smoothly now. I really appreciate your help.

I appreciate your support in fixing the issue!


DCJ-638: Remove old approved users API

Addresses
https://broadworkbench.atlassian.net/browse/DCJ-638
Summary
Minor cleanup of the unused, original download dataset approved users endpoint

Have you read CONTRIBUTING.md lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

Looks good but there are a few changes that look like they'd be reformatted following a linter run, would you mind running that?
More generally, what would you think about putting a lint check in PRs?

@okotsopoulos - I created https://broadworkbench.atlassian.net/browse/DCJ-646 for this suggestion, thank you! I'll reformat this PR after rebasing from other changes.


Mame titles not scraping (fix included)

Hey sselph.
I love this program, it makes it so much easier to scrape than via EmualtionStation,  I came across one issue and that was the title screen scraping for mame did not return any results, I have found the culprit in the source and recomplied and it worked perfect after the changes,
Might be worth considering to make the changes on the main branch.
In mamedb.go change the following,

Line 34, replace:
	titleImgRE   = regexp.MustCompile("<img src='/title/(.*?)\\.png'")
With:
	titleImgRE   = regexp.MustCompile("<img src='/titles/(.*?)\\.png'")

Hope this helps someone out :)
Mongo

Thanks. I incorporated the fix into the master branch and will roll out a fix to the binaries.


Sort featured July #12in23 exercises into the tree

Users who chose to do learning mode can see the featured exercises in the tree.
I did all five exercises with the minimum of tools available and came to the sorting seen in the config.json file.
This is what I came up with:
Bob

loops
strings

Allergies

classes
std::unordered_set
string
const
reference
unsigned

Reverse String

string
const
reference
loops

High Scores

Classes
vector
size_t
iterators

Armstrong Numbers

loops
includes

Some of these concepts are not yet in the tree, so I will make another PR to add to their instructions about what challenges may lay ahead of the students.

I also removed some of the beta status for the exercises, so the non-maintaining user can see them.


Add pydoc for BaseSensor

Very tiny cosmetic change for better IDE support when writing new Sensors

+1

Again cleaned my messy history of commits with force push

Merged, thanks.


Support for OAuth2?

It's not quite clear in the documentation, I'm almost certain at 100% that this gem is only for OAuth1, is it the case ?
If yes, do you have any substitute for OAuth2? I will do a PR to update the README to clarify that important point.
Thank you!

https://github.com/intridea/omniauth-oauth2

omniauth is the core lib and omniauth-oauth2 is built off of that. Likewise, gems requiring OAuth2 are built off of omniauth-oauth2. Ex: omniauth-facebook and omniauth-github.


Receive Controller: UI improvements

[x] try adding "Your Address" somewhere so that it's clear to the user what that address string and QR code is for.

[x] the title for controller: instead of using coin symbol in title use it's name. So, the title for Bitcoin receive controller should be "Receive Bitcoin", not "Receive BTC"

@TalgatNurdinov consider it done1


GeometryArrayTrait::value() return Option

closes https://github.com/geoarrow/geoarrow-rs/issues/129.

As part of https://github.com/geoarrow/geoarrow-rs/pull/235, I'm aligning with the arrow-rs API, which panics if the index is out of range: https://docs.rs/arrow/latest/arrow/array/trait.ArrayAccessor.html#tymethod.value


Reserve Memory for type

In code-writers, we are looping through a range of type in types, and we emplace_back using that value.
For this reason, we should preallocate memory for the struct using reserve.

Done!

@kennykerr

/azp run


How do I customize the onSearchChange ?

Hello Allen.
Is there any way to customize the result of search field?
I want to customize a column of "Name" which its value is from "First Name" and "Last Name". For the view I customize it with dataFormat.
const customComponent = (cell, row) => (
  <span>{row.first_name} {row.last_name}</span>
)

const users = [
  { first_name: 'User', last_name: 'Test' },
  { first_name: 'User', last_name: 'Fake' },
  { first_name: 'User', last_name: 'Example' },
]

<BootstrapTable data={users} search>
  <TableHeaderColumn dataFormat={customComponent}>Name</TableHeaderColumn>
</BootstrapTable>

For the default the search is based on dataField and in this case it's not possible the dataField's value has like 'first_name last_name'. So how do I make the search to return value consist of first_name and last_name?

There're couple workarounds you can choose,

merge your source data with your expectation before you put them into table. ex:

const users = [
  { row: 'seq1', name: 'User Test' }
];

The dataField is a best to assign, so you can assign any field you like and use filterFormatted to tell react-bootstrap-table to filter/search that column with formatted data instead original data

<BootstrapTable data={users} search>
  <TableHeaderColumn dataField='first_name' dataFormat={customComponent} filterFormatted>Name</TableHeaderColumn>
</BootstrapTable>

use filterValue, you can also check https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/manipulation/search-format-table.js

Let me know if you have any questions, thanks

Hi Allen,
I want to implement remote search on react-bootstrap-table. I am using react-bootsttrap-table version 4.3.1. Currently we have onSearchChange method but i want onEnter event. Is there any way to do that?


Initilizing a Numpy structured array inside a jitclass constructor throws an error

This works:
from numba.experimental import jitclass
from numba import from_dtype
import numpy as np

values_dtype = np.dtype([
    ('one', 'U10'),
    ('two', 'f8')
])

class My_test:
    def __init__(self):
        self.values = values = np.empty(2, dtype=values_dtype)

my_test = My_test()
print(my_test.values)

But when jitting the class, it throws an error:
from numba.experimental import jitclass
from numba import from_dtype
import numpy as np

values_dtype = np.dtype([
    ('one', 'U10'),
    ('two', 'f8')
])

@jitclass([
    ('values', from_dtype(values_dtype))
])
class My_test:
    def __init__(self):
        self.values = values = np.empty(2, dtype=values_dtype)

my_test = My_test()
print(my_test.values)

Cannot cast unaligned array(Record(one[type=[unichr x 10];offset=0],two[type=float64;offset=40];48;False), 1d, C) to Record(one[type=[unichr x 10];offset=0],two[type=float64;offset=40];48;False): %".96" = load {i8*, i8*, i64, i64, [48 x i8]*, [1 x i64], [1 x i64]}, {i8*, i8*, i64, i64, [48 x i8]*, [1 x i64], [1 x i64]}* %"$12call_function_kw.5"
Any works arounds would be greatly appreciated!
Thanks :)
numba: 0.49.1
numpy: 1.18.4
python: 3.7.1

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Thanks for the issue report - it looks to me like the code is creating an array of record types with np.empty(2, dtype=values_dtype) and assigning it to self.values, which is declared as a record type. This works in Python because you don't need consistency between the different types that a variable can be assigned, but you do for compiled code. The error message is perhaps easier to interpret if you examine the types that it's casting from:
array(Record(one[type=[unichr x 10];offset=0],two[type=float64;offset=40];48;False), 1d, C)

and to:
Record(one[type=[unichr x 10];offset=0],two[type=float64;offset=40];48;False)

on separate lines.
However, my quick attempt to fix this, changing the jitclass values type with:
diff --git a/repro.py b/repro.py
index 2e1ba82..d8a43fd 100644
--- a/repro.py
+++ b/repro.py
@@ -8,7 +8,7 @@ values_dtype = np.dtype([
 ])

 @jitclass([
-    ('values', from_dtype(values_dtype))
+    ('values', from_dtype(values_dtype)[:])
 ])
 class My_test:
     def __init__(self):

to declare values as an array rather than a record, results in another traceback:
Traceback (most recent call last):
  File "repro.py", line 18, in <module>
    print(my_test.values)
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 1506, in _array_str_implementation
    return array2string(a, max_line_width, precision, suppress_small, ' ', "")
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 712, in array2string
    return _array2string(a, options, separator, prefix)
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 484, in wrapper
    return f(self, *args, **kwargs)
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 517, in _array2string
    lst = _formatArray(a, format_function, options['linewidth'],
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 838, in _formatArray
    return recurser(index=(),
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 794, in recurser
    word = recurser(index + (-i,), next_hanging_indent, next_width)
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 748, in recurser
    return format_function(a[index])
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 1294, in __call__
    str_fields = [
  File "/home/gmarkall/miniconda3/envs/numba/lib/python3.8/site-packages/numpy/core/arrayprint.py", line 1294, in <listcomp>
    str_fields = [
UnicodeDecodeError: 'utf-32-le' codec can't decode bytes in position 0-3: code point not in range(0x110000)

I'm looking into this next traceback now.

Ah, never mind - the traceback is because it was printing uninitialized memory from np.empty. The following works:
from numba.experimental import jitclass
from numba import from_dtype
import numpy as np

values_dtype = np.dtype([
    ('one', 'U10'),
    ('two', 'f8')
])

@jitclass([
    ('values', from_dtype(values_dtype)[:])
])
class My_test:
    def __init__(self):
        self.values = values = np.zeros(2, dtype=values_dtype)

my_test = My_test()
print(my_test.values)

producing:
[('', 0.) ('', 0.)]

@gmarkall Thank you so much for your quick reply and help! :)


Problems with CouchRest hitting CouchDB through a proxy

The Set-Up
We have a simple ruby app where we allow for a proxy to be set on the CouchRest database:
  def self.database
    CouchRest.proxy(AppConfig.database.proxy_uri) if AppConfig.database.use_proxy?
    @db ||= CouchRest.database(AppConfig.database.uri)
  end

Everything works fine if we don't use the proxy. It's when we start to use the proxy, and move a lot of data through the client that we get into trouble.
We're doing one at a time - not using the bulk_save call, if that matters at all.
We are using JRuby <IP_ADDRESS>, again, if that matters.
The Problem
When we're pushing about 4000 documents to the remote, proxied, CouchDB, we get about half way through the set and then get the following exception:
Errno::ECONNREFUSED: Connection refused - Connection refused
                          initialize at org/jruby/ext/socket/RubyTCPSocket.java:121
                                 new at org/jruby/RubyIO.java:876
                                open at org/jruby/ext/socket/RubyTCPSocket.java:147
                             connect at /Users/bbeaty/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/1.9/net/http.rb:644
                             timeout at org/jruby/ext/Timeout.java:79
                             connect at /Users/bbeaty/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/1.9/net/http.rb:644
                            do_start at /Users/bbeaty/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/1.9/net/http.rb:637
                               start at /Users/bbeaty/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/1.9/net/http.rb:626
                               start at /Users/bbeaty/.rvm/rubies/jruby-<IP_ADDRESS>/lib/ruby/1.9/net/http.rb:625
                            transmit at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/rest-client-1.6.7/lib/restclient/request.rb:172
                             execute at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/rest-client-1.6.7/lib/restclient/request.rb:64
                             execute at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/rest-client-1.6.7/lib/restclient/request.rb:33
                             execute at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/couchrest-1.1.3/lib/couchrest/rest_api.rb:94
                                post at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/couchrest-1.1.3/lib/couchrest/rest_api.rb:55
                            save_doc at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/couchrest-1.1.3/lib/couchrest/database.rb:141
                            save_doc at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/couchrest-1.1.3/lib/couchrest/database.rb:139
                               store at /Users/bbeaty/Developer/quantum-lead/lib/database.rb:34
                             process at /Users/bbeaty/Developer/quantum-lead/lib/quantum_lead.rb:79
                                each at org/jruby/RubyArray.java:1615
                             process at /Users/bbeaty/Developer/quantum-lead/lib/quantum_lead.rb:78
              process_with_new_relic at /Users/bbeaty/Developer/quantum-lead/lib/new_relic.rb:21
  perform_action_with_newrelic_trace at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/newrelic_rpm-3.4.1/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:262
              trace_execution_scoped at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/newrelic_rpm-3.4.1/lib/new_relic/agent/method_tracer.rb:242
  perform_action_with_newrelic_trace at /Users/bbeaty/.rvm/gems/jruby-<IP_ADDRESS>@quantum-lead/gems/newrelic_rpm-3.4.1/lib/new_relic/agent/instrumentation/controller_instrumentation.rb:257
              process_with_new_relic at /Users/bbeaty/Developer/quantum-lead/lib/new_relic.rb:20
                              (root) at bin/process.rb:12

It appears that we're getting a timeout, and then trying to reconnect and getting the 'Connection Refused'. This isn't the first send in the 4000, but it never makes it through the complete set of 4000 without this error.
Any help would be greatly appreciated.

Okay, this is old! Sounds like a proxy issue, but the new HTTPClient has proxy support that should work. Closing this issue.