MQ container is not starting up

I am trying to run the MQ image (as default)  , the queue is not starting up.
sudo docker run
--env LICENSE=accept
--env MQ_QMGR_NAME=QM1
--volume /var/example:/var/mqm
--publish 1414:1414
--detach
ibmimages/mqadvanced
When i did a
"docker inspect imageid"
In status it gives Exit code as 71
The msconfig gives everything as pass (i changed a setting in /etc/sysctl.conf and saved it)
The MQ is still not starting up.
Can anyone please let me know what i am missing
Thanks

Is there anything in the docker logs output?  One thought is the filesystem for /var/example.  MQ only supports certain filesystem types, so if the /var/example directory (in this case) were on an unsupported filesystem, it would fail - you should get a message about this in the logs though.

Name:        WebSphere MQ
Version:     <IP_ADDRESS>
Level:       p800-002-150303.DE
BuildType:   IKAP - (Production)
Platform:    WebSphere MQ for Linux (x86-64 platform)
Mode:        64-bit
O/S:         Linux 3.16.7-tinycore64
InstName:    Installation1
InstDesc:
Primary:     No
InstPath:    /opt/mqm
DataPath:    /var/mqm
MaxCmdLevel: 801
LicenseType: Developer
mqconfig: V3.7 analyzing Ubuntu 14.04.2 LTS settings for WebSphere MQ V8.0
System V Semaphores
semmsl     (sem:1)  250 semaphores                     IBM>=32           PASS
semmns     (sem:2)  0 of 32000 semaphores      (0%)    IBM>=4096         PASS
semopm     (sem:3)  32 operations                      IBM>=32           PASS
semmni     (sem:4)  0 of 128 sets              (0%)    IBM>=128          PASS
System V Shared Memory
shmmax<PHONE_NUMBER>3692774399 bytes         IBM>=268435456    PASS
shmmni              0 of 4096 sets             (0%)    IBM>=4096         PASS
shmall              0 of<PHONE_NUMBER>3692774399 pages (0%)    IBM>=2097152      PASS
System Settings
file-max            928 of 524288 files        (0%)    IBM>=524288       PASS
Current User Limits (root)
nofile       (-Hn)  1048576 files                      IBM>=10240        PASS
nofile       (-Sn)  1048576 files                      IBM>=10240        PASS
WebSphere MQ queue manager 'QM1' starting.
The queue manager is associated with installation 'Installation1'.
AMQ7017: Log not available.
Its saying "AMQ7017: Log not available." does it imply the same??

Given that you seem to have a TinyCore Linux kernel, I'm guessing that you're using boot2docker.  Boot2docker uses the "rootfs" filesystem type for its root filesystem, including everything in /var.  MQ doesn't support this filesystem.  The solution is to put the volume elsewhere - for boot2docker, I'd recommend changing /var/example to /mnt/sda1/example.  Alternatively, you can omit the -v option completely, which will cause Docker to assign a valid volume - note that this then makes it harder then to check MQ's logs (which it writes to the volume).
A script in the Docker image is supposed to be checking this and giving an error message if the filesystem type is wrong, but doesn't seem to be happening - I will investigate.
This is not a supported filesystem type, and MQ is giving this (fairly unhelpful) message.

Thanks Arthur.
Yes, i am using boo2docker for Windows 7
I was able to get  the MQ Started by changing path  /var/example to /mnt/sda1/example.
I am trying to connect this MQ from a java client using MQ APis.
It giving Authetication error.i was assuming that by default its disabled
It will be really helpful if you can guide

Using MQSC command .Ran these two commands
ALTER QMGR CHLAUTH(DISABLED) CONNAUTH(' ')
REFRESH SECURITY TYPE(CONNAUTH)
But still no suceess .

FYI, I wrote a blog entry showing how to do this without turning CHLAUTH off completely (also see Morag Hughson's recent blog post).  Glad to hear you're up and running though.

Hi,
I had the same problem with volumes. I omitted the -v and got the QM running but I'm confused as to why this worked. Surely all volumes in the container are rootfs which MQ doesn't seem to like (couldn't find anything documented as to why MQ doesn't like these BTW). I also created my own image from scratch and ran into the same log issues despite installing MQ from OS up and creating the QM.

Hi All,
Thanks all for the valuable informations
while i am running my mqadvance from boot2docker vm in my windows 7 system , I am getting the following error . I would be good if anyone can help me regarding this
docker@boot2docker:~$ sudo docker run \

--env LICENSE=accept
--env MQ_QMGR_NAME=QM1
--publish 1414:1414
ibmcom/mqadvanced:MQv8

Name:        WebSphere MQ
Version:     <IP_ADDRESS>
Level:       p800-002-150303.DE
BuildType:   IKAP - (Production)
Platform:    WebSphere MQ for Linux (x86-64 platform)
Mode:        64-bit
O/S:         Linux 3.18.5-tinycore64
InstName:    Installation1
InstDesc:
Primary:     No
InstPath:    /opt/mqm
DataPath:    /var/mqm
MaxCmdLevel: 801
LicenseType: Developer
mqconfig: V3.7 analyzing Ubuntu 14.04.2 LTS settings for WebSphere MQ V8.0
System V Semaphores
semmsl     (sem:1)  250 semaphores                     IBM>=32           PASS
semmns     (sem:2)  0 of 32000 semaphores      (0%)    IBM>=4096         PASS
semopm     (sem:3)  32 operations                      IBM>=32           PASS
semmni     (sem:4)  0 of 128 sets              (0%)    IBM>=128          PASS
System V Shared Memory
shmmax<PHONE_NUMBER>3692774399 bytes         IBM>=268435456    PASS
shmmni              0 of 4096 sets             (0%)    IBM>=4096         PASS
shmall              0 of<PHONE_NUMBER>3692774399 pages (0%)    IBM>=2097152
PASS
System Settings
file-max            224 of 202141 files        (0%)    IBM>=524288       FAIL
Current User Limits (root)
nofile       (-Hn)  1048576 files                      IBM>=10240        PASS
nofile       (-Sn)  1048576 files                      IBM>=10240        PASS
ERROR: mqconfig returned a non-zero return code
In th above log the "System Setting " part is failing , although I am not using -v option

Try this :
Configuration changes before creating container.

Additional entries   required in linux kernel file (/etc/sysctl.conf)
fs.file-max = 524288
net.ipv4.tcp_keepalive_time = 300
Save it
$ sysctl –p

Hi
Thanks for valuable feedback , It is working fine now: gud luck

Hi
It would be very helpful , If any one can help me with the next steps to configure the queue , Actually my intention to run a queue with in docker and doing the pub/sub by using that docker container with queue images

You can use MQ client to configure Queues like MQExplorer , MQ Java libraray etc

Thanks a lot , My intention to configure MQ Advance Telemetry(MQTT) in docker , Is anybody has done this before
Thanks again
Sudip


Orchard.Layouts - Admin CSS gobbles up br tags in layout editor

Fresh installed 1.9.x
If you use shift-enter to add
 tags they aren't displayed correctly in the admin panel.
Example screenshot below:

Markup was:

This has some br breaks here:

and here:

But a rule in the admin stylesheet gobbles it up.

Offending rule:

This is an admin only bug, the
 tags are saved correctly and displayed on the front end.

@DanielStolt do you remember where you got this br reset snippet from because it doesn't seem to work?

@rtpHarry Hmm... My memory is somewhat vague on this, but I think I actually constructed this reset based on some spec from W3C detailing a "default user agent stylesheet". But I have noticed that lately this reset does not seem to have the desired effect anymore, because text in the layout editor seems to use fonts from the admin UI again... been meaning to look into it but haven't gotten around to it.

I checked it out and found w3c spec for html 4, that applied it to the br::before instead of br.
That's fixed it.

@sebastienros I think this one should have got moved over to the Orchard 1.10.2 milestone when it the pr was accepted yesterday. Is that how it works? 1.10.x while its up for grabs and then when it gets accepted it moves over to 1.10.2 so you can track for the release notes, etc


Automate creation of models, controllers, and views

Research, implement, and test ways to do the following:

Build scripts for creating models
Build scripts for creating controllers
Build scripts for creating views

Inspiration is based on similar functionality found in Laravel.

Added commands to console for generating models and controllers.


Update wind and gravity first so they are taken into account by aligned

Currently 'aligned' 2d particle effect setting doesnt take wind and gravity into account. This simple change corrects this issue.
See #4461

Actually, this doesnt quite work.


Fix disable swipe gesture

Fixed issue #25 .
Sorry @RichardLindhout I forgot a piece of code from my patch.

thanks :)


NIFI-3017: Exclude org.json dependency from Hive bundle

Backport of #1194

Reviewing...

+1, merged


🔖(lti_toolbox) bump version to 1.0.1

Fixed

Replace url method by re_path for django 4.0 compatibility

@lunika :thinking: weird... but I like it that it works now without diving in :laughing:


Release <IP_ADDRESS> is missing Static binaries

We also want to automate the procedure of creating these binaries.

This seems fixed https://github.com/input-output-hk/cardano-db-sync/releases/tag/<IP_ADDRESS>?

This seems fixed https://github.com/input-output-hk/cardano-db-sync/releases/tag/<IP_ADDRESS>?

I manually added them, but I'm still working on the automation


Some vim9 remote tests will fail if GVIM server exists

Steps to reproduce

start a GVIM server
build vim (features, etc unimportant, I think)
run test:  make test_vim9_builtin.res
view file test.log

You will see that tests that use an empty string for the servername have failed.
For example, the call remote_expr("","") in Test_remote_expr() should fail with error E241- "Unable to send to ", but instead fails with error E449- "Invalid expression received".  You will also see the same result for the remote_foreground("") call in Test_remote_foreground().  Finally, the remote_send("","") call in Test_remote_send() should fail with error E241 but does not fail.
These tests fail because a GVIM server is running while the tests are being executed.
Expected behaviour
These tests will pass if a GVIM server is not running during the test.
Version of Vim
8.2.4330
Environment
Linux (I don't think anything else matters)
Logs and stack traces
These tests fail because Vim internally replaces the empty string servername with "GVIM".  I couldn't find anything in the help pages for remote_expr(), et al that documents this policy.

I suspect you haven't seen this in your test environment because your build procedure creates an executable named "vim" even if it includes GUI support.

Yeah, the tests sometimes don't work when something in the environment interferes.  That is unavoidable.  You can run the build and test process in a separate container if needed.  The CI works that way.
I don't think we can fix this without losing test coverage.

I agree that it is undesirable to reduce test coverage.  However, if the purpose of the tests is to verify failure to send because a server does not exist, why not use some unlikely name for the server as is done in Test_remote_foreground():
assert_fails('remote_foreground("NonExistingServer")', 'E241:')
assert_fails('remote_foreground("")', 'E241:')
The first call makes the purpose of the test clear.  As a side note, isn't the second call redundant or is its purpose to test the substitution of "GVIM for "" under the assumption it does not exist?
If the tests are to be changed, I suggest using something other than an empty string and adding the substitution to Vim documentation.

Hi,
On Sat, Feb 12, 2022 at 7:29 AM Michael Soyka @.***>
wrote:

I agree that it is undesirable to reduce test coverage. However, if the
purpose of the tests is to verify failure to send because a server does not
exist, why not use some unlikely name for the server as is done in
Test_remote_foreground():
assert_fails('remote_foreground("NonExistingServer")', 'E241:')
assert_fails('remote_foreground("")', 'E241:')
The first call makes the purpose of the test clear. As a side note, isn't
the second call redundant or is its purpose to test the substitution of
"GVIM for "" under the assumption it does not exist?

The purpose of the second test is to verify the behavior of
remote_forground() with an empty
string for the server name (as you described). This test was added as part
of checking the
behavior of built-in functions with an empty string as an argument
(8.2.3459).

Yegappan

If the tests are to be changed, I suggest using something other than an

empty string and adding the substitution to Vim documentation.

workaround has been mentioned. Let's close it.


encoding/json: UnmarshalJSON methods of embedded fields are ignored

Go version
go version go1.21.4 linux/amd64
What operating system and processor architecture are you using (go env)?
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/branden/.cache/go-build'
GOENV='/home/branden/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/branden/go/pkg/mod'
GONOPROXY='*.redacted.net'
GONOSUMDB='*.redacted.net'
GOOS='linux'
GOPATH='/home/branden/go'
GOPRIVATE='*.redacted.net'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.4'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2911026133=/tmp/go-build -gno-record-gcc-switches'

What did you do?
https://go.dev/play/p/bNXLi9KmwHA
type (
	Bocchi struct {
		Bocchi string `json:"bocchi"`
	}
	Ryou struct {
		Ryou string `json:"ryou"`
	}
	Kessoku struct {
		Bocchi
		Ryou
	}
)

func (b *Bocchi) UnmarshalJSON(p []byte) error { return errors.New("kita") }
func (r *Ryou) UnmarshalJSON(p []byte) error   { return errors.New("nijika") }

func main() {
	var k Kessoku
	err := json.Unmarshal([]byte(`{"bocchi":"bocchi","ryou":"ryou"}`), &k)
	fmt.Printf("%#v\n", k)
	fmt.Println(err)
}

I.e., define a type embedding two other types that each implement json.Unmarshaler, then unmarshal into the containing type, which does not implement json.Unmarshaler.
What did you expect to see?
Empty fields in k and a non-nil error. The decoder unmarshals each field according to its respective rules.
I would also accept empty fields and a nil error as if the decoder unmarshals each embedded field as if it had its type as its field name, such that {"Bocchi":{"bocchi":"kita"}} would unmarshal to an object equal to Kessoku{Bocchi: Bocchi{"kita"}}. (Unmarshalling that document instead results in an error mentioning "Go struct field Kessoku.bocchi", which doesn't actually exist, but I'm not certain I'd call that a bug.)
What did you see instead?
Filled fields and a nil error. The decoder unmarshals the containing type as if it has exactly the list of promoted fields on the type, without regard to any json.Unmarshaler.
#39175 is related, but there the report was that the behavior between one and two embedded fields was inconsistent (which is due to Go's language rules) rather than that the behavior with two is surprising per se. In my case, the containing type not implementing UnmarshalJSON by promotion is the point, but I want the embedded fields which are unmarshalers to have their logic respected.
The practical goal in my project is to have the equivalents of Bocchi and Ryou unmarshal according to default rules and then each perform validation before returning from their respective UnmarshalJSON. I sometimes need to handle a Bocchi explicitly without a Ryou, hence using separate types. It's straightforward to get the behavior I want by defining an UnmarshalJSON on Kessoku which unmarshals each field explicitly; I'm reporting as an issue because I got what I consider the most surprising behavior when I tried without.
The most flexible solution for my problem is probably #6213, which is addressed by #63397, so there might not be anything to do here.

see
https://go.googlesource.com/go/+/9b4b3e5acca2dabe107fa2c3ed963097d78a4562/src/encoding/json/encode.go#1175
https://go.googlesource.com/go/+/9b4b3e5acca2dabe107fa2c3ed963097d78a4562/src/encoding/json/encode.go#1202

@rsc @dsnet either of you care to take a look?  I also wish @seankhliao's pair of links abovecame with at least a brief translation.

my understanding is that fields of embedded structs get promoted, so they're treated as fields in the parent struct, triggering a direct match based on tag/name, so there's no reason to call UnmarshalJSON

The rules that the "json" package follows are based on the embedding rules of the Go language itself.
Both Bocchi and Ryou are embedded in Kessoku, which means that both the fields and methods are promoted to Kessoku. Since both Bocchi and Ryou have UnmarshalJSON methods, they cancel each other out. Thus, semantically Kessoku has both promoted Bocchi string and Ryou string fields, but not UnmarshalJSON method.
The currently observed behavior is a natural outflow of the above semantic structure. I don't think we should change these rules.

The practical goal in my project is to have the equivalents of Bocchi and Ryou unmarshal according to default rules and then each perform validation before returning from their respective UnmarshalJSON.

I'm not sure what "default rules" means since in my mind the current behavior is a sensible application of the embedding rules in Go.
There are two possible workarounds I can suggest:
type Kessoku struct {
	Bocchi Bocchi
	Ryou Ryou
}

In this example, we avoid embedding, and thus avoid the promotion of fields.
Another example:
type Kessoku struct {
	Bocchi `json:"Bocchi"`
	Ryou `json:"Ryou"`
}

while embedding is used, we explicitly name the embedded fields, which makes it behave as above.

Looking back through the documentation, I think this is closer to #27031 than anything. I skipped the paragraph about how encoding/json handles "anonymous" struct fields and didn't find anything about embedded fields. Since the CLs there have stalled, I can send another one to address that and to clarify that the same rules apply to methods as well as fields for this issue.


Hard pruning

Pruned Group M Thompson got 263.00 points. Pruned Group M Thompson won 51.8% of the 500 games of the tournament. Pruned Group M Thompson won 51.8% of the 500 games it played during the tournament.
Pruned Group M Thompson won 51.8% of the 500 games against Group M Thompson.
Group M Thompson got 237.00 points. Group M Thompson won 46.6% of the 500 games of the tournament. Group M Thompson won 46.6% of the 500 games it played during the tournament.
Group M Thompson won 46.6% of the 500 games against Pruned Group M Thompson.
---- Ranking ----
Pruned Group M Thompson: Win rate 0.53 +/- 0.01	Mean Ordinal 1.47 +/- 0.01
Group M Thompson: Win rate 0.47 +/- 0.01	Mean Ordinal 1.52 +/- 0.01


PyAFQ w/ MrTrix Error

Description
I am preprocessing HCP-like acquisitions using QSIPrep 0.16.0RC3, running both preprocessing and reconstruction in a single command. My recon-spec is custom, but starts by doing DKI and NODDI modeling (no modification), runs tractography from MrTrix MSMT HSVS (no connectivity workflows), and passes that into PyAFQ. I get an error as described below during PyAFQ; all outputs from other steps look okay.
Singularity 3.9.5, CentOs 7.6, 48 GB, 16 CPU
Command
singularity run -B $IMG $BIDS $DERIVATIVES participant --participant_label $SUB -w $WORK --fs-license-file $LICENSE --unringing_method mrdegibbs --denoise-method patch2self --skip-bids-validation --output_resolution 1.25 --$FS_DIR --skip-odf-reports --stop-on-first-crash --notrack --recon-spec /$CODE/pyafq_mrtrix_multishell_msmt_ACT-hsvs_DKI_NODDI.json --mem-mb 47500
Recon Spec
{
  "name": "pyafq_mrtrix_multishell_msmt_ACT-hsvs_DKI_NODDI",
  "space": "T1w",
  "atlases": [],
  "anatomical": [
    "mrtrix_5tt_hsvs"
  ],
  "nodes": [
  {
      "name": "fit_noddi",
      "action": "fit_noddi",
      "software": "AMICO",
      "input": "qsiprep",
      "output_suffix": "NODDI",
      "parameters": {
        "isExvivo": false,
        "dPar": 1.7E-3,
        "dIso": 3.0E-3
      }
    },
   {
      "name": "dki_recon",
      "software": "Dipy",
      "action": "DKI_reconstruction",
      "input": "qsiprep",
      "output_suffix": "DKI",
      "parameters": {
        "write_mif": false,
        "write_fibgz": false
      }
    },
    {
      "name": "msmt_csd",
      "software": "MRTrix3",
      "action": "csd",
      "output_suffix": "msmtcsd",
      "input": "qsiprep",
      "parameters": {
        "mtnormalize": true,
        "response": {
          "algorithm": "dhollander"
        },
        "fod": {
          "algorithm": "msmt_csd",
          "max_sh": [
            8,
            8,
            8
          ]
        }
      }
    },
    {
      "name": "track_ifod2",
      "software": "MRTrix3",
      "action": "tractography",
      "output_suffix": "ifod2",
      "input": "msmt_csd",
      "parameters": {
        "use_5tt": true,
        "method_5tt": "hsvs",
        "use_sift2": true,
        "tckgen": {
          "algorithm": "iFOD2",
          "select": 10000000,
          "max_length": 250,
          "min_length": 30,
          "power": 0.33,
          "crop_at_gmwmi": true,
          "backtrack": true
        },
        "sift2": {}
      }
    },
	{
            "name": "pyAFQ_full",
            "software": "pyAFQ",
            "action": "pyAFQ_full",
            "input": "track_ifod2",
            "output_suffix": "PYAFQ_FULL_ET",
            "parameters": {
                "use_external_tracking": true,
                "directions": "prob",
                "max_angle": 30.0,
                "sphere": "",
                "seed_mask": "",
                "seed_threshold": 0,
                "n_seeds": 1,
                "random_seeds": false,
                "rng_seed": "",
                "stop_mask": "",
                "stop_threshold": 0,
                "step_size": 0.5,
                "min_length": 10,
                "max_length": 1000,
                "odf_model": "CSD",
                "tracker": "local",
                "nb_points": false,
                "nb_streamlines": false,
                "seg_algo": "AFQ",
                "reg_algo": "",
                "clip_edges": false,
                "parallel_segmentation": "{'n_jobs': -1, 'engine': 'joblib', 'backend': 'loky'}",
                "progressive": true,
                "greater_than": 50,
                "rm_small_clusters": 50,
                "model_clust_thr": 1.25,
                "reduction_thr": 25,
                "refine": false,
                "pruning_thr": 12,
                "b0_threshold": 50,
                "prob_threshold": 0,
                "roi_dist_tie_break": false,
                "dist_to_waypoint": "",
                "rng": "",
                "return_idx": false,
                "presegment_bundle_dict": "",
                "presegment_kwargs": "{}",
                "filter_by_endpoints": true,
                "dist_to_atlas": 4,
                "save_intermediates": "",
                "n_points": 100,
                "clean_rounds": 5,
                "distance_threshold": 5,
                "length_threshold": 4,
                "min_sl": 20,
                "stat": "mean",
                "min_bval": "",
                "max_bval": "",
                "filter_b": true,
                "robust_tensor_fitting": false,
                "csd_response": "",
                "csd_sh_order": "",
                "csd_lambda_": 1,
                "csd_tau": 0.1,
                "gtol": 0.01,
                "brain_mask_definition": "",
                "bundle_info": "",
                "reg_template_spec": "mni_T1",
                "mapping_definition": "",
                "reg_subject_spec": "power_map",
                "profile_weights": "gauss",
                "scalars": "['dti_fa', 'dti_md']",
                "import_tract": "",
                "sbv_lims_bundles": "[None, None]",
                "volume_opacity_bundles": 0.3,
                "n_points_bundles": 40,
                "sbv_lims_indiv": "[None, None]",
                "volume_opacity_indiv": 0.3,
                "n_points_indiv": 40,
                "viz_backend_spec": "plotly_no_gif",
                "virtual_frame_buffer": false
            }
        }
  ]
}

Relevant Log Output
	 [Node] Executing "run_afq" <qsiprep.interfaces.pyafq.PyAFQRecon>
INFO:nipype.workflow:[Node] Executing "run_afq" <qsiprep.interfaces.pyafq.PyAFQRecon>
220616-16:14:25,177 nipype.workflow INFO:
	 [Node] Finished "tck_sift2", elapsed time 1109.829533s.

  0%|          | 0/779288.0 [00:00<?, ?it/s]
  0%|          | 1/779288.0 [00:00<34:36:54,  6.25it/s]
....... (REMOVED FOR SPACE)
100%|█████████▉| 779093/779288.0 [03:16<00:00, 3616.20it/s]
100%|██████████| 779288/779288.0 [03:16<00:00, 3967.21it/s]ERROR:concurrent.futures:exception calling callback for <Future at 0x2b54cabafd90 state=finished raised BrokenProcessPool>
Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.8/concurrent/futures/_base.py", line 328, in _invoke_callbacks
    callback(self)
  File "/usr/local/miniconda/lib/python3.8/site-packages/nipype/pipeline/plugins/multiproc.py", line 159, in _async_callback
    result = args.result()
  File "/usr/local/miniconda/lib/python3.8/concurrent/futures/_base.py", line 437, in result
    return self.__get_result()
  File "/usr/local/miniconda/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
/usr/local/miniconda/lib/python3.8/site-packages/joblib/externals/loky/backend/resource_tracker.py:318: UserWarning: resource_tracker: There appear to be 6 leaked semlock objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '
/usr/local/miniconda/lib/python3.8/site-packages/joblib/externals/loky/backend/resource_tracker.py:318: UserWarning: resource_tracker: There appear to be 2 leaked folder objects to clean up at shutdown
  warnings.warn('resource_tracker: There appear to be %d '

More information
PyAFQ wf has output CSD and DTI models, and then the job appears to hang. It did not automatically error out. Job did not hit walltime. As of right now, all subjects that have made it this far run into the same error.

I just realized that the streamline count for PyAFQ in the input_trk spec is usually 1million, not 10million (like the default MrTrix tracking)! I will restart the jobs but reduce the streamline count from HSVS tracking, will close if it works.

It finished without errors on a smaller connectome. Closing.


Update for 1.15

Don't merge.

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)


Add a tracing span for run criteria.

Objective
Adds a tracing span for run critieria.
This change will be invalidated by stageless, but it was a simple change.
Fixes #4681.
Changelog
Shows how long a run criteria takes to run when tracing is enabled.

bors r+


Carousel support for event emittion

Using the carousel for more complex elements than just images, i need events for Slide and SlideAnimationEnd.
As a far as I understood, the current (0.14.3) version does not support them.
So I modified the goNext function to get them on my own.
    $scope.$emit('uibCarousel:onSlide');
    angular.extend(slide, {direction: direction, active: true});
    angular.extend(self.currentSlide || {}, {direction: direction, active: false});
    if ($animate.enabled() && !$scope.noTransition && !$scope.$currentTransition &&
      slide.$element && self.slides.length > 1) {
      slide.$element.data(SLIDE_DIRECTION, slide.direction);
      if (self.currentSlide && self.currentSlide.$element) {
        self.currentSlide.$element.data(SLIDE_DIRECTION, slide.direction);
      }

      $scope.$currentTransition = true;
      if (NEW_ANIMATE) {
        $animate.on('addClass', slide.$element, function(element, phase) {
          if (phase === 'close') {
            $scope.$currentTransition = null;
            $animate.off('addClass', element);
            $scope.$emit('uibCarousel:onSlideAnimationEnd');
          }
        });
      } else {
        slide.$element.one('$animate:close', function closeFn() {
            $scope.$currentTransition = null;
            $scope.$emit('uibCarousel:onSlideAnimationEnd');
        });
      }
    }

Would like to know, if this implementation is right.
Are there any plans to add more event emitters to the libraries components?

This is better implemented via a custom directive with negative priority using $animate.on('addClass', ...) there.
This is not a feature we want, since it is easily pluggable on the user's side & it has performance implications to all consumers.

Thank you for the feedback.
I need these events in a parent directive, which creates the markup for the carousel.
I would appreciate, if you could point to me a good example for your proposal.
Thanks in advance!

Something like this


Fix bug in HandEvaluator

When we have four of a kind and flush hand types as possible combinations, the best hand type chosen should be four of a kind, but instead flush was returned. Fixed that and also added a unit test case in four of a kind for this particular case.

Thanks!

in fact this situation is never possible - no equal cards available, as well as more than 7 cards in total,
except if provided by test fixture, of course, or buggy dealing

You are right, I will add more test cases with realistic scenarios. Still it is a bug, beacause you could have had full house and flush possible hand types, and the best hand type chosen would have been flush which is wrong.

flush takes at least 5 cards - not equal by type of course + at most 2 more cards - no possible FullHouse or 4ofAKind if flush appears - see #8

Yes, you are right. Even for full house it is not possible. I got confused because in the tests there are 8 cards in total. Thanks for clarifying.

Created a pull request to revert these changes, thanks @kiko81 ! Previous version from you was indeed better in the context of hold-em rules.


Fix deployment and ensure uptime

This PR fixes several things with the deployment:

Hopefully fixes the girder build issues by using virtual envs (haven't run into the problem testing it myself, but it's sometimes hard to induce)
Changes the behavior of the deploy script to keep the service up while building, so that downtime is restricted to just the time it takes to restart the docker-compose service (and if there are no changes, there is no downtime)
Pulls down the latest viame docker image (if there is one) before each build
Add project_directory variable for easier development

Can you manually log into the server where builds were failing, docker pull girder/girder && docker pull kitware/viame:gpu-all-models-latest and try re-running the build?

Yeah I can try that, I should be able to do it without disrupting up-time.

Steps to reproduce would be ideal, but evidence that this is still happening at all I think is necessary before we try to fix it.

I'd usually agree, but at one point in a previous change, I had thought I solved the problem, because I added a fix and the errors stopped occurring for a little while, only to start happening again. All of that to say, for this particular bug, I'm not sure that being free of the bug for a short period of time is enough evidence to say it's not bound to happen again, just because that's what's happened in the past.
I understand that by that philosophy, we're actually still in the same position with this change, but I'd rather the change possibly fix it than not attempt to fix it at all. If the error starts cropping up again, then we'll know that this didn't definitively fix it. Also, due to the other changes included in this PR, if the builds start failing again, the server should handle it gracefully.

I thought about this a bit over the weekend, and I'm currently pretty convinced that the virtual env fix is just a band-aid, which is fine, but nothing is stopping us from fixing it permanently.

The whole point of docker is to build in a consistent environment.  non-deterministic build failures should be impossible.
If, like you're saying, the issue is caused by a conflict between the system python installation and a package in girder (or in our package) then the appropriate fix would seem to be:

Generate a lockfile with pip freeze so builds are always based on the exact same package versions.  We should have been doing this already anyway.
Change the version of python installed on the system.  We rely on the girder base image, so that would need to be fixed in girder.  I think this has already been done because lastest image builds are passing for me.  This is what your virtual env was doing.

Finally, I think this fix may be a placebo, but I'm not sure.  You created a virtual env inside docker, but as far as I can tell you never used it.  when you run pip install further down after making the venv, that's still the system version of pip and python, not the venv version.  You can verify this with which python before and after your changes.

@BryonLewis can provide the image tag for a version of girder where build is failing.
If I understand docker/python correctly, once we add a lockfile and get a successful build, that should be an absolute guarantee that we fixed this problem.

ENV PATH="$VIRTUAL_ENV/bin:$PATH"
I think I'm wrong about the placebo.  By prepending to path, you encounter the virtual versions of pip/python before the system versions. Is that right?

ENV PATH="$VIRTUAL_ENV/bin:$PATH"
I think I'm wrong about the placebo. By prepending to path, you encounter the virtual versions of pip/python before the system versions. Is that right?

Yes that's correct

I thought about this a bit over the weekend, and I'm currently pretty convinced that the virtual env fix is just a band-aid, which is fine, but nothing is stopping us from fixing it permanently.

The whole point of docker is to build in a consistent environment.  non-deterministic build failures should be impossible.

If, like you're saying, the issue is caused by a conflict between the system python installation and a package in girder (or in our package) then the appropriate fix would seem to be:

Generate a lockfile with pip freeze so builds are always based on the exact same package versions.  We should have been doing this already anyway.

I agree

Change the version of python installed on the system.  We rely on the girder base image, so that would need to be fixed in girder.  I think this has already been done because lastest image builds are passing for me.  This is what your virtual env was doing.

I don't understand what you mean by changing the version? Do you mean just using a virtual env?


windows 24H2

on windows 24H2 computer name assignement is asked even if specified as assigned automatically DEKSTOP-??????

on windows 24H2 ask for ad join computer or account online

same file xml works fine on 23H2
thanks

autounattend_xml.txt

Message:
"
i attach the file autounattend.xml that works correclty with win11(23H2), no problem perfect
the same file autounattend.xml doesnt work with win11(24h2)
for the iso i've used the one downloaded from Microsoft license portal site with official version licensed, relased official 24H2 on 02 oct 2024

the fist image 01.jpg ask for computername: "Assegna un nome al dispositivo" -> "Assign a name to your device"
the second image 02.jpg ask for login with microsoft account or other option to use local account or next active directory join
the third image 03.jpg "Configurazione per uso personale" -> "Configure for personal use" /// "Configura per l'uso aziendale o dell'istituto di istruzione" -> "Configure for organizational usage"
thanks for your support.
regards, livio.
"

I used your autounattend.xml file with the official Win11_24H2_Italian_x64.iso image downloaded from Microsoft, and the installation ran without interruption from start to finish. When you see any dialogs during the installation process, I assume this must be due to the .iso image you used.

thanks, for your support i will try and i give you a feedback

Hi,

I used your autounattend.xml file with the official Win11_24H2_Italian_x64.iso image downloaded from Microsoft, and the installation ran without interruption from start to finish. When you see any dialogs during the installation process, I assume this must be due to the .iso image you used.

Hi,
you are rigth, there was a mistake on building a usb key with rufus, now i've rebuild the usb key with rufus and no other option checked and it's works.
sorry for my error!
regards, livio


iOS Doesn't Compile for 0.4.0

Hi, thank you for all of your work on this! It seems that the iOS code is missing a comma, not letting it compile. I will edit this shortly with the error message.

There is just a comma that needs to be removed

Thank you, fixed

Great thanks!


Newton Propagator is still buggy

Looks like the Newton propagator still has some subtle bug.
See https://github.com/QuantumControl-jl/QuantumPropagators.jl/runs/3295191405?check_suite_focus=true
The propagator works for small dimensions (N=10), but not for N=1000. Interestingly, the reference implementation at https://github.com/qucontrol/newtonprop works perfectly for this test case! Thus, it shouldn't be too hard to figure out what is different between the Julia and the Python implementation.
@alastair-marshall Just raising this issue in case you had planned to use the Newton propagator for GRAPE.jl (which I would definitely recommend, once it actually works)

@alastair-marshall Just raising this issue in case you had planned to use the Newton propagator for GRAPE.jl (which I would definitely recommend, once it actually works)

Thanks for bringing it up, I'll use expv from ExponentialUtilities for now just so that I can slowly build up my code

That sounds good! It would actually actually like to have an exp-propagator available in QuantumPropagators.jl as well, with the same interface as the other propagators, so e.g. expv!(Psi, H, dt, wrk) where wrk might be necessary to hold a temporary state to enable in-place propagation and/or expv(Psi, H, dt, wrk=nothing) for something not in-place that works with AD.  Should be a fairly simple wrapper. For small Hamiltonians (dimension < 10), exponentiation is actually faster and safer than polynomial expansion. So if you like, feel free to add it.

Oh, I see...  If you can get expv into the same interface as newton!, that would be an extremely interesting thing to benchmark! I just wonder how my handwritten Arnoldi-based Newton propagator compares to other Arnoldi/Krylov Julia packages that evaluate exp(A) Ψ. I'd be very open to wrapping any of those packages in QuantumPropagators.jl


[ioc] add typed ioc based on generics

Codecov Report

Merging #17 (9188c90) into master (b50e8a1) will decrease coverage by 0.44%.
The diff coverage is 58.62%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   71.35%   70.91%   -0.45%
==========================================
  Files          20       21       +1
  Lines         803      832      +29
==========================================
+ Hits          573      590      +17
- Misses        225      235      +10
- Partials        5        7       +2

Impacted Files
Coverage Δ

ioc/ioc.go
58.62% <58.62%> (ø)

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 b50e8a1...9188c90. Read the comment docs.


Is there a way I  can compile this project into a .exe or a .dll and call it from c# code.

I am a c# developer and I am looking for an option to use it. Last month I work on FFmpeg binary. call the exe with the parameter and it does the work and returns the result (reading console output).
I am looking for using project similar to like that. Calling the exe with parameter and get the output. @tducret  please check if there is a better way to use it.
I have used python but don't like to translate the code to C#. Anything else to use it in c#.
Thanks

Hi @anirudhagupta ,
Have you tried to call python.exe to execute this script?
Have a look at this > https://stackoverflow.com/questions/11779143/how-do-i-run-a-python-script-from-c?answertab=votes#tab-top
What do you think?


trying to set a read only property doesn't cause a compiler error

If one try to set a property that hasn't any getter defined, the compiler doesn't emit any error or warning and the code silently fails à runtime.
example:
class Greeter {
    private _greeting: string;
    get greeting(): string { return this._greeting; }

    constructor(message: string) {
        this.greeting = message; //no error at compile time and silent failure at execution time
    }
    greet() {
        return "Hello, " + this.greeting;
    }
}

Essentially a dupe of #295 (and other issues) but related to/would be fixable by #12 being resolved.

Please search for duplicates before logging issues.


Add bottom bar to the History

@jaindiv26 is already working on a bottom bar for home. Can you wait so that the implementation can be coherent ?

@teolemon Can i work on this?

👌 if you can mutualize the code with what you've already done, as suggested by @deniger

Alright

It seems there is no way to mutualize the XML code for that... Let's try at least to mutualize the java part...

Sorry, but will not be working on this.

Est-ce que l'ordre a un impact ?

@deniger Ideally the order should be same throughout the app. If this is the order which is being followed everywhere then this is good to go.

See the allergen view (with 5 items, should we stick to 4 ?)

We can have 5 items.  I removed the history item as we are in the history view.
---- On Wed, 15 May 2019 23:47:58 +0200<EMAIL_ADDRESS>wrote ----
See the allergen view (with 5 items, should we stick to 4 ?)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

We should keep the current item, otherwise the order becomes unpredictable

Should I add it to the home page too ?

Yup
Le jeu. 16 mai 2019 à 11:30, deniger<EMAIL_ADDRESS>a écrit :

[image: image]
https://user-images.githubusercontent.com/47569605/57843095-f988bd80-77cd-11e9-841f-c068b4583b56.png
[image: image]
https://user-images.githubusercontent.com/47569605/57843131-05747f80-77ce-11e9-8547-1f6d30129455.png
Should I add it to the home page too ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/2396?email_source=notifications&email_token=AAM4RV7NSRNZIATMARPGGYDPVUSUVA5CNFSM4G453JY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVRHU4Y#issuecomment-492993139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM4RV7BYT4UV3C2XPVSK53PVUSUVANCNFSM4G453JYQ
.

In scan it will hide when the bottom card will be displayed. Also the current should be highlited somehow to show that it is selected. Maybe by changing the front or icon color.

I thought we could display the bottom card above it ?

Yes, I modified the layout for that. Let's test
---- On Thu, 16 May 2019 21:26:48 +0200<EMAIL_ADDRESS>wrote ----
I thought we could display the bottom card above it ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

fixed by @deniger


docker files into docker folder

docker could get an extra folder e.g. ./Dockerfiles or /install /docker

Still need to do this.

done


cmd/compile: Fix riscv ginsnop() to generate ADDI $0, ZERO

ginsnop() used to generate ADD ZERO, ZERO. The actual NOP defined
is an ADDI instruction. This commit fixes the NOP generation, and
generates a ADDI $0, ZERO, ZERO

I guess I have to go through: https://review.gerrithub.io/#/q/project:riscv/riscv-go after reading the comments on the previous pull request.


[type:feat] add gobatis support

With pull requests:

Open your pull request against main
Your pull request should have no more than two commits, if not you should squash them.
You should pass all tests by go test -v ./... at the project root path in local.
It should pass all tests in the available continuous integration systems such as GitHub Actions.
You should add/modify tests to cover your proposed code changes.
If your pull request contains a new feature, please document it on the README.

Codecov Report

Merging #70 (036e74f) into main (a14ff9b) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #70      +/-   ##
==========================================
- Coverage   68.62%   68.47%   -0.16%
==========================================
  Files           8        8
  Lines         204      203       -1
==========================================
- Hits          140      139       -1
  Misses         48       48
  Partials       16       16

Impacted Files
Coverage Δ

internal/pkg/config/conn_metadata.go
86.95% <100.00%> (-0.55%)
:arrow_down:

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 a14ff9b...036e74f. Read the comment docs.


Is this dead?

I am wondering if plan to stop supporting graphcool in favour of prisma.
The last relase is from last december..

I have the same feeling. Graphcool is a killer for simple and internal projects.
Using Prisma I will need another server.

I feel like most of their team is focusing on Prisma... Prisma is okay, but its web admin interface is limited. Plus the whole needing a server. Docker makes that a little easier though.


Script and api for run projects

Make a generic script to run project and store project's output in DB.
Then make an API to register a project, add it to scheduler (night running) and run it using the above script.

Done usign rq_scheduler


Lowering the severity of the sec group policy

Description
Severity was set too high for the value it provides to the user and the attention we want from the user.
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

Danger has errored
[!] Invalid Dangerfile file: Please add a changelog
 #  from Dangerfile:10
 #  -------------------------------------------
 #  if (has_app_changes.length != 0) && no_changelog_entry
 >    raise "Please add a changelog"
 #  end
 #  -------------------------------------------

  Generated by :no_entry_sign: Danger


Python debugger support for Python 3 (in addition to Python 2)

Added safe_ord compatibility to pass through int arguments
Fixed JerryDebugger to decode bytes as utf8 strings when necessary
Fixed WebSocket send_message method to use packed_data[0:1] bytes slice

JerryScript-DCO-1.0-Signed-off-by: Zac Medico<EMAIL_ADDRESS>

Have you tried running the debugger tests?  ./tools/run-tests.py --jerry-debugger for me this returned various errors which should be also fixed for Python 3.
(I've did a quick hackish changes to resolve some of them: https://gist.github.com/galpeter/a6ac851b6ab113aaad62d60001c5df23 )

I've included your changes, and the debugger tests do pass with them. Thank you! I will look into making you suggested safe_ord change now.

Have you tried running the debugger tests?  ./tools/run-tests.py --jerry-debugger for me this returned various errors which should be also fixed for Python 3.
(I've did a quick hackish changes to resolve some of them: https://gist.github.com/galpeter/a6ac851b6ab113aaad62d60001c5df23 )

I've included your changes, and the debugger tests do pass with them. Thank you! I will look into making you suggested safe_ord change now.

this can be closed, python3 is already supported?

this can be closed, python3 is already supported?

Thank you! Closing now.


Feature request: Flag indicate end of stream

Hi, during request streaming it'll be helpful to have a flag to indicate end of generation. Can you help with this feature request?
I believe that means returning the bool flag from https://github.com/triton-inference-server/tensorrtllm_backend/blob/release/0.5.0/inflight_batcher_llm/src/libtensorrtllm.cc#L892
Ref: https://github.com/NVIDIA/TensorRT-LLM/issues/240

Thanks for making this issue, @yunfeng-scale ! We'll get back to you once we have a chance to look into this. & we're always happy support community MRs too!

Also need this feature!


Ordering in hasManyThrough relation doesn't work

I have ProjectEntity with such relation in it
'users' => $mapper->hasManyThrough($entity, 'Api\V2\Entities\UserEntity', 'Api\V2\Entities\UserProjectEntity', 'user_id', 'project_id')->active()->order(['displayname' => 'ASC'])
->order() does not affect on the result, its sorted by id of UserProjectEntity (it has simple structure id - user_id -project_id)

Yeah, I don't think that will work out of the box. It's possibly a bug.

I am curious about this now. What table is the column displayname on? Is it on either of those join tables?

Hi! Any updates on this issue?

You can fix this by editing the eagerLoadOnCollection method in vendor/vlucas/spot2/lib/Relation/HasManyThrough.php and changing this:
foreach ($collectionRelations as $relatedEntity) {
$relatedEntityPk = $relatedEntity->$relationRelatedForeignKey;
if ($relatedEntityPk == $throughForeignKey) {
    $entityRelations[$throughLocalKey][] = $relatedEntity;
}

}
to this:
foreach ($collectionRelations as $idx=>$relatedEntity) {
$relatedEntityPk = $relatedEntity->$relationRelatedForeignKey;
if ($relatedEntityPk == $throughForeignKey) {
    $entityRelations[$throughLocalKey][$idx] = $relatedEntity;
}

}
ksort($entityRelations[$throughLocalKey]);


firstPostId() is not always present on the discussion model

In some instances, the firstPostId() method is not present on the Discussion model, meaning that loading the page results in an error as the extension cannot load the article. This error breaks the forum's frontend.

I have two forms got this too, really confused.

form A info

Flarum core 1.1.1
PHP version: 8.0.11
MySQL version: 8.0.24
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, ctype, curl, dom, filter, ftp, gd, gettext, hash, iconv, intl, json, mbstring, SPL, session, pcntl, standard, PDO, mysqlnd, pdo_sqlite, Phar, posix, Reflection, pdo_mysql, shmop, SimpleXML, soap, sockets, sodium, mysqli, sysvsem, tokenizer, xml, xmlreader, xmlwriter, zip, fileinfo, exif
+--------------------------------------+-------------+--------+
| Flarum Extensions                    |             |        |
+--------------------------------------+-------------+--------+
| ID                                   | Version     | Commit |
+--------------------------------------+-------------+--------+
| flarum-flags                         | v1.1.0      |        |
| flarum-suspend                       | v1.1.0      |        |
| flarum-bbcode                        | v1.1.0      |        |
| flarum-tags                          | v1.1.0      |        |
| flarum-lock                          | v1.1.0      |        |
| fof-spamblock                        | 1.0.1       |        |
| flarum-subscriptions                 | v1.1.0      |        |
| flarum-likes                         | v1.1.0      |        |
| afrux-forum-widgets-core             | v0.1.6      |        |
| wolfgang-demeter-bbcode-5star-rating | v0.1.1      |        |
| v17development-seo                   | v1.8.0      |        |
| v17development-blog                  | 0.4.2       |        |
| ralkage-hcaptcha                     | 1.0.0       |        |
| pipecraft-id-slug                    | v1.1.0      |        |
| nearata-internal-links-noreload      | v2.0.1      |        |
| nearata-embed-video                  | v3.0.0      |        |
| mickmelon-coloured-usernames         | 0.1.1       |        |
| michaelbelgium-discussion-views      | v7.1.0      |        |
| justoverclock-skypemoji              | dev-main    |        |
| justoverclock-purify                 | 0.1.7       |        |
| itnt-uitab                           | v0.4.0      |        |
| ianm-level-ranks                     | 1.0.0       |        |
| ianm-html-head                       | 1.0.0       |        |
| glowingblue-password-strength        | 3.0.0       |        |
| fof-user-directory                   | 1.0.2       |        |
| fof-user-bio                         | 1.0.0       |        |
| fof-upload                           | 1.0.5       |        |
| fof-subscribed                       | 1.0.0       |        |
| fof-stopforumspam                    | 1.1.1       |        |
| fof-split                            | 1.0.0       |        |
| fof-socialprofile                    | 1.1.0       |        |
| fof-sitemap                          | 1.0.2       |        |
| fof-reactions                        | 1.0.2       |        |
| fof-profile-image-crop               | 1.0.0       |        |
| fof-prevent-necrobumping             | 1.0.1       |        |
| fof-pretty-mail                      | 1.0.1       |        |
| fof-polls                            | 1.0.3       |        |
| fof-nightmode                        | 1.0.0       |        |
| fof-merge-discussions                | 1.0.0       |        |
| fof-links                            | 1.0.3       |        |
| fof-linguist                         | 1.0.3       |        |
| fof-ignore-users                     | 1.0.0       |        |
| fof-html-errors                      | 1.0.0       |        |
| fof-geoip                            | 1.0.1       |        |
| fof-formatting                       | 1.0.1       |        |
| fof-follow-tags                      | 1.0.2       |        |
| fof-drafts                           | 1.0.3       |        |
| fof-disposable-emails                | 1.0.0       |        |
| fof-default-user-preferences         | 1.0.0       |        |
| fof-bbcode-tabs                      | 1.0.0       |        |
| fof-bbcode-details                   | 1.0.0       |        |
| fof-analytics                        | 1.0.0       |        |
| flarum-sticky                        | v1.1.0      |        |
| flarum-statistics                    | v1.1.0      |        |
| flarum-pusher                        | v1.1.0      |        |
| flarum-nicknames                     | v1.1.0      |        |
| flarum-mentions                      | v1.1.1      |        |
| flarum-markdown                      | v1.1.0      |        |
| flarum-lang-english                  | v1.1.0      |        |
| flarum-lang-chinese-simplified       | v<IP_ADDRESS>9 |        |
| flarum-emoji                         | v1.1.0      |        |
| flarum-approval                      | v1.1.0      |        |
| ffans-clipboardjs                    | v1.0.0      |        |
| dem13n-topic-starter-label           | 0.1.7       |        |
| davwheat-share                       | v1.0.1      |        |
| darkle-fancybox                      | 0.2         |        |
| clarkwinkelmann-username-blacklist   | 1.0.0       |        |
| clarkwinkelmann-circle-groups        | 1.0.0       |        |
| clarkwinkelmann-author-change        | 1.0.2       |        |
| blomstra-horizon                     | 0.2-beta.2  |        |
| askvortsov-pwa                       | v3.0.4      |        |
| askvortsov-markdown-tables           | v1.2.1      |        |
| antoinefr-money                      | v1.1.0      |        |
| afrux-top-posters-widget             | v0.1.3      |        |
| afrux-forum-stats-widget             | dev-main    |        |
+--------------------------------------+-------------+--------+
Base URL: ttt.***.com
Installation path: /www/wwwroot/ttt.***.com
Queue driver: redis
Mail driver: smtp
Debug mode: off

form B info

Flarum core 1.1.1
PHP version: 8.0.11
MySQL version: 8.0.24
Loaded extensions: Core, date, libxml, openssl, pcre, sqlite3, zlib, bcmath, ctype, curl, dom, filter, ftp, gd, gettext, hash, iconv, intl, json, mbstring, SPL, session, pcntl, standard, PDO, mysqlnd, pdo_sqlite, Phar, posix, Reflection, pdo_mysql, shmop, SimpleXML, soap, sockets, sodium, mysqli, sysvsem, tokenizer, xml, xmlreader, xmlwriter, zip, fileinfo, exif
+-----------------------------------+-------------+--------+
| Flarum Extensions                 |             |        |
+-----------------------------------+-------------+--------+
| ID                                | Version     | Commit |
+-----------------------------------+-------------+--------+
| flarum-flags                      | v1.1.0      |        |
| flarum-suspend                    | v1.1.0      |        |
| askvortsov-auto-moderator         | v0.1.2      |        |
| afrux-forum-widgets-core          | v0.1.6      |        |
| fof-spamblock                     | 1.0.1       |        |
| flarum-tags                       | v1.1.0      |        |
| flarum-approval                   | v1.1.0      |        |
| yannisme-cntheme                  | 1.0.4       |        |
| v17development-user-badges        | v0.2.1      |        |
| v17development-seo                | v1.8.0      |        |
| the-turk-diff                     | 1.1.1       |        |
| sycho-github-milestone            | v0.1.2      |        |
| pipecraft-id-slug                 | v1.1.0      |        |
| nearata-internal-links-noreload   | v2.0.1      |        |
| michaelbelgium-discussion-views   | v7.1.0      |        |
| justoverclock-hot-discussions     | 0.1.2       |        |
| justoverclock-custom-html-widget  | 0.1.4       |        |
| itnt-uitab                        | v0.4.0      |        |
| fof-user-directory                | 1.0.2       |        |
| fof-user-bio                      | 1.0.0       |        |
| fof-upload                        | 1.0.5       |        |
| fof-terms                         | 1.1.1       |        |
| fof-subscribed                    | 1.0.0       |        |
| fof-stopforumspam                 | 1.1.1       |        |
| fof-split                         | 1.0.0       |        |
| fof-socialprofile                 | 1.1.0       |        |
| fof-sitemap                       | 1.0.2       |        |
| fof-profile-image-crop            | 1.0.0       |        |
| fof-prevent-necrobumping          | 1.0.1       |        |
| fof-pretty-mail                   | 1.0.1       |        |
| fof-polls                         | 1.0.3       |        |
| fof-nightmode                     | 1.0.0       |        |
| fof-merge-discussions             | 1.0.0       |        |
| fof-links                         | 1.0.3       |        |
| fof-linguist                      | 1.0.3       |        |
| fof-github-autolink               | 1.0.0       |        |
| fof-geoip                         | 1.0.1       |        |
| fof-frontpage                     | 1.0.1       |        |
| fof-formatting                    | 1.0.1       |        |
| fof-drafts                        | 1.0.3       |        |
| fof-disposable-emails             | 1.0.0       |        |
| fof-default-user-preferences      | 1.0.0       |        |
| fof-cookie-consent                | 1.0.1       |        |
| fof-byobu                         | 1.0.1       |        |
| fof-best-answer                   | 1.1.5       |        |
| fof-ban-ips                       | 1.0.0       |        |
| fof-analytics                     | 1.0.0       |        |
| flarumite-simple-spoilers         | 1.0.0       |        |
| flarum-subscriptions              | v1.1.0      |        |
| flarum-sticky                     | v1.1.0      |        |
| flarum-statistics                 | v1.1.0      |        |
| flarum-pusher                     | v1.1.0      |        |
| flarum-nicknames                  | v1.1.0      |        |
| flarum-mentions                   | v1.1.1      |        |
| flarum-markdown                   | v1.1.0      |        |
| flarum-lock                       | v1.1.0      |        |
| flarum-likes                      | v1.1.0      |        |
| flarum-lang-english               | v1.1.0      |        |
| flarum-lang-chinese-simplified    | v<IP_ADDRESS>9 |        |
| flarum-emoji                      | v1.1.0      |        |
| flarum-bbcode                     | v1.1.0      |        |
| ffans-clipboardjs                 | v1.0.0      |        |
| darkle-fancybox                   | 0.2         |        |
| clarkwinkelmann-group-list        | 1.0.0       |        |
| clarkwinkelmann-emojionearea      | 1.0.0       |        |
| clarkwinkelmann-create-user-modal | 1.3.0       |        |
| clarkwinkelmann-circle-groups     | 1.0.0       |        |
| clarkwinkelmann-author-change     | 1.0.2       |        |
| blomstra-horizon                  | 0.2-beta.2  |        |
| askvortsov-markdown-tables        | v1.2.1      |        |
| askvortsov-discussion-templates   | v0.8.3      |        |
| afrux-top-posters-widget          | v0.1.3      |        |
| afrux-online-users-widget         | v0.1.5      |        |
| afrux-news-widget                 | v0.1.0      |        |
| afrux-forum-stats-widget          | dev-main    |        |
+-----------------------------------+-------------+--------+
Base URL: discuss.***.com
Installation path: /www/wwwroot/discuss.***.com
Queue driver: redis
Mail driver: smtp
Debug mode: off


Key Error when training with KITTI-0002

Hey, firstly thank you for making this great project public. I had some queries regarding training the model with KITTI-0002 dataset.
I'm getting a key error when I train it with KITTI-0002. I used both the latent codes : latent_codes_car_van_truck.pt and KITTI-MOT/car-object-latents/latent_codes02.pt but in vain. The error persists. This is also followed by a wandb 0.000mb of 0.013 mb completed error.
File "/usr/local/lib/python3.8/dist-packages/nerfstudio/engine/trainer.py", line 479, in train_iteration
_, loss_dict, metrics_dict = self.pipeline.get_train_loss_dict(step=step)
File "/usr/local/lib/python3.8/dist-packages/nerfstudio/utils/profiler.py", line 127, in inner
out = func(*args, **kwargs)
File "/app/mars/mars/mars_pipeline.py", line 135, in get_train_loss_dict
model_outputs = self.model(ray_bundle)
File "/usr/local/lib/python3.8/dist-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.8/dist-packages/nerfstudio/models/base_model.py", line 142, in forward
return self.get_outputs(ray_bundle)
File "/app/mars/mars/models/scene_graph.py", line 445, in get_outputs
result = model.inference_without_render(ray_obj)
File "/app/mars/mars/models/car_nerf.py", line 206, in inference_without_render
self.car_latents[int(obj_id)].view(1, -1).to(obj_id.device),
KeyError: 0
wandb: \ 0.000 MB of 0.wandb: | 0.000 MB of 0.013 MB uploaded
I have made the changes in the cicai_config.py file and launch.json and set the depth to False for 0002. Can you suggest a fix for this? Works fine when training KITTI-0006 but fails for KITTI-0002

Hi! @ng169 @amoghskanda
Thanks for your reply! This seems to be a known issue #16. If possible, we will train and upload a new latent code.

yeah sure, thank you!

The problem seems still exist in the KITTI-0002 0001, is latent code the updated version ?


Add pre-push hook to reliably catch presubmit issues

If I'm understanding it right, the current git hooks work like this:

in prepare-commit-msg, add special markers to the commit message if problems are detected.
in commit-msg, fail commits if the markers are found.

The problem here is that prepare-commit-msg only runs when preparing the default commit message, not when an existing commit is modified. Various dev changes such as rebasing or amending commits can produce code that would fail tests, but this doesn't get detected since tests don't get re-run in this case.
I think we should be able to run essentially the same tests in a pre-push hook. One complication is that it's hard to find the set of changed files for the push without knowing the base commit. Currently it's still pretty fast to just lint all Python files, for example:
$ flake8 $(git ls-files '*.py')

(This takes 0.4s on my machine for the current source.)
If checking everything gets too slow, we could reduce the set of checked files by using a diff list versus @{upstream} or origin/dev.
Out of curiosity, why does the current test setup use "1"/"0" string output for results? Seems easier to just base the logic on plain exit codes, but I may be missing something.

Out of curiosity, why does the current test setup use "1"/"0" string output for results? Seems easier to just base the logic on plain exit codes, but I may be missing something.

We borrowed them from the good folks at GoogleCloudPlatform/kubernetes :)

Closed by #376, #363.

FYI, the current pre-push hook is opt-in since there's no entirely reliable way to determine the correct base branch for use in comparisons. See https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/blob/master/hooks/README.md for instructions how to activate it.


serialize_to_file fail but return JSONSuccess

json_serialize_to_file
json_serialize_to_file_pretty

in read-only filesystem those function return JSONSuccess

Thanks, fixed in https://github.com/kgabis/parson/commit/19c11750643cff6279cabac8939823dbf8aca24c


fix dtd parsing

Hi, everyone!
Fighting with a big DTD file I found a bug parsing null references. I wish you can integrate this PR.
The DTD afected is:
https://publication-bdds.apps.epo.org/bdds/bdds-bff-service/prod/api/public/products/19/delivery/472/item/1284/download
Regards,
Antonio.

Another option is transform Block elements attribute from LinkedHashSet to LinkedList to allow duplicated elements, and always generate a default class when element is #PCDATA, at Element clasClass() method. In this way, avoids NPE and JAXB runs correctly.
Regards,
Antonio.

Any updates about this?
Thanks a lot! Regards,
Antonio.

thanks!


Change ActorCache backpressure to be based on dirty bytes rather than…

… dirty keys

I'm not sure what to use for the default limit, I started with 2MB but that's probably too low?

I'm not sure what to use for the default limit, I started with 2MB but that's probably too low?

I guess I started talking about this in the wrong place (https://github.com/cloudflare/workerd/pull/342#discussion_r1096051793), but I'd go with either 4 or 8 MiB given that our value size limit is 4x what it was when the 64 key limit was put in place and documented. If you want a specific answer then I'd say 8 MiB, but I don't have a strong preference between 4 and 8.


labelArrow option

Fixes #510. Supersedes #702.
Plot now applies a directional arrow such as → or ↑ automatically, even if the scale label is specified explicitly, as long as the given label does not already include a directional arrow. The arrow can be suppressed by setting the labelArrow option to none, null, or false. In addition, the arrow can be forced in cases where it would not appear automatically, such as for ordinal scales, by setting the labelArrow option to true or one of the four orientations: up, right, bottom, or left.
Previously in our repo there were 175 instances of Unicode arrows in specified labels; with this change, there are now only 14 instances! (−92%) The remaining instances are solely for double-ended arrows such as ← Women · Men →.

As context, there are several benefits of removing the arrows:

Arrows are hard to type. (You need to copy-paste an existing one, or bring up the special characters palette.)
Arrows are context-dependent: they are appropriate for axes, but not for tips.
Arrows are orientation-dependent, making it harder to update the plot (e.g., to reverse a scale or swap x and y).


Conflict between julia and python binaries/artifacts

Affects: JuliaCall
Describe the bug
When using a conda/mamba environment and juliacall I encountered an issue when NetCDF files are read by the julia code. When trying to read the files the julia code would raise the following error and crash the kernel:
symbol lookup error: .../.julia/artifacts/*/lib/netcdf.so: undefined symbol: H5Pset_all_coll_metadata_ops

It turns out that this error only occured if python packages depending on netCDF were imported.
For example, the following code would crash:
import esmpy
from juliacall import Main as jl

jl.seval("using NCDatasets")
ds = jl.Dataset("file.nc")

While this runs fine:
from juliacall import Main as jl

jl.seval("using NCDatasets")
ds = jl.Dataset("file.nc")

Workaround:
I managed to avoid this crash by ensuring that the Julia and Python packages used the exact same version of the netcdf5 and hdf5 binaries, in which case things went fine.
However, this can be very challenging to do.

Yes this is an unfortunate effect of using the same library installed by two essentially independent package managers.
A few options I can think of:

What you currently do - specify exact versions of the libraries.
The same, but delegate to a second package such as CondaPkgNetCDFCompat which does nothing except each version specifies a compatible pair of versions of the libraries in Julia and Conda.
Modify CondaPkg to handle this for us. There already exists a special (secret) syntax for libstdc++ to ensure it is installed at the same version as ships with Julia. Could have similar ones for HDF5 and NetCDF which find the version of the JLLs installed and insert a corresponding compat for Conda.

I just ran into this issue as well.  I wonder if it's possible to have a translation table between JLLs and python packages?  Then we can set compat appropriately on the Python end, based on the JLLs in the active Manifest.

I think we could implement the compat packages as extensions of CondaPkg for the corresponding JLL packages so that they would be imported once CondaPkg and some JLL is loaded together.
We could have a global lookup table with the package name or UUID and the compatible versions that could then be checked in CondaPkg._resolve_find_dependencies

@BSchilperoort  How did you find the versions that you had to restrict to make NetCDF work from both python and Julia?

I manually installed the same versions of netCDF4 for python and julia, 1.6.4 for each.
However, in the end we've gone with containerizing the julia numerical model and communicating via a RESTful API instead.


mgmt, codesigning, update tspconfig

No API change.
ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[x] Other, please clarify:

update tspconfig

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Hi @weidongxu-microsoft, it seems trustedsigning is the name for trustedsigning, and they didn't share the namespace review result for codesigning yet.

Hi @weidongxu-microsoft, it seems trustedsigning is the name for trustedsigning, and they haven't shared the namespace for codesigning yet.

Yeah. It is in email
•	Java: azure-resourcemanager-trustedsigning
•	Go/Golang: sdk/resourcemanager/trustedsigning/armtrustedsigning
•	avaScript: @azure/arm-trustedsinging
•	Python: azure-mgmt-trustedsigning

But I cannot find corresponding namespace review issue in azure-sdk repo.

namespace review https://github.com/Azure/azure-sdk/issues/7099


Sorting in reports with link steps doesn't work as expected

When sorting a table which is showing a link step, the sort seems to order numbers based on text sorting rules, not on number sorting rules.
See the column bb n1; the values are numeric but the descending order was done using character order.

@katrinDY this should be done in the next sprint because it's quite a big deal

Found and resolved the issue; has to clean up the code a bit before submitting a PR


⚠ AGEG website (prod) has degraded performance

In d5f59a1, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 2235 ms

Resolved: AGEG website (prod) performance has improved in 3e80646.


Re-enable java in CodeQL action

Signed-off-by: Jean Gauthier<EMAIL_ADDRESS>Re-enable java in CodeQL action (was disabled in #23338)
Contributor Checklist

[X] Review Contribution Guidelines
[X] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[X] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[X] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[X] Ensure that tests pass sanity check: ./gradlew sanityCheck
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation

I've triggered the following builds for you:

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you.


:star: add(css_varriables): Add variables for bar height and color

I added 2 variables, and formatted the css file

Thanks - let me roll this in with the next version on #218.
I'd prefer the variable names to be prefixed (eg, --nprogress-color) so it plays well with other libraries. It'd also be great if there are non-variable fallbacks for the benefit of legacy browsers. I'm going to implement them over at #218.
Thanks for your contribution!


Rework CI to better utilise available workers

4m 17s to 1m 44s, despite MacOS having longer queue times than usual.


Directives that change the shape of the data?

Was having a play with a directive for doing groupBy
query {
    labourItems @groupBy(column: workTypeId) {
      workTypeId
    }
}

which seemed basic enough

  public class GroupByDirectiveProcessor : DirectiveProcessor<GroupByArguments>
    {
        public override string Name {  get => "groupBy";  }

        public override string Description { get => "groups the results by col names"; }

        public override Expression? ProcessExpression(Expression expression, object? arguments)
        {
            var args = arguments as GroupByArguments;
            return GroupByMember(expression, args.column);
        }

        public Expression GroupByMember(Expression expression, string memberPath)
        {
            var parameter = Expression.Parameter(expression.Type.GetGenericArguments()[0], "x");

            var member = memberPath.Split('.')
                .Aggregate((Expression)parameter, Expression.PropertyOrField);

            var selector = Expression.Lambda(member, parameter);

            var groupByCall = Expression.Call(typeof(Queryable), "GroupBy",
                new Type[] { parameter.Type, member.Type },
                expression, Expression.Quote(selector));

            return groupByCall;
        }

        public override BaseGraphQLField? ProcessField(BaseGraphQLField field, object? arguments)
        {
            return field;
        }
    }

    public class GroupByArguments
    {
        public string column { get; set; }
    }

Now obviously I'm not dealing with the fact that you can't select random columns without some form of aggregation (which is why i'm just pulling back the column I'm grouping by currently)
Problem is the code explodes deep within EQL
ExpressionUtil.MakeSelectWithDynamicType
around line 420
MakeSelectWithDynamicType
var call = isQueryable ? MakeCallOnQueryable("Select", new Type[] { currentContextParam.Type, dynamicType }, baseExp, selector) :
                    MakeCallOnEnumerable("Select", new Type[] { currentContextParam.Type, dynamicType }, baseExp, selector);

currentContextParam.Type is a LabourItem instead of a Igrouping, currently trying to figure out if I can somehow change that type in the directive, or if
currentContextParam.Type
just needs to be switched to
baseExp.Type.GetGenericArguments()[0]
Any thoughts?
of course i'd also need to update the selector to take the IGrouping type also which makes me think i need to do this somewhere else in the code.

aware i could probably use a field extension instead, however wasn't sure if that could conditionally change the shape of the output either (pet peeve I have with the pagination at the moment, not that I have a solution either).
So maybe I should be using extension to start the grouping
query {
    labourItem(groupBy: workTypeId) {
      workTypeId
      anotherField @sum
    }
}

then a directive to specify the aggregation type
but I kinda feel like i'd hit the exact same issue with IGrouping

I used to have code that did things like this. But I went down the road of supporting the GraphQL spec to make use of all the tooling.
GraphQL doesn't have support for things that change the shape of the defined schema. I wish they would introduce them. So adding things like this will/may break other tooling you use (generating types etc).
I have thought about bringing them back as an extra feature and noting that they are not technically GraphQL compliant.
Issue is the directive assumes the shape and parameter types will not change. We could look at expanding directive processor to support things like this. Otherwise I think is is possible in a field extension, as that has access to everything needed and can change them.
Introspection likely wouldn't work as you expect as it will only know of 1 return type for the field but it actually has multiple.
I assume your pet peeve with paging is that if you do not supply paging arguments you just want a "flat" array of the entity?
If you're interested in keeping support for GraphQL (and tooling etc - e.g. we generate both Typescript and C# from queries / schema). You'd have to have 2 fields
type Query {
  labourItems: [LabourItem!]
  labourItemsGrouped(groupBy: GroupedLabourItemField): [GroupedLabourItem!]
}

or adding the field and type on the LabourItem so you end up with a query like so
{
   labourItems {
      groupBy {
         workTypeId { # we group by this field
            # selecting from IGrouping
            key # select the key
            connection { #could be named anything
              # fields you want from LabourItem
            }
         }
      }
   }
}

I really wish GraphQL spec introduced support for either methods (labourItems.groupBy) or allow directives that change the return type.
Anyway, could like get something working. I'd have to play with it myself. You best bet is field extensions right now.

I assume your pet peeve with paging is that if you do not supply paging arguments you just want a "flat" array of the entity?

Yep that's exactly it.

You best bet is field extensions right now.

yeah i'll probably go down that path, along with maybe a helper method that lets me add it easily to all fields / subfields.


Audio quality question

So I'm running this bot perfectly fine on an old laptop I found and the audio quality is poor, sounds like its in a tunnel, with no bass. I want to get a Raspberry Pi for the bot, will the audio be better? I want the audio quality to be similar to the Rythm bot. Will the raspberry pi be able to provide the same quality as Rythm?
Thanks!

I also want to add. The audio quality is extremely bad when using the mobile app (inside the home network and outside). I havent been able to test the quality on a pc outside the network, but if someone would like to ill gladly send you a link!!

The bot streams at the best quality available from the service provided (e.g YouTube) as well as what Discord actually supports. If the video requested is a bad quality, the bot won't magically make it sound better. Discord's mobile app is also low quality anyway on some devices, compared to PC.


Is there an equivalent of DelayLoadMetadata in IdentityServer4?

Greetings Everyone,
Is there an equivalent of DelayLoadMetadata in IdentityServer4?
https://identityserver.github.io/Documentation/docsv2/consuming/options.html
Mostly, I am interested in adding Issuer Name and the Signing Certificate to statically validate tokens, but I don't see them yet on version 4.

sure - in the access token validation MW for idsrv4

Hi,
I still could not figure out where the DelayLoadMetadata option is in IdentitySever4 . Would be really helpful if someone could help. :)
Regards,
NIlav Ghosh

it's the default behavior now.

Yes Dominick,
I figured this out. Thanks so much.
Regards,
Nilav Ghosh
On Thu, Jan 5, 2017 at 6:43 PM, Dominick Baier<EMAIL_ADDRESS>wrote:

it's the default behavior now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/IdentityServer/IdentityServer4/issues/126#issuecomment-270641113,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoHAwm_h605lYuJwyUdxDcTasEb7lgVks5rPOyPgaJpZM4I1k-C
.


Packages order is weird

For example: https://componette.com/search/grid
There should be order by starts, shouldn't it?

Fixed and specially deployed for you.
Order by popularity is not only stars.
        switch ($orderBy) {
            case 'push':
                $builder->orderBy('[g.pushed_at] DESC');
                break;
            case 'newest':
                $builder->orderBy('[a.created_at] DESC');
                break;
            case 'popularity':
                $builder->orderBy('IFNULL([g.stars], 0) * 2 + IFNULL([g.watchers], 0) + IFNULL([g.forks], 0) DESC');
                break;
        }

Right. Thanks. :)


Node connection wire issue

Hi ,
While updating the connection am getting the saved data on UI but node connection wire or connectors are not visible initially.
If we move any node then only get the connection wire related to that node help me to get out of this issue.
Without moving node

After moving the node

Thanks in advance.

Duplicate:

https://github.com/jerosoler/Drawflow/issues/708