Pretrained models config

Hi, How can I know configurations used for pre-training models?
e.g. u_patchout, s_patchout_t, s_patchout_f etc...
Thank you!

Hi,
Here is the config for the main pre-trained models:
passt-s-f128-p16-s10-ap.476.pt: {"embed": "default", "input_fdim": 128, "input_tdim": 998, "s_patchout_f": 4, "s_patchout_t": 40, "tstride": 10, "arch": "deit_base_distilled_patch16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "fstride": 10, "u_patchout": 0, "audioset_pretrain": false, "instance_cmd": "get_model"}

passt-s-f128-p16-s10-ap.472.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "fstride": 10, "tstride": 10, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "s_patchout_t": 40, "s_patchout_f": 4, "instance_cmd": "get_model"}

passt-s-f128-p16-s14-ap.469_swa471.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "fstride": 14, "s_patchout_f": 3, "s_patchout_t": 30, "tstride": 14, "pretrained": true, "n_classes": 527, "in_channels": 1, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "instance_cmd": "get_model"}

passt-s-f128-p16-s16-ap.468_swa473: {"embed": "default", "fstride": 16, "input_fdim": 128, "input_tdim": 998, "s_patchout_f": 1, "s_patchout_t": 20, "tstride": 16, "arch": "deit_base_distilled_patch16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "u_patchout": 0, "audioset_pretrain": false, "instance_cmd": "get_model"}

passt-s-f128-p16-s12-ap.470_swa473.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "fstride": 12, "s_patchout_f": 3, "s_patchout_t": 40, "tstride": 12, "pretrained": true, "n_classes": 527, "in_channels": 1, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "instance_cmd": "get_model"}

If you need the configuration for other specific models, let me know.

Hi,
Thank you so much for replying.
I have another question.
Is there any pre-training model with the architecture of Unstructured PaSST
or  PaSST-B?
I would like to know which model has  configurations that 'u_patchout' is
not zero (PaSST-U) or u_patchout', 's_patchout_t/f' (PaSST-B) are all zero.
Because I want to compare them.
Thank you!
2022년 10월 3일 (월) 오후 6:23, kkoutini @.***>님이 작성:

Hi,
Here is the config for the main pre-trained models:
passt-s-f128-p16-s10-ap.476.pt: {"embed": "default", "input_fdim": 128, "input_tdim": 998, "s_patchout_f": 4, "s_patchout_t": 40, "tstride": 10, "arch": "deit_base_distilled_patch16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "fstride": 10, "u_patchout": 0, "audioset_pretrain": false, "instance_cmd": "get_model"}
passt-s-f128-p16-s10-ap.472.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "fstride": 10, "tstride": 10, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "s_patchout_t": 40, "s_patchout_f": 4, "instance_cmd": "get_model"}
passt-s-f128-p16-s14-ap.469_swa471.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "fstride": 14, "s_patchout_f": 3, "s_patchout_t": 30, "tstride": 14, "pretrained": true, "n_classes": 527, "in_channels": 1, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "instance_cmd": "get_model"}
passt-s-f128-p16-s16-ap.468_swa473: {"embed": "default", "fstride": 16, "input_fdim": 128, "input_tdim": 998, "s_patchout_f": 1, "s_patchout_t": 20, "tstride": 16, "arch": "deit_base_distilled_patch16_384", "pretrained": true, "n_classes": 527, "in_channels": 1, "u_patchout": 0, "audioset_pretrain": false, "instance_cmd": "get_model"}
passt-s-f128-p16-s12-ap.470_swa473.pt: {"embed": "default", "arch": "passt_deit_bd_p16_384", "fstride": 12, "s_patchout_f": 3, "s_patchout_t": 40, "tstride": 12, "pretrained": true, "n_classes": 527, "in_channels": 1, "input_fdim": 128, "input_tdim": 998, "u_patchout": 0, "instance_cmd": "get_model"}
If you need the configuration for other specific models, let me know.
—
Reply to this email directly, view it on GitHub
https://github.com/kkoutini/PaSST/issues/25#issuecomment-1265167323, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATHDT3GMGR4CGA54IZETXSTWBKQX3ANCNFSM6AAAAAAQYATBMA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi,
Thank you so much for replying.
I have another question.
Is there any pre-training model with the architecture of PaSST-U or  PaSST-B?
I would like to know which model has configurations that 'u_patchout' is not zero (PaSST-U) or u_patchout', 's_patchout_t/f' (PaSST-B) are all zero.
Because I want to compare them.
Thank you!


invalid swagger.json file generated, validation fails in swagger editor

Context

hapi-swagger version:7.4.0
any other relevant information:

What are you trying to achieve or the steps to reproduce ?
generate documentation and get a valid swagger.json file
Describe your issue here, include example route or JOI schemas.
The swagger.json file hapi swagger generates is not valid and gives some validation errors for routes like
abc/def/{paths*}.
does swagger supports hapi js routes like mentioned above
const server.routes({...})

What result did you get?
What did you expect ?

Closing due to inactivity.


Handle previously processed countries

As in this issue, we need to add a mechanism to label each data with date and let the user know that some data from one country is already exist (so they won't download twice). As a response, in this pull request I added:

date in the created folder name (in the temporary files folder)
mechanism to choose if we want to overwrite the data, or skip the download if we already have the data

Thank you^^

Thank you for all of the nice catches @Arun-kc ! I will fix them all in one commit

LGTM🚀

It doesn't make a big difference in sorting since all files for one country are in separate folders. So having the date first should speed up the sorting. But that is neglectable since it's not many files.

[update] the latest push has been tested, and works well... Sorry for the delay ^^

[Update] I ran this, and now it's well tested... Sorry for the delay ^^

[Update] I ran this, and now it's well tested... Sorry for the delay ^^


Add HybridConnectivity RP registration

This RP is optional but important for some scenarios

@edyoung : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Thanks for the update @edyoung !
#sign-off


add CPLEX 12.9 to julia 1.1.1

So I have this text when i try to add cplex to julia
julia> Pkg.build("CPLEX")
  Building CPLEX → `C:\Users\Cheng\.julia\packages\CPLEX\FUtHu\deps\build.log`
┌ Error: Error building `CPLEX`:
│ ERROR: LoadError: UndefVarError: is_apple not defined
│ Stacktrace:
│  [1] top-level scope at none:0
│  [2] include at .\boot.jl:326 [inlined]
│  [3] include_relative(::Module, ::String) at .\loading.jl:1038
│  [4] include(::Module, ::String) at .\sysimg.jl:29
│  [5] include(::String) at .\client.jl:403
│  [6] top-level scope at none:0
│ in expression starting at C:\Users\Cheng\.julia\packages\CPLEX\FUtHu\deps\build.jl:18

Should be fixed in https://github.com/JuliaOpt/CPLEX.jl/pull/248/

Can you confirm that
] add CPLEX#master
] build CPLEX

fixes the issue ?

Closed by the v0.6.0 tag: https://github.com/JuliaOpt/CPLEX.jl/releases/tag/v0.6.0.


Main service as headless if using ClusterIP

When using ClusterIP, it only provides one record of the server to the client. When using LoadBalancer or a headless service in a Statefulset, the client could receive all the records for every replica inside the server. Using a headed clusterIP service, the client will only receive one of the multiple replicas on every client request.

sorry I'm little late...
There's already an headless service for this purpose: infinispan-ping. Can't we just rely on that one for this use case?

how to get full IP addresses list is in #88


Empty CREATE TABLE statement breaks the migration

I.e. this structure in the source Postgres DB:
CREATE TABLE t_add_inf_value
(
)
WITH (
OIDS=FALSE
);
will give an error during Schema creation (but will continue):
/Library/Ruby/Gems/2.0.0/gems/taps-0.3.24/lib/taps/schema.rb:63:in block in load': undefined method apply' for nil:NilClass (NoMethodError)     from /Library/Ruby/Gems/2.0.0/gems/sequel-3.20.0/lib/sequel/database/connecting.rb:76:in connect'
from /Library/Ruby/Gems/2.0.0/gems/sequel-3.20.0/lib/sequel/core.rb:119:in connect'     from /Library/Ruby/Gems/2.0.0/gems/taps-0.3.24/lib/taps/schema.rb:61:in load'
from /Library/Ruby/Gems/2.0.0/gems/taps-0.3.24/bin/schema:44:in <main>'
Therefore, migration fails during data import since the table does not exist in the target schema.

@fero8 is the schema file you specified a Ruby migration or a SQL script?

Not exactly sure, this was a long time ago. It was a simple PG to MySQL database export as I recall.


[Bug]:

What happened?
When I am trying to connect to a CDX environment using my credentials it is throwing an unknown error.
What version of the tool are you using?
v<IP_ADDRESS>
What version of Visual Studio Code are you running?
No response
Any relevant session id from VSCode?
9d72a098-c39c-4b7b-8ba5-e3949ef802c11723056423301
Relevant log output
VSCode version: 1.92.0.
Extension version: 2.2.0.
Error occured in addConnection command.
Error code: undefined.
Error message: undefined.
Error stack: undefined.

Hello Danish, Can you please provide an update for the same

Which login type did you use?


OCPBUGS-18948: CRD Compatibility Validation

Correct CRD validation to validate CRs against each version of the updated CRD.
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 242f63f

/jira refresh

/retest-required

This should wait for the automated sync... and everything else that's happening to fix testing.

/retest

/test e2e-gcp-olm


fetch() Failing for No Reason I can Find

My code looks like this, which as far as I can tell has no substantial difference with the example.
var topicUrl = 'http://localhost:8000/topics.json'
fetch(topicUrl)
  .then( response => {
  return response.json();
})

This fails no matter what url I use. specifically, then() is never called. In stepping through the code, I've determined that req.on('response', function(res) {}) is never called, neither is req.on('error') (index.js, lines 136 and 131). I haven't been able narrow the problem down further.
node: 6.7.0
node-fetch: 1.6.3

Also: Darwin Kernel Version 15.6.0

Withdrawing this. The problem turned out to be rather more exotic and have nothing to do with node-fetch. Sorry for the spam.


OpenEBS Volume - support for retain and recycle reclaim policy.

Kubernetes supports the following three relcaim policies:

Retain
Recycle
Delete (default for volumes provisioned with Dynamic Provisioner)
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming

There may be some usecases where Delete may not be the best reclaim policy. The user should be able to specify which relcaim policy to use via the storage class.

The retain policy can be used for a given PVC using the following manual steps.
(a) Create a StorageClass with retain policy.
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: jiva-retain
  annotations:
    openebs.io/cas-type: jiva
    cas.openebs.io/config: |
      - name: ReplicaCount
        value: "3"
provisioner: openebs.io/provisioner-iscsi
reclaimPolicy: Retain
---

(b) Create a PVC
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: jiva-vol1-retain-claim
spec:
  storageClassName: jiva-retain
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 4G

(c) A PV will be created with retain policy.
kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM                           STORAGECLASS   REASON    AGE
pvc-46387102-567b-11e9-b9b1-42010a800110   4G         RWO            Retain           Bound    default/jiva-vol1-retain-claim   jiva-retain              41m

(d) Delete PVC, check that PV still exists in Released state.
kubectl describe pv
Name:            pvc-46387102-567b-11e9-b9b1-42010a800110
Labels:          openebs.io/cas-type=jiva
                 openebs.io/storageclass=jiva-retain
                 pvc-name=jiva-vol1-retain-claim
Annotations:     openEBSProvisionerIdentity=gke-kmova-helm-default-pool-17eeeaaa-ldm9
                 openebs.io/cas-type=jiva
                 pv.kubernetes.io/provisioned-by=openebs.io/provisioner-iscsi
StorageClass:    jiva-retain
Status:          Released
Claim:           default/jiva-vol1-retain-claim
Reclaim Policy:  Retain
Access Modes:    RWO
Capacity:        4G

(e) To reuse the above PV, modify the PVC YAML spec to include volumeName pointing to above PVC.
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: jiva-vol1-retain-claim
spec:
  storageClassName: jiva-retain
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 4G
  volumeName: pvc-46387102-567b-11e9-b9b1-42010a800110

(f) The PVC will be in pending state, but attached to the previous PV.
kubectl describe pvc
Name:          jiva-vol1-retain-claim
Namespace:     default
StorageClass:  jiva-retain
Status:        Pending
Volume:        pvc-46387102-567b-11e9-b9b1-42010a800110
Labels:        <none>
Annotations:   kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{
},"name":"jiva-vol1-retain-claim","namespace":"default"},"spec":{"accessMo...
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      0
Access Modes:
Events:        <none>

(g) Patch the PV - to refer to the new PVC.
Get the UID of the PVC
kubectl get pvc jiva-vol1-retain-claim -o=custom-columns=NAME:.metadata.name,UID:.metadata.uid
NAME                     UID
jiva-vol1-retain-claim   a208ba3d-5681-11e9-b9b1-42010a800110

Patch the PVC claimRef UID
kubectl patch pv pvc-46387102-567b-11e9-b9b1-42010a800110 --patch '{"spec": {"claimRef": {"uid": "a208ba3d-5681-11e9-b9b1-42010a800110"}}}'

(h) Wait for the PVC to show the capacity.  Takes about 5s to 10s.
kubectl get pvc
NAME                     STATUS    VOLUME                                     CAPACITY   ACCESS MODES  STORAGECLASS   AGE
jiva-vol1-retain-claim   Bound     pvc-46387102-567b-11e9-b9b1-42010a800110   4G         RWO           jiva-retain    3m

(a) Create a StorageClass with retain policy.

And to obtain an up-to-date template of the "stock" Jiva StorageClass (with the default "Delete" reclaimPolicy), you can use:
$ kubectl get $(kubectl get sc -o name | grep jiva) -o yaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  annotations:
    meta.helm.sh/release-name: openebs
    meta.helm.sh/release-namespace: openebs
  creationTimestamp: "2023-03-06T11:29:52Z"
  labels:
    app.kubernetes.io/managed-by: Helm
  name: openebs-jiva-csi-default
  resourceVersion: "203291"
  uid: dbafba16-fcfb-49bc-9940-784812d95337
parameters:
  cas-type: jiva
  policy: openebs-jiva-default-policy
provisioner: jiva.csi.openebs.io
reclaimPolicy: Delete
volumeBindingMode: Immediate

Then edit out the unique data from metadata.annotations to get an up-to-date and universal sc manifest file.

(a) Create a StorageClass with retain policy.

It should be perhaps added, that while the data and the PV itself (auto-created when PVC is created under reclaimPolicy: Retain) will be preserved after deleting the PVC, the uderlying user data will still have to be manually copied to the new PV, which will be created fresh and empty, in spide of the PVC keeping the same name as previously, which is a bit of a bug IMHO (tested under OpenEBS Host Path StorageClass, but much less obvious - if at all doable - under Jiva).


Add custom angles to polar area graph

Old Behavior
Every angle is 360/#values °
New Behavior
Provide custom value for each angle of the polar graph.
Solution
  	var options = {
 		type: 'polarArea',
 		data: {
 		labels: ["A", "B", "C", "D", "E"],
 		datasets: [{}]
 		},
 		options: {
 			customAngles: [
 				1.0566, 1.7566, 1.0566, 2.1566, 0.2566
 			]
 		}
 	}

Live demo:
https://codepen.io/anon/pen/ZXEmQm

@MarioIannotta please don't create a new PR for every update, simply push to your branch new changes.

Referring to #4752, but maybe you close this one for another reason :)

Yeah, the reason is that I was sleepy :)
Let's use this one :)

Your codepen example doesn't seem to be working

Sorry, there was an issue with github hosting and codepen, it's fixed now.

Thanks for fixing the codepen. It helps demonstrate your PR.
I'm not sure about the name customAngles because really all options are custom, so we could put custom in many of the options. Perhaps calling it just angles would be sufficient?

I like the idea of a scriptable option (I think we should be doing this for all new options if possible).  I believe the current angle is 360 * value / sum_of_values

Closing due to inactivity


Intellisense popup cover command prompt

happens when command prompt stay at the last line of screen,
see attatchment
Version : 4.4.2
CLR     : 4.0.30319.42000

The reason I use Poderosa is Cygwin but now we have WSL,
Then only reason is command prompt, but now I have fzf, it's time to give up.


Restore interprocess communication

This restores the interprocess communication scheme from v2, phasing out the new use of AssemblyLoadContext. This gives us a few benefits at the cost of more messaging passing between processes:

No more assembly loading surprises such as in #259
No more suspicious GetAwaiter().GetResult() in the Test Adapter implementation.
Restores the ability to detect likely StackOverflowException when a runaway test crashes the run.

The interprocess communication scheme used in v2, however, relied on a Windows-specific mode ("Message" mode) for named pipes. This time we use the cross platform "Byte" mode, and rely on StreamReader/StreamWriter to carefully handle byte[] chunks comprising distinct messages.
I've tested this in a solution with 25000 xUnit tests and 25000 Fixie tests to measure the impact of the interprocess communication, with Fixie still running about twice as fast.

Since this was a fairly invasive change, I'd be grateful for some confirmation of the alpha build before I release it.
This PR resulted in experimental MyGet build 3.1.1-alpha.0.3 on the feed https://www.myget.org/F/fixie-ci/
<PackageReference Include="Fixie.TestAdapter" Version="3.1.1-alpha.0.3" />

@jayotterbein  This should resolve your Razor template / dynamic assembly loading issue. I had success with your repro case. It'd be nice to get confirmation from you in your full solution in case you run into something else after this bug is out of your way, but that is not strictly necessary if you don't have that version of the code handy.
@garoyeri I'm more concerned with whether this breaks things outside of Windows. All IDE-based runs would be affected and this would be the first attempt with this interprocess communication technique outside of Windows. In Rider on a mac, could you try the following with this build?

Running all tests with at least one failure included.
Running a small number of selected tests.
Running a test under the debugger and hitting your breakpoint.
Making a test throw a stack overflow exception (a test that just calls itself should hit that in a few seconds). Run all, expecting the run to halt in the middle of the run (StackOverflowException is an unstoppable force), but with a strong user-facing hint in the test result that your offending test threw a StackOverflowException. In VS Test Explorer, the offending test correctly shows as a failure with details like so:

 Message:
    The test assembly process exited unexpectedly with
    exit code -1073741571, indicating the test threw a
    StackOverflowException.

  Stack Trace:
    Fixie.TestAdapter.TestProcessExitException

The 3.1.1 alpha version works for my whole test suite

I tested against a large test suite with that version as well and there were no issues.

Same test suite runs on Rider in Mac in half the time. 💯

Stack Overflow in Rider:

Ok, good to learn that the status code we look for is windows specific, but at least we're catching and reporting exactly what IS coming back from the process even on a mac. I don't consider that a blocker for this release.

Trying to hit a breakpoint in Rider for Mac is failing, it doesn't seem that it ever attaches to the debugger.

Ok, so either Rider isn't picking up on the effect of this magic: https://github.com/fixie/fixie/blob/d17d209608b5edd65e87afe617046c23d33f9f21/src/Fixie.TestAdapter/TestAssembly.cs#L68 or more likely I'm doing a poor job of finding the dotnet executable here: https://github.com/fixie/fixie/blob/d17d209608b5edd65e87afe617046c23d33f9f21/src/Fixie.TestAdapter/TestAssembly.cs#L100

Let me know if there's something I can do help troubleshoot, you know how to get in touch with me :D

Here be dragons.
Documenting a lot here, mostly to give context to future work.

Before this PR, the use of in-process runs of a test assembly within the Test Adapter process itself proved problematic per Jay's original example.
That led to this PR reverting to the v2 style of interprocess communication, and a part of that was the need to provoke the debugger attachment from the original Test Adapter process to enlist the secondary test assembly process. In v2 and now in this PR, we accomplish that by delegating the responsibility to VsTest's provided LaunchProcessWithDebuggerAttached method.
That change broke running tests under the debugger not outside of Windows, but in fact broke running tests under the debugger outside of Visual Studio. I can repro Garo's broken debugger attempts in Rider on Windows, which led me to see confirmation in https://github.com/microsoft/vstest/issues/2815 and related https://github.com/SpecFlowOSS/SpecFlow/issues/2310 where they face the same basic challenge of needing to generally run tests in a dedicated process, but one that is then hard to attach the debugger to.
I can't thread the needle to satisfy all cases seamlessly, but I'm now aiming for a compromise that helps out as often as possible: use the interprocess communciation approach whenever possible, and fall back to the in-process technique when we have no choice. That means we'll have in-process runs outside of Visual Studio when the user chooses to debug their tests. The only known failure case, then, would be if Jay's assembly generating code were attempted under the debugger in Rider & Friends; he can debug in Visual Studio without ill effect.
So a user outside of Visual Studio, with an assembly loading complication like the original bug report, running under the debugger, with get a test failure that makes little sense. Their recourse would be to run the test project itself under the debugger (it is a console app that runs its own tests).
I've left a hint over on the VsTest issue for a suspicious discrepancy that might account for the real issue here. I can try to phase out this workaround once that lands.


Feature creep... macro to call another macro

I had a cool way of making a bit of display code very easy, by calling a macro from another.
I made sure the one being called was first in the file.
I thought, great, this is easy.
Back of my mind, I wondered if it would work.
ez80asm gave no errors, so must be ok.
Didn't work.
Looked at LST file, did not include that bit of code, just jumped over it :-(
Read docs, not implemented :-(
Something for the future, when you have nothing else to do!
I re-wrote with functions instead...

Yup; it's not implemented, nor will it be, very probably. But maybe ;-)

No worries, I thought I was being too clever... or optimistic!
You can trust me to try to use features that nobody else would even think existed.

Well, it looks like I do have something cooked up that seems to work. Included some recursion limit and detection as well. If you'd like to test it out, I can push the branch out tomorrow

Try this one - https://github.com/envenomator/agon-ez80asm/tree/nestedmacros

I will try it out today :-)

OK, quick test. Maybe more work that you thought...
Nested macros work with fixed values, but not if values need to be passed into them from the calling macro, eg:
This test calls:
PRINTCAPTION_AT_XY caption2, 2, 15,20
To print a caption with a colour at a x,y tab location.
This WILL work:
macro TAB_TO_XY x, y
ld a, 31
rst.lil $10
ld a, x
rst.lil $10
ld a, y
rst.lil $10
endmacro
macro SETCOLOUR colour
ld a, 17
rst.lil $10
ld a, colour
rst.lil $10
endmacro

macro PRINTCAPTION_AT_XY caption, **colour, x, y**
SETCOLOUR **5**			;colour
TAB_TO_XY **3,5**		;x, y
ld hl, caption
call printString
endmacro

BUT where values should be passed from one macro to another does NOT work and gives error:
macro PRINTCAPTION_AT_XY caption, **colour**, **x, y**
SETCOLOUR **colour**
TAB_TO_XY **x, y**
ld hl, caption
call printString
endmacro

Macro [SETCOLOUR] in "nested_macro_test.asm" line 29 - Unknown identifier 'colour'
	ld a, colour
	SETCOLOUR colour
Invoked from "nested_macro_test.asm" line 90 as
	PRINTCAPTION_AT_XY caption1, 1, 10,10

Ahh.. the invocation of a macro instruction wasn't ever transformed into macro-local arguments before, because there was no 'level'.

Can you try again with the latest commit in this branch?

FABULOUS... initial testing seems to work.
NOTE, all testing done on Mac ez80asm build, not Agon.
First, I tested 1 level of nesting, using the following calls.
PRINTCAPTION_AT_XY caption1, 1, 0,0
PRINTCAPTION_AT_XY caption2, 2, 5,5
PRINTCAPTION_AT_XY caption3, 5, 10,10
PRINTCAPTION_AT_XY caption4, 7, 15,15

To macros:
macro TAB_TO_XY x, y
ld a, 31
rst.lil $10
ld a, x
rst.lil $10
ld a, y
rst.lil $10
endmacro

macro SETCOLOUR colour
ld a, 17
rst.lil $10
ld a, colour
rst.lil $10
endmacro

macro PRINTCAPTION_AT_XY caption, colour, x, y
SETCOLOUR colour
TAB_TO_XY x, y
ld hl, caption
call printString
endmacro

Then I tested with a second level nesting and all worked still :-)
PRINTCAPTION_AT_XY caption1, 2, 0,0
PRINTCAPTION_AT_XY caption2, 3, 5,5
PRINTCAPTION_AT_XY caption3, 4, 10,10
PRINTCAPTION_AT_XY caption4, 5, 15,15

macro TAB_TO_XY x, y
ld a, 31
rst.lil $10
ld a, x
rst.lil $10
ld a, y
rst.lil $10
endmacro

macro SETCOLOUR colour
ld a, 17
rst.lil $10
ld a, colour
rst.lil $10
endmacro

macro PRINTCAPTION_AT_XY caption, colour, x, y
TAB_TO_XY x, y
PRINTCOLOURCAPTION colour, caption
endmacro

macro PRINTCOLOURCAPTION colour, caption
SETCOLOUR colour
PRINTCAPTION caption
endmacro

macro PRINTCAPTION caption
ld hl, caption
call printString
endmacro

Well done!!!
Good that order of macros is not important, it finds the macro even if not yet defined.
I will add into my projects over time and should be a good feature for setting up graphics and data were we have fixed data.
I know ultimately it doesn't actually affect binary size, but it does (sometimes) make the code easier to write or to read.
It almost allows the creation of a whole new user defined language in z80 assembly !
However, I appreciate that when we need dynamic data, obviously, functions will be the way to go still.

Nice. There are still a few things that need to be completed before I'll merge this feature into main. Currently the Macro level is already indicated in the listing, so that's done. I'll need to work on surfacing nested warnings next and the error it throws at a maximum depth. I think for now a sensible depth would be 4-8 nestings deep, let's set it at 8. The stackspace usage isn't very large, but we need to set a max depth.

8 levels deep should be plenty. I had to think hard to get a meaningful use case for 2 levels deep (if what I have done you would deem to be '2 levels' deep'), but I am sure it will arise.

Warning/error surfacing complete, and now show exactly how they were called including expanded arguments. Included your testfile as automated test. Merged with the main branch as it looks solid.

Cool, I will do a new build and try it in the morning.

Thinking about things I might miss before doing another release with this code, I only just thought about this:
I don't allow global labels in a macro body, only local- and anonymous labels. When using local labels, upon expanding the macro twice inside the same outside label scope (for example after a global label, before the next global label), you'll get a collision warning that the local label has already been defined. If you invoke it the second time in another global label's scope, that won't happen.
With anonymous labels you won't have this issue, but if the macro is expanded using anonymous labels surrounding the location it's being expanded from, one might be jumping/referring to an unintended anonymous label.
What do you reckon a good solution would be going forward?

Disable local labels within a macro, only allowing anonymous labels, provide a warning in the docs
Create some additional scope code, that would somehow allow macro bodies to have their internal local label scope
Do nothing and mark it as treacherous waters in the docs

Would love to hear your thoughts on this.

I'll give it some more thought today, but my initial thoughts are....
So far, I have kept things simple and haven't used labels in macros at all, so the issue/question hasn't arisen. I would have to think of some use cases for making macros bigger that needed those labels. Also, note to self... Labels can be used to hold a variable, or as a jump point...
I had always considered macros as 'fixed' code, rather than really runtime, if that makes sense? As macros in my mind are not 'dynamic' code, but just expanded at assemble time, my gut reaction has been to keep them for simple routines that are just snippets of code that can be read easier with a name assigned to them, such as CLS, TABTO X, Y, etc.
OR, I used macros for a bunch of data to be sent to VDP, which purely builds a bigger string of data, but in an easy to read format.
eg. MAKEBITMAP W,H,ID, file
I have never (so far) made any macros where any decisions need to take place, so need to think of a use case example of that. I have not used JR z, xxxx etc inside a macro, which would be the reason for including local labels
eg, MAKE_RECTANGLE X,Y,X2,Y2 where the code puts predefined values into X, Y, etc.
Nor have I used a global 'variable' within a macro. However, they could to be. Whilst you cannot pass a variable value into a macro like a function, there is no reason that global 'variables' couldn't be used inside the expanded code. Therefore, global labels would be essential.
However, if the macro could refer to labels, then it could be used like a function.
BUT, then the question is, why do a macro if you can do a function?? A function if called more than once, will be more efficient on memory usage.
My assumption was that any labels created inside that macro would be local, because I think the docs said so. But I don't see why they should be. If truly expanded, maybe they should be treated as if they were a global label. ie, Only ever allow a label name to be used once, a global, would make sense to me, but I am not a hardened coder like some. Anonymous labels (which I have only just got my head around in my main body of code) could work, but I can see the issue if you make a call within a macro to another, by the time you expand, that may no longer be the next anon label @@. However, this could also be an issue with any code written, whether inside a macro or not.
So, maybe allow anon labels with the docs caveat of 'watch out', but allow global labels to be used, and cut out local labels?

Good point about collision.
I would opt for keeping it simple, whatever that is!

I'm releasing a new version in a few weeks, early next year. It will likely take a long, long while before I'll release another version after that. I consider this version to be functionality as complete as I want it to be.
I'll consider (small) feature requests and/or bug fixes before releasing.

If I spot anything, or hear anything from anyone, will let you know. Other than that, it's a brilliant piece of work, something you should be really proud of achieving.
NOTE: I could not have done all the Agon work without your tools and support. I, and I know everyone else in the Agon community, really appreciate your work on the Agon system. If I ever stop Agon coding, I shall have to re-visit my ZX Spectrum...
I have by some miracle, managed to build ez80asm on my old Raspberry Pi400 today, just to see if I could. I put a new OS on the Pi first. I got Sublime Text working, so just need to link the two the same way I do it on my Mac. I need to get pySerial installed too for sending over UART. Not that I will ever develop on the Pi, just useful to know or document how it can be done.
Thank You.


Support running under UID 500

When started by the Flatcar core user, the SDK failed to use UID 500
because inside the SDK there already is the core user from nss-altfiles
with the same ID. This way, the SDK user was continuing with UID 1000
and had permission errors.
Allow to reuse an existing ID for the SDK user. To take effect without
creating new images, the sdk_entry.sh file from the scripts repo is
used instead of the internal copy. However, this only works when
usermod doesn't find a process that uses this ID, and we had a race
between the SDK entry points called by "docker start" and by
"docker exec". The race is unwanted anyway because we don't want to
execute the commands while setup_board is still running. Solve it by
setting the entrypoint for "docker start" to "sleep infinity" in
"docker create".
How to use
Backport
Testing done
Tested on Flatcar manually
Pipeline run with SDK (ongoing)
Pipeline run from Packages job (ongoing)

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
↑ not needed

Also, we likely want to back-port this change to Alpha, Beta, Stable, and LTS 2022.


Fixing Wiki bibitems with [obeyspaces]{url} introduces new anomaly

Hi - package 'hyperref' could not be used because it redefined  "\C" which I use to denote the
complex number field, and altering all those instances is liable to lead to typos and errors I might not catch.
So I used \usepackage[obeyspaces]{url}, and it seems to work OK, changing
@misc{ALTwiki:Kabsch_algorithm,
author = "Wikipedia:Kabsch",
title = "{Kabsch algorithm} --- {W}ikipedia{,} The Free Encyclopedia",
year = "2018",
howpublished = {\url{http://en.wikipedia.org/w/index.php?title=Kabsch%20algorithm&oldid=838166818}},
note = "[Online; accessed 22-August-2018]"}
to
@misc{ALTwiki:Kabsch_algorithm,
author = "Wikipedia:Kabsch",
title = "{Kabsch algorithm} --- {W}ikipedia{,} The Free Encyclopedia",
year = "2018",
howpublished = {\url{http://en.wikipedia.org/w/index.php?title=Kabsch algorithm&oldid=838166818}},
note = "[Online; accessed 22-August-2018]"}
Except that now in the PDF bibliography, it inserts MANY spaces, not one, so the reader of a paper copy would not immediately understand what the actual number of spaces in the URL was supposed to be:
Wikipedia. Kabsch algorithm — Wikipedia, the free encyclopedia.
http://en.wikipedia.org/w/index.php?title= Kabsch      algorithm&oldid=1154985301, 2023k. [Online; accessed 31-July-2023].
Wikipedia. Hurwitz’s theorem (composition algebras) — Wikipedia, the free encyclopedia. http://en.wikipedia.org/ w/index.php?title=Hurwitz’s     theorem     (composition    algebras)&oldid=1164729916, 2023j. [Online; accessed 31-July-2023].
HOWEVER,  very very strangely, when I COPY out of the pdf file, which prints with multiple spaces as above,
it PASTES BACK into this email with single spaces!   So I am not certain what I should do before I turn in the book
on Sept 18 to fix this ??
Wikipedia. Hurwitz’s theorem (composition algebras) — Wikipedia, the free encyclopedia. http://en.wikipedia.org/ w/index.php?title=Hurwitz’s theorem (composition algebras)&oldid=1164729916, 2023j. [Online; accessed 31-July-2023].
Best, Andy

Oh wow ---  when it inserted my text into your Issue text above,  it DELETED the extra spaces I inserted in the two
copied bibitems (Kabsch and Hurwitz) after "what the actual number of spaces in the URL was supposed to be:"
So you can't see what I see in the pdf, which is a zillion extra spaces everywhere I replaced %20 by  a single
typed .

Hi, - leave it as it is. As long as an input is correct, we can deal with it.


RUST_BACKTRACE advice on Engine panic is weird

Noticed while reproducing https://github.com/prisma/prisma/issues/12704
With no RUST_BACKTRACE defined:
PS C:\Users\Jan\Documents\throwaway\12704> node .\script.js
thread 'tokio-runtime-worker' panicked at 'not yet implemented', query-engine\connectors\mongodb-query-connector\src\logger.rs:160:31
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
PrismaClientUnknownRequestError:
Invalid `prisma.user.create()` invocation in
C:\Users\Jan\Documents\throwaway\12704\script.js:6:32

  3 const prisma = new PrismaClient()
  4
  5 async function main() {
→ 6   let user = await prisma.user.create(
  not yet implemented
    at Object.request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:45582:15)
    at async PrismaClient._request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:46405:18)
    at async main (C:\Users\Jan\Documents\throwaway\12704\script.js:6:14) {
  clientVersion: '3.12.0'
}

Then with RUST_BACKTRACE=1:
PS C:\Users\Jan\Documents\throwaway\12704> $env:RUST_BACKTRACE=1
PS C:\Users\Jan\Documents\throwaway\12704> node .\script.js
thread 'tokio-runtime-worker' panicked at 'not yet implemented', query-engine\connectors\mongodb-query-connector\src\logger.rs:160:31
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
PrismaClientUnknownRequestError:
Invalid `prisma.user.create()` invocation in
C:\Users\Jan\Documents\throwaway\12704\script.js:6:32

  3 const prisma = new PrismaClient()
  4
  5 async function main() {
→ 6   let user = await prisma.user.create(
  not yet implemented
    at Object.request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:45582:15)
    at async PrismaClient._request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:46405:18)
    at async main (C:\Users\Jan\Documents\throwaway\12704\script.js:6:14) {
  clientVersion: '3.12.0'
}

Then with RUST_BACKTRACE = "full":
PS C:\Users\Jan\Documents\throwaway\12704> $env:RUST_BACKTRACE = "full"
PS C:\Users\Jan\Documents\throwaway\12704> node .\script.js
thread 'tokio-runtime-worker' panicked at 'not yet implemented', query-engine\connectors\mongodb-query-connector\src\logger.rs:160:31
stack backtrace:
   0:     0x7fff2b4ee4af - napi_register_module_v1
   1:     0x7fff2b50fe7a - rust_eh_personality
   2:     0x7fff2b4e5bd8 - napi_register_module_v1
   3:     0x7fff2b4f12db - napi_register_module_v1
   4:     0x7fff2b4f0dd4 - napi_register_module_v1
   5:     0x7fff2a370a30 - <unknown>
   6:     0x7fff2b4f1896 - napi_register_module_v1
   7:     0x7fff2b4f166f - napi_register_module_v1
   8:     0x7fff2b4eedf7 - napi_register_module_v1
   9:     0x7fff2b4f1399 - napi_register_module_v1
  10:     0x7fff2b69f3a0 - rust_eh_personality
  11:     0x7fff2b69f2ec - rust_eh_personality
  12:     0x7fff2a845623 - napi_register_module_v1
  13:     0x7fff2a844a40 - napi_register_module_v1
  14:     0x7fff2a8457a4 - napi_register_module_v1
  15:     0x7fff2a72eb40 - napi_register_module_v1
  16:     0x7fff2a7924f5 - napi_register_module_v1
  17:     0x7fff2a48e665 - napi_register_module_v1
  38:     0x7fff2b3f2d6f - napi_register_module_v1
  39:     0x7fff2b3e6444 - napi_register_module_v1
  40:     0x7fff2b3dcae6 - napi_register_module_v1
  41:     0x7fff2b3eb440 - napi_register_module_v1
  42:     0x7fff2b3f7816 - napi_register_module_v1
  43:     0x7fff2b3e9745 - napi_register_module_v1
  44:     0x7fff2b3e72e3 - napi_register_module_v1
  45:     0x7fff2b4fb8dc - napi_register_module_v1
  46:     0x7fffaee454e0 - BaseThreadInitThunk
  47:     0x7fffafb2485b - RtlUserThreadStart
PrismaClientUnknownRequestError:
Invalid `prisma.user.create()` invocation in
C:\Users\Jan\Documents\throwaway\12704\script.js:6:32

  3 const prisma = new PrismaClient()
  4
  5 async function main() {
→ 6   let user = await prisma.user.create(
  not yet implemented
    at Object.request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:45582:15)
    at async PrismaClient._request (C:\Users\Jan\Documents\throwaway\12704\node_modules\@prisma\client\runtime\index.js:46405:18)    at async main (C:\Users\Jan\Documents\throwaway\12704\script.js:6:14) {
  clientVersion: '3.12.0'
}

Note how RUST_BACKTRACE=1 did not actually do anything useful 😞
This might of course just be a Rust thing we can not influence.

Hi there,
As part of our effort to clean up our GitHub repo, we’re closing this issue to help focus on features and improvements that align with our focus areas and those of our community.
This issue was originally created for internal tracking purposes, but if you feel this is important to you, feel free to reopen the issue and get like-minded users to upvote as we will prioritize fixing issues based on community interest.
For more insight into our priorities and how we’re thinking about the future of Prisma, please see our blog post: https://www.prisma.io/blog/prisma-orm-manifesto.
Thank you for your understanding and support!


Variety field is mandatory. Please update documentation

order_id = kite.place_order(tradingsymbol="INFY",
exchange=kite.EXCHANGE_NSE,
transaction_type=kite.TRANSACTION_TYPE_BUY,
quantity=1,
order_type=kite.ORDER_TYPE_MARKET,
product=kite.PRODUCT_NRML)

closed


s2n_map: a basic map implementation

This change adds s2n_map, a very basic, append-only map implementation for s2n.
Updates are append only and are not thread-safe, but once built a map is
considered immutable and thread-safe lookups are possible.
Internally s2n_map is a simple hash map which uses linear-proving go resolve
any collisions. The load-factor is maintained at 50% or below so the worst-case
collision probability on a fully-loaded map is:
1 probe:  50%
2 probes: 25%
3 probes: 12%
4 probes: 6%
5 probes: 3%
6 probes: 1%

and so on. s2n_map "owns" all of its own memory, so when keys and values are
added their contents are duplicated and the caller may release the originals.
The copies in the map are freed when the map itself is freed.
This map is intended for looking up client certificates and other indexing
problems within s2n.
NOTE: for now, s2n_map uses SHA256 as its hash. A later change may implement
CRC32 or murmer as an s2n_hash implementation, for additional speed.

Another note: We'll also likely use this map implementation to support certificate selection based on SNI, etc.


Service API calls timeout

Hi there!
I'm experiencing some problems when running commands related to services such as bx service offerings or bx service create calls.
Since I'm using the CLI for the Bluemix Essentials Devworks course, I don't know how to test other verbs or actions related to services.
I'm not using a HTTP proxy or setting up specific firewall rules.
I've pasted the terminal session since login in this link: https://pastebin.com/i4b72xVi
I don't know if it is a network issue or some sort of instability. Hope you guys can help me!
Thanks in advance!

It seems it was a network issue. Worked perfectly under new network conditions.
Issue closed.

thanks for the update, closing the issue.


Ubuntu 20 setup issues

@marinagmoreira
I am setting up the simulator on a Ubuntu 20 machine, and the OpenCV build clashes with ROS. Namely, "libvtk6-dev" clashes with it and wants to uninstall it.
I'll try to find a fix for it and report back here - unless you have a fix already? :)

We build opencv now with debbuilder (in the install debians script), no need to install it from source.
We've ran into similar issues when both were trying to be installed at the same time (making the debian while having opencv installed from source), my advice is to start from a clean machine if possible and follow the instructions closely not to install opencv from source.

Hi @marinagmoreira, you are right, changing the installation order fixed it!
However, when running
./src/scripts/configure.sh -l -F -D -p $INSTALL_PATH -w $WORKSPACE_PATH , I get the error that "w" is an illegal option. Upon inspecting the configuration script, I see that there is no option for w - is this deprecated?
Cheers,
Pedro

Thanks @marinagmoreira , it worked with the new release. Also, the -mtune and -march flags were nto a problem anymore, so I'm closing this issue :)


enhance: support recognizing env names from var file suffixes

Currently we support grouping var files like prd.tfvars with prd-defaults.tfvars. This adds similar support to also group prd.tfvars with defaults-prd.tfvars.
Also for the case where we have vars called redis-prd.tfvars and redis-dev.tfvars, we still want to add them to the project if there's no other matching prd.tfvars or dev.tfvars file.
This also includes a fix to update the module loader tests since it looks like TFC registry has switched to using the commit ref instead of tag.

Test failures look unrelated.


test-branch/execute-job/quoted-authorization/7303d2eb-22c7-4973-82ae-f084d504090c

PR for testing 55c0cac152e4f3b397be27491da004b99adba212

/canonical/self-hosted-runners/run-workflows 55c0cac152e4f3b397be27491da004b99adba212


How do you return the auto-generated id after inserting data?

How do you return the auto-generated id after inserting data?
My configuration:
spring.shardingsphere.sharding.tables.transaction.key-generator.column=id
spring.shardingsphere.sharding.tables.transaction.key-generator.type=SNOWFLAKE
spring.shardingsphere.sharding.tables.transaction.key-generator.props.worker.id=123
spring.shardingsphere.sharding.tables.transaction_item.key-generator.column=id
spring.shardingsphere.sharding.tables.transaction_item.key-generator.type=SNOWFLAKE
spring.shardingsphere.sharding.tables.transaction_item.key-generator.props.worker.id=124
LOG:
INSERT INTO transaction_201912  ( user_id,amount,created_time , id) VALUES(?, ?, ?, ?) ::: [1, 300, 2019-12-11 11:23:27.853,<PHONE_NUMBER>29676289]
I want to get the auto-generated id after inserting the data.
My code:
Transaction transaction = new Transaction();
transaction.setUserId(userId);
transaction.setAmount(amount);
transaction.setCreatedTime(new Date());
transactionService.insert(transaction);
    TransactionItem transactionItem = new TransactionItem();
    transactionItem.setTransactionId(transaction.getId());
    transactionItem.setNum(num);
    transactionItem.setGoodName("1");
    transactionItem.setPrice(price);
    transactionItem.setCreatedTime(new Date());

    transactionItemService.insert(transactionItem);

BUT:
transaction.getId() is null.
What should I do?

Can you try to example first?

Can you try to example first?
There are table1 and table2, the table1_id of table2 is the ID of table1, and the table1 ID is generated automatically by the snowflake algorithm built in sharding-jdbc.
Now, I'm in the same transaction, I'm adding a piece of table1 data (the transaction didn't commit), and then I need to add table2 data, but I need the ID value of table1, the ID value of this table1, and I can't get that ID at this point.
In mybatis, if table1's ID is automatically generated, the generated ID is automatically injected into the inserted entity class. So I can get the generated ID value from the ID field in the entity class.

you can try shardingshpere-example org.apache.shardingsphere.example.core.jdbc.repository.OrderRepositoryImpl#insert()

Closed because no response anymore.


Generalize pooling to support arbitrary layout

enables pool2d support arbitrary layout, as long as there's H and W.
the change here also assumes a layout convention (I will make a PR to NNVM), upper case C indicates an axis (e.g., channel) and lower case with factor size 16c indicates the split axis of C.
cc @kevinthesun @yidawang

Since this is an API improvement, we want to document it clearly.
please add a document of the new layout convention string here, and add the comment to the c++ and python part.

@tqchen you mean change the calculation & document here?https://github.com/dmlc/tvm/blob/d64ff0f19049a34a37d8a17d73bb9b90cfa6d14f/topi/python/topi/nn/pooling.py

@yzhliu I just mean add documentation about what are the additional options, and how should they correspond translate to the calculation rule. It would be nice to update the topi python implementation as well, as we haven't yet fully transit to c++

@tqchen I have added more to c++ function documents. I feel it would be better to redirect python implement to c++ one, other than implement again in python. Any easy way to do so?

yes, checkout topi/tests/python_cpp, which should have already been doing so

I see. thanks.
and could you check why the CI failed?

@tqchen ci passes, ready for review.

Given that layout is a topic of increasing interest, I want to have a more in-depth discussion, created a RFC here https://discuss.tvmlang.org/t/datalayout-structure/80


Docs say "helper" property instead of "helpers"

The docs say:

Built in helper methods are stored on the Poet instance's helper property. Used internally, and in the view locals, they can be used outside of Poet as well.

Shouldn't that be helpers instead?

Yes, this should be fixed


PrintLabel, get carriers lbs price

Hello,
Thank for this package. It helps too much for our project. We have questions.
How can we create labels for our orders that created manually?
How can we check prices for our account, which carrier, which lbs return price?
Thank you,
Best regards

Hi there,
I'm not sure. These aren't use cases I've personally ever had to implement. I'd recommend reading through their API docs to determine what is/isn't possible.


Trigger an alert for each event should't have number of alerts generated capped at 20

I am creating a new custom connector for azure sentinel integration. The platform I am integrating with has their own statuses and severity, so when I ingest that data into the logs and promote it to azure sentinel incidents, it has status and severity as New and Medium(severity according to what I have set in analytic rules). I am syncing the status and severity using a playbook where it reads the description of alert(using analytic rule I have added status and severity info of other platform to description of incident) and then updates accordingly. If I get multiple events grouped into single alert, it will be impossible to update status or severity, or even keep track of and analyse those individual events as a threat analyst.
Please increase the cap to a much, much larger number so that it will not create problems for historical poll, or even better, don't keep a cap at all.

Hello @shikhin-metron, please raise this as a feature request in Sentinel user voice, thanks!
https://feedback.azure.com/d365community/forum/37638d17-0625-ec11-b6e6-000d3a4f07b8?WT.mc_id=m365-0000-rotrent


logging: printk: Fix userspace issue

The syscall needed by CONFIG_LOG_PRINTK is completely problematic, it does
not check ANY parameter that is given and it uses variadic argument
that are not copied / checked before being used in the implementation,
instead it just pass a pointer to user stack with unknown data that is
blindly consumed by the kernel.

Kind of wild we had this at all

I got surprise how long this exists.  Just enable CONFIG_LOG and s/printf/printk in hello_world_user sample and:
Booting from ROM..
*** Booting Zephyr OS build zephyr-v3.5.0-1431-g4fe2605160fd ***

[[0000:00:00.010.:,000]00:00.010,000] rr>1;31 os: <RAX: 0<err> ooa0b900116877bf00 RBX: 0x0000000000000010 RCX: 0x0000000000000000 RDX: 0xeneral protection fault (code 0n
0))[00:00:00.010,000] <err> os: RSI: 0x0000000000000008 RDI: 0xa0b900116877bf00 RBP: 0x0000000000155ca0 RSP: 0x0000000000155be8
00:00:00.010,000] <err> os:  R8: 0x0000000000000000  R9: 0xa0b900116877bf00 R10: 0x0000000000000000 R11: 0x000000000011681a
[00:00:00.010,000] <err> os: R12: 0x0000000000155cd8 R13: 0x0000000000000000 R14: 0x000000000000000a R15: 0x0000000000000008
[00:00:00.010,000] <err> os: RSP: 0x0000000000155be8 RFLAGS: 0x0000000000000246 CS: 0x0018 CR3: 0x0000000000161000
0[00:00:00.010,000] <err> os: RIP: 0x0000000000114162
[00:00:00.010,000] <err> os: >>> ZEPHYR FATAL ERROR
0: CPU exception on CPU 0
[00:00:00.010,000] <err> os: Current thread: 0x120000 (unknown)
[00:00:00.020,000] <err> os: Halting system

That to not tell the kind of wild things a more elaborated payload could do.


Adding EOL notice for v1 in README

Summary
Adds a notice about v1 EOL and where to find more information on running v1.x
Don't be afraid of providing feedback on this one! I just wanted to get the discussion/idea started, if there's a better way I am 100% behind it!

I like the idea! Can we also define the tab spaces and basic formatting rules so that we do not have to face any formatting problems!

I agree @ShubhamPalriwala that it would be good to have some guidelines for the coding style, at the moment we tend to follow the style of the file that we are changing. Did you want to raise an issue for this?

I think a separate issue would be great.  We can also tailor the eslint rules and .gitconfig for line endings, indentation, code style, etc. :)


[SDP-1032] Flip SDP's flag usage from ENABLE_RECAPTCHA to DISABLE_RECAPTCHA and add a Secure Operation Manual

What
Flip SDP's flag usage from ENABLE_RECAPTCHA to DISABLE_RECAPTCHA.
Also, add a new section for Secure Operation Manual.
Why
To remain in sync with the change from https://github.com/stellar/stellar-disbursement-platform-backend/pull/150

Preview is available here:http://developers-pr292.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr292.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr292.previews.kube001.services.stellar-ops.com

@ziyliu: this PR will need to be merged after we release 1.0.2.

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr292.previews.kube001.services.stellar-ops.com


update openaps-install for Pi

This PR makes openaps-install work properly with the Raspberry Pi (2017-09-07-raspbian-stretch-lite.zip), and should preserve compatibility with the Edison as well.

This is ready to merge if no objections.

This now includes some changes (improvements, I hope) to oref0-setup.  They look good to me, but if anyone wants to review those before merging, please speak up.  Otherwise I'll merge them to test further in dev.

LGTM


Implemented and Tested CachedKey.

There was no way to check if there exists a cachedHandle with a specific template so I added CachedKey, which returns a key if the template exists at a given handle. It will return an error if it does not find the exact key template.

/gcbrun


one question about scaling of images

Hi again Saafke,
i wanted to quest you something.When we augment our data using scaling with 0.6 , 0.7, 0.8, 0.9 factor then we have to downscale them again with the scale factor(2 or 3 or 4) to produce the training data?

Hi johnnie,
Yes, as a first step, we do data augmentation, with as only goal to generate more diverse training data. In the original paper they do:

resizing the images with scale-factors 0.6, 0.7, 0.8, 0.9 (more variation because of the downscaling)
rotating the images (more variation because the images are in different orientations)

The second step is to actually build the training dataset. That is, to create the input-output pairs. Remember that our task is to increase the resolution for images. So the network should learn to do this. We therefore create input-output pairs, where the input will be the smaller resolution images, and the output will be the higher resolution images. We already have the higher resolution images (the normal images, our result from step 1), so to create the corresponding lower resolution images, we just downscale them again by the desired factors (2, 3 and 4) in this case.
Then during training, we can feed as input the lower-resolution images to the network. The output or ground-truth images (that the network will learn to predict) will be the corresponding higher-resolution images. The network will then learn to up-scale images by a scale factor of 2, 3 or 4.
Hope it makes sense. Let me know if it's unclear.


Tidy up a comment

English is not my first language

Oh, that commit got wrong issue number in the comment

Thank you ¡ I have no much idea 💡 of what's allbthis projects set up ,but
I try to Follow.
Have a great day ¡
On Sat, Nov 27, 2021, 7:53 PM Tobias Brox @.***> wrote:

Oh, that commit got wrong issue number in the comment
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/python-caldav/caldav/pull/135#issuecomment-980814998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM7HBENQGNP6JIVUUHIPG7DUOF4OXANCNFSM4XGUXMGQ
.


Writing files from preopened directories with Reactors

I have been trying to write to a pre-opened directory from a Wasm Reactor however I continually get the error.
Write fileopen /test.txt: errno 76

From looking into this I found this issue on wasmtime:
https://github.com/rust-lang/rust/pull/79997#issuecomment-759856446
It states that you must call _initialize in order to use pre-opened directories but I have tried this and failed to get it working.
I am initiating the runtime using the following code.
  public void init() {
    WasiCtx wasi = new WasiCtxBuilder().inheritStdout().inheritStderr().preopenedDir(Path.of("./"), "/").build();

    store = Store.withoutData(wasi);
    engine = store.engine();
  }

Then from Go I have a simple function, the complete wat can be found below.
//go:export write_file
func write_file() int {
	fmt.Printf("Write file")

	err := ioutil.WriteFile("/test.txt", []byte("Hello"), 0644)
	if err != nil {
		fmt.Println(err)
		return 1
	}

	return 0
}

Before callingfile_write I call _initialize like so.
    Func f = linker.get(store, "", "_initialize").get().func();
    WasmFunctions.Consumer0 fn = WasmFunctions.consumer(store, f);
    fn.accept();

I did get this working with a Command and adding the file write code into main with the wasmtime cli but not successfully from a reactor.
Kind regards,
Nic

I am just looking at another issue where this was raised, I am actually using windows at the moment, will try on my mac to see if I get the same issues.

I have tested this on both windows and on my mac (both with absolute and relative paths) and in both instances I get an error 76 and the report that the file is not accessible.
Go wat:
go.zip

The _initialize function in your wasm module has empty body so it's no-op.
$ grep -A 3 '^ *(func $_initialize' go.wat
  (func $_initialize (type 6))
  (func $hello (type 2) (param i32) (result i32)
    (local i32 i32 i32 i64 i32)
    global.get 0

Actually I've had the same experience before and it turns out that I have to implement my own _initialize function when I build a wasm module as a reactor. This insight is specific to the Rust compiler of the year older version than the current latest so I'm not sure if that's still a case, but at least your tinygo compiler doesn't seem to support generating appropriate _initialize function from the generated wasm.
Please refer my blog post for the detail: https://engineering.linecorp.com/en/blog/adding-experimental-webassembly-support-to-decaton-part-1/#AddingexperimentalWebAssemblysupporttoDecatonPart1-ImplementaDecatonprocessorwithWasm/WASI

So I did some digging and it actually seems that TinyGo correctly pre-opening the files however it only does this in the command _start method.
However, as a workaround, if I rename the export _intialize then wasmtime correctly calls this method before running my module functions and this sets up all the directories.
sed -i 's/(export "_start" (func \$$_start/(export "_initialize" (func \$$_start/g' ../go.wat

I will report these things back to the TinyGo team. Next up are memory issues.


Postman regression test - initial

In this initial version of the regression test the following endpoint/extensions will be included:

[x] wallet
[x] usermanager
[x] LNURLp
[x] LNURLw

Action/config included to run daily at https://lnbits.com

Codecov Report

Merging #270 (01aa0fe) into master (3331dfe) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #270   +/-   ##
=======================================
  Coverage   30.21%   30.21%
=======================================
  Files          31       31
  Lines        2317     2317
=======================================
  Hits          700      700
  Misses       1617     1617

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 3331dfe...01aa0fe. Read the comment docs.

@arcbtc this is the first running version of the postman test. I'm planning to add LNURLw short term, that's why this one is ready for review yet.

Added LNURLw, first version ready for use.
@arcbtc

Please let me know if you have any question.
I think the environment.json should contain secrets so the testdata can't be messed up by users.
Any suggestions on what to add next based on usage of extension?

Test covers now:

wallet
usermanager
LNURLp
LNURLw
Paywall
Captcha

Added a webhook check.

@arcbtc , I think the test is stable now. Running against my own instance for 14 days with no problems.
Did you already look into it?

@cryptoteun hey, it's been a while since the last messages. Is this PR still relevant? I'm cleaning up a bit.

@callebtc , it was created before the move to fastapi. Currently don't have time to check if it's still completely working. Is there still a need for such a test, which could run during build/deploy?

@cryptoteun see #566 for the new test pipeline with FastApi! :)


updates

merge updates

@go-keiryo - thank you for this fork - do you consider making a binary release? Seems @michaelvillar has abandoned the app.


New version: SimulatedNeuralMoments v1.0.0

Registering package: SimulatedNeuralMoments
Repository: https://github.com/mcreel/SimulatedNeuralMoments.jl
Created by: @mcreel
Version: v1.0.0
Commit: e9327eca6d7212f341dbe79e967b5082003f7680
Git reference: v1.0.0
Description: package for Bayesian and classical estimation and inference based on statistics that are filtered through a trained neural net
Release notes:

examples use Turing for sampling

I believe that the issues have been fixed. The package does not depend on Distributions now. This PR seems to be stuck.

@giordano Thanks. I have made a PR for version 1.0.1 now, so this PR can be closed. I would do it, but I don't think that I can.

That's not going to work...


PyPI and Anaconda

Start slowly preparing to do this.

Now that #178 is merged, I will focus on this.

Hi, @flying-sheep,
I'm struggling to put CellRank on testpypi, the main culprit being here: https://github.com/theislab/cellrank/blob/master/setup.py#L42
The problem is this: HTTPError: 400 Client Error: Invalid value for requires_dist. Error: Can't have direct dependency: 'msmtools @ git+git://github.com/msmdev/msmtools@krylov_schur#egg=msmtools' for url: https://test.pypi.org/legacy/
This problem occures when I build bdist_wheel. If I only build sdist, it gets uploaded.
However, after running pip install -i https://test.pypi.org/simple/ cellrank==1.2.3.dev2,
I get the following error and I don't know how to fix it:
Installing build dependencies ... error
  ERROR: Command errored out with exit status 1:
   command: /home/michal/.miniconda3/envs/cellrank/bin/python /home/michal/.miniconda3/envs/cellrank/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-ant09w4q/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://test.pypi.org/simple/ -- setuptools setuptools_scm wheel
       cwd: None
  Complete output (3 lines):
  Looking in indexes: https://test.pypi.org/simple/
  ERROR: Could not find a version that satisfies the requirement setuptools (from versions: none)
  ERROR: No matching distribution found for setuptools
  ----------------------------------------
ERROR: Command errored out with exit status 1: /home/michal/.miniconda3/envs/cellrank/bin/python /home/michal/.miniconda3/envs/cellrank/lib/python3.8/site-packages/pip install --ignore-installed --no-user --prefix /tmp/pip-build-env-ant09w4q/overlay --no-warn-script-location --no-binary :none: --only-binary :none: -i https://test.pypi.org/simple/ -- setuptools setuptools_scm wheel Check the logs for full command output.

Here's the full log.
Based on this, I'm not sure if it's even possible to specify dependency that way.
As far as I know, dependency_links could've worked (haven't tried them, they were deprecated).
Other thing I tried is using cmdclass in setup.py, calling pip install <the package>, similar to this, but it always fails with not being able to find pip:
Traceback (most recent call last):
      File "/home/michal/.miniconda3/envs/cellrank/bin/pip", line 7, in <module>
        from pip._internal.cli.main import main
    ModuleNotFoundError: No module named 'pip'

Any help on this would be greatly appreciated!

In the meantime, I would vote for putting it on pypi without the msmtools dependency, include msmtools it in the installation instructions and initiate a merge of the krylov-schur branch into upstream msmtools.

We could even let functions/methods default to CFLARE if no msmtools is found and print a message, urging the user to install msmtools...

@flying-sheep, can you help us with this?

The reason one can’t have URLs as dependencies is explained in pypa/pip#6301.
One option to solve this is to vendorize it, i.e. bundle the dependency with your package. This tool could help, I think it’s able to resolve and install from an URL since it uses pip.
The way it works is that you use the CLI command python-vendorize to install the package to a local (git-ignored) directory, and include that directory when building a package for PyPI.
I suggest you use an URL with a commit hash instead of the branch name in the URL. This way when building a package, you always get the same version and not whatever is the newest one at build time.

@flying-sheep  Thanks a lot!
That's what I was afraid of - bundling stuff together, but if it's the only solution, then so be it. There were some issues with docs + tests, but  https://github.com/theislab/cellrank/pull/225 should make it work.

Done via #225 and later commit. Will create separate issue for Anaconda.

Amazing, thanks so much.


Fix error handling to prevent application crashes in async functions

Description
This pull request addresses the issue where unhandled errors in middleware could cause the server to crash. The current behavior terminates the server without handling the error, leading to an incomplete response to the client.
Proposed Solution
To handle unhandled errors in middleware, I have made changes to the lib/router/layer.js file. Specifically, I modified lines 95-101 to include an error handling block. This ensures that errors occurring within middleware are caught and can be handled appropriately.
Code Changes
Here is an example of the modified code:
app.use((error, req, res, next) => {
  // Handle the error appropriately, e.g., log the error, send an error response, etc.
  // ...
})

Thank you for this. You can change the behavior of unhandled promise rejections uaing Node.js flags, of course. You can find this already landed in Express 5, so closing since it has already landed, in a more complete implementation than what is in this pull request 👍
If you are using Express 4, you need to use only plain functions unless you are using a third party module to add in async func support.


Fix README to correct API usage

Description
Fix README to correct API usage.

mistake choose public/private key.
correct usage for verify method.

Motivation and Context
Fixing readme.
How Has This Been Tested?
Only changed document.
Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Oh no, I have not printer. Why missing online sign up form like Google.

 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.

Thanks CLAassistant suggestion, online CLA agreement process with github auth is nice than print out pdf and scan that is linked from PULL_REQUEST_TEMPLATE.md.
@Andrew-Lees11 I just signed to CLA.


tinymce validation broken

as of 1.9.0 (at least in ff and chrome)
http://jquery.bassistance.de/validate/demo/tinymce/

just notice ignore settings when you init your validate form. try to set ignore:"" on your config


[Bug] Lazy load plugin

Is there an existing issue for this?

[X] I have searched the existing issues

Have you updated FilePond and its plugins?

[X] I have updated FilePond and its plugins

Describe the bug
I try to load FilePond including some plugins by using dynamic lazyload.
While trying to register the plugin(s) I got:
Uncaught (in promise) TypeError: plugin is not a function
Error caused by this line: https://codesandbox.io/s/filepond-lazy-load-example-josspz?file=/src/components/file-upload.js:959-992
Not really sure if it's a problem with the plugin or if I overlooked something.
Reproduction
Go to https://codesandbox.io/s/filepond-lazy-load-example-josspz
The important part is inside of https://codesandbox.io/s/filepond-lazy-load-example-josspz?file=/src/components/file-upload.js
Environment
- Device: -
- OS: MacOS
- Browser: Chrome 101

This is an implementation problem, please post it as a question on Stack Overflow.


Rename 'Fds' to 'File Descriptors' in docker info

This makes the docker info more readable. Also change a log line
in a test file renaming Fds
Signed-off-by: Ankush Agarwal<EMAIL_ADDRESS>

LGTM

LGTM, thanks!

@tiborvass  is this one really ok to do given people may be parsing it (its a UX change instead of a bug)?

@duglin good point... I'm not sure... @crosbymichael what do you think?

Can we provide a inspect like output for info when an additional option is passed like docker -j info

@ankushagarwal I'm not sure I understand what docker -j info means.
The /info API didn't change, it's only the displaying that changed which could be parsed by shell scripts. I don't know, I sorta think it's okay.

I think a note should be added in the release notes, for those that do parse the output.
On the other hand; is the CLI output considered a stable API? If not, the docs should include a general note that states that CLI output is not a stable API and cannot be relied on for parsing. A section with examples on how to use the remote API in shell-scripts could be nice there (may be a nice Bday Party task as well)

Since Docker doesn't make a clear distinction between machine-readable output and human-readable output, we kind of have to assume any of it can, and will, be machine parsed.  So to me, unless we consider this a bug, I don't think we should be changing the output on people in a dot-release.
@crosbymichael - need your thoughts on this.

@tiborvass : I am sorry if I wasn't clear. I was proposing adding a -j (j for json) option to the info command. The -j option produces a machine readable output which can be parsed, but I guess they can talk to the server at /info to get a machine readable output. Or a general -j (or some other appropriate letter) option across the docker cli commands which just spits out the server's response as is.
@duglin : The motivation for this change was that Fds was very unclear in a human readable output and it was documented nowhere in the code that Fds means File Descriptors.
People shouldn't be relying on docker client's human readable output, they should be talking to the server at /info directly. But, I do agree that this can potentially break things.

People should use the API /info if they want machine readable, and guarantee on output format.


Please allow passing options to Dir::open()

Sometimes options like O_DIRECT are required. Current API doesn't support that.
See also: https://github.com/tailhook/openat/issues/1

I am thinking about some builder pattern here, maybe I can do a 'proof of concept' soon (I'll need control over O_CLOEXEC) as well:
Example:
// Creates a 'Flags' builder
let dir = Dir::new()                            // (defaults only to O_CLOEXEC)
             .with(libc::O_SEARCH)
             .without(libc::O_CLOEXEC)
             .open("somedir");                // Calls back to Dir::open

let subdir =
    dir.without(libc::O_CLOEXEC)  // Flags builder references a Option<Dir> as well
    .subdir("inner");                          // Call back to the Dir

let file = subdir.with(libc::O_DIRECT).open_file("test.txt");
// open_file (and other method) will add the required flags, but leave the rest untouched

Flags are passed as raw libc::c_int and not abstracted in rust and no validated.

To allow OS specific flags the implementation doesn't know about
Invalid Flags will eventually result in runtime / io errors


refactor: remove unused (array) cast on array

Description
when already array, no need to cast.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[ ] Conforms to style guide

Ready to merge 👍

Thank you @paulbalandan for the review, let's merge ;)


ENH: Improve typing for pivot and pivot_table

[ ] Tests added: Please use assert_type() to assert the type of any return value

@twoertwein any ideas about the pyright failure?

@twoertwein any ideas about the pyright failure?

Sory for the late reply, I assume you fixed the error as pyright seems to pass now (but a pytest error).

@Dr-Irv it is green now.


User dropdown not working

Adding $('.dropdown-toggle').dropdown(); to the page (ie in resources/views/vendor/adminlte/_layout/js.blade.php) fixed it. Is there a better way to do it ?

Not yet.
I'm currently working on it.

@gionnivaleriana , did you make any progress yet, or shall I apply the change as suggested by @rigelk ?

I found a js error from the firebug console. It looks like the jQuery version conflict.

SleepingOwl Admin already included some libs, I try to remove these lines:
<script src="{{ URL::asset('packages/almasaeed2010/adminlte/plugins/jQuery/jQuery-2.1.3.min.js') }}"></script>
<script src="{{ URL::asset('packages/almasaeed2010/adminlte/bootstrap/js/bootstrap.min.js') }}" type="text/javascript"></script>
<script src="{{ URL::asset('packages/almasaeed2010/adminlte/plugins/morris/morris.min.js') }}" type="text/javascript"></script>

It works fine for me.

I created a pull request for these changes.


Patreon: Error 403

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
No response
Provide a description that is worded well enough to be understood
Getting error 403 while downloading patreon content
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[download] Downloading item 171 of 172
[Patreon] Extracting URL: https://www.patreon.com/posts/yoga-and-art-70837877
[Patreon] 70837877: Downloading API JSON
[generic] Extracting URL: https://zhouyiqin.vids.io/videos/709edab51f16ebc1f9/yoga-and-stretching-art-afternoon-meditation
[generic] yoga-and-stretching-art-afternoon-meditation: Downloading webpage
ERROR: [generic] Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 718, in extract
  File "yt_dlp\extractor\generic.py", line 2392, in _real_extract
  File "yt_dlp\extractor\common.py", line 863, in _request_webpage

  File "yt_dlp\YoutubeDL.py", line 4082, in urlopen
  File "yt_dlp\networking\common.py", line 114, in send
  File "yt_dlp\networking\_helper.py", line 204, in wrapper
  File "yt_dlp\networking\common.py", line 325, in send
  File "yt_dlp\networking\_requests.py", line 343, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden

Looks like a sproutvideo embed. Related: #2933
But the URL requires cookies or some other form of auth.
There's likely no way anyone will be able to fix this unless you are willing to share your account


MFA registration screen + skip registration

User story
As a CMS user without a registered MFA method, I want to be presented with a registration screen to set
up a MFA method up after I've logged in, so that I can add extra security to my CMS account.
Designs: https://projects.invisionapp.com/share/3PNSKZQYBJZ#/screens/321189816
ACs

[ ] This is the first page of the React app, displayed after a successful CMS login
[ ] This screen is only displayed to users without a registered MFA method
[ ] If MFA is mandatory, and the grace period hasn't ended, this registration screen is shown each time a user logs in
[ ] If MFA is non-mandatory, and the user has previously skipped registration, do not show this screen again
[ ] Functionality exists to 'set up later' as per notes below
[ ] Text in designs is static
[ ] Create default styling within the app, using generic class names that could be overwritten by a site developer

Skip functionality follows:
https://github.com/silverstripe/silverstripe-mfa/issues/14:

[ ] Skip function is available if global grace period is enabled and it has not ended
[ ] Skip function is available if MFA is not mandatory
[ ] Skip function is hidden if MFA is mandatory and global grace period has ended

If MFA is non-mandatory, the registration screen will be shown intermittently to remind CMS users it is available

This might need further discussion. It would be good practise to remind users that MFA registration is enabled for them, but we may need to implement something to stop this screen from appearing permanently if the user doesn't want it.

Graphics are exportable from the Invision flows

In grooming we discussed how this would work for site users who have an account, but don't have access to the CMS. For these users, if they skip, they wouldn't have the ability to setup MFA later as they don't use the CMS.
The MFA 'app' is permanlinked so the route could be built into the frontend by a developer, so it could be accessed again.

https://github.com/silverstripe/silverstripe-mfa/pull/63


Android Build

blocked by https://github.com/filip26/titanium-json-ld/issues/166

blocked by https://github.com/setl/rdf-urdna/issues/4

RDF-URDNA is bundled with jre8 build, see src/java8


Add support for React 15

Also made some changes to the npm scripts to support cross-platform development on windows.

👍

Thanks!


Add e2e test for automatic sidecar injection

Reviving https://github.com/istio/istio/pull/4926.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ostromart
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
bc73cc68eb3c898c9d09e16cf24738e097139146
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ostromart: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ostromart: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ostromart: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-simpleTests.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test e2e-simple

prow/istio-pilot-e2e.sh
f056861de55f9114f0a4089879e74e5ac41b15e1
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Email from Rockstuhl

Dear Prof. Barba,
I have seen your paper in arxiv yesterday ("Reproducible Validation and Replication Studies in Nanoscale Physics”) and wanted to approach you shortly to stress that the work is very interesting and important. The ability to reproduce data is of utmost importance and I admit that 15 years ago, we have not been so careful in making computational code available so that others can reproduce results that we have published. I would like to assure you that nowadays we store all the codes that were used to produce figures. That is even requested by most funding agencies.
I would have just one scientific comment on your paper. I understand, and you clearly discuss this, that your 3D quasi-static simulations are not exactly comparable to our 2D Maxwell simulations. However, you should also take care with a statement like “We computed extinction cross-section (scattering plus absorption) while Rockstuhl et al. present only scattering cross-section. But, since the quantity of interest is the wavelength at which the resonance modes occur, the results can be compared.” If you associate the peak in the extinction or scattering cross section as the wavelength were the ‘resonance' occurs, you would even conclude in much more simpler scenarios on different wavelengths.
In dipole approximation, where we may describe the response of a particle by some polarizability \alpha, the scattering cross section is calculated by k^4/(6π)|\alpha|^2 while absorption cross section is calculated by kIm(\alpha). So the “resonance" should be defined by \alpha where it is driven into some singularity (finite absorption prevents this). However, this is not the wavelength where scattering peaks nor the wavelength where absorption peaks. The multiplication with the wavenumber distorts the functions and indeed modifies their peak positions. The effect is more pronounced the broader the resonance is. Because than k^4 or k changes quite drastically across the resonance.
Extinction cross section, as you look at, is the sum of scattering and absorption, so the scaling is even more complicated, but for small particles absorption dominates (absorption is linear in polarizability that is in turn proportional to the volume of the particle while scattering cross section is quadratic in polarizability, so for a small volume the quantity just gets even further smaller), so it makes sense to equate rather absorption and extinction cross section for small particles. Then, obviously, not just that the resonance you see in your spectra happens at different wavelength, you will also identify a different 'resonance wavelength’ for scattering and absorption because of the different scaling factor.
That should be somehow reflected in your work.
I hope this helps you. I am attaching you also some more literature for you to read.
Kind regards
Carsten

Response to Rockstuhl:
Dear Prof. Rockstuhl,
Thank you for writing, and for your interest in our work! I was glad to receive your email, and wanted to reply right away, but it caught me in a shock wave of delayed tasks that required my full attention.
My student Natalia and I also took time to discuss your comments, to reply thoughtfully. Even though we were aware that absorption dominates, as you mentioned, we did not recognize this as possible source for the extra peaks we obtained in our result. Adding some new language about this in the paper is a good idea. We were just happy that the main peaks in our results matched yours (Fig. 5 in our preprint) and declared that a replication victory!
Since you brought up the concern about comparing extinction with scattering, we looked into it. Using the analytical expression for a sphere (Sca = k^4/(6π)|\alpha|^2 and Abs=kIm(\alpha)), we made the calculations for a SiC sphere of radius 2,000 Angstroms, in a wavelength range of 10 to 12 microns, and the peaks for scattering and absorption occur at the same wavelength. But we’re confused: are you saying that this should not be called “resonance” peaks?
We also found some papers where the spectra for scattering and absorption look fairly similar despite the magnitude of the peaks:  for a 40 nm silver cube (https://pubs.acs.org/doi/abs/10.1021/jp0608628), and also for gold nanorods (https://pubs.acs.org/doi/pdf/10.1021/jp057170o). So it sounds like we should be able to compare extinction with scattering for this case, but we do need a better discussion about this in the manuscript.
The paper from Okamoto that you suggested shows that when including retardation effects (not included in our results), there is a difference between where peaks happen in the absorption and scattering spectra. However, for the smaller particles (quasistatic limit) the difference in the wavelength at which the peaks happen, is minimal. In this limit, our results replicate well the wavelength of the peaks on Figures 14 a and b of your paper (our Figure 5), but we still have an extra one that can be attributed to the dominance of absorption in our spectrum, and we need to addressed it, as you suggested.
Thank you ever so much for writing. I have always been a big fan of preprints, and receiving your email emphasized for me the benefits, once again!
Kind regards,
Lorena.

At the end of Rockstuhl section we should discuss the topic of the email. The section finishes
"The  replication  results  are  presented  in  Figure  5:  the  main  resonance peaks presented in Rockstuhl et al. are closely matched. While we still have the presence of a third peak in our results, we conjecture that this is a consequence of the 3D effects in our geometry"
It is worth mentioning that another cause of discrepancy between Rockstuhl and our spectra can be attributed to the fact that me measure extinction, which is absorption + scattering, but in the long wavelength limit it is mainly dominated by absorption. Even though we have found literature (cite cube and nanorods papers) which shows that scattering and absorption spectra are very similar, except on the intensity, we can not ensure that they are identical. Therefore in the extinction spectrum the absorption differences will be accentuated. This can also be an explanation for the difference between our results (extinction) and Rockstuhl ones (scattering).
Note should we add a note saying that in the plots Rockstuhl results are scattering? I think it's not fully clear on the plots. I don't want to change the plots since the repropacks are already online.

Addressing sentence quoted by Rockstuhl in the email: 02ea83b

Clarify caption: 3c1f673

Add to acknowledgements: b3163ee

Last response after we modify the script.
Our email
Dear Prof. Rockstuhl,
We received our review reports on this manuscript, requesting minor revisions. As we worked on this, we also introduced a few changes in response to your comments—thank you again!
Our practice lately has been to work through responses to referees using GitHub issues on the repository used for writing the manuscript. If you’re interested, here  is that for this manuscript:
https://github.com/barbagroup/pygbe_validation_paper/issues
The issues also link to the specific changes we made in the paper.
I saw from your automated out-of-office reply a few days ago that you are currently away, but expect to be back next week.
We’re ready to send back our revision, but will give it a few days, and perhaps you’ll have a chance to look at the minor modifications we made.
Thank you again for getting in touch and for your feedback on the manuscript.
Kind regards,
Lorena.
Response
Dear Lorena,
indeed, I just came back from vacation that is a precious time to me in which I prefer not reading emails.
Thank you first of all for your original answer. Again, I think (just as the referees) that you did a very nice job in writing this paper. Also, the way you have reacted on my comments is just fine.
I would just like to add that possibly you go somewhat too far with this statement that the appearance of an additional resonance (2 in my paper vs. 3 in your paper) could also be an issue because you consider a 3D case whereas I have considered a 2D case.
“While we still have the presence of a third peak in our results, we conjecture
-that this is a consequence of the 3D effects in our geometry.
+that this is a consequence of the 3D effects in our geometry,
+as well as the fact that we compute extinction cross-section, while Rockstuhl et al.\ report scattering.”
Again, under the assumption of the validity of the quasi-static approximation, the response of the particle to an external em-field manifests in some (electric dipolar) polarization. The response to the excitation is mediated by the (electric dipolar) polarizability. I wish (in reaction to comments in your first email) to stress that (to my understanding) this polarizability is the primary quantity that can be driven into resonance and the “resonance wavelengths” of a particle should refer to the wavelengths where this quantity diverges in magnitude. Now if you look into scattering or absorption as the observable quantities, the peak wavelength of the respective quantity shows a tiny but non-zero difference relative to the peak wavelength of the polarizability. That is because these observable quantities are multiplied by functions that depend on wavelength/frequency. The difference in the peak wavelength is stronger the broader the resonance is. Check the impact out for yourself while plotting (depending on some frequency) a Gaussian and a Gaussian multiplied with the frequency and a Gaussian multiplied with a frequency in the fourth power. The emerging peak in these quantities will happen at different frequencies especially for broader Gaussians (relative to the central frequency).
In your case this should have a very minor impact because the resonances are quite narrow and super sharp. Indeed, SiC is simply an excellent material for this purpose of exciting scattering resonances.
So considering scattering vs. absorption in your case should only cause a small shift in the resonance wavelengths (that you, nevertheless, compare up to a certain precision in digits and that’s why it is worth to mention) but it will not be responsible to cause the appearance of a new resonance. That’s why I would not change the manuscript at the place mentioned above.
I would also think that the appearance of a further resonance is due to the fact that you consider a 3D geometry.
My best wishes
Carsten

After reading the response I believe we misunderstood the original email. I remove the sentence that stated that the discrepancies might also be due to the "differences between scattering and absorption". This, as pointed out by Rockstuhl, in our case  is not a difference that would be noticeable . We (and Rockstuhl too) believe that the main differences are due to our 3D model vs their 2D model.
Modifications in commit 53cf28c

Possible paragraph to replace the changes on 02ea83b after reviewing latest email with Rockstuhl.

Nevertheless, when the resonances are sharp and narrow, the main peaks for scattering and absorption do occur at nearly
the same frequency. For example, Wiley et al.\ show simulation results for a silver nanocube where the main peaks in the
spectra are aligned \cite{wiley-etal-2006}. Since silicon carbide has more pronounced resonances than silver, the wavelength at which the peaks occur in the extinction and scattering spectra, are comparable.

Revised version:

We can measure scattering cross-section, absorption, extinction cross-section (scattering plus absorption), as well as reflection. Since the \textit{quantity of interest} is the wavelength (frequency) at which the resonance modes happens, these different approaches are comparable in some cases, e.g., whether we measure reflection or extinction cross-section, the wavelength (frequency) at which the peaks happen remains the same.


Classification references does not work without distributed setup

If you don't set the respective env vars
https://github.com/pytorch/vision/blob/d5bd8b728f14c33b339fc45c90ca39be339bce3f/references/classification/utils.py#L255-L258
training will not be distributed and in turn the backend will not be initialized. However, during evaluation we check
https://github.com/pytorch/vision/blob/d5bd8b728f14c33b339fc45c90ca39be339bce3f/references/classification/train.py#L88
unguarded, which then fails with
RuntimeError: Default process group has not been initialized, please make sure to call init_process_group.

cc @datumbox

Same for segmentation:
https://github.com/pytorch/vision/blob/cac4e228c9ca9e7564cb34406e7ebccfdd736976/references/segmentation/train.py#L84

I think this case is implicitly guarded on
https://github.com/pytorch/vision/blob/d5bd8b728f14c33b339fc45c90ca39be339bce3f/references/classification/train.py#L87
since len(data_loader.dataset) != num_processed_samples shouldn't be true on non-distributed setting.
Do you get the error during non-distributed training @pmeier ?


[Broken Link] GraphQL Fake seems to be broken

The site is returning 502 status code.

@francisbrito You right, thanks for reporting it.
I will wait a couple of days to see maybe it's only temporary and remove it.

Alright
On Sun, Mar 25, 2018, 2:26 PM Ivan Goncharov<EMAIL_ADDRESS>wrote:

@francisbrito https://github.com/francisbrito You right, thanks for
reporting it.
I will wait a couple of days to see maybe it's only temporary and remove
it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/APIs-guru/graphql-apis/issues/20#issuecomment-375992044,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACFG1mdaD6D2lvAP3weudxj3tJZk9RCpks5th-FQgaJpZM4S6LhI
.

Still down.

@millette Thanks for the ping 👍
Deleted ❌


Invoke-downloadchocopkg require PowershellGet v3.0.0

PowershellGet 3.0.0 is still beta and cannot be installed
Install-Module PowerShellGet -Force -AllowPrerelease
Install-Module : A parameter cannot be found that matches parameter name 'AllowPrerelease'.
At line:1 char:37

@hb9chm does the Invoke-DownloadChocopPkg require PowerShellGet 3.0.0, or would it be ok to reduce the required version?

PowerShellGet Version 3.0 Preview 12 or higher is needed, because of  the feature "Save-PSResource -AsNupkg"
(see https://devblogs.microsoft.com/powershell/powershellget-3-0-preview-12-release/)

AllowPrerelase is not supported on the "preinstalled" powershellget module version <IP_ADDRESS>
First upgrade to the lastest offical version (2.2.5)
install-module powershellget -force
(for upgrading from the <IP_ADDRESS> Version to 2.2.5)
Restart Powershell
Powershellget 2.2.5 supports the allowprerelease parameter
install-module powershellget -allowprerelease -force

Ah, right, that is why there was the prerelease error.
@sylvainlavoie You can either use the provided method to install the v3.0.0 beta of Powershellget, or alternatively if you are not intending to use the Invoke-DownloadChocoPkg command, then you should be able to locally change the required version to allow you to use the other parts without having to upgrade Powershellget.

I've refactored Invoke-DownloadChocoPkg to no longer require PowerShellGet