Channel Maps

Replaces #195 as a tool for making channel maps in a grid

Example:
cube = SpectralCube.read('/Users/adam/work/w51/alma/FITS/longbaseline/velo_cutouts/w51e2e_csv0_j2-1_r0.5_medsub.fits')
subcube = cube.spectral_slab(16*u.km/u.s, 87*u.km/u.s)

norm = vis.ImageNormalize(subcube,
                          interval=vis.ManualInterval(-0.01, 0.1),
                          stretch=vis.LogStretch())

fig = pl.figure(1, figsize=(18,18))
subcube.plot_channel_maps(5, 5, np.arange(25), norm=norm,
                          cmap='gray_r',
                          fig=fig,
                          contourkwargs=dict(
                          levels=[0.02,0.04,0.06,0.08,0.1,0.125,0.15],
                          colors=['w']*10,
                          linewidths=[0.5]*10,)
                         )

Coverage decreased (-0.5%) to 76.903% when pulling 4c939660de6bc6a6fc3c804a6b51f342e1d3a3c0 on keflavich:channel_maps into 42047837ef59f646a7519e82562bcafd5ad0d5f0 on radio-astro-tools:master.

Open question: how do we force a tight layout (no whitespace horizontally or vertically between figures) without forcing a particular figure size?  This is definitely possible, but every stackoverflow question shows how to "work around" the issue by forcing a specific figure size, which I have defined here as not an acceptable solution, and the matplotlib gallery shows a bunch of examples that are incompatible (afaict) with projection=.
@astrofrog, any ideas?  You've probably dug into this as much as anyone.

Nico added some suggestions about tightening the layout, it now looks like this:

I've pseudo-automated the color selection for labels, but there ought to be a much better way to do this (e.g., https://gamedev.stackexchange.com/questions/38536/given-a-rgb-color-x-how-to-find-the-most-contrasting-color-y) that should be incorporated into matplotlib, I'd think.
Do we want to auto-add ra/dec labels of some sort?  We need to add colorbar.

:+1:  RA/Dec labels along the edges seem like a good default.

how should we decide on the labels?  Does astropy have a mapping from wcstype -> conventional label?  It should... I just don't know immediately

I'd suggest setting a default color for the velocity/frequency labels because the colormap also has a default. E.g. red labels will work on any grayscale map.
Imho: If you want to set another cmap yourself, it's your problem to find a matching overlay color.

regarding this: fig.subplots_adjust(margin,margin,1.-margin,1.-margin,0.,0.)
Interesting to see that it works without setting the figure margins explicitly. For my tests, I had to force equal margins around the grid. This might depend on the default margins in matplotlibrc.

tight_layout breaks the alignment of the panels and needs to be removed.
savefig(... bbox_inches='tight')still works though and crops some whitespace.

hm, both with and without tighten=True look the same for me.  Maybe this is backend-dependent?  That would suck.
axes = cube.plot_channel_maps(3,3,np.arange(0,80,9), output_file='test.pdf', tighten=False, savefig_kwargs={'bbox_inches':'tight'})
axes = cube.plot_channel_maps(3,3,np.arange(0,80,9), output_file='test_tightened.pdf', tighten=True, savefig_kwargs={'bbox_inches':'tight'})

Maybe. I've used Qt5Agg for my tests.

Ready to merge if we can get tests passing; see #558


Use hard-coded SDK path for system module map

We've been down this path before. Unfortunately, /usr/include/sqlite3.h isn't reliably available on all Macs. Because module maps don't yet have dynamic support (something that the Swift Package Manager intends to have solved soon), we need to hardcode the SDK path (or use a script to substitute it).
Fixes #319.
@mikemee Thoughts?

Let's  try it. I don't know if everyone has this installed either, but likely a better bet as we know now that the other is not universal.

On 11 Jan 2016, at 5:47 AM, Stephen Celis<EMAIL_ADDRESS>wrote:
We've been down this path before. Unfortunately, /usr/include/sqlite3.h isn't reliably available on all Macs. Because module maps don't yet have dynamic support (something that the Swift Package Manager intends to have solved soon), we need to hardcode the SDK path (or use a script to substitute it).
Fixes #319.
@mikemee Thoughts?
You can view, comment on, or merge this pull request online at:
https://github.com/stephencelis/SQLite.swift/pull/320
Commit Summary
Use hard-coded SDK path for system module map
File Changes
M SQLite3/module.modulemap (5)
Patch Links:
https://github.com/stephencelis/SQLite.swift/pull/320.patch
https://github.com/stephencelis/SQLite.swift/pull/320.diff
—
Reply to this email directly or view it on GitHub.

@mikemee Yeah, I think we can make standard Xcode installation a requirement (in lieu of a better way for the moment).

Don't forget to tag to 0.9.1 to keep carthage happy. Not sure if cocopods updates automagically or not. Probably should add that to the makefile later if not.

CocoaPods depends on the branch, too, so we'll be good to go :)

Very nicely done!
You also removed my CocoaPods hackery by adding the missing (oops!) APPLICATION_EXTENSION_API_ONLY and setting fts3_tokenizer.h private (as you'd previously suggested but I misunderstood by trying it in the Xcode file not the pod file). That all seems to have allowed CocoaPods to do it's thing correctly (I take back all those things I said about it 😎), which nicely gets everything back into alignment and also removes the warning (I'm guessing).

@mikemee The warning actually went away when I removed the SQLite.swift module.modulemap file. I'm not sure what's different with the module map Xcode generates, but it seems to have killed that warning! :)
As far as the private header goes, I just wanted to make sure it wasn't exposed externally to CocoaPods consumers.

Some combination of the two I suspect.  I didn't have the module.modulemap file originally and only added it when I couldn't make CocoaPods happy. However, in hindsight, CocoaPods probably wasn't happy because the ..API_ONLY wasn't set (though I'm surprised Xcode wasn't upset without that).
Anyhow, the great thing is that it is all much improved now!

What is a big deal about APPLICATION_EXTENSION_API_ONLY? By reading to https://developer.apple.com/app-extensions/, I am curious why Database needs to access it.

@iNoles I enabled it so that SQLite.swift can be used in Today/Watch/etc. extensions.

Hmm, now that you've given me that link @iNoles, I realize I was confusing it with the other magic Xcode setting that says "This is a framework, not an app". (Which I've just gone looking for but haven't found yet...)  Sorry about the confusion.


Target and area

main points
Using the halo target selector for elements in an area does not work. Only the area itself is selected

@darth-cheney i played around with this some looking into event.target, event.originalTarget etc etc   It's not clear to why one is prioritized over the other when you have children in an area. It doesn't not seem deterministic
there is some 'first come first serve' dynamic; if you move a subpart to the area border then it's more likely to be selected..
not sure what to do here really.


:sparkles: CI plugin

Description
Add a plugin for CI projects
Test Coverage

[ ]  This change is covered by existing or additional automated tests.
[ ]  Manual testing has been performed (and evidence provided) as automated testing was not feasible.
[x]  Additional tests are not required for this change (e.g. documentation update).

Codecov Report

Merging #51 (4b8fd91) into main (45408a0) will increase coverage by 0.44%.
The diff coverage is 65.11%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
+ Coverage   68.31%   68.76%   +0.44%
==========================================
  Files          44       45       +1
  Lines        2348     2388      +40
==========================================
+ Hits         1604     1642      +38
- Misses        744      746       +2

Impacted Files
Coverage Δ

continuous_delivery_scripts/__init__.py
100.00% <ø> (ø)

continuous_delivery_scripts/assert_news.py
54.11% <ø> (ø)

continuous_delivery_scripts/create_news_file.py
48.00% <ø> (ø)

continuous_delivery_scripts/generate_docs.py
79.41% <ø> (ø)

continuous_delivery_scripts/generate_news.py
42.50% <ø> (ø)

continuous_delivery_scripts/get_config.py
0.00% <ø> (ø)

continuous_delivery_scripts/get_version.py
0.00% <ø> (ø)

continuous_delivery_scripts/language_specifics.py
100.00% <ø> (ø)

continuous_delivery_scripts/license_files.py
77.19% <ø> (ø)

continuous_delivery_scripts/plugins/__init__.py
100.00% <ø> (ø)

... and 35 more


Fix: Challenge Description

Changed the word world to other on category Permissions, challenge chmod. o comes from other.
Also fixed exexute to execute a few lines above.

Wow... Decades of Linux later, and TIL... Thank you!


Abstract body tracking API

Same as PR #21 from sxrsdk
GVRBodyTracker class
GearVRf DCO signed off by: Nola Donato<EMAIL_ADDRESS>

Oh yeah it needs changes too. I will do a PR against demos.


Subscriptions not Appearing in AntennaPod after Sync.

Describe the bug
Sucessfully did a sync in AntennaPod using local ip addess (so no domain) of PodFetch docker instance.Sync completes with a sucess message. However nothing appears inside the app on the Home or Subscriptions page. I have several podcasts in PodFetch.
Reproduction
Setup new instance of Podfetch.
Subscribed to Podcast with RSS feed.
Connect to local IP of Podfetch container in AntennaPod
Nothing appears in subscriptions page of AntennaPod
System Info
System: Unraid 6.12.3

Used Package Manager
n/a
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

That is expected behaviour. I had to set them up separately. If another user wants to connect to AntennaPod he/she would download everything that the administrator downloads to PodFetch. That is why PodFetch and AntennaPod podcasts are separate identities. You can download them independently. But if the listening history matches it syncs in both ways.
This enables all users to have different podcasts on their phones but still sync to PodFetch.

Ok. There doesn't seem to be any documentation that explains this either on this repo or the AntennaPod repo unless I missed it (which is very possible). If there isn't anything written my suggestion would to be to add something to the bottom of this page

Thanks. I added a note at the bottom.


cythonizing forward

Wanted to share this with you to get a sense of the opportunities for speedup. This is not something you probably want to merge.
   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
     4391    0.718    0.000   58.747    0.013 pyhacrf.py:124(predict_proba)
     4391    0.255    0.000   52.379    0.012 pyhacrf.py:326(__init__)
     4391   33.744    0.008   52.124    0.012 pyhacrf.py:385(_build_lattice)
     4390    0.045    0.000    5.565    0.001 pyhacrf.py:356(predict)
     4390    0.122    0.000    5.267    0.001 pyhacrf.py:362(_forward_probabilities)
     4390    0.007    0.000    5.142    0.001 pyhacrf.py:376(_forward)
     4390    5.134    0.001    5.134    0.001 {pyhacrf.algorithms.forward}
     4391    0.005    0.000    3.314    0.001 pyhacrf.py:275(fit_transform)
     4391    0.008    0.000    3.309    0.001 pyhacrf.py:291(transform)
     4391    2.506    0.001    3.302    0.001 pyhacrf.py:307(_extract_features)

If we changed alpha from a dict to a numpy array.
     3059    0.324    0.000   41.912    0.014 pyhacrf.py:124(predict_proba)
     3059    0.217    0.000   40.386    0.013 pyhacrf.py:326(__init__)
     3059   25.773    0.008   40.169    0.013 pyhacrf.py:385(_build_lattice)
     3059    0.005    0.000    2.604    0.001 pyhacrf.py:275(fit_transform)
     3059    0.007    0.000    2.599    0.001 pyhacrf.py:291(transform)
     3059    1.958    0.001    2.592    0.001 pyhacrf.py:307(_extract_features)
     3058    0.046    0.000    1.130    0.000 pyhacrf.py:356(predict)
     3058    0.112    0.000    0.881    0.000 pyhacrf.py:362(_forward_probabilities)
     3058    0.006    0.000    0.766    0.000 pyhacrf.py:376(_forward)
     3058    0.759    0.000    0.759    0.000 {pyhacrf.algorithms.forward}

In the pure prediction case, we don't need to track 'edge nodes' so, alpha can just be a
cdef np.ndarray(double, ndim=3) alpha = numpy.empty_like(x_dot_parameters)
alpha.fill(-np.inf)

We only need another 10x speed improvement, then this will be usable in dedupe. Very exciting!

Thanks Forest, this is wonderful!
Since I don't have much experience optimizing python like this, can you maybe explain why the first change works?

So if cython knows the variable type for variables, it can compile more of the code to C. Because numpy.arrays are already typed, cython can make fast C code out of anything that uses them, if you fully declare what types of variables the array will contain.
Using the dictionary slows the code down, because python dictionaries can contain a heterogeneous mix of variable types. Cython actually calls cPython for getting and settings of dict variables.
Finally, cython has some pure C versions of numpy.math functions, which is what I'm getting by doing numpy.math cimport logaddexp
A really useful tool for optimizing cython is the cython annotation mode: http://docs.cython.org/src/quickstart/cythonize.html#determining-where-to-add-types

Thanks that is very helpful, especially the -a switch.

@fgregg I should have tested this before merging, but I can't build the project now using python setyp.py build_ext --inplace. Guess it has something to do with https://github.com/datamade/pyhacrf/commit/e187a21b0a01e1a38e36c0b2f9e7887a5e5299d9#diff-2eeaed663bd0d25b7e608891384b7298R7 but the link seems to be broken. How are you building?

Run 'cython pyhacrf/algorithms.pyx' the run build_ext
On Fri, May 22, 2015 at 1:34 AM dirko<EMAIL_ADDRESS>wrote:

@fgregg https://github.com/fgregg I should have tested this before
merging, but I can't build the project now using python setyp.py
build_ext --inplace. Guess it has something to do with datamade@e187a21
#diff-2eeaed663bd0d25b7e608891384b7298R7
https://github.com/datamade/pyhacrf/commit/e187a21b0a01e1a38e36c0b2f9e7887a5e5299d9#diff-2eeaed663bd0d25b7e608891384b7298R7
but the link seems to be broken. How are you building?
—
Reply to this email directly or view it on GitHub
https://github.com/dirko/pyhacrf/pull/3#issuecomment-104537409.

To expand on that a little bit, I hacked this up because I wasn't sure how to pass the npymath library arguments to cythonize (that's what **get_info('npymath')) is doing, but I knew how to pass the argument as an extension.
That said, I do use the pattern in my cython/numpy for the following reasons.

Cython is a heavy dependency. I build the c files myself when I'm ready to make a distribution release and they will be included with python setup.py sdist.
I try to avoid numpy as a top level dependency of the setup.py file. If the user doesn't have numpy, then python can't read the rest of the setup.py file and provide useful informatoin to the user. The whole point of NumpyExtension is to encapsulate the numpy dependency so all users can run setup.py.

Seems reasonable - I'll just add something on the readme.
When I now first run cython pyhacrf/algorithms.pyx I get:
Error compiling Cython file:
------------------------------------------------------------
...
            i0, j0, s0, i1, j1, s1, edge_parameter_index = node  # Actually an edge in this case
            # Use the features at the destination of the edge.
            edge_potential = (x_dot_parameters[i1, j1, edge_parameter_index]
                              + alpha[(i0, j0, s0)])
            alpha[node] = edge_potential
            alpha[(i1, j1, s1)] = logaddexp(alpha.get((i1, j1, s1), -np.inf),
                                          ^
pyhacrf/algorithms.pyx:27:43: Call with wrong number of arguments (expected 1, got 2)

Something to do with the numpy version maybe?
When I change logaddexp(...) to logaddexp((...)) the cython command completes successfully but  setup.py build_ext returns:
pyhacrf/algorithms.c:1762:62: error: too few arguments to function call, expected 2, have 1
      __pyx_t_6 = PyFloat_FromDouble(npy_logaddexp(__pyx_t_27)); if (unlikely(!__pyx_t_6)) {__pyx_filename = __pyx_f[0]; __pyx_lineno = 27; __pyx_clineno = __LINE__; goto __pyx_L1_error;}
                                     ~~~~~~~~~~~~~           ^
~/anaconda/lib/python2.7/site-packages/numpy/core/include/numpy/npy_math.h:305:1: note: 'npy_logaddexp' declared here
double npy_logaddexp(double x, double y);
^
1 warning and 1 error generated.

Any ideas?

There was a bug in cython that was fixed in cytho 22.
On Mon, May 25, 2015 at 7:09 AM dirko<EMAIL_ADDRESS>wrote:

Seems reasonable - I'll just add something on the readme.
When I now first run cython pyhacrf/algorithms.pyx I get:
Error compiling Cython file:
...
i0, j0, s0, i1, j1, s1, edge_parameter_index = node  # Actually an edge in this case
# Use the features at the destination of the edge.
edge_potential = (x_dot_parameters[i1, j1, edge_parameter_index]
+ alpha[(i0, j0, s0)])
alpha[node] = edge_potential
alpha[(i1, j1, s1)] = logaddexp(alpha.get((i1, j1, s1), -np.inf),
^
pyhacrf/algorithms.pyx:27:43: Call with wrong number of arguments (expected 1, got 2)
Something to do with the numpy version maybe?
When I change logaddexp(...) to logaddexp((...)) the cython command
completes successfully but setup.py build_ext returns:
pyhacrf/algorithms.c:1762:62: error: too few arguments to function call, expected 2, have 1
__pyx_t_6 = PyFloat_FromDouble(npy_logaddexp(__pyx_t_27)); if (unlikely(!__pyx_t_6)) {__pyx_filename = __pyx_f[0]; __pyx_lineno = 27; __pyx_clineno = LINE; goto __pyx_L1_error;}
~~~~~~~~~~~~~           ^
~/anaconda/lib/python2.7/site-packages/numpy/core/include/numpy/npy_math.h:305:1: note: 'npy_logaddexp' declared here
double npy_logaddexp(double x, double y);
^
1 warning and 1 error generated.
Any ideas?
—
Reply to this email directly or view it on GitHub
https://github.com/dirko/pyhacrf/pull/3#issuecomment-105222790.


Three digit T codes causes unhandled exception

T codes using numbers larger than 99 cause a program fault.
Examples:
T88 - result OK
T300 - unhandled exception
Steps to repro: Send a three digit T code via mdi or file read.
************** Exception Text **************
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at GrblPanel.GrblGui.showGrblStatus(String data)
at GrblPanel.GrblIF.raiseAppSerialDataEvent(String data)
at GrblPanel.GrblIF.VB$StateMachine_40__client_ComReadData.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
----------------------------------------"

I will add Error 38 text but Grbl will still spit back:
"38","Invalid gcode ID:38","Tool number greater than max supported value."

Fixed missing error message


Minify CSS

Didn't do much, just minified the CSS and saved 4 KBs.

Thank you! I agree that a minified version is something Tufte CSS should have.
I'm still deciding how best to achieve that long-term. Generally I'm opposed to added tooling such as proposed in #122, but I'm also not excited about an error-prone (or at least forget-to-do-it-prone) manual process.
So, this won't get merged or closed right away, but I am thinking about it. Again, thank you for your contribution. :)

I decided to go with a manual strategy using clean-css. Thanks for this PR; you really motivated me to finally do this. Cheers.


[release-1.6] Update base image

Update base image. Manual cherry-pick of #25282 since the base image tag differs across releases.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ericvn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
44e036692e732783f437aa12a96dcd44aee6b8b1
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


DC Connected battery and gid outages

Run parametrics in attached SAM project file - one case dc connected and one case ac connected.
No annual output shown for dc case
base case has undersized battery and shows same system output in heat map on summary page but no annual output.
I can’t tell what’s meeting the critical load at night. The inverter efficiency appears to drop to zero at night, and with a two hour battery there shouldn’t be enough power to meet the critical load anyway.
Changing the parameters such as inverter efficiency cutoff and re-sizing the system doesn’t fix the problem.
Based on that, the issue is either in the inverter model or in the post-battery loss accounting for DC connected systems.
MiniGrid.zip

Fixed in #725


Ability to upload maps to dropbox

Is your feature request related to a problem? Please describe.
Users will be able to export the Kepler.gl file onto their Dropbox user account.
Describe the solution you'd like
When users export their configuration and data, they will have the ability to choose Dropbox as destination. Users must authenticate against Dropbox before they could perform the saving action.
Auth Flow
It is important to remember that Kepler.gl doesn't require a back end server to run on therefore all

User click on export map in the current Tab (aka parent tab)
User will click on auth button which will redirect the user to dropbox by opening a new tab/window (aka child tab)
The parent tab will subscribe to local storage events (required for other steps)
After a successful login, dropbox will redirect the user to kepler.gl/#/auth which will read the auth token provided by dropbox and store in the local storage always remaining the child tab.
The child tab will automatically close after storing the token.
The parent tab will receive the storage event and will read the auth token from local storage which will be used to upload and store the file in Dropbox.

The above flow will allow users to work on their map and perform the Dropbox auth without losing their current work. If we were to log users on the same tab where they are performing their mapping they would lose their work completely because the app would reload completely after the auth process
Constraints
It looks like OAuth 2 protocol does not accept callback URIs with fragments, e.g. /#/demo. This could be an issue for our demo instance since we are running on github pages and the hash sign is required.
I will look for a possible solution.
Describe alternatives you've considered

Google Drive: not available everywhere
Box: their APIs are not as easy as Dropbox ones

Additional context
New UI is required

Slight change to the implementation, In order to pass a token from child tab to the parent one we are now using the message feature and then storing the auth token into local storage


make normative statements more useful in isolation

There is probably more than can be done, but here are a few nits I picked.

remove pronouns that become ambiguous when statements are used in isolation
break up compound statements

:+1: thank you @bobholt. Will you be updating the normative statements as well?

I will, should either land @tkellen.


Tasmota Charger - Enable Multi-Relay Devices

Refer to #3367

@andig
PR tested successfully by @sveba: https://github.com/evcc-io/evcc/issues/3367#issuecomment-1127348842


Add a test to verify batched dispatches result in a single render

Test file may need renaming/relocating.
Test does two separate rtl.act wrapped dispatches to verify that they result in 2 renders then repeats this wrapped in batch.

@markerikson I thought I'd have a crack at this. batch looks good to me. Let me know what changes I need to make, or if I've missed the mark completely.

Seems like a good first check at behavior.
Left one edit request for the code structure.
Also, could you add a second test for the alternate-renderers entry point? something like:
import {batch as defaultBatch} from "../../../something/alternate-renderers";

// later
defaultBatch(() => {
    dispatch(increment())
    dispatch(increment())
})

expect(numberOfRenders).toBe(2)

I see what you did there.. that something is more elusive than expected.
import { Provider as ProviderMock, batch, connect } from '../../src/index.js'
import { batch as defaultNoopBatch } from '../../src/alternate-renderers.js'

Cannot find module '../../src/alternate-renderers.js' from 'batch.spec.js'

tests indicate that defaultNoopBatch is just as effective as the real thing.. I'm guessing the tests are flawed.

copying the defaultNoopBatch function into the test and removing the import showed it worked as expected so with the combined tests/imports it seems the defaultNoopBatch was actually the real thing. Splitting the tests into separate files has resolved this.

Should we be testing the render props are as expected, or is that out of scope?
eg
      expect(componentSpy).toHaveBeenLastCalledWith(
        {
          bar: 2,
          dispatch: store.dispatch,
          foo: 2
        },
        {}
      )

Is this dead?

I'm happy to make changes if needed, I was just waiting for feedback.

I'll try to look at this over the weekend

Hey @lecstor, I'm going to close this out since it's gotten a bit messy. Feel free to reopen it with a fresh branch and I'll take a look ASAP.


Add option to set the loglevel of npm

https://docs.npmjs.com/misc/config#loglevel
Some modules output way too much information. If I could set the loglevel to "silent" would be amazing :)

Use the new args option for this. (thanks to #29)


Make sure Hugging Face download stats work, better discoverability #168

Dear authors,
Thanks for this nice work! I wrote a quick PoC to showcase that you can easily have integration with the 🤗 hub so that you can automatically load the various VisionLSTM models using from_pretrained (and push them using push_to_hub), track download numbers for your models (similar to models in the Transformers library), and have nice model cards on a per-model basis. It leverages the PyTorchModelHubMixin class which allows to inherits these methods.
Usage is as follows:
from vision_lstm import VisionLSTM

model = VisionLSTM.from_pretrained("nx-ai/vil-tiny")

# optionally, one can push a trained model to the hub
model.push_to_hub("nx-ai/vit-tiny-finetuned")

This means people don't need to manually download a checkpoint first in their local environment, it just loads automatically from the hub. I've pushed a demo model here for now: https://huggingface.co/nielsr/vil-tiny. We could move all checkpoints to separate repos to an organization on the hub or your personal user account if you're interested.
See also this Colab notebook for basic usage.
Would you be interested in this integration?
Kind regards,
Niels

Hi @BenediktAlkin is there any interest in this?


Certificate Validation failing

Hi Thank you for your response for the earlier issue.
I have one more question, I want to validate the server certificates at client side, So I enabled validate_certificates as True in client side while creating DTLSConfiguration but I receive errors: mbedtls.exceptions.TLSError: TLSError([0x2700] 'X509 - Certificate verification failed, e.g. CRL,
CA or signature check failed').
I have used the same CA certificate created by server in client.
Can you please help what I might be doing wrong in the process.
Originally posted by @Souravkumar2434 in https://github.com/Synss/python-mbedtls/issues/121#issuecomment-2330607904

Hi, I apologize but I cannot offer that kind of support. You may want to try a different support channel such as stack overflow.


Pass Variables via URL string

Currently variable URL strings are ignored with PKPass, has anyone resolved this? So that URL variables can be passed to make generation of passes easy for end users.
For example:
www.example.com/pass/?name=John&barcode=12345
Which can then fill the required fields to generate dynamic passes automatically.

Hi there, have a look at this example to see how to use GET or POST parameters to make your pass dynamic:
https://github.com/tschoffelen/php-pkpass/blob/master/examples/starbucks_sample/index.php#L29
This example uses $_POST, but it is of course easy enough to replace that by $_GET to access the URL parameters.

Cool thanks for that, that sort of covers part of what I'm wanting to do.
However I was more wanting the URL parameters to pre-fill the text input fields, so say a user wanted to edit their pass to update their name for example.
So sending the data in the URL would pre-fill the text fields, but still allow them to edit any of the pre-filled fields before creating the pass?
Also one other thing I've not been able to solve for, is using hyperlinks for the backfields on the back of the pass. Whenever I add hyperlinks the PHP won't load, it just crashes.
I'm wanting to add the hyperlink as an option on the back of the pass as "Update Pass" option, which takes them to the above mentioned dynamic URL with the variable parameters.

Both of these things seem more like general PHP questions than anything related to this library, so it might be better to just do some googling or search on Stack Overflow.

Yeah was more so if someone had already resolved these issues and was planning a pull, especially around hyperlinks in the PHP code, which are outlined in Apple's pass developer documenation, if any of these have spaces or special characters being passed through variables, the PHP crashes.
I've made the changes to the PHP code to allow both variables to auto generate and populate text fields, so I'll close off this issue.


fix(workflow): fix sleep logic

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1084  👈
#1083
#1078 : 1 other dependent PR (#1079 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


remove skipDocumentsValidation from near-operation-file

This field is no longer needed as the proper fix was introduced in
7c60e5accb.
Description
In 2019 dotansimha/graphql-code-generator#2143 lead to 1559ab6820. This resulted in typechecking being disabled for near-operation-file presets.
Since that change the ability to toggle this setting was introduced in: 7c60e5accb.
Running the same tests from dotansimha/graphql-code-generator#2143 it should now be possible to remove the default disable of typechecking for near-operation-file preset.
Typechecking is important and should be enabled by default.
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Related dotansimha/graphql-code-generator-community#214
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

This has been tested using the following repo to run the tests here: https://github.com/klyve/graphql-codegen-preset-test

Test Environment:

OS: macOS
NodeJS: 16.16.0
@graphql-codegen/near-operation-file-preset: 2.4.1 + change
@graphql-codegen/cli: 2.11.5
@graphql-codegen/introspection: 2.2.1
@graphql-codegen/typescript: 2.7.3
@graphql-codegen/typescript-operations: 2.5.3
@graphql-codegen/typescript-react-apollo: 3.3.3

Checklist:

[X] I have followed the CONTRIBUTING doc and the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

@klyve, thank you for your raising this concern!
I've pushed a more conservative alternative, let me know what you think 👀

I agree with the change you have pushed. It's a way more conservative fix to the problem, thanks 👍

@klyve, thank you for your raising this concern!
I've pushed a more conservative alternative, let me know what you think 👀

I agree with the change you have pushed. It's a way more conservative fix to the problem, thanks 👍 Might want to re-add the test / enable the ability to change this through preset options?

I agree, we should restore the test and enable changing it through the presetOptions
Thanks

Hi!
All community plugins (see list below) have been moved to a new dotansimha/graphql-code-generator-community.

Community plugins:

@graphql-codegen/typescript-react-apollo
@graphql-codegen/typescript-graphql-request
@graphql-codegen/typescript-apollo-angular
@graphql-codegen/typescript-apollo-client-helpers
@graphql-codegen/typescript-react-query
@graphql-codegen/typescript-urql
@graphql-codegen/named-operations-object
@graphql-codegen/urql-introspection
@graphql-codegen/flow-resolvers
@graphql-codegen/typescript-vue-apollo
@graphql-codegen/typescript-rtk-query
@graphql-codegen/flow-operations
@graphql-codegen/typescript-msw
@graphql-codegen/typescript-mongodb
@graphql-codegen/typescript-type-graphql
@graphql-codegen/jsdoc
@graphql-codegen/typescript-vue-urql
@graphql-codegen/kotlin
@graphql-codegen/typescript-vue-apollo-smart-ops
@graphql-codegen/java
@graphql-codegen/c-sharp-operations
@graphql-codegen/hasura-allow-list
@graphql-codegen/typescript-stencil-apollo
@graphql-codegen/relay-operation-optimizer
@graphql-codegen/typescript-oclif
@graphql-codegen/java-resolvers
@graphql-codegen/java-apollo-android
@graphql-codegen/flutter-freezed

Please move your PR by following these steps:
From your current PR branch:

git remote add codegen-community git@github.com:dotansimha/graphql-code-generator-community.git
git fetch codegen-community
git push codegen-community

Open the PR on dotansimha/graphql-code-generator-community and close this PR.
Thank you!

was merged https://github.com/dotansimha/graphql-code-generator-community/pull/383


Add agent and map tests for 'NavigationServer3D'

This commits fixes a bug in free() function as well.
This is just another PR which is part of https://github.com/godotengine/godot/issues/73132 activity I'm performing to properly cover the navigation area with tests.

Thanks!


Fixed vulnerabilities by upgrading dependency versions

I upgraded node-gyp and mocha to fix 1 critical and 2 high security vulnerabilities.
The older version of node-gyp was using an old version of tar, where a vulnerability was discovered recently.
And mocha had 1 critical and a few medium vulnerabilities.
All tests past after the dependency upgrade.
@zhm would appreciate it if you could review and accept if the change looks good.  The pg-query-walker npm module that I maintain depends on this module.

Thanks! A new version has pushed that includes the latest versions of these dependencies.


rtt_resend_factor

https://github.com/cBournhonesque/lightyear/blob/303a2f00201a0e55bdd84fb940e955ee47387187/lightyear/src/channel/builder.rs#L199
Docs say this is a Duration. Is this wrong? It's an f32.

Yea docs are wrong, its a factor, not the actual duration

Yep, it's a multipler of the current RTT estimate, the docs need to be updated


Support for poetry, pipenv

Check for existing issues

[ ] Completed

Is your feature request related to a problem?
Primary issue: #205
This issue answers the core venv structure, but displays problem with real build tools. Problem in build tools, that are used with python development. In python development we have:

Pipenv
Poetry
Original pip

All of them creating virtual environment, that Zed doesn't see. And there is no option to activate any of them. I read through the issue, that I mentioned, but there is still no decision about that. Manual configuration in config folder doesn't seem like good decision at all.
Describe the solution you'd like
I think that there is three ways of solution. There is no way of configuration, I see only hard wrap around these tools.
Solution through confing file
Maybe here need to add documentation about manual configuration through the file of workspace. I think, that We need in something like
// .zed/settings.json
{
  "python": {
    "venv": "$HOME/.venv/pretty-project-52331fds/",
    "tool":  "pipenv" //  | "poetry" | "pip"
  },
  ...
}

This is might be useful in any cases. This could help with fast loading of workspaces and sharing configuration with teammates.
Solution through selecting with menu
See mockups in bottom section. Selecting through menu might be more user friendly than manual configuration.
Just selecting item
See mockups in bottom section. I would like to see this way also. It is also good approach of how to activate virtual environment.
If applicable, add mockups / screenshots to help present your vision of the feature
Example of UI with selecting of env

Selecting Python tool

I forgot to mention solution, that might help for developers of Zig. I don't know the API of the application, but suggest this code to work fine, I guess.
For Tools I suggest to have some sort of wrap, that might be helpful. You possibly need to wrap all of them in such way:

#[derive(Debug)]
struct Pipenv implements LanguageTool {
  pub fn loadLibraries(ctx: WorkspaceCtx) {
    // Here goes workspace context loading with libraries
  }

  pub fn configureLSP(lsp: LanguageServer) {
    // Configure LSP
  }
}

This might work, but don't know for real or not. Probably loading of workspace tools, like additional linters, package managers and other things are not supported here, but I just guess it might work

Hey @AssertionBit, wanted to thank you for the amount of detail you put into this feature request.  I would love it if we could support Poetry.  For anyone who isn't a Python dev, Poetry to Python is what Cargo is to Rust.

It would also be helpful to to have support for miniconda, mamba, and micromamba, which are frequently used in the machine learning space.

UP


Standarization of certain terms

For example, there is not a word in Spanish for "cheatsheet". There exist some words but they are used by certain regions, (In my opinion). I was thinking of translations as "Hoja de ayuda" but I found a translator used "Hoja de trucos", which seems better to me.
Like "cheatsheet", there are other terms/words that don't have a simple translation and 2 translator could use different words. I propose to standardize some expressions looking for the consistency across all the material.

I agree. Maybe we can take a look at the French translation done by the authors. For example, we can see that neither "Dropout" or "Cross-entropy" are translated (to mention some).

For 'cheatsheet' -> "Hoja de referencia"
Please, vote to agree with the term.


Add delegate for ReadToken similar to SignatureValidator

Customers that have legacy code or who want to apply different configuration for tokens could use this delegate to read the token once, obtain the correct policy and proceed with validation.

Is available in 5.x


Fix Helm chart naming

Please see the discussion here for rationale of these changes: https://github.com/habitat-sh/habitat/pull/4638

A commit message says

We'll need it to create --help string for --version CLI option in a
following patch.

Is this supposed to happen in this PR?

Is this supposed to happen in this PR?

It is, just that github messed up the order of commits. :(

Closing for https://github.com/habitat-sh/habitat/pull/4681


[CAMEL-15061] Cache failed attempts to load classes to greatly improv…

…e performance
[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

sure, waiting...

Sounds good to me, +1


The node's transform in b3dm is invalid

There are multiple grids and multiple nodes in b3dm in 3dtiles, and its transformation becomes 0, 0, 0, which is invalid

Sorry, I don't know what you mean, Can you elaborate?

The translation, rotation, and scale in the nodes node under Gltf seem to be invalid

Hi @kak0na, if possible, can you share the asset so that we can take a look into it?

https://user-images.githubusercontent.com/37468607/119425182-7cd43680-bd39-11eb-9948-90d2ef37a940.MP4
Change the suffix to 7z

https://we.tl/t-vDwajkrWcB

@baothientran

@kring

so many glTF features don't work at all！

Sorry it took so long to look at this @kak0na, but the the link above has expired. I think it's very likely this was fixed by #397, though. Please reopen this issue if you're still experiencing this problem.


feat: 🎸 add {affirm,reject,withdraw}_as_mediator to Instruction

Description
adds a set of methods to allow instruction mediators to manage their affirmation status
Breaking Changes
None
JIRA Link
✅ Closes: DA-1022
Checklist

[ ] Updated the Readme.md (if required) ?

:tada: This PR is included in version 24.0.0-alpha.11 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 24.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 24.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


💡 [Feature]: Create docs web page for this product

🎯 Aim of the feature
Every product needs a place to store documentation. Currently we use GitHub wiki for that  which is not the best pick as it is: not indexed so not searchable, the UI is not elastic and the menu may only be sorted in alphabetical order, and it may only be modified by a maintainer (it is impossible to get help from contributors to update it with a PR).
The idea is use GitHub pages and create dedicated Docs web page. Many other PnP products already have it like
https://pnp.github.io/cli-microsoft365/ or https://pnp.github.io/powershell/ or https://pnp.github.io/pnpjs/
The idea is to do something similar and use wiki only to document internal repo processes like pipeline explanation or technical related info. Everything else which is related to extension feature and guidance and usage examples should be moved to the Docs web page.
Before we go about it we need to:

First check what pages we should have? Should we just recrate what we have on wiki? so just manuals and explanation? what about examples, place for demos of specific usage scenarios, maybe some FAQ etc. Lets ask others for help to define the scope/structure of docs webpage and create separate issues for each part and start only with a basic page
Second we need to define the tech. I was thinking to use docusaurus as this is something I already use in CLI for Microsoft 365 and it is JS based with react so it is something I am familiarly with and is easy to extend but the biggest disadvantage is that it has biggest carbon footprint https://starlight.astro.build/environmental-impact/ so we should invest in some trees🌳 in exchange 😉. Previously I used MKDocs which is quite simple to use. The biggest problem is that it uses python which I have only basic knowledge off but hey. we may always learn right? Other options we may consider are: VitePress, Docus, Hugo

📷 Images (if possible) with expected result
No response
🤔 Additional remarks or comments
No response

@Adam-it I’ll do this, will share my ideas shortly 😇

@Sandeep-FED This issue is not ready to be taken.
I may only assign you to issues with label 🙏 help wanted.
This is still under prep work so I still need to think how I would like to go about it. But here I am open for discussion and suggestions (so needs discussion label) that is why it would be really awesome if you could brainstorm with me what is the best way to go about this issue, what are the ideas for doc pages, what would you like to have on such a doc page for SPFx toolkit which would be helpful for others 👍


ADT sensors not updating status

Hi,
I have the add-on set up, and I can see my entities/zones in the dashboard. All the door, window and motion sensors show up with the appropriate icons, and I'm able to arm/disarm my system.
However, the entity states are not updating at all in the addon, with the exception of the armed/disarmed status. The only way to get my door/window/motion sensors to update in the UI, is if I force a state via Developer Tools -> States.
Anything obvious I may be missing?

Are you getting any errors in the add-on log? Something like, "::TypeError: Cannot read property '1' of null"?

 I put the zones in the binary_sensor parts in all lowercase; turns out the capitalisation matters!
Once I fixed that, the sensors now work. Thanks for this great addon.

Awesome, glad to hear you got it sorted!


assert_str(null).is_equal('blabla')

The used Godot version:
Godot-3.3.2
OS including version:
Mac OS Big Sure 11.4
Describe the bug

The output from assert_str(null).is_equal('blabla') is confusing.
The diffing somehow inserts <Nu and later > in 'b<Nulabla>'
Diff is done against  **string value ** <Null> as colors shows. Same goes for a Dictionary but not for Node2D
I guess using assert_str with a non string value should not call internal _to_string().
What do you think?
Steps to Reproduce

Run the assert in a test.
	assert_str(null).is_equal('blabla')
	assert_str('apple').is_equal('blabla')
	assert_str({}).is_equal('another test')
	assert_str(Node2D.new()).is_equal('tes2ting')

Minimal reproduction project:

Hi @clemens-tolboom this is not a bug.
The string diff shows characters missing in red and matching characters in green this is the expected behavior.
Using assert_str() is only allowed for String types and using a Dictionary like in your example is not allowed and will print out an error.
For Dictionary testing you have to use assert_dict() or assert_that() where is auto typing.
This is described here https://github.com/MikeSchulze/gdUnit3/wiki/Asserts

Hmmm ... I tried to explain by silly examples. I called a function expecting a string but got null. I got confused by the stringification of the null or {}

Using assert_str() is only allowed for String types

Guess the func signature could/should then be
func assert_str(current:String,

which then gives

res://test/wp_connectTest.gd:19 - Parse Error: At "assert_str()" call, argument 1. The passed argument's type (null) doesn't match the function's expected argument type (String).

or for Dictionary

res://test/wp_connectTest.gd:19 - Parse Error: At "assert_str()" call, argument 1. The passed argument's type (Dictionary) doesn't match the function's expected argument type (String)

Thanks for your quick response :-)
I really like GDUnit but need to learn too much still :-/

Your feedback is always welcome ;)
Yes, the typing is a bit messy, since it does not allow the assignment of null values.
This is the reason why the typed asserts have no typesave argumen


Memory limits htex

Applying new options to specify memory limits per worker for HTEX.

It seems something is wrong with the travis build right now.
$ git diff --name-only FETCH_HEAD...$TRAVIS_BRANCH | grep -qvE '(\.rst$)|(^(docs))/' || {
    echo "Only docs were updated, stopping build process."
    exit
  }

Only docs were updated, stopping build process.


chore: add publisher to iss file

Describe Your Changes

Fixes Issues

Closes #
Closes #

Self Checklist

[ ] Added relevant comments, esp in complex areas
[ ] Updated docs (for bug fixes / features)
[ ] Created issues for follow-up changes or refactoring needed

@hiento09 found the cause of the error. There is no need for this PR so I will close it. Thanks.


[bitfinex] [bitstamp] Added method for getting history (bitfinex) and general method for withdraw (bitstamp)

Isn't the Bitfinex part already exist?
Please check BitfinexAccountService.getDepositWithdrawalHistory and BitfinexAdapters.adaptFundingHistory.

@roeiba You mentioned request https://api.bitfinex.com/v:version/history/movements, I imlemented other request https://docs.bitfinex.com/v1/reference#rest-auth-balance-history.


Decide what to do with the legacy setuptools tracker on bugs.python.org

Originally reported by: ncoghlan (Bitbucket: ncoghlan, GitHub: ncoghlan)

MvL pointed out that http://bugs.python.org/setuptools/ is currently still live and needs to be dealt with so people don't get confused about where to report setuptools issues.
@pje pointed out that there is some info on issues there that hasn't yet been replicated in the docs or migrated to this issue tracker, so it likely needs to be reviewed before the instance can be terminated.
MvL suggested making it read-only for the time being. That sounds like a good idea to me, but a better long term resolution is needed.

Bitbucket: https://bitbucket.org/pypa/setuptools/issue/174

It seems that the old bug tracker was disabled and is no longer accessible from the old URL... so time might have solved this issue for us...
I think we can close this issue now, considering that the entire community is already used to the new GitHub system, but if anyone would like to keep it open please feel free to comment here...


A pull request that closes Issue #33.

Closes #33.

Pull Request Test Coverage Report for Build 69

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

wse-common/src/main/java/com/github/glusk2/wse/common/util/Comparison.java
0
19
0.0%

Totals

Change from base Build 66:
-3.0%

Covered Lines:
317

Relevant Lines:
459

💛  - Coveralls


Adding multiple liveness results in Exception, "More then one sequence found"

I have multiple environments and I am trying to place health checks for all of them through single BeatPulse.UI instance, below is my  startup configuration.
I have also placed a check that if only the given environment is meant to be checked for liveness then spin only the relevant services, otherwise add all the services for liveness.
I am also using 4 different appsettings.json files , one for each environment.
/health returns the valid result, but /beatpulse-api produces exception.
var showEnvironmentWise = Configuration.GetValue<bool>("showEnvironmentWise");
var environment = HostingEnvironment.EnvironmentName.ToLower();

`
        var connectionString_D = Configuration.GetConnectionString("MySql-D");
        var connectionString_Q = Configuration.GetConnectionString("MySql-Q");
        var connectionString_S = Configuration.GetConnectionString("MySql-S");
        var connectionString_P = Configuration.GetConnectionString("MySql-P");

        var rabbitMq_D = Configuration["RabbitMQ-D"];
        var rabbitMq_Q = Configuration["RabbitMQ-Q"];
        var rabbitMq_S = Configuration["RabbitMQ-S"];
        var rabbitMq_P = Configuration["RabbitMQ-P"];

        var apiHealthUrl_D = Configuration["ApiHealthUrl-D"];
        var apiHealthUrl_Q = Configuration["ApiHealthUrl-Q"];
        var apiHealthUrl_S = Configuration["ApiHealthUrl-S"];
        var apiHealthUrl_P = Configuration["ApiHealthUrl-P"];

        services.AddBeatPulse(setup =>
        {

            if (showEnvironmentWise)
            {
                setup.AddMySql(connectionString_D, name: $"storage-{environment}", defaultPath: $"storage-{environment}");
                setup.AddRabbitMQ(rabbitMq_D, name: $"queue-{environment}", defaultPath: $"queue-{environment}");
                setup.AddUrlGroup(opt =>
                {
                    opt.AddUri(new Uri(apiHealthUrl_D), uri =>
                    {
                        uri.UseGet()
                            .ExpectHttpCode(200);
                    });
                }, $"api-{environment}", $"api-{environment}");
            }
            else
            {
                setup.AddMySql(connectionString_D, name: "storage-development", defaultPath: "storage-development");
                setup.AddMySql(connectionString_Q, name: "storage-quality", defaultPath: "storage-quality");
                setup.AddMySql(connectionString_S, name: "storage-staging", defaultPath: "storage-staging");
                setup.AddMySql(connectionString_P, name: "storage-production", defaultPath: "storage-production");

                setup.AddRabbitMQ(rabbitMq_D, name: "queue-development", defaultPath: "queue-development");
                setup.AddRabbitMQ(rabbitMq_Q, name: "queue-quality", defaultPath: "queue-quality");
                setup.AddRabbitMQ(rabbitMq_S, name: "queue-staging", defaultPath: "queue-staging");
                setup.AddRabbitMQ(rabbitMq_P, name: "queue-production", defaultPath: "queue-production");

                setup.AddUrlGroup(opt =>
                {
                    opt.AddUri(new Uri(apiHealthUrl_D), uri =>
                    {
                        uri.UseGet()
                            .ExpectHttpCode(200);
                    });
                }, "api-development", "api-development");

                setup.AddUrlGroup(opt =>
                {
                    opt.AddUri(new Uri(apiHealthUrl_Q), uri =>
                    {
                        uri.UseGet()
                            .ExpectHttpCode(200);
                    });
                }, "api-quality", "api-quality");

                setup.AddUrlGroup(opt =>
                {
                    opt.AddUri(new Uri(apiHealthUrl_S), uri =>
                    {
                        uri.UseGet()
                            .ExpectHttpCode(200);
                    });
                }, "api-staging", "api-staging");

                setup.AddUrlGroup(opt =>
                {
                    opt.AddUri(new Uri(apiHealthUrl_P), uri =>
                    {
                        uri.UseGet()
                            .ExpectHttpCode(200);
                    });
                }, "api-production", "api-production");

            }

        });`

turns out I was targeting the wrong appsettings.json file, after targeting the right one, I was able to fix  the issue.


Error 503 when reaching /.well-known/acme-challenge

Hello,
I am trying to use kube-lego but I am running into a problem. According to the logs it returns a 503 error. I have read that this problem is usually caused by the namespaces, so I put both nginx-ingress-controller and kube-lego under kube-system where the rest of the ingresses are in default, but nothing changed.
You can read the manifests of both the ingress controller and kube-lego here.
I can manually validate that both HTTP and HTTPS requests to $DOMAIN/.well-known/acme-challenge are retiring a 503 error.
What could it be?

Same issue here.
It worked perfectly until now, when my ingress controller (nginx-ingress-controller) and kube-lego where in the default namespace. I moved ingress and kube-lego to another namespace, and now I got the same issue. I tried with kube-lego versions 0.1.4 and 0.1.3, same thing.
When kube-lego try to renew/request a certificate, it log this (debug log level)
time="2017-05-31T08:00:19Z" level=debug msg="testing reachablity of http://www.domain.tld.well-known/acme-challenge/_selftest" context=acme domain=www.domain.tld
time="2017-05-31T08:00:19Z" level=debug msg="error while authorizing: reachabily test failed: wrong status code '503'" context=acme domain=www.domain.tld

I got this on my ingress controller logs :
 - [<IP_ADDRESS>, <IP_ADDRESS>] - 52788 -  - - [31/May/2017:07:59:04 +0000] "GET /.well-known/acme-challenge/_selftest HTTP/1.1" 503 214 "-" "Go-http-client/1.1" 318 0.000 [-] - - - -
<IP_ADDRESS> - [<IP_ADDRESS>] - 56374 - 56374 - - [31/May/2017:07:59:04 +0000] "GET /.well-known/acme-challenge/_selftest HTTP/1.1" 503 214 "-" "Go-http-client/1.1" 143 0.001 [default-kube-lego-nginx-8080] <IP_ADDRESS>:8181 214 0.001 503

It seems that the kube-lego backend for .well-know is not working, returning HTTP 503.

Ok, just solved it.
Actually I got 2 kube-lego-nginx ingress rules for .weel-know/acme-challenge : one on the current kube-lego namespace (infra for me) and another (the old one) on the default namespace. I just delete the old one and it works.
@koalalorenzo Not sure if it is the same for you, but try to run :
kubectl get --all-namespaces ing | grep kube-lego and delete all kube-lego-nginx ingress rules which are not in the same namespace as your current kube-lego pod.
If not working, can you share your kube-lego and ingress controller logs ?

So, the way to solve this for me was to deploy kube-lego in its own namespace. But I think that this should still be marked as bug, as probably there is something that tight and strictly links kube-lego to its own namespace.
The logs were the same (very similar) to the one that you have!

I don't really know how exactly kube-lego works internally, but on my side I was able to made kube-lego works and I have the following organisation :

kube-lego running in a namespace infra
some other stuff (like my nginx-ingress-controller) also running in namespace infra
some other stuff on a lot of various namespaces
So I think it is possible to made everything works without a dedicated namespace for kube-lego.
I am running on kubernetes 1.5.6.

Had the same problem on 1.6.2. The config generated by nginx-ingress-controller listed <IP_ADDRESS>:8181 as the upstream. Running
kubectl expose deployment kube-lego --port=8080 --name=kube-lego-nginx
fixed that. No separate namespace was necessary, in fact deploying kube-lego in its own namespace messed with my fine-tuned RBAC rules.

The latest version actually seems tho have this fixed! Thank you so much for your help! In case it will change I will re open the task!


Pass mimeType option not working

I try pass mimeType to options props is "video/mp4" but the output is always "video/x-matroska;codecs=avc1,opus".
Seems mimeType option is not working.

Same goes for the sizing props, unless they work for you.... if you set a maxHeight in that options object, it will not apply.

Thanks for the feedback! Will have a look today.

@dattm97 @aLx450 I've update the package with a new version - please have a look at the updated Codesandbox demo.
I've refactored the code a bit so there are some breaking changes but nothing too bad. Nonetheless passing the filetype should set the mimeType now accordingly, as well as setting the width and height  should work too now!


[MRG] Switch to recommending to install from master

We only make a release every three months but run master on mybinder.org
which means people see bugs that were long fixed when they run locally. So
we often tell people "try master".
I can't think of a concrete reason not to recommend this. WDYT?
closes #841

One disadvantage of installing from the zip:
$ python3 -m pip install -U https://github.com/jupyter/repo2docker/archive/master.zip
...
$ repo2docker --version
0+unknown

Installing from git requires git to be installed but shows a version:
$ python3 -m pip install -U git+https://github.com/jupyter/repo2docker.git
...
$ repo2docker --version
0.11.0+13.g26542df

I think versioneer lets you install the package from a non-git URL but without a version. Compare this with e.g. setuptools-scm which will fail if you try an installed a development version thats not a git URL.

We now make (more) regular releases so this isn't needed any more.


Pub / Sub Subscriber: CPU Usage eventually spikes to 100%

This is a distillation of this report from many other issues. Large thanks to @anorth2 and @dmontag for reporting and helping refine the issue.
Issues that have been partially resolved (except for the CPU spike) are being collapsed into this one:

#4274
#4563
#3965
(more to come?)

Core issue: there is a spinlock bug in gRPC (present in all recent versions 1.6.x, 1.7.x, 1.8.1). A "bandaid" fix exists but has not been merged (as of noon Pacific on December 15, 2017).
Potential workaround: compile grpcio from source (e.g.) while including the bandaid fix or just use the 64-bit manylinux wheel that I already created (I may be open to creating Mac OS X wheels, not sure about Windows)

@anorth2 Would you mind trying with the patched grpcio==1.7.4.dev1? (This is a follow-up to https://github.com/GoogleCloudPlatform/google-cloud-python/issues/4274#issuecomment-351790352)

Testing it out now, I'll edit this comment once I have it deployed.

@anorth2

What command are you running to get that error? (I assume you've downloaded the wheel and are running pip install grpcio....whl)
Feel free to ping me on Hangouts

Fixed by #4642.

Hi @dhermes ,
I am still having problem with high CPU usage. After around one hour CPU usage is 100%.
google-api-core (0.1.3)
google-auth (1.2.1)
google-cloud-pubsub (0.30.1)
googleapis-common-protos (1.5.3)
grpc-google-iam-v1 (0.11.4)
grpcio (1.8.2)


Adding Aragog to list of community integrations

@cla-bot check

Thanks a lot for your contribution to ArangoDB!
We would like to accept your patch, but for legal reasons we need you to fill out and sign our Contributor License Agreement (CLA). We use an Apache 2 CLA for ArangoDB, which can be found here: https://www.arangodb.com/documents/cla.pdf
You can scan and email the CLA PDF file to<EMAIL_ADDRESS>or send it via fax to +49-221-2722999-88.

Dear @Simran-B, I've signed it, the Saturday, May 21st, 2022 at 18:29 (Paris time)

Apologies, @Nainterceptor. A coworker confirmed that it arrived. Thank you very much!


Add docs.rs metadata and custom builds

This patch is adding Metadata type used in cargo::ops::CompileOptions to customize
docs.rs builds.
An example metadata in Cargo.toml:
[package]
name = "test"

[package.metadata.docs.rs]
features = [ "feature1", "feature2" ]
all-features = true
no-default-features = true
default-target = "x86_64-unknown-linux-gnu"
rustc-args = [ "--example-rustc-arg" ]
rustdoc-args = [ "--example-rustdoc-arg" ]
dependencies = [ "example-system-dependency" ]

This patch is still work in progress and aiming to fix: #29, #48 and #50
TODO

[x] Save default target to database.
[ ] Install system dependencies before building a package.
[ ] Redirect to default-target if its specified.

Do you have a staging server? I'd be happy to test this out for you with the ring crate, which needs to be built with --features=rsa_signing to get correct documentation.

Unfortunately there isn't any staging server and docs.rs is only working with central repository (crates.io). I'll upload a dummy package to test this.

Coming here from https://github.com/onur/docs.rs/issues/23#issuecomment-242943910.
We are facing a similar issue while trying to automate Debian packaging, and we'd like to have some hints from crate author regarding which system packages needs to be installed in order to properly build.
The package.metadata.docs.rs.dependencies could be a good start, but I think it is possibly missing:

distro selector (a library may have a different package name in debian, ubuntu, fedora, etc...)
suite selector (a library may get renamed/split in debian-jessie->debian-stretch->debian-sid)
a version selector (a crate may depends on symbols introduces in newer versions of a library, even without soname changes)

May I suggest putting together a strawman proposal of a metadata schema somewhere (eg. https://wiki.debian.org/Teams/RustPackaging/)?
/cc @infinity0 @joshtriplett

opam, the ocaml package manager, is able to deal with non-ocaml system dependencies and interact generically with a system package manager. I will dig out docs for that later today and comment in more detail.

What is this blocked on?

Actually there is nothing blocking this issue. I wanted docs.rs to build everything automatically without requiring any user input but looks like its not enough. I'll finish this feature and add into docs.rs next week.

@onur have you seen https://github.com/joshtriplett/metadeps? It is supposed to solve this problem in a distro-agnostic way.
/cc @joshtriplett

This is so very sorely needed. Can this be merged soon?

@SergioBenitez I am working on it.

Checking in. How's it going, @onur?

Good work with this. This would be grate for a number of projects that are currently failing to build on docs.rs. If there's any way we can help, let us know.


#3713 white text, bg changes

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[x] Refactoring

What's new?

[x] PR closes #3713
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

Just small details:
Stats: Sales: the first row is dark - can we fix it to white as other categories in stats? Picture:

Explore: collections/gallery: Not sure if this is also something our dev team can fix, but maybe it would be prettier if the "loading form" of NFTs had our logo on a white background. You can see in this picture that our K logo is on a black background, and it's kinda ruining the whole white mode effect.

Also, it would be nice to have a white version of the short loading gif, that appears after you open each NFT. This one:

Settings: can we use here a white background instead of grey? It hurts my eyes to read pink words.

Thx

Explore: collections/gallery: Not sure if this is also something our dev team can fix, but maybe it would be prettier if the "loading form" of NFTs had our logo on a white background. You can see in this picture that our K logo is on a black background, and it's kinda ruining the whole white mode effect.

I've made issue #3754

https://deploy-preview-3742--koda-nuxt.netlify.app

fixed

Just small details: Stats: Sales: the first row is dark - can we fix it to white as other categories in stats? Picture:

Explore: collections/gallery: Not sure if this is also something our dev team can fix, but maybe it would be prettier if the "loading form" of NFTs had our logo on a white background. You can see in this picture that our K logo is on a black background, and it's kinda ruining the whole white mode effect.
Also, it would be nice to have a white version of the short loading gif, that appears after you open each NFT. This one:
Settings: can we use here a white background instead of grey? It hurts my eyes to read pink words.
Thx

Fixed, except the image changes

Seems tests fails? 👀

Seems tests fails? 👀

which tests?

now it's ok!

pay 50

😍 Perfect, I’ve sent the payout
💵 $50 @ 55.25 USD/KSM ~ 0.905 $KSM
🧗 EzGc4s9PgCPx1YnF3fqzhLzVHpHMTL4LWPScwpDrR8JKgSU
🔗 0x841c9226d7fb05813bab584f11f0a052f956eff9d721f631260a781aac6c8336
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[Issue] outputs from main.bicep added to .azure/.env occasionally include a casing error

[x] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here:
azd version 0.1.0-beta.4 (commit fd96b3e9b283598bc4dc736e893f1b47080fbf7d)
Output from az version
Run az version and copy and paste the output here (minimum required version is 2.38.0):
azd version 0.1.0-beta.4 (commit fd96b3e9b283598bc4dc736e893f1b47080fbf7d)
Describe the bug
Description of issue you're seeing...
Occasionally (not always) outputs from main.bicep are exported to .env with casing errors:
output POSTGRES_USER string = binding.outputs.POSTGRES_USER
results in:
pOSTGRES_USER=XXXXXXX
To Reproduce
Output variables from main.bicep
Expected behavior
Environment variables should respect casing when added to .env file.

Related? https://github.com/Azure/azure-dev/issues/289

This is somewhat surprising as we do explicit work to try to prevent this from happening.  ARM does not retain the case of output property names (this is a known issue) in the deployment object and so we use ARM Template to discover the canonical case of the outputs and then use that when updating the environment.
That logic lives here: https://github.com/Azure/azure-dev/blob/eff5410e6e0d1cac190823ee0ab5dfa06f43c1c4/cli/azd/pkg/iac/bicep/compile.go#L41-L59
It's possible that we aren't running it in some cases?
@greenie-msft You mentioned this is intermittent - I'm wondering what azd command you're running when you trigger this?  The intermittentness concerns me.
Also - when this happens is the original (correctly cased) POSTGRESS_USER removed from the environment or is it still around as well as the bad cased version?

@ellismg, I just reviewed my shell history and the command I used (every time) was : azd env set POSTGRES_USER XXXX
When behavior occurs, it does not remove the correct environment variable from previous attempts. I had the below in my .env file:
POSTGRES_USER=XXXX
pOSTGRES_USER=XXXX

I'm pretty consistently running into this on a MacBook. Will investigate further, but at a glance:

The casing in .env file is correct
When running bicep build of the .bicep file, the outputs have correct casing
But in the deployment, I can see the casing is messed up:

Suspicious that ARM may be involved here.

This has been lingering for a while -- but the underlying issue was in the ARM deployment outputs. To handle this, azd normalizes all casing outputs -- please reopen if there are further issue around this.


FRONTEND WITH FRAMEWORK: REACT-1.1 WHAT IS JSX?

Contributors are required to include what is JSX and why it is used, its relation with react as a framework. An example and its syntax should also be included.
Also make sure -
Avoid copy/paste, We will be checking.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ dir inside Frontend_Web_Development_React_Angular_Vue branch.
Task will be assigned on first come first serve
Check out Contribution Guidelines
and Code Of Conduct

Hi @praveenscience Sir, This is Titas Nath(batch 6, frontend with HTML, css). May I contribute on this topic?

Hi, This is Titas Nath(batch 6, frontend framework). May I contribute on this topic?

@trip0le I have assigned you a work already,after that i will assign you this work

Can I contribute on this?
Sahil Srivastava Batch-6 Frontend-Framework

@anandhu720 hello mentor I'm from Batch-1 Frontend-Framework. can I start working on this issue ?

Can I work on this issus?
I am from Batch-3 Frontend-Framework

@anandhu720 I have a basic idea about JSX I want to contribute to this issue. I am from batch-2-frontend-framework

@sahil9510 I have assigned you on this. @iamsuyashpatel07 @nik09877 @Saurabh-crypto16 It is a fist come first serve basis. Wait for other issues. Just keep checking "Frontend with frameworks" milestone

okay @the-pro.

Can i work on the video part of it?

@sahil9510  any updates of your work

@anandhu720 I have made a PR. Please review it

@sahil9510 ok

This issue is completed


parameters

google drive api give parameters:
"client_id"
"project_id"
"auth_uri"
"token_uri"
"auth_provider_x509_cert_url"
"client_secret"

in install lost point about parametrers from service
gdrive_directory_base_id
gdrive_directory_splited_id
kasifi_gdrive.google_drive_client_email
kasifi_gdrive.google_auth_sub
gdrive_oauth_https_callback_prefix
by name not undersatnd what parameters your mean ?
and you declareted:
Resources Finder:

Search a resource
List children of a resource
Get resource metadata
Download files

where realization for download file example ?

You're right. I'll add it to the documentation.

@shubaivan: You can update the bundle to the 0.8.3 via composer update lucascherifi/google-drive-bundle.
Regards,
Lucas.


Live demonstration broken

The SoSSIM live demonstration is broken.
The most likely explanation for this is that there are new pyscript versions that are not backwards compatible. The app/sossim.html script uses the latest pyscript version, which is not the same as the one the SoSSIM code has been tested against. The fix is then to make the version number explicit.
While looking into this, it was also discovered that the development server does not work according to the instructions in the README file. The link to the locally served web page is old, it should now be pointing to the app directory.

Mesa also had some breaking changes when moving from version 2.1.5 to version 2.2.0. Mesa is installed using micropip in __main__.py, so this needs to be modified to use the older version.

Issue fixed by making pyscript and mesa version explicit. Note that mesa version needs to be specified in two places: requirements.txt for local installation used for batch running, and in __main__.py for dynamically loading the library using micropip when running interactively in the browser. The pyscript version is set in sossim.html in the link address to the pyscript core.


Unsupported is prefix for Column getters

Column documentation states that methods with get and is prefixes are supported as columns, but in fact the is prefix is not supported.

Resolved via #910.


Express/Connect Middleware Documentation is Sparse

I had to read the source code to get an idea for how the middleware works and how it should be used. I don't think this is very helpful or explicit enough, and I do think that developers are going to want to know what the middleware does for both Express and Connect.
For example, it wasn't explained that if an error has a status code less than 500, that errorHandler wont log it to Sentry. This is important information to know about the middleware. Also, it could be suggested that one could still use next(err) for errors that you wouldn't want logged (such as user related errors; invalid input from the user). Would be very useful to know.
Also, it would be helpful to know what requestHandler does and why it is required. It is useful to know  that it wraps your routes in a domain, and delegates errors captured in the domain to errorHandler. Also, how does this effect the use of patchGlobal()?

For example, it wasn't explained that if an error has a status code less than 500, that errorHandler wont log it to Sentry.

Anything less than a 500 is not an error. errorHandler is a middleware so it's always called. It's up to the middleware then to determine if it should pass or do something with it. In our case, we want to intercept errors, which are 5xxs.

Also, it could be suggested that one could still use next(err) for errors that you wouldn't want logged (such as user related errors; invalid input from the user). Would be very useful to know.

Can you explain this more? I'm not sure the use case or how this would work. I'm not personally very familiar with Connect and Express.

Also, it would be helpful to know what requestHandler does and why it is required.

It's not technically required since domain objects are optional. But the idea is that we can wrap the entire request cycle in an error domain which captures exceptions more effectively.

Also, how does this effect the use of patchGlobal()

It shouldn't at all. They can be used together.

1
The point about 500 status code is that it should be explained in the docs that errorHandler works this way. If devs are unaware about how this middleware uses statusCode/status_code on their error objects, then they might wonder why they're errors aren't being logged when they use these properties for their own purposes.
2
To explain more about the second point: If users are aware that the middleware wont log errors with statusCodes < 500, then a user can use this to their advantage if they want to respond to a request that has an error and display a message to the user, but doesn't want to log the error. For example, a user might have invalid input in a POST request, so tell the user what went wrong, but don't log the error.
3
If it's not technically required, the docs should be clear about that. Right now the docs say:
// Should be the first item listed
app.use(raven.middleware.express.requestHandler('{{ SENTRY_DSN }}'));

"Should be first item listed" makes me think that it's required. If it's not, then why should it be first item, what does it do, how should I use it, etc?

The point about 500 status code is that it should be explained in the docs that errorHandler works this way. If devs are unaware about how this middleware uses statusCode/status_code on their error objects, then they might wonder why they're errors aren't being logged when they use these properties for their own purposes.

I guess this is a point of confusion for me. I'd argue that if you're wanting to log an error like that, then the middleware is not for you. A middleware is intended to capture uncaught exceptions. Not the general way to just report errors. You'd use the client directly to log an error that you've captured yourself.
Is that reasonable? Or is there a pattern that I'm misunderstanding that people implement? I'd need to see some code examples since this is unfamiliar to me.

In Express, it is standard practice to hand off any kind of errors to the middleware by doing next(error)- this isn't just for 500 errors.
I had expected that all requests would be logged to Sentry, even if they succeeded.

@mattrobenolt

I'd argue that if you're wanting to log an error like that, then the middleware is not for you.

But how would I know that the middleware is not for me if I don't know what the middleware does. Having documentation about the middleware would help me make a decision on whether to use it. Does it make sense why it would be important to explain/document what the middleware does (which is what this issue is really about)?

I confirm the documentation could be improved on this part. I tried many things and the raven express middleware still doesn't report my server errors (captureMessage works).
A working express server example would help a lot I think.

I've improved this a bit, but we might want to do more. For now I want to close this out, but feel free to send PRs as we're actively trying to improve this.

has anyone got an example of the above working in the correct way?
I'm confused; it sounds like i should respond with 500, but not throw the error using next??
i.e. can someone help with the following:
server.js
import express from "express";
import routes from "../shared/routes";
import raven from 'raven';

const app = express();

const SENTRY_DSN = 'https://' + process.env.RAVEN_KEY + ': ' + process.env.RAVEN_SECRET +<EMAIL_ADDRESS>+ process.env.RAVEN_APP_ID
const client = new raven.Client(SENTRY_DSN);
raven.patchGlobal(client);
function onError(err, req, res, next) {
  // The error id is attached to `res.sentry` to be returned
  // and optionally displayed to the user for support.
  res.statusCode = 500;
  res.end(res.sentry+'\n');
}
// The request handler be the first item
app.use(raven.middleware.express.requestHandler(SENTRY_DSN));

// The error handler must be before any other error middleware
app.use(raven.middleware.express.errorHandler(SENTRY_DSN));
// Optional fallthrough error handler
app.use(onError);

app.use('/api/v0', routes);

routes.js
import express from 'express';
let router = express.Router();

router.get('/routeExample', (req, res, next) => {

   fnReturnsAPromise({uuid: req.params.uuid})
        .then((data) => {
            res.locals.data =data;
            next();
        })
        .catch((err) => {
            res.status(500);
           next(err)
        })
});

export default router;


2.1.x

Search field added to men list and css added to make it sticky and flicker issue is resolved

Not from code igniter. It was committed for this change "Comment is not maintained properly". Not sure why that was not merged. This is needed if we have only the + button to add comment. If we go for - and + this will not be needed

Alright. Allow me some time to review and merge.


Value as JSON Reference document

Validation documents are an extension of JSON Reference documents. The JSON documents that are being validated are just plain JSON.
This task is to refactor so that we are validating JSON Reference documents, not plain JSON documents.

Done.


Tests with inactive modules?

If i turn off certain module in my module_statuses.json how can i make it so that tests inside that module are not being run?

Hi,
That status file isn't linked to phpunit, so it will keep running the tests.
To ignore some tests, you need to remove the test doc blocks accordingly.

So there is no way to due that dynamically based on module status?

There might if phpunit has a programatic api for you to hook into.
I've not looked into this myself though.


Docs.MS Release Updates for azure_storage_file_datalake

Update docs metadata and targeting for release of azure_storage_file_datalake

Docs Build status updates of commit 7f077b8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/preview/storage-file-datalake-readme.md
:warning:Warning

Details

ci-configs/packages-preview.json
:white_check_mark:Succeeded

docs-ref-services/preview/storage-file-datalake-readme.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 9, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'datalakestorage(gen2)'.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Add Aurelia extension modules to skeleton

How about if we add things like aurelia-dialog and aurelia-validation to the skeleton libraries?
Apart from the fact the constantly changing nature of these skeletons means we have to change the base tooling and startup configuration for our project each time there's a rethink, we then find none of the additional libraries work any longer, suggesting they either haven't been tested with the new changes, or the required reworkings are non-obvious and/or not documented.
For third-party libraries I wouldn't expect examples, but for official libraries we really need this to be better monitored, and including them in the skeletons seems a good way to do so.
I'm experiencing this today, as I find easy-webpack has been removed, and after spending several hours getting the new structure slotted in (which I like the look of) I then find half of the Aurelia extension modules don't load.
Is this something I've missed, or an incompatibility? I have no idea, but proof that the modules co-exists with the latest recommended skeleton framework would at least tell me if it's my fault or not.

@jods4 @niieani Haven't we tested all the official modules with the new webpack setup now?

@EisenbergEffect That is important, although it's not just testing them, it's explaining what's different and needs to be changed to make it work for existing projects.
In my case I get the error
Error: Unable to find module with ID: aurelia-dialog/ai-dialog

Now this may be because of something I've not done, done, or someone else has done. If I had dialog code used in the skeleton I could both see it working and compare it to my solution to identify the issue, otherwise I flounder for an indeterminate length of time trying to work out where and why it might occur.
All I know right now is that it worked until I updated the loader.
Most importantly, if I get this issue then there are probably hundreds of other people who experience the same problem and simply give up. It would be nice to retain all those developers.

@EisenbergEffect I tracked which of our libs are confirmed OK at aurelia/pal#21.
aurelia-dialog is not ticked yet.
I also opened aurelia/dialog#254.
Given aurelia/dialog#272 I think it should work out-of-the-box in the next release.
In the meantime ModuleDependenciesPlugin is the workaround, see this comment.

does aurelia-validation work with webpack currently? when I try it, I consistently get
Error: BindingLanguage must implement inspectTextContent().

with chrome on windows

@ariovistus I'm not an aurelia-validation user myself, but according to the linked issue it was tested to work.
On the other hand I implemented the Webpack plugins and I should say that this is not your typical Webpack error.
Generally Webpack errors manifest as modules not found at runtime, this looks rather different.

this
https://github.com/ariovistus/skeleton-navigation/commit/37125efc9781301162803725d42269f6cee6755e
is all I'm doing, not sure if I missed something

I think that you should open an issue in aurelia/validation.

@ariovistus Did you manage to find a solution for that issue? I'm experiencing the same..

nope

I have a starter kit, which is heavily based on the skeleton-typescript-webpack with the latest versions and with validation, dialog and i18n, additionally I have added some small examples: https://github.com/w3tecch/aurelia-typescript-boilerplate
Maybe this helps you @jsobell
Anyway I would totally support having these plugins in the official skeleton of aurelia.

@dweber019 Thanks, it's good as a reference to point people to.
I have it all working, (and my main developer is on the Aurelia core team, which helps), but the point is that if your project is not updated in sync with the core packages, it won't help in situations where teams update those elements and integration with validation or dialog fails.
Also, we don't want to depend on external projects to prove or validate official extensions.

@jsobell I'm with you. Dialog, validation and i18n should be part of the official skeleton.

@jods4 @jsobell I have just installed all the latest aurelia packages and I'm getting:

In my webpack config in my module dependencies plugin I have:

@jasonbiondo no idea what goes wrong here. Doesn't look like a missing webpack dependency.

@jods4 @EisenbergEffect should I downgrade to an older version of aurelia dialog because this seems pretty broken.

Is there any chance you are displaying a dialog before calling aurelia.start() ? Because that's an error when aurelia-templating-binding has not been loaded.

@bigopon nope, I'm not displaying a dialog before aurelia.start().  One thing I noticed is that I even tried downgrading different versions of the dialog plugin but I still get the same errors.  Any more ideas?

@jasonbiondo  The error means you are some how compiling a view with out registering proper binding language, so downgrading won't help. aurelia.start() is responsible for loading up aurelia-templating-binding for the binding language and that's why we were checking if it's called before aurelia.start().
Without looking at your code, properly the only way is to comment out dubious plugins / features to see where the issue comes from.

aurelia-dialog uses it's own version aurelia-binding there (visible in the screenshot), hence the error i presume
there's a solution for those interdependencies https://github.com/aurelia/templating/issues/629#issuecomment-399591821


esbuild: finding a solution that works for all versions

I was having some problem with a package failing on esbuild (missing the binary of course)
I was thinking we should potentially have a json file with all the versions and hashes for a couple of packages.
We could potentially make a script to populate that binary.lock file. (we could call it anything you want).

Yes I think something like that might be a good idea. I mean, the cleaner solution would probably be to build these binaries from source if the source is vendored.

Here is what I think we should do.
have an override for minor versions that all patch versions will use.
Something like
 "add-binary-0.12" = {
        _condition = pkg: (lib.versionAtLeast pkg.version "0.12") && (lib.versionOlder pkg.version "0.13");
        ESBUILD_BINARY_PATH = let
          esbuild = pkgs.buildGoModule rec {
            pname = "esbuild";
            # using 0.12 latest version
            version = "0.12.17";

            src = pkgs.fetchFromGitHub {
              owner = "evanw";
              repo = "esbuild";
              rev = "v${version}";
              sha256 = "sha256-wZOBjNOgGmwIQNCrhzwGPmI/fW/yZiDqq8l4oSDTvZs=";
            };

            vendorSha256 = "sha256-2ABWPqhK2Cf4ipQH7XvRrd+ZscJhYPc3SV2cGT0apdg=";
          };
        in "${esbuild}/bin/esbuild";
      };

then we have one override for each "major" version. The api supposedly is compatible. So we should have only 3-4 versions that we need to write by hand that would be valid for everything.
If that sounds good to you, happy to give it a go in a PR.

Wonderful, I think this is a good approach.
You could shorten the condition by using satisfiesSemver "~0.12"

how do I get access from the satisfiesSemver function from outside of dream2nix. I wanted to test on a flake directly before submitting a merge request.
I tried checking into dlib, but didn't find a path after that. And nix repl . complains that there is no default.nix in the repo
 dlib = inputs.dream2nix.lib.dlib.
I'm going to make an MR and work off the branch for now, but would be nice to have an example in the readme of how to access the satisfiesSemver function from an outside flake.

satisfiesSemver is currently not in dlib. I will put it there soon.
For now it can be used like this:
nix-repl> :lf ./.
Added 17 variables.

nix-repl> lib.x86_64-linux.utils.satisfiesSemver
«lambda @ /nix/store/jrsj7h4ibxlfiv99i5sxmiid3ixmjc8c-source/semver.nix:81:21»

nix repl complains for me that there is no default.nix probably my nix is too old.
oh, no, you just have to nix repl flake.nix, okay my brain is not working.
found the repl and learned about :lf
I've just submitted a PR for esbuild 0.14, I'll be doing more as I encounter them.
I think this can be closed for now.
Thanks for the help!

It's probably not the end for this one
 Cannot start service: Host version "0.14.23" does not match binary version "0.14.38"
I'm looking for a way to de-activate the version check.

I've got a PR ready

also, last question, in the flake overrides, how will I access the pkgs representing nixpkgs. Do you re-export it or is my best alternative to do
      pkgs = import inputs.dream2nix.inputs.nixpkgs { system = "x86_64-darwin"; };
was also thinking it would be good to include in the example flakes comment a more involved override just to give a good sense of how to do it.

No need to re-import nixpkgs if you don't use overlays (see: https://zimbatm.com/notes/1000-instances-of-nixpkgs). You can access it via:
inputs.dream2nix.inputs.nixpkgs.legacyPackages.x86_64-darwin.
Yes, I think it would be an amazing idea to add an example flake to the readme that uses all possible features and is commented.


New version: Zoom.Zoom.VDI version 6.0.25100 (<IP_ADDRESS>00)

Created by 🥟 Dumplings in workflow run #6363.

Log
Updated: <IP_ADDRESS>60 → <IP_ADDRESS>00
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

https://github.com/microsoft/winget-pkgs/issues/142854


Installation documentation not available

When I click the link to go to the installation documentation it takes me directly to the homepage because it can't locate the document.
https://github.com/eapowertools/QlikSenseQMCUtility/wiki/Installing-QMC-Utilities

Sorry about that, will have updated install documentation soon.  The installer is pretty straightforward so if you are feeling brave have a go.

Thanks!

Updated Documentation here: https://github.com/eapowertools/QlikSenseQMCUtility/wiki/QMC-Utilities-Installation-Instructions


Cleaned up edge service

Proposing changes suggested in external review:

Remove _name suffix from fields that have it.
Remove unused (and not well defined) field api_protocol.
Some extra documentation.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jkohen
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @jkohen. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Note that for this and related changes, we will need a migration story to ensure that 1.0 and 1.1 deployments of Istio don't get borked when upgrading to 1.2.
We don't have versioning on templates at the moment. Either we'll need to do this for 1.2 and mark your updates as being new versions, and still support the old. Or we'll need some mechanism to migrate user config forward.

What do you suggest? 1.2 sounds fine if we can count on on-the-wire
compatibility.
The other changes are just documentation. Do we need a migration story for
that?
On Tue, Mar 5, 2019, 10:11 Martin Taillefer<EMAIL_ADDRESS>wrote:

Note that for this and related changes, we will need a migration story to
ensure that 1.0 and 1.1 deployments of Istio don't get borked when
upgrading to 1.2.
We don't have versioning on templates at the moment. Either we'll need to
do this for 1.2 and mark your updates as being new versions, and still
support the old. Or we'll need some mechanism to migrate user config
forward.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/12254#issuecomment-469715825, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG0TaCrrdZOfJ1ohnMA6xQT6n_bpdLkgks5vTokNgaJpZM4bensa
.

Doc changes don't need migration, that's fine.
If the actual config format changes, we need to make sure customer's setups continue to work as they upgrade to a new version of Istio. This particular change you're making will be part of 1.2 (as 1.1 is just about done). So before 1.2 comes out officially, we need to have a strategy in place. I think it's fine to file a bug stating that "Implement approach to migrate customers to new config format" or whatever, so long as we keep track.
What we likely need to do is in 1.2 is:

Introduce support for multiple concurrent versions of a given template or config.

Support both formats in the code.

Provide a migration tool that converts a deployed config from the old format to the new format.

Publish a warning indicating the old format will be deprecated.

In 1.3, we remove support for the old format,

As discussed with Doug, I'm going to drop this change in favor of a Stackdriver-specific template.


version 4?

Looks like version 4 has been published to npm, but this repo doesn't reflect the changes.

It appears this repo is no longer maintained.
The published version points back to cssnano, so the code now lives in https://github.com/cssnano/cssnano/tree/master/packages/postcss-discard-duplicates