CNV-43176: Allow user to select namespace in Add volume modal

📝 Description
These changes in this PR:

allow the user to select the project the bootable volume will be created in directly from the Add bootable volume modal
change the default namespace in the bootable volume list to All projects
fix a bug where the DataSource wasn't deleted when the DataVolume is deleted

jira: https://issues.redhat.com/browse/CNV-43176
🎥 Screenshots
Before

After

/cherry-pick release-4.16


Rush update fails using Node v17 on MacOS 11.6.1 (Big Sur)

The following error occurs when running rush update using Node v17  but successfully passes when using v16.
Here are the versions I was using when the command failed:
Node - 17.0.0
NPM - 8.3.1
Python - 3.9.7
macOS - 11.6.1
The output of the error is below:
node_modules/.pnpm/https://github.com/Azure+msal-node-extensions@1.0.0-alpha.13/node_modules/@azure/msal-node-extensions:
Running install script, failed in 1.5s
.../@azure/msal-node-extensions install$ node-gyp rebuild
│ gyp info it worked if it ends with ok
│ gyp info using<EMAIL_ADDRESS>│ gyp info using<EMAIL_ADDRESS>| darwin | x64
│ gyp info find Python using Python version 3.9.7 found at "/Users/hamsa/anaconda3/bin/python3"
│ gyp info spawn /Users/hamsa/anaconda3/bin/python3
│ gyp info spawn args [
│ gyp info spawn args   '/Users/hamsa/.rush/node-v17.0.0/pnpm-6.19.1/node_modules/pnpm/dist/node_modul
│ gyp info spawn args   'binding.gyp',
│ gyp info spawn args   '-f',
│ gyp info spawn args   'make',
│ gyp info spawn args   '-I',
│ gyp info spawn args   '/Users/hamsa/VSCode/azure-sdk-for-js/common/temp/node_modules/.pnpm/@azure+ms
│ gyp info spawn args   '-I',
│ gyp info spawn args   '/Users/hamsa/.rush/node-v17.0.0/pnpm-6.19.1/node_modules/pnpm/dist/node_modul
│ gyp info spawn args   '-I',
│ gyp info spawn args   '/Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/common.gypi',
│ gyp info spawn args   '-Dlibrary=shared_library',
│ gyp info spawn args   '-Dvisibility=default',
│ gyp info spawn args   '-Dnode_root_dir=/Users/hamsa/Library/Caches/node-gyp/17.0.0',
│ gyp info spawn args   '-Dnode_gyp_dir=/Users/hamsa/.rush/node-v17.0.0/pnpm-6.19.1/node_modules/pnpm/
│ gyp info spawn args   '-Dnode_lib_file=/Users/hamsa/Library/Caches/node-gyp/17.0.0/<(target_arch)/no
│ gyp info spawn args   '-Dmodule_root_dir=/Users/hamsa/VSCode/azure-sdk-for-js/common/temp/node_modul
│ gyp info spawn args   '-Dnode_engine=v8',
│ gyp info spawn args   '--depth=.',
│ gyp info spawn args   '--no-parallel',
│ gyp info spawn args   '--generator-output',
│ gyp info spawn args   'build',
│ gyp info spawn args   '-Goutput_dir=.'
│ gyp info spawn args ]
│ No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
│ No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
│ No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
│ gyp info spawn make
│ gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
│   CXX(target) Release/obj.target/dpapi/src/dpapi-addon/main.o
│ In file included from ../src/dpapi-addon/main.cpp:6:
│ In file included from ../../../../../nan@2.15.0/node_modules/nan/nan.h:58:
│ In file included from /Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/node.h:63:
│ In file included from /Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/v8.h:25:
│ In file included from /Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/v8-array-buffer.h:13:
│ In file included from /Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/v8-object.h:10:
│ /Users/hamsa/Library/Caches/node-gyp/17.0.0/include/node/v8-persistent-handle.h:10:10: fatal error:
│ #include "v8-weak-callback-info.h"  // NOLINT(build/include_directory)
│          ^~~~~~~~~~~~~~~~~~~~~~~~~
│ 1 error generated.
│ make: *** [Release/obj.target/dpapi/src/dpapi-addon/main.o] Error 1
│ gyp ERR! build error
│ gyp ERR! stack Error: make failed with exit code: 2
│ gyp ERR! stack     at ChildProcess.onExit (/Users/hamsa/.rush/node-v17.0.0/pnpm-6.19.1/node_modules/
│ gyp ERR! stack     at ChildProcess.emit (node:events:390:28)
│ gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
│ gyp ERR! System Darwin 20.6.0
│ gyp ERR! command "/usr/local/bin/node" "/Users/hamsa/.rush/node-v17.0.0/pnpm-6.19.1/node_modules/pnp
│ gyp ERR! cwd /Users/hamsa/VSCode/azure-sdk-for-js/common/temp/node_modules/.pnpm/@azure+msal-node-ex
│ gyp ERR! node -v v17.0.0
│ gyp ERR! node-gyp -v v8.3.0
│ gyp ERR! not ok
└─ Failed in 1.5s
 ELIFECYCLE  Command failed with exit code 1.
The command failed:
/Users/hamsa/VSCode/azure-sdk-for-js/common/temp/pnpm-local/node_modules/.bin/pnpm install --store /Users/hamsa/VSCode/azure-sdk-for-js/common/temp/pnpm-store --no-prefer-frozen-lockfile --strict-peer-dependencies
ERROR: Error: The command failed with exit code 1
Giving up after 3 attempts

Related conversation: https://github.com/Azure/azure-sdk-for-js/pull/20229#issuecomment-1042058965

@hamsa-s hello hello!
I was unable to reproduce this problem. Can you try in a new fork, running rush update with Node 17? please tell me if it fails then.
Alternatively, you can remove all of the local cache that Rush has. You can run rush reset-workspace and then rush update. Keep in mind that: rush reset-workspace will remove all the .gitignored files, like your .env files.
Your feedback is appreciated 🙏

Wait, I just realized I didn’t test in MacOS. I’ll be back.

@hamsa-s alright, after upgrading msal-node-extensions to 1.0.0-preview.15 the problem went away for me! I have made a PR with this change: https://github.com/Azure/azure-sdk-for-js/pull/20441 — please let us know if that solves the problem you were experiencing 🙏

Hmm for some reason I still get the same error. I pulled the PR and tried to run rush update. Is there anything else I should do?

@hamsa-s it could be something else in the environment. I could also be missing something.
Can you try on a fresh new clone of the repository?

Also, please make sure you have the XCode developer tools (just the command-line tools are sufficient) from Apple: https://developer.apple.com/download/all/

I created a new clone of the repository, ran rush reset-workspace and rush update and the issue still exists. I have v11 of the command line XCode tools from Apple. Let me know if updating the XCode tools could make a difference and I can try that too!

@hamsa-s thank you! I’ll take a look in a couple of days 🙏

@hamsa-s I can’t follow up at the moment. Give me some more days

Out of curiosity, is this an ARM Mac (M1, M1 Pro/Max), or an Intel Mac?

It's an Intel Core i7 Mac.
Also, I'm still able to work in the repository with Node 16 so take your time with this issue! I'm not in a big rush or anything since I can get it working in other ways.

@hamsa-s I’m on Core i7 as well. Ohh! Can you try with Node 17.6.0? I can’t make it fail, but perhaps is that slight change of Node version.

@sadasant that worked!! Thank you so much for taking the time to look into this!

Awesome!!! I’ll close this issue then 👍 Thank you for your patience and for your contributions 🙏


feat: show decoded call data on eth tx details

closes #3097
closes #3096
Show user decoded data (if possible, if not show raw data) in transaction details so that he can figure out what the contract call did. This does not exactly solve the issues but seems like the best solution. Etherscan also only shows the decoded data since it would be impossible to create resolvers/parsers for every contract out there

Result of decoding for some transactions are not user friendly. 0xe67f85397da69f6d81b9e56beeb21d663dbf1487d745c76dc72be82980965cda

Result of decoding for some transactions are not user friendly. 0xe67f85397da69f6d81b9e56beeb21d663dbf1487d745c76dc72be82980965cda

The screenshot shows the raw data, which by design is not user-friendly.
(in some cases (like on the screenshot) the API returns deprecated instead of the raw data, maybe in those cases we don't show any information)
Also if the decoding fails we are showing a warning to the user that it failed.
If it is successful I believe we need to show whatever the result was. Whether this is user-friendly or not shouldn't matter.

The raw data suppose to show this field.
"input": "0xa9059cbb000000000000000000000000d2fbf4c86816d3c830d63f8ca0472d93fc07bc60000000000000000000000000000000000000000000000000002386f26fc10000",

Instead of deprecated.

Result of decoding for some transactions are not user friendly.

Issue is fixed, but for most of my transactions i see message that wallet failed to decode input.

For some Txs there are still few data is showing: 0x20311fa3a73dbe373fd23a371e6387a4708f07c1b50e5094dcc3838935be699b
https://github.com/user-attachments/assets/586182af-2aaf-47a0-8f66-0d1e7ce6d5e2
but for others looks good to me.

For some Txs there are still few data is showing: 0x20311fa3a73dbe373fd23a371e6387a4708f07c1b50e5094dcc3838935be699b

There is nothing to decode for data 0x.

lgtm


Changing the button "Arm/Disarm" position?!

Checklist

[X] I checked for similar existing requests (both open and closed) before posting.
[X] My request is generic, other users may benefit from it too.

Proposal
[clear description of what you want to see changed or added]
There is any way to change the "ARM/DISARM" button position?
Additional info
[some example of how the new functionality should look like]
I would like to put the button "ARM/DISARM" to the left of button "0" (zero). In this way, I will have a more compact design

I done this through CSS, but it will be great if there is an "native" option in the card settings.
#armActions{position:absolute;margin-top:243px;margin-left:71px;width:100px}     alarmo-button{width:100px !important}
I am using Alamo in order to turn on/off my computer.
This is how it is looking after the button position.


Added changelog and upgraded the versions for household, individual a…

…nd service request

Summary by CodeRabbit

New Features

Introduced a BOOLEAN DataType for enhanced attribute definition capabilities in the service request framework.
Implemented fixes for ExistentEntityValidator in health services.

Version Updates

Updated service request module to version 1.0.1.
Updated household module to version 1.1.4.
Updated individual module to version 1.1.6.

Documentation

Updated changelogs for service request, household, and individual modules to reflect recent changes and version updates.

@coderabbitai review


renderTestCaseEditForm() not working properly

hello , i want to ask function renderTestCaseEditForm() not working properly, may be some help?

this functionality is not ready yet


feat: bump @azure/identity to v4

<EMAIL_ADDRESS>has recently been released with a support for node v20. This package should take it into account. I can create a PR if you're ok with it @NiklasPor

Ah awesome, I'm just about to release a new verison. I'll bumpt it 👍

Bumped in 17.0.0.


How to confirm which image the bbox and score in result.pkl belong to ?

Hello, I want to add an item in  the result.pkl(generated by RPN) to indicate the image name when eval bbox, so as to confirm which image the bbox and score in result.pkl belong to. How should I do it ?
Looking forward to your reply.

If you are using 3.x version, it will be a dict[img_name: result], which may answer your question
For 2.x version, it will be a list, and the sequence will be the annotation sequence.

If you are using 3.x version, it will be a dict[img_name: result], which may answer your question
For 2.x version, it will be a list, and the sequence will be the annotation sequence.

Sorry, I don't really understand the meaning of 'annotation sequence'. If I choose 2000 images in COCO val2017 to eval, is the sequence of the result the sequence of these 2000 image names?

For 2.x version, it will be a list, and the sequence will be the annotation sequence.

Does the annotation sequence refer to the image sequence contained in the 'images' field in coco instances_val2017.json?

I got it, thank you!


[Bug]: SnowflakeIO does not escape quote characters

What happened?
I am seeing an error in my dataflow job:
org.apache.beam.sdk.util.UserCodeException: java.lang.IllegalArgumentException: No enum constant com.example.api.constants.proto.entitytype.EntityType.2022-10-01 01:10:01.000

The field being returned to my SnowflakeIO.CsvMapper are this:
fields[0] = customerid,
fields[1] = ....',USER,....',
fields[2] = 2022-10-01 01:10:01.000

but they should be
fields[0] = customerid,
fields[1] = ....'
fields[2] = USER
fields[3] = ....'
fields[4] = 2022-10-01 01:10:01.000

Switching to " quote character is not a sufficient workaround for me because the second field in my query can contains both ' and " chars, so the issue still exists even if I switch.
Repro: Set up a read with a snowflake query that produces two columns: a string column containing the quote character, in my case ', but it could also be ", and a second column, containing anytihng. SnowflakeIO connector will incorrectly decide that the first column continues past the , delimiter so the second column won't exist, or will be malformed.
eg.
NAME, DATE
....',2022-01-01
Will be parsed as
NAME = ....',2022-01-01
DATE = ???
The connector should make use of the Snowflake file format ESCAPE field to properly escape the quote char, and the SnowflakeIO connector should
Expected behavior:
SnowflakeIO provides an escape sequence and properly parses the CSV fields from my query, even when the fields contain the quote char.
Issue Priority
Priority: 2
Issue Component
Component: io-java-snowflake

.add-labels P2

.remove-labels P3

.take-issue

“.take-issue”


Hundres of hidbridge failed to load messages

Hundreds of hidbridge failed to load, Error: No device connected console messages.
Why is it not getting debounced?
hidbridge failed to load, Error: No device connected
51pxtlib.js:1398 hidbridge failed to load, Error: No device connected
pxtlib.js:1398 hidbridge failed to load, Error: No device connected
18pxtlib.js:1398 hidbridge failed to load, Error: No device connected
pxtlib.js:1398 hidbridge failed to load, Error: No device connected
47pxtlib.js:1398 hidbridge failed to load, Error: No device connected

makes it really hard to debug.

Nevermind, seems like a local issue.

Actually the setInterval starts out by polling ever 5 seconds, and then all of a sudden ends up in an infinite loop. Maybe it's calling itself?

P0 any instance of an editor. The serial polling logic is calling itself.

Introduced by this change: https://github.com/Microsoft/pxt/pull/3309/files
@mmoskal what was the reason for adding startHidConnectionPoller inside of initSerial?

The intention of my change was not to re-start the HID connection in the middle of the flashing.
However it seems I've messed it up. In the #3326 it is now fixed correctly - we run a HID ping operation in a loop and only when this fails we restart the serial poller.
CC @caitlin-hennessy


Error after transformed into ONNX

I have used the following code to transform the pytorch model into onnx and found that the output of onnx is different from the original pytorch model.
unet_model = UNet(n_channels=3, n_classes=1, bilinear=True)

model_weight = './checkpoints/CP_epoch100.pth'
unet_model.load_state_dict(torch.load(model_weight))

# Input to the model
batch_size = 1

x = torch.randn(batch_size, 3, 160, 128, requires_grad=True)

torch_out = unet_model(x)

# Export the model
torch.onnx.export(unet_model,  # model being run
                  x,  # model input (or a tuple for multiple inputs)
                  "./onnx/points_unet.onnx",  # where to save the model (can be a file or file-like object)
                  export_params=True,  # store the tra-ined parameter weights inside the model file
                  opset_version=11,  # the ONNX version to export the model to
                  do_constant_folding=True,  # whether to execute constant folding for optimization
                  input_names=['input'],  # the model's input names
                  output_names=['output'],  # the model's output names
                  dynamic_axes={'input': {0: 'batch_size'},  # variable length axes
                                'output': {0: 'batch_size'}})

unet_model.eval()


SIGSEGV in training-operator container

The training-operator pod seems to continually crash:
~$ k get pod -n kubeflow training-operator-64886bdddc-q6nr5 -w
NAME                                 READY   STATUS             RESTARTS       AGE
training-operator-64886bdddc-q6nr5   0/1     CrashLoopBackOff   20 (24s ago)   79m
training-operator-64886bdddc-q6nr5   0/1     Running            21 (90s ago)   80m
training-operator-64886bdddc-q6nr5   0/1     Error              21 (109s ago)   80m
training-operator-64886bdddc-q6nr5   0/1     CrashLoopBackOff   21 (5s ago)     81m
training-operator-64886bdddc-q6nr5   0/1     Running            22 (2m47s ago)   83m
training-operator-64886bdddc-q6nr5   1/1     Running            22 (3m6s ago)    84m
training-operator-64886bdddc-q6nr5   0/1     Error              22 (3m7s ago)    84m
training-operator-64886bdddc-q6nr5   0/1     CrashLoopBackOff   22 (13s ago)     84m
training-operator-64886bdddc-q6nr5   0/1     Running            23 (5m11s ago)   89m
training-operator-64886bdddc-q6nr5   1/1     Running            23 (5m30s ago)   89m
training-operator-64886bdddc-q6nr5   0/1     Error              23 (5m30s ago)   89m
training-operator-64886bdddc-q6nr5   0/1     CrashLoopBackOff   23 (9s ago)      89m

Here are the logs:
$ k logs -n kubeflow training-operator-64886bdddc-q6nr5
1.6831492767944047e+09	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": ":8080"}
I0503 21:27:57.936384       1 request.go:682] Waited for 1.047013258s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/apps/v1?timeout=32s
I0503 21:28:07.936448       1 request.go:682] Waited for 1.447652758s due to client-side throttling, not priority and fairness, request: GET:https://<IP_ADDRESS>:443/apis/scheduling.k8s.io/v1?timeout=32s
1.6831492959898794e+09	INFO	setup	starting manager
1.6831492959905822e+09	INFO	Starting server	{"path": "/metrics", "kind": "metrics", "addr": "[::]:8080"}
1.683149295990631e+09	INFO	Starting server	{"kind": "health probe", "addr": "[::]:8081"}
1.6831492959908807e+09	INFO	Starting EventSource	{"controller": "tfjob-controller", "source": "kind source: *v1.TFJob"}
1.6831492959908864e+09	INFO	Starting EventSource	{"controller": "pytorchjob-controller", "source": "kind source: *v1.PyTorchJob"}
1.6831492959910178e+09	INFO	Starting EventSource	{"controller": "pytorchjob-controller", "source": "kind source: *v1.Pod"}
1.6831492959909546e+09	INFO	Starting EventSource	{"controller": "paddlejob-controller", "source": "kind source: *v1.PaddleJob"}
1.6831492959910433e+09	INFO	Starting EventSource	{"controller": "pytorchjob-controller", "source": "kind source: *v1.Service"}
1.6831492959910588e+09	INFO	Starting Controller	{"controller": "pytorchjob-controller"}
1.6831492959910316e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.MPIJob"}
1.6831492959909766e+09	INFO	Starting EventSource	{"controller": "tfjob-controller", "source": "kind source: *v1.Pod"}
1.683149295991097e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.Pod"}
1.68314929599107e+09	INFO	Starting EventSource	{"controller": "paddlejob-controller", "source": "kind source: *v1.Pod"}
1.6831492959911213e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.ConfigMap"}
1.6831492959911323e+09	INFO	Starting EventSource	{"controller": "paddlejob-controller", "source": "kind source: *v1.Service"}
1.6831492959911401e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.Role"}
1.6831492959911938e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.RoleBinding"}
1.68314929599115e+09	INFO	Starting Controller	{"controller": "paddlejob-controller"}
1.6831492959911199e+09	INFO	Starting EventSource	{"controller": "mxjob-controller", "source": "kind source: *v1.MXJob"}
1.6831492959912286e+09	INFO	Starting EventSource	{"controller": "mpijob-controller", "source": "kind source: *v1.ServiceAccount"}
1.683149295991192e+09	INFO	Starting EventSource	{"controller": "tfjob-controller", "source": "kind source: *v1.Service"}
1.6831492959912865e+09	INFO	Starting EventSource	{"controller": "mxjob-controller", "source": "kind source: *v1.Pod"}
1.6831492959913003e+09	INFO	Starting Controller	{"controller": "tfjob-controller"}
1.683149295991317e+09	INFO	Starting EventSource	{"controller": "mxjob-controller", "source": "kind source: *v1.Service"}
1.6831492959913347e+09	INFO	Starting Controller	{"controller": "mxjob-controller"}
1.6831492959912405e+09	INFO	Starting EventSource	{"controller": "xgboostjob-controller", "source": "kind source: *v1.XGBoostJob"}
1.6831492959913042e+09	INFO	Starting Controller	{"controller": "mpijob-controller"}
1.683149295991399e+09	INFO	Starting EventSource	{"controller": "xgboostjob-controller", "source": "kind source: *v1.Pod"}
1.6831492959914432e+09	INFO	Starting EventSource	{"controller": "xgboostjob-controller", "source": "kind source: *v1.Service"}
1.6831492959914646e+09	INFO	Starting Controller	{"controller": "xgboostjob-controller"}
time="2023-05-03T21:28:16Z" level=info msg="MPIJob default/distributed-pytorch is created."
1.6831492960953653e+09	INFO	Starting workers	{"controller": "pytorchjob-controller", "worker count": 1}
1.6831492960979536e+09	INFO	Starting workers	{"controller": "mxjob-controller", "worker count": 1}
1.683149296098295e+09	INFO	Starting workers	{"controller": "mpijob-controller", "worker count": 1}
1.6831492960982726e+09	INFO	Starting workers	{"controller": "xgboostjob-controller", "worker count": 1}
1.6831492960983038e+09	INFO	Starting workers	{"controller": "paddlejob-controller", "worker count": 1}
1.683149296098327e+09	INFO	Starting workers	{"controller": "tfjob-controller", "worker count": 1}
time="2023-05-03T21:28:16Z" level=info msg="Reconciling for job distributed-pytorch"
1.6831492960995376e+09	DEBUG	events	ServiceAccount: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "ServiceAccount is exist"}
1.6831492960998297e+09	DEBUG	events	LauncherRole: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "LauncherRole is exist"}
1.6831492960998945e+09	DEBUG	events	RoleBinding: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "RoleBinding is exist"}
1.683149296100283e+09	DEBUG	events	ServiceAccount: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "ServiceAccount is exist"}
1.6831492961005068e+09	DEBUG	events	LauncherRole: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "LauncherRole is exist"}
1.6831492961005259e+09	DEBUG	events	RoleBinding: distributed-pytorch-launcher	{"type": "Normal", "object": {"kind":"MPIJob","namespace":"default","name":"distributed-pytorch","uid":"3f79ab3c-01ef-40b1-9933-28d4850aab97","apiVersion":"kubeflow.org/v1","resourceVersion":"14930637"}, "reason": "RoleBinding is exist"}
1.683149296100843e+09	INFO	Observed a panic in reconciler: runtime error: invalid memory address or nil pointer dereference	{"controller": "mpijob-controller", "object": {"name":"distributed-pytorch","namespace":"default"}, "namespace": "default", "name": "distributed-pytorch", "reconcileID": "3684a27a-dd10-4f63-be0b-f732937ff5d5"}
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x165dd6e]

goroutine 1919 [running]:
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1()
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:118 +0x1f4
panic({0x18a95e0, 0x2a95b90})
	/usr/local/go/src/runtime/panic.go:884 +0x212
github.com/kubeflow/training-operator/pkg/controller.v1/mpi.(*MPIJobReconciler).UpdateJobStatus(0xc0003f0280, {0x1ac0a80?, 0xc000e51860?}, 0x1ac0a80?, 0xc00089c780)
	/workspace/pkg/controller.v1/mpi/mpijob_controller.go:597 +0x16e
github.com/kubeflow/common/pkg/controller.v1/common.(*JobController).ReconcileJobs(0xc0003f0280, {0x1ac0a80, 0xc000e51860}, 0x1dbaf40?, {{0xc0007148c0, 0x1, 0x1}, 0x0, 0x0, 0x0, ...}, ...)
	/go/pkg/mod/github.com/kubeflow/common@v0.4.6/pkg/controller.v1/common/job.go:333 +0x1e35
github.com/kubeflow/training-operator/pkg/controller.v1/mpi.(*MPIJobReconciler).Reconcile(0xc0003f0280, {0x1da5158, 0xc0006c7110}, {{{0xc000724378, 0x7}, {0xc0012980d8, 0x13}}})
	/workspace/pkg/controller.v1/mpi/mpijob_controller.go:161 +0x472
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0x1da50b0?, {0x1da5158?, 0xc0006c7110?}, {{{0xc000724378?, 0x1a2ef20?}, {0xc0012980d8?, 0x4045d4?}}})
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121 +0xc8
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc000b172c0, {0x1da50b0, 0xc000a9f700}, {0x1938ce0?, 0xc0009bc0a0?})
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320 +0x33c
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc000b172c0, {0x1da50b0, 0xc000a9f700})
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273 +0x1d9
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:230 +0x333

I've seen it mentioned on previous issues that requested memory or certain probe timeouts might need to be increased, e.g., #1717. Does this seem like one of those cases?

After deploying freshly, it seems to stay in Running without a problem until the instant I launch an MPIJob, at which point it crashes.

I should mention that I installed the operator with the following:
kubectl apply -k "github.com/kubeflow/training-operator/manifests/overlays/standalone?ref=v1.6.0"

And here's my k8s:
Client Version: v1.26.1
Kustomize Version: v4.5.7
Server Version: v1.26.1

https://github.com/kubeflow/training-operator/blob/8a066f9386e9fb739815e9001f4fe53158227646/pkg/controller.v1/mpi/mpijob_controller.go#L597
It looks like spec.Replicas is nil pointer.

After deploying freshly, it seems to stay in Running without a problem until the instant I launch an MPIJob, at which point it crashes.

Could you provide the mpijob yaml?

Ah, that was it. I had no value for mpiReplicaSpecs.Launcher.replicas, thinking that it would default to 1. Adding that back into the spec prevents the bad behavior I observed earlier.

We can add a default in the next release

agree.

We can add a default in the next release

/assign
I will add a default for custom job.


Broken image links on the README

The images under "Additional Information" are broken.
See:

I'm closing the issue, since it's fixed see: https://github.com/w3f/Grants-Program#additional-information


FreeConsole() doesn't work past 5s during CTRL_CLOSE_EVENT

Windows Terminal version
1.17.11461.0
Windows build number
10.0.19045.3086
Other Software
c++
mingwx64
an ide of your choice
cpu arch: x64
Steps to reproduce
compile this code in c++ and run it.
go to task manager --> open terminal group processes --> program.exe --> go to details
click the x button on windows terminal.
the process of program.exe is no longer running and if you insert a while loop in the handler it closes 5 seconds later. This bug is reproducible with cmd powershell and conhost and windows terminal. I don't know which program issue or issues its on so I am reporting it here
BOOL WINAPI controlHandler(DWORD sig)
{
	if(sig == CTRL_CLOSE_EVENT)
	{
		Beep(800, 500);
		FreeConsole();
		return TRUE;
	}
}
int main()
{
   SetConsoleCtrlHandler(&controlHandler, TRUE);
   while(true);
}

Expected Behavior
the process to stay open
Actual Behavior
process closes
Related Note:
FreeConsole() api doesn't have a parameter of PID and doesn't free all child processes another bug

The 5s timeout stems from SPI_GETHUNGAPPTIMEOUT and you cannot prevent the console from killing your process by calling FreeConsole at the moment. Personally speaking, I'm actively not wishing to fix this right now. It'd be weird if a previously visible console application could keep running indefinitely even after the user closed the window explicitly. It's like the window vanishing on its own when FreeConsole is called, but even worse in a way?
If you ever choose to do hacks like this one I need to point out that they can (and honestly probably will, given enough time) break in the future if we ever choose to not inject threads anymore.

It might be better to suggest this to terminal-wg, but maybe it's appropriate to mention it here. I'm drafting a ngvt-input-mode protocol and clarifying compatible options. Perhaps this mode will allow applications to continue working in case of an attempt to close the terminal window (see Shutdown section).

I think we should investigate whether we should support this. If it's easy to implement: Let's just do it! (We'd also accept a PR if it's a simple change.) But we don't really believe that this is an important aspect to fix and implement right now, unless more people request this or if any other circumstances change.


Hive custom storage handlers

Replacement for https://github.com/TeradataCenterForHadoop/presto-td/pull/11

Just checking what's the status of this pull request?

@losipiuk @pnowojski @arhimondr if #3488 replaces this PR, can you close this one please?

Closing based on our discussion yesterday.


Replaced video link - Credential Guard

Related to PR: https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3789
Sorry for the delay, I have corrected the article to remove the video at the top and then at the bottom replace the video with the LinkedIn video relevant to this article.  I also put a note and link to the LinkedIn Learning subscription that is needed.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@martyav This is a follow-up on the previous PR #3789 that you have reviewed. Would you care to comment as the time permits? Thank you.


Zero value is treated as false

If the variable is having zero as the value, the placeholder is not replaced.

Good catch!

Simple hack.
if (value == 0) {                     value = '0'                 }

Thank you so much for quick fix. Appreciate it!!

Actually, I'm checking like this: if (value !== undefined)
It's in the CI pipeline right now, should be available in npm in a few seconds.
Thanks for your collaboration.


Using env.get instead of if...in

I had a question about the following piece of code in falcon.request.Request:
# PERF(kgriffs): if...in is faster than using env.get(...)
        if 'QUERY_STRING' in env:
            self.query_string = env['QUERY_STRING']

            if self.query_string:
                self._params = parse_query_string(
                    self.query_string,
                    keep_blank_qs_values=self.options.keep_blank_qs_values,
                )

            else:
                self._params = {}

        else:
            self.query_string = ''
            self._params = {}

For the part,
 if 'QUERY_STRING' in env:
     self.query_string = env['QUERY_STRING']

Arent you performing two hash operations (one for checking and one for retrieving)? Based on that, env.get should be better?

This's faster than both .get() and if ... in ...:
try:
    self.query_string = env['QUERY_STRING']
except KeyError:
    pass

Arguably more Pythonic, too (EAFP and all that.)
On Wed, Oct 21, 2015 at 12:16 AM, Philip Tzou<EMAIL_ADDRESS>wrote:

This's faster than both .get() and if ... in ...:
try:
self.query_string = env['QUERY_STRING']except KeyError:
pass
—
Reply to this email directly or view it on GitHub
https://github.com/falconry/falcon/issues/637#issuecomment-149777120.

--
.

I agree that is more Pythonic but the query string does not always exist so based on that it could be slower because catching the exception is the expensive part.

try/catch is actually cheaper in python than people seem to assume, see,
inter alia,
http://stackoverflow.com/questions/2522005/cost-of-exception-handlers-in-python
On Wed, Oct 21, 2015 at 11:15 AM, Usman Ehtesham Gul <
<EMAIL_ADDRESS>wrote:

I agree that is more Pythonic but the query string does not always exist
so based on that it could be slower because catching the exception is the
expensive part.
—
Reply to this email directly or view it on GitHub
https://github.com/falconry/falcon/issues/637#issuecomment-149928413.

--
.

Lol...that was the exact link i was referring to where if you see below in the same link:
"A try/except block is extremely efficient if no exceptions are raised Actually catching an exception is expensive."

@ueg1990 QUERY_STRING is one of the standard WSGI envrion keys. I consider it's a strong signal that QUERY_STRING exists in most circumstance. I also did a small investigate of some popular HTTP servers which are compatible with WSGI and below is my result:

In Gunicorn, QUERY_STRING is one of the default environs
In CherryPy, QUERY_STRING defined in get_environ() method
In Tornado, QUERY_STRING is one of the defaults in environ() method
Even nginx's uwsgi_params file defined QUERY_STRING

thanks for sharing...that does help alot :)

Based on @philiptzou's observations, it seems like moving this to a try..catch would make sense.

I will be working on this :)


Provide compatible types for v5.x

Upgrading from 5.0.0 to 5.1.1 causes Typescript errors: https://github.com/MetaMask/json-rpc-engine/actions/runs/5660095486/job/15335070066?pr=147
https://github.com/MetaMask/json-rpc-engine/pull/147#pullrequestreview-1393995103
Would be great to fix the types so a new ^5.0.0 install works with code implemented towards 5.0.0.

@Mrtenz Did you have a chance to look at this?

I don't really have the time to look into this at the moment. If you want to take a look, feel free!


Adding filler_word augmentation

Adding augmentation based on filler words (for English).
Initial commit is only for SentenceOperation / Text Classification / English.
Could be extended to other tasks.
Ex.:
"Ujjal Dev Dosanjh served as 33rd Premier of British Columbia from 2000 to 2001"
"Ujjal Dev Dosanjh uhm served as 33rd Premier of British Columbia I feel from ahh 2000 to 2001"
IMDB accuracy goes from 96 to 92 (aychang/roberta-base-imd)

Hi, thanks for the transformation! If I understand correctly, the filler words are inserted at random places, is this correct? If so, are we convinced this is the "best" way to introduce these words? I suppose that for starters we could use random insertions, but some kind of parameter to control their plausibility would be nice. Also, this is one perturbation that it would be nice to be able to control the rate of, similarly to the Butterfingers typo ones, where the rates of 0.02 and 0.05 correspond to different degrees of frequency of the perturbation in the input.

Hi, thanks for the transformation! If I understand correctly, the filler words are inserted at random places, is this correct? If so, are we convinced this is the "best" way to introduce these words? I suppose that for starters we could use random insertions, but some kind of parameter to control their plausibility would be nice. Also, this is one perturbation that it would be nice to be able to control the rate of, similarly to the Butterfingers typo ones, where the rates of 0.02 and 0.05 correspond to different degrees of frequency of the perturbation in the input.

Thanks for the feedback.
The filler words are inserted at random places, that is correct. They can, in principle, appear before any word in the sentence, so the augmentation is plausible as it is. I was considering applying a more restrictive strategy (e.g.: at the beginning of the sentence, before/after the predicate, subject, and object), but decided against it as that would make the augmentation too dependent on external resources and libraries and too language specific. Currently it can easily be adapted to other languages and tasks with very simple modifications. However I can incorporate such change if you think that would be better.
The rate of the insertion is a parameter of the generate function, so it can be changed (default is 0.166 corresponding to 1 in 6 words).
The generate function also has parameters for the types of filler words and phrases to be used (default is use all words and phrases).

Thanks for the answer!

Thanks @venelink for your changes. I think this satisfies the review criteria. The README has been nicely written with the appropriate citation of the source of the phrases. Just one thing missing is the keywords.
Besides, I think overall, this can be easily extended to the multilingual case (in a separate PR). There are some good resources here.

Thanks for the feedback. I checked the keyword resources, and I believe the correct keywords would be:
noise, rule-based, external-knowledge-based, tokenizer-required, possible-meaning-alteration, high-coverage, high-generations
However, the keywords documentation doesn't say where those keywords should be put. Could you please let me know where I should introduce them?
Thanks in advance.

Seems the checks are failing. You might want to pull the latest main. There were a couple of changes that were done in the base repository which your code might not have. And here is the sample keywords variable.

Added the keywords to the class, as suggested.

Hi @venelink thanks for your changes. I like the fact that you have chosen to split the filler words into 3 categories. I have a couple of suggestions here:

The list of words are limited in each set. Maybe other lexicons could be explored to make this transformation stronger.
Each of the 3 sets you've defined can probably be 3 different transformations?
You should consider performing a robustness evaluation to add it to the leaderboard here.

I am going ahead and merging with this one meanwhile. Feel free to incorporate the above suggestions in a separate PR. :)


[BUG] @Builder.ObtainVia with a super class does not work anymore in JDK1

Following construct works fine in JDK8
@AllArgsConstructor
@Getter
@Setter
public class SuperClass {
    private Long id;
    private Date createdDate;
}

@Getter
@Setter
public class TestClass extends SuperClass {
    private String name;

    @Builder(toBuilder = true)
    protected TestClass( @Builder.ObtainVia(method = "getId") Long id,
                         @Builder.ObtainVia(method = "getCreatedDate") Date createdDate,
                          String name ) {
        super(id, createdDate);
        this.name = name;
    }
}

However this fails to compile in JDK11 with the error:
[ERROR] /Users/marc/Code/temp/demo/src/main/java/com/example/demo/TestClass.java: incompatible types: java.util.Date cannot be converted to java.lang.Long

It's like it keeps looking at the first argument of that builder?

@slyoldfox
Remove toBuilder = false .  Then no error occurs. Use Builder() insted of toBuilder().

@devdotlog thank you for the suggestion, it is exactly what I had to do (and rework a bunch of code). toBuilder is an instance method which copies the existing object (well not quite - not the super class unles you specify your own builder, which is what we have it in place for).
We mainly use it for dto update scenario's.

You could also give @SuperBuilder a try. It also supports toBuilder and you don't have to manually use @ObtainVia.
However, this is still a bug and should be fixed.

@janrieke yes I know about that.
But @SuperBuilder would imply also a @SuperBuilder on the super class?
The super class is not part of our code so we cannot go down that road.
Just adding @SuperBuilder on the subclass does not work because it fails to compile with cannot find symbol SuperClassBuilder

Yes, then you cannot use @SuperBuilder.


api interface /api/generate I need to make sure that every question is not answered from the previous record  How to do?

api interface /api/generate I need to make sure that every question is not answered from the previous record  How to do?

As long as you don't use the context parameter, generate does not keep chat memory.

As long as you don't use the context parameter, generate does not keep chat memory.

Hi @royjhan , can you please let me know how to use this context parameter, I'm unable to figure it out by reading the documentation.
I want to use the context from previous responses in current one.
Pls help me out, if possible give me a code example it would be a great help. Thanks!


API endpoint

We need to start working on API endpoint. We can use the old one - but we need to introduce the new field into
https://github.com/keenlabs/Keen-Web/blob/774ebdb97b507a92c7ade7011f10c412c66cc656/app/models/dashboard.py
the field will contain the whole JSON that the builder produces

let's move our conversations into
https://github.com/keen/dashboard-builder/issues/32


Log4Net StackdriverAppender: Use %property values in custom labels

Is your feature request related to a problem? Please describe.
Attempting to use %property syntax on custom label values. It shows up in Stackdriver like this:
labels: {
  Key:  "%property{AccountID}"
...
 }

I want the value inserted at runtime, similar to what I can do with the message:
<conversionPattern value="%property{AccountID} ...
Describe the solution you'd like
I'd like to label my logs with some context from the application.
<customLabel>
      <key value="AccountID" />
      <value value="%property{AccountID}" />
</customLabel>

Describe alternatives you've considered
Put the dynamic data into the log message directly.
Additional context

I think this is where a replacement would happen.
I saw that adding new labels dynamically was prevented completely in #1036. I would just be looking to change the values dynamically.

Assigning to Chris to consider this.

@chrisdunelm Any updates on considering this feature request?

@rkalasky @bryanroth It isn't entirely obvious how to support this.
The patterns require parsing by PatternLayout (which is essentially a collection of PatternConverters).
We cannot re-use any already-present PatternLayout, as there is no guarantee there will be one at all; and even if there is it is not possible to use multiple patterns within a single PatternLayout instance.
So we'd need to create a new PatternLayout instance for each label, which could be done, but I cannot see any simple way of allow this layout to be configured (beyond the pattern), so no custom converters would be possible.
The use of patterns within custom labels would be gated on a flag, something like UsePatternWithinCustomLabels - the default of false would preserve existing behaviour.
Please let me know your views on this, or whether you can see a better way to achieve this.

I would be totally fine with this behavior being gated behind a flag.
My understanding of the log4net internals is novice level, but I don't think custom converters are necessary. I would be happy with the built-in %property{...} (PropertyPatternConverter?) syntax.
We're putting this data into the log message directly today using the above syntax.

Any news on this? It would be required for us to put the %property{log4net:HostName} in one label to filter our logs.

@chrisdunelm Any idea when this change will get published?

@bryanroth It's already in beta on nuget: https://www.nuget.org/packages/Google.Cloud.Logging.Log4Net/2.4.0-beta01

@chrisdunelm Brilliant. Thanks for letting me know. Is there a good way to see the release notes for updates to this nuget package?


missing tools

Documentation feedback

Page title: CrateDB Clients and Tools
Page URL: https://crate.io/docs/crate/client-tools/en/latest/index.html
Source: https://github.com/crate/crate-clients-tools/blob/master/docs/index.rst

@joemoe reported that Azure Functions and R are missing from this page

@joemoe can you provide more details? what would you like to include/add here, explicitly?

I'd also scan our blogposts. E.g. we can add SQL Pad and also link external blogposts like this.
https://devblogs.microsoft.com/azure-sql/querying-and-visualizing-data-using-sqlpad/

Tied to https://github.com/crate/tech-writing-domain/issues/106

Related to https://trello.com/c/4Wi958uf/67-how-to-blogpost-pentaho-old-card


Updated react-native-fetch-blob

start from react-native v0.47, createJSModule is removed in android and it causes android not building. In order to fix this issue, underline library react-native-fetch-blob needs to be upgraded.

@kfiroo as I explained, this patch has to go though in order for this library to be compiled in android. Would you please merge and update the npm?

@alinz Hey! Thanks so much for this!
I will soon release v1.4.0 with compatibility with RN47 and I'll include this PR there.

Is there an ETA on 1.4.0?

@beeglebug its published as 1.4.0-rc if you want to give it a shot


ZEPPELIN-269 : Adding Notifications Service for Zeppelin

Adding Notifications Service for Zeppelin

[x] Notifications feature added
[x] UI-Notifications component added
[x] Zeppelin notifications can be configured
[x] Different level of notification

Notification.primary()
Notification.info()
Notification.success()
Notification.warning()
Notification.error()

Screen shots

looks good... what is the guideline on when to show this notification?

zeppelin Notifications are designed to inform users about status of zeppelin.
(All Notifications messages should give informative feedback.)

Error Notifications will inform system issues.
eg: Network issue, File loading issue,  System failtures

Warning Notifications are based on incorrect user interactions such as wrong data types/ queries/ wrong data model for chart types.

Primary notifications inform basic informations to the users. There are few other notification levels as well.

Default message will be shown for 10000 ms (time is configurable) and after that the message starts fading out. If user noticed the notification, user can remove it by clicking on it.

Just tested it out a bit.
I'm not a big fan of the hover effect on the error (it gets a bit transparent)
I also think the message time should be reduced to something like 6000ms, currently its too long.
I'm not getting the console.log anymore when the error is showing.
(Need to check it out, because we can't have those errors not showing in console)
I think it could also be nice not to include any error call in this PR (just the service) and add error calls in another PR.
Because in current Zeppelin state, there is a lot of problems making the error spam a lot, for example:

I get the angular error everytime I hide/show the editor code.
I get the angular error 3 times when running the paragraph (because bind is called 3 times)

@corneadoug Thanks for the feedback I will update PR

also what if I want to copy the error? If I click it disappears. Maybe a close X or something and the text is selectable?

@djoelz this could be useful.
But I guess this type of error is only as a visual signal that something went wrong and message would be pretty short, you would usually find a stack in the console.

@corneadoug think of a case where the user does not have access to the console. Think Zeppelin hosted as a website. Then users might run into issues that they want who ever is hosting the site to investigate. How would they send these errors? That's why I think being able to copy the text would be useful.

console = web browser dev tools console.
What I mean is that those message are visual feedback, they wouldn't be enough for debug.
But copy pasting it could be a plus.

@djoelz Current Zeppelin doesn't have facility to show error messages or system failures for the users on web user interface. So the notification service will enable this. Zeppelin developers could use this notification service for error handling. The answers @corneadoug have given are correct.
If any more uncleared issues please let us know.
Thanks.

@corneadoug
Hover is fixed for less transparent and Error Notifications have removed so PR only contain notification services.
Default message time is 6000ms.If notification message is needed to show for more duration than default time. It can be done as below.
  // Message with custom duration
  Notification.error({message: 'Error notification', delay: 1000});

@Leemoonsoo : Ready for Merge
@bzz, @corneadoug This contain notification services

I have more feedbacks/changes, especially to match @djoelz comments.
So I will do a PR on your branch :)

@Madhuka Can you update the PR description with new screenshot from my PR?

@corneadoug Thanks
I will share it

Moved to 'ngToast Directive' from 'angular-ui-notification'. It include below features

Button to close the notification
Auto close at 6000ms
No close event on notification click
Changed the original ngToast style
Error message can be copied

Notifications can be used by including ngToast service in the controller. It support four different level of notification:

ngToast.danger('message')
ngToast.warning('message')
ngToast.info('message')
ngToast.success('message')

Looks good to me (obviously) :)
Merge +1

That looks great! Good job guys!

It is good to go for Merge.
+1

I wanted to mention that there were similar effort before. https://github.com/apache/incubator-zeppelin/pull/224.
Can someone tell me how i can use this feature?

@Leemoonsoo
Yes, #224 also had same feature but in here we some improvements you can see it UI.
You can used notification service by calling.
//passing danger notification for user
ngToast.danger('message')

//passing warning for user
ngToast.warning('message')

//passing some information for user
ngToast.info('message')

//giving success notification for user
ngToast.success('message')

Thanks for usage. tested and working well.
LGTM!

#224 was closed, and I'm not sure why.
You can find most of the differences in this PR thread, main ones being:

Copy paste of message allowed (no more close notification when clicked)
Closing button on the notification

This PR only brings the Notification Service, so that we separate adding the notifications in the zeppelin code from adding the Notification Service.
On top of what @Madhuka said, you will also have to inject the service in your controller, for example:
angular.module('zeppelinWebApp')
  .controller('ParagraphCtrl', function($scope, $rootScope, $route, $window, $element, $routeParams, $location, $timeout, $compile, websocketMsgSrv, ngToast) {


Stack frame names have [Unoptimized]  prefix

I'm not sure if this is deliberate, but it seems a bit strange. We use the name from the source in StackFrame to show in the IDE, and in a recent dev build they've started being prefixed with [Unoptimized]:

It seems like this would be better as a flag to let the editor choose how to display it rather than putting it here (or at least, having it on the end so it doesn't truncate the visible method names as much).
(@a-siva is this something you'd know about?)

Where are you reading this from? There is no type called 'StackFrame' exposed over the VM service.

Sorry, I should've been more explicit. We read the name field from a Frame's code., for ex. getStack().frames[x].code.name. I don't know if this is the correct thing for the IDE to show in the call stack list, but it seemed appropriate (up until now, at least).
If there's something better, I can easily change this though.

getStack().frames[x].function.name should give you the function name

The value in .function.name doesn't seem to be as descriptive as the one from .code, for example:
frame.code.name:     main.<anonymous closure>.<anonymous closure>
frame.function.name: <anonymous closure>

I think that IntelliJ also uses .code.name if I'm looking in the right place (@pq?):
https://github.com/JetBrains/intellij-plugins/blob/5fb99c284ae67a4895da6120a349b270c9149699/Dart/src/com/jetbrains/lang/dart/ide/runner/server/vmService/frame/DartVmServiceStackFrame.java#L79
So I'm not sure what to do - I think changing it to .function would be less useful (and the issue would probably still exist for IntelliJ). Do we need to have the prefix in .code.name or could we change it back (or add it as its own field or something)?

No, Code objects should not be displayed. Even before this change, Code.name would sometimes be prefixed with a star (which meant optimized). The appropriate name to display to users is Function.name, which can be qualified if desired by pretending the name of Function.owner.

I tried prefixing with the .owner's names (recursively), but I found instances where frame.func.name and frame.func.owner.name are the same, so I end up with duplication (that wasn't there in the previous code):

I'm not really sure what is the correct representation for these since they're kind cryptic.
@pq @devoncarew maybe if you figure out what you're going to do for IntelliJ I can just borrow it? 😁

Implicit closures are objects used to represent tear-offs, so they have the same name as the original non-torn off method. I think you can detect this case easily by checking the kind.

Thanks! Is there an easy way to tell what the full list of kinds are (or whether any others may be the same as their parents like this)? It doesn't look like they're in this doc - or at least, I can't see ImplicitClosureFunction in there.


Kegbot bugreport - local variable 'output' referenced before assignment

/kegadmin/bugreport/
local variable 'output' referenced before assignment
This is happening after upgrade to 1.2.3
See the following for details:
http://dpaste.com/212PV3E - stack trace with DEBUG = True
http://dpaste.com/2YJZR54 - python traceback
http://dpaste.com/2DDK5FM - bugreport from comman line running 'kegbot bugreport'
I tried editing /pykeg/web/kegadmin/views.py to set output to None before the try block.  This did get rid of the "local variable 'output' referenced before assignment" error, however the "CalledProcessError: Command 'kegbot bugreport --noinput' returned non-zero exit status 127" remained

Figured out what the issue was....not running in the virtual environment.  I finally noticed that the python that was being used to run subprocess.py was /usr/lib/python2.7 and not the one in the kegbot virtualenv
Sorry for the erroneous issue report.


Chex dataclass defaulting mappable_dataclass=True

To start with, thanks for open sourcing your work on Chex, it's a great tooling library for building robust Jax applications!
As I was upgrading to the latest release 0.0.3, I noticed quite a few of my tests breaking. It happens that the default option mappable_dataclass=True in chex.dataclass is breaking the usual interface of dataclasses (which is clearly expected reading  the code documentation!)
I guess probably from the perspective of Deepmind usage, it makes sense to default this option. But from an external user point of view, it is rather surprising to have a dataclass decorator not behaving like a dataclass. I think it would be great to make it clear in the library readme that this option needs to be turned off to get the full dataclass behaviour (or turned it off by default).

Thanks for the positive feedback, we're happy that you found Chex useful in your projects!
The goal of Chex dataclasses is to extend the original interface rather than change it.
At this moment, the only existing incompatibility is that chex implementation prohibits positional arguments in constructor, which is done intentionally:
a) to reduce a risk of hard-to-detect errors related to wrong arguments ordering and
b) to improve code readability.
Apologies that this is not mentioned in the docs. Is it a reason of the breakage that you observed in your tests?

Thanks for the explanation. I completely agree with the motivation behind removing positional arguments. I guess I just got unlucky with using positional args on some very simple dataclasses + redefining the __getitem__ on some other for slicing purposes, which conflicted with the dict interface chex is setting up.
But no big deal, I guess mentioning it more clearly in the docs would avoid the surprise for others :)


SSLContext warning

Email by: Roy Thorsby
I'm currently reverse geocoding a big file of addresses and trying to compare the results from multiple geocoders.  I've had success with some but a few such as google, mapbox and geocode farm seem to print this error/warning:
C:\Python27\ArcGIS10.3\lib\site-packages\requests\packages\urllib3\util\ssl_.py:120: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning

I'm not a programmer by trade and mostly work with GIS processes so the cause for this eludes me.   I was wondering if you were familiar with this issue at all.  I'd appreciate any feedback.

I would recommend downloading the latest version of Python 2 or 3.
$ python --version
Python 2.7.10

https://www.python.org/downloads/
I believe some ArcGIS platforms come with a built-in Python 2.6 or lower.
Best way would be to create your own virtualenv.
$ virutalenv env
$ source ./env/bin/activate
$ pip install geocoder


IMPORTANT use migrations instead of sync

this is really important if we wanna add more models
use this in development aswell --> easier to transition to production
https://sequelize.org/v5/manual/migrations.html

implemented

implemented


No generics

Motivation
Now that we plan a new genesis, I'm moving to just break the binary compatibility and prepare for the future.
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
existing coverage
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/main/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

/land

:broken_heart: Test Failed - ci-test

/land


As a developer, I'd like to investigate the usage of Login Flows to improve the new user experience for the NPSP

Might be worth investigating this feature as we think more comprehensively about the new user experience and onboarding process
https://help.salesforce.com/apex/HTViewHelpDoc?id=security_login_flow_create.htm&language=en_US

all the samples really point towards using it to enable additional login security protocols, vs. a new user wizard.  I assume you were thinking about the latter?

Yeah, I'm curious if it allows you to drop into any generic flow or if its 2-factor only

**lurch: attach W-007358

Tracking W-007358

This has been marked as "Never" internally.


Internal Mobile Releases

Motivation
As the Shabad OS team, we'd like to be able to run the mobile app on our own devices, so that we can continuously test.
Goal

A change to main/trunk should automatically reach our devices, with no intervention from developers and testers

iOS
Android

The app should at least have some basic functionality (already done/almost there)

Opening bookmarks
Reading a shabad
Search

Stories/Tasks

#6
#136
#160
#13

We have TestFlight + Play Store releases to 2 different apps: com.shabados.app and com.shabados.next.app, to represent our 2 different environments.
Each has a Core Team group, Beta Testers (Instant) group, and on Testflight, Beta Testers external group.


Tree.lexicalScope

Prerequisites:

[ ] Online mirror with support for Ref.symbol (#606)
[ ] Rudimentary functionality to work with symbols (#609)

A fairly frequent feature request from scala.reflect users and now from scala.meta users (via our Gitter channel and via scalafix) is the functionality to enumerate definitions visible from a given location in the program. Here's one important practical motivation for introducing this functionality: https://github.com/scalacenter/scalafix/pull/42.

This functionality would also be useful to view implicits in scope.

Recently, we decided to limit the surface of our work to actionable items only - either bugs in existing code or feature requests that are warranted by the roadmap.
While semantic API is definitely on our roadmap, we're going to figure out desired APIs from use cases, not from reflecting on scala.reflect and pondering what functionality from there we should add to Scalameta. That's why I'll be closing this issue and letting feature requests be submitted naturally by our users.


Prepare v0.6.4 release

The primary difference as of this release is that we generate release notes with changie before releasing, and we use this file in GoReleaser. For now this is manual, but it will be automated as soon as we are confident that this is the right approach.
Opening as a draft PR, want to double-check in my fork that releasing works as expected (wouldn't want to have to fix issues half-way through releasing).

Do you need to run changie merge in all four directories?

I just checked on my fork that this works as expected: https://github.com/gerhard/dagger/releases/tag/v0.6.4

Converting this PR to ready for review so that we can finally merge & produce the Engine & CLI releases.


set tab width for listings

Hello. Is there any way to have the debugger show tabs with something other than the standard 8 spaces? Would make for much more readable listings for me  👍

Since the debugger prints to the terminal, this is likely more a terminal feature than a debugger feature. You can potentially change the tab width for interactive shells using tabs: https://askubuntu.com/questions/63424/how-to-change-tab-width-in-terminal-in-ubuntu-10-04
If anybody wants to send a pull request to add a special option (environment variable maybe?), the code for node-inspect has been moved to the main nodejs/node repository.


Ability to Drag and Drop Items/Abilities out of Sheet

While currently you can drag items into the NPC sheet, it would be nice to have a way to drag them back out, as currently you have to change the NPC sheet to the default one, drag things out, and revert.

Agreed. I’ll look at that.
On Nov 17, 2022 at 3:27 PM -0800, Kailan7401 @.***>, wrote:

While currently you can drag items into the NPC sheet, it would be nice to have a way to drag them back out, as currently you have to change the NPC sheet to the default one, drag things out, and revert.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

I'm not actually sure why dragging out of the sheet won't work...


[REQ] Component Request: Medium Vibration Sensor Switch

What's the full name of the component you'd like to see in Adafruit.io WipperSnapper?
The full name of the specific component.
What type of component is this (i.e.: Pin, I2C)?
Pin, digital
Product URL or Datasheet
https://www.adafruit.com/product/2384
Additional context
Add any other context about the component request here.

This issue is marked for Hacktoberfest 2022. If you are participating in Hacktoberfest and want to take on this issue, please first fully read through the guide for "How to add a new component to Adafruit IO WipperSnapper".
For I2C Components to work, please note that you are required to add both an I2C component definition (see this guide page for more information) to this repository and an I2C component driver (see this guide page for more information) to the WipperSnapper Firmware Repository.
If you have any questions, comments, or concerns, please feel free to tag me in the comments here, or in your pull request for review.
Happy Hackin'!


Connecting Remotely Not Possible When Server Listening on TCP 1433 and UDP 1434

Hello All
I successfully installed SQL Server 2022 Developer onto an ARM64 device using these scripts and it works fine on the local network after enabling TCP/IP in the registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.SQLDEVELOPER\MSSQLServer\SuperSocketNetLib\Tcp

TCP port 1433 and UDP port 1434 are open in the Windows firewall on that machine and are forwarded from the router and if I switch the rule on the router back to the old SQL Server it all connects straight away but if I switch to the new one then it just times out.
I know this installs as a named instance (whereas the old server is installed without an instance) but I have tried connecting with:

EXTERNAL_IP
EXTERNAL_IP,1433
EXTERNAL_IP\SQLDEVELOPER
EXTERNAL_IP\SQLDEVELOPER,1433
EXTERNAL_IP,1433\SQLDEVELOPER (some reported this way around worked)

Internally I can just use the DNS name or internal IP and it connects.
According to netstat the server is listening on port 1433 and establishing connections:

I know the named instances require the SQL Browser service but it is running and connections across the internal network work without any issues connecting in a second or two and switching the router to point at the old SQL server then this connects remotely but when I switch to the new server it just times out.
I have followed various guides but so far nothing has made any difference.
Is it possible for the script to perhaps let you install it without adding an instance name as if you only plan to install the one instance then it would be better if it could just be the default.
My issue has to be either related to working with a named instance or perhaps it is an issue with the ARM64 install script but it works fine internally.
Thanks
Robin

Sorry for raising the above issue as just troubleshooted this again and there was a configuration issue on the routing and it actually works fine over the external network and I am able to connect. Some of the firewall rules were set as paused and I hadn't realised meaning they were essentially doing nothing.


[Extensions] Migrated Search Top Anomaly Result to extension

Description
This PR migrates Search Top Anomalies Results to extension for the below requests.

[x] GET  _extensions/_ad-extension/detectors/lxkMxYcBs8GyCDhBVHXy/results/_topAnomalies?historical=true
[x] GET _extensions/_ad-extension/detectors/lxkMxYcBs8GyCDhBVHXy/results/_topAnomalies?historical=false

Issues Resolved
https://github.com/opensearch-project/opensearch-sdk-java/issues/379
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.

Codecov Report

Merging #884 (91e9244) into feature/extensions (ee9e963) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@                   Coverage Diff                    @@
##             feature/extensions     #884      +/-   ##
========================================================
- Coverage                 34.99%   34.92%   -0.07%
+ Complexity                 1888     1887       -1
========================================================
  Files                       300      300
  Lines                     17843    17863      +20
  Branches                   1862     1862
========================================================
- Hits                       6244     6239       -5
- Misses                    11151    11175      +24
- Partials                    448      449       +1

Flag
Coverage Δ

plugin
34.92% <0.00%> (-0.07%)
:arrow_down:

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

Impacted Files
Coverage Δ

...va/org/opensearch/ad/AnomalyDetectorExtension.java
0.00% <0.00%> (ø)

...a/org/opensearch/ad/model/AnomalyResultBucket.java
74.28% <0.00%> (ø)

...arch/ad/rest/RestSearchTopAnomalyResultAction.java
0.00% <0.00%> (ø)

...ansport/SearchTopAnomalyResultTransportAction.java
3.82% <0.00%> (ø)

... and 1 file with indirect coverage changes

@vibrantvarun addressed your comments here: https://github.com/opensearch-project/anomaly-detection/pull/885


[Bug]: crystaldiskinfo cannot be downloaded and the version is not the latest

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
crystaldiskinfo
Expected/Current Behaviour
^^
Steps to Reproduce
PS> scoop install extras/crystaldiskinfo
WARN  Purging previous failed installation of crystaldiskinfo.
ERROR 'crystaldiskinfo' isn't installed correctly.
Removing older version (9.1.0).
'crystaldiskinfo' was uninstalled.
Installing 'crystaldiskinfo' (9.1.0) [64bit] from extras bucket
INFO  Following redirect to http://osdn.dl.osdn.net/crystaldiskinfo/78950/CrystalDiskInfo9_1_0.zip...
The remote server returned an error: (502) Bad Gateway.
URL https://dotsrc.dl.osdn.net/osdn/crystaldiskinfo/78950/CrystalDiskInfo9_1_0.zip is not valid

Possible Solution
"homepage": "https://osdn.net/projects/crystaldiskinfo/" Do Not Respond
Also, the newest version is (9.1.0) https://crystalmark.info/download/zz/CrystalDiskInfo9_1_1.exe
Scoop and Buckets Version
PS > scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
59dbb1b9a (HEAD -> master, origin/master, origin/HEAD) yuescript: Update to version 0.17.8

'java' bucket:
ea424d80 (HEAD -> master, origin/master, origin/HEAD) temurin8-jre: Update to version 8.0.382-5

'main' bucket:
3c89c14b0 (HEAD -> master, origin/master, origin/HEAD) mongodb-database-tools: Update to version 100.7.4

'nonportable' bucket:
701560e (HEAD -> master, origin/master, origin/HEAD) 10x-np: Update to version 1.0.60

'versions' bucket:
2a59d5f1e (HEAD -> master, origin/master, origin/HEAD) odin-nightly: Update to version 2023-07-21

Scoop Config
PS > scoop config

last_update        scoop_branch scoop_repo
-----------        ------------ ----------
2023/7/22 15:35:41 master       https://github.com/ScoopInstaller/Scoop

PowerShell Version
PS > $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

Installing 'crystaldiskinfo' (9.1.0) [64bit] from extras bucket
INFO  Following redirect to http://osdn.dl.osdn.net/crystaldiskinfo/78950/CrystalDiskInfo9_1_0.zip...
CrystalDiskInfo9_1_0.zip (7.0 MB) [===========================================================================] 100%
Checking hash of CrystalDiskInfo9_1_0.zip ... ok.
Extracting CrystalDiskInfo9_1_0.zip ... done.
Running pre_install script...
Linking D:\scoop\apps\crystaldiskinfo\current => D:\scoop\apps\crystaldiskinfo\9.1.0
Creating shim for 'DiskInfo'.
Creating shortcut for CrystalDiskInfo (DiskInfo64.exe)
Persisting Smart
Persisting DiskInfo.ini
'crystaldiskinfo' (9.1.0) was installed successfully!

'crystaldiskinfo' (9.1.0) was installed successfully , but it took several attempts.
Can you provide an updated version and download URL for 'crystaldiskinfo' (9.1.1)?

https://github.com/ScoopInstaller/Extras/issues/11604#issuecomment-1642507649


💡 [FEATURE] Adding Login/Sign page

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
There is no Login/SignUp page in this project I can add the login/signup page to authenticate users.
Explain your solution
No response
Any alternative approaches/features
Some what like this

Additional Context
No response

@jfmartinz can you assign me this issue with appropriate labels

This is nto needed at the moment


Export Map to PNG

Is there any way to export to png instead of printing? Would be a nice feature to add to a Print / Export menu.

Please use other plugin to export it as PNG, this plugin can only call browser print action for now.

Please use other plugin to export it as PNG, this plugin can only call browser print action for now.

Thanks @Igor-Vladyka, I have used easyPrint.js to get a PNG of the map in the browser for the moment.
One thing I quite like about Browser Print is that I can print a different base map from the one being viewed by the user. At the moment we normally display a simple basemap, but on print we are printing a high quality Sea Map from Transas.
My ideal solution is going to be for the user to select that he wants to print a "Route Report" from the browser, this will send his route (waypoints on the map) to the API controller. The controller will render the map in a headless brower, plot the waypoints on the map and zoom the map so that all waypoints are in view. Create a png of this image and then sent it to jsReports to be included in a PDF report which will be viewed / downloaded by the user.

Current plugin prepares map to print and uses in-browser action for actual printing. You can override actual browser behavior.
Here is more details: download-map-as-image
And full example with added custom action to export image in AUTO mode.
Regards,
Igor


Random sockets not opening

The randomness makes this hard to document, but it seems a httpsocket sometimes get assigned the same number and one of them basically stalls. For the current version of tests, the number of simultaneous sockets has been reduced to alleviate the problem.
This functionality comes from HtttpServer, which currently has some deprecation warnings and may have slower reaction than normally.
Of course, to debug, one needs to temporarily add some logs in HttpServer. But such logging takes more time than just opening a socket and is likely to increase the problem.
It may seem to be less of a problem on cygwin / julia compiled with 8 threads than on the downloaded binary. HttpServer opens sockets as async tasks, not threads or processes.

This was due to blocking asyncronous calls. Servers are still easily overloaded.


Hotfix sync queries

The order of the columns in case of SELECT * and sync queries were depending on the ingestion order of the columns (kind of random).
We correct that in ordering the columns according to the order metadata information.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 64.214%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

daiquiri/query/process.py
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
4712

Relevant Lines:
7338

💛  - Coveralls


melpaBuild: allow nix unstable version format

Before, an unstable version of melpaBuild has to be in MELPA format, which has some disadvantages:

existing update scripts cannot be reused1
it causes inconsistence.

This patch fixes that by allowing an unstable version to be in Nix format.
We heuristically detect if it is an unstable version in Nix format. If so, we convert it to MELPA format.
This does not bring evaluation performance overhead.  Here is my benchmark result using hyperfine-1.18.0 and nix-2.18.1.
Without this patch:
Benchmark 1: NIXPKGS_ALLOW_BROKEN=1 nix eval --include nixpkgs=$PWD --file . emacs.pkgs.melpaPackages --apply 'pkgSet: map (drv: drv.drvPath) (builtins.filter (p: p.type or null == "derivation") (builtins.attrValues pkgSet))' --no-eval-cache >/dev/null
  Time (mean ± σ):      9.126 s ±  0.048 s    [User: 6.531 s, System: 0.997 s]
  Range (min … max):    9.056 s …  9.186 s    10 runs

With this patch applied:
Benchmark 1: NIXPKGS_ALLOW_BROKEN=1 nix eval --include nixpkgs=$PWD --file . emacs.pkgs.melpaPackages --apply 'pkgSet: map (drv: drv.drvPath) (builtins.filter (p: p.type or null == "derivation") (builtins.attrValues pkgSet))' --no-eval-cache >/dev/null
  Time (mean ± σ):      9.124 s ±  0.057 s    [User: 6.522 s, System: 1.011 s]
  Range (min … max):    9.040 s …  9.220 s    10 runs

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I believe this is an extra reason to merge https://github.com/NixOS/nixpkgs/pull/315949 :)

Why is this PR taking so long to land?
https://nixpk.gs/pr-tracker.html?pr=316726

The current PR to update staging-next takes a bit more time than usual.


Location SEEMS to not error, but doesn't return accurate geo. tried to replace with address.city but is 'undefined'

.. Will be addressing this anyway to integrate location finder

Fixed

Logic changed and using Lat Lon. Also faster now.


WIP: Bitmap alpha format support

What does the pull request do?

Skia and D2D backends hardcode alpha formats for bitmaps loaded directly from memory. This PR is trying to fix that by allowing users to provide alpha format.
How was the solution implemented (if it's not obvious)?

Direct2D and Skia backends now require alpha format to be provided when loading bitmaps from memory. Writeable bitmap also accepts alpha formats and will default to premultiplied alpha.
Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Breaking changes

Fixed issues

It seems that GPU-accelerated SKCanvas ignores the alpha-type on bitmaps.

Bug in Skia it seems, after updating to latest SkiaSharp EAP (2.84.0-pr.1321.3 currently) it works correctly.

@MarchingCube any updates? :)

@MarchingCube any updates? :)

I guess until we update Skia we can't merge this in. Or we would need to implement some kind of fallback but I don't like that idea since this is fixed properly in newer Skia.

Waiting for https://github.com/AvaloniaUI/Avalonia/pull/4222.

@kekekeks After updating to new Skia everything works fine. Had to change theme in render demo since I couldn't see sidebar anymore.

@MarchingCube Any way this will be part of 0.10 preview 2? :)

@adirh3 I've updated this PR to latest master and fixed conflicts. Can you actually test it to see if it fixes your problem?

@adirh3 I've updated this PR to latest master and fixed conflicts. Can you actually test it to see if it fixes your problem?

Thanks, just checked and it fixed my issue (#4103) when changed AlphaFormat to Unpremul.

@danwalmsley @kekekeks Updated this PR to remove API break in non-platform interface part. There are still changes in the rendering interface, but this part is pretty much internal so I hope it won't cause problems.


Fix Safari window focus

This PR fixes an issue with Safari by forcing the correct window to the front.
Resolves #4.
Resolves #7.
Resolves #11.

🚀  This has been released with v1.0.4


Guide for Ubuntu headless vps installation?

I want to install this on a remote vps and then use an IP:port to access it in a browser window. Is this possible?

Yes, you can try the self-hosted web version of iptvnator https://github.com/4gray/iptvnator/blob/electron/docker/README.md


Add web development and python course (Farsi/Persian)

What does this PR do?
A new Farsi/Persian course in python section was added.

TIP OF THE DAY: One branch per contribution, especially if it has already been reviewed and marked to be merged


Complete E2E Rest API coverage

Add E2E tests to ensure complete coverage of rest API including webhooks.

Well - full coverage with integration tests and good smoke tests for E2E.  This is done (some gRPC still need to be completed).


Add gcovr generate GCC code coverage reports

Looks good as a starting point.
Next steps:

Fix commented issues
Make automated report in Travis, (ideally which fails if Pull Request decreases percentage of the coverage)

Is it still valid since you add llvmcov?

This commit is closed due to the fact that there is the most suitable tool 'llvm-cov gcov':
https://github.com/Pelagicore/facelift/pull/297


refactor: add null safety

Thank you very much for your work on this package @pepsighan.
I am hoping that it might be possible to release a null safe version.

Awesome, thanks for the PR. The PR changes look good to be merged.

I have pushed the new version at https://pub.dev/packages/mdi/versions/5.0.0-nullsafety.0. Thanks for your effort.

Thank you for pushing up that version, I can confirm that it is working perfectly!

Hi @pepsighan any date when this will be released as stable version?


Replace github.com/appscode/pat with gorilla/mux

Done. https://github.com/kubevault/operator/releases/tag/v0.3.0


Update output transform matrix calculation

Improve transform matrix calculation in wlr_output to help the pixman rendering process.

Breaking change: the projection has been moved from wlr_output.transform_matrix to the GLES2 renderer. Compositors using wlr_output.transform_matrix only with the GLES2 renderer don't need an update.

Got correct results with this: https://l.sr.ht/zxBA.txt

Runs well with rotation, output-layout and fullscreen

Can you squash these two commits, and add the motivation for this change in the commit message?

Done, let me know if you want more info in the commit message.

It seems like this breaks cursors. Applied this patch to the Wayland backend and works again:
https://l.sr.ht/zCxh.txt
Can you do something similar for DRM and X11?

Good catch, I'll make a fix soon.

I squashed the fix into the first commit. Do you think drm_surface_blit could break too?


Fix possible service resource name conflict

When defining an instance the service resource gets the instance name.
While the resulting service is elasticsearch-$name it could happen that the service resource name can conflict with other modules.

test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/1/
Test FAILed.

test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/4/
Test FAILed.

test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/5/
Test FAILed.

test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/6/
Test FAILed.

test this please

test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/7/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/8/
Test FAILed.

test this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://build-eu-00.elasticsearch.org//job/Puppet_Elasticsearch_PR/9/
Test PASSed.


Support default/secure metrics-server installation

As of today, installing metrics-server requires tweaking the configuration since the default is to reach out to nodes by DNS and use TLS. A fair number of users have asked to support the default setup including TLS, which is a highly reasonable request.
The issue has originally been discussed in https://github.com/digitalocean/digitalocean-cloud-controller-manager/issues/150. Several comments describe how to run metrics-server in TLS-less mode as a workaround for now.

I just set up the metrics-server with the components.yaml from the v0.3.6 release and made sure to inject the --kubelet-preferred-address-types=InternalIP flag as mentioned here. (Using kustomize and a JSON patch for this)
Everything seems to be running just fine and I get no errors. With kubectl top node i see some metrics. However I see no change in the DOKS dashboard as suggested in official dashboard docs:

This is my view instead:

Am I missing something?

@mbrodala is this the dashboard we integrate in the DigitalOcean cloud control panel, or a separate deployment you manage on your own?

@timoreimann this is the original dashboard provided by DOKS.

@mbrodala this may indeed be an issue on our end. I filed an internal bug report so that we can look into the matter more closely.
Thanks for bringing this to our attention. I'm going to report back to this issue once we've identified and fixed the problem.

@timoreimann Any news on this?
I'm also facing the exact same issue - metrics server works properly (with the mentioned modifications) & I can see the stats using the top command, but the (built-in) dashboard isn't showing them in the UI.

The dashboard metrics are served by a different, separate sidecar, which we yet have to integrate. I created #21 to track the effort.

I installed metrics-server with doctl kubernetes cluster create --1-clicks="metrics-server" .... When I run kubectl top pods --all-namespaces I get:
W1031 04:06:49.790056 1123183 top_pod.go:265] Metrics not available for pod default/external-dns-68cf9b5c56-4bjqs, age: 40m32.790034709s
error: Metrics not available for pod default/external-dns-68cf9b5c56-8bjqs, age: 40m32.790034709s

The metrics pod logs something like this:
I1031 03:03:25.598399       1 manager.go:148] ScrapeMetrics: time: 5.606118ms, nodes: 1, pods: 0
E1031 03:03:26.647337       1 reststorage.go:160] unable to fetch pod metrics for pod cert-manager/cert-manager-cainjector-6d59c8d4f7-7l274: no metrics known for pod
E1031 03:03:26.647589       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/cilium-operator-6cb976fbcf-rc8lv: no metrics known for pod
E1031 03:03:26.647701       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/cilium-rl67k: no metrics known for pod
E1031 03:03:26.647793       1 reststorage.go:160] unable to fetch pod metrics for pod cert-manager/cert-manager-webhook-578954cdd-9vwph: no metrics known for pod
E1031 03:03:26.647843       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/kube-proxy-4f2vb: no metrics known for pod
E1031 03:03:26.647900       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/coredns-76bcfddf46-rkfvt: no metrics known for pod
E1031 03:03:26.647957       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/do-node-agent-wx74s: no metrics known for pod
E1031 03:03:26.648048       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/csi-do-node-skgr8: no metrics known for pod
E1031 03:03:26.648137       1 reststorage.go:160] unable to fetch pod metrics for pod default/external-dns-68cf9b5c56-8bjqs: no metrics known for pod
E1031 03:03:26.648196       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/cilium-operator-6cb976fbcf-z5vmk: no metrics known for pod
E1031 03:03:26.648288       1 reststorage.go:160] unable to fetch pod metrics for pod cert-manager/cert-manager-86548b886-j655n: no metrics known for pod
E1031 03:03:26.648387       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/coredns-76bcfddf46-lsvm5: no metrics known for pod
E1031 03:03:26.648433       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/metrics-server-5b8f47666-m6sn5: no metrics known for pod
E1031 03:03:26.648487       1 reststorage.go:160] unable to fetch pod metrics for pod kube-system/kube-state-metrics-6f4b6669f9-zhgw2: no metrics known for pod
E1031 03:03:26.648544       1 reststorage.go:160] unable to fetch pod metrics for pod ingress-nginx/ingress-nginx-controller-98cb87fb7-bfvvr: no metrics known for pod

@feluxe  I have just the same issue with you

@feluxe @johnwook and I have the same issue as you guys too.

1.19 users are presumably affected by an incompatibility with Docker 18 as described in kubernetes/kubernetes#94281.
We plan to release a DOKS 1.19 update (ideally today) that is going to address the problem by moving to Docker 19.03.

@timoreimann as a 1.19 user I can confirm I'm affected by that (or something else) and currently don't have pod metrics through metrics-server

FYI:
1.19.3-do.2 was just released and should fix the problem. Please report back if that's not the case.
Originally posted by @timoreimann in https://github.com/digitalocean/digitalocean-cloud-controller-manager/issues/150#issuecomment-722604873
Can confirm this is now fixed for me

Same here. kubectl top ... works with the new update, but the stats still don't show within the dashboard web UI.

the stats still don't show within the dashboard web UI.

Unfortunately, that's unrelated to the latest release. It's still on the agenda to get it fixed as well.

Hi this is still biting me on 1,22. I have to change the endpoints to be InternalIP and enable the apiService


Test macos installation

This PR adds logic to test @sandeep-krishnamurthy's python installation guide for MacOS CPU on Travis.
We test the installation in a clean environment via pip, virtualenv, and from source.

can you please add a little bit context here? do you want to test all the installation on travis? how many time will it cost? my concern is that our travis testing is pretty slow so we'd like not to add heavy tasks to it.

@mli yes, sure.
There are two tasks that I've added to Travis as shown in the .travis.yml file:

installation_packaged_test

Tests instructions for installing MXNet via either 1) virtualenv 2) pip
Runs a simple Python sanity test (create NDArray)
Takes 2 minutes

installation_source_test

Tests instructions for installing MXNet from source
Runs a simple Python sanity test (create NDArray)
Takes 16 minutes
Needed to be put in a second task because it needs a clean environment

A successful run can be viewed here: https://travis-ci.org/lxn2/mxnet/builds/231756599
We did consider that it might cause Travis runs to be slower too, but testing installation instructions was high priority for v0.10 release and that's why we committed time to it.

Perhaps I can add to the following file to check whether the install.md guide has changed. If it has changed, we run the task. If not, we skip? Although I notice we've disabled this check...
https://github.com/dmlc/mxnet/blob/master/tests/travis/is_core_changed.sh

@lxn2 @mli @sandeep-krishnamurthy I vote for making the macOS build automation as a nightly test and not something that runs for every code submission.

Closing temporarily.

I added logic to run installation tasks only if the diff between this branch and the mxnet's master branch contains install.md.
Note the installation_source_test task fails in Travis because my changes to install-mxnet-osx-python.sh needs to be merged.
Also @mli the Jenkins server couldn't clone this repo for some reason...can you help retrigger the build?

i don't know jenkins failed to clone this pr, maybe due to there is too many commits. but it seems to be fixed now

Yes I think it's a known issue with git pull request builder.

Why are we testing pip install here? Shouldn't it be tested in mxnet-distro? That's the place that's creating the pip packages.

@piiswrong This tests the installation instructions to make sure that the guide works. The testing in mxnet-distro needs to happen too, but that is a separate in-progress item.

pip install depends on the pip package which is not in this repo. Putting it here can cause test fails without changes in mxnet repo. These tests should be moved into mxnet-distro
source install tests can be here.

I advocate to push this in because

this should on run if there is a change to install.md installation guide
we're in progress of moving mxnet-distro into mxnet anyway @szha

I've added the tests in mxnet-distro for the immediate release.
Eric has a point that having external dependencies for tests is bad and unless we mock the dependencies there isn't a way around it. Also, adding a test for pip install mxnet doesn't help much anyways. Ly, see if you could find a way to mock the invocation of commands, or come up with a better way, or exclude the pip command from doc tests.


Directory.Move fails when a directory with different case already exists

Here is a unit test that reproduces the issue.
`
[Test]
public void Move_DirectoryExistsWithDifferentCase_DirectorySuccessfullyMoved()
{
// Arrange
var fileSystem = new MockFileSystem();
<EMAIL_ADDRESS>[6.2.3 135907]\TestShellHotFix\Data"); // HotFix with capital F
fileSystem.AddFile(     @"\builds\Builds\Suites\<IP_ADDRESS>9 [6.2.3 135907]\TestShellHotfix\Data\Content\DriverBuilder\ActiproSoftware.Navigation.Wpf.dll", new MockFileData("abc"));
        // Act
<EMAIL_ADDRESS>[6.2.3 135907]\TestShellHotfix", // HotFix with lower f
                @"\\builds\Builds\Suites\<IP_ADDRESS>9 [6.2.3 135907]\Hotfix1 for CloudShell 6.2.3 GA [<IP_ADDRESS>]");

        // Assert
        Assert.IsTrue(
<EMAIL_ADDRESS>[6.2.3 135907]\Hotfix1 for CloudShell 6.2.3 GA [<IP_ADDRESS>]\Data\Content\DriverBuilder\ActiproSoftware.Navigation.Wpf.dll"));
    }

`

Can we get a unit test that doesnt have so much specificity?  The paths you
have there are very specific, since you're testing for case, just create a
unit test where the directory name is C:\CaseSensitiveTest (for example).
On Wed, Jul 8, 2015 at 7:33 AM, Boris Modylevsky<EMAIL_ADDRESS>wrote:

Here is a unit test that reproduces the issue.
`
[Test]
public void
Move_DirectoryExistsWithDifferentCase_DirectorySuccessfullyMoved()
{
// Arrange
var fileSystem = new MockFileSystem();
<EMAIL_ADDRESS>[6.2.3
135907]\TestShellHotFix\Data"); // HotFix with capital F
fileSystem.AddFile( @"\builds\Builds\Suites\<IP_ADDRESS>9 [6.2.3
135907]\TestShellHotfix\Data\Content\DriverBuilder\ActiproSoftware.Navigation.Wpf.dll",
new MockFileData("abc"));
    // Act
<EMAIL_ADDRESS>[6.2.3 135907]\TestShellHotfix", // HotFix with lower f
            @"\\builds\Builds\Suites\<IP_ADDRESS>9 [6.2.3 135907]\Hotfix1 for CloudShell 6.2.3 GA [<IP_ADDRESS>]");

    // Assert
    Assert.IsTrue(
<EMAIL_ADDRESS>[6.2.3 135907]\Hotfix1 for CloudShell 6.2.3 GA [<IP_ADDRESS>]\Data\Content\DriverBuilder\ActiproSoftware.Navigation.Wpf.dll"));
}

`
—
Reply to this email directly or view it on GitHub
https://github.com/tathamoddie/System.IO.Abstractions/issues/134.

@ericnewton76 Test was changed to be less specific. Can you review and accept the PR?
Thanks!

Fixed by #135


add feature to download the html version of a document

Can we introduce a feature to be able to download the html in it´s latest version before it is printed to a pdf by weasyprint? This feature would be helpfull when debugging complex Jinja-templates (after processing the markdown-variables) in combination with stylesheets.
FYI: I assume that https://github.com/desklab/doku-styles/issues/9 is caused by an additional html element introduced by the way we convert the variables and would like to check the 'final' html.

You can now append /html to the url when editing a document. Similar to /render, this will return the HTML output of the Jinja Template. Should be only used for debugging purposes and is thus not available from the UI.

You can now append /html to the url when editing a document. Similar to /render, this will return the HTML output of the Jinja Template. Should be only used for debugging purposes and is thus not available from the UI.

Example:
https://doku.desk-lab.de/document/83/html

Example:
https://doku.desk-lab.de/document/83/html

Note that this is before resolving any URLs. Resources such as SVGs will be placed by WeasyPrint and are thus not available at this point.

Note that this is before resolving any URLs. Resources such as SVGs will be placed by WeasyPrint and are thus not available at this point.


LEDVANCE Wifi SMART+ Planon Frameless LED RGBW 30x30 3000-6500K

Trying to get this "lamp" offline into a localtuya/minituya. The existing LEDVANCE exploit works up until the point where it attempts to query h3.iot-dns.com and fails with a generic SSL Error.
Since I plan on moving these lamps to not-important rooms anyway, is there any way I can help with getting these exploited? I can probably disassemble one of them for a dump, assuming I can find the necessary dumping tools in stock anywhere.

If you have the device already connected to Smart Life, can you provide the version listed under "device update" in the Smart Life app?

Sorry for the late reply, I ended up throwing these away due to an automatic firmware update turning red into purple, purple into purple, blue into yellow, and yellow into green. I can dig them out of the e-waste pile, though i probably won't be able to connect them to proper 230V power.

Closing as stale.  Re-open if you decide to try the devices again.