Custom plugins examples

We need to add examples, how to set custom plugins in config. Like ./my-plugin.
This config doesn’t work:
module.exports = {
  plugins: {
    './postcss-plugin': 2
  }
}

Module build failed: Error: Cannot find module './postcss-plugin'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at load (/home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:21:50)
    at /home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:27:18
    at Array.forEach (native)
    at loadPlugins (/home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:26:24)
    at /home/ai/Dev/test/node_modules/postcss-load-config/index.js:20:18

This config doesn’t work too:
module.exports = {
  plugins: [
    require('./postcss-plugin')(2)
  ]
}

Module build failed: Error: Cannot find module '0'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at load (/home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:21:50)
    at /home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:27:18
    at Array.forEach (native)
    at loadPlugins (/home/ai/Dev/test/node_modules/postcss-load-plugins/lib/loadPlugins.js:26:24)
    at /home/ai/Dev/test/node_modules/postcss-load-config/index.js:20:18

yep, the question is if it not better to 'enforce' one format, since using a function  as config is now possible ?

Yeap, I think one format is better, than multiple. It is easy to show one format in docs, rather than "use this format for this case, and that format for different".

i will try
modules.exports = {
 parser: ...,
 plugins: [
   require('postcss-plugin')
 ]
}

simply 'passthrough' the array, but it's a potential error pit, if to fragile I leave it for now, anything should be possible with 'standard formatted' config()/config by now :)

Array in JS syntax and object in package.js on and JSON config? Looks good.

config.plugins can be an {Object} or an {Array} in JS, .postcssrc (JSON) is an standard format {Object} only during the lack of require(), the array will be checked if plugins are required and returned

When finished is ping you and you can finally approve it before npm publish ? :)

@michael-ciniawsky we had some problem with array. I will retest it, when you ping me with 1.0 pre-release.
Sure, ping me before release.

:+1: yep maybe leave it enterily abd curently postcss-load-config v1.0.0-alpha4 there is no array support 😛

Using an Array works know, this should resolve the issue requiring a local plugin (develop, testing) aswell.
module.exports = (ctx) => {
 parser: 'sugarss',
 plugins: [
   require('./postcss-dev')(ctx.dev)
 ]
}

@michael-ciniawsky I saw that you updated examples. They become much better.
Few extra changes, that I suggest:

Make first example simpler. Most of developers will not use context. Let’s move context example to the bottom of doc.
Split array and object example with explicit “or you can use arrays”

@ai 👍


Documentation is broken for API

Where breakage was detected. https://github.com/HumanCellAtlas/dcp-cli/commit/ced76f472b28830329ff197f5fa7b21cce10a7bf
This page shows the current status of the DSS documentation https://hca.readthedocs.io/en/latest/api.html

Fixed by #227


move package from qq.droste to higherkindness.droste

There’s something wrong in the Bazel stage. Do you know what can it be?


Youtube thumbnail quality issues

https://aisafety.info/questions/8RHW/What-is-"jailbreaking"-a-large-language-model-(LLM)
vs
https://www.youtube.com/@Computerphile/search?query=jailbreak

Confirmed fixed on desktop. As a bonus the videos are now larger :)


Error writing checkpoints at high core counts

I've been running GCHPctm with MAPL 2.2.7 for various grid resolutions and core counts on the Harvard Cannon cluster. I am encountering an error while writing checkpoint files when running with high core counts, in my case 1440 cores. The error is in UCX, so not MAPL specifically, but it is specific to the MAPL checkpoint files:
srun: error: holy2a01303: task 0: Killed
[holy2a19302:73246:0:73246]    ud_iface.c:746  Fatal: transport error: Endpoint timeout
==== backtrace ====
[holy2a19304:31734:0:31734]    ud_iface.c:746  Fatal: transport error: Endpoint timeout
==== backtrace ====
    0  /usr/lib64/libucs.so.0(ucs_fatal_error_message+0x68) [0x2b64849e1318]
    1  /usr/lib64/libucs.so.0(+0x17495) [0x2b64849e1495]
    2  /usr/lib64/ucx/libuct_ib.so.0(uct_ud_iface_dispatch_async_comps_do+0x121) [0x2b648b0267c1]
    3  /usr/lib64/ucx/libuct_ib.so.0(+0x1d902) [0x2b648b02a902]
    4  /usr/lib64/libucp.so.0(ucp_worker_progress+0x5a) [0x2b64843679ea]
    5  /n/helmod/apps/centos7/Comp/gcc/9.3.0-fasrc01/openmpi/4.0.2-fasrc01/lib64/libmpi.so.40(mca_pml_ucx_send+0x107) [0x2b6481f48727]
    6  /n/helmod/apps/centos7/Comp/gcc/9.3.0-fasrc01/openmpi/4.0.2-fasrc01/lib64/libmpi.so.40(MPI_Gatherv+0xf0) [0x2b6481e354c0]
    7  /n/helmod/apps/centos7/Comp/gcc/9.3.0-fasrc01/openmpi/4.0.2-fasrc01/lib64/libmpi_mpifh.so.40(pmpi_gatherv__+0xad) [0x2b648196212d]
    8  /n/holyscratch01/jacob_lab/elundgren/testruns/GCHPctm/13.0.0-alpha.10/scalability/gfortran93/gchp_standard_c180_1440core/./geos() [0x13d93e8]
   etc
===================
Program received signal SIGABRT: Process abort signal.

My libraries are as follows (plus UCX 1.6.0):
  1) git/2.17.0-fasrc01      7) zlib/1.2.11-fasrc02
  2) gmp/6.1.2-fasrc01       8) szip/2.1.1-fasrc01
  3) mpfr/3.1.5-fasrc01      9) hdf5/1.10.6-fasrc03
  4) mpc/1.0.3-fasrc06      10) netcdf/4.7.3-fasrc03
  5) gcc/9.3.0-fasrc01      11) netcdf-fortran/4.5.2-fasrc04
  6) openmpi/4.0.2-fasrc01  12) cmake/3.16.1-fasrc01

My run is at c180, and NX=16 and NY=90. I am using 24 cores per node across 60 nodes, reserving full 128G memory for each. Originally I encountered this error at the beginning of the run because I had periodic checkpoints configured (RECORD_* in GCHP.rc) which caused a checkpoint to be written at the beginning of the run.
@LiamBindle also encountered this problem on a separate compute cluster with c360 using 1200 cores.
Have you seen this before?

I received a similar error running a C360 sim on 1200 cores. The error message I got was
 ExtData Run_: Calculating derived fields
 ExtData Run_: End
 Character Resource Parameter: GCHPchem_INTERNAL_CHECKPOINT_TYPE:pnc4
 Using parallel NetCDF for file: gcchem_internal_checkpoint.20160701_0000z.nc4
[compute1-exec-78:49   :0:49]    ud_iface.c:747  Fatal: transport error: Endpoint timeout
==== backtrace ====
    0  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/libucs.so.0(ucs_fatal_error_message+0x60) [0x7fb40badbaa0]
    1  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/libucs.so.0(ucs_fatal_error_format+0xde) [0x7fb40badbc0e]
    2  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/ucx/libuct_ib.so.0(+0x4d355) [0x7fb4035d2355]
    3  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/ucx/libuct_ib.so.0(uct_ud_iface_dispatch_async_comps_do+0x10b) [0x7fb4035d246b]
    4  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/ucx/libuct_ib.so.0(+0x5bb90) [0x7fb4035e0b90]
    5  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/ucx-1.6.1-mcuwvv4bxhdyir2feixbksjpmymja2s7/lib/libucp.so.0(ucp_worker_progress+0x6a) [0x7fb40bf3cdba]
    6  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/openmpi-3.1.5-cfthlxoibydafwjia7vserai7ta7ip56/lib/libmpi.so.40(mca_pml_ucx_progress+0x17) [0x7fb40da757d7]
    7  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/openmpi-3.1.5-cfthlxoibydafwjia7vserai7ta7ip56/lib/libopen-pal.so.40(opal_progress+0x2b) [0x7fb40a51a3ab]
    8  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/openmpi-3.1.5-cfthlxoibydafwjia7vserai7ta7ip56/lib/libmpi.so.40(mca_pml_ucx_send+0x275) [0x7fb40da77645]
    9  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/openmpi-3.1.5-cfthlxoibydafwjia7vserai7ta7ip56/lib/libmpi.so.40(PMPI_Gatherv+0x190) [0x7fb40d95f830]
   10  /opt/spack/opt/spack/linux-centos7-skylake_avx512/gcc-8/openmpi-3.1.5-cfthlxoibydafwjia7vserai7ta7ip56/lib/libmpi_mpifh.so.40(MPI_Gatherv_f08+0xab) [0x7fb40dfb1d9b]
   11  /scratch1/liam.bindle/C1AT/GCHPctm/build-gnu/bin/geos() [0x136e57e]
   12  /scratch1/liam.bindle/C1AT/GCHPctm/build-gnu/bin/geos() [0x1380cec]
    .
    .
    .

My libraries are
bash-4.2$ spack find --loaded
==> 14 installed packages
-- linux-centos7-skylake_avx512 / gcc@8 -------------------------
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>rdma-core@20  <EMAIL_ADDRESS><EMAIL_ADDRESS>
In my run I have NX=10, NY=120. I used 30 cores per node across 40 nodes with 300 GB or memory per node.

A couple of things. First, do you set any OMPI_ environment variables or pass any mca options to the mpirun command?
Second, as a test can you see if adding:
WRITE_RESTART_BY_OSERVER: YES

to AGCM.rc (or your equivalent) does anything? I set it when I run GEOS with Open MPI but that's actually for a performance reason, not a 'things go crash' reason. (Or, conversely, if you run with that set to YES, can you try it with NO.)

For me,

First, do you set any OMPI_ environment variables or pass any mca options to the mpirun command?

My only OMPI MCA setting is:
bash-4.2$ env | grep OMPI_
OMPI_MCA_btl_vader_single_copy_mechanism=none

I must admit, I'm not familiar with these settings. Our sysadmin set this and I've used it blindly.
For the second point, I'll give WRITE_RESTART_BY_OBSERVER a try and report back once the job has run!

I've got a rerun in the queue with the WRITE_RESTART_BY_OSERVER setting and should have results tomorrow.
I actually use srun rather mpirun. I have nothing containing OMPI in env. Should I? My OpenMPI build settings are summarized in this file in case it's useful:
ompi_info.txt

It looks pretty standard. It looks like you built with UCX instead of verbs which I think is the current preferred method for Infiniband. I will note I often have issues with srun on discover, but maybe Cannon is different. I tend to stick with mpirun because I'm old. I suppose you could try that, but in the end I imagine Open MPI does the same thing.
The OMPI_MCA_btl_vader_single_copy_mechanism is one I've seen before when using Open MPI with containers and indeed:
https://github.com/GEOS-ESM/MAPL/blob/34eae4b436695ded67a9830ffe47a286de897bc9/.circleci/config.yml#L10
so I can't complain.
If I had a thought from what you've said, it might be to try a newer version of UCX. Say one in the 1.8 or the new 1.9.0. Though maybe that'll just cause different errors...

I checked this morning and my sim is ~3 days in, so it looks like
WRITE_RESTART_BY_OSERVER: YES

worked! Thanks! What does this switch do?

This is now solved for me as well. My first run kept srun but added WRITE_RESTART_BY_OSERVER. It crashed before even hitting writing the first checkpoint, but I think this was due to cluster issues given a couple other runs inexplicably failed but are fine today. For my latest run I swtiched to mpirun which adds some uncertaintly on what the fix exactly was, srun or not using the o-server for restart write. I'll narrow it down.

I checked this morning and my sim is ~3 days in, so it looks like
WRITE_RESTART_BY_OSERVER: YES

worked! Thanks! What does this switch do?

I'll ping @weiyuan-jiang to the thread to be more specific, but when I was trying to run with Open MPI on Discover, I found that it was taking ages to write out restarts. I think I eventually tracked it down to Open MPI having some bad MPI_GatherV (or Gather? can't remember) timings.  And guess what calls are used when writing checkpoints/restarts? 😄
So, I asked around and it turns out @weiyuan-jiang added a (somewhat hidden) ability for the IOSERVER to write the restarts instead of the "normal" path. The IOSERVER uses Send/Recv I think, so it bypassed the bad performing call.
Now, I will say that in our GEOSldas @weiyuan-jiang found some sort of oddity happening with the WRITE_RESTART_BY_OSERVER method. I can't remember what (binary restarts?) but I have never seen any issues in my testing with the GCM.

This is great. I'll add the line to the default GCHP.rc file for the GCHP 13.0.0 release, pending a response from @weiyuan-jiang on what the observed oddity was of course.

@lizziel Note that I only turn this on with Open MPI. I keep our "default" behavior with Intel MPI, etc. because, well, it works so don't rock the boat.
(Well, we do need I_MPI_ADJUST_GATHERV=3 for Intel MPI because the other GatherV algorithms seemed to have issues on our system, etc.)

I am checking with @bena-nasa . Eventually, we will eliminate the parameter WRITE_RESTART_BY_OSERVER.  So far without this parameter, the program goes to different branch which may cause problems.

If you do eliminate it, that would probably mean I have to stop using Open MPI on discover. It is the only way I can write checkpoints due to the crazy slow MPI_GatherV performance.

Could you update checkpoint writing to be similar to History writing so it avoids the problem?

Even we use WRITE_RESTART_BY_OSERVER, we still use mpi_gatherV. I am wondering if that is the problem.

@weiyuan-jiang But isn't it the case that when we use the OSERVER, the gatherv() is on a much smaller set of processes?    For the main application there are many cores and there are therefore many very small messages.   On the server it is much fewer cores and thus fewer and larger messages.

Oserver does not have mpi_gatherV.  This gatherV happens in the client side only in 1d tile space.  On the client side, it gathers all the data and then send it through oserver.  For multi-dimension, WRITE_RESTART_BY_OSERVER bypassed the gatherV. @tclune

@lizziel  Do you have problem after you set WRITE_RESTART_BY_OSERVER to yes?

It looks like you hit an MPI problem in a gatherV. Like Weiyan said, if you do the write by oserver option it bypasses doing a gatherV and takes whole different code path to write the checkpoint. So you have sidestepped the problem by not exercising the code that was causing the initial problem.

I have not noticed any run issues after setting WRITE_RESTART_BY_OSERVER to yes.

I am going to close this issue. Please keep @LiamBindle and myself informed if there is a new fix in a future MAPL release, or if this fix is to be retired without a replacement for the problem.

Last week I tried C360 with Intel MPI on Compute1 (WashU cluster) and the checkpoint file was being written extremely slowly. I saw @mathomp4's comment about about I_MPI_ADJUST_GATHERV=3, and I just thought I'd mention that this fixed my problem. Thanks @mathomp4!

Thanks @mathomp4—I will give that one a try as well.


Incorporate several modifications to the main script (detailed in the CHANGELOG file)

Hi @Hoohm,
I've been using your script and, because I find it very useful, I decided to incorporate some changes of my own to improve it. I've detailed them in the CHANGELOG.md file. Among the incorporated changes are: bug fixes, performance improvement, new features,  documentation, and some code refactoring (move some functionality into functions).
Please, consider incorporating this changes. And do not hesitate to contact me if you want to discuss anything.
Cheers,
Santiago

Thanks for this PR! I'll look at it this week :)

I've read the code.
A big thank you for the improved documentation of the functions, nice work.
I'm now testing your version with some real-life data. I'll get back to you when I'm done.

Sorry for the long time it took to deal with this.
It's now in the develop branch. I'll change one thing and push it to master. Instead of using e for the fuzzy grep, I'll use s to only deal with substitutions. You caught a nice mistake there, I actually wanted to deal with substitutions only and not insertions. Thanks a lot.
I'm working on a rework of citeseqcount to using multiple processes and lower memory usage. I hope to do this during those holidays.


add 'e-clickable' to allow element with e-form to still be clickable

I needed to auto-focus on a x-editable element automatically (i.e. when adding a set of fields in a ng-repeat directive, I wanted one of them to already be ready to receive keystrokes).
I saw that there was a $editable property published to the directive scope, but there is no documentation of examples on how to actually use it. I would be very interested to hear your thoughts on this.
I'm asking for a pull request of a change that would allow someone who'd like to externally trigger an editable field to also be able to keep the click behavior by adding e-clickable to the field. Here's an example:
{{myTest || 'Empty'}}

I updated the docs but I didn't updated the tests because they were run on the docs page and I didn't want to just add a variation of the "Trigger Manually" section. If you'd like me to do so, let me know.
If you think I can achieve a similar result differently, please let me know. What I really need is simply to publish the editable-text's $show function to the parent controller.

+1!


[release 4.8] Update CI vars

This should go a long way to helping fix the e2e tests in the OpenShift ci-operator checks.

@jarrpa is this PR still relevant?


[SPARK-50534][SPARK-50535][TEST][CONNECT] Fix sporadic test failures

What changes were proposed in this pull request?

Fix sporadic Spark Connect test failures.

SPARK-50534: VerifyEvents.this.listener.executeHolder was not declared "volatile", causing the thread to repeatedly read potentially outdated value. The data structure is only used by the test suite.
SPARK-50535: org.apache.spark.sql.connect.service.SparkConnectSessionManager.invalidateAllSessions is susceptible to system time synchronization (e.g., NTP), leaving stale sessions. invalidateAllSessions is only used by test suites.

Why are the changes needed?

Fix sporadic test failures.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Repeatedly ran testOnly org.apache.spark.sql.connect.planner.SparkConnectServiceSuite and org.apache.spark.sql.connect.service.SparkConnectServiceE2ESuite.
Was this patch authored or co-authored using generative AI tooling?

No.

Merged to master.


Small readme changes, a sample config file and an initial hello world…

… example while we sort things out
fixes #15

The passing build would seem to indicate I got the config.json correct. If we merge this one - we could then test exercism fetch pharo HelloWorld to see if things come down.
Next step would then be to officially put the exercism pharo packages somewhere official, so we could then try retrieving hello world in -image

I'm pretty happy with what you have there. Small steps (for a Small Talk 😂 ) but it's an improvement on what we had (an empty repo). I've left a few comments for you to consider, but I'm happy for you to merge this or continue working on it as you see fit.


KAFKA-15372: Reconfigure dedicated MM2 connectors after leadership change

This explores a non-forwarding solution to KAFKA-15372, in which a dedicated MirrorMaker2 leader will reconfigure connectors upon becoming the leader. This allows a rolling restart to apply connector configuration changes, while never needing a REST API to forward connector configurations between workers.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc: @dengziming as you might be interested in reviewing this

Test failures appear unrelated, and the mirror and runtime tests pass locally.


How to conditionally build com.auth0.jwt.algorithms.Algorithm instance based on properties

I have this JWT validation block where I need to build an Algorithm instance based on the 'alg' used by Identity Provider for signing. It could be 'RS256', 'HS256', 'RS512' or anything else.
Algorithm algorithm = Algorithm.RSA256((RSAPublicKey) getPublicKey(), null);
Verification verifier = JWT.require(algorithm);
verifier.build().verify(Jwt);

So my line of code "Algorithm.RSA256((RSAPublicKey).... " is now kind of hardcoded. How do I make this generic based on an Environment property input?
I'm using below version.
	<dependency>
		<groupId>com.auth0</groupId>
		<artifactId>java-jwt</artifactId>
		<version>3.10.3</version>
	</dependency>

@kamath237 The constructor for the Algorithm class has protected visibility, so this wouldn't be possible today. I assume you could do a when/switch statement over the algorithm name variable to decide that. Can you share a bit more about your use case? Especially about how that algorithm name value is dynamic and not known in advance.
Related: https://github.com/auth0/java-jwt/issues/434

@lbalmaceda I intend to do this in my product which goes to different customers who would invoke the APIs
that this product exposes with their own auth server issued token. As per the customers token specifications, I just need to update my application.yml with alg, issuer, x5c etc required to verify JWT - No choose changes and rebuild.
As you mentioned, switch case is an option, but I need to bring up an exhaustive list.

We don't have plans to add support for more algorithms in the near future, and we also don't want to support instantiating algorithms from a string / name value (decision made on the issue linked above). HS vs RS/EC algorithms vary in how the "secret" piece is passed, so there's no nice generic solution that we can ship with the SDK.
Although you might want to limit the allowed algorithms that your API supports, depending on your specific use case; you will have to maintain this list or switch yourself in case this happens to change.

Closing this issue as our decision is final.


[feat]: allow connections over plain http

Prerequisites

[X] I have searched for existing issues that already suggest this feature.

Describe the Feature Request
Embassy allows for some limited activity using http over the local network. However, when trying to use a service, we get a "You are using an unencrypted http connection". I realize this is trying to force people to be more secure, but the steps required to setup a CA are a bit more involved than I want to mess with just to test and evaluate Embassy and see if I want to use it at all. Also, every time I re-image an SD card, aren't I going to need to re-load a new CA everywhere?
Describe the Use Case
Testing and evaluation of start9/embassy
Describe Preferred Solution
Allow http after a warning message is confirmed.
OR
Allow a simpler, less intrusive setup like a wireguard VPN as is mentioned here: https://github.com/Start9Labs/embassy-os/issues/1607#issuecomment-1450733202 . The wireguard VPN can easily be setup and torn down on the client using Network Manager.
Describe Alternatives
Use kiosk mode, but this is limited because I can't copy/paste anything into that.
Anything else?
No response

Is there a reason you can't just add a security exception for the site in your browser? An encrypted connection without a trusted cert is still better than a plaintext connection. ARP spoofing attacks are more common than we are comfortable ignoring.

That option seems to have been removed in recent versions of Firefox.

I'm getting the following:

After further investigation, it seems this specific error comes when you try to go to the embassy by its IP address rather than a hostname. There are a few reasons why I want to do that (1) to choose whether I'm accessing the embassy by wifi or ethernet and (2) because I run a local fully resolving nameserver on my workstations so whatever magic you use to establish the .local hostnames is not possible. I'm not sure if my setup leads to a further incompatibility because you seem to be running a proxy web server that takes connections to different alias host names and redirects it to different webservers inside of docker containers?
When I use a workstation that does not run a fully resolving local nameserver, I get the same message as you show above.

I'm getting the following:

After further investigation, it seems this specific error comes when you try to go to the embassy by its IP address rather than a hostname. There are a few reasons why I want to do that (1) to choose whether I'm accessing the embassy by wifi or ethernet and (2) because I run a local fully resolving nameserver on my workstations so whatever magic you use to establish the .local hostnames is not possible. I'm not sure if my setup leads to a further incompatibility because you seem to be running a proxy web server that takes connections to different alias host names and redirects it to different webservers inside of docker containers?
When I use a workstation that does not run a fully resolving local nameserver and try connecting with a .local hostname, I get the same message as you show above.

mDNS (and aliasing) is what we're using - obviously we cannot support all the possible network configurations, but most routers support this.  You will have more options in this regard soon though, as our story around connectivity is evolving, beginning with our upcoming OS update (no ETA at this time).

We now sign certs for plain IP too, so you don't need mCNS to use SSL :)


HARP-7828: Update the npm packages

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1035   +/-   ##
=======================================
  Coverage   45.08%   45.08%
=======================================
  Files         237      237
  Lines       22255    22255
  Branches     5061     5061
=======================================
  Hits        10033    10033
  Misses      12222    12222

Continue to review full report at Codecov.

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


(#9158) Support old and new versions of STOMP gem.

The STOMP gem, up to release 1.1.4, used send to push messages to the
queue.  From 1.1.5 onward this is replaced by publish, and send issues a
deprecation warning, but still works.
This commit dynamically adapts to the best available method: if publish is
present we use that, otherwise we fall back to send, and fail cleanly if we
drift further.
This should behave correctly with all known versions of the STOMP gem, avoid
deprecation warnings, and still end up with the right results.
Signed-off-by: Daniel Pittman<EMAIL_ADDRESS>

Merged this into 2.7.x with 999355facb493509e3648845286d6fefe6f598fd


Possible duplication bug with Crafter

The Liquid Dirt mod has a shapeless recipe for making mud:
Dirt + Water Bucket -> Bucket of Liquid Dirt
This recipe works fine in a vanilla Crafting Table, but when crafted in an EnderIO Crafter it produces an extra bucket:
Dirt + Water Bucket -> Bucket of Liquid Dirt + Empty Bucket
Is this bug caused by an error in the Liquid Dirt mod, or with EnderIO?
EnderIO-1.7.10-<IP_ADDRESS>8_beta.jar
liquidDirt-1.3.jar
BTW, EnderIO is fantastic.  Thanks for all the hard work you put into this mod.

This requires that a crafting event is fired by the crafter


fix(aks-microservices-content.md): fixed linked to ri-deploy page whi…

Fixed Link to GitHub repo. current link resolves to 404

@doodlemania2 - Could you review? The change looks good, but I can't tell whether this is reference content that needs to be updated in another location or content that can be updated directly in the file. Thanks.

@ktoliver this looks good. @chauhansachinkr thanks for opening the PR.
We have recently migrated to a new architecture browser, and a few links were inadvertently updated from md > yml. These links have all been fixed in a PR against our private copy of this repo a few days ago. I'm assuming these fixes will go live today.
https://github.com/MicrosoftDocs/architecture-center-pr/pull/2218/files
We should be ok to also merge the PR from @chauhansachinkr.


TA Review (SRS): Fix Fit Criterion

Summary
The following feedback should be implemented:

[x] Fit criterion for MS2 inadequate
[x] Fit criterion missing for CR1, LR1
[x] Lot's of redundant rationale for requirements, or information that should just be included in the requirements itself (Ex. JG4)
[x] Rationale could be added to SR2

Deadline
Jan 8th, 2023
Estimated Work Hours
1 hour

Resolved with commits 3de0e651989dadceab6873d6cd86ff4da9c1fe73 and 6130a300bdadaddacc7561825ea496b8ce966312


blade html not indent

VSCode Version: 1.17.2 (1.17.2)
OS Version: OSX High Sierra 10.13.1

Hi i have problem with Laravel blade in vscode
I got this problem around 2 month ago, create issue at extension repository(https://github.com/onecentlin/laravel-blade-snippets-vscode)
extension-creator said it happen because html(php) not worked in blade
if i change syntax to html it's work fine but when change back to Laravel blade syntax it's not indent
How to solve this problem?
Thanks
ps. sorry for my bad english

I commented in the issue at the blade repo:
https://github.com/onecentlin/laravel-blade-snippets-vscode/issues/9#issuecomment-342758042


Fix compiler register allocation #117

Fix for the wrong register allocation of #117.
I introduced suffix_destreg() that selects the best candidate for register in case of suffix, similarly to codedestreg(). It looks if one or both of the suffix parameters are ETREG, and uses the lowest as a target (instead of allocating a new register). If both are different registers, one is freed.
I also needed to change the way compound allocation worked, since GETMBR/GETIDX normally re-uses the current register, compound assignment passes the target register in a new dst argument to multiple functions.
I finally changed some semantics in dst. Now dst < 0 means "don't care", i.e. allocate a new register if needed, whereas a specific number tells to use this register as target. dst < 0 makes it simpler than using finfo->freereg since the value can change along the run.
Added test case. All tests passed OK and changes tested extensively in the code base of Tasmota.

I did a dive deep in the code and added also my own comments. It's my understanding of the code and there may be some inaccuracies.


modules/nixpkgs: Make customizable & support multiple evaluations

I would highly appreciate review & comments on this. My main concerns going in were, roughly in order of priority:

Easily support overlaying Nixpkgs with self.overlays.default for use in pkgs
Easily support config.allowUnfree for use in NixOS or packages that require unfree
Keep merging & defaults simple & predictable
Efficiently evaluate Nixpkgs, ideally no more than once for a Nixpkgs argument attrset (including localSystem)
Easily support multiple Nixpkgs evaluations for use with (multiple) NixOS configurations

I feel like this patch's design addresses all of those concerns, with a relatively simple module to boot. I think the code is alright, but it could very well be better. I'm not confident.
Here's an example flake declaring its packages in a Nixpkgs overlay & consuming them via pkgs:
{
  description = "A program that produces a familiar, friendly greeting";

  inputs.flake-parts.url = "github:hercules-ci/flake-parts";
  inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
  inputs.systems.flake = false;
  inputs.systems.url = "github:nix-systems/default";

  outputs = { ... } @ inputs: inputs.flake-parts.lib.mkFlake {
    inherit inputs;
  } ({ inputs, lib, self, ... }: {
    config.systems = import inputs.systems;
    config.flake = {
      overlays.default = pkgsFinal: pkgsPrev: {
        hello = pkgsFinal.callPackage ./nix/nixpkgs-pkgs/hello { };
      };
    };
    config.nixpkgs.overlays = [
      self.overlays.default
    ];
    config.perSystem = { config, pkgs, ... }: {
      config.devShells.default = pkgs.callPackage ({ mkShell
      , hello
      }: mkShell {
        inputsFrom = [ hello ];
      }) {
      };
      config.packages = {
        inherit (pkgs) hello;
      };
      config.pkgs.default = config.pkgs.hello;
    };
  });
}

All that was necessary to integrate self.overlays.default into pkgs was a simple value for the nixpkgs.overlays option, and these derivations from pkgs can be directly used for perSystem.packages.
Let's say that the author also wants an easy way to test building their package against the latest NixOS stable, without switching inputs.nixpkgs.url or using --override-input nixpkgs <flake-url>.
--- a/flake.nix
+++ b/flake.nix
@@ -4,2 +4,3 @@
   inputs.flake-parts.url = "github:bb010g/flake-parts/enhanced-nixpkgs";
+  inputs.nixos-stable.url = "github:NixOS/nixpkgs/nixos-22.11";
   inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
@@ -18,5 +19,6 @@
     config.nixpkgs.overlays = [ self.overlays.default ];
-    config.perSystem = { pkgs, ... }: {
+    config.nixpkgs.evals.nixos-stable.input = inputs.nixos-stable;
+    config.perSystem = { nixpkgs, pkgs, ... }: {
       config.devShells.default = pkgs.callPackage ({ mkShell
       , hello
       }: mkShell {
@@ -26,3 +28,4 @@
       config.packages = {
         hello = pkgs.hello;
+        hello-nixos-stable = nixpkgs.nixos-stable.hello;
       };

Only 3 lines added and 1 line changed, which I'm pretty happy with. nixpkgs.evals has now been introduced, but the flake author knows that they're dealing with multiple Nixpkgs instantiations by this point, and they don't have to write Nixpkgs application boilerplate to do it. This example is contrived, but you can imagine this approach instead used so that a development NixOS machine can be using unstable Nixpkgs while a server is using stable Nixpkgs, maybe plucking a package or two from the same unstable as the development machine.
I'm imagining a lot of nixpkgs.config usage will just look like config.nixpkgs.config.allowUnstable = true;. I haven't bothered replicating the Nixpkgs config module here because I think it'd be more bother than it's worth. As such, values of nixpkgs.config are types.raw and they'll eagerly fail to merge. This may be annoying for flake authors but it prevents unintended merge behavior.
By utilizing perSystem, all Nixpkgs evaluations can be shared between modules and the nixpkgs and pkgs module arguments won't force extra evaluations (to my knowledge). I don't know if perSystem.nixpkgs.evals.<name>.output should be hidden / internal, but I leaned towards public for now, partially so it's clear to flake authors what's going on. The documentation for this option should probably be improved to reflect that.
I debated about using RFC 42–style nixpkgs.settings, nixpkgs.evals.<name>.settings, & perSystem.nixpkgs.<eval>.settings options, to be used like nixpkgs.settings.overlays, but I don't know if the flexibility provided there justifies the extra verbosity. These options would likely be submodules with config._module.freeformType = types.lazyAttrsOf types.raw; if they did exist, so that options like nixpkgs.settings.overlays can be documented & specified to merge. This would also be more future-proof, but if Nixpkgs does accept this upstream, then that flexibility would not an issue.
This patch does not configure transposition or otherwise expose any option config data under flake.<system>. Sharing of values (e.g. via flake output) for config.nixpkgs.config or any other option is left up to the user. I personally wouldn't mind placing some of this data in the output, but that's a larger proposal that I want to avoid here.
I don't really know where _file is and is not inferred in flake-parts modules. Documentation on this for module authors somewhere would be nice.

I refactored the top-level nixpkgs module to have a freeform nixpkgs.settings submodule. Options no longer need to be re-declared in nixpkgs.evals.<name>.settings. perSystem.nixpkgs.evals.<name>.settings has been added to make default localSystem less magical.

Short turnaround, but I changed the nixpkgs.settings submodule to use shorthandOnlyDefinesConfig. nixpkgs.settings.config.allowUnfree = true; really should just work, and not require nixpkgs.settings.config.config.allowUnfree = true;, and settings.config.config would probably be a problem in future attempts to upstream this module to Nixpkgs and move it out of flake-parts. This deviation from project style is explained in comments in the module source.

This is a big module. That's not necessarily bad, but not good for everyone. Flake-parts is meant to be an unopinionated core, so this module should, as suggested in nixpkgs.nix, not be merged. Instead, users should choose which module to use.

If that's the case, would the current Nixpkgs module be moved to extra? I'm worried about incompatibility if other flake modules decide to build off this. (I've been concurrently working on a perSystemNixosConfigurations module on top of this module, and it meshes really nicely. Sharing a minimal amount of Nixpkgs evaluations between a whole set of machines is great, and it falls out naturally from this module's design.)

That said, of course I appreciate your effort, and I would like your module to be listed on flake.parts, so here's a review. Also, would you mind if I merge just some of your maintenance-oriented commits?

If you want to start merging maintenance comments now, go for it. I tacked on a few more commits extending the dev debugging tools & evaluation test suite while exploring an existing flake-parts regression that I thought was due to new code. (I think flakes really need to pass sourceInfo alongside self to flake.outputs for error messages involving the flake's path to not infinitely recurse. We can't do anything here besides suggest manually specifying _file = ./flake.nix; or flake-utils.lib.mkFlake { inputs = { sourceInfo.outPath = ./.; } // inputs; }.)

@roberth Reading https://github.com/divnix/call-flake/commit/5828e083daac39efb098dc719502379f2bf2ed8a, it looks like both outPath and sourceInfo would have to be inputs to outputs that don't force self in order to consistently provide proper error messages when evaluation of self errors?


Proptype validation

ReactImageUploadComponent.PropTypes = {
should be ReactImageUploadComponent.propTypes = {
an error is thrown in the console currently

Fixed with 1.0.3.


Compile error on half.hpp

In file included from ./support/Half.h:36:0,
from ./arm_compute/core/Types.h:29,
from ./arm_compute/core/IAccessWindow.h:29,
from ./arm_compute/core/AccessWindowStatic.h:28,
from src/core/AccessWindowStatic.cpp:24:
include/half/half.hpp:275:8: error: missing space between ‘""’ and suffix identifier
half operator""_h(long double);

We've never seen that error, could you please tell us what compiler version you're using and what SCons options?

scons on linux armv7a debug=0 assert=0


[ARTEMIS-1257] IJ020017: Invalid archive: file://RaActivatoractivemq-…

…ra when pooled connection factory rebalance-connections is set to true
ARTEMIS: https://issues.apache.org/jira/browse/ARTEMIS-1257

Well.. even if the change is valid.. we need to understand what is the issue..
perhaps the type needs to match the method?
on which case the description of the JIRA is wrong... it would be something generic not tight to Wildfly.

there are a lot of other booleans on the ActivactionSpec.. what if you set shareSubscriptions to true for instance?
I'm not convinced of an issue in Artemis yet.

At least the JIRA here is wrong.. this could be the cause of a Wildfly issue.. but the issue is there.. a mismatch somewhere. you should rename this to matching boolean property to Boolean as specified somewhere else.. I'm fine with this... but the file:// error won't translate here.


The trimWhitespace property does not work when pasting from .xlsx files

Description
When I copy rows from the .xlsx file to the handsontable, the leading and trailing spaces in the data are not removed, But if I click on a cell, the space will be removed. Even if I set the 'trimRows' and 'trimWhitespace' property values to true, the problem remains.
Steps to reproduce

Write a string with leading or trailing spaces in a .xlsx file;
Copy this string and paste it in a cell of handsontable;
Click the cell to see if the spaces exist.

Demo

no changes to the original demo,but this issue can be reproduced.
https://jsfiddle.net/handsoncode/c6rgz08x/
Your environment

React wrapper version: same as the demo
Handsontable version: same as the demo
Browser Name and version: Chrome 87.0.4280.88(64 bit)
Operating System: Windows10

Hi @GithubOfWZS
This issue seems to be the same as this one https://github.com/handsontable/handsontable/issues/3930
If there is something important what we missed please share a comment to https://github.com/handsontable/handsontable/issues/3930

Hi @GithubOfWZS
This issue seems to be the same as this one https://github.com/handsontable/handsontable/issues/3930
If there is something important what we missed please share a comment to https://github.com/handsontable/handsontable/issues/3930


Add French Language section

@13pass Whoa that's awesome thank you so much! Love the idea of including other languages!

You're welcome, actually I'd love to discover platforms for hispanic speakers as well.


call grpc_init for GoogleDefaultCredentials

The grpc_google_default_credentials_create call assumes grpc_init has been called, or it will crash if hit the gce detection part. Our C++ wrapper call grpc_init when a Credentials object is created and thus is too late.
I think default credentials is the only one with the problems as all others have trivial create() calls.

Fixes #2290

LGTM. Will merge when jenkins is greenish.


Userbase server redirects http requests to https

We might need to change some load balancer params for this to work. I don’t think it’s listening on port 80. But safe to merge.


fix(ios): Prevent removal of one or many pages at a time

Fixes #465
Prevent crash when removing one or many pages at a time
Test Plan

What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅

Checklist

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I updated the typed files (TS and Flow)

@yinjun322 could you resolve the conflicts ?

@yinjun322 could you resolve the conflicts ?

done

https://github.com/callstack/react-native-pager-view/releases/tag/v5.4.9

This issue is not fixed yet. The crash is still happening in iOS.


⚠ Thumbnails API Endpoint has degraded performance

In ba63fa7, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 4018 ms

Resolved: Thumbnails API Endpoint performance has improved in d8d09e5 after 9 minutes.


Universal Links not working on iOS

Build/Submit details page URL
https://expo.dev/accounts/sinan2000/projects/pocketchef-recipe-generator/builds/655bc067-68ab-4993-a62c-6345bf0a0cf8
Summary
I cannot setup Universal Links for iOS. As the AASA file is correctly setup, I doubt if the EAS build command correctly takes the applinks I setup inside app.json for my app, as it simply does not open any type of link inside my app. I test it on TestFlight, and have iOS 17.2.1. I do NOT have access to a Macbook, so I develop only on the managed workflow and cannot eject.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22631
Binaries:
Node: 18.17.1 - C:\Program Files\nodejs\node.EXE
npm: 10.2.2 - C:\Program Files\nodejs\npm.CMD
npmPackages:
expo: ^49.0.21 => 49.0.21
react: 18.2.0 => 18.2.0
react-native: 0.72.6 => 0.72.6
Expo Workflow: managed
✔ Check Expo config for common issues

✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✖ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK
Detailed check results:
Some dependencies are incompatible with the installed expo version:
<EMAIL_ADDRESS>- expected version: 1.18.2
Your project may not work correctly until you install the correct versions of the packages.
Fix with: npx expo install --fix
Found outdated dependencies
Advice: Use 'npx expo install --check' to review and upgrade your dependencies.
One or more checks failed, indicating possible issues with the project.
Error output
No response
Reproducible demo or steps to reproduce from a blank project
I have setup the AASA file correctly on my website, and it is uploaded to apple's CDN: https://app-site-association.cdn-apple.com/a/v1/pocketchef.ro
Inside my app, at app.json, this is my iOS setup:
"ios": {
"supportsTablet": true,
"bundleIdentifier": "com.sinan2000.pocketchef",
"buildNumber": "1.0.9",
"associatedDomains": [
"applinks:pocketchef.ro"
]
},
Inside my App.js, I configured linking as such:
const linking = {
prefixes: ['https://pocketchef.ro'],
config: {
screens: {
screen1: {
path: 'account/?mode=resetPassword',
parse: {
oobCode: (oobCode) => oobCode,
},
},
screen2: {
path: 'account/?mode=verifyEmail',
parse: {
oobCode: (oobCode) => oobCode,
},
},
},
},
};
The links I would like to open have the format https://pocketchef.ro/account/?mode=...&oobCode=...
I have already tried with a couple of builds and it seems like Universal Links is not working at all... I cannot figure out the issue.

It appears like it solved by its own. Maybe the CDN from apple or their systems took time to update.

hi my universal link works but want to ask a question,
when i use something like this: https://mysite.com, it works
but if it is prefixed by www, it dosent work
so: https://www.mysite.com, dosent work
is there any work around for this?

hi my universal link works but want to ask a question,
when i use something like this: https://mysite.com, it works
but if it is prefixed by www, it dosent work so: https://www.mysite.com, dosent work
is there any work around for this?

This saved my day, thanks.


Setting post_trial_gap after trial

Hi, I really enjoy using the library so far, great work!
Is there a way to control the post_trial_gap given what happens in the trial? As far as I understand, passing a function will evaluate it at the start of the trial. My use case is a task after which a "too slow" notice should be shown immediately, if the participant didn't answer. So I want to set the post_trial_gap to zero in case there was no response.

Hi @jkrumbiegel, I don't think there's a way to do that because, like you said, all of the trial's dynamic parameters will evaluate at the start of the trial (with the exception of event-related callback functions). A clumsy workaround would be to use a blank 'trial' as your ITI instead of the post_trial_gap, so that you can control when/whether the ITI occurs and its duration, based on what happened during the last trial. And if you always want an ITI of the same duration before the start of every trial, then you could just put the 'too slow' message inside of a conditional that comes directly after the main trial, and then have the ITI trial after the too slow conditional, like this:
    var trial = {
        type: 'html-keyboard-response',
        stimulus: 'Enter a key!',
        choices: jsPsych.ALL_KEYS,
        trial_duration: 1000
    };
    var too_slow = {
        type: 'html-keyboard-response',
        stimulus: 'Too slow!',
        trial_duration: 2000
    };
    var too_slow_conditional = {
        timeline: [too_slow],
        conditional_function: function() {
            var last_rt = jsPsych.data.getLastTrialData().values()[0].rt;
            if (last_rt == null) {
                return true;
            } else {
                return false;
            }
        }
    };
    var iti = {
        type: 'html-keyboard-response',
        stimulus: '',
        choices: jsPsych.NO_KEYS,
        trial_duration: 500
    };

    jsPsych.init({
        timeline: [trial, too_slow_conditional, iti, trial, too_slow_conditional, iti],
        on_finish: function () {
            jsPsych.data.displayData();
        }
    });

I hope this helps!

Hi Becky, the approach with the full trial and conditional timeline is exactly how I'm currently solving the problem, it's just not a very clean solution. Given that the post_trial_gap happens after the trial it seemed sensible to me that there should be some way of changing it during the trial, before the waiting period is initiated.
Basically, I think all trial aspects that only become relevant after the trial body is over, should have a way of being changed if one doesn't want to rely on workarounds with additional trials etc. Something like a deferredVariable() function that is called at trial end to resolve it's value

Sorry @jkrumbiegel, I once again mistook this for a discussion post question rather than an issue! Oops 😬 Thanks for the suggestion - I agree this would be a much cleaner solution.
@jodeleeuw what do you think about adding the ability to set the post_trial_gap value during/after the trial, so that trial data can be used to determine the value? (And the same for any other parameter values that aren't needed until the end of the trial, although I can't think of any others apart from data, which can already be modified in the on_finish function).

I suppose we could add a second optional parameter to on_finish that allowed modifying this parameter value in place. I'm a little hesitant to add the complexity for the single-use case. I'm trying to come up with other cases where the suggestion of a deferredVariable could be applied. @jkrumbiegel any ideas?

I suppose we could add a second optional parameter to on_finish that allowed modifying this parameter value in place. I'm a little hesitant to add the complexity for the single-use case. I'm trying to come up with other cases where the suggestion of a deferredVariable could be applied. @jkrumbiegel any ideas?


[Event Request] OnGetDeferralPostDate

Table 37 "Purchase Line"
 field(1700; "Deferral Code"; Code[10])
        {
            Caption = 'Deferral Code';
            TableRelation = "Deferral Template"."Deferral Code";

            trigger OnValidate()
            var
                DeferralPostDate: Date;
            begin
                GetSalesHeader();
                OnGetDeferralPostDate(SalesHeader, DeferralPostDate, Rec);
                if DeferralPostDate = 0D then
                    DeferralPostDate := SalesHeader."Posting Date";

                DeferralUtilities.DeferralCodeOnValidate(
                    "Deferral Code", DeferralUtilities.GetSalesDeferralDocType, '', '',
                    "Document Type", "Document No.", "Line No.",
                    GetDeferralAmount(), DeferralPostDate,
                    Description, SalesHeader."Currency Code");

                if "Document Type" = "Document Type"::"Return Order" then
                    "Returns Deferral Start Date" :=
                        DeferralUtilities.GetDeferralStartDate(DeferralUtilities.GetSalesDeferralDocType(),
                            "Document Type", "Document No.", "Line No.", "Deferral Code", SalesHeader."Posting Date");
            end;
        }

We need the Event "OnGetDeferralPostDate" also in Table 39 "Purchase Line" and Table 91 "Gen. Journal Line"
Table 39 "Purchase Line":
        field(1700; "Deferral Code"; Code[10])
        {
            Caption = 'Deferral Code';
            TableRelation = "Deferral Template"."Deferral Code";

            trigger OnValidate()
            var
                DeferralPostDate: Date;
            begin
                GetPurchHeader;
>>NEW CODE START
                OnGetDeferralPostDate(PurchHeader, DeferralPostDate, Rec);
                if DeferralPostDate = 0D then
                    DeferralPostDate := PurchHeader."Posting Date";
<<NEW CODE END
                DeferralUtilities.DeferralCodeOnValidate(
                  "Deferral Code", DeferralUtilities.GetPurchDeferralDocType, '', '',
                  "Document Type", "Document No.", "Line No.",
                  GetDeferralAmount(), DeferralPostDate,
                  Description, PurchHeader."Currency Code");

                if "Document Type" = "Document Type"::"Return Order" then
                    "Returns Deferral Start Date" :=
                      DeferralUtilities.GetDeferralStartDate(DeferralUtilities.GetPurchDeferralDocType,
                        "Document Type", "Document No.", "Line No.", "Deferral Code", PurchHeader."Posting Date");
            end;
        }

Table 91 "Gen. Journal Line"
        field(1700; "Deferral Code"; Code[10])
        {
            Caption = 'Deferral Code';
            TableRelation = "Deferral Template"."Deferral Code";

            trigger OnValidate()
            var
                DeferralUtilities: Codeunit "Deferral Utilities";
            begin
                if "Deferral Code" <> '' then
                    TestField("Account Type", "Account Type"::"G/L Account");
>>NEW CODE START
                OnGetDeferralPostDate(DeferralPostDate, Rec);
                if DeferralPostDate = 0D then
                    DeferralPostDate := "Posting Date";

                DeferralUtilities.DeferralCodeOnValidate("Deferral Code", DeferralDocType::"G/L", "Journal Template Name", "Journal Batch Name",
                  0, '', "Line No.", GetDeferralAmount(), DeferralPostDate, Description, "Currency Code");
<<NEW CODE END
            end;
        }

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Introduce U64HashSet to dedup u64 which are already hashed.

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


Add captured headers options for tracing

What does this PR do?
This PR introduces two options for copies of the request or response headers to client and server spans as attributes.
It follows the Open Telemetry semantic conventions for the attributes naming, e.g: http.request.header.<key> and http.response.header.<key>

Motivation
Provide an opt-in way to create span attributes from the request or response headers.
It supersedes PR #10423.

More

[x] Added/updated tests
[x] Added/updated documentation

Additional Notes
Co-authored-by: Baptiste Mayelle<EMAIL_ADDRESS>

@rtribotte Is this feature not available in versions prior to 3.0?

@rtribotte Is this feature not available in versions prior to 3.0?

Indeed, the changes are targeted for the v3, so the v2 won't have this feature.


fix: resolve pod creation failure on retry when using workspace.<name>.volume

fix #7886
Change the naming method of the workspace volume from completely random to hashed, ensuring that the name generated during a single taskRun lifecycle is consistent each time, and is unique within all current workspaces.
This way, we can reuse the logic of retrieving the taskSpec from the status, and also store the content after variable expansion in the taskSpec of the status for easy debugging; it will also not affect the reconstruction of the pod when retrying.

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] pre-commit Passed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

/kind bug
Release Notes
fix: resolve pod creation failure on retry when using `workspace.<name>.volume`

/lgtm

/lgtm


Integrate dtsc_sizing_test into Catalyst's mistserver build pipeline

Have a look at Marco's other regression testing

Endpoint of ticket: create additional testing tickets once this first unit test is implemented.

This is Mist isolated unit testing

They aren't available right now. @KatriOinonen is currently rewriting the tests to be meson compatible


[SPARK-18160][CORE][YARN] spark.files should not be passed to driver in yarn-cluster mode

What changes were proposed in this pull request?
spark.files is still passed to driver in yarn mode, so SparkContext will still handle it which cause the error in the jira desc.
How was this patch tested?
Tested manually in a 5 node cluster. As this issue only happens in multiple node cluster, so I didn't write test for it.

Test build #67699 has started for PR 15669 at commit 67a5ccf.

Test build #67699 has finished for PR 15669 at commit 67a5ccf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

@vanzin @JoshRosen @yanboliang @brkyvz Please help review.

I thought we had fixed this in 2.0 to make it consistent that anytime --files is specified with yarn it goes through distributed cache.  It shouldn't be using the spark addFiles method to distribute.  Perhaps that broke?  @vanzin  do you remember

Quite strange --files in yarn-client will fall into SparkContext? AFAIK it will be handled by yarn#client to add to distributed cache, it will not involve SparkContext's addFiles.

@jerryshao spark.files is always passed to driver so SparkContext.addFile is called in yarn-cluster.
https://github.com/apache/spark/blob/7bf8a4049866b2ec7fdf0406b1ad0c3a12488645/core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala#L609
    // Load any properties specified through --conf and the default properties file
    for ((k, v) <- args.sparkProperties) {
      sysProps.getOrElseUpdate(k, v)
    }

Seems the issue is that spark.files don't need to be passed to driver in yarn-cluster mode. In that case it can be fixed in SparkSubmit.scala, another thing is that I notice some suspicious code in SparkContext.addJar, Is the following code still needed ? https://github.com/apache/spark/blob/39e2bad6a866d27c3ca594d15e574a1da3ee84cc/core/src/main/scala/org/apache/spark/SparkContext.scala#L1710
 if (master == "yarn" && deployMode == "cluster") {
              // In order for this to work in yarn cluster mode the user must specify the
              // --addJars option to the client to upload the file into the distributed cache
              // of the AM to make it show up in the current working directory.
              val fileName = new Path(uri.getPath).getName()
              try {
                env.rpcEnv.fileServer.addJar(new File(fileName))
              } catch {
                case e: Exception =>
                  // For now just log an error but allow to go through so spark examples work.
                  // The spark examples don't really need the jar distributed since its also
                  // the app jar.
                  logError("Error adding jar (" + e + "), was the --addJars option used?")
                  null
              }
            } else {

From the code what I can is that spark.files will not be set in yarn mode.
      OptionAssigner(args.files, LOCAL | STANDALONE | MESOS, ALL_DEPLOY_MODES,
        sysProp = "spark.files"),

spark.files would still be passed to driver even in yarn-cluster if you check the following code.
https://github.com/apache/spark/blob/7bf8a4049866b2ec7fdf0406b1ad0c3a12488645/core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala#L609
    // Load any properties specified through --conf and the default properties file
    for ((k, v) <- args.sparkProperties) {
      sysProps.getOrElseUpdate(k, v)
    }

yeah so I think the fix here should be that we don't pass it through or don't handle it in sparkContext.  All the yarn stuff should go through the distributed cache.

I agree with Tom, for yarn cluster mode we should rely on distributed cache

If I understand the issue here, the problem is not --files but setting spark.files through --conf (or the config file). The former is translated into spark.yarn.dist.files by SparkSubmit but it seems the latter isn't, and to me that's the bug. So basically what Tom and Mridul have said.
I think the correct fix would be in either SparkSubmit.scala or YARN's Client.scala - probably the latter to keep the YARN-specific stuff in one place.

that's correct, it is due to spark.files, jira has been updated.  Will update the PR soon.

Test build #67868 has started for PR 15669 at commit 230d56c.

Test build #67868 has finished for PR 15669 at commit 230d56c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #67885 has started for PR 15669 at commit b8aa1fb.

Test build #67885 has finished for PR 15669 at commit b8aa1fb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

I think this issue also existed in yarn client mode, files will be added twice (once with Spark's file server, another with distributed cache), because both file server and yarn#client could find this file, then there's no exception. But this will be failed in yarn cluster mode since spark file server could not find out file with specified path.

That's correct, this PR will also fix the yarn-client case. PR title is updated.

One minor comment update, otherwise LGTM.

Test build #67941 has started for PR 15669 at commit 0dd5486.

I'm wondering is it enough to address issue in yarn client mode, since we will have to properties "spark.files" and "spark.yarn.dist.files", the former will be handled by SparkContext and the latter will be handled by yarn#client, while yarn#client is created after SparkContext is launched, so is it too late to remove "spark.conf" in yarn#client, also yarn#client only honors "spark.yarn.dist.files", this will still add files again.

hmm, notice spark.files is still passed to SparkContext in yarn-client mode, seems I need to do that in SparkSubmit

I think it would be better to treat that as a separate issue. spark.files has always worked like this in client mode; the behavior being changed here fixes an actual bug in cluster mode.
I'd consider using the cache for spark.files in client mode a separate enhancement.

Test build #67941 has finished for PR 15669 at commit 0dd5486.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Merging to master / 2.0.

Looks like there's a branch-2.1 now, so I merge into that branch too.


Music Assistant does not support the opus file format

What version of Music Assistant has the issue?
2024.1.x
The problem
opus files are not recognized by Music Assistant
How to reproduce
when i put  opus files in the local media folder they are not shown. Other file formats are
Relevant log output
No response
Additional information
the following Feature request  https://github.com/orgs/music-assistant/discussions/855 was asking for it too,
What version of Home Assistant Core are your running
2024.1.5
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Should be fixed in beta 86 when it is released. Report here after then if not and I will reopen.


feat(183909391): Add Project State Icon/Spinner

Pull Request Description
This PR adds an icon to each project in the table of projects owned by the user. This icon consists of a spinner + icon inside the spinner. The icon inside the spinner can either be a "play" or a "pause" icon. When the project is in a closed state, the icon will be a "play" icon. When the project is in an opened state, the icon will be a "pause" icon. Clicking on the button will start opening or closing the project, respectively. Opening or closing a project corresponds to starting a VM instance in the cloud with the project mounted on the filesystem and an IDE backend running the code on that filesystem.
While the project is in a transitional state (i.e., "opening" or "closing"), the spinner will spin around the icon, indicating that progress is being made. Once the project has finished "opening" or "closing", the spinner icon will change from a spinner icon (i.e. a ring with a rotating aperture) to a plain ring icon (i.e., with no aperture).
Important Notes

Adds spinner icon
Adds ring icon
Add play icon
Add pause icon
Add open project HTTP API
Add close project HTTP API
Modify ProjectsTable to use custom Entry, EntryModel, and EntryData types
Modify ProjectsTable FRP network to monitor for project entry selection and issue events
Add styles for project state icon/spinner

https://user-images.githubusercontent.com/641547/208096114-0b6f1c50-03f8-4756-b709-1e1dee423478.mov
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide build and ./run ide watch.

No desciption nor video.

Whoops, added now!

Given that we have decided to go with a React-based approach for the combined IDE & Cloud UI, this PR is no longer applicable and is being closed. The bug fixes and refactors from this PR that are still relevant have been separated into the following, smaller, PRs:
https://github.com/enso-org/cloud-v2/pull/116
https://github.com/enso-org/cloud-v2/pull/117
https://github.com/enso-org/cloud-v2/pull/118
https://github.com/enso-org/cloud-v2/pull/119
These PRs are being closed:
https://github.com/enso-org/enso/pull/3962
https://github.com/enso-org/cloud-v2/pull/98
The existing cloud_dashboard code is being removed in the following PR:
https://github.com/enso-org/enso/pull/4047


add reference to vector repo - insert called with nil-vector

Link creation to document without vectors (no text property) crashes:
Add property reference to object! Unexpected status code: 500, with response body: {'error': [{'message': 'add reference to vector repo: merge into index somelink: shard qYk4wrqx7Udm: update vector index: insert doc id 1 to vector index: insert called with nil-vector'}]}
How to reproduce:
import weaviate

client = weaviate.Client("http://localhost:8080")

client.schema.create_class({
                    "class": "SomeClass",
                    "vectorizer": "none", # explicitly tell Weaviate not to vectorize anything, we are providing the vectors ourselves through our BERT model
                    "properties": [
                        {
                            "name":"myClsProperty",
                            "description":"prop",
                            "dataType": ["boolean"]
                        }
                    ]
            })

client.schema.create_class({
                    "class": "SomeLink",
                    "vectorizer": "none", # explicitly tell Weaviate not to vectorize anything, we are providing the vectors ourselves through our BERT model
                    "properties": [
                        {
                            "name":"myLink",
                            "description":"document link",
                            "dataType": ["SomeClass"]
                        },
                        {
                            "name":"myProperty",
                            "description":"label",
                            "dataType": ["boolean"]
                        }
                    ]
            })

try:
    doc_id = client.data_object.create(
                        data_object={"myClsProperty":True},
                        class_name= "SomeClass"
                        )

    link_id = client.data_object.create(
                        data_object={"myProperty":True},
                        class_name= "SomeLink"
                        )

    client.data_object.reference.add(link_id,"myLink" , doc_id )

finally:
    #cleanup
    client.schema.delete_class("SomeClass")
    client.schema.delete_class("SomeLink")

Hi @ju-bezdek! I tried running your code snippet but cannot reproduce this with Weaviate 1.14.1 and Weaviate python client version 3.6.0. The clientdata_object_reference.add has been updated in the mean time, which now takes 2 additional arguments:
client.data_object.reference.add(link_id, "myLink", doc_id, "SomeLink", "SomeClass")
Please let us know if you're still running into this issue!


Theme Proposal

I've just written this Discord theme. Thoughts?

Seems good we need less transparent themes tbh


show & hide mapnik layers

Implements Windshaft-cartodb#550. Allows to show/hide layers by requesting the different layer indexes in the URL.
Note: It's still pending to use layer id as an alternative to current layer index

Mapnik layerId filtering is done.
I think we can CR.

I fixed layer interactivity issue. I'm ready for CR.
cc @rochoa


Fix several documents

REMARKS:

mbyte.txt
L804
Regression at https://github.com/vim/vim/commit/1c5728e0c4a9df930879f9f0ca108092d5902194#diff-b5ce8ea08d78c0baef6b22f54deb0c81f940d56c6d8cf651b29ce950e9367568L803-R804

syntax.txt
L937 - L946
Vim documentation typically follows the order "Code explanation" ---> "Code".
I have corrected the parts where the order was different.
If you don't like the default value writing style, change it.

--
Best regards,
Hirohito Higashi (h_east)

thanks!


fix(TFD-942): make Kafka getSample works, change to read from beginning

What is the current behavior? (You can also link to an open issue here)
Kafka getSample read the latest which not make sense
What is the new behavior?
Kafka getSample read from beginning
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Pull request test result: success :star:


Add a link for downloading Istio to the landing page.

Staging: https://geeknoid.github.io/istio.github.io/

tip: if you put
Fixes #962
somewhere in the description github will auto-closes the issue upon merge


Feedback for ocp-4.1

This pull request contains feedback after going through the ocp-4.1 workshop. I will also include notes on issues I could not address in this pr.

For the logging section, at the bottom of the page, the following instruction is present:
If you click the "x" in the column for the container name, and, in the left bar, click "add" for kubernetes.pod_name, you’ll then see your old Pod's logs, too. Remember, we scaled them down before coming here, so you can see how the log system is keeping a historical record.

I could not not the "x" as described above and could not complete this step. I'm wondering if it makes sense to remove it?

For the javascript-database section, there is a section about loading the data that says I should expect the following:
Items inserted in database: 2740

What I get is
504 Gateway Time-out
The server didn't respond in time.

For the logging section, at the bottom of the page, the following instruction is present:

If you click the "x" in the column for the container name, and, in the left bar, click "add" for kubernetes.pod_name, you’ll then see your old Pod's logs, too. Remember, we scaled them down before coming here, so you can see how the log system is keeping a historical record.

I could not not the "x" as described above and could not complete this step. I'm wondering if it makes sense to remove it?

Yes, can you remove it?

@jankleinert Removed it. Thanks for verifying.

Thanks @danielhelfand we updated the lab to ocp-4.5 can you check if everything have been fixed? In case you can open a new PR that help us fixing those in the new branch
Thanks!


Add support for new WDAC API

PR Summary
Implement new WDAC policy script file block option.
PR Context
WDAC API now supports the ability to allow/block PowerShell script files, whereas before the option was only to allow full/constrained language modes.  This PR implements the new API with fallback to original system lock down behavior.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

Ping - @anamnavi, @TravisEz13, @daxian-dbw

Sorry for the delay. Will do the review next Monday 😄

There was a breaking change in Windows 11 22H2 related to this feature which defaults CI script policy to block.  We should not backport this to 7.2 until we verify that this issue has been resolved.


Add NodeJS CI Workflow

Relies on #2  i.e. after Tests have been written.
Here is a possible
name: Node.js CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest

    strategy:
      matrix:
        node-version: [8.x, 10.x, 12.x]

    steps:
    - uses: actions/checkout@v2
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
    - run: npm install
    - run: npm run build --if-present
    - run: npm test
      env:
        CI: true

I've worked with github actions/workflows before. Can I take this one after the tests are written?

Ofcourse @trybick
@JuanVqz is working on #2
In the meantime, I will assign this to you.
Thanks

@trybick
Would you like to work on the tests in frontend i.e. docusarus while backend tests are being made?
In this Workflow, we will add both these tests.

I'm happy to do the workflow, but will pass on the tests, but thanks for the offer.

Hey @trybick
backend tests are in progress, in the mean time
Can you start on the frontend CI workflow that tests if the frontend build command i.e. npm run build is successful or not.
Let me know if you have any questions.

Yes I can start on the workflow - I should be able to start it tonight or next night 👍

Great 👍
here is a resource on this
https://v2.docusaurus.io/docs/deployment/#using-azure-pipelines
https://v2.docusaurus.io/docs/deployment/#triggering-deployment-with-travis-ci
P.S. no deploy command needed, only build
Thanks :)

@lelouchB I am confused about those two links - the original issue at the top has an example of a github workflow to run the tests, right? I thought that would do it

Yes, the issue is for tests but there are tests for frontend so currently a workflow to check build will be really helpful. because of the issues related to frontend.
After the backend tests are done, workflow will be updated to accomodate them
Does this make sense?
Let me know if you have any other questions

Still a little confused - We want a workflow to run the tests but those are on hold until backend tests are done. In the mean time we want to a workflow to run the build command? Does it need to deploy anywhere - or just check that build is successful?

Still a little confused - We want a workflow to run the tests but those are on hold until backend tests are done. In the mean time we want to a workflow to run the build command? Does it need to deploy anywhere - or just check that build is successful?

Yes that's correct.
I am fine with build only but if you want you can add deploy command too. It can be helpful to see actual changes.
What do you think?

Ok, just to confirm, the build workflow would just confirm the build is successful and then exit right? If we wanted to deploy too I think that would involve a lot more

Ok, just to confirm, the build workflow would just confirm the build is successful and then exit right? If we wanted to deploy too I think that would involve a lot more

Yes, it will tell if the build is successful and then exit.
yep, the deployment preview will involve a lot more so we can take it step by step. build is a priority right now so we should proceed with it first.
Thanks

Ok, thanks for clarifying!

Hey @trybick
Lint script has been added to backend, do you think you  an add it to workflow?
Thanks

Hey @lelouchB sure! Would that be a new workflow to just run the lint command in the backend?
I also was thinking, would you want a pre-commit hook added? - so every time someone commits it lints and prettifies the code - an option if you want to consider :)

Hey @lelouchB sure! Would that be a new workflow to just run the lint command in the backend?
I also was thinking, would you want a pre-commit hook added? - so every time someone commits it lints and prettifies the code - an option if you want to consider :)

Yes yes that pre commit hook would be amazing too.


Remove unused tracker detector instance

Task/Issue URL: https://app.asana.com/0/488551667048375/1206398717811159/f
Description
Remove unused tracker detector instance
Steps to test this PR
Smoke tests VPN/AppTP working separate and together

develop

#4100   👈

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite


Adding regex validation to HostnameValidator

Original PR by: @fletch3555
All credits go to him.
Simply test case created based on his info, Github is acting weird so that's why this is a new PR.

The only concern I have (other than the tests failing, not sure why yet) is that the hostname validator might now be too strict for local development. Can we include local domains as well in the test, eg localhost for simplicity sake?

@luceos
As per your message here and the quick discussion on Discord, I'll provide a more detailed answer here for documentation purposes as well.
Local Development
We should support Local Development as much as we can, however, at the end of the day, this is meant for production and not keeping things local. When checking the regex (on Regex101 we can see it matches exactly the domains as @fletch3555 stated.
I added a few local development domains based on the link you provided on discord and common sense.

"localhost" is not matching and I think we should keep it that way. If people would develop a multi-tenant application on a local machine, it would still use subdomains and those will match using the new HostnameValidator.
If you want to actually localhost as matching as well, you can try something like this as the regex:
^((?:(?:\*|(?!-)(?:xn--)?[a-zA-Z0-9][a-zA-Z0-9-_]{0,61}[a-zA-Z0-9]{0,1})\.)(?:(?!-)(?:xn--)?[a-zA-Z0-9][a-zA-Z0-9-_]{0,61}[a-zA-Z0-9]{0,1}\.)*(?!-)(?:xn--)?(?:[a-zA-Z0-9\-]{1,50}|[a-zA-Z0-9-]{1,30}\.[a-zA-Z]{2,})|localhost)$
Hardcoded localhost as simply allowing words would result in also matching "bread" or things like that and I think that's quite some weird behavior.


Build Issue - can't build with networking support on Alpine

Build Process
Following the instructions as precisely as possible.
Describe how you build polybar, list the exact commands you are using:
I used the exact commands from that document:
git clone --recursive https://github.com/jaagr/polybar
mkdir polybar/build
cd polybar/build
cmake ..
sudo make install

If you build polybar directly from this repository:

Output of git describe --tags:
3.2.1

If you use some other way (like the AUR):
nope
List exactly where you are building from and which version you are building.
Build Log
Post everything that is output to the terminal while building polybar below. This HAS to include the output of the cmake and make commands, if you used them.
cmake output...
-- Trying to enable ccache
-- Using compiler cache /usr/bin/ccache
-- The C compiler identification is GNU 6.4.0
-- The CXX compiler identification is GNU 6.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type specified; using RelWithDebInfo
-- Using supported compiler GNU-6.4.0
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.5.3")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Checking for module 'cairo-fc'
--   Found cairo-fc, version 1.15.12
-- Checking for module 'alsa'
--   Found alsa, version 1.1.6
-- Checking for module 'libnl-genl-3.0'
--   Found libnl-genl-3.0, version 3.4.0
-- Checking for module 'xcb-xkb'
--   Found xcb-xkb, version 1.13
-- Checking for module 'xcb-randr'
--   Found xcb-randr, version 1.13
-- Checking for module 'xcb-randr>=1.12'
--   Found xcb-randr, version 1.13
--  Build:
--    Type: RelWithDebInfo
--    CC: /usr/bin/cc  -O2 -g -DNDEBUG
--    CXX: /usr/bin/c++  -Wall -Wextra -Werror -Wno-noexcept-type -O2 -pedantic -pedantic-errors -O2 -g -DNDEBUG
--    LD: /usr/bin/ld
--  Targets:
-- [X]   polybar-msg
-- [ ]   testsuite
--  Module support:
-- [X]   alsa (1.1.6)
-- [ ]   curl
-- [X]   i3
-- [ ]   mpd
-- [X]   network (3.4.0)
-- [ ]   pulseaudio
-- [X]   xkeyboard (1.13)
--  X extensions:
-- [X]   xcb-randr (1.13)
-- [X]   xcb-randr (monitor support) (1.13)
-- [ ]   xcb-render
-- [ ]   xcb-damage
-- [ ]   xcb-sync
-- [ ]   xcb-composite
-- [X]   xcb-xkb (1.13)
-- [ ]   xcb-xrm
-- [ ]   xcb-cursor
--  Log options:
-- [X]   Trace logging
-- Found font: fixed:pixelsize=10
-- Found font: unifont:fontformat=truetype
-- Font not found: siji:pixelsize=10
-- Checking for module 'xcb-proto'
--   Found xcb-proto, version 1.13
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.15", minimum required is "2.7")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib/libxcb-image.so
-- Found XCB: /usr/lib/libxcb.so;/usr/lib/libxcb-icccm.so;/usr/lib/libxcb-ewmh.so;/usr/lib/libxcb-util.so;/usr/lib/libxcb-image.so
-- Searching for xcbgen with python2
-- Searching for xcbgen with python2.7
-- Searching for xcbgen with python3
-- Found xcbgen in /usr/lib/python3.6/site-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB_RANDR: /usr/lib/libxcb-randr.so
-- Found XCB: /usr/lib/libxcb.so;/usr/lib/libxcb-icccm.so;/usr/lib/libxcb-ewmh.so;/usr/lib/libxcb-util.so;/usr/lib/libxcb-image.so;/usr/lib/libxcb-randr.so
-- XCB[XKB]: Found component XKB
-- Found XCB_XKB: /usr/lib/libxcb-xkb.so
-- Found XCB: /usr/lib/libxcb.so;/usr/lib/libxcb-icccm.so;/usr/lib/libxcb-ewmh.so;/usr/lib/libxcb-util.so;/usr/lib/libxcb-image.so;/usr/lib/libxcb-randr.so;/usr/lib/libxcb-xkb.so
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Checking for module 'jsoncpp>=1.7.7'
--   Package 'jsoncpp', required by 'virtual:world', not found
-- Could not find jsoncpp>=1.7.7 -- building static lib...
-- JsonCpp Version: 1.7.7
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.15", minimum required is "2.6")
-- Configuring done
-- Generating done

make output...
[  4%] Built target xpp
[  9%] Built target jsoncpp_lib_static
[ 12%] Built target i3ipc++
[ 13%] Building CXX object bin/CMakeFiles/polybar.dir/adapters/net.cpp.o
/home/david/Projects/Software/polybar/src/adapters/net.cpp: In member function 'void polybar::v3_2_1::net::network::check_tuntap()':
/home/david/Projects/Software/polybar/src/adapters/net.cpp:197:41: error: 'caddr_t' does not name a type
     request.ifr_data = reinterpret_cast<caddr_t>(&driver);
                                         ^~~~~~~
/home/david/Projects/Software/polybar/src/adapters/net.cpp: In member function 'virtual bool polybar::v3_2_1::net::wired_network::query(bool)':
/home/david/Projects/Software/polybar/src/adapters/net.cpp:261:41: error: 'caddr_t' does not name a type
     request.ifr_data = reinterpret_cast<caddr_t>(&data);
                                         ^~~~~~~
/home/david/Projects/Software/polybar/src/adapters/net.cpp: In member function 'virtual bool polybar::v3_2_1::net::wired_network::connected() const':
/home/david/Projects/Software/polybar/src/adapters/net.cpp:286:41: error: 'caddr_t' does not name a type
     request.ifr_data = reinterpret_cast<caddr_t>(&data);
                                         ^~~~~~~
At global scope:
cc1plus: error: unrecognized command line option '-Wno-noexcept-type' [-Werror]
cc1plus: all warnings being treated as errors
make[2]: *** [bin/CMakeFiles/polybar.dir/build.make:89: bin/CMakeFiles/polybar.dir/adapters/net.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:822: bin/CMakeFiles/polybar.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Environment:

Distro (with Version):
Alpine Linux 3.8

Additional context
Add any other context that you think is necessary about the problem here.
When searching for general info about 'caddr-t' I found references to that type being rejected from becoming a posix standard and should be replaced with 'void *'. No idea if this idea has merit.
Wondering if I should just try the replacement and re-build, but the readme says to report any build issues, so here I am.

Replacing 'caddr-t' with 'void *' just raised complaints about assigning 'void *' to 'char *'.
Solution is to replace 'caddr-t' with 'char *' - that build successfully and appears to function correctly.

caddr_t is pretty damn old... not sure why it's being used here.
This fix should work, would you mind making a pull request for this?

sure thing :)


[POST]: initial WIP commit.  Need to figure out all required fields, …

…other constraints, and m2m models as well.

A few things worth pointing out:

number should be unique to a Post and a Project, not unique across the whole system. The number will need to be incremented and avoid the problem of a race condition.
we can leave out likes and comments counts for right now
status should be an enum of some sort. Not sure how to do in Elixir.
state is a state machine. Again not sure how to implement yet.
markdown is used to render the body to HTML
post depends on project, so this PR may be blocked until we implement that, which itself depends on organizations. We can still prep as much as we can
the markdown to HTML rendering pipeline in Rails renders the body with both syntax highlighting and github flavored markdown

Thanks for kicking this off. Let me know if you have questions about the above.

For the sequencing of posts, we used sequenced in Rails, which should be fairly trivial to port over to Elixir/Phoenix. Here's the relevant code that generates the ids.

I mentioned to @begedin in #62 that we can probably use earmark to accomplish the markdown and github-flavored markdown portions of this.
Syntax highlighting I have yet to figure out, but we may need to move over to the client, unfortunately.

We could replace aasm transitions from Rails with changeset pattern matching, something like:
def transition_changeset(%Model{state: "from_this_state"} = model, "to_this_state")
And then make a catchall that logs, complains, or just simply ignores transitions that we don't want.
Probably want to pass in a changeset and return that so we can pipe with other changesets in the model.

I believe that earmark is already implemented elsewhere so we can take what we learned there for the markdown portion.

Looks like for doing the number generation we can add a unique index on the [:repo_id, :issue_number] columns to ensure that no two issues within one repo can have the same number. Then we can use GenRetry to retry any failure to insert because of a duplicate index.

Closing in favor of #77. Will move relevant conversation from here over to there.


Add WITH_CXX11 configuration flag (currently for gcc and clang)

Hello!
Here's a patch for SociConfig.cmake. Instead of forcing the C++ standard to be 98, it adds a configuration switch. Unless the latter is explicitly turned on, the default mode is 98. Tested with Clang 3.3 and GCC 4.8.1 on Linux manually, since I'm not sure how to unit-test it (and not familiar with Travis, sorry).
(As of MSVC, its current level of C++11 support leaves me doubtful if it would compile at all...)

Since #336, we've got SOCI_CXX_C11 (default is OFF).