Using help, FSUM7351 is issued

bash-5.2$ which less
/hewitt/zopentools/zopen_repo/usr/local/bin/less

Confirmed build without env var check in fails:
bash-5.2$ c3270 --version
c3270 v4.3ga8 Mon Jun 24 17:25:58 UTC 2024 JENKINS
Build options: --enable-local-process --without-readline --without-curses-wide --with-iconv via gcc C/C++ for Open Enterprise Languages on z/OS, 2.0.0, Clang 14.0.0 (build 69e1330) 64-bit
TLS provider: OpenSSL 3.2.0 23 Nov 2023
SBCS host code pages (with aliases):
cp037 (cp37, us, us-intl), cp273 (german), cp275 (brazilian), cp277 (norwegian), cp278 (finnish, swedish), cp280 (italian), cp284 (spanish), cp285 (uk), cp297 (french), cp424 (hebrew), cp500 (belgian), cp803 (hebrew-old), cp870 (polish, slovenian), cp871 (icelandic), cp875 (greek), cp880 (russian), cp1026 (turkish), cp1047, cp1140 (us-euro), cp1141 (german-euro), cp1142 (norwegian-euro), cp1143 (finnish-euro, swedish-euro), cp1144 (italian-euro), cp1145 (spanish-euro), cp1146 (uk-euro), cp1147 (french-euro), cp1148 (belgian-euro), cp1149 (icelandic-euro), cp1160 (thai), bracket (oldibm, bracket437)

Copyright 1989-2024, Paul Mattes, GTRC and others.
See the source code or documentation for licensing details.
Distributed WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
bash-5.2$ c3270
c3270 v4.3ga8 Mon Jun 24 17:25:58 UTC 2024 JENKINS
Copyright 1989-2024 by Paul Mattes, GTRC and others.

Type 'show copyright' for full copyright information.
Type 'help' for help information.

c3270> help
/jenkins/zopen/usr/local/zopen/less/less-heads.v657.20240606_184125.zos/bin/less: FSUM7351 not found
  help all           all actions
  help 3270          3270 actions
  help interactive   interactive (command-prompt) actions
  help <action>      help for one <action>
  help options       command-line options
  help scripting     scripting actions
  help file-transfer file transfer options
c3270> quit
c3270>

Building code now with: https://github.com/ZOSOpenTools/c3270port/pull/18 and will add in an additional comment if this fixes the problem for me.

This works for me now. Ensure you have a build that is at least as current as:
bash-5.2$ c3270 --version
c3270 v4.3ga8 Tue Jun 25 01:24:49 UTC 2024 JENKINS
Build options: --enable-local-process --without-readline --without-curses-wide --with-iconv via gcc C/C++ for Open Enterprise Languages on z/OS, 2.0.0, Clang 14.0.0 (build 69e1330) 64-bit
TLS provider: OpenSSL 3.2.0 23 Nov 2023
SBCS host code pages (with aliases):
cp037 (cp37, us, us-intl), cp273 (german), cp275 (brazilian), cp277 (norwegian), cp278 (finnish, swedish), cp280 (italian), cp284 (spanish), cp285 (uk), cp297 (french), cp424 (hebrew), cp500 (belgian), cp803 (hebrew-old), cp870 (polish, slovenian), cp871 (icelandic), cp875 (greek), cp880 (russian), cp1026 (turkish), cp1047, cp1140 (us-euro), cp1141 (german-euro), cp1142 (norwegian-euro), cp1143 (finnish-euro, swedish-euro), cp1144 (italian-euro), cp1145 (spanish-euro), cp1146 (uk-euro), cp1147 (french-euro), cp1148 (belgian-euro), cp1149 (icelandic-euro), cp1160 (thai), bracket (oldibm, bracket437)

Copyright 1989-2024, Paul Mattes, GTRC and others.
See the source code or documentation for licensing details.
Distributed WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@gngrossi please verify when you get a chance

@MikeFultonDev
Upgraded c3270.

Is this the intended dialogue flow?

Entered help and this is displayed at the bottom of the screen which seems to require q to quit.

thanks

yes - that looks right. The (END) indicates that less is being run.


Fix format and replace variables in configure-azure-cni-dynamic-ip-allocation.md

Solve tab issue.
There are existing variables. No need to set one more time.

@asudbring
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


[CROSSDATA-69] [Mongo Datasource] Fix samplingratio with double

Fix an error introduced in PR #50

+1


Basic Types - minor problem

Followed the given instructions at page Documentation - The Basics
When I run this command:
tsc --target es2015 hello.ts
I get these:
../node_modules/@types/node/globals.d.ts:325:84 - error TS2792: Cannot find module 'undici-types'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?
325         type _Request = typeof globalThis extends { onmessage: any } ? {} : import("undici-types").Request;
~~~~~~~~~~~~~~
../node_modules/@types/node/globals.d.ts:326:85 - error TS2792: Cannot find module 'undici-types'. Did you mean to set the 'moduleResolution' option to 'nodenext', or to add aliases to the 'paths' option?
326         type _Response = typeof globalThis extends { onmessage: any } ? {} : import("undici-types").Response;

The 'moduleResolution' option is 'Classic' by default  when you set target as 'es2015' . In this way, tsc cannot find where "undid-types" is by import function.To solve it, you'd better set moduleResolution option nodenext.

@zhangzhuang15
How to proceed if I need my module to be AMD?

@arokettu Based on this answer we should downgrade @node/types to 20.0.0
https://github.com/pop-os/shell/issues/1664#issuecomment-1872839729
Since I was not using it directly (but it was being used by other dependencies) I had to install it (with this specific version) and it worked.

This confused me as well, because I did not expect to encounter an error while doing the basic tutorial.
I had success adding a tsconfig and extending from a base as described in the handbook https://www.typescriptlang.org/docs/handbook/tsconfig-json.html#tsconfig-bases
In my case, I installed Node 20 https://github.com/tsconfig/bases/?tab=readme-ov-file#node-20-tsconfigjson


Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN

After upgrading to 1.2.1 all applications using MahApps.Metro show a "Set property 'System.Windows.ResourceDictionary.DeferrableContent' threw an exception." on start which is due to a mismatch of the public key token.
Any Idea how to fix this?

hmm.. guess we got the same issue: https://github.com/MahApps/MahApps.Metro/issues/2314 posted the issue just a few minutes apart, too ;-)

-> #2314


wepwebkit-depends: check commercial license

acceptance properly for openh264 and gstreamer1.0-libav. For both LICENSE_FLAGS_ACCEPTED needs to
contain "commercial" to use it

@psaavedra the walnascar error looks unrelated - my hot guess would be https://git.yoctoproject.org/poky/commit/meta/recipes-support/icu?id=315588665f9a15f130b770c7a69ecfc37a9edf9d - there has been some changelog regarding UnicodeString in ICU 76

@psaavedra the walnascar error looks unrelated - my hot guess would be https://git.yoctoproject.org/poky/commit/meta/recipes-support/icu?id=315588665f9a15f130b770c7a69ecfc37a9edf9d - there has been some changelog regarding UnicodeString in ICU 76

Yes, like in https://github.com/Igalia/meta-webkit/pull/522#issuecomment-2522014820  .
I've created https://github.com/Igalia/meta-webkit/issues/523 for addressing this separately.

@clopez  can you r? this change. Thanks.


Menu Entry Swapper Suggestion - Swap the 'Pick' option with 'Inspect' on flowers

Issue:
Currently it is easy to misclick a flower used for protecting crops from disease and pick it out, resulting in losing the protection and having to replant said flower.
Solution:
Add the ability to swap the 'Pick' option with 'Inspect' to stop accidentally picking flowers.
Additional context:
Option should exclude Limpwurt Roots and Woad Seeds as they only provide crops, without protecting other crops from disease (so there is no reason not to pick them).

This can now be done with the changes in 92aac53f4273e7944c3da767637e083847c03808


Add descriptions how to update, remove or rename runtime kinds and language families

Removing or renaming runtime kinds and language families by simply changing the runtime manifest breaks existing actions. This change introduces documentation and adds background information to the pre-defined runtime manifests.
For example, a change like #4390 breaks existing actions.
This PR adds a description property to all pre-defined runtime manifests without updating the ExecManifest tooling. As a consequence, the description property is ignored by controllers and invokers and only serves documentation purposes. With that change, I hope to prevent unconscious changes of the runtimes breaking existing actions.
My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[x] Documentation
[x] Pre-defined runtime manifests

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[x] I updated the documentation where necessary.

@falkzoll @sciabarracom do you want to take a look at this PR from a runtime maintainer perspective?

Codecov Report

Merging #4627 into master will decrease coverage by 5.67%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4627      +/-   ##
==========================================
- Coverage   84.44%   78.77%   -5.68%
==========================================
  Files         183      183
  Lines        8305     8305
  Branches      574      574
==========================================
- Hits         7013     6542     -471
- Misses       1292     1763     +471

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.89%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0% <0%> (-94.74%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedListener.scala
0% <0%> (-86.67%)
:arrow_down:

...e/database/cosmosdb/cache/KafkaEventProducer.scala
0% <0%> (-76.48%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-74.08%)
:arrow_down:

...a/org/apache/openwhisk/common/ExecutorCloser.scala
0% <0%> (-66.67%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
4% <0%> (-52%)
:arrow_down:

... and 7 more

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 2036548...79ec1d1. Read the comment docs.

@dgrove-oss thanks a lot for reviewing and providing clarifications / improvements. I incorporated your proposals.

👍 to document how to remove an existing runtime/kind in a controlled way from an already running openwhisk makes a lot of sense. Thanks for providing this guidance.

@rabbah @dgrove-oss all feedback should be addressed and I added your suggestions (thanks a lot for improving wording). Can any of you please merge?

Thanks for all your work on this @sven-lange-last  -- merging

@sven-lange-last I'v try the API docs on my Mac. And yes, it would show swagger.json for documentation like dgrove-oss said. See those picture:

Hope to get more progress on this, since wrong documentation would mislead the action developers...


JSQMessagesBubbleImageFactory initialized with custom image for chat bubble not working

New issue checklist

[ ] I have read all of the README, documentation, and FAQ.
[ ] I have reviewed the contributing guidelines. Confirmation: ____
[ ] I have searched existing issues and this is not a duplicate.

General information

Library version(s):
iOS version(s):
Devices/Simulators affected:
Reproducible in the demo project? (Yes/No):
Related issues:

Bug report
Expected behavior

...

Actual behavior

...

Steps to reproduce

...

Crash log? Screenshots? Videos? Sample project?

...

Question or Feature Request

...

Help Needed
Need to hide the default image of bubble and show my own bubble image, try to change image using following code but not working
outgoingBubbleImageView = JSQMessagesBubbleImageFactory.init(bubbleImage: UIImage(named: "bubbleMine"), capInsets: UIEdgeInsetsZero).outgoingMessagesBubbleImageWithColor(UIColor.grayColor())

...

Thanks @bikram109 ! 😄
You need to return your images from the data source method, messageBubbleImageDataForItemAtIndexPath:


Using Ollama models

OSError: ollama/llama3.1 is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'
Took me a while to figure out why I couldn't use llama3.1 given that another I could in another virtual environment. I realised that the pipeline-llm extra is needed.
Perhaps it would be helpful to provide the option when installing?

Just added pipeline-llm to requirements.txt


Issue with Data Flow

I'm getting an error message on Step 4 - Import the App - I get this error message on the Data Flow:
Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: { "status": 404, "message": "List not found\r\nclientRequestId: d5622a97-5e53-497a-8b20-2686b59afb1e\r\nserviceRequestId: d5622a97-5e53-497a-8b20-2686b59afb1e" }'.
Any ideas what we're doing wrong please?

Anyone help with this?
I have the same error:
Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: { "status": 404, "message": "List not found\r\nclientRequestId: 897770d3-7d71-407b-ac08-16af811c5982\r\nserviceRequestId: 897770d3-7d71-407b-ac08-16af811c5982" }'.

Anyone help with this?
I have the same error:
Flow save failed with code 'DynamicOperationRequestClientFailure' and message 'The dynamic operation request to API 'sharepointonline' operation 'GetTable' failed with status code 'NotFound'. This may indicate invalid input parameters. Error response: { "status": 404, "message": "List not found\r\nclientRequestId: 897770d3-7d71-407b-ac08-16af811c5982\r\nserviceRequestId: 897770d3-7d71-407b-ac08-16af811c5982" }'.

Same here here to.... GetTable failed with status code 'NotFound'

Same here here to.... GetTable failed with status code 'NotFound'

Hi, I have now resolved the issue by recreating the the CLASSROOMDROPIN definition file but being very careful to get the exact SharePoint info added. It turns out I had 1 extra character in the file causing this to fail

Hi, I have now resolved the issue by recreating the the CLASSROOMDROPIN definition file but being very careful to get the exact SharePoint info added. It turns out I had 1 extra character in the file causing this to fail


[Bug] [seatunnel-connector-spark-File] source and sink default config don't take effect

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Purpose: Source[File]  -> Sink[File]
Error:

Source[File] default config format doesn't take effect
Sink[File] default config path_time_format has problem

SeaTunnel Version
dev
SeaTunnel Config
#
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

######
###### This config file is a demonstration of batch processing in SeaTunnel config
######

env {
  # You can set spark configuration here
  # see available properties defined by spark: https://spark.apache.org/docs/latest/configuration.html#available-properties
  spark.app.name = "SeaTunnel"
  spark.executor.instances = 2
  spark.executor.cores = 1
  spark.executor.memory = "1g"
  spark.master = local
}

source {
  # This is a example input plugin **only for test and demonstrate the feature input plugin**
//  Fake {
//    result_table_name = "my_dataset"
//  }
  file {
    path = "file:///Users/mac/Desktop/filetest/logs"
    result_table_name = "access_log"
  }

  # You can also use other input plugins, such as hdfs
  # hdfs {
  #   result_table_name = "accesslog"
  #   path = "hdfs://hadoop-cluster-01/nginx/accesslog"
  #   format = "json"
  # }

  # If you would like to get more information about how to configure seatunnel and see full list of input plugins,
  # please go to https://seatunnel.apache.org/docs/spark/configuration/source-plugins/Fake
}

transform {
  # split data by specific delimiter

  # you can also use other transform plugins, such as sql
  # sql {
  #   sql = "select * from accesslog where request_time > 1000"
  # }

  # If you would like to get more information about how to configure seatunnel and see full list of transform plugins,
  # please go to https://seatunnel.apache.org/docs/spark/configuration/transform-plugins/Split
}

sink {
  # choose stdout output plugin to output data to console
  file {
    path = "file:///Users/mac/Desktop/filetest/logs2"
    serializer = "text"
  }
  # you can also you other output plugins, such as sql
  # hdfs {
  #   path = "hdfs://hadoop-cluster-01/nginx/accesslog_processed"
  #   save_mode = "append"
  # }

  # If you would like to get more information about how to configure seatunnel and see full list of output plugins,
  # please go to https://seatunnel.apache.org/docs/spark/configuration/sink-plugins/Console
}

Running Command
LocalSparkExample

Error Exception
error 1:
org.apache.seatunnel.command.BaseTaskExecuteCommand  - Plugin[org.apache.seatunnel.spark.source.File] contains invalid config, error: please specify [format] as non-empty

error 2:
Exception in thread "main" java.lang.RuntimeException: Execute Spark task error
	at org.apache.seatunnel.command.spark.SparkTaskExecuteCommand.execute(SparkTaskExecuteCommand.java:52)
	at org.apache.seatunnel.command.spark.SparkTaskExecuteCommand.execute(SparkTaskExecuteCommand.java:32)
	at org.apache.seatunnel.Seatunnel.run(Seatunnel.java:48)
	at org.apache.seatunnel.example.spark.LocalSparkExample.main(LocalSparkExample.java:33)
Caused by: java.lang.IllegalArgumentException: Illegal pattern character 'p'
	at java.text.SimpleDateFormat.compile(SimpleDateFormat.java:826)
	at java.text.SimpleDateFormat.initialize(SimpleDateFormat.java:634)
	at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:605)
	at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:580)
	at org.apache.seatunnel.common.utils.StringTemplate.substitute(StringTemplate.java:40)
	at org.apache.seatunnel.spark.sink.File.output(File.scala:63)
	at org.apache.seatunnel.spark.sink.File.output(File.scala:33)
	at org.apache.seatunnel.spark.batch.SparkBatchExecution.sinkProcess(SparkBatchExecution.java:89)
	at org.apache.seatunnel.spark.batch.SparkBatchExecution.start(SparkBatchExecution.java:102)
	at org.apache.seatunnel.command.spark.SparkTaskExecuteCommand.execute(SparkTaskExecuteCommand.java:50)
	... 3 more

Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You should specify the format parameter, the documentation has errata, can you submit a PR to fix it?

Or you can submit pr to set default parameters
I will submit fix a PR to fix the documentation

fixed #1590


catch all/wild card matching

There is no documented way (and appears to be no technical way) of matching against a wildcard value
we want to be able to do
bloomrun.add({}, {meow: 1})
bloomrun.lookup({foo: 'bar'}) // {meow: 1}

and
bloomrun.add({foo: /.*/}, {meow: 1})
bloomrun.lookup({foo: 'bar'}) // {meow: 1}

@davidmarkclements Could you do a slight of hand with the first to light it up? The second should work, if not I know @mcollina wanted it to work like that. It may not be overly performant though (for technical reasons with bloom filters)

from what I can see the second doesn't work
haven't figured out a way to do the first either  -  what I'm going for in the first, is an empty object means is an empty pattern which means that if no other patterns match, it still matches empty

I'm pretty sure @mcollina wrote some stuff around enabling the second one, it might be in my mails, I will see if I can find it. It was actually a reasonably simple solution but it was a slight of hand. I think the first is as you say but it may be a little slow since the idea of the filter is the make the decision as quick as possible. We could use something like {default$:true} when we know the supplied lookup has no key, that would speed up the match but I don't know how I feel about it... Conflicted

@davidmarkclements CF: https://github.com/mcollina/bloomrun/blob/master/lib/deepMatch.js#L6

so .. we need to be able to add a wild card route, e.g.
var b = require('bloomrun')()
b.lookup({a: 'foo'})

I've added a bug here. Tests claim we support this, CF regexp support in the pattern But this test is faulty. It is matching due to the second k:v pair.
Both {} and {a: /.*/} are not being correctly stored in the bloom filter I think. @mcollina This may have to do with the magic implementation in the patternSet.js file.

All features landed in #32

Closed via #32


#CleanCode CreateLibraryView.vue is the brother of EditLibraryView.vue

@mai-soup To me it seems that CreateLibraryView.vue is the brother of EditLibraryView.vue, nearly identical even, and could use a component. What's your take on this? 😁

Thanks for spotting it! I noticed it a while ago with LibraryView.vue and OwnedLibraryView.vue (#41), this one's similar, just slipped my attention.


updates rqlite statefulset's cpu for gke autopilot

What this PR does / why we need it:
PR is to update the rqlite statefulset's cpu request if a gke autopilot cluster is identified.
This is done to meet autopilot's minimum cpu requirement of 500m.
Which issue(s) this PR fixes:

Fixes # SC-61237
Installing or Upgrading to kots version 1.89 or newer fails with error:
Error: failed to deploy: failed to deploy admin console: failed to ensure rqlite: failed to ensure rqlite statefulset: failed to create rqlite statefulset: admission webhook "gkepolicy.common-webhooks.networking.gke.io" denied the request: GKE Warden rejected the request because it violates one or more policies: {"[denied by autogke-pod-limit-constraints]":["workload 'kotsadm-rqlite' cpu requests '{{250 -3} {\u003cnil\u003e}  DecimalSI}' is lower than the Autopilot minimum required of '{{500 -3} {\u003cnil\u003e} 500m DecimalSI}' for using pod anti affinity.

Special notes for your reviewer:

Steps to reproduce

Upgrade kots admin-console upgrade or install kots install using the latest version of kots in a gke autopilot cluster.
Does this PR introduce a user-facing change?

NONE

Does this PR require documentation?

NONE

@garcialuis is there a LimitRange specified in a GKE autopilot cluster? I'm wondering if there's a more generic solution here....

@garcialuis is there a LimitRange specified in a GKE autopilot cluster? I'm wondering if there's a more generic solution here....

@marccampbell It must be enforced some other way, there is no LimitRange in the cluster:
$ kubectl get limitrange -A
No resources found


fix: osmo swapper balances weren't showing

Description
Osmo needs to support cross account trade
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #
Risk
NONE

Testing
Balances should show on sell asset with OSMO swapper

Engineering
same as testing

Operations
same as testing

Screenshots (if applicable)

btw @toshiSat, a change to production code is always a non-zero risk.

I figured because it's behind a feature flag it should be no risk, but I can be more thorough in that section in the future


Rias: Background image {width} and {quality} placeholders not replaced

The {width} and {quality} placeholders in ReSRC.it link are not being replaced.
This is my background image setup:

I'm using the RiAS plugin quality setting with simple support for background images (I've also tried the ls.unveilhooks.js plugin, but that didn't work either):
// LazySizes RiAS plugin config
document.addEventListener('lazyriasmodifyoptions', function(event) {
	event.detail.quality = (window.devicePixelRatio || 1) > 1.4 ? 65 : 80;
});

// LazySizes support for background images
document.addEventListener('lazybeforeunveil', function(e) {
	var bg = e.target.getAttribute('data-bg');
	if(bg) {
		e.target.style.backgroundImage = 'url(' + bg + ')';
		e.target.removeAttribute('data-bg');
	}
});

You can see a (not) working implementation here, right at the top: http://altair.studiodumbar.com
What am I doing wrong? Looks like {width} and {quality} aren't calculated/replaced for data-bg?
Thanks for your help and for this really great plugin!
Jonathan

Unfortunately the RIaS plugin only allows to work with img/picture.
Fortunately the bgset plugin does this transformation and I just changed some code in RIaS to work together with the bgset plugin.
So

update lazySizes (including its plugins)
add the bgset plugin
and use data-bgset instead of ``data-bg```

Please close if this works for you.

Great it's working with the updates, this is the output in Safari 8.0.6.:

<picture style="display: none;"><source data-srcset="http://app.resrc.it/s=w96/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 96w, http://app.resrc.it/s=w160/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 160w, http://app.resrc.it/s=w320/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 320w, http://app.resrc.it/s=w480/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 480w, http://app.resrc.it/s=w640/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 640w, http://app.resrc.it/s=w800/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 800w, http://app.resrc.it/s=w960/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 960w, http://app.resrc.it/s=w1280/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1280w, http://app.resrc.it/s=w1600/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1600w, http://app.resrc.it/s=w1920/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1920w, http://app.resrc.it/s=w2240/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2240w, http://app.resrc.it/s=w2560/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2560w, http://app.resrc.it/s=w2880/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2880w" sizes="1278px" srcset="http://app.resrc.it/s=w96/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 96w, http://app.resrc.it/s=w160/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 160w, http://app.resrc.it/s=w320/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 320w, http://app.resrc.it/s=w480/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 480w, http://app.resrc.it/s=w640/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 640w, http://app.resrc.it/s=w800/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 800w, http://app.resrc.it/s=w960/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 960w, http://app.resrc.it/s=w1280/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1280w, http://app.resrc.it/s=w1600/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1600w, http://app.resrc.it/s=w1920/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 1920w, http://app.resrc.it/s=w2240/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2240w, http://app.resrc.it/s=w2560/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2560w, http://app.resrc.it/s=w2880/o=65/http://altair.studiodumbar.com/thumbs/cover-01-8cf8e463ff29bb83468bcd9b417471ab.jpg 2880w"></picture>

Link: http://altair.studiodumbar.com
Though the initial data-bgset with the placeholder {width} and {quality parameters is stil present in there. Is that on purpose? Necessary? Can it be removed after background image is lazyloaded? Except for this it's working perfectly (at least in latest Safari and Chrome on Mac).
Thanks!

Yes, it is on purpose. But it is not necessary. If you want you can remove it after a lazybeforeunveil event. But this is just cosmetics, you won't get anything from it.


On Using FMIX my dataloader is unable to mix the data in training loop

I have used the following training loop for my plant image dataset
def train_loop_fn(data_loader, model, optimizer, device, scheduler=None):
    running_loss = 0.0
    running_corrects = 0

    model.train()

    alpha, decay_power = 1.0, 3.0

    for batch_index,dataset in enumerate(data_loader):
        image = dataset["image"]
        label = dataset["label"]

        image = image.to(device, dtype=torch.float)
        label = label.to(device, dtype=torch.float)

        image, perm, lambda_value = sample_and_apply(image, alpha, decay_power, (224, 224))
        optimizer.zero_grad()

        outputs = model(image)

        loss = loss_fn(outputs, label) * lambda_value + loss_fn(outputs, label[perm]) * (1 - lambda_value)

        loss.backward()
        xm.optimizer_step(optimizer)

        running_loss += loss.item()

    scheduler.step()

    train_loss = running_loss / float(len(train_dataset))

    xm.master_print('training Loss: {:.4f} '.format(train_loss))

and my dataset class look like this
import cv2
import torch
from torchvision import transforms
import albumentations
from PIL import Image

class leaf_classification(Dataset):
    def __init__(self, ids, image_id, label, mean , std , is_valid):
        self.ids = ids
        self.image_id = image_id
        self.label = label
        self.is_valid = is_valid
        if self.is_valid == 1: # transforms for validation images
            self.aug = albumentations.Compose([
               albumentations.Normalize(mean , std , always_apply = True)
            ])
        else:                  # transfoms for training images
            self.aug = albumentations.Compose([
                albumentations.Normalize(mean , std , always_apply = True),
                albumentations.ShiftScaleRotate(shift_limit = 0.0625,
                                                scale_limit = 0.1 ,
                                                rotate_limit = 5,
                                                p = 0.9)
            ])

    def __len__(self):
        return len(self.ids)

    def __getitem__(self, index):
        # converting jpg format of images to numpy array
        img = np.array(Image.open('../input/cassava-leaf-disease-classification/train_images/' + self.image_id[index]))

        img = cv2.resize(img, dsize=(224, 224), interpolation=cv2.INTER_CUBIC)
        img = self.aug(image = img)['image']
        img = np.transpose(img , (2,0,1)).astype(np.float32) # 2,0,1 because pytorch excepts image channel first then dimension of image

        return {
            'image' : torch.tensor(img, dtype = torch.float) ,
            'label' : torch.tensor(self.label[index], dtype = torch.float)
        }

And its generating the error
while training it generating this error

please help me in resolving this error . Here's the link to my notebook

Hi, looks like you're on the right lines. I've created a copy of your notebook and made a few changes here: https://www.kaggle.com/ethanwharris/fmix-cassava-leaf-disease-classification
Changes made

used from FMix.fmix import ... instead of cd FMix (which cause the file error as after the cd everything was one level lower)
used sample_mask instead of sample_and_apply which used a mask from numpy and didn't seem to work with the XLA device
moved model.to(device) as the torchsummary package was moving the model to CPU
added train_loss to the scheduler.step call (although this should probably be a val loss)

There are still some errors in eval_loop_fn but these aren't related to FMix
Hope that helps!

Thanks brother , really appreciate your work as well as your help as it started working after I made the necessary changes . But I just wanna know am I going wrong with regards to your point number 4 ?

Hello Ethan ,
I am again started facing error for this line x1, x2 = image * mask, image[perm] * (1 - mask)
getting this error

in the function
defining the training loop
def train_loop_fn(data_loader, model, optimizer, device, scheduler=None):
    running_loss = 0.0
    running_corrects = 0

    model.train()

    alpha, decay_power = 1.0, 3.0

    for batch_index,dataset in enumerate(data_loader):
        image = dataset["image"]
        label = dataset["label"]

        lambda_value, mask = sample_mask(alpha, decay_power, (224, 224), 0.0, False)
        mask = torch.from_numpy(mask).to(device)
        perm = torch.randperm(image.size(0))

        x1, x2 = image * mask, image[perm] * (1 - mask)
        image = x1 + x2

        image = image.to(device, dtype=torch.float)
        label = label.to(device, dtype=torch.float)

        optimizer.zero_grad()

        outputs = model(image)

        loss = loss_fn(outputs, label) * lambda_value + loss_fn(outputs, label[perm]) * (1 - lambda_value)
#         loss = loss_fn(outputs, label)

        loss.backward()
        xm.optimizer_step(optimizer)

        running_loss += loss.item()

    train_loss = running_loss / float(len(train_data))
    scheduler.step(train_loss)

    return train_loss

don't konw why it was working fine earlier.
Notebook link

Hi, sorry I missed this.
Not sure what the error was here, it looks like the tensors are the wrong sizes. So might need to squeeze / unsqueeze in places to get it to work. Closing this issue as it looks like it's not a bug in our code.

Hi, sorry I missed this.
Not sure what the error was here, it looks like the tensors are the wrong sizes. So might need to squeeze / unsqueeze in places to get it to work. Closing this issue as it looks like it's not a bug in our code.


Additional properties true or false?

Do we allow the schema to be extended or is data per this schema locked to this, and only this.
If extensions are not allowed we should set additionalProperties to false.

As I understand it additionalProperties=false should be added. Right @gabywh ?

Discussed already with Semantic SG. My position: Postel's law. If there is more data in any JSON document then we simply ignore it. Applying additionalProperties=false would violate this so I removed it consistently.

@gabywh Yes, but in that case "minimum data set" equals "maximum data set" doesn't hold anymore.

Perhaps we should set additionalProperties=True where we allow it to be explicit?

@martin-lindstrom yes, I know.
Let me perhaps phrase it differently and somewhat more verbosely:
So the general approach started out with being very strict and enforcing "to the max" all the constraints we could possibly apply. 3 reasons for that (1) to catch outliers in the data and force at that point implementers to "clean up their (data) act" if they need to, and (2) to demonstrate clear compliance to both the EU proposed legislation as well as the eHealthNetwork documentation, (3) last and definitely not least: to help implementers in generating very clean and tight code, direct from spec and thus allow good interoperablility (Rose's Law, we'll come to Postel's law in a minute...) since the specification would leave very little - if any - room for manoeuvre (which is the bane of most developer's lives when having to deal with medical data in the first place).
However, the general approach has now shifted to one of being far more relaxed about all kinds of constraints (Postel's law) and accepting pretty much most things providing we can make some kind of sense of them (discussion on-going e.g. about the person name parts and what is mandatory and what is not).
My own personal opinion: in this case, I think applying Postel's law here makes for a very sloppy spec and whilst I in general agree with Postel's law for interoperability of already-existing systems, I think Rose's law makes a very valid point that applying Postel's law without constraint leads to very sloppy systems -> entropy, if you so will.  So I would prefer a much tighter, cleaner JSON schema here -> including additionalProperties=False. However, it is not about my own personal opinion but what is generally required and whilst mu opinion may differ on a personal level, I still aim to follow the overall approach. This entails having a generally consistent approach throughout, which I think only helps (having a mix of strict and lax approaches at seemingly arbitrary points just leads to confusion). So that general approach is de-constraining the constraints, again without going so far as to say "everything is a string", which is too extreme. I hope to have found a balance here in that approach -> and that entailed for me removing any additionalProperties=false constraints.
@jschlyter I do like your suggestion of at least being explicit about intentions: in general, good programming practice. Yet JSON itself is designed to have  lot of implicits and be flexible rather than constraining (although I do find comments not supported in JSON in general to be rather irritating, but again that's a personal opinion ;). For JSON schema additionalProperties=True is "on" by default in any case, does being explicit here actually help or just add more parsing (also human parsing ;) "noise"? If we state additonalProperties=True then it would imply we set in other places additionalProperties=False elsewhere, at least that would be my expectation as a developer. If we allow the default of additionalProperties=True everywhere (as in the general, less-constraining approach), then there would be no need to specify it at all.
So in summary: yes, I did think about it, quite a bit in fact ;)

So how do we proceed? True/False/undef

well it can never be undef -> is by default defined to be True
but I get what you mean: not explicitly defining it ;)
How to proceed? Leave as-is

As say. Leave it "as is", with no mentioning of additionalProperties. In this way we don't explicitly invite for extensions, but does not actively prevent it either.

I say: Leave it "as is". In that way we don't explicitly invite for extensions, but do not actively prevent it either. A compromise.


Update troubleshooting-nextgen.md

https://harness.atlassian.net/browse/CDS-75313
will add another pr to add it to the CG section
(better to do 1 action per pr)
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Add a guide for monitoring jobs

A how to guide to introduce Cuetopia, adding views, and monitoring jobs for a show.

Fixed in https://github.com/imageworks/opencue.io/pull/21


[impl] port of the WPF example to WinUI

Hey. I just checked and it works fine for me (Loaded-Event fires). I'm also new to WinUi, but were able to easily port some smaller WPF apps. There is nothing much on the Window class, you'd expect from a WPF window. Most events have to be used from Pages or FrameworkElements.
I followed the approach from here: https://docs.microsoft.com/en-us/windows/apps/winui/winui3/create-your-first-winui3-app
Just had the appropriate workload from VS Installer and the basic templates installed.
I'm currently on VS v17.2.3 (guess you are on the 17.3 preview for the MAUI stuff!?).

Had to submit a new PR #388 to correct some issues found when working on this with the WinUI3 team.  Thanks for doing the work here - it was a great help!


Add Ohm Language

Adding an Ohm language for .ohm extension. Expected to only occur once per repo.
Description
Ohm is a parsing toolkit consisting of a library and a domain-specific language. One can use it to parse custom file formats or quickly build parsers, interpreters, and compilers for programming languages.
 The Ohm library provides a JavaScript interface for creating parsers, interpreters, and more from the grammars you write.
Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com. As this language is used for making parsers, and interpreter/compiler frontends, it's extension is expected to occur only once per repository (except for the repositories in ohmjs organization):

Search results for each extension:

Not forks (~440 files)
Not forks, excluding ohmjs organization (~380 files)

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

ohm-grammar.ohm is adapted from it's version in ohmjs/ohm

Sample license(s): MIT License

[x] I have included a syntax highlighting grammar: novusnota/vscode-ohm
[x] I have added a color

Hex value: #A469F8
Rationale: Most used on the language website, primary color.

[ ] I have updated the heuristics to distinguish my language from others using the same extension. No other language has the same extension, so I didn't update heuristics.

For what it's worth, here's a complete and well-tested tree-sitter grammar for Ohm, which may be used by the relevant GitHub team to supersede TextMate grammar from this PR once or if it gets merged :)

Cabe mencionar qué es el individuo el que genera la aplicación de ese tal
rama si no ya lo hubieras hecho tú o sea que es claro que me necesita y si
no se queda hasta ahí además esperemos en la nueva era que esto se termine
con tranquilidad y paz
El jue., 29 de febrero de 2024 12:20 p. m., Novus Nota <
@.***> escribió:

For what it's worth, here's a complete and well-tested tree-sitter
grammar for Ohm https://github.com/novusnota/tree-sitter-ohm, which may
be used by the relevant GitHub team to supersede TextMate grammar from this
PR once or if it gets merged :)
—
Reply to this email directly, view it on GitHub
https://github.com/github-linguist/linguist/pull/6693#issuecomment-1971702024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGBR7ZN3SCJKRPWWBQHHMMDYV5YP5AVCNFSM6AAAAABCSCTPL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZRG4YDEMBSGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Converted to draft to enhance and/or re-write the grammar :)


IRQ on CYW43_PIN_WL_HOST_WAKE not gpio13

fixes #1068 where the raw irq handler that was added masked on IO_IRQ_BANK0 (defined as 13) and not the gpio connected to the CYW43 i.e.  CYW43_PIN_WL_HOST_WAKE

Is a similar change also needed on line 212 ?

Also similar problems in https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_poll.c#L62 and https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_freertos.c#L141 ?

Also similar problems in https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_poll.c#L62 and https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_freertos.c#L141 ?

Yes - looks like the same mistake.

Also similar problems in https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_poll.c#L62 and https://github.com/raspberrypi/pico-sdk/blob/develop/src/rp2_common/pico_cyw43_arch/cyw43_arch_freertos.c#L141 ?

Yes - looks like the same mistake.

Yep -- I'll try and fix/test the others too later this week unless someone else gets in before me!

last week was too busy with work -- doing this now.


I want to know the meaning of 'sensor2lidar', 'camera2lidar' parameter

Now, i develop this repo to fit on real-time ROS2 detection. In this process, I have one question about 'sensor2lidar' parameter.
I'm using the 'yaml' file as a parameter file instead of 'pkl'. I copy the content related with calibration of 'pkl' and paste it to 'yaml'. And it is working well still. But as you know, this 'camera2lidar' value is related with 'sensor2lidar' and this value is related with 'ego coordinate'. I want to get external calibration parameter of 'camera' and 'lidar' directly without any information of ego and put in my own 'yaml' file.
So, I guess 'camera2lidar' is defining 'camera' rotation and translation based on 'lidar coordinate system' . I want to know this understanding is correct or not.

Thank you for your interest in our project. This repository is no longer actively maintained, so we will be closing this issue. Please refer to the amazing implementation at MMDetection3D. Thank you again!


Add support for SNO (Single Node)

Please add SNO support, cluster.yaml:
compute_count: 0
master_count: 1

Bootstrap in place wont work, because in place bootstrap might work only if you boot from iso and not direct into qcow2.

Installation still work-in-progress, but looks not so bad:
$ cat cluster-sno.yaml
cluster_name: sno
sdn_plugin_name: OVNKubernetes
vn_subnet: "<IP_ADDRESS>"

openshift_mirror: "https://mirror.openshift.com"

openshift_version: 4.8.0-fc.7
openshift_location: "{{ openshift_mirror }}/pub/openshift-v4/clients/ocp-dev-preview/{{openshift_client_version}}"

coreos_version: 4.8.0-fc.7
coreos_download_url: "{{ openshift_mirror }}/pub/openshift-v4/dependencies/rhcos/pre-release/{{ coreos_version }}/rhcos-{{coreos_version}}-x86_64-qemu.x86_64.qcow2.gz"
coreos_csum_url: "{{ openshift_mirror }}/pub/openshift-v4/dependencies/rhcos/pre-release/{{ coreos_version }}/sha256sum.txt"

#post_install_add_ons:
#  - name: 'ntp'
#    tasks_from: 'post-install.yml'

compute_count: 0
master_count: 1
$ oc get etcd/cluster -o yaml | grep -C5 single
kind: Etcd
metadata:
  annotations:
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    release.openshift.io/create-only: "true"
  creationTimestamp: "2021-06-07T18:40:26Z"
  generation: 1
  name: cluster
  resourceVersion: "19598"
$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version             False       True          23m     Unable to apply 4.8.0-fc.7: the cluster operator monitoring has not yet successfully rolled out

Installation done, works fine. So SNO works very well with simple cluster.yml settings:
compute_count: 0
master_count: 1

Everything is documented in devel branch, will be merged into master with PR #183


Temp directory in memory

Is your feature request related to a problem ?
With a small enough refresh interval for the source and kustomize controller they can create a lot of disk I/O on a system.
In our case it is just too much, the kustomize pod constantly uses 200% CPU and creates a lot of writes to the underlying file system.
Unfortunately there is no possibility to change the volume mount for /tmp. It is just a simply emptyDir volume.
https://github.com/fluxcd-community/helm-charts/blob/main/charts/flux2/templates/kustomize-controller.yaml#L134
Describe the solution you'd like.
My solution would be to add additional parameters for emptyDir or somehow using .Values.kustomizeController.volumes to override the temp volume.
The first idea would be the easiest one I guess:
      ...
      volumes:
      - name: temp
        emptyDir:
          {{ .Values.kustomizeController.tempOptions | toYaml | nindent 10 }}
      ...

Then there should be a default for that in values.yaml:
kustomizeController:
  tempOptions: {}

Which can be overridden like this:
kustomizeController:
  tempOptions:
    medium: Memory
    sizeLimit: 128Mi

Describe alternatives you've considered.
NONE
Additional context.
No response

@stefanprodan Thanks for your answer.
Good point indeed. Since this is a development environment I am talking about there are a lot of changes all the time, and because of that we thought it would be a good idea to make the interval on every Flux resource very small.
Apparently we did not read the documentation well enough to find out that the Kustomization interval is only for checking drifts and manual edits.
So just one final question for you from my side:
Am I right with the assumption that a small refresh interval for GitRepo is fine and it only pulls new changes if the commit hash of the given branch has changed? So basically there is no downside regarding too much disk I/O on the source controller side with git repositories?
And if there was a change in a git repository it automatically triggers the Kustomization controller anyway?
If all these questions can be answered with "Yes", then I guess we can close this ticket.

Am I right with the assumption that a small refresh interval for GitRepo is fine and it only pulls new changes if the commit hash of the given branch has changed?

Yes, what we've implemented in source-controller is the equivalent of git-ls-remote. We write to disk, only if the remote HEAD commit is different from what we have previously pulled in the cluster.

And if there was a change in a git repository it automatically triggers the Kustomization controller anyway?

Yes, all Flux controllers are event-based, if a source revision changes, an event is issued and no matter the interval, the changes get reconciled immediately.

Thanks a lot!
I guess this knowledge will make this ticket obsolete. Closing it right now.


Some spaces are extracted as dots

Attach (recommended) or Link to PDF file here:
Erudition_HSUHK-e-newsletter_May-2021.pdf
Configuration:

Web browser and its version: chrome 91
Operating system and its version: MacOS 10.14
PDF.js version: 2.7.570
Is a browser extension: no

Steps to reproduce the problem:

open attached PDF file
find link https://rb.gy/lmwemz
copy a few lines around it and past them to the notepad

What is the expected behavior? (add screenshot)
The spaces should be extracted as spaces:

What went wrong? (add screenshot)
When doing copy/paste some spaces are copied as dots:
The.University.would.like.to.seek.your.help.in.inviting.more.alumni.to.reconnect.with.us..If.you.happen.to.know.of.any.alumni.via.your.network,.please.pass.on.this.link.(https://rb.gy/lmwemz).so.that.we.can.keep.them.abreast.of.the.latest.news.and.developments.of.their.alma.mater.恒大一直重視與校友的聯繫，我們祈盼您能協助聯絡身邊的恒大校友，讓他們也能緊貼母校的最新資訊及發展。歡迎分享此連結（https://rb.gy/lmwemz），讓更多校友與母校保持聯繫。 Graduates of the School of Translation and Foreign Languages take a group photo with the faculty members. 翻譯及外語學院畢業生與教職員合照留念
The same issue occurs when parsing PDF file with pdfjs-dist library (Node.js v14):
const pdfjsLib = require('pdfjs-dist/es5/build/pdf.js');
let doc = await pdfjsLib.getDocument({data: filebuffer, nativeImageDecoderSupport: pdfjsLib.NativeImageDecoding && pdfjsLib.NativeImageDecoding.DISPLAY, disableFontFace: true, verbosity: 0}).promise;
let page = await doc.getPage(i);
let content = await page.getTextContent();
let text = content.items.map(itm => itm.str).join(' ');

Duplicate of #12237

@Snuffleupagus :

this file doesn't have /ActualText tags
when this file is opened in Chrome browser PDF viewer the text around the https://rb.gy/lmwemz link is copied correct. The issue exists with MacOS viewer and with pdfjs-dist library.

this file doesn't have /ActualText tags

Yes, it most certainly does:

It most certainly does:

It is strange. I don't see it in:
let doc = await pdfjsLib.getDocument({data: dataObject.buffer, disableFontFace:true, verbosity:0}).promise;
let pdfstr = (await doc.getData()).toString();

The pdf contains sequences like the following:
BT /Span <</ActualText (þÿ\0 )>>BDC  8 0 0 8 75.1664 356.8281 Tm <0001>Tj EMC  ET

The ActualText entry contains a white space but here we use the char drawn in the Tj instruction to put in the text layer.
So it's definitely a duplicate of #12237.
You can use qpdf to uncompress streams and have a look to the pdf in a text editor to see all the ActualText by yourself.

You can use qpdf to uncompress streams

I'll check it. Thank you.


Create a Docker Container for easy installation and exploration

Create a Docker Container for easy installation and exploration. The container would have a pre-built installation of the Delta Sharing server as well as Postgresql. Configuration would be by specifying environment variables in a docker-compose.yaml file.

Is this being worked on already? I have finished an experiment with the delta-sharing server from delta.io but the API for changing/adding shares looks good to me. So I want to start experimenting with this.
Never used rust but did my fare share of docker so glad to help out if needed.
I do think we only need to incorporate the sharing-server in the docker and make sure the postgres db is inside it's own docker image and make sure we connect them through an example docker-compose file.
Let me know if there is already work i can continue with or if I can start from scratch. Don't want to do unnecessary work but happy to help out.


Error when trying to animate reveal

I followed this tutorial and when I run the app, I get the following error referring to CircularReveal library.

Could not find method android.view.ViewAnimationUtils.createCircularReveal, referenced from method io.codetail.animation.ViewAnimationUtils.createCircularReveal

Could not find method android.view.ViewAnimationUtils.createCircularReveal, referenced from method io.codetail.animation.ViewAnimationUtils.createCircularReveal
me too

Disable thw hardware acceleration on your Activity or Application in manifests:
android:hardwareAccelerated="false"

Same issue here


React native issues with npm

Is this a bug report?
yes
Environment

react-native -v:
react-native-cli: 2.0.1
react-native: 0.45.1
node -v: v8.0.0
npm -v: 5.0.4
yarn --version (if you use Yarn): 0.24.5

Then, specify:

Target Platform (e.g. iOS, Android): Android
Development Operating System (e.g. macOS Sierra, Windows 10): Linux
Build tools (Xcode or Android Studio version, iOS or Android SDK version, if relevant): Android SDK 23

Steps to Reproduce

create-react-native-app AwesomeProject
cd AwesomeProject
npm start

Expected Behavior
Expected to  start a development server for you, and print a QR code in your terminal.
Actual Behavior
Got these errors (attaching the log)
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/divyam/summerProjects/AwesomeProject/node_modules/.bin:/home/divyam/nitHack/google-cloud-sdk/bin:/home/divyam/.rbenv/shims:/home/divyam/.rbenv/bin:/home/divyam/.rbenv/shims:/home/divyam/.rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/divyam/Android/android-sdk/platform-tools
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/divyam/summerProjects/AwesomeProject
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'react-native-scripts start' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: `react-native-scripts start`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:283:16)
14 verbose stack     at emitTwo (events.js:125:13)
14 verbose stack     at EventEmitter.emit (events.js:213:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:125:13)
14 verbose stack     at ChildProcess.emit (events.js:213:7)
14 verbose stack     at maybeClose (internal/child_process.js:887:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/divyam/summerProjects/AwesomeProject
17 verbose Linux 4.11.3-1-ARCH
18 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
19 verbose node v8.0.0
20 verbose npm  v5.0.4
21 error code ELIFECYCLE
22 error errno 1
23 error<EMAIL_ADDRESS>start: `react-native-scripts start`
23 error Exit status 1
24 error Failed at the<EMAIL_ADDRESS>start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

Hi,
I think it's was probably best to write in the create-react-native-app repo.
However I have tried in my development environment and I work.
MacOS
node -v v7.9.0
npm -v 4.2.0
react-native-cli: 2.0.1
react-native: 0.45.1
I found this: https://github.com/react-community/create-react-native-app/issues/233
It may be that it is not compatible with Node > 8.0 and/or npm > 5.0.1

yes, it's similar. Probably npm > 5.0.0 as react-community/create-react-native-app#233 has 5.0.1 probably.

Try using npm 4. Agree that this is best opened in the CRNA repo.


dots-circle-vertical

heroicons.com has dots-circle-horizontal but not dots-circle-vertical
I just noticed when I went to see if vertical looked better.
Tilting my head, I do like horizontal better. Just adding incase it was overlooked.

this?
`
<svg
class="w-6 h-6"
fill="currentColor"
viewBox="0 0 20 20"
xmlns="http://www.w3.org/2000/svg"

`

@ArielOnoriaga yup!


Feature Request: disable-next-line

Hello, and thanks for the excellent linter!
Currently, markdownlint has the disable-next-line directive, which is quite a handy feature!
For example, the README.md file gives the following example:
<!-- markdownlint-disable-next-line no-space-in-emphasis -->
deliberate space * in * emphasis

Unfortunately, this not the greatest example, because if you have Prettier installed (which many projects do nowadays), as soon as you hit Ctrl + s in VSCode to save the file, Prettier will automatically reformat it to the following:
<!-- markdownlint-disable-next-line no-space-in-emphasis -->

deliberate space * in * emphasis

And now the comment will no longer apply.
This happened to me earlier today. Being familiar with ESLint, I intuitively knew how to fix the problem, so I tried this:
deliberate space * in * emphasis <!-- markdownlint-disable-line no-space-in-emphasis -->

But unfortunately, that doesn't work, because surprisingly, markdownlint only supports disable-next-line and not disable-line.
Can this please be added?

You can do this with disable/restore as shown in the documentation: https://github.com/DavidAnson/markdownlint#configuration

@DavidAnson Thanks for the quick response.
I see in the docs that it is possible to do disable/restore, but this is pretty cumbersome.
It also is not very DRY - programmers will have to duplicate the code on multiple lines.
It would be better UX and less maintenance for end-users if this linter could also have the disable-line feature, which would allow programmers to specify the directive and associated rule exactly one time.

In my opinion, "next line" is better than "line" because it is clear, it doesn't interfere with the content, and it doesn't risk creating too-long lines. The problem is that Prettier breaks that and needs to be worked around. It would be nice if Prettier were more respectful here, but I can look into adding "line" as an alternative.

I know of just one other Markdown linting tool in the Node ecosystem. I think they could handle it if they wanted to. :)

Well, what about CSpell? Surely, many people need to spell check their markdown documents. If you're not familiar with it, it has syntax like this:
It is common to misspell the word absence as "absense". <!-- cspell:disable-line absense -->

That would have to be added as well. And what if some other extension for spell checking started to get more popular than CSpell or markdownlint? Should that be added too?
It seems pretty weird for Prettier to be in the business of hard-coding popular tools, as that would be a maintenance burden, especially for a hypothetical niche feature like this.


Encrypt your code climate token

This repository contains a code climate token in .travis.yml.
Please see e.g. this description on how to encrypt it.
https://coderwall.com/p/5mtq6q/encrypt-your-code-climate-repo-token-for-public-repositories-on-travis-ci
While doing so, it might be wise to revoke it and create a new one.

Thanks! Done. 👌


Add PyPI username and password in Travis.yml

@lewismc Please add your username and password (encrypted) to .travis.yml file.
You'll need travis cli installed (instructions here)
Encrypted password can be generated using travis encrypt 'plain-text-password'

@jarifibrahim username and password for Pypi?

@lewismc yes, please take a look at this for reference.

Done, please see .travis.yml


make rust error messages more explicit

Closes #1992

#1993  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite


Location lat long coversion from DMS to Decimals

Use LatLon to allow conversions between degree minutes seconds to degree decimals?
https://pypi.python.org/pypi/LatLon/1.0.2
Other packages to do this?

There are functions for this in utils.py


Issue retrieving data from AF or Pi Points

Hello,
First off thanks for the work on this plugin.
I'm trying to connect to our AF database via the piwebapi. I'm able to see the tag elements/attributes populate via AF, and the Pi Points tag names all populate properly, but when I select one, I only ever get No Data returned by the query.
If I query via Postman/browser I'm able to get data, but not using the plugin.
Grafana version = 9.3
PiWebAPI 2018 SP3
I was wondering if I have to upgrade to PiWebAPI 2021 or downgrade Grafana. Or if perhaps there's a good way to debug the values for the PI/AF Connection Details.
Thanks,
Jon

Click on Inspect->Query and look at the query being done to the PiWebAPI. This will help debugging.

Thanks coderReview. A little trial and error with the query inspector and it turned out to be the PiWebAPI version. If it helps anyone else, upgraded to 2021 SP3 and the plugin worked just fine.
Looks like PiWebAPI changed syntax from 2018 to 2021.


Wrap rec.time in a Date object before calling toISOString

rec.time is already an ISO formatted string for me, so I'd get errors otherwise. Wrapping a Date object in new Date() returns a clone of the same date object, so this doesn't break the case where rec.time is a Date

should not harm. thanks @bioball


Include homebrew release

In order to consume hammer updates from the mac packagemanager homebrew, it'd be nifty if hammer published a consumable homebrew repo as part of the goreleaser process.
pivotal-cf/om does a similar thing
thanks for considering it; feel free to close whenever 👍

Good suggestion, thanks! I hadn't realised it was relatively nicely built into goreleaser.

Added homebrew releasing and released v0.6.0 which can be installed with:
brew tap pivotal/hammer https://github.com/pivotal/hammer
brew install hammer

Again thanks for the suggestion, feel free to re-open this if there is anything else related.


Add register event for guest customer

1. Why is this change necessary?
When you subscribe the CustomerRegisterEvent you don't get notified when it is a guest. The really good way to check if there is a guest registration you need to subscribe the DAL events for customer insertions. This sort of makes sense as a guest is not registered but in the end the person has a customer entry so they are still in the system and were entried via the registration form. You still miss it when you subscribe the normal event.
2. What does this change do, exactly?
As it would be a breaking change as the existing event CustomerRegisterEvent would be triggered more often and thus send more emails I add a new event that gets dispatched instead. It extends the existing event so the same event handler can be used and just have to be subscribed twice.
3. Describe each step to reproduce the issue or behaviour.

Subscribe CustomerRegisterEvent to transfer customer data to CRM
Order as guest
Look into CRM and don't have a new contact

4. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-9258
Please use this issue to track the state of your pull request.

Thank you for merging 💜 💙

thank you for your contribution @JoshuaBehrens 👍🎉💙


Main map purple tracks have stopped processing again

Tracks have finished processing, points have been assigned, but the purple tracks do not appear to have shown up on the main map.

Please provide relevant URL to help us view

https://kartaview.org/map/@37.25342214249055,-122.05223958928786,12z
Map View
https://kartaview.org/details/4550921/0/track-info
Track

Worth noting it seems that it gave 10 points for every photo so it does not appear to have processed correctly

All uploaded tracks regardless of platform seem to be giving 10 points per image and not processing for the main map

@joeybab3  fixed it, could you please check again?

i will close this issue. you can reopen this if you have any question . Thanks for your feed back.


Use backticks to distinguish code from prose in Doxygen documentation

In a number of recent issues we've made a point to update the Doxygen documentation to use backticks around things like std::null opt or references to other SFML APIs to ensure that C++ constructors are differentiated from prose. I'm opening this issue to make a note to ourselves that we ought to audit the codebase to find more places where this pattern can be employed.
Here's a before and after to illustrate how this change improves the readability of the docs. The effect is subtle but useful and requires minimum changes to our code. Note how the style of std::nullopt has changed.

In particular this needs to happen in the documentation for public APIs. I'm much less concerned about the cleanliness/hygiene/uniformity of private APIs. We don't even run Doxygen on those private APIs.

One open question is/was whether we should backtick-ify the SFML types as well. As such this issue is kept open.

I started looking into whether we do this for SFML types and realized it will be a pretty big PR to make such a change. We can do it but there are a lot of places where our docs refer to other SFML types. I do think the monospaced symbol name looks better though.


[trivial] Test std.algorithm.sort with unpredictable data

Using Random(1) yields the same data for uniform each time. Instead, let uniform default to rndGen, which is unpredictable.
(https://dlang.org/phobos/std_random.html#.uniform)

👍

I disagree with this type of change. Random numbers have traditionally caused havoc with unit tests, because a change can get merged that is incorrect (i.e. not caught with the random numbers that happened to be selected), but then caught at random by other PRs, sometimes very infrequently.
If you wish to do random testing, generate the random data (or seeds) and then hard-code them in. We don't want non-repeatable failures.

The failures could be repeatable if the initial state (before the first use of uniform) of rndGen is printed in case of error.

I disagree with this type of change. Random numbers have traditionally caused havoc with unit tests, because a change can get merged that is incorrect (i.e. not caught with the random numbers that happened to be selected), but then caught at random by other PRs, sometimes very infrequently.
If you wish to do random testing, generate the random data (or seeds) and then hard-code them in. We don't want non-repeatable failures.

I highly agree with you - randomness in tests should always be seeded and in fact I recommend to specify the random engine too.
import std.random : Mt19937;
auto gen = Mt19937(42);

@schveiguy:

a change can get merged that is incorrect [...], but then caught at random by other PRs, sometimes very infrequently. If you wish to do random testing, generate the random data (or seeds) and then hard-code them in.

If only very infrequent randomly generated data trigger the bug, then we won't find those bugs with hardcoded tests. The point of unit tests is to find bugs. Everything else (other than performance) seems much less important.
Also, I marked this trivial because the other tests I saw all used unpredictableSeed, I didn't notice any hard-coded tests.
I agree with ZombineDev about printing debugging info in the case of failure for reproducibility.

Unit tests are for verifying code works as expected when given predetermined data. Imo no true randomness should be in unit tests.

If only very infrequent randomly generated data trigger the bug, then we won't find those bugs with hardcoded tests. The point of unit tests is to find bugs. Everything else (other than performance) seems much less important.

Yep but you want to know what you are testing & don't want a random failure ;-)

Also, I marked this trivial because the other tests I saw all used unpredictableSeed, I didn't notice any hard-coded tests.

Then go ahead & fix them ;-)
Pinging two other random experts @9il @joseph-wakeling-sociomantic

Unit tests are for verifying code works as expected when given predetermined data. Imo no true randomness should be in unit tests.

Agreed

Yea, I think we need to distinguish unittests from (say) stress-tests or tests of quality-of-randomness, which should probably be done by some other kind of testing utility.

Phobos will be more buggy without random tests.

Phobos will be more buggy without random tests.

Phobos will be neither more or less buggy with unit tests. I'm being pedantic, but tests do not create or fix bugs, they only test for them. Will random unit tests find more bugs? If there are zero bugs that pertain to the random tests, then no.
It's surely possible that there is a bug in Phobos that some day random unit tests will uncover. There's a good chance that the bug is ignored (WTF, this has nothing to do with my PR?) or lost in the noise.
A much better possibility is that someone using Phobos some day finds a bug, files an issue in bugzilla with repeatable data, and then we fix the bug and the specific unit test.


Issue with some open results not coming in the visualization page

Some of the open results are not coming on the visualization page

Fixed now by adding pagination.


Create template blend file for intersections

Since we are going to start off with hand-crafted intersections before getting to generated ones, we should be sure to create a blend file template that matches what a user would use in-editor, to make it easier to create your own variations.
This should include a template object which acts like the forward/reverse sizing, but this of course should itself not be made visible.
The blend file template should be checked in as an LFS object into a demo or templates folder.

This task likely won't be necessary as-written anymore, as the hope is to show off a workflow whereby users can export a scene glTF file including all meshes as a starting point. If we can managed to just create even a single edge loop for each roadpoint in mesh form, it would make it much more feasible for someone to then create the rest of the model themselves.

Re-defining this task as creating a text tutorial on how to create custom road meshes, which is already possible. This will also be the guide to follow for intersections.

Created the basis of the tutorial here, although I'd like to create actual visuals to go along with it:
https://github.com/TheDuckCow/godot-road-generator/wiki/User-guide:-Custom-road-meshes

Will close this and work on the release since this can be edited out of line of the actual release.


Replace default Android storage engine to support JSON docs > 2Meg

The default android storage engine, that wraps SQLite has a CursorWindow class that limits content of a single row to 2MBytes. This results in errors for large JSON documents.
CursorWindow is specific to the Android storage engine framework, the issue is not seen on iOS or Portable Java.
Need a strategy for replacing the default Android storage engine to fix this.

Is it possible to access the embedded android SQLite directly via our own storage engine, can we cope with different SQLite versions on different devices?

Provide an optional external SQLite native library (i.e. from Portable Java) with our own storage engine. Can we cover all Android target architectures (ARM/Intel?) using a custom build.

hi @tleyden do you know if the ForestDB team tried LevelDB  https://github.com/google/leveldb  and why that wasn't the choice for replacing the storage engine on mobile? https://issues.couchbase.com/issues/?jql=text ~ "LevelDB"
context: we just hit an SQLite error in Android 5.0 which was fixed in cblite so we are trying to decide what would be the best upgrade plan for our old touchdb app (we haven't tried couchbase yet, we are still using couchdb with REST bolted on for image upload)

The idea behind forestdb is to build something more performant than leveldb or the other kvstores available.
Here are the published benchmarks

we haven't tried couchbase yet, we are still using couchdb with REST bolted on for image upload

cblite should still be compatible with couchdb -- although if you search the issue tracker for "couchdb" you might find some outstanding issues.  It's not in our release test matrix, so is more likely to have issues than couchbase server + sync gw.

We're going to be providing an optional, custom SQLite binary as part of our upcoming 1.2 release which should resolve this issue.

Notes for testing:

Inserting document does not have issue with the doc size > 2MB.
Reading document which size is larger than 2MB causes this issue.

java.lang.IllegalStateException: Couldn't read row 0, col 0 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.
at android.database.CursorWindow.nativeGetString(Native Method)
at android.database.CursorWindow.getString(CursorWindow.java:434)
at android.database.AbstractWindowedCursor.getString(AbstractWindowedCursor.java:51)
at com.couchbase.lite.android.SQLiteCursorWrapper.getString(SQLiteCursorWrapper.java:27)
at com.couchbase.lite.store.SQLiteStore.getDocument(SQLiteStore.java:692)
at com.couchbase.lite.Database.getDocument(Database.java:1283)
at com.couchbase.lite.Document.getRevision(Document.java:219)
at com.couchbase.lite.Document.getCurrentRevision(Document.java:112)
at com.couchbase.lite.Document.getProperties(Document.java:165)
at com.couchbase.lite.performance.Test3_ReadDocs.testReadDocsPerformance(Test3_ReadDocs.java:84)
at java.lang.reflect.Method.invokeNative(Native Method)
at com.couchbase.lite.LiteTestCase.runBare(LiteTestCase.java:20)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:554)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)

@hideki ForestDb supports doc more than 2mb?

@NitzDKoder no limitation.
FYI, from 1.2.0, SQLite version does not have 2mb limitation anymore.


build: Add typings for node-dir

Was just reading through the code and VS Code was complaining that it couldn't figure out the typings after I did npm install.
Most of the lock file changes were actually caused by my initial npm install, but I'll call those out inline.

Hi @nschonni , thanks for the contributions!


Still image ok, video not working

Hi,
I have this config:
{
  "platform": "Camera-ffmpeg",
  "cameras": [
    {
      "name": "Kamera kint",
      "videoConfig": {
      	"source": "-re -i rtsp://xy:xy@192.168.1.xy:9002/Streaming/Channels/102/",
        "stillImageSource": "-i http://xy:xy@192.168.1.xy:9000/Streaming/channels/1/picture",
      	"maxStreams": 1,
      	"maxWidth": 352,
      	"maxHeight": 290,
      	"maxFPS": 1
      }
    }
  ]
}

Still  image is refreshing fine, but I can't get video to work. If I click on camera image in Home app to open live video I get immediately:
No response, this camera is not responding
In process I can't see the fffmpeg running.
If I open this camera on my Apple Watch I see connecting... and I see fffmpeg in the processes, cpu usage is around 10%. But the video never loads.
If I run manually:
ffmpeg -re -i rtsp://xy:xy@192.168.1.xy:9002/Streaming/Channels/102/ /home/madrian/remove.mp4
$ ffmpeg -re -i rtsp://xy:xy@192.168.1.xy:9002/Streaming/Channels/102/ /home/xy/remove.mp4
ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 4.8 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  configuration: --extra-libs=-ldl --prefix=/opt/ffmpeg --mandir=/usr/share/man --enable-avresample --disable-debug --enable-nonfree --enable-gpl --enable-version3 --enable-libopencore-amrnb --enable-libopencore-amrwb --disable-decoder=amrnb --disable-decoder=amrwb --enable-libpulse --enable-libfreetype --enable-gnutls --disable-ffserver --enable-libx264 --enable-libx265 --enable-libfdk-aac --enable-libvorbis --enable-libtheora --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libspeex --enable-libass --enable-avisynth --enable-libsoxr --enable-libxvid --enable-libvidstab --enable-libwavpack --enable-nvenc --enable-libzimg
  libavutil      55. 58.100 / 55. 58.100
  libavcodec     57. 89.100 / 57. 89.100
  libavformat    57. 71.100 / 57. 71.100
  libavdevice    57.  6.100 / 57.  6.100
  libavfilter     6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.
Any ideas?

Same issue for me.

Exact same issue, figure anything out? Mine was working great @720p 30fps. Instead of using rtsp I use video4linux pointing at /dev/video0

@TannerH
You are right. It's working only with setting @720p 30fps.
But why?


Error: SyntaxError: invalid syntax

Here's the full traceback, has anyone gotten these?
No handlers could be found for logger "GoogleScraper"
Traceback (most recent call last):
File "/usr/local/bin/GoogleScraper", line 9, in
load_entry_point('GoogleScraper==0.1.18', 'console_scripts', 'GoogleScraper')()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 356, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2476, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2190, in load
['name'])
File "/usr/local/lib/python2.7/dist-packages/GoogleScraper/init.py", line 20, in
from GoogleScraper.core import scrape_with_config
File "/usr/local/lib/python2.7/dist-packages/GoogleScraper/core.py", line 150
print(self.progress_fmt.format(self.num_already_processed, self.num_keywords), end='\r')

GoogleScraper is written in Python3. Try to install with Python3. Sometimes you need to install like this
sudo pip**3** GoogleScraper

instead of
sudo pip GoogleScraper

I changed to python 3, and checked the version to make sure, but now I'm getting this error after running pip3 install Google Scraper:
File "/usr/bin/pip3", line 9, in
load_entry_point('pip==1.5.6', 'console_scripts', 'pip3')()
File "/usr/lib/python3/dist-packages/pip/init.py", line 227, in main
cmd_name, cmd_args = parseopts(initial_args)
File "/usr/lib/python3/dist-packages/pip/init.py", line 206, in parseopts
cmd_args.remove(args_else[0].lower())
ValueError: list.remove(x): x not in list


Docker plugin doesn't display the autocomplete correctly

Hi, I have enabled the docker plugin and I think it doesn't display info correctly, that's what I'm getting then hitting TAB with docker logs
➜  ~ docker logs db_redis_1
2c517e6e124b
7288fb4ac9cc
db_pg_admin_1
db_postgres_1
db_redis_1
db_mongo_1
aba0af60ee56
bf72718a2dd4
--          4 days, redis:alpine
--          6 days, mongo:latest
--          8 days, fenglc/pgadmin4:python3.6-alpine
--          8 days, postgres:alpine
db_php_my_admin_1
docker_jhipster-registry_1
e0bd97474e16
d747bf7739d4
--          8 days, phpmyadmin/phpmyadmin:latest
--          6 days, jhipster/jhipster-registry:v4.0.0

It used to look good before the update.
➜  ~ zsh --version
zsh 5.3 (x86_64-apple-darwin17.0)

That's how my .zshrc file looks:
export ZSH=/Users/kgregorczyk/.oh-my-zsh
ZSH_THEME="robbyrussell"
plugins=(git docker kubectl zsh-autosuggestions zsh-completions)

source $ZSH/oh-my-zsh.sh
fpath=(~/.zsh/completion $fpath)
VIRTUALENVWRAPPER_PYTHON=/usr/local/bin/python
source /usr/local/bin/virtualenvwrapper.sh
autoload -Uz compinit && compinit -i
export REMOTE_LINUX_MACHINE=kgregorczyk.krp.corp.google.com
export GOPATH="$HOME/go"
export PATH="$GOPATH/bin:$PATH"

Which docker version do you have?

I updated zsh and it seems to be working, I can't remember which version of
docker I had
wt., 7 sie 2018, 23:05 użytkownik Marc Cornellà<EMAIL_ADDRESS>napisał:

Which docker version do you have?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/issues/7010#issuecomment-411202007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI1koJRGxLbGDaedl_AYA2mOcPkx4OGHks5uOgEYgaJpZM4VXvj0
.


Enhance python script interface to read multiple input data types.

As of met-8.0, the MET tools are able to call python scripts to read a gridded data file, load it into a NumPy array, define metadata, and pass it back to MET through memory.

However, this logic only works when Python stores that data as double-precision floating point values (i.e. "float64" in Python).  Passing integers or single-precision floats (i.e. "float32" in Python) results in either a segfault or unexpected behavior in MET.

This task is to update the logic in MET to figure out the Python data type that was used and interpret the data values correctly when loading them into a DataPlane object.
[MET-1056] created by johnhg

There is a member function "const char * Python3_Numpy::dtype() const" in the Python3_Numpy class that returns a string specifying the numeric data type specified in the numpy array.  The code can essentially switch on this as shown in the attached table.
numpy_types.pdf

Ok, the python numpy code now supports numpy arrays of integer type size 1, 2,4 or 8 bytes, signed or unsigned, and single or double precision floating-point types.  The data can be either little endian or big endian.
load_numpy.pdf
ifelse.pdf


Resource 'ciscoise_network_access_policy_set' returns 400 error

Environment:
ISE version and patch: ISE 3.1 patch 4
Terraform version: 1.3.1
ISE provider version: 0.6.10-beta
OS version: MacOS 12.6
Describe the bug
When using the 'ciscoise_network_access_policy_set' resource to create a Policy Set with a nested AND block, the following 400 error is returned.
As there is no example of this type of configuration, I'm not sure if this is a bug in the TF resource or if my example code is written incorrectly.
Error
│ Error: Failure when executing CreateNetworkAccessPolicySet
│
│   with ciscoise_network_access_policy_set.wired-mm-test,
│   on policy.tf line 274, in resource "ciscoise_network_access_policy_set" "wired-mm-test":
│  274: resource "ciscoise_network_access_policy_set" "wired-mm-test" {
│
│ error with operation CreateNetworkAccessPolicySet
│ {
│   "message" : "request has bad input format in the body",
│   "code" : 400
│ }

TF code example
resource "ciscoise_network_access_policy_set" "wired-mm-test" {
  provider = ciscoise.ise31-2
  depends_on = [
    ciscoise_network_device_group.ndg_mm
  ]
  parameters {

    condition {
      condition_type = "andBlock"
      is_negate = "false"
      children {
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
      }
      children {
        dictionary_name  = "DEVICE"
        attribute_name  = "Deployment Stage"
        operator = "equals"
        attribute_value = "Deployment Stage#Monitor Mode"
      }
    }
    default     = "false"
    description = "Wired Monitor Mode TEST"
    is_proxy    = "false"
    name         = "Wired_MM_TEST"
    rank         = 0
    service_name = ciscoise_allowed_protocols.mab-eaptls.item[0].name
    state        = "enabled"
  }
}

API GET response for the same Policy Set configured from the GUI
{
    "version": "1.0.0",
    "response": {
        "default": false,
        "id": "b8731cac-dba3-43bc-ac2b-f3205e01e8c1",
        "name": "Wired_MM",
        "description": null,
        "hitCounts": 0,
        "rank": 0,
        "state": "enabled",
        "condition": {
            "link": null,
            "conditionType": "ConditionAndBlock",
            "isNegate": false,
            "children": [
                {
                    "link": null,
                    "conditionType": "ConditionAttributes",
                    "isNegate": false,
                    "dictionaryName": "Radius",
                    "attributeName": "NAS-Port-Type",
                    "operator": "equals",
                    "dictionaryValue": null,
                    "attributeValue": "Ethernet"
                },
                {
                    "link": null,
                    "conditionType": "ConditionAttributes",
                    "isNegate": false,
                    "dictionaryName": "DEVICE",
                    "attributeName": "Deployment Stage",
                    "operator": "equals",
                    "dictionaryValue": null,
                    "attributeValue": "Deployment Stage#Monitor Mode"
                }
            ]
        },
        "serviceName": "MAB_EAP-TLS",
        "isProxy": false,
        "link": {
            "rel": "self",
            "href": "https://ise31-2.ise.domain.com/api/v1/policy/network-access/policy-set/b8731cac-dba3-43bc-ac2b-f3205e01e8c1",
            "type": "application/json"
        }
    }
}

Hi @fmunozmiranda. I tried creating the above Policy Set after updating to the 0.6.11-beta using the following code block and it still throws a 400 error.
TF Code
resource "ciscoise_network_access_policy_set" "wired-mm-test" {
  provider = ciscoise.ise31-2
  depends_on = [
    ciscoise_network_device_group.ndg_mm
  ]
  parameters {
    default     = "false"
    name         = "Wired_MM_TEST"
    description = "Wired Monitor Mode TEST"
    rank         = 0
    is_proxy    = "false"
    service_name = "MAB_EAP-TLS"
    state        = "enabled"
    condition {
      condition_type = "andBlock"
      is_negate = "false"
      children {
        condition_type = "ConditionAttrs"
        is_negate = "false"
        dictionary_name  = "Radius"
        attribute_name  = "NAS-Port-Type"
        operator = "equals"
        attribute_value = "Ethernet"
      }
      children {
        condition_type = "ConditionAttrs"
        is_negate = "false"
        dictionary_name  = "DEVICE"
        attribute_name  = "Deployment Stage"
        operator = "equals"
        attribute_value = "Deployment Stage#Monitor Mode"
      }
    }
  }
}

If the code format/syntax I am using is not correct, can you suggest what my TF resource block should look like to create the same same policy set as per this API request body that returns a 201 Created response?
API Body
{
        "default": false,
        "name": "Wired_MM",
        "description": null,
        "rank": 0,
        "state": "enabled",
        "condition": {
            "link": null,
            "conditionType": "ConditionAndBlock",
            "isNegate": false,
            "children": [
                {
                    "link": null,
                    "conditionType": "ConditionAttributes",
                    "isNegate": false,
                    "dictionaryName": "Radius",
                    "attributeName": "NAS-Port-Type",
                    "operator": "equals",
                    "dictionaryValue": null,
                    "attributeValue": "Ethernet"
                },
                {
                    "link": null,
                    "conditionType": "ConditionAttributes",
                    "isNegate": false,
                    "dictionaryName": "DEVICE",
                    "attributeName": "Deployment Stage",
                    "operator": "equals",
                    "dictionaryValue": null,
                    "attributeValue": "Deployment Stage#Monitor Mode"
                }
            ]
        },
        "serviceName": "MAB_EAP-TLS",
        "isProxy": false
    }

Hey @aussietexan, I think the problem is in your condition_type values it seems that accepted values are:
ConditionAttributes
ConditionAndBlock
ConditionOrBlock

Could you tested with those changes?

Hi @fmunozmiranda , I tested using those values and the resource worked. Please update the documentation as per Issue #68

I will update documentation in next realese, thanks for report it @aussietexan .


Sprint 2

Coverage decreased (-1.04%) to 90.01% when pulling 599d47f5fd307e1c6221c57c3926b538f1ab5765 on develop into 9e2ae7d1c217abfcaf2fc947296cfec6de745cff on master.

Coverage decreased (-0.9%) to 90.194% when pulling 4a2b46af5d877a717be391c61e557c5c27f5a960 on develop into 9e2ae7d1c217abfcaf2fc947296cfec6de745cff on master.


After install, opencv version displayed by 'jtop' and python script by 'cv2.getBuildInformation()' doesn't match.

Hi, Thanks to your file build_opencv.sh, I installed opencv on Jetson Xavier NX devkit with specific version- 4.5.4.
MY ORIGINAL SETTINGS : JetPack ver 5.0.2, Ubuntu20.04, CUDA 11.4.239, cuDNN <IP_ADDRESS>, OpenCV 4.5.4-with CUDA:NO,  pytorch: 1.11.0 , torchvision:0.12.0
I executed "./build_opencv.sh 4.5.4" and it seems worked. But, when I try to check the result, jtop says opencv 4.5.4 installed successfully..and here is the problem. When I print cv2.getBuildInformation() in python script after import cv2, opencv4.8.1 version gets out so I can't run YOLO model with GPU support.

This is what I can see during build process - I can see opencv with version 4.5.4 and also has NVIDIA CUDA , cuDNN attribute at second picture.

and this is result of "cv2.getBuildInformation()" - opencv 4.8.1-dirty.
I didn't touch any additional setting at all!!  And even worse, I can't see NVIDIA CUDA , cuDNN in this script.

I can't figure out what's the cause of the problem.. How can I fix this?
this is a screenshot for more detail

I have the same problem.
I successfully installed OpenCV 4.6.0. In the jtop info, it shows:

OpenCV: 4.8.0 with CUDA: YES

However, when I checked with pip3 list, I found:

opencv-python 4.1.1

In Python 3.6, the OpenCV version is 4.1.1 without CUDA support.
I checked and CV2 4.8.0 was build in Python 2.7
I want to use OpenCV 4.8.0 with Python 3.6. How can I do this?


Cannot build from a virtual workspace in Rust 1.40.0

After updating to Rust 1.40, I can no longer run cargo web build -p package in a virtual workspace. it says that:
error: error: --features is not allowed in the root of a virtual workspace

I found this line in the Chagelog of Cargo 1.40:

--features and --no-default-features in the root of a virtual workspace will now generate an error instead of being ignored. rust-lang/cargo#7507

I'm encountering this as well.

This is currently breaking the virtual_manifest test

My workaround up till now was to override rust version to 1.39.0 which is the latest working version.
Except within the last month remove_dir_all was updated to v0.5.3 and now uses cfg(doctest) which is apparently experimental in rust 1.39.0, so cargo-web doesn't even build on 1.39.0 anymore. (I don't know where in the dependency tree remove_dir_all comes from, but since cargo-web doesn't freeze versions for it's dependencies, it's always the latest version that will be used.)
The only way to get it to work is to first cargo install cargo-web with the latest rust, and only then rustup override set 1.39.0 and build your project.
Link to my working CI script


Basic folders setup

Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] 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 not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

Reviewed each file √, everything looks good.  Make sure to fill out the form above, delete what you don't need or checkoff checklist and type of change.  Not sure if github will like that the files are empty. Know they don't upload empty folders.. we will find out. Good job! 🙌🏻


loading save slots crashes on hardware

try to load a program from any slot
999 error

The save slot are containing programs with the old format; we should swallow deserialization issues.

this is not a huge issue. people will start with fresh hex files, for the most part. I don't really think it is worth keeping the old JSON format alive, do you?

https://github.com/microsoft/microcode/commit/0bc0fefd4aae37a5a7d47604db48f6743c07fe80


Implement shared R workspace

Following our recent post and tweet trialing VS Code and VS Live Share for remote pair programming in R, it would be great if the VS Live Share team could collaborate with the excellent R extension team at vscode-R to implement a shared R workspace in Live Share.

Hey @gvelasq , any VS Code primitives (language services, terminals, debugging, ...) should be supported by Live Share natively. Any custom extension behavior should be made collaborative inside of the extension using Live Share's extensibility API.
So if you're seeing VS Code primitives not working, that's a bug on Live Share and we'd love to hear which ones aren't working. Is that the case?
If this is a request for custom extension behavior to work in a Live Share session, that would be a feature request on the R extension. But do let us know if you need help getting started or if the API is lacking anything you need.

@daytonellwanger, thanks for this information. The R workspace is implemented in the custom extension vscode-R so I'll file a feature request there.

Thanks! I'll go ahead and close this for now. If you run into specific bugs while adding Live Share support to the R extension, please file them.