What is the different between your model and other mobilenet model?

Hi, I run your project using mobinet v1.  But the speed is only a half compare to your model. When I tried mobinet v2, I got error. Therefore I want to ask What is the different between your model and other mobilenet model?
Second problem is:
when I used your .config file to train on Pascal VOC data, after training I got model file and do object detection using your code. But, got this error:
ValueError: graph_def is invalid at node u'Preprocessor/map/TensorArray_2': Input tensor 'Preprocessor/map/strided_slice:0' not found in graph_def. Any suggestion?? Thank you!

@GustavZ any suggestion?

hello @nvnnghia this project works with and only for ssd_mobilenet which is supplied by tensorflows object_detection model zoo.
The reason why is the following:
If you take a look at my code you see that it manually splits the model into two parts, one for gpu and one for cpu. This only works because it was manually investigated and HARD CODED where the exact layer names are that are good to use as a split point.
NOW: IF you use another model, that maybe has other layer names, even though it is a SSD MOBILENET, it won't work!
My hack/work is not scalable, but still you can reproduce it if you log the time of each layer and finf a point to split your model, but you need to code that by your own.
Unfortuantely there is no other way to do so.
If you want to know how to log your model with the time used in each layer, have a look at my other prokect realtime_segmentation and in this the file test.py, this file creates such a log file.
I hope i could make some things clear to you.

@nvnnghia  Hey, I'm looking to work on a similar project. I was wondering if you'd be interested in getting in contact with me so we could maybe discuss ways to get it working for mobilenet_v2.

yes, I'm interest to learn.

Hi, Do you think the splitting would work on faster-rcnn models? I tried finding a layer for splitting, but the layers after the splitting point are dependent on the ones before.

@azadef it could be possible, but it won’t be as straight forward / easy as with ssd.
But if you achieve it, it would be great to hear of you :)

@GustavZ Sure, will let you know if I succeed :)


from devito import *

Shouldn't we automatically import all or key sympy types when doing from devito import * , such as Eq, ...? Which is sort of the Devito language

Where do we have that?

I am not sure I understand why we would want that since pep8 recommends avoiding wildcard imports.

Because we are a super special case -- it's the magic statement you need to have the "Devito language(s)" at your full disposal
Same strategy adopted in FEniCS and Firedrake

I personally dislike namespace clutter so in my opinion this is a non-issue. But that's just me.

this is a non-issue

That's why I had marked it as question :) I however prefer the from devito import * (only because this is a special case, in user-land)

Fine, closing


Clear data on card.

Is there a way to clear the data saved on the card.

Which type of card do you use?
For example, with a DesFIRE EV1, you need to select the master app (and to authenticate) and then, send the formatPICC command
https://www.mifare.net/support/forum/topic/desfire-ev1-reset-to-factory-default/


A way to disable creation of connInfoSecret

We do our own Just-In-Time provisioning of serviceusers and credentials for our Aiven services, so we don't need or use the secret created by the Aiven Operator (the "connInfoSecret").
Every now and then, some enterprising developer notices that there exists a secret with the same name as the service instance and attempts to use the credentials stored in the connInfoSecret. We would rather that they didn't, and it would be useful if we could just disable the generation of the connInfoSecret entirely.
This is somewhat related to #472 , but while that suggests the operator should use an already existing secret, we want there to be no secret at all.

Hey, thanks for the idea.
I'm taking this to the sprint.


chore(lspkind): Update icons for consistency.

This commit update icons for lspkind (lspsaga) so that they stay consistent with cmp and navic.

Maybe you need to resolve the conflict then PR.

@ayamir We're all set 👍


Launch Plan: Mobile Replay

Mobile replay is pretty far along. It's worth throwing some light on it with a launch, IMO. However, since it's far along I don't think we need a Before/During/After launch plan - just a couple of initiatives to put a spotlight on it and help it flourish.
CC @marandaneto @pauldambra @ioannisj  @andyvan-ph @charlescook-ph
Best practices

Ensure the product has at least one customer story within 3 weeks of launch
Ensure we publish best practice content for the product and link to it from docs
Ensure that products have at least one pre-made template (or similar) for users
Ensure the product has at least one tutorial at launch
Ensure the product has a robust docs page, and product page if needed
Ensure the product is added to email and in-app onboarding flows

Launch plan

[x] Publish a mobile case study - @joethreepwood
[ ] Update session replay page to spotlight mobile functionality - @joethreepwood
[x] Blog post - @ivanagas
[ ] Changelog post announcing that mobile replay is now officially out of beta for both Android and iOS
[ ] Take the beta tags off - @joethreepwood
[ ] Potential newsletter about building our first Mobile product? - @andyvan-ph (could do well on HN?)
[x] Add mobile replay details (and links to mobile dashboard) to onboarding email flow - @joethreepwood
[x] Update G2 categories to include mobile replay categories - @joethreepwood
[ ] Add mobile replay link to footer - @joethreepwood
[ ] Email to all recently engaged users announcing that mobile replay is now available - @joethreepwood
[ ] Paid ads - @andyvan-ph / Hey Digital

Feedback and other ideas
All feedback and additional ideas from @marketing is appreciated.

We already wrote this blog FYI: https://posthog.com/blog/mobile-session-replay

What's the timeline to charging specifically for mobile replay? I figure that would be the point we'd want to do a bigger launch.

That'd be a @annikaschmid and @marandaneto question.
The big hit of this plan would be the email, and agree we should time it to coincide with this. Unless we decide to bill with normal replays.

That'd be a @annikaschmid and @marandaneto question.
The big hit of this plan would be the email, and agree we should time it to coincide with this. Unless we decide to bill with normal replays.

@pauldambra was gonna pair up with the growth team to figure out the final details about pricing, RFC, since we had an offsite, not sure if that happened.

@pauldambra @marandaneto Looping back on this: Are we basically good to set about announcing this now, or is pricing still being decided?


Restructuring causing merged style rules to be overwritten

Using<EMAIL_ADDRESS>with the following rules:
.button--black {
  color: tomato;
  border-color: black;
  border-bottom-color: rgba(0, 0, 0, .2);
}

.button--blue {
  color: tomato;
  border-color: blue;
  border-bottom-color: rgba(0, 0, 0, .2);
}

will be minified into the following (unminified for readability):
.button--black, .button--blue {
  color: tomato;
  border-bottom-color: rgba(0, 0, 0, .2);
}

.button--black {
  border-color: #000;
}

.button--blue {
  border-color: #00f;
}

See the border bottom color will be overwritten because the merged rule is moved aboved border-color:#000. While turning off restructuring the code works as intended, but is this considered a bug on clean-css?

It's a bug indeed! Fix is coming.

It's fixed in 3.4.21.


strange output time from these machines

Hi
i load and run the same recordcount on two machine (machine1: ci3 2G Ram , machine2:16core 32G Ram) but machine2 was slower , for example  run time with 2000 record on machine1 was 5s but on machine2 was 6s , why?

Hi Hadi - couple questions about your benchmark:

Which db are you using and is the db installed on the same machine as YCSB is running?
How many times did you run the benchmark on each machine type? What is the variance in your results?

my db is cassandra
as i said for machine1 run time was 5 second but for machine2 was 6 second.

OK - a few things.

It is generally advisable to run benchmarks several times and compare the results. You want to do this so that you can see if your results are consistent or not. So, I would suggest you run your benchmark on each machine a few times to make sure that you have consistent results and can build an average run time for each.
Runtimes of only 5-6s are tiny workloads. When you work with workloads that small ANY sized machine will likely perform at the same speed, there just isn't that much work to do. So, I would suggest you increase the size of the workloads.
Yes, 6 > 5, but not by much. As I said before your workloads are tiny, a difference in 1 second is not a good indicator that one machine is truly faster than the other.

you say correct but these two machine according their hardwares are not comparable
i bench mark with larger size of record count and will say result.

i do benchmark with 128000 record on machine1 114s on machine2 110s , i think ycsb on machine2 use only 1 core of cpu but while machin2 have 32G ram.

Can you post all of the parameters of the workload you are running?

bin/ycsb load cassandra2-cql -p hosts="localhost" -p recordcount=2000 -P workloads/workloada > ~/result/workload_res.txt
bin/ycsb run cassandra2-cql -p hosts="localhost" -p operationcount=2000 -P workloads/workloada > ~/result/workrun_res.txt

One note, if you are raising the recordcount, you still need to provide the correct recordcount in addition to the operationcount to the run command, so that the full range of keys are available for the operations.
I'm assuming that when you set the recordcount to 128000 that that means the operation count was also that value? You might want to rerun with both operationcount and recordcount being set on the run command.
At this point we won't really be able to tell you why one system is performing above another. We know nothing about the two systems you have setup. One thing you could do to make sure it is not YCSB as the bottleneck is to do a run command with a very high operationcount against the basic db. Compare the results you get from the two machines.

less than 2 minutes is still not enough time to get out of the JVM's warm up. I suggest you start with a run of 1 or 2 million records and operations.
note that by default YCSB only uses a single thread per client. you have to specify the {{-threads}} option to get more.

@kruthar if i got your opinion correctly , well generally we set recordcount on Load phase the same of operationcount on Run phase.

@busbey i think at least not should Runtime on machine2 bigger than Machin1 but while i benchmark with number of threads.

there are too many factors to say, especially with such a short run time. Frankly, I'm surprised you can run both a Cassandra server and a YCSB client on a machine with 2GiB of memory.

with 16 thread on machine2 run time was 13s , but loadtime is 76s that it is very much for this machine while on other machine Loadtime was 46s.

What does "cors" mean in this context?
76s is very short. are you doing the larger number of records / operations I suggested earlier?
please include the actual command lines you use when referencing the time it takes for particular runs.

ok , core of cpu
even i load on machine2 got this error(time out ) :
com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during write query at consistency ONE (1 replica were required but only 0 acknowledged the write)
Load command :
bin/ycsb load cassandra2-cql -p hosts="localhost" -p recordcount=1024000 -P workloads/workloada > ~/result/workload_res.txt

even i load on machine2 got this error(time out ) :
com.datastax.driver.core.exceptions.WriteTimeoutException: Cassandra timeout during write query at consistency ONE (1 replica were required but only 0 acknowledged the write)

This looks like misconfiguration of your cassandra cluster. you should first ensure your Cassandra cluster is correctly set up. Please see the cassandra website or their mailing list for help doing that.

Load command :
bin/ycsb load cassandra2-cql -p hosts="localhost" -p recordcount=1024000 -P workloads/workloada > ~/result/workload_res.txt

You are still only using a single thread to do the loading. you must pass -thread n to run with more threads, e.g. -thread 4 will have YCSB launch 4 threads in the client. These additional threads are how you get YCSB to make use of more cpu cores (though they may not due to e.g. blocking on IO to the datastore).

-thread X  only use for run phase correct?

What are you trying to accomplish with YCSB?  Are you really trying to see if machine A is faster than machine B?  Based on the specs, I would say machine B is faster.  You don't need YCSB for that.
So, why is your YCSB results not showing that?  Well, you're not using it right.

  You should have a run that lasts at least 10-20 minutes in order to draw some meaningful conclusions.  (Even that is an arbitrary number... I would look at throughput and see how long it takes for throughput to reach a steady state and then run for some meaningful amount after that.)
You are running single threaded.  On an 16 core machine and you have a single threaded operation, then the other 15 cores are doing a lot of just waiting around.  So, I wouldn't expect very different results assuming other factors are similar like cpu speed, number of other processes running, etc.

I believe you should be trying to simulate your real world use cases.  How many concurrent connections do you expect to handle (this should be your thread count).  How many operations a day do you want to be able to perform?  How large will your data set be?
Then setup your db and run.  And make your observations.  Generally, I disregarded the results of a load phase because my use cases were more read heavy with some inserts and a few updates.
-Are you trying to see if the machine can handle your real world use case?  While YCSB is running, check your machine statistics to see if RAM is being over or under utilized.
-Are you trying to see what different configurations of cassandra will yield the most optimal results?  Then make the changes to cassandra, run again, and observe.
-Are you trying to see if a different database like mongo will work better?  Then, swap out the db, change the YCSB binding to mongo, run and observe.
I hope you see where I'm going here.  Be deliberate with your calculations.  This is going to take longer than just a few seconds.  Sorry, for being gruff with this post.  Feels like tough love is needed. :)

so, even though on machine2 there is a good size of RAM , on your opinion what is reason to slower than machine1  even 1s?

The amount or kind of memory on the machines is almost certainly immaterial given the workload sizes you've been using.
Please go back again to @cmatser's starting question. You must begin your investigation by deciding what it is you hope to understand.

ok ,
if we have for examlpe 8 core of cpu , load action is overall all cores? or only one core?

Any further questions on this one @Hadi14?

Closing as stale. If you're still working on this issue please reopen.


Datatable Pagination doesn't work in component with VeeValidate useForm

The items per page select won't work when used in parent component that uses vee validate useForm. v-model can be passed and @update:model-value does being called with the correct value when selection changes. However, the UI just stuck on "Select" instead of showing actual value. The var being passed in v-model also not being updated.
The issue is caused by VSelect which is the component being used for the select input. under vee validate Form or useForm, VSelect requires name prop to be defined to work properly.
Issue can be reproduced under storybook by adding this
<v-select
        wrapper-class="mb-4"
        label="Gender"
        v-model='modelVal'
        placeholder="Select your gender"
        :items="genders"
      />

into the Validation story with modelVal being const modelVal = ref().

Sorry for the inconvenience.
Can you share the full reproduction code?

I've forked the lib and create a branch in here : https://github.com/gits-gretchelin/ui-component/blob/repro/issue-81
I've edited this particular storybook's story to showcase the problem in VDataTablePagination
https://github.com/gits-gretchelin/ui-component/blob/602a4afe5cf340a8627596873be07c002b1924c0/packages/table/src/VDataTablePagination.stories.ts#L122-L144
And here, I updated VSelect story to show that the issue due to VSelect since given the same situation, VSelect behave exactly the same, which is not working.
https://github.com/gits-gretchelin/ui-component/blob/602a4afe5cf340a8627596873be07c002b1924c0/packages/select/src/VSelect.stories.ts#L165-L236

Thanks for the clear reproduction. I confirm that this issue occurs because vee-validate's useField requires the name prop to be defined.
For now, I think we can replace the VSelect with the basic <select> input.

Maybe in the future, we need to drop useField from all forms components if this will cause other issues and give the user freedom to use other validation libraries.

still open bro @gravitano ?
i have same issue when using  on vee-validate
Here is what i found.
VSelect display [object Object] in Search Text. it weirds, user have to clear text then type search

here the reproduction code :
<form class="mt-5 gap-2" @submit="onSubmit">         <VSelect           label="Label"           placeholder="Cari"           :items="items"           searchable           clearable         /> ........

Hi @karis, sorry for the inconvenience. Yes, the issue is still in fixing.

Hi @karis, I just released a new version 0.14.0, including fixes for this issue. Give it a try and report back if anything breaks.

im so relieved
lets get started new version..
thank you @gravitano..

I think now we can close this issue. Feel free to reopen it if it still occurs.


share image gallery: expose --no-wait on creating/updating image versions

The replication will get long enough (hours) to get people feel really bored
//CC @singhkays

@yugangw-msft Can we make no wait the default?

Making no-wait by default will cause inconsistencies across CLI, because we have lots of other commands which expose no-wait as well; however, I can output a warning to tell users that they can use this flag, and then use the az sig image-version wait command later to ensure the image version did get updated correctly
Sounds good?

Sure, warning sounds good


some fixes for mac users

OK, been travelling and here's a bunch of fixes to make run_pair.sh work on Mac.

:+1:

Looks like a bunch of things were introduced that break on Mac; I'll have to revisit this when I'm back after holidays.

Ugh, sorry.
Cheers,
$ ls
Lally Singh | Google Ideas http://www.google.com/ideas/ | Engineering |
<EMAIL_ADDRESS>On Fri, Jul 17, 2015 at 5:03 PM, trevj<EMAIL_ADDRESS>wrote:

Looks like a bunch of things were introduced that break on Mac; I'll have
to revisit this when I'm back after holidays.
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy-docker/pull/9#issuecomment-122415127.

Sorry, looks like the fixes required are pretty minor -- worse is that Docker seems to be down right now, I can't pull any new images :-)

Mystery solved: there's something about operator precedence that bash on Mac doesn't like. I just had to change these lines from:
source "${BASH_SOURCE%/*}/utils.sh" || echo "cannot find utils.sh" && exit 1

to
source "${BASH_SOURCE%/*}/utils.sh" || (echo "cannot find utils.sh" && exit 1)

Since that line was my suggestion, seems only fair I should fix it :-)


Microsoft Defender Issue

My organizations Microsoft Defender custom detection rules have all disappeared, about half of our blocked IOC's have vanished as well. I'd like to know if this is peculiar to anyone and if there is a solution?

Hi, I am not aware of this issue. If you have enabled UAL for MDE you can view what caused this activity. If there is no entry and the UAL activities are enabled I suggest creating a support ticket for MS Support to investigate this particular issue. Both Indicator and custom detection rule deletions/changes (and creations) are logged in UAL.


update JS deps including TypeScript from v3.4 to v3.5

Announcing TypeScript 3.5 | TypeScript https://devblogs.microsoft.com/typescript/announcing-typescript-3-5/
🚀

Codecov Report

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

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   96.57%   96.57%
=======================================
  Files          15       15
  Lines         906      906
  Branches      183      183
=======================================
  Hits          875      875
  Misses         31       31

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 bed120e...b9440f4. Read the comment docs.


📖 Documentation: Syncing code to AWS CodeCommit

Similar to Bitbucket this option is only available in the Enterprise plan.

@overbit please add any information needed to explain how to connect to AWS CodeCommit
How is it different from connecting to GitHub or Bitbucket

@overbit @GreenMachine01 do you have some additional information on Notion that I could reference for this issue?

No worries and thanks for the update @overbit! Let me know when this one is ready to work on.

@GreenMachine01 and I agreed that we can document AWS now mentioning that the configuration of the integration will happen during the onboarding where the user will be asked to provide the following information:

AWS region : this is the region whereas the AWS CodeCommit repositories will be stored in AWS
AWS HTTPS Git credentials for AWS CodeCommit: used by the amplication[bot] to interact with each git repository . I'd add a link to here for more details: https://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-gc.html
AWS User Access Key Id and Access Secret Key: used by amplication to manage the repositories tasks (i.e. create new repos, create PRs, add comments, etc). The AWS user will require the AWS managed policy AWSCodeCommitPowerUser to gain the necessary permissions.

That makes sense, @overbit. If I have any additional questions I'll ask here on this issue.

This one is taken care of in PR #394.


Upgrade to rTorrent stickz version 5.1

Here are the highlights, the full changelog since the latest release on this docker container can be found here:
Full Changelog: https://github.com/stickz/rtorrent/compare/v4.0-0.9.8-0.13.8...v5.1-0.9.8-0.13.8
Version 5.1 Release
This release raises the throttle feature limit to approximately 33 gigabits, allowing the throttle plugin on ruTorrent to operate virtually without limits. It also adds a version check feature when typing rtorrent -h into terminal.
What's Changed

https://github.com/stickz/rtorrent/pull/18 by @stickz
https://github.com/stickz/rtorrent/pull/17 by @ac1dburnz

New Contributors

@ac1dburnz made their first contribution in https://github.com/stickz/rtorrent/pull/17

Version Changelog: https://github.com/stickz/rtorrent/compare/v5.0-0.9.8-0.13.8...v5.1-0.9.8-0.13.8
Version 5.0 Release
This release contains a significant performance improvement for downloading files. CPU usage is reduced under load, allowing a higher download ceiling to be reached. Higher priority files are also download faster, due to a reduction in normal priority pieces queued.
What's Changed

https://github.com/stickz/rtorrent/pull/16 by @stickz

Version Changelog: https://github.com/stickz/rtorrent/compare/v4.3-0.9.8-0.13.8...v5.0-0.9.8-0.13.8

@crazy-max More ground breaking improvements to rTorrent. Please tag a new release after merging this version. It will have a significant impact for everyone using this docker container.

Users no longer need to disable the throttle plugin on ruTorrent. It can operate without limits now.
The CPU usage when downloading files is significantly reduced. A 50% higher download ceiling is expected.


Accidental assignment in guzzle3/src/Guzzle/Service/CachingConfigLoader.php

if ($result = $this->cache->fetch($key)) {                 return $result;             }
Is this intentional or accidental?

Intentional.

@mtdowing pardon my ignorance but why it this way?


Update to  go 1.17

Hi, as there is a lot of vulnerabilities in earlier packages and 1.12 is a bit out of date..
I have created a PR for this and tested an action,  however I definitely think some more testing should be done, is there any recommended tests?
Thank you
Pull Request: https://github.com/IBM-Cloud/redli/pull/42

@ullumullu Hi, are you still involved in this project?


Harden restart_node_test

See discussion in CASSANDRA-10870
@mambocab or @stef1927 to review. We'll give this a week or so after merging to see if the flapping tests start passing on CI, before we resolve 10870.

Code looks good, but I'd wait on a review from @stef1927 as well.

Ping @stef1927 -- could you have a look, please? Thanks.

Sorry I missed the initial ping. LGTM.

:+1: not a problem, that's what pinging is for! Thanks for the review/merge.


Installation upgrade instructions in the README

Add a section on how to upgrade your Reservoir installation using xr.sh.

Closed in c025491.


Build fails on PICO_W

With latest sources, both micropython and ucrypto. Trying to make a build for pico w board, but it always fails in the last steps :
The building keeps failing with Error
selected processor does not support ***** in Thumb mode
instruction not supported -- '*******'
To the best of my knowledge these kind of asm issues should be automatically solved by compiler, but it seems currently not.
What else can be done to make things work or it's just a unsolvable platform supporting issue?

I've never tried a build for pico w, I don't think asm for rp2040 is supported by the tomsfastmath library, probably just disable asm optimizations and use the C implementation.
At the moment I don't have so much time to spend on the library, as soon as I can take a look I will update you.

After commenting out all TFM flags the building works indeed.
Though it's taking about 8 seconds for pico to do the gen_keypair() -> ecdsa.sign() -> ecdsa.verify() procedure.
Also a new issue on uhashlib emerged, I'll get another opened.

@dmazzella Sorry but the build seems still not working with latest version.

I found that I can set TFM_NO_ASM in tfm_mpi.h. The building does work but I don't know how to make it responsive to specific board.

I can't reproduce it, can you give me some more information?

Just did the example steps in (README.md)[https://github.com/dmazzella/ucrypto/blob/master/README.md]. All I did else is modifying the USER_C_MODULES into the micropython's root.
git clone https://github.com/micropython/micropython.git
cd micropython
cp -R examples/usercmodule .
git clone https://github.com/dmazzella/ucrypto.git usercmodule/ucrypto
(vim edit the usercmodule/micropython.cmake, change contents to only bulild ucrypto)
make -j4 -C mpy-cross
make -j4 -C ports/rp2 BOARD="PICO_W" USER_C_MODULES="$(pwd)/usercmodule/micropython.cmake"
I bet it's because of version or environment difference, I use python3.10 and gcc-arm-none-eabi in ubuntu. Perhaps docker can be used to do the checking.

can you try to set this:
#define TFM_NO_ASM

#define TFM_ECC192
#define TFM_ECC224
#define TFM_ECC256
#define TFM_ECC384
#define TFM_ECC512
#define TFM_RSA512
#define TFM_RSA1024
#define TFM_RSA2048

with these options do you have a correct build and performance improvements?

With different setup I've got these two uf2s. Will be testing them tomorrow.

Tested and it turns out that:
NO_ASM + optimizations off -> around 8100 millis.
NO_ASM + TFM_ECC256 on -> around 8000 millis.
NO_ASN + optimizations on ->around 9000 millis.
on test-ecdsa.py.


s2i-build + push-to-registry. Update image problem in Selfhosted runner.

Hi in some test I've used s2i-build + push-to registry in a selfhosted runner and I think there is a problem when you build the image for second time. What I saw in the source code is if there is no image in the podman registry, the action try to pull the image from the docker registry, thas works ok the first time because the s2i-build leaves the created image in the docker registry. The second time, s2i-build creates a new version of the image in the docker registry, but when the push-to-registry action get the images form de podman registry, the image already exist, so the push-to-registry push again the previous version of the image and not the new one. I' ve mitigated this runing "podman rmi name:tag" after the push.

Thank you for reporting this - we will check it out.

Thank you for reporting this - we will check it out.

The problem is that a docker-built image will be pulled into the podman image storage, but only if it doesn't exist there already.
https://github.com/redhat-actions/push-to-registry/blob/main/src/index.ts#L35

The problem is that a docker-built image will be pulled into the podman image storage, but only if it doesn't exist there already.
https://github.com/redhat-actions/push-to-registry/blob/main/src/index.ts#L35


Fall through case for broken enum

This is an attempt to allow discord user Andreloupgarou to fix their account.

I assume you've tested that this actually fixes the issue. Does it duplicate the card in any way though? Having a duplicate might be a bit annoying, especially since we should probably find a way to make it so that over time all decks end up using the right one and the database could be checked to see if any are left still before being able to remove the incorrect one.

This does fix the bug, but also adds a duplicate to the deck editor. It does not allow any illegal decks. I was able to recreate the bug Andreloupgarou encountered by creating a deck with the duplicate card, then removing the duplicate from the file. Adding the duplicate back allowed the deck editor to be accessed again. Unfortunately, even after deleting the decks with the duplicated card, reverting the file caused the original error. This seems like something only @axpendix can fix properly, but this has been an issue for this user for over a month, and I think that the partial fix is justified until a permanent solution can be found.


Added Phind in Chatbot section

Description
Added an AI coding assistance in the chatbot section. It's called Phind.
Checklist
Before submitting this pull request, please ensure that you have done the following:

[x] Read and understood the Contributing Guidelines.
[x] Checked that your changes align with the repository's goals and content.
[x] The submission is not already present in the list

Related Issues
Relates to #34
Additional Notes (if applicable)
Add any additional information or context that may be relevant to this pull request.

By submitting this pull request, you confirm that you have read and agree to abide by the Code of Conduct and the Contributing Guidelines of the AI Tools Collective project.

Great job @Giridharan002 !! , thank you for the contribution.


Excluding base url prefix to cdn thumbnails

Before:
The 'base-URL' will be the prefix of the thumbnail's URL if it does not start with "HTTP".
Issue
Many thumbnails are served from CDNs (URLs starting with "//") and thus will not require "1337x.to" as the base URL.
Fix
URLs starting with "HTTP" and "//" i.e CDN URLs will be discarded from any base URL addition process.
Sample URL: https://1337x.to/torrent/5464180/Black-Adam-2022-FullHD-1080p-H264-Ita-Eng-AC3-5-1-Sub-Ita-Eng-realDMDJ-DDL_Ita/

Thanks for pointing the issue. I have applied the patch and released a new version.


rolling().sum() is numerically unstable

What happened?
On an input array like
array([0.        , 0.        , 0.        , 0.57392103, 0.57392103,
       0.57392103, 0.57392103, 0.57392103, 0.57392103, 0.57392103,
       0.57392103, 0.57392103, 0.        , 0.57392103, 0.57392103,
       0.57392103, 0.57392103, 0.57392103, 0.57392103, 2.29551022,
       2.29551022, 2.29551022, 2.29551022, 2.29551022, 2.29551022,
       2.29551022, 2.29551022, 2.29551022, 2.29551022, 2.29551022,
       2.29551022, 2.29551022, 2.29551022, 0.57383408, 0.57383408,
       0.57383408, 0.57383408, 0.57383408, 0.57383408, 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.        , 0.        ,
       0.        , 0.        , 0.        , 0.
The issue aggravates as the rolling window increases.
What did you expect to happen?
the rolling calculation could be more numerically precise by keeping track for instance of the Kahan compensation term.
https://en.wikipedia.org/wiki/Kahan_summation_algorithm
MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X ] New issue — a search of GitHub Issues suggests this is not a duplicate.

Environment
this is reproducible across xarray versions, but mine is 2022.09.0.

Do you have bottleneck installed? Could you try xr.set_options(use_bottleneck=False)?

Do you have bottleneck installed? Could you try xr.set_options(use_bottleneck=False)?
use_bottleneck=False seems to solve it on the latest version of xarray, but I don't think it's compatible with previous versions of xarray like 0.11.3:

ValueError: argument name 'use_bottleneck' is not in the set of valid options set(['keep_attrs', '
enable_cftimeindex', 'cmap_sequential', 'arithmetic_join', 'warn_for_unclosed_files', 'file_cache_maxsize', 'cmap_
divergent', 'display_width'])

In our setting, we actually are trying to preserve compatibility for v0.11.3 as well.

You'll have to uninstall bottleneck then - the use_bottleneck option was added more recently.

You'll have to uninstall bottleneck then - the use_bottleneck option was added more recently.

Does xarray use bottleneck in other places than rolling operations?
That'd help me assess the scope of this change!


CLSCompliant?

I just recently upgraded to version 7.03 from the 6.xx stream and noticed that the assembly is no longer marked CLS compliant.  The AssemblyInfo.cs has been completely removed.  Was this intended?

The assemblyinfo is generated at runtime. The new-style SDK projects used for building netstandard-based assemblies don't contain assemblyinfo files anymore, but the csproj contains the necessary metadata which is used to generate the assemblyinfo during compilation. I probably just forgot to migrate that particular attribute across. I'll look at re-adding it to the next version.

Thanks Jeremy, version 7.1.1 resolves this issue.


Allow client timeout to be a float

What does this PR do?
Allow the client to accept a float as a timeout.
The underlying requests library used by pusher allows floats to be used when making requests. (see https://requests.readthedocs.io/en/latest/api/#requests.request)
Related issue: https://github.com/pusher/pusher-http-python/issues/194
CHANGELOG

[ADDED] Allow Client to accept float as a timeout
[ADDED] Tests for Client to validate timeout is a number

@benjamin-tang-pusher just a friendly bump, is there anything else that needs to be done before we could merge this?


Fix typo in README example

Same as https://github.com/github/time-elements/pull/52

If the difference is intentional in order to communicate adjustments made for timezone, might I suggest making it obviously different, such as 21:30?


Bug when changing negative floating point number

https://github.com/daangn/urlpack/blob/6593d09872497422adb92e4c886fb4d006a850ca/packages/msgpack/src/utils.ts?_pjax=%23js-repo-pjax-container%2C div[itemtype%3D"http%3A%2F%2Fschema.org%2FSoftwareSourceCode"] main%2C [data-pjax-container]#L1
The isFloat function in the util file does not work if input is negative. So there is a problem that it is handled to incorrectly (Uint8Array(1) [ 255 ]) when changing negative floating point number.

There is already a scheduled major change. It will be included in the v1 release.
Thanks for reporting this.


We should not validate RequestContent

This issue comes from https://github.com/Azure/azure-sdk-for-net/pull/27713#discussion_r835592572
Currently we validate RequestContent as
public virtual Response PostModel(string mode, RequestContent content, RequestContext context = null)
{
    Argument.AssertNotNull(mode, nameof(mode));
    Argument.AssertNotNull(content, nameof(content));
}

@annelo-msft we validate RequestContent becaue in swagger, it is marked as required. E.g., for dpg-update1 we have marked operation params_postParameters with body required. https://github.com/Azure/autorest.testserver/blob/e6c0690ce7016242eed0a6c7187965d11d1eb37e/swagger/dpg-update1.json#L105
Therefore, this RequestContent is validated. If we remove the required in swagger, then we will not validate the RequestContent.
So, this issue is by design to me.

According to https://github.com/Azure/azure-sdk-for-net/pull/27713#discussion_r854377749.

we can revisit it if it ever becomes a problem.

Close it for now.


remove v0.2.0 artifacts

Comment:
The v0.2.0 mistakenly shipped a statically linked libsecp256k1 library. It uses 1M by itself @conda-forge/core

Wrong action: ignore

If you ever need to mark pkgs as broken see https://github.com/conda-forge/admin-requests?tab=readme-ov-file#mark-packages-as-broken-on-conda-forge

Right, I was reading the Maintainer KB and mixed-up the broken and archive paragraph. I pushed: https://github.com/conda-forge/admin-requests/pull/960
Let me know if this is correct, if you get the chance
Thanks


focus error between gdscript & shader editor

Godot version:

master branch, commit 96899b7ee1cb442ce9625232d558670fe7011c2c
OS/device including version:

Linux Mint 18.2, Linux 4.8.0-53-generic x86-64, GTX 1080
Issue description:

You need to have shader editor and gdscript editor open at the same time to reproduce this bug.
When commenting code with ctrl+k, the shader receive the command, no way to send the command to the gdscript editor without closing the shader editor first.
Steps to reproduce:

open a shader and open editor
switch to Script tab and open a .gd
press ctrl + k

Godot rocks!

Duplicate of #12916


Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0

Expected Behavior

I encountered a problem compiling gradle source code
Could not complete compilation.
I started to doubt the correctness of the github source code.
I'm not familiar with the source code content and ask for help.
Current Behavior

Commands I execute:

./gradlew assemble

Context

This is compiler infomation:
[16:14:47@zhubo gradle]$
[16:14:47@zhubo gradle]$./gradlew assemble
Partial virtual file system invalidation is an incubating feature.

> Task :buildSrc:kotlinDsl:compileKotlin
w: /home/zhubo/gradle/buildSrc/subprojects/kotlin-dsl/build/generated-sources/kotlin-dsl-accessors/kotlin/gradle/kotlin/dsl/accessors/_2ebcc113f61c6c248bfd09a507eedcb7/Accessors63c9fvdqy5asv1rzj19c14d1p.kt: (61, 88): 'ValidateTaskProperties' is deprecated. Deprecated in Java
w: /home/zhubo/gradle/buildSrc/subprojects/kotlin-dsl/build/generated-sources/kotlin-dsl-accessors/kotlin/gradle/kotlin/dsl/accessors/_2ebcc113f61c6c248bfd09a507eedcb7/Accessors63c9fvdqy5asv1rzj19c14d1p.kt: (62, 49): 'ValidateTaskProperties' is deprecated. Deprecated in Java

> Task :buildSrc:buildquality:compileKotlin
w: /home/zhubo/gradle/buildSrc/subprojects/buildquality/src/main/kotlin/org/gradle/gradlebuild/buildquality/incubation/IncubatingApiAggregateReportTask.kt: (52, 24): 'submit(Class<out Runnable!>!, Action<in WorkerConfiguration!>!): Unit' is deprecated. Deprecated in Java
w: /home/zhubo/gradle/buildSrc/subprojects/buildquality/src/main/kotlin/org/gradle/gradlebuild/buildquality/incubation/IncubatingApiReportTask.kt: (84, 36): 'submit(Class<out Runnable!>!, Action<in WorkerConfiguration!>!): Unit' is deprecated. Deprecated in Java

> Task :cli:compileJava
错误: 不再支持源选项 6。请使用 7 或更高版本。
错误: 不再支持目标选项 6。请使用 7 或更高版本。

> Task :cli:compileJava FAILED

> Task :pineapple:compileJava FAILED
错误: 不再支持源选项 6。请使用 7 或更高版本。
错误: 不再支持目标选项 6。请使用 7 或更高版本。

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':cli:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':pineapple:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1m 16s
222 actionable tasks: 40 executed, 182 up-to-date
[16:17:17@zhubo gradle]$

Steps to Reproduce

Commands I execute:

./gradlew assemble

Your Environment

Build scan URL:
env:
[16:20:14@zhubo gradle]$./gradlew -v

------------------------------------------------------------
Gradle 6.1
------------------------------------------------------------

Build time:   2020-01-15 23:56:46 UTC
Revision:     539d277fdba571ebcc9617a34329c83d7d2b259e

Kotlin:       1.3.61
Groovy:       2.5.8
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          13.0.2 (Oracle Corporation 13.0.2+8)
OS:           Linux 4.15.0-33-generic amd64

[16:20:28@zhubo gradle]$

The problem is cli and pipeapple
I compiled the cli separately

./gradlew cli:compileJava --info

> Configure project :smokeTest
Evaluating project ':smokeTest' using build file '/home/zhubo/gradle/subprojects/smoke-test/smoke-test.gradle.kts'.

> Configure project :snapshots
Evaluating project ':snapshots' using build file '/home/zhubo/gradle/subprojects/snapshots/snapshots.gradle.kts'.

> Configure project :soak
Evaluating project ':soak' using build file '/home/zhubo/gradle/subprojects/soak/soak.gradle.kts'.
kotlin scripting plugin: created the scripting discovery configuration: integTestKotlinScriptDef
kotlin scripting plugin: created the scripting discovery configuration: kotlinScriptDef
kotlin scripting plugin: created the scripting discovery configuration: testKotlinScriptDef
kotlin scripting plugin: created the scripting discovery configuration: testFixturesKotlinScriptDef

> Configure project :testingBase
Evaluating project ':testingBase' using build file '/home/zhubo/gradle/subprojects/testing-base/testing-base.gradle.kts'.

> Configure project :testingJunitPlatform
Evaluating project ':testingJunitPlatform' using build file '/home/zhubo/gradle/subprojects/testing-junit-platform/testing-junit-platform.gradle.kts'.

> Configure project :testingJvm
Evaluating project ':testingJvm' using build file '/home/zhubo/gradle/subprojects/testing-jvm/testing-jvm.gradle.kts'.

> Configure project :testingNative
Evaluating project ':testingNative' using build file '/home/zhubo/gradle/subprojects/testing-native/testing-native.gradle.kts'.

> Configure project :testKit
Evaluating project ':testKit' using build file '/home/zhubo/gradle/subprojects/test-kit/test-kit.gradle.kts'.

> Configure project :toolingApi
Evaluating project ':toolingApi' using build file '/home/zhubo/gradle/subprojects/tooling-api/tooling-api.gradle.kts'.

> Configure project :toolingApiBuilders
Evaluating project ':toolingApiBuilders' using build file '/home/zhubo/gradle/subprojects/tooling-api-builders/tooling-api-builders.gradle.kts'.

> Configure project :toolingNative
Evaluating project ':toolingNative' using build file '/home/zhubo/gradle/subprojects/tooling-native/tooling-native.gradle.kts'.

> Configure project :versionControl
Evaluating project ':versionControl' using build file '/home/zhubo/gradle/subprojects/version-control/version-control.gradle.kts'.

> Configure project :workerProcesses
Evaluating project ':workerProcesses' using build file '/home/zhubo/gradle/subprojects/worker-processes/worker-processes.gradle.kts'.

> Configure project :workers
Evaluating project ':workers' using build file '/home/zhubo/gradle/subprojects/workers/workers.gradle.kts'.
All projects evaluated.
Selected primary task 'cli:compileJava' from project :cli
Tasks to be executed: [task ':verifyBuildEnvironment', task ':cli:compileJava']
:verifyBuildEnvironment (Thread[Execution worker for ':',5,main]) started.

> Task :verifyBuildEnvironment
Caching disabled for task ':verifyBuildEnvironment' because:
  Build cache is disabled
Task ':verifyBuildEnvironment' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
:verifyBuildEnvironment (Thread[Execution worker for ':',5,main]) completed. Took 0.004 secs.
:cli:compileJava (Thread[Execution worker for ':',5,main]) started.
This JVM does not support getting OS memory, so no OS memory status updates will be broadcast

> Task :cli:compileJava
Caching disabled for task ':cli:compileJava' because:
  Build cache is disabled
Task ':cli:compileJava' is not up-to-date because:
  Task has failed previously.
The input changes require a full rebuild for incremental task ':cli:compileJava'.
Full recompilation is required because no incremental change information is available. This is usually caused by clean builds or changing compiler arguments.
Starting process 'Gradle Worker Daemon 14'. Working directory: /home/zhubo/.gradle/workers Command: /home/zhubo/jdk13/jdk-13.0.2/bin/java @/tmp/gradle-worker-classpath7400781463320307782txt -Xmx512m -Dfile.encoding=UTF-8 -Duser.country=CN -Duser.language=zh -Duser.variant worker.org.gradle.process.internal.worker.GradleWorkerMain 'Gradle Worker Daemon 14'
Successfully started process 'Gradle Worker Daemon 14'
Started Gradle worker daemon (0.95 secs) with fork options DaemonForkOptions{executable=/home/zhubo/jdk13/jdk-13.0.2/bin/java, minHeapSize=null, maxHeapSize=null, jvmArgs=[], keepAliveMode=SESSION}.
Compiling with JDK Java compiler API.
错误: 不再支持源选项 6。请使用 7 或更高版本。
错误: 不再支持目标选项 6。请使用 7 或更高版本。

> Task :cli:compileJava FAILED
:cli:compileJava (Thread[Execution worker for ':',5,main]) completed. Took 2.6 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':cli:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 12s
2 actionable tasks: 2 executed
Stopped 1 worker daemon(s).
[15:42:35@zhubo gradle]$

"错误: 不再支持源选项 6。请使用 7 或更高版本。
错误: 不再支持目标选项 6。请使用 7 或更高版本。"
translation
Error: Source option 6 is no longer supported. Please use version 7 or higher.
Error: Target option 6 is no longer supported. Please use version 7 or higher.
I don't know what "cli: compileJava" is. How do I find the problem? Ask for help! Thank you！

Please use Java 11 to build from source code. You're using Java 13 and -target 1.6 is not supported by 13.

Please use Java 11 to build from source code. You're using Java 13 and -target 1.6 is not supported by 13.

Didn't you say that gradle6.0 supports jdk13? I need to port to a mipsel device after the x86 machine is compiled. Our mipsel only has jdk13 and jdk1.8.

You're confusing runtime JDK and build JDK. Gradle does support Java 13, but building Gradle requires Java 11 because of -target 1.6.

What is -target 1.6? What I want to know is that gradle compiled with jdk11 on x86 platform can be used on 13 of other platforms?

You're confusing runtime JDK and build JDK. Gradle does support Java 13, but building Gradle requires Java 11 because of -target 1.6.

Let me describe my purpose: I have problems using gradle on the loognson mpisel platform. The error is "unknown os.arch: mips64el"; therefore, I don't think gradle supports loongson mipsel; that's why I compiled gradle source code.

You're confusing runtime JDK and build JDK. Gradle does support Java 13, but building Gradle requires Java 11 because of -target 1.6.

What is -target 1.6? What I want to know is that gradle compiled with jdk11 on x86 platform can be used on 13 of other platforms?

@adammurdoch IIUC, Gradle depends on some native library which might not support other platform, right?

What we need is gradle to run properly on the mipsel platform. The jdk versions available on mipsel are jdk1.8 and jdk13. Please tell me what I should do, thank you!

@adammurdoch IIUC, Gradle depends on some native library which might not support other platform, right?

Please tell me what I should do! Waiting for your reply.

@adammurdoch IIUC, Gradle depends on some native library which might not support other platform, right?
@adammurdoch IIUC

I replaced jdk11 and still have problems.
Compilation is complete, but no binary files are generated.
The terminal information is as follows：
[11:18:03@root gradle_01]#./gradlew assemble
Partial virtual file system invalidation is an incubating feature.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 41s
697 actionable tasks: 91 executed, 606 up-to-date
[11:18:48@root gradle_01]#
[11:21:59@root gradle_01]#./gradlew -v

------------------------------------------------------------
Gradle 6.1
------------------------------------------------------------

Build time:   2020-01-15 23:56:46 UTC
Revision:     539d277fdba571ebcc9617a34329c83d7d2b259e

Kotlin:       1.3.61
Groovy:       2.5.8
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          11.0.2 (Oracle Corporation 11.0.2+9)
OS:           Linux 4.15.0-76-generic amd64

[11:22:20@root gradle_01]#
[11:22:21@root gradle_01]#
[11:22:21@root gradle_01]#
[11:22:21@root gradle_01]#tree build
build
├── build-receipt.properties
├── determined-commit-id.txt
└── kotlin
    └── sessions

2 directories, 2 files
[11:22:42@root gradle_01]#

[11:22:42@root gradle_01]#java --version
openjdk 11.0.2 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
[11:27:00@root gradle_01]#


Fix bind's overeagerness, tighten invariants

Closes #18
After creating a Binding, Coordinators.bind would immediately call its
onViewAttachedToWindow, without regard for whether that was true.
The idea was to eliminate a potential race, where bind was called
after the View was already attached to the Window. When that happened the
Binding wouldn't be called by the platform, so the Coordinator would
never learn that it was attached unless bind called it directly.
That implementation created a problem though: If the View was not
already attached to the Window, the Coordinator would still receive an
attach call. This violated expectations around the interaction between
Coordinator and View lifecycle. Technically that was fine, because no
promises were made; but it was still surprising.
With this change, bind will still call onAttachedToWindow but only
if the View actually is already attached. This should alleviate any
confusion.
As a side effect, there's also no longer any potential for a duplicate
onAttachedToWindow call. This means we can tighten up the assertions
in the Binding. I also took the opportunity to tighten up all of the
assertions in Binding, so now it enforces a very strict 1:1:1
relationship between the Binding, View, and Coordinator and fails loudly
if that invariant is violated.

Removed that redundant view reference and updated the assertions, thanks.


Support odd version strings

Hey,
I'm trying to use this with this: https://central.sonatype.com/artifact/org.jboss/jboss-vfs/3.2.17.Final but the ".Final" is causing the following:
The "MavenDependencyVerifierTask" task failed unexpectedly.
System.ArgumentException: '3.2.17.Final' is not a valid version string.
Parameter name: value
   at NuGet.Versioning.NuGetVersion.Parse(String value)
   at MavenNet.MavenVersionRange.Satisfies(String version)
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
   at Prototype.Android.MavenBinding.Tasks.DependencyResolver.IsDependencySatisfied(Dependency dependency, MicrosoftNuGetPackageFinder packages, LogWrapper log)
   at Prototype.Android.MavenBinding.Tasks.MavenDependencyVerifierTask.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()	Tesseract.Binding.Droid	C:\Users\kfrancis\.nuget\packages\xamprototype.android.mavenbinding.tasks\0.0.7\build\XamPrototype.Android.MavenBinding.Tasks.targets

They seem to include that in all their versions: https://central.sonatype.com/artifact/org.jboss/jboss-vfs/3.2.17.Final/versions

Fun!  🙄
I'll look into what we can do about it.

Released version 0.0.8 which should fix this.


Fatal error: Class Org_Heigl\TextStatistics\Util\SyllableFilter contains 1 abstract method

Fatal error: Class Org_Heigl\TextStatistics\Util\SyllableFilter contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (Org\Heigl\Hyphenator\Filter\Filter::doConcatenate) in ...\vendor\org_heigl\textstatistics\src\Util\SyllableFilter.php on line 32

Changed:
"require": {  "org_heigl/textstatistics": "^0.1" }
to:
"require": {  "org_heigl/textstatistics": "^0.2" }
Now it works. Seems like the composer dependencies are broken.


Ebml body

response to @mbunkus's comment on a vague 'it': https://github.com/MediaArea/ebml-specification/commit/0ec80d2dafc00311acb8d05308b0a2c5e5260aba


Unable to fetch secret from AWS secret manager

Describe the bug
$ printenv | grep AVP
AVP_AWS_ACCESS_KEY_ID=xxx
AVP_AWS_REGION=ap-northeast-1
AVP_TYPE=awssecretsmanager
AVP_AWS_SECRET_ACCESS_KEY=xxx

$ argocd-vault-plugin generate all.yaml
apiVersion: v1
kind: Service
metadata:
  name: nginx
spec:
  ports:
  - port: 80
    protocol: TCP
    targetPort: 80
  selector:
    app: nginx
---
Error: Replace: could not replace all placeholders in Template:
NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors
Usage:
  argocd-vault-plugin generate <path> [flags]

Flags:
  -c, --config-path string   path to a file containing Vault configuration (YAML, JSON, envfile) to use
  -h, --help                 help for generate
  -s, --secret-name string   name of a Kubernetes Secret containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD)

Replace: could not replace all placeholders in Template:
NoCredentialProviders: no valid providers in chain. Deprecated.
	For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Additional context
I'm running argocd-repo-server in k8s
$ /usr/local/bin/argocd-vault-plugin version
v1.0.0

@Yapcheekian this does appear to be a bug. The aws go sdk expects AWS_SECRET_ACCESS_KEY and AWS_ACCESS_KEY_ID as environment variables without the AVP prefix. Will work on a fix.


Maybe impl IntoParallelIterator for CompletionQueue

As the code currently stands, we do this sort of thing:
// This all happens within a Rayon ThreadPool.
// In one thread:
let completion_queue: Vec<Entry> = ring.completion().collect();

// Submit tasks to the thread pool:
let results = completion_queue.par_iter().map(processing_func);

Instead of collecting the completion queue into a vector, it may be slightly more efficient to directly impl IntoParallelIterator for CompletionQueue. Although, due to Rust's orphan rule, we can't directly impl IntoParallelIterator for CompletionQueue, because IntoParallelIterator and CompletionQueue come from external crates.
I believe the standard way round the orphan rule is to do something like this (NOTE THAT THIS DOESN'T COMPILE!!):
use io_uring::cqueue;

struct CompletionQueueWrapperParIter<'a>(cqueue::CompletionQueue<'a>);

impl<'a> IntoParallelIterator for CompletionQueueWrapperParIter<'a> {
    type Item = cqueue::Entry;  // TODO: Should be EntryMarker
    type Iter = IntoIter<'a>;

    fn into_par_iter(self) -> Self::Iter {
        IntoIter { cqe: self }
    }
}

/// Parallel iterator that moves out of a CompletionQueue.
pub struct IntoIter<'a> {
    cqe: cqueue::CompletionQueue<'a>,
}

fn main() -> io::Result<()> {
    // ...
    let cq_par_iter = CompletionQueueWrapperParIter(ring.completion());
    let cq: Vec<cqueue::Entry> = cq_par_iter.collect();
    let cqe = cq[0];
}

For now, collecting into a Vec is fine.
But, if I do want to impl IntoParallelIterator for CompletionQueueWrapperParIter, then here are some useful resources:

https://geo-ant.github.io/blog/2022/implementing-parallel-iterators-rayon/
https://github.com/rayon-rs/rayon/blob/master/src/iter/plumbing/README.md
https://github.com/tokio-rs/io-uring/blob/master/src/cqueue.rs
https://github.com/rayon-rs/rayon/blob/master/src/vec.rs

Also, I could consider submitting a PR to io_uring to directly impl IntoParallelIterator for CompletionQueue.

Actually, far easier, I think I can just use Rayon's ParallelBridge!

Actually, in the latest design (see issue #16), I'm no longer planning to use parallel iterators.


Installing multiple packages only shows one package in the Installed

Describe the bug
I added multiple packages from a custom source.  The installed only shows 1 of the custom packages in the UI.
Version
1.3.1-nightly.220254
Browser

[x] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to package manager
Add a custom feed \fusebox\public\feed
Add a Humanizer  package from the custom feed
click on installed, the package is not listed.
Add javascript package, go to installed, the package is not listed
add Recognizer package, go tinstalled, the package IS listed.

Expected behavior
Installed should show all packages which are installed.  I suspect the issue is that you are assuming that components have to a .schema file, and that is a false assumption.
These are components which extend the adaptiveexpression functions with custom functions.  There is not a schema file for these components.  The fact that they have the bf-component tag in the metadata is the signal to say that this is a component.
Screenshots

Additional context

This was related to the selection criteria requiring that a package contain schema to be displayed.  It now uses the msbot- tags to determine if a package should be displayed here.


Don't re-use rustc cache when RUSTC_WRAPPER changes

We cache initial rustc --version invocations, to speed up noop builds.
We check the mtime of rustc to bust the cache if the complier changed.
However, before this PR, we didn't look at mtimes of RUSTC_WRAPPER /
RUSTC_WORKSPACE_WRAPPER, so we could've re-use old cache with new
wrapper.

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

I'm trying to better understand the motivation for this change.  Can you explain more what comes up in practice?
If wrappers return different values for the output, that seems like it would cause trouble since cargo may not always use the same rustc for every invocation. For example, with RUSTC_WORKSPACE_WRAPPER, that will only be used for workspace members, and then regular rustc will be used for dependencies.  Cargo assumes the different rustc executables will return the same version and capability information. If they don't, then it is likely it will get confused and have the wrong behavior.
I guess as long as RUSTC_WORKSPACE_WRAPPER returns the same output as the "other" rustc, it should be ok, but that seems somewhat brittle.

So the problem I am originally solving is solely about RUSTC_WRAPPER: I was unaware of WORKSPACE_WRAPPER before making this PR.
I was developing my own wrapper and the first version was buggy. Fixing that was hard, because cargo cached the buggy behavior, so all my bug fixes didn’t seemingly fix the problem. I thought the fixes were wrong, but it was that cargo just didn’t run my fixed code at all.
so hats why I went ahead and added rustc_wrapper to the cache (there’s already logic in place to track rustc binary mtime)
While at it, I’ve noticed that there’s workspace wrapper as well, so I decided to treat it in a similar way. I am not sure what’s the right behavior for ws wrapper is, and I donor know if that process ~> workspace process change in particular is a good idea.
Though, without that change, the test in this PR fails. The test does demonstrate a surprising behavior where the code doesn’t get rebuild when workspace wrapper is updated.

OK, makes sense. There is some risk with changing this, but I think it should be fine. For example, every time one switches between clippy and a regular build will rebuild the rustc cache. I don't think that will be noticeable performance-wise, though.
@bors r+

:pushpin: Commit f6070b3e3fbd7783adf0b1738096a46c0ee35371 has been approved by ehuss

:hourglass: Testing commit f6070b3e3fbd7783adf0b1738096a46c0ee35371 with merge 1243c378b9a637dc4beb9b2ad7b955af3affa47e...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 1243c378b9a637dc4beb9b2ad7b955af3affa47e to master...

Agree about the risk! If you want to, I can flip process back and test
just the RUSTC_WRAPPER. The process change is there solely to make the
test pass, it’s not something required to fix my immediate problem
On Sunday, 18 April 2021, bors @.***> wrote:

Merged #9348 https://github.com/rust-lang/cargo/pull/9348 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/cargo/pull/9348#event-4609345344, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3M2IWGOEFSUWISNMZZDTJML23ANCNFSM42Y67HJA
.

Nah. We can always change it later if it does seem like an issue. We could also change the cache to keep multiple entries (keyed off the fingerprint maybe) so that switching through different rustc versions will keep them all cached. But I don't see an immediate need for that.


Change GitHub project name to onebusaway-ios

In preparation for iPad support.

We have iPad support now.
@aaronbrethorst is renaming the repo worth the potential hassle?  I tend to avoid these things due to potential friction, although Github promises it will forward everything - https://help.github.com/articles/renaming-a-repository/.

I tend to avoid these things due to potential friction, although Github promises it will forward everything

Concur. Thanks, all :)


Create DBConnectionAdapter

Create DBConnectionAdapter (like as DBConnectionFilter in activeweb) for using in  non http threads of activeweb based projects.

if all  you need is to open a connection in specs, use DBSpec: http://javalite.io/testing_with_db_connection

you can inherit it or call directly:
DBSpec dbSpec =  new DBSpec();
dbSpec.openTestConnections();
System.out.println(Base.connection());
dbSpec.closeTestConnections();

This class is required not for testing. Testing can be is one case of usage.

@yanchevsky please, describe what  you want in greater detail.

@yanchevsky, any input?

Is this a duplicate of: https://github.com/javalite/javalite/issues/910 ?


Add support for Wrapping and Saturating

This should be feature gated as saturating_impls, and don't enable that for the MSRV test. I am planning to bump to 0.2 and clean up a bunch of cruft soon (within the next month) anyway, so I'll just raise the MSRV for that.

I was wondering why CI was failing, turns out Wrapping is 1.0 but Saturating is 1.74. Let me add that feature gate


Provide a license please

Hi,
Thanks for the amazing plugin. Can you provide a license as well please?
Many thanks!

Thanks for picking this up! MIT license added.

Thank you!


prefer more idiomatic deps declaration in README

Happy with a middle ground! 😁
Thank you a million for making this, by the way 🙇

No problem! If you don't mind just push up a change to that format and I'll squash and commit.


Update Composer dependencies (2023-05-20-00-10)

Visual regression test passed!
View the visual regression test report


[ BUG ] Using 'links' option in an entry breaks sitemap generation

Describe the bug
When adding the 'links' option to a sitemap entry that is already working, it is causing sitemap creation to fail validation.  From the 'Options you can pass' example:
links: [
    { lang: 'en', url: 'http://test.com/page-1/' },
    { lang: 'ja', url: 'http://test.com/page-1/ja/' }
  ],

Expected behavior
I expected the sitemap to add the <xhtml:link xmlns:xhtml="http://www.w3.org/1999/xhtml" rel="alternate" hreflang="en" href="https://url.example" /> entry to the sitemap, which it does.  The problem is that the entire sheet fails validation after doing so.
Context:

Library Version 7.1.1

Additional context
I am currently generating the sitemap with the 'Serve a sitemap from a server and periodically update it' example from this package.

the same for me...

bump

same for me

@martinsilha can you show me your sitemap example ? And how does it fail ? Are you not seeing the proper layout in the browser when navigating to sitemap ?

same here, if I add links I don't get xml anymore but just a string with link sequences without structure

same for me

Thanks for the comment above. This fixed the issue:
const sitemapXml = (await streamToPromise(smStream)).toString();

// Thanks to this comment:
// https://github.com/ekalinin/sitemap.js/issues/397#issuecomment-1438062056
const sitemapXmlHttps = sitemapXml.replace(
new RegExp('http://', 'g'),
'https://',
);

Ok, when we say "fails validation" I think people are simply talking about browsers rendering of XML right?
Questions

If we're talking about a browser rendering:
a. Which browser are we talking about?  Chrome?  Something else?
b. Are we opening the file locally or from a web server?
c. If from a web server, what is the exact value of the Content-Type response header and what is the name of the file (e.g. is it sitemap.html or sitemap.xml)?
If we we're talking about something other than browser rendering
a. please provide a link to the validator

Note that all the Google docs for sitemaps still show all the xmlns links as http:// in their examples.  I'd hesitate to change these to https:// to solve a browser rendering issue when it may actually break the sitemaps for crawlers.
https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap

right, if you change the xmlns attribute to https it will fail validation by the google crawler (at least as of a couple years ago). xmlns looks like a link but is in fact just a specification token. You can go to that in the browser and it will probably redirect you to https but when this was changed several years ago google would flag it as an invalid sitemap.
And yeah gonna need more info on what "fails validation" is.

@derduher, I feel like this is not a bug; you are both correct. The only problem is browser XML rendering, but the sitemap itself is entirely correct.


Niloofar Sadeghi / Node 18, React 18, Gatsby 5 migration

This PR includes these file changes:

Node migration to V18
React migration to V18
Gatsby migration to v5
Replacing gatsby-plugin-react-helmet and gatsby-plugin-react-helmet-canonical-urls with gatsby-plugin-canonical-urls
Removing gatsby-plugin-page-progress, react-perfect-scrollbar, storybook
Replacing gatsby-background-image and gbimage-bridge with gatsby-plugin-image
...

One issue:
After React 18 and Gatsby 5 migration we couldn't see our SEO tags in our pages source map!
Changes:
I replaced React Helmet with Gatsby Head Api
The gatsby-plugin-react-helmet package will be deprecated in the future. The new Gatsby Head API is easier to use, more performant, has a smaller bundle size, and supports the latest React features, also it is more compatible with Gatsby 5
A small guide of the usage of Head Api: https://www.gatsbyjs.com/docs/reference/built-in-components/gatsby-head/#:~:text=Gatsby includes a built-in,supports the latest React features.
Type of change

[ ] Bug fix
[ ] New feature
[x] Update feature
[x] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[x] Dependency update
[ ] Documentation update
[ ] Release

@niloofar-deriv good job,
Just one concern, I see that you have added the bad practices
I recommend you to add correct ones too.
so who ever see the bad practice immediately see how to fix it too.


Update partyreadycheck

This PR needs to have its merge conflict resolved

This PR needs to have its merge conflict resolved

Thanks, must've missed that.

Thanks @Nightfirecat, this is resolved now.

You should also try to close the Clip resource even if an error occurs using a finally clause: https://github.com/scainburger/partyreadycheck/compare/ed6d42032811888e8378db68657ea853d665db6a...scainburger:7f2dbe19371fc19ee2f7dda1feb0bb4697d489ed#diff-27b24bcdd3d76fec8ce0a2ec9a20f97a3adc79203a49ea1eeb3716e53af6736dR124

Thanks for the heads up @LlemonDuck. I've closed the clip in the catch clause as it wasn't behaving properly in the finally, please let me know if you forsee any issues with this.


Add Schema Registry

Schema Registry Solutions

(Skipped as Confluent Avro is not standard) Confluent Schema Registry

Kubernetes Deployment Solutions

(Succeed) Confluent Schema Registry packaged by Bitnami

My questions & tickets

(Solved) https://stackoverflow.com/questions/76157961/how-to-install-confluent-schema-registry-using-bitnami-helm-chart-for-external-k

(Failed) strimzi-registry-operator

My questions & tickets: https://github.com/lsst-sqre/strimzi-registry-operator/issues/84

REST API: https://docs.confluent.io/platform/current/schema-registry/develop/api.html
License

Schema Registry is licensed under the Confluent Community License.
A Confluent Enterprise license is required for the Schema Registry Security Plugin and for broker-side Schema Validation on Confluent Server.

Schema Registry UI

Kubernetes Deployment Solutions

https://artifacthub.io/packages/helm/cloudnativeapp/schema-registry-ui

My questions & tickets: https://github.com/cloudnativeapp/charts/pull/151

https://github.com/ricardo-aires/helm-charts

My questions & tickets: https://github.com/ricardo-aires/helm-charts/issues/12

(Succeed) Apicurio Registry

Kubernetes Deployment Solutions

(Official) Apicurio Registry Operator
(Unofficial, succeed) Ultimate Helm chart for Apicurio Registry

REST API: https://www.apicur.io/registry/docs/apicurio-registry/2.1.x/assets-attachments/registry-rest-api.htm

Confluent Schema Registry Compatible endpoint: /apis/ccompat/v6

My questions & tickets

(Solved) https://stackoverflow.com/questions/76145463/java-lang-classnotfoundexception-io-apicurio-registry-serde-avro-avrokafkaseria
(Solved) https://github.com/Apicurio/apicurio-registry/issues/3309
(Solved) https://stackoverflow.com/questions/76149658/how-to-use-spark-kafka-jdbc-sink-connector-with-avro-correctly

(Failed) Karapace: https://github.com/aiven/karapace

My questions & tickets

https://stackoverflow.com/questions/76144191/got-servname-not-supported-for-ai-socktype-when-deploy-karapace-schema-registr
https://github.com/aiven/karapace/issues/593

(Skipped, not popular) Registry
(Skipped, commercial solution) AWS Glue Schema Registry
strimzi-kafka-operator

Won't have its own schema registry, but can integrate with other popular solutions such as Confluent Schema Registry, Apicurio Registry easily which makes sense: https://github.com/strimzi/strimzi-kafka-operator/issues/29

Compare

https://supergloo.com/streaming/schema-registry/

(Apicurio Registry has managed service offering too now at https://console.redhat.com/application-services/service-registry)

https://github.com/aiven/karapace/issues/397

Added by https://github.com/Hongbo-Miao/hongbomiao.com/pull/8478


Change file format from json to yaml

Coverage decreased (-1.6%) to 85.396% when pulling 071c9155b6f73f7d1db004ed8fe0701ab2caf9e9 on upload_yaml into df69f5d0140030f196393e3b070ec6a2b1aa5962 on add_upload.

Coverage decreased (-1.01%) to 86.004% when pulling 18fd20b7699b2f6d52484017235110de29cf36b0 on upload_yaml into df69f5d0140030f196393e3b070ec6a2b1aa5962 on add_upload.


Use of LiteLLM Router for load balancing and fallbacks

As DSPy is using LiteLLM internally, I wonder how to use the LiteLLM router. In particular, I would like to add load balancing and fallbacks via LiteLLM.
Another example. LiteLLM provides rate limit aware routing strategy that routes the call to the deployment with the lowest tokens per minute value (see https://github.com/BerriAI/litellm/discussions/4510, https://docs.litellm.ai/docs/routing#advanced---routing-strategies-). I would want to use the router
Thank you

Link: https://github.com/stanfordnlp/dspy/blob/main/examples/migration.ipynb

Thank you, Omar! I think it makes sense to expose router of LiteLLM as well. Under some circumstances, one would not want to run a separate proxy server and prefer using the LiteLLM Router for fallbacks, load balancing, and request prioritization

@denisergashbaev Isn't the LiteLLM router a proxy? Perhaps I'm mistaken about the nature of the LiteLLM router.

Yes, I think we should support this. It seems like we should inherit dspy.LM and just accept a list of models instead of one model. This seems cool. Do you need this soon? We'd certainly appreciate a PR.

Down to work on this if needed

@zhaohan-dong Thanks a lot! How do you envision the interface looking like? Let's agree on the right API before doing anything intensive :D

Exactly what I hoped to ascertain I think litellm tries to have similar signature for Router as the plain generation methods. So I'm thinking it could be progressively do dependency injection as first step:

An argument router: Optional[litellm.Router] = None
If router != None, the inference call would invoke router.text_completion()
If model not in the router's model_list, throw error (Not 100% this is the cleanest way)

Otherwise could inherit LM with AnotherClass(model_list=model_list, **kwargs), so people who wnat to use the router would use that, and not affecting other users. Not sure what's the best naming/file to put it in.
Happy to proceed either way or do something else you'd suggest.
Fundamentally I see the plain litellm.text_generation() as a special case of Router.text_generation(), where there's only one model in the model_list.

Thanks a lot @zhaohan-dong ! I like the idea of a class that inherits from dspy.LM

Thanks for the response and your willingness to help. Let me know if I could help as well.

@denisergashbaev I tried a PR here: https://github.com/stanfordnlp/dspy/pull/1611. Dunno if you could collab?

Hi! Checking in on this, I would love to leverage this if someone has on a branch somewhere. Would be happy to write some integration tests so that it can be merged eventually.

@ryanh-ai Have a branch here https://github.com/zhaohan-dong/dspy/tree/litellm-router


pretrained models for places365 scene recognition dataset

can we have pretrained models for places365 scene recognition dataset.
https://arxiv.org/abs/1610.02055

@andresusanopinto  Could you please confirm if this is open for external contributions or has this been taken care internally ?

Hello @andresusanopinto @hgadig I would like to work on this as part of GSoC under the project TensorFlow Hub Module Creation and Support for TensorFlow.js.


Do not update pod labels if they haven't changed

Why are these changes needed?
See #1303 for more context.
I decided on some light future-proofing by checking if any labels have changed before updating the pod (though there is only one label being changed right now).
Related issue number
Closes #1303
Checks

[x] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

I followed DEVELOPMENT.md and was able to stand up a RayService in a local kind cluster using an operator image built from this PR:
❯ k get po -n default
NAME                                                      READY   STATUS    RESTARTS   AGE
ervice-sample-raycluster-pn4cd-worker-small-group-qfntp   1/1     Running   0          6m46s
kuberay-operator-5987588ffc-dg2mn                         1/1     Running   0          23m
rayservice-sample-raycluster-pn4cd-head-fnsl6             1/1     Running   0          6m46s

❯ k get svc -n default
NAME                                          TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                                                   AGE
custom-ray-serve-service-name                 LoadBalancer   <IP_ADDRESS>   <pending>     8000:30266/TCP                                            5m54s
kuberay-operator                              ClusterIP      <IP_ADDRESS>    <none>        8080/TCP                                                  23m
kubernetes                                    ClusterIP      <IP_ADDRESS>       <none>        443/TCP                                                   25m
rayservice-sample-head-svc                    ClusterIP      <IP_ADDRESS>     <none>        10001/TCP,8265/TCP,52365/TCP,6379/TCP,8080/TCP,8000/TCP   5m54s
rayservice-sample-raycluster-pn4cd-head-svc   ClusterIP      <IP_ADDRESS>    <none>        10001/TCP,8265/TCP,52365/TCP,6379/TCP,8080/TCP,8000/TCP   6m29s

❯ k describe pod/ervice-sample-raycluster-pn4cd-worker-small-group-qfntp
Name:         ervice-sample-raycluster-pn4cd-worker-small-group-qfntp
Namespace:    default
Priority:     0
Node:         kind-control-plane/<IP_ADDRESS>
Start Time:   Tue, 08 Aug 2023 15:06:05 -0500
Labels:       app.kubernetes.io/created-by=kuberay-operator
              app.kubernetes.io/name=kuberay
              ray.io/cluster=rayservice-sample-raycluster-pn4cd
              ray.io/group=small-group
              ray.io/identifier=rayservice-sample-raycluster-pn4cd-worker
              ray.io/is-ray-node=yes
              ray.io/node-type=worker
              ray.io/serve=true
Annotations:  ray.io/ft-enabled: false
              ray.io/health-state:
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  RayCluster/rayservice-sample-raycluster-pn4cd
Init Containers:
  wait-gcs-ready:
    Container ID:  containerd://ee18aa5754c97cf592f10a24fc04b712354b6577a0a778de47ec9c5aa04e74a9
    Image:         rayproject/ray:2.5.0
    Image ID:      docker.io/rayproject/ray@sha256:cb53dcc21af8f913978fd2a3fc57c812f87d99e0b40db6a42ccd6f43eca11281
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      -lc
      --
    Args:

                            SECONDS=0
                            while true; do
                              if (( SECONDS <= 120 )); then
                                if ray health-check --address rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local:6379 > /dev/null 2>&1; then
                                  echo "GCS is ready."
                                  break
                                fi
                                echo "$SECONDS seconds elapsed: Waiting for GCS to be ready."
                              else
                                if ray health-check --address rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local:6379; then
                                  echo "GCS is ready. Any error messages above can be safely ignored."
                                  break
                                fi
                                echo "$SECONDS seconds elapsed: Still waiting for GCS to be ready. For troubleshooting, refer to the FAQ at https://github.com/ray-project/kuberay/blob/master/docs/guidance/FAQ.md."
                              fi
                              sleep 5
                            done

    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 08 Aug 2023 15:06:06 -0500
      Finished:     Tue, 08 Aug 2023 15:06:17 -0500
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  2Gi
    Requests:
      cpu:     500m
      memory:  2Gi
    Environment:
      FQ_RAY_IP:  rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local
      RAY_IP:     rayservice-sample-raycluster-pn4cd-head-svc
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-fftq7 (ro)
Containers:
  ray-worker:
    Container ID:  containerd://ed185f50ffaf8a90922efa821d143969eec271740f4780877890f498596ca56d
    Image:         rayproject/ray:2.5.0
    Image ID:      docker.io/rayproject/ray@sha256:cb53dcc21af8f913978fd2a3fc57c812f87d99e0b40db6a42ccd6f43eca11281
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      /bin/bash
      -lc
      --
    Args:
      ulimit -n 65536; ray start  --metrics-export-port=8080  --block  --dashboard-agent-listen-port=52365  --num-cpus=1  --memory=2147483648  --address=rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local:6379
    State:          Running
      Started:      Tue, 08 Aug 2023 15:06:18 -0500
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  2Gi
    Requests:
      cpu:     500m
      memory:  2Gi
    Environment:
      FQ_RAY_IP:                                  rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local
      RAY_IP:                                     rayservice-sample-raycluster-pn4cd-head-svc
      RAY_CLUSTER_NAME:                            (v1:metadata.labels['ray.io/cluster'])
      RAY_PORT:                                   6379
      RAY_timeout_ms_task_wait_for_death_info:    0
      RAY_gcs_server_request_timeout_seconds:     5
      RAY_SERVE_KV_TIMEOUT_S:                     5
      RAY_INTERNAL_SERVE_CONTROLLER_PIN_ON_NODE:  0
      RAY_ADDRESS:                                rayservice-sample-raycluster-pn4cd-head-svc.default.svc.cluster.local:6379
      RAY_USAGE_STATS_KUBERAY_IN_USE:             1
      REDIS_PASSWORD:
      RAY_DASHBOARD_ENABLE_K8S_DISK_USAGE:        1
    Mounts:
      /dev/shm from shared-mem (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-fftq7 (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             True
  ContainersReady   True
  PodScheduled      True
Volumes:
  shared-mem:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  2Gi
  kube-api-access-fftq7:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason     Age    From               Message
  ----    ------     ----   ----               -------
  Normal  Scheduled  7m56s  default-scheduler  Successfully assigned default/ervice-sample-raycluster-pn4cd-worker-small-group-qfntp to kind-control-plane
  Normal  Pulled     7m55s  kubelet            Container image "rayproject/ray:2.5.0" already present on machine
  Normal  Created    7m55s  kubelet            Created container wait-gcs-ready
  Normal  Started    7m55s  kubelet            Started container wait-gcs-ready
  Normal  Pulled     7m44s  kubelet            Container image "rayproject/ray:2.5.0" already present on machine
  Normal  Created    7m43s  kubelet            Created container ray-worker
  Normal  Started    7m43s  kubelet            Started container ray-worker

❯ k describe svc/custom-ray-serve-service-name
Name:                     custom-ray-serve-service-name
Namespace:                default
Labels:                   custom-label=custom-ray-serve-service-label
                          ray.io/serve=rayservice-sample-serve
                          ray.io/service=rayservice-sample
Annotations:              custom-annotation: custom-ray-serve-service-annotation
Selector:                 ray.io/cluster=rayservice-sample-raycluster-pn4cd,ray.io/serve=true
Type:                     LoadBalancer
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
Port:                     serve  8000/TCP
TargetPort:               8000/TCP
NodePort:                 serve  30266/TCP
Endpoints:                <IP_ADDRESS>:8000,<IP_ADDRESS>:8000
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

So cluster formation looks good, but I'm not really sure how to test the opposite case where the label should go from true to false. Open to suggestions!
Also I don't really know anything about go - please review carefully for style and correctness :)

Thank you for the PR! I will review it today.

Thank you for the contribution! Would you mind running some e2e tests by the following command in the root directory of kuberay repository? Currently, these tests are not in CI pipeline due to some CI infra issues.
RAY_IMAGE=rayproject/ray:2.5.0 OPERATOR_IMAGE=controller:latest pytest -vs tests/test_sample_rayservice_yamls.py --log-cli-level=INFO

This PR looks good to me, provided it can pass the e2e tests in your local environment.

The autoscaling test is actually failing on both master and my branch, at least for me 😬
FAILED tests/test_sample_rayservice_yamls.py::TestRayService::test_service_autoscaling - TimeoutError: Cluster did not scale to the expected number of 1 worker pod(s) within 400 seconds. Cluster is currently at 5 worker pods.

So that doesn't seem related to my change... but maybe related to something else in my local setup? Thoughts?

In the future, I might consider using a readiness probe to determine whether a worker Pod is ready to serve requests. Relying on the KubeRay operator to check the availability of each Pod doesn't seem scalable.

I was actually just asking about something related on Ray Slack and @edoakes was talking about some other changes to the Serve HTTP proxy related to autoscaling, where the proxy now returns a 503 error if the Ray worker doesn't have any other Serve replicas on it. We were seeing these 503s in the KubeRay operator, which triggered some of our alerting. So moving to a k8s readiness check would fix that (no 503s between the operator and the worker pods)... but then our pods would be unready and we also alert on that!
I haven't thought deeply about it, but it seems like the problem is that we need to distinguish between a variety of states:

The worker pod is healthy (health)
The worker pod is healthy and has a healthy Serve proxy on it (ready)
The worker pod is healthy, has a healthy Serve proxy on it, and traffic should be routed to that pod (ready and... enabled? 🤔 )

But maybe those states will change with the work @edoakes was talking about?

The autoscaling test is actually failing on both master and my branch, at least for me 😬
FAILED tests/test_sample_rayservice_yamls.py::TestRayService::test_service_autoscaling - TimeoutError: Cluster did not scale to the expected number of 1 worker pod(s) within 400 seconds. Cluster is currently at 5 worker pods.

So that doesn't seem related to my change... but maybe related to something else in my local setup? Thoughts?

cc @zcin do you have any thoughts?

I was actually just asking about something related on Ray Slack and @edoakes was talking about some other changes to the Serve HTTP proxy related to autoscaling, where the proxy now returns a 503 error if the Ray worker doesn't have any other Serve replicas on it.

I'm confused about this. In my understanding, if a node lacks the requested replica, the HTTP Proxy Actor would forward the request to the node containing that replica rather than returning 503. I will check the Ray Serve team, and will keep you updated.

The worker pod is healthy (health)
The worker pod is healthy and has a healthy Serve proxy on it (ready)
The worker pod is healthy, has a healthy Serve proxy on it, and traffic should be routed to that pod (ready and... enabled? 🤔 )

Would you mind explaining the difference between (2) and (3)? From my understanding, a failed readiness probe will cause the container's service endpoint to be removed, and it will not receive any new traffic. Hence, (2) will not receive any new traffic.

Sorry, I should have linked more context - this is very specifically about the question I asked here: https://ray-distributed.slack.com/archives/CNCKBBRJL/p1691532723786239?thread_ts=1690284353.203859&cid=CNCKBBRJL .
re: (2) vs (3) My thought was that a pod with nothing on it but the proxy actor would actually report unready and thus be taken out of the Service, as you say. But it's not really "unready" in a k8s sense (it could serve a request), we just don't want traffic flowing to it. That might mess up monitoring schemes that check for unready pods, which is a fairly common pattern (at least from what I've seen).

That might mess up monitoring schemes that check for unready pods

Would you mind adding more details on how does "monitoring schemes" work for unready Pods? Thanks!

Btw, I can reproduce this error. I thought I broke something recently 😭. I will fix it ASAP.

[Update] "503 error"
When a Ray node is not properly serving traffic (either the node is unhealthy or there are no replicas on the node), the health check queries to /-/healthz or /-/routes will get 503 to avoid load balancers (e.g. ALB) routing traffic to this node. The actual requests will still be forwarded.

Btw, I can reproduce this error. I thought I broke something recently 😭. I will fix it ASAP.

[Update]
I found that the tests failed because the image kuberay/operator:nightly is pretty old (~ months ago). I deleted the image, ran the tests again, and they passed.
RAY_IMAGE=rayproject/ray:2.5.0 OPERATOR_IMAGE=kuberay/operator:nightly pytest -vs tests/test_sample_rayservice_yamls.py --log-cli-level=INFO

I cloned your branch, built the image, and ran the tests:
RAY_IMAGE=rayproject/ray:2.5.0 OPERATOR_IMAGE=controller:latest pytest -vs tests/test_sample_rayservice_yamls.py --log-cli-level=INFO

That might mess up monitoring schemes that check for unready pods

Would you mind adding more details on how does "monitoring schemes" work for unready Pods? Thanks!

Sure - I will DM you on Ray Slack so I can provide some more details


How can I get current index in child controllers?

I am looking at the readme and found that there is a currentIndex var.
However this is only available in parent view controller. How do I get this var in 3 of my child controllers where when I print this var in viewDidAppear I can get 1,2,3 respectively?
Anywhere other way to capture the current index in child controllers?
Someone please help me
Thanks

override func updateIndicator(for viewController: PagerTabStripViewController, fromIndex: Int, toIndex: Int, withProgressPercentage progressPercentage: CGFloat, indexWasChanged: Bool) {
super.updateIndicator(for: viewController, fromIndex: fromIndex, toIndex: toIndex, withProgressPercentage: progressPercentage, indexWasChanged: indexWasChanged)
if indexWasChanged && toIndex > -1 && toIndex < viewControllers.count {
print("New index: (toIndex)")

Can this help you? #179


No license?

Hey! I see there seems to have no license mentioned in this repo, is it on purpose?
Very clean UI btw!

:)


S3 cache: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.

Hi,
I am getting the following error durring saving file to S3 cache:
s3util.Create failed: unwanted http status 400: "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error>InvalidRequest<Message>The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.</Message>
I found the same error in another repos and it seems that it's related to the buckets that are placed in Frankfurt: http://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4

I've now switched over to the official aws-sdk-go package, which supports the newer v4 authentication method.  I've tested it myself with a bucket in Frankfurt, and everything seems to work well.


Records fetch limit decreases after several requests

Hello.
I'm trying to fetch records from my org.
For first several requests it returns the amount, as the same SOQL in Develop Console, e.g. 1500
But then, after several requests it begins to return only maximum 1000 records.
Firstly, I queried al through query chain, and this happened.
Then, I switched to single string, and again, after 10-15 successful responses, SF became to return maximum 1000 records with same conditions.
Is there a way not to use OFFSET? Maybe it happens because of limits of requests from concrete IP or what?

Salesforce will return a different number of records based on how expensive the dataset is. E.x. if you have a subquery in your SOQL and all records have related child recs, that will return fewer records.
This is not something that can be controlled and it is how the SFDC API works and is not related to JSForce. I have seen as few as 100 records be returned or as many as 2000 records being returned from any individual query.

Salesforce will return a different number of records based on how expensive the dataset is. E.x. if you have a subquery in your SOQL and all records have related child recs, that will return fewer records.
This is not something that can be controlled and it is how the SFDC API works and is not related to JSForce. I have seen as few as 100 records be returned or as many as 2000 records being returned from any individual query.

Thanks for the answer, paustint.
But still, why it used to return full set of records with same conditions at several early responses?


Open source some of the configuration files of private server

See https://github.com/libnapc/libnapc-documentation-site/


More ways to use hops

From comment: "Good app, just needs more features. I like that the description is right there with each ingredient. Adding a selection for First Wort Hops or whirlpooling hops would make it better."
Regarding flame-out hops: Ideally we'd like to calculate some IBU addition for this, though I can't find appropriate literature for that calculation.  The addition is probably minimal, but still significant.

#24 and #23 add some support for additional hop varieties.  Should go into next release.


Issue with loading saved models

Hi,
I'm trying to save and load the tokenizer and model.
I use the following to save them:
tokenizer = AutoTokenizer.from_pretrained("prithivida/informal_to_formal_styletransfer")
tokenizer.save_pretrained('./data/style_tokenizer')
model = AutoModelForSeq2SeqLM.from_pretrained("prithivida/informal_to_formal_styletransfer")
model.save_pretrained('./data/style_model')

But when I try to load them, from the local path, I get the following error:
OSError: Can't load config for '../data/style_tokenizer'. Make sure that:

- '../data/style_tokenizer' is a correct model identifier listed on 'https://huggingface.co/models'

- or '../data/style_tokenizer' is the correct path to a directory containing a config.json file

This somehow makes sense since saving the vectorizer, no config.json is being created.
Any idea how can I save/load the tokenizer and model?

Refer to bug 1
It's better to check if there are any similar closed bugs before opening one.


How to choose appropriate thread, connection and rate ?

These three factors are tightly related. It's very easy for users to give a wrong rate which doesn't match with the given threads or connections. How should we avoid this ?
Furthermore I don't understand why rate parameter is required. What if I just want to stress the server with unlimited rate ?

Check the following two images. Why does the latency go up heavily when I increase rate ?

When I want rate to be fixed, but I don't know the lower bound numbers of connections can reach that fixed rate. After all I'd rather choose that number, because when num of connections go up, the latency go up too.

Just some thoughts, this doesn't answer your question.
I think you bring up a great question. Some general guidance on how to set these parameters would be great. That said, I think the answer to your question of "what if I want an unlimited rate" is to simply set rate some ungodly large number like 10 billion requests per second.
As for connection count. I think the appropriate value here might be more related to the server you are stress/load testing. It's likely dependent on how many connections the server you are trying to test can handle.
As for threads, I always just match it up with the number of threads/cores on the machine running wrk2.

Greate qustion.
Check the following two images. The result is very confusing！


feature - improve ux

Github Issue URL/Tags (required)
What's this PR do? Please give a technical summary (required)

[x] up font size of menu title, item of home, delete user name

Any references (stackoverflow …) (optional)

:+1: There are no linter violations.