No jupyter_server.prometheus

$ phoila install .
Traceback (most recent call last):
  File "/usr/local/miniconda3/envs/ibis-vega-transform/bin/phoila", line 6, in <module>
    from phoila.app import main
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/app.py", line 5, in <module>
    from .serverapp import ServerApp
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/serverapp.py", line 70, in <module>
    import jupyter_server.prometheus.metrics
ModuleNotFoundError: No module named 'jupyter_server.prometheus'
$ pip freeze | grep jupyter-server
jupyter-server==0.1.1
$ pip freeze | grep phoila
phoila==0.3.0

If I do a dev install of jupyter server this works. So I guess the most recent released version of phoila depends on an unreleased version of jupyter server?
$ pip install git+https://github.com/jupyter/jupyter_server.git
Collecting git+https://github.com/jupyter/jupyter_server.git
  Cloning https://github.com/jupyter/jupyter_server.git to /private/var/folders/m7/t8dvwtnn32z84333p845tly40000gn/T/pip-req-build-rz6yptc5
  Running command git clone -q https://github.com/jupyter/jupyter_server.git /private/var/folders/m7/t8dvwtnn32z84333p845tly40000gn/T/pip-req-build-rz6yptc5
  Running command git submodule update --init --recursive -q
Requirement already satisfied: jinja2 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (2.10.1)
Requirement already satisfied: tornado>=5.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (5.1.1)
Requirement already satisfied: pyzmq>=17 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (18.0.2)
Requirement already satisfied: ipython_genutils in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (0.2.0)
Requirement already satisfied: traitlets>=4.2.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (4.3.2)
Requirement already satisfied: jupyter_core>=4.4.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (4.4.0)
Requirement already satisfied: jupyter_client>=5.3.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (5.3.1)
Requirement already satisfied: nbformat in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (4.4.0)
Requirement already satisfied: nbconvert in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (5.6.0)
Requirement already satisfied: ipykernel in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (5.1.2)
Requirement already satisfied: Send2Trash in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (1.5.0)
Requirement already satisfied: terminado>=0.8.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (0.8.2)
Requirement already satisfied: prometheus_client in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter-server==0.2.0.dev0) (0.7.1)
Requirement already satisfied: MarkupSafe>=0.23 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jinja2->jupyter-server==0.2.0.dev0) (1.1.1)
Requirement already satisfied: six in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from traitlets>=4.2.1->jupyter-server==0.2.0.dev0) (1.12.0)
Requirement already satisfied: decorator in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from traitlets>=4.2.1->jupyter-server==0.2.0.dev0) (4.4.0)
Requirement already satisfied: python-dateutil>=2.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jupyter_client>=5.3.1->jupyter-server==0.2.0.dev0) (2.8.0)
Requirement already satisfied: jsonschema!=2.5.0,>=2.4 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbformat->jupyter-server==0.2.0.dev0) (3.0.2)
Requirement already satisfied: mistune<2,>=0.8.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (0.8.4)
Requirement already satisfied: pandocfilters>=1.4.1 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (1.4.2)
Requirement already satisfied: pygments in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (2.4.2)
Requirement already satisfied: defusedxml in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (0.5.0)
Requirement already satisfied: bleach in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (3.1.0)
Requirement already satisfied: entrypoints>=0.2.2 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (0.3)
Requirement already satisfied: testpath in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from nbconvert->jupyter-server==0.2.0.dev0) (0.4.2)
Requirement already satisfied: ipython>=5.0.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipykernel->jupyter-server==0.2.0.dev0) (7.7.0)
Requirement already satisfied: setuptools in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat->jupyter-server==0.2.0.dev0) (41.2.0)
Requirement already satisfied: attrs>=17.4.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat->jupyter-server==0.2.0.dev0) (19.1.0)
Requirement already satisfied: pyrsistent>=0.14.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jsonschema!=2.5.0,>=2.4->nbformat->jupyter-server==0.2.0.dev0) (0.15.4)
Requirement already satisfied: webencodings in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from bleach->nbconvert->jupyter-server==0.2.0.dev0) (0.5.1)
Requirement already satisfied: backcall in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.1.0)
Requirement already satisfied: jedi>=0.10 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.15.1)
Requirement already satisfied: pexpect; sys_platform != "win32" in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (4.7.0)
Requirement already satisfied: prompt-toolkit<2.1.0,>=2.0.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (2.0.9)
Requirement already satisfied: pickleshare in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.7.5)
Requirement already satisfied: appnope; sys_platform == "darwin" in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.1.0)
Requirement already satisfied: parso>=0.5.0 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from jedi>=0.10->ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.5.1)
Requirement already satisfied: ptyprocess>=0.5 in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from pexpect; sys_platform != "win32"->ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.6.0)
Requirement already satisfied: wcwidth in /usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages (from prompt-toolkit<2.1.0,>=2.0.0->ipython>=5.0.0->ipykernel->jupyter-server==0.2.0.dev0) (0.1.7)
Building wheels for collected packages: jupyter-server
  Building wheel for jupyter-server (setup.py) ... done
  Created wheel for jupyter-server: filename=jupyter_server-0.2.0.dev0-cp37-none-any.whl size=202596 sha256=0a45308568e11edae7482b636c0da9f848ac9d4827adceb1279b333d443654e2
  Stored in directory: /private/var/folders/m7/t8dvwtnn32z84333p845tly40000gn/T/pip-ephem-wheel-cache-apothcgw/wheels/06/bb/12/cf3ac7f4f4bcceff670c9ff94c71df2d48e8fdead10435845e
Successfully built jupyter-server
ERROR: voila 0.1.13 has requirement jupyter-server<0.2.0,>=0.1.0, but you'll have jupyter-server 0.2.0.dev0 which is incompatible.
Installing collected packages: jupyter-server
  Found existing installation: jupyter-server 0.1.1
    Uninstalling jupyter-server-0.1.1:
      Successfully uninstalled jupyter-server-0.1.1
Successfully installed jupyter-server-0.2.0.dev0
$ phoila install .
Building jupyterlab assets (build:dev:minimize)

One option would be to wait for jupyter server to make a release(https://github.com/jupyter/jupyter_server/issues/89)
Another would be to allow running on an older version of jupyter server.
If it's just this logging stuff, @vidartf what do you think about putting it behind an try .... except ImportError: so it can work with the released version? Pip makes it really hard to depend on a version from github.

It look likes comm_open messages are not allowed?
[W 12:09:29.182 PhoilaApp] Received message of type "comm_open", which is not allowed. Ignoring.

@saulshanabrook Ah, I missed that option in the metric grid (I added support for the new prometheus module in server + metrics OR prometheus in notebook). I'll add that.

It look likes comm_open messages are not allowed?

I think I just copy pasted that code from voila, so it is likely to be an issue there as well:
https://github.com/voila-dashboards/voila/blob/d8c040fcbec2ba826d0985d2a1a126116b86ae7a/voila/app.py#L381-L391

I think I just copy pasted that code from voila, so it is likely to be an issue there as well:

I added it in https://github.com/vidartf/phoila/pull/11. Sorry I should have posted that error in the other thread about comms, to keep these issues separate.

Does https://github.com/vidartf/phoila/commit/77d90082741805f60cd7b567e5293d8bbae705a3 fix the metrics issue?

It did, but I had to downgrade my version of notebook as well. with pip install "notebook<6.0"
Otherwise I got:
$ phoila examples/Charting\ Example.ipynb
Traceback (most recent call last):
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/serverapp.py", line 77, in <module>
    import notebook.prometheus.metrics
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/notebook/prometheus/metrics.py", line 15, in <module>
    ['method', 'handler', 'status_code'],
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/prometheus_client/metrics.py", line 499, in __init__
    labelvalues=labelvalues,
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/prometheus_client/metrics.py", line 107, in __init__
    registry.register(self)
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/prometheus_client/registry.py", line 29, in register
    duplicates))
ValueError: Duplicated timeseries in CollectorRegistry: {'http_request_duration_seconds_bucket', 'http_request_duration_seconds_created', 'http_request_duration_seconds_count', 'http_request_duration_seconds_sum'}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/serverapp.py", line 87, in <module>
    sys.modules['notebook.prometheus.metrics'] = sys.modules['jupyter_server.prometheus.metrics']
KeyError: 'jupyter_server.prometheus.metrics'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/miniconda3/envs/ibis-vega-transform/bin/phoila", line 6, in <module>
    from phoila.app import main
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/app.py", line 5, in <module>
    from .serverapp import ServerApp
  File "/usr/local/miniconda3/envs/ibis-vega-transform/lib/python3.7/site-packages/phoila/serverapp.py", line 91, in <module>
    'Cannot use an older version of jupyter_server with a newer version of notebook'
RuntimeError: Cannot use an older version of jupyter_server with a newer version of notebook

Yeah, that is expected (I don't know how to correct "split" a sys.modules entry into two, PRs welcome 😉).

(I don't know how to correct "split" a sys.modules entry into two, PRs welcome 😉).

Hah I don't even know what that means! Not the end of the world to require an old version.


HDDS-9038. Enable dynamic reconfiguration of EC container provider properties

What changes were proposed in this pull request?
Allow dynamic reconfiguration of WritableECContainerProvider config.
https://issues.apache.org/jira/browse/HDDS-9038
How was this patch tested?
Updated integration test.
Tested in ozone compose example:
$ ozone freon ockg -n10 -t10 --type EC --replication rs-3-2-1024k
...
$ ozone admin container list | jq -r '.containerID' | wc -l
5
# edit /etc/hadoop/ozone-site.xml, add ozone.scm.ec.pipeline.minimum=10
$ ozone admin reconfig --address scm:9860 start
SCM: Started reconfiguration task on node [scm:9860].
$ ozone admin reconfig --address scm:9860 status
SCM: Reconfiguring status for node [scm:9860]: started at Tue Jul 18 19:28:06 UTC 2023 and finished at Tue Jul 18 19:28:06 UTC 2023.
SUCCESS: Changed property ozone.scm.ec.pipeline.minimum
	From: "5"
	To: "10"
$ ozone freon ockg -n10 -t10 --type EC --replication rs-3-2-1024k
...
$ ozone admin container list | jq -r '.containerID' | wc -l
10

CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/5591531483

Thanks @kaijchen for the review.


[REQ] More Precise Quality Control

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
So... This might sound weird...
I don't know if roblox might restrain this but,
It would be nice if Bloxstrap could manually control each aspect of quality.
So instead of one slider that controls shaders, material and render distance but 3 sliders that control each.
If Roblox restrains it, I understand but it would be cool, especially on large and dark maps that lower shaders might make it more visible.

Not possible, sorry.

@pizzaboxer if I requested it to Roblox do you think they can try??


Fix cargo clippy

Hi there
I was kind of studying the source code and decided to delivery a clippy fixes along the way.
A note:
Unit address_size is unused so could be deleted.
Maybe there's some plan for it so I've left it.
PS: if you don't mind could you elaborate on this comment?
// TODO: handle `lea rax, [rip + offset]; call rax`

As I understand the offset will be no calculated correctly in case of lea usage?

Please don't merge it.
I've incidentally found that now there a bunch of
Segmentation fault (core dumped)

OK it was a mem::transumute as I understand.
Not sure exactly why it happend though.

Thanks for working on this. However, I find some of the clippy warnings to be too opinionated, and I prefer not to apply them. I do occasionally go through and fix warnings I agree with, and I think it would be a better use of my time to do that myself, rather than review this PR and try to do a back and forth to get it into a state that I'm happy to merge.
In general, it's not a good idea to fix warnings (either compiler warnings or clippy warnings) without understanding the code that you are changing. This especially applies to unsafe code.

PS: if you don't mind could you elaborate on this comment?
// TODO: handle `lea rax, [rip + offset]; call rax`

As I understand the offset will be no calculated correctly in case of lea usage?

The purpose of this code is to find all addresses that the function calls. However, we currently only look at individual call instructions. Thus if the individual instruction is call rax, we currently can't determine what address that is calling, but in theory we should be able to work out what this address is in some cases, such as if the previous instruction was a RIP relative offset calculation.


🐛 codescene: Use authenticated request towards proxy backend

Plugin Name
codescene
📜 Description
There's an incoming change to the @backstage/plugin-proxy-backend to require all requests to be authenticated by default. This means that plugins that rely on the proxy backend now need to start passing a Backstage user token in their requests.
👍 Expected behavior
The FetchApi should be used to make the request, for example like this: https://github.com/backstage/community-plugins/blob/a25418c4f52b759f78a1e4256b28f891e673f334/workspaces/puppetdb/plugins/puppetdb/src/api/PuppetDbClient.ts#L44-L56
👎 Actual Behavior with Screenshots
Plain fetch API is used without credentials: https://github.com/backstage/community-plugins/blob/a25418c4f52b759f78a1e4256b28f891e673f334/workspaces/codescene/plugins/codescene/src/api/api.ts#L65
👟 Reproduction steps
Inspect the request to the proxy plugin in the network tab, If working correctly there should be an Authorization header present.
📃 Provide the context for the Bug.
Incoming change through https://github.com/backstage/backstage/pull/24643
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, I don't have time to work on this right now

Example implementation PR for inspiration: https://github.com/backstage/community-plugins/pull/427


Adds is_reliable_language property to language detection

Follow up from the discussion in https://github.com/textpipe/textpipe/pull/53#discussion_r210245818, I made the language detection a bit more robust and expose the is_reliable_language property from  cld2-cffi.

It might be nice to already include a usage of this attribute in the commit. Could you for example replace all these statements (there must be quite a few in the repo):
lang = self.language if self.language != 'un' else self.hint_language
With these:
lang = self.language if self._is_reliable_language else self.hint_language
Or do you think that's inappropriate?

I agree it would be nice to include the usage in this PR. The change to lang = self.language if self.is_reliable_language else self.hint_language means that we will be using the hint_language when there is a detected language, but the score of the second language is too close to really call it reliably. I think it makes sense to switch over to that.

👍


Chef - Agent Version support for old versions that depends a cookbook.

Is there a better recommendation to check the chef agent version on a node via metadata.rb? what we want is to support older chef agents while we do migrating them by batch to a newer and we the case is that the older version depends on a cookbook (in particular, its the chef_handler cookbook). The newer version of chef infra agent from 14 onward its already part as a chef resource and no longer depends on a cookbook. For what attempted, this is the code tried:
if "#{Chef::VERSION.split('.')[0]}" <= '13'
  depends 'chef_handler'
end

No, metadata.rb is compiled to JSON so you can't usefully use if statements at all, for anything (and conditional dependency graphs based on the target chef-client version would make everything about dependency resolution and management quite crazy).  You'll need to have two different versions of the cookbook to be able to have entirely different dependent cookbooks based on which version you are on.  You may want to fork the cookbook entirely and abandon the old one depending on how complicated it is.


improve ksonnet prototype for kubebench-job

so as to adapt to the improved workflow as in #50.

/priority p1

/assign

Closing the issue as it was addressed by #74.


Fix for darkmode

There was a problem with showing loader in dark mode: The cover area in CutoutView was always white.
How I resolved: Recursively find nearest available parent's backgroundColor to fill the cover area in CutoutView
The result:
Before:

After:

An example for dark mode/light mode was also added

@malkouz can you take a look at this pull request?


Battery full at as 100%

Currently, when using full-at configuration, it does not change the calculated value when not totally charged.
[module/battery]
type = internal/battery
battery = BAT0
adapter = ADP1
full-at = 84

When my battery reaches 84, polybar displays it as 100%, but as soon as I unplug it, the value shown is 84, 83, etc.
Other status bar have an option to use the real maximum value (84) or the maximum value (100%), it would be nice if I could see my battery percentage.

Try with this patch ( git apply ...), it uses the charge_max and charge_now values to calculate the percentage instead of the reported capacity value.
diff --git a/include/modules/battery.hpp b/include/modules/battery.hpp
index 8c49c9d..fe46528 100644
--- a/include/modules/battery.hpp
+++ b/include/modules/battery.hpp
@@ -19,7 +19,6 @@ namespace modules {
     ADAPTER,
     CAPACITY,
     CAPACITY_MAX,
-    CAPACITY_PERC,
     VOLTAGE,
     RATE,
   };
diff --git a/src/modules/battery.cpp b/src/modules/battery.cpp
index d50bea7..c08f75f 100644
--- a/src/modules/battery.cpp
+++ b/src/modules/battery.cpp
@@ -32,11 +32,6 @@ namespace modules {
     }
     m_valuepath[battery_value::ADAPTER] = path_adapter + "online";

-    if (!file_util::exists(path_battery + "capacity")) {
-      throw module_error("The file '" + path_battery + "capacity' does not exist");
-    }
-    m_valuepath[battery_value::CAPACITY_PERC] = path_battery + "capacity";
-
     if (!file_util::exists(path_battery + "voltage_now")) {
       throw module_error("The file '" + path_battery + "voltage_now' does not exist");
     }
@@ -103,7 +98,7 @@ namespace modules {
     }

     // Create inotify watches
-    watch(m_valuepath[battery_value::CAPACITY_PERC], IN_ACCESS);
+    watch(m_valuepath[battery_value::CAPACITY], IN_ACCESS);
     watch(m_valuepath[battery_value::ADAPTER], IN_ACCESS);

     // Setup time if token is used
@@ -147,7 +142,7 @@ namespace modules {
       if (chrono::duration_cast<decltype(m_interval)>(now - m_lastpoll) > m_interval) {
         m_lastpoll = now;
         m_log.info("%s: Polling values (inotify fallback)", name());
-        file_util::get_contents(m_valuepath[battery_value::CAPACITY_PERC]);
+        file_util::get_contents(m_valuepath[battery_value::CAPACITY]);
       }
     }

@@ -262,14 +257,11 @@ namespace modules {
    * Get the current capacity level
    */
   int battery_module::current_percentage() {
-    auto capacity = file_util::get_contents(m_valuepath[battery_value::CAPACITY_PERC]);
-    auto value = math_util::cap<int>(std::atof(capacity.c_str()), 0, 100);
+    auto capacity_now = std::strtoul(file_util::get_contents(m_valuepath[battery_value::CAPACITY]).c_str(), nullptr, 10);
+    auto capacity_max = std::strtoul(file_util::get_contents(m_valuepath[battery_value::CAPACITY_MAX]).c_str(), nullptr, 10);
+    auto percentage = math_util::percentage(capacity_now, 0UL, capacity_max);

-    if (value >= m_fullat) {
-      return 100;
-    } else {
-      return value;
-    }
+    return percentage < m_fullat ? percentage : 100;
   }

   /**

Something happened now and I don't have /sys/class/power_supply/BAT0 anymore. Which causes the module to fail...

I'm not sure if I have correctly applied the patch, couldn't see the difference.
Perhaps I'll compile it manually instead of trying to mess around with gentoo ebuild. :P

I'm sure I have compiled with the patch applied now, will see how it goes and reply here.

Okay, I think this patch has broken the battery module because I can't see the battery with this anymore.

What's the output of:
$ ls -1 /sys/class/power_supply/**/*

The problem is the same, BAT0 is not present.
/sys/class/power_supply/ADP1/online
/sys/class/power_supply/ADP1/type
/sys/class/power_supply/ADP1/uevent

/sys/class/power_supply/ADP1/device:
driver
hid
modalias
path
physical_node
power
power_supply
subsystem
uevent

/sys/class/power_supply/ADP1/power:
autosuspend_delay_ms
control
runtime_active_time
runtime_status
runtime_suspended_time
wakeup
wakeup_abort_count
wakeup_active
wakeup_active_count
wakeup_count
wakeup_expire_count
wakeup_last_time_ms
wakeup_max_time_ms
wakeup_total_time_ms

/sys/class/power_supply/ADP1/subsystem:
ADP1

That's weird. Is the acpi module loaded?

Also check  acpi --everything

It's currently saying that I don't have a acpi command.

You probably have to install it. Also scan through dmesg for info.

# acpi --everything

Adapter 0: off-line
Cooling 0: x86_pkg_temp no state information available
Cooling 1: Processor 0 of 10
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
Cooling 5: LCD 0 of 100

Nothing on dmseg that popped something.

I'm guessing it's a kernel issue.

Is the battery module loaded?
$ lsmod | grep battery

battery                11989  0

After a third restart, my battery is showing again. Crazy.

I believe this is working! :+1:
A very cool addition would be to not need to add a full-at value and use the last full capacity value:
Battery 0: Discharging, 83%, 04:08:34 remaining
Battery 0: design capacity 7150 mAh, last full capacity 5870 mAh = 82%
Adapter 0: off-line
Cooling 0: x86_pkg_temp no state information available
Cooling 1: BAT0 no state information available
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
Cooling 5: Processor 0 of 10

I'm using version 2.4.8 and it seems to be working fine. I'll reopen this if not!
Thanks!


Low text contrast for Button

Looking at https://www.sanity.io/ui/docs/primitive/button, the contrast ratio between text and background color for the "Publish" button does not seem high enough to meet WCAG 2.0 criterion 1.4.3, i.e. at least 4.5:1 (with default browser settings the text has font-weight: normal and font-size: 19px, so it doesn't count as "Large" text).

tone="primary" (#ffffff on #2276fc): 4.15:1
tone="default" (#ffffff on #8690a0): 3.22:1
tone="brand": same as default
tone="positive" (#ffffff on #3ab564): 2.63:1
tone="caution" (#ffffff on #b7991e): 2.76:1
tone="critical" (#ffffff on #f03e2f): 3.86:1

With mode="ghost" it's mostly above 4.5:1, except

tone="positive" in the hover state (3.81:1)
tone="caution" in the hover state (3.96:1)

(With mode="bleed", the contrast ratio looks to be high enough for all variations tested!)
Contrast ratio was calculated using https://webaim.org/resources/contrastchecker/.

Thank you for reporting @oyvind-stenhaug 🙏  This is probably the main aspect lacking in terms of accessibility in @sanity/ui.
Fwiw, there‘s currently work being done to remedy this discrepancy on feature/improve-colors.

https://sanity-ui-workshop-il5ybwl8t.sanity.build/color/overview


Rename toc.md to TOC.md

@Banani-Rath,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@Banani-Rath Changes to TOC files belong in the private repo. I'm closing this pull request so that you can make updates in azure-docs-pr. Thanks.


How to automatically reconnect?

Is automatically retrying to connect possible? This is especially important during development as it's really annoying to refresh my browser. I'm new to websockets. It seems possible in socket.io, but not mentioned in this library's README. If it's not possible, then this is a feature request. I also looked in the Sails.js in Action book's chapter on websockets and it wasn't mentioned there.
In the meantime, I'm trying to do it myself. I'm using this library like is shown in the top of the README, as in, "node style", rather than the script tag. I have something like this:
const io = sailsIoClient(socketIoClient)

io.socket.on('disconnect', () => {
  function tryToReconnect() {
    setTimeout(() => {
      try {
        io.socket.reconnect()
      } catch (error) {
        tryToReconnect()
      }
    }, 5000)
  }
  tryToReconnect()
})

Note the try/catch. This try/catch doesn't work due to the asynchronous nature of websocket connections in the browser! So I need to get the raw socket so that I can provide an 'onerror' callback, as mentioned in this example.

I read the Proposing Features and Enhancements section of the Contributing Guide. If you tell me that it's not yet possible, I'll propose my feature request there. Thanks! :-)

Hi @tylercollier.  You can enable automatic reconnection by setting io.sails.reconnection to true.   Looks like the docs for the socket client need to be updated to include this setting!

You win for speedy replies @sgress454! Thanks, I got the reconnection option working!


Trees don't account for surrounding terrain

Ie. the base of the tree can hang out over the void, looking quite odd:
https://ibb.co/MCvH7B4

It looks like the trees only follow a couple of specific shapes. They're pasted into the world block-for-block instead of more organically like vanilla trees which can have slightly different heights and branch locations.
Checking to see if a tree would have more than 25% of its base over the edge might be easier to implement code wise.

I doubt this mod will ever be active. Unless you're willing to continue this mod, then its dead.

should be fixed in my fork (indev) : https://github.com/quentin452/enderoni-continuation/


OpenAPI 3 specification using Swagger UI?

I see that the distribution and submission services each contain an api_v1.json file containing openapi documentation.
I propose the addition of openapi and Swagger UI to have the project automatically generate the OpenAPI 3 specification docs and making them available for live discovery. Documentation and a general introduction of what I propose can be found from https://www.baeldung.com/spring-rest-openapi-documentation.
Should this be something the project leadership is interested in having contributed, I have both the interest and bandwidth available to prepare a PR. Please let me know if this is something the group would like me to pursue.

Thanks for the input and your offer to support. At this point, we decided to stick to the manually maintained submission service api_v1.json and distribution service api_v1.json.
Interested consumers can easily import these into Postman or into Swagger Editor for easier consumption.
Related: https://github.com/corona-warn-app/cwa-server/issues/372


Update ipn.rst

Explained how 'custom' parameter is used in the example. Also verified that only 'return_url' requires @csrf_exempt and only in the case of single payments.

You're right my mistake, I will send a new PR.


Delay setting content root until after build is called.

Besides adding a new main that will call WebHostBuilder.UseContentRoot(), is there any way to write a test for this?

You can extract this logic into a class and mock iisConfigData.

Closing for now. This approach won't work and I think we will need to design a new way of doing this.


Configuration

I had the app up and running rather quickly but the installation instructions stop at the configuration process. How do you configure the app with your own settings? I can browse to "http://webreflections.azurewebsites.net/create" on the Pi but the configuration is incredibly slow and unusable with the animations enabled.
Maybe I am misunderstanding how this works, are these instructions just to get a demo of your app with your configuration settings running on my pi? Do I have to sign up for azure and configure my own instance? I noticed in your youtube video you do the "setup" process on your laptop, I tried running same setup process on my laptop and the snapshot doesnt work on any of my 4 computers. Am I missing something?

@ajzolnoski, you need to create a hosted web app with http://webreflections.azurewebsites.net/mirror as the start page and deploy that app to the Pi. The mirror subdomain is the UI of the mirror. The create subdomain is to create your profile and is meant to run on your desktop.
You are not supposed to have to create your own Azure instance. You should be able to use ours. What are you seeing when you go through the create profile process?

I'm not sure if @ajzolnoski is running into the same complication as I am, but I can't figure out how to get to the create experience. All the published information assumes we'll be able figure that out (perhaps there's some hosted app dev knowledge that isn't commonly known?). Could you make a dummies guide for this missing configuration step?
The app is deployed to my Pi and the camera is recognizing me with a prompt of "Hello, is that you?". Because I have no profile it's understandable that I don't go any further than that on the Pi.
So, now the question I have is this: how to I get to the create experience? I tried browsing to my Pi with http://[ip]/create, http://[ip]:3000/create (the only port number I could find in the source code) and http://[ip]:8080/create (the port number for the device portal). None would give me a create experience. I watched the TechEd video on YouTube, it only said the app was running on the laptop, it didn't say how it was launched or installed. If I run the app locally from VS I just get the mirror UI with no way to navigate to the create experience.

I'm not sure if @ajzolnoski was struggling with the exact same issue as I was, but I couldn't figure out how to get to the configuration experience to begin with.
Here's what I did ( @andypavia , please let us know if this is the expected method or if there's an easier way):

Follow the instructions for setting up visual studio and deploy the app to your Pi.
In visual studio, change the start page to http://webreflections.azurewebsites.net/create
Still in visual studio, change the target CPU to your PC's
Change the run/debug target from device to local machine
Run the app from within visual studio

At this point you'll have the create experience running locally on your PC (hopefully you have a web cam). Fill in the information and submit to save your face profile information to the cloud (make sure you throw away your anti-big brother tin foil hat first, it will interfere with the saving of the image).

@andypavia Andy - is it possible to host the web application locally on the Pi rather than on the Azure instance?  I would assume this means that Windows 10 IoT on the Pi would need to run NodeJS as a web server.  Is it possible?

@tomjaimz - it is possible to run node.js locally on the Pi - https://blogs.windows.com/buildingapps/2015/05/12/bringing-node-js-to-windows-10-iot-core/ While we didn't build the project this way, you can run the web server portion locally. Likely there is a bit more work.


No such file or directory when trying to run tests in another docker container than it was built in

Hey
I build the tests in a docker stage and execute them in the next.
I run into
│ Running tests in sequence                                                                                │
│   Extracting 1 binaries to /tmp/nextest-archive-bb9dDJ                                                                                │
│    Extracted 3 files to /tmp/nextest-archive-bb9dDJ in 1.58s                                                                                │
│ Error:                                                                                │
│    0: error building test list                                                                                │
│    1: running ''/tmp/nextest-archive-bb9dDJ/target/debug/deps/integration_tests-9cdfa58268cee69f --list --format terse'' failed                                                                                │
│    2: No such file or directory (os error 2)                                                                                │
│                                                                                │
│   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━                                                                                │
│                                 ⋮ 3 frames hidden ⋮                                                                                │
│    4: cargo_nextest::dispatch::App::build_test_list::h0b139060a3d7e2cb                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│    5: cargo_nextest::dispatch::CargoNextestApp::exec::hc26ab86754cfce02                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│    6: cargo_nextest::main::h1c3419e2de29e9b3                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│    7: std::sys_common::backtrace::__rust_begin_short_backtrace::h29484de5e2a0cf31                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│    8: std::rt::lang_start::{{closure}}::ha37d78b2499ee6c9                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│    9: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::had4f69b3aefb47a8                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/ops/function.rs:259                                                                                │
│   10: std::panicking::try::do_call::hf2ad5355fcafe775                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:492                                                                                │
│   11: std::panicking::try::h0a63ac363423e61e                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:456                                                                                │
│   12: std::panic::catch_unwind::h18088edcecb8693a                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panic.rs:137                                                                                │
│   13: std::rt::lang_start_internal::{{closure}}::ha7dad166dc711761                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/rt.rs:128                                                                                │
│   14: std::panicking::try::do_call::hda0c61bf3a57d6e6                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:492                                                                                │
│   15: std::panicking::try::hbc940e68560040a9                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:456                                                                                │
│   16: std::panic::catch_unwind::haed0df2aeb3fa368                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panic.rs:137                                                                                │
│   17: std::rt::lang_start_internal::h9c06694362b5b80c                                                                                │
│       at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/rt.rs:128                                                                                │
│   18: main<unknown>                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│   19: __libc_start_main<unknown>                                                                                │
│       at <unknown source file>:<unknown line>                                                                                │
│   20: _start<unknown>                                                                                │
│       at <unknown source file>:<unknown line>

I dug around the code and think the default runner is not found. But I did not understand what the default runner actually is. I tried overriding it but to no avail.
Do you have any hints how to get it to run?
When I just run /tmp/nextest-archive-bb9dDJ/target/debug/deps/integration_tests-9cdfa58268cee69f --list --format terse i get the list of tests successfully :)
Thanks,
Noah

Thanks for the report! Given that running the command directly doesn't cause issues my main suspicion is a misconfigured target runner. Do you have any configured, either in a .cargo/config.toml or ?
In any case this should result in a better error message, and we should also add some sort of debugging support to print information about what target runner might be in use.

Which config file do you mean? nextest does not have a hard dependency on needing any config files on disk -- it has a default config shipped with the application.

nextest does not have a hard dependency on needing any config files on disk

I theorized that this might not be true and it does by mistake. I might be dead wrong ofc :)
I don't know what config locations it checks but I believe it cannot find the default cargo config (for the user/system) which then triggers this "File not found" error. But it's only a shot in the dark :)
I tried to change the runner to bash -c and similar but to no avail.

Hmm, it looks like the error's happening here:
https://github.com/nextest-rs/nextest/blob/3efdbc30d56f47a0b8f0f9db00e8e760c0c8ad5c/nextest-runner/src/list/test_list.rs#L584-L593
One issue is that we don't print out the target runner there -- we really should.

Yeah :) The question is: What default runner is assumed if there is no system wide cargo config file and also no workspace to look it up from?

None — the binary should be run directly.

(In fact that's the configuration used by almost everyone, which is why I was so surprised)

Welp, that wont work tho I believe :) /tmp/nextest-archive-bb9dDJ/target/debug/deps/integration_tests-9cdfa58268cee69f is not something that std::process::Command will accept as a runable command :) At least I had this issue in the past.

Just released cargo-nextest 0.9.17 with better error reporting for your situation. Could you try it out and update this post if this works better for you?

I just ran across this today. I wanted to update my CI runners to allow for caching of the test runs and all I get is this fun output:
root@buildkitsandbox:/# cargo nextest run --archive-file tests.tar.zst
  Extracting 6 binaries and 1 linked paths to /tmp/nextest-archive-Iqouk4
   Extracted 36 files to /tmp/nextest-archive-Iqouk4 in 0.19s
error: creating test list failed

Caused by:
  for `gw2api-http`, running command `/tmp/nextest-archive-Iqouk4/target/debug/deps/gw2api_http-b9d0137b2908f102 --list --format terse` failed

Caused by:
  No such file or directory (os error 2)
root@buildkitsandbox:/# /tmp/tests/target/debug/deps/gw2api_http-b9d0137b2908f102 --list --format terse
root@buildkitsandbox:/# $?
bash: 0: command not found
root@buildkitsandbox:/# ls /tmp
tests
root@buildkitsandbox:/# cargo nextest --version
cargo-nextest 0.9.17
root@buildkitsandbox:/#

This is from an interactive shell inside the container. I've manually extracted the .tar.zst because I initially thought it was missing some dynamic dependency.

Thanks @greaka -- this is really interesting and I'm not sure what's happening. Is this open source and/or is there a way for me to try this locally?
Also, can you try reproducing this outside of a container context? I'm wondering if there's something about the container environment that could be causing this -- could be some sort of bind-mount issue.
re dynamic deps, the archive does include any dynamic deps (linked paths) published by Cargo build scripts.

Thanks for that quick answer @sunshowers!
I cannot reproduce this issue outside a container, but I don't have a second pc to fully encapsulate environments.
you can reproduce this by installing https://earthly.dev and cloning my repo https://github.com/greaka/gw2api
inside the repo earthly --push +test-all is all you need

Thanks! Do you know if there's a way with earthly to hit an interactive shell at a specific moment?

ofc :slightly_smiling_face:
You can use earthly --push -i +test-all to get thrown into an interactive shell right after the failing command

Thanks. Looking at this now -- this is super interesting.

OK so this is happening because the source isn't checked out. Please note the requirement for the source to be checked out at https://nexte.st/book/reusing-builds.html#requirements.
If the workspace is in a different location across both machines, use --workspace-remap as specified in https://nexte.st/book/reusing-builds.html#specifying-a-new-location-for-the-workspace.
This is a pretty terrible and misleading error message, though. I'll fix it.

Ahh, I've read that and didn't know what was really expected. Could you tell me what it needs it for and what parts of it it needs?
It may be worth to also put that in the documentation to get a better grasp.

It's just that the source code (i.e. Cargo.toml and Rust files) needs to be available because some tests depend on test fixtures within the source code. In particular, while running tests, cargo test sets the current directory to the directory containing the project's Cargo.toml, and nextest copies that behavior.
It would be convenient if nextest archives included the source code, but they don't because the exact definition of source code is quite complicated. For example, do we want to depend on the details of a specific version control system like Git, and should untracked files be included. It's tricky business so we defer to the user for now.
In your case, where you do:
COPY --dir .config ./
COPY --dir http ./
COPY --dir model ./

If you can also make the contents of .config, http and model available while running tests, things should start working.
I've updated the documentation at https://nexte.st/book/reusing-builds.html#requirements to try and make it clearer -- happy to take suggestions.

Thank you very much for your help!
I can now start fixing the other issues in my build, unrelated to nextest. If you are still interested in how that would look like, I will probably update the repository tomorrow, it's almost 3am over here.
For the documentation, I would put the newly added lines right between the following existing lines:
        Non-test binaries used by integration tests

Currently, the only format supported is a Zstandard-compressed tarball (.tar.zst).

This is what gave me the impression that everything that it needs is packaged. And I would maybe state more clearly in that new paragraph that the same files that were needed for building the archive are still needed for executing it.
I'm not a native english speaker, so take my word with a grain of salt :slightly_smiling_face:

Released the better error messages in cargo-nextest 0.9.18. I think this should be completed now. Thanks for all your help debugging this!


Allowing symbols as WeakMap keys.

Merged in https://github.com/oracle/graaljs/commit/a48f3e5bbcacfb879f45fcc05624a0c0fcc656ec (I rebased the commit because of conflicts).


About  nuscenes datasets: test in ./projects/BEVFusion

Prerequisite

[X] I have searched Issues and Discussions but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version (dev-1.x) or latest version (dev-1.0).

Task
I'm using the official example scripts/configs for the officially supported tasks/models/datasets.
Branch
main branch https://github.com/open-mmlab/mmdetection3d
Environment

Reproduces the problem - code sample
1
Reproduces the problem - command or script
python tools/test.py /home/lxt/mmdetection3d/projects/BEVFusion/configs/bevfusion_lidar-cam_voxel0075_second_secfpn_8xb4-cyclic-20e_nus-3d.py /home/lxt/mmdetection3d/checkpoints/bevfusion_lidar-cam_voxel0075_second_secfpn_8xb4-cyclic-20e_nus-3d-5239b1af.pth --show --show-dir ./result/nuscenes --task multi-modality_det
Reproduces the problem - error message
When I used the above command to infer bevfusion on the Nuscenes test set, the following error occurred

Afterwards, I changed the task to multi-view_det,The project can operate normally and obtain Map and NDS. But -- show did not work and did not show prediction results. There is also no file generation in ./result/nuscenes
What surprised me was that Bevfusion is a multimodal 3D detection model, but its chosen task is multi-modality_det, but it can operate normally, although it cannot produce predicted PKL results. I am certain that my dataset is complete, but errors may occur when choosing multimodal tasks.
Can you please explain to me which task should be selected when I test bevfusion? And why executing the above instructions cannot visualize and generate prediction results?
Thanks!
Additional information
No response

It's because your infos.pkl have no num_pts_feats. You can follow nuScenes infos https://mmdetection3d.readthedocs.io/en/latest/advanced_guides/datasets/nuscenes.html to generate your dataset infos.


[PE-D] Clearing data and exporting causes data to reappear

After clear, following with an export causes the data to reappear.
Steps to reproduce included in video:
IMG_20211029_172449_705_01.mp4

Labels: type.FunctionalityBug severity.Medium
original: atyhamos/ped#14

probably has to do with state manager. in this case,

clear should place an empty address book on top, and
export should also hence create another empty addressbook and
add it to the top until yes command given.
after which, it should revert to empty addressbook state in 1)

Solution: either add a dummy state or just decouple export and history manager completely


Implement Input Field + Label

Description:
Make an input field with corresponding storybook integration
UI:

Approved :+1: :)


Alternative Images PoC

Nothing serious yet but should play around with the following alternative images as a proof of concept.

Cumulus
IOS-XR
EOS

Update: @cloudtoad working on Cumulus and FRR. The Endpoint re-vamp work also makes this very possible.
I'm going to close this, as the feasibility of this has been proven - anyone is now welcome and empowered to create any kind of network image.


other features

hey i know that in ms paint there's no layers but
what do u think of adding it to jspaint 👍

Check out Paint.NET for a very solid desktop program, and Photopea for an online one.
I want to build advanced features into my new app Mopaint and then eventually base jspaint off of mopaint. You'll be able to treat every brush stroke as a layer if you want to, but group operations and name the groups for organizational purposes. It'll be like a vector editing program, but not limited to "traditional vector graphics stuff", like, you'll be able to still do selection based editing and all that jazz.
If I added just layers support, I'd have to establish some way of storing the multiple layers in the session for autosave, which would complicate things later when writing code to upgrade sessions to the mopaint type format. And I would want a way to save/load files with layers, which means choosing a format, like .psd or .ora to support. And this opens a can of worms of compatibility. Not to mention that adding layers support already opens a can of worms of supporting different blending modes and various UI for creating, renaming, deleting, reordering, hiding/showing, and editing properties of layers.
So this is a long term goal.


variant: minor color adjustments

Some minor style adjustments

we can now control values for h1
fix some IE fallbacks
fix search box subtleties
adjust home link colors

What's the intention behind this?
https://github.com/McShelby/hugo-theme-relearn/blob/8569a64c2b15164a08717b9ea1d6af05f69cdbbb/static/css/theme.css#L115-L119
Are there any issues with changing it to the --MENU-SEARCH-color variable? Therefore if you have a white background, you can adapt to the text colors used for the rest of the search box.
For example, the icons and placeholder wont change according to --MENU-SEARCH-color nor --MENU-SEARCH-border-color

You are right. This was not as intended as the documentation clearly states that --MENU-SEARCH-color is used for icons and text color.
I've made a new issue #437


This Repo has been Excluded from Hacktoberfest 2023

Unfortunately this repo has been excluded from Hacktoberfest 2023. Pull/merge requests for this repo are not currently counting towards Hacktoberfest 2023 contributions. Maybe there is a way to contact the organizers and have this repo become included again?

I will keep you posted about the same.


Define a generic type for version

Define a type that must be generic and comparable, similar to sys.version_info in python

You already have the Version class but you want it to be comparable, aren't you?


Deleting Kismac Cask

Domain is not accessible any more

Looks like they still exist on GitHub: https://github.com/IGRSoft/KisMac2
but:

Mac OS 10.7 - 10.10 (64-bit only)

@numbermaniac it looks like it has not been updated in a while, so probably best to remove it.


Update the start-local script (kleros-v2/web)

Issues :

The current start-local script just spins up the server on localhost with this command
REACT_APP_SUBGRAPH_ENDPOINT=http://localhost:8000/subgraphs/name/kleros/kleros-v2-core-local parcel
But this command alone does not compile the wagami.config.ts file. That results in compile-time errors like this :

Solution :
To fix this issue need to run the generate-hooks command before starting the server  :

- "start-local": "REACT_APP_SUBGRAPH_ENDPOINT=http://localhost:8000/subgraphs/name/kleros/kleros-v2-core-local parcel"
+ "start-local": "yarn generate-hooks && REACT_APP_SUBGRAPH_ENDPOINT=http://localhost:8000/subgraphs/name/kleros/kleros-v2-core-local parcel"

It should work now, I've updated the docs and tmux script. I don't want to change the start-local and start behaviour because it would slow down the devs workflow whenever they make changes which don't require to generate.
yarn workspace @kleros/kleros-v2-web generate
...

yarn workspace @kleros/kleros-v2-web start-local
...


can not run in tensorflow 0.12.1

When I run the main.py, getting the following errors:
Traceback (most recent call last):
File "main.py", line 5, in
from trainer import Trainer
File "/Users/peng.huangp/github/pointer-network-tensorflow/trainer.py", line 7, in
from model import Model
File "/Users/peng.huangp/github/pointer-network-tensorflow/model.py", line 4, in
from layers import *
File "/Users/peng.huangp/github/pointer-network-tensorflow/layers.py", line 22, in
dynamic_rnn_decoder = tf.contrib.seq2seq.dynamic_rnn_decoder
AttributeError: 'module' object has no attribute 'dynamic_rnn_decoder'
I check <IP_ADDRESS> API of tensorflow, and can not find the definition for 'dynamic_rnn_decoder', and it is in the 0.1.0 API

hi, I met the same problem with you. But the 0.1.0 api is not available now, is there something I can do to fix it? Thank you very much!

same story


Use a separate file for Git aliases and functions

As I added more and more Git aliases and functions, both .bash_aliases and .bash_functions have become polluted with Git-specific stuff, and it would be great to separate it into a new dotfile so it's easier to mantain.

Done as part of c65fddac


Issues in Character Virtual test

From #24, the Character Virtual test has some issues that need to be fixed:
Hitting some objects too hard results in some weird physics, kicking the user or the object away. Possibly because the user is set to be very heavy.
The default example.js of tying the physics engine to the requestAnimationFrame causes weird things if you background the tab and foreground, causing the physics force to build over time and snap the user out of the world all at once. Get on the conveyor belt or start jumping, background the tab, wait, foreground and get a snap up or sideways.

Fixed in 6e41ceed82edd8a9b9136c9da1d0c4a9a3f52023

About the changing windows tab - the issue here is that delta time passed by rAF becomes too large. We usually clamp it, so it doesn't become unreasonable. If the simulation is supposed to run at 1/60, then that would be a good max value.

You can set the max to 1/30 or even 1/15 for example as long as during the update you then increase the number of steps so that each step is roughly 1/60th (so 1/60 = 1 step, 1/30 = 2 steps, 1/15 = 4 steps). Note that it is possible to run the simulation at a lower frequency and it will really depend on your scene if the simulation will be stable or not, if you run at 1/30 with 1 simulation step for example, all constraints will be much softer and there's a bigger chance of objects 'tunneling' through other objects.


Very helpful!

As usual, the documentation is very useful and provides much of the information needed to learn about how to best use an app or to proceed with the development of an app. Thank you!

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

ID: 9dd4d05c-4aa3-0376-f3a1-b0ea0793f482
Version Independent ID: 7f1ff943-61b0-60e1-9ca3-d4a84bfdb068
Content: Install Visual Studio
Content Source: docs/install/install-visual-studio.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @ornellaalt
Microsoft Alias: ornella

@BJAdams -- Bill, you're very welcome!
cc @ornellaalt as the author


Changes regarding Meilisearch v1.4.0

This issue gathers the changes related to the v1.4.0 of Meilisearch that will impact the integrations team.
📅  Release date: Sep 25th, 2023
The whole milestone of v1.4.0 is here!
⚠ The SDKs, which should be done by the release date, are only tier #1. Some of the features described may be done for tier #2 but will not be ready for the release day. Check the features below to understand which tier will receive which feature.

🖖 Click here to check the current tiers state of the integrations:

  Understand everything about tiers here.

Integration
Tier

Javascript
#1

PHP
#1

meilisearch-js-plugins
#1

Cloud Providers
#1

Kubernetes Chart
#1

Python
#2

Ruby
#2

Go
#2

Strapi
#2

.NET
#2

Rails
#2

Rust
#2

Symfony
#3

Java
#3

Firebase
#3

docs-searchbar.js
#3

docs-scraper
#3

Dart
#3

Swift
#3

Vuepress
#3

Gatsby
#3

Flutter
#3

⚠ If no change in the public API is added during the bump pull requests, there is no need for a new release, according to the Integrations team's versioning policy guideline.

 Customize text separator
Related to:

issue: https://github.com/meilisearch/meilisearch/issues/3610
spec: https://github.com/meilisearch/specifications/pull/254

Adapts Meilisearch to specific term nomenclature and thus covers more use cases by adding customization to the engine.
Make Meilisearch more customizable and adaptable to different types of data set content and, therefore, different use cases by letting them configure the separators to be indexed.
What needs to be changed:

Add two new settings: separatorTokens and nonSeparatorTokens with get, update, and reset methods
Update the /settings API to enable the possibility to receive in the payload the two new configurations separatorTokens and nonSeparatorTokens

blueprint of the methods:
client.index('indexName').getSeparatorTokens();
client.index('indexName').updateSeparatorTokens(['|', '/', '&sep']);
client.index('indexName').resetSeparatorTokens();

client.index('indexName').getNonSeparatorTokens();
client.index('indexName').updateNonSeparatorTokens(['@', '#']);
client.index('indexName').resetNonSeparatorTokens();

 Load a user-defined dictionary
Related to:

issue: https://github.com/meilisearch/meilisearch/issues/3917
spec: https://github.com/meilisearch/specifications/pull/255

Some Languages are not always space-separated (Chinese, Japanese, Korean...), forcing Meilisearch to rely on common word dictionaries to segment a text into words. However, this strategy only segments common words and struggles when a text contains domain-specific, technical, or People Nouns.
Because it is impossible to have an exhaustive list of words of all the possible domains or a complete list of Nouns, Meilisearch should allow users to add their list of words specialized for their use case.
What needs to be changed:

Add the new setting: dictionary with get, update, and reset methods
Update the /settings API to enable the possibility of receiving in the payload for dictionary

client.index('indexName').getDictionary();
client.index('indexName').updateDictionary(['|', '/', '&sep']);
client.index('indexName').resetDictionary();

I close this issue since everything has been done for v1.4.0 on integration side
Issues are opened on the repo that are missing the feature.


Development log

This is a log where I can write some "behind the scenes" notes, credits, thank contributors, write down ideas for next week's posts etc? Without blasting my mailing list?

Monday, August 19

todo: contributors to the ad issue? there were so many!
thank last week's contributors? the two who commented on substack
next week, thinking about the "employee of the world" stuff?


Alias for skip install -si is not working

Versions
Angular CLI: 1.7.1
Node: 9.6.1
OS: win32 x64

Repro steps

type ng new MyNewApp -st -si in terminal to generate a new project, without downloading npm dependencies

Observed behavior
It does download all dependencies.
Desired behavior

-si as an alias for skip install.
Mention any other details that might be useful (optional)

1.x is no longer actively support (outside security issues).  Those aliases have also been removed from the latest version (6.x)


Support adding Rational to Integer

(Marking this one as a draft for a second, since there are some hairy yaks lining up)

I added subtraction too, and only then I realized this is the wrong way to fix things.
It started out with this code for adding to an Integer:
Value IntegerObject::add(Env *env, Value arg) {
    if (arg->is_float()) {
        return Value::floatingpoint(m_integer + arg->as_float()->to_double());
    } else if (arg->is_complex()) {
        return arg->send(env, "+"_s, { this });
    } else if (!arg->is_integer()) {
        arg = Natalie::coerce(env, arg, this).second;
    }
    arg->assert_type(env, Object::Type::Integer, "Integer");

    return create(m_integer + arg->as_integer()->integer());
}

The issue here is in the use of the call to coerce. The check for arg->is_complex() is a workaround to make a statement like 1 + Complex(2) work, which should be handled by type coercion. The call to coerce should not convert the argument into an Integer, but convert the current object into a class compatible with the argument. This means the combination of arg = Natalie::coerce(...) and assert_type won't work.
The code should more like this (I haven't tried this code yet, so please read it as pseudocode):
Value IntegerObject::add(Env *env, Value arg) {
    if (arg->is_float()) { // (1)
        return Value::floatingpoint(m_integer + arg->as_float()->to_double());
    } else if (!arg->is_integer()) {
        auto coerced = Natalie::coerce(env, arg, this);
        if (!coerced.first->is_integer()) // (2)
            return coerced.first.send(env, "+"_s, { coerced.second });
        arg = coerced.second;
    }
    arg->assert_type(env, Object::Type::Integer, "Integer");

    return create(m_integer + arg->as_integer()->integer());
}

I'm not sure if this still needs the arg->is_float() check (1), this should probably be handled by the coercion as well.
I'm also not sure about the second is_integer check (2), I don't think it should be here, but we might end up in infinite loops if we call this with an argument that has a coerce method that returns Integers.
A short Ruby script as an illustration:
rat = Rational(3)
p rat.coerce(1)
p 1 + rat

puts ''
puts 'Update Rational#coerce to return Integers'
class Rational
  def coerce(other)
    [other, numerator]
  end
end
p rat.coerce(1)
p 1 + rat

Running this with MRI shows how the updated coerce method is used:
[(1/1), (3/1)]
(4/1)

Update Rational#coerce to return Integers
[1, 3]
4

But Natalie (with this patch) still returns a Rational:
[(1/1), (3/1)]
(4/1)

Update Rational#coerce to return Integers
[1, 3]
(4/1)

So I guess I should pretty much drop these changes, rewrite them to using coerce (and update the other operations like IntegerObject::mul as well). And there are probably many more locations where this pattern is present.

I'll trust you on this one. 😅 It's been awhile since I looked at the coerce stuff, so I think I've forgotten how that works for the most part.

I'll trust you on this one. sweat_smile It's been awhile since I looked at the coerce stuff, so I think I've forgotten how that works for the most part.

Honestly, I don't think I ever understood it before I started working on this case :blush:

What do we need to do here? Can we go ahead and merge this?

I still feel like I've mixed some assignments up, I just need to take some time to go over all of it again. I'll try to do it somewhere this week.

It looks like the upstream specs for coercion with bitwise operators were broken too, I pushed an upstream fix in https://github.com/ruby/spec/pull/1011
TODO list for myself:

Clean up test/natalie/integer_spec.rb, it has some duplication with upstream specs
Add some tests for failure cases (like calling Integer#& with a mock that has a coerce result with objects not supporting &)

Well, that took way longer than it should have, but I think this is it.


Add AudFlow, Statis, CkFlow, QrFlow and DdFlow plugins

text to speech plugin

it's stasis stands for statistics 🤦♂
but any thing😁

Statis tested. Don't have any more time today. will do it later.

ok, take your time
i work on anthor two plugins, when i finish i pull request them 🫡

the 5 plugin merged?
if i want to make an simple edit in one readme because a typo ,i should PR the plugin again ?😅

the 5 plugin merged? if i want to make an simple edit in one readme because a typo ,i should PR the plugin again ?😅

By readme do you mean the description in the json? If so, yes.

no in my plugin readme not here

no in my plugin readme not here

Then you don't have to. Publish a release and updates are automatically done (see readme of this repo).

Thank you very much,
it simple typo There is no need to update it😊
thank you for hard work 🫡


API overview documentation

Is your feature request related to a problem? Please describe.
v0.7.0 introduced API but there is not a single line about it in documentation.
Describe the solution you'd like
There should be an overview to explain what ressource endpoint are available, the serializers used in list/details and that it is a barebone implementation where user could be able to enable third tool like JW token authentication, API browser, etc..
Describe alternatives you've considered
If we could state about #63 before doing this, we could add a hint notice about how to enable it.

Done in v0.8.0


Detect cycle in an undirected graph

Is your feature request related to a problem? Please describe.
I want to add an algorithm using BFS and DFS both to find if there is a cycle present in a graph. pLease assign me this issue. Thank you!
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

refer #122


Feature request: Typos connected to subdomains

The company I work for has an web application that is accessed by tens/hundreds of clients over a subdomain (e.g. spec.nonsense.com). Out of curiosity I registered the domain specnonsene.com (without a dot), cloned our web app and logged the access to it. I was suprised that there were a hand full of users that tried to log in to the website with their credentials in a short period of time. Another example that also comes to mind is a hyphen instead of a dot (spec-nonsense.com). Especially since a dot and hyphen are directly next to each other at some keyboards.
So I would argue that it makes sense to also check for things like that when going through registered domain names. If you agree, I would be glad if that could be implemented.

Thanks for this suggestion. It has been implemented.
$ ./dnstwist.py -f list spec.nonsense.com |egrep spec.nonsense\.com
spec.nonsense.com
spec-nonsense.com

it makes sense to also check for things like that when going through registered domain names
I don't get this, could you please explain?

Not of if importance. With "checking for things like that" I just meant that it makes sense to also include URLs with missing dots or hyphens. Thanks for adding this that quickly!


Amplify Wordpress Theme Update?

Hello,
I use the Wordpress theme version of Propeller, and was wondering if there was going to be an update for WP 5.0? I got errors all over the place.

Hello @coinformant,
We have checked the theme with WordPress version 5.0.1 and are unable to find any issue on the coding side. However, there is one plugin - WordFence which is conflicting. So try removing that plugin and check if your error is getting solved.
If your issue still prevails, can you please share a demo URL or elaborate the issues you are facing for our better understanding.
Regards,
Monika


doc: add description about estargz and nerdctl support

Signed-off-by: Yan Song<EMAIL_ADDRESS>

@imeoer , a new test job has been submitted. Please wait in patience.

@imeoer , your pull request has been updated, but a test job is already running. A new test job wil be submitted after the current job is finished.

@imeoer , your test job is running now. Please wait in patience.

@imeoer , your pull request has been updated, but a test job is already running. A new test job wil be submitted after the current job is finished.

@imeoer , your test job is running now. Please wait in patience.

@imeoer , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Sorry, the current test job result is not valid, because your pull request has been updated, and a new test job will be submitted.

@imeoer , your pull request has been updated. A new test job will be submitted. Please wait in patience.

@imeoer , the test job has been submitted. Please wait in patience.

@imeoer , your pull request has been updated, but a test job is already running. A new test job wil be submitted after the current job is finished.

@imeoer , your test job is running now. Please wait in patience.

@imeoer , your pull request has been updated, but a test job is already running. A new test job wil be submitted after the current job is finished.

@imeoer , your test job is running now. Please wait in patience.

@imeoer , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Sorry, the current test job result is not valid, because your pull request has been updated, and a new test job will be submitted.

/retest

@yqleng1987 , the test job has been submitted. Please wait in patience.

@yqleng1987 , The CI test is completed, please check result:

Test CaseTest Result

merge-target-branch:white_check_mark:SUCCESS

build-docker-image:white_check_mark:SUCCESS

compile-nydus:white_check_mark:SUCCESS

compile-ctr-remote:white_check_mark:SUCCESS

compile-nydus-snapshotter:white_check_mark:SUCCESS

start-nydus-snapshotter-config-containerd:white_check_mark:SUCCESS

run-container-with-nydus-image:white_check_mark:SUCCESS

Congratulations, your test job passed!


No completion before extra positional argument that could be named

Create a file containing the following code (minus the carats):
void f(int a, {int b = 0}) {}
void g() {
  f(2, ^ 3); // no suggestions, should suggest 'b:'
  f(2, ^); // suggests 'b:'
}

There should be a suggestion on the third line to add the missed name.

@pq


Enhancement: Add mapping for web port (9000)

Problem/Motivation

To have the ability (like in many other addons) to access portainer locally without hassio (and authorization)

Proposed changes

adding port mapping for port 9000 being unset by default, so the user can decide wether the port should be opened or not

This has been removed in favor of Home Assistant Ingress.


Added SRG model and updated MC and MC++

Description

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


TableViewCell not show

I try to using this image with url https://www.thuthuatweb.net/wp-content/uploads/baiviet/2014/01/windows-phone-loading-animation.png but the demo does not show anything.
Could you check this?

Hi, @truong15.  I will check this out

I think this is same issue as here.
please see it, and some example i create this branch.

Thank you for your help. It's a great library.


Get manager up and running with OIDC type = Tigera

Replaced with https://github.com/tigera/operator/pull/1293


Is there a way for this integration to see device and entity changes in real-time?

Currently I use this template to read in various entities and their states:
{%- for area in areas() %}
  {%- set entities = area_entities(area) -%}
  {%- set area_info = namespace(printed=false) %}
  {%- if entities -%}
    {%- for entity_id in entities -%}
      {%- set entity_state = states.entity_id -%}
      {%- if entity_state is not none %}
        {%- if not area_info.printed %}
{{ area_name(area) }}:
          {%- set area_info.printed = true %}
        {%- endif %}
- {{ entity_id }}: {{ states(entity_id) }}
      {%- endif %}
    {%- endfor %}
  {%- endif %}
{%- endfor %}

This only updates entity states when the Azure OpenAI integration is reloaded, is there any way for this information to be read by the Azure OpenAI integration in real-time?

@ubersandwich You need to create a new session with Azure OpenAI unfortunately, because the initial states are read and sent at startup time, it's the same behaviour for the official OpenAI integration.


Colorize dendrogram

Adds colorizing the dendrogram with the same colors that are used for the tag sets
Resolves #49

Nice functionality. I tested the "cluster lineage tree" plugin and it works as expected. The test coverage is impressive. Which gives me confidence that the code will run reliably.
The code quality is goof. But I see one mayor point for improvement. This PR adds new methods to the "Classification" class. The class became a bit unorganized. I think restructuring it would be valuable.
Regarding javadoc & comments: There are sometimes concepts or surprises in the code. That are nowhere described, for example:
* The class ID in the Classification class, what does it refer to.

* We no the the "WeightedLinkageStrategy" class is named wrongly. And therefor we decided extend the class. This should be described in the commet.

* That a class is a copy of a class from another repository.

* There are  tests that only test a side effect "CustomizedClusterComponentTest"

Please add, one sentence of javadoc to each class in the repository. One sentence that describes the purpose of class.
There is a small problem the color of the 4th class is always black. This is due to the use of the glasby lookup table and the fact that the first 5 colors in there are "outliers colors". I would suggest to exclude the first five colors.

Thanks for the review.
I did the following steps:

restructured the Classification class so that the IDs are no longer needed
Added a comment explaining that WeightedLinkageStrategy was overridden, because it is wrong
Added comments to the copied (or rather re-implemented classes)
Explained that CustomizedClusterComponentTest has only limited testing value
Added a javadoc to each new class
Skipped the first five colors of the Glasbey color pallette.


⚠ API - Lens has degraded performance

In 82971a6, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 328 ms

Resolved: API - Lens performance has improved in 73982e1.


RapidStart services-role cener

"When you use RapidStart Services, we recommend that you use the RapidStart Services Implementer Role Center as it provides the correct context for your configuration work"
I assigned all the right and am a Super User but the RapidStart Services Implementer Role is nowhere to be seen in the "Role Center-list"
How do I start the RapidStart Services Implementer?

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

ID: cd5f8ff5-018b-67f8-5bc7-1784b054167c
Version Independent ID: 1bfdf570-9515-9e0c-7718-189ac71a3bfb
Content: How to Use the RapidStart Services Role Implementer Center - Business Central
Content Source: business-central/admin-how-to-use-the-rapidstart-services-role-center-to-track-progress.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Thank you for the feedback
This Role Center, along with many others, will be added within the next couple of updates. I will therefore leave the topic unchanged.
You can still access the functionality. Simply search for Configuration Worksheet, as stated in step 1.
Soren
Business Central writer

As at today, this functionality is still not available. I understand that these might be published in advance, but this seems a long time in advance with still not released into the product.  It is very confusing for users when the help materials do not line up with functionality available.

Hello heatherr-nz,
Thank you for your feedback! I have forwarded your feedback to the team who own this Role Center, and they say that it is indeed not currently available. We (the people who do the docs) were told 6 months ago that it would be made available shortly, as my colleague states above, but the team changed that decision.
I will get the Help updated accordingly, and I've asked the product team to revise the decision on which Role Centers are available.

Thanks very much for the feedback.
From: Eva Dupont<EMAIL_ADDRESS>Sent: Thursday, 4 July 2019 9:28 PM
To: MicrosoftDocs/dynamics365smb-docs<EMAIL_ADDRESS>Cc: Heather Roggeveen<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/dynamics365smb-docs] RapidStart services-role cener (#69)
Hello heatherr-nz,
Thank you for your feedback! I have forwarded your feedback to the team who own this Role Center, and they say that it is indeed not currently available. We (the people who do the docs) were told 6 months ago that it would be made available shortly, as my colleague states above, but the team changed that decision.
I will get the Help updated accordingly, and I've asked the product team to revise the decision on which Role Centers are available.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/dynamics365smb-docs/issues/69?email_source=notifications&email_token=AMQU5XTTPHFVMEG47D7GWEDP5W7BPA5CNFSM4GG7EC22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZG4BVI#issuecomment-508412117, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMQU5XQAFCCB2GUFOAMTJDLP5W7BPANCNFSM4GG7EC2Q.
This e-mail may contain privileged and confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that you must not distribute, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.


Install Glimpse now I cannot add service references?

I installed glimpse and now I get a warning and an error when adding a service reference that Glimpse 1.8.2 could not be found or loaded. I looked in my packages folder and I have Glimpse 1.8.6 installed. Apparently there is still some reference to 1.8.2 having to do with adding a service reference in Visual Studio but I have not been able to find it. Ideas?

@KevinBurton Can you give me the list of Glimpse related NuGet Packages installed in the project where you are adding your service reference?
Just check the packages.config file
My first idea is that the custom tool generating the client classes when adding the service reference, is not talking the web.config into account, where the binding redirects are being configured. Most likely it is loading all assemblies in the project's bin folder into memory and applying some reflection upon it, hence a specific Glimpse assembly, one depending on Glimpse.Core 1.8.2, is loaded, but since the bin folder most likely contains a newer version of the Glimpse.Core and there are no binding redirects defined for that custom tool process the tool crashes
I'm not sure if that can be solved directly, and somehow I guess other assemblies added by means of NuGet packages might have the same problem, but to be sure we first need the information above to try to reproduce it, just to make that is actually the problem

I have attached the packages.config which should give you an idea of the packages that I have installed. Ntoice that the config file seems to have it right. it is referenceing 1.8.6

By the way I have tried rebooting to eliminate the possibility of something loaded in memory. I didn't notice any Glimpse related assemblies in the GAC. But as you said it may be another assembly that references an older version of Glimpse.

On Mar 26, 2015, at 8:14 AM, Christophe Gijbels<EMAIL_ADDRESS>wrote:
@KevinBurton Can you give me the list of Glimpse related NuGet Packages installed in the project where you are adding your service reference?
Just check the packages.config file
My first idea is that the custom tool generating the client classes when adding the service reference, is not talking the web.config into account, where the binding redirects are being configured. Most likely it is loading all assemblies in the project's bin folder into memory and applying some reflection upon it, hence a specific Glimpse assembly, one depending on Glimpse.Core 1.8.2, is loaded, but since the bin folder most likely contains a newer version of the Glimpse.Core and there are no binding redirects defined for that custom tool process the tool crashes
I'm not sure if that can be solved directly, and somehow I guess other assemblies added by means of NuGet packages might have the same problem, but to be sure we first need the information above to try to reproduce it, just to make that is actually the problem
—
Reply to this email directly or view it on GitHub.

Are you able to create a sample which reproduces the issue?

It seems that when I install Glimpse.MVC4 it is when I start seeing the problem. I can install Glimpse Core and Glimpse ASP.NET and the project doesn't have a problem but as soon as I install Glimpse MVC4 I start seeing the error.
I have a project in my Dropbox account - https://www.dropbox.com/s/hb3prz7p7p0u3zp/OaisysDemo.zip?dl=0
The state of the project is Glimpse MVC4 has not be installed yet. This project has two web references. If these require access that you don't have remove them and try to add another reference that you know will work. I suspect that after Glimpse MVC4 has been install the import of the service reference (VS 2013) will fail.

For this sample, is it possible that you start with a new project and add
in components until you find the combination that breaks, or from the
project you have remove everything that doesn't have to do with the problem
until you find the issue?
On 26 March 2015 at 11:23, KevinBurton<EMAIL_ADDRESS>wrote:

It seems that when I install Glimpse.MVC4 it is when I start seeing the
problem. I can install Glimpse Core and Glimpse ASP.NET and the project
doesn't have a problem but as soon as I install Glimpse MVC4 I start seeing
the error.
I have a project in my Dropbox account -
https://www.dropbox.com/s/hb3prz7p7p0u3zp/OaisysDemo.zip?dl=0
The state of the project is Glimpse MVC4 has not be installed yet. This
project has two web references. If these require access that you don't have
remove them and try to add another reference that you know will work. I
suspect that after Glimpse MVC4 has been install the import of the service
reference (VS 2013) will fail.
—
Reply to this email directly or view it on GitHub
https://github.com/Glimpse/Glimpse/issues/892#issuecomment-86655957.

The combination that breaks is I add Glimpse Core and Glimpse ASP.NET and the step that breaks is installing Glimpse MVC4.

@KevinBurton before you install Glimpse.Mvc4 do you see a Glimpse 1.8.2 being mentioned in the dependency graph?
Can you check with the Glimpse.Elmah assembly as well? (I saw that package in your first list of packages)
Either way, I can build your solution you made available on Dropbox, and I was able to add a reference to another service and compile without any problem.

So I downloaded the zip
opened solution in VS2013
compiled => no issue
added another service => no issue
compiled again => no issue
removed added service
installed package Glimpse.Mvc4 => no issue
compiled => no issue
added another service => no issue
compiled => no issue
added even Glimpse.Elmah => no issue
compiled => no issue

so I have no idea where to go further
can you enable logging of assembly bindings? so that you can see the load failure with the fuslogvw.exe that might give you an idea about the application directory from where the custom tool is started and where it starts looking for the Glimpse assembly...

It is definitely Glimpse MVC4. When I add it an try to update the service reference I get the error and warnings. Once it is removed I no longer get the error. I am not entirely familiar with fuslogvw. But, invoking it in an administrator window yields no information. It is blank both before and after.

@KevinBurton it is quite possible that the Glimpse.Mvc4 might trigger the issue, but the question remains whether it is the root cause, which for me is still not clear.
Regarding the fuslogvw.exe, you must enable it first before bindings are being traced

It's possible you might have to reboot VS2013 if it remains empty, but you should be able to see something...
Either way, can you describe a good reproducible case, as in:

create new empty web project
add the following packages....
add service reference pointing to a wsdl (can you try for instance with this free online webservice: http://www.service-repository.com/service/overview/517838238 so if you have issues with that one as well, then we can take your services out of the equation)
add glimpse.mvc4
BROKEN?....

Still broken. I just started a new MVC project, added Elmah, Glimpse.Core, and Glimpse.ASP.NET. I ran the project and it showed the default ASP.NET page. Then I added Glimpse.MVC4 again I tried the application and it seemed to work. When I tried to add a service reference (with fuslogvw running as administrator and the settings set as you suggested) I get the error that I have illustrated earlier. Nothing showed up in fuslogvw. If I click on "settings" and close it out it seems to have the same effect as refresh. The UI seems questionable. I don't see an attempt to load Glimpse 1.8.2. I do see a failure for almost all the other Glimpse and Elmah assemblies. This is what I see:

@KevinBurton do you have the same issue with the example soap service I provided? Otherwise we need your wsdl to try to reproduce it...
are these all bind failures shown in the printscreen? Or just all binds? Either way, you should be able to delete them all and then run the add service reference, then at least the new entries should be related to running the custom tool, if that is the issue

The problem is that these "error" seem to occur in a batch. They occur at the same time or near the same time and they occur all when i try to add a service reference. These are the new entries.

Ah ok, makes sense
could you send us the details for instance of the log entry for the Glimpse.Core 1.8.6 ? Just doubleclick it to get the details, you should be able to see the working directory there as well.
It is strange though that we see a fail entry for Glimpse.Core 1.8.6 and not for the 1.8.2
Regarding the 1.8.2, I think it is the Glimpse.Elmah assemlby that is linked to that one, so do you see a Glimpse.Elmah log entry in there somewhere?
Either way, do you have the same issue with the other service I pointed you to? It is just that I can still not reproduce the issue, which makes it kinda hard to figure it all out :wink:

Forgive me but I am not sure how to check the log entry for Glimpse.Core 1.8.6. I am not sure where to double click on to get the log.
I don't try to install the Glimpse.Elmah package so I don't think it is the culprit. It is only when I try to install the Glimpse.MVC4 package that I start seeing the errors.
I don't seem to have access to http://www.service-repository.com/service/overview/517838238 as when I try to add a service reference to this service I get an error:

@KevinBurton the service url can be found at the link I mentioned, the link itself is not the service. If you go to that page then you'll find the following link: http://www.predic8.com:8080/shop/ShopService?wsdl which you should try to use...
I know you don't try to install the Glimpse.Elmah package, but is it already installed?
If so, do you have the same problem if you first uninstall that package and then add the Glimpse.Mvc4 package?
In the fuslogvw overview, you can just double-click on a specific entry or click on a log entry en choose View Log in the right menubar
Either way, the Glimpse.Elmah check (if applicable) might already give a better idea on the situation

Thank you. I do not install and it is not already installed (Glimpse.Elmah).
I tried adding the service that you indicated rather than the one that I was trying and I no longer get the error about Glimpse 1.8.2 after I add Glimpse.MVC4. So what do you think this means? After installing Glimpse.MVC4 I can install and update the service that you specified but the service that I need to install will not install or update after Glimpse.MVC4 is installed. The error I get is detailed earlier as there is some reference to Glimpse 1.8.2. I cannot imagine that the service I install has a reference to Glimpse 1.8.2 as it is a service reference. It shouldn't matter but it does. One works and another doesn't. Ideas?

Is this still an issue for you?

I have not been able to solve it yet.
From: Anthony van der Hoorn<EMAIL_ADDRESS>Sent: Thursday, April 23, 2015 6:20 PM
To: Glimpse/Glimpse
Cc: KevinBurton
Subject: Re: [Glimpse] Install Glimpse now I cannot add service references? (#892)
Is this still an issue for you?
—
Reply to this email directly or view it on GitHub https://github.com/Glimpse/Glimpse/issues/892#issuecomment-95745749 .  https://github.com/notifications/beacon/AChWbmirMlqYjd3uYRkX_hzCqTV9crU2ks5oCXWxgaJpZM4D1KlZ.gif

I have same issue, when I try to create/update WCF service client.
Installed Glimpse packages: