keras.models.clone_model creates different weight names for RNN layers

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS
TensorFlow installed from (source or binary): PYPI
TensorFlow version (use command below): v2.11.0-rc2-17-gd5b57ca93e5 2.11.0
Python version: 3.7.12

Describe the problem.
When cloning a Keras RNN model using keras.models.clone_model(...) the weight names of the inner RNN cells get incremented instead of being cloned. The problem does not occur when using save_model(...) and then load_model(...).
Describe the current behavior.
Here an example:
import tensorflow as tf

inputs = tf.keras.Input(batch_shape=[1, 2, 3])
layer = tf.keras.layers.SimpleRNN(units=5)(inputs)
model = tf.keras.Model(inputs, layer)

print("Original:")
for w in model.weights: print(w.name)
print()

cloned = tf.keras.models.clone_model(model)

print("Cloned:")
for w in cloned.weights: print(w.name)
print()

tf.keras.models.save_model(model, 'save')
saved = tf.keras.models.load_model('save')

print("Saved:")
for w in saved.weights: print(w.name)

This produces:
Original:
simple_rnn/simple_rnn_cell/kernel:0
simple_rnn/simple_rnn_cell/recurrent_kernel:0
simple_rnn/simple_rnn_cell/bias:0

Cloned:
simple_rnn/simple_rnn_cell_1/kernel:0
simple_rnn/simple_rnn_cell_1/recurrent_kernel:0
simple_rnn/simple_rnn_cell_1/bias:0

Saved:
simple_rnn/simple_rnn_cell/kernel:0
simple_rnn/simple_rnn_cell/recurrent_kernel:0
simple_rnn/simple_rnn_cell/bias:0

As you can see, the cloned model has simple_rnn_cell_1 instead as simple_rnn_cell as name. When using other layers, i.e., Conv the weight names are correct. The problem occurs with all types of RNN layers (SimpleRNN, LSTM and GRU).
Describe the expected behavior.
The names are set correctly ;)
Contributing.

Do you want to contribute a PR? (yes/no): no -> I don't think I know enough of Keras internal to contribute here.
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing): To me it seems the rnn_cell.name attribute needs to be put into the RNN's config, so when cloning the model it gets set properly, and not the automatic enumeration method is triggered.

In the model.summary() function's output the names of the layers are the same. The error shows up only when we print the name of the layers.

Yes. The reason is, that model.summary() shows the name of the keras.layers.[LSTM,GRU,SimpleRNN] class. But all of them have a member cell that is generating the weights see here: https://github.com/keras-team/keras/blob/master/keras/layers/rnn/lstm.py#L533
And cell_kwargs doesn't have a name field, so the names for the cell always get auto-generated.

@mergian  Could you point me to where the cell names get auto generated while using weights.name attribute?

Alternativly, the name could always be name='cell', as the name of the parent LSTM/GRU/SimpleRNN is already unique within the model. So it would be [model_name]/[rnn_name]/cell/[weight_name].

@gowthamkpr,
I was able to reproduce the issue on tensorflow v2.9, v2.11 and nightly. Kindly find the gist of it here.


--ephemeral should be the default?

I personally only use this mode since I want to easily clean the server state for testing.
Wondering if others share this preference..

I think it's reasonable to have a default of file persistence. Even if it wasn't reasonable, it's the current expectation by the many users of this binary, no need to change it now. What's the harm of providing the single CLI arg? Especially compared to harm of incompatibly changing everyone's default to stop persisting to disk.

Based on 0 data, I gather that the majority of users do not want persistence by default.
Reasons that could back my theory:

temporalite is often used in CI where ephemeral is a better default
defaulting to persisting in a non-user supplied location could lead to surprises when restarting and finding workflows being scheduled and test workflow IDs being taken
current issue with missing permissions to write to the default location (reported by some Windows users) would be entirely avoided
easier to upgrade versions that require schema changes

As far as breaking compat, the implication isn't too bad, it's not like people lose their data.

I gather that the majority of users do not want persistence by default.

I actually agree with this. But having data not persisted should still be opted into I think so it's clear.
Regardless, I just don't see why it's so important to change the current default instead of leaving it the way it always has been. Is there something that is causing this issue to be opened? Are there complaints or ergonomics issues for anyone's setup? Or is it just a random idea to change existing default? If the latter, there is no benefit over opting into data loss.
If the default option of using a file is a problem, we can force them to choose, but changing the default to loss of data seems like you're only causing trouble to save a few CLI arg characters.

it's not like people lose their data.

Yes they do.

I gather that the majority of users do not want persistence by default.

I actually agree with this. But having data not persisted should still be opted into I think so it's clear to the user.

I also agree that the majority are probably using the ephemeral mode. But I also think it's important that any non-durable usage is self-documenting. This is why there is no short form of the --ephemeral flag and no environment variable to set it by default (which I'm just now realizing we should add a code comment about).
Although it's not currently recommended, my vision is for Temporalite to be stable enough for small-scale production usage in addition to CI and local dev. I don't think we should ship defaults that cause users to second-guess whether their configuration could become unsuitable for production at any time.

That said we could always add a new subcommand for convenience (temporalite yolo??) which is like start but defaults to ephemeral, creates a default namespace for you, and is explicitly for these throwaway use cases.

temporalite start-ephemeral I think would be a great compromise here.

it's not like people lose their data.

What I meant by this is that if they already had a DB, they upgrade and ephemeral is the default, the data in their DB is preserved.
I have no strong opinion, feel free to close this issue, I brought it up as a suggestion.
I don't think there's that much value in a "yolo" or "start-ephemeral" command, it doesn't save much. Having the explicit params at least informs the user what's going to happen (creating a default namespace and opting into ephemeral mode).

if they already had a DB, they upgrade and ephemeral is the default, the data in their DB is preserved.

I think the concern is not so much about losing the old data, but that you could conceivably upgrade and then not notice that new workflow executions are not being persisted until the next restart.
I'll go ahead and close this for now, but definitely happy to entertain new subcommands in the future if we think they bring significant value.


README example is mutable

I ran the first code example in a Node 4.1.1 console and everything that should not have mutated did. What could I be missing?
var Immutable = require('seamless-immutable');
var array = Immutable(["totally", "immutable", {hammer: "Can’t Touch This"}]);

array[1] = "I'm going to mutate you!"
array[1] // "I'm going to mutate you!"

array[2].hammer = "hm, surely I can mutate this nested object..."
array[2].hammer // "hm, surely I can mutate this nested object..."

for (var index in array) { console.log(array[index]); }
// "totally"
// "I'm going to mutate you!"
// { hammer: "hm, surely I can mutate this nested object..." }

JSON.stringify(array) // '["totally","I'm going to mutate you!",{"hammer":"hm, surely I can mutate this nested object..."}]'

I have tried similar in Node 4.1.1, Node 0.12.7 and babel-node running on 4.1.1. I have also explicitly used an IIFE to ensure strict mode.
var list = Immutable([1,2,3])
list.pop()
console.log(list) // => [1,2]

I've run into the same issue myself... and this issue https://github.com/rtfeldman/seamless-immutable/issues/50 seems related

Many thanks!


igGrid - Unable to cancel an event defined in markup

Description
Unable to cancel an event if the event is declared in your template.
Template:
<ig-grid [(widgetId)]='id' [(options)]="gridOptions" [(dataSource)]="messages" "primaryKey]="'messageId'" >

<column [key]="'messageId'" [headerText]="'message Id'" [dataType]="'string'" [hidden]="'true'"></column>
<column [key]="'englishText'" [headerText]="'English Text'" [dataType]="'string'"></column>
<column [key]="'translatedText'" [headerText]="'Translated Text'" [dataType]="'string'"></column>

<features>
<updating  [editMode]="row" [showDoneCancelButtons]="true"
 (editRowEnding)="editRowEnding($event)" ></updating>
</features>
</ig-grid>

Component:
public editRowEnding(e, ui) {
          return false;
  }

Steps to reproduce

Define a grid with the updating features in the template
Assign an event-handler like rowEnding to the feature
Return false from the event handler to cancel the event

Result
Unable to cancel an event declared in a template.
Expected result
According to the api documentation, an event is cancelled by returning false in the event handler.

Attaching sample that reproduces the issue.
igGridUpdating_CancelEvent.zip

We use EventEmitter to emit the custom component events, however those don’t return the result from the emitted event handler so you cannot cancel the event in that way.
The event passed as part of the arguments however is the custom widget event, so you can directly access and cancel it using preventDefault(), for example:
onEditRowEnding = (args): boolean => {
args.event.preventDefault();
}
Let me know if that solves your issue.

Closing the issue @tommye  reopen the issue if you have any further questions :)


Cannot read the response

I'm on Mac OS X El Capitan and I'm stuck with this problem:
PHP Fatal error:  Uncaught Http\Client\Exception\NetworkException: Cannot read the response in /Users/smacalalag/Code/project/vendor/php-http/socket-client/src/ResponseReader.php:56
Stack trace:

My code:
$docker = $container->get('docker');

$containerManager = $docker->getContainerManager();

die(print_r($containerManager->findAll()));

Here is my docker client config in Symfony:
    docker_client:
        class: Docker\DockerClient
        arguments:
            - remote_socket: "%docker_host%" # tcp://<IP_ADDRESS>:2376'
            - ssl:                    true

Can someone please help and point me in the right direction. The exception doesn't explain much.
Thanks!
P.S.
I tried this on my machine and it worked.
wget --no-check-certificate --certificate=$DOCKER_CERT_PATH/cert.pem \
     --private-key=$DOCKER_CERT_PATH/key.pem \
     https://YOUR_VM_IP:2376/images/json -O - -q

Okay, I think I am getting there but this just return an empty array.
$client = new Docker\DockerClient([
    'remote_socket' => 'tcp://<IP_ADDRESS>:2376',
    'ssl' => true,
    'stream_context_options' => [
        'ssl' => [
            'cafile' => '/Users/smacalalag/.docker/machine/machines/default/ca.pem',
            'local_cert' => '/Users/smacalalag/.docker/machine/machines/default/cert.pem',
            'local_pk' => '/Users/smacalalag/.docker/machine/machines/default/key.pem',
        ]
    ]
]);

Try to use the following config
docker_client:
        class: Docker\DockerClient
        arguments:
            -
                remote_socket: "%docker_host%" # tcp://<IP_ADDRESS>:2376'
                ssl:    true
                stream_context_options:
                    ssl:
                        cafile: %DOCKER_CERT_PATH%/ca.pem
                        local_cert: %DOCKER_CERT_PATH%/cert.pem
                        local_pk: %DOCKER_CERT_PATH%/key.pem
                        peer_name: boot2docker

Where DOCKER_CERT_PATH is the directory

Argh too late xD
Empty array is normal if you don't have any running container, use the all parameter of the findAll method to get all containers.

This ssl config example is missing in the docs BTW, will add that in the near futur

I missed that - I was supposed to be looking at the images. I'm glad you point my oversight. I got it working now.
Thank you, sir.

Want to keep this open for side note on documentation, thanks for the report !

Closing this as this issue is rather old.


docs(ref): Specify 'rust_version' in Index format

See rust-lang/crates.io#6267

Do we want to mention that is not currently available from the publish JSON?
Do we want to mention that it is currently not read by cargo and is optional?
Both of which may change in the future.

crates.io 503: https://github.com/rust-lang/cargo/actions/runs/4810738015/jobs/8563779797?pr=12040
deployment history: https://rust-lang.zulipchat.com/#narrow/stream/318791-t-crates-io/topic/deployments/near/352857644
cc https://github.com/rust-lang/crates.io/issues/6385

Do we want to mention that is not currently available from the publish JSON?

As there is a section to call out differences between the Publish API and the Index, I've noted it there

Do we want to mention that it is currently not read by cargo and is optional?

I do mention it is optional.  We don't have a location to point people to yet and cargo's use of it which makes me hesitant to do so.

yeah, same thing as I mentioned yesterday, during deploys of crates.io itself apparently we are getting more and more 503s these days :-/

Thanks for the clarification.
@bors r+

:hourglass: Testing commit 4dd2b28e3e96974b8cad1a3961808a3c62c472f4 with merge 284fd3f0f13b4d0c608c36c920ad1660c05f6e85...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 284fd3f0f13b4d0c608c36c920ad1660c05f6e85 to master...


13.0.1 without the dependency on clang-activation with the same version

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Depends on https://github.com/conda-forge/staged-recipes/pull/18113


Loading Stipple affects convertion of JSON3.Dict into Dict

After loading Stipple package, the behavior of conversion of a JSON3.Dict object into a Dict is changed such as the type of keys changes from Symbol to String.
Original behavior:
using JSON3

data = Dict(
    :hello => 1.1,
    :hi => 2.2)

JSON3.write("test.json", data)

julia> raw = JSON3.read("test.json")
JSON3.Object{Vector{UInt8}, Vector{UInt64}} with 2 entries:
  :hi    => 2.2
  :hello => 1.1

julia> dict = Dict(raw)
Dict{Symbol, Any} with 2 entries:
  :hi    => 2.2
  :hello => 1.1

Modified behavior:
using JSON3
using Stipple

data = Dict(
    :hello => 1.1,
    :hi => 2.2)

JSON3.write("test.json", data)

julia> raw = JSON3.read("test.json")
JSON3.Object{Vector{UInt8}, Vector{UInt64}} with 2 entries:
  :hi    => 2.2
  :hello => 1.1

julia> dict = Dict(raw)
Dict{String, Any} with 2 entries:
  "hi"    => 2.2
  "hello" => 1.1

The above change in the type of Dict keys seems like an undesirable side effect.
I first thought it may be related to StructTypes, but only loading that package instead of Stipple still keeps the Dict keys as symbols.

Good finding. It's related to Genie, though.
julia> jd = JSON3.write(data) |> JSON3.read
JSON3.Object{Base.CodeUnits{UInt8, String}, Vector{UInt64}} with 2 entries:
  :hi    => 2.2
  :hello => 1.1

julia> Dict(jd)
Dict{Symbol, Any} with 2 entries:
  :hi    => 2.2
  :hello => 1.1

julia> using Genie

julia> Dict(jd)
Dict{String, Any} with 2 entries:
  "hi"    => 2.2
  "hello" => 1.1

typing
julia> Dict(jd,

plus TAB key reveals the culprit
Dict(o::JSON3.Object) @ Genie.Router C:\Users\helmu\.julia\packages\Genie\XpFvB\src\Router.jl:832

It is definitely type piracy and should be removed. Are you going to raise this in Genie or should I do it?

It's fixed in Genie. I propose, we leave this open until the next Genie version is registered.

@hhaensel I tagged a new Genie version yesterday: https://github.com/GenieFramework/Genie.jl/releases/tag/v5.18.2

I confirm that the issue has been solved per my tests - closing.


jenkins-cli commands don't work when Jenkins authentication is turned on

I have Jenkins' own database authentication turned on with matrix based security and the ansible script can't install extensions or restart Jenkins:
failed: [<IP_ADDRESS>] => {"changed": true, "cmd": ["java", "-jar", "/opt/jenkins/jenkins-cli.jar", "-s", "http://localhost:8080", "safe-restart"], "delta": "0:00:00.866460", "end": "2014-12-10 15:55:43.202089", "rc": 1, "start": "2014-12-10 15:55:42.335629"}
stderr: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission

Could we have the ability to provide a username and password to use for these commands? This, and/or public key auth:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI#JenkinsCLI-WorkingwithCredentials

any plans to fix that? and it would be great to configure security using that role too

see https://github.com/ICTO/ansible-jenkins/issues/61

I have worked around this by setting up an SSH key and adding  -ssh -user {{ jenkins_admin_user }} to the end of jenkins_cli_cmd . But I don't know how to automate generating an ssh key and adding it to Jenkins config.


Remove button icon

Is it possible to change the icon of the remove button on the tag?

Any thoughts on the above question ?

@poojakaluskar have u find the solution?


.NET 6 Build Environment Variables

In keeping with the build environment naming conventions, we need NSwagExe_Net60 and NSwagDir_Net60 to be defined in src/NSwag.MSBuild/NSwag.MSBuild.props. Now that .NET 6 in in RC stage, it would be great if this could be made available sooner rather than later.
Thanks!

@RicoSuter @thenadz Looks like this exists now, this item should be closed in case others think the issue is still outstanding.


Mutable State and History Events may be out of sync when DB timeout happens

Version of Cadence server, and client(which language)
This is very important to root cause bugs.

Server version: 0.22.x

Describe the bug
When DB timeout happens, mutable state and history events of a workflow may be out of sync which will cause history corruption. Here is an example of history corruption,
{
    "branch_id": "ab57643b-b75e-4be1-b29b-6ba1290f986c",
    "node_id": 446,
    "payload": "WQ8ACgwAAAABCgAKAAAAAAAAAb4KABQWkBcMF6WZ+AgAHgAAAAUKACMAAAAAAAAAAAoAJAAAAAACYAcPDABaCgAKAAAAAAAAAbwLABQAAAAmMTE4QGFnZW50NzQ2OS1kY2E4QGNhZGVuY2UtYmVuY2gtdGwtMTQLAB4AAAAkNTg2ZjFhODctMDE4ZC00ZWY2LTk0NDMtOTk2YTk3ODNkNzJiAAAA",
    "payload_encoding": 1,
    "shard_id": 5404,
    "tree_id": "ca82b07a-2fab-4eda-a70d-844a49b24f6a",
    "txn_id": -39847696
}
{
    "branch_id": "ab57643b-b75e-4be1-b29b-6ba1290f986c",
    "node_id": 446,
    "payload": "WQ8ACgwAAAACCgAKAAAAAAAAAb4KABQWkBcJQ9uEWwgAHgAAAAcKACMAAAAAAAAAAAoAJAAAAAACYAcKDABuCgAKAAAAAAAAAbwKABQAAAAAAAAAAAgAHgAAAAEAAAoACgAAAAAAAAG/CgAUFpAXCUPbqrkIAB4AAAAECgAjAAAAAAAAAAAKACQAAAAAAmAHCwwAUAwACgsACgAAABNjYWRlbmNlLWJlbmNoLXRsLTE0AAgAFAAAAB4KAB4AAAAAAAAAAAAAAA==",
    "payload_encoding": 1,
    "shard_id": 5404,
    "tree_id": "ca82b07a-2fab-4eda-a70d-844a49b24f6a",
    "txn_id": -39847692
}
{
    "branch_id": "ab57643b-b75e-4be1-b29b-6ba1290f986c",
    "node_id": 448,
    "payload": "WQ8ACgwAAAABCgAKAAAAAAAAAcAKABQWkBcUpt4qkAgAHgAAABIKACMAAAAAAAAAAAoAJAAAAAACcAAADAC+CwAKAAAAAzI1OQoAFAAAAAAAAAGdAAAA",
    "payload_encoding": 1,
    "shard_id": 5404,
    "tree_id": "ca82b07a-2fab-4eda-a70d-844a49b24f6a",
    "txn_id": -40894465
}
{
    "branch_id": "ab57643b-b75e-4be1-b29b-6ba1290f986c",
    "node_id": 449,
    "payload": "WQ8ACgwAAAABCgAKAAAAAAAAAcEKABQWkBcY6nprvwgAHgAAAAUKACMAAAAAAAAAAAoAJAAAAAACcAADDABaCgAKAAAAAAAAAb8LABQAAAAmMTEwQGFnZW50OTM5Mi1kY2E4QGNhZGVuY2UtYmVuY2gtdGwtMTQLAB4AAAAkNWViZDczM2QtZjU3Zi00OGEzLThlNWItNGZkM2MyYjgzZjI3AAAA",
    "payload_encoding": 1,
    "shard_id": 5404,
    "tree_id": "ca82b07a-2fab-4eda-a70d-844a49b24f6a",
    "txn_id": -40894468
}

The payloads of the data are
{"eventId":446,"timestamp":1625824806184524280,"eventType":"DecisionTaskStarted","version":0,"taskId":39847695,"decisionTaskStartedEventAttributes":{"scheduledEventId":444,"identity":"118@agent7469-dca8@cadence-bench-tl-14","requestId":"586f1a87-018d-4ef6-9443-996a9783d72b"}}
+++++++++++++++++++++++++
{"eventId":446,"timestamp":1625824794041353307,"eventType":"DecisionTaskTimedOut","version":0,"taskId":39847690,"decisionTaskTimedOutEventAttributes":{"scheduledEventId":444,"startedEventId":0,"timeoutType":"SCHEDULE_TO_START"}}
{"eventId":447,"timestamp":1625824794041363129,"eventType":"DecisionTaskScheduled","version":0,"taskId":39847691,"decisionTaskScheduledEventAttributes":{"taskList":{"name":"cadence-bench-tl-14"},"startToCloseTimeoutSeconds":30,"attempt":0}}
+++++++++++++++++++++++++
{"eventId":448,"timestamp":1625824842947111568,"eventType":"TimerFired","version":0,"taskId":40894464,"timerFiredEventAttributes":{"timerId":"259","startedEventId":413}}
++++++++++++++++++++++++
{"eventId":449,"timestamp":1625824861261294527,"eventType":"DecisionTaskStarted","version":0,"taskId":40894467,"decisionTaskStartedEventAttributes":{"scheduledEventId":447,"identity":"110@agent9392-dca8@cadence-bench-tl-14","requestId":"5ebd733d-f57f-48a3-8e5b-4fd3c2b83f27"}}

The first history event branch overwrites the second history event branch, but the following history event follows the second history event branch. So as a result, eventId 447 is missing in workflow history. The expected result is that the first event branch does NOT overwrite the second event branch.
Here is a theory explaining how this happens:
event id 444 decision task scheduled to start timed out, event id 446 and 447 is created
TX1: History event persisted
TX2: MS persist timed out -> but still in progress in database
Close shard

Reload shard, does NOT see next event id = 448, because TX2 is not committed, and next event id = 446
A decision started event arrives, and we set the event id = 446
TX3: History event persisted
TX4: Could not update MS because shard is still being locked by the phantom transaction
Close shard

TX2 committed
Reload shard, because TX2 is commited, not the next event id = 448, but the history events does NOT contain event id 447 (the branch created by TX1 was overwritten by TX3)
TX5: History event persisted and History is corrupted
TX6: MS persisted

My understanding (at least for cassandra based persistence implementation)
TX2 is a CAS operation on range_id field. When shard is reloaded, then range_id will be increased. So either TX2 succeeds before the shard is reloaded or it is guaranteed to fail since the range_id is changed.

The issue is because we allow a closed shard to append history events to a workflow. And it was fixed by https://github.com/uber/cadence/pull/4547


Fix DebuggerMarshalls errors while profiling

Fixed check for array size before func_size: when func_size is 0 there's only 1 entry left and not 3.
Fixes #43795

Thanks!


Would it be appropriate to use Resque::Scheduler for requeueing?

In my domain I use Whenever to spawn a list of about 20 resque jobs every 15 minutes.  Most of those jobs finish in <5 seconds, but there are 1 or 2 that can take much longer (anywhere from 30 seconds to 2 hours) There are a couple issues I'm having with this code and the way it requeues jobs.  Let's say I have just enqueued all 20 jobs, and all of them are completed, except My::LongJob.  It is still being processed, and will take 2 more hours.  I have 4 workers total, and 3 are idle.  15 minutes later, those same 20 jobs are each queued again.
...
else
  sleep(requeue_perform_delay)
  Resque.enqueue(self, *args)
  raise Resque::Job::DontPerform
end

If I leave the requeue_perform_delay at the default 1 sec, when the other jobs finish, My::LongJob 2 will continually be picked up by the free worker, which will check the lock, pause 1 sec, and then requeue.  If I watch the stats in resque it'll add these jobs to the "processing" count, so that number will go up at the rate of 1/sec, even though they are just failing/requeuing.

If I set the perform delay higher, like 60 seconds, then the worker will be blocked while it sleeps.  This means that when I requeue the other shorter jobs, they need to wait for the worker to finish the delay.  If I had 2 different jobs that each took a long time, I might have 4 workers blocked on these 2 jobs, so any other faster jobs would wait in the queue for up to a minute.

So, would it be appropriate to interrogate Resque::Scheduler, and if it's present queue the job up for a later time?  Something like:
if Resque.redis.msetnx lock_result.zip([true]*lock_result.size).flatten
  lock_result.each do |lock|
    Resque.redis.expire(lock, worker_lock_timeout(*args))
  end
else
  if defined? Resque::Scheduler
    Resque.enqueue_in(requeue_perform_delay, self, *args) # run a job in 5 days
  else
    sleep(requeue_perform_delay)
    Resque.enqueue(self, *args)
  end
  raise Resque::Job::DontPerform
end

This would offload the sleep onto the scheduler process, instead of the workers.  Happy to PR this, but wanted to get some thoughts first.

Interesting problem, and thanks for taking the time set it out it so clearly!
I agree that workers with self.requeue_perform_delay should not be sleeping and instead take other jobs. It is better to use Resque.enqueue_in instead of sleep.
Secondly, even when enqueue_in is used, the processing count will go up, because you will not be always be able to estimate the minimum amount of delay required. It could be possible to ignore jobs that issued a Job::DontPerform in before_perform in the statistics, but I guess it is not important to everyone. It could also be helpful to see the processing count go up as long as you know what caused it. It is probably best to keep the code as simple as possible and just interrogate Resque::Scheduler like you suggested.
Looking forward to the PR!

@theSteveMitchell
Just checking in, did you have time to take a look at this?

Thanks for the reminder!  Yes I tried the approach and it seems to work, the code is very easy but the tests are hard :frowning: Give me another week or two for a PR :smile:

Ok, thank you! :+1:

+1 for this feature to be incorporated

Closed because @bogdanovich added this: https://github.com/bartolsthoorn/resque-workers-lock/pull/9


Algorithm to pick the normalization point

At the moment the normalization point is hardcoded.
Instead, based on the selected regions, we could try to find the earliest continous patch with smallest stdev to normalize against.
This would mean that a normalization point between Estonia and Italy would be much earlier than Italy, China and USA.

fixed with the rewrite merge


Drop support for Python 3.6/3.7 and extend test matrix to Python 3.11/3.12

I've dropped support for all EOL versions of Python (3.6 and 3.7) and extended the CI test matrix to run tests against Python 3.11 and 3.12.

Black wasn't compatible with the resolved version of Click, so I updated it to the latest available version and ran it on the code base.

This will also enable f-strings 🔥🔥

Should we just replace flake, isort etc with ruff? Wdyt?

The old Flake8 version isn't compatible with Python 3.12, so I've updated Flake8 to the latest available version. Since Flake8 requires Python 3.8.1+, I added a corresponding marker to Flake8, as this constraint originates only from a dev dependency and shouldn't leak into runtime constraints.

Should we just replace flake, isort etc with ruff? Wdyt?

Yes, perhaps in a follow-up PR? Just to avoid mixing concerns.

In fact, there's more I'd regarding cleanup. IMO, dev dependencies should be pinned, and to support maintenance of those pins, I'd add Dependabot or Renovate to assist. Just an idea, it's up to you of course.


Make HTML TestUtils wait functions cancellable

Replace suspendCoroutine with suspendCancellableCoroutine to allow timeout cancellation of waitForRecompositionComplete and waitForChanges
Fixes #3317

Test: waitForChanges_cancels_with_timeout, waitForRecompositionComplete_cancels_with_timeout

@eymar @igordmn


'laravel-echo-server' is not recognized as an internal or external command, operable program or batch file.

After installing npm install -g laravel-echo-server command
when i want to run this above command "laravel-echo-server init"
it shows the following error
'laravel-echo-server' is not recognized as an internal or external command,
operable program or batch file.
any help????

Hey there, this issue was opened a while ago. I'm going to close this issue, if this issue still exists, please open a new issue or open a Pull Request.


Update ListOperation.php

Use built in method.

A new inspection was created.

It is a duplication of https://github.com/Laravel-Backpack/CRUD/pull/3125

The inspection completed: 5 updated code elements


Cv2 pytorch

Allows for the use of OpenCV in the PyTorch image.
https://app.clickup.com/t/1250339/DATA-522

Task linked: DATA-522 fix cv2 install in PyTorch image


Remove duplicate see also reference to BIO_s_mem.

[x] documentation is added or updated

Documentation fix only.
Please don't merge this, I'd like it to be a benign test of my merge capabilities after approval.

alpha

(errrr...  "alpha"?)

Alpha is a beginning.
Omega is the end.

That was kind Revealing ;-)


unexpected slowness (non-recursive)

There are files with terms in this directory (to be root) in the commit https://github.com/groupoid/om/tree/ac585365a69d8dcd6c43a31a424486d5718c2522/priv/barbers/Hurkens/lambda (also available as a gist here https://gist.github.com/zraffer/dc90b5d076eda6156277 ), a few of which take a very long time to typecheck and normalize. Especially ShadowTrans and Shadow-MkOk. The terms do not use recursion and need just a few reductions to normalize. Moreover, usage of this terms in simple expressions (call id for example --- file test/Shadow-MkOk as well as othes files in that directory) take much more time, so typechecking seems to have exponential time complexity in such cases. Therefore long typechecking time for simple terms makes morte unusable for development.
Older versions (since 1.1) from hackage were tested producing the same time results.
However fully normalized versions of the terms (from morte output, at https://github.com/groupoid/om/tree/ac585365a69d8dcd6c43a31a424486d5718c2522/priv/barbers/Hurkens/output ) have got typechecked immediately (no slowness).

I have a pretty good guess at what the problem is and how to fix it.  The issue is (probably) this line of code:
https://github.com/Gabriel439/Haskell-Morte-Library/blob/master/src/Morte/Import.hs#L285
Whenever morte embeds a remote expression morte type-checks the expression first, for two separate reasons:

First, morte needs to verify that the imported expression is closed (i.e. no free variables).  morte requires this invariant in these two places:
https://github.com/Gabriel439/Haskell-Morte-Library/blob/master/src/Morte/Core.hs#L488
https://github.com/Gabriel439/Haskell-Morte-Library/blob/master/src/Morte/Core.hs#L510

Second, morte type-checks expressions upon import to give better error messages.  This is how morte can give you the import trace to the expression in the import graph that failed to type-check like:
morte:
⤷ #foo
⤷ #bar
{some type error here}

However, in the worst case this type-checking of imports can lead to quadratic behavior, type-checking the exact same expression multiple times.
The fix is simple: instead of type-checking imports we only verify that they are closed expressions.  This means that error messages will be a little bit worse for imports, but we can always re-implement that later more efficiently once I add support for annotating expressions with source/import locations.
This also explains why fully resolved expressions are type-checked much more quickly.  It's actually not the normalization process that's slow, but rather the import resolution step that is slow.
A really easy way to verify that this is indeed the problem for you is to just delete the type-checking step that I linked to above and check to see if type-checking gets much faster.  Later I can fix this code to only check that the import is closed (or you can contribute the pull request if you get to it before me).

Actually, I found an even better solution, which was to just not even type-check an import if it was already cached (since being in the cache implies that it was already type-checked).  See the associated commit for more details

$ time ./morte < Shadow-MkOk
real    3m29.352s
user    3m26.926s
sys    0m1.753s

@Gabriel439 , did you checked your fix on the proposed gist? It seems that fixed Morte is more slow.

No, I haven't checked on the proposed gist.  However, the slowdown is unusual since it should always be doing strictly less work.  See the diff to see what I mean.
Are you checking exactly before and after that commit (i.e. on ba318b262240fe1aafb89c8ba91737fe899d6249 vs 6b363de017adc58543c77868d3955b176728729f)?  The reason I ask is that I made another change a few commits earlier that might also affect performance, which was changing how Context manipulation worked, and I want to make sure that's not causing the performance degradation.

Okay, so the latest commit to add support for caching was not responsible for the slowdown; it had no effect on speed in my test:
$ time morte < ShadowTrans # after caching
...
real	2m33.028s
user	2m32.568s
sys	0m0.512s
$ time morte < ShadowTrans # before caching
...
real	2m32.917s
user	2m7.512s
sys	0m25.488s

I'm now testing whether or not the recent changes to the Context type are responsible for the slowdown.

Yep, it looks like the changes to Context handling contributed to the slowdown.  Here is the timing when I switch to the old Context implementation:
$ time morte < ShadowTrans
...
real	0m57.867s
user	0m57.692s
sys	0m0.196s

I did this change to Context to improve the time complexity of some expensive Context-related operations (such as for encoding strings) but it looks like it gave a constant factor slowdown.  I'll see if I can get it to match the old performance.

Me too removed caching as it has no drastical effect on tests running.

BTW:
$ time om type a "#ShadowTrans" , mode src-hurkens
real	0m4.972s
user	0m3.897s
sys	0m1.666s

Alright, so I reverted back to the old Context implementation on master so that it should at least be the same speed as before.
I'm still investigating the source of the slowness and profiling has narrowed this down to the type-checking step


Check sum url from env if set in install.sh

Hi team.
Check sum url is located in release page same place as executable binary.
I think this may be not safe,  because if someone can be modify binary, then they possibly can modify checksum.txt too.
That why I want to set checksum url by myself,  and verify it in install.sh (install.sh is so usefull. i want to keep using it)
Maybe there is another good way.
and Im not good at shell, so please point if it is wrong.

[x] Updated Unreleased section in CHANGELOG or it's not notable changes.

Thanks!
Sorry i didnt notice it.
Close this PR for now 🙏


Simplify migrations

Opening this to test junit formatter by seeing if it works fully if the PR is done from the same repo instead of from an external fork.

Codecov Report
Patch and project coverage have no change.

Comparison is base (a6876a2) 6.24% compared to head (9a7d95d) 6.24%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #20   +/-   ##
=====================================
  Coverage   6.24%   6.24%
=====================================
  Files         20      20
  Lines       1713    1713
=====================================
  Hits         107     107
  Misses      1606    1606

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


issue 6: WantToHelp added

#6 please i have completed the issue

#4 i have also solved this issue

Hello @danpercic86 the changes have been resolved, review and let me know if they are okay


feat: adds section to device info for certificate information and allows for downloading of certs

PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

Web ui should look like this with the automatic TLS cert and one wifi configuration

Some choices that might need to be changed include:

ID for key is the first 10 chars of the key
ID for a cert without a common name is the first 10 chars of the cert
File extensions for downloads are .pem for certs and .pub for keys

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

GitHub release
v3.18.0

Your semantic-release bot :package::rocket:


Solution - Microsoft Defender Threat Intelligence missing 4 playbooks

Describe the bug
The content hub solution "Microsoft Defender Threat Intelligence" only has 4 playbooks but GitHub solution itself reports 8 playbooks.
To Reproduce
Steps to reproduce the behavior:

Go to Content Hub.
Install content solution 'Deploy the content hub solution "Microsoft Defender Threat Intelligence" and you will get 4 playbooks.'
Go to automation -> Playbook templates.
Filter for 'MDTI'.
Output is 'MDT-Automated-Triage', 'MDTI-Intel-Reputation', 'MDTI-Base', 'MDTI-Data-WebComponents'.

Expected behavior
Output should have the following playbooks

MDT-Automated-Triage
MDTI-Intel-Reputation
MDTI-Base
MDTI-Data-WebComponents
MDTI-Data-Cookies
MDTI-PassiveDns
MDTI-PassiveDnsReverse
MDTI-Trackers

See Playbook folder in GitHub - https://github.com/Azure/Azure-Sentinel/tree/master/Solutions/Microsoft Defender Threat Intelligence/Playbooks
Screenshots

Hi @MikeP1375, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 01-02-2024. Thanks!

Hi @MikeP1375, I hope you are doing well. We have created a pull request by including those playbooks in the solution. The changes will be reflected in the upcoming version of the solution.
Thanks!


add a simpler solution to Priority Queue

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Existing solution is a bit overkill (reduce + temp array).
This PR introduces, I believe, a shorter and simpler to understand solution.
Thanks!

@bonham000 since it was likely you who created this original challenge, would you be interested in taking a look at @JoolsMcFly's solution and merging if you think it's an improvement?

I actually did not write this one but I agree with OP and this passes tests — merging.

Awesome, thanks!

unsubscribe
On Thu, Mar 23, 2017 at 2:56 AM, Jools<EMAIL_ADDRESS>wrote:

Awesome, thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/pull/14013#issuecomment-288632817,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVkc33nmOOXZindmFDbMJzW-bKLcCTtWks5rohemgaJpZM4MiLk_
.

@mooseworx
looks like you may have accidentally subscribed to all notifications for the FreeCodeCamp repository. To stop receiving notifications please visit the subscriptions page and select "Not watching". Additionally, you can visit the GitHub Help page on managing notification delivery methods for more help.
We are sorry for your inconvenience!


[SPARK-44928][PYTHON][DOCS] Replace the module alias 'sf' instead of 'F' in pyspark.sql import functions

What changes were proposed in this pull request?
This PR proposes the alias name sf instead of F for pyspark.sql.functions alias in public documentation:
from pyspark.sql import functions as sf

This PR does not change the internal or test codes as it's too invasive, and might easily cause conflicts.
Why are the changes needed?
from pyspark.sql import functions as F

isn’t very Pythonic - it does not follow PEP 8, see Package and Module Names.

Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves
readability. Python packages should also have short, all-lowercase names, although the use of underscores
is discouraged.

Therefore, the module’s alias should follow this. In practice, the uppercase is only used at the module/package
level constants in my experience, see also Constants.
See also this stackoverflow comment.
Does this PR introduce any user-facing change?
Yes, it changes documentation so users
How was this patch tested?
Manually checked.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @zhengruifeng @LuciferYang @allisonwang-db

cc @ueshin and @itholic too FYI

I think we should leave them for now. I initially changed all .. then realised that there are too many files being touched.. so I changed them back. That will cause conflicts too much when we backport, etc. Let's leave them for now.

I think we should leave them for now. I initially changed all .. then realised that there are too many files being touched.. so I changed them back. That will cause conflicts too much when we backport, etc. Let's leave them for now.

OK ~

merged to master


Physical Flow: soft code transport types into enum-value table

Could be problematic as we currently have aliases defined against them which willl also need to become soft-coded.  Unfortunately we can't easily achieve this via entity-alias as it needs entities and enum values aren't entities (they have no identifying entity ref).
Options:
Abort
Abort this change.
Ignore aliases
This would reduce the functionality of the  bulk importer
Hardcode aliases
Makes this change a little redundant
Add aliases in a single column on the entity_enum table
Makes the task fairly simple but may be hidden gotchas and means we will always need a decoder to use properly
Promote entity_enum to be a full entity
This means adding a generated long PK.  Quite simple and would allow us to then use entity_alias
Add a new table for entity_enum_alias
Would look a bit like: enum_kind | enum_value | alias
Votes ?

We should probably go with the 'promote' option.  Probably the most work but may lead to a more generally useful way of interacting with enums.

Is the promote option to promote enum_value to a full entity? There seems to be a typo in the proposal.
My vote would be to add a new table entity_enum_alias and store the aliases there.
In my view, entity_alias is meant to store and display aliases (alternate names) for an entity, but entity_enum_alias will work the opposite way, it will be used to convert multiple aliases to a single enum value.

Good point happy to implement this way.  Anyone else got an opinion ?

The case for a full entity ref would be to allow roll up by transport type for example, essentially following a similar approach to existing aggregations. Are we likely to need to do this?

Ok, will go with: add enum_value_alias table  alternative

cascade delete from entity_enum to entity_enum_alias


message_fetch: Allow spectators to access all messages view.

Added some prep commits.

Merged after fixing https://github.com/zulip/zulip/pull/29190#discussion_r1520322060, thanks @amanagr!


Invalid BigNumber value on bridge input

Describe the bug
BigNumber value on bridge input:

Call revert:

Similar to https://github.com/connext/nxtp/issues/2757, It's the response of the calculatedAmountReceived. Can you please verify my input?

See https://github.com/connext/nxtp/issues/2824


Plugin start fails if no java files are found under src directory.

Runner start fails because plugin tries to compile all files under src directory.
Ideally it should still start in case all the step implementations are located in jars as dependencies.

Fixed in commit


Database table configuration either undocumented or doesn't work

Issue Summary
I am trying to use different names for the database tables.  I don't know whether the existing documentation is incomplete or whether the table name configurations are failing.  I tried the most obvious configuration
config.enabled                 = true
config.badge_enabled           = true
config.badge_position          = 'top-left'
config.skip_paths              = []
config.profiled_requests_table = :profiler_requests       # these get errors
config.flamegraphs_table       = :profiler_flamegraphs    # when starting
config.traces_table            = :profiler_traces         # Rails
config.flamegraph_enabled      = true
config.flamegraph_sample_rate  = 0.0125

There was a hint that these 3 configurations were meant to be nested together under 'storage', but there were no examples.   I tried
  config.enabled                 = true
  config.badge_enabled           = true
  config.badge_position          = 'top-left'
  config.skip_paths              = []
  config.storage do |conf|
    conf.profiled_requests_table = :profiler_requests
    conf.flamegraphs_table       = :profiler_flamegraphs
    conf.traces_table            = :profiler_traces
  end
  config.flamegraph_enabled      = true
  config.flamegraph_sample_rate  = 0.0125

This was just a guess, and it allowed me to start up Rails, but in turn I got
PG::UndefinedTable: ERROR: relation "rmp_profiled_requests" does not exist LINE 8: WHERE a.attrelid = '"rmp_profiled_requests"'::regclass ^

Steps to Reproduce

Use the configs above
Observe errors

Technical details

Rails version: rails --version
Ruby version: ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-darwin19]

Just noticed another clue in the config file, and tried this:
  config.storage = RailsMiniProfiler::Storage do |conf|
    conf.profiled_requests_table = :profiler_requests
    conf.flamegraphs_table       = :profiler_flamegraphs
    conf.traces_table            = :profiler_traces
  end

It also failed.

I noticed by poking around in Pry that  there's a RailsMiniProfiler.storage_configuration method, so I tried
  config.storage = RailsMiniProfiler::Storage
  config.storage_configuration.profiled_requests_table = :profiler_requests
  config.storage_configuration.flamegraphs_table       = :profiler_flamegraphs
  config.storage_configuration.traces_table            = :profiler_traces

but that got a response of

`defined method `storage_configuration' for #RailsMiniProfiler::Configuration:0x00007fd342d70e48 (NoMethodError)`

I tried putting this outside of the |config| block:
RailsMiniProfiler.storage_configuration.profiled_requests_table = :profiler_requests
RailsMiniProfiler.storage_configuration.flamegraphs_table       = :profiler_flamegraphs
RailsMiniProfiler.storage_configuration.traces_table            = :profiler_traces

and this gave me

ActiveModel::MissingAttributeError in UcbRailsUser::UsersController#edit
can't write unknown attribute `rmp_profiled_request_id

Thanks for the detailed write-up, it's super helpful! :raised_hands:
You are right, the documentation here is definitely lacking. I looked into this briefly, there seem to be some issues with storage configuration in general at the moment. I think you may be able to get this to work with some small modifications for now:
Try updating your configuration to this:
RailsMiniProfiler.configure do |config|
  config.storage.profiled_requests_table = 'my_new_table_name'
end

Now, there is a bug that results in things breaking here. But it's an easy fix. Using bundle open rails_mini_profiler, you can open the file lib/rails_mini_profiler.rb and update storage_configuration like so:
def storage_configuration
  # remove the last 'configuration' from 'configuration.storage.configuration'
  configuration.storage
end

Regarding the original error you got: Did you run the migrations, and is a table rmp_profiled_requests available? :thinking:
Feel free to open a PR with documentation improvements (if you want). I'll try and get a fix out soon :slightly_smiling_face:

@brandondrew This issue should be resolved in 0.2.0. Documentation has been improved, hopefully it is more clear how storage can be configured. If you face any other issues please do not hesitate to let me know.
Thanks again for contributing to this project! :bow:

I ran into this issue, and upgrading from 0.1-something, I needed to pass an instance to the configuration for storage:
# Use RailsMiniProfiler::Storage::ActiveRecord to store profiles in your Database
- config.storage = RailsMiniProfiler::Storage
+ config.storage = RailsMiniProfiler::Storage.new


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/27 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit dd3b5a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Passing file descriptor numbers to avoid tempfiles

Continuing from https://github.com/Unibeautify/unibeautify-cli/issues/82#issuecomment-426633766

The file descriptor support seemed weird at first but it's starting to grow on me. Tempfiles are the bane of inter-process communication. It's much cleaner to pass everything around with pipes. If we support routing output to arbitrary file descriptors, callers can create a pipe for every kind of output they need, then just assign the pipes to pre-determined file descriptors and tell unibeautify about those fd numbers. No tempfiles ever 🎉

And from https://github.com/Unibeautify/unibeautify-cli/issues/82#issuecomment-431613985

No tempfiles ever 🎉

#82 (comment)

@lassik A goal I share. I'd be open to receiving a Pull Request implementing this. Of course, we need to continue support for Linux, Mac, and Windows.

Linux, Mac and all other unixes are easy - passing around file descriptor numbers has a long history there and the relevant APIs are extremely stable.
After investigating for a bit, I think it can be done the same way one Windows, but not sure if there are any gotchas.

This is actually an implementation detail of each individual beautifier -- not specific to Unibeautify CLI or even Unibeautify core itself. Ideally, we don't use anything except stdin and stdout, however, for too many beautifiers this is not an option 😢. Therefore, this issue is more so a discussion of the best practice for developing beautifiers and then each beautifier which is currently afflicted with temporary files should be migrated towards the best practice.

Ah, I thought people who call our CLI would benefit from having the option to use arbitrary file descriptors of their choosing. I agree that we should definitely call the beautifiers using stdin/stdout/stderr whenever possible. If it works at all (on Windows) then it should be quite easy to implement. It's definitely easy on Unix if Node comes with an OS API of similar scope to e.g. Python.


Bug: onComplete firing before onCurrentPageChanged with 'complete survey' trigger

Are you requesting a feature, reporting a bug or ask a question?
Reporting a bug.
What is the current behavior?
When using the 'Complete survey' trigger on a question, the onComplete event is fired before the onCurrentPageChanged one.
What is the expected behavior?
The correct order should be first onCurrentPageChanged then onComplete .
How would you reproduce the current behavior (if this is a bug)?
See above.
Provide the test code and the tested page URL (if applicable)
Tested page URL:
https://codepen.io/fastclemmy/pen/wyNwOE
Specify your

browser: Firefox
browser version: 58.0.2
surveyjs platform (angular or react or jquery or knockout or vue): jQuery
surveyjs version: 1.0.11

@fastclemmy I have fixed it, by adding a new unit test and fixed it.
However, I'm not sure you will like the solution. Because onCurrentPageChanged doesn't call at all in this case. In fact the page is not changed, the survey state is changed from "running" to "completed".
You may look at my fix. What do you think?
Thank you,
Andrew

Sounds good to me, thanks you!


extension named nodes

allow to name nodes in extension definition
name arriving node with
-> (<NAME>) 'x' ->

transition to node
-> 'y' @<NAME>

This will need to define transitions on many lines to allow caming back to a named node (looping or branching)

done release 1.9.0


[NeurIPS 23 Sparse Track] Update config for team NLE

Hi, we decided to change the configs a bit to increase the maximum recall to try to guarantee at least 1 run on the final set with >90% recall.
Should have done this in the first submission, sorry for adding to the amount of pull requests right now

@cadurosar  once merged, these will be the params for final eval. You are OK with that?

@cadurosar once merged, these will be the params for final eval. You are OK with that?

Yes I am, thanks


SVG on firefox

Hi,
i tried html2canvas and it works fine on chrome, safari but not on firefox. I'm using inline svg and I've been trying to figure out why it won't work on firefox. Any idea?

Please share an example on jsfiddle

Thanks for your quick response. Here's the jsfiddle
https://jsfiddle.net/mahmoodchowdhury/nt6v24wa/

html2canvas works like a charm for chrome! But facing issues with firefox and IE. Any planned resolution date for above firefox issue?
Thanks!

Same issue with IE - using mahmoodchowdhury example and with our app (Leaflet mapping) - SVG elements working great in Chrome, not in IE or FF.
Thanks.

Just wondering if there's an ETA on a fix?

Same for me. While html2canvas seems to work in Chrome and IE (with an distorted Pie chart) , in FF it sometimes displays only text but often doesn't render any svg. I made an example in JSFiddle that illustrates the issue. I tested it with all alpha and beta versions of version 0.5.0 . None of them seem to work under FF.

Hi guys,
So I managed to get this working. There are two main things I had to add:

call the svg image as an external image source
Add "allowTaint", "useCORS", "taintTest" properties to the html2canvas function

Here is the working fiddle: https://jsfiddle.net/mahmoodchowdhury/x0724yj3/2/
If you guys want to compare the original fiddle I posted, here's the link: https://jsfiddle.net/mahmoodchowdhury/nt6v24wa/
Hope this help.

Fixed in v1.0.0-alpha.1 https://jsfiddle.net/nt6v24wa/3/


[cleanup][build] Use netty.version consistently

Trivial changes. cc @codelipenghui @lhotari

[x] doc-not-needed

I think this patch is ready for merge.


Minor typo in export activity logs article

@pilor : Thanks for your contribution! The author, @johnkemnetz, has been notified to review your proposed change.


Multiple callback triggers in 'settings' subsystem

Golioth Firmware SDK Commit Hash
a6115ea1385c6409d389730359084ee9d2ca2a99
Platform/OS
Zephyr 3.7
Hardware Target
ESP32
What host OS are you using?
Windows 11
Current Behavior
When the device boots, the callback for each registered setting is triggered multiple times (it seems that it is triggered n times where n is the total number of settings - but I can easily be wrong about the exact number).
Expected Behavior
A callback for each setting should be triggered exactly once.
Steps To Reproduce
I'm using Zephyr 3.7 together with Golioth v0.15.0. The target is espressif esp32 WROOM.
Logs, console output, or any kind of debug information
[00:00:19.069,000]  hp_golioth_settings: Set MQTT broker name to xxx.com
[00:00:19.072,000]  hp_golioth_settings: Set MQTT port to 1883
[00:00:19.412,000]  hp_golioth_settings: Set cooling threshold to 2.50
[00:00:19.413,000]  hp_golioth_settings: Set MQTT broker name to xxx.com
[00:00:19.416,000]  hp_golioth_settings: Set MQTT port to 1883
[00:00:19.692,000]  hp_golioth_settings: Set MQTT port to 1883
[00:00:19.692,000]  hp_golioth_settings: Set cooling threshold to 2.50
[00:00:19.695,000]  hp_golioth_settings: Set MQTT broker name to xxx.com
[00:00:19.985,000]  hp_golioth_settings: Set MQTT port to 1883
[00:00:19.987,000]  hp_golioth_settings: Set cooling threshold to 2.50
[00:00:19.988,000]  hp_golioth_settings: Set MQTT broker name to xxx.com

Hi @OgnjenX! Thanks for opening this issue and apologies for the delay in our reply.
You're correct in your assessment of the behavior. Each time we register a setting, we do a GET request to the server to ensure that we have an up-to-date value for that setting. The server returns the full settings payload each time, and so we call each of the registered handlers to update them. During initialization, when registering multiple settings, this manifests in the behavior you've described. This is inefficient, and we have plans to improve this in the future, both in terms of UX and bandwidth usage.
Note that even with improvements to settings registration, the settings handler will still need to be resilient to being called when the setting hasn't changed. This is because whenever there is an update to one or more settings in the cloud console, the whole settings payload is sent to the device, and the device does not know which of the settings has changed and which remains the same.


[Nightly] support external network send mail

Coverage remained the same at 57.166% when pulling 7bf0be00ddc430ccfc2f6a0c6b96f0e74cc2ce34 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage increased (+0.04%) to 57.21% when pulling 5ef0fa029a46e4d151c86ae523c353933f662607 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 5ef0fa029a46e4d151c86ae523c353933f662607 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 749a1e690e86bd8b58994687b1cee2ea50720732 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 2b11ded5a67b03bf9483a1428d83479dac47e39f on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 2b11ded5a67b03bf9483a1428d83479dac47e39f on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling c1ef0b37d65c29424a058d5e12da76ee6c8c1625 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 41fa9a5432b5eb909dca18d49d31c812ece2411d on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 61986d62f3702d546c70a53e2ce32cc0a64380f1 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 758e374ca2d733df548afb0f00e8a0d9bba5f7f7 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling fe64687883402b2f0449e932a43163377dbf2331 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage increased (+0.04%) to 57.21% when pulling 6a32fe10e95d94c0bd67216dd85cc1e4d3aa2884 on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling 11e7a3171146fe4bb5d2343bc12914235a417f6a on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling a900360cef8d2755524a391be9d897511e5cdcfd on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage increased (+0.04%) to 57.21% when pulling a900360cef8d2755524a391be9d897511e5cdcfd on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.

Coverage remained the same at 57.166% when pulling a15f7afcb3b5c4ba4082e2f40a382f1a3a149cdd on wy65701436:drone-test into 48edfe4e6dfc201e1671f443c15e79b1566c683e on vmware:drone.


Attribute value is not stored on a new entity if it comes from com.fulcrologic.rad.form-options/default-value

When storing a RAD entity with an attribute that has com.fulcrologic.rad.form-options/default-value set and the value is the default value then the attribute will not be stored into Asami because it seems unchanged from the diff, as in this example:
; rad.pathom:- 46 - transaction:
[{({:com.fulcrologic.rad.form/id #fulcro/tempid[“dc85612d-31b3-4919-8b26-938b78cdb228”],
    :com.fulcrologic.rad.form/delta {[:account/id #fulcro/tempid[“dc85612d-31b3-4919-8b26-938b78cdb228"]]
                                     {:account/email {:before nil, :after<EMAIL_ADDRESS>
                                      :account/active? {:before true, :after true}, ; <-- from `fo/default-value true`
                                      :account/files {:before [], :after []}}},
    :com.fulcrologic.rad.form/master-pk :account/id}
   com.fulcrologic.rad.form/save-form)
  [..]} :tempids]

Fixed in Fulcro 3.5.33 by not sending the value in :before, see https://github.com/fulcrologic/fulcro/commit/09b84b4b0454009d6d903ad3e6e6fbc97e931b24


Adding two lines from Virgilios Ecloga, adding a picture

Not sure if it matches the spirit of your composition, you can merge or ask me for changes

I like classical Latins and Greeks are one of my favourites. Nice pictures

Ok thanks!


add toggle pip command

Related tasks:
https://linear.app/whereby/issue/PAN-292/add-event-listenerhook-for-pip-button
https://linear.app/whereby/issue/PAN-345/add-embed-element-command-for-opening-and-closing-picture-in-picture#comment-d02b647d

Doesn't actually work
https://developer.mozilla.org/en-US/docs/Web/API/HTMLVideoElement/requestPictureInPicture#security


Question about the example of collision world in the documentation

For the following example from the collision world
rp3d::WorldSettings settings ;
settings.nbVelocitySolverIterations = 20;
settings.isSleepingEnabled = false ;

// Create the world with your settings
rp3d::CollisionWorld world ( settings );

The compiler says
class "reactphysics3d::WorldSettings" has no member "nbVelocitySolverIterations"
What is wrong with this?
Also,  what is rp3d::CollisionWorld world ( settings )?
Is it a function? I am a little confused of how to use it.
Thank you

This code is not up to date in the user manual online. I will update it.
As you can see here in the online API documentation, the nbVelocitySolverIterations variable is now called defaultVelocitySolverNbIterations. You should try to use a code completion tool on your IDE to prevent those issues in the future.
The following line:
rp3d::CollisionWorld world ( settings );
is simply a call to the constructor of the CollisionWorld class with the settings in parameter. If you do not understand this, I really suggest that you learn C++ first before diving into physics simulation.


avoid unnecessary model validation during server processing

Is your feature request related to a problem? Please describe.
Because our fhir-model is immutable, whenever we want to modify an existing object we need to copy it into a new builder (via toBuilder()).
After that, when the object is built again, we will re-perform model validation.
This sounds expensive, but its not actually too bad because its a shallow validation (we won't revalidate all the members of this new model object...just the object itself).
Still, in places where we know what we're adding is valid (e.g. when we set the 'id' and 'versionId' fields during create/update), I think we could skip this validation.
Describe the solution you'd like
Skip model validation in places where we call toBuilder() and add only fields that we already know will be valid.
Describe alternatives you've considered
Acceptance Criteria

GIVEN [a precondition]
AND [another precondition]
WHEN [test step]
AND [test step]
THEN [verification step]
AND [verification step]

Additional context

Looks like we already set 'isValidating' to false in FHIRPersistenceUtil.copyAndSetResourceMetaFields so we're doing better than I thought:
https://github.com/IBM/FHIR/blob/main/fhir-persistence/src/main/java/com/ibm/fhir/persistence/util/FHIRPersistenceUtil.java#L260-L265
There's still a couple places that I think we could update (e.g. FHIRRestHelper.addLinks), but might not even be worth it.

Not worth it.  Closing.


 in XML attributes

In xliff exported by Xcode,
 is a replacement for \n. However, when decoded and encoded by XMLCoder, the
 is replaced by a hard line break
original by Xcode
<trans-unit id="Got an attributed String.
Will create a image.

" xml:space="preserve">

decoded and encoded by XMLEncoder
<trans-unit id="Got an attributed String.
Will create a image.

" xml:space="preserve">

However, the latter is then not accepted by Xcode as a valid translation.
My Question
Should I think this as a bug of XMLCoder or something that I should deal with in my own app?

Hi @owenzhao, thanks for reporting this. With the new API in master you can do something like encoder.charactersEscapedInAttributes += [("\n", "
")] to make it work for your case.


Fix spelling of hexadecimal in openapi.yaml

It was spelled as hecadeximal instead of hexadecimal.
Signed-off-by: S m, Aruna<EMAIL_ADDRESS>

@arsulegai Looks like this needs to be rebased to get some rust formatting fixes.

@arsulegai Looks like this needs to be rebased to get some rust formatting fixes.

Done


ISPN-7447 fix for DefaultExecutorService without keys specified.

ISPN-7447 fix for DefaultExecutorService without keys specified.
And also make the with keys specified work like others. Clone the task.getCallable for target equals me.
I don't know what is the clone for. But the Callable is cloned in other submit DistributedTask methods. So I added it as well. Maybe anyone can tell whether the clone is required? I just added it like other submit DistributedTask methods.
For no keys specified, it's submitted to local. And it's reuse the submit(Address, DistributedTask). So the features like failover in DistributedTask will work.

@SetoKaiba There is a need for cloning; I wrote this code appx. four-five years ago and I remember the need for cloning, but I did not write the comment why! Also, I could not read your repo where you have put the tests. See how we wrote other DES unit tests and maybe you can adapt your tests to our framework. Perhaps you can add your tests to this PR as well? :-) Thoughts @wburns

@vblagoje But the original implementation doesn't clone. I added it because I take other methods as reference and find others are all with cloning for local.
My repo is deleted because I have found out the bugs.  It's not test case, but for reproducing.
I'll add a TestCase for submit method without keys specified, which is fixed in the patch. But since the original DistributedExecutorFailoverTest is with cluster. I have to shutdown others before this test.
And the future.get is not working only occurs in 8.2.x. But it's difficult for me to fix it. Because it use a delegate NotifyingFutureImpl for LocalDisitributedTaskPart. So I migrated to 9.x.

@vblagoje test case is added.

@SetoKaiba @vblagoje The cloning is needed because the task may have non-transient fields that change during execution. If the task starts executing on the local node and marshalling tries to write those fields from another thread, it could cause hard-to-track errors.
I find the case where there are no input keys a bit weird. Normally we execute the task on one of the primary owners of the input keys, but if there are no keys, there are no owners, so IMO we should not execute the task at all.

And also, no input keys and input cache is normal for my case. Just use it as ClusterExecutor. Use CDI to inject the cache for data modification. And without input keys, it's run locally.

Ok. I know how change it.

@vblagoje @danberindei @slaskawi According to the result from CI, the problem is caused by cloning. But cloning exists in the methods below.

submit(Address target, DistributedTask task)
submit(DistributedTask task, K... input)
submitEverywhere(DistributedTask task)

So I added cloning to the submit(DistributedTask task, K... input) as well.
But it seems that the cloning will check something. But adding ExternalPojo to every Callable should not be required. The problem is caused by the below isAllowed call.
assert ExternallyMarshallable.isAllowed(obj) : "Check support for: " + obj.getClass();

@slaskawi Added ExternalPojo to Callable test cases which is required. And also remove the kill of other managers. The test suite should be okay now.

Integrated, thanks @SetoKaiba !
I added another commit to make use of our TestException and Exceptions.expectExecutionException().


Tunnistamo review instance

Description :sparkles:
Review environment uses local tunnistamo (instead of KuVa tunnistamo-qa) and local kultus-api instances.
Build arguments is possible set as pipeline parameter.
Most of changes has been done on kultus-pipelines kultus-pipeline pr5830
Issues :bug:
Closes :no_good_woman:
DEVOPS-547
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Local kultus-api database is empty.  Admin-ui can login but there is not any other data.
Screenshots :camera_flash:
Additional notes :spiral_notepad:

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr305.dev.hel.ninja :rocket::rocket::rocket:

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr305.dev.hel.ninja :rocket::rocket::rocket:


[FeatureRequest] or Documentation Gap: How to customize InstanceName property in Codeless Approach

Because Microsoft recommend "codeless approach" in logging- Microsoft should give us a way to customize "InstanceName" property of each request.
Currently, in codeless approach, runtime set instancename from azure function name, while this name must be unique as part of fqdn. Without customization - on applicationMap we see ugly "wegehsrthetr" instead of something human-readable for example "app1_backend"
Please, if such customization exist- tell us how.
If not exist- classify this request as - FeatureRequest.

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

ID: 13672b67-22ea-3dda-8b6b-3332c24e6030
Version Independent ID: fdc60aeb-9971-1d9f-a6ba-b3ad818cf0d5
Content: Monitor Azure Functions
Content Source: articles/azure-functions/functions-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @SychevIgor Thanks for reaching out. We will review and update as appropriate.

@SychevIgor I have assigned this to content author for further review and update as appropriate.

Hi @SychevIgor, this sounds like a feature request for Functions. Can you please reopen this request in the Azure/azure-webjobs-sdk product repo?

Since this isn't technically a docs issue #please-close.


Features/interpreter regex

Désolé pour le retard, en ce moment le test A-Z fonctionne pas, mais ça devrait passer une fois la PR de output merge.

Codecov Report

Merging #27 into staging will increase coverage by 0.06%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           staging      #27      +/-   ##
===========================================
+ Coverage    99.61%   99.67%   +0.06%
===========================================
  Files           18       18
  Lines          257      308      +51
===========================================
+ Hits           256      307      +51
  Misses           1        1

Impacted Files
Coverage Δ

src/interpreter/MarkdownParser.js
100% <100%> (ø)
:arrow_up:

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 6c86029...94e8605. Read the comment docs.


Some browser field in bundling modules are ignored when target = "electron-renderer"

Bug report

What is the current behavior?
When bundling modules which have browser field in package.json, the alternative script specified in the field will be used for webpack bundling by default. It is also true when the target is set to electron-renderer, but only when the browser field has object-style replacement, the replacement is not working in target="electron-renderer".
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/stomita/webpack-browser-field-test
To reproduce the issue:

Checkout the repos above
Run npm install
Run npm run build to generate bundled scripts
Run npm test to get the result

The output will be:
----------
target = web
module with browser field (string) => browser.js
module with browser field (object) => browser.js
----------
target = electron-renderer
module with browser field (string) => browser.js
module with browser field (object) => index.js

What is the expected behavior?
A webpack config with target: "electron-renderer" should handle modules with object-style browser field correctly as the config without target (= target: "web").
So the above example result should be like:
----------
target = web
module with browser field (string) => browser.js
module with browser field (object) => browser.js
----------
target = electron-renderer
module with browser field (string) => browser.js
module with browser field (object) => browser.js

Other relevant information:
webpack version:  4.19.0
Node.js version: 8.11.4
Operating System: macOS High Sierra (10.13.6)
Additional tools: no

Please send a PR:
This line
https://github.com/webpack/webpack/blob/5258471fa13ea450992255767faf38f01c143511/lib/WebpackOptionsDefaulter.js#L330
need to be similar to
https://github.com/webpack/webpack/blob/5258471fa13ea450992255767faf38f01c143511/lib/WebpackOptionsDefaulter.js#L337-L341

Nice that PR was broke applications which use axios for example (or webtorrent) by default...


Broadcast not found

If broadcast not found Periscope api returns "Not Found".
https://api.periscope.tv/api/v2/getBroadcastPublic?broadcast_id=1LyxBeXmWObJN
Need verify response.text before parse to JSON.

Thank you for pointing this out. I will take this on in the next version.

oh well it's needed in other places too.


Feat: Support notes as tooltips for district rows as well

Description of PR
Support notes as Tooltips for district rows
Relevant Issues
Fixes #1472
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots
At the time of pull request all district note were empty. If it receive a note it will look like this

Hey @Abhinav-Mani , it removed the tooltip from unknown in district sub-table. Since unknown doesn't have a note in it, the tooltip icon is not rendered. A default tooltip note was present for unknown ones.

@nayakrahul I didn't knew that.


Adding filename truncation based on process.cwd()

This makes the output look relative if you're running it from the root of your project directory

Will wait for your approval @pixari, see if you like this solution!

I think it is totally fine.
Maybe in future we can offer another way to show the report, something like a log file or a CSV.
There we can write the whole path without any concern.
However: great job @Spittal, as always!


Creating the BottomSheet component for select

Imagens

Video
https://github.com/Mobilecn-UI/nativecn-ui/assets/72309855/6ef20b6e-f212-4de8-bc9b-62a17dbb599c

Hi @Antonio-Sitoe, thanks for the PR – it looks great. Could you add docs for the component? Check out some examples here

Hi @Antonio-Sitoe, thanks for the PR – it looks great. Could you add docs for the component? Check out some examples here

Ok, sure i Will do it

Hi @Antonio-Sitoe, thanks for the PR – it looks great. Could you add docs for the component? Check out some examples here

You can see the doc here


[o1js] Reset feature flags before assertion

This is https://github.com/MinaProtocol/mina/pull/14402 for o1js-main, plus the temporary hack from https://github.com/MinaProtocol/mina/pull/14405 to unblock work with custom gates

!ci-build-me

!ci-build-me


Tracking issue: Use remote npm versions of packages

Currently errors when using the published npm versions of the following packages. See package.json for name on npm (e.g. @penumbra-zone/zquery)
===
(priority for skip integration)

[ ] #9
[ ] #10
[ ] #11
[ ] #12

===

[ ] #13
[ ] #14
[x] #15
[ ] #16
[ ] #17
[ ] #18
[ ] #19
[ ] #20
[ ] #21
[ ] #22

These are currently not published:

[ ] #23
[ ] #24
[ ] #25
[ ] #26

@grod220 Most of the packages are integrated, can we close them? The only ones left are zquery and ui

status of this tracking issue?


Enable some kind of gradual typing in test_runner

It's not realistic to enable full-blown type checks
within test_runner's codebase, since the amount of
warnings revealed by mypy is overwhelming.
Tests are supposed to be easy to use, so we can't
cripple everybody's workflow for the sake of imaginary benefit.
Ultimately, the purpose of this attempt is three-fold:

Facilitate code navigation when paired with python-language-server.
Make method signatures apparent to a fellow programmer.
Occasionally catch some obvious type errors.

Just to check my understanding: these are only type "hints", that are completely ignored by the interpreter, right?
I question the comment that type hinting is optional. It seems like this implies a higher level of discipline from everyone touching the code: they all have to use the same tools to run the same static checks, or else things will constantly be getting broken.
That suggests there should be a CI check, and a client-side git hook, but I'm wondering if there's a point where the costs start exceeding the benefits.

Just to check my understanding: these are only type "hints", that are completely ignored by the interpreter, right?

That's right. The interpreter doesn't perform any checks, you're supposed to run a separate tool called mypy.

they all have to use the same tools to run the same static checks, or else things will constantly be getting broken.

That's why I had to take some precautions:

Add mypy to Pipfile and pin its version in Pipfile.lock.
Carefully tune mypy's settings to make it as permissive as possible.

That suggests there should be a CI check, and a client-side git hook, but I'm wondering if there's a point where the costs start exceeding the benefits.

Maybe. I had the idea that we could experiment with types and see if it's worth it. The "manual mode" gives us the opportunity to check them out without giving anyone too much of a headache. I deliberately didn't change anything in CI's config.

Anyway, I won't be sad if this patch doesn't find its way to the main branch.


bug: incorrectly selection cmp cmdline completion

Did you check docs and existing issues?

[X] I have read all the noice.nvim docs
[X] I have searched the existing issues of noice.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
v0.9.0-dev-1319+g10baf8971
Operating system/version
Arch Linux @ kernel 6.2.12
Describe the bug
When continusly cycling through options, by holding in Tab, it incorrectly randomly selects a completion item, and starts  cycling on that instead.
I'm only able to reproduce this with cmp, noice and lualine activated.
https://user-images.githubusercontent.com/2284724/235151788-7e14f447-be6f-42e8-9ba3-71c7cb887aaa.mp4
Steps To Reproduce

Run reproduction config.
Press :.
Hold Tab.
Wait until it selects an completion item.

Expected Behavior
It should just continuously cycle through the same completion items.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
	vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
	vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
	"folke/tokyonight.nvim",
	{
		"folke/noice.nvim",
		opts = {
			cmdline = {
				view = "cmdline",
			},
		},
		dependencies = {
			"MunifTanjim/nui.nvim",
		},
	},

	{
    'nvim-lualine/lualine.nvim',
    config = true
	},
	{
		"hrsh7th/nvim-cmp",
		dependencies = {
			"hrsh7th/cmp-buffer",
			"hrsh7th/cmp-cmdline",
			"hrsh7th/cmp-path",
		},
	},
}
require("lazy").setup(plugins, {
	root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")

local cmp = require("cmp")
local anyWord = [[\k\+]]

cmp.setup.cmdline(":", {
	mapping = cmp.mapping.preset.cmdline(),
	sources = cmp.config.sources({
		{ name = "path" },
		{ name = "cmdline", option = { ignore_cmds = { "!" } } },
		{
			name = "buffer",
			keyword_length = 4,
			option = { keyword_pattern = anyWord },
		},
	}),
})

Why would this be caused by Noice?

Hi,
Using cmp + noice with tab configured as
        ["<Tab>"] = cmp.mapping(function(fallback)
            if cmp.visible() then
                cmp.select_next_item()
            elseif vim.fn["vsnip#available"](1) == 1 then
                feedkey("<Plug>(vsnip-expand-or-jump)", "")
            elseif has_words_before() then
                cmp.complete()
            else
                fallback()
            end
        end, { "i", "s", "c" }),
        ["<S-Tab>"] = cmp.mapping(function(fallback)
            if cmp.visible() then
                cmp.select_prev_item()
            elseif vim.fn["vsnip#jumpable"](-1) == 1 then
                feedkey("<Plug>(vsnip-jump-prev)", "")
            else
                fallback()
            end
        end, { "i", "s", "c" }),

works fine


The "Ships To" Input disappears If you search "Trade" first

Brief Description:
The "ship to" input does not appear and the "accepted currencies" are all un-checked on the filter column if you [see al]l of the "Trade" category before making another search.
Operating System (OS and version): Ubuntu 18.04
OpenBazaar version (shown on About OpenBazaar page in menu): 2.3.3
Hardware: i5 Laptop
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce): Always
Steps to reproduce:

Click the "Discover" button on the OB broswer
Click the "OB1" button link
Scroll down to the bottom of the "Trade" table and click "See All"
Click on "Books" in the "Suggestions" bar below the OB1 search bar
Look at the filter column below the "Suggestions".

Observed Behavior:
The filter column on the OB1 search is missing the "Ships To" input that is usually at the top.
Also the "Accepted Currencies" are all unchecked which makes the next search more difficult
Expected Behavior:
We should be able to see the "Ships To" input and having the "Accepted Currencies" all checked makes the next search easier similar to having the default settings.
Additional info (links, images, etc go here):

Thank you for reporting this, @apothan I've confirmed the bug, and have a good idea of what's causing it.


where is the dockerfile for the container that kitematic manages?

Expected behavior
Export or view the effective "dockerfile" for a container configuration listed in kitematic
Actual behavior
Cannot find any "dockerfile" representing current configuration
Information about the Issue
I am on macOS Sierra using the native beta docker app.
Steps to reproduce the behavior
Pull an image into container. Change settings. Look for dockerfile.

Dockerfile is what is used to build the image. The image is what you distribute. Some image creator share the dockerfile, some don't.
You can always use their image as the base of your Dockerfile and create your own modifications to it.

Yeah... I see it now. It seems strange to me that the Dockerfile does not get embedded or cannot be inferred from the image or container via the inspect command or similar.
Also awkward is the wiring up of the networks known as linking which can only be done prior to instantiating a container from an image.
In any case, for reference the current workflow for modifying a kitematic container is as follows:

docker commit containername yourgithubaccount/yourcontainername
docker run yournewoptions (e.g. --link) thenewimage

Linking is the old way to wire up containers - You can now create a network specific to a set of containers and dynamically add them to that network.


Regular autocomplete is lost

On version 0.1.2
When I start writing a word in a file, usually Code gives me at least code completion for plain text words (see the small 'abc' icon) searching on open files. This works for all kinds of files, and even for Elixir unsaved ('Untitled', not on disk) files. Like this:

This does not work for me on Elixir pre-existing files (i.e. part of an actual project). Like this:
Is it some misconfiguration from my part? Or is it a bug?
Thanks

The same is on my machines too, even after everything is compiled.
I'm on Elixir 1.4, are you too?

Yes Elixir 1.4
El 13 mar. 2017 5:34 p. m., "Aleksandar Kex Trpeski" <
<EMAIL_ADDRESS>escribió:

The same is on my machines too, even after everything is compiled.
I'm on Elixir 1.4, are you too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fr1zle/vscode-elixir/issues/56#issuecomment-286163774,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAc292oKmkK83c_XXBcVP-4biB1JensMks5rlXAPgaJpZM4MbB5T
.

Hmm i currently can't reproduce this issue:

Could you maybe open up developer tools (via Help) and paste anythings thats looks like an error in here?

I attach you the complete sequence of an example. I expect the word
'expression' to be suggested when I write 'exp', as it is a word that is
present in the current file.
While I go on writing you can see that some completions are suggested, but
not the plain text one.
The last one is the output in console. It's the same output repeated
several times.
Hope it helps !
[image: Imágenes integradas 1][image: Imágenes integradas 2][image:
Imágenes integradas 3][image: Imágenes integradas 4][image: Imágenes
integradas 5]
2017-03-13 19:59 GMT+01:00 fr1zle<EMAIL_ADDRESS>
Hmm i currently can't reproduce this issue:
[image: image]
https://cloud.githubusercontent.com/assets/311019/23870665/7649fb54-0827-11e7-81f8-4c096101e9fd.png
Could you maybe open up developer tools (via Help) and paste anythings
thats looks like an error in here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fr1zle/vscode-elixir/issues/56#issuecomment-286209026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAc29-B6fdMTSaIn2avlilGseTQC8JUGks5rlZIAgaJpZM4MbB5T
.

Hey @rubencaro appearently github doesn't include images send via mail. Could you upload them via the web interface?
Thanks a bunch!

Thanks @rubencaro, seems to be the same issue as #30, will look into it once i get some time!

This might be related to https://github.com/Microsoft/vscode/issues/21611

I have the same issue


Messages are clipped

I encountered strange layout of text within cells. All messages are clipped by length of the first message. What am I doing wrong?
Example of normal length

Example of clipped length
The second message actually contains Hello, but it has been displayed as Hell

Must be something about reusing cells but not resizing them when text changes.

Sounds like you haven't implemented hash, or overridden it improperly.
See #631


Solved for MNIST file downloading problem

A lot of folks (#6742, #8126, #8134,#8116) were having trouble regarding this issue. Even I faced it today while writing the MNIST code as the mnist.py was unable to connect with the source url. I downloaded the files and pasted it in the folder containing the code and made some changes in the code which solves the need for connecting it to the website. Hope so this works out.

Can one of the admins verify this patch?

I signed it!

Hello @caisq , the website is not allowing us to connect what is the solution now?

Sorry - I'm confused what you mean by the website not allowing you to connect. I just tried
wget --spider https://storage.googleapis.com/cvdf-datasets/mnist/train-images-idx3-ubyte.gz
wget --spider https://storage.googleapis.com/cvdf-datasets/mnist/train-labels-idx1-ubyte.gz
wget --spider https://storage.googleapis.com/cvdf-datasets/mnist/t10k-images-idx3-ubyte.gz
wget --spider https://storage.googleapis.com/cvdf-datasets/mnist/t10k-labels-idx1-ubyte.gz

The commands all work, indicating remote files exist.

I am getting the following output
Traceback (most recent call last):   File "mnist_softmax.py", line 79, in <module>     tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)   File "/home/pratik/tensorflow/venv/local/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 48, in run     _sys.exit(main(_sys.argv[:1] + flags_passthrough))   File "mnist_softmax.py", line 37, in main     mnist = input_data.read_data_sets(FLAGS.data_dir, one_hot=True)   File "/home/pratik/tensorflow/venv/local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/datasets/mnist.py", line 240, in read_data_sets     source_url + TRAIN_IMAGES)   File "/home/pratik/tensorflow/venv/local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/datasets/base.py", line 208, in maybe_download     temp_file_name, _ = urlretrieve_with_retry(source_url)   File "/home/pratik/tensorflow/venv/local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/datasets/base.py", line 165, in wrapped_fn     return fn(*args, **kwargs)   File "/home/pratik/tensorflow/venv/local/lib/python2.7/site-packages/tensorflow/contrib/learn/python/learn/datasets/base.py", line 190, in urlretrieve_with_retry     return urllib.request.urlretrieve(url, filename)   File "/usr/lib/python2.7/urllib.py", line 94, in urlretrieve     return _urlopener.retrieve(url, filename, reporthook, data)   File "/usr/lib/python2.7/urllib.py", line 240, in retrieve     fp = self.open(url, data)   File "/usr/lib/python2.7/urllib.py", line 208, in open     return getattr(self, name)(url)   File "/usr/lib/python2.7/urllib.py", line 437, in open_https     h.endheaders(data)   File "/usr/lib/python2.7/httplib.py", line 1013, in endheaders     self._send_output(message_body)   File "/usr/lib/python2.7/httplib.py", line 864, in _send_output     self.send(msg)   File "/usr/lib/python2.7/httplib.py", line 826, in send     self.connect()   File "/usr/lib/python2.7/httplib.py", line 1220, in connect     self.sock = ssl.wrap_socket(sock, self.key_file, self.cert_file)   File "/usr/lib/python2.7/ssl.py", line 487, in wrap_socket     ciphers=ciphers)   File "/usr/lib/python2.7/ssl.py", line 243, in __init__     self.do_handshake()   File "/usr/lib/python2.7/ssl.py", line 405, in do_handshake     self._sslobj.do_handshake() IOError: [Errno socket error] [Errno 1] _ssl.c:510: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

This seems to be a network connectivity problem specific to you.

Well at first I thought it was due to some proxy configuration settings but now turning off all proxies and switching my connection to another network..it shows
IOError: [Errno socket error] [Errno 111] Connection refused


feat: User profile

What
Implements a method to fetch a user's profile to the SDK, adds relevant endpoints to the gRPC service and HTTP API.

Add unit test