Documentation does not say anything about LARAMETRICS_FROM_EMAIL

I've just updated the project and got +7k errors because of the new default FROM email that is<EMAIL_ADDRESS>and I don't have this email registered in my SES account as a sender.
Searching in the code I've found that now I can customize the sender email using the env variable LARAMETRICS_FROM_EMAIL. I couldn't find anything about it in the documentation.
Besides that, I think it should be a config and not just an env variable.

If it is not in the config file it won't work in the production file. I've just had to disable the email notifications because it was still trying to send via<EMAIL_ADDRESS>even after changing the .env and clearing the config cache.

I've added several references to possible .env values that you can set for the email sending functionality. You can view them on the main package's readme, or on this page of the docs: https://larametrics.com/docs/config-reference.html


x/tools/cmd/goimports: adds unexpected renamed imports

Three mysterious problems here (running in GOPATH mode):
$ go get -u golang.org/x/tools/cmd/goimports
$ echo 'package p; var _ = f.hash' | goimports
package p

import f "golang.org/x/exp/winfsnotify"

var _ = f.hash
$

goimports should not be trying to find an import for f.hash at all.
No import could possibly provide a lower-case name.
goimports should not be wasting time scanning packages at all.

Even if goimports were to look for a package,
why on earth did it decide to import golang.org/x/exp/winfsnotify to f?
(That package is package winfsnotify.)

Even if goimports were to look for a package and rename it to f,
why did it pick golang.org/x/exp/winfsnotify? That package does not
contain the string hash anywhere in its sources.

Like I said, mysterious (and really very annoying).
/cc @heschik @ianthehat @bradfitz

Pretty funny bug, I couldn't quite believe it so I had to look. I think this is partly new in my rewritten code and partly old.
The example hits two corner cases in the goimports logic. First, the code that collects missing references knows that lower-case identifiers can't be exported by a package, so it doesn't add them as things to look for -- but it does that after it has registered that it's looking for a package named f. Now it's looking for f, and it doesn't have to export anything.
So then it goes looking for 'f'.  As it does that it tries to check the package statement of each file, and if it finds one that doesn't match, rejects the package as mismatched. But winfsnotify is for Windows, and all of its files are build tagged as such. So it never finds a package statement to check. Normally that wouldn't matter since it also didn't find anything exported. Here, though, it's good enough.
Both should be easy fixes.


Spyder 5.5.2 crashes with RuntimeError: wrapped C/C++ object of type SpyderKernelManager has been deleted

Problem Description
Spyder 5.5.2 crashes when attempting to access any main menu item.
What steps reproduce the problem?

Open Spyder
Graphical IDE loads fine.
Click on any menu, or any menu item such as  "File>>Open" . Spyder crashes with the message below.

This reproduces the crash identically every time.
What is the expected output? What do you see instead?
The entire IDE is crashing to command line.
Paste Traceback/Error Below (if applicable)
fromIccProfile: failed minimal tag size sanity
Traceback (most recent call last):
  File "/home/xpswhite/cfpga/cfpga_venv/bin/spyder", line 8, in <module>
    sys.exit(main())
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/app/start.py", line 256, in main
    mainwindow.main(options, args)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 1847, in main
    mainwindow = create_window(MainWindow, app, splash, options, args)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/app/utils.py", line 300, in create_window
    main.post_visible_setup()
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/app/mainwindow.py", line 1050, in post_visible_setup
    plugin.on_mainwindow_visible()
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/plugins/ipythonconsole/plugin.py", line 401, in on_mainwindow_visible
    self.create_new_client(give_focus=False)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/plugins/ipythonconsole/plugin.py", line 538, in create_new_client
    self.get_widget().create_new_client(
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/plugins/ipythonconsole/widgets/main_widget.py", line 1522, in create_new_client
    self.connect_client_to_kernel(client, km, kc)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/spyder/plugins/ipythonconsole/widgets/main_widget.py", line 1792, in connect_client_to_kernel
    kc.start_channels(shell=True, iopub=True)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/qtconsole/kernel_mixins.py", line 47, in start_channels
    super().start_channels(*args, **kw)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/jupyter_client/threaded.py", line 319, in start_channels
    self.shell_channel._inspect = self._check_kernel_info_reply
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/jupyter_client/client.py", line 352, in shell_channel
    self._shell_channel = self.shell_channel_class(socket, self.session, self.ioloop)
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/jupyter_client/threaded.py", line 73, in __init__
    f.result(timeout=10)
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 446, in result
    raise TimeoutError()
concurrent.futures._base.TimeoutError
Exception ignored in: <function KernelManager.__del__ at 0x7fdc98d833a0>
Traceback (most recent call last):
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/jupyter_client/manager.py", line 217, in __del__
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/jupyter_client/manager.py", line 336, in _close_control_socket
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/traitlets/traitlets.py", line 732, in __set__
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/traitlets/traitlets.py", line 721, in set
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/traitlets/traitlets.py", line 1505, in _notify_trait
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/traitlets/traitlets.py", line 1517, in notify_change
  File "/home/xpswhite/cfpga/cfpga_venv/lib/python3.8/site-packages/traitlets/traitlets.py", line 1540, in _notify_observers
RuntimeError: wrapped C/C++ object of type SpyderKernelManager has been deleted

Versions

Spyder version:  5.5.2
Python version:  3.8.18
QtAwesome  1.2.3
QtPy  2.4.1
PyQt5                         5.15.10
PyQt5-Qt5                     5.15.2
PyQt5-sip                     12.13.0
PyQtWebEngine-Qt5             5.15.2
Operating System name/version:  Ubuntu 22.04.1 jammy x86_64 x86_64 x86_64 GNU/Linux
Operating System Kernel: 6.5.0-25-generic
Operating System GUI : KDE Plasma Version 5.24.7

Dependencies
PyOpenGL                      3.1.7
qtconsole                     5.5.1
rope                          1.12.0
jedi                          0.18.2
pyflakes                      3.2.0
Sphinx                        7.1.2
Pygments                      2.15.1
pylint                        3.0.4
pycodestyle                   2.11.1
psutil                        5.9.5
nbconvert                     7.16.2
QtAwesome                     1.2.3
pickleshare                   0.7.5
pyzmq                         25.0.2
QtPy                          2.4.1
chardet                       5.2.0
numpydoc                      1.6.0
cloudpickle                   2.2.1

Hey @moschles, thanks for reporting. It seems you're mixing your Linux distro Python packages with the ones installed from PyPI in your venv, which could be the cause of this problem.
To avoid it, please remove that venv and install Spyder in a clean virtualenv, as described in our documentation:
http://docs.spyder-ide.org/current/installation.html#using-pip
Let us know if that works for you.

@ccordoba12    Thank you for the response.  Unfortunately, that virtual environment is absolutely required for a large framework within Matlab, Simulink, and a 3rd-party python library that interops with those two.   I am not the creator or maintainer of that venv, and it uses path variables that are initialized by their own scripts.   Since I require Spyder solely for the purposes of using that framework , there is no point in me playing around with freshly-created  virtual environments for no other purpose than to get Spyder working.

@ccordoba12  I have working 5.5.3 now, as per your directions.   One extra step was required after installation.
spyder --reset

That enabled the IPython Console .

Great! I'm glad you're able to use Spyder now.


xcode 8 and swift 3.0 support

HEAD on master is able to run on xcode8 with swift3 but not released yet

0.1.6 is released. closed


Telemetry for installing recommended extensions

This PR adds an event to track if the "Install" button on a recommended extension is clicked by the user.
I am piggy backing on the Extensions payload. Couldn't find any other way to pass the information that the extension is recommended all the way to ExtensionAction.ts. Suggestions are welcome.
In the future we will properties to denote the source of the recommendation as well.
cc @kieferrm

Somehow this PR got closed and I can't re-open it!!

No worries.. I see we can ignore this PR as I do not see any changes.


Add 'namespace' parameter support to LowNodeUtilization strategy

Hello.
I think that would be great if 'namespace' parameter is supported with LowNodeUtilization strategy.

@korjek thanks for opening this issue. I'm assuming you are referring to the namespace filtering feature that was just added in the v0.19.0 release.
When the namespace filtering enhancement was initially discussed it was determined that it would not make sense to enable this for all descheduler strategies. For example for the LowNodeUtilization strategy to be effective it needs to be able to process as many nodes as possible.
Can you provide any additional details on your use case?

@korjek are the pods running in this namespace running on a different set of nodes? Could you maybe filter using a node selector?

@seanmalloy no, they are using the same nodes pool.
But what's the reason to do not have namespace filtering for LowNodeUtilization strategy?

LowNodeUtilization needs to consider as many pods as possible to accurately calculate each node's resource consumption. Only considering a subset of these for eviction would hurt its effectiveness at balancing cluster resource usage.
Can you give some more details on what your use case is? Perhaps there is another approach with the scheduler/descheduler that would fit better

@damemi but why the descheduler needs to calculate node's resource consumptions if that info is available from node's status?
How I see this: when LowNodeUtilization strategy generates a list of pods for eviction it should take into account namespace filtering (ie when evaluating pods for eviction, skip pods that are filtered by namespace).  The rest of the logic shouldn't be changed.
Here is my usecase https://github.com/kubernetes-sigs/descheduler/issues/391#issuecomment-687212687

If you limit the pods that are available for eviction with LowNodeUtilization, the strategy won't work very well. The point of it is to balance entire node usage, so unless the namespace you're restricting it to makes up a large portion of your cluster's consumption then there isn't much point to running this strategy in this namespace.
By your use case, I meant why do you specifically want to run LowNodeUtilization in one namespace? I understand that you want to restrict evictions to certain idempotent pods, but are you just trying to keep these pods spread out between nodes?
If we can know your end goal with this strategy, we can better determine if this is a real use case or if something else is more appropriate (like Pod Topology Spreading or RemoveDuplicates)

Our usecase is that we have a separate namespace where idempotent to restart pods are running. So the idea with using namespace filtering with LowNodeUtilization strategy is that Descheduler will evict pods only from that specific namespace.

IIUC, the specific namespace is like a bank of pods to be sacrificed when certain nodes starts to be overutilized. Assuming what you are asking for is implemented, in case no pod from the specific namespace runs on any of the overutlized nodes, the strategy will have no effect. More or less the same hold if a small fraction of pods from the namespace runs on the overutilized nodes (debatable, yet depending on a particular use case).
I can see how it aligns with LowNodeUtilization strategy though unless the bank of pods are concentrated around overutilized nodes, I don't see any other benefit. I can see the case where a set of nodes have a main application (each). Each main application concentrates a bank of workers (in the specific namespace). In case the worker pods start to eat too much cpu/memory (upper bounded by resource limits), nodes can get overutlized in which case it makes sense to reschedule/evict only some of the worker pods from the bank. Is this the use case close enough?

@damemi
Yes, these pods are the biggest portion of node's usage (~90% of all cluster).
Of course I can go and update PriorityClass for pods in this namespace or pods on other namespaces (or both at the same time) and use PriorityClass filter. But using namespace filtering requires less effort in this case.

IIUC, the specific namespace is like a bank of pods to be sacrificed when certain nodes starts to be overutilized. Assuming what you are asking for is implemented, in case no pod from the specific namespace runs on any of the overutlized nodes, the strategy will have no effect. More or less the same holds if a small fraction of pods from the namespace runs on the overutilized nodes (debatable, yet depending on a particular use case).

But that's actual for PriorityClass filtering too: if all pods except a small amount are using higher PriorityClass than specified using PriorityClass filter, strategy will have no effect.

I can see how it aligns with LowNodeUtilization strategy though unless the bank of pods are concentrated around overutilized nodes, I don't see any other benefit. I can see the case where a set of nodes have a main application (each). Each main application concentrates a bank of workers on the same node (in the specific namespace). In case the worker pods start to eat too much cpu/memory (upper bounded by resource limits), nodes can get overutlized in which case it makes sense to reschedule/evict only some of the worker pods from the bank. @korjek Is this use case close enough?

Almost. The main load (~90%) are caused by pods running in one namespace. So once AWS reclaims node, other nodes become really overloaded.
As I relied to @damemi , I can handle my case using PriorityClass filter, but it will require more changes from my side.

The main load (~90%) are caused by pods running in one namespace. So once AWS reclaims node, other nodes become really overloaded.

This is the key here, and I think it's a legitimate use case. Ultimately there isn't much "risk" with enabling namespace filtering for this strategy, the only risk is that if used improperly it will hurt the strategy's effectiveness (or maybe cause it to hotloop/run every iteration with no results but we could probably get around this by only listing the viable pods when calculating usage). If we do enable this, those outcomes should be clearly noted in the docs that it is not normally recommended to run this strategy with namespace filtering.
@seanmalloy @ingvagabund wdyt?

The main load (~90%) are caused by pods running in one namespace. So once AWS reclaims node, other nodes become really overloaded.

This is the key here, and I think it's a legitimate use case. Ultimately there isn't much "risk" with enabling namespace filtering for this strategy, the only risk is that if used improperly it will hurt the strategy's effectiveness (or maybe cause it to hotloop/run every iteration with no results but we could probably get around this by only listing the viable pods when calculating usage). If we do enable this, those outcomes should be clearly noted in the docs that it is not normally recommended to run this strategy with namespace filtering.
@seanmalloy @ingvagabund wdyt?

@damemi I'm fine with this as long as it is clearly documented.

Semantics of filtering namespaces through Namespaces field here is different from other cases. The expected semantics is filter pods and then run strategies. In this case it's run a strategy and then filter pods. I am inclined to introduce a new field, e.g. EvictableNamespaces to distinguish the difference and have it "only" include namespace without excluding.

I'll not sure this requires a new field, it would probably be sufficient to document the difference because it's just for one strategy.

because it's just for one strategy.

two, once HighNodeUtilization strategy gets implemented

This strategy is different as it's a strategy for Node, I think Namespace parameter in this strategy can only be understood as EvictableNamespaces(so we needn't a new parameter), because node's utilization is a property of Node, and filtering pods shouldn't change this property, Namespace parameter here can only be used to limit the scope of evictable pods. We can mention this in README to prevent misunderstanding.

Nobody reads a documentation unless it's really needed. I will not argue against reusing Namespaces field. Just wanted to voice my concerns.

/remove-lifecycle rotten

/remove-lifecycle rotten

I was fooled by this too. I assumed the filter to let me have some namespaces to be untouched by descheduler, but that's clearly not the case.

I was fooled by this too. I assumed the filter to let me have some namespaces to be untouched by descheduler, but that's clearly not the case.

I think that adding a top-level setting for excluding namespaces is a valid request. In OpenShift, we currently have our operator manually append system namespaces to each strategy's exclude list and a cluster-wide setting would be more convenient.
I also think that excluding namespaces from LowNodeUtilization has (a) more utility and (b) less risk as opposed to the includeNamespaces for it. So, I have no problem excluding namespaces from LNU with a clear note that using it too broadly can have negative effects on the strategy.

LowNodeUtilization filters through the namespace, which does not affect applications in other namespaces. If the entire cluster is used, production applications will be unavailable.

+1 for allowing to set a list of excluded namespaces only yet clearly expressing risks of misusing it. Also stressing the setting applies in eviction phase only.
The strategy evicts pods in order to move pods from overutilized nodes to underutilized ordering pods from the least priority to the most. In case the list of excluded namespaces is configured improperly, some of the least priority pods might stay and pods with higher priority might get evicted instead. Which still improves resource usage among nodes, though not always respecting the priority. Description of LowNodeUtilization strategy does not mention the priority ordering is respected during eviction. Worth mentioning what behavior each strategy actually guarantees.

/reopen

/reopen


PhaseEncodingDirection  of EPI

I am trying to run preprocessing of some 7T data with fieldmap distortion correction. The data was collected in sagittal slices.
Data acquisition sequence is : Saggital > Coronal > Transversal
Sagittal R >> L
Coronal A >> P
Transversal F >> H
I am using dicm2niix to convert my dicoms to NIFTI. In the .json file, I am getting the PhaseEncodingDirection for my functional scan as “i”. In saggital slices, "i" should be A>P direction.
However, in the fmriprep output HTML, I see that the phase-encoding direction of the EPI is specified as ""LEFT-RIGHT". Because of this the fieldmap distortion correction is also being applied in the LEFT-RIGHT direction.
Is this an error with fmriprep? I have tried changing the phase encoding direction in the .json file to "j" and fmriprep detects the direction to be Anterior-Posterior as expected.

Can you provide the fslhd of your file?

sizeof_hdr     348
data_type      INT16
dim0           4
dim1           162
dim2           218
dim3           126
dim4           250
dim5           1
dim6           1
dim7           1
vox_units      mm
time_units     s
datatype       4
nbyper         2
bitpix         16
pixdim0        0.000000
pixdim1        1.100917
pixdim2        1.100917
pixdim3        1.100000
pixdim4        2.690000
pixdim5        0.000000
pixdim6        0.000000
pixdim7        0.000000
vox_offset     352
cal_max        0.0000
cal_min        0.0000
scl_slope      1.000000
scl_inter      0.000000
phase_dim      1
freq_dim       2
slice_dim      3
slice_name     Unknown
slice_code     0
slice_start    0
slice_end      0
slice_duration 0.000000
time_offset    0.000000
intent         Unknown
intent_code    0
intent_name
intent_p1      0.000000
intent_p2      0.000000
intent_p3      0.000000
qform_name     Scanner Anat
qform_code     1
qto_xyz:1      0.000000  0.000000  -1.100000  68.750000
qto_xyz:2      -1.100917  0.000000  0.000000  97.043587
qto_xyz:3      0.000000  1.100917  0.000000  -135.242950
qto_xyz:4      0.000000  0.000000  0.000000  1.000000
qform_xorient  Anterior-to-Posterior
qform_yorient  Inferior-to-Superior
qform_zorient  Right-to-Left
sform_name     Scanner Anat
sform_code     1
sto_xyz:1      0.000000  0.000000  -1.100000  68.750000
sto_xyz:2      -1.100917  0.000000  0.000000  97.043587
sto_xyz:3      0.000000  1.100917  0.000000  -135.242950
sto_xyz:4      0.000000  0.000000  0.000000  1.000000
sform_xorient  Anterior-to-Posterior
sform_yorient  Inferior-to-Superior
sform_zorient  Right-to-Left
file_type      NIFTI-1+
file_code      1
descrip        TE=29;Time=115439.485;phase=1;mb=3
aux_file

Can you provide the fslhd (or header readout from any tool, really) of your file?

Here you go, thanks

So your orientation is PSL, so "i" is A->P, so the inputs look good. When we report it, we use the function get_world_pedir:
https://github.com/nipreps/fmriprep/blob/4961a56fa61884304c477403c68d7608e29efb33/fmriprep/interfaces/reports.py#L277-L298
Which seems to give the right result:
>>> from fmriprep.interfaces.reports import get_world_pedir
>>> get_world_pedir("PSL", "i")
'Anterior-Posterior'

So it seems we must be either providing an incorrect orientation or reorienting your input file without adjusting the PhaseEncodingDirection to match.

Do you have single-band reference images that are in a different orientation to your BOLD?

Do you have single-band reference images that are in a different orientation to your BOLD?

No, I do not have any single-band reference files in my folder.
Interestingly, when I used the different phase-encoded fieldmaps (AP / AP), the fieldmap correction seems to work in the right direction (even though the HTML reports the PhaseEncodingDirection as L-R). When I use the Phase-Magnitude pair fieldmap, however, distortion correction is applied in the L-R direction.
Of note, when I use FSL, I do have to input unwarpdir= x- in FUGUE to get distortion correction in the AP direction.

Is there any chance you could provide a minimal dataset that reproduces? e.g., One subject, with one T1w and one BOLD image, and whatever necessary fieldmap data?

Is there any chance you could provide a minimal dataset that reproduces? e.g., One subject, with one T1w and one BOLD image, and whatever necessary fieldmap data?

Of course, here you go: https://www.dropbox.com/sh/ardkp6myddlgt8c/AAAuKb7TWkLaWc0d6NMGIgpMa?dl=0
Thanks a lot.

Please note, this only has the Phase-magnitude pair fieldmap.

Thanks. That should be enough to reproduce the issues you've described.

@Avijit-Chowdhury1 When I run fMRIPrep 21.0.0rc0 on the data you provided, I see the following functional summary:

Summary

Original orientation: PSL
Repetition time (TR): 2.69s
Phase-encoding (PE) direction: Anterior-Posterior
Single-echo EPI sequence.
Slice timing correction: Applied
Susceptibility distortion correction: FMB (fieldmap-based) - phase-difference map
Registration: FSL flirt with boundary-based registration (BBR) metric - 6 dof
Non-steady-state volumes: 0

And looking at the report, the SDC occurs in the A/P direction. Could you verify you were using a new working directory, and share your command and version?

Hi, it might have something to do with my fmriprep version. When I run
python -m pip install --user --upgrade fmriprep-docker
the version installed is fmriprep-docker-20.2.3. How do I install the latest version?

Add the --pre flag to get the release candidate.

crash-20210922-194243-root-ds_t1w_ref_xfms-997633b9-e43b-4a3c-9230-722ced4e4686.txt
I get the following error when trying to run fMRIPrep 21.0.0rc0

Is that a reliable error? It looks like a filesystem issue, which are often pretty stochastic.

Is that a reliable error? It looks like a filesystem issue, which are often pretty stochastic.

I tried again and it works now. The distortion correction is also being applied in the correction direction. Guess this is an issue with the older version of fmriprep?
Also a follow-up question: If I put both types of fieldmaps in my BIDS folder (opposite phase-encoded EPI and Phase-magnitude pair), will the distortion correction be done twice?

I tried again and it works now. The distortion correction is also being applied in the correct direction. Guess this is an issue with the older version of fmriprep?

Probably. 21.0.0 saw a complete overhaul of SDC correction.

If I put both types of fieldmaps in my BIDS folder (opposite phase-encoded EPI and Phase-magnitude pair), will the distortion correction be done twice?

No. If IntendedFor is set for both, then phase difference fieldmaps will take priority over PE-polar. If you want to choose among them, the easier thing would be to move to B0FieldIdentifier/B0FieldSource, so that you're changing the metadata on the BOLD files rather than on the fieldmaps.

I tried again and it works now. The distortion correction is also being applied in the correct direction. Guess this is an issue with the older version of fmriprep?

Probably. 21.0.0 saw a complete overhaul of SDC correction.

If I put both types of fieldmaps in my BIDS folder (opposite phase-encoded EPI and Phase-magnitude pair), will the distortion correction be done twice?

No. If IntendedFor is set for both, then phase difference fieldmaps will take priority over PE-polar. If you want to choose among them, the easier thing would be to move to B0FieldIdentifier/B0FieldSource, so that you're changing the metadata on the BOLD files rather than on the fieldmaps.

https://fmriprep.org/en/1.0.1/api/index.html#sdc-base
.
this link says PE-polar will take priority over phase-diff fieldmaps.

The order of priority has changed in 21.0. Unfortunately, I'm not finding up-to-date documentation. I'll make an issue for that.


Adding defaultHeader method

Hi! This PR allows to set default headers to every response.
closes #3

Nice work, @gabteles! Do you think you can also implement this in the Scala module?

@gabfssilva I'll try to!

Nice! I guess you should change three things:

Use the implicit asScala/asJava instead of other methods, it is easier. Instead of:

mapAsJavaMap(map)

Do:
map.asJava

You just need to use this import:
import scala.collections.JavaConverters._

Since defaultHeaders is a global variable, you don't need to pass it into handle method.

Instead of:
def handle(path: String, produces: String, method: String, matcher: Function[ScalaDslRequest, Boolean], handler: Function[ScalaDslRequest, Future[_ >: Any]], defaultHeaders: Map[String, String])(implicit ec: ExecutionContext): Unit

You could go back to
+  def handle(path: String, produces: String, method: String, matcher: Function[ScalaDslRequest, Boolean], handler: Function[ScalaDslRequest, Future[_ >: Any]])(implicit ec: ExecutionContext): Unit

And use the global variable inside the method:
(...)
addHandler(new RequestHandler(method, path, produces, javaFunc, javaMatcher, defaultHeaders.asJava))

You should do the same in Java version (org.geryon.Http)

Also, de defaultHeader method should receive a Tuple[String, String] instead of two parameters:

def defaultHeader(header: (String, String)): Unit = {
  val (name, value) = header
  HttpServerHandler.defaultHeaders(name) = value
}

If you want to set a defaultHeader:
defaultHeader("X-Powered-By" -> "Geryon")

I guess after that it'd be okay to merge. Thanks again! ;)

@gabfssilva, i've fixed the issues you pointed, thanks for the code review.
I also did some refact of the generation of responses in RequestDispatcher, to improve legibility a bit.

Merged, thanks!


Consider using AutoValue for all result classes

I would like to be able to log the result objects. Implementing toString for each object may become cumbersome to maintain in the future, so AutoValue seams like a good fit here.
For FingerprintDecyptionResult auto-value-redacted can be used to avoid leacage of sensetive data in logs.

Yep, that might make sense. I don't expect it to raise the method count by much so it's something to consider.

I'll make a PR then later today.


Set service port for github deployment

Description :sparkles:
Issues :bug:
Closes :no_good_woman:
DEV-XXX:
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr291.dev.hel.ninja :rocket::rocket::rocket:

Codecov Report

Merging #291 (db87fc8) into master (d356fbd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head db87fc8 differs from pull request most recent head bdd4bea. Consider uploading reports for the commit bdd4bea to get more accurate results

@@           Coverage Diff           @@
##           master     #291   +/-   ##
=======================================
  Coverage   82.22%   82.22%
=======================================
  Files         244      244
  Lines        4681     4681
  Branches     1452     1452
=======================================
  Hits         3849     3849
  Misses        801      801
  Partials       31       31

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr291.dev.hel.ninja :rocket::rocket::rocket:

kultus-admin-ui branch is deployed to platta: https://kultus-admin-ui-pr291.dev.hel.ninja :rocket::rocket::rocket:


Simulation does not account for Asymptomatic/Pre-symptomatic Spread

Is your feature request related to a problem? Please describe.
Yes, without this feature the projection should not be used.  To be effective as a tool for planning school reopening, this simulation should account for asymptomatic/pre-symptomatic spread that has been shown in newer studies to be non-negligible. Recent JAMA study shows ⅓ of subjects tested positive shows no symptom, ⅕ eventually show symptoms when in isolation. Conclusion from paper:
“Many individuals with SARS-CoV-2 infection remained asymptomatic for a prolonged period, and viral load was similar to that in symptomatic patients; therefore, isolation of infected persons should be performed regardless of symptoms.”
Describe the solution you'd like
Just like it allows for distancing effectiveness as a parameter to drive the simulation, it should allow an input for non-symptomatic contagious carrier as ratio of population, and percentage of test coverage for this group, and show the effect in the projection.
Describe alternatives you've considered
None.
Additional context

JAMA,  ⅓ of subjects tested positive shows no symptom but some are contagious (https://jamanetwork.com/journals/jamainternalmedicine/fullarticle/2769235)

This is already included in Covasim, see the symp_prob parameter. In Fig. 2 of this paper, we see 31% asymptomatic transmission:
https://www.medrxiv.org/content/10.1101/2<IP_ADDRESS>54765v3.full.pdf


Update release planner with new TypeSpec info blurb

We need to make sure that both API readiness app have the same consistent info blurb. it should cover greenfields and brownfields.
The message should be the same as the one our CI tooling is using. https://github.com/Azure/azure-sdk-tools/issues/8406

Here is the verbiage we will use:  "TypeSpec usage for API definition has been a requirement for all new (greenfield) data plane and management plane services. This is now a mandatory requirement and will be enforced by the API Stewardship Board for data plane services and ARM API Review Board for management plane services. Starting by the end of July 2024, the tooling warning on API Spec builds not complying with the TypeSpec requirement will be changed from a warning to a blocking error for new data plane and management plane service API spec Pull Requests."

Data plane app:

Management plane app:


Create UML diagram for Sort

I created a diagram. Going to need help from someone else to render the diagram and put it in the DG so that the scaling is correct

#195 Fixes the bugs and creates the diagram


[MERGE] Branch 1.3 to master

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11733/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11736/
Test PASSed.

Merged build finished. Test PASSed.

@calvinjia

LGTM


slimserver fails to communicate with Spotify on Raspberry Pi 4

Describe the bug
After fixing the problems in #108617 (cf this branch), the Spotify plugin for slimserver fails to run the Spotify helper binaries it ships with.
To Reproduce
Steps to reproduce the behavior:

Set up NixOS for a Raspberry PI 4 using the images indicated by the nixos wiki.

Apply the patch outlined in #108617 (cf this branch)

Set up slimserver (services.slimserver.enable = true).

After startup, slimserver will log the following error message (visible in journalctl -u slimserver):
Plugins::Spotty::Helper::get (51) Didn't find Spotty helper application!
Plugins::Spotty::Helper::get (52) Last error:
sh: /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-hf: No such file or directory

Additionally, in the "Plugins" tab of the settings page, the following text is visible:
There has been a problem running the Spotty helper application. You might want to give the additional "Spotty Helper Application for ARMv8/aarch64 architecture" plugin a try.
Operating system: Linux / aarch64-linux

Helper Applications Folder:
/nix/store/iif6k1ldrzlncbwf9fm89xgcgw1ss59z-lame-3.100/bin
/nix/store/zpiq0sj3nlqz6pkq88f4vqixs5xwzgqp-flac-1.3.3-bin/bin
/nix/store/ad4h1d0l2z1v05q0pvpsagqmqz6qd24d-faad2-2.10.0/bin
/nix/store/6rr1y8q5zsy185ahabjzp81aqpfw0f39-sox-14.4.2/bin
/nix/store/6f2a3df8l8z563ad3dib5bjpj9c28hyb-monkeys-audio-3.99-u4-b5/bin
/nix/store/x2x9qzggq2vwyl0jn8kalcnqfiifisn8-wavpack-5.3.0/bin
/nix/store/mc7s5nla8y7nr8x5j1yz1kmq8xh1bhcg-coreutils-8.32/bin
/nix/store/5xiyazii9004aipigb5bp6rm6aqi4mak-findutils-4.7.0/bin
/nix/store/qqa9c02q397zk1mqi2n8rd93ksm8xvh3-gnugrep-3.6/bin
/nix/store/vjhx2pa94y87r50mfmkasf6cmrgff63y-gnused-4.8/bin
/nix/store/7l8g3cahr0yiszwl3ca8aic59b8ap02v-systemd-247.2/bin
/nix/store/7l8g3cahr0yiszwl3ca8aic59b8ap02v-systemd-247.2/sbin
/usr/bin
/var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/aarch64-linux
/var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin
/var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux
sh: ldd: command not found

On x64, I was able to set slimserver up accordingly and use the Spotify plugin without running into any issues.
When trying to run the correct binary directly from a shell, bash reports the same error:
[nixos@nixos:~/source/nix/nixpkgs]$ /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/aarch64-linux/spotty
-bash: /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/aarch64-linux/spotty: No such file or directory

OTOH, this works on x64:
λ ~/ /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty
spotty v0.35.0
error: Required option 'name' missing
Usage: /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty [options]

[... and so on; I'll omit the help message here]

Expected behavior
The spotty helper application is runnable and the Spotify plugin for slimserver can be used.
Notify maintainers
@phile314
Metadata
 - system: `"aarch64-linux"`
 - host os: `Linux 4.19.118, NixOS, 21.03pre260232.733e537a8ad (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(root): `"nixos-21.03pre260232.733e537a8ad"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
- pkgs.slimserver
# a list of nixos modules affected by the problem
module:
- services.slimserver

While looking for explanations for this error, I found this forum post, stating that most likely, a missing program interpreter might be the culprit.
And indeed:
[nix-shell:~/source/nix/nixpkgs]$ readelf -a /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/aarch64-linux/spotty | fgrep -i requesting
      [Requesting program interpreter: /lib/ld-linux-aarch64.so.1]

[nix-shell:~/source/nix/nixpkgs]$ readelf -a "$(which ls)" | fgrep -i requesting
      [Requesting program interpreter: /nix/store/4pc5akylpxdi0azn6mcqcg0qaj4wz88r-glibc-2.32-10/lib/ld-linux-aarch64.so.1]

At the same time, the helper binary for i386 doesn't seem to contain such a path (i.e. there's no output):
[nix-shell:~]$ readelf -a /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty | fgrep -i requesting

[nix-shell:~]$

I'm not sure how to proceed from here, though. Is there a way to set up an environment so that binaries that weren't built through Nix itself can still run? Patching them in a nix derivation would seem complicated to me, since they are shipped by the Spotify plugin and not through the slimserver package itself...

While looking for explanations for this error, I found this forum post, stating that most likely, a missing program interpreter might be the culprit.
And indeed:
[nix-shell:~/source/nix/nixpkgs]$ readelf -a /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/aarch64-linux/spotty | fgrep -i requesting
      [Requesting program interpreter: /lib/ld-linux-aarch64.so.1]

[nix-shell:~/source/nix/nixpkgs]$ readelf -a "$(which ls)" | fgrep -i requesting
      [Requesting program interpreter: /nix/store/4pc5akylpxdi0azn6mcqcg0qaj4wz88r-glibc-2.32-10/lib/ld-linux-aarch64.so.1]

At the same time, the helper binary for i386 doesn't seem to contain such a path (i.e. there's no output):
[nix-shell:~]$ readelf -a /var/lib/slimserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty | fgrep -i requesting

[nix-shell:~]$

I'm not sure how to proceed from here, though. Is there a way to set up an environment so that binaries that weren't built through Nix itself can still run? Patching them in a nix derivation would seem complicated to me, since they are shipped by the Spotify plugin and not through the slimserver package itself...

Reading the GitHub readme of the Spotty plugin, I discovered that the spotty helper application is maintained in a separate repository.
The Bin directory in the plugin's original repository also contains some notes on how these helper binaries are supposed to be built on different architectures.
Since the text from the plugin settings page (cf. the original issue description) lists nix store paths before anything else, I'll try to write a new nix derivation expression that builds such a binary on the current architecture and can be included as a build input in the slimserver derivation.
If I'm successful, I hope this would lead the server to try executing this binary first, effectively replacing the binaries distributed by the plugin itself. If so, my suggestion would be to introduce a new option to toggle this dependency.

Reading the GitHub readme of the Spotty plugin, I discovered that the spotty helper application is maintained in a separate repository.
The Bin directory in the plugin's original repository also contains some notes on how these helper binaries are supposed to be built on different architectures.
Since the text from the plugin settings page (cf. the original issue description) lists nix store paths before anything else, I'll try to write a new nix derivation expression that builds such a binary on the current architecture and can be included as a build input in the slimserver derivation.
If I'm successful, I hope this would lead the server to try executing this binary first, effectively replacing the binaries distributed by the plugin itself. If so, my suggestion would be to introduce a new option to toggle this dependency.

Ah,yes, this is going to be problematic. As far as I remember, these plugins are installed using slimserver and are completely outside of the control of nixpkgs, right?
I think your proposed solution sounds like a good approach.

Ah,yes, this is going to be problematic. As far as I remember, these plugins are installed using slimserver and are completely outside of the control of nixpkgs, right?
I think your proposed solution sounds like a good approach.

Hi @phile314,
thanks for your response!
Unfortunately, the experiments on the spotty helper application I stared yesterday weren't really successful:
The Cargo project of spotty uses Cargo's replace feature to switch out the dependency of rust-crypto with a specific feature branch (something related to AES with AVX2 that was discussed here in librespot).
Unfortunately, this clashes with #30742 as cargo vendor seemingly still has no proper support for replace dependencies, which means building the app simply through buildRustPackage fails.
And since spotty uses a custom version of librespot, I'm currently not sure if I can simply remove the replace definitions or not (I can't find the respective entry in the fork's Cargo.lock). I'll have to investigate further.

Hi @phile314,
thanks for your response!
Unfortunately, the experiments on the spotty helper application I stared yesterday weren't really successful:
The Cargo project of spotty uses Cargo's replace feature to switch out the dependency of rust-crypto with a specific feature branch (something related to AES with AVX2 that was discussed here in librespot).
Unfortunately, this clashes with #30742 as cargo vendor seemingly still has no proper support for replace dependencies, which means building the app simply through buildRustPackage fails.
And since spotty uses a custom version of librespot, I'm currently not sure if I can simply remove the replace definitions or not (I can't find the respective entry in the fork's Cargo.lock). I'll have to investigate further.

I was able to resolve the build problems I mentioned above: spotty built fine through Nix once I removed the patched version of rust-crypto from the project's dependencies. I pushed the nix code I have running so far to a branch on my nixpkgs fork.
Now, I'm not sure how to proceed. First of all, removing the custom package generates quite a couple of changes to the project's Cargo.lock file. Also, since the original discussion on the custom rust-crypto branch used revolved around issues on Intel Westmere CPUs, the resulting binary will most likely not work properly on those. At the same time, since spotty uses a customized fork of librespot, simply updating that dependency also isn't enough to avoid the rust-crypto fork, although the mainline library seemingly has moved on to another crypto library in 2018.
On my branch, I just added it as another entry under pkgs/tools/audio, but given the above, that might not be the best idea. Would it be a better option to add it as a separate nix file to pkgs/servers/slimserver and just importing and adding it to wrapProgram using optional?
...or should I better just maintain this in a separate repository and pull it in via pkgs.slimserver.overrideAttrs and services.slimserver.package? If so, can you give me a hint on how I could influence the wrapProgram call via overrideAttrs (I've never done that so far)?

I was able to resolve the build problems I mentioned above: spotty built fine through Nix once I removed the patched version of rust-crypto from the project's dependencies. I pushed the nix code I have running so far to a branch on my nixpkgs fork.
Now, I'm not sure how to proceed. First of all, removing the custom package generates quite a couple of changes to the project's Cargo.lock file. Also, since the original discussion on the custom rust-crypto branch used revolved around issues on Intel Westmere CPUs, the resulting binary will most likely not work properly on those. At the same time, since spotty uses a customized fork of librespot, simply updating that dependency also isn't enough to avoid the rust-crypto fork, although the mainline library seemingly has moved on to another crypto library in 2018.
On my branch, I just added it as another entry under pkgs/tools/audio, but given the above, that might not be the best idea. Would it be a better option to add it as a separate nix file to pkgs/servers/slimserver and just importing and adding it to wrapProgram using optional?
...or should I better just maintain this in a separate repository and pull it in via pkgs.slimserver.overrideAttrs and services.slimserver.package? If so, can you give me a hint on how I could influence the wrapProgram call via overrideAttrs (I've never done that so far)?

I just realized I failed to mention the most important thing: With the spotty helper binary building, the Spotify plugin for slimserver actually works. I simply had to add it to the wrapProgram call, and the plugin picked up the right binary.

I just realized I failed to mention the most important thing: With the spotty helper binary building, the Spotify plugin for slimserver actually works. I simply had to add it to the wrapProgram call, and the plugin picked up the right binary.

I don't know anything about the rust part, but I guess that could be problematic.
I see two options:

Add the spotty binary to the path of the systemd service (systemd.services.slimserver.path)
Add an extra-parameter to the slimserver package derivation to splice in extra binaries to the wrapProgram call

I think option 1 is cleaner. I think that way you can also keep spotty in your private branch or try to get it merged into nixpkgs proper, whichever you prefer.

I don't know anything about the rust part, but I guess that could be problematic.
I see two options:

Add the spotty binary to the path of the systemd service (systemd.services.slimserver.path)
Add an extra-parameter to the slimserver package derivation to splice in extra binaries to the wrapProgram call

I think option 1 is cleaner. I think that way you can also keep spotty in your private branch or try to get it merged into nixpkgs proper, whichever you prefer.

Thank you very much for your hint on systemd.services.slimserver.path!
I tested it here, and the spotty plugin for slimserver indeed picks up the correct helper binary if it's provided in this way, making further changes to the slimserver derivation unnecessary.
Since my nix derivation for spotty currently won't work on every platform (see my comment above), I decided to just pull it in through a custom nix file in my own config (at least until #30742 is fixed). If anyone runs into the same issues, they're welcome to just copy the spotty.nix and use-cargo-rust-crypto.patch files from my configuration.
Since this setup works for my device (the only issue being some long rust compilation times), I'll close this issue. Thanks again for your help, @phile314! :-)

Thank you very much for your hint on systemd.services.slimserver.path!
I tested it here, and the spotty plugin for slimserver indeed picks up the correct helper binary if it's provided in this way, making further changes to the slimserver derivation unnecessary.
Since my nix derivation for spotty currently won't work on every platform (see my comment above), I decided to just pull it in through a custom nix file in my own config (at least until #30742 is fixed). If anyone runs into the same issues, they're welcome to just copy the spotty.nix and use-cargo-rust-crypto.patch files from my configuration.
Since this setup works for my device (the only issue being some long rust compilation times), I'll close this issue. Thanks again for your help, @phile314! :-)


Resource Excuted error while training object detection model in google colab

i try to train model  Google  Colab using gpu . while training at one time i got error like rosirce exvuted error  OMM like this. i don't understand why i got this error. Please help me to sort it out this error.

@RD191295
Memory error indicates that the process has consumed all of the ram memory. You may want to reduce the batch size/image size and try again. [please refer to #38414]

I am using batch size : 16 and image size is 420x420. Train.record file size is 2 mb..

Even it not start 1 epoch also and  before that only memory was consumed...

@RD191295
We see that the issue template has not been filled, could you please do so as it helps us analyse the issue [tf version, steps followed before you ran into this error or stand alone code to reproduce the issue faced]

Error while using model_main_tf2.py file for training object detection model i got such error:
2020-12-02 03:59:43.514873: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2020-12-02 03:59:46.353952: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2020-12-02 03:59:46.363592: E tensorflow/stream_executor/cuda/cuda_driver.cc:314] failed call to cuInit: CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
2020-12-02 03:59:46.363634: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:156] kernel driver does not appear to be running on this host (f6a8f84517f0): /proc/driver/nvidia/version does not exist
2020-12-02 03:59:46.363975: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  AVX512F
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2020-12-02 03:59:46.378641: I tensorflow/core/platform/profile_utils/cpu_utils.cc:104] CPU Frequency:<PHONE_NUMBER> Hz
2020-12-02 03:59:46.378943: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x1df1100 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-12-02 03:59:46.378979: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
WARNING:tensorflow:There are non-GPU devices in tf.distribute.Strategy, not using nccl allreduce.
W1202 03:59:46.381007<PHONE_NUMBER>48640 cross_device_ops.py:1202] There are non-GPU devices in tf.distribute.Strategy, not using nccl allreduce.
INFO:tensorflow:Using MirroredStrategy with devices ('/job:localhost/replica:0/task:0/device:CPU:0',)
I1202 03:59:46.381281<PHONE_NUMBER>48640 mirrored_strategy.py:341] Using MirroredStrategy with devices ('/job:localhost/replica:0/task:0/device:CPU:0',)
INFO:tensorflow:Maybe overwriting train_steps: None
I1202 03:59:46.746428<PHONE_NUMBER>48640 config_util.py:552] Maybe overwriting train_steps: None
INFO:tensorflow:Maybe overwriting use_bfloat16: False
I1202 03:59:46.746670<PHONE_NUMBER>48640 config_util.py:552] Maybe overwriting use_bfloat16: False
INFO:tensorflow:Reading unweighted datasets: ['annotations/train.record']
I1202 03:59:46.797454<PHONE_NUMBER>48640 dataset_builder.py:148] Reading unweighted datasets: ['annotations/train.record']
INFO:tensorflow:Reading record datasets for input file: ['annotations/train.record']
I1202 03:59:46.798697<PHONE_NUMBER>48640 dataset_builder.py:77] Reading record datasets for input file: ['annotations/train.record']
INFO:tensorflow:Number of filenames to read: 1
I1202 03:59:46.798857<PHONE_NUMBER>48640 dataset_builder.py:78] Number of filenames to read: 1
WARNING:tensorflow:num_readers has been reduced to 1 to match input file shards.
W1202 03:59:46.798953<PHONE_NUMBER>48640 dataset_builder.py:86] num_readers has been reduced to 1 to match input file shards.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/builders/dataset_builder.py:103: parallel_interleave (from tensorflow.python.data.experimental.ops.interleave_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.data.Dataset.interleave(map_func, cycle_length, block_length, num_parallel_calls=tf.data.experimental.AUTOTUNE) instead. If sloppy execution is desired, use tf.data.Options.experimental_deterministic.
W1202 03:59:46.809036<PHONE_NUMBER>48640 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/builders/dataset_builder.py:103: parallel_interleave (from tensorflow.python.data.experimental.ops.interleave_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.data.Dataset.interleave(map_func, cycle_length, block_length, num_parallel_calls=tf.data.experimental.AUTOTUNE) instead. If sloppy execution is desired, use tf.data.Options.experimental_deterministic.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/builders/dataset_builder.py:222: DatasetV1.map_with_legacy_function (from tensorflow.python.data.ops.dataset_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.data.Dataset.map() W1202 03:59:46.855802<PHONE_NUMBER>48640 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/builders/dataset_builder.py:222: DatasetV1.map_with_legacy_function (from tensorflow.python.data.ops.dataset_ops) is deprecated and will be removed in a future version. Instructions for updating: Use tf.data.Dataset.map()
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/dispatch.py:201: sparse_to_dense (from tensorflow.python.ops.sparse_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Create a tf.sparse.SparseTensor and use tf.sparse.to_dense instead.
W1202 03:59:53.997627<PHONE_NUMBER>48640 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/dispatch.py:201: sparse_to_dense (from tensorflow.python.ops.sparse_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Create a tf.sparse.SparseTensor and use tf.sparse.to_dense instead.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/dispatch.py:201: sample_distorted_bounding_box (from tensorflow.python.ops.image_ops_impl) is deprecated and will be removed in a future version.
Instructions for updating:
seed2 arg is deprecated.Use sample_distorted_bounding_box_v2 instead.
W1202 03:59:56.998954<PHONE_NUMBER>48640 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/dispatch.py:201: sample_distorted_bounding_box (from tensorflow.python.ops.image_ops_impl) is deprecated and will be removed in a future version.
Instructions for updating:
seed2 arg is deprecated.Use sample_distorted_bounding_box_v2 instead.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/inputs.py:281: to_float (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
W1202 03:59:58.767645<PHONE_NUMBER>48640 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/inputs.py:281: to_float (from tensorflow.python.ops.math_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.cast instead.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/model_lib_v2.py:349: set_learning_phase (from tensorflow.python.keras.backend) is deprecated and will be removed after 2020-10-11.
Instructions for updating:
Simply pass a True/False value to the training argument of the __call__ method of your layer or model.
W1202 04:00:05.767568<PHONE_NUMBER>23424 deprecation.py:323] From /usr/local/lib/python3.6/dist-packages/object_detection-0.1-py3.6.egg/object_detection/model_lib_v2.py:349: set_learning_phase (from tensorflow.python.keras.backend) is deprecated and will be removed after 2020-10-11.
Instructions for updating:
Simply pass a True/False value to the training argument of the __call__ method of your layer or model.
 See above for specific issues. Use expect_partial() on the load status object, e.g. tf.train.Checkpoint.restore(...).expect_partial(), to silence these warnings, or use assert_consumed() to make the check explicit. See https://www.tensorflow.org/guide/checkpoint#loading_mechanics for details.
W1202 04:01:09.311225<PHONE_NUMBER>48640 util.py:158] A checkpoint was restored (e.g. tf.train.Checkpoint.restore or tf.keras.Model.load_weights) but not all checkpointed values were used. See above for specific issues. Use expect_partial() on the load status object, e.g. tf.train.Checkpoint.restore(...).expect_partial(), to silence these warnings, or use assert_consumed() to make the check explicit. See https://www.tensorflow.org/guide/checkpoint#loading_mechanics for details.
WARNING:tensorflow:From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/deprecation.py:574: calling map_fn_v2 (from tensorflow.python.ops.map_fn) with dtype is deprecated and will be removed in a future version.
Instructions for updating:
Use fn_output_signature instead
W1202 04:01:25.383937<PHONE_NUMBER>30720 deprecation.py:506] From /usr/local/lib/python3.6/dist-packages/tensorflow/python/util/deprecation.py:574: calling map_fn_v2 (from tensorflow.python.ops.map_fn) with dtype is deprecated and will be removed in a future version.
Instructions for updating:
Use fn_output_signature instead
^C

@RD191295
As requested earlier please share simple stand alone code such that we can replicate the issue reported or if possible share a colab gist with the error.

I try login from other gmail account it's working fine but if I do on that mail id I got that error!! Don't understand what is wrong with that account!! But account switch help me to solve problem

@RD191295
Please move the issue to closed status if resolved.

Thank you for help!!

Thank you for helping to solve issue


add documentation how to listen to view_closed events #1010

Summary
Fix #1010 Add documentation how to handle view_closed events as requested by #1010.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Just to be sure: My current understanding is that all you requests are solved now and there is nothing to do from my side. If not please tell me what else needs to be adjusted.

Thanks for your work @TheManWhoStaresAtCode !

hmm unfortunatly the code example for the view_closed event is not displayed properly - https://slack.dev/bolt-js/concepts#view-submissions :thinking:

Hmm you are right. I tried playing around with the markdown structure / "section content" div, but it looks like we can only have one right "sidebar" example code per markdown page (otherwise they overlap, like you see on the live page). Maybe we can try to break out the view closed event and example into its own markdown page?

I pushed up a fix in https://github.com/slackapi/bolt-js/commit/4158bc5b84e8bcfe028cb3d040eda1a83c3531c4 - should be live shortly.

thanks @filmaj - style is still a little bit broken but at least the code blocks are now available


ElasticSearch PVC can be allocated separately

ElasticSearch PVC can be allocated separately ，because master and client nodes do not need  Storage as much as Data nodes，so master and client nodes need to set a smaller storage.
Please refer to ：
https://github.com/jetstack/navigator/blob/master/docs/quick-start/es-cluster-demo.yaml
such as:
apiVersion: kubedb.com/v1alpha1
kind: Elasticsearch
metadata:
name: topology-es
namespace: demo
spec:
version: 5.6
topology:
master:
prefix: master
replicas: 1
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 50Mi
data:
prefix: data
replicas: 5
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
client:
prefix: client
replicas: 2
storage:
storageClassName: "standard"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 50Mi

Fixed in 0.8.0 . Supported here: https://github.com/kubedb/apimachinery/blob/master/apis/kubedb/v1alpha1/elasticsearch_types.go#L129


Support for SSL

Currently errors out if SSL is required

Changing line 757 to look like this:
s = Server(args.host, port=636, use_ssl=True, get_info=ALL)

Worked as a temp fix

putting a simple flag in to enable SSL and a check for the error would be awesome, sorry I can't provide the error :/

Did you try to specify the host with ldaps://hostname (or IP)? Then it will automatically switch to use SSL.

Assuming the fix in b905d9c makes SSL support somewhat more clear, closing.


added codecov badge

Codecov Report

Merging #2 (e518764) into main (100e322) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main      #2   +/-   ##
=====================================
  Coverage   9.42%   9.42%
=====================================
  Files          9       9
  Lines        403     403
=====================================
  Hits          38      38
  Misses       365     365

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 100e322...e518764. Read the comment docs.


Values are not selectable.

This control would be particularly useful for developers. Developers are power users. Developers get annoyed when the values that they're working with have to be typed out manually instead of copied and pasted.

Fixed by https://github.com/summerstyle/jsonTreeViewer/commit/0f8f4afe41be35ea0fb446945f64c3614116740b
Thank you.


Angular 1.6 support

@johnaudas built latest in order to consume via bower.

This change is

Sorry, I don't know what I'm doing. :)


Update for Radomir's comments

@randomir if you merge this I can complete my fixes for doctest failures


Eras should center and zoom when selected

This is a feature that's currently implemented in diverseLevant. The data is included below. The zoom level column will need to be updated to use actual zoom numbers.

@bwellington Can you also have it update the extents on the era preview screen as well?


Update README.md

I'm the creator of HubPress, maybe this PR is not really objective.
I shall let you judge if HubPress is awesome enough to be in this awesome repository :smile:
I understand if the PR is rejected.

@anthonny HubPress is most definitely awesome :+1:

Thank you! :+1:


Add global annotation Property

This usefull when you want to set meta data between shards (and dont want to create annotations for every shard).
Also fix bug with yaml and json umapped usage.

specs failed, i think in 0.25.1 add only line: types["Property"] = AnnotationType.new self, self, "Property", what you think?

It's a nice idea, but Property looks way too generic to me, maybe Serialization(ignore: true) ? This way I think it's easier to see what it is about, and how it relates to JSON/YAML/you-name-it (de)serialization.

this is need not only for serialization but for many other things.

Can you give examples of non-serialization usecase?

I think we still haven't set in stone that we never will impose a specific interface on annotations. When we do decide this, this would backfire quite a bit, so I'm not sure I like it and be it for the reason that it makes it harder to later do enforce interfaces on annotations.

Just ignore for YAML, JSON, and any other format you want. Crystal should not become a "write less oriented" language.

example: when you have many modules which generate methods based on instance_vars:
# generate doc for class
module Doc
  def to_doc
     {% for ivar in @type.instance_vars %} ... {% end %}
  end
end

# Calculate md5 based of class fields
module Md5
  def to_md5
     {% for ivar in @type.instance_vars %} ... {% end %}
  end
end

# Generate methods to_named_tuple, to_hash, ...
module To
  def to_named_tuple
     {% for ivar in @type.instance_vars %} ... {% end %}
  end

  def to_hash
     {% for ivar in @type.instance_vars %} ... {% end %}
  end
end

and others.
And you want to use it like this:
class A
   include JSON::Serializable
   include YAML::Serializable
   include MessagePack::Serializable
   include Doc
   include Md5
   include To

   @a : Int32

   @[Property(ignore: true)]
   @b : String?
end

instead of:
@[JSON::Field(ignore: true)]
@[YAML::Field(ignore: true)]
@[MessagePack::Field(ignore: true)]
@[Doc::Field(ignore: true)]
@[Md5::Field(ignore: true)]
@[To::Field(ignore: true)]
@b : String?

And another usage is modules which extend class with another variable:
module Bla
   @[Property(ignore: true)]
   @some_storage = Hash(String, String).new
end

class A
  include JSON::Serializable
  include JSON::Serializable
  include Bla
end

you dont know where this module would be included, and what ignore it should add (JSON::Field, or others.)
So shared Property would be nice in all this examples:

@kostya The thing is, nobody will write such code (maybe only you?). When I write a REST API, I provide JSON output, not ten thousand kinds of outputs. When I parse a file with yaml configuration, I use YAML serialization. When I want to send something over a socket fast, maybe I'd use msgpack. But combining serialization just to be as generic as possible doesn't seem to have a good use case.
And even if there's a use case, just write all that code. You write a lot of code in C# and it's consistent. You write a lot of code in Elixir and it's consistent. The way to destroy consistency is by introducing hacks just because you don't want to write more.


Option to add custom templates or edit default templates

What would you like to be added:
Option to add custom templates or edit default templates.
Why is this needed:
Templates are a super useful feature, but currently users are limited to the default templates in Lens which unfortunately limits that feature a lot.
Environment you are Lens application on:

Kubernetes distribution: k3s
Desktop OS: macOS

Hi, I believe this has been addressed here: https://github.com/lensapp/lens/pull/2327

@jim-docker You're right. At least that's what it looks like from the GIF in the pull request you've mentioned.
But according to the PR this feature should already be available in Lens 5... which it isn't (or maybe I'm blindfolded because I can't find any option to create custom templates in Lens 5 😀).

@mamiu All you need to do is create new folder inside /.k8slens/templates and add some *.yaml files in there. Right after you will see your new templates grouped by the name of the directory.

We're working on improving documentation to cover this feature. Sorry for the confusion.

@aleksfront That's amazing! Thanks a lot!


"Computing the diff for you" - editor hangs

I found split-diff to solve a problem I was having, since it seemed like the ideal tool.
I used as described... opened the file, ran "split diff: toggle"... but all I get is a loading message saying "Computing the diff for you" which crashes the editor, necessitating a force-quit.
I've seen other issues with similar results dating back to 2016.
Atom: 1.19.2
Split-diff: 1.5.1

@QuintinS any chance you can reproduce with the console open? (ctrl+shift+p then search dev tools) Then if you run split-diff, does the console say anything? Does it happen on all files or specific files? Thanks

@mupchrch I'm also seeing this issue.
I ran it with dev tools open and the only thing I see is this but that was there before running split diff
IntersectionObserver.observe(target): target element is not a descendant of root.
It's seems to only happen to me on large files eg I'm trying to diff a file that's 52,000 lines.
In task manager there is a atom process that's at 9.9% CPU and 700MB of RAM. the usage is only hitting one process on the 12 the system has (ryzen system).
I let it run on the "Computing the diff for you" for 45 mins then force quite atom.
Atom: 1.21.1
Split-diff: 1.5.1

I am experiencing the same issue but with split-diff 1.5.2

Hangs on finding the diff.
BufferedNodeProcess code was 1
split-diff.coffee? [sm]:326 module.js:545
    throw err;
    ^

Error: Cannot find module 'diff'
    at Function.Module._resolveFilename (module.js:543:15)
    at Function.Module._load (module.js:473:25)
    at Module.require (module.js:586:17)
    at require (internal/module.js:11:18)
    at _computeDiffChunks (/Users/ujs818/.atom/packages/split-diff-master/lib/compute-diff.js:22:16)
    at Object.<anonymous> (/Users/ujs818/.atom/packages/split-diff-master/lib/compute-diff.js:10:18)
    at Object.<anonymous> (/Users/ujs818/.atom/packages/split-diff-master/lib/compute-diff.js:193:3)
    at Module._compile (module.js:642:30)
    at Object.Module._extensions..js (module.js:653:10)
    at Module.load (module.js:561:32)


Add UBI Dockerfiles

Add UBI Dockerfiles
These were forgotten from the PR that was supposed to introduce them
(https://github.com/kubernetes-sigs/security-profiles-operator/pull/172)
NONE

/ok-to-test

Pull-request updated, HEAD is now 84f2e8e68ff1ea68d9ebbc1f81ec57749bd2f7d3


[43+] Navigator docs are mentioned, but the links are broken:

See: https://facebook.github.io/react-native/releases/next/docs/navigation.html
Find
Check out the Navigator API reference for specific examples that cover each of these scenarios.
The Navigator API reference is linked to https://facebook.github.io/react-native/releases/next/docs/navigator.html
That URL is not valid. :(
Navigator is still useful as react-navigation still has problems and is no where as near as flexible today as Navigator is.  :(

FWIW, Seems like 0.42 docs are fine. https://facebook.github.io/react-native/releases/0.42/docs/navigator.html
¯_(ツ)_/¯

Navigator is deprecated and has been removed from the core react-native package. It can now be installed and imported from react-native-deprecated-custom-components instead of react-native.
These remaining references are in error and I'll remove them shortly. Docs for the now deprecated Navigator can always be accessed by loading docs for older releases prior to its deprecation.


v0.2.2

scimlsensitivity upgrade

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.03%. Comparing base (985e86e) to head (de4c192).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #14   +/-   ##
=======================================
  Coverage   82.03%   82.03%
=======================================
  Files           4        4
  Lines         412      412
=======================================
  Hits          338      338
  Misses         74       74

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat(rust, python): add HDFS support via hdfs-native package

Description
Add support for HDFS using hdfs-native, a pure* Rust client for interacting with HDFS. Creates a new hdfs sub-crate, adds it as a feature to deltalake meta crate, and includes it in Python wheels by default. There is a Rust integration test that requires Hadoop and Java to be installed, and makes use of a small Maven program I ship under the integration-test feature flag to run a MiniDFS server.
*Dynamically loads libgssapi_krb5 using libloading for Kerberos support
Related Issue(s)

Resolves #2611
Documentation

@Kimahriman LGTM! Can you please also add some docs on the integration in the .MD files and if possible links some docs of the possible configs that can be set
@rtyler can you also go over it?

@Kimahriman LGTM! Can you please also add some docs on the integration in the .MD files and if possible links some docs of the possible configs that can be set

Yeah I agree there should be some, but I didn't see anything for other storage backends so I wasn't sure where to add it. Any recommendation? A new page under integrations/?

@Kimahriman LGTM! Can you please also add some docs on the integration in the .MD files and if possible links some docs of the possible configs that can be set

Yeah I agree there should be some, but I didn't see anything for other storage backends so I wasn't sure where to add it. Any recommendation? A new page under integrations/?

Yeah under integrations makes sense, perhaps called object storage and then a page for hdfs there
@avriiil any inputs on this? Having some small explanation per object store for S3, adls, gcs and mounted storage would make sense, do you want to help on this?

Yeah under integrations makes sense, perhaps called object storage and then a page for hdfs there

I added a page. I couldn't get the docs to build locally to verify things though. Just kept getting
griffe.exceptions.AliasResolutionError: Could not resolve alias deltalake._internal.DeltaError pointing at _internal.DeltaError (in python/deltalake/_internal.abi3.so:None)

Yeah under integrations makes sense, perhaps called object storage and then a page for hdfs there

I added a page. I couldn't get the docs to build locally to verify things though. Just kept getting
griffe.exceptions.AliasResolutionError: Could not resolve alias deltalake._internal.DeltaError pointing at _internal.DeltaError (in python/deltalake/_internal.abi3.so:None)

Yeah there is something broken with the docs for some time now

Late to the party, I was OOO for a couple of days.
Happy to take a look at creating some more docs if that still makes sense
@ion-elgreco?
~ ~ ~
Avril Aysha
DevRel & Content
+351 963681498
On Fri, 21 Jun 2024 at 07:22, Ion Koutsouris @.***>
wrote:

Merged #2612 https://github.com/delta-io/delta-rs/pull/2612 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/delta-io/delta-rs/pull/2612#event-13238027097, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQLWMSQ4OSQHETPDAUM7PSLZIPBA7AVCNFSM6AAAAABJSWGJNKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGIZTQMBSG4YDSNY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@avriiil yeah some docs for each object store would be great 😃

sounds good, adding this to my list for next week @ion-elgreco


iphone7可以吗

I didn't try running it on iPhone7. But I suppose it works. For the project supports both iPad/iPhone and all orientations. The memory peak in training is about 350M which is safe on all types of iPhone/iPad.


Cannot find native module ReactNativeLocalNetworkPermission

The library works fine on android but crash on ios displaying this error Cannot find native module ReactNativeLocalNetworkPermission @benjaminkomen

This library is specifically meant for iOS, not Android.
Can you provide a minimum reproducible example?

I simply follow the documentation, import the library and call the function.
async function checkLocalNetwork()
{
const request = await requestLocalNetworkAccess();
const result = await checkLocalNetworkAccess();
console.log(request,result)

}
useEffect(()=>{
checkLocalNetwork()
},[])
On android return undefined and true on ios return Cannot find native module ReactNativeLocalNetworkPermission im using expo and traying in expo go @benjaminkomen

You cannot directly use this library in Expo Go, you need to create a development build because the native code in this library.

ok, thank you i will try.


Auth error

We're getting the following error:
Running "rackspaceInit" task
[D] Task source: /Sites/shomei.com/source/node_modules/grunt-rackspace/tasks/rackspace.js
[D] requesting token from https://auth.api.rackspacecloud.com/v1.0
Fatal error: Cannot read property '_' of undefined

I've tried adding the authUrl to what is shown at http://docs.rackspace.com/auth/api/v2.0/auth-client-devguide/content/QuickStart-000.html and tried v1 and v2 Urls and we get this:
Running "rackspaceInit" task
[D] Task source: /Sites/shomei.com/source/node_modules/grunt-rackspace/tasks/rackspace.js
[D] requesting token from https://lon.identity.api.rackspacecloud.com/v2.0/
Fatal error: No authentication token was returned in the headers. Request url: https://lon.identity.api.rackspacecloud.com/v2.0/. Try setting "authUrl" to something else.

And
Running "rackspaceInit" task
[D] Task source: /Sites/shomei.com/source/node_modules/grunt-rackspace/tasks/rackspace.js
[D] requesting token from https://lon.identity.api.rackspacecloud.com/v1.0/
Fatal error: Cannot read property '_' of undefined

I'm having this issue as well.

Same here.

2 years and no reply on this?!


Will JS similar to Py Arrow ever have the ability to read parquet from disk into arrow?

From what I understood, Parquet is for storage and arrow for in memory querying, are you planning to offer this on the JS side or that project is mainly for learning only?
Similarly, it seems in the Python version one can specify partitioning options for writing multiple files which is not present in the JS version but helps when large amounts of data is involved.
Also there seems to be no way of reading JSON data either and provide arrow schema and load it into a table.
It's an exciting technology, looking forward to see it mature more!

From what I understood, Parquet is for storage and arrow for in memory querying

I would leave it at "arrow is for in memory" but yes, you are correct.

are you planning to offer this on the JS side or that project is mainly for learning only?

You could search the mailing list, that's probably the closest you will come to a project-wide long term plan.  However, from a cursory search, I do not see anyone actively working on this feature.  I don't know of any reason it couldn't happen.  I'm not sure what you mean by "learning only"?  There are many use cases for JS projects that don't read files from disk, for example, any browser project.
Parquet would be a nice feature, especially for node-based backend servers, but it isn't a necessary feature for data analysis.  For example, there are many visualization libraries written in JS.  These libraries can just accept Arrow data from external applications via IPC and don't need to read it from disk themselves.

Similarly, it seems in the Python version one can specify partitioning options for writing multiple files which is not present in the JS version but helps when large amounts of data is involved.

This is correct.  This is the "datasets" API and it is not part of the Arrow Columnar Format and at the moment I think it is limited to the implementations based on C++ (Python,R,Ruby,C/Glib).

Also there seems to be no way of reading JSON data either and provide arrow schema and load it into a table.

There is no implementation that currently reads JSON (https://arrow.apache.org/docs/status.html#third-party-data-formats).  There is nothing preventing it but it has not been a high enough priority for anyone to implement.

Thanks. Confirmed my thoughts. For a node.js serverless or backend application this is not an option as a query engine. It's just for browser based things.


KeyVault swallows error when not logged in

Describe the bug
Running az keyvault secret show --name  --vault-name  returns nothing on Windows.
To Reproduce
Run az keyvault secret show --name  --vault-name
Expected behavior
Should show the secret
Environment summary
Install Method: MSI / CLI version 2.0.50 / Windows 10 1809 / Shell Type: cmd.exe
Additional context
Add any other context about the problem here.

It would be good to run with --debug and check out the response on payload

Interesting, using --debug revealed this (among other things):
az keyvault secret show --vault-name mcr-test-global-kv --name McrflowApp-Password --debug
Suppress exception There are no active accounts.
Suppress exception Please run 'az login' to setup account.
And so, indeed, I had not done az login in this box yet. After login the command worked just fine.
Wish I got that additional bit when running without --debug.

Thanks @julioct you are right--the command should not swallow this error. I've updated the issue to reflect this bug.

I will take a look since it is also related with auth. This has been a common user confusion since 2017

Thanks for looking into this!


List of tasks as a parameter in task_all

Hi @IllidanS4,
The current task_all implementation uses rest parameter for passing a number of tasks.
I would love to request a feature that you can pass a list (or any other dynamic containers) of tasks to task_all as a parameter, not a rest one.
This is super useful when we work with loops, for example:
new Task:tasks[100];
for(new i = 0; i != sizeof tasks; ++i) {
	tasks[i] = task_new();
	task_set_result_ms(tasks[i], 1, 1000);
}
await task_all(tasks);
for(new i = 0; i != sizeof tasks; ++i) {
	task_delete(tasks[i]);
}

new List:listOfTasks = list_new();
for(new i = 0; i != 100; ++i) {
	new Task:t = task_new();
	task_set_result_ms(t, 1, 1000);
	list_add(listOfTasks, t);
}
await task_all(listOfTasks);
list_clear_deep(listOfTasks);

Hello, would using pawn_call_native be sufficient?
await Task:pawn_call_native(pawn_nameof(task_all), "l", listOfTasks);

hay @duydang2311

Hello, would using pawn_call_native be sufficient?
await Task:pawn_call_native(pawn_nameof(task_all), "l", listOfTasks);

Thanks for the fast response!
There are few runtime errors in pp_on_error when I run a test with pawn_call_native.
hook OnGameModeInit() {
	new List:listOfTasks = list_new();
	for(new i = 0; i != 100; ++i) {
		new Task:t = task_new();
		task_set_result_ms(t, 1, 1000);
		list_add(listOfTasks, t);
	}
	await Task:pawn_call_native(pawn_nameof(task_all), "l", listOfTasks);
	return 1;
}

SOURCE: pawn_call_native
MESSAGE: native function 'task_all' has raised an AMX error 5: Invalid memory access

SOURCE: task_wait
MESSAGE: task reference is invalid (value 0x0)

SOURCE: task_get_result
MESSAGE: task reference is invalid (value 0x0)

Sorry, my bad, I forgot that l actually copies the contents to the function as values, not references (which are needed in this case). A quick fix would be to store the task as array in the list, i.e.:
new List:listOfTasks = list_new();
new Task:t[1];
for(new i = 0; i != 100; ++i) {
	t[0] = task_new();
	task_set_result_ms(t[0], 1, 1000);
	list_add_arr(listOfTasks, t);
}
await Task:pawn_call_native(pawn_nameof(task_all), "l", listOfTasks);

Would you be fine with this solution?

I see, it's a bit unclean. It solves my issue though.
Yes, I'm fine with this. Thank you.

I agree that a better-looking solution would be nice. I will think about it. By the way, list_get still works the same if you have array elements in a list, so if you intend to use that list for other things, you don't have to change much of the code.


"View in SQL Lab" button in charts displayed on the basis of role instead of permission

In the chart wizard, the "view in SQL Lab" button only appears in the context menu for the dataset if the user specifically has the sql_lab role, rather than depending on the relevant permission associated with this action: [SQL Lab].[menu_access]. Update this check to look for the permission instead of the role. Since the sql_lab role has that permission, it will continue to work as normal, but with a more appropriate check.
This fixes for the case where this permission has been assigned to a different role.
How to reproduce the bug

Add the [SQL Lab].[menu_access] role to the Gamma role, or some other role associated with a user
As a Gamma user, view a dataset in the chart explorer
Click on the three dots next to the dataset name in the top left
See that View in SQL Lab button is missing

Expected results
User should see the option to go to SQL Lab as they have SQL Lab access.
Actual results
Button is missing on the frontend.
Environment
(please complete the following information):

browser type and version: N/A
superset version: 2.1.0
python version: N/A
node.js version: N/A
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
I discussed this with @villebro who made the original change to check the role and agreed on the solution being to check the permission I named here instead; I'll raise a PR for this issue now as I already have this fixed and tested in our fork.

PR: https://github.com/apache/superset/pull/24903


K8SPXC-1027 Fix cross-site test

If the operator catches an error between updating an internal secret and updating a replication password, it will never update the replication password. That's why we should update the replication password in internal secret only after updating it for replication channels

Test name
Status

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1164/commits/cc1203a34028c599df216af0ee8f79816f0561a3
image: perconalab/percona-xtradb-cluster-operator:PR-1164-cc1203a3

Test name
Status

recreate
passed

storage
passed

upgrade-haproxy
passed

cross-site
passed

haproxy
passed

scaling
passed

big-data
passed

scheduled-backup
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

upgrade-proxysql
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

smart-update
passed

affinity
passed

one-pod
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
failed

We run 33 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1164/commits/cc1203a34028c599df216af0ee8f79816f0561a3
image: perconalab/percona-xtradb-cluster-operator:PR-1164-cc1203a3

Test name
Status

big-data
passed

cross-site
passed

upgrade-haproxy
passed

scheduled-backup
passed

storage
passed

self-healing
passed

haproxy
passed

recreate
passed

scaling
passed

self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

self-healing-advanced
passed

limits
passed

demand-backup
passed

security-context
passed

self-healing-advanced-chaos
passed

monitoring-2-0
passed

pitr
passed

operator-self-healing
passed

affinity
passed

demand-backup-encrypted-with-tls
passed

operator-self-healing-chaos
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

tls-issue-cert-manager-ref
failed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1164/commits/cc1203a34028c599df216af0ee8f79816f0561a3
image: perconalab/percona-xtradb-cluster-operator:PR-1164-cc1203a3

Test name
Status

storage
passed

scaling
passed

haproxy
passed

upgrade-haproxy
passed

big-data
passed

cross-site
failed

scheduled-backup
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

self-healing-advanced
passed

upgrade-proxysql
passed

self-healing-advanced-chaos
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

smart-update
passed

affinity
passed

one-pod
passed

pitr
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

upgrade-consistency
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
failed

We run 34 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1164/commits/0579ff5ccfc1182357f953a3795f646436742c9f
image: perconalab/percona-xtradb-cluster-operator:PR-1164-0579ff5c

Test name
Status

recreate
passed

storage
passed

scheduled-backup
failed

haproxy
failed

cross-site
passed

scaling
passed

upgrade-haproxy
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

init-deploy
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
passed

limits
passed

smart-update
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

monitoring-2-0
passed

pitr
failed

affinity
passed

one-pod
passed

auto-tuning
passed

upgrade-consistency
failed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

proxy-protocol
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1164/commits/f3d2cd417b081ab9ed075cb01c1af166b9fe7abf
image: perconalab/percona-xtradb-cluster-operator:PR-1164-f3d2cd41


feat: complete melt and create spore

Description
add meltThenCreateSpore high-level interface to facilitate community demand about: melt blind box and then mint a new spore.
Issues

[x] #9

@SpectreMercury problem has been solved, please review, this PR will be merged to YOUR branch.


Test Issue created at Fri, 09 Jul 2021 02:16:04 GMT

Test issue body  Fri, 09 Jul 2021 02:16:04 GMT

Comment on issue at Fri, 09 Jul 2021 02:16:06 GMT


update elasticsearch to 5

https://github.com/mobz/elasticsearch-head#running-with-built-in-server
– for Elasticsearch 5.x:
site plugins are not supported. Run elasticsearch-head as a standalone server

Running as a standalone comes with a security risk.
"your cluster is open to cross origin from anywhere."

check out this setup and see if we can use something similar: https://hub.docker.com/r/blacktop/elastic-stack/

es5 is not stable, so leaving at es2 for now.


Add bottom border to toolbar for One Light/Dark UI themes

At some point in time, Atom's bottom bar became full width.
This caused the toolbar to look like this when using One Light/Dark UI themes:

Please look at the lack of a bottom border on the toolbar.
With a border it looks like this (much better in my opinion):

The style used to add the border (although I'm sure you don't need it, just adding it for completeness):
// Styling for one-dark/light-ui theme
.theme-one-dark-ui, .theme-one-light-ui {
  // Add border bottom to vertical tool-bar
  .tool-bar.tool-bar-vertical {
    border-bottom: 1px solid @base-border-color;
  }
}

Thanks for reporting, this will be fixed in the next release.


2FA support

I'd like to know if you can use gcli authorize and 2FA.  It doesn't seem to be the case.  I can manually create an OAuth token but I thought it would be nice to have.

@hkim823 workaround didn't work for me. Is there no plan to update this? Many companies require 2FA now and I'd like to use this tool.

@AndrewHuffman There is a plan to update this library but it is low on the priority list. I'm currently really focused on the tty gems and their ecosystem and as a sole OSS developer I have limited time as to what I can achieve. The last time I released this lib was 2013 and I cannot see getting round to releasing new version any time soon. I want to be as honest as possible as to when rewrite of this lib may happen. However, if you decide to submit PRs and get to work on it then we may stand a chance releasing something sooner.

@piotrmurach I fully understand. I'll fork and see how quickly this work could be done and hopefully contribute back. This CLI tool was the only one I found that also supported gists and thus my desire to use it.
Thanks for your explanation & contributions!

I just noticed your [https://github.com/piotrmurach/github](github API) repo, and it appears to support 2FA. I presume this is on an out dated API?

@AndrewHuffman The github_api gem is definitely kept current and should work with 2fa via token param. If I were you I would probably start by going through api calls and add/remove/update them one by one. Each endpoint should have a corresponding spec as well. If you submit any PRs my preference would be to do it in small chunks, easier to review and merge.


June Heartbeat draft

I am working on a picture for the blog. Edits welcome!

@shcheklein think I got all the revisions and added a header. feel free to merge tonight, since i'll share on social tomorrow!

@shcheklein I shrunk down the header to 1600 px on the long axis- let me know how it looks to you. Also, the next biggest image is the spongebob meme; it's ~560x800 px. Let me know if you think that should get shrunk too?

@andronovhopf yep, looks good, but try to run them through the https://tinypng.com/ please.


[FEATURE] Improvements and bugs in search bar

If I enter a username with spaces the user they don't come up in results
Cannot search based off types, which is what I would see the majority of people trying this for

I'd consider removing the search bar if some of these are difficult or take a bit of time to add

Let's break this one up into two independent issues.


Have status effects panel operate on all controlled tokens

This actually works out quite cleanly:

If no token is controlled, right-clicking on a token also controls it.
Right-clicking any token among a set of controlled tokens maintains the controlled status of all tokens.
If a token isn't among those controlled when right-clicking it, controlled tokens are cleared, and the right-clicked token is then controlled.

Not a bad idea! Though I can imagine it getting a little hairy if one token has frightened one and then you click on another token (which by default in foundry doesn't deselect the first one) also apply frightened to that one, thus making the original token frightened 2.

By default in Foundry it does deselect the first one.

I remember it used to work that way without left click deselect, but I guess that's been changed. Neat, then this shouldn't cause any issues!


SDK freezing on importing a blender model

I'm trying to import a model generated using the procedural spaceship generator (discussion here: https://hub.jmonkeyengine.org/t/procedural-spaceship-generator-in-blender/36198).
Convert to j3o and view model produce basically the same freeze. The loading procedure seems normal until it tries to load the normal map and pops up a warning "The texture coordinates type is not supported: TEXCO_GLOB. The texture 'Normal Map'".  After restarting the SDK the j3o is there but without textures.
Now the problem lies here: the texture coordinates once really were global, but I changed them to UV (well, I tried pretty much everything). SDK still says that they are global. What's going on? Is SDK using some old copy or might the spaceship generator keep overriding my fixes?

Regarding old texture mappings:
I changed them in one material but not the other :facepunch:
However I think that SDK shouldn't freeze for that.
Also OS details: Ubuntu 15.10 32 bit

I was using version 3.1-beta1-SNAPSHOT (github relase). Triangulate modifier was applied, but SDK still didn't like it...
Later it started to complain about Java heap memory error...

docs/reporting_issues.md states that you should supply your model :stuck_out_tongue:
Also try the xbuf release since that triangulation/log spam fix occured after beta1, maybe it's still the same issue but spamming when it doesn't like blenders triangulation or something.
As for heap, you have to look into the wiki: SDK: Increasing Heap Memory, this happens mostly when your Textures are simply big

I'm closing this for now because of inactivity. If this issue is reproducable on any model feel free to post it here.
As a next step it would be good to see what happens when loading the same model as a regular jme project, to see if it is only sdk related or maybe some endless loop inside of the blender/xbuf importer.


libplacebo: Take out glslang patch not needed after #94049

From some reason, if we take this patch out, libplacebo builds fine, and
mpv is again usable.

Motivation for this change
Make libplacebo build again after #94049.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Did you intend to close this?