Firmware 04.08.02 not supported?

Hi,
I want to use this integration with Buderus WSW196iT heat pump. It has integrated KM200 interface. After proper configuration, integration starts but shows one device with no entities at all.

Debug show info that firmware might be not supported. Can I do anything to make it working?
debug.txt
attached bosch_scan.json
bosch_scan.zip

No entity after update

Hi,
I want to use this integration with Buderus WSW196iT heat pump. It has integrated KM200 interface. After proper configuration, integration starts but shows one device with no entities at all.

Debug show info that firmware might be not supported. Can I do anything to make it working? debug.txt
attached bosch_scan.json bosch_scan.zip

I think Buderus sent updates to the km200 gateways.  My configuration stopped working today with a incompatibility message in home assistant

I released pre release 0.17.2. Can you check it out?

Unfortunately update didn't help. Deleting and adding integration again doesn't help either. Debug still shows the same error:
2022-01-31 20:31:20 INFO (MainThread) [custom_components.bosch] Setting up Bosch component version 0.17.2.
2022-01-31 20:31:20 DEBUG (MainThread) [custom_components.bosch] Initializing Bosch integration.
2022-01-31 20:31:20 DEBUG (MainThread) [custom_components.bosch] Checking connection to Bosch gateway as <IP_ADDRESS>.
2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/uuid
2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/bus
2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/versionFirmware
2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/brand
2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/info
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/systemType
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/DateTime
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'iCom_Low_NSC_v1', 'name': 'Enviline/Compress 6000/7000', 'type': 'NSC_ICOM_GATEWAY'} with id 172
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'RC300', 'name': 'RC300/RC310/Nefit Moduline 3000', 'type': 'RC300_RC200'} with id 158
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Using model iCom_Low_NSC_v1 as database schema
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.base] Found device {"value": "iCom_Low_NSC_v1", "name": "Enviline/Compress 6000/7000", "type": "NSC_ICOM_GATEWAY"}
2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.db] Attempt to load database from file /usr/local/lib/python3.9/site-packages/bosch_thermostat_client/db/nsc_icom_gateway/040802.json
2022-01-31 20:31:21 ERROR (MainThread) [custom_components.bosch] You might have unsuporrted firmware version 04.08.02
2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Bosch BUS detected: EMS
2022-01-31 20:31:21 INFO (MainThread) [custom_components.bosch] Bosch initialized.
2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Registering services.
2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Bosch component registered with platforms [].

Unfortunately update didn't help. Deleting and adding integration again doesn't help either. Debug still shows the same error:
2022-01-31 20:31:20 INFO (MainThread) [custom_components.bosch] Setting up Bosch component version 0.17.2. 2022-01-31 20:31:20 DEBUG (MainThread) [custom_components.bosch] Initializing Bosch integration. 2022-01-31 20:31:20 DEBUG (MainThread) [custom_components.bosch] Checking connection to Bosch gateway as <IP_ADDRESS>. 2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/uuid 2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/bus 2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/versionFirmware 2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/brand 2022-01-31 20:31:20 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/info 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /system/systemType 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.connectors.http] Sending GET request to /gateway/DateTime 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'iCom_Low_NSC_v1', 'name': 'Enviline/Compress 6000/7000', 'type': 'NSC_ICOM_GATEWAY'} with id 172 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Found supported device {'value': 'RC300', 'name': 'RC300/RC310/Nefit Moduline 3000', 'type': 'RC300_RC200'} with id 158 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.ivt] Using model iCom_Low_NSC_v1 as database schema 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.gateway.base] Found device {"value": "iCom_Low_NSC_v1", "name": "Enviline/Compress 6000/7000", "type": "NSC_ICOM_GATEWAY"} 2022-01-31 20:31:21 DEBUG (MainThread) [bosch_thermostat_client.db] Attempt to load database from file /usr/local/lib/python3.9/site-packages/bosch_thermostat_client/db/nsc_icom_gateway/040802.json 2022-01-31 20:31:21 ERROR (MainThread) [custom_components.bosch] You might have unsuporrted firmware version 04.08.02 2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Bosch BUS detected: EMS 2022-01-31 20:31:21 INFO (MainThread) [custom_components.bosch] Bosch initialized. 2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Registering services. 2022-01-31 20:31:21 DEBUG (MainThread) [custom_components.bosch] Bosch component registered with platforms [].

It's not fixed probably because 040802.json has to be added to .../bosch_thermostat_client/db/nsc_icom_gateway/ directory not .../bosch_thermostat_client/db/rc300_rc200/

I know, I think they unified firmware version for both heat pump and RC300.

iCom_Low_NSC_v1
Firmware: 04.07.07 works great.
Finally got 'Return Temperature' back

https://github.com/bosch-thermostat/home-assistant-bosch-custom-component/releases/tag/v0.17.3

@pszafer thank you, v0.17.3 works with firmware 04.08.02 on IVT Geo 500.


create + get + delete task

Description
[Multi tenancy enabled for Create + Get + Delete task
sdk client is not implemented for Create task yet. I'll do that when I'll work in deploy api. Trying to keep the PR smaller.
]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks like tests failing on compile errors from https://github.com/opensearch-project/ml-commons/pull/2553 which was merged with failing compile checks.

Looks like tests failing on compile errors from #2553 which was merged with failing compile checks.

Looks like tests failing on compile errors from #2553 which was merged with failing compile checks.

Added this commit now to fix the compile issue: https://github.com/opensearch-project/ml-commons/pull/2564/commits/72ff4b2eb3b142478dee8406efb6739528eb2f59
Tests are passing now. I'm going to merge this PR now then.


Events not working inside shadow root

I tried using this library. to render a component inside shadow root but the click events in children, copy/paste event on the canvas(canvas is rendered inside shadow DOM) and custom context menu doesn't work.

Hmm, could you please create a Codesandbox with an example of what doesn't work for you?

@Wildhoney Its currently under development, I will share the link soon

@Wildhoney here is the code sandbox link
I tried using shadow DOM to integrate excalidraw
You can try copy-pasting the shapes you draw or doing right-click, it's not working when inside shadow-dom.
and here is without shadow dom

Events do work, but I suspect it's more an issue with <iframe /> rendering in the excalidraw library. Maybe you want to open a ticket with them to investigate?
I did a little look around and and found a thread that mentioned: "The basic gist is that each Hosted Fields iframe requires access to window.parent.frames, but when an iframe is added to the shadow dom, it is not added to window.frames, so the Hosted Fields iframes cannot initialize."
Perhaps the creators of excalidraw are doing something similar or related @ad1992?

@Wildhoney I am not using Iframe to render inside excalidraw, You can check that in the above link as well. I have created an npm package which can be used to render inside host app itself, in case you want to check the code its here https://github.com/excalidraw/excalidraw-embed

Sorry,  I was referring to the dialogs that open, such as the share button. It seems all the buttons that don't do anything open and render their content in iframes, whereas the buttons that don't open iframes (such as create a circle) work perfectly well.

Looking again, I suspect it's something in the excalidraw stylesheet, as putting the stylesheet outside of the shadow boundary causes it to show up: https://codesandbox.io/s/react-shadow-r8gwc?file=/src/index.js
Events are working either way though, so that's unrelated. It's just the styles for the modal don't get applied.

Looking again, I suspect it's something in the excalidraw stylesheet, as putting the stylesheet outside of the shadow boundary causes it to show up: https://codesandbox.io/s/react-shadow-r8gwc?file=/src/index.js
Events are working either way though, so that's unrelated. It's just the styles for the modal don't get applied.

@Wildhoney Iframe is not used anywhere and in the above link, the context menu is opening but still shortcut link cmd+c/cmd+v keys don't work and the color picker also doesn't work when using shadow DOM. Not sure whats going on 🤔

@ad1992 I believe it might be associated to how React handles events (pre React 17). Some info can be found in this issue


Add obscure v0.6 postOp() behavior

Hello @aviggiano - I recently became aware of some interesting/obscure behavior in the v0.6 entrypoint, and thought it could be useful to add to the checklist as well. WDYT?

Hey, thanks for the contribution.
I wasn't aware of this issue, and it's nice to add it to the checklist, although as they mentioned is not a critical one. It's a good recommendation though.

@aviggiano awesome - would you be able to merge this PR in?

Yes I was waiting to see if you had any other comments
Merging!


not support for XCode 9.1 & XCode 9.2

thank for your feedback, fixing

fixed, you can download the demo again


Confirm The Ending. confirmEnding("Open sesame", "same"); should return false instead of true.

Challenge Confirm the Ending has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/53.0.2785.143 Chrome/53.0.2785.143 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function confirmEnding(str, target) {
  // "Never give up and good luck will find you."
  // -- Falcor
  var arr = str.split(" ");
  if (arr[arr.length - 1] == target){
    return true;
  }
  else {
    arr = str.split("");
    if(arr[arr.length - 1] == target){
      return true;
    }
    return false;
  }
}

confirmEnding("Open sesame", "same");

confirmEnding("Open sesame", "same"); should return false instead of true.
Please fix it.

Hi @mtyrio! Thank you for reporting this issue.
The challenge here is to check whether all of the letters in the target equal all of the last letters of the string. You're only checking the last letter.
The letters to check in this test case are "same". The last four letters of "Open sesame" are "same". As you can see, the ending matches, so the result should be true.
If you need coding help, please click the "Help" button on the challenge.
If you think I'm wrong in closing this issue, please reopen it and add further clarification.
Happy coding!

`function confirmEnding(str, target) {
// "Never give up and good luck will find you."
// -- Falcor
//var arr = str.split(' ');
//str = arr[arr.length-1];
str = str.substring(str.length-target.length);
return str == target ;
}
confirmEnding("He has to give me a new name", "name");`


.last/.first should not add _id: 1 sorting in some cases

In case when there any other sorting conditions in current Criteria scope, Mongoid should not add _id: 1 ordering options, on "first" and "last" calls, because this can cause selection without using indexes, and cause performance degradation on large collections.
Also, I think it will be better use natural ordering instead of just sorting by primary keys, since there no such thing like "first" or "last" record in mongo collections.

Since Mongoid was previously guaranteeing order by the primary key on first/last, I'm going to have to flag this for 3.0.0 since it's backwards compatible... If you need a workaround for this you can monkey patch the mongo context by just changing the lines in the first/last methods...
lib/mongoid/contexts/mongo.rb:
sorting << [:_id, :asc] if sorting.empty?


Make all inputs their own packages

Gone back and forth on this a couple times. Convinced inputs should be independent packages w/ an Input interface gluing everything together.

Should consist of:

Associated routes (inc squawk)
Event repr
Envelope builder


Remove misleading hardware requirements hint

Not sure why you think the links to k3s/rke2 are misleading ?! 🤔

Yes in fact as you put links to the docs and not copy/paste the requirement values directly it's OK to keep as-is, we're still safe from Elemental PoV as we are not writing "fixed" values for these requirements.

Since @kkaempf pointed out this is not actually misleading and @ldevulder also agrees it is fine to have these recommendation, I'll drop the PR.


Something is wrong with escaped type names parsing

I'm using Sourcery 10.1 (but it seems to be reproducible with head version too).
protocol AutoHashable {}
protocol AutoEquatable {}

public struct Model: AutoEquatable, AutoHashable {
    public enum `Type` {
        case foo
    }

    public let type: `Type`
}

extension Model.`Type`: AutoEquatable, AutoHashable {
    public init?(rawValue: String) { self = .foo }
    public var rawValue: String { return "" }
}

Generated code is not compilable as "Type" is not fully escaped. Also, var hashValue is not public as the rest of the code.
extension Model: Hashable {
 // everything is fine here
}
// MARK: - Model.`Type AutoHashable
extension Model.`Type: Hashable {
     var hashValue: Int {

        return combineHashes([
            0])
    }
}

Same happens in AutoEquatable. codel
If I replace Type with MyType  and remove backticks everything is fine.
I don't have full knowledge of how Sourcery works under the hood, but it may go as deep as SourceKit:

Xcode itself fails to provide proper highlighting (but it compiles).

Strange, when I run this code through I got name Model.Type without back ticks

It's weird, I tracked it down to this pr https://github.com/krzysztofzablocki/Sourcery/pull/169 but can't remember why I did it and even it's name is opposite to what is done 😅
So I'll revert it, with it type names will not be escaped, so type.name should be correct.


feat: initial support for cron container

Hi @jippi
Thank you for the cron container, it was a problem to me as stories was not working. This should solve the issue.
But my container refuse to start:

As everything else works well, I assume this is specific to this container. Any thought?

Nevermind, using v0.12.3 solved the issue.


Tests: Ignore warnings from PandasUsing

Closes https://github.com/Nuitka/Nuitka/issues/2013

See my comment, this is the "wrong" solution. Instead, the "info" given should be properly recognized, which it will be with my recent changes.

ok


tensorflow.python.framework.errors_impl.InternalError: Failed to create session.

I am running some preparation code with tf, it seems it doesn't to much memory for it. But:
(tensorflow) lab-huang.zhongyi@gpu-2:~/workspace/vae-npvc$ python build.py
452 files found
Processing Tensor("ReaderReadV2:0", shape=(), dtype=string)
2017-11-10 12:24:55.938368: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.1 instructions, but these are available on your machine and could speed up CPU computations.
2017-11-10 12:24:55.938398: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use SSE4.2 instructions, but these are available on your machine and could speed up CPU computations.
2017-11-10 12:24:55.938408: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX instructions, but these are available on your machine and could speed up CPU computations.
2017-11-10 12:24:55.938427: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use AVX2 instructions, but these are available on your machine and could speed up CPU computations.
2017-11-10 12:24:55.938435: W tensorflow/core/platform/cpu_feature_guard.cc:45] The TensorFlow library wasn't compiled to use FMA instructions, but these are available on your machine and could speed up CPU computations.
2017-11-10 12:24:57.272601: E tensorflow/core/common_runtime/direct_session.cc:138] Internal: failed initializing StreamExecutor for CUDA device ordinal 0: Internal: failed call to cuDevicePrimaryCtxRetain: CUDA_ERROR_OUT_OF_MEMORY; total memory reported:<PHONE_NUMBER>
Traceback (most recent call last):
File "build.py", line 100, in
main()
File "build.py", line 24, in main
with sv.managed_session() as sess:
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/contextlib.py", line 59, in enter
return next(self.gen)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/supervisor.py", line 964, in managed_session
self.stop(close_summary_writer=close_summary_writer)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/supervisor.py", line 792, in stop
stop_grace_period_secs=self._stop_grace_secs)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/coordinator.py", line 389, in join
six.reraise(*self._exc_info_to_raise)
File "/home/lab-huang.zhongyi/.local/lib/python3.5/site-packages/six.py", line 693, in reraise
raise value
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/supervisor.py", line 953, in managed_session
start_standard_services=start_standard_services)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/supervisor.py", line 708, in prepare_or_wait_for_session
init_feed_dict=self._init_feed_dict, init_fn=self._init_fn)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/session_manager.py", line 273, in prepare_session
config=config)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/session_manager.py", line 178, in _restore_checkpoint
sess = session.Session(self._target, graph=self._graph, config=config)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1292, in init
super(Session, self).init(target, graph, config=config)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 562, in init
self._session = tf_session.TF_NewDeprecatedSession(opts, status)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/contextlib.py", line 66, in exit
next(self.gen)
File "/home/lab-huang.zhongyi/anaconda3/envs/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/errors_impl.py", line 466, in raise_exception_on_not_ok_status
pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.InternalError: Failed to create session.
and when I checkout "nvidia-smi", some GPUs still have many memory:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.66                 Driver Version: 375.66                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1080    On   | 0000:04:00.0     Off |                  N/A |
| 49%   69C    P2    57W / 180W |   8046MiB /  8114MiB |     45%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1080    On   | 0000:05:00.0     Off |                  N/A |
| 48%   69C    P2    53W / 180W |   7393MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 1080    On   | 0000:08:00.0     Off |                  N/A |
| 53%   72C    P2    54W / 180W |   7917MiB /  8114MiB |     19%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 1080    On   | 0000:09:00.0     Off |                  N/A |
| 60%   76C    P2    54W / 180W |   7413MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   4  GeForce GTX 1080    On   | 0000:84:00.0     Off |                  N/A |
| 24%   41C    P8    12W / 180W |   2684MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   5  GeForce GTX 1080    On   | 0000:85:00.0     Off |                  N/A |
| 24%   35C    P8    12W / 180W |   1895MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   6  GeForce GTX 1080    On   | 0000:88:00.0     Off |                  N/A |
| 67%   82C    P2   163W / 180W |   6105MiB /  8114MiB |     88%      Default |
+-------------------------------+----------------------+----------------------+
|   7  GeForce GTX 1080    On   | 0000:89:00.0     Off |                  N/A |
| 67%   82C    P2   144W / 180W |   6097MiB /  8114MiB |     89%      Default |
+-------------------------------+----------------------+----------------------+
and here is the code:
https://github.com/JeremyCCHsu/vae-npvc/blob/master/build.py
Thank you all so much, I am really just a beginner.

Oh it it really don‘t  enought memories.
I solved it by allocating memories dynamically:
import tensorflow as tf
import os
os.environ["CUDA_VISIBLE_DEVICES"] = '0'   #use GPU with ID=0
config = tf.ConfigProto()
config.gpu_options.per_process_gpu_memory_fraction = 0.5  # maximun alloc gpu50% of MEM
config.gpu_options.allow_growth = True      #allocate dynamically
sess = tf.Session(config = config)

In my case, it was installing:
sudo apt install nvidia-cuda-toolkit
which seemed to do the trick.  It updated the drivers to a newer version (looked like 410).  First, the ppa was added:
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update


bugs in the masking code

hi, i found that in decoder there is a subsequent mask which mask out the future information here . However, in line 123, you feed in the dec_input(which is the target embeding) at first layer.  now  check this line and then the MultiHeadAttention moudle's forward function, it has a residual connection and will make dec_input directly reached output, see here.  so it doest not use the subsequent mask,  which means that the model knows the future.  am i correct?

may be that can expalin why i get 99.9% correct on the multi30k validation set  using your code.

sorry, i made a mistake, it actually doesnot know the future, because at a paticular timestep, it only use current target words and the attention over the past words.

sorry to re-open this issue still, during inference, i think your code is wrong, because it feeds the current groundtruth words.

Hi @eriche2016 ,
I think the residual connection issue is a misunderstanding?
The residual part will not let the word access the future words.
It is a validation part, not inference part, and it is in a teacher forcing fashion.
So I think feed in the groundtruth words is not inappropriate?
The validation part in OpenNMT-py may be worth checking.
Besides, I will not do this during inference, please check the code in Translator.py.

no, in evaluation mode, you cannot feed in the current groudtruth words.  you can see here, i guess they use previous predicted word and shift the groundtuth sentence

hi, @jadore801120, what's the point using eval in train.py by feeding current groundtruth words to evaluate your model here? i am wandering it will be better if we can evalute it here.  what is your opinion?

teacher forcing  is  used  to  train  the  model， i doubt  it  can  be  used  for  validating  or  evaluating  the  model

check here, i am new machine translating field. If i am correct, using current groundtruth words to validate your model is accceptable? or is it a commonly practice. I think that this validation performance of the MT model is surely unreliable and tells us nothing about the models generatlization ability because it is using the currently groundtruth label.

i think we need to add a teacher forcing ratio and set it to 0 when we want to validate the model.


New version: Logitech.LGS version 9.04.28

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Resolves #56313

Microsoft Reviewers: Open in CodeFlow

@wingetbot help

@wingetbot run

@wingetbot waivers Add Validation-Domain


[Misc] Add uninitialized params tracking for AutoWeightsLoader

Currently, model have uninitialized parameters won't raise any error even a warning message. This makes some bugs like https://github.com/vllm-project/vllm/pull/10297#discussion_r1840989950 and https://github.com/vllm-project/vllm/pull/9422#issuecomment-2418746915 caused by incorrect weights loading/model initialization difficult to be found.

Add feature to track uninitialized weights for AutoWeightsLoader.

Hmm. not sure whether we're being too strict or is the weight loader buggy?

Hmmm, seems that strict=True is too strict for sharded safetensors, because in that case the weights of a module will be sharded into multiple files, and it will trigger strict check then raise error while the module is partially loaded from one of the shared files...
Perhaps we should add the loading check on top of DefaultModelLoader in loader.py instead of AutoWeightsLoader.

Agreed, let's move the weight loading check to a higher level.

Since we may skip loading some layers in vision models / PP case, we should update the check to error out when weights inside the initialized model fail to be loaded, rather than when some weights from the checkpoint aren't loaded.

I found that this PR causes speculative tests to fail on main. PTAL @Isotr0py


Removed use of ProcessBuilder

Hello,
Version 4.1 of Sami is currently not working when using GitVersionCollection, because it relies on Symfony\Component\Process\ProcessBuilder, which has been removed in version 4 of symfony/process.
Version 4.0 of Sami pointed to version ~3.0 of symfony/process, so that works regularly. According to the Symfony upgrade guide, instead of relying on ProcessBuilder, we just use Process directly.
The Phar at http://get.sensiolabs.org/sami.phar is affected, so it might be breaking some CI builds (that's how I discovered about this).

Thank you @dborsatto.


properties don't update if set to current value

This will prevent resources from getting _dirty if they are set to the same thing, and prevent _on_prop_change from firing.
This requires implementing equal in properties.

In v >= 0.2.0 this is still an issue. Now, this requires implementing a third type of listener besides validate and observe

Implemented in #125, thanks to equal method.


Analysis of target '//cc:libtink.so' failed

This seems to be a quite common error as I can see this in several previous issues as well like #134, although I am using Linux Ubuntu machine. Can someone tell the exact steps that I need to follow in order to get this setup running as I am not able to figure it out otherwise.

Hi Shubham,
could you please provide more info on  the issue, like which command failed and what was the log output?  (the issue #134 was resolved by #151)
Thanks!

@coder579 please reopen if you can provide more info as @przydatek suggested. Thanks!


Bring location finding in

As per: https://github.com/praekelt/go-usaid-clinicfinder/blob/develop/src/app.js
Current functionality is just a placeholder. Please transfer code as-is into this repo.

@imsickofmaps please review.  not sure if current qa config file will do... it looks ok

@NicolaasDieBaas ping me again when you've made the search change and I'll review all together

@imsickofmaps please review

👍

@NicolaasDieBaas landing for QA deploy


Just crush when I click "Run"

So I tried Whisper Largev3 and tiny, Faster Whisper Larvev3 and tiny. Task Transcribe, language English, export TXT. Windows 11

@gogolevmatvey Can you please check the logs. Paste this in Windows address bar %USERPROFILE%\AppData\Local\Buzz\Buzz\Logs and check what is in the logs.txt
Does your PC have a GPU? If so what GPU is it?
Also please try some Whisper.cpp model size. Whisper.cpp will use CPU so may help us identify some GPU related issues.
If the export TXT is checked Buzz will save the transcript to the same location where the input audio or video file is located. Is this location regular folder or maybe some network drive.
Something strange is happening on your system that is not usually happening. Let's see if we can debug what is causing this.
Feels like you may be running into some issue with ffmpeg. Did you install the Buzz v1.1.0 with the installer from the releases section or by some other means?

Sorry, I forgot to tell that I'm trying to transcribe YouTube video by URL. It's only now that I realized that maybe it's not supported.
I have rtx 2060.
Same with Whisper.cpp
I installed from the releases section.

@gogolevmatvey  Support for YouTube urls via File -> Import Url was fixed recently. You can get the version where this works here https://github.com/chidiwilliams/buzz/actions/workflows/ci.yml?query=branch%3Amain
To download you will need to log into the Github.

@raivisdejus I don't understand how to get it there

@gogolevmatvey Yes, first time around this can be a bit confusing. Hope the screenshots will help.
So first you need to select any latest build in the link I posted above.

Then scroll down to the artifacts section and click the download icon near Buzz-Windows-X64

You need to be logged in to the Github to see the download link.
A .zip file will be downloaded, unzip it and the Buzz installation will be in it.

@raivisdejus Sorry, I just needed to scroll down


npm shows 4 high severity vulnerabilities

npm audit report
async  <2.6.4
Severity: high
Prototype Pollution in async - https://github.com/advisories/GHSA-fwr7-v2mv-hh25
No fix available
node_modules/jake/node_modules/async
jake  >=8.0.1
Depends on vulnerable versions of async
node_modules/jake
ejs  >=3.1.2
Depends on vulnerable versions of jake
node_modules/ejs
@opensaas/keystone-nextjs-auth  *
Depends on vulnerable versions of ejs
node_modules/@opensaas/keystone-nextjs-auth
4 high severity vulnerabilities

Hi @muhad-bk
Thanks for flagging this, these packages have now been patched.
Thanks


[Formrecognizer] Update analyze API to require document length

Update analyze API to require document length when sending the analyze request to the service.
The document length is required by downstream restproxy and cannot be null. This will  require the users to initialize binary data document using:
BinayrData document = BinaryData.fromStream(inputStream, length) when using this API.

API change check
API changes are not detected in this pull request.


1 test failed. relative time:custom rounding (2721.3)

Client info
Date String   : Wed Mar 08 2017 09:24:46 GMT+0100 (Västeuropa, normaltid)
Locale String : 2017-03-08 09:24:46
Offset        : -60
User Agent    : Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
Moment Version: 2.17.1

====
relative time:custom rounding (2721.3)
Round down towards the nearest day
// Expected in 30 days
// Actual   in a month
"in a month" === "in 30 days"

Thanks for making an issue.
This is a duplicate of #3801


[BUG] guaranteed-engine-manager-cpu and guaranteed-replica-manager-cpu settings are no longer supported

Describe the bug

Longhorn's guaranteed-engine-manager-cpu and guaranteed-replica-manager-cpu settings are no longer supported and replaced by guaranteed-instance-manager-cpu.
Note this applies to the upcoming v1.2.2 release (Longhorn v1.5.5) and v1.3.0 (Longhorn v1.6.0). v1.2.1 still uses Longhorn v1.4.3 and doesn't have this issue.
To Reproduce
Steps to reproduce the behavior:

Install the harvester with the two configurations:

https://docs.harvesterhci.io/v1.3/install/harvester-configuration#installharvesterlonghorndefault_settingsguaranteedenginemanagercpu
https://docs.harvesterhci.io/v1.3/install/harvester-configuration#installharvesterlonghorndefault_settingsguaranteedreplicamanagercpu

These settings don't take effect.

Expected behavior

We should support configuring the CPU on instance-manager pod with the guaranteed-instance-manager-cpu setting.
We should update the document.

Support bundle

Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

@albinsun It looks like all v1.3/v1.2 backport issues are all verified. Can you also help check this main issue?

Test Result

Overall Status: InProgress

Environment

harvester-v1.4.0-dev-20240918

Profile: 2 nodes QEMU/KVM (8C/16G/500G per node)
ui-source: Auto

Prerequisite

 VM => ⋮ => Migrate

Check 1
SCREENSHOT

Scenarios
w/o install.harvester.longhorn.default_settings.guaranteedInstanceManagerCPU

 :yellow_circle: No any configs -> cpu should be 960m (8 x 1000m x 0.12 (default value))

842 / 0.12 / 1000 ~ 7.02
Behavior not the same as v1.3.1

 :white_circle: Even with guaranteedEngineManagerCPU & guaranteedReplicaManagerCPU -> cpu should still 960m

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

w/ install.harvester.longhorn.default_settings.guaranteedInstanceManagerCPU

 :white_circle: guaranteedInstanceManagerCPU: 10 -> cpu should be 800m (8 x 1000m x 0.10)

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

 :white_circle: guaranteedInstanceManagerCPU: 13 -> cpu should be 960m (8 x 1000m x 0.12)

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

 :white_circle: guaranteedInstanceManagerCPU: 12 -> cpu should be 960m (8 x 1000m x 12)

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

 :white_circle: guaranteedInstanceManagerCPU: 0 -> Not to explicit requests CPU limit

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

 :white_circle: guaranteedInstanceManagerCPU: q -> Should error due to non-integer

Check 1
SCREENSHOT
Check 2 :x:

:warning:: Fail due to reason
SCREENSHOT

Supportbundle
Note

...

QA Check List

[ ] Labels: not-require/test-plan, not-require/release-note, require-ui, regression...
[ ] Update corresponding tests ticket lables

Hi @w13915984028 ,
We found the behavior in v1.4.0-dev-20240918 is not indentical to v1.3/v1.2.
Using the same 8 cpus, I get 842m (7.02 x 1000m x 0.12) not 960m (8 x 1000m x 0.12).
Is this expected?
cc. @bk201

@albinsun The differences should be related to node usable CPU, in each version (with different rke2&k8s) the node usable CPU may vary as  k8s reserves some CPU for itself at first,  when LH  tries to get a percentage CPU from the node, it is based on the kubeNode.Status.Allocatable.Cpu, not the physical available CPU on the node.
For the validation, we can compare: the LH CPU with [guaranteed-instance-manager-cpu] and without (use the default value) in the same version, with bigger guaranteed-instance-manager-cpu LH get more CPU.
Comparing the absolute CPU value between different releases can be an reference.
thanks.
LH CPU resources calculation code, there looks no change.
allocatableMilliCPU := float64(kubeNode.Status.Allocatable.Cpu().MilliValue())

https://github.com/longhorn/longhorn-manager/blob/a3768493385042b65da343d569daa9e977ebf928/controller/controller_manager.go#L273
https://github.com/longhorn/longhorn-manager/blob/3dde300284b4a7ca8dfa1c2757ee2c2613c766be/controller/controller_manager.go#L161

Test PASS, close as fixed.
Environment

harvester-v1.4.0-dev-20240918

Profile: 2 nodes QEMU/KVM (8C/16G/500G per node)
ui-source: Auto
Allocatable CPU: 7.02

Scenarios
w/o guaranteedInstanceManagerCPU

 No any configs -> cpu should be 842m :heavy_check_mark:

7.02 x 1000m x 0.12 (default)

 Even with guaranteedEngineManagerCPU & guaranteedReplicaManagerCPU -> cpu should still 842m :heavy_check_mark:

7.02 x 1000m x 0.12 (default)

w/ guaranteedInstanceManagerCPU

 guaranteedInstanceManagerCPU: 10 -> cpu should be 702m :heavy_check_mark:

7.02 x 1000m x 0.10

 guaranteedInstanceManagerCPU: 13 -> cpu should be 842m :heavy_check_mark:

PXE Server

Harvester

7.02 x 1000m x 0.12 (default)

 guaranteedInstanceManagerCPU: 0 -> Not to explicit requests CPU limit :heavy_check_mark:

PXE

Harvester

 :white_circle: guaranteedInstanceManagerCPU: q -> Should error due to non-integer :heavy_check_mark:

Reference

https://docs.harvesterhci.io/v1.4/install/harvester-configuration#installharvesterlonghorndefault_settingsguaranteedinstancemanagercpu
https://longhorn.io/docs/1.7.1/references/settings/#guaranteed-instance-manager-cpu

QA Check List

[ ] Labels: not-require/test-plan, not-require/release-note, require-ui, regression...
[ ] Update corresponding tests ticket lables


Proposed server rules

This is a blend of https://907.life/about and https://ottawa.place/about/more plus a bit of our own context.
Good enough for now?

OK I've shortened them up massively, and added the land acknowledgement as suggested by @ShaneK777 here.
WDYT @tillkruss is this better?


Redesign of artist header

Redesign for the artist page header. Important components:

artist name / nationality, dates / follower count (like on the web; image attached below)
follow button with a following state
a tab-y view switcher (already exists on the 'You' view in switching between favorite artworks, artists, categories)

Header overview:

Spec for the iPhone artist header:

Spec for the iPad portrait and landscape header (only changes from the iPhone header are marked):

For reference, here's the web version:

10/10 points for a great issue.
:star2:

Closing in favor of https://github.com/artsy/eigen/issues/1131


Tentant

This is really nitpicky, but I've noticed that "tenant" is referred to as "tentant" quite a few times in the code. This might be a little confusing for people modifying this since it's an important value and is spelled incorrectly here and there.

Fixed in #5


Incompatible type but it's a union type

Flow version: 1.156.0
Expected behavior
If I defined a maybe type id: number | string I expect it to accept any object with an id: string or id: number.
Actual behavior
When passing the object as arguments, the type check won't pass.
/* @flow */

// types.js
type Record = {
  id: number | string,
  name: string
}

interface SelectOptionObject {
  id: string,
  toString: () => string
}

const toSelectOptionObject = (r: Record): SelectOptionObject => ({
  id: String(r.id),
  name: r.name,
  toString: () => r.name
})

// application.jsx
type Plan = { id: number, name: string }

const plans: Plan[] = [{ id: 0, name: 'Plan 0'}, { id: 2, name: 'Plan 2'}]

plans.map(toSelectOptionObject) // <- Error

Link to Try-Flow or Github repo: https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVxhgC4E8AOApgM4B0AVsankWAEqEDGcATgCZgC8YA3qmGACWbAFxgAdgFcAtgCNCLMAB8wxbC0HiA5gBp+EgIbTCYtRu2oAvuk3YFUA40JgAyoRhNsAeXzZBccS9Zck9efWFTdU1dfWw4FyjtMQAKAEouAD5VRK0rdGZxNRx4908fPwCgkMZsLjBkljEGZnZUsTcPGvL-QODQzizkvgEI1xyG0mFUvQFxIxMwFlI54xnihPMtFPSBxeX5q1T0TDADfHwYQUYDCvEKYgAPagJnAAUYA3E6niFRCRl5CwdIZjJFNmBrKgCkULp9iGJ3p8ANoAXTqSJ+owADMCVgsAOSIr5Y-GWYGYv4AJlx8zEhI+X0ppJR6FhhVI0jOyTiHTKvh6VU8qSAA

You can fix this by making id a read-only property in Record, like this.
The reason this is necessary is because otherwise, you'd be able to write a string to r.id inside toSelectOptionObject, which would violate the type of the elements of plans, like so. Making Record.id read-only prevents this from happening and allows your original program to pass.


[DRAFT] Service load-balancing with StateDB

This is first of many PRs to refactor Cilium's load-balancing control-plane to use StateDB to store
the service and backend information.
Since we want to mature this implementation gradually and to answer the still many small questions
related to this (topo-aware services, clustermesh, NodePort frontend IP expansion etc.), this PR is
introducing the support via a feature flag (enable-new-services) so this can be tested and developed
gradually. This hidden feature flag will allow using the Services API instead of ServiceManager.
The flag enables a reconciler the state in tables to ServiceManager.
Nothing yet uses the new API and the flag is disabled by default, so this code has no impact
to normal operation, but it allows further collaborative development on the API and on the final
reconciler that goes directly to the load-balancing BPF maps.
The implementation is structured as follows:
pkg/loadbalancer/experimental is chosen as the package for these. This clearly separates
the new code from the production code. Eventually it will make sense to move the code into the
loadbalancer package that already defines the data structures related to load-balancing.
pkg/loadbalancer/experimental/tables.go:
Defines Table[Frontend] and Table[Backend]. The Frontend type is very similar to SVC but does
not include the backends. It is at the same level of detail however in that it represents a single service frontend
(unlike e.g. k8s.Service). Frontend type in comparison to SVC has additional fields related to reconciliation status and backend revision (the link between the two tables). To avoid modifying existing code I've opted to copying the type definition and converting between them. experimental.Backend is similarly almost  the same as loadbalancer.Backend, but adds source and frontend references. Long term we would likely include more fields into these to include more metadata (e.g. ServiceAffinity, Cluster name etc.). The fields that can be modified externally are split into FrontendParams to make the division between fields managed by the Services API and those managed by users clear.
pkg/loadbalancer/experimental/services.go:
Implements the "writer" to Table[Frontend] and Table[Backend]. We don't want to give write access to the tables directly as we want to validate and merge changes and we need to mark service's status as pending to ask the reconciler
to process it. Also any changes to backends require bumping the backend revision of each referenced service to trigger
reconciliation.
Inserting a service and backends looks as follows:
var s *experimental.Services
// Create a WriteTxn against frontend and backend tables.
txn := s.WriteTxn()

// Insert a new frontend.
created, err := s.UpsertFrontend(
  txn,
  experimental.FrontendParams{
    Name: loadbalancer.ServiceName{Name: "test", Namespace: "default"},
    Frontend: loadbalancer.NewL3n4Addr(...),
    Type: loadbalancer.SVCTypeClusterIP,
    Source: source.Kubernetes,
  },
)
if err != nil {
  // error can be non-nil if there are validation problems or conflicts with existing services
  // we can choose to abort the whole transaction and throw away changes.
  txn.Abort()
  return
}

// Insert backends for the given service.
// If backends already exist, then the reference to the service is added, but existing
// e.g. backend state is kept.
err := s.UpsertBackends(
  txn,
  loadbalancer.ServiceName{Name: "test", Namespace: "default"},
  &loadbalancer.Backend{L3n4Addr: addr1, State: loadbalancer.BackendStateActive},
  &loadbalancer.Backend{L3n4Addr: addr2, State: loadbalancer.BackendStateActive},
  &loadbalancer.Backend{L3n4Addr: addr3, State: loadbalancer.BackendStateActive},
)

// Commit the transaction and notify watchers of Table[Frontend] and Table[Backend].
txn.Commit()

The changes to these tables can be watched as usual with StateDB LowerBound queries
(or with DeleteTracker for delete events as well):
var db *statedb.DB
var frontends statedb.Table[*experimental.Frontend]

// Iterate through changes in revision order.
latestRev := statedb.Revision(0)
for {
  iter, watch := frontends.LowerBound(db.ReadTxn(), statedb.ByRevision(latestRev+1))
  for svc, rev, ok := iter.Next(); ok; svc, rev, ok = iter.Next() {
    latestRev = rev
    // process changed service
  }
  // Wait for table to update
  <-watch
}

// To wait for datapath reconciliation we can query and watch the reconciliation status:
for {
  fe, _, watch, found := frontends.FirstWatch(db.ReadTxn(), experimental.FrontendIndexL3n4Addr.Query(addr))
  if !found { break }

  if fe.Status.Kind == reconciler.StatusKindDone {
    break
  }

  // Wait for the service to update.
  <-watch
}

More examples of the API can be found from pkg/loadbalancer/experimental/services_test.go.
Read access to these tables is directly through Table[Frontend] and Table[Backend]. This is the general approach with StateDB: we want to keep the StateDB API always directly available for reading to reinforce the use of this common API and reduce overall API complexity by not wrapping queries.
The feature flag can be enabled and support tested with:
$ cilium config set enable-new-services true
# wait for restart

$ kubectl exec -it -n kube-system ds/cilium -- bash
# cilium-dbg statedb dump | jq .frontends
# cilium-dbg statedb dump | jq .backends
# cilium statedb health|grep -i new-services-reconciler

This PR does not yet include "cilium-dbg statedb" commands for these tables as we need to first switch
cilium/cilium to use cilium/statedb (https://github.com/cilium/cilium/pull/32125). That switches the StateDB
REST API to use JSON encoding instead of gob, which we need to be able to transmit structs that have
private fields.
The implementation is currently such that it can slot between ServiceCache and ServiceManager, which
means it still relies on e.g. the service expansion done in K8sWatcher. Also backend filtering (topology awareness) and correlation is still kept in ServiceCache/K8sWatcher, but some of it can definitely be moved into the experimental.Services
API later on. pkg/service also performs backend selection that could be made part of GetBackendsForService later.
This PR is meant to have zero impact on normal production use of Cilium by having all new code behind
a hidden and disabled feature flag.
Rough follow-ups to this PR will be:

Rebase this once cilium/cilium has moved to cilium/statedb. This allows reconcilers to modify the objects they're reconciling which gives a natural way to push information upwards, e.g. to set the allocated ID or pull other data from BPF towards these objects.
Replace ServiceCache with a proxy implementing the same API on top of Services API and the tables
Introduce an alternative to ServiceManager for reconciling the changes to the tables directly to BPF maps.
Replace uses of ServiceManager/Resource[Service]/Resource[Endpoints]/ServiceCache etc. with Table[Service]/Table[ServiceBackend].
Remove Resource[Service] and Resource[Endpoints] and directly write to the tables with a client-go Reflector without the additional cache.Store.
Remove ServiceCache and ServiceManager

Service type in comparison to SVC has additional fields related to reconciliation status and backend revision (the link between the two tables).

I believe Service should be Frontend.

Implements the "writer" to Table[Service] and Table[ServiceBackend].

And here probably these should be Table[Frontend] and Table[Backend].

Ok, after some discussions with @robscott I ended up adding back the ServiceManager wrapper into this PR and then some "test/controlplane" tests to exercise the implementation all the way from K8s objects to fake LBMap updates. The changes introduced here should have no production impact whatsoever as long as the hidden "enable-new-services" flag is disabled.

/test

/test

/test

/ci-runtime

Hey, could I get some reviews? It has been 3 weeks now.


Update-mgdevicemanagementmanageddevice -devicecategory

Does the cmdlet work ?
because can't make work with -bodyparameter or -devicecategory, eveytime he result with an error
$Params = @{     DeviceCategory = @{     "DisplayName" = "$NewCategory"} } | ConvertTo-Json try {     # Changer la category Update-MgDeviceManagementManagedDevice -ManagedDeviceId $Device -BodyParameter $Params

I cannot make it work either with the built-in cmdlets.
`Update-MgBetaDeviceManagementManagedDevice -ManagedDeviceId $myIntuneDevice.Id -DeviceCategory $category
Update-MgBetaDeviceManagementManagedDevice : Cannot apply PATCH to navigation property 'deviceCategory' on entity type 'microsoft.management.services.api.managedDevice'.
Status: 400 (BadRequest)
ErrorCode: ModelValidationFailure
Date: 2023-10-03T17:24:51
Update-MgBetaDeviceManagementManagedDeviceCategory -ManagedDeviceId $myIntuneDevice.Id -Id $category.Id
Update-MgBetaDeviceManagementManagedDeviceCategory :
Status: 404 (NotFound)
ErrorCode: UnknownError
Date: 2023-10-03T17:03:16
`
The only way to make it work is like this:
 $body = @{<EMAIL_ADDRESS>= "https://graph.microsoft.com/beta/deviceManagement/deviceCategories/$($category.Id)" } Invoke-MgGraphRequest -Method PUT -Uri "beta/deviceManagement/managedDevices/$(myIntuneDevice.Id)/deviceCategory/$ref" -Body $body
`

I cannot make it work either with the built-in cmdlets.
Update-MgBetaDeviceManagementManagedDevice -ManagedDeviceId $myIntuneDevice.Id -DeviceCategory $category
Update-MgBetaDeviceManagementManagedDevice : Cannot apply PATCH to navigation property 'deviceCategory' on entity type 'microsoft.management.services.api.managedDevice'.
Status: 400 (BadRequest)
ErrorCode: ModelValidationFailure
Date: 2023-10-03T17:24:51

Update-MgBetaDeviceManagementManagedDeviceCategory -ManagedDeviceId $myIntuneDevice.Id -Id $category.Id
Update-MgBetaDeviceManagementManagedDeviceCategory :
Status: 404 (NotFound)
ErrorCode: UnknownError
Date: 2023-10-03T17:03:16

The only way to make it work is like this:
$body = @{<EMAIL_ADDRESS>= "https://graph.microsoft.com/beta/deviceManagement/deviceCategories/$($category.Id)" }
Invoke-MgGraphRequest -Method PUT -Uri "beta/deviceManagement/managedDevices/$(myIntuneDevice.Id)/deviceCategory/`$ref" -Body $body

This one work for me :
Update-MgBetaDeviceManagementManagedDeviceCategory -ManagedDeviceId $Device -BodyParameter $BodyParams
With the new category in the body parameter


[FEATURE] Update logging format for heroku

Is your feature request related to a problem? Please describe.
With the current console.log things will be hard to debug if there are multiple calls going on at the same time due to the log messages lacking any kind of meta-data.
Describe the solution you'd like
After #119 we should update the format to include the following:

messageId/reactionId(?)
user who performed the action
update format to something that easily "searchable" and "filterable", maybe json or otherwise. This is due to
heroku not really providing any logging tools.

These 2 things should allow us
Describe alternatives you've considered
We could also use some other service to handle logs, and use winston as the "abstraction layer". Regardless we will want to have this meta-data passed to the log statements before hand.
Additional context
See winston format documentation:
https://github.com/winstonjs/winston#formats

Hey, @bradtaniguchi/ @nhcarrigan I would like to work on this. Could you please guide me?

Heya @kaiwalyakoparkar,
Thanks for your interest in this issue. At the moment, I need to do some investigating to see which parts of this are still needed (the bot is no longer deployed on Heroku, for example).
I'm going to remove the good first issue label for the time being, but once I have a better understanding of how we want to approach this task, I'll reach out to you and get you set up to contribute 🙂

Thank you so much @nhcarrigan. Is there any other issue in other fcc repos I can do my first contribution to?

I don't know of any off hand, unfortunately. Worth keeping an eye on our main repository, where most of our issues are tracked - you can watch for first timers only issues there 🙂

@nhcarrigan we can close this issue, since it isn't applicable anymore.


Timeseries API returns Null Values for Queries Outside Data Range for Reg. TS

If a regular timeseries is queried outside of the timeseries extent, datetimes, null values, and qualifiers are returned. This is not desirable for large, period of record pulls because it results in a large data transfer. It would be better if it didn't return anything if it's outside the range.
Let's say I want to merge 15min regular data with 1 hr regular data using cwms-python. I would have to query the extents of the timeseries using the catalog endpoint and them build my query off of those extents. Could CDA first query the extent of a regular timeseries from the timeseries end point and then know not to manufacture null values for data that doesn't exist?
Note, this occurs in the CDA 3.1.3.

A "trim" flag was recently added.  Does that help?

Thanks, I think it would! I would expect that would've been the default behavior, but maybe there are use cases I'm not thinking of for creating the null values.

Tagging @Enovotny to track as well

@rma-rripken can the trim flag default to True?  So the default is to have the values trimmed?

I don't see why not.  Lets check that cwms-data-access-client is making use of the flag and then I think we can make the default whatever you want it to be.


Move everything not needed for 'tracker-core' into the 'java-tracker'

Looking back at what we have currently, we have a better idea now of what needs to be in the core and what doesn't. There are some java-tracker dependencies that are unnecessary for the android tracker, but we get them because we inherit from core.
Early list:

[ ] SLF4J - Android logging is superior in it's own domain. SLF4J can be used in java-tracker only.
[ ] Jackson - this can go in java-tracker since we don't need Jackson's performance gains in android
[ ] Network implementations (http-client in android-tracker is different from java-tracker, we can do without having it in core since we don't use it there, but we still download it. Also causes warnings in Android builds.)

This would be a big change so it would be better to put this in 0.6.0 to work on once I'm done with immediate android stuff.

This is no longer required, because: #116


Add telemetry to consensus engine (look at aura)

 Authored by dependabot[bot]
Feb 8, 2024

Superseded by #61.


Problem with switching data types from bytes to words in a certain portion of memory.

This one is a little odd - I had a jump table documented with the display mode as JumpAddress and I just noticed they'd disappeared and were back to being a stream of bytes, but if I hit d on any of them they don't change to a word (they show up as grey).  If I hit C to change it to code and then D and D again, it does switch from code to byte to word.  I have to do this on every byte pair.  I then set the display mode again so they have references to the function names and save.  When I load back they come back as a stream of bytes again.
I can provide the Cobra image and Project as it stands thus far to see the problem in context, as I've never seen it do this before and something may be awry with the project file.

This sounds odd and something I've not had happen before so I would like to investigate it.
If you could send me the files then that would be great!
You can also set a pair of bytes to be a pointer by selecting the first byte and hitting 'P'

No problem; do you want me to send it directly or just attach to here?

It's up to you. It'll be public if you attach it here, if you don't mind that then go ahead.

I've added a new command on the 'J' key btw, it marks a data item as a jump address, creates a function label at the address and marks the memory at the address as code. It seems to make the process of documenting jump tables and their code easy but maybe it does too much? I'm going to use it for a bit and see how well it works.

Hiya. Ever the perfectionist, the REing is not quite fit for public consumption yet (there's like a dozen functions not documented yet!) - if you drop me an email at<EMAIL_ADDRESS>I'll fire over a zip when I get home.  Once it's done I'll publish it along with some notes on how things like the scroll, the sprite plots and the audio multiplexing work.


Issue with Linked Items and auto update to DnD Beyond

Having what I think is a ddb-importer + Link Item & Resource DnD5e. I've set up an item called Javelin (Thrown), which uses the new Link Item functionality to link ammo to a resource slot. I also have the auto-update to DDB turned on. When I set the number of Javelin (Thrown) to some number, say, 5, and use it, the quantity drops to 1 and multiple versions of the Javelin (Thrown) are created on the char sheet. This ONLY happens when DDB-importer auto update to DDB is on. Works fine when it's off. So I think it's an issue here.
Definitely seems related to the auto update of DDB-import, because I just looked at the char sheet on dndbeyond.com, and the char had several dozen javelins...
Hope this helps.

Thanks for the issue - this will be fixed in v 2.6.17 released in the next few hours. You'll want to re-import your characters from DDB to get it to work correctly, and probably remunch your items to the items compendium you're using.


add citation?

Dear @albangossard
Thanks for the excellent and helpful work! By any chance, if you are using the derivation of DOI: 10.1109/TCI.2023.3240081, could you please add the reference in the readme and comments? It would be helpful for the following researchers to debug and find the theory.
Best,
Guanhua

Dear @guanhuaw
Thank you for your message, this is indeed a good idea. I've added a reference section in 50f1403.
Best,
Alban


Error setting up task in Windows Server 2008 R2 -

Everything works fine creating the cert in IIS, except no task is created. Keep getting this error.
[EROR] Failed to create task
System.ArgumentException: A valid system account name must be supplied for TaskL
ogonType.ServiceAccount. Valid entries are "NT AUTHORITY\SYSTEM", "SYSTEM", "NT
AUTHORITY\LOCALSERVICE", or "NT AUTHORITY\NETWORKSERVICE".
Parameter name: userId
at Microsoft.Win32.TaskScheduler.TaskFolder.RegisterTaskDefinition(String pat
h, TaskDefinition definition, TaskCreation createType, String userId, String pas
sword, TaskLogonType logonType, String sddl)
at PKISharp.WACS.Services.TaskSchedulerService.EnsureTaskScheduler()
[INFO] Adding renewal for www.*****.com
[INFO] Next renewal scheduled at 2018/8/16 17:28:37 PM
Please choose from the menu:
Steps to reproduce
Please include the command line and/or manual input, relevant details about the IIS bindings, your scripts, etc.
v<IP_ADDRESS>
Windows Server 2008 R2

That's curious, the exception reads "Valid entries are "NT AUTHORITY\SYSTEM", "SYSTEM", "NT
AUTHORITY\LOCALSERVICE", or "NT AUTHORITY\NETWORKSERVICE"."
But "SYSTEM" is exactly what we use.
                            _log.Debug("Creating task to run as system user");                             task.Principal.UserId = "SYSTEM";                             task.Principal.LogonType = TaskLogonType.ServiceAccount;                             taskService.RootFolder.RegisterTaskDefinition(                                 taskName,                                 task,                                 TaskCreation.CreateOrUpdate,                                 null,                                 null,                                 TaskLogonType.ServiceAccount);
I'm wondering if this is a bug in the latest version of the Task Scheduler library that we are using. Can you try v<IP_ADDRESS> or before to check if those work?

We haven't been able to reproduce this and also haven't had any reports about it in the better part of a year, so I'm going to remove this from our active issue list for now.


Geocoder does not work with restricted API key on iOS

Summary
using the following libs..
If i DO NOT restrict the key for iOS, then the whole google maps is invisible inside the iOS build on Testflight, however the geocoding, the Places and Directions API, they all works. When I DO restrict the key, the google maps becomes visible, however all other libs such as geocoder, directions, places API, they seize to work. lol
Explain this to me.
The API/s i have restricted for my bundle identifier:
some.expo.app
Geocoding API
Geolocation API
Maps SDK for iOS
Directions API
Distance Matrix API
Maps Elevation API
Maps Embed API
Maps JavaScript API
Maps Static API
Places API
Roads API
Routes API
Time Zone API
Reproducible sample code
import MapView, {Marker, PROVIDER_GOOGLE} from 'react-native-maps';
import MapViewDirections from 'react-native-maps-directions';
import Geocoder from 'react-native-geocoding';

"react-native-geocoding": "^0.5.0",
"react-native-maps": "1.10.0",
"react-native-maps-directions": "^1.9.0",
"expo": "~50.0.20",

Steps to reproduce
restrict/unrestrict iOS key
Expected result
working google maps + libs of use inside Google Maps API
Actual result
Does not work.
React Native Maps Version
1.10.0
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.73.6
What version of Expo are you using?

Additional information
How can i solve it?

I can confirm react-native-geocoding does not support restricted API keys, which is a shame.

I can confirm react-native-geocoding does not support restricted API keys, which is a shame.


Add travis testing

I just realized this repo doesn't have travis testing.
@gregoryross : It would only take me ~20 min to get that set up for this repo. Should I take a stab at that now?

Do you mind if I have a stab at this?

Go for it! But we should get some travis testing going for this (any any other major projects) soon.

Great! I'll get on this tomorrow.

How's this coming along?

I plan to migrate the simulation results and analysis first, so that the continuous integration tests only assess the main code.

@gregoryross : How about I put this framework in place given you're short on time?

Only if you have the time! There's still a bunch of stuff I want to move out of this repo but the API and simulation code itself is pretty stable

simulation code itself is pretty stable

Travis will be the judge of that. ;)

Starting this now.

I've completed the implementation of travis tests in #8, but code issues need to be fixed by @gregoryross for tests to pass. I suggest merging it and then fixing the issues afterwards in a separate PR.

As stated above, this has been addressed in PR #8.


check for CA Bundle when True is specified for verify

Describe the bug
The verify argument when creating a client is documented to be of type boolean/string and defaults to None. While the longer description explains that it can take on a value of False or a path to a CA bundle, it currently does not allow you to pass a value of True -- in the case that True is passed, the current implementation will not check the ca_bundle configuration variable here.
This is exacerbated when using other tools such as MLFlow and DVC that allow you to swap out storage interfaces. In such tools you can also set a verify parameter to True, False or path/to/ca/bundle however you cannot specify None. In this case it is impossible to use Boto3 when a CA Bundle is required to be used.
The solution to this issue is extremely simple, just checking for verify being either None or True here
Steps to reproduce
If you're behind a corporate firewall that requires custom cert bundle, try to create a session with verify set to True and it will not load the CA bundle from the env vars.
Expected behavior
When a user passes True it should work the same as passing None
Debug logs

Hi @koelemay, thanks for posting. Can you provide a more concrete example of how you are configuring MLFlow or DVC to use boto3 and the verify parameter? The MLFlow documentation shows to use the AWS_CA_BUNDLE environment variable in the case of using a custom certificate bundle:
https://mlflow.org/docs/latest/tracking.html#amazon-s3-and-s3-compatible-storage

If the MinIO server is configured with using SSL self-signed or signed using some internal-only CA certificate, you could set MLFLOW_S3_IGNORE_TLS or AWS_CA_BUNDLE variables (not both at the same time!) to disable certificate signature check, or add a custom CA bundle to perform this check, respectively:
export MLFLOW_S3_IGNORE_TLS=true
#or
export AWS_CA_BUNDLE=/some/ca/bundle.pem

Thanks for the details. Marking this as a feature request for now, but need to do some more research on your use case and what impact it could have.

Any chance we can get this merged soon? We are experiencing the same issue. boto never looks at AWS_CA_BUNDLE

Plz merge this PR !
Also have a script where with configurable verify=  (because for local testing need to set verify=false where an ssh tunnel needs to be used)
I could never imagine this "True" (boolean) value to be unsupported  (with custom ca certs setting)
( I wasted at least half a day debugging  ( initially updating custom local docker images, assuming incomplete root/intermed. cacerts )  ..  until I delta-debugged , and removed  the verify flag alltogether , and that worked)

Hey everyone, thanks for opening this feature request and the discussion.  This is not a change we're likely to make at this time, and I'm going to close the issue accordingly.  This change affects certificate precedence, which is a breaking change.  We're closing the pull request for similar reasons.  Thanks again for contributing.


Qwik starter: squigglies appear after an edit

Describe the bug
As soon as I edit and save a file (in this case, index.tsx), the editor gets flooded with the red squigglies typically signifying a syntax error.

Link to the blitz that caused the error
https://stackblitz.com/edit/qwik-starter-cevvhd?file=README.md,src%2Froutes%2Findex.tsx
Steps to reproduce

Go to the starter
Open src/routes/index.tsx
Make an edit and save

Expected behavior
No squigglies
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
I've checked the project on my local machine

Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 109
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 112859450,
  "usedJSHeapSize": 82415618,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 522185bb0134fb732ed5ecb9887332d7f888ce1b

Additional context
First reported here

@sylwiavargas Do they eventually go away once the server is built for you?

They don't, sadly. Made an extended video now:
https://user-images.githubusercontent.com/45401242/215905131-4af45666-a90c-4093-ae30-0b7ff8967638.mov

This should be fixed now.


Add Channel Poll Event's & Poll-Parser

It often happens that the PubSub-Socket break, in this case people can't see active poll's.
It would be a helpful enhancement, to be able to post the current state of an active poll and the result, after the poll ends. With this feature, chatter could vote with the /vote X command, instead of reloading the page.
Therefor 2 new events are necessary and some templates:
New Events:

channel.poll.begin
channel.poll.end

Templating:

Poll Parser to get => pollTitle, vote1Title, vote1Count, [...], vote5Count

With this feature, chatter could vote with the /vote X command, instead of reloading the page.

Sadly this isn't true in the most cases: When the raid isn't available to the client /vote X doesn't work either…

Implemented

poll_begin, poll_end, poll_progress events: 04648a2
lastPoll function: 8ad973a


Speedup inferrence time.

HI @cliffordkleinsr very nice work. I would be very much happy and interested in speedup the inferrence time. Are you working on it ?

Yes the new code has sped up the inference time effectively halving the frame parsing, will share the colab code to run the inference publicly, where you can run the inference

@cliffordkleinsr sure, looking forward to it. thanks

Have you tested out the code?

Yeah I have checked in my local. but will love to see your colab version.

will do

The code now has both terminal and colab implementations on the repo, give it a try and let me know how it goes


Migration contains bad (old) annotation for identity column

The initial migration generated by Package Manager -> add-migration
contains 1.x version annotation for identity column configured in Fluent Api as below:
    builder.Property(c => c.Id)
    .IsRequired()
    .ValueGeneratedOnAdd() ;

The wrong annotation is:
.Annotation("SqlServer:ValueGenerationStrategy", SqlServerValueGenerationStrategy.IdentityColumn)
and does not build
it should be probably:
.Annotation("DatabaseGenerated", DatabaseGeneratedOption.Identity)
Further technical details
EF Core version: 2.0.0
Database Provider:Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017

@pila13 Can you provide more details about this? The "wrong annotation" seems correct to me at first look, and the annotation you are expecting is not something I would ever expect to see. In one way are things not working? When you say, "does not build" do you get an error? If so, what is that error?

I' m sorry - it was my misunderstanding + missing reference. I thought that enum SqlServerValueGenerationStrategy  had been removed in 2.0 which is obviously not true.  Please close the issue.


Switch with a dynamic label always renders as off

Well this is weird. If you have a Switch that has a label with content that changes based on the Switch checked state then the component always renders as "off" even though the internal state of the underlying input looks correct.
https://codesandbox.io/s/l79j15vxq7
Try toggling the first switch on!
I guess the dynamic label is causing a remount or something?
RMWC 3.0.9

Need to look into it but this might be a similar problem to a recent checkbox issue that was buried deep down in MDC where native getters and setters were being patched causing issues with Reacts render cycle for controlled components. Thank you for reporting.

This fixes it for now (could also use a key but that seems to cause ripple issues.)
class VeloSwitch extends React.Component {
  switch = React.createRef();

  componentDidUpdate(prevProps) {
    if (prevProps.label !== this.props.label) {
      // Update checked state if the label changes
      this.switch.current.foundation_.setChecked(this.props.checked);
    }
  }

  render() {
    return (
      <Switch ref={this.switch} {..this.props} />
    );
  }
}

You definitely get the reward for finding the strangest bugs with the strangest workarounds! Thanks for always digging in and the repros, helps a bunch and the library is getting more resilient with every point release.

We do push it quite hard. I'm going to make time to contribute back.

Been slowly rewriting things to the recommended adapter / foundation pattern (which is why you've been seeing some of these bugs resurface). This one was low hanging fruit so I went ahead and converted it over and added a test for the issue to prevent a regression. Will be released in a bit.


[Bugfix] Unit adjoint

This PR fixes the auto-adjointness of the GSI SABER block when the surface pressure is used. The inverse of a unit conversion was used instead of its adjoint.

@danholdaway and @rtodling: this PR is required for the one I'll open in SABER, to use GSI data within BUMP. Could you review and merge? Thanks!

This is not correct as it is. I am not even sure a scaling of PS that was done around line 803 is now gone! Indeed, the code being submitted as "correct adjoint" can't be write since it would need a scaling of PS to be consistent between the ad and tl routines.
I am pulling this branch and putting a revised version of your changes in place - no matter what: these changes will break the c-tests in fv3-bundle  ...


Add script to streamline image building and testing

I think it is a good idea to have the following practice before pushing any docker image:

Build image with minimal requirements
Based on previous image install test_requirements
Run all tests in a container
if all tests pass push image built in 1.)

I think we should enforce this with a bashscript that automates the process. We should then also use this in CI env to build and push images.
What do you think @mdank @vitords ?
 :P

Hahaha no that's why they are ignored right ;) but unittests at least.


Enhanced functionality for Find My Mouse

Description of the new feature / enhancement
A setting to disable find my mouse when Left, Right, or Middle Mouse is down.
Scenario when this would be used?
This would be really useful as I use blender (which requires alot of middle-mouse movement) and just adding a million applications to my excusions is tedious.
Supporting information
No response

/dup #17723


qt.qpa.xcb: could not connect to display

PredatorNonSense doesn't work on Hyprland. It's a wayland compositor.
I get this error:
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

zsh: IOT instruction (core dumped)  QT_QPA_PLATFORM=xcb pkexec python ~/git/PredatorNonSense/main.py

I have tried setting environment variables like QT_QPA_PLATFORM=xcb etc. as mentioned in the Arch wiki. Nothing worked.

Try the below:

QT_QPA_PLATFORM="wayland;xcb" as suggested in Arch wiki

cd into the folder, run sudo python3 main.py

Also try
QT_QPA_PLATFORM="wayland" as suggested in https://stackoverflow.com/questions/49583671/pyqt5-unable-to-find-wayland-plugin

I am still getting the same error.

Please provide additional info...
OS, python version, pyqt5 version, have you tried running it on any other DE or WM??

Quick note, are you using sudo -E ?
export QT_QPA_PLATFORM="wayland;xcb
sudo -E python3 main.py

Please provide additional info...
OS, python version, pyqt5 version, have you tried running it on any other DE or WM??

Some output from QT_QPA_PLATFORM=xcb qtdiag:
OS: Arch Linux [linux version 6.2.6-arch1-1]

Python 3.10.10
It was working in KDE. But I don't think I tried running it in KDE Wayland.

Quick note, are you using sudo -E ?
export QT_QPA_PLATFORM="wayland;xcb"
sudo -E python3 main.py

I tried sudo -E as well. Didn't help. :(

It works on KDE Plasma-Wayland on my end, so probably works for you too...
I use Manjaro BTW...
At the end, you said didn't help, did you get the same error or was there anything different??
Quick Q: you are running this directly on the laptop, not over SSH or other, right? have you tried running it through konsole in hyprland?

https://wiki.archlinux.org/title/Running_GUI_applications_as_root#Using_xhost
xhost si:localuser:root
More refs 😅

https://wiki.archlinux.org/title/Running_GUI_applications_as_root#Using_xhost
xhost si:localuser:root
More refs sweat_smile

I was  about to install Konsole just to try out your suggestion. But the xhost method worked! Thanks!
Also, no I am not running it over SSH.
Btw, is this something that can be fixed on your end or is this something that can't be fixed. I know running gui apps with root privileges is very tricky in wayland.

sudo -E works in hyprland default conf on my end as well...

I haven't given much thought to wayland actually, I should probably test stuff there too...
I was hoping to switch from Kubuntu Focal X11 to Fedora 36, KDE, Wayland. But my experience wasn't smooth at all (nvidia hardware fgs) and I switched to Manjaro KDE X11. That was the end of my wayland saga 🫠.
For now, I will include above in the readme, have to research more for a long term solution...
Thank you for opening this issue : ]

Also, do leave your laptop specs if you don't mind...

Damn..

My experience with Wayland has been mostly neutral. Haven't encountered too many issues like this one. Most programs just work.
Although I am loving Hyprland, so far. xD
Btw, my laptop is Predator G3-572. It's getting old...

Predator G3 and the fan control works??! Interesting...
The RGB section is useless to everyone, it always has been broken lol.
Have you tried the battery limiter and GPU Overclock/Fan curve tabs?? Please report your findings at your convenience...

I have enabled the battery limiter. Will take some time to find if it's working.
I don't see any fan curves in the program. I was able to change the GPU overclock to Boost, but I have no way to test if it's working.

yea so,
The GPU Boost section just changes the fan curve, i.e. the fans will run faster at a certain temperature in boost when compared to normal. It doesn't increase the GPU Power limit or add overclock, but runs the fans faster, like below...

I thought you meant the app was supposed to have a way to manually adjust the fan curve à la MSI Afterburner. But yeah, I still don't know if it really changed anything.

Battery charge limit isn't working.

for gaming, I only tried Hades and a couple of indie titles. They all worked flawlessly. Fullscreen and all.

Its Kwin+Wayland+Nvidia, known to break...

Battery charge limit isn't working.

Expected, as your laptop is an older varient and may not have this feature implemented

But yeah, I still don't know if it really changed anything.

If you have the overclock section in your windows predator sense application, gpu boost/ fan curve works...


Green light on the LED faints away...

The first user input lights up the corresponding green light accordingly. The second user input triggers a second green light. However, from this point onward, no green light can be lit up and the first two turn off as well. The green light seems a lot dimmer than normal. The LEDs can light up red with no issues throughout the game.
I am suspecting there is a limit on how much power the GPIO ports can output overall. Also, the green light somehow consumes more more than the red light. My next step is to dig into the power limit of the pi and see if I wire up the green light node with different resistors.

http://www.mosaic-industries.com/embedded-systems/microcontroller-projects/raspberry-pi/gpio-pin-electrical-specifications#rpi-gpio-input-voltage-and-output-current-limitations
All the GPIO ports can only source 50 mA of current simultaneously. However, each LED will need ~10 mA to operate.
Thus...  We will need a new design....


found "preceeding" a misspelling of "precedeing" (misspell)

i think the correction should be "preceding" not "precedeing"

weird... thanks @shawnps   not sure how this one slipped through.


Add a method to compute the solid angle for PS normalization (beam squared)

This was a requested feature.

It sounds like this is no longer seen as useful for power spectrum normalization work. Is that right @acliu ?

This was done in PR #303


Add restored objects labels

Update velero-plugin to label restored objects by migmigration and migplan refs.
Adds functionality of https://github.com/konveyor/openshift-migration-plugin/pull/58 (replaced raising error on missing label with info log entry).
Related to https://github.com/konveyor/mig-controller/issues/663

Removal of current migmigration refs is planned to land when mig-controller gets updated to use migplan ref only for migration itinerary.

@dymurray Hi Dylan, thanks for review! I've updated the PR and I think it is ready for review.
Labels are now being set on restored objects, example:
  labels:
    app: rocketchat
    migration.openshift.io/migplan-ref: 2a68aa61-9995-445a-9616-c35b4aa7e9a1
    migration.openshift.io/migrated-by: 37561dd4-bd63-42e5-ab43-31c8bacb93d3
    openshift.io/deployment-config.name: rocketchat
    velero.io/backup-name: mig-run-mqdhq
    velero.io/restore-name: mig-run-8nmvw

Thanks, updated. Labels on restored objects look like e.g.:
...
  labels:
    migration.openshift.io/migrated-by-migmigration: 4c2cfcf0-408d-4a07-88c2-4b6687a449f9
    migration.openshift.io/migrated-by-migplan: 0a34500f-6745-4f15-be67-14babede937e
    velero.io/backup-name: mig-run-2h8xm
    velero.io/restore-name: mig-run-rgvg9
...


Disassembler runtime-code

Description
Currently the -d option only outputs the disassembly of the runtime bytecode for a contract.
When using the -c option, the input is automatically assumed to be creation bytecode.
myth -d -c "0x6060" therefore returns nothing.
With the addition of supporting both runtime code and creation code we need to add an adaption to support printing the disassembly of both runtime and creation code.
Requirements:
With the -d option enabled mythril should output the disassembly for both runtime bytecode and creation bytecode if both are available
Runtime Disassembly:
0 ADD ...
...

Disassembly:
0 ADD ...
...

If either one is not provided then only the other should be printed ( this is the case in myth -d -c "0x6060":
Disassembly:
0 ADD ...
...

#787


TypeError: $state.get(...).getState is not a function

I was having issues of permissions not being honored (i.e. able to navigate to a state that I don't have permissions for). However, this was only happening some of the time and I got very confused. At first, I thought it was a problem with my app.run function that defines permissions.
However, I put a console.log("permissions checked") in one of my functions that defines permissions so I could see if it was somehow missing permission checks at the right times (see below).
// Permissions definitions go below
        PermissionStore.definePermission('anonymous', function () {
            console.log("permissions checked");
            return !$auth.isAuthenticated();
        })

Looking at my console, I could see that on every state load, it checked the permissions twice (not sure why, but whatever...it's still checking). Then, on a few states, I would get the following error:
TypeError: $state.get(...).getState is not a function
    at compensatePermissionMap (angular-permission.js:86)
    at angular-permission.js:42
    at Scope.$broadcast (angular.js:16311)
    at Object.transitionTo (angular-ui-router.js:3229)
    at Array.<anonymous> (angular-ui-router.js:2346)
    at Object.invoke (angular.js:4478)
    at handleIfMatch (angular-ui-router.js:1836)
    at angular-ui-router.js:1891
    at check (angular-ui-router.js:2007)
    at update (angular-ui-router.js:2016)

After that error, it seems that I stopped seeing permissions checked on every state change in my console. Thus, I could navigate to pages for which I did not have permissions. If I refresh the page, everything seems to work OK until this error pops up on certain states.
Digging into the issue further, states where the error appears seem to be defined in a file loaded before my permissions.run.js is loaded (working off a framework with several predefined states in ui-router). I'm not sure if that would make a difference, but it could be helpful in debugging.
Any ideas on what could be causing this? I'll see if i can get a plunkr to reproduce the issue. Thanks so much for your help!

Awesome. Thanks for replying so quickly. I'll see if this works and, if not, I'll get a plunkr that reproduces the problem up ASAP.

Ok...you were right. Thank you. I included permissions right before including ui.router in my main module's dependencies. The  $state.get() errors went away (might want to add this note to the docs as I can't imagine I'm the first one who's run into this issue).
However, I'm still having issues with some routes that are restricted. They will often work (successfully blocking a route) when the page is first loaded, then quit working (allowing access to a restricted route) as I navigate around and use the single page app for longer. I will do some further debugging and keep you posted...I'm stumped right now.

I've played around with my single-page app a little bit and inserted some console.logs at strategic points. Correct me if I'm wrong, but the first time one accesses a state that requires permissions, angular permissions runs the definePermission function to see if a user has access. Doesn't it then generate a PermissionStore and read permissions from there for subsequent state changes.
It seems that state changes where it's reading from my permission store are problematic.  In other words, the first time I go to a restricted route, it evaluates the definePermission methods and does the right think, revoking or allowing access. However, it seems when reading from PermissionStore   on a state change, it doesn't seem to get the permissions right.

So it appears that $stateChangePermissionAccepted or $stateChangePermissionDenied are firing ONLY the first time I access a state. After that, they don't get broadcasted anymore....

Hmm, looking further, it appears areSetStatePermissions(toState) is returning false after the first time a state is accessed.

Wait, scratch that. This block under $on('$stateChangeStart' is causing me issues:
if (toState.$$isAuthorizationFinished) {
      return;
 }

I understand that $stateChangeStart can fire multiple times and this block prevents the inevitable infinite loop, but states don't seem to be authorizing when I go to them a second or third time because this statement is returning.


Fix empty path git warnings

This replaces all leading / in the log path by ./ and prepends it to paths not starting with / (for consistency).

I added a test that uses / as path, but I don't know how I would check for the warning (especially since it depends on the git version), so all you could do is run the test and check if there's warnings.


Slow apply physics

Diagnostics to report slow/inefficient operations in ApplyPhysics to attempt to get to the bottom of the high CPU usage on crossings.

Looks good to me.  That utility can be useful in many places even if only during dev: I could have used it when chewing on #257.

I'm going to have some more slow reports to add, and yes it is mostly for experimental dev testing.  However, I the tests also need to include a merged #270.