Kubelet: record the timestamp correctly in the runtime cache

Currently, the timstamp is recorded after getting the pods from the container
runtime. This could lead to pod workers seeing stale pods which were retrieved
before their last sync finished. This change fixes that.

/cc @bprashanth

Since there are multiple pod workers updating the cache simultaneously, you also need to ensure that the timestamps always move forward to prove that each pod worker sees the effects of its previous update (which is really what's needed).
Also it would be great to get a ut or something, though I realize runtime_cache doesn't have any so upto you.

Please add a test that illustrates the failure you're correcting-- otherwise it will probably break again in the future, as this change is not obvious to the casual reader (me).

/subscribe
/ref #7561

Also it would be great to get a ut or something, though I realize runtime_cache doesn't have any so upto you.

@bprashanth, what do you mean by getting a "ut"?

A unittests, preferably one that fails without your fix (so straddles pod_worker and runtime_cache)

Since there are multiple pod workers updating the cache simultaneously, you also need to ensure that the timestamps always move forward to prove that each pod worker sees the effects of its previous update (which is really what's needed).

I agree that the timestamp should always move forward. In fact, pod workers won't have this problem because they call ForceUpdateIfOlder, which acquires the lock before calling docker. The calls are serialized by the lock and the timestamp always moves forward. It's different for the updating thread though since it grabs the lock after getting the pods from docker (which I assume is a performance optimization).
I updated the PR with the timestamp checking, along with some unit tests.

In fact, pod workers won't have this problem because they call ForceUpdateIfOlder, which acquires the lock before calling docker. The calls are serialized by the lock and the timestamp always moves forward.

you can still have ForceUpdateIfOlder set the cache and timestamp in pod worker1, and before pod worker1 does a GetPods the timestamp and cache get clobbered with an older cache from pod worker 2 if you don't check timestamps.

you can still have ForceUpdateIfOlder set the cache and timestamp in pod worker1, and before pod worker1 does a GetPods the timestamp and cache get clobbered with an older cache from pod worker 2 if you don't check timestamps.

I don't think that'd happen given that pod worker2 will update the pods AFTER pod worker1, so the cache would only have newer pods than pod worker1 expected. Newer pods are okay though.

I suppose you're safe with just handling the background thread case, which could potentially get invoked from any pod worker. The podworkers themselves should be safe as long as they update both timestamp and pods with the lock as you mentioned.

LGTM


Fixed #221. The problem with complex sqrt

:shipit:

Yes, I first thought using the same formulation which is a bit more robust.
Reference "How to Find the Square Root of a Complex Number" by Stanley Rabinowitz 1993.
However, this implementation still suffers from potential floating point overflow/underflow.
This is why I suggest something even more robust (and more accurate) like:
Implementing Complex Elementary Function Using Exception Handling
ACM Transactions on Mathematical Software - October 1994
Ping Tang and 3 other authors
See https://source.squeak.org/trunk/Kernel-nice.1459.diff

Oh, this is cool!
Thanks @nicolas-cellier-aka-nice
I like the idea of scaling

I will merge this PR for now and open a new issue for a more robust sqrt implementation

I will merge this PR for now and open a new issue for a more robust sqrt implementation

Issue #257


set fileHandleLimit to 1024

Can you provide a testcase?

@RSulzmann can you shove the DockerOpenFileLimitTest.scala to open? also it needs to increase its limit.

Here is an action code (nodejs) to check the file handle limit boundary:
var fs = require('fs');

function main(params) {
	console.log (process.versions)

    return new Promise((resolve, reject) => {

        fs.writeFile("DATA", "LOTS OF FILES!!!!", function(err) {
        	console.log ("write")

            if (err) {
            	console.log ("reject write")
                reject(err);
            }

            var latch = params.N;

            function read(iter) {
                fs.readFile("DATA", "utf8", function(err, contents) {
                    if (err) {
                    	console.log ("reject read " + iter + " " + err)
                        reject(err);
                    } else if (--latch === 0) {
                    	console.log ("resolve")
                        resolve({N: params.N});
                    }
                });
            }

            for (let i = 0; i < params.N; i++) {
                console.log ("read "+i)
                read(i);
            }
        });
    });
}

create an action with the code above copied to a file:
wsk action create actionName actionFileName
invoke with the parameter N 1024:
wsk action invoke actionName -p N 1024
check log output:
wsk activation logs activationID

turn that into a test? (didn't we have one already?)

Yes, we have one, that we will move to openwhisk.

@RSulzmann @markusthoemmes is this ready? is there a pg?

PG1/1110.

@markusthoemmes I pg'ed this PG1/1110.

I rebased this pr in my branch and ran new PG which failed. PG1/1124 for reference.

Rebased with companion, pg2/1010 running.

Made the fixes suggested here in new PR.


Similiar "Zero Stars" challenge on /recycle

Within http://localhost:3000/#/recycle, you are able to bypass the disabled button, submitting large chunks of text, or nothing at all, beating the limits of the form. I didn't see this within the score board, maybe it's minor... thanks!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I think I'd rather fix this by enforcing the same limits on the database-side as on the client, because "Recycling" will be part of a new CAPTCHA bypass challenge soon. Another client-side validation bypass challenge would be a bit too similar to existing ones.


send value to editor from JS

Can't add text to editor.
$('#editor').val('Some text');

But this does not work.

This does not work using an asp textbox:
$("#text_area").wysihtml5();
var editorObj = $("#text_area").data('wysihtml5');
var editor = editorObj.editor;
editor.setValue(html_goes_here);
It says that the editor is undefined. I have linked the bootstrap3-wysihtml5.all.min, jquery, and bootstrap.js.min.

Thank you @abishekrsrikaanth you saved my day! Is there any documentation about the methods available on that editor object?

Basically it is a version of this one: http://wysihtml.com/

Thanks @abishekrsrikaanth ! you saved my day as well. works like a charm.

Why @abishekrsrikaanth  answer is not on readme?

$('iframe').contents().find('.wysihtml5-editor').html('your new content  here');


docker network ls  ,then can not find net?

after install netplugin  then docker network ls  I  am not find the work?

but run docker network ls, exists some question

could you please provide more details ?
netctl --version
which orchestration you are using ? (swarm / k8s etc)

@gaurav-dalvi
wo have no use  (swarm / k8s etc), my machine only  install docker engine and ovs
env:
I have one machine named centos7.2, I have go env, then git clone https://github.com/contiv/netplugin.git,

cd   ./netplugin/ ./netmaster/ ./netctl/netctl/ ./mgmtfn/k8splugin/contivk8s/
./mgmtfn/mesosplugin/netcontiv/
at these dir ,run go install ,
in GOPATH/bin can bring some binary
$ cp scripts/contrib/completion/bash/netctl /etc/bash_completion.d/netctl
then
$ nohup ./netplugin &
$ nohup ./netmaster &
$ netctl net create contiv-net --subnet=<IP_ADDRESS>/24
$ docker network ls

if can not find network,

wo look up netplugin  log,  find some error :

git checkout v0.1-12-23-2016.19-44-42.UTC
I first create network  always exist some error, the second time create network can success,

I know reason ，docker.service   add  --cluster-store=etcd://<IP_ADDRESS>:2379/
thank you!

@fiser321 : I am glad you were able to execute this.


Fix README.md badges

All badges point to catenax-ng GH repository. Please fix.

This is now fixed. Yesterday we updated the repo with the newest changes and fixes.

Badges are corrected now in READE.md.
Thank you very much.


Smartnoise Synth Installation Breaking with OpenDP 0.4.0

Hey I am loving smartsynth and had a great time playing with it on my OpenDP 0.3.0 build. However, it seems it is only compatible with opendp 0.3.0. When I upgrade to opendp 0.4.0 I run into issues with installation. I'm wondering, will this be updated to run with 0.4.0? It may break my project if not!
Any help is appreciated!

Hi Adam,
So glad that you're enjoying the tool!!
That's odd - would you mind sharing a stack trace/a bit more about your machine and environment? That'll help me figure out what's going on.
Thanks so much!

Ah, I see. We need to update our requirements. Thanks for pointing this out!

Ok, so we will do a new release that fixes the package issue. In the meantime, if you get a package dependency error that looks something like:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
smartnoise-synth 0.2.5 requires opendp<0.4.0,>=0.3.0, but you have opendp 0.4.0 which is incompatible.

You can feel free to ignore it! I just verified that all the snsynth tests pass with smartnoise-synth=0.2.5  and opendp=0.4.0, so it shouldn't effect performance to manually upgrade to opendp=0.4.0 despite pip's complaints.
Thanks again for pointing this out - if your use case is not working for any reason, feel free to drop it in here and I can try and help you figure out what's going on : )

Ahh thank you! I was a little late in getting back here.  I was originally getting the complaint when I was installing to Windows but I switched to an ubuntu kernel and it just reinstalled opendp to 0.3.0 as part of the pip install process. I'll try upgrading to the new release!

We have also updated this in the v0.2.6 release so it will automatically use 0.4.0


chore(main): release typescript-config 0.1.0

:robot: I have created a release beep boop
0.1.0 (2024-12-27)
Features

typescript-config: add initial typescript-config package (946c78c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

typescript-config-v0.1.0
:sunflower:


Consolidate action annotation constants

Currently, the defined action annotation names are not centrally defined.  Consolidate them as constants into a single location and change the existing code to use those constants.
Example annotations

web-export
final
raw-http
web-custom-options
require-whisk-auth

@mdeuser I would be interested in taking this up.
My task would be to move the actions in here, to another object class and reference them in the core and in tests. Is this correct?

Awesome @kiran002 - welcome to the community.

@kiran002 - thanks for picking this up :heart:  i defer to @rabbah, but in addition to what you have suggested, you may want to consider providing the list of these annotations via the openwhisk endpoint.  just like what is done with the set of system limits and runtime..

@mdeuser can you please point me to where the system limits and runtime endpoints are defined?

@kiran002 - i'm not sure exactly were that code is.  it's the output from the curl https://openwhiskhost  this might be a good starting place https://github.com/apache/incubator-openwhisk/blob/d22ef30fe613d60d84a5310a6b89cdbe2c495995/core/controller/src/main/scala/org/apache/openwhisk/core/controller/Controller.scala#L190

cool thanks will look into it! :)

@rabbah
Before i go all out and implement these changes, I wanted to get some feedback from you guys, So my idea is to have an annotations object
object Annotations {
  val FinalParamsAnnotationName = "final"
  val WebActionAnnotationName = "web-export"
  val WebCustomOptionsAnnotationName = "web-custom-options"
  val RawHttpAnnotationName = "raw-http"
  val RequireWhiskAuthAnnotation = "require-whisk-auth"
  val ProvideApiKeyAnnotationName = "provide-api-key"
}

and i intend to change all instances of
 annotations = Map(WhiskAction.provideApiKeyAnnotationName -> JsBoolean(true)))

to
 annotations = Map(Annotations.ProvideApiKeyAnnotationName -> JsBoolean(true)))

👍 sounds like a good plan to me.

Don’t think you need to toJson method - not sure what your intent is there.

toJson method was for  providing the list of these annotations via the openwhisk endpoint, do you think its necessary?

Interesting thought. That hadn't occurred to me. Do you know how clients might use this?


307 update jetstream inertia v1 to v2

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Please provide enough information so that others can review your pull request:

Explain the details for making this change. What existing problem does the pull request solve?

Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.

Closing issues
List all issues this PR resolves.

closes #XXXX

Pre-Merge checklist
Complete these items before requesting reviews

[ ] Static Analysis Rules Validated
[ ] All commits follow naming conventions

Sub-tasks Checklist

[ ] UI Implementation
[ ] UI Test
[ ] Backend Implementation
[ ] Backend Tests
[ ] Integration Tests
[ ] System Tests
[ ] Documentation

Closing this PR as this is not a priority for this release.

Closing this PR as this is not a priority for this release.


Ch/docker readme

@cedriking  @kouraf is there anything left to add ?

Hey @cedriking , I have made changes 😄 . Can you review now ?


Link to JavaDocs

Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 99.668%. Remained the same when pulling 745f9b34a95fdbd250c4eb3807ceb4bf6e669c9d on javadocs into dc051a2390a244c5457d177493b5373d15131e0c on main.


Some tiny edits to report.

Cleaned up crud in intro. Deleted extra colons in figure references. Added a bit to the data section.

Looks good, Did you guys notice that the abstract couldn't load the bib link? Probably fix that later.

Looks good jane


tighten up array handling, fix bug with array_slice output type inference

Description
This PR adjusts array handling in the direction of standardizing the representations on Object[] as well as long[], double[], and float[]. This is follow-up to https://github.com/apache/druid/pull/12498#discussion_r941829087 and a follow-up discussion I had with @gianm.
The main changes are removing the remaining leaks of typed object arrays such as Long[], Double[], and Float[] from the expression system, as well as adding support for handling arrays of java primitives such as long[], float[], and double[]. Expressions do not produce these primitive arrays, but aggregators and post-aggs can.
I've added javadocs to try to help provide additional details on native type matters.
I've adjusted the behavior of the expression column value selector when the virtual column output type is STRING to behave a bit more like a normal multi-value string column, and return the value directly when there is only a single value contained in the list. This does slightly change scan query results, which for multi-value string expressions would always produce array typed results, but now will produce a mix of array and scalar values. I think this behavior is more consistent with how the multi-value string columns themselves behave, but I can put it behind a flag if anyone is worried about this change.
I encountered a bug with array_slice output type inference, which was not indicating its output as array output, instead reporting the output type of its argument. This issue became clear due to the stronger separation between multi-value string handling and array handling that now occurs in the expression selectors.
Several redundant uses of NullHandling.emptyToNullIfNeeded have been removed from expression selectors, since it is baked into StringExprEval itself:
    private StringExprEval(@Nullable String value)
    {
      super(NullHandling.emptyToNullIfNeeded(value));
    }

In a follow-up PR, I'm going to try to see if I can remove the rest of the representation of ARRAY types as List, which is primarily the grouping engine. I decided to split it out from this PR to keep change set small.

This PR has:

[x] been self-reviewed.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] been tested in a test Druid cluster.

4 for Dereferenced variable may be null

Do these matter?


What ruby versions are available?

This page should display or link to a document that shows the available ruby versions.

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

ID: 02568f8b-6928-c8f1-178a-79e4cb0d93e2
Version Independent ID: 1107622c-4165-dcff-741a-279757b35323
Content: Use Ruby Version
Content Source: docs/pipelines/tasks/tool/use-ruby-version.md
Product: devops
GitHub Login: @erickson-doug
Microsoft Alias: dastahel

Thanks, @jmoody!  This should be live in the documentation later today.


Allow crash dump path to be configured

If PhantomJS fails, it places a crash dump in a hard-coded directory.
I use PhantomJS in a SaaS CI environment, where I don't have access to the /tmp directory. If PhantomJS crashes on CI, I would like to be able to retrieve the crash dump so I can see what went wrong.
Would it be possible to make the crash dump location a configuration option?

Not relevant anymore.

Could you provide a link what makes this irrelevant?

@timirwin we removed Breakpad in this commit https://github.com/ariya/phantomjs/commit/7a53778b276f0e1ca3671406ed87275d4d0e1e88
That means there are no more crash dumps. They were useless. Instead of that we ask users to provide a minimal test case to reproduce their problem.


Modeling the FDCE with timing for VPR

I tried to make a test for V2X timing import that incorporates a sequential logic, namely the FDCE.
Given the FDCE verilog model:
module fdce (DIN, CE, CLK, S, OUT);
 input  wire DIN;
 input  wire CE;
 input  wire CLK;
 (* SDF_ALIAS = "SR" *)
 input  wire S;
 (* SDF_ALIAS = "Q" *)
 output reg  OUT;

 always @(posedge CLK or posedge S)
  if      (S)   OUT <= 1'd0;
  else if (CE)  OUT <= DIN;

endmodule

I hand-wrote the model XML due to issue https://github.com/SymbiFlow/symbiflow-arch-defs/issues/784  with the V2X. And I generated the pb_type XML using my WIP version of the V2X which injects timings from SDF (https://github.com/SymbiFlow/symbiflow-arch-defs/pull/765). The XML files look like that:
<models xmlns:xi="http://www.w3.org/2001/XInclude">
  <model name="fdce">
    <input_ports>
      <port clock="CLK"  name="CE"/>
      <port is_clock="1" name="CLK"/>
      <port clock="CLK"  name="DIN"/>
      <port clock="CLK" combinational_sink_ports="OUT" name="S"/>
    </input_ports>
    <output_ports>
      <port clock="CLK" name="OUT"/>
    </output_ports>
  </model>
</models>

<?xml version='1.0' encoding='utf-8'?>
<pb_type xmlns:xi="http://www.w3.org/2001/XInclude" blif_model=".subckt fdce" name="fdce" num_pb="1">
  <input name="CE" num_pins="1"/>
  <clock name="CLK" num_pins="1"/>
  <input name="DIN" num_pins="1"/>
  <output name="OUT" num_pins="1"/>
  <input name="S" num_pins="1"/>
  <T_clock_to_Q clock="CLK" port="OUT" min="2.440e-10" max="3.030e-10"/>
  <T_hold clock="CLK" port="CE" value="-9.000e-12"/>
  <T_hold clock="CLK" port="DIN" value="2.250e-10"/>
  <T_setup clock="CLK" port="CE" value="1.090e-10"/>
  <T_setup clock="CLK" port="DIN" value="-4.600e-11"/>
  <delay_constant in_port="S" out_port="OUT" min="6.160e-10" max="7.640e-10"/>
  <T_setup clock="CLK" port="S" value="4.040e-10"/>
  <T_hold clock="CLK" port="S" value="-2.480e-10"/>
</pb_type>

And the VPR complains that it does not have a timing defined:
Error 1: /home/mkurc/Repos/google-symbiflow-arch-defs/build/utils/vlog/tests/timing_ff/fdce.arch.merged.xml:-1 <pb_type> 'fdce' timing-annotation/<model> mismatch on port 'S' of model 'fdce', port is a sequential input with internal combinational connects but has neither min nor max T_clock_to_Q specified
So after poking around I manually added timings which the VPR required and ended up with the following pb_type XML (the model remains unchanged)
<?xml version='1.0' encoding='utf-8'?>
<pb_type xmlns:xi="http://www.w3.org/2001/XInclude" blif_model=".subckt fdce" name="fdce" num_pb="1">
  <input name="CE" num_pins="1"/>
  <clock name="CLK" num_pins="1"/>
  <input name="DIN" num_pins="1"/>
  <output name="OUT" num_pins="1"/>
  <input name="S" num_pins="1"/>
  <T_clock_to_Q clock="CLK" port="OUT" min="2.440e-10" max="3.030e-10"/>
  <T_hold clock="CLK" port="CE" value="-9.000e-12"/>
  <T_hold clock="CLK" port="DIN" value="2.250e-10"/>
  <T_setup clock="CLK" port="CE" value="1.090e-10"/>
  <T_setup clock="CLK" port="DIN" value="-4.600e-11"/>
  <delay_constant in_port="S" out_port="OUT" min="6.160e-10" max="7.640e-10"/>
  <T_setup clock="CLK" port="S" value="4.040e-10"/>
  <T_hold clock="CLK" port="S" value="-2.480e-10"/>

  <T_clock_to_Q clock="CLK" port="S" max="3e-10"/>
  <T_setup clock="CLK" port="OUT" value="1e-11"/>
  <T_hold clock="CLK" port="OUT" value="1e-11"/>
</pb_type>

The VPR accepted such architecture definition.
My questions are:

Is the model XML correct ?
What those additional timings actually represent ?
The additional timings are not present in SDF so what values (or tags) should i place there ?

I believe http://docs.verilogtorouting.org/en/latest/tutorials/arch/timing_modeling/#mixed-sequential-combinational-block is the closest example.  And the error is pretty clear, you need a T_clk_to_Q from the SR pin to the output

I think:
      <port clock="CLK" combinational_sink_ports="OUT" name="S"/>

Should be:
      <port combinational_sink_ports="OUT" name="S"/>

And you still specific T_hold/T_setup to model the recovery/release constraints.

But the T_clk_to_Q tag should specify timing for a path from clock to output. I don't understand the meaning of timing specified like in the VPR example, it concerns clock and input:
<T_clock_to_Q max="200e-12" port="mem_sp.addr" clock="clk"/>

I did the <port combinational_sink_ports="OUT" name="S"/> change. And now the VPR complains that there are timings specified which consider CLK and S but the signal S is async according to the model (which makes sense).
The error refers to the line 58 in arch which is T_setup tag.
fdce.arch.merged.xml:58 <pb_type> timing-annotation/<model> mismatch on port 'S' of model 'fdce', model specifies no clock but timing annotation specifies 'CLK'

@litghost I did another test. I copied model and pb_type from the VPR documentation and changed only names to "fdce". And the VPR fails with error:
fdce.arch.merged.xml:53 <pb_type> timing-annotation/<model> mismatch on port 'addr' of model 'fdce', model specifies no clock but timing annotation specifies 'clk'

The model is:
<model name="fdce">
  <input_ports>
    <port combinational_sink_ports="out" name="we"/>
    <port combinational_sink_ports="out" name="addr"/>
    <port combinational_sink_ports="out" name="data"/>
    <port is_clock="1" name="clk"/>
  </input_ports>
  <output_ports>
    <port name="out"/>
  </output_ports>
</model>

And the pb_type is:
<pb_type blif_model=".subckt fdce" name="fdce" num_pb="1">
  <input name="addr" num_pins="9"/>
  <input name="data" num_pins="64"/>
  <input name="we" num_pins="1"/>
  <output name="out" num_pins="64"/>
  <clock name="clk" num_pins="1"/>
  <!-- External input register timing -->
  <T_setup clock="clk" port="mem_sp.addr" value="50e-12"/>
  <T_setup clock="clk" port="mem_sp.data" value="50e-12"/>
  <T_setup clock="clk" port="mem_sp.we" value="50e-12"/>
  <!-- Internal input register timing -->
  <T_clock_to_Q clock="clk" max="200e-12" port="mem_sp.addr"/>
  <T_clock_to_Q clock="clk" max="200e-12" port="mem_sp.data"/>
  <T_clock_to_Q clock="clk" max="200e-12" port="mem_sp.we"/>
  <!-- Internal combinational delay -->
  <delay_constant in_port="mem_sp.addr" max="800e-12" out_port="mem_sp.out"/>
  <delay_constant in_port="mem_sp.data" max="800e-12" out_port="mem_sp.out"/>
  <delay_constant in_port="mem_sp.we" max="800e-12" out_port="mem_sp.out"/>
</pb_type>

Maybe the rest of the architecture definition confuses the VPR...

At this point I'd assume the documentation is broken.
I recommend we open an issue with upstream VTR to:

Add a way for their documentation cases to be tested.  I believe in this case the documentation example is simply broken
Determine what the best way forward is

Async resets on FF's are no uncommon features, so I assume there must be a way to do this.

Probably it is broken. I'll prepare a more reproducible example and file the issue tomorrow.

@mkurc-ant / @litghost - We should update the VtR documentation to include all of async flip flop, sync flip flop and latch examples in their tutorial. As @litghost mentioned these types are relatively common things found in FPGAs.

@litghost @mithro I submitted an issue to the VtR: https://github.com/verilog-to-routing/vtr-verilog-to-routing/issues/617

@mkurc-ant With kmurry's answer please send a pull request to the VtR docs with info on how to model these flip flop types as examples.

@mithro But I am still confused how to model an async S/R flip-flop. From the kmurry's answer:

At the moment VPR assume any sequential port (i.e. with a clock="") is defining a FF, and has no direct combination connections, but may connect to internal timing paths (as shown here).

It seems that we need to completely decouple SR and CLK inputs. and then define delay_constant from SR to Q plus T_clock_to_Q for CLK to Q. I already tried that but it seems that the VPR does not support such timing configuration.
For now the only solution is to have a FF in with no timing spec on the async input.

I tried to decouple the CLR (or SR) input from Q and specify no timings for it. Now the VPR accepts such architecture:
<model name="fdce">
  <input_ports>
    <port name="CLR"/>
    <port is_clock="1" name="CLK"/>
    <port clock="CLK" name="DIN"/>
    <port clock="CLK" name="CE"/>
  </input_ports>
  <output_ports>
    <port clock="CLK" name="Q"/>
  </output_ports>
</model>

<pb_type blif_model=".subckt fdce" name="fdce" num_pb="4">
  <input name="CLR" num_pins="1"/>
  <clock name="CLK" num_pins="1"/>
  <input name="DIN" num_pins="1"/>
  <input name="CE" num_pins="1"/>
  <output name="Q" num_pins="1"/>
  <T_setup port="fdce.CE"  clock="CLK" value="1e-10"/>
  <T_hold  port="fdce.CE"  clock="CLK" value="1e-10"/>
  <T_setup port="fdce.DIN" clock="CLK" value="1e-10"/>
  <T_hold  port="fdce.DIN" clock="CLK" value="1e-10"/>
  <T_clock_to_Q port="fdce.Q" clock="CLK" max="1e-10"/>
</pb_type>

Though this may be not what we want.

Then I managed to add recovery/release (as setup/hold) for the async CLR input. The VPR accepts that but it thinks that the CLR is a sequential input just like D and CE.
<model name="fdce">
  <input_ports>
    <port name="CLR" clock="CLK"/>
    <port is_clock="1" name="CLK"/>
    <port clock="CLK" name="DIN"/>
    <port clock="CLK" name="CE"/>
  </input_ports>
  <output_ports>
    <port clock="CLK" name="Q"/>
  </output_ports>
</model>

<pb_type blif_model=".subckt fdce" name="fdce" num_pb="1">
  <input name="CLR" num_pins="1"/>
  <clock name="CLK" num_pins="1"/>
  <input name="DIN" num_pins="1"/>
  <input name="CE" num_pins="1"/>
  <output name="Q" num_pins="1"/>
  <T_setup port="fdce.CE"  clock="CLK" value="1e-10"/>
  <T_hold  port="fdce.CE"  clock="CLK" value="1e-10"/>
  <T_setup port="fdce.DIN" clock="CLK" value="1e-10"/>
  <T_hold  port="fdce.DIN" clock="CLK" value="1e-10"/>
  <T_clock_to_Q port="fdce.Q" clock="CLK" max="1e-10"/>
  <T_setup port="fdce.CLR" clock="CLK" value="1e-10"/>
  <T_hold port="fdce.CLR" clock="CLK" value="1e-10"/>
</pb_type>

And when I try to make the relation between CLR and Q combinational by adding combinational_sink_ports="Q" to CLR in the model then the VPR throws an error:
Error 1: ../arch.xml:-1 <pb_type> 'fdce' timing-annotation/<model> mismatch on port 'CLR' of model 'fdce', port is a sequential input with internal combinational connects but has neither min nor max T_clock_to_Q specified

For me it makes no sense to add T_clock_to_Q for CLR input thus it does not define async timing from one port to another.

Now I realized that defining Trec/Trel for async reset makes no sense at all..

I filed an issue to the upstream VPR with request for adding the ability to model async S/R flip-flop.


Bright future plans

Doc about implementing cluster expansion/upgrade/reconfiguration.

Plus make cassandra network topology aware.


Add local validator manager API

Why?
The main goal of this effort is to increase client diversity. UIs are very important to some users so this standard should ensure all clients have at least one.
The secondary goal is to offload UI work from core dev teams to other parties that can prioritize this work over Altair, the merge, etc.

WIP: This standard must be cheap to implement to be successful. Core devs are encouraged to voice concerns around complexity to ensure a timely implementation.

EDIT: Note - this proposal is initially motivated for a specific type of validator operator: the solo home DIY staker without good technical knowledge. This API is a simplification of the existing Prysm's validator API, which is also designed for that type of staker

Minimal validator API to enable a basic validator manager workflow. Supports:

Import, delete keystores
Import, export slashing db

Does not support:

Metrics visualization or plotting any type of chain data. Instead, should be done with metrics tooling such as Grafana or block explorers
VoluntaryExit. Instead, should be done with the deposit cli tooling.
Backup accounts. When migrating validator clients stakers should re-generate the keystores from the mnemonic or retrieve them from a self-managed backup.
Displaying logs.

All routes SHOULD be disabled by default and only be enabled with a CLI flag such as --enable-validator-api.
All sensitive routes MUST be authenticated. There SHOULD exist a single password per validator client binary such that multiple users are not supported.
The validator API MUST allow to add and delete accounts but SHOULD not allow to retrieve them. Users are encouraged to use alternative locations to backup their keystores and use them to perform validator client migration.

See the hackmd document for more context https://hackmd.io/@dapplion/eth2-validator-api

I'm a little concerned about this. Allowing remote access to this kind of functionality may make it very easy to get slashed...
Having CLI access implies a level of admin access, and I guess with that a level of responsibility, and it'd be potentially less open to error with export/import processes...
If a validator client with a password doesn't stop their validator from where ever its running and imports it to another client, that'll result in a slashing event, so we need to think really carefully whether this actually needs to be accessible from the standard rest api...
If we were to allow it, I think you'd want the key/slashing data in a single payload, so that you can't load a key without having slashing protection data, or do something like without the slashing protection enforce a 2 epoch delay or something...
We might be able to do something like verify it the specified validator hasn't attested or something currently, i'm not sure what validations could be worked in for altair - potentially there's a way to see the validator isn't active...
We also would need to be very careful about stipulations on how this is secured. I'm not sure we want to stipulate that a single password is used, as it should be up to the person running the client and in line with security requirements that the company has.  If they want to go and do one-time-passwords or 2FA, all power to them IMHO.
We can definitely suggest that it's disabled by default without providing a flag etc, and that they need to be authenticated routes, but ultimately that's really the level we can stipulate to, and maybe that at least basic auth should be supported or something like that.
The response of deleting keystores may need to contain more context about slashing summary of the keys removed...
If we do go this way, it would probably be pertinent to not require a login/logout structure, but also to be able to just issue an authenticated api call that has no real 'session'. Partially I say this because sessions can be particularly painful to manage in balanced environments.
Create/list accounts is something that needs more discussion. It's a definite attack vector to start creating millions of random accounts, and list accounts is something that non admin users shouldn't really be able to do (get half of the user/password problem, then brute force passwords)
Potentially this should be a separate repo, given its dealing purely with keys etc, and won't be dealing with any of the structures in eth2.0-api? It's a whole bunch of infrastructure to confuse the existing apis if we add it all here, and fairly unrelated in real terms... Just a thought...

I would like to echo the concerns of @rolfyone and add a few of my own.
First, and most importantly, this locks in a specific way of thinking about a validator, specifically that there is an endpoint that is responsible for both validating and signing.  This is becoming more commonly not the case, with multiple remote signer implementations available and being used.  This is not only a conceptual issue but a practical one: which process runs the API?  This repo builds an API that is run on the beacon node, and that's no use for these endpoints in many cases.  Ditto the validator client, as it may not have ownership of the keys (but does need to know the pubkeys for which it is validating).  The signer part is the most likely place to put this, or some of this, but they are generally built to be highly secure and allowing creation and deletion of keys seems to be an unlikely fit wit with their existing security model.
Second, the general idea of accessing slashing protection data from an active endpoint is a Bad Thing.  By definition, fetching this data from a running system means that it is out of date as soon as it has been retrieved and so cannot be trusted to be a complete picture when stored or imported elsewhere.
More of an implementation "detail", but the lack of HTTPS is something that seems to be massively insecure.  The idea that the keystore, plus the passphrase to access its private data, are both sent in the same request and in plaintext is a very concerning.
Regarding the goals of this PR: I think that both are laudable, however I suspect that this would be very low impact.  Client diversity, from what I have seen with those that install the software, is much more a question of ease of installation (and, long-term, maintenance) of the beacon node software.  The operations to import validators, although not standard between implementations, is relatively simple and so would not benefit massively from having an API rather than its existing CLI.  As for UI, the majority of any such project would be around the monitoring of an active beacon chain rather than its setup, in which I include the creation of validators.

You are right, in that this proposal is initially motivated for a specific type of validator operator: the solo home DIY staker without good technical knowledge. This API is a simplification of the existing Prysm's validator API, which is also designed for that type of staker. This proposal is definitely not for professional staking pools or institutional stakers.
@rolfyone

Potentially this should be a separate repo, given its dealing purely with keys etc, and won't be dealing with any of the structures in eth2.0-api? It's a whole bunch of infrastructure to confuse the existing apis if we add it all here, and fairly unrelated in real terms... Just a thought...

Moving this to a different repo is great idea since I agree this functionality doesn't have any resemblance with existing routes. The server for the validator manager API should be served by the a different process, the validator client. Happy to move this PR to a new repo once it exists.

If we were to allow it, I think you'd want the key/slashing data in a single payload, so that you can't load a key without having slashing protection data, or do something like without the slashing protection enforce a 2 epoch delay or something...

I agree, that's a great point. The counter-argument there is to not allow to extract the keys in anyway with this API, to contain the damage if auth fails.

We also would need to be very careful about stipulations on how this is secured. I'm not sure we want to stipulate that a single password is used, as it should be up to the person running the client and in line with security requirements that the company has. If they want to go and do one-time-passwords or 2FA, all power to them IMHO.

This simple auth scheme is meant to be served and used locally for solo stakers. In a company setting a more complex setup would have to be used.

The response of deleting keystores may need to contain more context about slashing summary of the keys removed...

That's a great point, I will add it.
@mcdee

This is not only a conceptual issue but a practical one: which process runs the API? This repo builds an API that is run on the beacon node, and that's no use for these endpoints in many cases.

This API should not be run by the beacon node, it should be run by the validator client unless using remote signing.

First, and most importantly, this locks in a specific way of thinking about a validator, specifically that there is an endpoint that is responsible for both validating and signing. This is becoming more commonly not the case, with multiple remote signer implementations available and being used.

That's a great point. I noted this API is motivated for the solo home staker. However I will research how new approaches to validating can influence this.

Second, the general idea of accessing slashing protection data from an active endpoint is a Bad Thing. By definition, fetching this data from a running system means that it is out of date as soon as it has been retrieved and so cannot be trusted to be a complete picture when stored or imported elsewhere.

@rolfyone idea of fetching slashing protection data only after deleting the keystores from the validator is good step in that direction.

More of an implementation "detail", but the lack of HTTPS is something that seems to be massively insecure. The idea that the keystore, plus the passphrase to access its private data, are both sent in the same request and in plaintext is a very concerning.

If users are able to get SSL certificates they should, or just do self-signed certs for local networks. Should the openapi doc reflect that?

Client diversity, from what I have seen with those that install the software, is much more a question of ease of installation (and, long-term, maintenance) of the beacon node software

Given that all projects publish to docker registries it's quite easy to build systems around that. The goal of this is to allow staking without forcing CLI interaction.

As for UI, the majority of any such project would be around the monitoring of an active beacon chain rather than its setup, in which I include the creation of validators.

We have the metrics standardization effort for that front.

I've updated and simplified the routes to do a simple atomic keymanager flow:

POST / Import keystores + slashing protection data
GET / List current known keys
DELETE / Atomically stop validating and export slashing protection data

I've removed the login, logout routes and added notes about the need to protect this routes. I left the suggestion of using an auth token in all requests that should be distributed in some way.

This code has been moved to this repo https://github.com/ethereum/keymanager-APIs/blob/master/keymanager-oapi.yaml
Thank you so much everyone for engaging in this initiative :heart: To continue the discussion please open an issue to new repo.

I can open an issue for token auth and format since that's the most contentious issue right now. https://github.com/ethereum/keymanager-APIs/issues/3


Add ItemsControl.PreparingContainer event

Add a new event that is raised before an item container is prepared for use.
What is the current behavior?
Currently it is not possible to intercept item container preparation. There is only the ContainerPrepared event, which is raised after the fact.
This causes issues in our product, which sometimes needs to do DI work before constructing item container templates.
Breaking changes
None
Obsoletions / Deprecations
None

Actually, while this change does fix the issue we were having, an even better solution for us would be to hook into template construction (to record the DI context) and template instantiation (to restore the DI context). We can do this by creating our own template types derived from the normal ones. Then we can get the behaviour we need at any time, without an ItemsControl.
I'll leave this PR open, as IMO it still makes sense to add the event for general purpose use.


use standard framework compatability table, despite caveats

@omsmith think he knows what this is about and it's not drastic.
We probably want to match msbuild exactly rather than second guess it here. If we made this decision later it would be a breaking change, and we probably want to avoid the possibility of that more.


Issue with calling purescript functions from javascript

This commit demonstrates how I tried and failed to go from using a main-based function to using function calls from within

require("./output/NotMain");                  // builds but runtime error
// require("NotMain");                        // doesn't build
// import NotMain from "./output/NotMain";    // builds but runtime error

Granted, this was with parcel bundler - the Spago Readme sort of implied that i might need to use something other thanspago bundle-module if using js libs (this uses React) - please correct me if I'm wrong.
CC'ing @ajnsit, the author of the original code, as he might have some insight, particularly on the parcel-bundler choice.
Error in browser
SyntaxError: An invalid or illegal string was specified hmr-runtime.js:29:2
    parcelRequire<["node_modules/parcel-bundler/src/builtins/hmr-runtime.js"]< hmr-runtime.js:29
    newRequire purescript-concur-starter.e31bb0bc.js:47
    parcelRequire purescript-concur-starter.e31bb0bc.js:81
    <anonymous> purescript-concur-starter.e31bb0bc.js:8

To reproduce
git clone https://github.com/bbarker/purescript-concur-starter.git
cd purescript-concur-starter
git checkout function_call_from_js
npm run start
# now browse to the dist/index.html page in your browser

I now have also tried:
 "start2": "spago bundle app --main NotMain --to dist/index.js && cp index.html dist/",

alternatively with bundle module instead of bundle app.
Int this case I get an error from the browser: ReferenceError: require is not defined[Learn More] index.js:3503:7 (as might be expected for the bundle module case based on the documentations).

Using  parcel, and index.js = import * as NotMain from "./output/NotMain";, if we pass --no-hmr to parcel, then the error goes away. But, thee app function calls to notMain(), notMain, NotMain.notMain(), NotMain.notMain still appears to have no effect.
In the generated output:
var notMain = Concur_React_Run.runWidgetInDom("root")(hello);
module.exports = {
  hello: hello,
  notMain: notMain
};

var NotMain = _interopRequireWildcard(require("./output/NotMain"));

Giving the sense that notMain may be evaluated upon load, though hard to tell from the generated JS output
In any case, rearranging like this did not help:

Workaround (as pointed out by tex on Slack), is to have the following index.js
var NotMain = require("./output/NotMain");
window.NotMain = NotMain;

@bbarker it sounds like this is a parcel quirk, but maybe we should still document it as a "gotcha" in here?

I think it is definitely worth a mention in docs somewhere. Maybe there
should be a docs repo/gist on Purescript and Parcel and link to that?
On Fri, May 10, 2019, 11:41 AM Fabrizio Ferrai<EMAIL_ADDRESS>wrote:

@bbarker https://github.com/bbarker it sounds like this is a parcel
quirk, but maybe we should still document it as a "gotcha" in here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spacchetti/spago/issues/193#issuecomment-491334079,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAG7XDWYYCUL3Z5IVHBR6MTPUWJRHANCNFSM4HL7IQEQ
.

@bbarker 👍
We could point to the TodoMVC with react-basic and spago since it's already linked somewhere else in the docs


Export QueueOptions type

R: @tropicadri
Fixes #2893
Adds a type to our package's exports.

Awesome thanks guys!


additions to description field section in contributing guide

per chat w/ @ddbeck, this section should note that:

markdown is ok
property names should be enclosed in backticks

I've opened https://github.com/web-platform-dx/web-features/pull/1646 to fix this. @autonome might you take a look?


Promise.race(): different behavior from the native one

Promise.race([1, Promise.resolve(2)]).then(function (val) {
    console.log(val);
});

—The value logged to the console should be 1, instead of 2 here (maybe?)

seems to work as expected:
var Promise = require('es6-promise');
Promise.race([1, Promise.resolve(2)]).then(console.log.bind(console);
>> 1


Xwayland process stuck and begins to consume 100% CPU with NVIDIA GPU

Environment
Microsoft Windows [Version 10.0.22000.258]
Release:        20.04`
WLSg 1.0.26
Steps to reproduce

wsl --shutdown
Open Ubuntu Prompt
$ glxinfo

WSL logs:
versions.txt
weston.log
stderr.log
dmesg.txt
Expected behavior
output from glxinfo
Actual behavior
It's hung.
Additional info:
In this machine I have an RTX 3060 and a GT710. If I disable the RTX 3060, then I do get output from glxinfo. I have tried this machine with only the RTX3060 installed. In that case it also fails
/dev/dxg is present
jaga@JAGA:/mnt/wslg$ ls /mnt/wslg/.X11-unix/
X0
system distro# ps -aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   2944  1780 ?        Sl   20:20   0:00 /init
root         2  0.0  0.0   3032  2036 ?        Sl   20:20   0:00 /init
root         6  0.0  0.0   2944   144 ?        S    20:20   0:00 /init
root         7  0.0  0.1  14040  6136 ?        S    20:20   0:00 /usr/bin/WSLGd
wslg        10  0.0  0.6<PHONE_NUMBER>6 ?        Sl   20:20   0:00 /usr/bin/weston --backend=rdp-backend.so --xwayland --s
wslg        12  0.0  0.0   2856     4 ?        S    20:20   0:00 /tools/init /mnt/c/Program Files/WindowsApps/MicrosoftC
message+    13  0.0  0.0   7164  3716 ?        S    20:20   0:00 /usr/bin/dbus-daemon --syslog --nofork --nopidfile --sy
wslg        14  0.0  0.1 233900  6872 ?        Sl   20:20   0:00 /usr/bin/pulseaudio --log-target=file:/mnt/wslg/pulseau
wslg        18  0.0  0.0   7032   372 ?        Ss   20:20   0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --pr
wslg        20  0.0  0.1  14948  7772 ?        S    20:20   0:00 /usr/libexec/weston-rdprail-shell
root        47  0.0  0.0   2964    80 ?        Ss   20:20   0:00 /init
root        48  0.0  0.0   2964    96 ?        R    20:20   0:00 /init
root        49  0.0  0.0   7772  4516 pts/0    Ss   20:20   0:00 -bash
root        73  0.0  0.0   3052    88 ?        Ss   20:20   0:00 /init
root        74  0.0  0.0   3052   104 ?        S    20:20   0:00 /init
wslg        75  0.0  0.0  10056  5044 pts/0    Ss   20:20   0:00 -bash
wslg        88  0.0  0.0   5660  1684 pts/0    S+   20:20   0:00 glxinfo
wslg        89 99.3  0.7<PHONE_NUMBER>8 ?        Rl   20:20  11:06 /usr/bin/Xwayland :0 -rootless -core -listen 73 -wm 74
root        95  0.0  0.0   3228  2004 pts/0    R+   20:31   0:00 ps -aux

Possibly the same as #505

@Swicegood, thanks for reporting the issue, would you please take core dump of Xwayland process and share with us? thanks!

Ok hope this is it
coreXwayland.zip
.

What's the status of this issue? I have got the same issue.
To add some clues:

At first I was using an AMD GPU and the GUI apps inside wsl worked pretty well. At that time the glxinfo -B output was like this:

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Microsoft Corporation (0xffffffff)
    Device: D3D12 (AMD Radeon(TM) Graphics) (0xffffffff)

Then I switched to RTX3060ti, I uninstalled all the AMD drivers and installed the NVIDIA drivers. Also, I installed cuda support inside wsl as described here

Then the GUI Apps inside wsl began to stuck. Like I input glxinfo -B, nothing outputs, the process just stuck there, never finish. gedit behaves the same way.
In /mnt/wslg/weston.log, Xwayland server was spawned but no window is initialized
[19:24:06.647] rdp_rail_notify_app_list(): rdp_peer 0x555a443ede70
[19:24:06.647]     inSync: 1
[19:24:06.647]     syncStart: 0
[19:24:06.647]     syncEnd: 1
[19:24:06.647]     newAppId: 1
[19:24:06.647]     deleteAppId: 0
[19:24:06.647]     deleteAppProvider: 0
[19:24:06.647]     appId: display-im6.q16
[19:24:06.647]     appGroup: (null)
[19:24:06.647]     appExecPath: /usr/bin/display-im6.q16 -nostdin
[19:24:06.647]     appWorkingDir: (null)
[19:24:06.647]     appDesc: ImageMagick (color depth=q16) (Ubuntu-20.04)
[19:24:06.647]     appIcon: 0x7f9cc801fbe0
[19:24:06.647]     appProvider: (null)
[19:24:11.015] Audio sink thread: connection successful on socket (68).
[19:24:11.015] RDP Sink version (1 - 1)
[19:28:39.444] Spawned Xwayland server, pid 97
[19:29:06.636] rdp_rail_idle_handler is called on peerCtx:0x555a443ede70

In /mnt/wslg/stderr.log, I got
dbus[10]: Unknown username "pulse" in message bus configuration file
/usr/share/icons/hicolor/scalable/apps/org.gnome.gedit.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
/usr/share/icons/hicolor/scalable/apps/ibus-setup.svg: unrecognized file header 0x3c 0x3f 0x78 0x6d
glamor: 'wl_drm' not supported
Missing Wayland requirements for glamor GBM backend
Failed to initialize glamor, falling back to sw

@antiwinter, which verson of NVIIDA driver are you using? Thanks!

Hi @hideyukn88 ,
I'm using <IP_ADDRESS>6 on Windows side. To verify wsl distro without CUDA driver, I imported a fresh new Ubuntu 22.04, and installed only gedit. The process still stuck
I guess the problem is on Win host side

I used Studio driver at first.
Just now I switched to Game Ready driver,
no luck

I think I have the same problem running Ubuntu 22.04 on a Dell Inspiron 15 with NVIDIA Graphics card. At system shutdown I get: Waiting for process: Xwayland


New package: MshReader v0.1.1

Registering package: MshReader
Repository: https://github.com/jorgepz/MshReader.jl
Created by: @jorgepz
Version: v0.1.1
Commit: 375cd3084e35e0877c95fd2e7feee0123cc808c1
Reviewed by: @jorgepz
Reference: https://github.com/jorgepz/MshReader.jl/commit/375cd3084e35e0877c95fd2e7feee0123cc808c1#commitcomment-77577946
Description: a minimal msh mesh format file reader

this should not be merged since another version was set in https://github.com/JuliaRegistries/General/pull/63570


Support binding to POCO when message body uses AMQP value

Fixes https://github.com/Azure/azure-sdk-for-net/issues/31440

/azp run net - servicebus - tests

API change check
API changes are not detected in this pull request.


Question: No Metadata Classes to process.

I'm trying to get this working in Silex but struggling when setting it up.
I get "No Metadata Classes to process." when trying to create the schema through my console app.
The schema validates fine if I run orm:validate-schema
Below is my config. Example\Api\Entities is mapped to "src/Example/Api/Entities" in my composer.json file (similar namespaces are working)
"orm.em.options" => array(
    "mappings" => array(
        // Using actual filesystem paths
        array(
            "type" => "annotation",
            "namespace" => "Example\Api\Entities",
            "path" => __DIR__."/../src/Example/Api/Entities",
        ),
    ),
),

Changing the path to a none existant path breaks validate-schema as expected.
This is my entity file
<?php

namespace Example\Api\Entities;

use Doctrine\ORM\Mapping as ORM;

/**
 * @ORM\Entity
 * @ORM\Table(name="example")
 */
class Example
{
/**
 * @ORM\Column(type="integer")
 * @ORM\Id
 * @ORM\GeneratedValue(strategy="AUTO")
 */
protected $id;

/**
 * @ORM\Column(type="string", length=100)
 */
protected $name;

/**
 * @ORM\Column(type="decimal", scale=2)
 */
protected $price;

/**
 * @ORM\Column(type="text")
 */
protected $description;
}

I'm not really sure how to fix this. Any help would be greatly appreciated.

Does this help at all? It seems like it would not matter if things are working for the schema part but maybe it loads up slightly differently?

@simensen was also my first idea ;-)

Thanks for the quick support, I've tried adding the AnnotationRegistry to both my console.php and index.php (where orm.em.options is) and still no luck.

@mikebell Where is the orm:validate-schema command coming from? And which command are you running to try and create your schema? Maybe posting your console.php to a gist/pastebin would be useful?

Here is my console.php - https://gist.github.com/mikebell/b7f7e94887cd00723830
It resides inside src/

@mikebell Nothing is jumping out at me as being wrong. :-/ I haven't used those commands like that in awhile so I'm not sure what they are looking for or are expecting. You can look at the command that works (ValidateSchemaCommand) and see how it differs from the one that does not (CreateCommand ). It is possible the commands in the SchemaTool namespace have different dependencies than the ValidateSchemaCommand. I'd look to see how each is using the HelperSet and see if there is something else you need to be adding to it in order for the CreateCommand to work.
If you end up finding a solution here it would be great if you could report that here so we can track this down in the future or look to adding it into some documentation somewhere.

@mikebell it seems you register the Annotation Registry after calling the entity manager

@dominikzogg d'oh. i was looking at how far down the annotation registry was being added but i decided in the end that i wouldn't mention it. i usually do that right after the class loader is created so i've never run into anything like this.
@mikebell my guess is that @dominikzogg is right on this. try moving the annotation registry call before you get $em from the container.
thank you so much, @dominikzogg!

@simensen i hope it's the solution and you know i try to support this provider as it would be mine ;-)

Seem to be getting somewhere now. I've updated my console.php to - https://gist.github.com/mikebell/b7f7e94887cd00723830
I know get:
PHP Fatal error:  Uncaught exception 'InvalidArgumentException' with message 'A callable is expected in AnnotationRegistry::registerLoader().' in /var/www/kardio.dev/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationRegistry.php:111
Stack trace:
#0 /var/www/kardio.dev/src/console.php(14): Doctrine\Common\Annotations\AnnotationRegistry::registerLoader(Array)
#1 /var/www/kardio.dev/src/console(3): require('/var/www/kardio...')
#2 {main}
  thrown in /var/www/kardio.dev/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationRegistry.php on line 111

@mikebell change 10/11 with 13/14

I think this is because of how require_once works. I believe you are probably doing require_once in web/index.php already. So when you require_once again, it doesn't actually return the $loader since it was already required in web/index.php. I'd suggest putting these lines just before you include web/index.php.
$loader = require_once __DIR__.'/../vendor/autoload.php';
\Doctrine\Common\Annotations\AnnotationRegistry::registerLoader(array($loader, 'loadClass'));

All of which is a longer form (with explanation) of what @dominikzogg just said while I was writing this. :)

Back to the "No Metadata Classes to process." error again. I'm going to park this for now, thanks for both your help, didn't expect to get this much help!

@mikebell your welcome

Try and change:
    "path" => __DIR__."/../src/Example/Api/Entities",

with:
    "path" => __DIR__."/../src",

That should work.

My problem with the "No Metadata Classes to process." error was that my generated entities were missing a namespace.  I used it in my silex skeleton which by default has example entities setup. It lacks proper documentation so if you need help setting it up then gimme a shout. Skeleton can be found at:
https://github.com/marcojanssen/silex-rest

Hi, i had this pb.
In the ORM/Configuration.php you have this line
"Adds a new default annotation driver with a correctly configured annotation reader. If $useSimpleAnnotationReader is true, the notation @Entity will work, otherwise, the notation @ORM\Entity will be supported."
And, when you use console to generate your entities, they are generate with this annotation.
"@ORM\Table(name="yourTable")"
By default, useSimpleAnnotationReader is true, so you need to change your Entity annotation @ORM\Table to @Table
That works for me

Did you found solution?

exact same problem here with no success!

Hello. You need to set alias to 'core' and disable use_simple_annotation_reader.
['mappings' => [
    [
        'alias' => 'core',
        'type' => 'annotation',
        'namespace' => 'TestApp\Entity',
        'path' => __DIR__ . '/TestApp/Entity',
        'use_simple_annotation_reader' => false,
    ],
]]

It's an old post but if someone have the same problem, I suggest adding "use_simple_annotation_reader" => false, it worked for me.
"orm.em.options" => array(
    "mappings" => array(
        // Using actual filesystem paths
        array(
            "type" => "annotation",
            "namespace" => "Example\Api\Entities",
            "path" => __DIR__."/../src/Example/Api/Entities",
            "use_simple_annotation_reader" => false,
        ),
    ),
),

Hope it will helps someone


Fetch upstream

Resolves https://github.com/RasaHQ/rasa/issues/9791

@m-vdb the upstream repo changed the default branch from master to main. Do we want to sync with it?

I've updated the default branch to main in this repo, thanks @HotThoughts 🙏🏻

Will take a look at why this is failing next week
https://github.com/RasaHQ/create-or-update-project-card/runs/4103914558?check_suite_focus=true


Add missing pages.

Docs-side fix for #1822.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4133ed84adebc80d85d925500e8c42e05d719ee4/

That would be great, thanks!

OK, I'll push some updates soon.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/44d537e1ae7efe08f966c15e453e0ac226a91009/

Review status: 0 of 7 files reviewed at latest revision, all discussions resolved, some commit checks pending.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/dd9711cff67840dd6914e84160e159ed419b3993/


[Windows Upgrade] [BugFix] D2IQ-65203: fixed way the detect script is executed

High-level description
BugFix: currently if some NativeApplication being failed on Windows machine, and then when the detect script (cmdlet) is ran, $LASTEXITCODE of a previous Native Application (not cmdlet, but python, or an exe, or some service) being picked up instead of real exit code of cmdlet. As per official documentation $LASTEXICODE works only with external apps such as cmds, python, exe, etc, but not with Powershell cmdlets. Which is very odd limitation of PS as scripting language.
Therefore for running the detect script only "Invoke-NativeApplication" removed as executor, new executor  suggested -  simple try { } catch { }  construction.
Corresponding DC/OS tickets (required)

D2IQ-65203  upgrade_win.ps1 stops with an error

Related tickets (optional)

D2IQ-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot changelog-not-required Windows Upgrade minor change

@mesosphere-mergebot request-review  @OleksandrBielov

@mesosphere-mergebot request-review @vadymzagorodko

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review @jongiddy

@mesosphere-mergebot request-review @DominikDary

So, Invoke-NativeApplication does not work ...

It's valid point, @jongiddy . Please have a look on new version. I've also contacted creator asking his email approval to use the helper function


apps/watchman: remove mount of watchman-data PVC

We're on MySQL, so we don't need this mount. Also, ReadWriteOnce
prevents concurrnet mounts.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #125   +/-   ##
=======================================
  Coverage   78.37%   78.37%
=======================================
  Files           1        1
  Lines          37       37
=======================================
  Hits           29       29
  Misses          4        4
  Partials        4        4

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 5e334d4...9d50c35. Read the comment docs.


Review Current Dash 'Multi-Page' Code and Organization

The current mult-page AWS Dashboard application is our FIRST application (there will hopefully be a number of tailored, customized apps for clients). The way this application is set up is documented here:

https://docs.google.com/presentation/d/116GRosKqHS3vBC8RdyJ9uGbZbHQe0Mgg6sac4l-0wZE/edit?usp=sharing

Review slides and then review the code

sageworks/applications/aws_dashboard.  (Dash code)
sageworks/src/sageworks/web_components (Plotly 'graphs/figures')
sageworks/src/sageworks/views (The components that isolate the gathering of AWS services data)

@brifordwylie
Here’s a mock for an improved organization of the multi-page app:
pages/
…./page_xx
……../assets/              (page-specific assets)
……../components/          (page-specific Dash components )
……../callbacks.py         (endpoints logic, thin layer of Python code)
……../layout.py            (organization and style of visual elements)
……../page.py              (this page’s main script)
…./page_yy
……../ ….
…./assets/         (shared assets)
…./components/     (shared Dash components)
…./services/       (shared functions)
…./clients/        (e.g. SageWorksClient, basically sageworks.views)
…./app.py          (main Dash app script)
…./requirements.txt
…./Dockerfile
…./README.md

With an organization similar to this we would be achieving:

modularization and standardization of page-specific content (callbacks, layouts, assets)
standardization of shared resources (components, assets, clients, services, etc…)
helps us with a better separation of concerns between backend logic (services, clients) and the frontend logic (callbacks and layout)
definition of app’s dependencies (requirements.txt), documentation (README.md) and containerization (Dockerfile) to improve distribution and re-usability of the aws web server

All those changes might be too much to do right now, though. We should consider the priorities of the SageWorks project as a whole.
Open questions:

should we rename /sageworks/web_components  to /sageworks/graphic_components?
each web_component depends on the information of at least one View to be used. How do we formalize these dependencies? E.g. if web_components are specific to just one View, we probably would like to have this dependency explicitly reflected in the project’s organization as well, with folders for each view with a sub-folder /webcomponents for all visual components related to that view

@luiztauffer this looks good. Lets use the proposed file/directory reorg above 👍


[Feat] 💄 User Image.svelte to display the picture in the message

Message
{"prompt":"A rocket launching off the surface of the moon, with the moon's grey, cratered landscape in the foreground. The rocket is leaving a trail of fire and smoke as it ascends into the dark, starry space. Earth is visible in the background as a small, blue and green sphere.","size":"1792x1024"}

![🖼 图片预览](https://chatgpt-file.oss-cn-hongkong.aliyuncs.com/image_20240804202313.png?OSSAccessKeyId=LTAI5tJNJAdjFcAHdWwimH4n&Expires=1723378996&Signature=WmNOr8gzV%2B9t%2Bl4bzlPOD1mwn%2BE%3D)

[🖼 点击下载图片](https://chatgpt-file.oss-cn-hongkong.aliyuncs.com/image_20240804202313.png?OSSAccessKeyId=LTAI5tJNJAdjFcAHdWwimH4n&Expires=1723378996&Signature=WmNOr8gzV%2B9t%2Bl4bzlPOD1mwn%2BE%3D)

https://github.com/user-attachments/assets/6bfbcda9-bdcd-4e8b-a947-fbb5021793e4

@tjbck 👀

Added to dev.

Thanks！


Fix where no oncall returned if missing configuration variable

Introduced in #117. Also fixes case where an ignored schedule would still appear in the logs if no username was assigned to it.
Fixes #118

/cc @RussellRollins for review.

Released in v3.1.1

thanks much for the quick turnaround, we appreciate you!


Typescript support

Currently there is no npm package called @types/google-cloud__automl
This could enhance the experience users have with the library. Since other google cloud package feature typescript support also, it makes sense to create this npm package.

👋 @nicobrinkkemper you'll be happy to hear that there is currently an effort to add TypeScript support to all of the client libraries.

This package is now written with TypeScript, and ships its own types :)  Enjoy!


New zone can't be added to rules unless it already exists in a rule

Describe the bug
I added 2 new zones in the GUI, but when I try to add them to rule (from-Add/to-Add) it fails stating the zone doesn't exist.  If I manually add the zones to at least one rule, the command will work.  I didn't try the force option.
Expected behavior
A new zone should be added to a rule without having to manually adding to a rule first.
Current behavior
I get an error:
PS C:\tools\pan> php -r "require_once 'C:/tools/pan/pan-os-php/utils/pan-os-php.php';" type=rule in=api://panorama.domain.com location=DG1 actions=to-Add:NewZone 'filter=(to has ExistingZone)'

*********** pan-os-php.php type=rule UTILITY **************

PAN-OS-PHP version: 2.1.20 [WIN] [8.2.12]

Downloading config from API...

  If not, make it so I don't have to manually add a new zone to a rule for the command to work.
Steps to reproduce
See PowerShell command under Current Behavior
After failure, if I manually add NewZone to a rule (I only added it to one) and commit to Panorama (I don't know if the commit step is necessary), the command works and adds it to the remaining rules.
Context
I have new zones to add to our rules.  Today was the first time trying to add a new zone that wasn't already in a rule.
Your Environment

Version used: 2.1.20
Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): PowerShell v5
Operating System and version (desktop or mobile): Windows 10

as Panorama DeviceGroup is specific, you can directly add zone information without creating a real Zone object in template in Panorama GUI;
explicit therefor as mentioned in the pan-os-php script:
"zone named 'NewZone' not found, you can try to use xxx-add-force action instead"
please use:
....in=api://panorama.domain.com location=DG1 actions=to-Add-force:NewZone 'filter=(to has ExistingZone)'

ok, thanks!


Performance variance

Hi ,
Many thanks for sharing the code and I really like this interesting work. I ran the code on the data your shared, but the performance seems slightly different from the reported in the table. For example, this is the average result for the 5 splits I obtained on 50salads, "Acc:82.7, Edit:77.9, F1@10: 83.1, F1@25: 81.7, F1@50: 75.9". I was wondering what I missed in the reproduction.
Best regards

@lyhisme I have the same question with you.But I don't know why...

@txyxju1997 @lyhisme I also find the performance varies a lot with different epochs....


Remove double space from create message

Signed-off-by: tpmccallum<EMAIL_ADDRESS>

Thanks @itowlson and @rajatjindal


 In the attached image, the left ("test-hi-dpi") was rendered with my screen at 4K resolution, while the right was rendered with my screen at 1080p. The screenshot was taken with a 4K resolution on my screen.
I don't know if this is a markdown-themable-pdf issue or an atom issue at large.

Hello! I can not imagine that it has to do with the screen resolution.
For generation a headless browser is used, which is not based on your screen resolution, but on the configuration in the package settings.
I switch between a Full HD and 4k monitor every day. Should you find out, it would be nice if you let me know. Currently I work in the background at the v2. A test with it would be nice.

It's been a while, but with v1.2.1 and the Windows 10 April Update the font is rendered tiny unless the main display is set to 1080p. Current workaround is to render to html and print from my browser, but that obviously rids the document of the custom header/footer.
What are you using for the headless browser? Looking for the right repo to file a bug in.

Hey @mrbmi513,
in the file https://github.com/cakebake/markdown-themeable-pdf/blob/master/package.json you will find the used repositories.
v1 uses html-pdf (phantomjs) and v2 puppeteer / chromium. I could not publish v2 yet, because there are problems regarding header and footer in chromium.

4k small font also.


container not getting started

Once i came to ecs-monitor role the task is not getting creating why means the container are not creating the error i faced was
CannotPullContainerError: inspect image has been retried 5 time(s): failed to resolve ref "docker.io/prom/prometheus:latest": failed to do request: Head https://registry-1.docker.io/v2/prom/prometheus/manifests/latest: dial tcp <IP_ADDRESS>:43: i/o timeout

Probably it's because your environment doesn't have internet access. You can either make it public or upload the docker images to ECR.


id_token doesn't contain custom claims like user roles when grant type is Hybrid

I'm using Hybrid grant type and request with response_type = "id_token code"
After getting result i then request for access_token. In my Client application I need end user roles defined in Identity Server, unfortunately id_token contains only predefined claims. However when I remove code from response type i get id_token with all the necessary claims.
what is the preferable way to have id_token with all claims and refresh_token,access_token (I don't need roles here).

https://leastprivilege.com/2016/12/14/optimizing-identity-tokens-for-size/


[Roots 3] References to runic shears should only be added to Patchouli when unlocked

I.e., until such a point a time that you actually unlock them (and it should be clarified that you use them on the crop rather than the actual carrot, etc), there's no point mentioning runic shears at all: it just gets extremely confusing.

Fixed by removing references to removed mechanics


Can't run Ajax requests in InAppBrowser plugin's webview.

Running an Ajax request, I get this:
I/chromium(26077): [INFO:CONSOLE(0)] "XMLHttpRequest cannot load http://URL_OF_MY_REQUEST_ON_MY_SERVER. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access.", source: file:///android_asset/www/comments.html (0)
This issue is not present in Cordova or crosswalk-cordova-android.
My manifest.json seems correct too.
    "name": "APP_NAME",
    "description": "A Sample Chrome App",
    "manifest_version": 2,
    "minimum_chrome_version": "23",
    "version": "0.1.1",
    "offline_enabled": true,
    "icons": {
        "16": "assets/icons/icon16.png",
        "36": "assets/icons/icon36.png",
        "48": "assets/icons/icon48.png",
        "57": "assets/icons/icon57.png",
        "72": "assets/icons/icon72.png",
        "96": "assets/icons/icon96.png",
        "114": "assets/icons/icon114.png",
        "128": "assets/icons/icon128.png",
        "144": "assets/icons/icon144.png"
    },
    "app": {
        "background": {
            "scripts": [
                "background.js"
            ]
        }
    },
    "permissions": [
        "<all_urls>"
    ]
}```

It seems like CORS is disabled app-wide and the `manifest.json` permissions aren't applying to InAppBrowser instances.

Closing this issue, based on lack of further information.  Feel free to re-open if there are further details.


Lint getting started guide

I am going to merge this, with a follow up to lint the getting started guide

Originally posted by @dyladan in https://github.com/open-telemetry/opentelemetry-js/pull/1374#issuecomment-669307493

I would like to work on this one.

Awesome thanks!


Missing localisation keys for DateModified

I believe the localisation keys for Search.SortBy.DateModified were inadvertently overlooked for the default and en-US locale files. Prior to making these changes, this option was displaying as a raw key name on my copy.

Thanks!


Update spyder to not use google code

See #10461

Thank you for the contribution. It was merged directly as cd18dd082012f91e601092817642bcfdcb448fc8 to keep commit history cleaner. Your contribution is still credited to you.


[Enhancement] Allow specifying a recipe for blueprints without any

I'm looking at a number of generic "template" factories with f.ex. 20 assemblers, and belts for 2 inputs and 1 output. These templates do not have any recipe on them, so I can't currently edit the templates recipe before placing :/
I'm amazed by all the other stuff I can do though, so I hope this can be added as well :)
I imagine that any assembler, smelter or chemical plant without a recipe, would be grouped in the recipes section, with maybe a dotted-box signifying an empty assembler/smelter/chemical plant?
Clicking this should open the recipe menu as usual.

Unfortunately I do not take feature requests at the moment.

(Reopening since I'm taking feature requests right now)

Feature implemented in Blueprint Tweaks v1.6.0


Fixed typo in nullinux.py and added more links

Fixed typo in nullinux.py
Added more links and usage to README.md

@thehappydinoa, thank you for contributing to the project.  I apologize for just seeing your pull request now. The shebang statement was identified a few weeks ago and has already been addressed in a previous commit. Your pull request cannot be directly merged but I liked your ideas for modifying the README.md and making the program’s usage more readily available. These ideas will be added to the next
Commit as well as a section for acknowledging nullinux’s contributors. Thank you again for your contributions to the project!


Add auto-generate samples for Chaos and DataLakeAnalytics

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Can't use multiple themes in same time with Vite

Hello,
Thanks a lot for this greate package, I use it with every project even If I need single theme! really in love with it 💌
The issue :
In version 2 with the vite thing, when we do npm run build:theme1 and then npm run build:theme2
There is only one build folder in public and one manifesto file, which breaks everything.
Not like the v1 when using mix, there were multiple build folders for each theme in public/theme1/css and public/theme2/css etc ..
Any idea how this will be resolved ?
Thanks.

I am so glad you like this package. And thank you for pointing out this issue. I have fixed this issue in v2.0.2. So, run composer update and create a new theme from scratch.
or make the following changes to your theme:

In the file themes/theme-name/vite.config.js, add buildDirectory option.

...

plugins: [
        laravel({
            input: [
                "themes/theme-name/css/app.css",
                "themes/theme-name/js/app.js"
            ],
            buildDirectory: "theme-name",
        }),
...

Update @vite directive in the blade layout file.

@vite(['themes/theme-name/css/app.css', 'themes/theme-name/js/app.js'], 'theme-name')

Works great! Thanks a lot @hkp22  🙏


Pathlib's Path as input will raise exceptions

FYI

Which version are you using?

@version 2.0.0
Raises:
                        f'is not JSON serializable')
E       TypeError: Object of type PosixPath is not JSON serializable


Want to change the splash screen

Want to remove the Title bar and Navigation bar from splash screen to make it spread on full screen of your device.

I can do this @akshatbhuhagal please can you assign it to me.


Revise "Manage Operators" documentation

This is a re-org/rewrite of the "operator management" user guidance.
The changes apply to 3.x and forward, and so should be made available in the "live" 3.x documentation.

@rjeberhard This pull is ready for your review and merge. Dongbo, Rosemary, and I have all finished our passes.


add netdevops-primer to CONTACT_MESSAGE_TYPEs

Codecov Report

Merging #182 (bf46f88) into prep-release (11306f9) will not change coverage.
Report is 5 commits behind head on prep-release.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@              Coverage Diff              @@
##           prep-release     #182   +/-   ##
=============================================
  Coverage         48.04%   48.04%
=============================================
  Files               140      140
  Lines              5120     5120
=============================================
  Hits               2460     2460
  Misses             2660     2660

Files Changed
Coverage Δ

src/fullctl/django/enum.py
0.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Using TLS 1.3 methods

I'm using OpenSSL and Winsock and I want to use the TLS 1.3 protocol because I heard that TLS 1.3 will not renegotiate during communication between server and client. So my question is how to invoke SSL_CTX_new for TLS 1.3?

Just use:
SSL_CTX *ctx = SSL_CTX_new(TLS_server_method());

or
SSL_CTX *ctx = SSL_CTX_new(TLS_client_method());

as appropriate. This will enable the highest protocol version supported by both client and server to be negotiated.
Optionally you can enforce a lower bound on the protocol version that will be negotiated. For example to fail the handshake if a TLSv1.2 only peer connects then you can use:
SSL_CTX_set_min_proto_version(ctx, TLS1_3_VERSION);

Do you have any idea why OpenSSL ,in the context of Windows Sockets, triggers FD_READ events with 0 bytes ready to be read?

Thanks


⚠ Samsung has degraded performance

In 450c5fa, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2467 ms

Resolved: Samsung performance has improved in 7bac614.


Is this project active?

Hi all.
I want to help, but I want to know if this project is active. Is this project active?

Hello,
As much as I'd like to keep it alive, I simply don't have the time to maintain it anymore, also I stopped using Redmine years ago but tried to keep the theme working with newer versions whenever I could find the time for it.
Any help would be appreciated, and active maintainers even more so!


update user path takes userName

Previously, we were running PUT to /users
In order to update a user, we should PUT to /users/

Not 100% on this.  I looked at https://github.com/spring-projects/spring-petclinic/blob/6730a229a0cf22562fe148d68c3f33d03c44e539/src/main/java/org/springframework/samples/petclinic/owner/OwnerController.java#L111
And they simply overwrote the incoming entity with the userName from the URI path.
This makes sense, as the userName is unique.  We do not allow people to change user names however.
The alternative is more work.  tbh, not sure it is worth the complexity

Closes #74


Add support for sorting *array.Binary columns

This commit adds sorting *array.Binary and dictionary of *array.Binary. I wanted GenericTable to automatically sort records before write. This is the only blocker.

We are getting closer to a smoother frostdb ux. Using GenericTable will  make sure the arrow.Record is sorted before being inserted into the  db.

Nice! Could you add test coverage for this?

@asubiotto I addressed your comment PTAL.

@asubiotto thanks for the review, I addressed your comments PTAL.


Move examples into sub dir

Codecov Report

Merging #31 (381b2d3) into master (2c424b2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   92.25%   92.25%
=======================================
  Files           1        1
  Lines         878      878
=======================================
  Hits          810      810
  Misses         68       68

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 2c424b2...381b2d3. Read the comment docs.


How to support pagination in chat?

We cannot echo 600 server hardware when someone says list all.  Whats the max? How does the user get more?

I'm working on it. Now when the user says list all, the resources will be listed in parts of 10.


Array as state is cast to Object

This example does not work as expected: https://codepen.io/zaceno/pen/RgqOzL
It fails becasue the state is initialized as state: ['X', 'Y'], but then internally transformed into: {'0':'X, '1': 'Y'} (which does not have join, map or other array methods)
I believe this is a bug. Or it should be documented.

@zaceno Yes, you are right. Currently the only supported state types are object, string and number. We should write a proper essay on the state property and include this detail here.

Whoops! 😉

@zaceno Added it to #244.


How to start distributed servers without sync?

Hi,Is there any way to start 3 distributed servers without synchronize?
Can I use autoDeploy = false?
We are copying the same DB to both 3 servers. But when we start, one of then send this request:
2015-06-19 16:29:52:666 WARNI [orientdb01]->[[orientdb21]] requesting deploy of
database 'ilang' on local server... [OHazelcastPlugin]
The problem is that it spends almost 3 hours, because our DB is 80GB.
Thanks in advance.

Yes, this is exactly the purpose of autoDeploy setting. If you set it = false the database is never asked to the cluster, but local copy is used.

I'm using, but getting a lot of errors ( conflicts,  timeout and querum 2 not reached)... Do you have any Idea where is my mistake? Here is my log.
https://s3.amazonaws.com/a-several/orient-server.log.0

Seems database are not aligned on all the servers. For example if you have 1 record more in the  database on server 01, the next createRecord will assign a RID higher on server 01, forcing a rollback. The solution is to align databases at the beginning, by hand (copy files before starting) or activate "autoDeploy:true" in cfg.

Lvca, ontem à noite, eu copiei o mesmo banco de dados para todos os servidores (3). Quando me virei no segundo servidor solicitou um deploy banco de dados que foi corretamente iniciado no primeiro servidor. Então eu me virei em terceiro servidor, que solicitou um banco de dados implantar também. Hoje de manhã apenas o segundo servidor foi implantado e ONLINE. Não posso virar o terceiro servidor quando o segundo está implantando? Você sabe se esta solução distribuída funciona bem em meu cenário (banco de dados maior do que 80GB e elevado número de atualização)?

Could "hotAlignment=true" be the problem?

Next release will support incremental backup (we're designing this feature right now to work on distributed), but for now you could copy the database manually and set autoDeploy:false. Question: are the servers on the same LAN? What's the fastest way to copy the database on all the nodes?

I'll try again. All server are in the same AWS region, but distinct  availability zone, for us it's the same LAN. I normally copy and paste (80GB/8 min), its faster than compress - copy - extract.

Ok, It's working now, but we got a lot of this WARN:
2015-06-22 13:53:22:721 WARNI Local node 'orientdb21' is not the master for cluster 'useronline' (it's 'orientdb21').
Switching to a valid cluster of the same class: 'useronline_orientdb21' [ODistributedStorage]
Is it normal?
Right now one node is in deadlock. For this problem I'm opening an Issue.
Thank You


label studio start error: AttributeError: module 'attr' has no attribute 's'

Describe the bug
I just installed label studio on a fresh AWS t3 instance and am seeing the error below when trying to start.
To Reproduce
Steps to reproduce the behavior:

Create a new AWS t3 Linux  instance and SSH
sudo yum install python3-pip
pip3 install label-studio
label-studio

Expected behavior
label studio starts without error
Environment (please complete the following information):

OS: Amazon Linux ami-0ab193018f3e9351b / al2023-ami-2023.0.20230517.1-kernel-6.1-x86_64
Python: 3.9.16
Label Studio Version: 1.7.3

Additional context
=> Database and media directory: /home/ec2-user/.local/share/label-studio
=> Static URL is set to: /static/
=> Database and media directory: /home/ec2-user/.local/share/label-studio
=> Static URL is set to: /static/
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /pypi/label-studio/json HTTP/1.1" 200 56465
Can't read version file: ls-version_.py. Fall back to: version_.py
Traceback (most recent call last):
File "/home/ec2-user/.local/bin/label-studio", line 8, in
sys.exit(main())
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/server.py", line 296, in main
_setup_env()
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/server.py", line 40, in _setup_env
application = get_wsgi_application()
File "/home/ec2-user/.local/lib/python3.9/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application
django.setup(set_prefix=False)
File "/home/ec2-user/.local/lib/python3.9/site-packages/django/init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/ec2-user/.local/lib/python3.9/site-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/home/ec2-user/.local/lib/python3.9/site-packages/django/apps/config.py", line 301, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib64/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/users/models.py", line 18, in
from projects.models import Project
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/projects/models.py", line 15, in
from projects.functions.utils import make_queryset_from_iterable
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/projects/functions/init.py", line 4, in
from tasks.models import Annotation, Task
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/tasks/models.py", line 32, in
from core.label_config import SINGLE_VALUED_TAGS
File "/home/ec2-user/.local/lib/python3.9/site-packages/label_studio/core/label_config.py", line 9, in
import jsonschema
File "/usr/lib/python3.9/site-packages/jsonschema/init.py", line 11, in
from jsonschema.exceptions import (
File "/usr/lib/python3.9/site-packages/jsonschema/exceptions.py", line 152, in
@attr.s(hash=True)
AttributeError: module 'attr' has no attribute 's'

Bumped into this as well. There are two functionally similar dependencies attr and attrs, except for attrs if a more feature-full option. After I had removed the attr package, the issue gone. My dumb guess would be: because their module names clashes python resolves attr from attr first, not giving the way to the attr from attrs

Removing the attr package as suggested by @dns-xyz-glk solves this problem (thanks!):
pip3 uninstall attr

This worked for me

This is still a problem when following the quick start guide on a fresh installation

The workaround worked for me as well. Thank you @kulnor

@BhooshanDeshpande , thanks. It's working well.


Add support for "<%", "%>" and "-%>" delimiters in templating in @angular-devkit/core

🚀 Feature request
Command (mark with an x)

[x] generate

Description
The templating for the @angular/devkit library uses EJS, sort of but doesn't support whitespace slurping the way that the documentation of EJS has declared it. Having this would enable schematic templates to be much more flexible with their whitespace and therefor easier to read while still creating nicely formatted files.
Describe the solution you'd like
The three delimiters: "<%_", "_%>" and "-%>" should just be added and work the same way that they do in EJS.
I already have an idea of the code that I'd like to add, and a pull request almost ready. It's very simple and only affects one file.
Examples
Within @schematics/angular this would allow an example like the following
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
<%_ if (routing) { %>
import { AppRoutingModule } from './app-routing.module';
<%_ } -%>
import { AppComponent } from './app.component';

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    <%_ if (routing) { -%>
    AppRoutingModule,
    <%_ } -%>
    BrowserModule
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Which would generate with the correct whitespace.

Looking forward to this feature  🙏🙏

This feature would be great 👍


feat: disable everything, show only monetization status

Ok, I  had thought you just wanted this in a branch

@sublimator that was my initial idea but I'd rather we merge this in since then main is in the final state that we have an up to date version of the extension of which is released.

Should be able to get to it today or tomorrow (my time)


Update security-center-alerts-overview.md

Customer confusion on a support case regarding the availability of alerts on Free tier

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


Add required Github secret. Closes #15. Breaking change, bump to 2.0.0

This adds a github webhook secret, required checks for env key, bumps to 2.0.0 due to breaking changes. Should be merged in tandem with docs PR at https://github.com/zpnk/stage.now/issues/13

@zpnk Ok this is all set. Docs PR is done so both should be able to go whenever you are done reviewing.

Good idea. I'll try moving it inside.

@amccloud Changes implemented and available for review. Webhook errors can be generated on a per provider basis but are thrown by the individual provider implementations. Currently only github is provided but it would be trivial to add Gitlab or others.

👋  @jimthedev I really like this! I'm 👍 on merging, except for one thing: does this merit a 2.0 version bump? I understand that it's technically "breaking" because of being required, but feels kinda weird to call this v2. I guess I'm not sure how we should version, because stage-ci is consumed a bit differently than a library/framework. Do you have any thoughts on this? I think I'd be for going with v1.1.
Sorry to be a bit pedantic!

@zpnk No worries. On my repos I am pretty liberal with my version bumps because otherwise I feel like semantic versioning starts to lose meaning. For example, think of how many version of Chrome there are.
With that said I am happy to use whichever scheme you prefer. 👍

@zpnk Rebased to 1.1.0. Ready to go.

🙌  Thanks for this feature @jimthedev! Great work 👍

🎉  Thanks for the merge. btw I am the author of commitizen so ChangeLine sounds interesting!


fix(module:date-picker): added missing type attributes for buttons

This should fix #7012
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix

What is the current behavior?
Issue Number: #7012
What is the new behavior?
Buttons are not submitting the form anymore.
Does this PR introduce a breaking change?
[ ] Yes
[ ] No
[x] Don't think so

Other information

@wenqi73 no problem. When is it going to be released? This issue is seriously affecting our products.


Claim failed

Is it a CORS related problem?

Seems like this is caused by www subdomain. Will notify to request a change in the env variables.


protein prep is currently removing crystal waters

we need to retain crystallographic waters throughout our prep workflows so that we make sure that these are used for docking, viz and FECs.

yes we used to be able to do that, shouldn't be too hard to add back