Remove maxLength for fcp_templ_id_list and fix bug for creating fcp tmpl

In this PR:

Remove maxLength for fcp_template_id_list since we have the fcp tmpl id check.
When creating fcp template, if not set storage_providers, its default value is None. Then error will be raised.

It's related to:
https://github.ibm.com/zvc/planning/issues/9968
https://github.ibm.com/zvc/planning/issues/10109
Signed-off-by: xingjing<EMAIL_ADDRESS>

______________________________________ summary _________________________________________
pep8: commands succeeded
py36: commands succeeded
docs: commands succeeded
congratulations :)


Improve dataset performance by shuffling first in image_captioning example

First of all, thanks for this (and also all the others) example! It was a great starting point for a small captioning project I'm working on.
I've found that there is a performance bottleneck in the input pipeline, when performing the shuffling of the dataset, which could be avoided by shuffling the images names list first, and then loading the images from disk.
The change is pretty straightforward (just requires mapping of the image + caption together instead of zipping later on), and I've checked for consistent improvements both locally and using Colab.
Before change (Colab GPU instance)

After change (Colab GPU instance)

Besides the performance gain, since we are shuffling only the filenames, the whole list can be fitted into the shuffling buffer, thus achieving better randomness in the shuffle.
Feel free to merge/reply with comments.

@fedeallocati please fix the formatting by applying black: https://github.com/keras-team/keras-io/runs/4056187619?check_suite_focus=true

@fchollet sorry about that, should be good now. Thanks!


Task 28

Complete all the PDF activities task in one or two Sequence.

SourceCode/2024/May 2024/Bhavya/Task 28/project.json
activity_read_pdf_text.xaml
The file name is quite generic and doesn't give much context about what this activity does. Consider renaming it something like "Extract Text from PDF" or "Read PDF Content". This would make it easier for others (and yourself) to understand the purpose of this activity.
activity_read_pdf_with_ocr.xaml
Similar to above, the file name is quite generic and doesn't provide much context about what this activity does. Consider renaming it something like "Extract Text with OCR from PDF" or "Read PDF Content with Optical Character Recognition".
activity_tesseract_ocr.xaml
Again, the file name is quite generic and doesn't provide much context about what this activity does. Consider renaming it something like "Use Tesseract OCR to Extract Text" or "Perform OCR on Text Using Tesseract Library".
activity_get_pdf_page_count.xaml
The file name is quite generic and doesn't provide much context about what this activity does. Consider renaming it something like "Get Page Count from PDF" or "Count Pages in PDF File".
nofile
It looks like the organization requires the project to have an Automation Hub URL defined. This can be easily fixed by going to the Project Settings and adding the missing information.

SourceCode/2024/May 2024/Bhavya/Task 28/project.json
ReadPdfText.xaml

Activity name is quite generic. Suggest renaming it something like "Extract Text from PDF" or "Read PDF Content".
This change will make it easier for others (and yourself) to understand what the activity does.

ReadPdfWithOcr.xaml

Same as above, the default name is quite vague. Consider renaming it something more descriptive like "Extract Text and Data from PDF with OCR".

TesseractOcr.xaml

Same as above, the default name doesn't give much away. Suggest renaming it to something like "Perform OCR on PDF using Tesseract" or "Recognize Text in PDF using Tesseract".

GetPdfPageCount.xaml

Similar to the others, the default name is quite generic. Consider renaming it something more descriptive like "Get Page Count from PDF File" or "Determine Number of Pages in a PDF".

NoFile.xaml

The organization requires an Automation Hub URL defined for the project. This information should be added via Project Settings.

Score: 5/5


about the reproduction of DIVERSIFY

Thank you for your impressive work.
I noticed that your released code is built on Pytorch-1.13. However, the Cuda driver version on our server can not support Pytorch-1.13 and I can not install docker on our server. So, I created an environment with PyTorch-1.7.1 on our server and tried to reproduce the result. However, the result is very different from yours as shown in the image:

So, I think there must be other things affecting the results. Could you provide more details about the environment with PyTorch-1.7.1 (for instance, the version of Scipy in our server is 1.7.3?
BTW, do you have any specific selection approach?
Thank you for your help
Regards.

The test-env is 0

Hi @gkyustc, thank you for your interest in this work. First of all, different pytorch versions can definitely lead to different results, but I think the difference should not be large. Second, the best practice is to run hyperparameter search in different version due to such difference. Therefore, it is natural that you did not get the same or close results as we claimed in the code since you did not perform hyperparameter search in this 1.7 version. Am I right?
Suggestions for next steps: try to upgrade to the same version (you can leverage Google Colab which supports GPUs); run hyperparameter search on your current version to get the best results.
Involving @lw0517 here for further assistance.

Thank you for your reply.
I recheck the hyperparameter and find that the epoch number in the paper is different from the cmd in readme.md. So I rerun the code and the result is shown in the following:

Here, I provide the command running the code:
python train.py --data_dir ~/data/EMG/ --task cross_people --test_envs 0 --dataset emg --algorithm diversify --latent_domain_num 10 --alpha1 1.0 --alpha 1.0 --lam 0.0 --local_epoch 3 --max_epoch 150 --lr 0.01 --output ~/data/EMG/logs
The above cmd is same as the cmd in readme excluding the --max_epoch.
Please let me know if there is anything wrong. Thank you very much
Regards.

Hi, I don't think you carefully read my first reply. Since you use a different pytorch version, the environment is not the same. Therefore, you need to perform hyperparameter search instead of using the hyperparameters we provided.

Thank you for your advice.  I got a significant improvement on the performance after modifying the hyperparameter.  But there is still a little issue confusing me:
The results on the four test-envs are
0.6995      0.8616        0.7703         0.7667
It seems like the performance on the first two domains is not as stable as the last two domains. I am not sure if you have the same issue. Whatever, thank you for your help very much.
Regards.


function on alt animation?

Describe your problem here.
i need help making a lua funciton for when an alt-animation is played.
i want this to play when an alt animation is used
makeAnimatedLuaSprite('ghostdown','characters/ghost', ghdwnx,ghdwny)
addAnimationByPrefix('ghostdown','alt down','ghost Down alt',24,false)
addLuaSprite('ghostdown',false)
objectPlayAnimation('ghostdown','alt down',true)
setProperty('ghostdown.alpha',0)

and if it isnt an alt animation, this
makeAnimatedLuaSprite('ghostdown','characters/ghost', ghdwnx,ghdwny)
addAnimationByPrefix('ghostdown','down','ghost Down',24,false)
addLuaSprite('ghostdown',false)
objectPlayAnimation('ghostdown','down',true)
setProperty('ghostdown.alpha',0)
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

Check callbacks on wiki


publish wheel

we should put a (universal) wheel on pypi

Implemented in https://github.com/onefinestay/nameko/pull/242


Bukkit website has deleted the forums entirely?

All of the Guides and Troubleshooting posts that I had created on the Bukkit website appear to be gone completely since there is no access to the forums that were there, as far as I can tell.
Are you seeing this also?

Hey there,
The forums aren’t deleted; all of the data still exists on the old database. Unfortunately there wasn’t time to complete that feature on the new sites before the end of our timetable to decommission the old sites, so they will temporarily be unavailable. The project forums will make a return, however, so please bear with us during the transition.
We’re very sorry for the inconvenience!
Take care,
Torhal

ok, good to know -- I've also pinged folks in #bukkitdev
gotta love curse messing up things again

Thank you very much for continuing the maintenance and updates on PEX which I have been using since 2012. I am trying to set up a new server with a late build of spigot 1.11.2 and have a problem of PEX not adding the default group to a new player's entry in the permissions.yml file when PEX creates their record in it.
I have posted this issue to the Spigot server plugin forum several days ago and not even a comment was added there. The Spigot forums are almost useless because there are so many posting in the same category and thread updates shove others back up to the top of the list, within a day or two my issue is shoved several pages down in the list of threads.
My question is since PEX forum on bukkit still is not back up, where is the best place to post PEX issues?

My question is since PEX forum on bukkit still is not back up, where is the best place to post PEX issues?

This is the official ticket location for PEX, so here is fine.  (But you should have started your own ticket, instead of adding to an old one.)

PEX not adding the default group to a new player's entry in the permissions.yml file when PEX creates their record in it.

This is actually working as intended in PEX 1.x because PEX knows that any user not showing a group in the users: section belongs to whichever group is default: true.  This is so server owners who are using PEX don't have to manually move hundreds or thousands of users from and old default: true group into whatever new default: true group the server changes to.

My server is not working this way. New players are not getting any permissions at all. I will start a new thread here as"PEX not adding new players to the default group.". Thanks.

Without a maintained plugin, we have no need of a forum, so this issue is no longer a problem.


Ensure silence is active during healthcheck

To ensure that a silence is always active we set the silence at the beginning of the for loop before we run the healthcheck.
If there is no silence set, we set it to 1 hour and remove the silence if the healthcheck is successful. If the healthcheck is not successful we loop and validate that silence is at least active for another 15 minutes before running the next healthcheck, if it isn't we edit the healthcheck and set it to expire in 15 minutes from now.
Future updates:
Don't set the updated silence to 15 minutes, we could compute the total time required from available envs.

/lgtm

/lgtm


Consider enforcing the use of the default keyword

Is your feature request related to a problem? Please describe.
Consider the following example:

from pydantic import Field, BaseModel

class Foo(BaseModel):
    foo_property: int = Field(0)

class Bar(BaseModel):
    bar_property: int = Field(default=0)

foo = Foo()
# Intellisense output: (*, foo_property: int) -> None

bar = Bar()
# Intellisense output: (*, bar_property: int = 0) -> None

Without the explicit use of the default keyword, intellisense fails to provide the default value of the class. (I am using vscode, not sure if other editors suffer from the same problem).
Describe the solution you'd like
Enforce the use of the default keyword to make the lives of people using the schemas easier. Having the default value be provided as part of the IntelliSense string is a really helpful hint! We should also investigate if it is possible to run a check on all models and see if the keyword exists. Could even be part of the unit tests.
Describe alternatives you've considered
N/A
Additional context

I'm okay with this. @jtyoung84?

I'm okay with this. @jtyoung84?

I'm cool with this also. I'm not sure how to programmatically enforce it without adding the mypy library or something, which might turn into a larger task.

Can we please keep using this standard? It makes really difficult to use statically typed libraries if the default keyword is never used. For instance, the Session class seems to be a mix between properties with this standard and others without.


Re-implement operations in terms of Fn traits

Essentially, Op: Fn<Args> replaces Args: Eval<Op>. Generalizing Thunk to work with Fn requires implementing currying for Fn.

Already started doing this though currying isn't implemented yet.


[Testnet release] Risc scoring with HAPI

This is reopened PR https://github.com/near/near-wallet/pull/2840 with all the fixes https://github.com/near/near-wallet/pull/2849, https://github.com/near/near-wallet/pull/2845, https://github.com/near/near-wallet/pull/2853
Also PR closes this issue https://github.com/near/near-wallet/issues/2646

@followdarko Jenkins has been disabled will need to rebase this branch with master for it to clear


'Continue watching' row bug

Describe the bug
The order of items in a specific row seems to change if an item is played and the user returns to the grid screen.  This only occurs if the 'Continue watching' attribute is enabled in the manifest.
To Reproduce
Steps to reproduce the behavior:

Select and play an item on the Grid screen.
After a few seconds, stop.
Return to the Grid screen.
Notice the item is no longer in its original row and has been moved to the 'Continue watching' row.

Expected behavior
The item should remain in its original row and added to the 'Continue watching' row.
Screenshots
N/A
Version number:

Version <IP_ADDRESS>

Additional context
N/A

Resolved in <IP_ADDRESS>.


add selector to exclude storageClassName patch from some StatefulSets

make sure that StatefulSets that have no volumeClaimTemplates do not get the sas-ss-storageclass overlay.
fixes #126
fixes #121
tested by successfully deploying order with both Risk Management and SWO.

Could the transformers for these products not do this? Not a good idea to start hard coding product information into the deployment code base. @enderm work with the product teams to add transforms to their products to handle this and make sure they implement the same way. I am sure others will also have these issues.

@Thomas @.***> I agree that encoding production information is not ideal.
Can you please explain what you have in mind? How could the transformers for those product achieve what we need here?
From: Thomas S. Pangborn @.>
Sent: Friday, September 24, 2021 9:01 AM
To: sassoftware/viya4-deployment @.>
Cc: Matthias Ender @.>; Mention @.>
Subject: Re: [sassoftware/viya4-deployment] add selector to exclude storageClassName patch from some StatefulSets (#149)
EXTERNAL
Could the transformers for these products not do this? Not a good idea to start hard coding product information into the deployment code base. @endermhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fenderm&data=04|01|matthias.ender%40sas.com|edc9b16ad0b7435bcbf308d97f5b5cb7|b1c14d5c362545b3a4309552373a0c2f|0|0|637680852686044073|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OuMZINT%2BZxCmNQ8GhncB8YxRdkgSHrHxqq6euyT7exA%3D&reserved=0 work with the product teams to add transforms to their products to handle this and make sure they implement the same way. I am sure others will also have these issues.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsassoftware%2Fviya4-deployment%2Fpull%2F149%23issuecomment-926606155&data=04|01|matthias.ender%40sas.com|edc9b16ad0b7435bcbf308d97f5b5cb7|b1c14d5c362545b3a4309552373a0c2f|0|0|637680852686044073|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=EXU%2BgVpKXcwHBQsxIWXTVRyRMZvLQfhW059rsSCFFvk%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACUQLJMQ6RC2L4L3PPTHU5DUDRZA3ANCNFSM5ET6VB2Q&data=04|01|matthias.ender%40sas.com|edc9b16ad0b7435bcbf308d97f5b5cb7|b1c14d5c362545b3a4309552373a0c2f|0|0|637680852686044073|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=BYHDLvN08tWa2uGT3kr4%2FpjoM24H0XqFZ%2BvAOubunPA%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|matthias.ender%40sas.com|edc9b16ad0b7435bcbf308d97f5b5cb7|b1c14d5c362545b3a4309552373a0c2f|0|0|637680852686054029|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qNCRbLlmEi2Htvn%2Bc9TyTlWCiS3nI7MvOf7HYH32pio%3D&reserved=0 or Androidhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|matthias.ender%40sas.com|edc9b16ad0b7435bcbf308d97f5b5cb7|b1c14d5c362545b3a4309552373a0c2f|0|0|637680852686054029|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JxWR3b58SAEq%2FEmxc8PJjnKKHjzGVfPK2%2BWfXnsqBFY%3D&reserved=0.

If the development teams cannot create an empty transformer for the storage class, they will need to document how to add the entry into the sas-storageclass.yaml. If the teams are choosing other options for storage class type, this needs to be addressed. Granted I know the code works here; however, the list will soon grow. Going to bring this up to the K8s sig and see what their thoughts are on this one. Need a solution not a patch.

Are you done with this?
If yes, could you please create a private docker image which including this fix?

Merging to keep folks moving will re-address in the future for a more robust solution.


Remove System.Data.SqlClient and migrate to Microsoft.Data.SqlClient

Fixes: #323

CI complains about, no output received. It works actually. I couldn't re-trigger.

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received

Will take a look.


rcd shows wrong sort order with version _rc

I think I can "complain" and report this super low priority issue just because of the high level product that is iwdevtools
When I performed rcd dev-python/exceptiongroup on gentoo tree, the version where in wrong order:
$ rcd exceptiongroup
 > ~/dev/gentoo/dev-python/exceptiongroup
 D Backport of PEP 654 (exception groups) (1.0.0_rc9)
 H https://github.com/agronholm/exceptiongroup/
 H https://pypi.org/project/exceptiongroup/
 G https://packages.gentoo.org/packages/dev-python/exceptiongroup
 G https://bugs.gentoo.org/buglist.cgi?quicksearch=dev-python%2Fexceptiongroup
 M<EMAIL_ADDRESS> + Manifest
 + exceptiongroup-1.0.0.ebuild
 + exceptiongroup-1.0.0_rc8.ebuild
 + exceptiongroup-1.0.0_rc9.ebuild
 + metadata.xml

While the correct ordering should be:
pkgdev showkw
           a a   a     l       p r   s
           l m   r h i o m m   p i s p   e s r
           p d a m p a o 6 i p c s 3 a x a l e
           h 6 r 6 p 6 n 8 p p 6 c 9 r 8 p o p
           a 4 m 4 a 4 g k s c 4 v 0 c 6 i t o
---------------------------------------------------
 1.0.0_rc8 ~ + + + + ~ o ~ ~ + + ~ ~ + + 8 0 gentoo
 1.0.0_rc9 ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ 8 0 gentoo
 1.0.0     ~ ~ ~ ~ ~ ~ o ~ ~ ~ ~ ~ ~ ~ ~ 8 0 gentoo

I'm fine if you just close it as won't fix, but just reported it in case it can be easily fixed?

This is not really iwdevtools, this is just a basic default/example for --run:
  -R, --run=COMMAND   If atom matches a package, run COMMAND then exit with
                      its status, see *Running Commands* for details
                      (default: ls -1v --color=always)

People are encouraged to run their own scripts to display whatever is useful to them (see README.rst for some examples), and either keep running ls in it or some other commands as they prefer.

Of course, you can also do rcd --run="pkgdev showkw" and use ~/.config/iwdevtools/repo-cd.conf to make it default :eyes:


error

[WARNING]: RuntimeException: "yaml_parse(): scanning error encountered during parsing: found unexpected ':' (line 11, column 26), context while scanning a plain scalar (line 11, column 11)" (E_WARNING) in "/src/pocketmine/utils/Config" at line 148

Post your config file please.

default file

nothing change

fixed remove [ ]


Update clic.adoc

spelling error

thanks.  I ran a spell check and fixed some other spelling errors as well.


Forcing kubectl log to wait when container is creating

What would you like to be added:
When we do kubectl logs <pod> [-f] on a container in creation, we get this error message:
Error from server (BadRequest): container "<container>" in pod "<pod>" is waiting to start: [ContainerCreating, PodInitializing]

In this situation, in general we retry to launch the kubectl logs <pod> [-f] until the container is created.
A nice feature would be to have a the kubectl logs command to block until the container is created, so we run this command only one time.
Why is this needed:
To simplify the life of the user.

I guess you could use kubectl wait, then do kubectl logs after that.
Would something like this work?
kubectl apply -f foo.yaml && kubectl wait --for=condition=Ready pod/foo && kubectl logs foo
If so, you could turn that into a script and make it a plugin for convenience.

See also https://github.com/kubernetes/kubernetes/issues/79547

/triage accepted

I guess you could use kubectl wait, then do kubectl logs after that.
Would something like this work?
kubectl apply -f foo.yaml && kubectl wait --for=condition=Ready pod/foo && kubectl logs foo
If so, you could turn that into a script and make it a plugin for convenience.

Sometimes we want to follow 50 pods logs like this:
kubectl logs -l name=my-service-xxx --follow --max-log-requests 50

However, some pods are being creating and the whole requests will fail.
We need to wait for several creating pods and follow the running pods in the mean time.

/remove-lifecycle stale

Any workaround?

Looks like wait --for=condition=Ready doesn't work for jobs. Any workaround for this?

@homm I went with a bit ugly while loop to solve this.
while True ; do kubectl logs job/foo -f 2>/dev/null && break || continue ; done

Note, that there is no timeout with this solution.

@homm I went with a bit ugly while loop to solve this.
while true ; do kubectl logs job/foo -f 2>/dev/null && break || continue ; done

Note, that there is no timeout with this solution.

My solution (also ugly) when launching a container called sbt in a job called build:
filter="-l job-name=build"
for i in {1..70}; do
  case $(k get po $filter -o jsonpath='{.items[*].status.containerStatuses[?(@.name=="sbt")].state.terminated.reason}') in
    *OOMKilled*)
      echo SBT has been killed for low memory
      k get po | grep build-
      k get ev | grep build-
      k top no
      exit 1;;
    "Error")
      echo SBT has ended with errors
      k logs $filter -c sbt
      exit 1;;
  esac
  msj=$(k get po $filter -o jsonpath='{.items[*].status.containerStatuses[?(@.name=="sbt")].state}')
   case $msj in
    *terminated*)
      echo
      echo Detected container SBT has ended
      success=1
      break;;
    *waiting*)
      echo -n .
      sleep 2;;
    *running*)
      echo
      echo Detected container SBT under execution
      success=1
      break;;
    *)
      echo -n '*'
      sleep 2;;
   esac
done
[[ $success != 1 ]] && {
  echo $msj
  echo Too much waiting for container SBT to be created
  exit 1
}
k logs $filter -c sbt -f || {
  echo Fails getting logs
  exit 1;
}

/assign


Add support for IMPI Thread-Split mode using OpenMP

Add BF16 and Float16 datatype support.

Add support for duplicating communicators for each OpenMP thread.

Use OpenMP inside mpi_all_reduce to split msg across threads/comms.

If HANDOFF is defined to 1 at top of coll_mpi.cpp, do not use thread-split.

No need to merge yet, but sharing code here.

@stwhite91 when MPI backend create comms thread according to openmp threads, does it be active when communication is not happening?  I mean will it interfere with compute ops before and after communican, which also use openmp threads?

Sorry I didn't see your comment earlier. No the OpenMP threads I have added here are not active outside of the mpi_all_reduce, there is no problem using OpenMP threads elsewhere in the application.


.from matcher not matching "Full Name<EMAIL_ADDRESS>format

mail 2.7.0
Expected email to be sent from Full Name<EMAIL_ADDRESS>(actual deliveries: [#<Mail::Message:70115255463060, Multipart: false, Headers: <Date: Thu, 02 Nov 2017 15:19:50 +0100>, <From: Full Name<EMAIL_ADDRESS><To<EMAIL_ADDRESS><Message-ID<EMAIL_ADDRESS><Subject: Test subject>, <Mime-Version: 1.0>, <Content-Type: text/plain>, <Content-Transfer-Encoding: quoted-printable>>])

I'd expect
it { is_expected.to have_sent_email.from('Full Name<EMAIL_ADDRESS>}

to work as well. Or is there another matcher I missed?

This is expected. All recipient matchers are against the email address itself:
      def matches_on_sender?(delivery)
        delivery.from.include?(@sender)
      end

      def matches_on_recipients?(delivery)
        @recipients.all? {|recipient| delivery.to.include?(recipient) }
      end

      def matches_on_copy_recipients?(delivery)
        @copy_recipients.all? {|recipient| delivery.cc.include?(recipient) }
      end

      def matches_on_blind_copy_recipients?(delivery)
        @blind_copy_recipients.all? {|recipient| delivery.bcc.include?(recipient) }
      end

Matching full addresses would be cool, too. PR welcome 😊


EmbedMany

I think we should add a EmbedMany, that will run embed under the hood but instead of querySelector we use querySelectorAll and maybe the embed function over the list of dom nodes. Thoughts?
Use Case:
I have some virtual dom based elm apps that run in different locations on the browser window, but I want to share the same Elm app to these dom nodes. A good example sorted or filter UI on some value that will use widgets that are the same Elm app, but are not necessarily together on the UI.

Closed with https://github.com/knledg/elm-router/pull/8


Can´t make Shuttle work in Monterey

Hi there!
I thought I could do the same in Monterey that I did in BigSur (System Preferences -> Security & Privacy -> Accessibility -> Privacy -> unlock -> delete and add Shuttle, Terminal and iTerm but didn´t work.
Will appreciate another Shuttle fan feedback!

Weird, it works fine for me.

I suspect that in "Terminal" app preferences the default login shell must be set as well

same problem here, cannot make it work in Monterrey
@christianbraun can you explain a bit what you mean with default login shell?

Preferences of Terminal App. Some users might be using Homebrew and changed this to their liking.
Changing this back to the "default" setting made Shuttle work again...

thanks @christianbraun . Unfortunately not for me. I use only Terminal.app and it is default op "default login shell" but cannot open Shuttle.
Other suggestions?

It didn't work for me either - Only very rarly would it work. So I came here because I thought I would fork the repo and make a working version, but then I tried a few of the suggestions in this thread and now it seems to work.
I vent to terminal settings - In the "Shells open with" i selected "Command" and then immediately switched back to "Default login shell". After this I remove Suttle from Accessibility in security setting and then added it again. After this I restarted Shuttle and now it seems to work everytime I try to connect to SSH.

I've been having this same issue ever since I upgraded to Big Sur (like 2 years ago?).  I'd tried variations of the steps @angelbatalla listed at the top of this thread several times to no avail, though in hind sight I realize I'd never added Terminal.app to the list of apps allowed to control my computer (only Shuttle).
Today, after installing the Ventura 13.1 update, I thought I'd try this again.  I took @christianbraun 's suggestion and made sure my Terminal.app had the same default settings (which it did).  Then I went in to Settings > Privacy & Security > Accessibility and I removed both Shuttle and Terminal.app using the minus (-) sign.  I edited my shuttle.json settings to set the option back to "tab", and then rebooted for good measure.  After starting back up, I went back in to Settings > Privacy & Security > Accessibility and I added both Shuttle and Terminal.app using the plus (+) sign.  I then opened Terminal.app manually and tested out the Shuttle menu items and voila, it worked.  Maybe someone else will have similar luck.

Hi, since it does not seem like this app is being maintained I create a new Open Source app MenuBarSSHCommands. Its still basic but does what I needed it to do. Sharing for those on M1 / M2 Apple Silicon.


Added 2D Array

2D Array problems and simple solutions from various websites like LeetCode, GFG, PepCoading, etc, will help to understand 2D Array.

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <issue_number_here>

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[x] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[x] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

I have verified the code myself, run it many times in my system. merge it


How to reset the list of devices?

Hello, how do i clear the list of devices in the admin? It doesnt show anywhere on the page.

Data are stored in a json file in your homebridge default folder : you can remove it to clean your list

Thanks! How do I get to it if Im running the HB image on my RPi?

Indeed
I will try in next weeks to add a remove function if I have some time

That would be awesome! Also one thing, when my TV turns off, it goes unresponsive (the network card is not powered). This cannot be changed, but when I turn on the TV manually with the remote, it does not show as on until I restart my HB.

You need to set your AndroidTV not deep sleeping : there is a option for that.
Normally a process check regularly if your device is on/online : except if IP change it should work. It's preferable to set a fixed IP.


FEATURE - Code sandbox

Support a coding sandbox environment so people can implement their own BLE protocols.
Should likely expose the ble cordova class as well as a party instance. It would be nice to enable this environment in the nodejs backend so users have access to typical nodejs tools as well as in the frontend.
Features:

Connect to BLE devices
Create custom BLE peripherals
Party on all existing datatypes
Log custom data types (maybe they can have a whole party of their own?)
Prevent general network access(unless user allows)

Plugins as a dataparty service should solve this basic issue of implementation tooling
https://github.com/datapartyjs/dataparty-api/issues/36


Add check-onnx-backend to Mac CI.

Add check-onnx-backend to Mac CI.
Signed-off-by: Ettore Tiotto<EMAIL_ADDRESS>

@etiotto Thanks for adding instructions in Readme. Ideally this one should go before #1084 as this info is moved around.

Jenkins Linux s390x Build #3269 [push] Add check-onnx-backend t... started at 18:27

Jenkins Linux amd64 Build #3277 [push] Add check-onnx-backend t... started at 17:27

Jenkins Linux ppc64le Build #2385 [push] Add check-onnx-backend t... started at 18:32

Jenkins Linux s390x Build #3269 [push] Add check-onnx-backend t... passed after 36 min

Jenkins Linux amd64 Build #3277 [push] Add check-onnx-backend t... passed after 49 min

Jenkins Linux ppc64le Build #2385 [push] Add check-onnx-backend t... passed after 50 min


Updated with a new test case.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 27s
master passed

+1 :green_heart:
checkstyle
1m 33s
master passed

+1 :green_heart:
spotbugs
2m 53s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 22s
the patch passed

-0 :warning:
checkstyle
1m  4s
hbase-server: The patch generated 10 new + 0 unchanged - 0 fixed = 10 total (was 0)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
17m  5s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1 3.3.0.

+1 :green_heart:
spotbugs
3m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

42m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2726

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 662d9f271cbd 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / dfe3672266

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  5s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 41s
master passed

+1 :green_heart:
compile
1m 20s
master passed

+1 :green_heart:
shadedjars
6m 39s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 30s
the patch passed

+1 :green_heart:
compile
1m 22s
the patch passed

+1 :green_heart:
javac
1m 22s
the patch passed

+1 :green_heart:
shadedjars
6m 33s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m  2s
hbase-client in the patch passed.

+1 :green_heart:
unit
145m 52s
hbase-server in the patch passed.

176m 14s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2726

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux d5225b2cca5d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / dfe3672266

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/testReport/

Max. process+thread count
4039 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 11s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 44s
master passed

+1 :green_heart:
compile
1m 42s
master passed

+1 :green_heart:
shadedjars
7m 19s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  8s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 33s
the patch passed

+1 :green_heart:
compile
1m 41s
the patch passed

+1 :green_heart:
javac
1m 41s
the patch passed

+1 :green_heart:
shadedjars
7m 27s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  5s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
1m 21s
hbase-client in the patch passed.

+1 :green_heart:
unit
197m 30s
hbase-server in the patch passed.

232m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2726

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux daa292ea7429 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / dfe3672266

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/testReport/

Max. process+thread count
3783 (vs. ulimit of 30000)

modules
C: hbase-client hbase-server U: .

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2726/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Thanks Stack for review, pushing the changes.


react 18 upgrade

📝 Changed routes:

/[wallet]

(view full size)

Commit e91d1ff91ca8d78a6de31927fec1745df991a4ad (https://thirdweb-64npq8zrt-thirdweb.vercel.app).

🎉


fix(#2889): return always the same error contract from simplifyTest

Motivation/Description of the PR

Resolves #2889

Currently using patch-package with this fix on version 3.0.7 and been testing since then. With the complexity of the core api of codeceptjs, I could not find a way to replicate the error by sending an invalid object with inspect and cliMessage functions on it like shown in the reported issue. I would be glad to add some tests if someone could point me on how to build these tests to track the exact problem.
Applicable helpers:

[ ] WebDriver
[ ] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[ ] TestCafe
[ ] Playwright

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] coverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] stepTimeout
[ ] wdio
[ ] subtitles

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[x] Lint checking (Run npm run lint)
[x] Local tests are passed (Run npm test)

Thanks! I didn't get if that actually fixed the problem but this refactoring makes sense


UserRegistration

User registration API and Lamda handler implementations

Awesome :)

We can enhance it to accept  all api calls, i.e. GET, POST, and DELETE.
The path should be /users instead of create-user
We have a db collection user, so we can use that instead of users collection.
GET /users  -> return list of all users
GET /users/{id} return user with user_id as id
POST /users -> create new user
DELETE /users/{id} -> delete user with user_id as id
PATCH /users/{id} -> Patch user with user_id as id
See the taxi API for /taxi and /taxi/{id} implementation.
See the geocoder API for handling different HTTP methods in same API endpoint

I will make the changes. Thanks for the suggestions


Fixing the heatmap calendar color ranges in the Welcome page

@georgeke

Coverage remained the same at 81.605% when pulling 9953387c6c31797d4d912a77e7307f39ea04d31a on mistercrunch:fix_welcome into 607e1f941bdc19ebc9850657a8d2124f32217ba5 on airbnb:master.


Error while starting Transform module

The error message is shown in above pic from apollo 3.5. I could not find the files mentioned in those error msgs.
Besides,  the transform module can be turned on in dreamview but I was not sure if it worked.
It would be really appreciated if someone could provide any suggestion!

maybe you could give more info about your system and env?

maybe you could give more info about your system and env?
Thank you. I'm on Ubuntu 18.04 and using the image of lgsvl/apollo-3.5, nvidia graphics driver 440.33, cuda10.2.
As the error msg indicated some information about lidar, I don't think it was any problem with my system setup.

Hi @lh315936716 , you can try switching to another vehicle like mkz7 on dreamview panel. Besides, you can launch transform module by either turning on the button on dreamview panel, or running cyber_launch start /apollo/modules/transform/launch/static_transform.launch, but not both at the same time.


[RE] invite-only "manage permissions"

Hi guys, apologies for raising as an issue here.
I use extensively the add tradingview alerts tool, I really love it!!!
I was wondering if any of you was aware of any similar tool but to add permissions for invite-only scripts?
It'd be great if you could consider adding it. My first impression is that it should be at least way more simple than adding alerts as there's only a few fields and not many edge cases, and given that you have already the auth and chromium platform sorted out it would be a great addition!
I know MANY existing users of adding alerts would have a strong interest in being able to add permissions too.
Thanks!

Good news, I managed to implement this functionality
I'm not an expert in TS or JS, but I modified locally the JS files so it does exactly what I need.
I think it's in a POC state but definitely can be added as an extra feature here if you guys are up for it.
I think hundreds of users (at least) have been begging TV to support better management of invite only scripts so this could be big value as TV are not planning much in that area AFIK

could be interesting...what would we have to call this project then? Maybe "add-tradingview-alerts-and-sync-tradingview-invites-tool"? has a nice ring to it...

That's a very techie response :) you need a bit of business mindset too sometimes!
_Tradingview manager pro, supporting all repetitive tasks required for signal managers including:

alert management. Add your alerts to as many symbols as you want
invite-only permission management. Grant permission to your invite-only scripts to as many users as you want.
exchange symbol fetcher for Binance, FTX, etc_

Anyways, here are the changes in case any one else can benefit from them...appreciate that maybe this tool would be best to keep solving a single problem, maybe a separated one based on this (reusing many of the problems you already solved, auth, setup of chromium, etc)
The changes below are not even close to production ready but at least it will save the time to figure all the xpaths and it does work.
tv-page-actions.js changes:
`export const manageAccess = async (page) => {
const manageAccessButton = await fetchFirstXPath(page, '//button[@data-name='manage-access']');
log.trace("clicking manage access button");
manageAccessButton.click();
};
export const addUser = async (page, username) => {
//click manage
await waitForTimeout(.5);
const myUserInput = await fetchFirstXPath(page, '//input[@name='manage-access-user-search']');
log.trace("typing user");
await myUserInput.type(${username});
await waitForTimeout(.5);
try {
    //type user
    const userResult = await fetchFirstXPath(page, '(//div[contains(text(),\''+`${username}`+'\')])[1]', 1000);
    userResult.click();
    await waitForTimeout(1000);

    //uncheck box
    const checkbox = await fetchFirstXPath(page, '//input[@class=\'input-24iGIobO\' and @value=\'on\']', 10)
    const isChecked = await page.evaluate(element => element.checked, checkbox);
    if (isChecked){
        checkbox.click();
        await waitForTimeout(500);
    }
    //empty date field
    const dateInput = await fetchFirstXPath(page, '//input[@class=\'input-3bEGcMc9 with-end-slot-S5RrC8PC\']')
    clickInputAndDelete(page, dateInput)
    await waitForTimeout(500);
    // type date
    await page.evaluate((el) => el.value = "2021-07-01", dateInput);
    // await dateInput.type("2021-07-01");
    await waitForTimeout(500);
    //click submit
    const submitButton = await fetchFirstXPath(page, '//button[@class=\'button-1iktpaT1 size-m-2G7L7Qat intent-primary-1-IOYcbg appearance-default-dMjF_2Hu\']');
    submitButton.click();
    await waitForTimeout(500);
}
catch (e) {
    log.warn("user not found: ", username);
    const dismissButton = await fetchFirstXPath(page, '//span[@class=\'close-2sL5JydP\']');
    dismissButton.click();
    await waitForTimeout(500);
}

}`
changes to 'add-alerts.js'
const permissionRows = await readFilePromise(config.files.input);     for (const row of permissionRows) {         await manageAccess(page);         await addUser(page,row.username,config.permissions.date);     }         await browser.close();
The YAML file will require this extra field for the expiry date of the permission:
permissions:   date: 2021-07-01
and the txt file will only use one column with each username that needs to be added:
username, francisb01 mgrzegorzak ua87 matej-b legalDove56784

TradingView...Manager...Pro.. 🤔  I LOVE IT! way better than my name...
How much do you think people would pay for it?
FYI..here's a little teaser of something to come...

That looks spectacular 😮
People requiring to add hundreds of alerts fit into this profile:

were willing to pay hundreds to a yearly subscription to TV
most of them are needing to sell these alerts to their own customers
will consider an alert management tool a "profesional feature"
once they have all those alerts to trigger bots and buy orders on exchanges, they will also need a way to grant permissions to those users that "pay" for such access.

Is not in my best interest that you charge me more, of course, but I'm personally willing to pay from $50 to $100 a month for something that takes away ALL this hassle so I can focus on what I do which is building great strategies and selling them. As long as TV don't decide to release these features officially you got yourself a great opportunity to monetise it (maybe for a year?).
By the way, even though my code above is editing the value of the expiry date HTML input, the form seems to be reset back to its original value right before being submitted which made all my effort a waste of time :( I tried triggering manually some events like onType, onChange, onKeyUp, down, etc to try to find which event is updating their data model so it doesn't get reset back to default value but I ended up giving up. I'm sure it's doable but ran out of spare time to keep hacking around now.
I checked what their javascripts are doing, and its really complicated, I suspect they use vendor.js to protect from UI automation...who knows.

Hours spent chasing a solution and coming up empty-handed? I can relate..
took a brief look at TV's user management of private indicators...I think it's doable for automation, but frankly been heads-down trying to hammer out the frontend (any day now...right? 🙄 ). super strange there's no api to manage that. can imagine what a hassle that is for creators...
Thanks for weighing in - especially on pricing - those numbers are in-line with what I was thinking.
Perhaps I'll circle back with you and we could collaborate on a zoom call or something..

Absolutely!  Collaboration works for me
maybe not your cup of tea, but this is what I spend most of the time on these days
https://www.youtube.com/channel/UCrqilwm_w0Jww188AyxBq7w

@mlake hijacking this topic to ask your opinion. i have implemented this feature and would like to know if you are open to accept an MR for the same. if you have a business idea and you think this can be problematic, i will refrain from raising a MR. Thanks

Hi, there are tools for this. Try:
https://www.tradingintegration.com/
https://algoautomation.io/

Also, there are other unofficial solutions for this. Try:
https://rapidapi.com/financetrading/api/tradingview-rest


Time handling in antidote

With the change to Erlang 19 we removed all calls to erlang:now.
There are still some open problems with this change and the handling of time in general:

[ ] Monotonicity: Replacing erlang:now with erlang:system_time (as we did) should work, as system_time is still monotonic with the default time warp setting ("No Time Warp Mode"). However, this means that our code is not time warp safe and would be incorrect if Erlang is started with time warp mode enabled (which is recommended).
[ ] Uniqueness: Most old uses of erlang:now do not need uniqueness. I think it might still be required for generating transaction-ids (in clocksi_interactive_tx_coord_fsm, line 171). There might be other places.
[ ] Restarts:  erlang:now and erlang:system_time seem to loose their guarantees after a system restart. So after a restart we might get an older time stamp, which could break the protocol.

Is someone assigned to work on this?

Not a fix, but a suggestion is to run NTP on all nodes in a DC before any of the erlang VMs are started.
My understanding is that "time warp" is for large clock corrections, but there is also "time correction" which adjusts the erlang clock frequency by a small amount without violating monotonicity.  So if system clocks are synced before the start and continually then the hope is that "time correction" will be sufficient.  Though there might be other downsides of using no time warp mode?  Maybe worth testing.
The uniqueness of txids that you mentioned and after restarts do look like issues that could happen, but should be easy to fix I guess.

@balegas ?

I was checking the code and I think that timestamps in the bounded counter manager are used to timeout resource transfers requests. It does not depend on timestamps to set identifiers, or ordering.

Is this issue still open?
I implemented a very simple solution for this problem in gingko but I don't know if it performs well
Basically I used a gen_server that made sure that every new timestamp (regular erlang timestamp translated to microseconds) was strictly monotonic and if it was not then the last timestamp was incremented by one and used instead


[Task] Replace Blanket 500 error with specific errors wherever possible in service.ts files

Hey team! Please add your planning poker estimate with Zenhub @ayushpahwa @srix


Add contact information of relatives

We need to create a migration to insert a relative's contact info field to the personal information table (also add to the fillable list in the personal information modal, so that it can be filled by the controllers). Add the field to the ui in the personal information blade, and add a validation rule for that in the UserController's updatePersonalInformation function. It will be saved automatically with $user->educationalInformation->update($request->all()); on line 102


Add arguments property for commands

Description
Added missing arguments Command property, and changed link titles to match section titles
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the PR! Could you target the main branch instead of gh-pages?

@mathieudutour did https://github.com/raycast/extensions/pull/4930


Scala Common Enrich: get rid of Id instances

In SCE 1.0.0 in order to make it possible to compose IO we made a decision to switch all client libraries to final tagless like encoding:
trait Weather[F[_]] {
  def temperature: F[Int]
}

It works great with IO, Task, ZIO etc, but we cannot support them in Spark and Beam (or maybe we can and then we should!). We decided to use Id in Spark and Beam, which unfortunately makes SCE API not that composable as we would like to. Imagine following code:
implicit val idWeather = new Weather[cats.Id] {
  def temperature: Id[Int] = {
    println("Getting weather")
    20
  }
}

implicit def syncWeather[F[_]: cats.effect.Sync] = new Weather[F] {
  def temperature: F[Int] =
    cats.effect.Sync[F].delay {
      println("Getting weather")
      20
    }
}

def one[F[_]](implicit W: Weather[F], M: Monad[F]) = {
  val weather: F[Int] = W.temperature   // would be fine with def
  for {
    berlin <- weather
    moscow <- weather
  } yield moscow - berlin
}

def two[F[_]](implicit W: Weather[F], M: Monad[F]) = {
  val weather: F[Int] = W.temperature   // would be fine with def
  List.fill(5)(weather).sequence
}

one[Id] does a different thing from one[cats.effect.IO].unsafeRunSync(). As a result we just need to be very careful in with constructs like val x: F[Something] because in some cases it means it has been evaulated already and we cannot use many functional combinators, so the code is not much better than pre-1.0.0.
/cc @benjben

Migrated to https://github.com/snowplow/enrich/issues/51


SAM add support for box inputs

Code:
import { SamModel, AutoProcessor, RawImage } from '@xenova/transformers';

const model = await SamModel.from_pretrained('Xenova/slimsam-77-uniform', {
    revision: 'boxes',
});
const processor = await AutoProcessor.from_pretrained('Xenova/slimsam-77-uniform', {
    revision: 'boxes',
});

const img_url = 'https://huggingface.co/ybelkada/segment-anything/resolve/main/assets/car.png';
const raw_image = await RawImage.read(img_url);
const input_boxes = [[[650, 900, 1000, 1250]]];

const inputs = await processor(raw_image, null, null, input_boxes);
const outputs = await model(inputs);

const masks = await processor.post_process_masks(outputs.pred_masks, inputs.original_sizes, inputs.reshaped_input_sizes);

Inputs:

Visualization:
const image = RawImage.fromTensor(masks[0][0].mul(255));
image.save('img.png');

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks for all your work Xenova! I'm looking forward to this - very useful when segmenting parts of a larger whole, particularly for things which are rare in SA-1B.
In case it's helpful to anyone, here's the code snippet modified to have the embeddings step separate (so you can re-use it):

Code
const model = await SamModel.from_pretrained('Xenova/slimsam-77-uniform', {
    revision: 'boxes',
});
const processor = await AutoProcessor.from_pretrained('Xenova/slimsam-77-uniform', {
    revision: 'boxes',
});

const img_url = 'https://huggingface.co/ybelkada/segment-anything/resolve/main/assets/car.png';
const raw_image = await RawImage.read(img_url);
const input_boxes = [[[650, 900, 1000, 1250]]];

let imageInputs = await processor(raw_image);
let imageEmbeddings = await model.get_image_embeddings(imageInputs);
const outputs = await model({
    ...imageEmbeddings,
    input_points: null,
    input_labels: null,
    input_boxes: processor.reshape_input_points(
        input_boxes,
        imageInputs.original_sizes,
        imageInputs.reshaped_input_sizes,
        true)});

masks = await processor.post_process_masks(outputs.pred_masks, imageInputs.original_sizes, imageInputs.reshaped_input_sizes);

A couple questions (I can move these to a separate issue if that would be preferable):

Is it possible to pass batches of bounding boxes in the input_boxes array?  The nestedness and variable name suggests you could, and I think it works with points (although I haven't explored that much), but it crashes if I try to pass in more than one bbox.
post_process_masks accounts for the vast majority (~80%) of the runtime of my script.  Is this expected, or is there something I'm doing wrong/can do to speed it up?  Here's a performance profile from Firefox.  I'm running that segmentHold function a bunch of times in a loop because I have many instances to segment.

I put together a version of post_process_masks with higher throughput.  It doesn't cover the breadth of use cases that the built in one does and requires a heavy dependency in opencv.js but is suited to my use case.  Also converts the mask to contours but that could be skipped.

Code
// note: takes only a single mask, e.g. outputs.pred_masks[0][0][best_mask_index]
function post_process_mask(mask, original_size, reshaped_input_size, pad_size) {
    // mask: [256, 256]
    let opencv_mask = cv.matFromArray(256, 256, cv.CV_32FC1, mask.data);
    // upscale mask to padded size
    let padded_size = new cv.Size(pad_size.height, pad_size.width);
    cv.resize(opencv_mask, opencv_mask, padded_size, cv.INTER_LINEAR);
    // crop mask
    let roi = new cv.Rect(0, 0, reshaped_input_size[1], reshaped_input_size[0]);
    opencv_mask = opencv_mask.roi(roi);
    // downscale mask
    let downscaled_size = new cv.Size(original_size[1], original_size[0]);
    cv.resize(opencv_mask, opencv_mask, downscaled_size, cv.INTER_LINEAR);

    // note: You could stop here and skip the contour detection if you didn't need it
    //       (the opencv interpolation is still faster)
    // To 8 bit for contour detection
    opencv_mask.convertTo(opencv_mask, cv.CV_8UC1);
    // erode away stray pixels
    let M = cv.Mat.ones(5, 5, cv.CV_8UC1);
    let anchor = new cv.Point(-1, -1)
    cv.erode(opencv_mask, opencv_mask, M, anchor, 1, cv.BORDER_CONSTANT, cv.morphologyDefaultBorderValue());
    cv.dilate(opencv_mask, opencv_mask, M, anchor, 2, cv.BORDER_CONSTANT, cv.morphologyDefaultBorderValue());
    // find contours (external only)
    let contours = new cv.MatVector();
    let hierarchy = new cv.Mat();
    cv.findContours(opencv_mask, contours, hierarchy, cv.RETR_EXTERNAL, cv.CHAIN_APPROX_SIMPLE);
    let poly = new cv.MatVector();
    let contourArray = [];
    for (let i = 0; i < contours.size(); i++) {
        let tmp = new cv.Mat();
        let contour = contours.get(i);
        let epsilon = 0.002 * cv.arcLength(contour, true);
        cv.approxPolyDP(contour, tmp, epsilon, true);
        // might be a better/more direct way to get polygons?
        poly.push_back(tmp);
        // be sure to free the memory
        contour.delete();
        tmp.delete();
    }
    // convert to regular JS nested array and avoid passing the BufferArray around
    for (let i = 0; i < poly.size(); i++) {
        contourArray.push(Array.from(poly.get(i).data32S));
    }
    // free memory again
    opencv_mask.delete();
    M.delete();
    poly.delete();
    contours.delete();
    hierarchy.delete();

    return contourArray;
}

(Also, sorry for clogging up the PR with these semi-relevant comments.)

Revisiting this now. Thanks @jwlarocque for your testing!

Is it possible to pass batches of bounding boxes in the input_boxes array? The nestedness and variable name suggests you could, and I think it works with points (although I haven't explored that much), but it crashes if I try to pass in more than one bbox.

Could you provide example code for which it crashes? Also, what error message do you get?

post_process_masks accounts for the vast majority (~80%) of the runtime of my script. Is this expected, or is there something I'm doing wrong/can do to speed it up? Here's a performance profile from Firefox. I'm running that segmentHold function a bunch of times in a loop because I have many instances to segment.

Indeed this is a known limitation of the current approach (which does the post-processing in JavaScript), and is not easily solvable without introducing a massive dependency like opencv.js.


caffe-time-opencl and caffe-classification-opencl doesn't works on S7

It works now for Galaxy Note 4 with batch_size = 1 for all models
but fails for glaxy s7 for all models:
 F0126 11:12:14.358805 11623 D:\!FGG\Installations\lib-caffe-bvlc-opencl-clblast-android-trunk-android-ndk-4.9.x-1.62.0-0.2.19-85636ff-a
ndroid21-arm64\src\src\caffe\syncedmem.cpp:281] Check failed: mapped_ptr == cpu_ptr_ (0 vs. 0x7f96112000) Device claims it support zero copy
but failed to create correct user ptr buffer
     *** Check failure stack trace: ***
     Aborted

So it fails  at syncedmem.cpp:281 (case HEAD_AT_CPU) for Galaxy S7
but  fails at syncedmem.cpp:220 (case  UNINITIALIZED) for Galaxy Note 4
so it's different places but same reason do not enough GPU memory for buffer.
It  can be with 64-bit indexing mode (Galaxy S7) becasue:
      I0126 11:33:57.103912 12778 D:\!FGG\Installations\lib-caffe-bvlc-opencl-clblast-android-trunk-android-ndk-4.9.x-1.62.0-0.2.19-85636ff-android21-arm64\src\src\caffe\net.cpp:281] Memory required for data: 32314796
but for Galaxy Note 4 (32-bit):

caffe-classification-opencl works only with Squeeznet 1.1, but failed on all others

It works now after disblaing host unified memory with new compilation param
"DISABLE_DEVICE_HOST_UNIFIED_MEMORY"
for Mali GPUs because it does not support this feature in fact.
So issue could  be closed.

so finally for Mali GPUs
need to compile caffe-opencl lib and program with option:
--env.DISABLE_DEVICE_HOST_UNIFIED_MEMORY=ON


Attempt osx-arm64

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Attempt osx-arm64 build.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I think this works? I mostly followed along the instructions here: https://conda-forge.org/blog/posts/2020-10-29-macos-arm64/
If I understand correctly, all arm64 builds are cross-compiled on Intel Macs. And because the build produces arm64 binaries, the build machine can't actually run tests.

Here is the testflo output for the osx-arm64 build, Python 3.10. There is one failure in an SLSQP test. Perhaps relaxing the tolerance on the test would be sufficient.

(pyoptsparse) philchiu@m1-mbp pyoptsparse % testflo --verbose .
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
./tests/test_snopt_user_termination.py:TestUserTerminationStatus.test_sens ... SKIP (00:00:0.00, 53 MB)
Optimizer not available: SNOPT
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
./tests/test_snopt_user_termination.py:TestUserTerminationStatus.test_obj ... SKIP (00:00:0.00, 53 MB)
Optimizer not available: SNOPT
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
./tests/test_optProb.py:TestOptProb.test_finalize ... OK (00:00:0.01, 54 MB)
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_4_NLPQLP ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'NLPQLP')
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_5_ParOpt ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'ParOpt')
./tests/test_rosenbrock.py:TestRosenbrock.test_snopt ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_optProb.py:TestOptProb.test_mappings ... OK (00:00:0.04, 54 MB)
./tests/test_rosenbrock.py:TestRosenbrock.test_snopt_hotstart_starting_from_grad ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_hs071.py:TestHS71.test_nlpqlp_informs ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'NLPQLP')
./tests/test_hs071.py:TestHS71.test_optimization_0_SNOPT ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'SNOPT')
/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/pyoptsparse/pyOpt_MPI.py:68: UserWarning: mpi4py could not be imported. mpi4py is required to use the parallel gradient analysis and parallel objective analysis for non-gradient based optimizers. Continuing using a dummy MPI module from pyOptSparse.
  warnings.warn(warn)
./tests/test_optProb.py:TestOptProb.test_setDV_getDV ... OK (00:00:0.01, 54 MB)
./tests/test_hs071.py:TestHS71.test_ipopt_informs ... OK (00:00:0.01, 58 MB)
./tests/test_optProb.py:TestOptProb.test_setDV_VarGroup ... OK (00:00:0.02, 54 MB)
./tests/test_hs071.py:TestHS71.test_optimization_2_SLSQP ... OK (00:00:0.00, 54 MB)
./tests/test_hs071.py:TestHS71.test_optimization_5_NLPQLP ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'NLPQLP')
./tests/test_hs071.py:TestHS71.test_optimization_3_PSQP ... OK (00:00:0.00, 58 MB)
./tests/test_hs071.py:TestHS71.test_optimization_6_ParOpt ... SKIP (00:00:0.00, 54 MB)
('Optimizer not available: ', 'ParOpt')
./tests/test_hs071.py:TestHS71.test_psqp_informs ... OK (00:00:0.00, 58 MB)
./tests/test_hs071.py:TestHS71.test_slsqp_informs ... OK (00:00:0.00, 54 MB)
./tests/test_hs071.py:TestHS71.test_optimization_1_IPOPT ... OK (00:00:0.02, 58 MB)
./tests/test_hs071.py:TestHS71.test_snopt_informs ... SKIP (00:00:0.00, 58 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_hs071.py:TestHS71.test_snopt_setDVFromHist ... SKIP (00:00:0.00, 58 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_snopt_bugfix.py:TestSNOPTBug.test_opt ... SKIP (00:00:0.00, 58 MB)
Optimizer not available: SNOPT
./tests/test_snopt_bugfix.py:TestSNOPTBug.test_opt_bug1 ... SKIP (00:00:0.00, 58 MB)
Optimizer not available: SNOPT
./tests/test_snopt_bugfix.py:TestSNOPTBug.test_opt_bug_print_2con ... SKIP (00:00:0.00, 58 MB)
Optimizer not available: SNOPT
./tests/test_hs071.py:TestHS71.test_optimization_4_CONMIN ... OK (00:00:0.01, 55 MB)
./tests/test_hs015.py:TestHS15.test_optimization_0_SLSQP ... FAIL (00:00:0.00, 55 MB)
Traceback (most recent call last):
  File "/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/testflo/test.py", line 477, in _try_call
    func()
  File "/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/parameterized/parameterized.py", line 533, in standalone_func
    return func(*(a + p.args), **p.kwargs)
  File "/Users/philchiu/repos/pyoptsparse/./tests/test_hs015.py", line 128, in test_optimization
    self.assert_solution_allclose(sol, self.tol[optName])
  File "/Users/philchiu/repos/pyoptsparse/./tests/testing_utils.py", line 194, in assert_solution_allclose
    assert_allclose(sol_objectives, self.fStar[self.sol_index], atol=tol, rtol=tol)
  File "/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/numpy/testing/_private/utils.py", line 1530, in assert_allclose
    assert_array_compare(compare, actual, desired, err_msg=str(err_msg),
  File "/Users/philchiu/mambaforge/envs/pyoptsparse/lib/python3.10/site-packages/numpy/testing/_private/utils.py", line 844, in assert_array_compare
    raise AssertionError(msg)
AssertionError:
Not equal to tolerance rtol=1e-08, atol=1e-08

Mismatched elements: 1 / 1 (100%)
Max absolute difference: 0.0006391
Max relative difference: 2.08516973e-06
 x: array([306.499361])
 y: array(306.5)

./tests/test_hs015.py:TestHS15.test_optimization_1_PSQP ... OK (00:00:0.00, 55 MB)
./tests/test_hs015.py:TestHS15.test_optimization_2_CONMIN ... OK (00:00:0.00, 55 MB)
./tests/test_hs015.py:TestHS15.test_optimization_3_NLPQLP ... SKIP (00:00:0.00, 55 MB)
('Optimizer not available: ', 'NLPQLP')
./tests/test_hs015.py:TestHS15.test_optimization_4_ParOpt ... SKIP (00:00:0.00, 55 MB)
('Optimizer not available: ', 'ParOpt')
./tests/test_hs015.py:TestHS15.test_snopt ... SKIP (00:00:0.00, 55 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_hs015.py:TestHS15.test_snopt_hotstart ... SKIP (00:00:0.00, 55 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_hs015.py:TestHS15.test_snopt_snstop ... SKIP (00:00:0.00, 55 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_hs071.py:TestHS71.test_slsqp_setDV ... OK (00:00:0.26, 57 MB)
./tests/test_hs071.py:TestHS71.test_slsqp_scaling_offset_optProb ... OK (00:00:0.28, 61 MB)
./tests/test_hs015.py:TestHS15.test_ipopt ... OK (00:00:0.37, 62 MB)
./tests/test_tp109.py:TestTP109.test_slsqp ... OK (00:00:0.02, 62 MB)
./tests/test_tp109.py:TestTP109.test_snopt ... SKIP (00:00:0.00, 62 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_large_sparse.py:TestLarge.test_dense_workspace_too_small ... SKIP (00:00:0.01, 64 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_large_sparse.py:TestLarge.test_opt_0_SNOPT ... SKIP (00:00:0.14, 79 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_2_PSQP ... OK (00:00:1.04, 59 MB)
./tests/test_large_sparse.py:TestLarge.test_opt_2_SNOPT ... SKIP (00:00:0.01, 61 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVar.test_do_not_use_mpi ... OK (00:00:0.00, 61 MB)
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVar.test_no_mpi_requirement_given ... OK (00:00:0.00, 61 MB)
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVar.test_require_mpi ... SKIP (00:00:0.00, 61 MB)
mpi4py not available, skipping test.
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_do_not_use_mpi_check_paropt ... SKIP (00:00:0.00, 61 MB)
('Optimizer not available:', 'paropt')
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_no_mpi_requirement_given_check_paropt ... SKIP (00:00:0.00, 61 MB)
('Optimizer not available:', 'paropt')
./tests/test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_require_mpi_check_paropt ... SKIP (00:00:0.00, 61 MB)
('Optimizer not available:', 'paropt')
./tests/test_nsga2_multi_objective.py:TestNSGA2.test_opt ... OK (00:00:1.31, 67 MB)
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_1_SLSQP ... OK (00:00:1.60, 59 MB)
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_3_CONMIN ... OK (00:00:3.03, 60 MB)
./tests/test_rosenbrock.py:TestRosenbrock.test_optimization_0_IPOPT ... OK (00:00:4.68, 65 MB)
./tests/test_tp109.py:TestTP109.test_autorefine ... SKIP (00:00:5.67, 62 MB)
('Optimizer not available: ', 'SNOPT')
./tests/test_large_sparse.py:TestLarge.test_opt_1_IPOPT ... OK (00:00:6.81, 251 MB)
./tests/test_sphere.py:TestSphere.test_optimization_0_ALPSO ... OK (00:00:20.49, 65 MB)

The following tests were skipped:
test_hs015.py:TestHS15.test_optimization_3_NLPQLP
test_hs015.py:TestHS15.test_optimization_4_ParOpt
test_hs015.py:TestHS15.test_snopt
test_hs015.py:TestHS15.test_snopt_hotstart
test_hs015.py:TestHS15.test_snopt_snstop
test_hs071.py:TestHS71.test_nlpqlp_informs
test_hs071.py:TestHS71.test_optimization_0_SNOPT
test_hs071.py:TestHS71.test_optimization_5_NLPQLP
test_hs071.py:TestHS71.test_optimization_6_ParOpt
test_hs071.py:TestHS71.test_snopt_informs
test_hs071.py:TestHS71.test_snopt_setDVFromHist
test_large_sparse.py:TestLarge.test_dense_workspace_too_small
test_large_sparse.py:TestLarge.test_opt_0_SNOPT
test_large_sparse.py:TestLarge.test_opt_2_SNOPT
test_require_mpi_env_var.py:TestRequireMPIEnvVar.test_require_mpi
test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_do_not_use_mpi_check_paropt
test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_no_mpi_requirement_given_check_paropt
test_require_mpi_env_var.py:TestRequireMPIEnvVarOnParOpt.test_require_mpi_check_paropt
test_rosenbrock.py:TestRosenbrock.test_optimization_4_NLPQLP
test_rosenbrock.py:TestRosenbrock.test_optimization_5_ParOpt
test_rosenbrock.py:TestRosenbrock.test_snopt
test_rosenbrock.py:TestRosenbrock.test_snopt_hotstart_starting_from_grad
test_snopt_bugfix.py:TestSNOPTBug.test_opt
test_snopt_bugfix.py:TestSNOPTBug.test_opt_bug1
test_snopt_bugfix.py:TestSNOPTBug.test_opt_bug_print_2con
test_snopt_user_termination.py:TestUserTerminationStatus.test_obj
test_snopt_user_termination.py:TestUserTerminationStatus.test_sens
test_tp109.py:TestTP109.test_autorefine
test_tp109.py:TestTP109.test_snopt

The following tests failed:
test_hs015.py:TestHS15.test_optimization_0_SLSQP

Passed:  26
Failed:  1
Skipped: 29

Ran 56 tests using 8 processes
Wall clock time:   00:00:20.91

Instead of loosening the tolerance, maybe we just need to set a tighter ACC value for SLSQP so that it converges better. In any case, would you prefer bumping stuff upstream then waiting for all tests to pass, or just releasing this as-is and patch it separately?

I am OK with merging this as-is, as it's only the test which is failing for tolerance issues. If you don't have osx arm64 hardware I can help out with the upstream part.
Aside from the tolerance issues, there is a pesky issue where the osx_64_numpy1.19python3.8.____cpython build fails, seemingly intermittently, due to a missing .out file from another SLSQP test. I will re-run again and see if it solves itself...

The builds are passing because osx-arm64 isn't actually tested on CI. (On conda-forge, osx-arm64 builds are cross compiled on Intel Macs for now, so they can't actually run the built packages).  The tolerance error that I pasted above is from local testing on my M1 machine (using a built package I downloaded from CI as an artifact).

Ah I see, I'll merge this then.


Strong name signing for output assemblies

I know that there are two different camps of asseblies be signed with SNK or not.
At my company, we use SNK to ensure (together with authenticode signing) that the results are distributed to the users come from us.
Will the results of all projects included in ASPNET5 be signed with SNK (and maybe even authenticode signed)?
When will this happen in such cases (before RC I hope)?
if not, then all components that use ASPNET5 not be signed with SNK. How are we to ensure that the components come from us?

Strong naming is already supported: https://github.com/aspnet/dnx/pull/2004
However, the packages published for ASP.NET and EF are themselves not yet strong-named, but that's tracked here: https://github.com/aspnet/dnx/issues/2615
So, this should be resolved in the near future. For further discussion on that, feel free to comment on the linked issue. Thanks!


[VS Code] An error occurred while sending the request.

live_share_logs.zip
Error:
An error occurred while sending the request.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.379

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.25.0

platformName
MacOS

platformVersion
17.6.0

@tinghom Perfect! Thanks for confirming that 👍


Testing improvements - Core components

Unit/integration testing improvements for Core component extension methods. We have already Core component test project with 300 tests, but would need assistance on increasing the coverage around the additional method to get included to tests.
All contributions on this side are highly welcome.
Additional ideas and input around improved provisioning engine testing is also highly welcome.

@VesaJuvonen, what is the current status of the existing tests. I had a look into the unit tests in the projects and I find that the PowerShell tests are failing. SI this something in my environment or are these tests not ready to run yet. The initial connects seem to be working.

Since this is too generic issue, will close up for now.


Check for label null values for stderr

Default to stdout if no stderr

I believe wanted functionality is actually already implemented in https://github.com/teragrep/k8s_01/blob/f2a2f208d1a4df162526e142c62c6802625306a1/src/main/java/com/teragrep/k8s_01/config/AppConfigLabel.java#L37-L42 but just poorly documented. Setting labelStderr to null will use value set in labelStdout

It has been implemented already, closing


Snizhana backgrounds

Compressed an image with https://compressjpeg.com/
added the compressed image to /img folder
added a laughing.html background
referenced 'laughing' bg in 2 stories - 'laughing' and 'good-times'

LGTM


pcscd NOT authorized for action: access_pcsc

Describe the bug
Since updating nixpkgs-unstable this morning my Yubikey stopped working again with gpg.
Steps To Reproduce
Steps to reproduce the behavior:

Try to use anything using a smartcard with gpg (In my case a Yubikey.)

Expected behavior
Being asked for my PIN and unlocking things using pcscd gpg-agent stuff.
Additional context
It keeps asking me to insert my Yubikey despite being present.
Running gpg --card-status returns the following:
gpg: selecting card failed: Service is not running
gpg: OpenPGP card not available: Service is not running

Checking the status for pcscd gives me:
○ pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/etc/systemd/system/pcscd.service; linked; preset: enabled)
    Drop-In: /nix/store/6npwg6586svdyf1p4fdz8as91859kp34-system-units/pcscd.service.d
             └─overrides.conf
     Active: inactive (dead) since Fri 2024-02-23 10:31:13 CST; 27s ago
   Duration: 1min 16.442s
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
    Process: 6102 ExecStart=/nix/store/pkw8q8vf74c2mlj3ir51aafqjmz5q7ia-pcsclite-with-polkit-2.0.1/bin/pcscd -f -x -c /nix/store/38wcpbh4yss3vh35vrazm1wbns0vld61-reader.conf (code=exited, status=0/SUCCESS)
   Main PID: 6102 (code=exited, status=0/SUCCESS)
         IP: 0B in, 0B out
        CPU: 71ms

Feb 23 10:29:57 loki systemd[1]: Started PC/SC Smart Card Daemon.

Most telling here is the "NOT authorized for action" part. This looks like an issue that might have been resolved in nixpkgs previously.
https://github.com/NixOS/nixpkgs/issues/280826
I didn't see anything about PolicyKit, though, so not sure this is the same issue.
Notify maintainers
@anthonyroussel
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.17, NixOS, 24.05 (Uakari), 24.05.20240222.98b00b6`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

I just ran into this issue for the first time today after updating nixos-unstable.  The last time I updated was a couple weeks ago, which is strange considering this issue was reported in February.
@YaroKasear did you ever end up finding a resolution or workaround for this?

After upgrading yesterday, I had the same issue as @montchr. I believe this is a different issue than @YaroKasear's.
Some symptoms:

gpg --card-status shows Service is not running. Afterwards, the journal has this error scdaemon[…]: scdaemon[3810]: pcsc_establish_context failed: internal error (0x80100001).
KeepassXC cannot find the hardware key
There are no mentions of polkit errors in the journal

Rolling back my flake updates fixed the issue. After checking my lock file, it seems that the issue has been introduced some time after commit 63c3a29ca82437c87573e4c6919b09a24ea61b0f.

This should be fixed by #308884

The fix is still in staging next, so if you can not wait that long and are willing to rebuild quite a few packages, this overlay should work:
final: prev:

{
  pcsclite = prev.pcsclite.overrideAttrs (old: {
    postPatch = ''
      substituteInPlace src/libredirect.c src/spy/libpcscspy.c \
        --replace-fail "libpcsclite_real.so.1" "$lib/lib/libpcsclite_real.so.1"
    '';
  });
}

I was also running into the same problem with the latest unstable.
It seems like there were no polkit rules for pcsc-lite at /run/current-system/sw/share/polkit-1/rules.d/.
Adding these, albeit very liberal, rules resolved the issue for me.
security.polkit.extraConfig = ''
  polkit.addRule(function(action, subject) {
    if (action.id == "org.debian.pcsc-lite.access_card") {
      return polkit.Result.YES;
    }
  });

  polkit.addRule(function(action, subject) {
    if (action.id == "org.debian.pcsc-lite.access_pcsc") {
      return polkit.Result.YES;
    }
  });
'';

I don't know whether this is related but today I wanted to use gpg with Yubikey and "gpg2 --card-status" did not find a smart card although the Yubikey was plugged and visible with "lsusb". A reboot of my PC did not fix it.
I found these lines with "systemctl status pcscd" and restarted the daemon. After this the card was found.
Nov 30 15:08:01 bat.localdomain systemd[1]: Started pcscd.service - PC/SC Smart Card Daemon.
Nov 30 15:08:01 bat.localdomain (pcscd)[2481]: pcscd.service: Referenced but unset environment variable evaluates to an empty string: PCSCD_ARGS
Nov 30 15:08:23 bat.localdomain pcscd[2481]: 00000000 ../src/auth.c:145:IsClientAuthorized() Process 2605 (user: 987) is NOT authorized for action: access_pcsc
Nov 30 15:08:23 bat.localdomain pcscd[2481]: 00000096 ../src/winscard_svc.c:357:ContextThread() Rejected unauthorized PC/SC client

This means  I have to restart this daemon first before I can use gpg with Yubikey.
OS: Fedora 41 Silverblue
version: pcsc-lite-2.3.0-1.fc41.x86_64


feat: API 网关鉴权方案调整 (closed #1985)

PR
CheckList（PR Assigners）
确认已完成以下操作：

[ ] 已将分支与当前合入分支同步
[ ] 已在关联 Issue 中补充「功能自测」部分内容
[ ] 已更新关联 Issue 的状态 backlog -> todo -> for test -> tested（需通过测试同学测试） -> done
[ ] 将 PR 添加上 pr/reviewable

CheckList（PR Reviewers）
确认已完成以下操作：

[ ] 检查关联 Issue 「功能自测」部分内容
[ ] 必要时打回 pr/reviewable，要求重新修改
[ ] 及时 Approve

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2bea8e0) 74.71% compared to head (6204588) 74.78%.

Additional details and impacted files
@@              Coverage Diff               @@
##           v2.4.4-dev    #2094      +/-   ##
==============================================
+ Coverage       74.71%   74.78%   +0.07%
==============================================
  Files             404      401       -3
  Lines           28259    28160      -99
==============================================
- Hits            21114    21060      -54
+ Misses           7145     7100      -45

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


Authenticate Failed

Please describe the problem you are having in as much detail as possible:
It seems like the authenticate failed error is happening again. (b5de89a)
Error: Error: Connection not established within 15 seconds.
    at VoiceConnection.authenticateFailed (/home/andy/musicbot/node_modules/discord.js/src/client/voice/VoiceConnection.js:256:27)
    at connectTimeout.client.setTimeout (/home/andy/musicbot/node_modules/discord.js/src/client/voice/VoiceConnection.js:280:18)
    at Timeout.setTimeout (/home/andy/musicbot/node_modules/discord.js/src/client/Client.js:422:7)
    at ontimeout (timers.js:488:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:283:5)

Further details:

discord.js version: 11.2.1
node.js version: 8.0.1
Operating system: Linux

[ ] I found this issue while running code on a user account
[ ] I have also tested the issue on latest master, commit hash:

I'm having this exact issues with 11.2.1 and the current master (d8f6198)
{ Error [VOICE_CONNECTION_TIMEOUT]: Connection not established within 15 seconds.
    at VoiceConnection.authenticateFailed (E:\Development\KuroyukihimeBot\node_modules\discord.js\src\client\voice\VoiceConnection.js:260:27)
    at connectTimeout.client.setTimeout (E:\Development\KuroyukihimeBot\node_modules\discord.js\src\client\voice\VoiceConnection.js:284:18)
    at Timeout.setTimeout (E:\Development\KuroyukihimeBot\node_modules\discord.js\src\client\BaseClient.js:70:7)
    at ontimeout (timers.js:488:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:283:5) [Symbol(code)]: 'VOICE_CONNECTION_TIMEOUT' }

Discord Version: 12.0.0-dev
Node.js Version: v8.1.2
OS: Windows 10 Pro

I've spent the last 24 hours thinking I made a mistake somewhere. Funny enough @iCrawl I was following your music bot tutorial on youtube when I ran into this.

this error means you have bad internet

I am not sure if "bad internet" is the only cause of the issue. I mean I have encountered the same error before while I was testing my bot locally (though I couldn't recall the exact combination of commands that I used). And my local PC has a ping of 9ms @devsnek.

I'm fairly certain it's not my internet Speedtest

A speed test does in no way indicate a stable connection.

Well I can use voice normally on my desktop through discord.. Is there another thing I can test? a port I should frisk?

So turns out I was having this problem because I had 'VOICE_STATE_UPDATE' as one of my disabledEvents.. So for anyone else who has this problem.. check there first 😞
*Didn't intend on my bot having voice functionality when i created it so I disabled that event. I find it a little silly that the bot would ignore it's own voice_state_update though?

@zfbTony i think it would be sillier if we didn't disable events in the disabled events list

What about a check in voiceChannel.join() for the disabled event to log that as a reason for error? that doesn't seem all that silly, right?

An array of disabled websocket events. Events in this array will not be processed, potentially resulting in performance improvements for larger bots.  The safest one to disable with the most impact is typically TYPING_START.

We pretty much already warn about it.

I checked my disabled event and it doesn't contain anything. I will include the TYPING_START event into the disabled event as the comment suggested. Meanwhile, do you have others suggestions or tips which may help prevent the error? Thanks! @iCrawl

I have fixed this in a recent commit, you should now only get this error if it genuinely does take too long to receive anything from Discord.
As this is also an old issue, I will close it.

For those who might end here via Google, searching for "Error: Connection not established within 15 seconds", I just wanted to save you some time by pointing out that it is possible to get this error if your voice room doesn't have the "View Channel" permission enabled for the bot.


CLOUDP-169109: Add additional e2e tests for Atlas Search

Proposed changes

Jira ticket: CLOUDP-# CLOUDP-169109
Created the tests based on the documented static and combined mapping examples for Atlas Index creation: https://www.mongodb.com/docs/atlas/atlas-search/define-field-mappings/#static-mapping-example
EVG Patch: https://spruce.mongodb.com/task/mongodb_atlas_cli_master_e2e_atlas_clusters_atlas_search_e2e_patch_0506e355ba2068688fe8855fe9b137205607f471_642c0587e3c331f260813a94_23_04_04_11_10_07/tests?execution=0&sortBy=STATUS&sortDir=ASC

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

Needs rebase

I scheduled https://spruce.mongodb.com/task/mongodb_atlas_cli_master_e2e_atlas_clusters_atlas_search_e2e_patch_1307c981d4f07b9d6db80ebe432fcee8b64a27ae_6435321e32f4176b5edad814_23_04_11_10_10_39/logs?execution=0 so let's make sure those pass

Looks like good to merge


AME jars shrink singularity

About the PR
AME jars can now be pried open with a crowbar and thrown into the singularity to shrink it. Once opened, the jar leaks fuel at a rate of around 60 fuel per second, and singularity-shrinking-effectiveness scales with amount of fuel left in the jar. Max effectiveness is 100 energy with 1000 fuel. For comparison, singulo lv2 is at 200 energy, 3 at 300, 4 at 600, 5 at 1000, 6 at 1500. With, say, two AME crates totalling 6 jars, an engineer can hope to neutralize a lv4 singulo at best with six well-timed throws. At lv5, 6 jars can help but it's a gamble.
This is meant to give prepared engineers a chance to neutralize what is usually a round-ending event that is easily triggered either intentionally through sabotage or unintentionally through engineering fuckups. Keyword is Prepared, because they'll have to ask for surplus AME jars from cargo and act before the singuloose gets too big, or before it eats the unopened AME jars. Creates scenarios in which engineering can choose to throw all their fuel into the singulo in the hopes of dissipating it, or to gamble on the singulo flying away and keeping the station powered. It's also risky, because you need to get within throwing range of the singulo.
Other changes include a more detailed examination message and some visual cues to indicate the jar's state. Also, jars cannot be resealed once opened.
Screenshots

At three stages: leftmost is closed, middle is opened and leaking fuel (with blue light), rightmost is opened and empty.

Integration:

Changelog
:cl:

add: AME fuel jars can now be pried open and thrown into the singularity to shrink it. Current fuel is now also shown when examining.

very much like the idea of being able to neutralize the singularity with AME fuel but not sure I understand the purpose of tying it to a 'leaking' mechanic which seems a little obtuse and doesnt serve much other purpose?

The leaking mechanic serves as an intermediate step between having the AME jar and it being able to neutralize the singularity. Otherwise, there's nothing stopping engineers from just stocking two crates of AMEs beside the CFG or in the PA and calling it a day. With the fuel leaking out, the window to neutralize the singulo is shorter and more skill-based, i.e. dancing around the singulo while microing each jar, can even use a pneumatic cannon to launch it from a safer distance albeit with increased delay and thus less effectiveness.

@mirrorcult I've resolved your comments, changed some descriptions for integration (see screenies on main comment), and added a heating functionality leveraging the Artifact system. Let me know if you'd like anything else changed.

the fuel indicator should be salvaged, might do it later


re-enable integration tests for tpr-backed storage

Historically, the integration tests for tpr-backed storage have been partially disabled due to numerous bugs that we had a lot of difficulty tracking down. Then the big rebase on k8s 1.6 came along and @jpeeler had to disable the remainder of those tests to accomplish that rebase in a timely fashion. (fwiw, that had my blessing because we knew tpr-backed storage was full of bugs anyway and having a small subset of tests run and leave us with a false sense of confidence in the implementation didn't see a worthy reason to delay the rebase.)
Fast forward to now. @arschles and I have painstakingly chipped away at tpr-backed storage bugs in what has been a truly agonizing process. :wink: These integration tests should all work now. 🎉
@pmorie I know we have intentions of tpr-backed storage being tested in e2e, but integration tests and e2e tests are not the same thing. Re-enabling all these tests gives us more coverage and confidence sooner.
I would very much like for this to make it into 0.0.6.

Awesome that bugs have been fixed, and this specific PR is so small. LGTM pending CI

I have never seen any flakes in these integration tests-- only legitimate failures, and since fixing the underlying bugs, these consistently pass. I'm not terribly incline to run this 1k times as it takes several minutes to get through the whole integration test suite. That seems like an oddly high bar. Are we requiring that for all tests now??

What's motivating that? Are we requiring that for all tests now??

In this case, we had a lot of trouble with integration tests flaking, just feeling a little paranoid.  Not trying to block this PR or raise the bar; I chose 1k since that's the number of iterations I normally use for testing for flakes.
Sorry for the delay, I've been dealing with some personal stuff the last couple of days.


Enable custom retrievers

Description
Following remark #135 this PR simplifies a bit how we are supposed to work with a retriever.
Now a retriever only needs to implement the interface Retriever to be eligible to be used by the module.
This change enables the possibility of building custom Retrievers if wanted.
The configurations are still working with no changes, so don't be afraid about this change
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking changes (change that is not backward-compatible and/or changes current functionality)

Closes issue(s)
Resolve #135
Checklist

[x] I have tested this code
[x] I have added unit test to cover this code
[ ] I have updated the documentation (README.md and /docs)
[x] I have followed the contributing guide

Coverage decreased (-2.2%) to 94.523% when pulling 2aee3cf692bf1906de88e2e6c0135a21e516cdf4 on feat/custom-retriever into e8d956cee793a6d6ddc50eaa5565ed345c1396c5 on main.


Loss lambda parameters

Hi! I've realized that this loss implementation doesn't include the λcoord and λnoobj parameters. Is there any reason for that? Does the original Yolo v3 use them?

Thanks!

Same question for me. I searched everywhere but nobody talk about it. If you have any response let me know !


There is no document reference location for SSH Config

Please present a path to the config location in the documentation as there is no reference.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close