Initial installation - missing/relocated items

I recently installed the workstation on top of Ubuntu 14 LTS, and after the installation was completed (I used the bootstrap instal), I noticed the case, and mounting points folders were not present on the desktop.  I also noticed the cheat sheets were not present on the desktop.  I noticed the missing items, because approximately three months ago, I installed the workstation on the same Ubuntu build, and there were no missing items.  It would appear something changed with respect to the workstation installation process.  Ultimately, I did find the cases folder by changing directory to root, I did not find the cheat sheets, though.
I just want to make sure I installed correctly, since I am just starting to use SIFT.  Between this issue, and the other issue I posted - mounting a dd file and having to use a different syntax than the one listed in the cheat sheet, I figured I must've done something wrong with the install.

 If you did not run it with -iys then you will not get the PDFs, the background, folders etc ...

I used the command combination associated with installing everything (theme and PDFs).  Interestingly, I ran the same installation steps a few months back, and nothing was missing.  However, I then ran into an issue involving mounting dd files (see my other post in the issue section).  As a result, I attempted to reinstall SIFT in case there was a bug with the original instal.  Would it help if I posted my instal log?
Thanks.
Luis

On Jul 12, 2015, at 11:55 AM, Erik Kristensen<EMAIL_ADDRESS>wrote:
There are a few different ways to run the bootstrap command ... how did you run it? If you did not run it with -iys then you will not get the PDFs, the background, folders etc ...
—
Reply to this email directly or view it on GitHub.

@Lou511 have you had a chance to re-run the script?

I did re run the script.  And the same thing occurred - couldn't execute the terminal commands I referenced in my original post.  Also, the folders and cheat sheets didn't download to the desktop either.  I did find the "cases" folder by cd /, and then doing an ls command.  Somehow, the folder made it into that directory instead of the desktop.
Out of curiosity, I loaded the VMware appliance file to see if I'd get the same issues.  The result - i have been able to mount images and I have the folders on the desktop.  I am not sure what the difference is between running the script and using the VMware file.  I thought I'd get identical installs, so to speak.
Any suggestions or insight are welcomed.  Thank you for keeping your eye on my issue.
Thanks,
Luis

On Aug 9, 2015, at 11:47 AM, Erik Kristensen<EMAIL_ADDRESS>wrote:
@Lou511 have you had a chance to re-run the script?
—
Reply to this email directly or view it on GitHub.

You should get identical installs. There should be a sift-install.log available if you would like to gist that and post the link I'll take a look.

Erik, please let me know how I can post a "link" to my install log.  I'm sorry I do not understand how to do so.  I can't paste the log into the comment box, since it's too long.  Please let me know what to do next to make the log available to you.

paste it into https://gist.github.com and then paste the link here.

I hope this works:

Respectfully,
New guy

Oops, maybe this will work.  Sorry.
https://gist.github.com/0695a3fb17ba5c62da70.git

What is the exact command you are running?
It also seems to be failing to pull the sift-files.
Are you giving me the entire log file? It seems to just stop after sift-files.

I doubled checked the install log.  I copied and pasted the entire log as is.  The script that I ran to install SIFT was the combination that gets everything (pdfs, theme, etc).  I only encountered this issue when I ran the script.  There are no problems running the VMware appliance file.  Just out of curiosity, I'm going to build another workstation using the same script I've tried in past installs.  Thanks again for all of your help.

There is a bug https://github.com/sans-dfir/sift/issues/76 that is causing your problems. Closing this out in favor of the other issue, once that is closed, the issue should be resolved.


TrackObjectGrabAttach dropping objects early

Environment

Source of VRTK (master-branch, through git clone)
Version of VRTK (revision e16de5a)
Version of Unity3D (e.g. Unity 2017.2.0f3)
Hardware used (HTC Vive)
SDK used (SteamVR, also tested with NewtonVR's SteamVR camera rig)

Steps to reproduce

Open example project 021_Controller_GrabbingObjectsWithJoints
Select ExampleWorldObjects > TrackGrab_Cube (the green cube of the three)
Scroll the inspector to find Track Object Grab Attach options and set Velocity Limit to anything other than Infinity (I used 1, but this happens with any value). This affects Angular Velocity Limit aswell but not as demonstratibly.
Enter VR and attempt to move the green TrackGrab_Cube.

Expected behavior
The cube's movement speed should be limited and if you set the Velocity Limit to something like 1 or less, it should be visibly slowly following the controller. Otherwise the cube should follow the controller as previously to the changes to the example, except it's velocity should be limited.
Current behavior
The cube is difficult to pick up as it will stop following the controller if the controller moves even slightly too fast for the cube, but it won't even detach from the controller properly.
Example gif:

PR with fix: #1562

So what if you have velocity limit set to infinity and in your PR you're using infinity as the max delta difference?

I've used it a bit and it doesn't seem affected. However I'd like to ask what does Infinity actually do to the variable? Does it just set it to Float.MaxValue automatically, it needs to set it as a float value or it would cause a type exception. Whatever Unity sets for it though ends up in the maxDeltaDifference aswell.
The PR does nothing else than make the script consistent with itself. The only variable changed is a local variable in a function so it shouldn't interfere with anything outside the script, and whatever ends up as velocityLimit ends up as maxDeltaDifference aswell.

infinity is just a Unity keyword that gets replaced to Float.maxValue

New PR https://github.com/thestonefox/VRTK/pull/1600


Bump podman to v4.9.5

Bump podman to the latest available v4 release.
This shouldn't have breaking changes compared to the v4.2.1 that is bundled in this package up until now.

cc. @stapelberg

Manually tested:
[~] $ ssh<EMAIL_ADDRESS>              __
 .-----.-----|  |--.----.---.-.-----.--.--.
 |  _  |  _  |    <|   _|  _  |-- __|  |  |
 |___  |_____|__|__|__| |___._|_____|___  |
 |_____|  host:  "gokrazy-dashboard" |_____|
          model: Raspberry Pi 4 Model B Rev 1.2
          build: 2024-08-06T14:50:13+02:00

/tmp/breakglass3303943342 # podman version
Client:       Podman Engine
Version:      4.9.5
API Version:  4.9.5
Go Version:   go1.20.14
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/arm64

/tmp/breakglass3303943342 # podman ps
CONTAINER ID  IMAGE                                                COMMAND               CREATED         STATUS         PORTS       NAMES
8e8bbff8b4b5  quay.io/xxxxxxx  /usr/bin/chromium...  12 minutes ago  Up 12 minutes              gokrazy-kiosk

Merged as commit 390ca44d33dac3584f12d648d187a8c77ddb85ea, thank you!


Creating a directory for categorywise cpp code questions.[FEATURE]

Detailed description
Hello. I was suggesting that this repository can have a directory where we can include CPP codes which will cover logic building concepts problems for using CPP. Like problems on numbers, strings, arrays, integers, pattern printing etc.
Context
I have around 200-250 questions solved covering the questions I have mentioned above. I was willing to contribute my code.
Possible implementation
We can have a separate directory for this issue and inside we can have directories for different categories of problems.
Additional information
No response

do you mean like a leet code directory? or just general algorithms? in which case you should try to fit your algorithms to the pre existing directories

I have some general algorithms. But also a lot of practice code of my own covering topics like loops, arrays, pointers, Pattern printing and all.

I am not sure if that's too general for this repository. I think we are looking at more of problem solving type algorithms.
there are linked lists and binary tree traversal in one of the sub directories if that's what you mean. I'm sure one of the other maintainers knows more about this issue! thank for you for raising this one!

Created a discussion about this on the Discord community. Let's see what others think.
I personally think it'd be great as many people will learn from that, but I'm not sure it 100% fits this repository.

Can you add me to the discord please?

Can you add me to the discord please?

we have a discord server!
https://the-algorithms.com/discord


code refactor: mount in virt-handler for hotplugged volumes

What this PR does / why we need it:
Refactor some functions in pkg/virt-handler/hotplug-disk/mount.go and tries to simplify the flow avoiding repetitions
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

@awels @ShellyKa13 could you please have a look when you have time :)

/retest-required

/lgtm

Reedit the commit messaged as suggested

/lgtm

/approve
/lgtm
Thanks!

/test pull-kubevirt-e2e-kind-1.22-sriov-nonroot


[FEATURE REQUEST] Show info for MSStore packages

I said in https://github.com/martinet101/WingetUI/issues/502 that it was not possible to get info for MSStore packages. But after giving some thought I might have figured out a way using the id (or at least part of it). For example the MSStore package "NVIDIACorp.NVIDIAControlPanel_56…":
1- strip "NVIDIACorp." and "_56…"
2- convert from CamelCase "NVIDIAControlPanel" to NVIDIA Control Panel (not case sensitive)
3- use command winget show "nvidia control panel"

If this is indeed possible you would also have to specify the source, since some packages might also be available in winget. For example: winget show "Microsoft Edge" --source msstore

For the moment, since the mstore is quite broken, i would prefer not to include this for the moment.
I already tested that, but some packages it does not work, since they being "Microsoft Store" is not actually true, but rather the truth is that they were installed through .appx/.msix installers, but not necessarily microsoft store, then they might not be published on winget


CNAME error despite having installed all the necessary pkg

Hi,
I have tried to find all ways to resolve this issue, installed and reinstalled (updated) all pkgs required by this tool, yet getting Domain problem : Cname not found error each time I run the tool on a domain. Also, tried to change the DNS server to <IP_ADDRESS> and other resolvers but to no success.
Any pointers to help solve this prblm?
Best,

@anshumanbh @random-robbie @mhmdiaa would appreciate your feedback on the issue.

Same here bro any updates?

same error any update ?


Snippet saved successfully in both collections

I prefer the first one and made a PR for this. This is in regards to the issue #20 .

Check the comments on issue #20 , Thank you


5.0.0-alpha.7 maven jar doesn't contain classes

See published com.squareup.okhttp3:okhttp:5.0.0-alpha.7 version on Maven Central — https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp/5.0.0-alpha.7/

okhttp-5.0.0-alpha.7.jar                          2022-04-27 03:58     13361

13 KB.
But sources JAR is correct, 753 KB.

It's a mulitplatform jar, see https://repo1.maven.org/maven2/com/squareup/okhttp3/okhttp-jvm/5.0.0-alpha.7/
Can you explain what you are trying to do, what you build system is?

They definitely work from other projects, at least gradle.
And it's the same for a while now for other projects like https://repo1.maven.org/maven2/com/squareup/okio/okio/3.1.0/

It is broken since alpha 3. After alpha 3 I cannot update to alpha 4 and so on.

Can you explain what you are trying to do, what you build system is?

IntelliJ IDEA (JPS). Our project is 20+ years old and maven/gradle are not suitable for us :) Two JARs are used to compile:
~/.m2/repository/com/squareup/okhttp3/okhttp/5.0.0-alpha.3/okhttp-5.0.0-alpha.3.jar
~/.m2/repository/com/squareup/okio/okio-jvm/3.0.0/okio-jvm-3.0.0.jar
It was so before I do not see any transitive dependencies. Also I do not see any dependencies in POM file.
Do I use a wrong maven coordinates? Is something changed? Maybe you forgot to add some new dependency after some splitting in alpha 4+ (but why in this case sources jar is correct as before)?

And it's the same for a while now for other projects like

Yep. okio jar is also empty... The question in this case — where I supposed to get a correct JARs if published to a Maven Central are empty and do not have any transitive dependencies except kotlin?

I'm going to close this, because there isn't a change for us to make here.
I'd like to understand the answer to your question too, perhaps a stackoverflow question or an issue in the jetbrains issue tracker asking for a solution?
I suspect these files tell the kotlin compiler what else to request https://repo1.maven.org/maven2/com/squareup/okio/okio/3.1.0/okio-3.1.0-kotlin-tooling-metadata.json
But that's a guess.

I believe the fix is to use the -jvm artifact. Like this:
com.squareup.okhttp3:okhttp-jvm:5.0.0-alpha.7

We aught to call this out in our 5.x upgrade guide.

Indeed, that's because gradle’s dependency management engine is variant aware. Thanks for so quick response!

An issue https://youtrack.jetbrains.com/issue/KT-52323/Add-option-to-publish-Kotlin-multiplatform-library-in-a-way-that was created to make preserving backward compatibility more easier.


Double-free error in some cases when C_ell = 0 in correlation function calculation

Hi all,
During CI for TXPipe I've encountered an error in CCL where a zero C_ell going into correlation can lead to a corruption bug / crash.
I haven't quite figured out the precise path that causes, but have managed to put in some more checks that avoid it, in branch https://github.com/LSSTDESC/CCL/tree/double_free_bug .  That might just be evading another issue though.
Here's an example, which crashes for me at least in python 3.7 and pyccl 2.1.0 under ubuntu.
It doesn't happen in 2.0.1 on macos.
I've also put together a docker image in which you can run ths it at joezuntz/ccl-error-debug.  Notes on that below this script.
import numpy as np
import pyccl
C_ell = np.zeros(248)

theta = np.array([0.01281598, 0.02624485, 0.05326189, 0.10870941, 0.22152326,
       0.45065021, 0.9166528 , 1.86319592, 3.77051377])

method = 'fftlog'
cosmo = pyccl.Cosmology(Omega_c=0.2545, Omega_b=0.0485, h=0.682, n_s=0.971, sigma8=0.801, A_s=None, Omega_k=0.0, Omega_g=None, Neff=3.046, w0=-1.0, wa=0.0, T_CMB=None, bcm_log10Mc=14.079181246047625, bcm_etab=0.5, bcm_ks=55.0, mu_0=0.0, sigma_0=0.0, m_nu=0.0, m_nu_type=None, z_mg=None, df_mg=None, transfer_function='boltzmann_camb', matter_power_spectrum='halofit', baryons_power_spectrum='nobaryons', mass_function='tinker10', halo_concentration='duffy2008', emulator_neutrinos='strict')

ell = np.array([2.00000000e+00, 3.00000000e+00, 4.00000000e+00, 5.00000000e+00,
       6.00000000e+00, 7.00000000e+00, 8.00000000e+00, 9.00000000e+00,
       1.00000000e+01, 1.10000000e+01, 1.20000000e+01, 1.30000000e+01,
       1.40000000e+01, 1.50000000e+01, 1.60000000e+01, 1.70000000e+01,
       1.80000000e+01, 1.90000000e+01, 2.00000000e+01, 2.10000000e+01,
       2.20000000e+01, 2.30000000e+01, 2.40000000e+01, 2.50000000e+01,
       2.60000000e+01, 2.70000000e+01, 2.80000000e+01, 2.90000000e+01,
       3.00000000e+01, 3.10000000e+01, 3.20000000e+01, 3.30000000e+01,
       3.40000000e+01, 3.50000000e+01, 3.60000000e+01, 3.70000000e+01,
       3.80000000e+01, 3.90000000e+01, 4.00000000e+01, 4.10000000e+01,
       4.20000000e+01, 4.30000000e+01, 4.40000000e+01, 4.50000000e+01,
       4.60000000e+01, 4.70000000e+01, 4.80000000e+01, 4.90000000e+01,
       5.00000000e+01, 5.18135414e+01, 5.36928615e+01, 5.56403460e+01,
       5.76584674e+01, 5.97497878e+01, 6.19169621e+01, 6.41627416e+01,
       6.64899774e+01, 6.89016239e+01, 7.14007429e+01, 7.39905069e+01,
       7.66742039e+01, 7.94552408e+01, 8.23371482e+01, 8.53235847e+01,
       8.84183418e+01, 9.16253483e+01, 9.49486755e+01, 9.83925426e+01,
       1.01961322e+02, 1.05659543e+02, 1.09491902e+02, 1.13463264e+02,
       1.17578671e+02, 1.21843347e+02, 1.26262706e+02, 1.30842359e+02,
       1.35588119e+02, 1.40506013e+02, 1.45602282e+02, 1.50883398e+02,
       1.56356063e+02, 1.62027227e+02, 1.67904089e+02, 1.73994109e+02,
       1.80305020e+02, 1.86844832e+02, 1.93621849e+02, 2.00644674e+02,
       2.07922222e+02, 2.15463733e+02, 2.23278781e+02, 2.31377288e+02,
       2.39769534e+02, 2.48466173e+02, 2.57478247e+02, 2.66817196e+02,
       2.76494877e+02, 2.86523575e+02, 2.96916022e+02, 3.07685412e+02,
       3.18845417e+02, 3.30410205e+02, 3.42394456e+02, 3.54813387e+02,
       3.67682762e+02, 3.81018920e+02, 3.94838792e+02, 4.09159922e+02,
       4.24000491e+02, 4.39379340e+02, 4.55315993e+02, 4.71830681e+02,
       4.88944371e+02, 5.06678788e+02, 5.25056447e+02, 5.44100679e+02,
       5.63835661e+02, 5.84286448e+02, 6.05479001e+02, 6.27440226e+02,
       6.50198003e+02, 6.73781223e+02, 6.98219826e+02, 7.23544837e+02,
       7.49788407e+02, 7.76983854e+02, 8.05165702e+02, 8.34369728e+02,
       8.64633010e+02, 8.95993965e+02, 9.28492408e+02, 9.62169597e+02,
       9.97068285e+02, 1.03323278e+03, 1.07070899e+03, 1.10954449e+03,
       1.14978858e+03, 1.19149237e+03, 1.23470878e+03, 1.27949269e+03,
       1.32590095e+03, 1.37399248e+03, 1.42382832e+03, 1.47547176e+03,
       1.52898834e+03, 1.58444601e+03, 1.64191518e+03, 1.70146880e+03,
       1.76318249e+03, 1.82713458e+03, 1.89340626e+03, 1.96208167e+03,
       2.03324800e+03, 2.10699559e+03, 2.18341806e+03, 2.26261245e+03,
       2.34467927e+03, 2.42972273e+03, 2.51785079e+03, 2.60917532e+03,
       2.70381227e+03, 2.80188178e+03, 2.90350835e+03, 3.00882101e+03,
       3.11795344e+03, 3.23104419e+03, 3.34823684e+03, 3.46968016e+03,
       3.59552833e+03, 3.72594112e+03, 3.86108409e+03, 4.00112881e+03,
       4.14625307e+03, 4.29664110e+03, 4.45248383e+03, 4.61397911e+03,
       4.78133195e+03, 4.95475482e+03, 5.13446788e+03, 5.32069928e+03,
       5.51368545e+03, 5.71367139e+03, 5.92091098e+03, 6.13566733e+03,
       6.35821306e+03, 6.58883072e+03, 6.82781306e+03, 7.07546350e+03,
       7.33209642e+03, 7.59803763e+03, 7.87362474e+03, 8.15920763e+03,
       8.45514885e+03, 8.76182410e+03, 9.07962272e+03, 9.40894816e+03,
       9.75021850e+03, 1.01038670e+04, 1.04703426e+04, 1.08501106e+04,
       1.12436531e+04, 1.16514697e+04, 1.20740782e+04, 1.25120150e+04,
       1.29658361e+04, 1.34361178e+04, 1.39234569e+04, 1.44284722e+04,
       1.49518048e+04, 1.54941192e+04, 1.60561037e+04, 1.66384719e+04,
       1.72419630e+04, 1.78673433e+04, 1.85154066e+04, 1.91869758e+04,
       1.98829033e+04, 2.06040727e+04, 2.13513994e+04, 2.21258324e+04,
       2.29283546e+04, 2.37599850e+04, 2.46217794e+04, 2.55148317e+04,
       2.64402758e+04, 2.73992865e+04, 2.83930813e+04, 2.94229219e+04,
       3.04901156e+04, 3.15960174e+04, 3.27420311e+04, 3.39296117e+04,
       3.51602668e+04, 3.64355588e+04, 3.77571067e+04, 3.91265882e+04,
       4.05457419e+04, 4.20163696e+04, 4.35403381e+04, 4.51195822e+04,
       4.67561068e+04, 4.84519895e+04, 5.02093833e+04, 5.20305192e+04,
       5.39177093e+04, 5.58733492e+04, 5.78999219e+04, 6.00000000e+04])

pyccl.correlation(cosmo=cosmo, ell=ell, C_ell=C_ell, theta=theta, corr_type='gg', method='fftlog')

Running under gdb in the docker image reveals the following backtrace:
#4  0x00007fc4eff61e84 in _int_free (have_lock=0, p=0x1e64de0, av=0x7fc4f02b5c40 <main_arena>) at malloc.c:4281
#5  __GI___libc_free (mem=0x1e64df0) at malloc.c:3124
#6  0x00007fc4c1c24942 in ccl_tracer_corr_fftlog (status=0x7ffffd969ca8, taper_cl_limits=0x0, do_taper_cl=<optimized out>, corr_type=2001, wtheta=0x1e9c7b0, theta=0x1e8ea80, n_theta=9, cls=0x1e90630,
    ell=0xf8, n_ell=30808624, cosmo=<optimized out>) at /root/CCL/src/ccl_correlation.c:130
#7  ccl_correlation (cosmo=cosmo@entry=0x1c31f90, n_ell=n_ell@entry=248, ell=ell@entry=0x1d61a30, cls=cls@entry=0x1e90630, n_theta=9, theta=theta@entry=0x1e8ea80, wtheta=0x1e9c7b0, corr_type=2001,
    do_taper_cl=0, taper_cl_limits=0x0, flag_method=1002, status=0x7ffffd969ca8) at /root/CCL/src/ccl_correlation.c:389
#8  0x00007fc4c1c06cd7 in correlation_vec (cosmo=cosmo@entry=0x1c31f90, larr=larr@entry=0x1d61a30, nlarr=nlarr@entry=248, clarr=clarr@entry=0x1e90630, nclarr=nclarr@entry=248,
    theta=theta@entry=0x1e8ea80, nt=<optimized out>, corr_type=2001, method=<optimized out>, nout=<optimized out>, output=<optimized out>, status=0x7ffffd969ca8)
    at /root/CCL/build/pyccl/cclPYTHON_wrap.c:4312

The line ccl_correlation.c:130 is where it frees some memory after an error.
I think it's not actually a double free, but a memory overspill inside the interpolator function.
At a higher level of course, if the C_ell are all zero you can immediately skip to returning zero for a correlation function.

Thanks for finding this! It looks like it might be related / the same as Issue #785. I will have a look; @damonge may also have thoughts?

Yes, I suspect it has to do with how we chose to extrapolate the C_ells logarithmically. Log(0) is not great.
I meant to look into this but haven't had a chance yet.

@joezuntz is this fully solved by your recently merged PR?

It is for me - I wouldn't want to claim that the same issue will never raise its head in other situations, but it's fine for me for now.  Maybe close this but re-open later if needed?

Sounds good.


[T2A5][T09-A1]Ashley Ong

Ready for review.

Good job. Don't forget to edit the user guide too when you enhance a feature.


Added TLS 1.1 and 1.2

Added the necessary library files to use tls 1.2
@rminnich about ifndef in libsec: It came from plan 9 code, I didn't introduce it. If you want I can remove it, but I think it would be better to do it in a separate PR because it means I'll change a lot of files not only under libsec but in cmd tree as well. Do you agree?

yeah, you're right, it must have been when they imported it in the first place.

Be carefull with cmd stuff. All which needs pcc muat be moved to apex/cmd or replaced with newer ports. Many ifdefs comes from ported programs and they were in tree as old ape.

Commit f10806c1ba2d23b0ea934c3685d317a0c1951b17 is not signed-off.
Please fix these issues:

Rafa has not signed-off f10806c.

If you'd like more information on how to sign your commits please visit signed-off-by.me


return true when no file was created and overwrite was not set

Fixes https://github.com/lovell/avif-cli/issues/16

Thank you!


Migrate sensor drivers to device tree

[x] ak8975 [@galak] #22962
[x] bma280 [@pabigot] #22103
[x] dht (gpio) [@pabigot] #21424
[x] grove-light [@pabigot] #21602
[x] grove-temp [@pabigot] #21602
[x] mpu6050 [@pabigot] #21565
[x] pms7003 (uart device) [@galak] #22963

I can take the ST sensors (lis*, lsm*) work.

Thanks!

(Please note that in the above list the lis2mdl is missing as it has been recently added)

I added it to the list.

@MaureenHelm
Ticked lis2dh in the list above and moved on lis3dh.

@MaureenHelm
lis2mdl is ready but requires your review. (PR #11832)

@MaureenHelm
For completeness I added in the list above also lsm303dlhc accel/magn driver because they wer missing.
The good news is that they already use info from DT!

@Mani-Sadhasivam can you look at converting the ccs811 to DTS?

@galak Okay. Will do it this weekend.

@galak Okay. Will do it this weekend.

thanks

A more complete list of sensors that need to be converted is in #20017; could we close this and use that one?  @galak

I've transferred the entries added here to #20017 so we don't have to look in two places to see what's being worked on.  The original list there only focused on uses that included interrupts, so I'll be adding a few more to that issue.

I've transferred the entries added here to #20017 so we don't have to look in two places to see what's being worked on. The original list there only focused on uses that included interrupts, so I'll be adding a few more to that issue.

My changes are purely DT changes, I didn't make any conversions to new GPIO API.  So not sure about moving this list into #20017, unless we want that PR to handle both changes (DT & updated GPIO API support).

@MaureenHelm I'm digging around to see what sensors I have from this list, but found a hmc5883l so I can take that one, and I'll see if I can find any other parts that don't have owners yet.

@Mani-Sadhasivam can you look at converting the ccs811 to DTS?

Looks like it was pretty easy so I did it #20347

#22963 and #22962 should close this out.

#22963 and #22962 should close this out.

Merged


Simultaneous deletion of multiple bitstreams from the same bundle often compromises the state of the bundle

Describe the bug
If several parallel calls are made to the endpoint to delete bitstreams it may happen that these bitstreams are set with the deleted flag to true but only one of them is removed from the bundle. This means that the bitstreams still remain visible but no longer erasable.
To Reproduce
Steps to reproduce the behavior:

Login as administrator
Go to an item's page and click on "Edit this item"
Go to the edit bitstreams section and upload many bitstreams in the same bundle
Try to delete all the bitstream selecting them all and then deleting them with a single action
Some times not all the bitstreams are deleted and if you try to remove them another time you will get an error 404 from the REST

The erroneous behavior is more noticeable and frequent as the number of bitstreams deleted together increases.

Expected behavior
All the selected bitstreams should be flagged as deleted and removed from the bundle
I think the problem is the concurrent manipulation of the bundle2bistream relationship modeled through org.dspace.content.Bundle.bitstreams. In fact, the final status of the bundle2bitstream table would reflect the status of the last committed transaction, in which only one of those bitstreams is removed.
In particular it could be related to the fact that the collection of bitstreams in a bundle is modeled with a list rather than a set and this can cause inserts when removing a bitstream from the bundle, see https://vladmihalcea.com/the-best-way-to-use-the-manytomany-annotation-with-jpa-and-hibernate/
If this should actually be the problem, we could try to substitute the list with a set and see if the problem is solved.

@LucaGiamminonni : I'll pull this over to the 7.6 board to see if we can find a volunteer to look at this in more detail.  I agree it sounds like something we want to fix quickly.

@arvoConsultores has asked to claim this ticket. Assigned to their team.

Reviewing the data model it seems to me that we don't need a manytomany relationship from bundles to bitstreams. A bitstream cannot belong to more than one bundle, right?
So maybe we can delete bundle2bitstream table and move the extra columns to bitstream table. making it a one2many bundle to bitstream relation.

@aroman-arvo : I think we'd need to be very careful about removing bundle2bitstream table without a deeper analysis.  For example, I'm not sure whether it is being used by features like Item Level Versioning (where a content file can be shared across multiple versions of an Item... though I think in this scenario there may still be two Bitstream objects which shared the same content-file on disk).
You are correct though that the REST API only shows a Bitstream as belonging to a single Bundle: https://github.com/DSpace/RestContract/blob/main/bitstreams.md#bundle  (and never multiple Bundles)
So, I think you are correct. But, I'm just concerned I could be overlooking something here.  So, I feel we'd have to very carefully test/verify that bundle2bitstream could be removed easily.

I tested versioning and it generate a new item, with his bundles and bitstreams. Only internal_id is shared between instances.

I checked some 5.x and 6.x dspace instalations (production data) and was not able to find a case of shared bitstream between 2 bundles.
I used "select count() from bundle2bitstream group by bitstream_id having count() >1"

I do think we should ask ourselves why it was designed that way in the first place.  dspace-server-webapp is not the only possible client of the data model.  It would be good if we can eliminate a junction table, but it would be bad if we subsequently realize why we needed it.

One possible use, just to start some thinking:  de-duplicating the LICENSE bundles' bitstreams.

@aroman-arvo and @mwoodiupui : I tend to agree that we may not want to immediately jump to the conclusion that bundle2bitstream requires removal.  As noted in the original description by @LucaGiamminonni (see above) , the less complex solution might be to simply change the bundle2bitstream relationship from a List to a Set.  If that's all that it takes to fix this, that's a much easier code change than removal of bundle2bitstream.
So, I would recommend we look first at that simple approach.  If there's a reason that won't work, then we can investigate removal of bundle2bitstream.  Looking back, the bundle2bitstream table looks to have existed since DSpace v1.2.  I'm a little hesitant to rip it out suddenly. I'm concerned some sites could have used it in some way in an older version of DSpace & therefore there may be sites which have old data that relies on this table.  So, I'd prefer it if we first determine if there's a way to solve the problem with the bundle2bitstream table kept as-is.

I already tried the simplest solution, but the ordering would stop working. You can not simply change the list for a set.
I also tried to make the changes transactional so that deletions do not fail, and even make some synchronized methods but, although it improved a lot, in extreme cases it still leave bitstreams without deleting (it goes from delete only 1 of 10 in a bundle of 50, to delete 9 of the 10)
Now I'm trying to manually manage the order by creating the Bundle2Bitstream entity.
Working on it I have realized that it seems that the table does not contribute. I didn't expect to just delete it, but the next wise council should review it. A simple data model is always appreciated.


How do I report outage when LCS is down too?

a question

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1a326d11-a0a3-1e59-06d3-e576f72e6f5e
Version Independent ID: 7601cd35-9b1f-2dec-99ea-5e417f5f643b
Content: Report a production outage - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/dev-itpro/lifecycle-services/report-production-outage.md
Service: dynamics-ax-applications
GitHub Login: @manalidongre
Microsoft Alias: manado

Thanks for the comment. @manalidongre, can you please help with this question?

Should probably link to this information
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/cloud-powered-support-lcs#phone-support

I've updated the Report a production outage topic to link to the Phone support section. The change will be published in a day or two.


[WIP] policy: allocate identity for CIDR selectors on first use

This moves allocation of local identities for CIDRs from policy ingestion to selector parsing.
See individual commits for more detailed commentary.
TODO:

[ ] Get soft consensus that this is a good approach
[ ] Fix existing unit tests
[ ] Write more tests

@christarazi I've updated this to fix your concerns around and endpoint's PolicyRevision not being quite correct. The fix is to synchronously allocate Identities as part of inserting a prefix in to the ipcache metadata.
As per a synchronous discussion: "@joestringer might not hate this. might."
This required a bit of a rethink, along with some silly bookkeeping to ensure we didn't leak identities, but it seems to work. CIDR identities are allocated as needed, and de-allocated when no longer selected.
There are some small TODOs, mostly around patching up existing unit tests and writing new ones, but I don't want to get started on that until we agree that this is a good approach.

I'm recognizing that there's a lack of design docs and state sharing around a lot of the logic here, which I'll take partial responsibility for... sorry about that :-)

No worries at all. In fact, I feel I've a fairly good idea of where this all is going; and I've been trying to help work towards that goal. Especially in leaving the door open for the fqdn identity dance to be simplified.

Although I feel that I have a fair understanding of where this proposal is coming from, I admit that I found it difficult to follow the full reasoning about the approach.

Apologies for not writing more. This started out as an experiment, and most of the design discussions have been too in-person and "backroom".

I've got some broad code structure concerns about the proposal, both in terms of the code complexity and the way that the ipcache module interfaces with other modules. I've discussed some scenarios below, and raised some brainstorming threads on possible alternatives. I do have some vested interest/opinions in this area, but at the same time I've tried to focus my feedback on technical discussion topics that we can hopefully iterate and explore further together.

I've commented below; I think you're broadly right and this PR doesn't take the correct approach. I'll try and play around with an asynchronous implementation.

Closing this in favor of a new approach.


Publish 1.3.4

The extension still isn't released. Is it still due to the issue with the release token?

yes, @tmds, my apologies. It's on me to get this properly wired up. Setting out to do this now. Let's see if I can circumvent the world here. :-)

Failed twice. Will keep at it. I appreciate the patience.

@tmds, I believe we were able to solve the problem and published the release.

@squillace, I've just installed 1.3.4. Thank you!

it's a miracle, frankly


Added public methods of HTTPService to interface

We need them to access to objects methods when they were inherited from HTTPService and will be accessed by interface (var service:IHTTPService)

You're right, it was reported last week here
Thank you.


feat(internet-header): initialize package

Preview environments are getting posted here, as soon as they are ready!


define aggregation mixin uses for all

Currently working on improving these queries for talk.
Saw this and thought I'd just fix.
Am trying to just delete all of this soon enough
before:

5 aggregation mixin override the defaults use to vms and hosts
1 keeps default uses of all_relationships
1 overrides to all_relationships (seems unneeded)

after:

single common method
all classes call this value

implementation details:
define single method aggregation_mixin_virtual_columns_use
defaults to use hosts and vms table since it is 5 to 2

LGTM :+1:

not sure why this failed, rebasing and trying again


Group by which doesn't aggregate

I don't know if this is relevant at all, but it just struck me that I have come across this a number of times, and maybe it would be relevant. So for example I have a table called design groups, with a key called sig_id. I want to list design groups grouped by SIGs, so intuitively I feel like I want to "group by" sig_id... However, that only works if I use an aggregation function like count. Instead, what I want is
sig_id group_name
1      'hi'
1      'hola'
2      'ni hao'
2      'zdrastovoyte'

should be
%{1=> ["hi", "hola"], 2=> ["ni hao", "zdrastovoyte"]}

So far I've done this manually, by first doing the query, and then Enum.group_by etc. But it just struck me that it seems like a common pattern, and I wonder if it fits into Ecto. Or maybe it could be generalized to an external function. (Actually I would love to be able to do nested group_by, first by one key and then by a second key).

Yes, our group by ties in to the database. If you want to group by as you mentioned, then Enum.group_by is the proper alternative. I don't think we should provide such patterns in Ecto yet.


JSON output

Issue To Be Solved
Add the option to print all command outputs as JSON. This makes it easier for other programs to consume structured output from the CLI.
Suggest A Solution
Add a flag to each command that changes the output to JSON. Ideas: --json or --output=json

Solved in #100


colorscheme config

Hi thanks for this cool extension. I have the latest version of it. The issue i find is that the effectiveness depends a lot on the colorscheme (for example for most colorschemes (from the git repo  awesome-nvim-colorschemes) doesn't even trigger. In some others (like aurora, PaperColor) it triggers even in normal mode. So my clue is that the code depends heavily on what the colorscheme provides to the environment. Do you have any suggestions on how to provide some defaults that the extension won't brake after colorscheme switch. Also regarding the second behavior (the extra triggering) that could perhaps be an issue with the autocommands? Thanks in advance

I do not think this plugin depends on any colorscheme.
Do you have a minium config I can reproduce? You can start with
https://github.com/ray-x/lsp_signature.nvim/blob/master/tests/init_pack.lua

Thanks for the answer. As i tried reproducing some bug with the same config (without touching anything) i saw that the colorcheme indeed had nothing to do. What i notice at first though is that when i switch tabs, then the extension is not active on the new tab. It works only for the first tab/buffer. I have lunarvim project installed and in a lunarvim extension config they have added that whenever a tab closes then the associated buffer is wiped as well. I don't think that's the exact issue, but now it seems like a buffnr recognition issue of the code. Also after i open a new tab and try to activate lsp_signature then bugs start occuring. For example, it triggers in insert mode correctly, then i press esc and enter normal mode , then it triggers in normal mode automatically. In the second tab opened it won't trigger by autocommands. Though i have mapped  to manually trigger "lua require('lsp_signature').toggle_float_win()" (by touching the toggle_key option in the init.lua) and when i manually trigger in the second tab it shows. But after i enter normal mode the virtual text is still on screen

You can also try to use on_attach (see readme first example) to setup lsp_signature. This will make sure lsp_signature attach to the lsp server and buffer you editing.

Yes i am using that: "{
"ray-x/lsp_signature.nvim",
config = function() require "lsp_signature".on_attach() end,
event = "BufRead"
}". That's set by default in the lunarvim config file (using wbthomason/packer.nvim)

lsp_signature.on_attach() should be called inside lsp on_attach method with bufnr parameter. Otherwise pls use setup.

Oh okay now it works thanks for the help <3


Exceptions not working properly

VSCode Version: 1.13.0
OS Version: macOS Sierra 10.12.5 / Windows 10 Enterprise 1607

Steps to Reproduce:

Open a .NET Core project (reproduced with .NET Core 1.1)
Add a line which causes an exception (division by 0 for example or even Debug.Assert(false))
Run the code in debug

Expected behaviour:
Visual Studio Code breaks on the line and display exception, as in previous version.

Actual behaviour:
Visual Studio Code breaks but doesn't show the line and the exception. The debug panel remains empty for every thread.

I reproduced this bug also on latest Insider version (1.14.0). I also reproduced it on a fresh install with only Omnisharp extension (ms-vscode.csharp) in 1.10.0, 1.11.0-beta and 1.9.0 to be sure that it's a Visual Studio Code issue.

@RenaudThoraval C# debugging is implemented by the C# extension. The extension owners will be able to specify if the issue you are seeing is due to the extension or VS Code.

This issue was moved to OmniSharp/omnisharp-vscode#1564

@ramya-rao-a As I said in my post, I tested with previous version of C# extension and the future one in beta and I still reproduce the bug.
I made a clean install of VS Code 1.12.2 on MacOS and Windows 10. The exception works fine, as expected. But as soon as I update VS Code in 1.13, the bug reappears. I think it related with changes in VS Code extension API or something like that.
I hope that C# extension owners will find a fix.

@RenaudThoraval Sorry, it wasnt clear from your earlier message if this was a regression from VS Code's side.

cc @gregg-miskelly from the C# extension side to help out with the investigations here

@ramya-rao-a No problem ;) I'm not fluent in english so excuse me for all the mistakes I write. I stay tuned if you need more information. I'll do my best to help you in the debugging process.
Regards !

The issue here is that we are now fetching callstacks in two requests, first the top call stack then the rest.
This case reveals an issue when another thread stops in between the first fetch and the rest. In this case we wrongly fetch the top stack frame for both threads, instead of fetching the full call stack for one of the threads, and leaving the other to be lazily fetched when needed.
My fix should take care of this, however I can not verify due to the handshake so I triggered an unreleased insiders build to verify if all is good now. @gregg-miskelly please send me the private dot net debugger so I no longer get pestered by this in the future
fyi @weinand as this is potentially a candidate. Bottom line: multi threaded debugging sometimes shows incomplete stack frames.

I just verified the fix is good.

Thanks @isidorn for the fix !

Here's an example for which I could repro the issue and which we can use to verify
using System;
using System.Threading;

namespace dotnet
{

    class Program
    {
        static void Main()
        {
            Thread thread1 = new Thread(new ThreadStart(A));
            Thread thread2 = new Thread(new ThreadStart(A));
            thread1.Start();
            thread2.Start();
            thread1.Join();
            thread2.Join();
        }

        static void A()
        {
            Thread.Sleep(100);
            String.Format(null, 12);
            Console.WriteLine('A');
        }

        static void B()
        {
            Thread.Sleep(1000);
            String.Format(null, 12);
            Console.WriteLine('B');
        }
    }
}

@weinand noticed that the fix is incomplete and that in some corner cases we might still hit issues. In order to have a proper solution we need a callStackScheduler per Thread and this will be a larger refactoring which I am now looking into.
Since the proper fix will touch more code areas and since this issue does not happen that often I suggest that we do not release this in the recovery build.
The fix would be available soon in insiders in either way.


VS Code Breaks Down FREQUENTLY!!!

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.67.2.
OS Version: Windows 7 x64.

Steps to Reproduce:

Update VS Code to version 1.67.2.
Just open the editor and start coding as usual.
The app runs slowly. It may break down for even up to 3 times or even more within only 15min.! I sincerely hope this fatal bug will be fixed at once.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[EN] Feedback for: /web/fundamentals/primers/payment-request/?hl=en

Hi,
I would like to start playing with the payment-request API for Desktop.
Is there any Chrome Extension I can download which has this API? or any Beta version? if not, when do you think it will be ready? what is the road-map for implementing this API in Chrome?
BR,
Avish Yeshurun
<EMAIL_ADDRESS>

@agektmr - can you answer this?

Desktop version is under development. It should be available hopefully in Chrome 55.


Problems deploying to virtual server due to opencollective postinstall script failure with permissions denied

When trying to do npm install when deploying my app based on Nuxt.JS in some virtual hosting env, I  get an error:
npm ERR<EMAIL_ADDRESS>postinstall: `opencollective postinstall`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'opencollective postinstall'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nuxt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     opencollective postinstall
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs nuxt
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls nuxt
npm ERR! There is likely additional logging output above.

Didn't recognize which operation fails on missing priviledges, but definitely user account in the vhosting may be a little limited.
Apparently, this is known to opencollective devs, as they suggest to form postinstall like this just to make the script not preventing from installing the dependency:
  "scripts": {
    "postinstall": "./node_modules/.bin/opencollective-postinstall || exit 0"
  },

(from https://github.com/opencollective/opencollective-postinstall)

happening for me as well

rc5 is out https://github.com/nuxt/nuxt.js/releases/tag/v1.0.0-rc5


Interface for querying ingest job status

This is to be used by the client in #323 and the implementation in #324

It'll be easier to get the interface right if we define it as we write the client in #323, but implement the DB side separately. I'll close this for now.


target.hardware: whitelist HOME on Linux

This resovles errors when nextpnr-ice40 tries to create directories in the rootfs (follow on from #384)
See: https://github.com/YosysHQ/oss-cad-suite-build/issues/75

Absolutely not, this negates the point of doing hermetic builds.

The reason I whitelisted $PROCESSOR_ARCHITECTURE is that you can already get that information in a number of other ways, so it doesn't really make any difference. If a toolchain for some reason messes with $HOME this is a bug in the toolchain, plain and simple. And if you are hitting an issue with hermetic builds pulling in some sort of unexpected impurity, the solution is not to whitelist the impurity, because that is a route to breaking our caching scheme.

Oh, apologies.
So we're hoping / depending on https://github.com/YosysHQ/oss-cad-suite-build/issues/75 to resolve the issue?

Oh, apologies. I thought $HOME would be benign enough...

No, absolutely not! $HOME with its various configuration files is a prime example of what should not be in the builder environment.

So we're hoping / depending on YosysHQ/oss-cad-suite-build#75 to resolve the issue?

Why not write a pull request for oss-cad-suite?


UWP apps should better handle unsaved/working data to prevent accidental data loss during App Updating.

Proposal: UWP apps should  better handle unsaved data to prevent data loss during App Updating

Summary : when an App Update is installed from the store or locally through the App Installer , (Before installing the app update and Restarting the app ), it should first ask the user to whether save or cancel the working or unsaved documents or It could automatically save unsaved documents  and then resume again after the installing the update & restarting.

Is your app handling suspend/resume already? The same mechanism (suspend, terminate, update, resume) is used during any package updates.

Is your app handling suspend/resume already? The same mechanism (suspend, terminate, update, resume) is used during any package updates.

It is handling suspend/resume already. Still updating the app package locally neither suspend the unsaved documents nor resume it .  It actually terminates all the instances of the app right after installing updates. thus losing unsaved/working data. Actually this is the case with almost every other UWP apps. Any documentation using the same suspend/resume mechanics during package updating ?

I agree with the OP that all packaged apps be it win32 or UWP suffer from this Packaged Apps Update issue. they never save the current app data state during package updates and also never restarts itself after an update has been installed. so if an update has been installed all the unsaved data gets lost.😕
I will like Project Reunion consider & provide something like :.
installing package updates (store or I myself locally through App Installer) ➡ check if the app is open ➡ if not open , apply update silently ||| or if open, save all the unsaved current working data/app state ➡ terminate the process & apply package updates ➡ restart the app itself and restore the all the unsaved current working data/app state.           everybody happy.
This is a pain and needs to be fixed ASAP.

I agree with the OP that all packaged apps be it win32 or UWP suffer from this Packaged Apps Update issue.   they just never save the current app data state during package updates and also never restarts itself after an update has been installed. so if an update has been installed all the unsaved data gets lost.😕
I will like Project Reunion consider & provide something like :.
installing package updates (store or I myself locally through App Installer) ➡ check if the app is open ➡ if not open , apply update silently ||| or if open, save all the unsaved current working data/app state ➡ terminate the process & apply package updates ➡ restart the app itself and restore the all the unsaved current working data/app state.           everybody happy.
This is a pain and needs to be fixed ASAP.

I agree with the OP that all packaged apps be it win32 or UWP suffer from this Packaged Apps Update issue.   they just never save the current app data state during package updates and also never restarts itself after an update has been installed. so if an update has been installed all the unsaved data gets lost.😕
I will like Project Reunion consider & provide something like :.
installing package updates (store or I myself locally through App Installer) ➡ check if the app is open ➡ if not open , apply update silently ||| or if open, save all the unsaved current working data/app state ➡ terminate the process & apply package updates ➡ restart the app itself and restore the all the unsaved current working data/app state.           everybody happy.
This is a pain and needs to be fixed ASAP.

I agree with the OP that all packaged apps be it win32 or UWP suffer from this Packaged Apps Update issue.   they just never save the current app data state during package updates and also never restarts itself after an update has been installed. so if an update has been installed all the unsaved data gets lost.😕
This is a pain and needs to be fixed ASAP.
I will like Project Reunion consider & provide something like :.
installing package updates (store or I myself locally through App Installer) ➡ check if the app is open ➡ if not open , apply update silently ||| or if open, save all the unsaved current working data/app state ➡ terminate the process & apply package updates ➡ restart the app itself and restore the all the unsaved current working data/app state.           everybody is  happy. 👍

We'll check into this, thanks for the report.  If you can, collect a feedback hub trace during an update (Win+F, category "Install and Update" subcategory "App installation issues"). Use the "reproduce while collecting data" option.  Somewhere in the description add "from project reunion 129" or "task 30813592" so we can find it more easily.
Windows folks, reference http://task.ms/30813592

@jonwis  Done !! https://aka.ms/AAaei0v

See also https://github.com/microsoft/ProjectReunion/issues/300

Is your app handling suspend/resume already? The same mechanism (suspend, terminate, update, resume) is used during any package updates.

It is handling suspend/resume already. Still updating the app package locally neither suspend the unsaved documents nor resume it . It actually terminates all the instances of the app right after installing updates. (and Of course the app model never let devs, to ask the user to save or cancel current state.) thus losing unsaved/working data. Actually this is the case with almost every other UWP apps including Microsoft Store itself. Any documentation explaining usage of the same suspend/resume mechanism during package updating ?

Is your app handling suspend/resume already? The same mechanism (suspend, terminate, update, resume) is used during any package updates.

It is handling suspend/resume already. Still updating the app package locally neither suspend the unsaved documents nor resume it . It actually terminates all the instances of the app right after installing updates. (and Of course the app model never let devs, to ask the user to save or cancel current state.) thus losing unsaved/working data. Actually this is the case with almost every other UWP apps including Microsoft Store itself. Any documentation explaining usage of the same suspend/resume mechanism during package updating ?

This documentation  goes over app suspension and the deferrals that are required to prevent the app from suspending until the save is complete. Please take a look at the app suspend section in the document. If you have called these API's in your app, please file a feedback through the feedback hub with a repro of your app update under the section Developer Platform -> App Deployment. This would collect the necessary logs for us to diagnose the specific issue that you are hitting.

I agree with the OP that all packaged apps be it win32 or UWP suffer from this Packaged Apps Update issue. they just never save the current app data state during package updates and also never restarts itself after an update has been installed. so if an update has been installed all the unsaved data gets lost.😕
This is a pain and needs to be fixed ASAP.
I will like Project Reunion consider & provide something like :.
installing package updates (store or I myself locally through App Installer) ➡ check if the app is open ➡ if not open , apply update silently ||| or if open, save all the unsaved current working data/app state ➡ terminate the process & apply package updates ➡ restart the app itself and restore the all the unsaved current working data/app state. everybody is happy. 👍

Package update goes through the same flow that you have described above. It supports both silent updates and force updates. In case of silent updates, the package is not updated while the app is running. Platform would wait for the user to close the app before updating the package. In case of force updates, the apps are sent a suspend notification and then terminated. This documentation goes over app suspension and the deferrals that are required to prevent the app from suspending until the save is complete. Please take a look at the app suspend section in the document.
Feedback that you provided does not capture any repro. Can you please file a feedback through the feedback hub with a repro of your app update under the section Developer Platform -> App Deployment. This would collect the necessary logs for us to diagnose the specific issue that you are hitting.

@kanismohammed  Thanks for the app update scenario clarification.

In case of force updates, the apps are sent a suspend notification and then terminated. This documentation goes over app suspension and the deferrals that are required to prevent the app from suspending until the save is complete. Please take a look at the app suspend section in the document.

Does the same UWP specific save-suspend-resume mechanism apply to a packaged win32 app also?
Win32 apps don't support this suspend-save-resume scenario at least not yet. so, what happens when a user forcibly updates a running win32(packaged)  app? does the app immediately terminate all of its instances and thus also lose those current unsaved data?

Feedback that you provided does not capture any repro. Can you please file a feedback through the feedback hub with a repro of your app update under the section Developer Platform -> App Deployment. This would collect the necessary logs for us to diagnose the specific issue that you are hitting.

Sorry. For some reason , my machine is not sending the diagnostics.zip file.  here https://aka.ms/AAah8ox, I've attached it manually. now it should be there.

@kanismohammed Thanks for the app update scenario clarification.

In case of force updates, the apps are sent a suspend notification and then terminated. This documentation goes over app suspension and the deferrals that are required to prevent the app from suspending until the save is complete. Please take a look at the app suspend section in the document.

Does the same UWP specific save-suspend-resume mechanism apply to a packaged win32 app also?
Win32 apps don't support this suspend-save-resume scenario at least not yet. so, what happens when a user forcibly updates a running win32(packaged) app? does the app immediately terminate all of its instances and thus also lose those current unsaved data?

Feedback that you provided does not capture any repro. Can you please file a feedback through the feedback hub with a repro of your app update under the section Developer Platform -> App Deployment. This would collect the necessary logs for us to diagnose the specific issue that you are hitting.

Sorry. For some reason , my machine is not sending the diagnostics.zip file. here https://aka.ms/AAah8ox, I've attached it manually. now it should be there.

For Win32 apps, We follow the RestartManager shutdown logic

WM_QUERYENDSESSION is sent to all processes.
WM_ENDSESSION/WM_WMCLOSE is sent to windows applications & Ctrl+C to console applications.
We use the information registered in the RestartManager (if any) to restart the packaged win32 apps. But we do restart all apps even if they are not registered with RestartManager.

Let me dig into the logs in the feedback and get back to you.

We have investigated this issue thoroughly, including the logs provided, and the platform is following the standard suspend-before-terminate flow. UWP apps have the opportunity to save state during suspend. Unpackaged Win32 apps can use the RestartManager as described above. So, the requirement is already covered for both packaged and unpackaged apps, using one or other of the techniques available today. Note however that we are considering extending Restart behavior in the Windows App SDK for the 1.1 release. More details to follow.

Out of curiosity, what's the alternative for UWP applications that can't save its state in a manner that makes them resumable. I'm (of course) talking about Windows Terminal (https://github.com/microsoft/WindowsAppSDK/issues/300) where one could have running processes in a shell , open remote connections doing all kind of things on the remote side, etc.


Bootstrap fails if Use/Machine Environment contains TMP Environment variables in different case

Environment:
Win 10 1709 / VS 15+VS 17
Steps to reproduce:

Environment contains a TMP/TEMP (uppercase) variable in Machine Environment and a tmp/temp (lowercase) variable in User Environment.
The machine tmp directories are not writable by the user
the compile fails when building with .\bootstrap-vcpkg.bat.

Solution:
I found that in `cleanEnvironmentHelper.ps1' the line
$nameSet = ($specialEnvironmentMap.Keys + $machineEnvironmentMap.Keys + $userEnvironmentMap.Keys) | Sort-Object | Select-Object -Unique

does a case sensitive "unique" and should be changed to
$nameSet = ($specialEnvironmentMap.Keys + $machineEnvironmentMap.Keys + $userEnvironmentMap.Keys) | Sort-Object -Unique

which is caseinsensitive. After that change the build completes normal.
Best regards
Soenke Schau

Hi @xgcssch, thanks for posing this issue. I try to build it on my local and it can be built successfully. I can't reproduce it now. Please feel free to reopen this issue if this is still a problem for you.


error converting YAML to JSON: yaml: line 228: mapping values are not allowed in this context

When doing kubectl apply -n default -f https://github.com/SAP-samples/kyma-runtime-learning-journey/blob/main/unit_3/functions/hello-world-function.yaml
I get error error: error parsing https://github.com/SAP-samples/kyma-runtime-learning-journey/blob/main/unit_3/functions/hello-world-function.yaml: error converting YAML to JSON: yaml: line 228: mapping values are not allowed in this context
PS C:\Users\Novarto>

Thank you for improving the course content. We will update this with the upcoming course update.
BR,
Markus

Hi @kostadin-t ,
instead of applying the github based yaml file view, you need to apply the raw yaml file by using this URL in yout statement: https://raw.githubusercontent.com/SAP-samples/kyma-runtime-learning-journey/refs/heads/main/unit_3/functions/hello-world-function.yaml
Do you copied that command from somewhere which needs to get adjusted to the raw URL?


RFC: Removing Ruby 1.9.3 and adding Ruby 2.2.4 in cflinuxfs2

Hi there,
As you may be aware the cflinuxfs2 stack currently includes Ruby 1.9.3. As support for this version will be sunset [1] on February 24th, 2016 this presents a challenge with our current implementation.
We're happy to conclude that the results of our research found that changing the base Ruby version from 1.9.3 to 2.24 provided a desired level of backwards compatibility. If you’re interested in experimenting with the change, check out the ruby-2.2.4 tag in the cloudfoundry/cflinuxfs2 dockerhub repo [2].
Our preference is to make the change to cflinuxfs2 by 3/7/2016. If you have any concerns or feedback please comment on this issue.
[1] - https://www.ruby-lang.org/en/news/2015/12/16/ruby-2-0-0-p648-released/
[2] - https://hub.docker.com/r/cloudfoundry/cflinuxfs2/tags/

Just out of curiosity: Why is there ruby in the stack at all? Shouldn't every buildpack bring ruby itself if that is necessary? Or is something else running in there which requires ruby?

@voelzmo Thanks for asking!
The rootfs has carried a Ruby interpreter since the Dawn Of Time™[1]; and we have tried to fulfill a commitment to users that updates to the rootfs will be backwards-compatible if at all possible (which means we generally don't remove any packages; though obviously that may become unsustainable at some point).
Notably, though, Ruby is used relatively widely to implement Buildpacks, and it would perhaps put an undue burden on Buildpack maintainers to have to provide their own version of Ruby in order to bootstrap into, say, a Java application.
[1]: for some definition of the Dawn Of Time for Cloud Foundry

Thanks @flavorjones for the explanation. Now that I look at the code of the java buildpack, I see why a ruby interpreter is needed :D

This has been completed in Stacks release 1.42.0


ncnn::Layer

Dear author, I can run yolov3, but I can't run yolov5. The error is: ncnn:: layer is not defined. It seems that there is no definition. Can you give me some advice.

Dear @huyunlei,
YoloV5 has an user defined layer, which is not the case in YoloV3 or YoloV4.
My advise, make absolutely sure you have the latest ncnn version on your machine. (GitHub version 20210322),
Make also sure you use the same flags during compilation and linking as in the YoloV5.cbp file, even if you not using code::blocks.

@Qengineering 作者您好，emm，您可以看一下这个 https://github.com/Tencent/ncnn/issues/1376 用这个也可以解决。
Hello author, emm, you can take a look at this https://github.com/Tencent/ncnn/issues/1376 It can also be solved with this.

这是来自QQ邮箱的自动回复邮件。

您好，您发来的邮件已经收到，我会尽快给您回复。


Module build failed: Error: Couldn't find preset "es2015" relative to directory

Had to do

$ yarn add babel-preset-es2015

to make it work.
Could you add that to the installation guide or dependency?

@tsankuanglee It's already there in the package.json. The package.json was automatically generated by vue-cli, so I think it should be installed by default.

You are right. I have no idea what happened. I tested again and it worked this time.
Thanks for the tutorial!

odd, i'm getting this too, even with it listed in devDependencies

@clemsontiger could it be our particular yarn bulid? I'm using Arch here.

maybe, i ran the command as you did to get it to work:
$ yarn add babel-preset-es2015

It's looking for my preset es2015 up under node_module/vuetable-2. I would have thunk it would be under node_modules/ all proper and stuff. I have a feeling this is over my head but thought maybe it could help someone else figure something else out.
I suspect my problem is I did something out of order. I know composered then the cp .env && art key:gen and then npm install. But then I started installing everything balked on. I've rm -rfed node_modules once. So now I just do straight npm install. It didn't work. It's balking on the first thing I mentioned up top there. If I'm in the Rhumsfeldian state where I don't know enough to know I don't know, then disregard.

SANS My whole comment above. I was looking at the package.json on the sample you posted. I see everything I was missing. I bet it'll run this time. We out.


Unable to edit form content inside slide when "swipe": false #610

#610

Similar issues have been fixed in previous releases. Please try latest release, if the issue still persist for you, please feel free to reopen the issue.


feat: replace create root reducer with root duck

Description
N/A
Changes

Removed createRootReducer replaced with createRootDuck

Checklist

[x] This PR has updated documentation
[x] This PR has sufficient testing

Comments

Addition comments for reviewers

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ARS use case: phenotypes for Angel-shaped phalango-epiphyseal dysplasia

Source issue: https://github.com/NCATSTranslator/testing/issues/33
Original query:
{
  "message": {
    "query_graph": {
      "edges": {
        "e01": {
          "object": "n0",
          "subject": "n1",
          "predicate":"biolink:has_phenotype"
        }
      },
      "nodes": {
        "n0": {
          "id": "MONDO:0007114",
          "category":"biolink:Disease"
        },
        "n1": {
          "category": "biolink:PhenotypicFeature"
        }
      }
    }
  }
 }

When querying mydisease.info directly (http://mydisease.info/v1/query?q=mondo.mondo:MONDO:0007114), we do see phenotypes listed under hpo.phenotype_related_to_disease.

Looks like this is an issue of a malformed query asking PhenotypicFeature - has_phenotype - Disease.  Modifying this query to PhenotypicFeature - phenotype_of - Disease (first query below) OR Disease - has_phenotype - PhenotypicFeature (second query below) results in a valid, non-zero response.
{
  "message": {
    "query_graph": {
      "edges": {
        "e01": {
          "object": "n0",
          "subject": "n1",
          "predicate":"biolink:phenotype_of"
        }
      },
      "nodes": {
        "n0": {
          "id": "MONDO:0007114",
          "category":"biolink:Disease"
        },
        "n1": {
          "category": "biolink:DiseaseOrPhenotypicFeature"
        }
      }
    }
  }
 }

{
  "message": {
    "query_graph": {
      "edges": {
        "e01": {
          "object": "n1",
          "subject": "n0",
          "predicate":"biolink:has_phenotype"
        }
      },
      "nodes": {
        "n0": {
          "id": "MONDO:0007114",
          "category":"biolink:Disease"
        },
        "n1": {
          "category": "biolink:DiseaseOrPhenotypicFeature"
        }
      }
    }
  }
 }

For completeness, I also confirmed that the two inverse queries return the same 15 results.


Investigate deployment of deposit and notification services in pass-docker

This depends on #578 and #580. Note that pass-core needs to be configured to start an ActiveMQ broker with tcp transport.

We need to also figure out deployment architecture in staging and prod.

deposit piece:
https://github.com/eclipse-pass/pass-docker/pull/344

This ticket has been resolved as follows:

Solution for how to run deposit-services with dspace7 is in PR: https://github.com/eclipse-pass/pass-docker/pull/344
Infrastructure architecture was determined in staging meeting with ticket created: https://github.com/eclipse-pass/main/issues/640


fe-homework 15

use clear button to remove selected items

Drift

In case of no items initially then proper message must be shown
Directory structure could be better wrt to scss files
Few logics could be optimized (eg don't use === 0)
Nice work on the UI (but when edit is option is selected that UI could be better)
The commit message's format must be proper


Auto Response Github Action

Making a note for myself here.
In preparation for Hacktoberfest 2023, we want to add an action that auto-responds to pull requests (from Camperbot) thanking the contributor, asking for patience, and letting them know that we will review the pr when we are available.
This should cut down on the mention spam.

hey will we have the "new issues" set up for 2023 Hacktoberfest opening up soon? I see 2022 issues are locked even they are marked as open

HI @ht-l1 !
All of the issues open, with the exception of this one, are available for contribution for hacktoberfest 2023.
We are still looking for quiz questions in those specific areas which is why they remained open issues.

will we have the "new issues" set up for 2023 Hacktoberfest opening up soon?

we had a few small issues open up at the beginning of the month, but all of those have since been resolved which is why they are closed.
As for why the remaining issues are locked, there were a lot of conversations going on that didn't have to deal with the issue so we moved all conversations over to GitHub discussions.
https://github.com/freeCodeCamp/Developer_Quiz_Site/discussions
Hope that answers your question.
If you have any other questions, please feel free to reach out in the GitHub discussions and we can assist you there 👍

Going to close this as we now have the ability to post reminders from Camperbot's account through Discord.


Add bsa packaging to project files

Makes it harder for people to distribute files and compile scripts, so probably not too smart after all.


CD to git root directory

Is your feature request related to a problem? Please describe.
Easier way to change nvim cwd to git root using the file browser
Describe the solution you'd like
While in file_browser, C-r would change cwd to git root directory or some other keybind
Describe alternatives you've considered
Using vim fugitve then using telescope file_browswer.
Additional context
Add any other context or screenshots about the feature request here.

Does this implement what you are looking for?
require "telescope".setup {
  extensions = {
    mappings = {
      i = {
        ["<C-r>"] = function(prompt_bufnr)
          local git_root_path =
            require("plenary.job"):new({ command = "git", args = { "rev-parse", "--show-toplevel" } }):sync()[1]
          local current_picker = require("telescope.actions.state").get_current_picker(prompt_bufnr)
          local finder = current_picker.finder
          if finder.files then
            finder.path = git_root_path
          else
            finder.cwd = git_root_path
          end
          require("telescope._extensions.file_browser.utils").redraw_border_title(current_picker)
          current_picker:refresh(finder, { reset_prompt = true, multi = current_picker._multi })
        end
      }
    }
  }
}

I think running from the finder.path instead of vim's cwd would be better (cwd option in plenary.Job).
And I would suggest we check if the folder is a git repository before changing the path.
function(prompt_bufnr)
  local current_picker = require("telescope.actions.state").get_current_picker(prompt_bufnr)
  local finder = current_picker.finder
  local git_root_path = require("plenary.job"):new({
    command = "git",
    args = { "rev-parse", "--show-toplevel" },
    cwd = finder.path,
  }):sync()[1]
  if not git_root_path then
    print "[telescope] Not in a git repository"
    return
  end
  finder.cwd = git_root_path
  require("telescope._extensions.file_browser.utils").redraw_border_title(current_picker)
  current_picker:refresh(finder, { reset_prompt = true, multi = current_picker._multi })
end

Also, I'm not sure about this:

if finder.files then
  finder.path = git_root_path
else
  finder.cwd = git_root_path
end

I would expect this action to only change the cwd, not the path.
If we consider adding this to telescope-file-browser, I think we should differentiate cwd_to_git_repo and goto_git_repo.

I think running the command from the finder.path instead of vim's cwd would be better (cwd option in plenary.Job).

Good point :) whipped this up super quick.

I would expect this action to only change the cwd, not the path.

That one is really tricky; I'd actually guess that most users would expect to change the file_browser to git root.

I think we should differentiate two actions: cwd_to_git_repo and goto_git_repo.

I have to think about this some more; ideally I'd only want to have one action for these sorts of things to avoid confusion and cluttering fb_actions. Then again, you'd always kind of have to make assumptions as to what the user wants.
I'm inclined to design these sorts of aspects more as a library for users to create their own actions for which they just have to pass the path (for which we can have separate utility functions to be created) and then users just create their own actions. We would otherwise always run in these sorts of discussions.

Sorry for asking here, meaning that to avoid error message as below, i have to start nvim inside the git repos folder than only git status will appear correctly?

@thyeun sorry i'm not understanding the context of your issue. i can help you if you create a new issue with steps to reproduce.

@jamestrew is ok, since Nvchad already answer.


Send/Receive works?

I clone this app, and run on my device.
But it seems that send/receive does not work.
And is this published to app store?

Which api did you use for this project?
Is there any way to test without real bitcoin?

Blockcypher api.
Testnet not supported, but Ill add it to roadmap, seems like its a nice to have feature
On Apr 29, 2018, 13:32 +0100, StanislavSegreev<EMAIL_ADDRESS>wrote:

Which api did you use for this project?
Is there any way to test without real bitcoin?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Use system log file for rtsold dhcp6c messages

Hi all,
Since Opnsense 19.x, the main log file used by dhcp6c is system.log, not dhcpd.log like on 18.7
I didnt understand where this change was made, but there is another log related to dhcp6c on dhcpd.log
Maybe the good way is to have a dedicated log file, but on the 19.1.3, it's better to have all dhcp6c-related logs on the same place.
Thanks

Thanks, merged!


Module breaks PHP

No idea why, but I have verified this on two linux distributions. Apache PHP worked before module installation and after module removal. If you cannot reproduce this I can give more info.

I know it's been a while, but by any chance could you provide additional info? I'm maintaining a fork of this module and would like to migrate open issues to it.

(Posting from work account)
@jchampio I was using prefork (no pthreads) apache PHP module. I stopped using websocket for that project soon after I opened this issue so I'm afraid I can't provide much help. I got apache and PHP working without websockets though, so I feel like this should be a reproducible issue.

Okay. I have very little experience with mod_php -- when you said "breaks", do you remember how? Hangs, crashes, errors thrown? Either way, thanks for the info; I'll try to keep an eye out for interactions with mod_php.

I don't remember. Good luck!


[Bug Report] The table scroll bar is not displayed when the fixed property is set by the table component el-table-column.

Element UI version
2.10.0
OS/Browsers version
chrome
Vue version
2.6.10
Reproduction Link
https://codepen.io/uiexp/pen/gNXYPW
Steps to reproduce
无
What is Expected?
滚动条可见
What is actually happening?
滚动条不见了

请问解决了吗

pr welcome


Default to pandas for multilevel index and edge cases

What do these changes do?

Related issue number

[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff
[x] passes black --check modin/

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin/281/
Test FAILed.


Implemented parseTuple() function

this feature was added unkowingly by me in a previous commit. Closing this as this is no longer required. Thanks for the effort.


How to push to existing repo in specific folder?

@ajdruff  I see in readME under Step 3: ... you mentioned about pushing to new repo right. I would like to push to existing repo to new folder...can we do this?

i have used git subtree


Web Page Error

The web page is not rendering.

@Picodes10 that is the backend deployment link , check the frontend link.

As there isn't any issue with the rendering,so we are closing this issue


Usage with Turbo::Broadcastable

Looking for a good practice when using decorated objects inside templates broadcasted with Turbo::Broadcastable.
Since the rendering happens in Turbo::Streams::ActionBroadcastJob, the objects are getting serialised (#817) and the decoration is lost.
class Clearance < ApplicationRecord
  belongs_to :petitioner, class_name: "Contact"
  belongs_to :examiner,   class_name: "User"

  after_create_commit :broadcast_later

  private

    # Sends <turbo-stream action="replace" target="clearance_5"><template>
Other partial
</template></turbo-stream>
    # to the stream named "identity:2:clearances"
    def broadcast_later
      broadcast_replace_later_to examiner.identity, :clearances, target: self, partial: "clearances/other_partial", locals: { clearance: self }
    end
end

This is the quick solution I'm using currently, overriding the Turbo::Streams::ActionBroadcastJob job, as pointed by dhh in https://github.com/hotwired/turbo-rails/issues/190
class Turbo::Streams::ActionBroadcastJob < ApplicationJob
  def perform(stream, action:, target:, **rendering)
    rendering[:locals]&.transform_values! do |v|
      v.decorate
    rescue Draper::UninferrableDecoratorError, NoMethodError
      v
    end

    Turbo::StreamsChannel.broadcast_action_to stream, action: action, target: target, **rendering
  end
end


Feature/1 mainscreen

The main screen with all the basics

title
subtitle
button to start the game
and an empty new scene
start button will move player to the empty scene

preview

wtf I was supposed to push this to my repo lol


Hot Reloading: SelfHosted Component hot reloading

Part of #1172
Adds hot reloading functionality to Daprd, which is gated behind the HotReload preview feature.
If enabled, Daprd in Selfhosted mode will watch for resource updates from watching the resource directory(s). If a resource is detected as changed (spec is different to what is currently loaded), then Dapr will close/create/update the resource.
Supports Component except HTTP middlware which requires further changes to the HTTP server handler machinery. A warning is thrown if hot reloading is enabled and a HTTP middleware is updated.
The hot reloader reconciler is made generic to enable other resource types to be added in future.

When running in standalone mode, the disk loader watches the directories passed by --resources-path for updates to yaml files containing Components.
When an event occurs, the reconciler and differ are responsible for determining whether any resources have been created, updated, or deleted, by comparing the local store specs with that of the remote. If any have changed, the resource is closed (if it exists), and then re-initialized (if it exists). A resource will only be closed if it has been deleted, only initialized if it has been created, and closed & initialized if it has been updated.
We consider a resource to have changed generally if anything apart from its Kubernetes metadata or type meta object meta has changed, and therefore needs some kind of reloading.

Currently, if a reloading component errors and spec.ignoreErrors=false then Daprd will gracefully close, like a component loaded at startup today. It is intended that in future the component will be re-inited on a backoff queue in future in the case of errors, even if spec.ignoreErros=true.
HTTP middleware component hot reloading is not supported as it requires further changes to the HTTP server handler machinery, and I didn't want to grow this PR further.
The differ, loader, and reconciler have been made generic so that they can be reused when other resource types (HTTPEndpoint, Subscriptions etc.) can be added to hot reloading in future.
To use the HotReloading feature, which is currently only available as an alpha feature in Selfhosted mode, users need to add the following Configuration to the target Daprd;
apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: hotreloading
spec:
  features:
  - name: HotReload
    enabled: true

@JoshVanL thanks for your great job!
I see you close two PRs before, which make some conversations missing. Could we make changes as much as possible in one place to avoid reviewers starting over every time?
ping @ItalyPaleAle @mukundansundar @cicoyle

@JoshVanL thanks for your great job!
I see you close two PRs before, which make some conversations missing. Could we make changes as much as possible in one place to avoid reviewers starting over every time?
ping @ItalyPaleAle @mukundansundar @cicoyle

Thanks @daixiang0 :)
This was done intentionally as the original hot reloading PR has diverged significantly enough (this PR is only selfhosted, doesn't include middleware, doesn't include HTTPEndpoints, has loads of integration tests) that force pushing to the same PR would cause more confusion than it was worth imo.

This fails if the component namespace is defined, but not set to default. It even prevents the component from being loaded at all now.

@berndverst is this not expected behaviour? daprd in self-hosted mode does still have the concept of namespacing (though this isn't documented well and not clear to the user). The namespace of daprd is set via the environment variable NAMESPACE which itself is set by Kubernetes so is transparent to the user but still clear through context. daprd will default the namespace to default when the env var is not set.
If it is the case that daprd would previously consume Components through file in seflhosted mode, even if the namespace set did not match the NAMESPACE env, then this can be considered a breaking change. Please let me know if this is the case and if it is a breaking change we do not want to accept.


DDS: Cisco Secure Email Threat Defense: Crawler Integration without Assets

What does this PR do?
PR includes skeleton of Cisco Secure Email Threat Defense integration without any assets like dashboards, image, README content, etc.
Motivation
This is beta release of crawler integration and is intended for internal testing before going live. As per @nathanmadams's suggestion, we are planning to raise separate PR with assets and all necessary information later.
Additional Notes
Only crawler-based integration related changes are included in this PR.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
[ ] If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@Wyrine Previously for Cisco Secure Endpoint, we have received comment to to keep source_type_name as natural title-cased. Can you please let us know which one to keep?

natural title-cased is correct. Apologies for the confusion. Please fix merge conflicts and then I will approve

@Wyrine Have fixed merge conflicts.


Remove all MXNet dependencies from core

Issue #, if available:
Description of changes:
I've also pulled all try_import_XYZ into core, which is where they may be needed.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

What is missing here are changes to Jenkins etc in order to not require MXNet for core. I lack the skills to do that

All tests in core/tests/unittests pass in a venv without mxnet being installed.

Thanks for the PR! Could you rebase with mainline? Files were moved slightly in Tabular recently, but they should stay stable for awhile now.
The change that occurred is that files in tabular/utils/ml/ and tabular/utils/ were moved directly to tabular/


Fix mod crash when trying to register an existing material with Tinker's Construct TinkerRegistry.

Changed build.gradle so that dependencies are, for the most part, loaded from their maven repositories.
Changed the materials to private static final instead of public static. They are not changed in the code after being initialized. They are also only accessed in the class they were declared in. Renamed the corresponding fields to correspond with the naming conventions of constants.
Use of literals is discouraged. As such, replaced the literal with the material name used when checking if material is blacklisted, with the corresponding Material#identifier.
Made changes to the code to first check if material exists before trying to register it.
Made changes to the code to first check if the material was registered by us, before trying to make changes to it.
Small code cleanups.

Would also appreciate it if you could add the hacktoberfest tag to your repository assuming you find this PR helpful.

It's usually a good idea to contact someone before starting work on a pull request to see if they're actually intrested in pulling the changes you want to make.
I hate to say this but I don't really like most of the changes you've made here, I'll go through them;

I prefer to load dependencies from a local folder since an external repository could break at any time, this recently happened to tinkers construct. I also don't like that you added way too many mods that materialis does not depend on to the dependency list,
I prefer to keep my variables public and nonfinal in case an external mod wants to modify them, I've made a few addons for mods and it always bothers me when a variable I need to modify is not public or final. I know that's probably against best practices but as far as I know there aren't any actual benefits to making things private or final other than to prevent people from messing with them.
I'm not sure what I was thinking when I wrote that blacklisting code, I should have just used the material name from the material like you did.
I have considered checking if a material is registered before registering mine, but I decided against it because then most people who use the mod will not realise materialis has that material and continue to use the material from another mod, most of which are in my opinion inferior (I'm mostly talking about plustic and moar tinkers here).

I prefer to load dependencies from a local folder since an external repository could break at any time, this recently happened to tinkers construct. I also don't like that you added way too many mods that materialis does not depend on to the dependency list,
I'd like to point out that that's what your local maven is for. As for the added dependencies, I forgot to comment those out. They were there only to check how Materialis would behave in a TiC add-on rich environment.

I prefer to keep my variables public and nonfinal in case an external mod wants to modify them, I've made a few addons for mods and it always bothers me when a variable I need to modify is not public or final. I know that's probably against best practices but as far as I know there aren't any actual benefits to making things private or final other than to prevent people from messing with them.

Didn't know that was your intention

I'm not sure what I was thinking when I wrote that blacklisting code, I should have just used the material name from the material like you did.

Would you prefer I open a PR with just these changes?

I have considered checking if a material is registered before registering mine, but I decided against it because then most people who use the mod will not realise materialis has that material and continue to use the material from another mod, most of which are in my opinion inferior (I'm mostly talking about plustic and moar tinkers here).

Afaik those people will quite likely look at the crash log, see it was caused by Materialis and drop it. Modpack makers and other modders might have more patience and work out the kinks and compatibility issues.
I'm the original author of Armory Expansion and the current maintainer for Moar Tinkers. Moar Tinkers is pending a rewrite that will switch it over to Armory Expansion's system, thus allowing easily changing the stats and traits, as well as disabling specific material parts or the material altogether.
All in all though, I don't consider this effort useless, I went through someone else's code and saw how they did something I'm also doing. It gave me a fresh perspective.


Missing holiday in Augsburg/Bavaria/Germany

Hello,
the city Augsburg has a unique holiday on 8th August each year, which is not celebrated in the rest of bavaria or germany.
https://en.wikipedia.org/wiki/Public_holidays_in_Germany
https://de.wikipedia.org/wiki/Augsburger_Hohes_Friedensfest
https://www.augsburg.de/kultur/festivals/hohes-friedensfest

Hi @AndiLeni Thank you very much for this issue. Yasumi only is designed to record holidays for countries and subdivisions (such as states, provinces, etc.) but not cities. We can add this holiday to Bavaria, but it would mean Yasumi considers it a holiday for the entire Bavaria region.

Oh, I am sorry. I was not aware of this and just searched the issues fur duplicates.
I will close this issue since this date should not be a holiday everywhere in bavaria.
Thanks and kind regards


Fix default value for DefaultToolchain

fixes #71

Wait, that's not elan's default. The parameter should not be passed at all by default.

Hah, I was a few seconds too slow. Looks better!


cilium: various xdp related follow-ups

cilium status output
CI tests
Hide generic XDP for testing only

test-me-please

test-me-please

unrelated vagrant issue:
 97 9861M   97 9609M    0     0   100M      0  0:01:38  0:01:35  0:00:03  112M
 98 9861M   98 9721M    0     0   100M      0  0:01:37  0:01:36  0:00:01  112M
 99 9861M   99 9833M    0     0   100M      0  0:01:37  0:01:37 --:--:--  112M
100 9861M  100 9861M    0     0   100M      0  0:01:37  0:01:37 --:--:--  112M
11:27:23  The machine index which stores all required information about
11:27:23  running Vagrant environments has become corrupt. This is usually
11:27:23  caused by external tampering of the Vagrant data folder.
11:27:23
11:27:23  Vagrant cannot manage any Vagrant environments if the index is
11:27:23  corrupt. Please attempt to manually correct it. If you are unable
11:27:23  to manually correct it, then remove the data file at the path below.
11:27:23  This will leave all existing Vagrant environments "orphaned" and
11:27:23  they'll have to be destroyed manually.
11:27:23
11:27:23  Path: /root/.vagrant.d/data/machine-index/index
11:27:24  box locked or unavailable, adding box from vagrant cloud
11:27:25  The machine index which stores all required information about
11:27:25  running Vagrant environments has become corrupt. This is usually
11:27:25  caused by external tampering of the Vagrant data folder.
11:27:25
11:27:25  Vagrant cannot manage any Vagrant environments if the index is
11:27:25  corrupt. Please attempt to manually correct it. If you are unable
11:27:25  to manually correct it, then remove the data file at the path below.
11:27:25  This will leave all existing Vagrant environments "orphaned" and
11:27:25  they'll have to be destroyed manually.
11:27:25
11:27:25  Path: /root/.vagrant.d/data/machine-index/index
Post stage

Coverage decreased (-0.01%) to 46.687% when pulling ee37c1eab79b531494b10ace89e150f6aadc8f60 on pr/xdp-follow-ups into f5425fec71bff6762a5bcc5dc3f3078728020141 on master.

test-me-please

provisioning issue again:
[Pipeline] sh
12:37:23  + /usr/local/bin/add_vagrant_box /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/vagrant_box_defaults.rb
12:37:23  The machine index which stores all required information about
12:37:23  running Vagrant environments has become corrupt. This is usually
12:37:23  caused by external tampering of the Vagrant data folder.
12:37:23  [...]

test-me-please

Hit flake #10821

test-focus K8sService.*

test-focus K8sService.*

test-me-please

Hit flake #10821

test-focus K8sService.*

Cilium-Tests-With-Kernel provision issue
20:45:04  Checking for older boxes...
20:45:04  No old versions of boxes to remove...
20:45:04  VBoxManage: error: Machine '9c85c1b7-53ab-4012-837a-749c5acf0af8' is not currently running
20:45:04  0%...10%...20%...30%...40%...
20:45:04  Progress state: VBOX_E_OBJECT_IN_USE
20:45:04  VBoxManage: error: Machine delete failed
20:45:04  VBoxManage: error: Cannot close medium '/root/VirtualBox VMs/ubuntu-18.04.4-amd64-11_1586464889876_63179/ubuntu-18.04.4-amd64-11-disk001.vmdk' because it has 1 child media
20:45:04  VBoxManage: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), component MediumWrap, interface IMedium
20:45:04  VBoxManage: error: Context: "RTEXITCODE handleUnregisterVM(HandlerArg*)" at line 162 of file VBoxManageMisc.cpp
20:45:04  VBoxManage: error: Machine 'ab8f39a8-4e2d-4dc1-bb3e-da306b749f17' is not currently running
20:45:06  0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
20:45:06  Clean docker images from registry

test-with-kernel

test-focus K8sService.*

vagrant issue again in CI...

test-focus K8sService.*

test-focus K8sService.*

test-me-please

vbox error in CI:
00:31:39  Stderr: VBoxManage: error: Failed to create the VirtualBox object!
00:31:39  VBoxManage: error: Document is empty.
00:31:39  VBoxManage: error: Location: '/root/.config/VirtualBox/VirtualBox.xml', line 1 (0), column 1.
00:31:39  VBoxManage: error: /home/vbox/vbox-6.0.18/src/VBox/Main/src-server/VirtualBoxImpl.cpp[624] (nsresult VirtualBox::init())
00:31:39  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component VirtualBoxWrap, interface IVirtualBox
00:31:39  script returned exit code 143

test-me-please

Hit #10929 and #10930, will restart ginkgo.

restart-ginkgo

test-me-please

test-focus K8sService.*

Backported only 7d1a16f08c253add72ca3f4a13f86de9869c64ca to v1.7 (PR: https://github.com/cilium/cilium/pull/13595) as https://github.com/cilium/cilium/pull/13532 depended on this commit.


863 unit testing model importexport

This UT covers model import/export for following models.
RandomForestRegressor,
RandomForestClassifier,
DecisionTreeRegressor,
DecisionTreeClassifier,
DummyTreeRegressor,
XGBRegressor,
XGBClassifier,
Ridge,
Lasso,
ElasticNet,
LinearRegression,
LinearSVR,
PoissonRegressor,
AR,
MA,
ARMA,
ARIMA,

@vikash018 I've corrected many points but still the tests are not passing.
TODO:

Do not install tensorflow for py312 (try to change the script and the requirements for that)
Try to solve the errors with your tests (look at the Py311 kernel).

@vikash018 I've corrected many points but still the tests are not passing. TODO:

Do not install tensorflow for py312 (try to change the script and the requirements for that)
Try to solve the errors with your tests (look at the Py311 kernel).

@oualib - Thanks for fixing it. for model export, i am trying to create export model inside /tmp/ folder. do we need to have some extra permission?
Cannot create directory: [/tmp/test_fKzm/vpy_model/]
"SELECT EXPORT_MODELS('/tmp/test_fKzm', 'test_fKzm.vpy_model')"

@vikash018 I've corrected many points but still the tests are not passing. TODO:

Do not install tensorflow for py312 (try to change the script and the requirements for that)
Try to solve the errors with your tests (look at the Py311 kernel).

@oualib - Thanks for fixing it. for model export, i am trying to create export model inside /tmp/ folder. do we need to have some extra permission?
Cannot create directory: [/tmp/test_fKzm/vpy_model/]
"SELECT EXPORT_MODELS('/tmp/test_fKzm', 'test_fKzm.vpy_model')"

@afard please help @vikash018 asap we need to fix this today