Optional Chaining

Must be enabled in flowconfig manually. Rewrite GraphQL nullables checks.

Hmm, blocked by relay-compiler:
ERROR:
Parse error: SyntaxError: This experimental syntax requires enabling the parser plugin: 'optionalChaining' (68:33) in "components/CreateWeb.js"

Try yarn add relay@facebook/relay#master Chaining is super nice for all GraphQL nullables.
https://github.com/facebook/relay/issues/2452#issuecomment-389932217

But it's buggy, so don't use it yet. https://github.com/facebook/flow/issues/4303#issuecomment-385102833

Then fix // TODO: Use Optional Chaining.

React Native will support it soon as well. Yay!


SPA - Values are removed from the form until onUpdate resolves

Description
In a SPA application, values are removed from the form until onUpdate resolves. The result is a weird UX for the end user.
If applicable, a MRE
https://stackblitz.com/edit/sveltekit-superforms-bug-reporting-gpc2pm?file=src%2Froutes%2F%2Bpage.ts,src%2Froutes%2F%2Bpage.svelte

Submit behavior can be customized with these options: https://superforms.vercel.app/concepts/submit-behavior

None of the submit options changed this behavior. clearOnSubmit is about errors and messages, not values, and multipleSubmits is not related to the Issue.
I also tried defaultValidator: 'keep' and resetForm: false

You can call form.clear(): https://stackblitz.com/edit/sveltekit-superforms-bug-reporting-4jfvgg?file=src/routes/+page.svelte

The values shouldn't be removed on submit, I'll take a look and see what can be done.

Finally had some time to investigate this. It turned out onUpdate didn't wait for page invalidation, so the page was invalidated, loading the data again, clearing the form. I'll release a patch update for this soon.

@ciscoheat if you can guide me on what to change and where, I can open a PR

Thanks, but no need to do that, I've already fixed it. Will release an update tomorrow.

This should be fixed now in 0.8.7, just released. Let me know if that's the case!

@ciscoheat Fixed


XY clearance cannot exceed probe depth

If you prefer to avoid using the edge finding offset value you may want the "XY Clearance" value to be larger than your probing distance since your probe macro starting point is inside the corner.  In any case with the current rule your probe must be inside the corner to detect the work so having a rule for "XY Clearance" <= "probe depth" doesn't really make sense.

I am sorry I do not understand your argument.

since your probe macro starting point is inside the corner

The probe should be above the green point, that is above the corner itself regardless if it is an internal or external corner. The offset is the distance away from the corner along the edge to where the probe will touch the edge. The XY Clearance is the distance away from the edge. When the controlled point is at XY Clearance away from the edge it will first be moved Depth down and then the actual probing motion will be performed.

so having a rule for "XY Clearance" <= "probe depth" doesn't really make sense

Where is this rule to be found in the code? If it exists it is definitely incorrect.
XY Clearance must be less than the Probing distance not the Depth.
The Center finder had an invalid rule and message that I have fixed but not yet comitted.
The rule used the Offset as part of the rule and the error message was "Probing XY clearance too large for workpiece diameter." This has now been corrected to check the XY Clearance against the X/Y sizes (formely Diameter) and the message has been changed to "Probing XY clearance too large for workpiece X size." and "Probing XY clearance too large for workpiece Y size.".
This only applies to inside center probing so perhaps the message should end with "...hole size." or even the whole message should be completely changed to somthing more concise.
A new Edge build has just been uploaded, please check it out.
Moving forward it would be nice if you could upload the release folder somewhere. IMO a lot easier to relate to than reviewing pull requests, and a lot less work. It will also be easer for other users to review as there si no ned for a VS installation and meddling with code merges and what not.

I am sorry I do not understand your argument.

since your probe macro starting point is inside the corner

The probe should be above the green point, that is above the corner itself regardless if it is an internal or external corner. The offset is the distance away from the corner along the edge to where the probe will touch the edge. The XY Clearance is the distance away from the edge. When the controlled point is at XY Clearance away from the edge it will first be moved Depth down and then the actual probing motion will be performed.

so having a rule for "XY Clearance" <= "probe depth" doesn't really make sense

Where is this rule to be found in the code? If it exists it is definitely incorrect.
XY Clearance must be less than the Probing distance not the Depth.

this was a typo, i mean to say "XY Clearance" <= "probe distance"
for an external corner if you don't start your probe slightly inside the corner it will never contact because the probe distance will never be enough to trigger the probe assuming "XY Clearance" cannot be greater than the "probe distance"
If you can remove this constraint I can avoid using the offset value and still ensure my probe will not over travel.

A new Edge build has just been uploaded, please check it out.
Moving forward it would be nice if you could upload the release folder somewhere. IMO a lot easier to relate to than reviewing pull requests, and a lot less work. It will also be easer for other users to review as there si no ned for a VS installation and meddling with code merges and what not.

happy to do that and i'll check out the new build.


Energy Conservation for STFT

The project I am working on requires a short-time Fourier transformation. For this, I use scipy.signal.stft. From theory, we learn that the signal in time domain has the same energy as in time-frequency domain; Parseval's theorem (https://en.wikipedia.org/wiki/Parseval's_theorem). However, when I use scipy.signal.stft, I do not obtain the same amount of energy if I compare the computation for both values of energy. I am pretty sure, it is because there is some scaling involved when using scipy.signal.stft, so I spit through the source code. After some deep search, I have found a scaling factor of np.sqrt(1/(sum(win)**2)). However, using this scaling factor, does not work:
Example code:
fs = 10e3
N = 1e5
amp = 2 * np.sqrt(2)
noise_power = 0.01 * fs / 2
time = np.arange(N) / float(fs)
mod = 500*np.cos(2*np.pi*0.25*time)
carrier = amp * np.sin(2*np.pi*3e3*time + mod)
noise = np.random.normal(scale=np.sqrt(noise_power),
                         size=time.shape)
noise *= np.exp(-time/5)
x = carrier + noise

frame_size = 1000
window = scipy.signal.windows.hann(frame_size,sym=False)
f, t, Zxx = scipy.signal.stft(x, fs, window=window, nperseg=frame_size)
scale = np.sqrt(1/(sum(window)**2))
Zxx_scaled = Zxx/scale

Et=np.sum(x**2)
Ef=np.sum(abs(Zxx_scaled)**2)/N
print("Et = %.3f" % Et)
print( "Ef = %.3f" % Ef)

results in (depending on noise, but in the scale of):
Et = 1641328.607
Ef = 6158.539

Does anyone know how to properly scale the resulting STFT matrix values to obtain equal energy levels and prove energy conservation for the STFT?
(I am looking for a sum(window)**2 constant transformation (and window) and, as the window is used in the STFT and I-STFT, I assume I have a 'tight frame' transformation if I use the hann window. However, proving energy conservation is a first step.....)

I am not sure the answer to your question but recently I also tried to convert some custom STFT code that ensures the energy is conserved and was unable to do it with scipy.signal.stft's current API. So it's possible there is some bug or some limitation in our current code that prevents properly conserving the energy.
It's also possible that there is some scale factor that could be computed and applied to get equivalence, in which case we need to document it properly.

It sounds like the scaling you mention is these lines:
https://github.com/scipy/scipy/blob/e555bf30a35076cfe06d19c1d3e02b62d0312fa8/scipy/signal/spectral.py#L1803-L1811
where stft is hard-coded to use mode='spectrum' in _spectral_helper.
I wonder if the energy conservation problem only exists in the computation of one-sided STFTs, as we check the equivalence in the mean squared STFT magnitude to the power spectrum here, for the two-sided case:
https://github.com/scipy/scipy/blob/36ae01b16d6534c9e8c181959a33b8f6ff6a6f2b/scipy/signal/tests/test_spectral.py#L1158-L1176

@larsoner as an FYI, I've cleared the milestone (not much is happening here, and it's not a release blocker).

tl;dr: The internal function _spectral_helper() used by stft() can be parametrized to scaling='density' to provide the desired scaling. A solution might be to add that scaling parameter to stft().
Dealing with spectral densities can be quite finicky, so for reference the following script compares stf() scaling to using the rfft() directly on a stationary signal:
import numpy as np
from scipy import signal
from scipy.signal.spectral import _spectral_helper
import matplotlib.pyplot as plt

def my_stft(xx, fs=1.0, window='hann', nperseg=256, noverlap=None, nfft=None,
            detrend=False, return_onesided=True, boundary='zeros', padded=True,
            axis=-1, scaling='spectrum'):
    """This function differs to `signal.stft()` by exposing the `scaling` parameter. """
    freqs, time, Zxx = _spectral_helper(xx, xx, fs, window, nperseg, noverlap,
                                        nfft, detrend, return_onesided,
                                        scaling=scaling, axis=axis,
                                        mode='stft', boundary=boundary,
                                        padded=padded)

    return freqs, time, Zxx

# Generate a unit amplitude sine signal:
n, tau = 2**11, 10  # 16384 samples for a 10 s signal
m = 2**8  # window length
T = tau / n  # sampling interval

f0 = 50.4  # ensure to hit a frequency bin
t_x = np.arange(n) * T
x = np.sin(2 * np.pi * f0 * t_x)
print(f"The {f0} Hz sine signal is {tau} s long, consists of {n} samples, " +
      f"and has per definition the unit V.")
P_x = sum(x**2) / n  # signal power
print(f"The signal energy {P_x * tau:g} V²s is equal to power {P_x = :g} V² " +
      f"times duration {tau = :g} s.")

# Let's calculate a STFT with 'spectrum' and with `psd` scaling:
g = signal.windows.hann(m, sym=False)
kw = dict(fs=1 / T, window=g, nperseg=m, return_onesided=True)
f_stft, t_stft, Xs_stft = my_stft(x, scaling='spectrum', **kw)
Xd_stft = my_stft(x, scaling='density', **kw)[2]
a2_Xd_stft = Xd_stft.real ** 2 + Xd_stft.imag ** 2  # equals |Xd_stft|²

# For comparison, let's calculate a frequency line of the STFT directly with
# the rfft() and scale it to a magnitude spectrum or a PSD:
f_fft = np.fft.rfftfreq(m, T)
X_fft = np.fft.rfft(x[:m] * g)
X_mag = X_fft / (sum(abs(g)))  # unit area window
X_psd = X_fft * np.sqrt(T / sum(g ** 2))  # unit energy window
a2_X_psd = X_psd.real**2 + X_psd.imag**2

# Let's calculate the spectral power from the PSD:
df_fft = f_fft[1] - f_fft[0]
P_fft = np.sum(a2_X_psd) * df_fft
print(f"The one-sided spectral power {P_fft = :g} V² is half the signal power.")

# The spectral energy in signal can be calculated from the STFT as well:
df_stft, dt_stft = f_stft[1] - f_stft[0], t_stft[1] - t_stft[0]
Pt_stft = np.sum(a2_Xd_stft, axis=0) * df_stft  # integrate over f-axis
E_stft = np.sum(Pt_stft) * dt_stft  # integrate over t-axis
print(f"The energy of the one-sided STFT {E_stft = :g} V²s is half the signal energy.")

# Compare a frequency line of the STFT with the FFT:
fg2, (ax21, ax22) = plt.subplots(2, 1, sharex='all',  num=2, clear=True)
ax21.set(title="Magnitude Spectrum of $x(t)$ (unit is V)",
         ylabel="$|X(f)|$ in V", xlim=(0.9*f0, 1.1*f0))
ax22.set(title="Power spectral density", xlabel="Frequency $f$ in Hertz",
         ylabel=r"$\frac{d}{df}|X(f)|^2$ in V²/Hz")
k = len(t_stft) // 2  # pick a frequency line not to close to a border
ax21.plot(f_fft, abs(X_mag), 'C0-', alpha=.5, label="FFT")
ax21.plot(f_stft, abs(Xs_stft[:, k]), 'C1x--', alpha=.5, label="STFT (spectrum)")

ax22.plot(f_fft, a2_X_psd, 'C0-', alpha=.5, label="FFT")
ax22.plot(f_stft, a2_Xd_stft[:, k], 'C1x--', alpha=.5, label="STFT (density)")
for ax_ in (ax21, ax22):
    ax_.grid(True)
    ax_.legend()
plt.show()

Please note:
To ensure that the complete signal (energy) is captured by the STFT (more precisely: that it is a unitary mapping), the grid steps of the time-frequency grid need to be sufficiently small. E.g., Δf Δt ≤ 1 is an upper bound. See Sec. 7.5 in [1] for more details.
Even though the stft() can be used to obtain information of a signal's energy distribution in the time-frequency plane by utilizing density-scaling, the naming is a bit unfortunate, since a STFT it cannot be interpreted as an energy density:
A density implies that its marginal, e.g., integrating over f, is the corresponding (temporal) power density |x(t)|². Generally this is not the case for the STFT, due the window function not disappearing when integrating. The Wigner-Ville distribution has this marginalization property at the price of not guaranteeing non-negative values everywhere (which limits its usefulness considerably).
Furthermore, due to the Heisenberg uncertainty relation, a single point (t_p, f_p) in the time-frequency plane does not have a physical meaning — one has to look at areas of at least of size 1 to extract meaningful information about the energy distribution. See Sec 2 and Sec 3.3 in [1] for details.
Literature:
[1] Karlheinz Gröchenig, Foundations of Time-Frequency Analysis, Springer Science+Business Media, LLC, 2001.

The internal function _spectral_helper() used by stft() can be parametrized to scaling='density' to provide the desired scaling. A solution might be to add that scaling parameter to stft()... the naming is a bit unfortunate, since a STFT it cannot be interpreted as an energy density

It looks like density is already used publicly here:
https://docs.scipy.org/doc/scipy/reference/generated/scipy.signal.csd.html
If you think there is a better name for this mode, we could expose it and say that it's preferred, and keep 'density' around just for backward compatibility.
@vollbier it sounds like you have a good handle on this issue, would you be up for making a PR? I think the steps would be:

Add density argument
Add unit tests that show

That energy is preserved (i.e., Parseval's Theorem) when density is used, and
That when using scaling='density' on both STFT and ISTFT, you get your original signal back (round-trip test)

Then a follow-up PR could be made after that to add an alias for density to all the functions that have a density option (e.g., welch, csd, stft, etc.). It would be great if one variant was adapted from the code at the top of the issue (assuming it executes quickly enough).

@larsoner Concerning the naming { 'density', 'spectrum' } in csd()  and friends:   Densities in pure spectral  (or pure time) domains are unproblematic—so no problem there. Things become only hairy when looking at time-frequency distributions.
For the case of the STFT, a frequency line (i.e., fixed t) may be interpreted as a power spectral density (psd), but a  time-line (i.e., fixed f) is not a density function.  Hence, I would suggest to replace density with  psd only there.
If nobody else volunteers, I'd be happy to give a shot at writing a PR.

@vollbier this issue has been open for a while and nobody has worked on it, so feel free to open a pull request whenever you make some progress!


Add post-quantum cryptol specs and documentation

COS:

[x] Add All four NIST finalist algorithms
[x] Add README describing the algorithms/any info a user should know
[x] README(s) should include a section with "known issues" (e.g. Falcon spec issues, etc.)

[ ] Add corresponding issues for these caveats

[ ] Copy over issues from old project repo to this repo
[x] Add table of contents to top-level README
[x] Add appreciations for original spec authors

@andrew-bivin For adding and moving issues, perhaps we can do it after we merge? So that the issues correspond to main branch.


Webpack build navigation problems

When built and deployed to demo server (http://nhs-hackday.lfrg.uk/) navigation from the root url works, but trying to load pages directly fails with a 404 (e.g. http://nhs-hackday.lfrg.uk/graph). This is probably due to the nginx setup.

Changed nginx config to route to /index.html by default:
https://gist.github.com/cjus/b46a243ba610661a7efb


setting page - appearance

Add a simple theme setting option, close the issue for now, and reopen the issue for future settings.


Remove post-install message

Post-install messages are bad taste, and should be used ONLY for notifying about breaking changes (like "You are installing Daru 2.0, for porting from Daru 1.0 look at instructions [here]"

Ok. I kinda like the beer mug though :P

@v0dro - Me too. It was one of the "crazy inspirations" that made me interested in daru even without looking at the codebase. An impressive first impression, if you will. I was about to add it to daru-io too, but with a straw in the beer mug symbolizing the Import / Export of Daru. 😄

Art requires sacrifices!

Sad reacts only. 😢

@zverok alright.

Done in master.


fixes #250

checked output with master - no discrepancies as far as I can tell...

@daren-thomas can we keep "date" for now? other algorithms in the optimization part as well as on the output files of the demand call this vector date. It is easier to understand form our side.

done. it is just a really bad name, because, well a date is a singular date. time_steps explains more precisely what this is. dates would also work (but is still not as good).

Thanks, let's keep it in mind for the next milestone.....

Actually. I take that back. I have thought some more about it and now I get it. date is like all the other column names in tsd - except it is the index. So. Let's leave it :)


feat: Weather db

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

v1.10.0
v1.10.0
GitHub release

Your semantic-release bot :package::rocket:


Remove GetHeight from ClientMessage interface

Summary
Following implementation of #284, #285, and #286, GetHeight will no longer be necessary. This removal is necessary for the Wasm Light Client
Remove GetHeight from the ~Header~ ClientMessage interface. Usage in 07-tendermint can use the casted header function (cast to 07-tendermint type and use the concrete function)
Should be done after no longer setting the consensus state in updates in 02-client

For Admin Use

[x] Not duplicate issue
[ ] Appropriate labels applied
[x] Appropriate contributors tagged/assigned

Relayer operators might need consensusHeight (see comment)

Updated issue to reflect new interface naming 👍

After the discussion in #1208 linked above, the proposed solution moving forward is as follows:

Remove the GetHeight interface method from ClientMessage.
Return a list of heights []exported.Height from the new UpdateState interface.
Maintain the consensus_height event emitted from 02-client client update handler, but mark as deprecated for future removal. For example, with tendermint lightclients this will simply be heights[0] following a successful update.
Add an additional consensus_heights event, containing a list of updated heights. This provides flexibility for emitting multiple consensus heights from batched header updates.

closed! Great work @damiannolan


HARP-7856 Remove background tile when a covering tile is loaded.

Codecov Report

Merging #1202 into master will increase coverage by 0.11%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master    #1202      +/-   ##
==========================================
+ Coverage   52.94%   53.06%   +0.11%
==========================================
  Files         260      249      -11
  Lines       23390    23145     -245
  Branches     5177     5132      -45
==========================================
- Hits        12385    12281     -104
+ Misses      11005    10864     -141

Impacted Files
Coverage Δ

...e/harp-webtile-datasource/lib/WebTileDataSource.ts
34.4% <0%> (-0.56%)
:arrow_down:

@here/harp-mapview/lib/DataSource.ts
86.58% <100%> (+0.33%)
:arrow_up:

@here/harp-mapview/lib/BackgroundDataSource.ts
97.61% <100%> (+0.05%)
:arrow_up:

@here/harp-mapview/lib/Tile.ts
71.71% <100%> (+6.64%)
:arrow_up:

...e/harp-mapview/lib/geometry/TileGeometryCreator.ts
30.05% <50%> (+3.64%)
:arrow_up:

@here/harp-mapview/lib/VisibleTileSet.ts
73.01% <95.83%> (+2.23%)
:arrow_up:

...re/harp-text-canvas/lib/rendering/TextMaterials.ts
42.85% <0%> (-34.07%)
:arrow_down:

@here/harp-mapview/lib/ThemeHelpers.ts
6.55% <0%> (-0.68%)
:arrow_down:

@here/harp-mapview/lib/text/TextStyleCache.ts
56.66% <0%> (-0.21%)
:arrow_down:

...rp-mapview/lib/text/TextElementsRendererOptions.ts
100% <0%> (ø)
:arrow_up:

... and 38 more

Continue to review full report at Codecov.

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

@heremaps-bot retest this please


Blend shape normals look incorrect on export

Describe the bug
Not sure if I'm doing something wrong, but when I export this particular file I get incorrect normals on the resulting glb file.
To Reproduce
Steps to reproduce the behavior:

Download blendStudy.zip
Export as-is as glTF
Open in modelviewer.dev/editor, or babylon sandbox, or...
See wrong normals compared to expectation and Blender

Expected behavior

Screenshots

.blend file/ .gltf
blendStudy.zip
Version

OS: Windows
Version: Both latest 3.x and 4.x beta

Using Convert to Mesh on the blendshaped model looks correct (on the right side):

Investigation in progress


MinUV mucking up bandpass solutions

Beware, me hearties - there be some monsters at sea. We've found some wonky bandpass solutions using a minUV parameter of "200" in AOcalibrate. This presented itself as a smooth ripple in the Q/U cubes. Through investigating the AOcalibrate solutions, we found the same ripple in the X/U bandpass amplitudes:

After reprocessing with a higher cutoff of "500", this issue was resolved:

A few notes:

The bandpass solutions are being impacted by short-baseline interference. The Sun is a likely suspect.
AOcalibrate appears to use UVdist in wavelengths. i.e. "500" is 500 $\lambda$
The ASKAPsoft pipeline uses a cutoff in metres of 200m by default. For reference, 200m at 888MHz is about 592 $\lambda$

To avoid this in future we need a couple of things:

[ ] #50
[ ] #51

Yes -- I think this just goes to my misunderstand of what calibrate -minuv actually does.
The set of rows dropped within calibrate are done:
if((_minUVW >= 0.0 && (u*u + v*v + w*w < _minUVW*_minUVW))||(_maxUVW>=0.0 && (u*u + v*v + w*w > _maxUVW*_maxUVW)))
    selected = false;

which means that the -minuv is specifying the cutoff in lambda. i did not appreciate this when I was transplanting the code. Silly pirate that I be, arrr.
For the moment I have bumped value up to 500, but ideally it should be varied automatically based on the maximum (or nominal?) frequency in the measurement set.

Actually, upon reflect I do think the argument is in meters. I just misunderstood things, like a silly pirate. It just needs to be bump up from 200 to something higher.

I have a branch addressing these points under caibator-validation.
I think I should try to add an option to opt into attempting to upload the image artifacts to prefect, i.e. enable the functionality via a CLI argument.

I believe these have been addressed in #52 , which has been merged.


Newsletter 11: Breaking changes in glam 0.9 update

Part of #172 ("Newsletter 11: Coordination/Tracking")

Merged, thanks for the PR!


Difference between SKELETON_DATA.md and CUSTOM_DATASET.md

@yysijie ,hello, sorry to interrupt you, when I read the help documentation:
SKELETON_DATA.md and CUSTOM_DATASET.md are used to make data sets, can you tell me the difference and connection between SKELETON_DATA.md and CUSTOM_DATASET.md？

@yysijie Yes, please explain this. I used the custom_dataset.md to generate JSON files. Now, should I use the kinetics_gendata.py  to build the database?


Add full async for queries

What is the goal of this PR?
Added fully async queries, which allows clients to queue up multiple queries that will run in sequence without requiring additional round-trips to receive results. This is especially useful for streaming large amounts of writes.
What are the changes implemented in this PR?

Refactored the Transceiver to use the same pattern as other clients, but with more complicated threading.
[x] Refactor the query iterator to use the new pattern.
[x] Change the API to introduce Future for queries.

looks good! So query -> sends initial request; .get() blocks until it has a first response, right?

Yes, that's correct.

To help with reviewing, here's an overview of what's going on with the threading:
There are (or should only be) two threads, User and GRPC.
The User thread is any thread that the client makes API calls with. Technically, it could be called concurrently, which we actually support. A key thing to bear in mind is that API only ever returns sequential streams, so iteration methods like computeNext() are never called in parallel, even if they are being called by a User thread (we can safely assume it's always the same User thread).
The GRPC thread delivers our responses from the server. There is only ever one GRPC thread.
The User thread needs to fetch responses corresponding to requests that it sent, so there needs to be a way to hand off the correct incoming responses to the correct User thread that is waiting for it.
We achieve this by using "collectors", which provide one method to accept and buffer responses from the GRPC thread, and another method to fetch the corresponding buffered response in a blocking manner from the User thread. The result is that the User thread can make a call to fetch a result and it will be blocked until the GRPC thread has received that result.
The general flow for a unary call is:

User initiates a query
User thread simultaneously sends a request to the server and queues a Collector.
The User thread blocks on the get() method of the Collector.
The GRPC thread receives a response.
The GRPC thread dequeues the Collector and delivers the response.
The Collector saves the response from the GRPC thread call and then unblocks the User thread call, returning the saved response.

In the streaming flow, the responses from the GRPC thread are placed into a blocking queue, which achieves this effect.

Ok - you want to put a shortened version of that in the code itself or not?

Ok - you want to put a shortened version of that in the code itself or not?

What I actually want to do is refactor it in an upcoming PR so that the threading split is clear by class and interface. I also would like to introduce the idea of building in an "event-loop", which will require that refactor.


Instructions for finding the definition id only apply to classic pipelines

The system.definitionId variable referenced at the end of this page is only visible in the classic editor. For YAML pipelines it's not visible and it's not clear how to find the id.
Note that the ID is available in the URL of a YAML pipeline, so that could be added to this page if there isn't a better place to find it.

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

ID: b03d67d0-8738-72e6-dbe7-324c1784d4fc
Version Independent ID: bbb4d774-cd98-3ecb-7ccf-5f49e6f2b425
Content: Download Pipeline Artifacts task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/download-pipeline-artifact.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

You can still get to the old variables page, which will give this identifier, but it's not easy in YAML. +1 to the idea of just mentioning that it's in the URL.


Can you add the ability to use Named Credentials instead of setting headers (including authentication) in the code

What is missing from the application? Please describe.
I'd like the ability to used Named and External credentials instead of having to risk exposing Authentication tokens either in code or in some other setting.  Named and external credentials also provide the ability to change both endpoints used and authentication and callout headers without having to edit APEX code. It can be done using configuration
Describe the solution you'd like
Currently to send a request, you need to do something like this:
GraphQLRequest request = new GraphQLRequest(query)
.withHeader('Authorization', 'Bearer token');
// Provide GraphQL endpoint to the client constructor
GraphQLHttpClient client = new GraphQLHttpClient('https://your-gql-endpoint-url.com');
Using Named and External credentials, you'd create an External Credential (let's call it "GraphqlExternal") with a Named Principal called "Authorization" with a parameter called "Authorization" and value of the API Key
You'd then create a Named Credential (let's call it "GraphqlNamed")  that uses that External Credential and allows formulas in the header.  You'd add a Custom Header entry called "Authorization" and a formula value of {!$Credential.GraphqlExternal.Authorization}   You can also set other Header name-value pairs required such as
Content-Type = application/json
In your code, you'd then have a single line
GraphQLHttpClient client = new GraphQLHttpClient('callout:GraphqlNamed');
... which mimics how you'd used a Named Credential in a req.setEndPoint() command in System APEX
Describe alternatives you've considered
I've considered hardcoding credentials / API keys in code but this risks them leaking.  It also means that you can't run the same code across sandboxes and production environments unless you put keys in a custom setting or custom metadata (which also risks leaks)

Hi @stephenpstanley, thanks for your issue! Sounds like a nice feature indeed, I will see what I can do. Perhaps, I will be able to start during the next week

Hi Ilya
Thanks for the quick response. I'm looking at using your managed package for a corporate customer of mine - is it listed on the AppExchange and has it gone through the salesforce security review?
Stephen

From: Ilya Matsuev @.>
Sent: Sunday, 15 December 2024 11:12
To: IlyaMatsuev/Apex-GraphQL-Client @.>
Cc: stephenpstanley @.>; Mention @.>
Subject: Re: [IlyaMatsuev/Apex-GraphQL-Client] Can you add the ability to use Named Credentials instead of setting headers (including authentication) in the code (Issue #37)
Hi @stephenpstanleyhttps://github.com/stephenpstanley, thanks for your issue! Sounds like a nice feature indeed, I will see what I can do. Perhaps, I will be able to start during the next week
—
Reply to this email directly, view it on GitHubhttps://github.com/IlyaMatsuev/Apex-GraphQL-Client/issues/37#issuecomment-2543359668, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGFJDKAFYZZYP7TFMCKSWP32FSUMFAVCNFSM6AAAAABTT4ZM7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGM2TSNRWHA.
You are receiving this because you were mentioned.Message ID: @.***>

@stephenpstanley it's not a managed package, it's an unmanaged package that can be installed using the instructions from the readme file. It's not published to AppExchange. Therefore no, it didn't go through Salesforce security review

Hi @stephenpstanley,
I made a few tests and seems that you can already use named credentials like this:
GraphQLField countriesNode = new GraphQLField('countries')
    .withFields(new List<String> { 'name', 'capital' })
    .withField(new GraphQLField('languages').withField('name'))
    .withArgument('filter', new Map<String, Object> {
        'currency' => new Map<String, String> { 'eq' => 'EUR' },
        'continent' => new Map<String, String> { 'eq' => 'EU' }
    });

GraphQLQuery query = new GraphQLQuery(countriesNode);

System.debug('query: ' + query.build(true));

GraphQLRequest request = new GraphQLRequest(query);

// Specify named credentials here
GraphQLHttpClient client = new GraphQLHttpClient('callout:TestConnection');
GraphQLResponse response = client.send(request);

System.debug('response data: ' + JSON.serializePretty(response.getData()));

When sending GQL request, I'm still using the standard HttpRequest Apex class. So when you provide an endpoint like callout:something, Salesforce tries to find the named credentials with that name and alters the instance of HttpRequest right before it gets sent, setting the proper endpoint and headers.
Therefore, no changes are required here, you can go ahead and use named credentials like you proposed :)
Although, I'm going to put a not in the documentation about using named credentials.

That’s great news. I must admit I read the docs but didn’t every try it
I’ll alter my code and see how it goes
Stephen Stanley
On 24 Dec 2024, at 04:50, Ilya Matsuev @.***> wrote:

Hi @stephenpstanleyhttps://github.com/stephenpstanley,
I made a few tests and seems that you can already use named credentials like this:
GraphQLField countriesNode = new GraphQLField('countries')
.withFields(new List { 'name', 'capital' })
.withField(new GraphQLField('languages').withField('name'))
.withArgument('filter', new Map<String, Object> {
'currency' => new Map<String, String> { 'eq' => 'EUR' },
'continent' => new Map<String, String> { 'eq' => 'EU' }
});
GraphQLQuery query = new GraphQLQuery(countriesNode);
System.debug('query: ' + query.build(true));
GraphQLRequest request = new GraphQLRequest(query);
// Specify named credentials here
GraphQLHttpClient client = new GraphQLHttpClient('callout:TestConnection');
GraphQLResponse response = client.send(request);
System.debug('response data: ' + JSON.serializePretty(response.getData()));
When sending GQL request, I'm still using the standard HttpRequest Apex class. So when you provide an endpoint like callout:something, Salesforce tries to find the named credentials with that name and alters the instance of HttpRequest right before it gets sent, setting the proper endpoint and headers.
Therefore, no changes are required here, you can go ahead and use named credentials like you proposed :)
Although, I'm going to put a not in the documentation about using named credentials.
—
Reply to this email directly, view it on GitHubhttps://github.com/IlyaMatsuev/Apex-GraphQL-Client/issues/37#issuecomment-2559937053, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGFJDKG3UW7KZVYI2YXGZLT2HAWNHAVCNFSM6AAAAABTT4ZM7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZHEZTOMBVGM.
You are receiving this because you were mentioned.Message ID: @.***>

Perfect. Thank you

From: Ilya Matsuev @.>
Sent: Tuesday, 24 December 2024 04:50
To: IlyaMatsuev/Apex-GraphQL-Client @.>
Cc: stephenpstanley @.>; Mention @.>
Subject: Re: [IlyaMatsuev/Apex-GraphQL-Client] Can you add the ability to use Named Credentials instead of setting headers (including authentication) in the code (Issue #37)
Hi @stephenpstanleyhttps://github.com/stephenpstanley,
I made a few tests and seems that you can already use named credentials like this:
GraphQLField countriesNode = new GraphQLField('countries')
.withFields(new List { 'name', 'capital' })
.withField(new GraphQLField('languages').withField('name'))
.withArgument('filter', new Map<String, Object> {
'currency' => new Map<String, String> { 'eq' => 'EUR' },
'continent' => new Map<String, String> { 'eq' => 'EU' }
});
GraphQLQuery query = new GraphQLQuery(countriesNode);
System.debug('query: ' + query.build(true));
GraphQLRequest request = new GraphQLRequest(query);
// Specify named credentials here
GraphQLHttpClient client = new GraphQLHttpClient('callout:TestConnection');
GraphQLResponse response = client.send(request);
System.debug('response data: ' + JSON.serializePretty(response.getData()));
When sending GQL request, I'm still using the standard HttpRequest Apex class. So when you provide an endpoint like callout:something, Salesforce tries to find the named credentials with that name and alters the instance of HttpRequest right before it gets sent, setting the proper endpoint and headers.
Therefore, no changes are required here, you can go ahead and use named credentials like you proposed :)
Although, I'm going to put a not in the documentation about using named credentials.
—
Reply to this email directly, view it on GitHubhttps://github.com/IlyaMatsuev/Apex-GraphQL-Client/issues/37#issuecomment-2559937053, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGFJDKG3UW7KZVYI2YXGZLT2HAWNHAVCNFSM6AAAAABTT4ZM7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZHEZTOMBVGM.
You are receiving this because you were mentioned.Message ID: @.***>


Positive/negative lookbehind syntax is being identified as invalid in Monaco find dialog

monaco-editor version: v0.10.1 latest (see editor, here: https://microsoft.github.io/monaco-editor/index.html)
Browser: firefox, also VS Code editor
OS: Windows 10
Issue
In the Monaco sample editor (linked above), try to find any i's that are not immediately preceded by the letter r using the Find dialog with a regular expression. Steps:

Navigate to https://microsoft.github.io/monaco-editor/index.html.
In the embedded sample editor, press Ctrl+F.
Click the regex button.
In the search field, enter the following:
(?<!r)i

The editor currently shows an error, indicating that the search string contains an invalid regular expression group.
Expected behavior
The Monaco editor should support both positive and negative lookbehind in regular expressions, so that you can use those in your search strings.

This will work once JavaScript implements support for lookbehinds. i.e. this is nothing implemented in the Monaco Editor.
See https://v8project.blogspot.com/2016/02/regexp-lookbehind-assertions.html
https://github.com/goyakin/es-regexp-lookbehind


Institute Varification

K.J Institute of Engineering and Technology - Vadodara

https://www.kjit.org/
K J Campus
Opp. ITI, Javla-Savli, Savli - Halol Road,
PO. Savli - 391770
Dist. Vadodara, India.

@sbpolytechnic Pull request merged. Thank you!


Fix for CWE-1022  CWE-200

HTML links that open in a new tab or window allow the target page to access the DOM of the origin page using window.opener unless link type noopener or noreferrer is specified. This is a potential security risk.
In the following example, a JSX element is created that corresponds to an HTML link opening the URL http://example.com in a new tab. Since it does not specify a link type, that page will be able to access the DOM of the origin page.
var link = Example;
To fix this vulnerability, add a rel attribute:
var link = Example;
further details available at

CWE-1022
CWE-200

/preview

This particular file inherits from https://github.com/fastai/nbdev/blob/master/docs/_includes/image.html
So if you would like to make a PR against that, and I will change this as well.  Thanks,

This particular file inherits from https://github.com/fastai/nbdev/blob/master/docs/_includes/image.html
So if you would like to make a PR against that, and I will change this as well. Thanks,

I've raised PR for changes in https://github.com/fastai/nbdev/blob/master/docs/_includes/image.html, you'd review and merge the PR.


Correct rule description in web_apache_segfault.yml

Description
Rule description was "Detects a segmentation fault error message caused by a creashing apache worker process" and is now "Detects a segmentation fault error message caused by a crashing apache worker process"
Issues Resolved
Misspelling in rule description has been corrected.
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

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

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

Thanks, can you please amend this commit with -s -m @knarph for DCO.


Tab after dash accepted as valid separator in collection elements

The following is parsed as valid YAML (replace [TAB] with an actual tab character):
collection:
  - element 1
  -[TAB]element 2

It does seem to conform the spec: http://www.yaml.org/spec/1.2/spec.html#c-l-block-seq-entry(n)
What's wrong?

Ok, I figured out what is happening. I am consuming the YAML data in a Java application and leveraging the SnakeYAML  library for parsing. However, they are still at YAML 1.1, which apparently only accepts space after the dash:

Each block sequence entry is denoted by a leading “-” indicator, separated by spaces from the entry node.

Never mind, then. Thanks for looking into this.


require page-list when pagination included

The test that dc:source/source-of be present is working, but I noticed that there is no error if the page-list isn't present.

Sorry, my bad. Too many files open and looking at the wrong one...


Prisma Client Extension Error After Updating to 4.16.1

Bug description
I'm getting this issue with Prisma Client Extensions after upgrading to 4.16.1. This doesn't happen at all on 14.15.0. I'd love to know what's going on:
src/modules/common/prisma/prismaExtensions/useSupabaseRowLevelSecurity.ts:81:10 - error TS2615: Type of property 'AND' circularly references itself in mapped type '{ [K in keyof { AND?: Enumerable<current_locationScalarWhereWithAggregatesInput>; OR?: Enumerable<current_locationScalarWhereWithAggregatesInput>; ... 6 more ...; lat?: string | ... 3 more ... | DecimalWithAggregatesFilter; }]: Or<...> extends 1 ? { ...; }[K] extends infer TK ? GetHavingFields<...> : never : {} exte...'.

 81   return Prisma.defineExtension((client: BasePrismaClient) =>
             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 82     client.$extends({
    ~~~~~~~~~~~~~~~~~~~~~
...
104     }),
    ~~~~~~~
105   );
    ~~~

src/modules/common/prisma/prismaExtensions/useSupabaseRowLevelSecurity.ts:81:10 - error TS2615: Type of property 'AND' circularly references itself in mapped type '{ [K in keyof { AND?: Enumerable<eventsScalarWhereWithAggregatesInput>; OR?: Enumerable<eventsScalarWhereWithAggregatesInput>; ... 8 more ...; description?: string | StringNullableWithAggregatesFilter; }]: Or<...> extends 1 ? { ...; }[K] extends infer TK ? GetHavingFields<...> : never : {} extends FieldPaths<...> ? ...'.

 81   return Prisma.defineExtension((client: BasePrismaClient) =>
             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 82     client.$extends({
    ~~~~~~~~~~~~~~~~~~~~~
...
104     }),
    ~~~~~~~
105   );
    ~~~

src/modules/common/prisma/prismaExtensions/useSupabaseRowLevelSecurity.ts:81:10 - error TS2615: Type of property 'AND' circularly references itself in mapped type '{ [K in keyof { AND?: Enumerable<fcm_tokensScalarWhereWithAggregatesInput>; OR?: Enumerable<fcm_tokensScalarWhereWithAggregatesInput>; ... 5 more ...; platform?: string | StringNullableWithAggregatesFilter; }]: Or<...> extends 1 ? { ...; }[K] extends infer TK ? GetHavingFields<...> : never : {} extends FieldPaths<.....'.

 81   return Prisma.defineExtension((client: BasePrismaClient) =>
             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 82     client.$extends({
    ~~~~~~~~~~~~~~~~~~~~~
...
104     }),
    ~~~~~~~
105   );
    ~~~

How to reproduce
This is the extension I created and this is what I have:
// prisma-extension-enable-supabase-row-level-security

import { Prisma, PrismaClient as BasePrismaClient } from '@prisma/client';

export interface SupabaseRowLevelSecurityOptions {
  /**
   * The client extension name
   * @default 'supabaseRowLevelSecurity'
   */
  name?: string;
  /**
   * The name of the Postgres setting to use for the claims, `request.jwt.claims` by default.
   * Supabase sets using set_config() and get with current_setting()
   *
   * @default 'request.jwt.claims'
   */
  claimsSetting?: string;
  /**
   * A function that returns the JWT claims to use for the current request decoded from the Supabase access token.
   *
   * E.g.:
   *
   * {
   *   "aud": "authenticated",
   *   "exp":<PHONE_NUMBER>,
   *   "sub": "00000000-0000-0000-0000-000000000000",
   *   "email"<EMAIL_ADDRESS>   *   "phone": "",
   *   "app_metadata": {
   *     "provider": "email",
   *     "providers": [
   *       "email"
   *     ]
   *   },
   *   "user_metadata": {},
   *   "role": "authenticated",
   *   "aal": "aal1",
   *   "amr": [
   *     {
   *       "method": "otp",
   *       "timestamp":<PHONE_NUMBER>
   *     }
   *   ],
   *   "session_id": "000000000000-0000-0000-0000-000000000000"
   *  }
   */
  // eslint-disable-next-line @typescript-eslint/no-explicit-any
  claimsFn?: undefined | (() => Record<string, any>);
  /**
   * The error to throw when the policy check fails.
   */
  policyError?: Error;
  /**
   * Log errors to the console.
   * @default false
   */
  logging?: boolean;
}

const defaultSupabaseRowLevelSecurityOptions: SupabaseRowLevelSecurityOptions =
  {
    name: 'useSupabaseRowLevelSecurity',
    claimsSetting: 'request.jwt.claims',
    claimsFn: undefined,
    policyError: new Error('Not authorized.'),
    logging: true,
  };

export const useSupabaseRowLevelSecurity = (
  options: SupabaseRowLevelSecurityOptions = defaultSupabaseRowLevelSecurityOptions,
) => {
  const name = options.name || defaultSupabaseRowLevelSecurityOptions.name;
  const claimsFn =
    options.claimsFn || defaultSupabaseRowLevelSecurityOptions.claimsFn;
  const claimsSetting =
    options.claimsSetting ||
    defaultSupabaseRowLevelSecurityOptions.claimsSetting;
  const policyError =
    options.policyError || defaultSupabaseRowLevelSecurityOptions.policyError;

  return Prisma.defineExtension((client: BasePrismaClient) =>
    client.$extends({
      name: name || 'useSupabaseRowLevelSecurity',
      query: {
        $allModels: {
          async $allOperations({ args, query }) {
            const claims = claimsFn ? JSON.stringify(claimsFn() || {}) : '';
            try {
              const [, result] = await client.$transaction([
                client.$executeRaw`SELECT set_config(${claimsSetting}, ${claims}, TRUE)`,
                query(args),
              ]);

              return result;
            } catch (e) {
              if (options.logging) {
                console.error(e);
              }
              throw policyError || e;
            }
          },
        },
      },
    }),
  );
};

Expected behavior
This shouldn't cause any error.
Prisma information
Information added above.
Environment & setup
N/A
Prisma Version
Environment variables loaded from .env
prisma                  : 4.15.0
@prisma/client          : 4.15.0
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fbc245156db7124f997f4cecdd8d1219e360944 (at ../../../../.nvm/versions/node/v18.15.0/lib/node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.15.0-28.8fbc245156db7124f997f4cecdd8d1219e360944
Default Engines Hash    : 8fbc245156db7124f997f4cecdd8d1219e360944
Studio                  : 0.484.0
Preview Features        : multiSchema, postgresqlExtensions, clientExtensions

Thanks for splitting this out into its own issue.
Your "Prisma version" output still shows 4.15.0, and that you are still using clientExtensions. Can you please double-check that you are indeed running 4.16.1 by removing the preview feature flag and trying again?

@janpio My bad. I pasted the wrong prisma version (because I downgraded). However, I can confirm that in version 4.16.1, it does have an error versus in 4.15.0.

Hey @nocturnalflame thanks for the report. Could you please share your schema as well? Would you also mind trying<EMAIL_ADDRESS>&<EMAIL_ADDRESS>which may fix your issue? Thanks.

I took a look, and BasePrismaClient is not compatible with the extended client, if you remove the type BasePrismaClient to let it be inferred by us, then it should work as expected. Does that work for you?

I also faced this, and downgraded to 4.14.1, now working fine!

Ping @nocturnalflame, can you take a look at the suggestion by @millsp please?
(Same for you @moinulmoin, can you please try the suggestion? Thanks.)

@janpio I'm trying it right now. Will report in the next 30 minutes!

I actually still have the same issue:
Environment variables loaded from ../../.env
prisma                  : 4.16.2
@prisma/client          : 4.16.2
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at ../../../../../../.nvm/versions/node/v18.15.0/lib/node_modules/prisma/node_modules/@prisma/engines/migration-engine-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Default Engines Hash    : 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Studio                  : 0.484.0

Possibly related https://github.com/prisma/prisma/issues/7183

I haven't been able to reproduce this. I think we'd need your schema to be able to confidently reproduce. Could you share it with us? You can contact me via DM on slack if you don't want to make it public.

Hey @moinulmoin @nocturnalflame, could you please give 5.1.0 a try? If the problem still persists, could you please give us a reproduction?

Hey @moinulmoin @nocturnalflame, could you please give 5.1.0 a try? If the problem still persists, could you please give us a reproduction?

Hey, I am using 5.0.0 now. And it's working fine.

@nocturnalflame could you please give it a try on our latest version?

Hey @nocturnalflame, gentle ping to remind you that without your help we will not be able to make progress and will close the issue in a few days. We can always re-open it if you get back to us.

5.2.0 not working for me

Hey @hugosim97 could you please provide us with a reproduction?

Hey folks, with the lack of reproduction, we're now closing this issue. Feel free to re-open one if you have more info. Thanks


[demo] add more CI tests and examples

The demo chart is highly customizable but lacks CI tests and examples to ensure any changes will not break the expected working functionality.
CI tests and/or examples needed:

[x] Bring your own collector #629
[x] LivenessProbe #616
[x] Custom environment variables at default and component levels

We already have a LivenessProbe created for the featureflag service as part of every example and CI.


Errors are not shown in CI - Windows Test - ElevatedPesterTests

Non-terminating errors, specifically in BeforeAll sections, are not displayed in CI Test console.
Verbose and Warning messages are displayed just fine.
Not seeing errors in the output makes it really hard to investigate results, especially for test failures that happen only in CI, but not locally.
PS. looks like in Windows Test - UnelevatedPesterTests errors are shown.
Steps to reproduce

add Write-Error "Test Error for CI output" to any BeforeAll section
run this test file in CI Windows Test - ElevatedPesterTests

Expected behavior
error should show up in the output
Actual behavior
There is no error in the output

I mentioned this in a PR, https://github.com/PowerShell/PowerShell/pull/10226#issuecomment-545771337.


Company cards - "What's the Amex delivery file name" is missing a question mark

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.33-1
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Issue was found when executing this PR: https://github.com/Expensify/App/pull/48119
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:
Precondition:

Company cards feature is enabled.

Go to https://staging.new.expensify.com/settings/workspaces/policyID/company-cards/add-card-feed
Select AMEX.
Click Next.

Expected Result:
The sentence "What's the Amex delivery file name" should have a question mark.
Actual Result:
The sentence "What's the Amex delivery file name" is missing a question mark.
The sentence "What's the Mastercard distribution ID" (Mastercard) is also missing the question mark.
Workaround:
Unknown
Platforms:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/defea037-4b69-4713-9d5c-878770194ce3

View all open jobs on GitHub

We think that this bug might be related to #wave-control

Proposal
Please re-state the problem that we are trying to solve in this issue.
The sentence "What's the Amex delivery file name" is missing a question mark.
What is the root cause of that problem?
This copy is not correct
https://github.com/Expensify/App/blob/2830add7516b97c39d5c16ab5d1af8ab048f25c3/src/languages/en.ts#L2828
What changes do you think we should make in order to solve the problem?

Add question mark to the copy.

Proposal
Please re-state the problem that we are trying to solve in this issue.
The sentences "What's the Amex delivery file name" and "What's the Mastercard distribution ID" (Mastercard) is missing a question mark.
What is the root cause of that problem?

Its not included in en.ts file

What changes do you think we should make in order to solve the problem?

include ? at both place
https://github.com/Expensify/App/blob/2830add7516b97c39d5c16ab5d1af8ab048f25c3/src/languages/en.ts#L2828
https://github.com/Expensify/App/blob/2830add7516b97c39d5c16ab5d1af8ab048f25c3/src/languages/en.ts#L2832

What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Demoting from a deploy blocker, should be fixed by @waterim

Company cards are under NO QA label

Additionally I have found we are missing a ? here as well
https://github.com/Expensify/App/blob/2830add7516b97c39d5c16ab5d1af8ab048f25c3/src/languages/es.ts#L566
please fix along.

@joekaufmanexpensify Should it be closed as Company cards is under NO QA label?

not a deploy blocker as it's under beta

Yeah, let's close for now. This feature is still in implementation. We're going to start comprehensive manual testing soon, but any QA now is premature.


Service account on InstanceGroupManager

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
I'm trying to set up our cloud environment by using Pulumi and setting up the proper permissions (deprivileging  all default service accounts, and creating custom roles).
However, our service is using (regional) instance group managers, and in pulumi/gcp I haven't found any option for setting the service account for the manager to use. There seems to be an option to set the service account in the google-native version, but that library is developer preview and I intend to use this setup in production, so that's not an option unfortunately.
The workaround I'm trying out for now is to deprivileging all default accounts, and then explicitly setting the needed permissions/roles on the default accounts.
tl;dr: Add service account option to (Region)InstanceGroupManager.
I tried searching the issue list here in the repo, but couldn't find anything existing relating to this issue.

Hi @linco95. Thanks for raising this with us. This issue is tracked upstream as https://github.com/hashicorp/terraform-provider-google/issues/6858.

@iwahbe Thank you for directing me to the upstream issue, I didn't consider looking there. It's a problem throughout a lot of the gcp components. I'll keep tracking the issue upstream and continue working with the default account in the meanwhile.


Lots of build errors...

Hi!
Not sure if anyone still looks at this but I just built a new Aura Sync capable PC and wanted to use this library but I can't get it built. It gives a ton of build errors so I put them in a pastebin.
https://pastebin.com/Lf5KkhJe
I tried installing an older version of Visual Studio and an older version of Python to see if it would help but I just keep getting the same errors.
Any solutions?

Not sure if it is related, but are you sure that you are using a 32bit node? I had a lot of build errors with 64 bit node, too.

I am having the same issue. I have confirmed with NVM that I am using the 32bit node.

https://i.imgur.com/xG2KRWk.png
https://i.imgur.com/zpxwwov.png

So I was able to get it working by installing Node 8 (specifically 8.17.0 32bit).
I don't know if you have to go back quite that far, but I found this issue on an unrelated repository that listed a few functions that have been deprecated - the exact functions that are throwing errors in the build process. And I kept seeing that those functions aren't working in Node 12 while the issue references Node 8 so I just started with Node 8 and it worked.
If somebody wants to test with newer versions and arches feel free.


Release process

A release process (ideally automated in the CI pipeline) needs to be implemented and documented for all of the client language APIs. This includes:

Selecting specific builds (or Git commits) as releases and specifying their release version.
Publishing of release builds (to NPM registry, Maven Central etc.)
Creating GitHub releases and associated Git tags.

We need to be careful to use the lowest supported runtime version when building published packages. For example, Java 8 should be used explicitly rather than the default Java version in the build system (which I think is Java 11) since bytecode generated by later compilers may not be runnable by earlier JVM versions.

@denyeart the gateway node SDK is already being published without the @hyperledger namespace- are all the hyperledger node modules moving?

Discussed with @denyeart and from a TSC perspective, the recommendation is that all hyperledger projects should use the hyperledger scope
The existing fabric-gateway module will be deprecated and a new @hyperledger/fabric-gateway module published instead. There are very few existing users from the beta who will need to update their code, and hopefully having a deprecated module in the global namespace won't cause too much confusion for new users 🤞
For all Gateway SDKs, the plan is to release at version 1.0.0 and follow the Go versioning guidelines, i.e. stay at version 1.x.x keeping API changes compatible for as long as possible, only moving to a new major version if breaking API changes cannot be avoided
Mixing different language SDKs in the same repo means that the Go module includes the other SDKs, which is not ideal. I explored the possibility of releasing version 1.0.0 from a v1 directory, i.e. github.com/hyperledger/fabric-gateway/v1, however this makes the repository even more unusual from a Go module perspective, and the unrelated content would still be downloaded anyway. Leaving the Go module at the top-level is preferred until reaching a major version change

This Maven plugin looks like it might be useful for automating staging/release to Maven Central: https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin

Being able to sync the Hyperledger artifactory with Maven Central looks like it would be really nice if it's possible, but the staging plugin looks like a good potential interim solution, thanks.

Note to self: need to update github pages once the release is released! https://hyperledger.github.io/fabric-gateway/


Calendar reload

There should be a way to reload the calendar. I fetch data (calendar events) from a server and I want to add a dot for them on the calendar, but there isn't a way to trigger the calendar to reload after the data is received. Are there any plans to add such a method or is there a way I can force it to reload?

see the pull request, as soon as they merge my pull request there will be a method to refresh the calendar view, i can also work on a more advanced refresh depending on what you need

Okay sweet! Basically all I need the reload for is to add dots for days that have actives.

so the adding dots method in the demo has a parameter of dayView. so you can call the refreshMonth method that is new in my pull request and it will call the dots method in the demo for each dayView in the month... does that make sense?

done :)

I took a look at your PR. Basically I have this now:
extension CVCalendarContentViewController {
    public func refreshPresentedMonth() {
        for weekV in presentedMonthView.weekViews {
            for dayView in weekV.dayViews {
                removeCircleLabel(dayView)
                dayView.preliminarySetup()
                dayView.supplementarySetup()
                dayView.dotMarkers.removeAll()
                dayView.reloadContent()
            }
        }
    }
}

When I reload the dayView, clicking days leaves the elected circle visible. Am I missing something?

I'm not sure i understand your question
On Mon, Nov 9, 2015 at 3:39 PM, Anthony<EMAIL_ADDRESS>wrote:

I took a look at your PR. Basically I have this now:
extension CVCalendarContentViewController {
public func refreshPresentedMonth() {
for weekV in presentedMonthView.weekViews {
for dayView in weekV.dayViews {
removeCircleLabel(dayView)
dayView.preliminarySetup()
dayView.supplementarySetup()
dayView.dotMarkers.removeAll()
dayView.reloadContent()
}
}
}
}
When I reload the dayView, clicking days leaves the elected circle
visible. Am I missing something?
—
Reply to this email directly or view it on GitHub
https://github.com/Mozharovsky/CVCalendar/issues/156#issuecomment-155186235
.

Here is my setup:
I'm communicating with a server to retrieve calendar events. I then parse the events and want to add a dot marker on the calendar. Since the data is received after the calendar is loaded I need to reload everything that way the delegate methods are called to setup the markers on the calendar for given days. My dilemma is that when I get everything to reload and the dots to appear, selecting days leaves the election marker visible like so

oh yea so the dot marker isn't refreshed in my pull request. only the
circle view. i can work on refreshing the dot view in the next few days.
On Mon, Nov 9, 2015 at 3:43 PM, Anthony<EMAIL_ADDRESS>wrote:

Here is my setup:
I'm communicating with a server to retrieve calendar events. I then parse
the events and want to add a dot marker on the calendar. Since the data is
received after the calendar is loaded I need to reload everything that way
the delegate methods are called to setup the markers on the calendar for
given days. My dilemma is that when I get everything to reload and the dots
to appear, selecting days leaves the election marker visible like so
[image: screen shot 2015-11-09 at 12 43 23 pm]
https://cloud.githubusercontent.com/assets/2137365/11045992/7e59810e-86df-11e5-80a7-7b79edb03a77.png
—
Reply to this email directly or view it on GitHub
https://github.com/Mozharovsky/CVCalendar/issues/156#issuecomment-155187166
.

my refresh month calls my delete circle view method, which only deletes the
circle view not the dot view too. i'll work on the dot view
On Mon, Nov 9, 2015 at 3:50 PM, Joel Wasserman<EMAIL_ADDRESS>wrote:

oh yea so the dot marker isn't refreshed in my pull request. only the
circle view. i can work on refreshing the dot view in the next few days.
On Mon, Nov 9, 2015 at 3:43 PM, Anthony<EMAIL_ADDRESS>wrote:

Here is my setup:
I'm communicating with a server to retrieve calendar events. I then parse
the events and want to add a dot marker on the calendar. Since the data is
received after the calendar is loaded I need to reload everything that way
the delegate methods are called to setup the markers on the calendar for
given days. My dilemma is that when I get everything to reload and the dots
to appear, selecting days leaves the election marker visible like so
[image: screen shot 2015-11-09 at 12 43 23 pm]
https://cloud.githubusercontent.com/assets/2137365/11045992/7e59810e-86df-11e5-80a7-7b79edb03a77.png
—
Reply to this email directly or view it on GitHub
https://github.com/Mozharovsky/CVCalendar/issues/156#issuecomment-155187166
.

That would be great!

the pull request https://github.com/Mozharovsky/CVCalendar/pull/160 fixes your issue, pressure them to merge and you'll be able to do what you're intending to do

Cool, thank you for your work! Will test it out tonight!

Acutally, you are not reloading the dots in your "refreshPresentedMonth()" method, you'd need to call dayView.setupDotMarker() and dayView.topMarkerSetup() right after deleting them. Otherwise it's not a refresh at all.

If I may reenforce neugartf’s comment, the newly added refreshPresentedMonth() method does a fine job of removing existing Dot Markers (thanks so much for this addition :) ) but there doesn’t appear to be any attempt being made to repopulate the calendar’s date cells with potentially revised Dot Markers.

@16x9 i think that is now fixed in master ... since #180 :)

As stated correctly by @stefreak it is, hence closed!


[Bug]: Import app popup experience improvement

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

[ ] Text can be moved up a bit higher

[ ] Tooltip appears at the top right corner when app import is cancelled

Steps To Reproduce

Click on org settings on home page and choose import app to repro the above 2 scenarios

Environment
Release
Version
Cloud

This has been changed to a new experience here, this is the updated screen
@ramsaptami please have a look

Closing


Fixing wrong blending rect methods

Using Color.blend function instead of custom code
Fixes #31124
Related to #37503. Im leaving both PR's cause i'm not sure what would you prefer.

Approved by @reduz:
15:50 <reduz> Akien: yeah makes sense
15:50 <reduz> this is correct blending including source and destination alpha
15:51 <reduz> I am unsure why GPUs as of today cant do it

Thanks!

Cherry-picked for 3.2.2.


Order Model get parameter default

Is there a reason this parameter isn't defaulted to false like the other functions that do so?
https://github.com/Bandwidth/php-bandwidth-iris/blob/a10a1fd59534516ceb0b8ec50407c4bab26d1946/src/Order.php#L106

Hey @jklantz11 ,
Not sure why this was originally defined with tndetail set to true, the API endpoint uses false as the default.
I will discuss implications of changing this field with the team but see no reason not to follow the API.

Hey @jklantz11 ,
It looks to me like tnDetail is being set to false here in the order method of the orders class, which returns the order()->get() value and sets tnDetail to false by default.
It is not expected for order()->get() to be accessed directly - but instead through orders()->order() which sets tnDetail to false by default.
Let me know if my findings are incorrect or if you have any other questions. I will close this out for the time being but feel free to reopen this if you feel it hasnt been resolved properly


Typescript colorization issue

1.17, not 1.16
Looks fine if I delete the ++
if (a++ < b) {
}

export class A extends B {
}

This issue was moved to Microsoft/TypeScript-TmLanguage#526


Widevine support?

Hello! I have managed to get this extension built and running with godot 3.5, but was wondering if there is some way to get widevine CDM support?
I am currently testing on windows 10.
I have tried to follow the instructions here to get the latest dll and place it in the appropriate folder and nothing happened.
I have also found this however I don't think I can pass in "enable-widevine-cdm" as a config argument for this?
Any help or insight would be appreciated 😄

@monkeyman192 I'm sorry I know nuts about widevine (I have not yet head about it). https://peter.sh/experiments/chromium-command-line-switches/ Concerning https://magpcss.org/ceforum/viewtopic.php?f=6&t=16080 my knowledge in CEF starts to be rusty since I made long time I did not develop wrapper classes for Godot, but CefCommandLineArgs is not made for what you think. For what I remember (for what I understood reading the cefclient code example gdcef/addons/gdcef/thirdparty/cef_binary/tests/cefclient/), it's used to pass information to forked CEF processes like if you have pass command line directly to your Chromium application but does not make it active because you have to add some code and manage it (command line is to tell that you want this feature, but internally you have to set CEF settings to enable it) and that is why I does not offer API  CefCommandLineArgs in GDcef because in my opinion this is totally useless). So yep this will not help you to make it working.
If I understood well from https://www.magpcss.org/ceforum/viewtopic.php?f=6&t=17719 you should give the widevine extension to CEF. I started to implement plugins on our previous project https://github.com/stigmee/gdnative-cef/commit/55c10704bca3bdd98a6160ffc49be301737ba8cb since we implemented an extension, but I never finished because 1/ the coworker who made our extension never made it officially for version 2 (CEF only accept extension version 2 and now people use version 3, see https://magpcss.org/ceforum/viewtopic.php?f=6&t=10242) and my modified v2 extension worked only for CEFsimple gdcef/addons/gdcef/thirdparty/cef_binary/tests/cefsimple because I missed some functions in my code to make gdcef ables to load extension. In addition cef_web_plugin.h seems no longer exist.
Anyway adding extension for GDCEF can be nice to add some add block plugins.

https://bitbucket.org/chromiumembedded/cef/issues/3149/alloy-add-component-updater-support-for


[Python] Public API to consume objects supporting the PyCapsule Arrow C Data Interface

https://github.com/apache/arrow/pull/37797 is adding official dunder methods to expose the Arrow C Data/Stream Interface in Python using PyCapsules (https://github.com/apache/arrow/issues/34031 / https://github.com/apache/arrow/issues/35531).
In addition to official dunders to expose this to other libraries, we also need public APIs in pyarrow to import / consume such PyCapsules (or rather the objects implementing the dunders to give you the PyCapsule).
https://github.com/apache/arrow/pull/37797 already added this to the pa.array(..), pa.record_batch(..) and pa.schema(..) constructors, such that you can for example create a pyarrow array with pa.array(obj) given any object obj that supports the interface by defining __arrow_c_array__.
But that's not fully complete: we certainly need a way to construct a RecordBatchReader as well, where we don't have such a factory function available. For this, we could add a from_ function (similar to the existing from_batches) like RecordBatchReader.from_stream?

[x] #39217

(in addition there is also the Table, Field and DataType constructors, both those all have factory functions that could support this, similar to pa.array(..) et al)

Secondly, I am also wondering if we want to provide APIs that accept PyCapsules directly, instead of an object that implements the dunders. For example, if you are a library that has data in Arrow compatible memory, and you want to convert this to pyarrow through the C Data Interface, you might want to use a PyCapsule directly if your library doesn't expose a Python class that represents that data (to avoid that you need to create a small wrapper class just with the dunder to pass to the pyarrow constructor, although this is of course not difficult).

I also just hit an instance where having the pa.field constructor consume these objects would be helpful.
In particular, I was trying to read an arrow array with GeoArrow extension metadata but manually persist the field metadata:
schema_capsule, array_capsule = data.__arrow_c_array__()

class SchemaHolder:
    schema_capsule: object

    def __init__(self, schema_capsule) -> None:
        self.schema_capsule = schema_capsule

    def __arrow_c_schema__(self):
        return self.schema_capsule

class ArrayHolder:
    schema_capsule: object
    array_capsule: object

    def __init__(self, schema_capsule, array_capsule) -> None:
        self.schema_capsule = schema_capsule
        self.array_capsule = array_capsule

    def __arrow_c_array__(self, requested_schema):
        return self.schema_capsule, self.array_capsule

# Here the pa.field constructor doesn't accept pycapsule objects
field = pa.field(SchemaHolder(schema_capsule))
array = pa.array(ArrayHolder(field.__arrow_c_schema__(), array_capsule))
schema = pa.schema([field.with_name("geometry")])
table = pa.Table.from_arrays([array], schema=schema)

Aside from this, the only way to maintain extension metadata is to ensure that the extension types are registered with pyarrow, which is harder to control because if its global scope.

Yes, we should provide a public way to create a Field object as well (and from there you can also get a DataType).
(short term, I would say it is safe to use pa.Field._import_from_c_capsule, if you check that the method is available)
I suppose adding this to pa.field(..) would be the easiest, although signature-wise it's also not a great addition, given that right now this constructor always takes both a name and type required arguments)

Issue resolved by pull request 40818
https://github.com/apache/arrow/pull/40818


make molotov pypy3 compatible

we need to wait for a 3.5.x release

Works with two skips. https://travis-ci.org/loads/molotov/builds/245451713


Yreda1999/#76/create ros interface for pid param updates

Here are some things I still need to figure out if you know how to do these lmk:
i think i need to add fw_config.h as a dependency
i need to figure out how to compile my code
figure out id of arm board
i need to figure out if i need a msg file

Accidental close?

No, this is now being taken on by joshua


Use upgrade manifest in cilium upgrader

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Tabbar icon cropped

I've found that icon size getting here https://github.com/oblador/react-native-vector-icons/blob/master/RNVectorIconsManager/RNVectorIconsManager.m#L49 as
CGSize imageSize = CGSizeMake(fontSize, fontSize);

but it's wrong!!!
I understand that for calculating sizes of a glyph need using core text framework(https://github.com/waterlou/WTGlyphFontSet/blob/master/WTGlyphFontSet/WTGlyphFontSet.m#L137), but as temporary fix I've used
CGSize imageSize = CGSizeMake(fontSize * 1.5, fontSize);

Can't remember why I didn't go with the actual icon size from the beginning, but that should be fixed now.


UUID generation logic

UUID generation and use will be a consistent task across OSCAL document creation and updates.
Exposing UUID generation logic would be optimal for two scenarios currently:

Generation of a new UUID
idempotent Generation of a UUID given a specific input (maybe string?)

Task:
Create common UUID generation functions for use throughout the code base

Closed by #51


Bug: "sdk list java" returns a 404

Bug report
Downloaded sdkman using the instructions from the website. Ran sdk list java and received the following error:
$ sdk list java

<title>404 Not Found</title>

404 Not Found

nginx/1.15.12

System info
Ubuntu 20.04 (5.4.0-40-generic kernel)
5.0.16(1)-release
SDKMAN 5.5.12+269

Hi @drewandersen, can I ask you to try upgrading SDKMAN to the latest version please?
The current version is 5.8.3+506, and the API has changed a lot since 5.5.12 (released almost 3 years ago).
Please let me know how that goes.

No response and cannot replicate so closing this issue for now.

Hi!
I get this same error myself, but only when running sdkman through a proxy (here a Nexus raw proxy), could that be the issue here?
I use sdkman version: 5.12.2 on a company computer that is airgapped. We set up a proxy for the requests and have changed the environement variable SDKMAN_CANDIDATES_API=<proxyurl> and the proxy then points to https://api.sdkman.io/2.
This works perfectly for all candidates except java. I am also able to install java if I look up the version from another "normal" connected computer, so it is only when running sdk list java i get this issue. I attached an image showing the difference when running sdk list maven and sdk list java
I am aware this is not the default supported way of using sdkman, but as it works for all all candidates (at least the ones I have tested), could there be some kind of bug? Do you have any recommendations or fixes in mind for this, @marc0der ? :)
Best regards,
Jon Magnus


Angular 10 - ee* Error messages

Check that this is really a bug

[X] I confirm

Reproduction link
/
Bug description
Hi,
I just tried to install Swiper in my angular 10 project but I have these error message when I ng serve.

node_modules/@angular/core/core"' has no exported member 'ɵɵNgModuleDeclaration'
node_modules/@angular/core/core"' has no exported member 'ɵɵInjectorDeclaration'
static ɵinj: i0.ɵɵInjectorDeclaration;

Any solution ?
Thank you,
Have a nice day :)
Expected Behavior
No response
Actual Behavior
No response
Swiper version
7.0.4
Platform/Target and Browser Versions
macOs google Chrome
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

Swiper 7 compatible with Angular 12 +


Datepicker warning when datepicker-options is not supplied

Bug description:
When datepicker-options is not supplied, you get the warning "Literal date support has been deprecated, please switch to date object usage."
from here: https://github.com/angular-ui/bootstrap/blob/fc02fd1e307bcf2716eff56c058b003eef4a27db/src/datepickerPopup/popup.js#L209
This was committed recently:
https://github.com/angular-ui/bootstrap/pull/5732
Link to minimally-working plunker that reproduces the issue:
http://plnkr.co/edit/rk6oFGmgURnzloSmGNLm?p=preview
Click the first popup datepicker and view the console.  This problem does not arise if you include datepicker-options with min and max date.  This is strange, because it seems that this is checked for here:
https://github.com/angular-ui/bootstrap/blob/98eb8f1a77ca8d266d7b32b2d9fdf8dc96841c15/src/datepickerPopup/popup.js#L203
Version of Angular, UIBS, and Bootstrap
Angular:
1.5.3
UIBS:
1.3.1
Bootstrap:
3.3.6

This has already been fixed as part of 98eb8f1a77ca8d266d7b32b2d9fdf8dc96841c15


running  webcam.py  error.

hello,when running webcam.py has an error:
The configuration file used is  /configs/rotated/e2e_mask_rcnn_R_50_FPN_1x.yaml
python webcam.py
Traceback (most recent call last):
File "webcam.py", line 82, in
main()
File "webcam.py", line 73, in main
composite = coco_demo.run_on_opencv_image(img)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/demo/predictor.py", line 206, in run_on_opencv_image
predictions = self.compute_prediction(image)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/demo/predictor.py", line 240, in compute_prediction
predictions = self.model(image_list)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/maskrcnn_benchmark/modeling/detector/generalized_rcnn.py", line 65, in forward
features = self.backbone(images.tensors)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/container.py", line 97, in forward
input = module(input)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/maskrcnn_benchmark/modeling/backbone/resnet.py", line 147, in forward
x = self.stem(x)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/maskrcnn_benchmark/modeling/backbone/resnet.py", line 362, in forward
x = self.conv1(x)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/rotated_maskrcnn/maskrcnn_benchmark/layers/misc.py", line 33, in forward
return super(Conv2d, self).forward(x)
File "/home/onkymask/anaconda3/envs/rotated_maskrcnn/lib/python3.7/site-packages/torch/nn/modules/conv.py", line 339, in forward
self.padding, self.dilation, self.groups)
RuntimeError: Expected 4-dimensional input for 4-dimensional weight [64, 3, 7, 7], but got 5-dimensional input of size [1, 1, 32, 800, 1066] instead
Can you give me some advice?waiting for your reply,thank you very much!

Hey I didn't update the webcam.py code from the original repo. Have a look at my_tools/infer_demo.py, you can adapt the webcam part easily with the infer_demo.py code

Hey I didn't update the webcam.py code from the original repo. Have a look at my_tools/infer_demo.py, you can adapt the webcam part easily with the infer_demo.py code

when running infer_demo has an error,my infer_demo.py is:

error is:

Where should I change the configuration file?waiting for your reply

You're using the wrong infer_demo.py file (I guess I should remove this). Use the one in 'my_tools' folder.
my_tools/infer_demo.py

I tried it  as you said ,this is ok,thank you very much
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年10月16日(星期三) 凌晨4:07
收件人<EMAIL_ADDRESS>抄送: "。"1358420042<EMAIL_ADDRESS>主题: Re: [mrlooi/rotated_maskrcnn] running  webcam.py  error. (#5)
You're using the wrong infer_demo.py file (I guess I should remove this). Use the one in 'my_tools' folder.
my_tools/infer_demo.py
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Fixing packer.json file to work with newer versions of packer

In newer versions of packer, the packer.json file fails:
Failed to parse template: 4 error(s) occurred:

* variable docker_commit: '' expected type 'string', got unconvertible type 'bool'
* variable docker_pull: '' expected type 'string', got unconvertible type 'bool'
* variable include_x: '' expected type 'string', got unconvertible type 'bool'
* variable docker_autostart: '' expected type 'string', got unconvertible type 'bool'

This patch fixes those errors

Thanks for the fix @kellrott! Merged as https://github.com/galaxyproject/planemo-machine/pull/46. Small point is that packer.json shouldn't be updated directly. Need to update packer.yaml and do make packer to rebuild packer.json.


Monitor AppStateDb for send_to_ingress port.

Monitor AppStateDb for send_to_ingress port.
Build:
divya@bb9b9914ce91:/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
DEBUG: Rule 'com_github_nelhage_rules_boost' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1619053724 -0700"
DEBUG: Repository com_github_nelhage_rules_boost instantiated at:
/sonic/src/sonic-p4rt/sonic-pins/WORKSPACE.bazel:73:9: in
/var/divya/.cache/bazel/_bazel_divya/5fd88bad78ef03829a4685c83637a020/external/com_github_p4lang_p4c/bazel/p4c_deps.bzl:25:23: in p4c_deps
Repository rule git_repository defined at:
/var/divya/.cache/bazel/_bazel_divya/5fd88bad78ef03829a4685c83637a020/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in
INFO: Analyzed 223 targets (0 packages loaded, 0 targets configured).
INFO: Found 223 targets...
INFO: Elapsed time: 0.241s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test:
divya@bb9b9914ce91:/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS ...
DEBUG: Rule 'com_github_nelhage_rules_boost' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1619053724 -0700"
DEBUG: Repository com_github_nelhage_rules_boost instantiated at:
/sonic/src/sonic-p4rt/sonic-pins/WORKSPACE.bazel:73:9: in
/var/divya/.cache/bazel/_bazel_divya/5fd88bad78ef03829a4685c83637a020/external/com_github_p4lang_p4c/bazel/p4c_deps.bzl:25:23: in p4c_deps
Repository rule git_repository defined at:
/var/divya/.cache/bazel/_bazel_divya/5fd88bad78ef03829a4685c83637a020/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in
INFO: Analyzed 223 targets (0 packages loaded, 0 targets configured).
INFO: Found 144 targets and 79 test targets...
INFO: Elapsed time: 0.252s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
//gutil:collections_test                                        (cached) PASSED in 0.2s
//gutil:io_test                                                 (cached) PASSED in 0.3s
//gutil:proto_matchers_test                                     (cached) PASSED in 0.3s
//gutil:proto_test                                              (cached) PASSED in 0.2s
//gutil:status_matchers_test                                    (cached) PASSED in 0.2s
//gutil:table_entry_key_test                                    (cached) PASSED in 0.0s
//p4_pdpi:ir_tools_test                                         (cached) PASSED in 0.3s
//p4_pdpi/netaddr:ipv4_address_and_network_address_test         (cached) PASSED in 0.2s
//p4_pdpi/netaddr:ipv6_address_test                             (cached) PASSED in 0.2s
//p4_pdpi/netaddr:mac_address_test                              (cached) PASSED in 0.2s
//p4_pdpi/string_encodings:bit_string_test                      (cached) PASSED in 0.2s
//p4_pdpi/string_encodings:byte_string_test                     (cached) PASSED in 0.3s
//p4_pdpi/string_encodings:decimal_string_test                  (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:decimal_string_test_runner           (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test                      (cached) PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test_runner               (cached) PASSED in 0.1s
//p4_pdpi/string_encodings:readable_byte_string_test            (cached) PASSED in 0.2s
//p4_pdpi/testing:helper_function_test                          (cached) PASSED in 0.4s
//p4_pdpi/testing:info_test                                     (cached) PASSED in 0.1s
//p4_pdpi/testing:info_test_runner                              (cached) PASSED in 0.0s
//p4_pdpi/testing:main_pd_test                                  (cached) PASSED in 0.0s
//p4_pdpi/testing:mock_p4_runtime_server_test                   (cached) PASSED in 0.4s
//p4_pdpi/testing:packet_io_test                                (cached) PASSED in 0.1s
//p4_pdpi/testing:packet_io_test_runner                         (cached) PASSED in 0.0s
//p4_pdpi/testing:rpc_test                                      (cached) PASSED in 0.1s
//p4_pdpi/testing:rpc_test_runner                               (cached) PASSED in 0.1s
//p4_pdpi/testing:sequencing_test                               (cached) PASSED in 0.1s
//p4_pdpi/testing:sequencing_test_runner                        (cached) PASSED in 0.1s
//p4_pdpi/testing:table_entry_gunit_test                        (cached) PASSED in 0.4s
//p4_pdpi/testing:table_entry_test                              (cached) PASSED in 0.1s
//p4_pdpi/testing:table_entry_test_runner                       (cached) PASSED in 0.1s
//p4_pdpi/utils:annotation_parser_test                          (cached) PASSED in 0.3s
//p4_pdpi/utils:ir_test                                         (cached) PASSED in 0.3s
//p4rt_app/event_monitoring:app_state_db_port_table_event_test  (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:app_state_db_send_to_ingress_port_table_event_test (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:config_db_node_cfg_table_event_test (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:config_db_port_table_event_test     (cached) PASSED in 0.5s
//p4rt_app/event_monitoring:state_verification_events_test      (cached) PASSED in 0.5s
//p4rt_app/p4runtime:ir_translation_test                        (cached) PASSED in 0.4s
//p4rt_app/p4runtime:p4info_verification_schema_test            (cached) PASSED in 0.4s
//p4rt_app/p4runtime:p4info_verification_test                   (cached) PASSED in 0.4s
//p4rt_app/p4runtime:packetio_helpers_test                      (cached) PASSED in 0.5s
//p4rt_app/sonic:app_db_acl_def_table_manager_test              (cached) PASSED in 0.4s
//p4rt_app/sonic:app_db_manager_test                            (cached) PASSED in 0.4s
//p4rt_app/sonic:app_db_to_pdpi_ir_translator_test              (cached) PASSED in 0.5s
//p4rt_app/sonic:packetio_impl_test                             (cached) PASSED in 0.3s
//p4rt_app/sonic:packetio_port_test                             (cached) PASSED in 0.3s
//p4rt_app/sonic:response_handler_test                          (cached) PASSED in 0.4s
//p4rt_app/sonic:state_verification_test                        (cached) PASSED in 0.3s
//p4rt_app/sonic:vrf_entry_translation_test                     (cached) PASSED in 0.4s
//p4rt_app/sonic/adapters:fake_sonic_db_table_test              (cached) PASSED in 0.1s
//p4rt_app/tests:acl_table_test                                 (cached) PASSED in 0.7s
//p4rt_app/tests:action_set_test                                (cached) PASSED in 0.6s
//p4rt_app/tests:api_access_test                                (cached) PASSED in 0.5s
//p4rt_app/tests:arbitration_test                               (cached) PASSED in 0.6s
//p4rt_app/tests:fixed_l3_tables_test                           (cached) PASSED in 1.5s
//p4rt_app/tests:forwarding_pipeline_config_test                (cached) PASSED in 2.0s
//p4rt_app/tests:grpc_behavior_test                             (cached) PASSED in 5.0s
//p4rt_app/tests:p4_constraints_test                            (cached) PASSED in 0.4s
//p4rt_app/tests:p4_constraints_test_runner                     (cached) PASSED in 0.1s
//p4rt_app/tests:p4_programs_test                               (cached) PASSED in 0.8s
//p4rt_app/tests:packetio_test                                  (cached) PASSED in 2.9s
//p4rt_app/tests:port_name_and_id_test                          (cached) PASSED in 0.7s
//p4rt_app/tests:response_path_test                             (cached) PASSED in 1.2s
//p4rt_app/tests:role_test                                      (cached) PASSED in 0.6s
//p4rt_app/tests:state_verification_test                        (cached) PASSED in 0.7s
//p4rt_app/tests/lib:app_db_entry_builder_test                  (cached) PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                        (cached) PASSED in 0.0s
//p4rt_app/utils:table_utility_test                             (cached) PASSED in 0.3s
//sai_p4/instantiations/google:clos_stage_test                  (cached) PASSED in 0.2s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test (cached) PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test (cached) PASSED in 0.0s
//sai_p4/instantiations/google:sai_p4info_fetcher_test          (cached) PASSED in 0.3s
//sai_p4/instantiations/google:sai_p4info_test                  (cached) PASSED in 0.5s
//sai_p4/instantiations/google:sai_pd_proto_test                (cached) PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                 (cached) PASSED in 0.2s
//sai_p4/instantiations/google:union_p4info_up_to_date_test     (cached) PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test       (cached) PASSED in 0.0s
//sai_p4/tools:p4info_tools_test                                (cached) PASSED in 0.3s
Executed 0 out of 79 tests: 79 tests pass.
There were tests whose specified size is too big. Use the --test_verbose

@kishanps , i'm fine with these changes. Pl. let me know if we can go-ahead. If so, you can review and approve.
Thanks

@kishanps , i'm fine with these changes. Pl. let me know if we can go-ahead. If so, you can review and approve.
Thanks

@rkavitha-hcl Can you pls check the latest comments.


LAB_04_MFAConditionalAccessandAADIdentityProtection.md

English:
Identity Protection
Current Translation:
身分識別保護
Suggested Translation:
Identity Protection
Description:
Inconsistent translation. Global check

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run bugfix tool and waiting for result.


Provide a method for flushing all exporters

When my program panics, I'd like to:

log
flush all exporters
exit

Thank you @jadekler for the request, and welcome to OpenCensus!
Seems straightforward to implement, but I'll wait on the consensus of the team.
stats.FlushAllExporters() error?
trace.FlushAllExporters() error?

Thanks @odeke-em. 🙂Those methods look exactly like what I'm looking for!

@odeke-em on the error question, I am on the side of not returning an error. You have to ask yourself, which error do I want to return and then what do you expect the caller to do with it. In this case I think it's better to leave it up to the Exporter to log the error appropriately.

How is this different than flushing individual exporters? Not every exporter has a buffer. I'd suggest us not leaking this implementation detail to the stats and trace packages.
Flush the flushable exporters if it is required.


Jest: type objectContaining and peers as if they returned their described types

Coming from https://github.com/facebook/jest/pull/5751
cc @SimenB

@rattrayalex-stripe Can you rebase this against the latest version of master? That should allow the failing specs to pass.

Done, thanks for the tip @GAntoine


Official documentation says to not install on postgres user/ database which is the default.

Hello, the init script installs Postgis on the postgres database which is the default database and user on a classic Postgres installation.
The documentation here says to NOT do that: https://postgis.net/install/
I am unsure of why in big capitals it says to not do that, but I'm now adjusting the Postgis script to remove anything that creates an extension and I'm creating them manually in the database.

The init script installs into $POSTGRES_DB, which the postgres image defaults to $POSTGRES_USER. This does indeed default to postgres, so with all defaults it will install PostGIS into that database. In the absence of any documented adverse affects with running that configuration (other than it just not being a good idea), I don't think there's anything to be done in this image.


maliit-framework-qt5: fix postinst/postrm scripts

ERROR: do_rootfs: Postinstall scriptlets of ['maliit-framework-qt5'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Signed-off-by: Gianfranco Costamagna<EMAIL_ADDRESS>Signed-off-by: Gianfranco Costamagna<EMAIL_ADDRESS>Signed-off-by: Gianfranco Costamagna<EMAIL_ADDRESS>

Please note before merging: I don't think the logic of postrm is correct, you can't run it during build without using $D in the script

I pushed another commit to fixup the sadness.

Why don't you use pkg_postinst_ontarget_${PN} as suggested in the error message?

@shr-project I might do it, but I prefer to keep it simple :)
anyway, done now!

unfortunately it looks like there are no pkg_postrm_ontarget

I've squashed all 3 into 1 to keep it simple.
In master-next now, thanks
b61ea2c1..5144a99a  master-next -> master-next

thanks!


feat(gatsby-source-strapi): timeout setting for queries

Is your feature request related to a problem? Please describe.
Hey guys, the team I'm working with needs a feature that allows us to change the timeout for queries to Strapi. We utilize Strapi as a website builder and have many sites in the CMS. We have a couple of very large sites with over 100 pages, and when the query takes 60 sec or longer we get a 504 timeout error coming from [gatsby-source-strapi]/[axios]/lib/core/createError.js:16:15
Describe the solution you'd like
We'd like to be able to pass in our own timeout parameter for Strapi queries similar to how file fetching has the GATSBY_STALL_TIMEOUT env variable to alter the timeout settings (we've tried this and it doesn't work for our problem).
Describe alternatives you've considered
We have looked through the code to see where the query timeout is being set to 60 seconds and we're not able to find it.
Additional context

Sounds like a great feature. A PR would be welcome.

try changing the numbers in strapi  config/api.js  to get records per page.
maxLimit: 20 means 20 records per page, it should fix the timeout issue hope it helps.
module.exports = {
  rest: {
    defaultLimit: 20,
    maxLimit: 20,
    withCount: true,
  },
};

couldn't find how we can set or disable  this in `gatsby-source-plugin`

@yasirhaleem you can use queryLimit. It's not documented I just realized, but it's a feature.


Update iam auth version for Prow

Issue #, if available:
Description of changes:
Change the image version for iam auth
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve