Release Location Layer plugin 0.4.0

The ticket tracks the release of the location layer plugin 0.4.0 which brings many bug fixes and improvements to the library (see Changelog for list).
Release checklist

[x] Change version name to proper release versions in gradle.properties
[x] Publish artifacts to Maven Central
[x] Change version name back to -SNAPSHOT
[x] Update CHANGELOG.md's
[x] Tag releases in GitHub
[x] Close the respective plugin milestones

Post-release

[x] Update readme files @langsmith
[x] Update Javadoc @langsmith
[x] Update the constants.js file in android-docs repo @langsmith
[ ] Update the demo app @langsmith
[ ] Update version # in Studio Preview @langsmith
[ ] Update version # in pthfndr @langsmith

/cc: @mapbox/android

Note that this release is pending until https://github.com/mapbox/mapbox-plugins-android/pull/310 gets reviewed and merged

Build fails on release 0.4.0
Error:(2689, 55) No resource found that matches the given name (at 'navigationViewLocationLayerStyle' with value '@style/LocationLayer').

@vladgheorghe are you using 0.4.0 with the Navigation SDK?  If so, we need to update the nav SDK to accomodate the new default style provided by the plugin that was changed in https://github.com/mapbox/mapbox-plugins-android/pull/263/files#diff-a14596bc53259a2ef3bd185c1f76de34R118.  Otherwise, you will need to continue to use 0.3.0 for now

@danesfeder Yeah, I'm using navigation 0.9.0, any release date for 0.9.1 ?

@vladgheorghe working on a new release 0.10.0 for today, but we won't be able to get it in for this.  We should have a pretty quick 0.10.1 that will include these updates, but I can't provide a solid timeline on that at this time.

Error:(2689, 55) No resource found that matches the given name

In 0.4 we prefixed all our resources with mapbox_ to prevent resource conflicts. If you are customizing the user location icon inside your styles.xml, change the parent to mapbox_LocationLayer.
https://github.com/mapbox/mapbox-plugins-android/blob/c21b73ab8792a7e2bf902ded64d2f483a126e0e3/app/src/main/res/values/styles.xml#L13

I don’t have any customizations on the location layer, just the navi dependency 😔

@vladgheorghe as @danesfeder mentioned then, it will need to be fixed upstream in nav repo, sorry about this.
@langsmith, i've opened tickets in many of the app repos to address updating the plugins to the latest version. Going ahead and checking off these items here so I can close this.


Update main.415 abstract

https://acl2020.rocket.chat/channel/presenter-helpdesk?msg=ojJGg6TF4kZB9DcDA

Hi, same issue as Paul -- for my paper here on the virtual acl website https://virtual.acl2020.org/paper_main.415.html the abstract was updated quite a bit for camera-ready (camera-ready abstract here: https://www.aclweb.org/anthology/2020.acl-main.415/), and also now includes the link to the data and site. It would be awesome if it were possible to update. Thanks!

@hao-fang I can do this update

Thanks @anaerobeth


Set init_system fact

The ceph-osd role currently uses ansible_service_mgr, which is a fact
only available on ansible 2.x and greater.  This commit sets a similar
fact called init_system which will store the contents of /proc/1/comm
(systemd, init, etc.)
This commit partially resolves [1].
[1] https://github.com/ceph/ceph-ansible/issues/741

Does anyone know if this will work w/ docker?  Do we have a docker CI job that will fail if not?

@mattt416 we don't have a Docker CI yet :-(
The patch looks good though, thanks!


python without debugging won't start if there is a breakpoint

VSCode Version: 1.33.1
OS Version:Linux 5.0.7-200.fc29.x86_64
Steps to Reproduce:

Open Python code
create a breakpoint
run python without debugging (ctrl+F5)

Terminal output:
cd /home/user/dev/Pytool ; env PYTHONIOENCODING=UTF-8 PYTHONUNBUFFERED=1 /usr/bin/python3 /home/user/.vscode/extensions/ms-python.python-2019.4.11987/pythonFiles/ptvsd_launcher.py --default --nodebug --client --host localhost --port 36019 /home/user/dev/Pytool/mypytool.py
Terminated

Does this issue occur when all extensions are disabled?: Yes/No
Not sure - Python extension is required
Enabled Extensions:

Anaconda Extension PAck 1.0.1
Bookmarks 10.4.3
C/C++ 0.221
Gist 3.0.3
Git History 0.4.6
GitLens - 9.6.3
markdownlint 0.26.0
Python 2019.4.11987
Syncing 2.1.6
OpenCL 0.5.2
VEX 0.4.0
TAML 0.4.0

How do you know it’s an extension? If you have such info, could you please at least provide information- which extension ??

Python extension. https://github.com/Microsoft/vscode-python


Task broadcasting

Allow to send task to multiple agents with one request from client (important).

[ ] sutcp
Probably there should be button next to group name.
[x] sutserver
Main broadcasting logic of course is in server.
[x] sutagent
No special changes in agent required.

HTTP API
Change /tasks endpoint a bit. Target is now a comma-separated list of agents who should receive this task. If multiple agents are specified client will get JSON with following structure:
{
 "error": false,
 "results": {
  "agent1": {
    result object send by agent1
  },
  "agent2": {
    result object send by agent2
  },
  etc
 }
}

See 3ca8e49. Probably needs more thorough testing.


"W" icon on KDE neon

Hi,
I wasn't experiencing this issue on GNOME (Pop OS) and Unity (Ubuntu) but am seeing this on Plasma (KDE) :

Thanks

Yup. I've got the same problem. You can pin the desktop file to your panel, but after clicking it it will just open in a window with the Wayland icon.


Solved the Issue : Enhance User Experience by Integrating Links to Open in the Same Tab ! Update index.html

Integrated the links to open in the same tab by removing target="_blank" but didn't remove target="_blank" in the about us links for better user experience
Fixes Issue🛠

Closes #
Description👨💻

Type of change📄

[] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)

How this has been tested✅

Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have commented my code, particularly in hard-to-understand areas
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷

Please assign this issue under gssoc'24 to me


Clouddefense modified

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

/kind release

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area tests

/area proposals

/area CI

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

5cb2620 Add environment variable COLLECTOR_URL for reading collector url
d4a0d71 Add README.md
c9da75f Change falco.yaml to clouddefense.yaml
04c194c Change /etc/falco to /etc/clouddefense
2f0fe45 Change custom rules path
bb2a9cb Merge branch 'clouddefense-modified' of https://github.com/CloudDefenseAI/falco- into clouddefense-modified
1b9a8d3 Add clouddefenseAgent package
e10d54d Set default mode to bpf probe
ec7fe96 Add setup for automatically compiling the BPF probe
ac61908 Create and add tarball
335c188 adds filter to prevent collector from getting flooded

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


Error Code is cut off from bulk data when reading a SEND_INTERNAL_ERROR query

Bug Summary
When reading a received SEND_INTERNAL_ERROR query from Core, the library cuts off the first bulkData byte:
if (msg.getQueryType() == SecurityQueryType.NOTIFICATION && msg.getQueryID() == SecurityQueryID.SEND_INTERNAL_ERROR) {
    _bulkData = new byte[binHeader.length - _jsonSize - SECURITY_QUERY_HEADER_SIZE - 1];
} else {
    _bulkData = new byte[binHeader.length - _jsonSize - SECURITY_QUERY_HEADER_SIZE];
}
System.arraycopy(binHeader, SECURITY_QUERY_HEADER_SIZE + _jsonSize, _bulkData, 0, _bulkData.length);
msg.setBulkData(_bulkData);

This results in the library not being able to read this data later:
if (receivedHeader.getBulkData() != null && receivedHeader.getBulkDataSize() == 1) {
    DebugTool.logError(TAG, "Security Query module internal error: " + SecurityQueryErrorCode.valueOf(receivedHeader.getBulkData()[0]).getName());
} else {
    DebugTool.logError(TAG, "Security Query module error: No information provided");
}

This should be changed to:
_bulkData = new byte[binHeader.length - _jsonSize - SECURITY_QUERY_HEADER_SIZE];
System.arraycopy(binHeader, SECURITY_QUERY_HEADER_SIZE + _jsonSize, _bulkData, 0, _bulkData.length);
msg.setBulkData(_bulkData);

Reproduction Steps

Attempt to test Encrypted Video Streaming using an app with the app ID wrong_app_id and the default security lib

Expected Behavior:
Encrypted Video Streaming fails with the following log
Security Query module internal error: INVALID_CERT

Observed Behavior:
Encrypted Video Streaming fails with the following log
Security Query module error: No information provided

Which projects have you seen this bug on?
No response
Android Version(s)
9
Android Device(s)
Galaxy S9
sdl_java_suite Version
develop
Testing Environment(s)
SDL Core `release/8.1.0` branch + Generic_HMI `release/0.12.0` branch

Relevant log output
No response

Fixed with #1791


[ADDITION] Buildkite

Category
Developer Tools
Software to be added
Buildkite
Supporting Material
URL: https://buildkite.com/
Description: Buildkite is a platform for running fast, secure, and scalable continuous integration pipelines on your own infrastructure.
Size:
HQ: Melbourne
LinkedIn: https://www.linkedin.com/company/buildkite/
See Record on Airtable:
https://airtable.com/app0Ox7pXdrBUIn23/tblYbuZoILuVA0X3L/recidjoCEVU7ClE9u

Enough info in Airtable, adding to list


messages are not reaching to iothub

Hi i am tying on windows with opc publisher i am using the below command
dotnet opcpublisher.dll opcua HostName= --tc telemetryconfiguration.json --di=5
telemetry.json:
{
"Defaults": {
"EndpointUrl": {
"Publish": false,
"Pattern": "(.*)",
"Name": "EndpointUrl"
},
"NodeId": {
"Publish": true,
"Name": "NodeId"
},
"MonitoredItem": {
"Flat": true,
"ApplicationUri": {
"Publish": false,
"Name": "ApplicationUri"
},
"DisplayName": {
"Publish": false,
"Name": "DisplayName"
}
},
"Value": {
"Flat": true,
"Value": {
"Publish": true,
"Name": "Value"
},
"SourceTimestamp": {
"Publish": true,
"Name": "SourceTimestamp"
},
"StatusCode": {
"Publish": true,
"Name": "StatusCode"
},
"Status": {
"Publish": false,
"Name": "Status"
}
}
}
}
publishednodes.json:
[
{
"EndpointUrl": "opc.tcp://<IP_ADDRESS>:4840",
"OpcNodes": [
{
"Id": "i=20305",
"OpcSamplingInterval": 2000,
"OpcPublishingInterval": 5000,
"SkipFirst": false
}
]
}
]
i am getting the below message in log file
2019-02-15 20:01:04.676 +05:30 [INF] messages sent to IoTHub: 0
2019-02-15 20:01:04.677 +05:30 [INF] last successful msg sent @: 1/1/0001 12:00:00 AM
2019-02-15 20:01:04.680 +05:30 [INF] bytes sent to IoTHub: 0
2019-02-15 20:01:04.682 +05:30 [INF] avg msg size: 0
2019-02-15 20:01:04.685 +05:30 [INF] msg send failures: 0
2019-02-15 20:01:04.687 +05:30 [INF] messages too large to sent to IoTHub: 0
2019-02-15 20:01:04.688 +05:30 [INF] times we missed send interval: 0
2019-02-15 20:01:04.689 +05:30 [INF] number of events: 0

first thing: on windows native or windows containers you need to use --at X509Store
try that and post the log when OPC Publisher is starting up

Hi @hansgschossmann
i tried as you mentioned
dotnet opcpublisher.dll opcua  --tc tc.json --di=5   --at X509Store
but still getting same problem
2019-02-18 11:15:04.671 +05:30 [INF] Loaded 1 config file entry/entries.
2019-02-18 11:15:04.677 +05:30 [INF] There are 1 nodes to publish.
2019-02-18 11:15:04.680 +05:30 [INF] initialize hub communication.
2019-02-18 11:15:04.691 +05:30 [INF] IoTHub device cert store type is: X509Store
2019-02-18 11:15:04.694 +05:30 [INF] IoTHub device cert path is: My
2019-02-18 11:15:04.697 +05:30 [INF] Attempting to register ourselves with IoT Hub using owner connection string.
2019-02-18 11:15:06.553 +05:30 [INF] Device 'opcua' found in IoTHub registry. Remove it.
2019-02-18 11:15:06.848 +05:30 [INF] Adding device 'opcua' to IoTHub registry.
2019-02-18 11:15:07.382 +05:30 [INF] Generate device connection string.
2019-02-18 11:15:07.388 +05:30 [INF] Adding device connectionstring to secure store.
2019-02-18 11:15:08.632 +05:30 [INF] Attempting to read device connection string from cert store using subject name: opcua
2019-02-18 11:15:08.650 +05:30 [INF] Protocol used for IoTHub communication is'Mqtt_WebSocket_Only'
2019-02-18 11:15:08.695 +05:30 [INF] IoTCentral mode: False
2019-02-18 11:15:12.220 +05:30 [INF] Connection status changed to 'Connected', reason 'Connection_Ok'
2019-02-18 11:15:12.833 +05:30 [INF] Message processing and hub communication configured with a send interval of 10 sec and a message buffer size of 262144 bytes.
2019-02-18 11:15:12.839 +05:30 [INF] Creating task process and batch monitored item data updates...
2019-02-18 11:15:12.903 +05:30 [INF] initialize publisher diagnostics
2019-02-18 11:15:12.907 +05:30 [INF] DiagnosticsInterval :: 5
2019-02-18 11:15:12.909 +05:30 [INF]
2019-02-18 11:15:12.914 +05:30 [INF]
2019-02-18 11:15:12.917 +05:30 [INF] Publisher is running. Press CTRL-C to quit.
2019-02-18 11:15:12.926 +05:30 [INF] ShowDiagnosticsInfoAsync
2019-02-18 11:15:12.944 +05:30 [INF] Connect and monitor session and nodes on endpoint 'opc.tcp://<IP_ADDRESS>:4840'.
2019-02-18 11:15:15.075 +05:30 [INF] Create secured session for endpoint URI 'opc.tcp://<IP_ADDRESS>:4840' with timeout of 10000 ms.
2019-02-18 11:15:15.426 +05:30 [INF] Session successfully created with Id ns=1;g=a2a48d90-3646-645f-7c47-74f707f09f39.
2019-02-18 11:15:15.448 +05:30 [INF] The session to endpoint 'opc.tcp://<IP_ADDRESS>:4840/' has 2 entries in its namespace array:
2019-02-18 11:15:15.449 +05:30 [INF] Namespace index 0: http://opcfoundation.org/UA/
2019-02-18 11:15:15.450 +05:30 [INF] Namespace index 1: urn:unconfigured:application
2019-02-18 11:15:15.533 +05:30 [INF] Created subscription with id 1 on endpoint 'opc.tcp://<IP_ADDRESS>:4840'
2019-02-18 11:15:15.539 +05:30 [INF] Create subscription on endpoint 'opc.tcp://<IP_ADDRESS>:4840' requested OPC publishing interval is 5000 ms. (revised: 5000 ms)
2019-02-18 11:15:15.547 +05:30 [INF] Start monitoring items on endpoint 'opc.tcp://<IP_ADDRESS>:4840'. Currently monitoring 0 items.
2019-02-18 11:15:15.672 +05:30 [INF] Done processing unmonitored items on endpoint 'opc.tcp://<IP_ADDRESS>:4840' took 119 msec. Now monitoring 1 items in subscription with id '1'.
2019-02-18 11:15:18.013 +05:30 [INF] ==========================================================================
2019-02-18 11:15:18.017 +05:30 [INF] OpcPublisher status @ 2/18/2019 5:45:18 AM (started @ 2/18/2019 5:45:02 AM)
2019-02-18 11:15:18.021 +05:30 [INF] ---------------------------------
2019-02-18 11:15:18.026 +05:30 [INF] OPC sessions (configured/connected): 1/1
2019-02-18 11:15:18.032 +05:30 [INF] OPC subscriptions (configured/connected): 1/1
2019-02-18 11:15:18.039 +05:30 [INF] OPC monitored items (configured/monitored/to remove): 1/1/0
2019-02-18 11:15:18.043 +05:30 [INF] ---------------------------------
2019-02-18 11:15:18.048 +05:30 [INF] monitored items queue bounded capacity: 8192
2019-02-18 11:15:18.055 +05:30 [INF] monitored items queue current items: 0
2019-02-18 11:15:18.059 +05:30 [INF] monitored item notifications enqueued: 0
2019-02-18 11:15:18.064 +05:30 [INF] monitored item notifications enqueue failure: 0
2019-02-18 11:15:18.070 +05:30 [INF] ---------------------------------
2019-02-18 11:15:18.075 +05:30 [INF] messages sent to IoTHub: 0
2019-02-18 11:15:18.081 +05:30 [INF] last successful msg sent @: 1/1/0001 12:00:00 AM
2019-02-18 11:15:18.090 +05:30 [INF] bytes sent to IoTHub: 0
2019-02-18 11:15:18.095 +05:30 [INF] avg msg size: 0
2019-02-18 11:15:18.098 +05:30 [INF] msg send failures: 0
2019-02-18 11:15:18.102 +05:30 [INF] messages too large to sent to IoTHub: 0
2019-02-18 11:15:18.109 +05:30 [INF] times we missed send interval: 0
2019-02-18 11:15:18.113 +05:30 [INF] number of events: 0
2019-02-18 11:15:18.116 +05:30 [INF] ---------------------------------
2019-02-18 11:15:18.122 +05:30 [INF] current working set in MB: 91
2019-02-18 11:15:18.127 +05:30 [INF] --si setting: 10
2019-02-18 11:15:18.132 +05:30 [INF] --ms setting: 262144
2019-02-18 11:15:18.138 +05:30 [INF] --ih setting: Mqtt_WebSocket_Only
2019-02-18 11:15:18.141 +05:30 [INF] ==========================================================================
2019-02-18 11:15:23.160 +05:30 [INF] ==========================================================================
2019-02-18 11:15:23.164 +05:30 [INF] OpcPublisher status @ 2/18/2019 5:45:23 AM (started @ 2/18/2019 5:45:02 AM)
2019-02-18 11:15:23.168 +05:30 [INF] ---------------------------------
2019-02-18 11:15:23.174 +05:30 [INF] OPC sessions (configured/connected): 1/1
2019-02-18 11:15:23.176 +05:30 [INF] OPC subscriptions (configured/connected): 1/1
2019-02-18 11:15:23.178 +05:30 [INF] OPC monitored items (configured/monitored/to remove): 1/1/0
2019-02-18 11:15:23.180 +05:30 [INF] ---------------------------------
2019-02-18 11:15:23.183 +05:30 [INF] monitored items queue bounded capacity: 8192
2019-02-18 11:15:23.185 +05:30 [INF] monitored items queue current items: 0
2019-02-18 11:15:23.188 +05:30 [INF] monitored item notifications enqueued: 0
2019-02-18 11:15:23.190 +05:30 [INF] monitored item notifications enqueue failure: 0
2019-02-18 11:15:23.193 +05:30 [INF] ---------------------------------
2019-02-18 11:15:23.195 +05:30 [INF] messages sent to IoTHub: 0
2019-02-18 11:15:23.197 +05:30 [INF] last successful msg sent @: 1/1/0001 12:00:00 AM
2019-02-18 11:15:23.199 +05:30 [INF] bytes sent to IoTHub: 0
2019-02-18 11:15:23.201 +05:30 [INF] avg msg size: 0
2019-02-18 11:15:23.206 +05:30 [INF] msg send failures: 0
2019-02-18 11:15:23.208 +05:30 [INF] messages too large to sent to IoTHub: 0
2019-02-18 11:15:23.210 +05:30 [INF] times we missed send interval: 0
2019-02-18 11:15:23.212 +05:30 [INF] number of events: 0
2019-02-18 11:15:23.216 +05:30 [INF] ---------------------------------
2019-02-18 11:15:23.224 +05:30 [INF] current working set in MB: 91
2019-02-18 11:15:23.229 +05:30 [INF] --si setting: 10
2019-02-18 11:15:23.234 +05:30 [INF] --ms setting: 262144
2019-02-18 11:15:23.241 +05:30 [INF] --ih setting: Mqtt_WebSocket_Only
2019-02-18 11:15:23.245 +05:30 [INF] ==========================================================================
2019-02-18 11:15:28.262 +05:30 [INF] ==========================================================================

you configure the following node to be published:
"Id": "i=20305",
if that is in your namespace with index 1 "urn:unconfigured:application" then you need to configure it as:
"Id": "ns=1;i=20305",
best way to find this out is to connect to your OPC UA server with an client and check the details for the node. it specifies the namespace index in which your node lives.

Hi @hansgschossmann
thanks for the support  it is sending messages now
2019-02-18 20:19:25.491 +05:30 [INF] ---------------------------------
2019-02-18 20:19:25.493 +05:30 [INF] messages sent to IoTHub: 1
2019-02-18 20:19:25.495 +05:30 [INF] last successful msg sent @: 2/18/2019 2:49:20 PM
2019-02-18 20:19:25.497 +05:30 [INF] bytes sent to IoTHub: 102
2019-02-18 20:19:25.499 +05:30 [INF] avg msg size: 102
2019-02-18 20:19:25.500 +05:30 [INF] msg send failures: 0
2019-02-18 20:19:25.503 +05:30 [INF] messages too large to sent to IoTHub: 0
2019-02-18 20:19:25.505 +05:30 [INF] times we missed send interval: 0
2019-02-18 20:19:25.507 +05:30 [INF] number of events: 2
2019-02-18 20:19:25.509 +05:30 [INF] ---------------------------------
2019-02-18 20:19:25.511 +05:30 [INF] current working set in MB: 90
2019-02-18 20:19:25.513 +05:30 [INF] --si setting: 10
2019-02-18 20:19:25.515 +05:30 [INF] --ms setting: 262144
2019-02-18 20:19:25.517 +05:30 [INF] --ih setting: Mqtt_WebSocket_Only
2019-02-18 20:19:25.519 +05:30 [INF] ==========================================================================
2019-02-18 20:19:30.164 +05:30 [INF] encodedhubMessage305
2019-02-18 20:19:30.165 +05:30 [INF] hubMessageMicrosoft.Azure.Devices.Client.Message
2019-02-18 20:19:30.528 +05:30 [INF] ==========================================================================
2019-02-18 20:19:30.529 +05:30 [INF] OpcPublisher status @ 2/18/2019 2:49:30 PM (started @ 2/18/2019 2:48:58 PM)
2019-02-18 20:19:30.531 +05:30 [INF] ---------------------------------
2019-02-18 20:19:30.532 +05:30 [INF] OPC sessions (configured/connected): 1/1
2019-02-18 20:19:30.533 +05:30 [INF] OPC subscriptions (configured/connected): 1/1
2019-02-18 20:19:30.534 +05:30 [INF] OPC monitored items (configured/monitored/to remove): 1/1/0
2019-02-18 20:19:30.535 +05:30 [INF] ---------------------------------
2019-02-18 20:19:30.536 +05:30 [INF] monitored items queue bounded capacity: 8192
2019-02-18 20:19:30.538 +05:30 [INF] monitored items queue current items: 0
2019-02-18 20:19:30.539 +05:30 [INF] monitored item notifications enqueued: 3
2019-02-18 20:19:30.541 +05:30 [INF] monitored item notifications enqueue failure: 0
2019-02-18 20:19:30.543 +05:30 [INF] ---------------------------------
2019-02-18 20:19:30.545 +05:30 [INF] messages sent to IoTHub: 2
2019-02-18 20:19:30.547 +05:30 [INF] last successful msg sent @: 2/18/2019 2:49:30 PM
2019-02-18 20:19:30.548 +05:30 [INF] bytes sent to IoTHub: 305
2019-02-18 20:19:30.552 +05:30 [INF] avg msg size: 152
2019-02-18 20:19:30.556 +05:30 [INF] msg send failures: 0
2019-02-18 20:19:30.558 +05:30 [INF] messages too large to sent to IoTHub: 0
2019-02-18 20:19:30.560 +05:30 [INF] times we missed send interval: 0
2019-02-18 20:19:30.562 +05:30 [INF] number of events: 3
2019-02-18 20:19:30.564 +05:30 [INF] ---------------------------

great to hear.


Typescript warning (ts7016) is showed in Javascript Files

VSCode Version: 1.35.1
OS Version: macOS Mojave 10.14.5

Steps to Reproduce:

create a file ended in .js with import like my rollup.config.js

The only workaround I found is adding a typescript config  tsconfig.json in my javascript project folder like
{
    "compilerOptions": {
        "outDir": "./xyz",
        "noImplicitAny": true,
        "suppressImplicitAnyIndexErrors": true,
        "allowJs": true
    }
}

I hope one day I could get rid of typescript config from a javascript project...
Does this issue occur when all extensions are disabled?: Yes

The ... indicates a suggestion, not warning. In this case, the suggestion tells you won't get any IntelliSense for rollup-plugin-svelte because we could not find any typings for it. You can disable suggestions such as this by setting: "javascript.suggestionActions.enabled": false
Moving upstream to see if we want to change the UX

@mjbvz thanks for replying. it works 👍
vscode now shows suggestions with prefix like js(6133) or ts(7016).
I think showing js suggestions only for js file by default would generate better UX.

@mjbvz I don't think one feedback on this is enough to warrant doing anything. It's a good suggestion for people who want high-quality completion results

@RyanCavanaugh two feedbacks, now. How many feedbacks should I collect?
https://github.com/microsoft/vscode/issues/75858

Would it be possible to have a typescript.suggestionActions.enabled option?

Version: 1.36.0 (user setup)
Commit: 0f3794b38477eea13fb47fbe15a42798e6129338
Date: 2019-07-03T13:25:46.372Z
Electron: 4.2.5
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

I have to agree with @wangchou in this one. I don't want TS warnings, suggestions, etc, in my JS files, heck sometimes this errors pop up when I simply delete a line in my code, and they come in bunches all over a single file.
The main problem here is that somehow you're stating: "Use TS instead of JS". While there are advantages in using TS is just not right to force people to use a particular technology.
The only workaround I've found is to disable js validate, close the program, start it again and enable js validate again.
@RyanCavanaugh that would be three feedbacks now. While this is not happening a lot all over the user base it has been reported quite a few times already: #54261, #54868 and also if you look in stackoverflow you'll see a few incidences there.
Hopefully this can be solved.
Anyway thanks for your hard work and dedication, VSCode is a great piece of software that makes coding very easy and fun.
Best,
Rodrigo.

I don't want TS warnings, suggestions, etc, in my JS files, heck sometimes this errors pop up when I simply delete a line in my code, and they come in bunches all over a single file.

You can turn off this behavior, as noted above.

The main problem here is that somehow you're stating: "Use TS instead of JS".

This isn't the intent.

You can turn off this behavior, as noted above.

But it disables Javascript AND Typescript warnings.
This does not match the expected behavior. Disabling validation for JS should disable validation for JS, not other languages.
Can we just add a typescript.validate.enable, like javascript.validate.enable?
Seems to be a lot of pushback from the devs on the 3 or 4 tickets opened by users that are confused by this behavior. Is there a reason why?

@RyanCavanaugh I know that is not the intend and I'm not implying that and I'd like to apologize for not making myself clear.
Unfortunately the implementation in the software causes this discomfort, that forces to disable JS validation because of a different file type validation is being enforced in a file that has no trace of the aforementioned file type.
Finally the issue does not comes up every day and at every working hour, but I'm used to seeing it a couple of times a week for the past few months. I can't pinpoint when exactly this started but it has been a while though.
Once again, thanks for all your work and sorry I wasn't clear enough in my previous post.
Have a nice day!!

I want the js errors. I do not want the ts errors.
The codes are known.
Would it not be possible (and maybe even simple) to provide an option that allows the results to be filtered to exclude ts errors?

This is not very nice for libraries that do not want to provide TypeScript definitions. It is essentially forcing us to write definition files for TypeScript, when we may have no interest in TypeScript at all.

How does it make sense to show typescript errors in javascript files? I just spent an hour trying to figure out why this error was happening, and the real reason is because someone well-actually'd its inclusion and closed the ticket four years ago. Maybe the real fix is uninstalling VS Code.


Fix bitmasking / bitshifting code to encode / decode user data

Motivation:
Our bitmasking / shifting did not correctly handle negative values.
Modifications:

Change methods to allow passing user data
fix bitmasking / bitshifting code
Add unit test

Result:
Be able to pass in negative values as well

@njhill @chrisvest @chrisvest PTAL again


Add German translation

I'd like to contribute to the app and am willing to translate it to German. If that's possible, please tell me how to start

Thank you! I will add swedish translation and update README.md with a guide. I'll link the commit here when I'm done
I use i18n for translations, you can see example under src/locales.

I have now updated the README.md with a contribution guide. You can also check this commit out

Thanks, I will do it soon and will let you know. I'm closing the issue since you've updated the README.md file :)


Added first version of setup blog post for XM Cloud

We are starting a new Tutorial Blog Series on XM Cloud based on the  Video Tutorial Series. This is the first blog that needs to be further reviewed.
Description / Motivation
The blog we created now guides a developer that has not dealt with Sitecore Products from creating Project and Environment to getting ready to start development. Images are all embedded pulling from Content Hub public links.
How Has This Been Tested?
This was locally tested
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[X] Documentation update (non-breaking change; modified files are limited to the /data directory or other markdown files)

Checklist:

[X] I have read the Contributing guide.
[X] My code/comments/docs fully adhere to the Code of Conduct.
[ ] My change is a code change.
[X] My change is a documentation change and there are NO other updates required.
[] My change has new or updated images which are stored in the /public/images folder that need to be migrated to Sitecore DAM

@lovesitecore : I have done a bunch of review, and committed changes for quick edits. I went through all the comments and have resolved any that were fixed. The remaining comments still need to be resolved.

On top of other changes still pending: After all the content, we need some related resources for them to read.

I've resolved this one with the latest commit

Just checking, but it looks like the wrong screenshot is being used here, the same one is repeated twice. It feels like the first one should be a screenshot of the Portal link to Deploy right?

Adding some comments:

Just checking, but it looks like the wrong screenshot is being used here, the same one is repeated twice. It feels like the first one should be a screenshot of the Portal link to Deploy right?

Good catch! Our updates to crop images introduced a copy/paste issue. @lovesitecore has fixed this up now.

Missing whitespace here after "e,g."

"2. From here you provide a Project Name e.g.XM Cloud Tutorial Series and click the Continue button"

I've introduced a fix for this.

"-LicenseXmlPath: the path to your XM Cloud license file"

This is the first mention of a License file being required, do we want to include some information about where to get this?

I've added in a prerequisites section at the beginning which includes a callout for the license file and link to docs on how to use the CLI to download the license file.
I've also updated the title to use 'Tutorial' instead of 'Sprint Zero', along with changing 'blog' references to 'tutorial'. The Open Graph image has also been fixed.


Azure Table storage input bindings for Azure Functions - Usage

The description of Azure Table storage input bindings for Azure Functions contains a section about the usage (https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-table-input?tabs=javascript#usage).
In case of the language of JavaScript the statement is that the attributes partitionKey or rowKey should not be used. However, making use of them in JavaScript does not lead to error and the attributes work as expected as Filter.
It would be very helpful if the consequences of using them in JavaScript development would be a bit more elaborated. As the current description is quite irritating.

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

ID: d328a623-0293-30cd-1356-8c4750e4e88b
Version Independent ID: a71cd4b1-536f-3f9c-6d06-0437760395e3
Content: Azure Table storage input bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-table-input.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hi @lechnerc77 - Thank you for your feedback! We will review and update as appropriate.

@lechnerc77 Sorry for the late reply. The guidance in the Usage section pertaining to the partitionKey and rowKey is to not set them but you should be OK using them as Filters.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Shouldn't there then be an adjustment of the documentation that you can use them as filter?
Currently it sounds like they are forbidden which does not seem to be the case, if I understand you correctly


change leftButton init position

In navigationBar, when back to the previous view, the left button of the previous view should fade in like iOS native navBar, instead of move in. It's interesting that the right button acts correct.
React Native:

iOS Native:

By analyzing the blame information on this pull request, we identified @trave7er and @olegbl to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@dragonwong updated the pull request.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


RTL

There is a problem in the Netherlands category about RTL format.
@amin-setayeshfar

There is a problem in the Netherlands category about RTL format. @amin-setayeshfar

Do you mean the very problem you fixed the other night? if so, I believe we could close this issue


Defragmentation issue

It seems that a PDU fragmented over 2 BBFRames is not recovered and dropped.
Attached screenshot to see analysis from wireshark

Debug message (from an other capture) : Seems length calculation has issue ?
2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] extracted GSE Packet with header GSE Header (S = true, E = false, LT = broadcast label, GSE Length = 647 bytes, Fragment ID = 113, Total Length = 1348, Protocol Type = 0x0800, Label = broadcast)
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] start of GSE fragment ID = 113
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] no more GSE Packets in BBFRAME
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] extracted GSE Packet with header GSE Header (S = false, E = true, LT = broadcast label, GSE Length = 707 bytes, Fragment ID = 113)
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] pushing non-start GSE fragment ID = 113
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] end of GSE fragment ID = 113
[2022-11-29T17:17:04Z DEBUG dvb_gse::gsepacket] defragmented length 1346 does not match total length 1348

Hi, I have tested defragmentation by transmitting large ICMP packets with gr-dvbgse, so I'm surprised that this fails.
Let's check the sizes. The first fragment has a GSE length of 647 bytes. The header has a fragment ID field (1 byte), a total length field (2 bytes) and a protocol type field (2 bytes), for a total of 5 bytes. This means that the payload is 642 bytes. The second fragment has a GSE length of 707 bytes. Its header has a fragment ID field only (1 byte). However, since this packet is the last, it has a CRC-32 field at the end, whose size is counted in the GSE length. Therefore, besides payload, we have 5 extra bytes being counted in the GSE length. The payload is then 702 bytes.
In total, we have 1344 ( = 642 + 702) bytes of payload. The size of the protocol type field (2 bytes) is also counted towards the total length field. So the value of the total length field should be 1346. However, it is 1348, and this is what causes the packet to be dropped.
My understanding is that the total length field in the first packet does not have the correct value. Do my calculations make sense? Do you know the expected size of the payload, so that we can check that the problem is that the total length is too large, rather than some of the fragments being too short?

The relevant information from TS 102 606-1 is as follows:

GSE_Length: This 12-bit field indicates the number of bytes following in this GSE Packet, counted from the byte
following this GSE Length field. The GSE Length field allows for a length of up to 4 096 bytes for a GSE Packet. The
GSE Length field points to the start of the following GSE Packet. If the GSE packet is the last in the Base Band frame it
points to the end of the Base Band frame Data Field or the start of the padding field. For End packets, it also covers the
CRC_32 field.

Total_Length: This field is present in the GSE Header carrying the first fragment of a fragmented PDU. The 16-bit
field carries the value of the total length, defined as the length, in bytes, of the Protocol Type, Label (6 byte Label or
3 byte Label), Extension Headers, and the full PDU. The receiver shall perform a total length check after reassembly. It
may also use the total length information for pre-allocation of buffer space. Although the length of a single GSE Packet
is limited to almost 4 096 bytes, larger PDUs are supported through fragmentation, up to a total length of 65 536 bytes.
NOTE 2: Since the information in the total length field is intended for use by higher layers in the reassembly
process, the length of the CRC_32 field is therefore not included in the Total_Length.

The total length field shoud be 1346, I guess...See a gse packet end and start well handled.

This packet has GSE Length field 1346. It has a protocol tye field (2 bytes). Therefore, the PDU size (the size of the IPv4 payload) should be 1344 bytes. If the fragmented packet that you showed earlier has the same IPv4 payload size, then I think that my calculations check up (I got a payload size of 1344 bytes also) and the total length field produced by this transmitter is not correct, since I don't see how with 1344 bytes of payload one could get a total length of 1348, given that the CRC-32 doesn't count and there is no label or extension headers, so we can only add 2 bytes for the protocol type.

If this is a transmitter that you can't fix, you could try commenting out L214-L248 in gsepacket.rs. If this works (there is also the CRC check that needs to be passed to consider the defragmented packet as valid), then we might have an option to disable the total length field check.
However, if we're right that the total length field in this transmitter is wrong, it would be very advisable to fix the transmitter, since other receivers could have the same problem.

Commenting this is and get a stream much better..and nearly no error stream. Transmitter is from Newtec EL170, a reference in the dvb field , usually implementing new features prior to standards.  This is a second hand equipment, and could not access to firmware update (if available). Your analysis seems OK : the only explanation, for a 2 bytes mismatch could be the protocol type counted on the last frag (not present) ?

Here is a pcap capture from Longmynd BBframes. Hope you can replay it.
My dvb-gse command :
dvb-gse --listen <IP_ADDRESS>:1234 --tun tun0 --isi 171
gsebbframe.pcapng.tar.gz

This packet has GSE Length field 1346. It has a protocol type field (2 bytes). Therefore, the PDU size (the size of the IPv4 payload) should be 1344 bytes. If the fragmented packet that you showed earlier has the same IPv4 payload size, then I think that my calculations check up (I got a payload size of 1344 bytes also) and the total length field produced by this transmitter is not correct, since I don't see how with 1344 bytes of payload one could get a total length of 1348, given that the CRC-32 doesn't count and there is no label or extension headers, so we can only add 2 bytes for the protocol type.

And I agree with this calculation....weird !

Hi. My plan is to add an option so that this check can be disabled (turning it into a warning sounds good until we realize that there are potentially many of these packets per second, which would spam the log). This is a simple change, so I'll probably do it this week.
Indeed you're right about the label. In the second fragment it is set to 10 rather than 11. This is not something that my dvb-gse implementation cares about. I think it only looks at the label of the first fragment, and then considers that to be the value of the label for the defragmented PDU.

I have added a pull request #12 that adds an option to skip the checking of the total length field. I haven't tested this, but in principle it should solve the problems you have with the Newtec EL170. Can you give it a try?
By the way, no need to close this issue manually. It will get closed automatically when the pull request is merged.

Confirm that it fixes the issue. Without skip-total-length, lot of bbframes skipped, with option, all is OK.


Master needs a python git package for gitfs

https://docs.saltstack.com/en/2015.5/topics/tutorials/gitfs.html says it's the preferred method.
It looks like we're not managing any of the salt-master config within salt itself, so this dependency is the only change for #264

This change is

Do we still need to install git explicitly, or will it get pulled in as a dependency or fulfilled by python-pygit2? I only added it to support the existing workflow of manually pulling, so let's remove it if it's not needed.
Also, I think it also makes sense to move this state to a new folder + file salt/master.sls instead, to make its purpose more clear, and get rid of the git folder.

Actually, the Salt docs note that python-pygit2 isn't yet available in the Ubuntu repos, and Travis corroborates this.

Might as well just use GitPython, then.

Ubuntu 14.04 LTS and Debian Wheezy (7.x) also have a compatible version packaged:
$ sudo apt-get install python-git

Amended commit, and rebased onto current master branch to pull in the workaround for the Travis intermittents.

r? @larsbergstrom

Closing because I'm adding some other saltmaster-specific states and renaming the git directory for another PR, and I'll stick this change into there


AbstractValidator that sources validations from external data source

Based on #1008
Most of us are using AbstractValidator with Entity Framework (6 or Core) or NHibernate, and a subset of us are further using it with SQL Server.  ANSI SQL defines INFORMATION_SCHEMA.COLUMNS which provides a wealth of information that can be used to automatically validate properties.
Reasons against this idea

Perhaps the main reason this hasn't been done yet is most of us also follow a POCO model, and we might have situations where we have deep object graphs we want to validate, and we might not want to sort out mapping our Models to our database columns.
The other reason this hasn't been done yet is the school of thought that by defining the validations separately, we might catch errors between the validations and the database.

Proposed syntax would be AutoMap() similar to CsvHelper library.  FluentValidation would add a new IPropertyValidationSource or similar.
Jeremy, I almost feel bad proposing this , but just throwing an idea out there.  I'm not even sure it's a good idea.
In terms of problems this would solve, today I can definitely catch situations where fluent validation allows more data than a database column allows, but I can't catch situations where the database column allows more data than fluent validation allows (unless I call my validators on egress - which I've done before).

Thanks for the suggestion, but this is out of scope for the project.
The whole point of FluentValidation is to define rules in a strongly-typed way where the rules are defined at compile-time. If you need dynamic construction of rules from an external source, then FluentValidation is not the right tool for the job.

I think you're right; and all I really want is a way to materialize some of the validations as a table of properties ("data dictionary" in FoxPro talk).  For that, it would be simpler to create a Function Detour inside FluentValidator to log that information, stash it, and compare to the upstream data source's data dictionary.


URL fixes

fix URLs with hashes or ampersands
fix self-hosted iframely instances

Thank you for PR.


Allow deselecting selected option

Trello

Do we maybe want to make this behavior configurable? I guess we have cases where selecting an option is mandatory and we don't want the user to select a blank value.

I was originially thinking to tie this to the required option, but since we always hardcoded this options where we used chosen, I went for the simple option. I agree, though, that it makes sense to do it.

Updated it, so deselect works only for select fields that are not required.

:thumbsup: LGTM


.yet file, numbering problem

I'm trying to write a .yet file for a bible translation. I've found that there are some verses that sharing multiple numbers, for example:
5     text
6-7  text
8     text
I've tried added the following lines, but its not working:
verse	1	1	6-7	text
How to write it correctly?
Thank you very much for the help.
Update:
Related text:

The compiler may not allow you to skip verses. You can try this:
5 text
6 6-7 text
7 empty text (this verse and verse number will be hidden in the frontend)
8 text
On Wed, Apr 26, 2023 at 1:17 PM Joielechong @.***>
wrote:

I'm trying to write a .yet file for a bible translation. I've found that
there are some verses that sharing multiple numbers, for example:
5 text
6-7 text
8 text
I've tried added the following lines, but its not working:
verse 1 1 6-7 text
How to write it correctly?
Thank you very much for the help.
—
Reply to this email directly, view it on GitHub
https://github.com/yukuku/androidbible/issues/91, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIIXUYLPQTDF53DET43CTLXDDY5DANCNFSM6AAAAAAXMG6EGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Your suggestion is worked, but the result isn't blended with the rest of the verses numbering in the app. If there is no another way, I will use your suggestion.


transfer support

README file tells me baresip unattended call transfer. But, I find call_transfer function in src code.
Does forget to upgrade README file?

Unattended call transfer is supported.
Attended call transfer is not supported yet, it is on the Roadmap:
https://github.com/alfredh/baresip/wiki/Roadmap
the call_transfer function you found is most likely referring to "unattended" call transfer.
Alfred


[resolves #76] Provide camel-infinispan integration

retest this please

Works on my machine :wink: ...
The tear down / setup logic needs a rethink before this can build reliably.


Specific Sneak Enhancement

If possible make a blacklist and whitelist setting for the SNEAK ability to toggle certain mobs from aggroing.
For example, if someone wanted to create a Piglins power, they could make it so Piglins and Hoglins no longer aggro but other mobs will.

yeah that's a good idea


Fixed #2086

As discussed with @cortesi about this #2096  over IRC . Now it will set reply to DummyReply whenever we duplicate any flow. #2086 .

Hi there - this looks good. Could you please squash the commits in this PR together, and give the commit a germane title (something like "Fix crash when duplicating flow") and we'll merge.

I'm not sure about just setting a dummy reply on in the constructor. We probably want things to blow up rather than silently ignoring interactions when we unexpectedly don't have a .reply set. This is a delicate bit of the codebase, and I'm leery of unanticipated consequences here. I say we fix the immediate bug, and table a re-thinking of the reply mechanism later on.

Right, I'm happy with both. In this case, we should fix it here?

Hmm.. the copy method is still the right place for the fix - just say that if the flow being copied  has a non-null reply, we create a dummy reply in the duplicate.

@iharsh234 Just to recap the discussion here and a bit of chat on slack:

Make sure there's one commit with a clear name.
Make sure DummyReply is initialised
Tweak the code slightly to only create the dummy reply if the flow being copied has a non-None reply attribute.

Apologies for the slightly confusing progression of comments here, but that's how the sausage is made. :)


error: error parsing mirror registry "LOCALHOST:5000": "LOCALHOST:5000" is not a valid image reference: repository name must be lowercase

Version
$ oc-mirror version
Client Version: version.Info{Major:"0", Minor:"2", GitVersion:"v0.2.0-alpha.1", GitCommit:"4de61d62fd3a76a70abf4a46c178397be42974cd", GitTreeState:"clean", BuildDate:"2022-03-14T12:47:36Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}

What happened?
oc mirror --from ./archive/ docker://LOCALHOST:5000/olm-mirror --dest-skip-tls --dest-use-http
INFO Checking push permissions for LOCALHOST:5000
INFO Publishing image set from archive "./archive/" to registry "LOCALHOST:5000"
WARNING metadata has single-use label, using stateless mode
INFO No existing metadata found. Setting up new workspace
error: error parsing mirror registry "LOCALHOST:5000": "LOCALHOST:5000" is not a valid image reference: repository name must be lowercase
Attach the relevant portions of your .oc-mirror.log.
time="2022-03-16T13:58:39+01:00" level=info msg="Checking push permissions for LOCALHOST:5000"
time="2022-03-16T13:58:39+01:00" level=debug msg="Using image LOCALHOST:5000/olm-mirror/oc-mirror to check permissions"
time="2022-03-16T13:58:39+01:00" level=info msg="Publishing image set from archive "./archive/" to registry "LOCALHOST:5000""
time="2022-03-16T13:58:39+01:00" level=debug msg="Unarchiving metadata into oc-mirror-workspace/images.690595667"
time="2022-03-16T13:58:39+01:00" level=debug msg="Found archive archive/mirror_seq1_000000.tar"
time="2022-03-16T13:58:39+01:00" level=debug msg="Extracting archive archive/mirror_seq1_000000.tar"
time="2022-03-16T13:58:39+01:00" level=debug msg="looking for metadata file at "publish/.metadata.json""
time="2022-03-16T13:58:39+01:00" level=warning msg="metadata has single-use label, using stateless mode"
time="2022-03-16T13:58:39+01:00" level=debug msg="Using local backend at location oc-mirror-workspace"
time="2022-03-16T13:58:39+01:00" level=debug msg="looking for metadata file at "publish/.metadata.json""
time="2022-03-16T13:58:39+01:00" level=info msg="No existing metadata found. Setting up new workspace"
time="2022-03-16T13:58:39+01:00" level=debug msg="Unpacking any provided Helm charts to oc-mirror-workspace/results-1647435519"
What did you expect to happen?
I was expecting that since the capital hostname are resolved also the oc-mirror cli to be able to do so.
$ ping -c 4LOCALHOST
PING localhost (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from localhost (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.036 ms
64 bytes from localhost (<IP_ADDRESS>): icmp_seq=2 ttl=64 time=0.052 ms
64 bytes from localhost (<IP_ADDRESS>): icmp_seq=3 ttl=64 time=0.099 ms
64 bytes from localhost (<IP_ADDRESS>): icmp_seq=4 ttl=64 time=0.098 ms
--- localhost ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3107ms
rtt min/avg/max/mdev = 0.036/0.071/0.099/0.028 ms
How to reproduce it (as minimally and precisely as possible)?

$ podman run --privileged -d --name registry -p 5000:5000 -v /opt/registry/data/:/var/lib/registry --restart=always registry:2
$ oc-mirror --from ./archive/ docker://LOCALHOST:5000/olm-mirror --dest-skip-tls --dest-use-http

Anything else we need to know?
Enter text here.
References

Enter text here.

Thank you for using oc-mirror and submitting this issue!
Can you please provide some details and use cases for using LOCALHOST as opposed to localhost or $HOSTNAME?


tests: JSON/JSONB field test addition

Adds test for JSON/JSONB fields.  (closes #19)

Signed-off-by: Leonardo Rossi<EMAIL_ADDRESS>

It doesn't solve the problem with a Variant field.
duplicate of #58

I'm testing different queries from yours.
BTW, the with_variant() looks working properly on PostgreSQL.

Sure the queries on base JSON type work and there is no need in duplicating SQLAlchemy tests here. The problem is with specific PostgreSQL and Variant field.

Problem looks resolved
js = sa.Column(sa.JSON().with_variant(postgresql.JSONB(), 'postgresql'),)

And query:
session.query(table).filter(sa.cast(table.js['hello'], sa.String) == sa.type_coerce('world', sa.JSON)).first()

It works on mysql and postgresql.


Portfolio VaR based on algo's stock holdings

Described well here:
http://firsttimeprogrammer.blogspot.com/2015/01/portfolio-var-with-python.html

https://github.com/quantopian/pyfolio/blob/master/pyfolio/timeseries.py#L607 shows that we have a function to compute the VaR.


Browserpass native binary doesn't work

Describe the bug
After switching the 23.05 I realized the browserpass extension giving a generic error on firefox:
An unexpected error occurred

Yet no visible details on neither console log, nor on journal.
Turns out the binary built via this doesn't work correctly.
~> /nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/browserpass
/nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/browserpass: line 9: /nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/.browserpass-wrapped: cannot execute: required file not found

~> /nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/.browserpass-wrapped
zsh: no such file or directory: /nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/.browserpass-wrapped

~> file /nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/.browserpass-wrapped
/nix/store/bfjdzswkw0x8snmdzjpss3f9q6pjff24-browserpass-3.1.0/bin/.browserpass-wrapped: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=8LVw1JZFOeih4T3dtZvR/Baw78YUx4KpCoEt_cbuG/U7WYov3T1_kl4UC04TTA/mObpBzHeVTJPO7TiqsW8, not stripped

Steps To Reproduce
Steps to reproduce the behavior:

enable browserpass native extension for firefox
...
...

Expected behavior
Overriding the package to use 22.11's nixpkgs seems to make it work again
Screenshots
n/a
Additional context
A bit more detail on element
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.5, NixOS, 23.05 (Stoat), 23.05.533.c37ca420157`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"nixos-23.05"`
 - channels(gurkan): `"home-manager-23.05.tar.gz"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

@rvolosatovs @infinisil I'm seeing this as well.

Bisecting reveals 2d0df979436efb4dd24fe0ffffe787fd99b6191c as the cause:

git bisect log
# bad: [945f0625d549db0fc3e4d05484223cca14698064] Merge pull request #235947 from oneingan/elpa-devel
# good: [794a24afefde85c3e9b533443c4c73cd871f9e3a] aliyun-cli: 3.0.161 -> 3.0.165
git bisect start '945f0625d549db0fc3e4d05484223cca14698064' '794a24afefde85c3e9b533443c4c73cd871f9e3a'
# good: [c0c48b0cfc3e062efcd29970efbb9486139dae31] Merge master into staging-next
git bisect good c0c48b0cfc3e062efcd29970efbb9486139dae31
# bad: [34bf8c7d4747ba1fab5a988b7504e9a67d68c353] Merge pull request #235555 from r-ryantm/auto-update/python310Packages.python-lsp-ruff
git bisect bad 34bf8c7d4747ba1fab5a988b7504e9a67d68c353
# good: [3a84fc3a186a3616a668e4fe88449e140c5fcad2] Merge pull request #235351 from kirillrdy/mgmt
git bisect good 3a84fc3a186a3616a668e4fe88449e140c5fcad2
# good: [2aa950b1dff935b834809dfd4b4e317467798704] Merge pull request #234492 from fabaff/dissect-bump
git bisect good 2aa950b1dff935b834809dfd4b4e317467798704
# good: [649707a0f67c2a71ac1a10d0552557f2323b3697] Merge pull request #235453 from r-ryantm/auto-update/python310Packages.google-cloud-redis
git bisect good 649707a0f67c2a71ac1a10d0552557f2323b3697
# bad: [e3fb99b926f092da1e782bd4635ca00c1dc15f93] Merge pull request #235520 from marsam/update-arti
git bisect bad e3fb99b926f092da1e782bd4635ca00c1dc15f93
# good: [2275754cbbf70cc9448e218024bed2041d6250e3] Merge pull request #218450 from konradmalik/rtx
git bisect good 2275754cbbf70cc9448e218024bed2041d6250e3
# bad: [2bbedef32284e058ef1ba36281aa836e68177986] protonmail-bridge: unpin go
git bisect bad 2bbedef32284e058ef1ba36281aa836e68177986
# good: [d159eb3efb10d6be9facb2e821910bdf56312429] grafana-agent: unpin go
git bisect good d159eb3efb10d6be9facb2e821910bdf56312429
# good: [8874c57f3bc1a47007c148da52acc803a3f1e55b] victoriametrics: unpin go
git bisect good 8874c57f3bc1a47007c148da52acc803a3f1e55b
# bad: [2d0df979436efb4dd24fe0ffffe787fd99b6191c] browserpass: unpin go
git bisect bad 2d0df979436efb4dd24fe0ffffe787fd99b6191c
# good: [3075f52278094b1e73a64bd970236369c7d7e8d4] open-policy-agent: unpin go
git bisect good 3075f52278094b1e73a64bd970236369c7d7e8d4
# first bad commit: [2d0df979436efb4dd24fe0ffffe787fd99b6191c] browserpass: unpin go

So the build is now completing with Go 1.20, but it has a wrong interpreter /lib64/ld-linux-x86-64.so.2.

greetings !
I am the author of the commit of https://github.com/NixOS/nixpkgs/commit/2d0df979436efb4dd24fe0ffffe787fd99b6191c
I am trying to understand what went wrong so that we can prevent this from happening
@B4dM4n where are you seeing wrong interpreter ?
ldd /nix/store/dnpx8d8d3yayd3ly05cw0dfp50djnz2h-browserpass-3.1.0/bin/.browserpass-wrapped
	statically linked

cc @mweinelt

@B4dM4n ok i see the issue, will try to fix now, or revert golang version

I have a quick fix that should work, meanwhile I will have a look why change to go 1.20 produced wrong binary

I still have the issue on master (unstable) using Chromium and home manager:
Error: Error: Native host has exited.

/nix/store/dnpx8d8d3yayd3ly05cw0dfp50djnz2h-browserpass-3.1.0/bin/browserpass: line 9: /nix/store/dnpx8d8d3yayd3ly05cw0dfp50djnz2h-browserpass-3.1.0/bin/.browserpass-wrapped: cannot execute: required file not found

Using the package from 22.11 fixes back the issue:
nixpkgs.overlays = [
  (final: previous: {
    browserpass = (import <nixos-22.11> { }).browserpass;
  })
];

 ~ ➜ uname --all
Linux soywod 6.1.31 #1-NixOS SMP PREEMPT_DYNAMIC Tue May 30 13:03:33 UTC 2023 x86_64 GNU/Linux

 ~ ➜ sudo nix-channel --list
home-manager https://github.com/nix-community/home-manager/archive/master.tar.gz
nixos https://nixos.org/channels/nixos-unstable
nixos-22.11 https://nixos.org/channels/nixos-22.11

greetings !

master (unstable)

master and unstable are not the same thing
https://nixpk.gs/pr-tracker.html?pr=236258
as of writing this, that PR hasn't reached nixos-unstable

Possibly related: https://github.com/golang/go/commit/3315066f46d5dce3e4474bdcde0997d688c79436

Possibly related: golang/go@3315066

cool thanks, I'll give that a test
I think 1.20.5 landed in staging yesterday

That commit was introduced in 1.20, so presumably it is the source of the breakage, not the fix. (I haven't tested anything, I barely understand what the issue is)


Can't get past login screen

I made an account with my email, then it gives me the "what would you like to be called" dialog. I can't seem to get past this screen. I click the button but nothing happens. If I return to the site it seems to remember my choice of name, but then asks me for it again. Not sure what to do.

@nelsonam Thank you for bringing this to my attention. I was making some changes to our auth server last night and made a bad push. I thought I had fixed it up but I see not completely. I have just pushed what I believe will fix your problem. Can you try logging in again and setting your username?
Let me know if you have any issues, but I'm hopeful that it will work this time.


dagger do --help needs tests

@mircubed Is it still accurate?

@samalba @gerhard  I assume this was before launch, so can we close this?

I checked and there are tests already for do --help in tests/tasks.bats


[REQUEST] - Can you guy consider providing arm64 .deb file in the future ?

Can you guys please consider providing arm64 .deb file in the future ? I would love to use the Chives GUI on a Raspberry Pi 4 8GB just like the CHIA GUI...

We will see what we can do.


Book View not displaying

When I use the /Book renderer command, nothing displays.

I have the latest version of the both the plugin and Logseq.

having the same issue on latest plugin install

Fixed in v4.0.11


MAINT: stats.vonmises: wrap rvs to -pi, pi interval

Reference issue
Removes defect label from gh-4598
What does this implement/fix?
The distribution interface does not have proper support for circular distributions, so vonmises can produce random variates beyond the standard $[-\pi, \pi]$ interval when loc != 0 or scale > 1. This PR wraps the random variates produced by vonmises to the standard interval. We still need a proper circular distribution infrastructure (tracked in gh-15928), but let's fix this bug in the meantime.
Additional information
I don't really think there are backward compatibility concerns. It wouldn't make much sense for a user's code to rely on the random variates to go beyond the standard interval. Also, if a user's code wraps the random variates to the standard interval, it would just become redundant.
If desired, it would also be very easy to wrap input x to the standard interval inside methods like _pdf so that PDF/CDF/RVS would be consistent for scale=1.

It still wouldn't be meaningful for scale != 1 , but that's no worse than things are now.  (And isn't kappa the more familiar scale parameter anyway?) Since it's pretty simple, I think a partial fix is better than nothing. PDF already behaves like this; I misunderstood.

The three non-merge commits do cleanly cherry-pick to maintenance branch, so given the "defect" label I'll tentatively label for backport as well.


Added git as a build dependency

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Added git as build time dependency.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

version number will need to be incremented.


Update Duplicate Checks when Importing a QA/Cert data

Update the validations that check for Duplicate records when importing a QA/Cert
Notes:
When a user is importing a QA/Cert that is a duplicate, we will no longer prevent it from being imported by displaying the Duplicate Import Checks. In the future, we shall delete an existing record when a duplicate record is being imported.

The duplicate validations shall only be displayed/applicable when a user is manually creating a record

Testing
Tester: @JanellC

Import from historical data returns duplicate error message.
Import from historical for Greene County 2018-Q1 imported both linearity records:

LINEAR-4-A and other Import checks that need to be handles only as screen checks shall be addressed as part of another ticket


DOMA: consider clearing VALPOS

part 2 of #1053, as commented in #2981.
Clear DOMNAME and VALPOS

OK I'll try remember this in 4 months, and create a new PR.

we have it in the comment in the issue, someone will find it sometime :)
closing


[driver] Find mode is not auto-set to NORMAL when -w 2 option is used

The reason is that the change of state of miopen::debug::FindEnforceDisable is not observed when GetFindModeValue() is called.
While #336 is not implemented, this is a minor issue, but should be fixed together with #336.

#489


Consider deprecating?

In order to reduce confusion in npm, would you consider deprecating this lib in favour of https://github.com/leepowellcouk/passport-token?

Because my module is different!
My need is to use only the token and not the username!

@Lughino You can do that with his module :smile:. Here is a link to the issue where I describe how to do it.
I just put in a pull request for that functionality. Hopefully he merges it and it should make it easier.


dotnet nuget push times out when nuget push doesn't

Not sure if this is the right place to report this, or if there's a more nuget-specific place, but I've recently moved tooling over from msbuild/nuget to just dotnet for my project at https://github.com/fluffynuts/PeanutButter
Part of that project's automation is to build and push all new packages to nuget.org. I noticed that the 30 second timeout I was giving wasn't working out so well, especially for larger packages, like PeanutButter.TempDb.Runner. dotnet nuget push timed out several times -- and, watching a bandwidth monitor, appeared to be using a lot less bandwidth to push than when I tried with nuget.exe, and had my package pushed in short order.
I'm happy to help trying to track this down -- please let me know if I can provide more info.

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275


[Beta] Solution doesn't pass for challenge "React: Use Advanced JavaScript in React Render Method"

Challenge Name

https://beta.freecodecamp.org/en/challenges/react/use-advanced-javascript-in-react-render-method
Issue Description

Correct solution doesn't pass. Maybe I am missing something but code does exactly what is asked in challenge description but last test doesn't pass.
"When text is entered into the input element and the button is clicked, the MagicEightBall component should return a p element that contains a random element from the possibleAnswers array." - this test appears failed.
Browser Information

Browser Name, Version: Chrome, Version 64.0.3282.140 (Official Build) (64-bit)
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Your Code

const inputStyle = {
	width: 235,
	margin: 5
}

class MagicEightBall extends React.Component {
	constructor(props) {
		super(props);
		this.state = {
			userInput: '',
			randomIndex: ''
		}
		this.ask = this.ask.bind(this);
		this.handleChange = this.handleChange.bind(this);
	}
	ask() {
		if (this.state.userInput) {
			this.setState({
				randomIndex: Math.floor(Math.random() * 20),
				userInput: ''
			});
		}
	}
	handleChange(event) {
		this.setState({
			userInput: event.target.value
		});
	}
	render() {
		const possibleAnswers = [
			"It is certain", "It is decidedly so", "Without a doubt",
			"Yes, definitely", "You may rely on it", "As I see it, yes",
			"Outlook good", "Yes", "Signs point to yes", "Reply hazy try again",
			"Ask again later", "Better not tell you now", "Cannot predict now",
			"Concentrate and ask again", "Don't count on it", "My reply is no",
			"My sources say no", "Outlook not so good","Very doubtful", "Most likely"
		];
		const answer = possibleAnswers[this.state.randomIndex];
		return (

				<input
					type="text"
					value={this.state.userInput}
					onChange={this.handleChange}
					style={inputStyle} />

				<button onClick={this.ask}>Ask the Magic Eight Ball!</button>

Answer:

					{answer}

		);
	}
};

Screenshot

You have the correct solution. This should be an error with the challenge tests. I've reproduced this both in production and locally, on staging.
I will start working on a fix—the PR should be opened tomorrow.

I found the bug. Can I submit a PR?

@bqnguyen94 customarily, you would give the original responder a day or two to propose his/her solution. I had made my intentions clear in my previous comment.
Nevertheless, @maintainers, I've tested his solution locally and it works well.

Hey @antonshevyrin @jkao1 @bqnguyen94 !
Thanks guys, for pitching in and reporting and fixing this. Sorry about the delay, we will review and merge soon.
Happy coding!

seems fix solution doesn't pass for the challenge.

seems fix solution doesn't pass for the challenge.
The fix has not been deployed yet, it may take us a while to get into the beta server.

Still a bug on main site. Its keeping me from passing this exercise.

I thought I was going crazy. I cannot pass this challenge even with the correct answer either.

It might be helpful for you guys so I'm reporting that the bug is still there when using safari (logged in and out). When I tried to test with Chrome it just passed.
Browser User Agent String:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.1 Safari/605.1.15

@akositey You used the solution @antonshevyrin shows above?  If so, @moT01 can you confirm this?  I just tested this on production and seems to work fine (at least in Chrome, Edge, and Firefox).

safari is not passing with the code in the OP, firefox does pass.

@moT01 Any guess why?

I'm not sure what's happening here, I tried taking a closer look at the last test (the one that always fails). And when logging the info used in the assert, it looks like it should pass....

The two conditions in the assert are true, and it still fails.
The test is complex and difficult to pinpoint what the problem is, or why it only seems to be failing in safari. By lowering the timeout at the beginning of the test from 250ms to 50ms it will pass some of the time, but still fail sometimes as well. I don't know, that's where I'm at.


Torch 2.0 compatible with Torchdyn

What does this PR do?
This PR updates the code base compatible with Torch2.0 and TorchDyn1.0.6.
Fixes #60
Before submitting

[x] Did you make sure title is self-explanatory and the description concisely explains the PR?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you list all the breaking changes introduced by this pull request?
[ ] Did you test your PR locally with pytest command?
[ ] Did you run pre-commit hooks with pre-commit run -a command?

Did you have fun?
Make sure you had fun coding 🙃

Should we wait for torchdyn 1.0.7 or at least put a memo to discard these changes when  1.0.7 is out?


WebSocketClientInitializer: default frame size

Please make the default websocket frame size of 4194304 (WebSocketClientInitializer) configurable via a system property. We are using karate and chrome to create PDF's for some possibly very big HTML pages and are running frequently in this limitation.

@reini2150 sure that makes sense. this is the first time we've heard someone use the chrome / pdf capabilities, sounds like it works well for you ?

yes it works like a charme. we have 2 portable chrome instances running in debug mode as a windows service and are using karate to communicate with them

@reini2150 do you think you can build from source and check ? it is simple: https://github.com/intuit/karate/wiki/Developer-Guide
here is the draft documentation, there is a new start(Map) method: https://github.com/intuit/karate/tree/develop/karate-core#chrome-java-api

I build it from source and it does works like expected. Thanks a lot for your efforts.

released 0.9.3


Fix a minor typo.

Current coverage is 95.45%

Merging #1 into master will not affect coverage as of 5f0b1e8

@@            master      #1   diff @@
======================================
  Files            3       3
  Stmts           66      66
  Branches         0       0
  Methods          0       0
======================================
  Hit             63      63
  Partial          0       0
  Missed           3       3

Review entire Coverage Diff as of 5f0b1e8

Powered by Codecov. Updated on successful CI builds.

Coverage remained the same at 95.455% when pulling bcb7672d9322dfff3b522b1fd662d639548f3fbb on micrypt:patch-1 into f194da6573a4665b1a509b4112867589517a0dc6 on novascreen:master.

thanks @micrypt


Add endpoints, upgrade dependencies, adapt for "pending strategy account"

(just subscribed, so wanted to upgrade the lib to use when account setup 🚀 )
Also added some debug stuff into call-all-apis (and a logger) https://getpino.io/#/
fixes  #31 #37 #45 #47 #48 #49
Also update some types, handle "pending" investmentAccount state (can't access anything except screenshot below)

new functions

[x] getInvestProfileHistory (Public)
[x] getAdviceDTO 👀 (Usable even if "strategy" not fully defined aka waiting for "custom video")
[x] getTwitch
[x] getAdviceWaitingVideo
[x] getKycQuestions
[x] getKycCategories
[x]  getUserInvestmentAccountProviders
[x] getUserInvestmentAccount
[x] getInitialConsultingAnalysis
[x] getMonthlyConsultingAnalysis

Done some kind of charts with it (better than a "waiting" screen) : https://typescript-w3afxa.stackblitz.io

Thank you for your contribution 🤗

Feel free to take the ownership of the project. I never finished it. If I have time to contribute I'll be happy to do it.

I changed package.name to test a release deploy on NPM, maybe we should move it to an organization

As you wish you are way more motivated than me 😅

Taking ownership then, added docs + npm publish : https://www.npmjs.com/package/@m1m1s1ku/monpetitplacement_sdk


Just want to confirm if this failure is intended

I have a model acts like the test case attached. If tested with tf-v1.8 (which I previously worked on), incorrect dims will be output. If tested with master, a recently added assertion in tensorflow/lite/simple_memory_arena.cc:100 will be triggered.
To reproduce the error, posting test case is simpler. So even if this PR is more like an issue report, please kindly allow me to post here and ask if model like this is a misuse? Or it is not supported by TFLite? Thanks.

I signed it!

Is there any chance you can attach your model as well? There can be subtle differences between a loaded model and trying to manually construct it in a test.

Sure. I just realized there is Python front-end for TFLite now :) So it is possible to reproduce it in single Python script:
OS: Ubuntu Linux 18.04 LTS
Python & TF version:
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.3.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import tensorflow

In [2]: tensorflow.__version__
Out[2]: '1.13.1'

Reproduce steps:
import numpy as np
import tensorflow as tf

i = tf.placeholder(dtype=tf.float32, shape=[2, 2, 1, 1])
p = tf.placeholder(dtype=tf.int32, shape=[4, 2])
a = tf.placeholder(dtype=tf.float32, shape=[1])

n = tf.negative(a)
o = tf.add(tf.pad(i, p), n)

test_input = np.array([[[[0]], [[0]]],[[[0]], [[0]]]], dtype=np.float32)
test_pad = np.array([[2,2],[2,2],[0,0],[0,0]], dtype=np.int32)
test_pad_2 = np.array([[4,4],[4,4],[0,0],[0,0]], dtype=np.int32)
test_a = np.array([1], dtype=np.float32)

def test_tf():
    with tf.Session() as sess:
        out = sess.run(o, {i: test_input, p: test_pad, a: test_a})
        assert out.shape == (6, 6, 1, 1)

        out = sess.run(o, {i: test_input, p: test_pad_2, a: test_a})
        assert out.shape == (10, 10, 1, 1)

test_tf()

# convert
with tf.Session() as sess:
    conv = tf.lite.TFLiteConverter.from_session(sess, [i, p, a], [o])
    lite_model_bytes = conv.convert()

def test_tflite():
    interp = tf.lite.Interpreter(model_content=lite_model_bytes)

    #### I just hard-coded them:
    # print(interp.get_input_details())
    # print(interp.get_output_details())

    interp.allocate_tensors()
    interp.set_tensor(3, test_input)
    interp.set_tensor(4, test_pad)
    interp.set_tensor(5, test_a)

    interp.invoke()
    assert interp.get_tensor(0).shape == (6, 6, 1, 1)

    interp.set_tensor(4, test_pad_2)

    interp.invoke()
    assert interp.get_tensor(0).shape == (10, 10, 1, 1)

test_tflite()

Awesome, thanks for the minimal repro! Just to confirm, is this the line that is failing in your local repro?
If this graph works properly in TF, then it should also behave properly in TFLite, so it's most likely a bug or an issue with conversion. Feel free to file a bug in parallel while we investigate.

Awesome, thanks for the minimal repro! Just to confirm, is this the line that is failing in your local repro?

Yes. I got following console output:
RuntimeError: tensorflow/lite/simple_memory_arena.cc:100 erased_allocs_count != 1 (0 != 1)

If changing input and paddings to other reasonable values, we can get similar error like this one:
RuntimeError: tensorflow/lite/simple_memory_arena.cc:93 it->size != alloc.size (36 != 4)

If this graph works properly in TF, then it should also behave properly in TFLite, so it's most likely a bug or an issue with conversion. Feel free to file a bug in parallel while we investigate.

IMHO arena is not properly reset in some cases. If we force arena to re-compute before every invocation, this issue won't happen. But it is kind ugly...

So, I'm not able to repro the error from your Python test case, but I do see it with the native unit test case. Looking into it now.

I'm going to close the PR, but we're tracking this internally. If you want to file a separate issue that would be helpful, as it very likely could be a legit bug.

Ops have to be in specific order to trigger this, so we probably still need the model file to figure out. I posted the issue and model file here: #26549.


feat: Support '-F' as an alias for '--features'

What does this PR try to resolve?
Adds a short flag -F for --features to all cargo commands to be consistent with the -F` short flag being added in #10472.
How should we test and review this PR?
The decision for this is a part of #10472 which is in FCP.

It looks like all commands except cargo-add are using the prelude to
define --features, so this should hit them all.
Man pages were updated
I've updated completions to the best of my knowledge and am unsure of good testing strategies for them
I'm assuming we don't add tests for every sort flag but rely on clap
to have coverage to ensure it works.

Review the commits separately.  For the documentation change, the only manual change is in  src/doc/man/includes/section-features.md, the rest are code-generated.

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

Hmm… I still love to see them mentioned in manpages for users to discover this new alias when running cargo help build or else.
https://github.com/rust-lang/cargo/blob/d087aeb845d6fe2b740b27179318d2d5045c2ae9/src/doc/man/includes/section-features.md

Hmm… I still love to see them mentioned in manpages for users to discover this new alias when running cargo help build or else.
https://github.com/rust-lang/cargo/blob/d087aeb845d6fe2b740b27179318d2d5045c2ae9/src/doc/man/includes/section-features.md

Done

@bors r+

:pushpin: Commit f728045729d02afea8bec51f9a8cdd6a6d4e3d8b has been approved by weihanglo

:hourglass: Testing commit f728045729d02afea8bec51f9a8cdd6a6d4e3d8b with merge 46c7a2b39c2378d2e46b1b917a91130cc3b717b3...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 46c7a2b39c2378d2e46b1b917a91130cc3b717b3 to master...


⚠ Bofrost.at has degraded performance

In d4d9686, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2544 ms

Resolved: Bofrost.at performance has improved in 57b94eb.


Is there any way to specify Python version used in environment?

Currently, I am running the dependency-check on the requirements.txt file and the Python virtual environment folder.
Is there a way to specify the Python version being used so that I do not receive notifications about CVEs targeting Python versions lower than the one in use?
I appreciate your help.

CPEs do not encode the target language/platform version, and dependency check's CPE matcher does not look at the platform (if specified) in the first place.
Basically, the CVE ecosystem is not set up to support what you want.


Does only work with Linux Containers

Unfortunately, this version only works with Linux containers (Container action is only supported on Linux from GitHub actions). Is there any way to make this work on other container types? I would need it to change some content pre-building android and ios apps.
Thanks

I'm afraid GitHub only supports Linux with container actions.
This repo is a template repo for container actions written in go and therefore we can only support Linux.


Update libs with Statistics endpoints

Add support for two recently added Statistics endpoints:

Calculate Aggregate App Stats
Aggregate Event Types

Note that Aggregate Event Types is technically still hidden in our API documentation. Should we fix that?


fix: DevTools cannot be showed in Chrome and Firefox on Nuxt v4

🐛 The bug
I am using the nightly version of Nuxt (nuxt-nightly@4.0.0-28688968.58f4f477). I found Nuxt DevTools (no matter the nightly or<EMAIL_ADDRESS>does not work on Chrome 126 and Firefox 129.0b6 (Attachment #2). Notably, it works on Safari 17.5 (Attachment #1). It used to worked on Nuxt v3.

When adding breakpoints to the code related to Nuxt DevTools, I found Firefox (and Chrome) indeed ran import("./view/client") but setupDevToolsClient was never called, as the attachment #3 shown. Safari ran as expected (attachment #4). Not sure why.
https://github.com/user-attachments/assets/df0c3b68-3e77-4791-ba55-f837bfe0efb5
https://github.com/user-attachments/assets/0ad4a9cd-7570-4cb4-b62f-df250b996a32
🛠 To reproduce
https://github.com/pan93412/nuxt-4-devtools-regression
🌈 Expected behavior
The Nuxt DevTools should be able to show on Chrome, Firefox, and Safari.
ℹ Additional context
No response

duplicate #698


disable request sampling in IAST Java

Use environment variables to enable IAST (DD_IAST_ENABLE=true).
Also to disable sampling (DD_IAST_REQUEST_SAMPLING=100), currently supported by Java.
Mark rate limit test as bug for all Node variants.

it seems that there is side effect wioth the sampling scenario (see nodejs CI)

@cbeauchesne I extended the exclusion for that test, see the updated PR. The issue is already tracked at APPSEC-5427.

Thanks @smola ,
I'll re-run the CI two or three times, to check if there is no flackyness by adding this
ENV DD_IAST_ENABLED=true
ENV DD_IAST_REQUEST_SAMPLING=100

Side question, what is the meaning of DD_IAST_REQUEST_SAMPLING=100 ?

@cbeauchesne Side question, what is the meaning of DD_IAST_REQUEST_SAMPLING=100 (I mean, what is 100) ?

It's a percentage. IAST analysis will apply to 100% of (non-current) requests. There's another limit for the number of concurrent requests that can be analyzed (DD_IAST_MAX_CONCURRENT_REQUESTS, 2 by default).

Ok, thanks you. I've rerun Circle CI, it seems to be a circle ci failure not related with our change

@cbeauchesne Tests passed now. A test for Python/Django flaked, but I think it's unrelated (no IAST in Python AFAIK):
runner           | ==================================================== ASYNC FAILURE =====================================================
runner           | ____________________________________________ test_trace_header_count_match _____________________________________________
runner           |
runner           |         def test_trace_header_count_match(self):
runner           |             """X-Datadog-Trace-Count header value is right in all traces submitted to the agent"""
runner           |
runner           |             def validator(data):
runner           |                 for header, value in data["request"]["headers"]:
runner           |                     if header.lower() == "x-datadog-trace-count":
runner           |                         try:
runner           |                             trace_count = int(value)
runner           |                         except ValueError:
runner           |                             raise Exception(
runner           |                                 f"{self.count_header} request header in {data['log_filename']} wasn't an integer: {value}"
runner           |                             )
runner           |
runner           |                         if trace_count != len(data["request"]["content"]):
runner           |                             raise Exception(
runner           |                                 f"x-datadog-trace-count request header in {data['log_filename']} didn't match the number of traces"
runner           |                             )
runner           |
runner           | E           interfaces.library.add_traces_validation(validator=validator, is_success_on_expiry=True)
runner           |
runner           | tests/test_data_integrity.py:69: X-Datadog-Trace-Count header value is right in all traces submitted to the agent not validated on library interface

@robertomonteromiguel Done.


version 0.4.3 not available in bower

Hi guys, just an fyi - I tried to update to 0.4.3 and got
bower ENORESTARGET  No tag found that was able to satisfy 0.4.3

Additional error details:
Available versions in https://github.com/angular-ui/angular-ui-router-bower.git:
 1.0.15, 1.0.14, 1.0.13, 1.0.12, 1.0.11, 1.0.10, 1.0.9, 1.0.8, 1.0.7, 1.0.6, 1.0
.5, 1.0.4, 1.0.3, 1.0.1, 1.0.0, 1.0.0-rc.1, 1.0.0-beta.3, 1.0.0-beta.2, 1.0.0-be
ta.1, 1.0.0-alpha.5, 1.0.0-alpha.4, 1.0.0-alpha.3, 1.0.0-alpha.2, 1.0.0-alpha.1,
 0.4.2, 0.4.1, 0.4.0, 0.3.2, 0.3.1, 0.3.0, 0.2.18, 0.2.17, 0.2.16, 0.2.15, 0.2.1
4, 0.2.13, 0.2.12, 0.2.11, 0.2.10, 0.2.9, 0.2.8-bowratic-tedium, 0.2.7, 0.2.6, 0
.2.5, 0.2.0, 0.0.1

Thanks! I've published 0.4.3 to bower


UnauthorizedAccessException for C:\Users\user\Application Data

I cloned the repository, The following shows my local directory.

When I execute dotnet try in the directory or any subdirectory I get the message (in the Edge browser):
"An unhandled exception occurred.","exception":"System.UnauthorizedAccessException: Access to the path 'C:\\Users\\sam\\Application Data' is denied.\r\n
Perhaps I just do not understand the instructions.

 It works.


Overflow to HTML instead of BODY or both

This doesn't work unless we set overflow to the HTML instead of BODY.
Am I missing anything?

NVM I was just being stupid, I already had a css on html to set the overflow so this is why it didn't work :)


1.x Enforce patch scope by default.

NetflixOSS » eureka » eureka-pull-requests #1 SUCCESS
This pull request looks good

eureka-pull-requests #419 SUCCESS
This pull request looks good


Fix LM for banded jacobian

[ ] Make Multiple Shooting in https://github.com/SciML/BoundaryValueDiffEq.jl/pull/122 work Levenberg

I think we can go ahead with this. The 23 test problems for some seem a bit flaky. This PR doesn't even tough Broyden and it broke...


OneHot Layer

From my current modeling tasks, I see that it would be useful to have the flexibility to encode a categorical feature either in one-hot format or embedding format (using Embedding layer) right in the model construction phase instead of creating dummy columns in advance in case of one-hot encoding (it is the zero-based integers in case of Embedding). Though we can use Lambda layer for that purpose, I think it would be more convenient to have a OneHot layer instead. I wrote the code for the propose OneHot layer already which just calls K.one_hot() internally. Feel free to give your thought on whether we should add such layer or not in Keras. I am happy to contribute the code via a PR. Thanks.
The pseudo-code would be like this
models = []
for feature in features:
        if is_categorical(feature):
            model = Sequential()
            if to_encode(feature) == 'one_hot':
                model.add(OneHot())
            else:
                model.add(Embedding())
            models.append(model)
        else:
            model = Sequential()
            model.add(Dense())
            models.append(model)

model = Sequential()
model.add(Merge(models, mode='concat'))
...more layers added...

I created a PR https://github.com/fchollet/keras/pull/3846

Lambda(K.one_hot()) instead as suggested by @fchollet

There are a few catches when using Lambda(K.one_hot), but generally it's possible:

the input must be integer (uint8, int32, int64), not float32
you have to specify the number of classes explicitly
you have to specify the output shape explicitly

from keras import backend as K
from keras.layers import Input, Lambda

input_shape = (10, ) # sequences of length 10
nb_classes = 20
output_shape = (input_shape[0], nb_classes)
input = Input(shape=input_shape, dtype='uint8')
x_ohe = Lambda(K.one_hot, arguments={'nb_classes': nb_classes}, output_shape=output_shape)(input)

Try this like:
import numpy as np
from keras.models import Model
# 5 sequences of length 10
X_classes = np.random.randint(0, 20, size=(5, 10))
assert Model(input, x_ohe).predict(X_classes) == (5, 10, 20)

Full example in a gist: https://gist.github.com/bzamecnik/a33052ec46ee7efeb217856d98a4fb5f


camel-quarkus-support-azure-core fails to compile with Netty 4.1.68

azure-core depends on netty-tcnative-boringssl-static. Since the Quarkus main branch bumped to Netty 4.1.68, camel-quarkus-support-azure-core does not compile.
Seems the same issue as reported here https://github.com/netty/netty/issues/11691.
Failed to execute goal on project camel-quarkus-support-azure-core: Could not resolve dependencies for project org.apache.camel.quarkus:camel-quarkus-support-azure-core:jar:2.3.0-SNAPSHOT: Could not find artifact io.netty:netty-tcnative-boringssl-static:jar:${tcnative.version} in central (https://repo.maven.apache.org/maven2) -> [Help 1]
2021-09-17T05:11:11.5234936Z org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project camel-quarkus-support-azure-core: Could not resolve dependencies for project org.apache.camel.quarkus:camel-quarkus-support-azure-core:jar:2.3.0-SNAPSHOT: Could not find artifact io.netty:netty-tcnative-boringssl-static:jar:${tcnative.version} in central (https://repo.maven.apache.org/maven2)

We should maybe investigate trying to cut out tcnative, but it leads to some native compilation issues.

This makes my parametrized BOM PR fail in Azure grouped test. I filed https://github.com/quarkusio/quarkus/issues/20461


[sil-combine] Fix a bug in the cond_br (select_enum) -> switch_enum peephole

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

This transformation should not introduce any new critical edges, because sil-combine is not supposed to do this.
rdar://27767387

@swift-ci Please test

Merging since CI completed with no issues.


Validation: May 9th, Various alt-text added, and code-block indentation.

Validation fixes - alt-text added, and code-block indentation

@Rick-Anderson
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!


doc: improve the doc of Kubernetes deployment

Signed-off-by: YaoZengzeng<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did

Make user be able find the documents relevant to Kubernetes easily.

Make the document of how to deploy Kubernetes with Pouch more complete and user-friendly.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@allencloud PTAL

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1019   +/-   ##
=======================================
  Coverage   14.02%   14.02%
=======================================
  Files         125      125
  Lines        8469     8469
=======================================
  Hits         1188     1188
  Misses       7181     7181
  Partials      100      100

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 12435f4...50a8a5b. Read the comment docs.

LGTM, thanks a lot for your work. @YaoZengzeng


Add liftEff and liftAff variants for parent components

/cc @cryogenian
These types are nasty, but we can't refer to QueryF in here without having a circular dependency in the modules.

After chatting on Slack looks like these functions aren't too useful as inference can't use them without explicit typing, which pretty much defeats the point of these helpers.
Constraints being the problem as ever:
No instance found for

  Control.Monad.Eff.Class.MonadEff _1822
                                   (Aff ( now :: Now
                                        , file :: READ_FILE
                                        , err :: EXCEPTION
                                        , zClipboard :: ZCLIPBOARD
                                        , console :: CONSOLE
                                        , ref :: REF
                                        , ajax :: AJAX
                                        , avar :: AVAR
                                        , random :: RANDOM
                                        , dom :: DOM
                                        )
                                   )


Drop support for UIWebView

@Titozzz asked me if we could drop support for UIWebView in this package, and I had already mentioned this in the RFC. When testing this package, there are several issues with UIWebView, so it makes sense to drop support for it.
My proposal is to leave UIWebView in (for now) but not put engineering time into it, and in a few versions drop support for UIWebView entirely.

This package now uses WKWebView by default instead of UIWebView (per #3). I'll leave this issue open, as we'll want to fully drop support for UIWebView at some point.

Great 🎉

Dup of #312


Receiving and Sending Show Progress

Please Help.
I want to Show Receiving and Sending Progress in Progress Bar.
Thank you.

Hi @Mehsoor which Send methods are you using specifically - string, byte[], or stream?

Hi @Mehsoor , you could try to use the .Send method to send the length of the byte array you're willing to send first, then the byte array, then on the client side add an int variable that increments for each byte received which in turn calls a UI update method (At least, that's how I'd have done it)

Hi @Mehsoor which Send methods are you using specifically - string, byte[], or stream?

I'm using byte[] Method for 'Send' data.

Hi @Mehsoor thank you.  We could add a new series of Send APIs that take an Action as a parameter that gets invoked every time input data is read and then written to the underlying network.  That invocation could relay the number of bytes sent and the total number of bytes.  For receiving data, if you are consuming data from the network using StreamReceived you are already given the number of bytes to read and you control reads against the stream.  It wouldn't make sense to report progress on MessageReceived.
Would the enhancement above be sufficient?

Hi @Mehsoor thank you. We could add a new series of Send APIs that take an Action as a parameter that gets invoked every time input data is read and then written to the underlying network. That invocation could relay the number of bytes sent and the total number of bytes. For receiving data, if you are consuming data from the network using StreamReceived you are already given the number of bytes to read and you control reads against the stream. It wouldn't make sense to report progress on MessageReceived.
Would the enhancement above be sufficient?

thank you brother god bless you...


Installation

Sorry but I have python3 installed and first I can't clone the repo with your command (It must be git clone https://github.com/Lopinosaurus/FloppyRecorder.git)and if I download the files there is this:

Hello, thank you for your report !
Indeed, I made an error writing this command. I'll edit the README ASAP. Actually, the pip command is :
python3 -m pip install -r requirements.txt
If the clone command does not work, you probably just do not have your ssh configured. You can clone by an other way running this command :
git clone https://github.com/Lopinosaurus/FloppyRecorder.git
If you need help, do not hesitate to open an other issue, or add me on Discord : Lopinosaurus#0404


release 0.7.11

Checklist

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

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

there is some breakage when /tmp is on a different device. gonna skip this release.