bug: Broken duffle bundle sign

$ rm -rf ~/.duffle/
radu:bundles$ duffle bundle sign -f helloworld/bundle.json
==> Generating a new secret keyring at /home/radu/.duffle/secret.ring
==> Generating a new signing key with ID  <radu@SFB2>
==> Generating a new public keyring at /home/radu/.duffle/public.ring
Error: no parseable user identity attached to key

radu:bundles$ duffle key list
NAME            TYPE    FINGERPRINT
[anonymous key] signing 6749 AE5D 2EA5 D393 B6D0 29EC BE74 5C9E 1E7E C29C

$ duffle version
0.1.0-ralpha.4+dramallamabuie

I was unable to reproduce this myself on Windows:
PS C:\Users\me\code\go\src\github.com\deislabs\duffle\examples\helloworld> duffle bundle sign -f .\bundle.json
==> Generating a new secret keyring at C:\Users\me\.duffle\secret.ring
==> Generating a new signing key with ID Matthew Fisher <me@ULTRALISK>
==> Generating a new public keyring at C:\Users\me\.duffle\public.ring
Signed by Matthew Fisher <me@ULTRALISK> 9EE9 ACB7 99B7 D05B 9B66 E672 C7B0 647D BA24 D0D6

Perhaps it has something to do with running duffle under WSL?

Experiencing same issue on mac.


Installation guide out of date

I followed the installation guide https://projects.ampliapps.com/projects/ampli-sync/wiki#Installation. This is quite difficult:

There is a lot of name mixing "amplisync" versus "sqlitesync".
The "Docker" chapter is empty.

Finally I got the service running, although only with "root" id (not "tomcat").

We are under rebranding right now. The old name was SQLite-sync.com. We are
changing the name to AMPLI-SYNC. It's true, that is some places, there is
still an old name. We working on it.
I'm attaching an example Docker definition.
On Tue, Nov 12, 2019 at 12:31 PM fhintsch<EMAIL_ADDRESS>wrote:

I followed the installation guide
https://projects.ampliapps.com/projects/ampli-sync/wiki#Installation.
This is quite difficult:

There is a lot of name mixing "amplisync" versus "sqlitesync".
The "Docker" chapter is empty.

Finally I got the service running, although only with "root" id (not
"tomcat").
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlite-sync/SQLite-sync.com/issues/22?email_source=notifications&email_token=ACNU5N2HBFQ3LEGTDHHIQQ3QTKHZHA5CNFSM4JMCFLGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYVMEMQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNU5N5GOZNZGJ26MJM4HPTQTKHZHANCNFSM4JMCFLGA
.

--
Best regards
Tomek Dziemidowicz
E-mail<EMAIL_ADDRESS>Take care of the Environment with us!
Do not print this message or other documents if it is not necessary.

Dockerfile
FROM tomcat:8.5-alpine
ENV WORKING_DIR /working-dir/
RUN mkdir -p "/working-dir"
WORKDIR "/working-dir"
COPY ./working-dir/ .
docker-compose.yml
version: '3'
services:
sync:
build:
context: .
dockerfile: Dockerfile
expose:
- 80
restart: unless-stopped
environment:
VIRTUAL_HOST: virtualhost.example.com
VIRTUAL_PORT: 8080
LETSENCRYPT_HOST: virtualhost.example.com
LETSENCRYPT_EMAIL<EMAIL_ADDRESS>WORKING_DIR: "/working-dir/"
volumes:
- "./webapps:/usr/local/tomcat/webapps"
- "./working-dir:/working-dir"
networks:
default:
external:
name: nginx-proxy
On Thu, Nov 14, 2019 at 2:25 PM Tomek Dziemidowicz<EMAIL_ADDRESS>wrote:

We are under rebranding right now. The old name was SQLite-sync.com. We
are changing the name to AMPLI-SYNC. It's true, that is some places, there
is still an old name. We working on it.
I'm attaching an example Docker definition.
On Tue, Nov 12, 2019 at 12:31 PM fhintsch<EMAIL_ADDRESS>wrote:

I followed the installation guide
https://projects.ampliapps.com/projects/ampli-sync/wiki#Installation.
This is quite difficult:

There is a lot of name mixing "amplisync" versus "sqlitesync".
The "Docker" chapter is empty.

Finally I got the service running, although only with "root" id (not
"tomcat").
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlite-sync/SQLite-sync.com/issues/22?email_source=notifications&email_token=ACNU5N2HBFQ3LEGTDHHIQQ3QTKHZHA5CNFSM4JMCFLGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HYVMEMQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNU5N5GOZNZGJ26MJM4HPTQTKHZHANCNFSM4JMCFLGA
.

--
Best regards
Tomek Dziemidowicz
E-mail<EMAIL_ADDRESS>Take care of the Environment with us!
Do not print this message or other documents if it is not necessary.

--
Best regards
Tomek Dziemidowicz
E-mail<EMAIL_ADDRESS>Take care of the Environment with us!
Do not print this message or other documents if it is not necessary.


Where can i get the jar file?

Where can i get the jar file?

Paper shipped only as aar file.
https://bintray.com/pilgr/maven/paperdb/view#files/io/paperdb/paperdb


action form: fix styling issue and date input field

Closes https://github.com/inveniosoftware/invenio-administration/issues/149
Needs PR https://github.com/inveniosoftware/invenio-communities/pull/860

Adds placeholder and description to date input
Removes underscore from input label
Fixes spacing bugs for modal actions

Screenshot

Note
Discussed irl: the DatePicker will be added at a later point. See my comment on the task for details.

Changes
Removed datetime conditional block, and added placeholder to generateFieldProps.


Add path recommendations cache

While typing out #216, I realised that we could get a lot of utility out of having a path recommendations queue (or cache of some form) inside the fuzzer state.  The idea here would be that any insertion would automatically register its path (with the various flags) into the queue, and the payload generator would be able to pick that path instead of generating its own, if applicable.
One problem is that we don't have a theory of path motion, and so anything that could possibly invalidate paths would need to (for now) clear out the path recommendations.  (Yep, I'm about to file another issue for that)

Since the system for #216 is based on a function from payloads to recommendations, we could tie the two things together, and have the recommendation also suggest paths.  The motion problem still applies, as it might take several actions for a recommendation to get executed.


jose library imports fail

fastfed-node-sdk, npm run watch:

This appears caused by the upgrade:
-                 "jose": "^1.17.1",
+               "jose": "^3.11.6",

Reverting to jose 2.0.5 (latest in the still-supported 2.xx series) appears to resolve it. Will do that for now.


E-mail administrators about new offers

When someone submit a new offer, administrators should receive an e-mail telling that there is one new job offer pending review, and with the title/company name.
I'm personally fan of Mailgun, as I used it before and it's free for low quantity of emails/month. But I suppose using a standard mail library in Elixir is enough, as all providers has SMTP support.

I can do this. My idea was to use bamboo with the SMTP extension (I usually use sendgrid), and then it's just a matter of having the correct environment variables for the one being used and any provider will work?

Of course!
Remember that on production we use environment variables, while in development is on a secrets file.


operator: pkg util should not write logs

The util package is used both in the controllers and in the registration binary.
Not only the logging format differs between the two, but also the severity of the logs may change depending of the context (e.g., the MarshalCloudConfig func logs a warning if passed an empty cloud-config: a warning is fine for the registration client, while too much when processing the cloud-config in the seedimage controller).
Move all logging out of the util package (or at the very least, just allow debug logging in the util package).

fixed in v2


Update manage-skype-for-business-online-with-microsoft-365-powershell.md

Added syntax for Teams PowerShell Module 2.0

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


[improve][fn] Improve implementation for maxPendingAsyncRequests async concurrency limit

Fixes #23706
Motivation
See #23706
Modifications

replace LinkedBlockingQueue with Semaphore as the concurrency limit

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

The previous solution would retain order of the results. I'll have to check when that is necessary when whether that could be made configurable.

Codecov Report
Attention: Patch coverage is 90.62500% with 3 lines in your changes missing coverage. Please review.

Project coverage is 74.42%. Comparing base (bbc6224) to head (bc519d4).
Report is 782 commits behind head on master.

Files with missing lines
Patch %
Lines

...apache/pulsar/functions/instance/JavaInstance.java
90.00%
1 Missing and 2 partials :warning:

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #23708      +/-   ##
============================================
+ Coverage     73.57%   74.42%   +0.85%
- Complexity    32624    35100    +2476
============================================
  Files          1877     1945      +68
  Lines        139502   147483    +7981
  Branches      15299    16276     +977
============================================
+ Hits         102638   109768    +7130
- Misses        28908    29232     +324
- Partials       7956     8483     +527

Flag
Coverage Δ

inttests
27.25% <0.00%> (+2.67%)
:arrow_up:

systests
24.37% <37.50%> (+0.05%)
:arrow_up:

unittests
73.80% <90.62%> (+0.96%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines
Coverage Δ

...pulsar/functions/instance/JavaExecutionResult.java
33.33% <100.00%> (+8.33%)
:arrow_up:

...ulsar/functions/instance/JavaInstanceRunnable.java
73.29% <100.00%> (+0.24%)
:arrow_up:

...apache/pulsar/functions/instance/JavaInstance.java
81.44% <90.00%> (+3.81%)
:arrow_up:

... and 666 files with indirect coverage changes


feat: add extensive descriptions and examples to the schema v2.6.0

So I decided to enhance the spec-json-schema to include additional info and examples. This will enable tools like Studio, spec-visualizer and vscode to have the ability to get more information when consuming the spec-json-schema

Included descriptions of the schema definitions that are missing description
Enhanced/Replaced existing descriptions that lack enough information
Added examples payload to all required definitions

cc @derberg @smoya @fmvilas

so I ran your script and it looks good, the info examples is added

/rtm


Two of the diagrams have black text which is not visible in dark theme

Two of the diagrams have black text which is not visible in dark theme

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

ID: f4bc244f-e07c-f8a4-0f00-04c8e015821f
Version Independent ID: 2a37fdcf-eac8-3738-af46-7d70826ec660
Content: Scale Agile to Large Teams - Azure DevOps
Content Source: https://mseng.visualstudio.com/DefaultCollection/TechnicalContent/_git/devops-learn-pr?path=%2fdocs%2fagile%2fscale-agile-large-teams.md&version=GBlive&_a=contents
Service: unspecified
GitHub Login: @samgu
Microsoft Alias: gregboe

@slavizh I'm going to close all of these except for https://github.com/MicrosoftDocs/vsts-docs/issues/716 which I'll keep open until we have a fix. Thanks for reporting these.

This is fixed and should be live in a day or two, thank you.


Buffers run out inside loop after 16 iterations

Bug description
When calling ia.fetch_buffer() inside a loop to acquire images from a machine vision camera via a software trigger, only the first 16 calls will result in an image.
Steps to reproduce the behaviour:
Connect to the camera, set up the camera for a software trigger. Trigger the camera in software inside a loop and obtain the image from the buffer each time. img_arr[16] to img_arr[20] will have a 0 (no image, see code below).
ia = h.create_image_acquirer(list_index=0)
Camera_settings = ia.remote_device.node_map
Camera_settings.TriggerMode.value = 'On' # Trigger mode on
Camera_settings.TriggerSource.value = "Software" # Use software trigger
N_FRAMES = 20
img_arr = [None]*N_FRAMES
ia.start_image_acquisition()
while x < N_FRAMES:
Camera_settings.TriggerSoftware.execute()
time.sleep(0.05)
try:
    # Obtain image in the buffer
    buffer = ia.fetch_buffer(timeout = 1)
    payload = buffer.payload
    component = payload.components[0]
    width = component.width
    height = component.height
    data_format = component.data_format

    # Reshape the image so that it can be drawn on the VisPy canvas:
    if data_format in mono_location_formats:
        content = component.data.reshape(height, width)
    img_arr[x] = content
    x = x+1
except TimeoutException:
    print('Buffer timeout')
    content = 0
    img_arr[x] = content
    x = x+1

ia.stop_image_acquisition()
ia.destroy()
h.reset()
Expected behaviour
img_arr would now contain 20 images from the time at which the camera was triggered by software.
Desktop:

OS: Windows 10
Python: 3.7
GenTL Producer: Daheng Imaging

@Frodo181 You are not queueing any buffer after fetching them. Please take a look at this section.


Recipe App

In this PR, we have created the following pages:
A login page.
A registration page.
A food list (with all CRUD implementation, except for 'update).
A recipes list (with all CRUD implementation, except for 'update').
A general shopping list view (all missing food for all your recipes and total price).
A list of all public recipes from other users with their names and total prices.
Write tests using RSpec and Capybara testing libraries

Thank you for your overall feedback, the above requirements have been implemented.


Fix typo for Facebook unexpected messages

Fix typo in line 184 of botkit/lib/Facebook.js when logging unexpected messages.
It says:
botkit.log('Got an unexpected message from Facebook: ', facebook_message);

It should say:
facebook_botkit.log('Got an unexpected message from Facebook: ', facebook_message);

Apparently Facebook is now sending a new type of event/message (presumably read receipt events). This crashes the application and shows an error: ReferenceError: 'botkit' is not defined
This should be solved as soon as possible.

Same issue. These do indeed look like read receipt events:
  recipient: { id: '****************' },
  timestamp:<PHONE_NUMBER>729,
  read: { watermark:<PHONE_NUMBER>165, seq: 2896 } }```

Duplicate PR. Already, merged the other one.
Thanks for your contribution!


Come up with Colour Scheme and basic Design Language

Let's use Figma

Completed using Figma, all details exist on the design board


G-Tracking numbers don't link to G Analytics

Using a Web + App code (G-XXXXXX and not UA-XXXXX) don't work
I tried just switching the code to a UA-XXXXX (just web)  and worked out

This was cause it requires Google Tags integration.
Solved.


Improve list-prs-for-file's display

Fixes https://github.com/sindresorhus/refined-github/issues/2624

Groups multiple PRs under a dropdown in isSingleFile
Improves "single PR" wording and style in isEditingFile
Drops tooltips everywhere except "single PR" isSingleFile (everywhere else, links have context)

Test
https://github.com/sindresorhus/refined-github/blob/master/source/content.ts

https://github.com/sindresorhus/refined-github/edit/master/source/content.ts

https://github.com/sindresorhus/refined-github/blob/master/source/features/releases-tab.tsx

https://github.com/sindresorhus/refined-github/edit/master/source/features/releases-tab.tsx

I'm not getting the dropdown in https://github.com/sindresorhus/refined-github/blob/master/source/content.ts Just the +6 thing.

Yeah I noticed that the original TypeScript repo link also didn’t show any PRs. I wonder if the API request is the problem

It's working for me on the TypeScript file too: https://github.com/microsoft/TypeScript/blob/master/src/compiler/checker.ts
I don't see any issues if I add some logging, caching might have been the problem.


Creating a blueprint of target scope 'managementGroup'  fails

I'd like to create a blueprint with target scope managementGroup.
The template should then have multiple resourceGroups for statically defined subscriptions.
Is this possible?
When I create a blueprint via portal the target scope is always subscription and I have to pick a subscription on assignment.
The az command fails completely:
$> az blueprint create -n mgmt-group-test -m "<hidden>" --target-scope managementGroup

(InvalidSchema) Path:properties.targetScope, Schema:#/definitions/SharedBlueprintProperties/properties/targetScope, Error: Value "managementGroup" is not defined in enum.
Code: InvalidSchema
Message: Path:properties.targetScope, Schema:#/definitions/SharedBlueprintProperties/properties/targetScope, Error: Value "managementGroup" is not defined in enum.

It is not possible to have a single blueprint assignment deploy to multiple subscriptions. A blueprint assignment stored at MG scope can still only target one subscription.


stable/neo4j - "Connection refused" when trying to exec cypher-shell

Is this a request for help?:
Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Helm Client: v2.9.1
Helm Server:v2.9.1
Kubernetes: 1.13.0
Which chart:
https://github.com/helm/charts/tree/master/stable/neo4j
What happened:
"Connection Refused" is returned when trying to execute cypher shell.
Input:
kubectl exec neo4j-neo4j-replica-6dfcfcf675-btnhg -- bin/cypher-shell --format verbose \
"CALL dbms.cluster.overview() YIELD id, role RETURN id, role"

Output:
Connection refused
command terminated with exit code 1

Additionally, if I exec into the container, I'm still unable to access the cypher-shell.
bash-4.4# ./bin/cypher-shell
Connection refused

What you expected to happen:
I expected to be returned some results like the example shows:
$ kubectl exec neo-helm-neo4j-core-0 -- bin/cypher-shell --format verbose \
"CALL dbms.cluster.overview() YIELD id, role RETURN id, role"
+---------------------------------------------------------+
| id                                     | role           |
+---------------------------------------------------------+
| "32e6b76d-4f52-4aaa-ad3b-11bc4a3a5db6" | "LEADER"       |
| "1070d088-cc5f-411d-9e64-f5669198f5b2" | "FOLLOWER"     |
| "e2b0ef4c-6caf-4621-ab30-ba659e0f79a1" | "FOLLOWER"     |
| "f79dd7e7-18e7-4d82-939a-1bf09f8c0f42" | "READ_REPLICA" |
| "b8f4620c-4232-498e-b39f-8d57a512fa0e" | "READ_REPLICA" |
| "74c9cb59-f400-4621-ac54-994333f0278f" | "READ_REPLICA" |
+---------------------------------------------------------+

How to reproduce it (as minimally and precisely as possible):
Followed this guide
After installing and scaling the replica set, run the following command:
helm install --name neo4j-helm stable/neo4j --set acceptLicenseAgreement=yes --set neo4jPassword=mySecretPassword

Anything else we need to know:
This is all new to me, and I barely know what I'm doing, but I can certainly answer questions about what I did.

We also see this error:
Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=false, coreMembers={}}. Another member should have published a clusterId but none was detected. Please restart the cluster.". 	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:466) 	at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) 	at org.neo4j.server.AbstractNeoServer.start(AbstractNeoServer.java:212) 	... 3 more Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, /var/lib/neo4j/data/databases/graph.db 	at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:212) 	at com.neo4j.causalclustering.core.CommercialCoreGraphDatabase.<init>(CommercialCoreGraphDatabase.java:35) 	at com.neo4j.causalclustering.core.CommercialCoreGraphDatabase.<init>(CommercialCoreGraphDatabase.java:26) 	at com.neo4j.server.enterprise.CommercialNeoServer.lambda$static$0(CommercialNeoServer.java:29) 	at org.neo4j.server.database.LifecycleManagingDatabase.start(LifecycleManagingDatabase.java:88) 	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:445) 	... 5 more Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.causalclustering.core.state.CoreLife@61942c1' was successfully initialized, but failed to start. Please see the attached cause exception "Failed to join a cluster with members {clusterId=null, bootstrappable=false, coreMembers={}}. Another member should have published a clusterId but none was detected. Please restart the cluster.". 	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:466) 	at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107) 	at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:208) 	... 10 more Caused by: java.util.concurrent.TimeoutException: Failed to join a cluster with members {clusterId=null, bootstrappable=false, coreMembers={}}. Another member should have published a clusterId but none was detected. Please restart the cluster. 	at org.neo4j.causalclustering.identity.ClusterBinder.bindToCluster(ClusterBinder.java:167) 	at org.neo4j.causalclustering.core.state.CoreLife.start0(CoreLife.java:74) 	at org.neo4j.kernel.lifecycle.SafeLifecycle.transition(SafeLifecycle.java:124) 	at org.neo4j.kernel.lifecycle.SafeLifecycle.start(SafeLifecycle.java:138) 	at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:445)

Any update?
I have the same issue. I'have tried it using different environments:  minikube, Mac OS Desktop docker kubernetes, and Amazon EKS cluster.. And different computers (all Macs). Same result everywhere: "Connection Refused".
It occurs with auth enabled and without it too.

Any update on this issue. I am also getting same error.


lang: add expression lists

Summary
Add support for expression lists, where a series of expressions can be treated as a single expression. This allows writing zero or more unit or void expressions which must be followed by a final expression of any type.
Details
tbd

Note for Reviewers

[ ] write a proper commit message
[ ] write tests, needs effects or locals
[x] code changes:

[x] move Exprs decl with other non-void decls
[x] inference rules description in spec
[x] remove tmp usage

[x] Tests to add:

[x] single item expression lists
[x] invalid expression lists with non-void, non-unit types in leading positions
[x] valid expression lists ending in a void expression
[x] valid expression lists ending in a non-void expression
[x] expression lists ending in a non-void expression, but with a void expression somewhere earlier

I've gathered a list of things that need testing, but where the tests don't require effect-having expressions:

single item expression lists
invalid expression lists with non-void, non-unit types in leading positions
valid expression lists ending in a void expression
valid expression lists ending in a non-void expression
expression lists ending in a non-void expression, but with a void expression somewhere earlier

Right now the following:
(Exprs (Unreachable) (TupleCons) (FloatVal 1.0))

Fails because it results in the following L10, which has unreachable code errors:
(Unreachable)
(Drop (IntVal 0))
(FloatVal 1.0)

I'm conflicted as to what to do:

remove the restriction
remove the flag Stmt restriction
have Exprs processing culling everything after Unreachable and consider that desirable behaviour
accept this as a failing test and update the spec, if needed

The assertion message is maybe a bit unclear in this regard, but it triggers for all dead code situations, not just Unreachable. For example, the following code also trigger the assertion:
(ProcDecl (Ident "a") (UnitTy) (Params)
  (Stmts
    (Return)
    (TupleCons)))

Now, the assertion could be removed without causing any issues, as pass10 would just discard the dead code following the Return.
In general, I prefer aborting/crashing over silent error correction in case of easily detectable issues with the input, though I'm not sure whether dead code should really be considered an error in the L10 language (it's currently not described as such).

I'm conflicted as to what to do, some options I can think of:

remove the Unreachable restriction
remove the flag Stmt restriction
have Exprs processing culling everything after Unreachable and consider that desirable behaviour
accept this as a failing test and update the spec, if needed

My personal preference is towards number 3, though I think 4 would be fine too. If unreachable code being a hard error turns out to be too much of an ergonomic problem, then we can change it later on and allow void expression in non-trailing positions again.

The assertion message is maybe a bit unclear in this regard, but it triggers for all dead code situations, not just Unreachable. For example, the following code also trigger the assertion:
(ProcDecl (Ident "a") (UnitTy) (Params)
  (Stmts
    (Return)
    (TupleCons)))

Ah, good point, I took the message too literally, a break, continue, raise, non-terminal call, etc would likely all result in the same.

Now, the assertion could be removed without causing any issues, as pass10 would just discard the dead code following the Return.
In general, I prefer aborting/crashing over silent error correction in case of easily detectable issues with the input, though I'm not sure whether dead code should really be considered an error in the L10 language (it's currently not described as such).

That's why I was conflicted, I thought the error/failure had benefit.

I'm conflicted as to what to do, some options I can think of:

remove the Unreachable restriction
remove the flag Stmt restriction
have Exprs processing culling everything after Unreachable and consider that desirable behaviour
accept this as a failing test and update the spec, if needed

My personal preference is towards number 3, though I think 4 would be fine too. If unreachable code being a hard error turns out to be too much of an ergonomic problem, then we can change it later on and allow void expression in non-trailing positions again.

Looking at it today with fresher eyes, I think 3 makes more sense, too. Since the higher level layer knows why it's eliminating the code (read: doing it with good reason) I think it's safe and L10 can catch all the issues where a mistake have been made.

I didn't update the spec with non-trailing void expression post-expression elimination because it didn't seem like a particularly observable effect, but I could go either way.

I didn't update the spec with non-trailing void expression post-expression elimination because it didn't seem like a particularly observable effect, but I could go either way.

I don't think it's necessary now. Maybe it'll be in the future, for things like exception tracking (if that feature makes the cut), but that's still a long time away.

No idea, how I convinced myself that reporting an error for a trailing void made sense, good catch.
For the skipped sem check of post-void expressions, I was about to use a loop, but the template approach seems to read pretty cleanly. I also renamed the tests to drop _error from the file name because that's reserved for testing expected errors, instead of expected output that happens to be a runtime error.


Bump node to 1.25.1

Issue Number

Overview

[x] Bump node to 1.25.1
[x] Get CI to regen nix

Comments

Snapshot bump in: https://github.com/input-output-hk/cardano-haskell/pull/39

bors r+

bors r+

bors r+
(integration tests passed in buildkite in a batch, so failures should just be flakiness)

bors r+
(integration tests passed in buildkite in a batch, so failures should just be flakiness)


The serde version should be 1.1+

Since 1.0.0, serde has added some new features to its API, e.g. https://github.com/serde-rs/serde/commit/c162d518668de8363af67f6ffc1686ebec6de993
This affects crates that claim to be compatible with serde = "1.0", but actually aren't, e.g. serde_stacker won't work with the serde version it asks for in its [dependencies]:

method visit_i128 is not a member of trait de::Visitor
method skip_field is not a member of trait ser::SerializeStruct
no method named is_human_readable found for type S in the current scope

This involves somebody adjudicating whether every change is or is not a "feature", which I have not been interested in.
The serde_stacker issue seems mostly unrelated. That crate can declare a dependency on whatever serde version contains the things it needs, independent of how the serde releases are numbered.


chore(devenv): introduce theme chooser

Description
This change adds theme chooser Storybook add-on to Web Components storybook.
Changelog
New

Theme chooser in Web Components storybook env.

@asudoh looks like prettier issues, can you look?


Set version linter release branch to compatible

In CI, we were still comparing version types to develop as our stable release branch. This PR points this CI job back to compatible.

!ci-build-me

!ci-build-me


Remove stName from exo-plot choice.

stName should probably be removed from plot-exo parameters to plot.
Selecting stName plots most values at 0 so is not very informative but it also changes the min/max values to star names.
Then if you try to select a different parameter (without changing the limits) you get.
builtins.ValueError
ValueError: could not convert string to float: '11 Com'

If it is chosen as the color choice I get.
TypeError: unsupported operand type(s) for -: 'unicode' and 'unicode'

Fixed!


Maple (Samsung Smart TV) browser not detected

Maple browser is a proprietary browser from Samsung. Maple stands for MArkup engine PLatform for Embedded Systems.
Link: https://www.samsung.com/
Regex:
/(\sMaple)(\s)?(\d+[\.\d]+)/

Added a \s at the beginning to avoid conflicts as short name.
Example UA's:
Mozilla/4.0 (compatible; Gecko/20041115) Maple 5.0.0 Navi

Mozilla/5.0 (Windows; U; en-US; rv:<IP_ADDRESS>; Gecko/20071129; Firefox/2.5.0) Maple 6.0.00077

Add to [type] => television.

Link to: https://github.com/WhichBrowser/Parser-PHP/issues/212 discussion.

@NielsLeenheer

Take for example the Maple browser on Samsung television devices. I'm conflicted on how to detect this. Maple is an internal code name for the browser, not a consumer facing name. It was always labeled as "Web Browser". To me that is a big distinction. What also not helps it that Samsung sometimes refers to Maple as a development platform (for HTML based smart tv apps) and apps build using that development platform sometimes also use the token Maple in the UA string. So far I've not shown the name here, but used Maple as an identifier that we are dealing with a Samsung television device.

Taking this Example UA:
Mozilla/5.0 (Windows; U; en-US; rv:<IP_ADDRESS>; Gecko/20071129; Firefox/2.5.0) Maple 6.0.00077

I get the following results:
Lsxiao\UserAgent\UserAgent Object
(
    [browser] => WhichBrowser\Model\Browser Object
        (
            [using] =>
            [family] => WhichBrowser\Model\Family Object
                (
                    [name] => Firefox
                    [alias] =>
                    [version] => WhichBrowser\Model\Version Object
                        (
                            [value] => 2.5.0
                            [hidden] =>
                            [nickname] =>
                            [alias] =>
                            [details] =>
                            [builds] =>
                        )

                )

            [channel] =>
            [stock] =>
            [hidden] =>
            [mode] =>
            [type] => browser
            [alias] =>
        )

    [engine] => WhichBrowser\Model\Engine Object
        (
            [name] => Gecko
            [alias] =>
            [version] => WhichBrowser\Model\Version Object
                (
                    [value] => <IP_ADDRESS>
                    [hidden] =>
                    [nickname] =>
                    [alias] =>
                    [details] => 3
                    [builds] =>
                )

        )

    [os] => WhichBrowser\Model\Os Object
        (
            [hidden] =>
        )

    [device] => WhichBrowser\Model\Device Object
        (
            [manufacturer] => Samsung
            [model] =>
            [series] => Smart TV 2011
            [carrier] =>
            [identifier] =>
            [flag] =>
            [type] => television
            [subtype] =>
            [identified] => 4
            [generic] => 1
            [hidden] =>
        )

    [camouflage] =>
    [features] => Array
        (
        )

    [cache:WhichBrowser\Parser:private] =>
    [expires:WhichBrowser\Parser:private] =>
    [cached] =>
)

I can't see the word Maple in the above results ?
I was thinking and have a suggestion.
Any UA that contains the word Maple and gives the result of:
[manufacturer] => Samsung
[type] => television

Then create the results:
Browser Name: Samsung Internet
Browser Version: 6.0.00077

Which I took from the UA of Maple 6.0.00077

About: Mozilla/5.0 (Windows; U; en-US; rv:<IP_ADDRESS>; Gecko/20071129; Firefox/2.5.0) Maple 6.0.00077

Any UA that contains the word Maple and gives the result of:
[manufacturer] => Samsung
[type] => television

That is what the word Maple currently does.

Then create the results:
Browser Name: Samsung Internet
Browser Version: 6.0.00077

Samsung Internet is the name for the browser of the Tizen based Smart TV's from Samsung. The "Maple" browser did not have a name, so calling it Samsung Internet would not be correct. It might even lead to problems, because version number implies capabilities. And "Samsung Internet 6" on a 2011 Smart TV is way less capable than "Samsung Internet 1.5" on a Galaxy S5 from 2014.
The problem with that is there is no browser called Maple. It is just an internal codename for the rendering engine that underlies both the browser and app development platform.
The UA string above is from the 2011/2012 era. The consumer facing name for the browser was "Web Browser". And any app that was created using the Samsung Smart TV SDK 3.0 was using a UA string with the name "Maple 6.0".
So at most we could treat Maple as a platform and populate the "using" property in our result set. Similar to how we handle Adobe AIR or Electron at the moment.

https://github.com/WhichBrowser/Parser-PHP/blob/3810e9aceed8acab7f27d1145579cae30eb59ac0/src/Analyser/Header/Useragent/Using.php#L11-L40

~I'm closing issue that I have created a pr for - just to keep things tidy as I've opened around 300 issues.


"Insert Animation Key" shortcut ("K") does nothing

Godot version:
3.1 Stable
OS/device including version:
Windows & MacOS
Issue description:
The shortcut "K" for inserting a transform keyframe appears to do nothing
Steps to reproduce:
Create a Spatial and a connected AnimationPlayer with a new animation
Make sure Animation editor is open
Select the Spatial
Press "K"
Bask in the void of nothingness
Minimal reproduction project:
Not included

We still don't have a hotkey for inset Key frame, or do we?


comp toolbar is slow to open

network issue???

fixed https://github.com/Irrational-Encoding-Wizardry/vs-preview/commit/eaddb47b731d5fe02bcd93447098485c7cbe961c


Rotate bubble:// stream

Hello :)
I would like to rotate 90° my bubble stream, how to do this like the ffmpeg input #rotate=90 ?
Thanks :)

streams:
  camera1: bubble://...
  camera2: ffmpeg:camera1#video=h264#rotate=90


Store saved subtitle path in Subtitle class after call save_subtitles

Related to https://github.com/Diaoul/subliminal/issues/768
@Diaoul what do you think?
ping @ratoaq2

I don't like it as the Subtitle class is what allows to represent a subtitle from a provider POV. I see no added value in doing this and this adds coupling between the Subtitle class and the saving functions.

Ok thanks


Missing index.html

When I do ALGet:Managage packages I get the following error window;

I have examined the contents the the extension directories and cannot locate and index.html

Hi @TrippyZ
Thanks for reporting this issue. Please update to version 0.0.3, there it should be fixed.
~Chris


[SPARK-35829][SQL] Clean up evaluates subexpressions and add more flexibility to evaluate particular subexpressoin

What changes were proposed in this pull request?

This patch refactors the evaluation of subexpressions.
There are two changes:

Clean up subexpression code after evaluation to avoid duplicate evaluation.
Evaluate all children subexpressions when evaluating a subexpression.

Why are the changes needed?

Currently subexpressionEliminationForWholeStageCodegen return the gen-ed code of subexpressions. The caller simply puts the code into its code block. We need more flexible evaluation here. For example, for Filter operator's subexpression evaluation, we may need to evaluate particular subexpression for one predicate. Current approach cannot satisfy the requirement.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing tests.

Test build #140028 has started for PR 32980 at commit 59c7213.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44555/

Test build #140030 has started for PR 32980 at commit e8a03f5.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44555/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44557/

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44557/

Test build #140028 has finished for PR 32980 at commit 59c7213.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SubExprEliminationState(

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

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

Test build #140030 has finished for PR 32980 at commit e8a03f5.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SubExprEliminationState(

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

cc @rednaxelafx too FYI

cc @maropu @cloud-fan

Test build #140069 has started for PR 32980 at commit 777b9a4.

Test build #140069 has finished for PR 32980 at commit 777b9a4.

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

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

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44597/

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

Hmm, directly use the values in the map causes some test failure.

Test build #140099 has started for PR 32980 at commit c774797.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44627/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44627/

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

Test build #140102 has started for PR 32980 at commit 4574b30.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44630/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44630/

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

Test build #140099 has finished for PR 32980 at commit c774797.

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

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

Test build #140102 has finished for PR 32980 at commit 4574b30.

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

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

Any more thoughts? @cloud-fan @maropu

@cloud-fan Could you take another look? Thanks!

Test build #140369 has started for PR 32980 at commit 2ecb592.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44885/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44885/

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

Test build #140369 has finished for PR 32980 at commit 2ecb592.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class MergedBlockMetaRequest extends AbstractMessage implements RequestMessage
public class MergedBlockMetaSuccess extends AbstractResponseMessage
public abstract class AbstractFetchShuffleBlocks extends BlockTransferMessage
public class FetchShuffleBlockChunks extends AbstractFetchShuffleBlocks
public class FetchShuffleBlocks extends AbstractFetchShuffleBlocks
final case class FileNameSpec(prefix: String, suffix: String)
 class AvroSchemaHelper(avroSchema: Schema, avroPath: Seq[String])
class DecimalOps(FractionalOps):
class IntegralExtensionOps(IntegralOps):
class FractionalExtensionOps(FractionalOps):
class StringExtensionOps(StringOps):
           new_class = type(\"NameType\", (NameTypeHolder,),
class GroupBy(Generic[T_Frame], metaclass=ABCMeta):
class DataFrameGroupBy(GroupBy[DataFrame]):
class SeriesGroupBy(GroupBy[Series]):
       new_class = type(\"NameType\", (NameTypeHolder,),
class SparkIndexOpsMethods(Generic[T_IndexOps], metaclass=ABCMeta):
class SparkSeriesMethods(SparkIndexOpsMethods[\"ps.Series\"]):
class SparkIndexMethods(SparkIndexOpsMethods[\"ps.Index\"]):
class RollingAndExpanding(Generic[T_Frame], metaclass=ABCMeta):
class RollingLike(RollingAndExpanding[T_Frame]):
class Rolling(RollingLike[T_Frame]):
class RollingGroupby(RollingLike[T_Frame]):
class ExpandingLike(RollingAndExpanding[T_Frame]):
class Expanding(ExpandingLike[T_Frame]):
class ExpandingGroupby(ExpandingLike[T_Frame]):
sealed trait FieldName extends LeafExpression with Unevaluable
case class UnresolvedFieldName(name: Seq[String]) extends FieldName
case class ResolvedFieldName(name: Seq[String]) extends FieldName
case class Cast(
case class GetTimestampWithoutTZ(
case class ParseToTimestampWithoutTZ(
case class RebalancePartitions(
trait AlterTableCommand extends UnaryCommand
case class AlterTableDropColumns(
case class AlterTableRenameColumn(
    new SparkException(s\"Cannot find catalog plugin class for catalog '$name': $pluginClassName\")
    new SparkException(\"Cannot instantiate abstract catalog plugin class for \" +
    new SparkException(s\"Can not load in UserDefinedType $
final class ParquetReadState
case class MergingSessionsExec(
class MergingSessionsIterator(
trait StatefulOperatorCustomMetric
case class StatefulOperatorCustomSumMetric(name: String, desc: String)
trait TestGroupState[S] extends GroupState[S]

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

Test build #140394 has finished for PR 32980 at commit 014bc8b.

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

@maropu Any more comments? Otherwise I will merge this later. Thanks.

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

Thanks for review! Merging to master.

Thank you, @viirya . late lgtm.


Unclear source: "ExpStaleUserId - Indicator for configurations User ID matching with session User ID"

Hello,
please check this source string, it is not clear what is intended: "ExpStaleUserId - Indicator for configurations User ID matching with session User ID"

Does it mean "Indicator for configurations where User ID is matching with session User ID" or "Indicator for configurations where User ID is NOT matching with session User ID"
Kind regards,
Anne H.., QC

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

ID: 144e9c53-1af0-12f0-c083-7775acdc791e
Version Independent ID: 147f8437-1e9b-1f17-6a20-43904596003b
Content: Essential services for Office - Deploy Office
Content Source: DeployOffice/privacy/essential-services.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Webeditor mol wt calculations are incorrect

The following structure is entered as HELM and displays correctly.
RNA1{R(A)P.R(C)P.R(G)P}|RNA2{P.R(C)P.R(G)P.R(T)}$RNA1,RNA2,2:pair-9:pair|RNA1,RNA2,5:pair-6:pair|RNA1,RNA2,8:pair-3:pair$$$V2.0

If I copy the molfile of the structure from the structure box and paste it into ChemDraw I get the right structure and the correct mol wt of 1986.21.
The HELM webservices also calculate a mol wt of 1986.21.
However the mol wt calculated by the webeditor is incorrect.

Looking more carefully - I think the webeditor is adding together the mol wts of the individual unconnected monomers so it is always giving a mol wt that is too high. The webeditor mol wt includes the H and OHs that are lost on connection.

Fixed in 2018-10-15 update

Still wrong. Try PEPTIDE1{G.G}$$$$V2.0
The webeditor gives a mol wt of 150 when it should be 135.


SMD redirects + smart defaults

What's this PR do?

Temporarily redirects /donateform and /memberform to /donate, which will be the SMD campaign page.
Makes it so /donate doesn't 404 when an amount query parameter is not provided

Why are we doing this? How does it help us?
Amanda request so they can better track money earned during SMD.
How should this be manually tested?

Visit both /donateform and /memberform. No matter the query params appended to each, they should redirect to /donate?campaignId=70146000000M0pM.
Visit /donate with no params. It should default to $10/month.
Visit with an amount param but not an installmentPeriod one. It should show the amount and default to monthly.
Visit with an installmentPeriod=/monthly/yearly/once param but not an amount param. If monthly, the amount should be 10. If yearly, 75. If once, 60.
Visit with a bogus installmentPeriod param and no amount param. It should default to $10/month.
Visit with a bogus installmentPeriod param but a valid amount param. It should show the amount and default to monthly.

Have automated tests been added?
No.
Has this been tested on mobile?
NA.
Are there performance implications?
No.
What are the relevant tickets?
Off-sprint SMD prep.
How should this change be communicated to end users?
NA.
Next steps?
NA.
Smells?
The redirects are temporary, so meh.
TODOs:

[x] Confirm amounts with Amanda.

Has the relevant documentation/wiki been updated?
NA.
Technical debt note
Same.

WFM, see comment.


Add new Azure stencils

https://docs.microsoft.com/en-gb/azure/architecture/icons/?WT.mc_id=docsmsft-twitter

Did the licensing change?

Yes, they updated it.


Make a plain compiled version for generic usage.

Would be nice to  have a compiled JS file so I can drop it into any project, instead of relying on node modules. Also registering it as a package on Bower would be awesome.

Added xcase to bower and added a dist directory with precompiled standalone modules. You can just load the script and use xcase.camelize. Anything else?

Wow that was fast. Nope that's all! Thank you so much!
On Wed, Sep 21, 2016 at 12:47 AM Damian Kaczmarek
<
mailto:Damian Kaczmarek<EMAIL_ADDRESS>
wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }
Added xcase to bower and added a
dist
directory with precompiled standalone modules. You can just load the script and use
xcase.camelize
. Anything else?
—
You are receiving this because you authored the thread.
Reply to this email directly,
https://github.com/encharm/xcase/issues/1#issuecomment-248536967
, or
https://github.com/notifications/unsubscribe-auth/AB0LnhJ8EYY7J4nFrTushhhEdwfTw-5jks5qsOEvgaJpZM4KCS1r
.

Sure thing. Please re-open this ticket if you find any issues.


Bump alpine version

Description
Changes proposed in this pull request:

Bumped alpine version

Related issue(s)

/retest


Not installable using ansible-galaxy

When trying to install with ansible-galaxy I get the error message that this collection does not exist. Also if you search on https://galaxy.ansible.com/search there is no chance to find this collection either with citrix, nor with netscaler or adc
-> ansible-galaxy collection install citrix.adc
-> Process install dependency map
ERROR! Failed to find collection citrix.adc:*

The modules are not yet uploaded to Ansible Galaxy.
You can install them with the ansible-galaxy command line tool from this repository.
See this section of the README for details.


Feature request – plugin syncing

Would be great if you could add plugin syncing to this so that I can sync plugins (and version) between different Macs? I run Sketch non-concurrently on two machines (desktop/laptop) and keeping my plugin sets up-to-date and in-sync is tedious, to say the least!

Ideally, would this feature automatically install and update all your plugins, or would you rather get notified first before anything is installed or updated?


Error：Index was outside of the bounds of the array

I have used ssd-mobilenet-v1 to train my pb file,and edit the label txt file.
And run the detect demo,it cames out that error.
I have checked the detail!

I only got 5 objects to detect,and the valve is 5,so the label =  this.labels[5],so then out of the index.
I do not know how to fix this,cause the classes's valve came from the DetectAsync.
would you help?

@HolyShitKillingMachine,
Send me your model and labels, I'll check.

@Syn-McJ I have sent it to your<EMAIL_ADDRESS>

@Syn-McJ how about the pb file and the label files,are they ok for use?

@HolyShitKillingMachine, did you check your model with python before using it in my example?
I'm checking it now and it doesn't seem to work. Additionally, I can see it producing labels with index 5 while you have only 5 labels which means max index is 4, therefore it causes out of range exception.
This repository isn't meant for teaching how to train tensorflow models, for this please refer to the documentation at tensorflow.org.
Please refrain from creating new tickets before you made sure that your model works well with python inference code.


Why is query-string fixed to v5? This cause multiple query string in my final webapp bundle

Expected Behavior
I expect one query-string module in my final web app bundle
Current Behavior
strict-uri-encode (Found 2 resolved, 2 installed, 2 depended. Latest 2.0.0.)
1.1.0 ~/strict-uri-encode
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> query-string@5 -><EMAIL_ADDRESS>2.0.0 ~/@react-navigation/core/~/strict-uri-encode
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>Possible Solution
Do not fix query string version and upgrade it to latest
Steps to Reproduce
Not necessary
Environment

JS SDK Version: 8.16.1
Installation Method: yarn
Browser and Version: chrome latest

Hi @kopax-polyconseil
Thanks for using our SDKs.
Using the @latest version for one package might also have the same issue because other packages which have the same dependency might not use the same criteria.
You can use the npm dedupe to reduce the duplication in the package tree. https://docs.npmjs.com/cli/v8/commands/npm-dedupe.
Hope this works.

Thanks for your reply, problem here is that those package are not maintained anymore, perhaps an upgrade of the deps on all the dep tree would be the right move ? There's a reason why new versions come out, I hope you know it.

@yuhao900914 also we use yarn, and
dka@dka:[~/workspace/github.com/pass-culture/pass-culture-app-native (PC-16624)]: yarn dedupe query-string
yarn dedupe v1.22.15
error The dedupe command isn't necessary. `yarn install` will already dedupe.
info Visit https://yarnpkg.com/en/docs/cli/dedupe for documentation about this command.
dka@dka:[~/workspace/github.com/pass-culture/pass-culture-app-native (PC-16624)]: ^C
dka@dka:[~/workspace/github.com/pass-culture/pass-culture-app-native (PC-16624)]: yarn dedupe --strategy highest
yarn dedupe v1.22.15
error The dedupe command isn't necessary. `yarn install` will already dedupe.
info Visit https://yarnpkg.com/en/docs/cli/dedupe for documentation about this command.
dka@dka:[~/workspace/github.com/pass-culture/pass-culture-app-native (PC-16624)]: yarn dedupe --check
yarn dedupe v1.22.15
error The dedupe command isn't necessary. `yarn install` will already dedupe.
info Visit https://yarnpkg.com/en/docs/cli/dedupe for documentation about this command.

Hi @kopax-polyconseil
yarn install --flat is the equivalent to yarn dedupe. yarn install not dedupe the package very well.
Another workaround is to add a resolution in your package.json.
{
"name": "amplitude-js-demo",
"version": "0.1.0",
"private": true,
"resolutions": {
"query-string": "^7.1.1"
},
xxxx
}
The query-string@5 to the latest version has breaking changes. To support the older browser, we need to use query-string@5.

Thanks for your reply, on a big project like ours yarn install --flat is a bit risky, I've had a try and it's almost all our dependency that will move. I am not willing to take this risk, it will touch our react native and also the web application, while I only want to optimize the web build. But thanks for offering.
I manage to solve the dedupe of this problem using webpack resolve alias, and I will have another try using the resolution :)

Snyk jobs are now failing in our pipelines because of a downstream DoS vulnerability coming from a dependency in query-string:
<EMAIL_ADDRESS>><EMAIL_ADDRESS>><EMAIL_ADDRESS>
This has been fixed in v0.2.2 of decode-uri-component, and that's used in v7.1.3 of query-string, but if this project is pinned to v5 of query-string that vulnerability will continue to exist.

same issue at 8.21.4, setting "amplitude-js": "8.21.3" in package.json removes the error


Layered tiles dont work.

When I try using multiple layers the background stays black this problem occurs even when I try to build the examples 7 and 18.

I am on windows 10 with rust 1.43.0-nightly and using version 7.0.0 of rltk.

Good catch! I goofed on the initialization - it was meant to call with_sparse_console_no_bg. Thanks!


Update check22

Returned value is lower case "false". Thus, prowler will not detect a missing log file validation (false negative)
Probably, this behaviour should also be taken into account for other checks.
A quick grep for "False" indicated:

check_21
check_extra739
check_extra737
check_extra715
check_extra740
check_extra73

Ideally, the checks should be case-insensitive for more flexibility. But in bash this is somewhat unwieldy...

You are right, I'm going to see what is the best way to make those checks more consistent and fix it. I'll do it on devel branch first and we can test them before hand.

Ok, I have been taking a deep look to all checks you mentioned and this is what I have seen:

check22: awscli output is in text, so it is True or False (IF condition is correct), with json output it is lowercase true or false.
check21: awscli output is in text, so it is True or False (IF condition is correct)
check_extra739: no longer exist (removed in devel branch so far) because it is redundant with extra717 that works correctly despite the output is lowercase.
check_extra737: awscli output is in text, so it is True or False (IF condition is correct)
check_extra715: awscli output is in text, so it is True or False (IF condition is correct)
check_extra740: awscli output is in text, so it is True or False (IF condition is correct)
check_extra73: doesn't apply this case, there is not usage of true or false conditionals

You can run prowler like bash -x ./prowler -c check22 to see exactly the command and test with --output text and --output json to see what I'm saying. Most of the prowler checks are using --output text. Please, also check that you have the latest version of awscli installed, this is my setup: aws-cli/1.16.133 Python/2.7.16 Darwin/18.5.0 botocore/1.12.123
Please, let me know if it makes sense for you as well and we can close this issue.
Thanks!

Thanks for your investigation.
I have to apologize, the false negative in check22 was NOT caused by the lower/upper case, I did not thoroughly check this.
Instead, it is caused by the region. check22 will use the default region set by prowler, while trails may be residing actually in any region.
On the one hand, the describe-trails command will yield all trails for all regions when there is no --trail-name-list argument, regardless of the passed argument to the --region parameter.
On the other hand, when trying to get the validation enabled status of a specific trail, the --region argument has to match the region of the trail, otherwise an empty response is returned in CLI text mode. check22 does not take this into account, since any response that is not "False" will be considered "True".
So my proposal would be to get all output from a single describe-trails command and then parse the output. Would do you think about this?


swagger /ancestry/{ancestry_name} with_vulnerabilities

Using the API V3 trying to get the vulnerabilities from a given scanned image
it looks like the with_vulnerabilities parameter  is not respected
ref swagger spec
https://app.swaggerhub.com/apis/coreos/clair/3.0#/AncestryService/GetAncestry
Expecting a list of vulnerabilities  for a given image, only getting list of

Clair version/image:  Latest (using Helm)
Clair client name/version:  yebinama/paclair
Host OS: docker ubuntu
Kernel (e.g. uname -a): 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 GNU/Linux
Kubernetes version (use kubectl version):  GitVersion:"v1.11.2"
Helm version (use helm version):
Network/Firewall setup:  N/A (test open)

We don't respect that any more to simplify the API.
The swagger file on swagger hub is not updated. @jzelinskie
The V3 API is still unstable.

how do i get a list of vulnerabilities currently with V3

By API definition, it should directly give the vulnerabilities.
BTW, the master branch is now in half broken state, If you want to try out the API V3, you need commit on or short before:
8d5a0131c48d0812d1dd53b1af8e24ae4e51c4ba

ok, will stick with V2 for now then

Thanks for the help


GDScript LSP parse_local_script() crashes the editor

Godot 3.2.2 beta4
After reading how https://github.com/GDQuest/gdscript-docs-maker/blob/4c3020988c2542737abf467a7ae40d9f744e544c/godot-scripts/Collector.gd#L74 was written, I discovered there is an apparently undocumented access to GDScript language server, which I'd find very useful to have information about.
So I tried to grab that data and see what it provides, using a similar script. I used an EditorPlugin because that singleton doesn't exist in non-editor launches. Unfortunately, it crashes the editor when my script gets to call workspace.parse_local_script(file).
var data := {
	name = ProjectSettings.get_setting("application/config/name"),
	description = ProjectSettings.get_setting("application/config/description"),
	version = ProjectSettings.get_setting("application/config/version"),
	classes = []
}
var workspace = Engine.get_singleton('GDScriptLanguageProtocol').get_workspace()
for file in ["addons/zylann.gdscript_doc/gdscript_extractor.gd"]:
	workspace.parse_local_script(file) # CRASHES
	var symbols: Dictionary = workspace.generate_script_api(file)
	data["classes"].append(symbols)
var json = JSON.print(data, "   ")
var f = File.new()
f.open("result.json", File.WRITE)
f.store_string(json)
f.close()

ERROR: get: Condition "!res" is true. Returned: *res
   At: ./core/hash_map.h:304

Test project:
GDScriptDocCrash.zip
Go to ProjectSettings and enable the plugin.

Had to tweak the data dictionary so that it compiles in the master branch, the name = value Dictionary syntax is broken right now - likely due to StringName changes:
var data := {
	"name": ProjectSettings.get_setting("application/config/name"),
	"description": ProjectSettings.get_setting("application/config/description"),
	"version": ProjectSettings.get_setting("application/config/version"),
	"classes": []
}

The original MRP is a bit evil as it's a tool script that tries to parse itself... but the same crash happens when parsing another script without circular reference.

Will this be fixed in 3.2? Also is this a misuse? The GDScript docs maker uses it, and I would really like to use that data source as well...

Will this be fixed in 3.2?

Yes, that's what this label means:

Also is this a misuse?

I think so, but I'm not familiar enough with this to confirm 100%. Reading the code, it seems latest_client_id (which was invalid and triggering a crash in your code) is only assigned in GDScriptLanguageProtocol::poll(), so I guess you need to poll().

I can't find any place in this repo where poll is called: https://github.com/GDQuest/gdscript-docs-maker/search?q=poll&unscoped_q=poll
It just calls parse_local_script directly, and the script is called from a CLI execution of Godot.

Maybe @NathanLovato and @Razoric480 (who authored the GDQuest script) can weigh in.
Maybe parse_local_script could be made not to call notify_clients if there are no clients to notify. After my fix, it will currently raise an error when notify_clients is called without clients, but parse_local_script itself should succeed.

I can't really comment on this issue, despite me and Nathan working on the script that uses it; we never really encountered an issue with it, maybe because we specifically had used it in a way that it wouldn't reference itself (having the scripts in the root of the project, pointing to a specific directory) or because we run it from inside a launched editor instance.
Either way, it was sheer happenstance rather than a deliberate bug avoidance.


feat: Added option to get JWT from 'access_token' query parameter from original url header value

I tried using this solution but ran into an issue for some edge cases where we need to validate a JWT passed as access_token query parameter.
I messed around a bit with the nginx.ingress.kubernetes.io/auth-snippet and nginx.ingress.kubernetes.io/auth-proxy-set-headers annotations of the nginx-ingress controller, but it seems accessing the query parameters is not possible in those scenarios. I dug into it, it's nginx-ingress creates an intermediate internal location{} directive for the external auth service which causes the original request context to get lost.
So the next best thing I could think of was to make this service aware of such a query parameter and get if from the x-original-url header that nginx-ingress passes to the auth service.
Let me know if you have feedback or issues you'd like me to resolve.
From a security perspective, passing JWT's in query parameters is not a good practice, since they have high chance to be logged in various places, but alas in some scenarios (websockets, mobile apps which open urls in external browsers, ...) this is AFAIK the only solution.

Hey, thank you for PR, and I think makes sense to me.
Could please write a test or two for this? I would the /auth endpoint to have 100% code coverage.

Hey, thank you for PR, and I think makes sense to me.
Could please write a test or two for this? I want the /auth endpoint to have 100% code coverage.

Sorry for taking so long, I've added some tests around this.
I also added your docker username to the image name in the tests where the container is created, since it didn't work for me like it was, I assume because you're logged in with your username docker automatically prefixes it when not specified.
I also couldn't get all tests to pass since I don't have your client secret, I'll open an issue to refactor these tests so we can either test using oauth credentiallsl which can be made public, or by making it easier to switch to your own oauth provider

@AlexGoris-KasparSolutions, its released not, thank you and apologies for the delay.


Implement sensor handler

Issue Description
This is a periodic task that is constantly checking an internal queue. When it contains at least one element, the communication with the navigation layer starts. It sends the ID of the sensor that the operator requests to read, and waits for a response.
If another reading request arrives, it is added to the queue until the govern layer receives a response
Additional Info
Refer to the issue #3 for further details

Futher testing needed


Swift 2 Error handling

I’ve made a few changes to support Swift 2’s new error handling.
The XMLIndexer now has a new enum called XMLIndexerError. This is a
printable enum with different cases for different errors (Attribute,
Key, Index…).
The old XMLIndexer.Error case now takes an XMLIndexerError as
associated type.
if possible this old case got replaced by trowing an error.
Unfortunately subscripts can’t throw yet, because of that the index and
key subscript of XMLIndexer return an .Error(XMLIndexerError).
But I’ve added a key(String) and idx(Int) function which do the same as
the subscripts and throw.
To avoid catching at every XMLIndexer initialisation I’ve added two new
inits in XMLIndexer: one takes an XMLElement and the other a
LazyXMLParser. Both can’t fail.
The old init(AnyObject) throws an XMLIndexerError.Init and should
probably be deprecated.
The new error handling would look something like this.
do {
     return try xml.key("what").key("subelement").idx(5).key("no match")
} catch XMLIndexer.XMLIndexerError.Key(let key) {
    //handle wrong key
} catch XMLIndexer.XMLIndexerError.Index(let idx) {
   //handle wrong index
} catch let indexerError as XMLIndexer.XMLIndexerError {
   //handle any other XMLIndexerError
}  catch {
   //handle any other error (like default case)
}

Thanks for the PR! I do like that this approach to error handling is more intent revealing in terms of what the error actually is. Give me some time to pull down the code and check into it.

I think I lean towards having XMLIndexerError be in the outer scope instead of under XMLIndexer so that the catch statements look like this instead:
var err: XMLIndexerError?
defer {
    expect(err).toNot(beNil())
}
do {
    try xml!.key("what").key("subelement").idx(5).key("nomatch")
}
catch let error as XMLIndexerError {
    err = error
}
catch { err = nil }

I'm also thinking about the method names for key and idx - whether or not they should be something like byKey and byIndex. Maybe just spell out idx to index for now.

I also don't like the long name, but I think the enum should stay in the XMLIndexer's namespace. I'd propose to rename it to just Error, with that u could access the enum with XMLIndexer.Error.
I like the method names with the "by" prefix, although I think the names should be as short as possible. But I'd use the byIndex and byKey names.
With the latest beta release they added documentation support for the throwing stuff. Probably no big deal but definitely worth looking into it, because then everyone can see which errors can occur.

Great suggestion regarding having it as XMLIndexer.Error - results in fewer types in SWXMLHash scope, but also clearly defines which errors XMLIndexer can throw. :+1:
And agreed regarding having shorter names for accessing indexes/keys - to be honest, I think my favorite option would be to have Swift support subscripts that throw! Maybe a later beta...
Regarding documentation, yes, it would definitely be good to get that updated, but I'm fine with holding off on getting the docs updated after merging this PR in. Before this goes to master, the docs, pods and carthage notes will all need to be updated anyway.

@leoMehlig were you going to get a chance to take a look at my feedback (i.e. rename XMLIndexerError to Error and keeping it under XMLIndexer, plus adding the by prefix)? If not, I can manually merge this in with those fixes. No big deal either way.

I'll commit the changes tomorrow, it would be great if you could update the documentation.

Sounds great, thanks! And I'll take the docs.

I see the commit - I'll get this merged in. Thanks so much @leoMehlig!


Corrected alignment of 'Add port' section

Earlier the alignment was not perfect for 'Add Port' section. The user was not able to see the ports that he was entering. I have made the necessary changes related to spacing and cols for the same.

Thanks!


Regent: Make format.print* functions work with print_once

It would be good to make the format library work with print_once and friends so that it works with DCR without duplicate output.

It only took 4 years, but I got around to doing this for the SCR removal so that all the tests can be replicable now.


Refactor: simplify scripts

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

What does this PR do?
Fixes # (issue).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@ethanwharris cold ou pls check that the thumb pat is correct after refactor :rabbit:

I know that this file is not that large but since we already have a quite large history and every bit counts, I'd rather not add this

I would not have much concern about thumbnails, but rather all other illustrations...
on the other hand, when someone accidentally deletes it in S3, it is lost... so that we allow images here but precommut preventing adding large files:
https://github.com/PyTorchLightning/lightning-tutorials/blob/5dd7b1c261a3fb6bd5788a9f13f7e95d3ede4987/.pre-commit-config.yaml#L21


Use find_library to search for cholmod

@haampie, I believe this should address the concerns raised in https://github.com/ROCm/hipSOLVER/pull/252#issuecomment-2144871058.


dask array gradient multiplication: error

I am trying to use dask arrays to do image processing on very large datasets. A part of this is getting the gradient, doing some processing and multiplying them with each other. However, this results in an error.
Minimal example without the processing step:
import dask.array as da
data = da.random.random((100, 100), chunks=(10, 10))
grad0, grad1 = da.gradient(data, axis=(0, 1))
(grad0 * grad1).compute()

Gives the error: ValueError: operands could not be broadcast together with shapes (8,12) (10,10).
Python 3.6.6rc1 (most recent version in Debian Unstable), and dask 0.18.0 (the most recent version in PyPI).
The error also occurred with dask 0.17.5 (most recent Debian Unstable), but giving a slightly different error: ValueError: operands could not be broadcast together with shapes (8,10) (10,10).
(Originally posted on SO: https://stackoverflow.com/questions/50913251/dask-array-gradient-multiplication)

cc @jakirkham
On Mon, Jun 18, 2018 at 1:00 PM, Magnus Nord<EMAIL_ADDRESS>wrote:

I am trying to use dask arrays to do image processing on very large
datasets. A part of this is getting the gradient, doing some processing and
multiplying them with each other. However, this results in an error.
Minimal example without the processing step:
import dask.array as da
data = da.random.random((100, 100), chunks=(10, 10))
grad0, grad1 = da.gradient(data, axis=(0, 1))
(grad0 * grad1).compute()
Gives the error: ValueError: operands could not be broadcast together
with shapes (8,12) (10,10).
Python 3.6.6rc1 (most recent version in Debian Unstable), and dask 0.18.0
(the most recent version in PyPI).
The error also occurred with dask 0.17.5 (most recent Debian Unstable),
but giving a slightly different error: ValueError: operands could not be
broadcast together with shapes (8,10) (10,10).
(Originally posted on SO: https://stackoverflow.com/
questions/50913251/dask-array-gradient-multiplication)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/3633, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszErS4BsyvHHidwlPvU1bV3KvWVr-ks5t99y4gaJpZM4UsIjv
.

Thanks for the bug report and nice MRE, @magnunor, and the ping, @mrocklin.
Am able to reproduce it. Unfortunately don't know what is going on ATM.
Seems like the Dask Arrays report their correct shapes individually and have the correct shape when computed. The chunks are all reported as 10 on all sides as expected. Also am getting equivalent results for grad0 and grad1 from NumPy and Dask when using the same data for both.
My guess is the chunking is off somehow internally. Will need to look into it. Probably won't have a chance until later in the week.

FWIW can reproduce this issue independently of gradient using Python 3.6.5 and Dask 0.18.0 in the example below. So either there is a bug in my syntax below or there is a bug in map_overlap. Would be good to know either way.

In [1]: import dask.array as da

In [2]: a = da.random.random((100, 100), chunks=(10, 10))

In [3]: r = [
   ...:     a.map_overlap(
   ...:         lambda a: a + 1,
   ...:         dtype=a.dtype,
   ...:         depth={j: int(i == j) for j in range(a.ndim)},
   ...:         boundary="none"
   ...:     )
   ...:     for i in range(a.ndim)
   ...: ]

In [4]: r[0] * r[1]
Out[4]: dask.array<mul, shape=(100, 100), dtype=float64, chunksize=(10, 10)>

In [5]: (r[0] * r[1]).compute()
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-5-e550d80d199d> in <module>()
----> 1 (r[0] * r[1]).compute()

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/base.py in compute(self, **kwargs)
    154         dask.base.compute
    155         """
--> 156         (result,) = compute(self, traverse=False, **kwargs)
    157         return result
    158

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/base.py in compute(*args, **kwargs)
    398     keys = [x.__dask_keys__() for x in collections]
    399     postcomputes = [x.__dask_postcompute__() for x in collections]
--> 400     results = schedule(dsk, keys, **kwargs)
    401     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    402

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/threaded.py in get(dsk, result, cache, num_workers, **kwargs)
     73     results = get_async(pool.apply_async, len(pool._pool), dsk, result,
     74                         cache=cache, get_id=_thread_get_id,
---> 75                         pack_exception=pack_exception, **kwargs)
     76
     77     # Cleanup pools associated to dead threads

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in get_async(apply_async, num_workers, dsk, result, cache, get_id, rerun_exceptions_locally, pack_exception, raise_exception, callbacks, dumps, loads, **kwargs)
    519                         _execute_task(task, data)  # Re-execute locally
    520                     else:
--> 521                         raise_exception(exc, tb)
    522                 res, worker_id = loads(res_info)
    523                 state['cache'][key] = res

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/compatibility.py in reraise(exc, tb)
     66         if exc.__traceback__ is not tb:
     67             raise exc.with_traceback(tb)
---> 68         raise exc
     69
     70 else:

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in execute_task(key, task_info, dumps, loads, get_id, pack_exception)
    288     try:
    289         task, data = loads(task_info)
--> 290         result = _execute_task(task, data)
    291         id = get_id()
    292         result = dumps((result, id))

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in _execute_task(arg, cache, dsk)
    269         func, args = arg[0], arg[1:]
    270         args2 = [_execute_task(a, cache) for a in args]
--> 271         return func(*args2)
    272     elif not ishashable(arg):
    273         return arg

ValueError: operands could not be broadcast together with shapes (8,12) (10,10)

Appears to be some sort of name overlap issue within the graph somewhere as it can be gotten by simply calling compute on both arrays in the same graph. Using either array in separate graphs does not create the same issue.

In [1]: import dask

In [2]: import dask.array as da

In [3]: a = da.random.random((100, 100), chunks=(10, 10))

In [4]: r = [
   ...:     a.map_overlap(
   ...:         lambda a: a + 1,
   ...:         dtype=a.dtype,
   ...:         depth={j: int(i == j) for j in range(a.ndim)},
   ...:         boundary="none"
   ...:     )
   ...:     for i in range(a.ndim)
   ...: ]

In [5]: r[0].compute()
Out[5]:
array([[1.5012925 , 1.0350478 , 1.88693588, ..., 1.50677206, 1.46264745,
        1.77689762],
       [1.27108289, 1.04855157, 1.79591673, ..., 1.66965247, 1.69529417,
        1.02000646],
       [1.77773522, 1.97625295, 1.53803203, ..., 1.730561  , 1.57557426,
        1.72531022],
       ...,
       [1.18710225, 1.88434072, 1.17392878, ..., 1.28326933, 1.28642445,
        1.01822912],
       [1.91152816, 1.96181514, 1.55454789, ..., 1.82706619, 1.88655585,
        1.14938517],
       [1.16915801, 1.30166171, 1.18227674, ..., 1.85113454, 1.46219155,
        1.37203518]])

In [6]: r[1].compute()
Out[6]:
array([[1.5012925 , 1.0350478 , 1.88693588, ..., 1.50677206, 1.46264745,
        1.77689762],
       [1.27108289, 1.04855157, 1.79591673, ..., 1.66965247, 1.69529417,
        1.02000646],
       [1.77773522, 1.97625295, 1.53803203, ..., 1.730561  , 1.57557426,
        1.72531022],
       ...,
       [1.18710225, 1.88434072, 1.17392878, ..., 1.28326933, 1.28642445,
        1.01822912],
       [1.91152816, 1.96181514, 1.55454789, ..., 1.82706619, 1.88655585,
        1.14938517],
       [1.16915801, 1.30166171, 1.18227674, ..., 1.85113454, 1.46219155,
        1.37203518]])

In [7]: dask.compute(*r)
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-7-8d1667b13e30> in <module>()
----> 1 dask.compute(*r)

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/base.py in compute(*args, **kwargs)
    398     keys = [x.__dask_keys__() for x in collections]
    399     postcomputes = [x.__dask_postcompute__() for x in collections]
--> 400     results = schedule(dsk, keys, **kwargs)
    401     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    402

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/threaded.py in get(dsk, result, cache, num_workers, **kwargs)
     73     results = get_async(pool.apply_async, len(pool._pool), dsk, result,
     74                         cache=cache, get_id=_thread_get_id,
---> 75                         pack_exception=pack_exception, **kwargs)
     76
     77     # Cleanup pools associated to dead threads

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in get_async(apply_async, num_workers, dsk, result, cache, get_id, rerun_exceptions_locally, pack_exception, raise_exception, callbacks, dumps, loads, **kwargs)
    519                         _execute_task(task, data)  # Re-execute locally
    520                     else:
--> 521                         raise_exception(exc, tb)
    522                 res, worker_id = loads(res_info)
    523                 state['cache'][key] = res

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/compatibility.py in reraise(exc, tb)
     66         if exc.__traceback__ is not tb:
     67             raise exc.with_traceback(tb)
---> 68         raise exc
     69
     70 else:

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in execute_task(key, task_info, dumps, loads, get_id, pack_exception)
    288     try:
    289         task, data = loads(task_info)
--> 290         result = _execute_task(task, data)
    291         id = get_id()
    292         result = dumps((result, id))

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in _execute_task(arg, cache, dsk)
    268     elif istask(arg):
    269         func, args = arg[0], arg[1:]
--> 270         args2 = [_execute_task(a, cache) for a in args]
    271         return func(*args2)
    272     elif not ishashable(arg):

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in <listcomp>(.0)
    268     elif istask(arg):
    269         func, args = arg[0], arg[1:]
--> 270         args2 = [_execute_task(a, cache) for a in args]
    271         return func(*args2)
    272     elif not ishashable(arg):

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/local.py in _execute_task(arg, cache, dsk)
    269         func, args = arg[0], arg[1:]
    270         args2 = [_execute_task(a, cache) for a in args]
--> 271         return func(*args2)
    272     elif not ishashable(arg):
    273         return arg

/zopt/conda3/envs/nanshenv3/lib/python3.6/site-packages/dask/array/core.py in concatenate3(arrays)
   3710             while arr.ndim < ndim:
   3711                 arr = arr[None, ...]
-> 3712         result[idx] = arr
   3713
   3714     return result

ValueError: could not broadcast input array from shape (10,11) into shape (10,10)

In [8]: dask.compute(*(e.persist() for e in r))
Out[8]:
(array([[1.5012925 , 1.0350478 , 1.88693588, ..., 1.50677206, 1.46264745,
         1.77689762],
        [1.27108289, 1.04855157, 1.79591673, ..., 1.66965247, 1.69529417,
         1.02000646],
        [1.77773522, 1.97625295, 1.53803203, ..., 1.730561  , 1.57557426,
         1.72531022],
        ...,
        [1.18710225, 1.88434072, 1.17392878, ..., 1.28326933, 1.28642445,
         1.01822912],
        [1.91152816, 1.96181514, 1.55454789, ..., 1.82706619, 1.88655585,
         1.14938517],
        [1.16915801, 1.30166171, 1.18227674, ..., 1.85113454, 1.46219155,
         1.37203518]]),
 array([[1.5012925 , 1.0350478 , 1.88693588, ..., 1.50677206, 1.46264745,
         1.77689762],
        [1.27108289, 1.04855157, 1.79591673, ..., 1.66965247, 1.69529417,
         1.02000646],
        [1.77773522, 1.97625295, 1.53803203, ..., 1.730561  , 1.57557426,
         1.72531022],
        ...,
        [1.18710225, 1.88434072, 1.17392878, ..., 1.28326933, 1.28642445,
         1.01822912],
        [1.91152816, 1.96181514, 1.55454789, ..., 1.82706619, 1.88655585,
         1.14938517],
        [1.16915801, 1.30166171, 1.18227674, ..., 1.85113454, 1.46219155,
         1.37203518]]))

Seems there is more to the story as both graphs only share the initial key and nothing else. 😕

In [1]: import dask.array as da

In [2]: a = da.random.random((100, 100), chunks=(10, 10))

In [3]: r = [
   ...:     a.map_overlap(
   ...:         lambda a: a + 1,
   ...:         dtype=a.dtype,
   ...:         depth={j: int(i == j) for j in range(a.ndim)},
   ...:         boundary="none"
   ...:     )
   ...:     for i in range(a.ndim)
   ...: ]

In [4]: set([k0[0] for k0 in r[0].__dask_graph__().keys()]) & set([k1[0] for k1 in r[1].__dask_graph__().keys()])
Out[4]: {'random_sample-e8aa4b91ffd47d98f1888f720767e065'}

Have moved discussion of this map_overlap problem into issue ( https://github.com/dask/dask/issues/3634 ). Also have added a workaround in PR ( https://github.com/dask/dask/pull/3635 ), which should address this issue short term until the map_overlap issue is resolved.

Addressed in PR ( https://github.com/dask/dask/pull/3643 ). Adding a test for gradient specifically in PR ( https://github.com/dask/dask/pull/3647 ).

Solved with PR ( https://github.com/dask/dask/pull/3643 ), which deals with the underlying map_overlap bug ( https://github.com/dask/dask/issues/3634 ). Added a test in PR ( https://github.com/dask/dask/pull/3647 ), which verifies that da.gradient now works for this use case.


Issue: Runs are not showing up for a new project

Traces not showing up in Langsmith
I created a new account in Langsmith. I then created an API key as was suggested on the account page and then ran this example from a python notebook.
from langchain_openai import ChatOpenAI
import os
os.environ["LANGCHAIN_TRACING_V2"] = "true"
os.environ["LANGCHAIN_API_KEY"]=""
os.environ["OPENAI_API_KEY"]=""

llm = ChatOpenAI()
llm.invoke("Hello, world!")

I got this response without any errors
AIMessage(content='Hello! How can I assist you today?', additional_kwargs={'refusal': None}, response_metadata={'token_usage': {'completion_tokens': 9, 'prompt_tokens': 11, 'total_tokens': 20, 'completion_tokens_details': {'audio_tokens': None, 'reasoning_tokens': 0}, 'prompt_tokens_details': {'audio_tokens': None, 'cached_tokens': 0}}, 'model_name': 'gpt-3.5-turbo-0125', 'system_fingerprint': None, 'finish_reason': 'stop', 'logprobs': None}, id='run-e913c0c1-de07-4a30-9470-d7ba996ab2c4-0', usage_metadata={'input_tokens': 11, 'output_tokens': 9, 'total_tokens': 20, 'input_token_details': {'cache_read': 0}, 'output_token_details': {'reasoning': 0}})
However in the default project In langsmith I don't see the traces corresponding to this execution.
I then created a new project in Langsmith and set the following environment variable
os.environ["LANGCHAIN_PROJECT"]="project-name"
I ran and still did not see any trace. I still only see the default project. The default project has several runs which were not created by me, e.g.
Sample Agent Trace
RunnableLambda
ChatpromptTemplate
etc.
What am I missing?

Did you try restarting the notebook kernel before running that cell?


socket client

What feature or new tool do you think should be added to DevToys?

tcp client
udp client
mqtt client
websocket client

Why do you think this is needed?
Integration of socket client is useful for developing socket services.
Solution/Idea
No response
Comments
No response

Hi,
Thanks for the suggestion. If I'm not wrong, this would require an internet connection, which DevToys tries to avoid relying on. If that's the case, then it isn't a great fit for this app.


change the code in "GenerateCentroid.cs"

IF IT IS A NEW FEATURE REQUEST, INCLUDE THIS PART:
Feature description
it's more timesaving to break the foreach loop when it comes to the "multPoint = true",or change the foreach to linq.

How much time do you save?

I haven't tested or made any comparison actually. Forget about the execting time cost,But why continue the foreach loop when it comes to the "multiPoint=true;"?

You are not continuing the for-loop.
When multiPoint=true there is a break out of the loop.

Currently can't test this myself but shouldn't you be able to change those lines to
output.FeatureType = input1.Features.Any(f => f.Geometry.NumGeometries > 1) ?  FeatureType.MultiPoint: FeatureType.Point;


feat(cli): add cargo android dev and cargo ios dev

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information

I am bit confused, does this PR add cargo android dev subcommand or you meant tauri android dev?

I am bit confused, does this PR add cargo android dev subcommand or you meant tauri android dev?

Ooops i guess i've used cargo-mobile too much lol


Dendrogram link/arc issue

Hi Tim,
Great service ! you're examples worked out of the box :-)
I'm trying to implement the D4 version of a cluster dendrogram (http://bl.ocks.org/mbostock/4063570).
However, I'm running into a problem which most likely isn't related to the service but I'm hoping you can help.
In my implementation, the links between nodes are filled on.
I've attached the source and screen shot of the issue.
Hope you can shed some light on this.
Dave

d3Component.txt

As you suggested, is not an issue with the service. So in principle, stackoverflow should be a better place for this kind of question.
However, in short, your implementation likely did not implement the styling applied to the links in the referenced bl.ock. I.p., the style rule for fill: none is missing, e.g.:

.link {
  fill: none;
  stroke: #555;
  stroke-opacity: 0.4;
  stroke-width: 1.5px;
}

Hope this solves your problem, otherwise, please use SO for follow-up. Thanks for understanding 😄 . T


Errors on runtest.jl on feature/bazel on local

Running julia runtest.jl gave the following output on local, any idea what to look for?
$ julia runtests.jl                                                                                ─╯
julia   00_test.jl           00_test.txt: Error During Test at /home/alex/GitHub_dev/AoC2023/runtests.jl:59
  Got exception outside of a @test
  IOError: could not spawn `julia /home/alex/GitHub_dev/AoC2023/src/julia/00_test.jl ./inputs/00_test.txt`: no such file or directory (ENOENT)
  Stacktrace:
    [1] _spawn_primitive(file::String, cmd::Cmd, stdio::Vector{Union{RawFD, IO}})
      @ Base ./process.jl:128
    [2] #760
      @ ./process.jl:139 [inlined]
    [3] setup_stdios(f::Base.var"#760#761"{Cmd}, stdios::Vector{Union{RawFD, IO}})
      @ Base ./process.jl:223
    [4] _spawn
      @ ./process.jl:138 [inlined]
    [5] #eachline#766
      @ ./process.jl:340 [inlined]
    [6] eachline
      @ ./process.jl:338 [inlined]
    [7] readlines(s::Cmd; kw::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
      @ Base ./io.jl:590
    [8] readlines
      @ ./io.jl:590 [inlined]
    [9] run_solution
      @ ~/GitHub_dev/AoC2023/runtests.jl:28 [inlined]
   [10] macro expansion
      @ ~/GitHub_dev/AoC2023/runtests.jl:62 [inlined]
   [11] macro expansion
      @ /usr/local/bin/julia-1.9.4/share/julia/stdlib/v1.9/Test/src/Test.jl:1498 [inlined]
   [12] test_lang(day_num_str::String, input_path::String, reference_output::Vector{String}, lang::String)
      @ Main ~/GitHub_dev/AoC2023/runtests.jl:60
   [13] macro expansion
      @ ~/GitHub_dev/AoC2023/runtests.jl:76 [inlined]
   [14] macro expansion
      @ /usr/local/bin/julia-1.9.4/share/julia/stdlib/v1.9/Test/src/Test.jl:1498 [inlined]
   [15] top-level scope
      @ ~/GitHub_dev/AoC2023/runtests.jl:75
   [16] include(mod::Module, _path::String)
      @ Base ./Base.jl:457
   [17] exec_options(opts::Base.JLOptions)
      @ Base ./client.jl:307
   [18] _start()
      @ Base ./client.jl:522
Test Summary:                              | Pass  Error  Total  Time
Day 00                                     |    4      1      5  0.6s
  cpp     00.cpp               00_test.txt |    2             2  0.0s
  julia   00_test.jl           00_test.txt |           1      1  0.6s
  python  00.py                00_test.txt |    2             2  0.0s
ERROR: LoadError: Some tests did not pass: 4 passed, 0 failed, 1 errored, 0 broken.
in expression starting at /home/alex/GitHub_dev/AoC2023/runtests.jl:70

Can you manually run that line or no? Maybe Julia is not available from within the Julia, somehow?
Remember, Julia does not use the shell, it directly runs the executable

Apparently I'm bad at installing Julia, resolved : )