seg fault postgresql

I've had postgresql seg fault (and go into recovery mode) three times since switching one of our main materialized views to this new foreign data wrapper at the end of last week.
I usually configure materialized views on top of foreign tables, in particular when the FDW connects to a slow-to-query data store such as Treasure Data.
All three times the seg faults have occurred was while doing a concurrent refresh of one of those materialized views.  Each time was the first time I tried to refresh one of the new materialized views which were built on the new foreign data wrapper.  (I had no problem building the materialized views, this seems to come up on concurrent refresh.)
syslog.1:Apr 23 19:16:36 core-gce kernel: [1227591.706735] postgres[11068]: segfault at 7fffac700647 ip 00007fffac700647 sp 00007fffac6fff68 error 15
syslog.1:Apr 23 19:25:23 core-gce kernel: [1228119.372219] postgres[11067]: segfault at 7fffac700647 ip 00007fffac700647 sp 00007fffac6fff68 error 15
syslog.1:Apr 24 03:10:03 core-gce kernel: [1255999.025109] postgres[30642]: segfault at 7fffac700fe7 ip 00007fffac700fe7 sp 00007fffac700908 error 15
All three are at the same address.
We are running PostgreSQL 9.6.2 on Ubuntu 16.04.  I built it with the Rust 1.7.0.
Since it takes 12 hours to build these materialized views, I thought I would check in here before I back out and redeploy them with the multicorn fdw instead (like they were before).

@rotten Thanks for reporting the issue.
I tried to reproduce the issue, but I've not succeeded in reproducing it.
Can you give me the following information?

How long did it take to crash after starting REFRESH MATERIALIZED VIEW CONCURRENTLY?
Are there any log messages related to this issue in PostgreSQL's log files?
How many rows does the materialized view have?

Also, Rust 1.7 sounds a bit too old to me. Although I'm not sure Rust version is related, but I think it might be worth trying to upgrade Rust.

It took an hour or two after starting the refresh before it crashed.
The table has 45,527,173 rows in it and 26 columns, which doesn't seem too terribly big as far as these things go.
You are right, that isn't the version of Rust I used to build it.  That version didn't work.  (That was the latest version that Ubuntu supports in their Repo for 16.04).  The version I used was:
/root/.cargo/bin # ./rustc -V
rustc 1.16.0 (30cf806ef 2017-03-10)
This is the only thing in the postgresql logs other than the usual auto-recovery log entries:
2017-04-24 03:10:04.126 UTC     LOG:  server process (PID 30642) was terminated by signal 11: Segmentation fault
2017-04-24 03:10:04.126 UTC     DETAIL:  Failed process was running: refresh materialized view concurrently current_web_responses;
2017-04-24 03:10:04.126 UTC     LOG:  terminating any other active server processes

I refreshed these same materialized views last week with the multicorn FDW and they worked without any issues.  There have been no other significant changes to the data or database or server other than I added 3 new (varchar) columns to the view when I switched the FDW.
I thought I was successfully refreshing some smaller tables this morning (same order of magnitude of rows, but many fewer columns), however I just realized those are still using the multicorn FDW.

I finally succeeded in reproducing this crash with several times tries.
The stack trace in the core file is as follows though I forget to enable debug symbol with the PostgreSQL.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000000000003f in ?? ()
(gdb) bt
#0  0x000000000000003f in ?? ()
#1  0x00007f5b169417b7 in errfinish ()
#2  0x00007f5b1670969c in ExecRefreshMatView ()
#3  0x00007f5b16852a3f in ?? ()
#4  0x00007f5b16851e89 in standard_ProcessUtility ()
#5  0x00007f5b10567868 in CStoreProcessUtility (parseTree=<optimized out>, queryString=0x7f5b1716dd00 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;", context=PROCESS_UTILITY_TOPLEVEL, paramListInfo=0x0,
    destReceiver=0x7f5b1716eac0, completionTag=<optimized out>) at cstore_fdw.c:247
#6  0x00007f5b1684efd1 in ?? ()
#7  0x00007f5b1684fc16 in ?? ()
#8  0x00007f5b168507e5 in PortalRun ()
#9  0x00007f5b1684e2dd in PostgresMain ()
#10 0x00007f5b165f075d in ?? ()
#11 0x00007f5b167f348b in PostmasterMain ()
#12 0x00007f5b165f1462 in main ()

According to the stack trace, it looks like this crash was related to cstore_fdw in my case.
@rotten Are you using cstore_fdw in the PostgreSQL instance?

We are not using the cstore_fdw.  The only other fdw, besides td_fdw, that we have configured is one for MongoDB which is a multicorn one.  We are using my fork of the yam_fdw for that.  My fork has better handling of some of the data types than the original yam_fdw.
My database crashed again overnight last night when one of our automatied processes tried to refresh one of the new materialized views, so I can still reproduce it too.  :-(

Got detailed stack trace with PostgreSQL (REL9_5_STABLE: dba1f310a564e8dc3496cd5ddec14ab6645ffd15)
(gdb) bt
#0  0x0000000000ce6f88 in ?? ()
#1  0x000000000077f337 in errfinish (dummy=<optimized out>) at elog.c:432
#2  0x000000000056e45c in refresh_by_match_merge (save_sec_context=0, relowner=16385, tempOid=82067, matviewOid=58425) at matview.c:699
#3  ExecRefreshMatView (stmt=stmt@entry=0xd61fc8, queryString=queryString@entry=0xd61578 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;", params=params@entry=0x0, completionTag=completionTag@entry=0x7fff7ed21290 "")
    at matview.c:295
#4  0x00000000006a1e7c in ProcessUtilitySlow (parsetree=parsetree@entry=0xd61fc8, queryString=queryString@entry=0xd61578 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;", context=<optimized out>, params=params@entry=0x0,
    completionTag=completionTag@entry=0x7fff7ed21290 "", dest=0xd622f8) at utility.c:1396
#5  0x00000000006a1341 in standard_ProcessUtility (parsetree=0xd61fc8, queryString=0xd61578 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;", context=<optimized out>, params=0x0, dest=0xd622f8,
    completionTag=0x7fff7ed21290 "") at utility.c:892
#6  0x00007fdfe9dfede7 in CStoreProcessUtility (parseTree=<optimized out>, queryString=0xd61578 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;", context=PROCESS_UTILITY_TOPLEVEL, paramListInfo=0x0, destReceiver=0xd622f8,
    completionTag=<optimized out>) at cstore_fdw.c:247
#7  0x000000000069ed91 in PortalRunUtility (portal=0xd03ee8, utilityStmt=0xd61fc8, isTopLevel=<optimized out>, dest=0xd622f8, completionTag=0x7fff7ed21290 "") at pquery.c:1183
#8  0x000000000069f925 in PortalRunMulti (portal=portal@entry=0xd03ee8, isTopLevel=isTopLevel@entry=1 '\001', dest=dest@entry=0xd622f8, altdest=altdest@entry=0xd622f8, completionTag=completionTag@entry=0x7fff7ed21290 "")
    at pquery.c:1314
#9  0x00000000006a0389 in PortalRun (portal=portal@entry=0xd03ee8, count=count@entry=9223372036854775807, isTopLevel=isTopLevel@entry=1 '\001', dest=dest@entry=0xd622f8, altdest=altdest@entry=0xd622f8,
    completionTag=completionTag@entry=0x7fff7ed21290 "") at pquery.c:812
#10 0x000000000069e213 in exec_simple_query (query_string=0xd61578 "REFRESH MATERIALIZED VIEW CONCURRENTLY mv_city ;") at postgres.c:1104
#11 PostgresMain (argc=<optimized out>, argv=argv@entry=0xce58c8, dbname=0xce5778 "datatank", username=<optimized out>) at postgres.c:4051
#12 0x000000000046712a in BackendRun (port=0xd0c170) at postmaster.c:4255
#13 BackendStartup (port=0xd0c170) at postmaster.c:3929
#14 ServerLoop () at postmaster.c:1699
#15 0x0000000000649b99 in PostmasterMain (argc=argc@entry=3, argv=argv@entry=0xce49a0) at postmaster.c:1307
#16 0x0000000000467bf8 in main (argc=3, argv=0xce49a0) at main.c:228

We are not using the cstore_fdw
I see. Thanks.

I've observed the followings about this issue.

It's reproduced without cstore_fdw.
Fetching query result from Treasure Data using td-client-rust itself finished successfully
After fetching the query result, memory usage (RSS) was increasing and finally reached 3GB. And then it crashed

I'll compare the difference of behaviours in memory consumption between treasuredata_fdw and td_fdw (Multicorn).

@rotten I fixed one potential cause of this issue at https://github.com/komamitsu/treasuredata_fdw/pull/15 and confirmed this issue wasn't reproduced with the change in my testing environment.
Can I ask you to try the latest master branch? If this change works in your database, I'll release a new version 1.1.0. If it's hard for you to try that, I'll just release a new version.

Thanks, I have a bunch of other maintenance this weekend so I won't be able to pick up the newly recompiled extension (by restarting the database) until next weekend at the soonest.  I should be able to test the fix on my new Ubuntu laptop within the next couple of days though.  (I'm still setting it up there.)  I'll let you know how it goes.
Meanwhile, we had to revert to the Multicorn FDW because not having array support yet is a showstopper for us being able to use this FDW for most of our treasure data tables.

Okay. I'm closing this issue for now. But if this issue is still reproduced on your side, reopen the issue. Thanks

@komamitsu how to show the completionTag ? And what information we get from the completionTag? Thank you


CI for Publishing Updates to Firefox, Chrome, and Edge (?)

I already have this setup for another one of my extensions, using publish-browser-extension.
I'd prefer this be a single bash script though, that way it can be ran locally and though github actions.

Closed by #12


ImportError: Importing numba_dppy failed when numba-dppy is installed from the intel conda channel

I am trying to install numba-dppy in a dedicated conda environment with the following command:
$ conda create -n numba-dppy -c intel numba-dppy
Collecting package metadata (current_repodata.json): done
Solving environment: done
[...]
$ conda activate numba-dppy
(numba-dppy) $ python -c "import numba_dppy"
No device of requested type available. Please check https://software.intel.com/content/www/us/en/develop/articles/intel-oneapi-dpcpp-system-requirements.html -1 (CL_DEVICE_NOT_FOUND)
/home/ogrisel/mambaforge/envs/numba-dppy/lib/python3.9/site-packages/numba_dppy/config.py:57: UserWarning: Please install dpctl 0.8.* or higher.
  warnings.warn(msg, UserWarning)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ogrisel/mambaforge/envs/numba-dppy/lib/python3.9/site-packages/numba_dppy/__init__.py", line 528, in <module>
    raise ImportError("Importing numba_dppy failed")
ImportError: Importing numba_dppy failed

but dpctl 0.11.1 was installed in that env, here is the output of the conda list command:

# Name                    Version                   Build  Channel
bzip2                     1.0.8                hb9a14ef_9    intel
ca-certificates           2021.10.26           h06a4308_2    intel
certifi                   2021.10.8        py39h06a4308_0    intel
dpcpp-cpp-rt              2022.0.1             intel_3633    intel
dpcpp_cpp_rt              2022.0.1             intel_3633    intel
dpctl                     0.11.1           py39hbd01409_0    intel
dpnp                      0.9.0            py39h2493cab_0    intel
icc_rt                    2022.0.1             intel_3633    intel
intel-cmplr-lib-rt        2022.0.1             intel_3633    intel
intel-cmplr-lic-rt        2022.0.1             intel_3633    intel
intel-opencl-rt           2022.0.1             intel_3633    intel
intel-openmp              2022.0.1             intel_3633    intel
intelpython               2022.0.0                      0    intel
libffi                    3.3                          14    intel
libgcc-ng                 9.3.0              hdf63c60_101    intel
libllvm11                 11.0.0               h3826bc1_0    intel
libstdcxx-ng              9.3.0              hdf63c60_101    intel
llvm-spirv                11.0.0               h4616538_1    intel
llvmlite                  0.37.0           py39h188ca7a_1    intel
mkl                       2022.0.1              intel_117    intel
mkl-dpcpp                 2022.0.1              intel_117    intel
mkl-service               2.4.0           py39h4119f30_10    intel
mkl_fft                   1.3.1            py39h8344fd8_7    intel
mkl_random                1.2.2            py39h4ac99d2_7    intel
mkl_umath                 0.1.1           py39h03fa629_17    intel
numba                     0.54.1           py39h671cb0e_3    intel
numba-dppy                0.17.2           py39h31cfeb5_0    intel
numpy                     1.21.2           py39hec4e512_7    intel
numpy-base                1.21.2           py39h40791c5_7    intel
openssl                   1.1.1l               h7f8727e_0    intel
packaging                 21.0             py39h1546d3d_4    intel
pip                       21.2.4           py39h06a4308_0    intel
pyparsing                 3.0.4              pyhd3eb1b0_0    intel
python                    3.9.7                h718aa4a_4    intel
setuptools                58.0.4           py39h06a4308_0    intel
six                       1.16.0             pyhd3eb1b0_0    intel
spirv-tools               2020.5               h6bb024c_2    intel
sqlite                    3.36.0               hb9a14ef_3    intel
tbb                       2021.5.0              intel_707    intel
tbb4py                    2021.5.0         py39_intel_707    intel
tk                        8.6.10               h8e2d9d6_3    intel
wheel                     0.37.0             pyhd3eb1b0_1    intel
xz                        5.2.5                h74280d8_2    intel
zlib                      <IP_ADDRESS>             h1e99aa7_5    intel

And here is the output of lscpu:

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          8
On-line CPU(s) list:             0-7
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           140
Model name:                      11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
Stepping:                        1
CPU MHz:                         2800.000
CPU max MHz:                     4700,0000
CPU min MHz:                     400,0000
BogoMIPS:                        5606.40
Virtualization:                  VT-x
L1d cache:                       192 KiB
L1i cache:                       128 KiB
L2 cache:                        5 MiB
L3 cache:                        12 MiB
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_know
                                 n_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs
                                  ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec
                                 xgetbv1 xsaves split_lock_detect dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2
                                 intersect md_clear flush_l1d arch_capabilities

This might be related to a similar problem on dpnp:
https://github.com/IntelPython/dpnp/issues/1149

Note that I install the Python env from the APT package of oneAPI basetoolkit and configure the environment variables with . /opt/intel/oneapi/setvars.sh, then I can import numba_dppy on this same machine.
However, having to use a mix of 2 package managers to install numba_dppy is preventing to use this library in traditional deployments that only rely on conda (or pip) and therefore harming the adoption of this library.

I tried again after setting SYCL_ENABLE_HOST_DEVICE=1:
$ SYCL_ENABLE_HOST_DEVICE=1   python -c "import numba_dppy"
/home/ogrisel/mambaforge/envs/dpnp/lib/python3.9/site-packages/numba_dppy/config.py:50: UserWarning: dpctl could not find any non-host SYCL device on the system. A non-host SYCL device is required to use numba_dppy.
  warnings.warn(msg, UserWarning)
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/ogrisel/mambaforge/envs/dpnp/lib/python3.9/site-packages/numba_dppy/__init__.py", line 528, in <module>
    raise ImportError("Importing numba_dppy failed")
ImportError: Importing numba_dppy failed

so at least the error message makes sense now. However I do not understand why the sycl runtime does not find a non-host device on this machine:
lspci | grep Iris
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)

do I need to install additional drivers (this is a Ubuntu 21.10 system)?

For the latter point, installing additional drivers as explained here https://dgpu-docs.intel.com/installation-guides/ubuntu/ubuntu-focal.html fixed the problem.
Not that I used the focal / 20.04 apt repo on my impish / 21.10 system and it worked.

So to summarize:

the existing exception message is misleading because it mentions a dpctl dependency that is already fine
it should probably at least tell the user how to enable the CPU backend by setting the SYCL_ENABLE_HOST_DEVICE=1 or do it automatically if no other device is available
it should probably point the user to some documentation page to install drivers for GPU devices (either the existing page at https://dgpu-docs.intel.com/installation-guides/index.html but this only covers Intel GPU devices or new page with pointers to the documentation for various vendors that expected to be supported by numba-dpex/SYCL).

Apparently the misleading ImportError exception is no longer raised in numba-dpex (see: https://github.com/IntelPython/numba-dpex/issues/776#issuecomment-1253585774 for instance).
I opened https://github.com/IntelPython/numba-dpex/issues/777 to document the remaining usability improvements to help the user find out why no SYCL device is found by numba-dpex.


added toggleViewActions to gui's toolBarView

What are the issues this pull addresses (issue numbers / links)?
#516 #550
Did you add tests to cover your changes (yes/no)?
No
Did you update the documentation accordingly (yes/no)?
No
Did you read the CONTRIBUTING document (yes/no)?
Yes
Summary
Used every dockWindow's toggleViewAction() function to add toggle QAction to MetalGUI's toolBarView
Details and comments
Now includes toggle QAction for dockLibrary

Great!!
Maybe move the Library to the second slot from the top down


Fix testGetMicrosoftTimeZoneNameBad() test case

Hi @vboctor, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@vboctor Maybe this test should be splitted and annotated with @Test(expected = ...) what do you think?

@vboctor is this PR still needed?


Visual areas

Creating pull request to add the docs-visual-areas extension as a new extension to be published as part of the authoring pack.
Consistency checks

[x] followed overall consistency of the rest of the packages
[x] followed same eslint, except index.ts usage
[x] followed same prettier
[x] followed same webpack
[x] followed same script usage
[x] updated root package.json file for lint and compile steps

Visual Areas:

Easily keep track tabbed and zoned content with the following features:

Color coded gutters: Each tabbed or zoned section in your article gets a unique gutter color.

Area tooltips: Hovering over a line in a section reveals a tool tip with the area label.

Status bar: The status bar stays updated with the section name when your cursor is inside a tabbed or zoned section.

Demo video

Settings

Property
Description
Default

gutterIndicatorHeight
The height the of gutter indicator.
100

gutterIndicatorOffset
The offset from the left for the gutter indicator.
12

gutterIndicatorOpacity
The opacity percentage of the gutter indicator.
60

gutterIndicatorWidth
The width the of gutter indicator.
4

cc @craigshoemaker @kgremban @IEvangelist

Awesome, thank you @johnpapa! Hey @bharney0 - we need a CI run.

/azp run

@meganbradley can you review the description in this PR for getting the OK on adding this new extension to the Docs Authoring Pack?
Thank you @johnpapa for your contribution! Im working on reviewing the code and once that is setup I will need to create a CI pipeline for publishing to the VSCode Marketplace and future changes.

This looks great @johnpapa! We're currently under water at the moment, but we'll get this reviewed as soon as we can.

/azp run

Hey @johnpapa thanks again for the contribution. Just getting around to this. Sorry for the delay. Future PRs should be reviewed within a few days. Our Org was involved in a security audit which put a hold on other work. A few things I noticed from the code:

Can you remove the .DS_Store folder
Please avoid upper case file names for the test data

Overall the code looks well put together, however when I try to use the extension in the extension host I dont see the visual areas? Is there something I am doing wrong?

As far as next steps, I built a CI pipeline and need to run it under main branch for component governance checks and CodeQL analysis. I Just need to setup a CD pipeline to deploy under the Microsoft VS Marketplace.

Hi - thanks for the feedback, I will review this and reply soon.

@bharney0 - I made the fixes you requested to the PR and pushed them up.
I tried the extension locally and it worked for me (see below). Perhaps you are trying it on a file that is not an *.md ?

Hey @johnpapa this is the error I run into when I try to run the Extension Host

I also tried packaging it up into a .vsix for @meganbradley to test out but I am still getting the same error.

Let me know if I can help in any way, I would love to get this deployed to the authoring pack and get some more downloads.
Also can you resolve the package-lock.json conflict or even remove the package-lock so I can test the CI build pipeline to make sure we dont have any component governance issues?

@johnpapa I just changed some configuration settings in the .vscode file for tasks and launch.json files and updated the output directory for main in the package.json and everything seems to be working now.

I am going to send over a .vsix file for our PM to check out the extension and then merge it into main so we can get a build to check for component governance and security related code analysis. Then we should be able to publish to the market place. Thanks again for your patience. Hopefully in the future with other PRs we will be quicker to get things moving.

Thanks @bharney0. I am OOO til tomorrow, so I appreciate you keeping this moving forward.
I tried to mirror the extension after some of the others I saw in this repo, but I agree that some contribution guidelines and checklists may be incredibly helpful for future contributions.
No worries on the time this took. Y’all have been communicative and I understand my PR has to follow your structure. Thanks for considering this PR.
Let me know if there is anything else.


Update Sequence+Unbox.swift to use flatMap instead of compactMap

Hey @mumme! Why are you proposing this change?


Release automation improvement

This is an epic jira to track improvement work for Beam release automation.
Main goals are:

Address pain points during full cycle of release process in automatic way.
Improve existing automation tools to be more user friendly.

Imported from Jira BEAM-7887. Original Jira may contain additional context.
Reported by: markflyhigh.

The following subtask(s) are associated with this issue: #19756, #19757, #19758, #19759, #19760, #19761


Same Thing as Updating Column?

Does this just get the 'content' from the 'Wiki Content' column (WikiField) or does this do something else?  Would getting and updating the value of the Wiki Content column result in the same outcome?

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

ID: 2dc81e82-9707-dbb6-26f0-c6c1872ca620
Version Independent ID: fe6c6701-7495-6b2f-531c-7c1e0a0b83b2
Content: Get-PnPWikiPageContent (sharepoint-pnp)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Get-PnPWikiPageContent.md
Service: unspecified
GitHub Login: @techwriter40
Microsoft Alias: kirks

Luckily PnP PowerShell is open source, so we can trace back on what this actually does. In short answer is true. It provides the Wiki Content column with following steps.
The actual implementation of Get-PnPWikiPageContent is in the following location and it uses PnP Sites Core CSOM extension (like all PnP PowerShell cmdlet) - https://github.com/SharePoint/PnP-PowerShell/blob/master/Commands/Publishing/GetWikiPageContent.cs
Code calls Web.GetWikiPageContent(ServerRelativePageUrl) CSOM extension which is available from https://github.com/SharePoint/PnP-Sites-Core/blob/master/Core/OfficeDevPnP.Core/Extensions/PageExtensions.cs#L50
This in turn is using native oob CSOM and returns the WikiField value as follows.
        public static string GetWikiPageContent(this Web web, string serverRelativePageUrl)
        {
            if (string.IsNullOrEmpty(serverRelativePageUrl))
            {
                throw (serverRelativePageUrl == null)
                  ? new ArgumentNullException(nameof(serverRelativePageUrl))
                  : new ArgumentException(CoreResources.Exception_Message_EmptyString_Arg, nameof(serverRelativePageUrl));
            }

            var file = web.GetFileByServerRelativeUrl(serverRelativePageUrl);

            web.Context.Load(file, f => f.ListItemAllFields);

            web.Context.ExecuteQueryRetry();

            return file.ListItemAllFields["WikiField"] as string;
        }


New version: Unity.Unity.2021 version 2021.3.36f1

Created by 🥟 Dumplings in Run #3557.
Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run

This package installs and launches normally on a Windows 10 VM.


Add usage reporting pkg

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

49 of 70 (70.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.06%) to 65.526%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

usage/usage.go
49
70
70.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
3714

Relevant Lines:
5668

💛  - Coveralls

/gcbrun

/gcbrun


change the event date display

In the current implementation the dates are stored in the following format: YYYYMMDD as pure integer.
It's convinient to human read this information but not very convenient for display as dates will rapidly be split appart.
In BFAST and CUSUM we use instead the following :
YYYY.year_fraction which is yay much easier to interpret on a QGIS map.
example:
20120613 become 2012.51
What do you think ?

Dear Pierrick,
sorry, I did not follow that ...
Fine for me the way you propose.
Ciao, Andi
Am Do., 15. Juli 2021 um 11:03 Uhr schrieb Rambaud Pierrick <
@.***>:

In the current implementation the dates are stored in the following
format: YYYYMMDD as pure integer.
It's convinient to human read this information but not very convinient for
display as dates will rappidily be splitted appart.
In BFAST and CUSUM we use instead the following :
YYYY.year_fraction which is yay much easier to interpret on a QGIS map.
What do you think ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/12rambau/fcdm/issues/26, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH2SLMTU3X52K6H7NOWMGC3TX2P5DANCNFSM5ANDK4BQ
.


A lot of those Footprints are really wrong...

For instance, the SOD-523 - see the datasheet vs what you have.

Many of the footprints are incorrect.

Hi ajawamnet
From the snippet you shared I assume you are referring to the recommended mounting footprint of SOD-523 provided by ON Semiconductors (https://www.onsemi.com/pdf/datasheet/rb521s30t1-d.pdf).
We share the SOD-523 footprint  for more diodes in our component library. This footprint definition originates from NXP  (https://www.nxp.com/docs/en/package-information/SOD523.pdf).
Also the recommended SOD-523 pad geometry differs between diode vendors.
I think the biggest recommended SOD-523 package comes from Diodes (https://www.diodes.com/assets/Package-Files/SOD523.pdf) which assumes 0.6x0.7mm pad size.


Fix "make a guess" modifying classic position

Fix for #75. From my observations it's not just your guess, but we teleport back on every guess, but I don't know how it's possible we didn't notice this.

Will this also maybe fix issue #33 ?


Impossible to create a field with "term for ontology" type

I installed dbNp on a local server
This installation seems to work,
But I didn't succeed to create a new file in a template with "term for ontology" type.
Steps:

add/modify study template
create a new file
Select "term for ontology" for the type of the new file
click add new ontologie
type "NCBITAXON"

Ontology term is well retrieved but the dropdown is displayed under the popup window and not accessible to select.
did I do something wrong?

Just to be clear; you are not able to select '(NCBITAXON) National....'  as I do below?

Yes. I do the same, but the choice "(NCBITAXON) ...." appears desactivated (grayed uder the window).
A problem with the navigator ? I use Firefox.

I think you closed the issue on accident?
For me it also works when I use Firefox (49.0.1, on OSX 10.12).
Could you please try to reproduce your problem on dashin.eu/interventionstudies-test (u: user p: useR123!) and come back to me with the result?

I have the same result as in local (firefox 49.0.1 on Windows10).

It works fine now. No rational explanation.
So I close the issue.


possible inconcistencies with build_scenario

[x] use of loads_dir.csv not clear
[x] a scenario should only be build for given time span in config.txt
[ ] line 122 not correct
[ ] lines 115/116 not clear
[x] pv should be renamed to production
[x] #213
[x] does normalization belong in create_actor_from_config method? We need to find consistent way where data manipulation takes place and how it is controlled
[x] same for weight factors

closed in favor of new issues


Consider renaming the repo

Why rename

the quality bar is not "awesome or better" - it's not an "everything" list either though - I tend to add "useful and interesting things of at least decent quality"
I have no plans to submit to the official awesome meta list - the goals here are a little different (see the plan for deprecation)
confusion with CalvinWalzel/awesome-svelte - I knew about it when I started this project, but its maintenance didn't appear to match the pace of community activity after Svelte 3 was released
the awesome convention is "incredibly grating" to Svelte core contributors (eep lol)

Why keep the current name

awesome has significant recognition among programmers, or at least GitHub users, so for many people it's descriptive and searchable
the "-resources" suffix might be enough to differentiate it from CalvinWalzel/awesome-svelte
renaming might be confusing for some people

Proposed names

useful-svelte-resources - simple and to the point, and the more I look at the word "useful" the more I like it
bloated-svelte - the original tongue-in-cheek name, still redirects from ryanatkn/bloated-svelte to this project - it isn't descriptive and might confuse some people
something else?

I am considering forking this repo to create a sapper version. Would you be alright with this? If so, have you landed on a name here? I don't want to just straight copy necessarily, but I thought it would be neat to mimic it initially and treat it like a sibling resource.

Cool, for sure, fork away! I've seen a lot of demand for a Sapper version on Discord. It'll be nice to have a similar project to learn from to help improve this one. I'd be interested to hear any design thoughts that come up.
For the name, the only feedback I've seen is that "awesome" helps people find and understand the project. Those seem like good things to optimize. Do you agree with just keeping it how it is? I'm not sure the resources suffix helps at all, so you may want to consider dropping it, but I also like the idea of having them mirror each other as sibling projects.

Update: looks like the sveltejs/community is going to take on the aggregation role as brought up in #18. It's also going to include Sapper resources, and I'm sure they would welcome help.

A clarification - sveltejs/community may not be the actual repo, it's yet to be decided if resources should live as a separate site.


Generate character-based L-system expansion

Deterministic, context-free character-based L-system expansion in the console.

[] example task

### My tasks
- [ ] https://github.com/octo-org/octo-repo/issues/45
- [ ] Draft task

[ ] example

[ ] Create default L-system class
[ ] Add methods for specifying alphabet, rules and initial state


Can clipboardjs be made into an npm lib? (minus the ie check)

If not I was thinking of making one as I use it a lot.

basically I would just have:

Sure - but the API is super strange. I found a case where the clipboard didn't get updated even when the console.log claimed that everything worked.
I tried to use the logic inside a jQuery/bootstrap dialog and somehow Chrome didn't accepted the content in the clipboard. I guess it could have something to do with z-indexes.
Besides this: Go ahead - I'm not that familiar with npm or how to create a package.

Thanks Robert, are you the original author so I can give credit?

Nope, I found it here http://stackoverflow.com/a/30810322/602449 (and maybe some other SO threads). Have fun :)

So far the code is worked for me, I'll let you know if I can reproduce your issue.

Ay - and if you are done with your npm package, please inform me. I would like to add that npm link to the blogpost :)


Clean up team

Clean up the team page:

[ ] Remove all that are not in the slide below
[ ] Put them in same order as slide

Add same people, in same order.
Remove all who are not in this slide

@samaradel sorry... This slide does not feature Kristof, he needs to be the first in line.


Market visually accepts cancel from insufficent fund transaction

Canceled an order without the funds to pay the fee and while the transaction pop-up indicated correctly that the transaction failed the market visually reacted as if it hadn't. Screenshot 1of2 is after I closed the "Failed" dialog box and Screenshot 2of2 is when I left the exchange and came back in which returned it to the correct state.
Notice that order is listed with the "Cancel" option in the second photo but not the first.
![After Dialog close Image] (http://i.imgur.com/QE8XUqe.png)
![After returning to market Image] (http://i.imgur.com/slitL4Z.png)

This is a remnant from when we didn't have the confirmation popup and wanted to do optimistic updates of the orderbook state, I'll remove it.


Modify to output BCP-47 labels?

Firstly, thanks to the authors for releasing the model on GitHub 🙂!
I'm currently benchmarking different language identification models. As highlighted in Section 5.2 of the GlotLID paper, matching the language code metadata between models and datasets can be difficult.
Given that BCP-47 is backwards compatible with ISO-639-3 and is the IETF's best practice for language codes, would it be possible to have an alternative version of GlotLID that uses BCP-47 labels?
Thanks!

Hi @amstu2,
Thanks for bringing up the issue.
Do you know of a source for mapping all the languages available in ISO 639-3?
Wouldn't it be easier to have a function that maps the labels of GlotLID to another format, like BCP-47, instead of retraining the model for these mappings?
I'm aware of these language tags: https://huggingface.co/datasets/lbourdois/language_tags
Based on the BCP-47 description, we should check if the ISO 639-1 code is available for a language for which we already have an ISO 639 code, and then use that instead. However, I'm unsure about the country aspect for now. Regarding the writing system, it's unclear when we should mention the writing script and when we should not.


Update swagger.json

confidence_avg_local_score enum moved to confidence_type enum.
ModelArchive added to enums

Thanks @awaterho!


archive build fails with error "no such module combine"

Works fine on simulator but fails on Archive with error "no such module combine"
(Xcode Version 12.5, React Native 0.64.0)
I already tried to build with iOS Deployment Target 9, 13 and 14

Maybe this PR will solve it? It upgrades and runs RN 0.64 #13

Maybe this PR will solve it? It upgrades and runs RN 0.64 #13

Same error with this PR.
I wrapped the import with canImport and was able to archive with Xcode.
#if canImport(Combine) import Combine; #endif
Is "Combine" relevant for react-native-healthkit or can it be removed?

@kevinroehl I don't think it's currently needed. If you can verify that it works without I'd be happy to accept a PR! :)

@kevinroehl Thanks for your contribution! This has been released in the 4.2.0 version - sorry about the delay between merge and release 🚀


Update output for generatedCounter formatting fix

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock
[ ] Style conformance: stylish-haskell

This should fail initially.

@ttuegel the commit 49348fa is the evidence that it's failing CI correctly when test output doesn't match. This shouldn't be approved unless that commit shows a red-X next to it.


Attach static methods of wrapped component to loadable component

Attach static methods of wrapped component to loadable component
c1.mjs
import * as React from 'react'
const createElement = React.default.createElement
const Component = React.default.Component

export default class c1 extends Component {
  constructor( props ){
    super( props )
  }
  render(){
    return createElement( 'p', {}, 'hello' )
  }
  static async preloadDataState( parameters ){
    debugger
  }
}

main.mjs
import * as React from 'react'
const createElement = React.default.createElement

import * as LoadableComponents from 'loadable-components'
const loadable = LoadableComponents.default.default

import * as LoadableComponentsServer from 'loadable-components/server'
const getLoadableState = LoadableComponentsServer.default.getLoadableState

const c1 = loadable( () => import( /* webpackChunkName: "main.c1" */ './c1.mjs' ), {
  modules: [ './c1.mjs' ],
} )

const composition = createElement( c1 )

getLoadableState( composition ).then( ls => {
  console.log( c1.Component.preloadDataState )
} )

output:
[AsyncFunction: preloadDataState]

Suggestion:
attach static methods or fields directly to loadable component ( c1 ):
preloadDataState method available by c1.preloadDataState instead of c1.Component.preloadDataState

Is this feature available on the latest version?

Yes!

Actually i can't get the statics methods of the component nor the component it self :(
Test.js
import React from 'react';

const Test = () =>
Test
;
Test.staticMethod = () => console.log('test');

export default Test;

Main.js
import loadable from '@loadable/component';

const Live = loadable(() => import('./components/live/Live'));
console.log(Live);
console.log(Live.Component);
console.log(Live.staticMethod);

// { '$$typeof': Symbol(react.forward_ref),
render: [Function],
preload: [Function] }
// undefined
// undefined

Methods can't be added before the module is loaded. How could we know the methods? After the component being loaded, methods will be accessible.

Hum, so i need to resolve all loadable modules first before trying to access to static method?

Yes.

I get it now, thanks!

in ssr, how I can know that a loadable module has been loaded? loadableReady() must be called in browser only .

Methods can't be added before the module is loaded. How could we know the methods? After the component being loaded, methods will be accessible.

The only way to know if a component is rendered is in the component itself. The easiest method is to pass a function called when the component is mount.
import loadable from '@loadable/component';
const Test = loadable(() => import('./Test'));

<Test onLoad={() => console.log('loaded')} />

// Test.js
import React, { useEffect } from 'react'

export default function Test({ onLoad }) {
  useEffect(() => { onLoad() }, [])
  return null
}

@neoziro
client side:
router config:
{
    path: `/index`,
    exact: true,
    page: 'Index',
    meta: {
        title: 'aaaaa'
    },
    component: loadable(props => {
        return import(/* webpackChunkName: "Index" */
        `../pages/Index/Index`)
    })
},

index page:
../pages/Index/Index
IndexPage.serverApiNames = "indexApi,commonApi"  //static properties,

server side:
let currentRoute = routes[0].routes.find(router =>
    matchPath(ctx.request.path, {
        path: router.path,
        exact: router.exact
    })
)
let { exact, page, meta, component } = currentRoute

my question:
how can i get my static component.serverApiNames

Loadable Components is not design to work with "statical" approach. I recommend you to use "react-navi" for this kind of approach.

thanks , i'll have a try.

how can i get my static component.serverApiNames in server side.

this seems to be possible now - if you know which component is loading via a route match (react router or otherwise)
you can do
        const loadedComponent = await (component as LoadableComponent<any>).load();
        loadedComponent?.default?.accessYourStaticPropName
...


Unify delete mgmt

Issue #, if available:
Description of changes:
Adds a new delete workflow for mgmt clusters
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/approve

/lgtm


Add the ability to override default env variables for Kubernetes pipeline steps

Clear and concise description of the problem
I'm trying to run a buildah container in my pipeline which requires the HOME variable to be set to /home/build. Currently, the HOME variable seems to be hardcoded to /root here.
Suggested solution
It would be nice if we could use the standard pipeline environment variable config to override the HOME (and other) variables like so:
steps:
  build:
    image: quay.io/buildah/stable:v1.33
    environment:
      - HOME=/home/build

Alternative
I'm not sure if running a command before my main command like export HOME=/home/build will work. I haven't tested it yet. If that works, it would be a nice workaround. But, it would still be good to be able to set the variables directly, in my opinion.
Update: I have confirmed that I can run this at the beginning of my build scripts, and it works. So, we have a good workaround. I still do think it would be nice to be able to specify it in the pipeline config with other env variables.
Additional context
This is part of my ongoing efforts to get buildah running on Woodpecker (#2545). This should be the last piece of the puzzle once the AppArmor PR lands!
Validations

[X] Checked that the feature isn't part of the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@dominic-p I got buildah up and running (somehow) on k8s.... just have a look here: https://github.com/maltegrosse/woodpecker-buildah (please consider the performance vs. security aspect carefully)
appreciate feedback / improvements  :)

Thanks for sharing this, @maltegrosse; that looks really cool!
I'm curious how you are passing in registry credentials (see #3582). That's pretty much the last issue I'm having with my cobbled together setup.
By the way, in my particular setup, I have good control over the hosts, so I can make sure that things like fuse are installed and configured correctly to avoid the issues with vfs.

@dominic-p I dont pass any secrets directly from k8s to the ci pipeline - I let users setup their own (gitea) repo credentials.
I think drone is doing it with some plugins, see

https://docs.drone.io/runner/extensions/kube/
https://github.com/harness/drone-kubernetes-secrets
https://github.com/drone/charts/tree/master/charts/drone-kubernetes-secrets

Thanks for the confirmation. That's kind of what I figured.
The plugin looks pretty cool, by the way. I'll definitely keep an eye on it. :)

@dominic-p I am facing issues upgrading to woodpecker latest version and my plugin...do you have similiar issues using fuse?
https://github.com/maltegrosse/woodpecker-buildah/issues/1

I saw that in the tracker. I'm not currently running the latest WP version in my cluster, so I'm not sure. If I can get some time I'll upgrade and test it out.
That permission denied error looks pretty familiar. I would definitely check the audit logs on your node to see if you can find a corresponding entry.

Hello, I have the same problem.
I need to update k8s resources in CI using kubectl, kubectl will determine whether to assume in-cluster authentication based on whether it is in a container environment.
So if I want to access the k8s cluster through the service account, but because HOME is set, it will first look for $HOME/.kube/config and give an error:
error: error loading config file "/root/.kube/config": open /root/.kube/config: permission denied

After unset HOME, kubectl works fine, so is it possible to have an option to control the setting of HOME.


Docker container for feature request at issue #4

A simple docker container for issue #4
https://github.com/ZhangGe6/onnx-modifier/issues/4

Thanks for the request! It provides a very convenient and efficient way to launch onnx-modifier.
However, there is one issue with this request:
After clicking Download, we can't find the modified_onnx folder locally, which may be saved in the docker container.

@ZhangGe6 You are right. To fetch the modified ONNX model, we can mount modified_onnx folder locally. However, this workaround will prevent onnx_modifier from being deployed remotely as a service. Maybe it is possible to return the modified ONNX files from javascript for download?

This commit enables the modified ONNX model to be saved in onnx-modifier  folder locally and has been merged.
A more flexible downloading schema is also what I want to do, and has been added to the todo_list.
Thanks for the contribution!


Import / export

TODO

[x] Fix notifications not being added to projects
[x] Correctly handle (and differentiate between) Billing Groups and regular Groups.
[x] Allow export of project private keys (default disabled).
[x] Unhide import/export.

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated.
[x] Changelog entry has been written

This PR adds functionality for import and export of projects from and to lagoon:

Projects are exported to YAML.
All parts of a project including notifications, groups, users, environments, and env-vars (for both project and environment) are exported.
Notifications, groups and users can be excluded from the export, although the references to these will remain (so they must exist in the destination lagoon).
auto-idle on environments is not handled due to it not being an attribute of Lagoon's AddEnvironmentInput. auto-idle` on projects is handled correctly.
OpenshiftID is not exported and must be provided on the command-line on import.
Project private keys are not exported. Imported projects will have auto-generated keys instead.
Only import/export of individual projects is currently implemented (i.e. not all projects) because that's what I need right now :-P

This PR is a draft because it required some changes to the existing Lagoon API schema structs for ease of config YAML (un)marshaling. I've re-implemented these in the schema package to avoid breaking existing functionality. It still refers to the existing api package for enums.
This PR also has some other experimental changes that might need discussion:

Packages are placed in internal/ to avoid exporting unstable APIs.
The lagoon package implements a high-level API for operations against a Lagoon instance and uses dependency injection to ease testing.
client re-implements the Lagoon client functionality to take advantage of the built-in unmarshalling functionality of machinebox/graphql.
Generates embedded files, to separate query templates and and code.
Generates interface mocks for testing.
Uses the E variant of the cobra.Command struct's attributes to simplify error handling (RunE etc.).

The idea with these experimental changes is that if they seem like an improvement we can gradually migrate functionality across. Or not, if they don't :D
This has got some light unit test coverage, and I've done quite a bit of manual testing. I plan to use this branch to do some migrations in the next week or so which will help prove out the functionality, but I wanted to give the opportunity for feedback on the approach and the experiental bits in the
meantime :-)
This PR incorporates the changes from #83, #84, and #85. I've just split those out separately for ease of review.
Changelog Entry
Feature - Import/Export (#36)
Closing issues
Closes #36

This looks great so far.
I'll have a look at it in more depth to make sure I understand everything that proposed.

I just gave this a whirl, exporting a project from CH1 to k8s.
Things I liked:

Able to specify the OpenShiftID upon import (even though there is no OpenShift in this case)
I was able to clean up the YAML prior to import
All environment variables imported correctly, even the ones with special characters

I would change:

Remove the --environment option from export, as it is ignored and all environments are exported

I just gave this a whirl, exporting a project from CH1 to k8s.

Great, thanks!

Things I liked:
* Able to specify the OpenShiftID upon import (even though there is no OpenShift in this case)
* I was able to clean up the YAML prior to import
* All environment variables imported correctly, even the ones with special characters

:sunglasses:

Things I had to do manually:
* Copy the project SSH key across (I don't have admin access to the Git repo to add another deploy key)

Seems like this option would only be useful for testing because you've still got to set up the webhooks on the repo in which case you'd also have enough access to add a deploy key.
Maybe it should disabled by default but optionally enabled?

Alter the active_systems_deploy, active_systems_remove, active_systems_task to be k8s specific

Those options should probably just be set to the correct value by lagoon based on the targeted cluster. What happens at the moment if you don't set them explicitly on import for a k8s cluster? Does it set them to the (wrong) openshift values?

I would change:
* Remove the --environment option from export, as it is ignored and all environments are exported

This is a global option so it can't be removed even if a command doesn't use it. I'd also love to clean up the CLI structure to avoid these redundant options, but not in this PR.

Unsure about:
* Why the import and export commands are not in the list screens?

Not sure what you mean here.. could you elaborate? Do you mean lagoon help?

Things I had to do manually:

Copy the project SSH key across (I don't have admin access to the Git repo to add another deploy key)

Seems like this option would only be useful for testing because you've still got to set up the webhooks on the repo in which case you'd also have enough access to add a deploy key.
Maybe it should disabled by default but optionally enabled?

Yeah, I think an option to copy the private key would be ideal, as this way you have 1 less step to do.

Alter the active_systems_deploy, active_systems_remove, active_systems_task to be k8s specific

Those options should probably just be set to the correct value by lagoon based on the targeted cluster. What happens at the moment if you don't set them explicitly on import for a k8s cluster? Does it set them to the (wrong) openshift values?

Correct, they default to OpenShift specific tasks. Sounds like a Lagoon feature here.

I would change:

Remove the --environment option from export, as it is ignored and all environments are exported

This is a global option so it can't be removed even if a command doesn't use it. I'd also love to clean up the CLI structure to avoid these redundant options, but not in this PR.

Sounds like a new issue is needed

Unsure about:

Why the import and export commands are not in the list screens?

Not sure what you mean here.. could you elaborate? Do you mean lagoon help?

Yes.
$ go run main.go -l k8s help | grep -i import

So the export/import that I originally wrote exported the project key, and could also import the key. I don't see why this couldn't also support that feature. It would mean not having to have anyone re-add any new public keys to their repositories or anything.

Thanks for creating the new issues @seanhamlin!
Re: private keys, I agree that since the Lagoon API supports export of the private key material it makes sense to add the option here too.
The reason that I didn't add key export initially is that:

I didn't need it for the migration I'm working on since we're encouraging the customer to generate new keys per project.
IMO it's not great security-wise that the Lagoon API lets you pull the private key material at all.

On the last point, I think it would be better if you could add private key material but then only retrieve the fingerprint afterwards. I've been meaning to create a Lagoon issue for this..

As I'm also going to need this functionality soon, so I had a skim over the PR and the proposed changes. Works as intended, but I'll do some more functional testing with it tomorrow for my particular use case to see if anything is missing.
Overall, I'm happy with the proposed changes. I'm thinking it would be good to bring the rest of the CLI in line with these changes over a period of time so we can start doing better tests.
@smlx When do you think you will have this PR ready for review?

@shreddedbacon  I'll try to finish it off in the next 48 hours.. basically the bits I've identified as missing are in the TODO list at the top of the PR. It would be great for you to test this too -  there are probably some more rough edges I've missed.

That was a long 48 hours :cry:
I've updated this and it's ready for review.
Since the last review I've added:

handling for groups/billinggroups
handling for new notification types
ability to export project private keys (off by default)
unhide import/export commands in lagoon help

An important change that the notification and billinggroup handling introduces is the concept of lagoon versions. This is added as a field in .lagoon.yml. e.g. see the last line here:
  local:
    graphql: http://localhost:3000/graphql
    hostname: localhost
    port: "2020"
    token: <snip>
    ui: http://localhost:8888
    version: 1.2.0

By default (if version field is not defined) it will fall back to the simplest request type for compatibility. So if you want to export billinggroups or email/teams notifications you'll have to set the version to 1.2.0 or higher.


fix: refactored internal logic

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ImportError: cannot import name 'DualIAATransform' from 'albumentations'

I am trying to train the model but I got this error:
Traceback (most recent call last):
  File "/home/user/PycharmProjects/lama/bin/train.py", line 21, in <module>
    from saicinpainting.training.trainers import make_training_model
  File "/home/user/PycharmProjects/lama/saicinpainting/training/trainers/__init__.py", line 3, in <module>
    from saicinpainting.training.trainers.default import DefaultInpaintingTrainingModule
  File "/home/user/PycharmProjects/lama/saicinpainting/training/trainers/default.py", line 7, in <module>
    from saicinpainting.training.data.datasets import make_constant_area_crop_params
  File "/home/user/PycharmProjects/lama/saicinpainting/training/data/datasets.py", line 19, in <module>
    from saicinpainting.training.data.aug import IAAAffine2, IAAPerspective2
  File "/home/user/PycharmProjects/lama/saicinpainting/training/data/aug.py", line 1, in <module>
    from albumentations import DualIAATransform, to_tuple
ImportError: cannot import name 'DualIAATransform' from 'albumentations'

I solved it using
pip install albumentations==0.5.2


drivers: console: fix Kconfig DTS inference for mcumgr uart

The conversion last year in 8ce0cf01267982ac2f6be77c7a2307bc38c4be88 mixed up uart-pipe with uart-mcumgr.  Revert to the pre-conversion relationship.

@utzig Would you be so kind and add some information, within help to this Kconfig option, that it defaults to DTS choosen zephyr,uart-mcumgr when DTS is enabled and this option overrides this default?
Stupid question regarding the not working transport: do you have MCUMGR_SMP_UART also enabled?

Stupid question regarding the not working transport: do you have MCUMGR_SMP_UART also enabled?

Yes, that is what https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/subsys/mgmt/mcumgr/smp_svr/overlay-serial.conf does.

Yes, that is what https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/subsys/mgmt/mcumgr/smp_svr/overlay-serial.conf does.

Just asking because I have already managed to enable UART_MCUMGR without enabling MCUMGR_SMP_UART, which makes it compile fine it just does not work. It seems that here it is rather device issue.

It seems that here it is rather device issue.

Yes, which is why I was thinking it might have solved #27630: k64f (by inspection) would have used zephyr,uart-pipe as the default for CONFIG_UART_MCUMGR_ON_DEV_NAME, which might have been wrong.
It does make sense to document in each Kconfig that'ts defaulted to a devicetree chosen where its default comes from.  There's a lot of them, so I propose to do that in another PR and just leave this as the simple fix that it is.


Can we design an algorithm to find out copyrighted materials in Open Datasets

Like copyrighted books by ISBN numbers


No 'OER is not responding' for OER rates

I usually use OpenExchangeRate. It has not been supplying data regularly in the last day or two but I am NOT seeing a 'OpenExchangeRate is not responding' alert at start up.
MBHD fails over cleanly - you just don't get fiat info but there should be an alert

Looks like it's a redirect:

So OER has probably changed it's interface.
Anywhich way MBHD should respond appropriately

OER seems to be working now but there probably needs to be some tidy up so that it fails over better

I have added in a check for HttpStatusIOException which I think will cover it.
You can check for a related HTTP error code (409 - Conflict) by setting your exchange to OER/ GBP and then trying to switch to Hitbtc. The HTTP error code gets exposed on the UI correctly.
I believe this should also catch similar 303 errors when they occur again. (OER is not showing these errors currently.
Awaiting review and closing

Reduced error logging level. Closing.


[Suggestion] Fall damage numeric estimation

You might be able to take the fall damage estimation color feature a step further by plugging in the player's velocity into the fall damage curve. I'm not sure exactly where it is, but if you generate a full project dump and filter in the editor by data curve assets, you'll probably find it.

yeah I may look into that. I thought about changing the icon to the skull when the damage will actually kill you based on your health, but didn't find a quick solution at the time. But then I dont know much about unreal and modding, and hadn't looked into this Asset Toolkit at all either.
In general I wanted to get a few status attributes about the player that I couldn't find yet, like being in a vehicle for example.

If you do pursue this, here's the paths for the curves:
Normal
CurveFloat'/Game/FactoryGame/Character/Player/FallDamageCurve.FallDamageCurve'

Blade Runners
CurveFloat'/Game/FactoryGame/Equipment/JumpingStilts/JumpingStilts_FallDamageCurve.JumpingStilts_FallDamageCurve'

I'm not sure offhand how to detect being in a vehicle, but I think the Pawn possessed by the player controller will change when this is the case. Pawns/Controllers are an Unreal concept. You can get the local player controller via the blueprint node GetPlayerController or you can get it from an actor's instigator.

I tried getting the dump tool working but alpakit failed to build it for whatever reason. Didn't find a solution for that.
It just complained about not finding a file it was working on itself. No idea what's up with that. Maybe some future version will fix it.

Owner

You need to compile the project in VS before you alpakit. If you didn't do that already.

You need to compile the project in VS before you alpakit. If you didn't do that already.

I found the solution in the meantime. Alpakit was upset at the directory structure I used even though unreal editor is fine with it.

You need to compile the project in VS before you alpakit. If you didn't do that already.

I found the solution in the meantime. Alpakit was upset at the directory structure I used even though unreal editor is fine with it.

Great to hear! I was looking for ideas from the SF Modding Discord Server, and make a speedometer for MPH. I was wondering if you would be willing to teach me the basics of how the mod hooks in, and get's the speed, and all of that stuff?

@MinoDab492 The mod is open source, you should be able to clone it into a plugin folder in your current Unreal project and explore how the mod is set up from there

True, but I more meant could they help me actually understand what each thing does and all that.

True, but I more meant could they help me actually understand what each thing does and all that.

So did you see that I opened another thread for you? Or have you lost interest?


Server-side directives aren't applied on custom components

Version
v2.10.1
Reproduction link
https://codesandbox.io/s/codesandbox-nuxt-dyu6u
Steps to reproduce
Strange one... Nuxt Custom Directives don't seem to register on imported Components (but do work when added to regular template HTML)

    <div v-custom1="`this works`">Hello

    <HelloWorld v-custom1="`this doesnt work`"/>

  render: {
    bundleRenderer: {
      directives: {
        custom1(el, dir) {
          console.log("custom1", dir);
        }
      }
    }
  },

Reproduction:
https://codesandbox.io/s/codesandbox-nuxt-dyu6u
What is expected ?
Should log both custom directives
What is actually happening?
Only logs the first custom directive. Adding a custom directive to a custom component doesnt register.

This bug report is available on Nuxt community (#c9915)

Hey :wave:
Looks like a vue-server-renderer bug to me. Will investigate.
Anyway, you are registering "only" server-side directives here. If you want the typical (client-side) one, you can use a Nuxt plugin to register them globally or use the directives attribute on a specific component or page.
Further read on server-side directives in my blog post

Closing here as it is a vue server renderer bug indeed. Further info in https://github.com/vuejs/vue/issues/10733

Resolved via https://github.com/vuejs/vue/pull/12661 (v2.7.9 and up)


ganv: unstable-2019-12-30 -> 1.8.2

Description of changes
Upstream changed their build system to meson,
which fixes the waf build issue with Python3.12, so this PR fixes the ganv build.
nixpkgs-review says the ingen package is broken, that's because it depends on the raul package, and both ingen and raul have the same waf issue.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

1 package failed to build:

ingen

2 packages built:

ganv
patchage

cc @cillianderoiste

Add a :+1: reaction to pull requests you find important.

Done in #328112.


Proposal: styled can take function returning css tagged string

In a styled component that takes a lot of input from its props and needs to do intermediate calculations, it can be really cumbersome. Here's some real code we have (apologies for the lack of context, but wanted to illustrate the situation):
const borderWidth = dir =>
  dir === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
const borderColor = (dir, c) =>
  dir === 'right'
    ? `transparent transparent transparent ${c}`
    : `transparent ${c} transparent transparent`
const Arrow = styled.div`
  border-width: ${p => borderWidth(p.direction)};
  border-color: ${p => borderColor(p.direction, p.theme.colors.green)};
  border-style: solid;
  width: 0;
  height: 0;
`

This was refactored from:
const Arrow = styled.div`${({ theme, direction} => {
  const borderWidth =
    direction === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
  const borderColor =
    direction === 'right'
      ? `transparent transparent transparent ${theme.color}`
      : `transparent ${theme.color} transparent transparent`

  return  `
    border-width: ${borderWidth};
    border-color: ${borderColor};
    border-style: solid;
    width: 0;
    height: 0;
  `
}}`

What I'd like is more like:
const Arrow = styled.div({ theme, direction } => {
  const borderWidth =
    direction === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
  const borderColor =
    direction === 'right'
      ? `transparent transparent transparent ${theme.color}`
      : `transparent ${theme.color} transparent transparent`

  return css`
    border-width: ${borderColor};
    border-color: ${borderWidth};
    border-style: solid;
    width: 0;
    height: 0;
  `
})

So basically, I want the straightforward syntax of the first example (no nested template strings or dance of brackets, parentheses and backticks!) with the encapsulation and brevity of the second example (no functions inside interpolants). This is a small use case, but we have tons of similar stuff throughout our codebase, and situations where the proposed syntax would be even more of a sweet spot.
Apologies if this has been proposed before, or if I'm missing a more idiomatic solution that's already available. If this seems helpful to other folks, I'd tentatively say I'd be interested in trying to implement it.

I would also like this, as well as maybe being able to pass a style object
directly.
I know that @mxstbr is not a fan of extending the API, but maybe this will
sway him :)
On Sun, Mar 18, 2018, 4:27 AM Alan Johnson<EMAIL_ADDRESS>wrote:

In a styled component that takes a lot of input from its props and needs
to do intermediate calculations, it can be really cumbersome. Here's some
real code we have (apologies for the lack of context, but wanted to
illustrate the situation):
const borderWidth = dir =>
dir === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
const borderColor = (dir, c) =>
dir === 'right'
? transparent transparent transparent ${c}
: transparent ${c} transparent transparent
const Arrow = styled.div  border-width: ${p => borderWidth(p.direction)};   border-color: ${p => borderColor(p.direction, p.theme.colors.green)};   border-style: solid;   width: 0;   height: 0;
This was refactored from:
const Arrow = styled.div${({ theme, direction} => {   const borderWidth =     direction === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'   const borderColor =     direction === 'right'       ? transparent transparent transparent ${theme.color}      :transparent ${theme.color} transparent transparent`
return      border-width: ${borderWidth};     border-color: ${borderColor};     border-style: solid;     width: 0;     height: 0;
}}`
What I'd like is more like:
const Arrow = styled.div({ theme, direction } => {
const borderWidth =
direction === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
const borderColor =
direction === 'right'
? transparent transparent transparent ${theme.color}
: transparent ${theme.color} transparent transparent
return css    border-width: ${borderColor};     border-color: ${borderWidth};     border-style: solid;     width: 0;     height: 0;
})
So basically, I want the straightforward syntax of the first example (no
nested template strings or dance of brackets, parentheses and backticks!)
with the encapsulation and brevity of the second example (no functions
inside interpolants). This is a small use case, but we have tons of similar
stuff throughout our codebase, and situations where the proposed syntax
would be even more of a sweet spot.
Apologies if this has been proposed before, or if I'm missing a more
idiomatic solution that's already available. If this seems helpful to other
folks, I'd tentatively say I'd be interested in trying to implement it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/styled-components/styled-components/issues/1620, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADWlqp2DdjGrvYw2SP6iVsvw-qiKj9vks5tfdQ5gaJpZM4SvDlu
.

Both APIs you’re proposing are not impossible right now and seem like they make things simpler. But with good helper functions and segregated interpolations you gain a lot more. By removing duplication that becomes excessively long you will probably come up with some good helpers and props for your components.
Now, I think the presented use case there with four different border properties is kind of an edge case, but I would not like to argue against your workflows in particular.
But what I’d like to remind you of is that the approaches you present directly conflict with our static analysis / preprocessing plans. A function that returns a tagged template literal can have as many branches as you’d like and is this unlikely to be completely statically analysable. The same goes for functions returning objects (which I btw find inelegant, it’d encourage style props etc with bad perf, and is not a styled-components style API)
That’s just my opinion, but I’d love to hear @mxstbr and @probablyup’s opinions

@kitten Thanks for the feedback!
I don't think I fully understand what you're proposing as an alternative, although I think there's a pretty good chance that there are other solutions that I just haven't thought of. Just to be clear, when you say "good helper functions", do you mean my first example? I can certainly live with this approach, but my overall point was just that it breaks encapsulation of logic that really is specific to the Arrow component. Sure, it could be come more abstract in order to lose that specificity, but I don't think that's a great idea if there ends up being only one use case. And to be clear, this is just one use case that is probably of intermediate complexity in the scope of our styling.
By "segregated interpolations", I assume you mean something different than my second example, since that's more like "nested interpolations".
I don't know much about the static analysis situation, but maybe I'll look into it just to make sure I understand what you mean.
Anyway, maybe there's a solution that's a little wordy, but not too bad. Model the scope as a component, rather than a function that returns CSS.
const Arrow = withTheme(({ theme, direction }) => {
  const borderWidth =
    direction === 'right' ? '8px 0 8px 10px' : '8px 10px 8px 0'
  const borderColor =
    direction === 'right'
      ? `transparent transparent transparent ${theme.colors.green}`
      : `transparent ${theme.colors.green} transparent transparent`

  const Inner = styled.div`
    border-width: ${borderWidth};
    border-color: ${borderColor};
    border-style: solid;
    width: 0;
    height: 0;
  `
  return <Inner />
})

So in a nutshell your desired syntax is something like this?
styled.div(p => `
  color: ${p.color};
`)

or now with object support
styled.div(p => ({
  color: p.color,
}))

@probablyup Yeah, either way. The object syntax seems even better though. Does that work now?

Yeah objects were added in 3.3.0. The desired function syntax isn’t a thing yet though.

@probablyup Thanks for the head's up! If that PR merges, both syntaxes will be possible.


Reported rssi values are wrong

Description of problem:
The rssi value reported by the devices through get_rssi() are always -65535 in my environment (CCU2 with latest firmware). The reason for this is that all of the devices which I have access to provide their rssi value in the attribute RSSI_PEER, but pyhomematic checks RSSI_DEVICE.
Is there a particular reason why RSSI_DEVICE is used instead of RSSI_PEER? Is rssi reporting working for other people?
I have prepared the necessary changes (see referenced commit), which work for me, but I am not sure about this yet.
If it looks good to you I can prepare a PR for pyhomematic and homeassistant (two PRs required), but please tell me what you think about this first.

It's been a while since I have looked at that topic. I think back then it was unlcear which value was the relevant one. Having a quick look at it now it seems as if you are right.


bloxstrap account manager?

could bloxstrap possibly add an account manager? or is that not feasible?

Probably not, I don't really see the use for it. Besides, Roblox Account Manager already exists and is much better suited for that anyway.


Mondo build exceeds 50 minute hard limit of Travis

Travis has a hard limit of 50 minutes for running builds with the free plan.
There are afaics at least two places where we could save considerable time:

Currently we execute the entire battery of QC tests on three different artefacts. Any chance we can reduce this a bit? Maybe restrict ourselves to the sparql checks really necessary at each step?

robot verify -i mondo-edit.obo-noimports.owl
robot verify -i mondo.owl
robot verify -i mondo.obo

The reasoner is run twice, which consumes a lot of time:

owltools --no-logging --use-catalog  mondo-edit.obo disjoint_sibs.owl imports/equivalencies.owl --merge-support-ontologies --run-reasoner -r elk
robot reason -T true -x true -X true -i filtered.owl -r ELK

After the next ROBOT release, we can perhaps squeeze a few more minutes by empying the new Jena engine in ROBOT (as per @cmungall  suggestion).
Lastly, we can, as @ShahimEssaid suggested, retire the Travis job altogether in favour of Jenkins, but I would like to try getting it to run befor that, at least one more time.

For now I changed the .travis.yml configuration so that Travis doesn't run the "make" test. This allows the overall status to reflect the result of Jenkins. Jenkins build is also fixed and is working now.

@ShahimEssaid  cool! If jenkins runs all the qc now, maybe that is enough? @cmungall?

I think this is no longer an issue
closing, please reopen if needed

Hopefully never again :D


Bug: stylePanelLayout='circle' with allowMultiple=true causes unintended behavior

Please view this jsfiddle: https://jsfiddle.net/z513k7vq/
Upload a file and the control shows no progress indication or other apparent UI change. I'm pretty sure this is not the intended behavior. If it is, I don't see anything about it in the documentation. If allowMultiple is set to false, the UI changes to indicate progress (although no progress here since it's not hooked up to a real server).
I'm testing on Chrome 77, Mac OS Mojave 10.14.6.

It's not to be used with allowMultiple

Is this documented? Perhaps an exception should be thrown or a warning
should be printed?
On Thu, Oct 10, 2019 at 03:19 Rik<EMAIL_ADDRESS>wrote:

It's not to be used with allowMultiple
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pqina/filepond/issues/390?email_source=notifications&email_token=ABQIEPHTEDL676Y4Z55XM2LQN3JQBA5CNFSM4I7FVF62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA3ER5A#issuecomment-540428532,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQIEPA24PKK6TKIAJRM6GTQN3JQBANCNFSM4I7FVF6Q
.

It should be documented here https://pqina.nl/filepond/docs/patterns/api/filepond-instance/#properties but it seems it isn't.
Feel free to submit a PR https://github.com/pqina/filepond-docs


Transform logical assignment panic when using together with private prop

Describe the bug
es2021 introduced logical assignment ( ||=, &&=, ??= )
es2022 introduced private field ( this.#bar )
When transform logical assignment, SWC assert that there must not have any private field, as it should be processed by es2022::class_properties pass. Code
However private class field is supported from chrome 74, while logical assignment is supported from chrome 85.
So if I use browserslist query: chrome 75, it won't transform private field, but it will transform logical assignment, and logical assignment will find the private field, then assert failed
Input code
class Foo {
  #bar

  bar() {
    this.#bar ||= 1
  }
}

Config
{
  "jsc": {
    "target": "es2022",
    "parser": {
      "syntax": "typescript",
      "tsx": true
    },
  },
  "env": {
    "targets": "chrome 75"
  },
}

Playground link
https://play.swc.rs/?version=1.3.57&code=H4sIAAAAAAAAA0vOSSwuVnDLz1eo5lJQUE5KLOIC0kBKQxMsoqBQkpFZrAeSUKipsVUwBIrVctUCADAllIY3AAAA&config=H4sIAAAAAAAAA6vmUlBQyipOVrJSqAYygZySxKL01BIgXym12MjAyEhJByJekFhUnFoEVwcUKa7MK0msAKksqSxILU4uyiwogaoGmVMMkiopKk0Fi9SCJMCEUmpeGbp1xSBTkjOK8nNTFcxNlSBKawGa4cWUnQAAAA%3D%3D
Expected behavior
Transform correctly
Actual behavior
Panic
Version
1.3.57
Additional context
No response

Closing as fixed.
https://play.swc.rs/?version=1.3.107&code=H4sIAAAAAAAAA0vOSSwuVnDLz1eo5lJQUE5KLOIC0kBKQxMsoqBQkpFZrAeSUKipsVUwBIrVctUCADAllIY3AAAA&config=H4sIAAAAAAAAA6vmUlBQyipOVrJSqAYygZySxKL01BIgXym12FRJByJYkFhUnFoEVwQUKa7MK0msACkrqSxILU4uyiwogaoGGVIMkiopKk0Fi9SCJIBELQDrZ4gVbwAAAA%3D%3D


[FEAT]: Support system prompt in Sotopia

Description
System prompts have been a standard practice for many models.

https://platform.openai.com/docs/guides/prompt-engineering/tactic-ask-the-model-to-adopt-a-persona
https://llama.meta.com/docs/model-cards-and-prompt-formats/meta-llama-3/
https://api.python.langchain.com/en/latest/messages/langchain_core.messages.system.SystemMessage.html

We should enable Sotopia to support that.
Additional Information
No response

Can you make this clearer? In which function do you want to use the system message? And how would that argument be passed into the generation function?

we don't need this now! system prompt should not exist in the simulation.


How can i fix this

[ERROR]   The project [unknown-group-id]:[unknown-artifact-id]:[unknown-version] (/home/azureuser/pom.xml) has 4 errors
[ERROR]     Malformed POM /home/azureuser/pom.xml: Expected root element 'project' but found 'plugins' (position: START_TAG seen ... @1:9)  @ /home/azureuser/pom.xml, line 1, column 9 -> [Help 2]
[ERROR]     'groupId' is missing. @ line 1, column 9
[ERROR]     'artifactId' is missing. @ line 1, column 9
[ERROR]     'version' is missing. @ line 1, column 9

Hi @dwojcik57 - Thank you for your feedback! Could you share with us the URL of the documentation that your feedback is applicable to?

Hi, I was following steps from this quickstart
https://docs.microsoft.com/en-us/azure/app-service/app-service-web-get-started-java
and when trying to deploy, I've got that error.

Thanks for the link, @dwojcik57! We have assigned one of our engineers to take a closer look & assist you further.

@dwojcik57,  It looks like the dependencies are missing, kindly ensure that the Maven plugin is configured correctly. Just to isolate, check to see if the app works fine locally.
A deployment issue is an issue that causes the wrong set of files to get deployed to your site folder (typically site\wwwroot), or that causes some files not to get deployed at all.
A runtime issue happens when the files in your wwwroot folder are exactly what they should be, but for some reason the site doesn't run correctly.  Also, review the line 1, column 9 for the correct config. Take a look at this document - Make sure site correctly deploys locally for the steps.

@dwojcik57, Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and we will gladly continue the discussion.


How to include siblings and nephews with Include/ThenInclude

How would I include the data where I have the ?? below? If I try to use Include the value is user and not the previous value from ThenInclude.
context.User
	   .Include(user => user.Layouts)
			.ThenInclude(layout => layout.Pages)
				.??(page => page.Something)
				.??(page => page.SomethingElse)
				.ThenInclude(page => page.Configuration)
					.??(configuration => configuration.Prop1)
					.??(configuration => configuration.Prop2)
					.ThenInclude(configuration => configuration.Colors)

Hello @randellhodges ,
How this question is related to our library EF Plus? Perhaps you are in the wrong forum
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Is ThenInclude yours or a EF core function? I was playing with both it and IncludeFilter. I had the same question with IncludeFilter but I found that if I basically duplicated it and then changed the one thing, it worked. Unwieldy, but works.

Nope, ThenInclude is part of EF Core.
We added it in EF Classic but I don't think this is the one you are looking for.
The IncludeFilter still doesn't have the ThenIncludeFilter but we hope to find eventually the time to code it.

Thanks. I am able to use IncludeFilter but it is cumbersome with siblings. I'll check out the documentation for ThenIncludeFilter to see if, when it gets into EF Core that will help.
When I get a chance, I'll post a more complete example of what I'm trying to do.


Documentation structure

A few thoughts for the documentation that could be good to discuss to avoid major restructuring later?
Documentation of new materials
Currently, we seem to document both the creation of the AbstractMaterial type as well as the material_response function for that material. Would it be an idea to have a single documentation for the material_response function (similar to get_cache and initial_material_state), and only document each AbstractMaterial?
Documentation of internal functions
In my PR #28, I have a utility_functions.jl file with some general purpose functions. These are not exported, but perhaps it would be nice to document these functions in the docs - perhaps under "Internal utilities"? Here we could also document the nonlinear_solver.jl contents?

Might be nice to checkout https://diataxis.fr/

I think Daniele Procida makes many good points!
@fredrikekre do you know any equivalent small (julia) package documentation explicitly structured this way? I browsed the list but found mostly larger packages (e.g. some discussion JuliaLang/julia - but seems like Tutorial and HowTo are not included)
I'm trying to figure out how the Tutorial and HowTo should be differentiated.
In this package, I guess we have rather few external functions so perhaps we could have a structure like

Introduction (cf. explanations)
Short back-ground on material modeling etc.
How to use (cf. tutorials/how-to)

Tutorial style showing the exported functions, but excluding constructors. Only give examples required to demonstrate usage.
API of exported functions (cf. reference)

Material models
A structured overview of the different material models and their constructors
For developers

Developer guidelines
API of utility functions that we use internally but that are not exported

And in the future, perhaps one would want to add some examples e.g. for plotting a stress-strain response and for using Ferrite?

do you know any equivalent small (julia) package documentation explicitly structured this way?

No, I am only aware of https://juliacomputing.github.io/DataSets.jl/dev/ (doesn't have how-to).

I'm trying to figure out how the Tutorial and HowTo should be differentiated.

Yea, thats my main difficulty too. My current understanding is that tutorials should "teach" but howto should "describe" (e.g. from https://diataxis.fr/introduction/#characteristics-of-documentation). But I agree that it is not very clearcut.
Anyway, maybe it doesn't make sense to structure the docs for this package like that. This was just something I recently look into more closely.
Although, if one would use that system I suppose that (i) tutorials would be very introductory step-by-step guides that is easy to follow along, (ii) how-to would be similar(?) but perhaps for more specific tasks (e.g. how to integrate with Ferrite, how to implement your own model  etc), and (iii) reference would basically be the docstrings.

do you know any equivalent small (julia) package documentation explicitly structured this way?

Ha, just stumbled upon https://juliaactors.github.io/Actors.jl/dev/ minutes after my last reply

Nice!
The Actors.jl package is really clear-cut following that framework and certainly makes the documentation easy to get into!
It would be really nice to write a doc like that for a package - great input Fredrik!
But for this package, unfortunately I think I opened this issue prematurely for not being a core developer and I will close it to avoid having too many seemingly unsolved issues.


Support newer Python and package versions

Tested with Python 3.11 and latest versions of all packages. Fresh environment with (hopefully) only really necessary packages. fink-science is 5.6.2 as in corresponding PR.
Most of changes are backwards-compatible (so would work on current environment too) except for Flask that at some point of  1.0->2.0 transition (current is 3.0) renamed send_file arguments for giving the download file name.
The conversion of types in API calls is isolated into request_api endpoint which directly provide dataframe, json object, or just raw output (used only for cutouts).
The code is also slightly cleaned up from deprecated constructs like np.alltrue
Minor optimization is done for loading preview cutout - it now avoids extra API call, as it is not really necessary.

Thanks @karpov-sv ! Let me install the new environment on the dev server, and come back to this for feedback.

I really hope I resolved the conflict correctly!..


Delegate issue when assigned to self

Had an issue in my viewDidLoad where I accidentally set the sceneView delegate to self. Resulted in my not being able to view the added nodes or make use of the touch function. After removing that line of code, all worked fine again

@Jmats17 - PR to address this is in review: https://github.com/ProjectDent/ARKit-CoreLocation/pull/206

@Jmats17 - I'm closing this issue since that PR was merged in.


f2fs support along side ext4 thank u

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Can you clarify your use case?

Yes do decompile imgs that are f2fs and recompile f2fs without read write
protection
On Tue, Apr 5, 2022, 2:25 PM Ben Hillis @.***> wrote:

Can you clarify your use case?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/WSL/issues/8231#issuecomment-1089371423,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPJA4QMRROC5RNWC3YWI73VDSVTLANCNFSM5SQHNPHQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have my own fork with f2fs support, you can compile it yourself and use it - https://github.com/okineadev/WSL2-Linux-Kernel/tree/f2fs-support


scipy.stats.invwishart does not check if scale matrix is symmetric

The scale matrix argument for scipy.stats.invwishart should be symmetric, but it does not currently throw an error or warning. See documentation http://docs.scipy.org/doc/scipy-0.16.1/reference/generated/scipy.stats.invwishart.html

the scale matrix, which must be symmetric

The following code runs fine but should throw an error
df = 2
scale = [[1, 1], [0, 1]]
stats.invwishart.rvs(df=df, scale=scale)

I'm using scipy version 0.17.0.

I think we should loosely follow lapack and simply document which triangle is being ignored (upper or lower).  @ChadFulton?


Improve accuracy metrics

Fix typos (language-wise content) in function documentation.
Change the name of functions themselves to train_to_test_ratio/difference (or train_test_gap)

I think we can close this Issue? @marisanest

Yes, will be closed by PR #51.

Solved by PR #51

Solved by PR #51


[Races] Extract EventEmitter for reuse throughout ringpop

In an effort to reduce/eliminate all race conditions found in ringpop and as a good practice this PR will extract all EventEmitter logic into its own package with complete test coverage and race free code.
It has been separated from #178 to ease the reviewing process and builds upon #181 to speedup runs on travis.

Coverage decreased (-0.08%) to 95.077% when pulling 5931d2f3f9ccd6963dc2a446f1bc6ea453083529 on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

I left a number of comments. I'm a big fan of what your doing here and how you are doing it!

Coverage decreased (-0.2%) to 95.001% when pulling 2401032f5ab371ec3c6f21fe9a509fd616270c1e on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

Coverage decreased (-0.2%) to 95.001% when pulling 2401032f5ab371ec3c6f21fe9a509fd616270c1e on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

Coverage decreased (-0.2%) to 95.001% when pulling 2401032f5ab371ec3c6f21fe9a509fd616270c1e on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

I like it. Looks good.

LGTM

Coverage decreased (-0.2%) to 95.001% when pulling 0bb4576da8555356fad771c89b70a3b0d35b5c44 on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

Coverage decreased (-0.2%) to 95.001% when pulling 0bb4576da8555356fad771c89b70a3b0d35b5c44 on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.

Coverage decreased (-0.2%) to 95.001% when pulling 0bb4576da8555356fad771c89b70a3b0d35b5c44 on feature/event-emitter into f1793c9dacd81a5478be63681c45da3fd3e1aed6 on dev.


[SMALLFIX] Change default understorage type to be no persist

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5979/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5986/
Test PASSed.

LGTM, please update the documentation.

Should the documentation change as well?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/6004/
Test PASSed.

LGTM