fortune-mod update from 1.99.1 to 2.6.2

Issue description
The version on nixpkgs is too old.
Scripts
I try to make a pull request for this, but it is failed to build. I have no idea how to fix it.
patch:
diff --git a/pkgs/tools/misc/fortune/default.nix b/pkgs/tools/misc/fortune/default.nix
index 8e955733598..81256cd0e6d 100644
--- a/pkgs/tools/misc/fortune/default.nix
+++ b/pkgs/tools/misc/fortune/default.nix
@@ -1,28 +1,25 @@
-{ stdenv, fetchurl, recode }:
+{ stdenv, fetchurl, cmake, recode }:

 stdenv.mkDerivation {
-  name = "fortune-mod-1.99.1";
+  name = "fortune-mod-2.6.2";

   src = fetchurl {
-    url = http://ftp.de.debian.org/debian/pool/main/f/fortune-mod/fortune-mod_1.99.1.orig.tar.gz;
-    sha256 = "1kpa2hgbglj5dbfasvl9wc1q3xpl91mqn3sfby46r4rwyzhswlgw";
+    url = https://github.com/shlomif/fortune-mod/archive/fortune-mod-2.6.2.tar.gz;
+    sha256 = "89223bb649ea62b030527f181539182d6a17a1a43b0cc499a52732b839f7b691";
   };

-  buildInputs = [ recode ];
+  sourceRoot = "fortune-mod-fortune-mod-2.6.2/fortune-mod";

-  preConfigure = ''
-    sed -i "s|/usr/|$out/|" Makefile
+  buildInputs = [ cmake recode ];
+
+  configureScript = ''
+    cmake -DCMAKE_INSTALL_PREFIX=$out .
   '';

   preBuild = ''
     makeFlagsArray=("CC=$CC" "REGEXDEFS=-DHAVE_REGEX_H -DPOSIX_REGEX" "LDFLAGS=")
   '';

-  postInstall = ''
-    mv $out/games/fortune $out/bin/fortune
-    rmdir $out/games
-  '';
-
   meta = with stdenv.lib; {
     description = "A program that displays a pseudorandom message from a database of quotations";
     license = licenses.bsdOriginal;

The failure is mainly that cmake cannot find a command defined in another cmake file.
But if I run cmake within nix-shell -p recode cmake, it successes. And have another error with make.
This may fix shlomif/fortune-mod#33.

CMake Warning at cmake/shlomif_common_bootstrap.cmake:7 (MESSAGE):
  Could not find Shlomif_Common.cmake - you can find it here:
  https://bitbucket.org/shlomif/shlomif-cmake-modules/overview ; trying to
  download it for you.
Call Stack (most recent call first):
  CMakeLists.txt:3 (INCLUDE)

cmake is trying to download things at build-time, and nix is blocking network access
cmake then silently omits the network error, and tries to use the file it doesnt have

https://github.com/shlomif/fortune-mod/blob/master/fortune-mod/cmake/shlomif_common_bootstrap.cmake#L8
this file will need to be fetched using fetchurl and then copied to the right spot in preConfigure

Hi all!
Note that I provide release tar.xz s here: https://www.shlomifish.org/open-source/projects/fortune-mod/arcs/ . Perhaps I should attach them to the github tags.


Update app-templates.md

Adding following app template descriptions :
1- Training App Template
2- Quiz App Template

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

File
Status
Preview URL
Details

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 6350c05:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

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


Design Doc note to limit R-Libraries

With increased discussion of installation issues, there has been a suggestion that we try to get ahead and push new developers to" minimize new R-libraries, and reuse of R-libraries used by existing VE modules".  As such, I'm suggesting we include this quoted text in these wiki locations.
Does this make sense?
1- the Model System Design Documentation (possibly Sec 3 under "Operating System Independence" bullet?)
2- Explicitly mention Libraries in Contributor Review Criteria #1, "Consistent with Design Specs"

See https://github.com/gregorbj/VisionEval/wiki/Contribution-Review-Criteria and the upcoming commit I'm going to tag.


Make it easy to use clangd (i.e. an IDE) with the engine (especially post-RBE)

It was and still is possible to use clangd (i.e. with the VSCode clangd plugin) while working in the engine.
For example, here is an excerpt of my workspace settings (JSON):
"clangd.path": "${workspaceFolder}/buildtools/mac-arm64/clang/bin/clangd",
"clangd.arguments": [
  "--compile-commands-dir=${workspaceFolder}/../out/host_debug_unopt_arm64"
],
"clang-format.executable": "${workspaceRoot}/buildtools/mac-arm64/clang/bin/clang-format",

Even before RBE, this required manual configuration, and requires re-configuration as you change platforms (for example, editing C++ code that uses Android-only dependencies requires the --compile-commands-dir to point to a ../out/android_* target).
Post RBE, the default --compile-commands-dir for Google employees uses flags (wrappers) unrecognized by clangd:

One workaround is to intentionally create and use a target output that opts out of RBE:
./tools/gn --unopt --mac-cpu=arm64 --target-dir=host_debug_unopt_arm64_ide --no-rbe

Problems to address (outside of having to do all this manually):

By default, this produces many broken links as a result of (mostly Impeller?) generators that need to run. One such example:
# There are about ~3 sets of targets that need to be built so that clangd finds all generated files.
ninja -C ../out/host_debug_unopt_arm64_ide shader_fixtures

Because this target is not actually used, it will frequently get out of date. That is, you will need to need to gclient sync -D
and reset GN arguments for both the target you're actually working on (i.e. host_debug_unopt_arm64, using RBE), and this stub target (host_debug_unopt_arm64_ide).

I'm opening this issue to solicit ideas for addressing this. Incremental is good, automated is good, tested is better.

In my opinion, consuming raw compile_commands.json generated by gn isn't feasible for tools like clangd, since gn dumps raw commands with all the flags used to build the target. I don't work at Google and therefore don't use Goma or RBE, but I encountered the same issue a long time ago and developed a solution to parse compile_commands.json and filter out flags unnecessary for consuming tools.
You can find my script here: https://gist.github.com/bc-lee/8707d1e62d14f8bb6bd30ef6e67f1625
The script modifies the compile_commands.json file by removing flags that clangd doesn't need. It's not perfect, but it works for me. At least it's much easier than maintaining a separate output folder to avoid using unnecessary flags with clangd.
Example usage:
$ gn gen --export-compile-commands out/out_dir && parse-compile-commands out/out_dir

Thanks @bc-lee, that certainly is an option, maybe even the best one.
I'll let the rest of the engine team weigh, but I appreciate the contribution!


File storage fails on Heroku: Errno::ENOENT (No such file or directory @ rb_sysopen - /app/challenge/challenge)

1. Expected behavior
It just works.
2. Actual behavior
Does not store challenge.
Heroku error:
app[web.1]: Errno::ENOENT (No such file or directory @ rb_sysopen - /app/challenge/challenge):
app[web.1]:   vendor/bundle/ruby/2.3.0/gems/letsencrypt_plugin-0.0.8/app/models/letsencrypt_plugin/challenge.rb:13:in `read'
app[web.1]:   vendor/bundle/ruby/2.3.0/gems/letsencrypt_plugin-0.0.8/app/models/letsencrypt_plugin/challenge.rb:13:in `initialize'
app[web.1]:   vendor/bundle/ruby/2.3.0/gems/letsencrypt_plugin-0.0.8/app/controllers/letsencrypt_plugin/application_controller.rb:20:in `new'
app[web.1]:   vendor/bundle/ruby/2.3.0/gems/letsencrypt_plugin-0.0.8/app/controllers/letsencrypt_plugin/application_controller.rb:20:in `challenge_response'

No challenge file was created:
$ heroku run find /app/challenge/
Running find /app/challenge/ on foobar... up, run.1972
/app/challenge/
/app/challenge/.keep

(.keep was created by me)
3. Steps to reproduce issue

Add empty challenge directory.
Run heroku run rake letsencrypt_plugin
Logs say that challenge is stored, but ...
... no challenge file on remote server

This is because creating files silently fails on heroku (it's a read-only filesystem). The workaround would be to e.g. set challenge_dir_name to something writable like `tmp/challenge' instead or fail with a better error (saying that the challenge should be generated locally and added to git).
4. Your configuration (ruby, rails version, your Gemifile and Gemfile.lock files etc.)
Relevant part of config:
# (...)
challenge_dir_name: 'challenge'
# (...)

Hi,
please use DB storage for Heroku: https://github.com/lgromanowski/letsencrypt-plugin/wiki/Installation-guide#3-install-letsencrypt_plugin-migration

So does this mean that an app that doesn't use ActiveRecord (ie it uses MongoID) won't work with this gem?

At this moment it won't work (pull request with patches are welcome)


Unable to NewClient() for <IP_ADDRESS>

Which version of Elastic are you using?
[v] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
ES client is initialized
Please describe the actual behavior
ES client is nil, and the err is "no active connection found: no Elasticsearch node available"
Any steps to reproduce the behavior?

Launch ES 6.3.2 by docker

docker run --rm -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" docker.elastic.co/elasticsearch/elasticsearch:6.3.2

Make sure ES service is available

$ curl 'http://<IP_ADDRESS>:9200/_nodes/http?pretty'

{
  "_nodes" : {
    "total" : 1,
    "successful" : 1,
    "failed" : 0
  },
  "cluster_name" : "docker-cluster",
  "nodes" : {
    "0iANW4AqRkGpU4jINJt5_A" : {
      "name" : "0iANW4A",
      "transport_address" : "<IP_ADDRESS>:9300",
      "host" : "<IP_ADDRESS>",
      "ip" : "<IP_ADDRESS>",
      "version" : "6.3.2",
      "build_flavor" : "default",
      "build_type" : "tar",
      "build_hash" : "053779d",
      "roles" : [
        "master",
        "data",
        "ingest"
      ],
      "attributes" : {
        "ml.machine_memory" : "2096066560",
        "xpack.installed" : "true",
        "ml.max_open_jobs" : "20",
        "ml.enabled" : "true"
      },
      "http" : {
        "bound_address" : [
          "<IP_ADDRESS>:9200"
        ],
        "publish_address" : "<IP_ADDRESS>:9200",
        "max_content_length_in_bytes" : 104857600
      }
    }
  }
}

Import elastic and trying to use it, but it fails

package main

import (
	"fmt"
	elastic "gopkg.in/olivere/elastic.v6"
)

func main() {
	// Create a client
	elastic.SetSniff(false)
	client, err := elastic.NewClient(elastic.SetURL("http://<IP_ADDRESS>:9200"))
	if err != nil {
		fmt.Println(err)
	}

	fmt.Println(client)}

The output will be
no active connection found: no Elasticsearch node available
<nil>

Please disable sniffing in the config options. See the Wiki for details or search for sniffing in the issues.


Replace seqeval code with original classification_report for simplicity

Recently, the original seqeval has enabled us to get per type scores and overall scores as a dictionary.
This PR replaces the current code with the original function(classification_report) to simplify it.
Also, the original code has been updated to fix #352.

Related issue: https://github.com/chakki-works/seqeval/pull/38

from datasets import load_metric
metric = load_metric("seqeval")
y_true = [['O', 'O', 'O', 'B-MISC', 'I-MISC', 'I-MISC', 'O'], ['B-PER', 'I-PER', 'O']]
y_pred = [['O', 'O', 'B-MISC', 'I-MISC', 'I-MISC', 'I-MISC', 'O'], ['B-PER', 'I-PER', 'O']]
metric.compute(predictions=y_pred, references=y_true)
# Output: {'MISC': {'precision': 0.0, 'recall': 0.0, 'f1': 0, 'number': 1}, 'PER': {'precision': 1.0, 'recall': 1.0, 'f1': 1.0, 'number': 1}, 'overall_precision': 0.5, 'overall_recall': 0.5, 'overall_f1': 0.5, 'overall_accuracy': 0.8}

Hello,
I ran https://github.com/huggingface/transformers/blob/master/examples/token-classification/run.sh
And received this error:
100%|██████████| 407/407 [21:37<00:00,  3.44s/it]Traceback (most recent call last):
  File "run_ner.py", line 445, in <module>
    main()
  File "run_ner.py", line 398, in main
    results = trainer.evaluate()
  File "/data/2021/transformers/src/transformers/trainer.py", line 1470, in evaluate
    metric_key_prefix=metric_key_prefix,
  File "/data/2021/transformers/src/transformers/trainer.py", line 1622, in prediction_loop
    metrics = self.compute_metrics(EvalPrediction(predictions=preds, label_ids=label_ids))
  File "run_ner.py", line 345, in compute_metrics
    results = metric.compute(predictions=true_predictions, references=true_labels)
  File "/usr/local/lib/python3.6/dist-packages/datasets/metric.py", line 398, in compute
    output = self._compute(predictions=predictions, references=references, **kwargs)
  File "/root/.cache/huggingface/modules/datasets_modules/metrics/seqeval/81eda1ff004361d4fa48754a446ec69bb7aa9cf4d14c7215f407d1475941c5ff/seqeval.py", line 97, in _compute
    report = classification_report(y_true=references, y_pred=predictions, suffix=suffix, output_dict=True)
TypeError: classification_report() got an unexpected keyword argument 'output_dict'

I'm still trying multiple things to see if I can work around this, but I thought it might be useful to mention it here.
Name: transformers
Version: 4.3.0.dev0

Name: datasets
Version: 1.2.1

Hello,
I ran https://github.com/huggingface/transformers/blob/master/examples/token-classification/run.sh
And received this error:
100%|██████████| 407/407 [21:37<00:00,  3.44s/it]Traceback (most recent call last):
  File "run_ner.py", line 445, in <module>
    main()
  File "run_ner.py", line 398, in main
    results = trainer.evaluate()
  File "/data/2021/transformers/src/transformers/trainer.py", line 1470, in evaluate
    metric_key_prefix=metric_key_prefix,
  File "/data/2021/transformers/src/transformers/trainer.py", line 1622, in prediction_loop
    metrics = self.compute_metrics(EvalPrediction(predictions=preds, label_ids=label_ids))
  File "run_ner.py", line 345, in compute_metrics
    results = metric.compute(predictions=true_predictions, references=true_labels)
  File "/usr/local/lib/python3.6/dist-packages/datasets/metric.py", line 398, in compute
    output = self._compute(predictions=predictions, references=references, **kwargs)
  File "/root/.cache/huggingface/modules/datasets_modules/metrics/seqeval/81eda1ff004361d4fa48754a446ec69bb7aa9cf4d14c7215f407d1475941c5ff/seqeval.py", line 97, in _compute
    report = classification_report(y_true=references, y_pred=predictions, suffix=suffix, output_dict=True)
TypeError: classification_report() got an unexpected keyword argument 'output_dict'

I'm still trying multiple things to see if I can work around this, but I thought it might be useful to mention it here.
Name: transformers
Version: 4.3.0.dev0

Name: datasets
Version: 1.2.1

Can you try to update your local installation of seqeval ?
pip install --upgrade seqeval

Can you try to update your local installation of seqeval ?
pip install --upgrade seqeval


Update README: Ruby 2.0 required

Can't use my Ubuntu 14.04 bundled Ruby 1.9.3. Make a note about 2.0

Could you tweak this slightly to say that ruby 2.0.0 should be used? That is the version shipped with vagrant. You could even set this in the Gemfile
$ /opt/vagrant/embedded/bin/ruby --version
ruby 2.0.0p598 (2014-11-13 revision 48408) [x86_64-linux]


Exclude CGNAT address range

Task/Issue URL: https://app.asana.com/0/488551667048375/1204121327572584/f
Description
Exclude CGNAT IP range
Steps to test this PR
Smoke AppTP tests

Current dependencies on/for this PR:

develop

PR #2920   👈

This comment was auto-generated by Graphite.


End Portal Not Teleporting to THE END spawn

I'm beginning to wonder if I am missing something obvious. I have a second world with both a nether and the_end versions. Creating nether portals works fine and follows scaling rules. However, when an end portal is opened, players are teleported to the same location as that in the fromWorld, rather than using the default Notch behavior of spawn near the dragon. (0,64,0), or so. If I disable NetherPortals, the end portal works as expected.
I took a closer look at the source to see if I was missing some important configuration option, but if doesn't like it. As it stands, the onPlayerPortal gets a linkedWorld of null and drops down to the last else condition. From there because it is an end portal and nameChecker does find the_end world getNewTeleportLocation moves forward and teleports the player. Instead, it would be nice to shortcircuit getNewTeleportLocation and let the onPlayerPortal event take its natural course down the event change so that Notches default behavior is fired up.
Right now my only work around is to disable NetherPortal. Unfortunately, that limit me to having a single Nether for the main world, but at least The End comes up for either world.

I had an idea. While this may not be the most gallant way of doing this, at least this way, if there is no linked world defined for the_end, the onPlayerPortal will just do its default thing. If I specifically link the_end in the configuration file, then normal scaling and the rest applies.
	if (type == PortalType.END) {
		if (linkedWorld != null)
			this.linkChecker.getNewTeleportLocation(event, currentLocation,
					linkedWorld);
		else
			return;
	} else {
		if (linkedWorld != null) {
			this.linkChecker.getNewTeleportLocation(event, currentLocation,
					linkedWorld);
		} else if (this.nameChecker.isValidNetherName(currentWorld)) {
			this.linkChecker.getNewTeleportLocation(event, currentLocation,
					this.nameChecker.getNormalName(currentWorld));
		} else {
			this.linkChecker.getNewTeleportLocation(event, currentLocation,
					this.nameChecker.getNetherName(currentWorld));
		}
	}

Aye. I've wanted better end support for some time. I'm still on a holiday (github issues for iPhone ftw) but would love to read a pull request for this when I get back :)

I solute this putting 10000 ratio to the end

That's a clever temporary fix. Nice one umarth!


Slim 4: Change to League/Container

I think that dumping Pimple for League\Container will be a great movement for Slim 4, for many reasons.
First, I'm aware of the reason why you decided to use Pimple. It's simple and lightweight. But League/Container has some really good features Slim can benefit from.
League Container allows you to define delegate containers. These containers are kinda fallback containers. If a service is not found in the main container instance, then the delegate container is used to try to resolve the service.
Why is this useful for Slim? Well, currently, if one provides his own instance of a PSR-11 Container, then you have to manually register the Slim default services. I think that is not convienent, because the user then has to dig in the source code or documentation to check what are the required services or values for Slim to run correctly.
What League\Container would allow us to do is to define a main container, then register the Container a user passed as a delegate, and then register the Slim container (with all Slim Services already wired) as another delegate. If the user want's to override a slim setting or service, then they can do it in the container they passed to the App instance, but everything else will be able to work smoothly.
I can provide a pull request implementing the change, so you can see how it behaves in real life. I've used this strategy with a Micro Framework of my own and has worked really great.
League Container, as Slim, also has support for traditional features, like ServiceProviders, and this change will be transparent for the users.
What do you think? :smiley:

PS: Another feature is that League Container has a ReflectionContainer that the user could use as a delegate as well. This will avoid registering every service into the container explicitly, and use some reflection magic for autowiring. Optional for those who want fast prototyping and more development speed. :)

Slim 4 will not have any Container implementations as a dependency. You will provide your own. So there's not switching to be done.
See https://github.com/slimphp/Slim/pull/2290
Thanks


Moving mouse causes flicker in pipeline view

I only see this on Mac. Is the pipeline being redrawn when the mouse is moved? Do anyone else see this?

Do you still see this @rexissimus? I think @dakoop mentioned he didn't see it either...

This only happens while mirroring the desktop through TeamViewer. The view is not being updated and I do not see any additional events fired. It looks like TeamViewer is causing a redraw of the graphics view. The flickering is minor so I am closing this.


[events API 1/?]: Add new send and receive streaming RPCs

Replaces https://github.com/lightninglabs/taproot-assets/pull/773.
Fixes https://github.com/lightninglabs/taproot-assets/issues/781.
Fixes https://github.com/lightninglabs/taproot-assets/issues/806.
Fixes https://github.com/lightninglabs/taproot-assets/issues/739.
This PR adds new RPCs for being notified about inbound and outbound asset transfers.
The existing SubscribeSendAssetEventNtfns and SubscribeReceiveAssetEventNtfns were mostly built for asserting the internal state during integration tests and weren't super helpful for app builders. That's why these old RPCs were moved to the tapdevrpc package and are now only used in the integration tests.
The new RPCs notify on all send and receive states instead of only a few of them. The events also contain way more information that's useful to map them to the user action. And both RPCs allow the events to be filtered (either by address for receive events and by script key for send events).
This is part 1 of the "events API" saga. The follow-up PRs will base on this one and address:

Allow to be notified about past events (e.g. reading events from the database back to a certain specified date): https://github.com/lightninglabs/taproot-assets/issues/822
Add event RPC for the minting process
Notify on send errors: https://github.com/lightninglabs/taproot-assets/issues/254

BTW, CI failed on RPC and lint check.

Fixed!

Re-reviewed after rebases, still LGTM.


Add a lot of new types based on the API docs

I wanted to open this as a draft to get your thoughts, hopefully it's not too intrusive. I saw your Show HN, and dove right in!
This adds a couple of concepts to the library, as well as a bunch of new types. The biggest changes are the two Meta types, Meta, and ItemsMeta.
These structs contain a lot of the common fields that are a part of the API, as well as implement a simple Get(spotify.API, interface{}) error method that will fetch all current data for the given object. I've added an example of this here.
This also adds the Playlist, Album, Image,  and Owner types, as well as fleshes out the Track type a little more
TODO before completing the draft:

[ ] write some docs
[ ] add some testing for the Meta types

There are a few breaking changes that'll require fixing https://github.com/brianstrauch/spotify-cli,

I've got a local copy I've been testing, I can submit that once this merges (since it won't build correctly beforehand, anyway)

This last changeset seems to have gotten a bit out of hand... Let me know how I should proceed here


V1 is no longer supported

closes #1802

With V1 going away, we could change from qiskit_ibm_runtime import EstimatorV2 as Estimator  to from qiskit_ibm_runtime import Estimator as Estimator ? But @jyu00 and I discussed this and decided that it would be too confusing for anyone who isn't actually using the most current version of Runtime (because they would get the v1 Estimator instead of v2).  We can revisit changing the code in a while.

from qiskit_ibm_runtime import Estimator as Estimator

FYI this would be simply from qiskit_ibm_runtime import Estimator since you're not changing the name. I agree it's a good idea to wait 2-3 months at least until making this simplification.

Side question, when can we remove the ISA warning? Given we imposed that almost 6 months ago.

I'm asking about this.  I'm ready to delete it whenever.


Feature: Mock region

Feature to allow a user to specify a non-existing region. Having a non-existent region can be useful as an additional layer of protection, to ensure the user does not modify real AWS architecture.
This feature is disabled by default, but can be enabled with an environment variable. (MOTO_ALLOW_NONEXISTENT_REGION)
In order to make this work, all backends are now generated on-request, rather then on start-up.
This results in:

A single place where we can decide whether a region is valid/allowed
Better performance on start-up (we don't need to generate Backends for 27 regions, just the one required)
Better performance on reset (as we only need to reset a single Backend, instead of all 27.)

Closes #4252

Codecov Report

Merging #4699 (ffcc88d) into master (82588b2) will increase coverage by 44.75%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master    #4699       +/-   ##
===========================================
+ Coverage   50.52%   95.28%   +44.75%
===========================================
  Files         550      550
  Lines       60802    60386      -416
===========================================
+ Hits        30723    57538    +26815
+ Misses      30079     2848    -27231

Flag
Coverage Δ

servertests
47.48% <99.48%> (-0.32%)
:arrow_down:

test_responses
32.05% <99.48%> (-0.41%)
:arrow_down:

unittests
95.19% <100.00%> (?)

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

Impacted Files
Coverage Δ

moto/applicationautoscaling/__init__.py
100.00% <ø> (ø)

moto/cloudwatch/__init__.py
100.00% <ø> (ø)

moto/cognitoidentity/__init__.py
100.00% <ø> (ø)

moto/datapipeline/__init__.py
100.00% <ø> (ø)

moto/elastictranscoder/__init__.py
100.00% <ø> (ø)

moto/emrcontainers/__init__.py
100.00% <ø> (ø)

moto/iot/__init__.py
100.00% <ø> (ø)

moto/iotdata/__init__.py
100.00% <ø> (ø)

moto/medialive/__init__.py
100.00% <ø> (ø)

moto/rds/__init__.py
100.00% <ø> (ø)

... and 389 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 82588b2...ffcc88d. Read the comment docs.

Understandable! Thanks @bpandola


Boardwalk in android 7

Hi, i tried boardwalk in android 7, dosent work.
But i have a idea! I tried coping app data from working phone, but
this happens: https://goo.gl/ZuXbvX
It dosent respond to controls.
How i did:
1- Copy boardwalk folder in storage/emulated/0 to the android 7 tab
2- Copy boardwalk data in data/data/net.blabalbah... to the android 7 tab
3- Apply it
4- Repaired permissions
5- Runned
6- Opened boardwalk app
7- (the link)
Edit: both are root

ANSWER ME :(


Publisher runtime configuration issues in API Product

An error occurred when saving configuration related to API Product. (security, schema validation, response caching)

Close the issue as per above commit


⚠ Bofrost.de has degraded performance

In a4c266a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1228 ms

Resolved: Bofrost.de performance has improved in 83bd5e0 after 1 hour, 25 minutes.


where to get config.h?

config.h.txt
fftools\ffmpeg.c included this 'config.h'

config.h is not a public header, so you won't find it in the shared archives.

is it ok to make them (files like config.h) public to us?

What do you mean? It's an internal header, used to configure the build of ffmpeg itself. You don't need it to utilize the API.
If you want it to be a public one for whatever reason, you will need to discuss that on ffmpeg-devel.
Closing this one here, since it's not an issue with the builds.

I want to build ffmpeg.exe, and fftools\ffmpeg.c need header files like 'config.h'.

While building ffmpeg itself, config.h is available. So I'm not sure I understand what you're doing.

I just want to build fftools, but not ffmpeg itself. so I need thoese headers.

That makes no sense. ffmpeg.c cannot be built independently.
If you just want an ffmpeg binary, you can grab it from the static builds here. That's exactly what they're for.

I want to build my own fftools, so I download ffmpeg public binary and headers from BtbN, and I still need those non-public headers like 'config.h'.

You cannot build the fftools indepentendly of the rest of ffmpeg.
If you want to build them yourself, you got to build the entire rest of ffmpeg alongside as well.

Got you, really thank you.

发件人: BtbN @.>
发送时间: Sunday, July 25, 2021 7:49:51 PM
收件人: BtbN/FFmpeg-Builds @.>
抄送: HppZ @.>; Author @.>
主题: Re: [BtbN/FFmpeg-Builds] where to get config.h? (#92)
You cannot build the fftools indepentendly of the rest of ffmpeg.
If you want to build them yourself, you got to build the entire rest of ffmpeg alongside as well.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/BtbN/FFmpeg-Builds/issues/92#issuecomment-886190068, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC5XNDQXPX5OO7MHK2MKMU3TZP257ANCNFSM5A3TGE6Q.


implement EncodeCustom

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

41 of 72 (56.94%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 55.416%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

jwt/custom_encode.go
41
72
56.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
2302

Relevant Lines:
4154

💛  - Coveralls


Added GitHub Actions

Why did I hardcoded Laravel ^8.74?
Because at "prefer-lowest" we get an error:
PHP Fatal error:  During inheritance of IteratorAggregate: Uncaught ErrorException: Return type of Symfony\Component\HttpFoundation\ParameterBag::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/runner/work/fireable/fireable/vendor/symfony/http-foundation/ParameterBag.php:191

This is due to the fact that Laravel uses "symfony/http-foundation": "^5.1.4" before version ^8.74 in which there is no #[\ReturnTypeWillChange]: https://github.com/symfony/http-foundation/blob/5.1/ParameterBag.php#L205 but in 5.4 it already exists https://github.com/symfony/http-foundation/blob/5.4/ParameterBag.php#L212
Why did I hardcoded "orchestra/testbench": "^6.4"?
Because at "prefer-lowest" we get an error:
1) Envant\Fireable\Tests\FireableAttributesTest::testSetAnyValue
Error: Call to undefined method Envant\Fireable\Tests\FireableAttributesTest::getAnnotations()

To fix this, it was necessary to upgrade to newer versions. Since version "orchestra/testbench": "^6.4" this bug has been fixed.
I also removed support PHP 7.2

Closed because I opened a new one - https://github.com/envant/fireable/pull/22, where I fully maintained backward compatibility with the old versions of PHP and Laravel.


rhel7 has a git version with four digits (<IP_ADDRESS>)

rhel7 has a git version with four digits. Checking for git version > 2.X (large file support) fails

LGTM

LGTM


Allow creation of subnets from secondary VPC IPv4 CIDR blocks

This change allows creation of subnets from secondary VPC IPv4 CIDR blocks in the mock_ec2 framework.
Previously, if you attempted to create a subnet in a secondary VPC CIDR you would get a IP range validation error.
Fixes #3385

Coverage decreased (-0.3%) to 94.164% when pulling 978907c8c7e512cafd0ff6843672a8c1edf1f4c5 on davidaah:fix/vpc-cidr-validation into 99556620a95da8fbfc7bca71e1a904f5f54f08be on spulec:master.


Travis CI runs out of memory since latest docker image update (17-11-2017)

Hey there,
I see in the commit history that the latest change to this repo was 6 months ago, however according to dockerhub the latest build was done last friday. Since that time our CI has been broken with stalled builds. After debugging it turned out that we run out of memory.
Do you have any idea what could cause this? And how to fix this?
Thanks in advance

We're using 2.7, if you want to take a look at our dockerfile, it's here. The Ci we're using is Travis (also contacted them about it), builds can be found here.
After local tests it doesn't seem like the memory has actually increased though, we tested by building using the cached image and the new one while monitoring with docker stats.
Maybe you have a clue what goes wrong? The builds just stall...

I've cloned your repo, and I'm trying to build the image locally to see if I see any errors while building. I'll be back when its done

I've builded the image without any problem. I've looked through your Ci logs and it seems that its hanging perhaps on the wait-for-it script. I'm running the docker-compose now to do a couple of tests.

Ah yeah we've noticed that now too, it appears to be the exit statement or something (before we updated our dependencies it stalled in the middle of the pip install gevent so maybe that has exit too). Trying it now with the new docker healthchecks.

I was able to run the dockerfile and run the tests directly (python manage.py test --with-coverage --cover-erase --cover-package=lily), so I would say something is wrong with the wait-for-it.
I went to its repo, and found out this commit from 4 months ago that has a bug fix for when you pass parameters. I've checked and you indeed pass parameters wait-for-it.sh -b db:5432 and your version of the script is before that commit. Maybe you could test updating the wait-for-it script and rerun the build?


PartialEq implementation for structs with padding shouldn't use memcmp?

I'm unsure if this is by design or not, but windows-bindgen 0.43.0 has generated a struct that looks like this:
#[repr(C)]
pub struct DSTORAGE_REQUEST_OPTIONS {
    pub _bitfield1: u8,
    pub _bitfield2: u64,
}

This struct has 3 bytes of padding between _bitfield1 and _bitfield2.
The implementation of PartialEq is:
impl ::core::cmp::PartialEq for DSTORAGE_REQUEST_OPTIONS {
    fn eq(&self, other: &Self) -> bool {
        unsafe {
            ::windows::core::memcmp(
                self as *const _ as _,
                other as *const _ as _,
                core::mem::size_of::<DSTORAGE_REQUEST_OPTIONS>(),
            ) == 0
        }
    }
}

This means that test code like this fails:
    #[test]
    fn sanity_test() {
        use microsoft_directstorage::DSTORAGE_REQUEST_OPTIONS;

        let x = DSTORAGE_REQUEST_OPTIONS {
            _bitfield1: 0,
            _bitfield2: 0,
        };

        let y = DSTORAGE_REQUEST_OPTIONS {
            _bitfield1: 0,
            _bitfield2: 0,
        };

        assert_eq!(x, y);
    }

thread 'tests::sanity_test' panicked at 'assertion failed: `(left == right)`
  left: `DSTORAGE_REQUEST_OPTIONS { _bitfield1: 0, _bitfield2: 0 }`,
 right: `DSTORAGE_REQUEST_OPTIONS { _bitfield1: 0, _bitfield2: 0 }`', examples\src\bin\hello-directstorage.rs:238:9

I fixed this here: #2168

Awesome!  Do you know how far away this is from being in a release?

Releases are now on-demand: https://github.com/microsoft/windows-rs/issues/2156#issuecomment-1323816991
As Rafael points out, best to use a git dependency until you've worked out any kinks and are ready to go.
Once you're fairly confident that windows-rs provides the fixes you need, I'm happy to publish another release.

Thanks guys - I've switched to the latest git version and this is indeed working for me now.


RFC - Features I am working on

Once the current dev (or master) branch is working properly again (at the moment, the dev branch seems to just skip pokemon, and master has the session token expire after an hour, so I'm currently stuck on my own branch), I will be working on the following for possible submission:

[ ] Remote control - this will allow the creation of a simple file with a list of locations you can populate for the bot to "hunt". useful for providing a list of pokemon locations containing pokemon you want to catch. Instead of the bot looking for the next pokestop, it will head towards the next in the list.

[ ] Transfer limit - Instead of keeping the best one of each type, this will be configurable so you can keep your best two of each type (like I do)

[ ] Evolve before transfer - At present, the bot starts up, transfers all but one of each type (if specified) and then each loop checks for any evolutions. It would make much more sense to evolve first, and then discard any lower CP dupes and not have this run in each step. Possible re-running this evolve and transfer when the pokemon storage is full.

[ ] Travelling salesman algorithm - Given a list of pokestops, have the bot calculate the best route between them to maximise farming in a given area.

[ ] Command line args override - This one drives me bonkers having to edit the config every time I want to run the bot! It would be better I think to have the bot read the config file and then check the args for any overrides.

[x] Keep pokemon of any type if none in bag! - Currently if you come across a pokemon and it doesnt meet your CP / IV requirements, it gets discarded regardless! This is not good, I've "lost" various pokemon not yet in my collection due to the bot discarding even though I have none of that type. Should probably be kept the same way as the transfer limit as above so if you come across something youve not seen before, you still get to keep it.

I am not expecting any of these to be done by any others, these are not feature requests, but things I am currently working on to try to make the bot better for us all.

+1. Whoever pushed the changes to requiring a lame JSON file should be shot.

My main gripe with the farming of the bot currently is that it doesn't farm all the pokestops in an area (watching the web map submodule). The Traveling Salesman algorithm would be an amazing addition to the bot and seem more "human-like" (hopefully not walk across water either).

(hopefully not walk across water either)

You don't carry a boat with you when you walk around?

Evolve before transfer make a ton of sense.

The traveling salesman problem is np hard. I would suggest to use the prim algorith to compute a minimal spanning tree with the bots location and the pokestops location as nodes. Then  the bot can visit each node from the resulting tree in preorder.

The evolve feature should be smarter.

@alexejw - It is NP hard but we can be use an existing algorithm (pytsp comes to mind) to get a "good enough" solution. We don't want perfection, we just want something a bit better than randomly hitting pokestops all over town.

@Nurvx I agree, if the lucky egg flag is set then we should save all evolves to do at once.
Maybe a pidgey mode...

@MikeDX my thoughts about it: do your features as modular as possible.
About Travelling salesman algorithm: one guy on working on walking with Google Directions, I think he's work is better than a raw salesman algorithm because it calculates the best REAL walking route from point to point. If you still want to work on this, please try to follow the separation we did between Navigator (calculates final destination, can be Spiral farming, Square farming, something to walk from one city to another, etc) and Walker (walk step by step to final destination, this is where your travelling salesman algorithm would go, IMHO)

@MikeDX remote control will be implemented later through web sockets. So I kindly ask you to wait for this. We already agreed on doing it with web sockets, but there are much more important refactorings and features that have higher priority.

@MikeDX  I agree that you can approximate the tsp. The suggestion with the prim-algorithm and then traversing the resulting tree in preorder will give us a tour, that is maximal double of the length of the minimum tour.

@douglascamata Don't worry, I have learned from the login issue :)
A best "real" route may not be "better" in some respects though, if we are just looking to farm all pokestops in a given area as quickly as possible. There was talk about having multiple navigation options, so I guess that would just be a decision made in the config as to which pokenav to use when deciding where to go.
I'm not going to work on anything in particular at the moment, as I said, the current dev and master branches are a mess as it is - hence this being an RFC and nothing more for the time being.
The command args vs config thing though really does drive me crazy...

@alexejw pytsp pre-calculates the list of pokestops to visit too - am I missing something?

@MikeDX yes yes, but remember that Navigators just tell Walkers in what direction to go. So a travel salesman algorithm is a Walker, not a Navigator. Google Direction algorithm is also a Walker, not Navigator. They seem a bit overlapping, but are very different. I hope you understood.

@douglascamata That seems backwards to me, I would have thought the navigator gives the walker the new location to head to, which it does until it reaches that point and then moves to the next? Why would a navigator tell the TSA which way to go? Shouldn't the TSA tell the walker where the new point is?

@MikeDX the problem with pytsp is, that it is a interface to external solvers you can install. But the two listed solvers are only for academic use. We must implement a solver ourselves or use an open source solver with the right licence.

@alexejw Ah yes, I forgot about that issue...

@MikeDX did you check the Navigator examples that I gave? The navigator decides which place you want to reach from the current location. The walker traces and walk (slowly) the route from current location to final destination, stopping at every small step for interaction with cells nearby (that doesn't require more movements).

@douglascamata That seems to work well for a google navigation walker since it only wants to go from A to B but a TSA would have a list of A B C D etc to tell the walker where to go, so that's where the confusion lies. Your google direction algorithm makes sense to "walk" from pokestop A to B using the roads, but the TSA would want to just tell the walker where the next one is on its list of locations (in this case the walker would just be a straight line or whatever)

@MikeDX oh shit, now I understand. But there is a workaround. Let's say TSA walker works like this: given an array of N-points, it applies the algorithm as expected and walk the route. Then it's the navigator responsibility to give as much points as possible to have the best route. If the worst situation it gets the best route between 2 points.

@MikeDX this ways it works perfectly for farming, because you know where all the pokestops you want to go are. You can even add pokestops that you don't know at runtime and reapply TSA to increase you farming route.

@douglascamata @MikeDX if we reapply TSA with added pokestops we must exclude the pokestops with cool-down for 5 minutes.

This I why I love RFC.
@douglascamata So the TSA walker also needs a TSA navigator? Assuming the standard navigator only supplies 2 points (or one!). I am guessing that is what currently happens.
If we exclude the pokestops with the 5 minute cooldown we need to factor in how long it will take to get to that pokestop on the given route.. But I agree it needs to be taken into consideration - at present I have seen the bot bounce between two stops

@MikeDX The TSA walker works with any navigator. But to really take advantage of TSA the navigator needs to provide a good amount of points. As I already said, IMHO, perfect for farming. Did you have any objective with TSA before suggesting it? I would like to know.

@douglascamata The only real objective was to make the bot more efficient in a small area, just to maximize the stops visited and minimise steps taken - given that we need to travel at a (relatively) slow pace, it seems like a sensible option.

@MikeDX we could make two groups of pokestops. One with cooldown. One without. Calculate for both the tsp approximation. Start visiting the pokestops without cooldown and at the end go to the start point of the tsp with cooldown. Of course with the shortest cooldown. It is just a idea and I do not know how good the idea is.

in the context of above...
if navigator wants to take a decision when to send a walker...  i expect naturally it will use the distance to take that decision...
thus each walker should implement their own distance calculator method that will be callled by the navigator...
does this make sense?
(in the polylinewalker i implemented such a method because the walk is not in a straight line...)

Why is this closed?

Lots of things in this PR were implemented already, we only miss TSA.

@douglascamata I think that's a fair reason :)


proposal: support "var identifier = _" to mute an identifier in certain scope.

This is helpful to avoid using some identifiers which should be used in some scopes carelessly.
Example:
package main

func main(){
	var n = 123,
	// use n

	{
		// use n

		var n = _
		// now n disppears
	}

	// here, n is still alive
	// use n
}

you can simply shadow your variables
var n = 123
{
	// use n

	n := n // or var n = n
	// now the real n can no longer be accessed
}
// here, n is still alive

https://play.golang.org/p/KOUBa5TVIv

you can simply shadow your variables
it is not totally the same

How about
const n = 1i // complex number

or
n_ := n
\\ no longer allowed to use/change n
if n != n_ {
    panic("n was modified")
}

I still don't get your use case.

Maybe you also want to solve it like this:
https://play.golang.org/p/r1cG8oPS8I

Put this into any of your *_test.go files
func use(...interface{}) {}

Silent the unused variable(s) error anywhere by writing
use(n, o, p)

Bonus: The program does not build when not testing.

a more detailed example:
package main

func main(){
	var n = 123
	n++ // use n

	{
		n++ // use n

		var n = _ // this one will change spec few
		// now n disppears

		n++ // compiling error: n is undefined
	}

	// here, n is still alive
	n++

	var n = _ // // this one will change spec much
	// now n disppears

	n++ // compiling error: n is undefined

}

It is like the "unset" in some languages.

use unnamed vars
var n int
_ = n

var n int; _ = n

I already got what you want to accomplish, but I don't get what it is good for.

I already got what you want to accomplish, but I don't get what it is good for.

just let compiler report errors, just like the two error lines in my example. :)

@mattn,

use unnamed vars

This is not my intention.

@cznic, I don't get your code.

@cznic, I don't get your code.
It's also only for using unused vars, so not what you want.

Sorry, previous discussions of overloading _ to mean new things (such as the zero value when _ is used on the RHS) have been rejected. This is similarly not an acceptable language change.

@bradfitz, I think this one is more reasonable.
The underscore "_" is used in many cases now, but it is unnamed.
I think "deaf identifier" is a good name.

var _ = v // deaf variable can't hear anything

var v = _ // v becomes deaf too.

@stemar94,

I already got what you want to accomplish, but I don't get what it is good for.

here is a useful case in reality:
func DoTrasaction(db *sql.DB, sqlStr string) error {
	tx, err := db.Begin()
	if err != nil {
		tx.Rollback()
		return err
	}

	var db = _
	// if db can be unset, then we can safely avoid misusing tx as db in following lines

	// many callings of code
	// ...

	// we should call this
	tx.Exec(sqlStr)
	// but not this
	db.Exec(sqlStr) // if db is not unset, this line is ok
	                // for sql.DB and sql.Tx both has a same Exec method

	// ...

	err = tx.Commit()
	if err != nil {
		return err
	}

	return nil
}

You could do: db = nil. Or break the function up into smaller ones with more limited scopes.

ye, there are some ways to avoid this problem, but the unset solution is cooler, ;)


UPDATE remove guzzle requirement

guzzle should be covered by the Silverstripe installation

This should be ok to merge.  #92 should fix the broken test


Please avoid node dependency to "natives" module

Hi,
I am a developer on VSCode and wanted to reach out to inform you that this extension is either using or having a dependency to a node module "natives" that will soon no longer be supported in VSCode once we updated to node.js 8.x (as part of our Electron 2.0 update which is planned for the near term).
The full graph is:
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └─┬<EMAIL_ADDRESS>        └──<EMAIL_ADDRESS>
It would be great if this dependency could be avoided by either not depending on it anymore or updating the dependencies to newer versions so that this module is no longer pulled in.
As soon as any code in your extension (including node_modules) calls require("natives") we will throw an exception to prevent this module from getting loaded.
If this is just a devDependency and the module is never loaded in production, then you can ignore this issue and just close it!
More details in https://github.com/Microsoft/vscode/issues/47569
Thanks!
Ben
VSCode Team

Looks like this will involve getting xqlint to update update-notifier to a more recent version.

Released in v2.0.0-preview.3.

@DotJoshJohnson thanks


feat(vue-tel-input): emit event objects for standard events

This pull request proposes to include the actual event objects when emitting blur, focus, enter and space. This gives developers more control over side effects that may be triggered by those events.

thanks @erikbjoern! could you help include the changes in the docs too, please? https://github.com/iamstevendao/vue-tel-input/blob/main/docs/usage/events.md


[BUG] Value overlapped in page Instance Manager Image

Describe the bug (🐛 if you encounter this issue)
In Longhorn UI go to page Setting -> Instance Manager Image, the first 2 value overlapped.

To Reproduce
Navigate UI through Setting -> Instance Manager Image
Expected behavior
Field 'Name' and 'State' not overlap
Log or Support bundle
N/A
Environment

Longhorn version: master-head
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Number of Longhorn volumes in the cluster: 0

Additional context
Appeared in v1.4.1 and v1.3.3-rc1 as well

@chriscchien Don't add backport label directly next time, but rather specify the milestone (1.3.3) instead and mentioned it also happened in 1.4.1 like what we did in 1.4.1 regression testing.
cc @longhorn/qa

Verified Pass in longhorn-ui master ea6768 as below now the instance-manager name not overlapped.


Unable to load PDB with non matching GUID

Version and Platform (required):

Binary Ninja Version: 3.1.3561-dev (if version is stable, please also test the latest development build via the "Update Channel" option)
OS: MacOS
OS Version: Monterey 12.4 (21F79)
CPU Architecture: M1

** Also tested on a Windows 10 x64 machine.  **
Bug Description:
Unable to load PDB when executable is not compiled with /debug flags, or when GUID does not match between the PDB and .exe file.
Steps To Reproduce:

Load an .exe file not compiled with /debug
Tools > Plugins > PDB > Load PDB is greyed out

Additional Information:
There was discussion on Slack on this topic and the consensus was to have this allowed and display a warning for the user.

Thanks for the issue. I know this request has come up before but I don't see it as currently tracked. This should be resolved for the next stable release.

This is resolved as of 3.1.3718-dev. The automatic PDB loader will check for matching guid + info in the exe, but if you manually choose to load a PDB it will warn you and allow you to load it anyway.


NPM package

Hello, could you please add this to npmjs.com?
Thanks.

I published this package as ng-password-strength.
@subarroca If you want me to transfer the package to you, let me know.


Fatal Error: NIOAny.swift, line 101

Expected behavior

Work like developed and running on OSX
All requests work

Actual behavior

Fatal error: tried to decode as type Request but found Request with contents other(AsyncHTTPClient.HTTPClient.Request(method:

Fatal error: tried to decode as type ByteBuffer but found IOData with contents other(IOData

Steps to reproduce
Run your Server on Linux via Docker (swift:latest, ...)

https://github.com/IBM-Swift/Kitura/issues/1465

If possible, minimal yet complete reproducer code (or URL to code)
Pretty simple RestRequest (SwiftyRequest) with responseObject and responseData
SwiftNIO version/commit hash
2.10.1
Swift & OS version (output of swift --version && uname -a)
Swift version 5.1 (swift-5.1.2-RELEASE)
Target: x86_64-unknown-linux-gnu
Linux e965e14a2285 4.9.184-linuxkit #1 SMP Tue Jul 2 22:58:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

that's a bug in async-http-client, I filed the issue over there as https://github.com/swift-server/async-http-client/issues/138


create a FCDM module

What is the name of your repository ?
https://github.com/12rambau/fcdm/
The name of your dashboard app
Forest Canopy Disturbance Monitoring (FCDM)
A short description of the app
Mapping all kind of canopy disturbances (natural or human induced) within (semi-)evergreen forests
Is your module requiring a GEE account ?
yes
Any comment you want to add
As usual, release on prod and master on test if possible
Please don't close the issue until I add the real documentation
maintainer checklist

[x] Name is set
[x] Description set
[x] Comprehensive README
[ ] 3 languages documentation files (can be empty)
[x] The module works with the default available Python libs
[x] Existence of a release branch
[x] check behaviour

Added

Can this be closed?


Only run average analyses for surfaces if at least 2 measurements

So far analyses for surfaces are only shown if there are more than one topography.
The system still attempts to run them which can lead to unexpected error messages like
Traceback (most recent call last):
  File "/app/topobank/taskapp/tasks.py", line 127, in perform_analysis
    result = analysis.function.eval(subject, **kwargs)
  File "/app/topobank/analysis/models.py", line 278, in eval
    return self._implementation(subject_type).eval(subject, **kwargs)
  File "/app/topobank/analysis/models.py", line 330, in eval
    return pyfunc(subject, **kwargs)
  File "/app/topobank/analysis/functions.py", line 750, in variable_bandwidth_for_surface
    result = average_results_for_surface(surface, topo_analysis_func=variable_bandwidth,
  File "/app/topobank/analysis/functions.py", line 580, in average_results_for_surface
    result_series.append(average_series_list(series_list, num_points=num_points, xscale='log'))
  File "/app/topobank/analysis/functions.py", line 489, in average_series_list
    interpol = interp1d(s['x'], s['y'], bounds_error=False)  # inserts NaN outside of boundaries
  File "/opt/conda/lib/python3.8/site-packages/scipy/interpolate/interpolate.py", line 536, in __init__
    raise ValueError("x and y arrays must have at "
ValueError: x and y arrays must have at least 2 entries

Solution: Only trigger the average analyses if there is more than one measurement.

This is not needed for v0.10.0, because in general this is visible to the user, since only surface analyses
are shown if there is more than one topography.


Add examples on working with attachments, options etc in ballerina/email package

Description:
Better if some examples can be added on working with attachments, options, etc in the ballerina/email package since the BBE content only covers a few basic concepts.
Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

As API docs cover all the remaining features like in other modules, we can consider adding more content to BBEs as required in the future.


Run pylint. Fixes #18

Coverage remained the same at 100.0% when pulling 72942cfff2091b3aae0b59898e81fc96fc1bb69a on travis into 4b182337bddb77e81b5b2d7a2b5fdd93ccffea19 on master.

Coverage remained the same at 100.0% when pulling 72942cfff2091b3aae0b59898e81fc96fc1bb69a on travis into 4b182337bddb77e81b5b2d7a2b5fdd93ccffea19 on master.

Coverage remained the same at 100.0% when pulling 72942cfff2091b3aae0b59898e81fc96fc1bb69a on travis into 4b182337bddb77e81b5b2d7a2b5fdd93ccffea19 on master.

Coverage remained the same at 100.0% when pulling 0bdf6e9e12c8e8240009ee6f2584f04b14426a64 on travis into 4b182337bddb77e81b5b2d7a2b5fdd93ccffea19 on master.


Add GPLv2+ and GPLv3+ as license options

Dolphin, PPSSPP, and MAME, for example, are all using "GPL version 2 or later". These are technically distinct choices from "just" GPLv2, as they allow derivatives to use any future version of the GPL.
This was a problem brought up by the GNU Project, so I thought it was an important consideration to suggest.
From GPLv2:
"9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation."
From GPLv3:
"14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version."

Almost forgot: AGPL 3-or-later as well. My understanding is that we can literally just copy-paste the existing licenses and append "or later" to the header and they'll be good to go.

My understanding is that we can literally just copy-paste the existing licenses and append "or later" to the header and they'll be good to go.

That's an interesting idea. Do I understand correctly you mean like:

GNU GENERAL PUBLIC LICENSE
Version 3 or later, 29 June 2007

Neither Google nor GitHub searches turn up any instances of "Version 3 or later, 29 June 2007".
If that'd work it'd probably be a nice solution. I'm aware of the problem, which has been raised a few times eg https://github.com/github/choosealicense.com/issues/5 and https://www.reddit.com/r/programming/comments/1icwbb/choosealicensecom_from_the_good_folks_at_github/cb3ctel
I'd thought of using other annotations to indicate + in a way that choosealicense.com could hand out and licensee recognize. I suspect anything that doesn't require parsing notices where "or later" are usually indicated (which is beyond the capability of these two projects to hand out and parse at this time) would merit feedback from<EMAIL_ADDRESS>which is what I intended to ask for if I had a plausible solution. Maybe this is it, but I'm wary, as the *GPLvx.y license texts aren't intended to be modified.

@mlinksva Lots of results here: https://github.com/search?utf8=✓&q=License+Version+2+or+later&type=Code&ref=searchresults

@mlinksva on a second read, I'm actually wrong. The license itself shouldn't say that, only the license name, as the "or later" is already included in the body of the license.
From this email from Mike Gerwitz of the FSF:

So to clarify/break down the requirements:

"GPL v2" should be changed to "GPL v2 or later", and ditto for "GPL v3".
The license text should also be changed to reflect this.

In the license listing, yes, "or later" should be added.
With regards to the "license text"---do you mean the text that'll be
placed in `LICENSE'?  If so, then no: that should be the GPL
verbatim.  The license itself isn't saying "or later"---it's the actual
notice on the source files themselves that says "you can use the version
of the GPL that I have provided, or you can use a future version
published by the FSF".
So you should recommend that "or, at your option, any later version" be
included, as recommended here:
https://www.gnu.org/licenses/gpl.html

TL;DR The request should actually be to change the name of the license, not the license body itself. Sorry! (I blame their terrible mailing list site formatting at least partially)


[BEAM-5658] Re-enable findbugs on Dataflow worker

This fixes or suppresses all findbugs warnings on the Dataflow worker. These commits should not be squashed. In the event of a need for rollback it should be isolated as far as possible. There are some actual functional changes, particularly where erroneous use of integer division is now double precision division.
If they look like potential bugs, there is a Jira filed and linked in a comment. This does not enable nonnull by default, so there are 100+ potential bugs lurking.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
 The build that shows here as yellow shows as red in 0 ms but also has a log that is just truncated halfway. And the build history for Dataflow ValidatesRunner PR includes just a few builds that are all very very old.

The only changes that pose a real risk are the changes from integer division to double precision as the code appears to intend. I will merge and prepare to roll those back if they expose issues.


Wrong normal over floor edge, no floor detected

Tested versions

Reproduclibe in: 4.2.1 and 4.3-dev6

System information
Debian GNU/Linux 12.5
Issue description
Collisions between the edges of rectangle shapes are obviously wrong. An object falling and being stopped by an edge can't have a normal pointing to one side (in the X axis). All movements and shape edges are parallel to axes. In this case, any object stopping another object from falling has to be floor and have a normal pointing up.
In the example project, the floor isn't detected at first for several frames, then it starts being detected. It stops the object from falling from the start though.
Steps to reproduce
Try the MRP with "visible collision shapes" on to be able to see anything. Run the project and see the movement of the objects in the window and the messages in the console output.
Minimal reproduction project (MRP)
collision_normal_test.zip

See also:

https://github.com/godotengine/godot/issues/69137

Setting the safe_margin to the lowest value 0.001 seems to be working. It still detects a collision but the calculated normal is correct and the object can keep moving along the edge.
It remains to be seen why the engine doesn't decide if it's a floor and the correct normal with a higher safe_margin.


No Fulltext search

Hi,
I have tried out the Workspace App from Google Play...
Sadly the search is only looking for filenames, not for fulltext info.

We search the name, title, description, the full text (if available) and tags.
You can look up the details here: SeachApi.kt
Please keep in mind you can only search in docs supported by the transform service: https://docs.alfresco.com/content-services/latest/admin/transformations/#standard

then it is an Bug... on the old content android app it works... on the aca mobile website ist works...
but workspace app only delivers title matches.

Having just tested this I can confirm the functionality works.
Having said that maybe our expectations are different, so please provide screenshots, reproduction steps, a more comprehensive description of your expectation and maybe a sample document for us to test with.
Reopening and marking as bug.

Hi, here are the screens... 13 matches on web app... 2 on android app

We actually expect some results to differ compared to ACA as our search query has been adjusted to match Share which provides more accurate results.
Do your documents actually contain the search term?
Do you mind comparing your results to Share?

Hi Alexandru,
I have compared the results.
On my alfresco setup I have a library of cooking recipes, many in spanisch language.
I have used tomate (spanish tomato) as search term.
With the aca website i got 108 results.
On share I got 106 results.
With the app I got only the 13 documents with the word in the title.
All files are PDFs.

and finally all results of the app:

Thank you for providing access to your data.
After some testing I can confirm this issue is related to localization.
We already have an internal bug opened, and will get back to you once I know more.
If you switch your browser to English you'll notice the search results match across platforms but your results no longer include the textual matches.

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}  Thank you for stay me informed.Would that mean, maybe other issues with special German characters i had noticed in the past could be, because the server is German localized?                                                                                Von: @.***Gesendet: 25. März 2021 18:32An: @.***Antworten: @.Cc: @.; @.***Betreff: Re: [Alfresco/alfresco-mobile-workspace-android] No Fulltext search (#12)
Thank you for providing access to your data.
After some testing I can confirm this issue is related to localization.
We already have an internal bug opened, and will get back to you once I know more.
If you switch your browser to English you'll notice the search results match across platforms but your results no longer include the textual matches.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

Maybe, you'd need to report the individual issues on the separate products for investigation which we encourage you to do.

For a more complete picture could you please provide the following:

version of your Content Services deployment
search engine information (from your admin console head over to Repository Services / Search Service and provide which Search Service you're using and Full Text Search config (bottom of the page))

Having spoken to one of colleagues in search it seems the problem stems from your data being indexed in another language.
This can be resolved by enabling cross language searches: Step 3 in this guide https://docs.alfresco.com/search-services/latest/install/options/

If you use several languages across your organization, you must enable cross-language search support in all fields. To do > this update the alfresco-search-services/solrhome/conf/shared.properties file:

 alfresco.cross.locale.datatype.0={http://www.alfresco.org/model/dictionary/1.0}text
 alfresco.cross.locale.datatype.1={http://www.alfresco.org/model/dictionary/1.0}content
 alfresco.cross.locale.datatype.2={http://www.alfresco.org/model/dictionary/1.0}mltext

Hi Alexandru,
it looks like, that this helps.
But why isn't this feature enabled by default?
I think all Setups will have more than one language in their documents.
Regards
Ingo

It's a good question that I already plan to discuss with the team.
For now marking this as resolved. Thank you for your patience.


Create RELEASE.md

Checklist:

[x] Code contains relevant tests for the problem you are solving
[x] Ensure all new and existing tests pass
[x] Update any relevant READMEs and docs
[x] Submit to the develop branch instead of master

Description:
Creates a release checklist

This will, of course, be an always-in-progress doc. But I'm goign to merge it as-is and let us iterate from there.


Fix the guid content in the README file

Signed-off-by: RcXu<EMAIL_ADDRESS>Description
As the guid in the README, the version of JDK is 1.5.0, but there is something wrong when use the package io.dapr.Rule;
and it's used in example file also。
when configure the 1.5.0 version, can't find the package but 1.6.0 is ok.
Please reference the issue this PR will close: #759

As there are zero changes, closing PR.


Why event and not context, req, res?

Now
export default defineEventHandler(async (event) => {
    const body = await useBody(event)
    return { body }
})

Why not
export default defineEventHandler(async ({ context, req, res }) => {
    const body = await useBody(req) // req or context or what is used here
    return { body }
})

Why event.context.params.name and not request.params.name?

There are several considerations in API design:

Keeping event a generic namespace for future proof API (https://github.com/unjs/h3/issues/81)
Keeping event.context as an open namespace for plugins and utils such as router to be extended
Avoid modification of Node.js built-in req object nor advice to depend on it
(from your example) Also avoid destructre event object as { context, ... }) it is to be passed around as is consistent. Destructing prevents that and makes problem you first mention why event.* and not XYZ.* (XYZ a subkey of event)


atosl: subprograms.c:141: dwarf_errmsg: DW_DLE_VERSION_STAMP_ERROR (48)

i use atosl like this,
atosl -o SomeApp.app.dSYM/Contents/Resources/DWARF/SomeApp --load-address 0x3c00 0x12345 0x55555
it's give me "atosl: subprograms.c:141: dwarf_errmsg: DW_DLE_VERSION_STAMP_ERROR (48)"
but i use -g ,
atosl -g -o SomeApp.app.dSYM/Contents/Resources/DWARF/SomeApp --load-address 0x3c00 0x12345 0x55555
it's give me "atosl: subprograms.c:235: dwarf_errmsg: DW_DLE_PUBNAMES_VERSION_ERROR"
how to fix it? i don't why?

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

I'm going to close this for now. I did notice that there have been a number of updates to libdwarf as well, so if you do run into it, try running the latest version from http://www.prevanders.net/dwarf.html.


For building only rocksdb_replicator from rocksplicator, Does it require both fbthrift and thrift

I am only building rocksdb_replicator and common modules from rocksplicator in my own debian environment. I installed both fbthrift and thrift according to docker file. I am getting undefined reference to
CMakeFiles/thrift_router_test.dir/thrift_router_test.cpp.o: In function apache::thrift::server::TConnectionContext::setHeader(std::string const&, std::string const&)': /usr/local/include/thrift/lib/cpp/server/TConnectionContext.h:77: undefined reference to apache::thrift::transport::THeader::setHeader(std::string const&, std::string const&)'
CMakeFiles/thrift_router_test.dir/thrift_router_test.cpp.o: In function apache::thrift::server::TConnectionContext::getHeader() const': /usr/local/include/thrift/lib/cpp/server/TConnectionContext.h:69: undefined reference to typeinfo for apache::thrift::transport::THeader'
/usr/local/include/thrift/lib/cpp/server/TConnectionContext.h:69: undefined reference to typeinfo for apache::thrift::transport::THeader' thrift/libdummy_service_thrift.a(DummyService.cpp.o): In function apache::thrift::HandlerCallbackBase::transform(folly::IOBufQueue&)':

I added -L to the lib directory. It worked.


any status update on react components from #920?

I was wondering if there was a status update on https://github.com/algolia/instantsearch.js/issues/920?
It sounded like there would be something available in july but my search didn't turn anything up.
If it isn't ready yet, does anyone have alternative suggestions? I'm using react and redux at the moment (with meteor).

Hey,
I'm currently working full time on bringing Instantsearch to React. You can track my progress on the instantsearch-react* branches.
If everything goes as planned, we should have something out by the end of August.
For now, you can use the react-algoliasearch-helper. It's largely inspired by Redux, and allows you to connect your UI components to the state of an algoliasearch-helper.

Great news!


Use interact() with Short-Cadence Data

Problem description
When attempting to use intereact() on short-cadence TPF file, a RunTimeError comes up due to having more than 20,000 cadences.
Example
from lightkurve import KeplerTargetPixelFile
tpf=KeplerTargetPixelFile("ktwo212460519-c17_spd-targ.fits")
tpf.pipeline_mask
tpf.interact()

 BokehJS 0.12.16 successfully loaded.
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-141-79d3753be6aa> in <module>()
      4 tpf=KeplerTargetPixelFile("ktwo212460519-c17_spd-targ.fits")
      5 tpf.pipeline_mask
----> 6 tpf.interact()
      7

/home/jeff/anaconda2/lib/python2.7/site-packages/lightkurve/targetpixelfile.pyc in interact(self, lc)
    459         # https://github.com/bokeh/bokeh/issues/7490
    460         if len(lc.cadenceno) > 30000:
--> 461             raise RuntimeError('Interact cannot display more than 20000 cadences.')
    462
    463         # Map cadence to index for quick array slicing.

RuntimeError: Interact cannot display more than 20000 cadences.

Expected behavior
Ideally either a TPF could be trimmed to only include a certain cadence or time range, or interact() could have a variable that controls only including every Nth data point, or intereact() could have a cadence or time range as an input. Any of these options could get cadences < 20000 to allow interact() to work and perform smoothly.
Environment:

Linx
1.0b9
pip

At the CoolStars20 hack day, @nattieg and @rrpastro worked on this Issue alongside the "pixel selector" functionality.  Pull Request  #216 contains a Jupyter notebook demoing some of the approaches we tried.

Some additional comments from @nattieg provided by email:

Looks like other folks are interested in a range slider widget that I envisioned on Saturday:
https://github.com/jupyter-widgets/ipywidgets/issues/1351

In particular the implementation shown here is pretty perfect: http://jsfiddle.net/omnosis/Swd9S/

If this also allows for a max range to be set, it would be a super slick implementation of what we were doing at the hack day. A reminder, that we wanted to make the interact function usable for short or long-cadence light curves, but we have to limit the amount of the short cadence curve shown due to memory issues. So, if the maximum range allowed was, say, 10000, with a range slider the user could look at any range up to that value and drag the bar back and forth to see different regions of the light curve.

To make what is currently there a little more user-friendly, this morning I pushed a change making the range setting optional. If the ranges aren't defined by the user they default to 0-3000, which covers most of the range for long-cadence targets.

Nice!!  Thank you @nattieg and @rrpastro !! :+1:

The new .interact() tool that is about to be released ( #216 ) does not support short cadence yet.  The next step for interact is to add a module that detects whether the input TargetPixelFile is short cadence and, if so, adds a slider like the one @nattieg made at cool stars.  Using bokeh widgets makes this task much easier now, so I am confident we will be able to resolve this issue soon.

Hooray!  The recent TPF slicing feature has made it possible to use interact in short cadence!
Before-- without TPF slicing
len(tpf.cadenceno)
115213

tpf.interact() # Does not work -- too many cadences!
RuntimeError: Interact cannot display more than 30000 cadences.

New behavior with TPF slicing
# works with manual index slicing
tpf[1000:4500].interact()  # This works!

# works with boolean masking
mask = (tpf.time > 3298) & (tpf.time < 3300)
len(tpf[mask].cadenceno)
2919

tpf[mask].interact() # This also works!

Known Limitations

It'd be nice to be able to define the slicing windows on the fly, i.e. with the range sliders suggested above.  That's possible!  We can do it if there's user interest.
Slicing with non-unit steps has undesired effect of "greying-out" the missing cadences, for example if you want to show every 30th cadence, the other 29 are shown as gray postage stamps, instead of dropped.

undesired behavior
tpf[::30].interact() # Does not work!

I'm going to close this issue since Short Cadence interact is now possible, albeit with some loss of the "big picture".  If anyone out there wants a range slider for interactively defining the short cadence data window size, please open an issue requesting this feature.
Note that this slicing should work for both Kepler/K2 and TESS data!  Enjoy!


Hot fix librmm packages missing spdlog dependency

Follow up to PR ( https://github.com/conda-forge/librmm-feedstock/pull/5 )
The spdlog version used by librmm lacked run_exports. While subsequent librmm packages have been fixed to explicitly include spdlog and future versions of spdlog do have run_exports, the original librmm packages still need to be hot-fixed to include spdlog, which is what is done here.
cc @leofang @rlratzel @kkraus14

Checklist

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

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

Running show_diff.py locally, am seeing the following
linux-64::librmm-0.19.0-h1a5f58c_1.tar.bz2
-    "thrust >=1.9.0"
+    "thrust >=1.9.0",
+    "spdlog =1.7.0"
linux-64::librmm-0.19.0-h8b44402_1.tar.bz2
-    "thrust >=1.9.0"
+    "thrust >=1.9.0",
+    "spdlog =1.7.0"
linux-64::librmm-0.19.0-h96e36e3_1.tar.bz2
-    "thrust >=1.9.0"
+    "thrust >=1.9.0",
+    "spdlog =1.7.0"
linux-64::librmm-0.19.0-h97a9cb7_1.tar.bz2
-    "thrust >=1.9.0"
+    "thrust >=1.9.0",
+    "spdlog =1.7.0"
linux-64::librmm-0.19.0-hdc17891_1.tar.bz2
-    "thrust >=1.9.0"
+    "thrust >=1.9.0",
+    "spdlog =1.7.0"


Unit Test Hangs When Retrieving Undefined Service Metadata Name

What happened?
My unit test hangs (deadlock?) when attempting to retrieve a service's metadata name, which happens to be undefined.
Expected Behavior
Accessing an undefined value should return a default value or throw an error.
Steps to reproduce
See gist
Output of pulumi about
CLI
Version      3.66.0
Go Version   go1.20.3
Go Compiler  gc
Host
OS       Microsoft Windows 10 Pro
Version  10.0.19045 Build 19045
Arch     x86_64
Backend
Name           pulumi.com
URL            https://app.pulumi.com/Afford2945
User           Afford2945
Organizations  Afford2945, RivalCoins
Pulumi locates its logs in C:\Users\Jerome\AppData\Local\Temp by default
warning: Failed to read project: no Pulumi.yaml project file found (searching upwards from C:\Users\Jerome). If you have not created a project yet, use pulumi new to do so: no project file found
warning: Failed to get information about the current stack: no Pulumi.yaml project file found (searching upwards from C:\Users\Jerome). If you have not created a project yet, use pulumi new to do so: no project file found
warning: A new version of Pulumi is available. To upgrade from version '3.66.0' to '3.68.0', visit https://pulumi.com/docs/reference/install/ for manual instructions and release notes.
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Copying gist here for posterity;
using Grpc.Core;
using NUnit.Framework;
using Pulumi;
using Pulumi.Testing;

namespace PulumiBug;

public static class ExtentionMethods
{
    public static TValue Value<TValue>(this Output<TValue> output) => GetValueAsync(output).Result;

    public static Task<T> GetValueAsync<T>(this Output<T> output)
    {
        var tcs = new TaskCompletionSource<T>();
        output.Apply(v =>
        {
            tcs.SetResult(v);
            return v;
        });
        return tcs.Task;
    }
}

public class MyStack : Stack
{
    public MyStack()
    {
        var service = new Pulumi.Kubernetes.Core.V1.Service("MyServiceName", new());
    }
}

public class Mocks : IMocks
{
    public Task<object> CallAsync(MockCallArgs args)
    {
        return Task.FromResult((object)args.Args);
    }

    public Task<(string? id, object state)> NewResourceAsync(MockResourceArgs args)
    {
        return Task.FromResult((args.Id, (object)args.Inputs));
    }
}

[TestFixture]
public class Class1
{
    [Test]
    public async Task Test1()
    {
        var results = Pulumi.Deployment.TestAsync<MyStack>(new Mocks()).Result;

        var service = results.OfType<Pulumi.Kubernetes.Core.V1.Service>().First();
        var metaData = await service.Metadata.GetValueAsync();

        Assert.AreEqual("MyServiceName", metaData.Name);
    }
}


Update Makefile

drops unnecessary .PHONY

? it's not unnecessary, it lets you run the same command and recompile each time.


black screen was appeared when swipe too fast in demos/customanimation2

Hi, I found that the black screen is appeared, when I swipe the page too fast. Is there any solution for this? Thanks

If anyone's interested, this solution did it for me:
http://stackoverflow.com/questions/5380994/how-to-stop-the-swipe-event-in-jqtouch-whilst-a-slide-transition-is-occuring


[web3t] Fix inconsistent pricing

If I download a file that claims to "cost" 1300 wei, why do I end up paying far more than that? (Paying a little more is expected and probably ok, since we are using a basic buffered payment system).

Might get fixed alongside #1133 .

When the seeder blocks the leecher and then gets re-enabled, the leecher re-sends a lot of requests (some repeated) that shouldn't be resent, paying for stuff he already paid a bunch of times.
This gets worse when the leecher gets blocked several times (for big files, for example).
It seems that we didn't notice before, because the difference was pretty small 'till last week (because I used small amounts), and before that, the money was totally fake :confused:  .


Populate Objects to Rename via Search

Once selected objects have been reworked to not always take the selection, we could add the ability to add files from a search. This would probably be another button from inside the Selection Preview pane called "Find Objects" which would popup a utility window. The utility window should probably preview the objects it finds in a simple scrollview, and then you confirm it ("Add Objects") to add them to the selection. Possibly you could allow them to uncheck objects it found but that's a narrow use case. It would probably be better to allow them to uncheck objects in the preview pane and let them do it through that.
For an example of this type of use case, see: https://www.assetstore.unity3d.com/en/#!/content/84549

This was originally a suggestion from a user, but I haven't heard any other requests for it in a while. I personally it's an acceptable workflow to search Hierarchy and Project windows and then drag and drop the results into Mulligan. So I'm going to close this for now.


Auto-expand all 'details' information for projects

Right now, two of the five categories are auto-expanded when you click on 'details':

However, none of the exposed information is particularly interesting (IMO).  I would put 'Identifiers, citations, and license' at the top, and expand it, then the 'Methods and Tools', expanded, then the Model/simulation, expanded.
Finally, I'd put  'simulation run' and 'provenance' at the bottom, and probably go ahead and expand them?  But if you like it a bit more compact, then those are the ones I would leave collapsed.

I felt the same way about this. I selected the pre-opened panels based on the wishes of the team here at UConn. I would like to keep some panels closed on render to both keep the compact look and also prompt the user to interact with this reactive set of components. Personally, I would like to keep only Methods & tools and Simulation run panels open as I believe them to be the most informative in regard to the nature of the simulation itself.

:tada: This issue has been resolved in version 9.52.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Cannot config completer property of argument.

Current
c.argument('circuit_name', type=str, help='The name of the circuit.')

Prefer
c.argument('circuit_name', type=str, help='The name of the circuit.', completer=get_resource_name_completion_list('Microsoft.Network/expressRouteCircuits'))

Plan to support in the following way:
cli:
cli-directive:
- where:
group: groupName
feature:
completer: completer_name
validator: validator_name

Plan to support in the following way:
cli:
cli-directive:

where:
group: groupName
feature:
completer: completer_name
validator: validator_name

How can you find completer function only by it's name? Do you need import path?

Plan to support in the following way:
cli:
cli-directive:

where:
group: groupName
feature:
completer: completer_name
validator: validator_name

How can you find completer function only by it's name? Do you need import path?

cli:
  cli-directive:
  - where:
        group: groupName
     feature:
        completer: completer_name
        validator: validator_name
        imports:
            - azure.cli.core.completer.MyCompleter
            - azure.cli.core.validator.MyValidator

how about something like this?


offlineimap: 7.0.6 -> 7.0.9

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

/me testing if it builds on osx


Petr4 should catch name shadowing

Tests failing because of this:

examples/checker_tests/bad/issue1541.p4
examples/checker_tests/bad/template_e.p4
examples/checker_tests/bad/issue1932.p4
examples/checker_tests/bad/accept_e.p4
examples/checker_tests/bad/dup-param.p4
examples/checker_tests/bad/dupConst.p4

Marking this unsupported mostly because the spec is ambiguous and I'm not sure how strict I would want petr4 to be about it.

Raising an error for duplicated parameters in a single declaration or for duplicated type parameters in a single declaration deals with most of these.


You appear to have CocoaPods installed but it is not working.

          Hi @janpio, I had the same issue and I fixed after uninstalling cocoapods and adding `gem "cocoapods"` to the Gemfile and installing it via `bundle install`. Hope it helps.

Originally posted by @jorgefspereira in https://github.com/fastlane/fastlane/issues/16683#issuecomment-661751872
Warning: CocoaPods is installed but broken. Skipping pod install.
  You appear to have CocoaPods installed but it is not working.
  This can happen if the version of Ruby that CocoaPods was installed with is different from the one being used to invoke it.
  This can usually be fixed by re-installing CocoaPods.
To re-install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

CocoaPods not installed or not in valid state.

        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/helper/sh_helper.rb:80:in `sh_control_output'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/helper/sh_helper.rb:16:in `sh_no_action'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/fast_file.rb:223:in `block in sh'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/fast_file.rb:222:in `sh'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/fast_file.rb:216:in `sh'
        from Fastfile:103:in `block (3 levels) in parsing_binding'
        from Fastfile:100:in `chdir'
        from Fastfile:100:in `block (2 levels) in parsing_binding'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane.rb:41:in `call'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/command_line_handler.rb:34:in `handle'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:110:in `block (2 levels) in run'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:354:in `run'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/commands_generator.rb:43:in `start'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in `take_off'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/gems/fastlane-2.219.0/bin/fastlane:23:in `<top (required)>'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/bin/fastlane:25:in `load'
        from /opt/homebrew/Cellar/fastlane/2.219.0_2/libexec/bin/fastlane:25:in `<main>'

I tried this method and it didn't work. Is there any other effective method?

gem uninstall cocoapods
gem install cocoapods
I reinstalled cocopods like above and added the gem "cocoapods" to the Gemfile and it didn't work.


Use Linux i386/AMD64 binaries on FreeBSD.

FreeBSD can natively emulate Linux ELF binaries.
This commit allows automated Linux tools deployment on FreeBSD.
Signed-off-by: Tomasz 'CeDeROM' CEDRO<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your contribution.

I can confirm that this commit allows build Zephyr for ESP32 on FreeBSD using Linux toolchain when following instructions provided in the official Zephyr HandBook are met: https://docs.zephyrproject.org/latest/boards/xtensa/esp32/doc/index.html. It is very important to setup environmental variables as instructed :-)
It may be really nice to add west espressif path command that would quickly return full path to the xtensa toolchain location on the filesystem (installed with west espressif install), so that could be passed to set up the environment scripts before build :-)
If you are the authors of the west espressif part please consider such option :-)

cc @sylvioalves for west espressif part

@cederom yes, it was: https://github.com/zephyrproject-rtos/hal_espressif/pull/44

System default Python:
% python
Python 3.8.12 (default, Sep 11 2021, 01:14:09)
[Clang 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c on freebsd13
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> PYTHON_PLATFORM = platform.system() + '-' + platform.machine()
>>> print(PYTHON_PLATFORM)
FreeBSD-amd64

VEnv Python:
% zvenvsdk.sh venv
(venv38zephyr) python
Python 3.8.12 (default, Sep 11 2021, 01:14:09)
[Clang 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c on freebsd13
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> PYTHON_PLATFORM = platform.system() + '-' + platform.machine()
>>> print(PYTHON_PLATFORM)
FreeBSD-amd64

Okay, that was problem with my local Zephyr Env launcher script, I have removed and re-created everything from scratch and it works now! :-)
SORRY, and THANK YOU for your time @sylvioalves !! :-)
I can see that this ESP-IDF is a core for Zephyr and NuttX. Sweet! :-)
I would like to try ESP32-C3 / RISC-V on both Zephyr and NuttX :-)
Quick question what toolchain env variable should I use for riscv on Zephyr do you know? :-)

(venv38zephyr) west espressif install
=== downloading ESP-IDF tools..
Installing tools: xtensa-esp32-elf, xtensa-esp32s2-elf, riscv32-esp-elf, openocd-esp32
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
Skipping<EMAIL_ADDRESS>(already installed)
=== downloading ESP-IDF tools completed
The toolchain has been downloaded to /home/XXX/.espressif/tools/zephyr
Export or set the following variables into the environment:
export ESPRESSIF_TOOLCHAIN_PATH="/home/XXX/.espressif/tools/zephyr"
export ZEPHYR_TOOLCHAIN_VARIANT="espressif"

Blinky nor Hello World does not build yet, but I have a good starting point, thank you @sylvioalves ! I will return with success or when Im stuck :-) Thank you!! :-)


fix: typescript definitions

This should make the typescript definitions at least useable. Currently they seem to be quite broken (per #69, #67 )
Closes #54
Closes #47
Closes #69
Closes #67
Closes #62

Adds examples/typescript and build in CI step
Fixes definitions (trying to set defaults, chatStream returning wrong type)
Add signal (per #68) to typescript definitions
Fix interfaces (non-exhaustively) per: https://docs.mistral.ai/redocusaurus/plugin-redoc-0.yaml

@fuegoio
Please look :)

I suppose someone put "name" in there for OpenAI compat reasons at some
point, though it is just misleading, and also not necessary

Message ID: @.***>

Oh right, yeah, the enums aren't even defined at runtime are they. I added
literals (for ergonomics) and left the enums in there and moved on. They
are completely broken though aren't they.
A good argument to move to TS :)
On Tue, 7 May 2024, 2:51 pm Nicholas Dudfield, @.***>
wrote:

I suppose someone put "name" in there for OpenAI compat reasons at some
point, though it is just misleading, and also not necessary

Message ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/mistralai/client-js/pull/72#issuecomment-2097669949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEAHG6QYRPI5CS72RB4DX3ZBCBWLAVCNFSM6AAAAABHKCIQK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXGY3DSOJUHE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Oh right, yeah, the enums aren't even defined at runtime are they. I added literals (for ergonomics) and left the enums in there and moved on. They are completely broken though aren't they. A good argument to move to TS :)

In a d.ts file they do not make much sense no. I approve moving to TS to have this kind of nice feature.

@fuegoio
Anything else? I'll look at a full TS port when I have more time

Oh, wait, that's not working, enums still referenced, but no errors, hrmmm

I'll look at a full TS port when I have more time

In a separate PR, to be clear