mistake in Bayes by Backprop from scratch

I found a mistake in Bayes by Backprop from scratch (NN, classification)
In Model definition - Neural net modeling Section
def net(X, layer_params):
    layer_input = X
    for i in range(len(layer_params) // 2 - 2):
        h_linear = nd.dot(layer_input, layer_params[2*i]) + layer_params[2*i + 1]
        layer_input = relu(h_linear)

it shoud be
def net(X, layer_params):
    layer_input = X
    for i in range(len(layer_params) // 2 - 1):
        h_linear = nd.dot(layer_input, layer_params[2*i]) + layer_params[2*i + 1]
        layer_input = relu(h_linear)

range(len(layer_params) // 2 - 2 will make the second hidden layer to be ignored in forward propagation, but luckily in your case it did not cause a error.
I changed it to range(len(layer_params) // 2 - 1 and rerun the notebook. it wroks fine but seems that there are no improves in result.
Epoch 0. Loss: 2631.05110392, Train_acc 0.94465, Test_acc 0.9443
Epoch 1. Loss: 2607.93411326, Train_acc 0.96125, Test_acc 0.9584
Epoch 2. Loss: 2601.34667942, Train_acc 0.969633, Test_acc 0.9626
Epoch 3. Loss: 2596.63901145, Train_acc 0.974683, Test_acc 0.9679
Epoch 4. Loss: 2593.85184135, Train_acc 0.978433, Test_acc 0.9701
Epoch 5. Loss: 2590.91976531, Train_acc 0.979283, Test_acc 0.9693
Epoch 6. Loss: 2588.03490818, Train_acc 0.983067, Test_acc 0.9734
Epoch 7. Loss: 2586.94554946, Train_acc 0.985667, Test_acc 0.9739
Epoch 8. Loss: 2585.43967896, Train_acc 0.98685, Test_acc 0.9758
Epoch 9. Loss: 2582.76947339, Train_acc 0.98725, Test_acc 0.9755

I think you are right!!!


Suspend subscriptions of users who don't check messages

I've been thinking about ways to improve Updates and I think this is something worth pursuing. There's no need to be using our resources generating data for people that don't use it.
Using a dump from 10/10/2015, there are 33.4 million updates for 41,836 subscribers. 34,627 of those subscribers have not viewed any of their message we have on record (we are now keeping 3 months of updates, so they have not read any within the last 3 months). Those users account for 20.5 of the 33.4 million updates.
I'm proposing if we find someone hasn't read any messages in the last 3 months then we suspend their subscriptions (we can probably even keep their existing updates around since they will be deleted in another 3 months). If we find they come back and read messages, their subscriptions will be reenabled.
This could lead to generating 61% fewer updates, which will have all the benefits that go along with that (fewer and faster Updates delayed_jobs, less load on hevea, less storage in DB, faster dashboards, etc).

Sounds great to me.

Wow! 4/5 of people aren't opening their updates within 3 months? I wonder
if you'd have any success with a "[name], have you checked iNaturalist
lately?" email going out to all of those folks (or anyone who reaches the 3
months without checking in mark). Just a thought to try and re-engage some
of them.
Carrie
On Sun, Oct 25, 2015 at 7:22 PM, Ken-ichi<EMAIL_ADDRESS>wrote:

Sounds great to me.
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/758#issuecomment-150986881
.

--
Carrie E. Seltzer, Ph.D.
National Geographic's Great Nature Project
www.greatnatureproject.org

there are so many people who vanish... It's part of why community ID was
added, right? You can usually tell... someone who added stuff over a short
period of time and then stop. Often it is part of a class they were
required to do but there is no requirement to follow up and curate their
data.
On a more upbeat note, while most PEOPLE end up lapsing, most OBSERVATIONS
seem to be attached to people who are dedicated users and stick around.
The casual vs 'hardcore' user balance is already an odd mix, it would be
great if people stuck around more, i think the issue of class projects and
such is different from other users who arrive and then leave though.
On Sun, Oct 25, 2015 at 7:57 PM, carrieseltzer<EMAIL_ADDRESS>wrote:

Wow! 4/5 of people aren't opening their updates within 3 months? I wonder
if you'd have any success with a "[name], have you checked iNaturalist
lately?" email going out to all of those folks (or anyone who reaches the 3
months without checking in mark). Just a thought to try and re-engage some
of them.
Carrie
On Sun, Oct 25, 2015 at 7:22 PM, Ken-ichi<EMAIL_ADDRESS>wrote:

Sounds great to me.
—
Reply to this email directly or view it on GitHub
<
https://github.com/inaturalist/inaturalist/issues/758#issuecomment-150986881
.

--
Carrie E. Seltzer, Ph.D.
National Geographic's Great Nature Project
www.greatnatureproject.org
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/758#issuecomment-150989034
.

--
Charlie Hohn
Montpelier, Vermont

Is there any way to tell how many are simply gone, vs those who didn't check their updates but did open the web site or a mobile app in the intervening 3 months?

These are the updates pushed out as emails? How would you know if they were read?  Some of us have security/privacy settings that don't open remote images etc in emails.

It seems what is more important is if they look at the website. They could
lovingly read each email but if they are never coming back to the site it
doesn't really matter.
On Tue, Oct 27, 2015 at 4:46 AM, tnywlls<EMAIL_ADDRESS>wrote:

These are the updates pushed out as emails? How would you know if they
were read? Some of us have security/privacy settings that don't open remote
images etc in emails.
—
Reply to this email directly or view it on GitHub
https://github.com/inaturalist/inaturalist/issues/758#issuecomment-151415700
.

--
Charlie Hohn
Montpelier, Vermont

@tnywlls yes these are what users get in emails, and on the site and apps in the form of updates on things they follow - not updates about actions taken on their own content. So they would still get ID notifications for example. What is being suggested is if they don't log into the site or use any of the apps for 3 months, we suspend their subscriptions. We can't monitor if they read their emails, so if someone is just reading emails for 3 months and never using the site or apps, their subscriptions would be suspended too.
Here is what I recommend be done:

[ ] add last_active (Date) and subscriptions_suspended_at (Datestamp) fields to Users
[ ] add ApplicationController method to set users.last_active = Time.now and users.subscriptions_suspended_at = nil whenever there is a current_user
[ ] add rake task, or append logic to inaturalist:delete_expired_updates, which sets user.subscriptions_suspended_at = Time.now if a user has updates, but all updates.viewed_at are NULL
[ ] add logic to has_subscriptions which prevents updates from being generated for users with suspended updates

We could also have it send out a one-time email to the user when we set user.subscriptions_suspended_at. Something to the effect of, "You've been away and we stopped your subscriptions. Login to the site or use one of the mobile apps to resume". Does this seem reasonable? What to people think about sending an email when we suspend subscriptions?

@pleary It might be good to send out an email a couple/few days before the subscriptions are suspended and another when they actually are suspended.

The above commit handles all the tasks I created. There is nothing yet that will email or notify anyone. Anyone have more thoughts on if/how/when we should notify people?

IMO, it's probably worth sending them an email when they are suspended, but not before that. I think the email should say something like, "It looks like you haven't been visiting the site so we suspended update notifications for you. If you'd like to re-activate them, click here" and there should be a link to unsuspend updates for that user.

Initially there will be over 35,000 people we will be suspending updates for, as they haven't viewed any of their updates, which we keep for 3 months. Should we send emails to the initial 35,000 people? If so can we just use the Rails mailer or will that need something else than can handle the scale?
How about this for the email text:
Title: [iNaturalist.org] Your subscriptions are on hold
Body: Hi User,
You have been inactive on iNaturalist.org for a while, so we have suspended your subscriptions. To resume getting updates on site activity, please log in to your account again.

I think a Rails mailer is probably appropriate, since this is something we'll theoretically be doing on a semi-regular basis. Text looks good to me.


Dask lsf manger error

Description
Fixes 2 issues:

Errors in Queue Manager testing now report the whole error, rather than just the head
Fixed bug in monkey-patch of the Dask + LSF manager (Fixes #282)

Status

[ ] Changelog updated (will be updated with patch release)
[x] Ready to go

This previously changed the error message in Manger testing, but #281 fixes it better, so I reverted that here in deference to that one


brew install cocogitto

it would be nice if you provide recipe for Brew for users who don't have cargo
brew install cocogitto
brew also automate installing Shell completions

Hey @xmlking this would be very nice indeed.
I'll work on it soon, or maybe you want to work on this ?
If so please do it there : https://github.com/cocogitto/packages

I would suggest this work not be done here or in the upstream packages repos, but directly contributed to Homebrew. Unless there is some blocker why it can't be included in the main Homebrew repository there is really nothing but advantages to making it official. Easier for end users, better CI testing of builds, faster more open process for updates, etc.
As such anybody (including you @xmlking) can submit a Formula to homebrew-core.

Thanks a lot for new features

I see error message.

after running link command as suggested, seams like working

It looks like this is being deprecated in brew due to

This requires<EMAIL_ADDRESS>which is no longer maintained.[^1]


I wasn't sure if Github Actions would work when enabled on a branch, and the answer is it won't! So I think I'll have to merge this with master to see if it actually works or not.

Nevermind, making the pull request prompted the workflow to begin. Although the Ubuntu checks are failing as MSnbase dependencies aren't installed.
I'll try using a Bioconductor-specific Github Actions workflow instead (see biocthis).

Nevermind, making the pull request prompted the workflow to begin. Although the Ubuntu checks are failing as MSnbase dependencies aren't installed.
I'll try using a Bioconductor-specific Github Actions workflow instead (see biocthis).

Almost ready to go. Only the MacOS check is failing because of a recent update to the withr package that has not been added to CRAN yet (see https://cloud.r-project.org/bin/macosx/contrib/4.0/).
Once withr is at v2.4.1 then merge this PR.

Almost ready to go. Only the MacOS check is failing because of a recent update to the withr package that has not been added to CRAN yet (see https://cloud.r-project.org/bin/macosx/contrib/4.0/).
Once withr is at v2.4.1 then merge this PR.

Thanks for this Charlotte!

I generated .github/workflows/check-bioc.yml using biocthis and then modified it slightly. Technically biocthis is not an official Bioconductor core package. However it was the easiest way I found to implement GitHub actions CI with a package like camprotR that Imports Bioconductor packages.

I can't really review  .github/workflows/check-bioc.yml but I understand this is coming from Bioconductor. Is that correct? Aside from adding cutr, have you made other significant updates? Anything in particular in this file that needs reviewing? From my perspective, if it runs the testing OK, all fine with me 👍

No other significant changes! I just want to get this into master and then I'll pull it into the {ts}_test_test_test branch and start writing more tests.

Can't you merge this branch into {ts}_test_test_test directly in that case. Or am I missing something?

Yes you can. Good point I hadn't thought of that 😅 . I think I can edit the PR to change the target branch?

Great. So just waiting on withr update then?

Nope that's already solved otherwise the MacOS check wouldn't pass. I'll merge now 😁.


More robust input to pdbfixer

I suggest trim_env can set the CRYST1 line before creating the environment. Also it shouldn't require a CRYST1 line in the file. Finally there was a bug with trim that left a partial water block. I have no idea why the partial water block happens, so I skipped the trimming.
Adds a CRYST1 line so that trim_env doesn't complain
with open(pp.H_pdb,'r') as F:
dat = F.read()
with open(pp.H_pdb,'w') as F:
F.write('CRYST1\n')
F.write(dat)
from Bridgeport.utils.bp_utils import trim_env
trim_env(pp.H_pdb) # Measures appropriate box size
#Create Environment
print(datetime.now().strftime("%m/%d/%Y %H:%M:%S") + '//Creating environment with pdbfixer', flush=True)
pp._run_PDBFixer(mode=pp.env, padding=1.5, ionicStrength=pp.ion)
Check completion
if os.path.exists(pp.env_pdb):
print(datetime.now().strftime("%m/%d/%Y %H:%M:%S") + '//Output written to:', pp.env_pdb, flush=True)
Trim
print(datetime.now().strftime("%m/%d/%Y %H:%M:%S") + '//Trimming', pp.env_pdb, 'with padding of 15 Angstroms.', flush=True)
trim_env(pp.env_pdb, 15)

The Bridgeport.utils.trim_env method has been update with a more robust way to handle various naming schemes for HOH atoms. Please reopen this issue if errors continue.


Builds failing in the same way

Something has changed in the build process or main code that is breaking the build, possibly in this commit as this is when the failures started: https://github.com/sul-dlss/libsys-airflow/commit/466f789971c14bd369e5d6a35980254c23db1616

Builds seem to be passing again in main. @jermnelson says he thinks this is done. Closing.


Reduce dependencies

This library is coupled with a lot of libraries.
This list can be reduced.

symfony/polyfill-* can be removed.
mdanter/ecc should be suggested to allow the use of the ECDH-ES algorithms with P-256, P-384 and -
P-521 curves.
psr/cache should be removed (only for key mgmt that will have its own package)
beberlei/assert could be removed

Done. See a019fec22f718e146955eb7db600b0f04da3109c and branch v7


enclosures/open_pill_mini_w_coverplate: Can damage Micro-USB jacket due to less recess left on the top

The current version of the case unfortunately can damage the Micro-USB jacket. There should be more recess left on top. Printed with a Bambu P1S by the way, so nothing unusual.
Could you please release the original files of the model, so it can be modified?

I'm not sure it makes sense to publish the original models here in the repo, but if you email me at<EMAIL_ADDRESS>I'd be happy to send you a copy of it.

Cool! That is a primo first layer, BTW. 🧡


New posts on the blog aren't getting featured

New posts on the blog aren't getting featured and the featured image is rendering strangely, see this post: https://creativecommons.org/2016/07/05/icymi-june-oer-roundup/

Seems like some posts have the 'Featured' highlights set and two have 'Hero'
https://creativecommons.org/wordpress/wp-admin/edit.php?cc_highlight=featured
https://creativecommons.org/wordpress/wp-admin/edit.php?cc_highlight=hero
I guess you'll either need to set this on the next post, or unset it from previous posts.

The trick appears to be to set the "Highlight" as "hero"


Changed nginx template to implement changes suggested by NextCloud 14 release notes

The implemented changes were suggested by the release notes of NextCloud 14
For background compatibility I used Jinja if statements to only include these changes when nextcloud_version_14_or_higher is set to true.
Since new installs will probably go with the newest version anyway, I've set its default value to true.
However it would be a lot more elegant if the value of this variable would be calculated based on other nextcloud_version_... variables.

Hi again @belidzs
Thank you for the contribution
I was also privately working on this one but I wanted to find it "automatically" in order to keep the version selection system not more complicated than it is already.
While testing, I concluded that releases channels  and also the "special" type are not relevants to find if the version is newer than 13
Then I made this truth table  with true conditions. imply each time, "the variable is defined and ..."

OR
latest
major
full

-
yes and (major is null)
>13|master
split(".")[0] >13

I can implement this condition as a private boolean instead of the new variable on you PR if you allow me.
Regards, Aal.

hi @aalaesar! As you can see from the commit history I tried to reverse engineer the version selection system to make this work automatically but I eventually decided against it as many edge cases would have to be handled (like nightly builds after NC14 was released, etc) and it was too much work for me at the moment.
So I really don't mind if you pick up from here either in my repo or in yours. It's totally up to you :) I've granted the neccessary write permission already.
Thanks for your great work on this!

hi @belidzs,
What were the edge cases you were thinking about ? (may spare me some time 😄  )
With the truth table the only edge case I can think of (for now) is when the user provides an offline zip/tar.gz package
but this could be mitigated by making nextcloud_version_major mandatory in this case
(also updated the truth table for the daily channel)

To be honest the rule system for selecting versions was a bit hard to understand to me and this is why I stopped "reverse engineering" it.
For example I wasn't sure how illegal combinations were handled or what to do when the daily or special variables are defined. Now I start to understand but I still feel like you are better suited for this job.

To be honest the rule system for selecting versions was a bit hard to understand to me and this is why I stopped "reverse engineering" it.

You're right, the parameters and how they work are poorly explained. I initially tried a text/table only ReadMe but It will be much easier to understand with some graphic representation.

For example I wasn't sure how illegal combinations were handled or what to do when the daily or special variables are defined. Now I start to understand but I still feel like you are better suited for this job.

the "heart" of the "link computing system" is in  vars/main.yml
It contain one dict with 4 keys. each one representing some kind of jinja2 regex-like for the archive name.
Then in tasks/nc_download
A block a 2 tasks emulate an If,  then,  else condition  In case the user choosed latest ,because the file name is latest in this case.
I'll drawn a finite state machine to explain it in the readme. It may be more understandable.
Regards,
Aal

hi @belidzs
I've made this diagram in order to describe how nextcloud names its archives
do you think it make the parameters clearer ?
their is still some typos but the logic is here.
any suggestion is welcome
Regards,
Aal.

hi @belidzs
whould you like to review the 3 last commits ?
two brains are better than one :smile:

Ok.
no pb.
thank you for the feed back. 😃
Regards.
Aal.


[Enhancement]: Add systemd units for production deployments on Podman

What would you like to be added:
systemd units for running MicroShift on Podman on RHEL in production. This includes creation of the Podman volumes for keeping MicroShift state, least privileges (seccomp et al.), ensuring MicroShift restarts upon failure, etc. We should also suggest an auto-update strategy. That production deployment should use an external CRI-O instance, so MicroShift container restarts/redeployments don't disrupt workloads (however, we may want to also provide an example for the "all-in-one" MicroShift container with CRI-O).
Potentially useful: systemd for Podman, auto-updates, and seccomp for containers.
Why is this needed:
We need a prescriptive way how to do this, so we a) maximise chances users successfully deploy without requiring lots of upfront reading and b) we can provide better test coverage for this scenario.

scenarios:

all-in-one podman image and a systemd unit file with the recommended run command
podman image with crio and kubelet mounted from the host unit file with recommended run command
identify recommended seccomp profile
document update process, auto-update process - (feature within podman)

@husky-parul we get to use this! :grin: https://podman.io/blogs/2019/10/15/generate-seccomp-profiles.html#the-oci-seccomp-bpf-hook

@sallyom in the second scenario, the kubelet would still have to run in the container (i.e. just CRI-O on the host). As least until we support multi-node.

Background
Using podman to start containerized microshift can ensure timely image update to pick up the latest Microshift release.
Additionally, using crio service on host allows workload continunity during Microshift upgrade.

Start containerized microshift
podman run --privileged --ipc=host --network=host  \
         -d --rm \
        -v /var/run:/var/run \
        -v /sys:/sys:ro \
         -v /var/lib:/var/lib:rw,rshared \
         -v /lib/modules:/lib/modules \
         -v /etc:/etc \
         -v /run/containers:/run/containers \
         -v /var/log:/var/log \
         quay.io/microshift/microshift:4.7.0-0.microshift-2021-08-31-224727-linux-amd64

Demo
Check pods via kubectl:
[root@rhel microshift]# export KUBECONFIG=/var/lib/microshift/resources/kubeadmin/kubeconfig
[root@rhel microshift]# kubectl get pods -A
NAMESPACE                       NAME                                  READY   STATUS    RESTARTS   AGE
kube-system                     kube-flannel-ds-xlj66                 1/1     Running   0          38s
kubevirt-hostpath-provisioner   kubevirt-hostpath-provisioner-bfjvw   1/1     Running   0          39s
openshift-dns                   dns-default-s624v                     3/3     Running   0          38s
openshift-ingress               router-default-6d8c9d8f57-8n5qs       1/1     Running   0          38s
openshift-service-ca            service-ca-64547678c6-fd4bq           1/1     Running   0          39s

Check containerized microshift via podman:
[root@rhel microshift]# podman ps
CONTAINER ID  IMAGE                                                                           COMMAND     CREATED             STATUS                 PORTS       NAMES
428a0bfb8b5f  quay.io/microshift/microshift:4.7.0-0.microshift-2021-08-31-224727-linux-amd64  run         About a minute ago  Up About a minute ago              fervent_kare

Check crio pods:
[root@rhel microshift]# crictl ps
CONTAINER           IMAGE                                                                                CREATED             STATE               NAME                            ATTEMPT             POD ID
e1343381ab088       ebb673575b8b1081b417eb000208b5818cd7031ccbf7fdc583d003611a8f98f4                                                4 minutes ago       Running             dns-node-resolver               0                   58d75053d6191
21e6deca5b878       18248adc08dc2d2dbf1a7c192dc0a707bbc81766aecf8b9b615b8769d7cc3f8a                                                4 minutes ago       Running             kube-rbac-proxy                 0                   58d75053d6191
c4c9ac7080ac3       d3704d0b0df2e397b83dccbf31f0405b74a578e19eb16618adb04a7910d608ed                                                4 minutes ago       Running             dns                             0                   58d75053d6191
d1a6fab76e06e       52866d4b65279ebbba6c33b48d7aa08be85624a71d845b56ade6646749c8236a                                                4 minutes ago       Running             router                          0                   202b48eab1812
be1f092238e58       cfbfdcba5a82ceff418e260fbde0131a711e03a762a1e6f4062302ca6987fb4e                                                4 minutes ago
       Running             service-ca-controller           0                   825821bf835dc
99df18e71c3a0       quay.io/kubevirt/hostpath-provisioner@sha256:8cf5c2186a0357a70b835f2ef76430306e91da5743f375f87693f61a470ac75f   4 minutes ago       Running             kubevirt-hostpath-provisioner   0                   1cbc645342688
50be83ccf9e10       8522d622299ca431311ac69992419c956fbaca6fa8289c76810c9399d17c69de                                                4 minutes ago       Running             kube-flannel                    0                   6a8b86de590d2

@fzdarsky @sallyom @rootfs
The secomp filter are as following
{"defaultAction":"SCMP_ACT_ERRNO","architectures":["SCMP_ARCH_X86_64"],
"syscalls":[{"names":["accept4","access","arch_prctl","bind","brk","capget","capset","chdir","clone","close","connect","dup2","epoll_create1","epoll_ctl","epoll_pwait","epoll_wait","execve","exit_group","fallocate","fchdir","fcntl","fdatasync","flock","fstat","ftruncate","futex","getdents64","getegid","geteuid","getgid","getpeername","getpid","getppid","getrandom","getrlimit","getsockname","getsockopt","gettid","getuid","inotify_add_watch","inotify_init1","ioctl","listen","lseek","madvise","mkdirat","mmap","mount","mprotect","munmap","nanosleep","newfstatat","openat","pipe2","pivot_root","prctl","pread64","prlimit64","pwrite64","read","readlink","readlinkat","recvfrom","recvmsg","renameat","rt_sigaction","rt_sigprocmask","rt_sigreturn","sched_getaffinity","sched_yield","select","sendmsg","sendto","set_robust_list","set_tid_address","sethostname","setresgid","setresuid","setrlimit","setsid","setsockopt","sigaltstack","socket","stat","statfs","statx","sysinfo","tgkill","time","umask","umount2","uname","unlinkat","wait4","waitid","write"],"action":"SCMP_ACT_ALLOW","args":[],"comment":"","includes":{},"excludes":{}}]}


_ is not defined

Hi I applied the version in the guide. but get the error
angular-1.5.8.js:13920 ReferenceError: _ is not defined
at getFlag (http://......./js/angular-simple-feature-flags.js:56:23)
any suggestions?

issue above was resolved by including
underscore-min.js
lodash.min.js


Support aux builds in test suite

To support aux builds in our test suite (and hopefully to reuse that for rustc's test suite), @oli-obk suggested we could patch compiletest to support using a different build command for the final binary vs the aux builds.

Dependencies are supported now, @oli-obk do you think there is anything left to do for this issue?


Update markdown-content.mdx

Description
The stated repo was archived and forked back.

Discord user TheCell#2803

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.


[ONNX] Extend converter for Attention from Microsoft onnxruntime contrib opset

Earlier I added converter for QAttention (see PR#13654).
In this PR, I've added support for past input and unidirectional attribute in Attention. I've also moved the common code for QAttention and Attention into a base class.

@tvm-bot rerun


Flow does not detect missing destructured function parameters

When I use deconstruction on function parameters, flow does not detect missing ones. This is particularly painful when defining stateless functions and I add a parameter that is not there. Please see example below.
interface Context {
  user?: UserModel
}
const def: Context = {};
const { userId } = def; // DETECTED MISSING .. throwing error = OK

function foo({ userId }: Context) { // NOT DETECTED .. flow says that everything is fine
}

Ok, the error starts to appear on the first use of userId.
I was confused, in Typescript this pops up immediately. But makes sense the way it's done in flow.


Upgrade to stable 2.11.2

This PR:

re-initialized the git subtree onto stable-2.10.2
upgrades the subtree to stable-2.11.1
subtree to stable-2.11.2

Do not squash-merge This will destroy the subtree commits, instead use Create a merge commit

I'm not really confident with linkerd, yet. But maybe we could review this together.

@Gacko lets talk about this next week ;)


[fix] Fixed CopyableFieldsAdmin fields order #335

Fixes #335

Coverage: 98.8% (+0.002%) from 98.798% when pulling cb78d18516e2bca54066ce9ae304d7a396cde68e on issue-335/fix-copyable-admin-field-order into b10d3cdd1f3eadf3d224ccb5f078221b181f6721 on master.

I found that it's the conversion of a tuple to a set or vice versa that causes the random admin field order @nemesisdesign.
Without patch

When we convert a tuple to a set in python, the order of the elements in the tuple is not preserved because sets do not have an inherent order. Sets are implemented using a hash table, which means that the elements are stored in an arbitrary order based on their hash values. This order can change each time the set is created or modified, that's why I removed this in cb78d18 (#336)

When running the below sample test (test_copyablefields_admin_fields_order) a few times, it gives me a different result each time:

    def test_copyablefields_admin_fields_order(self):
        path = reverse('admin:test_project_project_add')
        response = self.client.get(path)
        ma = ProjectAdmin(Project, self.site)
        # uuid should be missing in ma.get_fields
        # because we're testing project admin add form
        print(ma.fields, ma.get_fields(self.client.request))
        print(ma.readonly_fields, ma.get_readonly_fields(self.client.request))

Results:
You may have noticed that we are receiving random admin field orders, as shown below. Therefore, if you remove this patch and run the new test case that I recently added in 5deafdb (#336), it is possible that the test might pass instead of failing. This is because the set conversion behavior, which I already explained above.


Replace infinite scroll with pagination

This issue is to replace the infinite scroll on the Submissions page and the Entity Data page with pagination. That's called for in the release criteria for v2025.1 and should also help a lot with performance on those pages.
Note that we have an existing Pagination component that we can use for this.

@lognaturel mentioned that one way that infinite scroll is useful is that users can search for particular text within the larger number of submissions on the page. We discussed that we could make the maximum page size selectable in the pagination component something large so that that type of searching is still easy to do. At some point, maybe we'll add a way for Backend to search submissions.


Kamal 2 compatiblity

Is this compatible with the new Kamal v2 and kamal-proxy?
Thank you!

I can confirm that kamal-skiff is compatible with Kamal v2 and the new proxy. I updated the kamal gem and followed the standard v1 -> v2 upgrade.


Filter: date range

Input two dates as a range for search filtering

Plan is to feed 'start' and 'end' values into parameters passed though the API query.


skywalking alarm filter usage not work

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

Question
in skywalking alarm filter, in the file :alarm-settings.yml, i want to create a alarm rule and filter out some endpoint and service,
use the exclude-names and exclude-names-regex, but seems not work
the version of my skywalking is 7.0
use it as below: hairuo-gateway is a service
exclude-names：

hairuo-gateway

exclude-names-regex:

./${server.error.path:${error.path:/error}}.
.hairuo-gateway.
/${server.error.path:${error.path:/error}} in component-distribution
/${server.error.path:${error.path:/error}} in component-distribution
bizcrm_saasb_initAcsDataFromContract in biz-crm-bridge-crm

the alarm i recevie is like this
[
{
"scopeId":3,
"scope":"ENDPOINT",
"name":"/crm/web/generic/bizcrm/saasb/home/queryHomeMenu in hairuo-gateway",
"id0":684,
"id1":0,
"ruleName":"endpoint_sla_49_rule",
"alarmMessage":"endpoint /crm/web/generic/bizcrm/saasb/home/queryHomeMenu in hairuo-gateway",
"startTime":1593581843991
}
]
[
{
"scopeId":3,
"scope":"ENDPOINT",
"name":"/${server.error.path:${error.path:/error}} in cloudwareaiinvite-web",
"id0":1279,
"id1":0,
"ruleName":"endpoint_sla_49_rule",
"alarmMessage":"endpoint /${server.error.path:${error.path:/error}} in cloudwareaiinvite-web",
"startTime":1593581845785
}
]
is there any wrong with it?
__
Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Endpoint is not service, it belongs to a service.

/crm/web/generic/bizcrm/saasb/home/queryHomeMenu in hairuo-gateway

This is the endpoint name in the alarm. Make sure your name regex matching them. RunningRule#in is the core, debug it if necessary.

for the endpoint mentioned above:
/crm/web/generic/bizcrm/saasb/home/queryHomeMenu in hairuo-gateway
i try to use
.hairuo-gateway.
to regex match to it ,but it seems not work

.*hairuo-gateway.*

You should not ask for Regex. This is not the thing we created.

I have told you the codes, do your local tests, and read codes.

exclude-names-regex:

.*/${server.error.path:${error.path:/error}}.*
.*hairuo-gateway.*
/${server.error.path:${error.path:/error}} in component-distribution
/${server.error.path:${error.path:/error}} in component-distribution
bizcrm_saasb_initAcsDataFromContract in biz-crm-bridge-crm


Update Gulp.md: gulp-uglify cannot handle ES6+ syntax

Use gulp-terser instead of gulp-uglify. For example, the latter (current version 3.0.2) doesn't recognize ES6 template literals:
GulpUglifyError: unable to minify JavaScript
Caused by: SyntaxError: Unexpected character '`'

After replacing it with gulp-terser, I managed to run the build without error.

I haven't tried this yet, but this is an older guide. Does this run? I can trust you on scout's honor 😄

Yeah I ran it. Trust me on scout's honor 😉


Topic Idea: Mental Health

Main questions:
What is the big picture/end result?
What topic in mental health are we focusing on?
(demographics: race, location, age, financial variables, etc.)


Support renaming of the XSL Transformation files

Changes in this PR:
In https://github.com/nationalarchives/ds-caselaw-public-access-service/pull/72
we will be renaming the XSL Transformation files in Marklogic from judgment0
and judgment2 to as-handed-down and accessible-html, in order to be more
descriptive. This commit supports those changes.
Trello card / Rollbar error (etc)
https://trello.com/c/dylwn8lt/830-rename-judgment2-and-judgment0-xslts-in-public-access-service

[ ] Requires env variable(s) to be updated

The renamed XSLTs are now in Marklogic on prod & staging


Cant get higher speed than 8000hz (Arduino due)

Hi, I am running the newest version on Arduino DUE, I am running in 1/8 microstepping with TMC2209. I cant get a speed over 8000, no matter if I setup slow acceleration, or a fast one I get the same result. 8000 works nice but when I tested 9k,10k,12k hz it just vibrating, the motor accelerates then it got to a high speed, and it just start moving back and forth really fast but still moving a little bit in one direction. like it is losing steps. The issue is definitely not the motor, as on the DUE I am still able to run AccelStepper with these speeds, tested up to 20k with 200k acceleration. But it would be nice to migrate to FastAccelStepper as I need to run 4 motors in these speeds.
I setup the tested motor at pins
STEP pin 6
DIR pin 7
an another motor was setup at pins, but was not set any instruction, after I saw what the motors did in my project when I switched AcceelStepper to FastAccelStepper
STEP pin 8
DIR pin 9
Thanks

Hmmm, I’ve definitely run faster than 8khz.  I suspect you’ve got more interrupts running on the processor.  That’s not to say that this code is behaving.  I documented in another post that I want to rewrite to only use the pwm interrupts.  I suspect that will fix a lot of issues.  There are some other optimizations to be had as well.  So this is not a works for me…not at all.  In fact, I’d like to know if you run just the steppers, does it work?  If it’s just barely not working, I’d bet changing the PIO interrupt to falling edge and killing the usleep would make something of a difference.  How much?  Not sure.  But I can probably make that change sooner than the whole rewrite.
That said, I do want to get to the rewrite.  However, the project I ported for initially is still dragging on.  (Not the software part). I should put up a project log somewhere…I’m fairly certain though, I’m done with the mechanicals.  So I should be back to the software soon.  In fact, if the latest change doesn’t fix the “backlash” I’m seeing, I’ll have to assume it’s real.  But I’d found a sensor was able to move…so, it’s unlikely.
so, my intended schedule is to get this thing tested this week, next week be some more integration testing, and hopefully the week after being back to some serious software work!

@clazarowitz no other interupts run on the arduino, it was just a test code for fast accelstepper, but I found out accelstepper was lying about the achieved speed, but it was still more than 8k, 12k was meassured. I moved to arduino giga and also wrote my timer based stepper micro library. But would like to use the due in the future. Sorry to bother. I tried to look into the source of this lib but to be honest I dont understand the timer stuff (I am new in this lower level programming), also chceked out DueTimer so maybe it could help, but all I got was was stable slow speed. On Giga I combined portenta timer with some port manipulation to control multiple steppers at the same time with Bresenhams algorhitm, and that did the magic for me, but I again hit the 12k steps/sec limit. I tried multiple ramping algos but 12k was the max I got. So for now I will stick to the giga and ordered some new motors with defined torque curves, but I can try the new motors on the Due and fastaccellstepper as well if this type of test would help you.


NuxtLink, target and config.app.baseUrl

Environment

Operating System: Linux
Node Version:     v20.2.0
Nuxt Version:     3.7.4
CLI Version:      3.9.0
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Describe the bug
NuxtLink is not using the Nuxt config app.baseUrl when target="_blank" is set.
Reproduction

Create an app with a baseUrl, eg /en
Add a NuxtLink without target, eg <NuxtLink to="/my-page">snip</NuxtLink>
Add a NuxtLink with target, eg <NuxtLink to="/my-page" target="_blank">snip</NuxtLink>

Result:

The first link will be transformed as snip
The second link will be transformed as snip

Additional context
No response
Logs
No response

Duplicate of #23737, resolved via https://github.com/nuxt/nuxt/pull/23751, already available on the latest nightly release ☺

Sorry, I didn't saw it during my search


track source files per target

With this MR we add tracking of source files per target. This means
that when we change a particular source file, all targets which depend
on it will be updated. Together with the target based dependency we already use,
we also maintain the correct order of compilation of targets.
This fixes #46.

@hv15 , this seem to be an overkill.  Dependencies to C files are propagated correctly, look:
build|master* => make seq-module-List
[100%] Built target seq-module-List
build|master* => echo "#define X 5" >> ../src/structures/src/List/hd.c
build|master* => make seq-module-List
Scanning dependencies of target seq-module-List
[ 33%] Generating /tmp/Stdlib/build/src-seq/structures/src/List/hd.o for target `seq'
[ 33%] Building module `List' for target `seq'
[100%] Built target seq-module-List
build|master* => make seq-module-List
[100%] Built target seq-module-List

This is achieved by IMPLICIT_DEPENDS C "${src}" in custom command.  So, I would say that Bob's problem can be fixed with:
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index a38a097..560f6f8 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -409,7 +409,7 @@ FOREACH (name ${SAC_SRC})
             ${SAC2C} -v0 -linksetsize ${LINKSETSIZE} ${NOTREE_FLAG} -o ${DLL_BUILD_DIR} "${src}"
         WORKING_DIRECTORY
             "${dir}"
-        DEPENDS ${targets_list}
+        DEPENDS ${src} ${targets_list}
         COMMENT "Building module `${dst}' for target `${TARGET}'")

     # Install compiled Tree/Mod parts of the compiled module

I think a more important question is: do we need to rebuild module A if it depends on B which have changed.
For example ArrayArith depends on Bool.  If I change the source file (or the c dependencies) of Bool, it would cause rebuild of Bool but not ArrayArith.  Do we need to? @sbscholz ?
I guess we might: if I remove a function in Bool that is being used in ArrayArith, there might be a linking error.  Or not?

@hv15 , this seem to be an overkill. Dependencies to C files are propagated correctly, look:
build|master* => make seq-module-List
[100%] Built target seq-module-List
build|master* => echo "#define X 5" >> ../src/structures/src/List/hd.c
build|master* => make seq-module-List
Scanning dependencies of target seq-module-List
[ 33%] Generating /tmp/Stdlib/build/src-seq/structures/src/List/hd.o for target `seq'
[ 33%] Building module `List' for target `seq'
[100%] Built target seq-module-List
build|master* => make seq-module-List
[100%] Built target seq-module-List

This is achieved by IMPLICIT_DEPENDS C "${src}" in custom command. So, I would say that Bob's problem can be fixed with:
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index a38a097..560f6f8 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -409,7 +409,7 @@ FOREACH (name ${SAC_SRC})
             ${SAC2C} -v0 -linksetsize ${LINKSETSIZE} ${NOTREE_FLAG} -o ${DLL_BUILD_DIR} "${src}"
         WORKING_DIRECTORY
             "${dir}"
-        DEPENDS ${targets_list}
+        DEPENDS ${src} ${targets_list}
         COMMENT "Building module `${dst}' for target `${TARGET}'")

     # Install compiled Tree/Mod parts of the compiled module

I thought so as well, and initially did make the same change as you propose. And exactly to your point in your next comment, is this sufficent or not? I think we do need to recompile all the modules that depend on module B, maybe not for used functions but definitely in the case where we import them. We otherwise risk then having two function definitions (namespaced of course) but which have different implementations which can could have different output from each other.

No it doesn't, here:
build|master* => make seq-module-ArrayArith
[  0%] Built target seq-module-ScalarArith
[100%] Built target seq-module-ArrayBasics
[100%] Built target seq-module-Bool
[100%] Built target seq-module-ArrayArith
build|master* => echo "int FOO() {return 1;}" >> ../src/structures/Bool.sac
build|master* => make seq-module-ArrayArith
[  0%] Built target seq-module-ScalarArith
[100%] Built target seq-module-ArrayBasics
[100%] Building module `Bool' for target `seq'
[100%] Built target seq-module-Bool
[100%] Built target seq-module-ArrayArith

The problem is that the actual library (.so file) does not have dependencies on the used/imported modules.
Here is the generated code (src-seq/CMakeFiles/seq-module-ArrayBasics.dir/build.make):
lib/host/seq/libArrayBasicsMod.so: src-seq/structures/ArrayBasics.sac
	@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=/tmp/Stdlib/build/CMakeFiles --progress-num=$(CMAKE_PROGRESS_1) "Building module \`ArrayBasics' for target \`seq'"
	cd /tmp/Stdlib/build/src-seq/structures && /tmp/sac2c/build_r/sac2c_p -DHAVE_CONFIG_H -cppI/tmp/Stdlib/build/include -cppI/tmp/Stdlib/include -DEXT_STDLIB -target seq -Xc "-DHAVE_CONFIG_H -I/tmp/Stdlib/build/include -I/tmp/Stdlib/include -DEXT_STDLIB" -Xtc "-DHAVE_CONFIG_H -I/tmp/Stdlib/build/include -I/tmp/Stdlib/include -DEXT_STDLIB" -v0 -linksetsize 500 -o /tmp/Stdlib/build/lib /tmp/Stdlib/build/src-seq/structures/ArrayBasics.sac

lib/tree/host/libArrayBasicsTree.so: lib/host/seq/libArrayBasicsMod.so
	@$(CMAKE_COMMAND) -E touch_nocreate lib/tree/host/libArrayBasicsTree.so

src-seq/structures/ArrayBasics.sac: ../src/structures/ArrayBasics.xsac
	@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=/tmp/Stdlib/build/CMakeFiles --progress-num=$(CMAKE_PROGRESS_2) "Building \`ArrayBasics.sac' from \`ArrayBasics.xsac' for target \`seq'"
	cd /tmp/Stdlib/build/src-seq/structures && /tmp/sac2c/build_r/sac2c_p -DHAVE_CONFIG_H -cppI/tmp/Stdlib/build/include -cppI/tmp/Stdlib/include -DEXT_STDLIB -target seq -Xc "-DHAVE_CONFIG_H -I/tmp/Stdlib/build/include -I/tmp/Stdlib/include -DEXT_STDLIB" -Xtc "-DHAVE_CONFIG_H -I/tmp/Stdlib/build/include -I/tmp/Stdlib/include -DEXT_STDLIB" -cc ccprog -Xc -E -Xc -x\ c -noprelude -o /dev/stdout /tmp/Stdlib/src/structures/ArrayBasics.xsac > /tmp/Stdlib/build/src-seq/structures/ArrayBasics.sac

seq-module-ArrayBasics: lib/host/seq/libArrayBasicsMod.so
seq-module-ArrayBasics: lib/tree/host/libArrayBasicsTree.so
seq-module-ArrayBasics: src-seq/CMakeFiles/seq-module-ArrayBasics
seq-module-ArrayBasics: src-seq/structures/ArrayBasics.sac
seq-module-ArrayBasics: src-seq/CMakeFiles/seq-module-ArrayBasics.dir/build.make

So we do have all the correct dependencies for the ArrayArith target.  But, not on the actual file.  So when we make ArrayArith it sees that Bool changed, so it rebuilds it, but as the output of ArrayArith is already built, it won't do anything else.
So really, all we need to do is to add something like lib/host/seq/libArrayBasicsMod.so: seq-module-ArrayBasics, that's all that is missing.  I guess one needs to consult with the cmake manual to find a canonical way of specifying this.  I bet there is an elegant way without computing things manually.

Hmm, actually, I might be wrong...  According to this:
https://samthursfield.wordpress.com/2015/11/21/cmake-dependencies-between-targets-and-files-and-custom-commands/
one needs to add the sources manually, similarly to what you do.
One more thought: have you considered extending RESOLVE_SAC_DEPENDENCIES, and return not only the list of targets, but the list of sources as well, as you actually have them in the code.  In this case you could avoid recomputing.

@ashinkarov I've re-implemented this, and its turned out much neater. I created a wrapper around the RESOLVE_SAC_DEPS_AS_TARGETS function, and append the source files to the target list.
I looked into using RESOLVE_SAC_DEPENDENCIES but this returns the shared library files to depend on, which is more useful for target depends then custom command depends.

@hv15 , the new stdlib diff looks much cleaner now!
As for the new function itself, I find its implementation weird, and I think that there are the following two problems with it.

Assumption that there exists a magic list of all the sources...  What if we don't have one?  This kind of breaks compositionality.
You hardcode the pattern "-([A-Za-z0-9_]+)$", but that is just wrong.  You don't know (in general case) what's inside the target_name_template.

As RESOLVE_SAC_DEPENDENCIES gets a sac file, calls  sac2c -M on that file, gets the list of the source dpendencies (the one that we are actually after) and turns it into a list of targets that you return, I would assume that the simplest solution here would be to add one more return variable ret_srcs and every time you update ret with target, you update ret_src with the source.  In this case you would automatically avoid both problems.  Am I missing something?  (After you have macro that returns 2 lists, you can add wrapper macros to get each list individually, and you can keep the original name, as the macro can be used in some existing code)
One more problem that we would have to test.  What happens if I change the imports in the sac module?  I guess this won't be picked up by the current design, right?  As we would need to call sac2c -M within the makefile target, and not as a configure step.

As for the new function itself, I find its implementation weird, and I think that there are the following two problems with it.

Assumption that there exists a magic list of all the sources...  What if we don't have one?  This kind of breaks compositionality.

You hardcode the pattern "-([A-Za-z0-9_]+)$", but that is just wrong.  You don't know (in general case) what's inside the target_name_template.

As RESOLVE_SAC_DEPENDENCIES gets a sac file, calls sac2c -M on that file, gets the list of the source dpendencies (the one that we are actually after) and turns it into a list of targets that you return, I would assume that the simplest solution here would be to add one more return variable ret_srcs and every time you update ret with target, you update ret_src with the source. In this case you would automatically avoid both problems. Am I missing something? (After you have macro that returns 2 lists, you can add wrapper macros to get each list individually, and you can keep the original name, as the macro can be used in some existing code)

The thing that is missing is how one should compose the source path. With sac2c -M I get module names, which equate to some Module.sac file, but we have no path information. The dependencies must be given with the correct path to the sources otherwise CMake complains it cannot find the files and satisfy the dependency. We do not use a standardised format for source paths, so there isn't an easy way to do this, unless:

we just pass the hardcoded sources paths (as is currently done), or
scan through $CMAKE_SOURCE_DIR for the file so that we have the complete path (can work, but will slow down configure a lot).

Hmmm, the other option might be to simplify the macro to just output the names of source files, and then within the stdlib build system actually figure out what the paths are... that might be the most practical solution for this. What do you think?

One more problem that we would have to test. What happens if I change the imports in the sac module? I guess this won't be picked up by the current design, right? As we would need to call sac2c -M within the makefile target, and not as a configure step.

I suppose so, I don't think we can capture this without re-configuring.

I might have a solution for this, but it depends on https://github.com/SacBase/cmake-common/pull/5 being accepted... what do you think @ashinkarov ?

Is anybody going to merge this code? Thanks...

FYI, macos build fails because we're using the latest sac2c for mac, which was built on the M1 using XCode 12.5 --- the github machines don't yet have XCode 12.5 generally available. See #62 for more details.


build(template): template for test project

Description
Add a template for test projects, so that it's easier to set up new test project structure through dotnet new test.project.
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

close since we implemented scaffolding in our generator.


Fix add/substract operation arguments in the docs

Fixes #11
It's been a while since this was reported, just noticed it's still there, so here's the PR :)

Coverage remained the same at 94.958% when pulling ba825310f1d2a3f106a27bcaad41895ca5d25784 on levacic:bugfix/update-documentation into b369eaa7f9e82544d40be19484b97f1e3d3a0220 on davidkalosi:master.


bumper

jden bump major
jden bump minor
jden bump patch
updates package.json
commits git repo
tags commit

omg wouldnt it have been great to know about npm version like three years ago?


cmd_

Fixes #234

Awesome! I didn't know this was possible, A few things to clean up, but a great addition!

Awesome - looks great. I'll need to play with it a bit this weekend to check it really is matching my expectation, but a fantastic addition. Shame GHC makes it so hard!

I tried again with just having Unit defined in the one module and it worked -- maybe I made a typo or something earlier. But I haven't tested it with GHC 7.{4,8}, hopefully the CI can illuminate any problems ...

All works nicely - many thanks!
With your revised code I had a shot at merging the Unit module into Command and it worked, so I guess whatever you managed to fix worked there too.

Yay!
I don't feel particularly strongly on it, but I think that having a separate module for Unit is better so that all the typeclass instances in Command.hs aren't marked as overlapping in GHC <7.10. I can only imagine it being a problem if an instance head in Command.hs is written incorrectly, though it still does seem like Better DesignⓇ to me.

Good point. I'm not so worried about that since GHC 7.8 is mostly legacy by now, and if they did overlap, GHC 8.0 would catch them anyway. If it had to be that way in newer compiler versions I'd have gone the separate module route.


Added ext-bcmath to the test app dependency.

Also removed composer.lock so that composer needs to refer to composer.json.
fixes #112

@cedricziel FYI

Thank you for covering my back! :)
LGTM

@bshaffer This change makes sure that the php.ini in the project root directory works during the build.

LGTM, although I wish the test was more explicit

@bshaffer merged, but pull request is welcome :)


no module named uber

I am using python3.5.1 right now. I have installed uberpy using pip.
when I was trying to import uberpy module in python IDE
it gives me following trace back
Traceback (most recent call last):
File "<pyshell#8>", line 1, in
import uberpy
File "C:\Users\thean_000\AppData\Local\Programs\Python\Python35-32\lib\site-packages\uberpy_init_.py", line 8, in
from uber import Uber
ImportError: No module named 'uber'
please help me work it out!
I will be appreciated!

Hello!
The library hasn't been updated in a long long time and I probably will not be working on this anymore.
However, you should be using from uberpy import Uber.
Hopefully this solves your issue.


Trims search result return by about 75%

Working on https://github.com/ga4gh/dockstore/issues/958

Working on https://github.com/ga4gh/dockstore/issues/958

Can straight up exclude the entire _source from everything except resultsQuery.

Codecov Report

Merging #114 into develop will decrease coverage by 0.08%.
The diff coverage is 33.33%.

@@             Coverage Diff             @@
##           develop     #114      +/-   ##
===========================================
- Coverage    65.15%   65.07%   -0.09%
===========================================
  Files           94       94
  Lines         2520     2531      +11
  Branches       320      320
===========================================
+ Hits          1642     1647       +5
- Misses         707      713       +6
  Partials       171      171

Impacted Files
Coverage Δ

src/app/search/query-builder.service.ts
13.23% <33.33%> (+0.73%)
:arrow_up:

src/app/workflow/launch/workflow-launch.service.ts
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Deprovisioning operations should be creasted as Pending

Description
Changes proposed in this pull request:

Deprovisioning operation must be created as pending

Related issue(s)

/hold

/unhold


Git: Offer to clean workspace when checkout fails due to dirty working tree #59600

Added new errorCode that give the option to the user to discard all changes and pull anyway.
Instead of Open Git Log and Cancel options, there's another option to pull force.
Issue #59600

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: EstevesAndre sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Ups, do I need to do something now?
Or I just need to close pull request!!

Unfortunately this doesn't cover checkout nor suggests to stash the changes, which would be a better option for the regular user. Closing this for now. Thanks anyway! 🙏


[5.3] Remove old failed() implementation from InteractsWithQueue.

I believe the failed() method in InteractsWithQueue should be removed.  After a conversation with @crynobone, it's original intention and lack of exception parameter seems to conflict with the new failed() method implementation in 5.3.
This came about because of this thread, and though it doesn't solve the original issue, this PR would remove some confusion around the new failed() functionality in 5.3.

I'm going to rename the method to fail instead. I think the purpose is to pre-emptively trigger the failed job handling, but yes the names would conflict.

@taylorotwell cool sounds good 👍   Also a bit unrelated, but as for our original issue...
Curious if you have any idea what's going on in this thread?  TL;DR: Sometimes a job is not released back onto the jobs/failed_jobs tables, then PHP dies and we lose the job.


New addition

Description
Hello,
As an active user of the AudioKit framework, I have created a well designed macOS app (user facing), that aims to simplify the learning curve for new developers. And was wondering if this is a good place to let users know about this.
Proposed Solution
Miano is an open-source macOS application designed to empower audio developers with:
Comprehensive Examples: It offers an extensive library of intuitive AudioKit framework examples, showcasing audio synthesis, processing, and manipulation capabilities.
macOS Focus:(( Besides AudioKit, it includes tutorials and examples leveraging macOS-specific features, perfect for macOS audio development.
User-Friendly Interface: The app's user-friendly design caters to developers of all levels, enabling easy exploration and experimentation with AudioKit functionalities.
Open Source: It's fully open source, encouraging collaboration and contributions from the developer community for ongoing improvement and expansion.
Describe Alternatives You've Considered
The AudioKit cookbook is indeed comprehensive and commendable, however, in terms of user interface and aesthetic appeal, it appears to fall somewhat short. Miano, on the other hand, is striving to bridge this gap. Of course, this observation is subjective, and different users may have various preferences.
Additional Context
I've added some screenshots for context. Let me know what you think :smi

First of all, let me commend Milano, it certainly does look really nice. I'll have a closer look at the code and see what we can do about merging the best of both projects. We do want to be just as nice on iOS as we are on macOS which I think is achievable.  Thanks for letting us know about your work. Would you like to be on the AudioKit discord?

@aure Of course, if be happy to join.

In case the discord group is invite only.

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAYZc3gwN28x8oqxHvtwzYyV531A4OCPYBnPTcUHkKOR aayush@mbp

Just  need your email address actually.

or you can email me

Just  need your email address actually.

scour.diopter0z [at] icloud  com


mnemosyne-ruby and sentry-raven are incompatible

The current version of mnemosyne-ruby and sentry-rave in version 3.0.0 are incompatible, probably due to the faraday version jump from 0.* to 1.* Therefore, Sentry does not receive any events.
2.6.0 :001 > Raven.capture do
2.6.0 :002 >       # capture any exceptions which happen during execution of this block
2.6.0 :003 >       1 / 0
2.6.0 :004?>   end
Traceback (most recent call last):
Sending event 015e79abe6da450f949108b16c33d93e to Sentry
        3: from (irb):1
        2: from (irb):3:in `block in irb_binding'
        1: from (irb):3:in `/'
ZeroDivisionError (divided by 0)
2.6.0 :005 > Raven HTTP Transport connecting to [URL]
Unable to record event with remote Sentry server (NoMethodError - undefined method `ancestors' for Faraday::Response::RaiseError:Faraday::RackBuilder::Handler):
/var/www/app/shared/bundle/ruby/2.6.0/gems/faraday-1.0.0/lib/faraday/rack_builder.rb:234:in `is_adapter?'
/var/www/app/shared/bundle/ruby/2.6.0/gems/mnemosyne-ruby-1.9.0/lib/mnemosyne/probes/faraday/base.rb:22:in `block in lock!'
/var/www/app/shared/bundle/ruby/2.6.0/gems/mnemosyne-ruby-1.9.0/lib/mnemosyne/probes/faraday/base.rb:22:in `find_index'
/var/www/app/shared/bundle/ruby/2.6.0/gems/mnemosyne-ruby-1.9.0/lib/mnemosyne/probes/faraday/base.rb:22:in `lock!'
/var/www/app/shared/bundle/ruby/2.6.0/gems/faraday-1.0.0/lib/faraday/rack_builder.rb:165:in `app'
/var/www/app/shared/bundle/ruby/2.6.0/gems/faraday-1.0.0/lib/faraday/rack_builder.rb:153:in `build_response'
/var/www/app/shared/bundle/ruby/2.6.0/gems/faraday-1.0.0/lib/faraday/connection.rb:492:in `run_request'
/var/www/app/shared/bundle/ruby/2.6.0/gems/faraday-1.0.0/lib/faraday/connection.rb:279:in `post'
/var/www/app/shared/bundle/ruby/2.6.0/gems/sentry-raven-3.0.0/lib/raven/transports/http.rb:24:in `send_event'
/var/www/app/shared/bundle/ruby/2.6.0/gems/sentry-raven-3.0.0/lib/raven/client.rb:44:in `send_event'
/var/www/app/shared/bundle/ruby/2.6.0/gems/sentry-raven-3.0.0/lib/raven/instance.rb:81:in `send_event'
Failed to submit event: <no message value>

Please test with 1.10.0.beta1.

Thanks for your release. It's working again as expected. ;)

Thanks. Release final 1.10.0 just now.


Add note about VitePress to README.md

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Provide a description in this PR that addresses what the PR is solving. If this PR is going to solve an existing issue, please reference the issue (e.g. close #123).

What is the purpose of this pull request?

[ ] Bug fix
[ ] New feature
[x] Documentation update
[ ] Other

Description

VitePress is so much better already, in so many respects. We recently migrated our highly customised site with ~370 pages and have not regretted it since. Given the slow development speed of VuePress, it feels like the responsible thing to do to make people aware of VitePress, so that they don't end up being stuck here.
I would understand it if you don't want to use VuePress as a vehicle to advertise the competing VitePress project, but IMHO the benefits of VitePress outweigh any concerns regarding fairness—especially because VitePress is more of an upgrade and less or a competitor to VuePress.

Thanks, but there is already a tip in the v1 repo.


NPC won't look at player until player moves

When you join any NPC next to you won't look at you until you move, which looks jerky if you stand still for a few seconds waiting for the world to load.
I'd offer to make a PR but the easiest fix would involve listening to the ShowNpcEvent.Post, and that's bad practice(, right?).
Another easy way to fix I didn't find
Anyways, looking at the CommonNpc file.

Yea that's quite unfortunate - I noticed that a few times before. I would not listen to the event in the lib directly, maybe we can offer a method in CommonNpc to simply a position sync for the user?

Already thought of that but it's not that easy because there is no way to get the distance to the player for the imitateDistance check (in CommonNpc). There is simply no (abstract) method to get the position of the player from the npc-lib-common module

I just took a closer look into the code: there is already an event listener that observes the exact event you wanted to intercept on 1.19.2 and lower to remove the npc from the tablist. So adding an option to make the behaviour opt-out (I guess that a better default than opt-in) to add a listener that rotates the npc into the player direction seems good to me.
Let me know if you want to make a PR for that, otherwise I will take a look to implement that later 😄

#110


[question] the page rendering on server side and client side

When try this example I show the page rendering twice on server side and rendering again on client side, Why this behavior occurs ?

Hi @Mahmoud-hassan87,
I have the same issue and looking for a solution, even though I don't think this seed is responsible for the issue, must be a Universal issue instead. They did have an issue for this particular bug but they closed it.

@Gbuomprisco can you please share the issue url here? Maybe I can catch something from the information there.

Your sample have this issue

@fulls1z3 What I experience is exactly what is described in this issue https://github.com/angular/universal-starter/issues/139, and also others. Thing is these might be outdated now as they were using last year's code.

@Gbuomprisco the info seems outdated, but can be useful. I'll dig into this a little this evening and see what can I do.
@Mahmoud-hassan87 thanks for the enlightment 👍

Thanks @fulls1z3, I'll try as well

@Mahmoud-hassan87  Not sure but you might be seeing this issue: https://github.com/angular/angular/issues/15716. Essentially the issue is that the server-rendered CSS is removed from the DOM before the client CSS is applied, causing a flicker regardless of if you transfer the state perfectly or not.
Apparently a fix should be landing in the next angular releases, i.e. 4.1.3 and 4.2.0-beta.2. Where the renderer waits for the client to finish before removing the server CSS.

Thanks @Koslun

@Koslun thank you so much for this information, now I realized the reason that I subscribed to the updates of https://github.com/angular/angular/issues/15716. Seems like we'll get it working soon, and I'm keeping this issue open in order to do not leave it unresolved.

Something is off here..
Just cloned the repo again, then I just added a console.log('test'); inside ngOnInit in app.component.ts, when I build the project for universal I get the log on nodejs and the browser

Is there any update on flickering issue??

@Skillnter we're working on this issue, as well as other enhancements to this seed project - so soon I'll be able to share some updates.

Is there any update on flickering issue??


No license file

Not having a license file prevents me from considering  / analyzing the source code for potential contribution

Hello @KnicKnic !
Added  a license by #4


Add hash variant to ProofObject

With winterfell 5.0, the security level is defined per type. We need to extend this as arguments of the ProofObject so we can replicate the used properties down the stack.
Originally posted by @bobbinth in https://github.com/0xPolygonMiden/miden-vm/pull/708#discussion_r1113005692

Closed by #715 and #716.


Async only API?

Sync, async API

Any update on this? Should we keep this as-is?

Not yet. This is required for GA, so I'm thinking on leaving it here and latter revisit

Sync methods have been implemented.

Sync methods have been implemented.


kuma sqlite Database Issues with k8s

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
After removing an unused monitoring from the Kuma UI, the Kubernetes Kuma pod is not running normally after a forced restart.
Currently, the pod is not running normally and keeps crashing off due to probe failure.
If I remove the EBS Block Storage I was using, it works fine, but I want to use the Database I was using.
📝 Error Message(s) or Log
Kuma Pod Log
==> Performing startup jobs and maintenance tasks
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Your Node.js version: 16
2023-12-29T02:48:24Z [SERVER] INFO: Welcome to Uptime Kuma
2023-12-29T02:48:24Z [SERVER] INFO: Node Env: production
2023-12-29T02:48:24Z [SERVER] INFO: Importing Node libraries
2023-12-29T02:48:24Z [SERVER] INFO: Importing 3rd-party libraries
2023-12-29T02:48:25Z [SERVER] INFO: Creating express and socket.io instance
2023-12-29T02:48:25Z [SERVER] INFO: Server Type: HTTP
2023-12-29T02:48:25Z [SERVER] INFO: Importing this project modules
2023-12-29T02:48:25Z [NOTIFICATION] INFO: Prepare Notification Providers
2023-12-29T02:48:25Z [SERVER] INFO: Version: 1.21.2
2023-12-29T02:48:25Z [DB] INFO: Data Dir: ./data/
2023-12-29T02:48:25Z [SERVER] INFO: Connecting to the Database
2023-12-29T02:48:25Z [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-12-29T02:48:25Z [DB] INFO: SQLite Version: 3.41.1
2023-12-29T02:48:25Z [SERVER] INFO: Connected
2023-12-29T02:48:25Z [DB] INFO: Your database version: 10
2023-12-29T02:48:25Z [DB] INFO: Latest database version: 10
2023-12-29T02:48:25Z [DB] INFO: Database patch not needed
2023-12-29T02:48:25Z [DB] INFO: Database Patch 2.0 Process
2023-12-29T02:49:08Z [SERVER] INFO: Shutdown requested
2023-12-29T02:49:08Z [SERVER] INFO: Called signal: SIGTERM
2023-12-29T02:49:08Z [SERVER] INFO: Stopping all monitors
Trace: Error [ERR_SERVER_NOT_RUNNING]: Server is not running.
    at new NodeError (node:internal/errors:387:5)
    at Server.close (node:net:1804:12)
    at Object.onceWrapper (node:events:627:28)
    at Server.emit (node:events:525:35)
    at emitCloseNT (node:net:1857:8)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ERR_SERVER_NOT_RUNNING'
}
    at process.<anonymous> (/app/server/server.js:1804:13)
    at process.emit (node:events:513:28)
    at emit (node:internal/process/promises:140:20)
    at processPromiseRejections (node:internal/process/promises:274:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
2023-12-29T02:49:10Z [DB] INFO: Closing the database

🐻 Uptime-Kuma Version
1.21.2-debian
💻 Operating System and Arch
AmazonLinux2
🌐 Browser
Chorme(120.0.6099.129)
🐋 Docker Version
Kubernetes 1.25/ K8S / AWS EKS
🟩 NodeJS Version
No response

I attached the sqllite pvc to another pod and checked the error.log, I saw "SQLITE_BUSY".
I'm not sure what to fix here.
}
[2023-12-28 03:14:07] [Error: insert into `heartbeat` (`down_count`, `duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (0, 30, false, 73, '200 - OK', 41, 1, '2023-12-27 18:14:02.318') - SQLITE_BUSY: database is locked] {
  errno: 5,
  code: 'SQLITE_BUSY'
}
[2023-12-29 03:14:03] [Error: insert into `heartbeat` (`down_count`, `duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (0, 30, false, 49, '200 - OK', 31, 1, '2023-12-28 18:14:01.207') - SQLITE_BUSY: database is locked] {
  errno: 5,
  code: 'SQLITE_BUSY'
}

EBS Block Storage

No chance. It's a network drive.
As the warning in the README:

Warning
File Systems like NFS (Network File System) are NOT supported. Please map to a local directory or volume.

Related issue:
https://github.com/louislam/uptime-kuma/issues/1757

HI, @louislam
I was previously running uptime-kuma on top of AWS EKS using EBS (block storage) as a PVC.
I removed some unused monitoring and when the pod was restarted, it didn't work properly.
As far as I can tell, I wasn't using NFS, and it seems to have worked fine before, so could it be an NFS issue?
I think it's a db lock related error in sqlite, but I'm not sure how to fix it.
kubernetes settings for uptime-kuma yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: uptime-kuma
  namespace: kuma
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: uptime-kuma-mgmt-1.25
      app.kubernetes.io/name: uptime-kuma
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: uptime-kuma-mgmt-1.25
        app.kubernetes.io/name: uptime-kuma
    spec:
      containers:
        - env:
            - name: UPTIME_KUMA_PORT
              value: '3001'
          image: 'louislam/uptime-kuma:1.21.2-debian'
          imagePullPolicy: IfNotPresent
          livenessProbe:
            exec:
              command:
                - extra/healthcheck
            initialDelaySeconds: 15
            timeoutSeconds: 2
          name: uptime-kuma
          ports:
            - containerPort: 3001
              name: http
              protocol: TCP
          readinessProbe:
            httpGet:
              path: /
              port: 3001
              scheme: HTTP
            initialDelaySeconds: 5
          resources: {}
          securityContext:
            privileged: true
            runAsUser: 0
          volumeMounts:
            - mountPath: /app/data
              name: storage
      securityContext:
        fsGroup: 0
      serviceAccountName: default
      volumes:
        - name: storage
          persistentVolumeClaim:
            claimName: uptime-kuma-pvc

## pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: uptime-kuma-pvc
  namespace: kuma
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 30Gi
  storageClassName: ebs-sc-retain

EBS Block Storage

No chance. It's a network drive.
As the warning in the README:

Warning
File Systems like NFS (Network File System) are NOT supported. Please map to a local directory or volume.

Related issue: #1757

HI, @louislam
I was previously running uptime-kuma on top of AWS EKS using EBS (block storage) as a PVC.
I removed some unused monitoring and when the pod was restarted, it didn't work properly.
As far as I can tell, I wasn't using NFS, and it seems to have worked fine before, so could it be an NFS issue?
I think it's a db lock related error in sqlite, but I'm not sure how to fix it.
kubernetes settings for uptime-kuma yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: uptime-kuma
  namespace: kuma
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: uptime-kuma-mgmt-1.25
      app.kubernetes.io/name: uptime-kuma
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: uptime-kuma-mgmt-1.25
        app.kubernetes.io/name: uptime-kuma
    spec:
      containers:
        - env:
            - name: UPTIME_KUMA_PORT
              value: '3001'
          image: 'louislam/uptime-kuma:1.21.2-debian'
          imagePullPolicy: IfNotPresent
          livenessProbe:
            exec:
              command:
                - extra/healthcheck
            initialDelaySeconds: 15
            timeoutSeconds: 2
          name: uptime-kuma
          ports:
            - containerPort: 3001
              name: http
              protocol: TCP
          readinessProbe:
            httpGet:
              path: /
              port: 3001
              scheme: HTTP
            initialDelaySeconds: 5
          resources: {}
          securityContext:
            privileged: true
            runAsUser: 0
          volumeMounts:
            - mountPath: /app/data
              name: storage
      securityContext:
        fsGroup: 0
      serviceAccountName: default
      volumes:
        - name: storage
          persistentVolumeClaim:
            claimName: uptime-kuma-pvc

## pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: uptime-kuma-pvc
  namespace: kuma
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 30Gi
  storageClassName: ebs-sc-retain

This issue has been resolved.
Copying the kuma.db file and restoring it again did not solve the problem, but it was solved through the sqlite3 command.
sqlite3 /app/data/kuma.db ".dump" | sqlite3 /app/data/new.db
sqlite3 /app/data/new.db "PRAGMA integrity_check"
rm /app/data/kuma.db
mv /app/data/new.db /app/data/kuma.db

Thanks @95jinhong, that worked brilliantly (my issue was a corrupt database due to unsafe shutdown).

Hi,
I got this same error using ECS Fargate and a shared EFS volume. This can happen when there is a new deployment and multiple Kuma instances are accessing the database at the same time. You must make sure that only one instance has access to the EFS volume at the same time.
With Fargate you can easily do this by using the following percentages on your task definition:
deployment_minimum_healthy_percent = 0
deployment_maximum_percent = 100

This will make sure that the first Kuma container gets shut down fully, before it starts a new one.
MongoDB needs similar settings if you run it through Docker on Fargate, because only one MongoDB instance can have access to the database directory.
PS - Maybe some locking table in SQLite could be used to prevent it


Create temperaturecontroller-2.json

First iteration, invalid file location model DTMI value was different than the file name.
Second iteration, bad dependent DTMI/resolution could not succeed with invalid model.
Subsequent iteration, branch out of date - force a branch update.


Add zero orientation support ignoring EXIF

Problem:
As some images have an EXIF orientation, I had the problem with rotating an image to its default orientation without EXIF. I just needed the EXIF orientation data to be ignored/deleted.
Solution:
Glide supports zero orientation to rotate an image in the same orientation as before but ignoring the EXIF orientation.
This PR adds the possibility to rotate an image by zero, deleting EXIF orientation.

Thanks!


lms7suite - no focus after connection settings closed

After the connections dialog is opened, and then closed. The menu items are all greyed out and the window cant be closed. This does not happen with the fft dialog for example.

Missing EndModal() calls: https://github.com/myriadrf/LimeSuite/commit/ac23d74fdd983ef13a17d0ccb0e542962ea99035
There may be others, so I am not closing this yet.


Why can not reproduce the experiment in 32GB memory?

In paper, you said "All our experiments are conducted under Ubuntu Linux 14.04 with 10-core CPU and 20GB memory." But now I run the code with 32GB memory, the same code and the sam dataset(581012 samples), it came out as below. I know that it is sklearn's memory error, but how can you run such a big dataset in 20GB memory?
Traceback (most recent call last):
File "sgd_spectral.py", line 280, in
affinity_matrix = rbf_kernel(train_data,gamma = gamma_value)
File "/usr/local/anaconda3/lib/python3.6/site-packages/sklearn/metrics/pairwise.py", line 842, in rbf_kernel
K = euclidean_distances(X, Y, squared=True)
File "/usr/local/anaconda3/lib/python3.6/site-packages/sklearn/metrics/pairwise.py", line 246, in euclidean_distances
distances = safe_sparse_dot(X, Y.T, dense_output=True)
File "/usr/local/anaconda3/lib/python3.6/site-packages/sklearn/utils/extmath.py", line 140, in safe_sparse_dot
return np.dot(a, b)
MemoryError

Hi, thanks for your interests in our work. For experimental study in the paper, we modified the original rbf_kernel function with CPython. We don't output the whole pairwise kernel matrix, instead, we only store the upper triangular part, since the kernel matrix is symmetric. In case the memory is still out of use, we conduct memory map in Python to save the memory cost while slightly sacrifice computational speed. This code is used for demonstrating the flow of the proposed algorithm without touching implementation details. For databases of large sizes, like shuttle, mnist and covtype, we observed the same issue as you pointed out when we directly ran this demo code on RAM-limited platforms. It is recommended to run this demo code with larger memory, e.g. 120GiB RAM, to reproduce the NMI scores.


Fix disabling insecure registry in create clusters script

CONFIGURE_INSECURE_REGISTRY_CLUSTER="${CONFIGURE_INSECURE_REGISTRY_CLUSTER:-y}" will substitute 'y' if the value is unset or null, which prevents disabling this configuration step. Removing the colon ensures that 'y' is substituted only if the value is unset.

LGTM

/lgtm
I found DOCKER_PUSH also has the same issue. I will handle it.


Makes code-sign optional

Identify the Bug
Fixes https://github.com/atom-ide-community/atom/issues/8
Description of the Change
Adds a SHOULD_SIGN env variable which allows skipping code signing when you are on the release branch. This allows building Atom without purchasing a code signing certificate. It is meant to facilitate the process of testing atom in the forks (particularly atom-community/atom)
Alternate Designs
Possible Drawbacks
Requires setting SHOULD_SIGN=true as an environment variable inside Azure.
Verification Process
Release Notes
N/A; this is a developer-facing change, not an end-user facing change.

A smaller change with similar effect would be to skip notarization when the required env vars are blank (just as code signing is already skipped when the env vars are blank).
Just add this snippet at the beginning of the main function of script/lib/notarize-on-mac.js:
  if (
    !process.env.ATOM_MAC_CODE_SIGNING_CERT_DOWNLOAD_URL &&
    !process.env.ATOM_MAC_CODE_SIGNING_CERT_PATH
  ) {
    console.log(
      'Skipping notarization because the ATOM_MAC_CODE_SIGNING_CERT_DOWNLOAD_URL environment variable is not defined'
        .gray
    );
    return;
  }

The snippet is copied from script/lib/code-sign-on-mac.js: https://github.com/atom/atom/blob/master/script/lib/code-sign-on-mac.js#L16-L25 (with a tweaked string of what is skipped, notarization instead of code signing.)
This makes natural sense, because per Apple documentation, notarization is for after you successfully sign your code.
If code signing is skipped, notarization should necessarily be skipped or it won't work anyhow.

One downside: in my testing, it requires setting all four of these vars as blank in Azure DevOps UI if you want to skip code signing/notarization on both Windows and macOS:

ATOM_MAC_CODE_SIGNING_CERT_DOWNLOAD_URL
ATOM_MAC_CODE_SIGNING_CERT_PATH
ATOM_WIN_CODE_SIGNING_CERT_DOWNLOAD_URL
ATOM_WIN_CODE_SIGNING_CERT_PATH

@aminya I don't know your thoughts on this, but last I remember we just found a way to do this kind of skipping automatically, no new env vars needed.
https://github.com/atom-ide-community/atom/pull/99/files
I think we should be able to do that for this PR (skipping code signing) as well.
@aminya @sadick254 if you don't mind I'm going to code up an implementation with that design.

Looks great.
I think we could set the environment variable on the CI yaml files. Like we do here
https://github.com/atom/atom/blob/d9d4e3756307dca5999b3099cf797b3859d0cb8d/script/vsts/platforms/macos.yml#L53-L63

@sadick254 You should add the variable in the Azure UI.

I don't know your thoughts on this, but last I remember we just found a way to do this kind of skipping automatically, no new env vars needed.

No, this variable acts as a kill switch. It is supposed to be independent of the provided code sign variables.

To clarify: I mean to propose an alternate solution. (The one we found for the API keys.)
Apologize for bringing it up last minute, but we only discovered/mastered this technique a few days ago.

@aminya Any reason you prefer having it added in the Azure UI?

@aminya Any reason you prefer having it added using the Azure UI?

The point of this variable is to be like an environment variable you pass to the program, not hardcoding it in the code. The reason we made this was to allow others to skip this by adding that variable to Azure UI.
If you hardcode this here, other people need to change it, which brings conflicts.

It would be inconvenient for forks to have to make a commit changing this variable.
That means they have to test on one branch (with changed variable) so that their CI works. Then rebase to another branch without the changed variable, to avoid sending the changed variable as part of their PR.

@aminya @sadick254 by the way the alternative I mentioned is working:

successfully skips code signing when vars not set: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=608&view=logs&j=e2cf4b02-5697-54ad-cf7c-fc2a840d53af&t=b808d44d-d1c2-5399-c2e1-8c4b890e97af&l=4955
Doesn't skip when credentials/URL vars set: https://dev.azure.com/DeeDeeG/b/_build/results?buildId=609&view=logs&j=e2cf4b02-5697-54ad-cf7c-fc2a840d53af&t=b808d44d-d1c2-5399-c2e1-8c4b890e97af&l=4955 (CI failure is expected here because I used fake/placeholder credentials.)

@DeeDeeG Thank you for the alternative implementation. Your solution is great, the only downside is it uses a workaround for the unset env vars.
I prefer us being more explicit by setting the SHOULD_SIGN env var.

Fair enough, works for me. 👍 Thanks for the mini-review, haha.


Bump dependency on signer-service

Closes #230.

I'm quite positive that it works. For example, the portal and also our other services are able to sign and submit extrinsics again without needing any custom changes (besides bumping the dependencies). Only subxt in Spacewalk required custom changes.


Made some updates on manifest.json as well as changin screenshot.png

Made some updates on theme

@AlphaLawless


Implement attributes starts wit E

This repository needs a good amount of ingestion of various css attributes. The framework is ready now and what is pending is to add all the leftover CSS attributes.
The target of this issue is to add all attributes start with E.

#11 created


Split World file

Split the world file into multiple smaller files for clarity and organization.
world/mod.rs re-exports the sub-modules to minimize path changes.

Why is the SectionSnapshot still called 'SectionSnapshot' if the Section was renamed to 'ChunkSection'

Also: this function is redundant and can be replaced with a simple cast of Ordering, at least afaik:      fn cmp(first: i32, second: i32) -> i32 {

Also: this function is redundant and can be replaced with a simple cast of Ordering, at least afaik: fn cmp(first: i32, second: i32) -> i32 {

The main intention of this PR is to split up the file, not alter functions inside the file. Alterations can be done later on.

Do you think this is ready to be merged?

I have no further work to do on this PR unless you want something to be changed.

After fixing the CI, this is ready to merge


latest vs v2 problem

Hello,
I've pulled both images "latest" and "v2" from docker hub today and when I run the "latest" image, no repositories show up on the page, however when I run "v2" the repositories show up.
Here's how I'm running them.
latest:
docker run --detach --env=ENV_DOCKER_REGISTRY_HOST=<IP_ADDRESS> --env=ENV_DOCKER_REGISTRY_PORT=5000 --publish=80:80 --name=kwk-frontend-ui --restart always konradkleine/docker-registry-frontend:latest
v2:
docker run --detach --env=ENV_DOCKER_REGISTRY_HOST=<IP_ADDRESS> --env=ENV_DOCKER_REGISTRY_PORT=5000 --publish=80:80 --name=kwk-frontend-ui-2 --restart always konradkleine/docker-registry-frontend:v2
And here's how the pages look like:
latest:

v2:

Another thing, in v2 sometimes when I click on "Browse Repositories" on the main page it goes to "http://localhost/repositories/20" (searches for 20; which shows nothing obviously).
Thanks,
Fadi

@farahfa  Please see example setup folder in github project for a working setup.

Hi guys,
I have the exact same pb. v2 installed and we see repos but can't suppress anything even with "BROWSE_ONLY=false" in our docker-compose.
We try the "lastest" version and we see Nothing in the repo.
I have check your "example setup", but it's seem do be a merge of v1/v2 setup? As an example your docker config.yml is for a v1 ? The docker-compose for a v2. Some configuration seems directly linked to the v1 version of the registry?
Nothing for a "latest" version.
Our configuration is really simple, no SSL at all. We just configure it to expose 8081:80 on the frontend, linked it to our registry:5000 and that's all :/
On the same host.
Our docker-compose :
docker-registry:
image: registry:2.1.1
ports:
- "<IP_ADDRESS>:5000:5000"
volumes:
- /forge/registry/data:/var/lib/registry
- /etc/localtime:/etc/localtime:ro
container_name: docker-registry
docker-registry-frontend:
image: docker.io/konradkleine/docker-registry-frontend:latest
image: docker.io/konradkleine/docker-registry-frontend:v2
ports:
- "8081:80"
environment:
- ENV_DOCKER_REGISTRY_HOST=docker-registry
- ENV_DOCKER_REGISTRY_PORT=5000
- ENV_MODE_BROWSE_ONLY=false
container_name: docker-registry-frontend
hostname: frontend
links:
- docker-registry:docker-registry
/etc/sysconfig/docker cut :
If you have a registry secured with https but do not have proper certs
distributed, you can tell docker to not look for full authorization by
adding the registry to the INSECURE_REGISTRY line and uncommenting it.
INSECURE_REGISTRY='--insecure-registry dr.forge-siterc'
Sorry for my English if it's not clear enough..
tx
Regards
RCH

I have same problem!


BUG: can't get local addresses in single node

Sealos Version
5.0.0
How to reproduce the bug?
2024-10-29T22:13:45 debug sync workdir: /root/.sealos/default
2024-10-29T22:13:45 debug copy files src /root/.sealos/default to dst /root/.sealos/default on <IP_ADDRESS>:22 locally
Error: could not get local addresses: route ip+net: no such network interface
func New(inner ssh.Interface) (Interface, error) {
	addr, err := net.InterfaceAddrs()
	if err != nil {
		return nil, fmt.Errorf("could not get local addresses: %v", err)
	}
	return &wrap{
		inner:          inner,
		localAddresses: sets.Set[string](netutil.AddressSet(isValid, addr)),
	}, nil
}

What is the expected behavior?
No response
What do you see instead?
No response
Operating environment
- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:

Additional information
No response

@cuisongliu  it might related to this issue? https://github.com/golang/go/issues/51934

@cuisongliu  it might related to this issue? https://github.com/golang/go/issues/51934

I think it should be. I have a problem in the process of installing the helm chart. At this time, I am creating a network card similar to flannel.

/reopen


Showheroes update

Type of change

[x] Updated bidder adapter  <!--  IMPORTANT: (1) consider whether you need to upgrade your bidder parameter documentation in

Description of change
Update the showheroes-bs bidder adapter.
PR has following updates:

remove legacy code that is not supported anymore
replace the old endpoint with prebid-sh with new openrtb2/auction
use ortbConverter to construct bid request
in case of outstream ads, provide the renderer related parameters in the response (old static renderer is not working anymore)
by using openRTB, automatically add support for: fpd, floor module, eids, etc.

Other information

@FilipStamenkovic the file showheroes-bsBidAdapter.md should be reviewed and updated, because there are two sets of test parameters

Official PR opened: https://github.com/prebid/Prebid.js/pull/12283


fixes for latest keripy development branch

Updates to support renaming in development keripy.

Merging this will require moving to latest keripy:development, currently we point to 1.1.0


Added S3 support using JetS3t.

I basically did (or attempted) to do what you outlined in the bottom of your future work. I understand this pull request is all over the place in formatting and everything, but I did manage to test it and it appears to be working correctly, but obviously this is a long way off from being anything mergable. I'd like to get the ball rolling on what you guys would like to do going forward with this to test and refactor it to stay within your design ideas.

@hntd187 Thanks, This is great!
I will review the code. Just a short question, what was the major refactoring to support S3? My initial impression was that ObjectStoreFileSystem and IStoreClient doesn't need much refactoring to support other object stores

@gilv I don't think I changed anything in those classes at all, I think the only thing I updated was some of the documentation because the check-style was complaining about some of the documentation strings and I wanted to fix the warnings. I'd say overall the interface is good given an object store functions like that in the first place, but I also refrained from adding exceptions or having anything like that bubble up out of concern on breaking your contracts so I left them alone for now.
Overall though it was pretty straight forward, but there were a few things which I'm not sure if I did correctly.

My configuration path, I made it fs.amazon.service.s3.**** but I'm not stuck on that and it can be made to be more inline with whatever, I wasn't sure if you wanted to stay with swift2d or if you were okay with object paths being in the s3 format.

My actual setup of S3 Paths relative to Hadoop, they are kind of redundant and some of the system checks in place here require you to do unnecessary things, like the initial bucket URI must be s3://bucket.bucket even though this isn't necessary to s3 working, but stocator wants that format to extract the service. I didn't want to mess too much with your validation or object contracts without first submitting this as I didn't want to break some idea that you had in mind to keep this working.

The underlying JetSet library whether you are reading or writing from S3 only uses input streams for communication, so some of the code is seemingly backwards because of it. Like downloading from S3 is mostly reading from an InputStream, but the uploading is the data is written to an internal OutputSteam in the class, but then when the handle is closed it will actually write that stream to the input stream necessary to upload to S3, this gets around the need to write a temporary file and check it's length because you just check the length of that stream when it's converted to a byte array, but this probably won't work well for very large files, so we'll have to test that.

@hntd187 Can you please add comment with this text ( with new pull requests it's added automatic ): https://github.com/SparkTC/stocator/blob/master/.github/PULL_REQUEST_TEMPLATE ?
Please also add line  at the end
Signed-off-by: Your-Name

Where do you want this added? @gilv

@hntd187 just copy-paste the text into comment. see this one for example
https://github.com/SparkTC/stocator/pull/7
I am in a process of the integration of many changes to the code. The new addition will cover all known fault tolerance issues with Spark. New code will support run time exception coverage in Spark, also support for speculative mode, including coverage  of https://issues.apache.org/jira/browse/SPARK-10063 and many other failure scenarios.
After code is merged, please rebase your pull request, You will need to add few small additions to your implementation to support fault tolerance mode.
After that -  i will be glad to review and merge your code. I think it's great addition.

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Signed-off-by: Stephen Carman<EMAIL_ADDRESS>

@gilv Let me know when you are ready and I'll make my fixes for you.

@hntd187 I did many modifications to the code, in order to support various Spark failure scenarios. The new code covers speculate mode, run time exceptions in Spark master, etc. The new code is stable now.
While most of the new logic was added to ObjectStoreFileSystem, there is some new logic in the Swift driver. In particular "list " method has changed and include new coverage.
I assume you will need to implement the same logic for "list". Swift return list of objects, sorted by name. I think the same is true for S3. If yes, you need to adapt list logic from Swift driver to your S3 driver
Can you please refactor your code?

@gilv Yup, give me some time and I can refactor for it. Hopefully it's not a lot of stuff, right?

@hntd187 No, it's not a lot of stuff. Most of the work was done in ObjectStoreFileSystem which is the same class for Swift and S3 implementations.
I think, only "list" should be modified in the S3 driver. May be some other minor changes. Also minor interface modifications.


Rename humg.txt to student.humg.txt

@phuqn10x lib/domains/vn/edu/student.humg.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


support Sequence

Feature Request
Sequence should be supported, I guess list and tuple should work, anything else?

Useful when you want a Tuple but don't yet know it's length.

Useful when you want a Tuple but don't yet know it's length.
Isn't a Sequence type always has __len__ and __getitem__ methods, so length should be known.
Could you give an example?

I guess list and tuple should work, anything else?
range maybe?

I guess the Tuple case we can support with Tuple[int, ...] etc.
Point of Sequence would just be to allow either List or Tuple.