'c' is not writable in folder name.

Type: Bug
When Capslock is ON-----
I can write 'C' simply by pressing the 'c' key on the keyboard. And to write 'c'  I'm pressing "SHIFT+c"  ... but nothing happens.
I can write other letters in upper case and lower case simply. Exceptionally' c' is not writable with keybinding "Shift+c" when capslock is on.
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:38:16.075Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 x 2904)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
7.95GB (3.03GB free)

Process Argv
--crash-reporter-id f0161305-f260-448a-84c0-e1af84fbfde2

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

flippidippi-theme
fli
0.0.8

code-runner
for
0.11.8

cmake-tools
ms-
1.12.27

cpptools
ms-
1.13.8

cpptools-extension-pack
ms-
1.3.0

material-icon-theme
PKi
4.23.0

cmake
twx
0.0.17

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
282f8724:30602487
gswce1:30612156
iaj6b796:30613358
89544117:30613380
fim-prod:30623723

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Problem is still in latest version.
On Wed, 21 Dec, 2022, 10:48 pm VSCode Triage Bot, @.***>
wrote:

Thanks for creating this issue! It looks like you may be using an old
version of VS Code, the latest stable release is 1.74.2. Please try
upgrading to the latest version and checking whether this issue remains.
Happy Coding!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/169768#issuecomment-1361694562,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZQJ3DGAWHTRZAAB3MZEAL3WOM3UZANCNFSM6AAAAAATF3HONI
.
You are receiving this because you authored the thread.Message ID:
@.***>

It looks like this is caused by a keybinding you might have defined. To remove all your keybindings, you can click on the gear icon, choose Keyboard Shortcuts, then press the Open Keyboard Shortcuts (JSON) button, and finally comment out all of the keybinding rules you have previously defined. You can then proceed to add back the keybinding rules which you want, uncommenting them:
https://user-images.githubusercontent.com/5047891/194806279-a9c10b8a-61a0-4f86-a9fc-c6884ace0053.mp4

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


read fbx file with texture issure

when i use pyprt to conver 3d models format(fbx to obj),there some issure with texture:
AssetWarning    0 'bin/formatchange.cgb' '' 'Potentially unsupported CGAC version 1.18 : newer than current (1.17)'
AssetWarning    0 '' '' 'Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/concrete_02_fine.jpg'
Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/build_01.jpg'
Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/concrete_02.jpg'
Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/concrete_01.jpg'
Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/concrete_02.jpg'
Failed to resolve texture with key 'file:/D://build_001//build_001.fbx/D:/build_001/texture/concrete_02_fine.jpg'

I think this issure with wrong path of texture.

Sorry for the very late response.
Do I understand correctly, that you are trying to create a textured initial shape from an FBX asset and then want to encode it to OBJ?
If yes, this will be supported in upcoming release 1.7: https://github.com/Esri/pyprt/blob/0fa19da2a92409765edc7c22451cd6b8a85246a4/CHANGELOG.md?plain=1#L7
This feature is already merged to the develop branch if you want to try it out (needs manual building of PyPRT module though).

Released in 1.7


raft.test failed for 386 arch on 0.9.0-rc7

Hi,
I faced the following issue on 0.9.0-rc7 at x86 arch.
[   64s] /usr/lib/go/pkg/tool/linux_386/8l -o $WORK/github.com/influxdb/influxdb/raft/_test/raft.test -L $WORK/github.com/influxdb/influxdb/raft/_test -L $WORK -w -extld=gcc $WORK/github.com/influxdb/influxdb/raft/_test/main.a
[   66s] $WORK/github.com/influxdb/influxdb/raft/_test/raft.test
[   68s] ok  	github.com/influxdb/influxdb	5.965s
[   68s] ok  	github.com/influxdb/influxdb/admin	0.031s
[   68s] ok  	github.com/influxdb/influxdb/client	0.017s
[   68s] ok  	github.com/influxdb/influxdb/cmd/influx	0.011s
[   68s] FAIL	github.com/influxdb/influxdb/cmd/influxd [build failed]
[   68s] ok  	github.com/influxdb/influxdb/collectd	0.018s
[   68s] ok  	github.com/influxdb/influxdb/graphite	0.010s
[   68s] ok  	github.com/influxdb/influxdb/httpd	2.269s
[   68s] ok  	github.com/influxdb/influxdb/influxql	0.040s
[   68s] ok  	github.com/influxdb/influxdb/messaging	1.716s
[   73s] ok  	github.com/influxdb/influxdb/raft	7.647s
[   73s] ?   	github.com/influxdb/influxdb/statik	[no test files]

Your build failed. Did you follow the build instructions in the README?

Running go test -x -v ./... I see the following:
# github.com/influxdb/influxdb/cmd/influxd_test
influxdb/cmd/influxd/config_test.go:31: constant<PHONE_NUMBER>0 overflows main.Size


⚠ Jenkins Plugins Artifactory has degraded performance

In 0b5a37a, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1213 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 335be79 after 16 minutes.


update metadata with normalized versions

Normalizes the version of vendors which ship major versions without minor/patch version.
Basically a replace of

"version":\s+?"(\d+)" with "version": "$1.0.0" (e.g. 21 --> 21.0.0)
"version":\s+?"(\d+)([-+].+)?" with "version": "$1.0.0$2" (suffixed variants e.g 21+13 --> 21.0.0+13)

@jdx This is unfortunately a huge PR i hope you don't mind. Added some basic tests to check for occurrences of non-semantic 'version' properties which should give us some confidence. Also tried to test this manually by pointing mise to pull versions directly from the ga/macosx/aarch64.json of this PR which looked fine IMO.
Also see #1 which addresses new versions coming in.

@jdx since #1 only deals with new Java versions we probably should also merge this to address the existing ones

@jdx It seems that the nightly update actions fail for some reason https://github.com/jdx/rtx-java-metadata/actions/runs/9448395893/job/26022304738


Removes the deprecated renew-before-expiry flag

What this PR does / why we need it:
Removes the --renew-before-expiry flag that was deprecated in v1.2.0
Users can specify how long before the real expiry a certificate should be renewed using Certificate.spec.renewBefore field and if they haven't set that, we use a default value at the time of calculating renewal- this is already the current behaviour, I have only removed the part that would overrwrite the default value with the one from the flag.
I think the calculation of renewal could be refactored a bit, but perhaps it would be better if before doing that there were some tests for the readiness controller, so I was going to add that to #3692
Fixes #3683
Signed-off-by: irbekrm<EMAIL_ADDRESS>Removes --renew-before-expiry flag that was deprecated in release v1.2.0

/kind cleanup

/lgtm
/hold

/approve
/hold cancel


Extracting P_gg from emulator

I have written some code to extract P_gg directly from the emulator (rather than w_p or deltaSigma). In that code I have called self._compute_p_2hcc etc. but I am getting the following error:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-6-f74c1312f5c2> in <module>
     21 Pk_dq_mg = DarkQuest.get_p_gm(hod, ks, z)
     22 if DQ_gg:
---> 23     Pk_dq_gg = DarkQuest.get_p_gg(hod, ks, z)
     24 else:
     25     Pk_dq_gg = np.copy(Pk_dq_mg)

~/Code/python_library/mead_DarkQuest.py in get_p_gg(self, k, redshift)
    724     self._compute_p_1hcs(redshift)
    725     self._compute_p_1hss(redshift)
--> 726     self._compute_p_2hcc(redshift)
    727     self._compute_p_2hcs(redshift)
    728     self._compute_p_2hss(redshift)

/usr/local/lib/python3.9/site-packages/dark_emulator/model_hod/hod_interface.py in _compute_p_2hcc(self, redshift)
    860             self._compute_ng()
    861         if self.p_hh_computed == False:
--> 862             self._compute_p_hh(redshift)
    863
    864         poff = self.gparams["poff"]

/usr/local/lib/python3.9/site-packages/dark_emulator/model_hod/hod_interface.py in _compute_p_hh(self, redshift)
    521
    522     def _compute_p_hh(self, redshift):
--> 523         self._compute_p_hh_spl(redshift)
    524
    525         logdens_de = self.g1.logdens_list

/usr/local/lib/python3.9/site-packages/dark_emulator/model_hod/hod_interface.py in _compute_p_hh_spl(self, redshift)
    439                 logdens2.append([logdens_m[j], logdens_p[j],
    440                                  logdens_m[j], logdens_p[j]])
--> 441         xi_dir_all = self._get_xiauto_direct_noint(np.concatenate(
    442             logdens1), np.concatenate(logdens2), redshift)
    443

/usr/local/lib/python3.9/site-packages/dark_emulator/model_hod/hod_interface.py in _get_xiauto_direct_noint(self, logdens1, logdens2, redshift)
    212         logdens2_mod = np.copy(logdens2)
    213         logdens2_mod[sel2] = -5.75
--> 214         xi_dir = self.xi_auto.getNoInterpol(
    215             redshift, logdens1_mod, logdens2_mod).transpose()
    216         if sel1.sum() != 0:

/usr/local/lib/python3.9/site-packages/dark_emulator/darkemu/auto.py in getNoInterpol(self, redshift, logdens1, logdens2)
     89         elif sindex >= 20:
     90             s0 = 20
---> 91             xia0 = np.array([rbs(-self.logdens_list, -self.logdens_list,
     92                                  self.xih_mat[:, :, s0, i])(-logdens1, -logdens2) for i in range(21)])
     93             return xia0

/usr/local/lib/python3.9/site-packages/dark_emulator/darkemu/auto.py in <listcomp>(.0)
     89         elif sindex >= 20:
     90             s0 = 20
---> 91             xia0 = np.array([rbs(-self.logdens_list, -self.logdens_list,
     92                                  self.xih_mat[:, :, s0, i])(-logdens1, -logdens2) for i in range(21)])
     93             return xia0

/usr/local/lib/python3.9/site-packages/scipy/interpolate/fitpack2.py in __call__(self, x, y, dx, dy, grid)
    905
    906             if (x.size >= 2) and (not np.all(np.diff(x) >= 0.0)):
--> 907                 raise ValueError("x must be strictly increasing when `grid` is True")
    908             if (y.size >= 2) and (not np.all(np.diff(y) >= 0.0)):
    909                 raise ValueError("y must be strictly increasing when `grid` is True")

ValueError: x must be strictly increasing when `grid` is True

Any idea on what is wrong? The ks array that I am passing to get_p_gg is strictly increasing.

FYI: The function I (actually Constance) has created to get the power is:
def get_p_gg(self, k, redshift):
    """get_p_gg

    Compute galaxy power spectrum :math:`\\P_\mathrm{gg}(k)`.

    Args:
        k (numpy array): 3 dimensional separation in :math:`h^{-1}\mathrm{Mpc}`
        redshift (float): redshift at which the galaxies are located

    Returns:
        numpy array: galaxy power spectrum
    """
    from scipy.interpolate import InterpolatedUnivariateSpline as ius

    self._check_update_redshift(redshift)

    self._compute_p_1hcs(redshift)
    self._compute_p_1hss(redshift)
    self._compute_p_2hcc(redshift)
    self._compute_p_2hcs(redshift)
    self._compute_p_2hss(redshift)

    p_tot_1h = 2.*self.p_1hcs + self.p_1hss
    p_tot_2h = self.p_2hcc + 2.*self.p_2hcs + self.p_2hss
    p_gg = ius(self.fftlog_1h.k, p_tot_1h)(k)+ius(self.fftlog_2h.k, p_tot_2h)(k)
    return p_gg

which is based on get_xi_gg from: https://github.com/DarkQuestCosmology/dark_emulator_public/blob/ee92edc1d8ac3de05187920a67d21466f6d9ea46/dark_emulator/model_hod/hod_interface.py#L1265

Further to this, this seems to be caused by attempting to evaluate at redshift=0. If I evaluate at redshift=0.01 the error goes away.

Thanks for raising this, Alex! Indeed, the redshift interpolation was treated differently within (0<z<1.4757) and outside (z<=0 or z>=1.4757) the support range of the emulator, with the endpoints treated as the latter case. The relevant function was only tested for the former case, and indeed, there was a bug in the latter case. I will fix this.


fix custom op

fix issue https://github.com/dmlc/mxnet/issues/4521
@lyttonhao See if this fixes it.

It works now. Thanks!


routing: use correct fees by searching backwards

@Roasbeef This is work in progress. Can you do a early check and tell me what you think?

What's this meant to fix? As they say, if it ain't broken, don't fix it...
On Mon, Jun 4, 2018, 2:12 PM Joost Jager<EMAIL_ADDRESS>wrote:

@Roasbeef https://github.com/Roasbeef This is work in progress. Can you
do a early check and tell me what you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/pull/1321#issuecomment-394501163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA87LsfwLbUu6WF5rdkmkOul6iBJ4Dp5ks5t5aKzgaJpZM4UZybJ
.

The original findPath implementation can come up with a path that is rejected in newRoute because of "channel graph has insufficient capacity". The reason is that findPath calculates with the same amt all the way, while newRoute takes into account that amt needs to increase with every hop (looking from target back to source).
This change make findPath use the correct fees and eliminates the possibility that newRoute returns the insufficient capacity error.

Gotcha, can you update the PR description, and also the commit messages with this information? Thanks!
In the past this wasn't an issue as each instance kicked off a k-shortest paths routine, so the failing paths would be excluded with a continue. We'll want to first get in the PR which adds fee limits to the path finding routine (say you don't want to pay more than 2% or w/e), as that will affect this implementation.

The fee limit PR as it is now will fail finding a route if the lowest weight route exceeds the max fee. There may be a possible route, but it isn't found because the time/fee weight balance doesn't favor that route.
When the fee limits are merged, I can update this PR to also take the fee limits into account already during findPath. This will lead to less failed route calculations, because the algorithm will continue exploring the graph for higher weight paths that do satisfy the fee limit (which means a higher total time lock).

@joostjager can you add a test case that exercise the failure scenario you are trying to fix? Will help  understanding the fix :)

Yes, I am working on that.

Quite some changes were needed to add this unit test in a maintainable way. I think trying to work towards a single test graph where many scenarios can be tested is better than setting up different graphs for different test cases.
Also, better visualization of the test graph would be useful. Maybe replace the ascii art with a graphviz generation script.
I see more potential work in the routing area, but will leave the scope of this PR as it is now to keep it manageable. Waiting for https://github.com/lightningnetwork/lnd/pull/1113

Also, better visualization of the test graph would be useful. Maybe replace the ascii art with a graphviz generation script.

The first graph there is just the most basic one, the other graphs themselves are a bit more complex, and agreed that having a rendering of them would make it easier to set up tests, however, it's also pretty straight forward to add additional vertexes/edges to the basic graph at runtime.

Yes indeed, runtime modifications is another option. Only makes it slightly more difficult to reason about what is happening.
The graph jsons contain info that could also be generated runtime. Another idea would be to describe the graph with only the essential values. For example, only aliases and generate the pubkeys (deterministically) in memory when the test runs. It makes the graph description short and can probably be described in go code instead of a separate json. Then, for a special test case like the one described in this issue, it is not much effort to bring up a custom graph.
This contradicts my comment above about working towards a single graph. It depends on the amount of effort required.

Implemented alternative way to describe graph in https://github.com/lightningnetwork/lnd/pull/1358

With regards to you other comments:

Naming and structure: Now that we are on the same page about the general idea of this PR, I will start that kind of finishing work. In this context, I also think that newRoute can be simplified. Because we already know that exact total amount to start the path with after findPath, we don't need to go backwards once again in newRoute.

I will look at msat vs sat. But channel capacities are an on-chain thing expressed in whole satoshis and I think it is good to keep that explicit by using btcutil.amount. Where did I say that edge weights are a bit off because of rounding? I know that the channel capacity check was not correct because of rounding, but don't think it affects the weights. Edge weights (on master) are indeed a bit off, but for another reason. And that is again that there is no running amount and fees (and therefore weights) are only based on payment amount.

Backward database lookup fixed.

I think this issue will fix another bug in path finding on master.
https://github.com/lightningnetwork/lnd/blob/9205720bea931d73e55a886f94d21a759180ff2b/routing/pathfind.go#L555
In this line, the weight for an edge is calculated. This calculation is performed for every edge, also the  edge from source to the first intermediate hop. The fee policy for that channel is not applicable, because source isn't forwarding a payment, but the weight of the policy is applied.
This may lead to non optimal routes. For example: source has a channel for which it charges a high relay fee. If source then initiates a payment, this channel will be incorrectly penalized.
In this PR, the weight is modified for the edge originating from the source to fix this problem.

Rebased after gofmt commits on master

Amended all commits with gofmt

Review comments addressed

Actually, I'll merge this as is, and then add a follow up commit to avoid the double DB transaction issue. Thanks for bearing with us through this review process! The final PR really turned out well!

Committed as 29b6bae4edea5de4096144c81674dbdb4636bd76!

I am happy that this one has been merged now. Will work the follow-up.

Ah, I see you fixed the open issues yourselves. I was thinking of adding a tx parameter to FetchLightningNode, but this works too of course.


fix node v8.x and above compatability

Fixes https://github.com/jugglingdb/sqlite3-adapter/issues/42
Atlassian's Confluence Plugin tutorial has a PoC that relies on jugglingdb-sqlite3, which is how I tripped over this.
/cc @1602 @haas85

🙏

Many thanks for merging this PR.
Any chance of releasing a new v1.x npm version with this included?

I released as 2.0.0, to avoid breaking anybody silently.


Tutorial steps are not reflecting portal options

When you reach the point to create the backend pool you need the vnet already created in order to add the subnet where the VMs will reside. We would need to create that vnet first thing instead of starting creating the app gateway as the article proposes.

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

ID: c4546e1f-9088-42ae-384d-df5237aa24e5
Version Independent ID: d22cab04-7c34-8365-aae4-413da2593843
Content: Tutorial - Create an application gateway with a web application firewall - Azure portal
Content Source: articles/application-gateway/application-gateway-web-application-firewall-portal.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@jpr2016git , Thank you for sharing your feedback.
Similar issue : https://github.com/MicrosoftDocs/azure-docs/issues/31798
I have assigned the issue to the author, and it will be addressed.
You can track the progress on the Issue which I linked here.


Hypixel Forums

Backstory

Data

name: Hypixel Forums
url: (https://hypixel.net/data-request)
url_CODE:
difficulty:

hard: Sites that require you to contact customer services or those that don't allow automatic or easy account deletion

notes: requires an extreme amount of PII

email:
email_subject: GDPR Request
email_body:
domains: hypixel.net

Name, address, and government-issued ID for a... Minecraft server. That's absolutely crazy. They don't even collect any of that information, what do they plan to "confirm" it against?

If you wish to cancel or delete your account, you can do so by accessing our platform or contacting us for assistance with the process. Our email is included at the end of the privacy policy.

Of course, there is no email included anywhere in their privacy policy.

We do not knowingly collect information for any child under the age of 13. If you are a child under the age of 13, you are not allowed to register nor participate on the Hypixel Forums.

I wonder if it would be easier to just tell them you're under the age of 13 and request account deletion...


Move @babel/preset-env to prod env

Solves release problem

What was the actual error you were seeing out of interest?
So my research a few month back led me to believe that the distinction between dependencies and devDependencies was largely organisational for webpacker stuff, but indeed it appears at though this isn't the case, and build dependencies should be listed under dependencies. I think I may have even moved some to the wrong location. (https://github.com/rails/webpacker/issues/117)
We should probably move the other babel dependencies as well.

Ahh, just saw it myself:
ERROR in ./app/javascript/packs/pipeline-graph.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Cannot find module '@babel/preset-env'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /home/runner/work/limber/limber/node_modules/babel-loader/lib/index.js
- /home/runner/work/limber/limber/node_modules/loader-runner/lib/loadLoader.js
- /home/runner/work/limber/limber/node_modules/loader-runner/lib/LoaderRunner.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/NormalModule.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/NormalModuleFactory.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/Compiler.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/webpack.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/utils/validate-options.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/utils/convert-argv.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/cli.js
- /home/runner/work/limber/limber/node_modules/webpack/bin/webpack.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at resolve (/home/runner/work/limber/limber/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:164:23)
    at resolveStandardizedName (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:111:7)
    at resolvePreset (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:59:10)
    at loadPreset (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:78:20)
    at loadPreset.next (<anonymous>)
    at createDescriptor (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:187:16)
    at createDescriptor.next (<anonymous>)
    at step (/home/runner/work/limber/limber/node_modules/gensync/index.js:261:32)
    at evaluateAsync (/home/runner/work/limber/limber/node_modules/gensync/index.js:291:5)
    at /home/runner/work/limber/limber/node_modules/gensync/index.js:44:11
    at Array.forEach (<anonymous>)
    at Function.async (/home/runner/work/limber/limber/node_modules/gensync/index.js:43:15)
    at Function.all (/home/runner/work/limber/limber/node_modules/gensync/index.js:216:13)
    at Generator.next (<anonymous>)
    at createDescriptors (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:142:41)
    at createDescriptors.next (<anonymous>)
    at createPresetDescriptors (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:134:17)
    at createPresetDescriptors.next (<anonymous>)
    at presets (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:73:26)
    at presets.next (<anonymous>)
    at mergeChainOpts (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:420:34)
    at mergeChainOpts.next (<anonymous>)
    at /home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:378:14
    at Generator.next (<anonymous>)
    at loadFileChain (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:232:24)
    at loadFileChain.next (<anonymous>)
    at buildRootChain (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:95:27)
    at buildRootChain.next (<anonymous>)
    at loadPrivatePartialConfig (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/partial.js:103:62)
    at loadPrivatePartialConfig.next (<anonymous>)
    at /home/runner/work/limber/limber/node_modules/@babel/core/lib/config/partial.js:149:25
    at Generator.next (<anonymous>)
    at step (/home/runner/work/limber/limber/node_modules/gensync/index.js:269:25)
    at /home/runner/work/limber/limber/node_modules/gensync/index.js:273:13
    at async.call.result.err.err (/home/runner/work/limber/limber/node_modules/gensync/index.js:223:11)

ERROR in ./app/javascript/packs/application.js
Module build failed (from ./node_modules/babel-loader/lib/index.js):
Error: Cannot find module '@babel/preset-env'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /home/runner/work/limber/limber/node_modules/babel-loader/lib/index.js
- /home/runner/work/limber/limber/node_modules/loader-runner/lib/loadLoader.js
- /home/runner/work/limber/limber/node_modules/loader-runner/lib/LoaderRunner.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/NormalModule.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/NormalModuleFactory.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/Compiler.js
- /home/runner/work/limber/limber/node_modules/webpack/lib/webpack.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/utils/validate-options.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/utils/convert-argv.js
- /home/runner/work/limber/limber/node_modules/webpack-cli/bin/cli.js
- /home/runner/work/limber/limber/node_modules/webpack/bin/webpack.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at resolve (/home/runner/work/limber/limber/node_modules/webpack-cli/node_modules/v8-compile-cache/v8-compile-cache.js:164:23)
    at resolveStandardizedName (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:111:7)
    at resolvePreset (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:59:10)
    at loadPreset (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/files/plugins.js:78:20)
    at loadPreset.next (<anonymous>)
    at createDescriptor (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:187:16)
    at createDescriptor.next (<anonymous>)
    at step (/home/runner/work/limber/limber/node_modules/gensync/index.js:261:32)
    at evaluateAsync (/home/runner/work/limber/limber/node_modules/gensync/index.js:291:5)
    at /home/runner/work/limber/limber/node_modules/gensync/index.js:44:11
    at Array.forEach (<anonymous>)
    at Function.async (/home/runner/work/limber/limber/node_modules/gensync/index.js:43:15)
    at Function.all (/home/runner/work/limber/limber/node_modules/gensync/index.js:216:13)
    at Generator.next (<anonymous>)
    at createDescriptors (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:142:41)
    at createDescriptors.next (<anonymous>)
    at createPresetDescriptors (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:134:17)
    at createPresetDescriptors.next (<anonymous>)
    at presets (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-descriptors.js:73:26)
    at presets.next (<anonymous>)
    at mergeChainOpts (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:420:34)
    at mergeChainOpts.next (<anonymous>)
    at /home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:378:14
    at Generator.next (<anonymous>)
    at loadFileChain (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:232:24)
    at loadFileChain.next (<anonymous>)
    at buildRootChain (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/config-chain.js:95:27)
    at buildRootChain.next (<anonymous>)
    at loadPrivatePartialConfig (/home/runner/work/limber/limber/node_modules/@babel/core/lib/config/partial.js:103:62)
    at loadPrivatePartialConfig.next (<anonymous>)
    at /home/runner/work/limber/limber/node_modules/@babel/core/lib/config/partial.js:149:25
    at Generator.next (<anonymous>)
    at step (/home/runner/work/limber/limber/node_modules/gensync/index.js:269:25)
    at evaluateAsync (/home/runner/work/limber/limber/node_modules/gensync/index.js:291:5)
    at /home/runner/work/limber/limber/node_modules/gensync/index.js:93:9


[android] remove the apk debuggable check and dependency on WXHack

          1 Warning

:warning:
Big PR

  Generated by :no_entry_sign: danger


Move "moderatable things" into separate class and inherit PrivateMessage from this class.

Implements #93.
This PR restructures some things so that VotableThing are a subclass of ModeratableThing, which is a class for Things that can have moderator actions (or have a score) applied to them.

I'm wondering if Subreddit should be under CreatedThing. I'd have to check the properties, but it might have similar ones.

Unfortunately, it doesn't have the author attribute (it does have the created and created_utc attributes). It can actually be moderated on (approved, removed, or spammed) if the user is an admin and is in admin mode (and there is a report button, but I doubt it does anything).
The fact that it doesn't implement created is really odd to me, especially because you can get that information on the desktop website.


is_visible error since updating to newest version

E5108: Error executing lua ...im/lazy/maximize.nvim/lua/maximize/integrations/tree.lua:13: attempt to call field 'is_visible' (a nil value)
stack traceback:
...im/lazy/maximize.nvim/lua/maximize/integrations/tree.lua:13: in function 'fn'
...im/lazy/maximize.nvim/lua/maximize/integrations/init.lua:11: in function 'clear'
...ocal/share/nvim/lazy/maximize.nvim/lua/maximize/init.lua:46: in function 'maximize'
...ocal/share/nvim/lazy/maximize.nvim/lua/maximize/init.lua:24: in function 'toggle'
[string ":lua"]:1: in main chunk

Do you have nvim-tree installed? What version are you using?


Quiz repeated very soon despite being answered correctly

Listen to the colloquial Finnish and write in standard Finnish:
> se on
⚠ Incorrect. Please try again, in standard Finnish.
> hän on
✅ Correct.
The colloquial Finnish spoken was 'se on'.
Meaning 'zij is'.

[Five other quizzes]

Listen to the colloquial Finnish and write in standard Finnish:
> hän on
✅ Correct.
The colloquial Finnish spoken was 'se on'.
Meaning 'zij is'.

This bug may have the same cause as #826.


CLUO uses pod name during deletion checks

The CLUO only checks the pod name for eviction checks. This is unsound, as pod names are not guaranteed to be unique or tied to a specific node.
https://github.com/coreos/container-linux-update-operator/blob/master/pkg/agent/agent.go#L362
It also serializes these checks for all pods where really they should be concurrent.

Note that logic was taken from kubectl drain: https://github.com/kubernetes/kubernetes/blob/v1.8.1/pkg/kubectl/cmd/drain.go#L565-L585 (and https://github.com/kubernetes/kubernetes/blob/v1.8.1/pkg/kubectl/cmd/drain.go#L475-L477)
I believe kubectl drain will have a similar problem.

Context: Specifically this is to address etcd-operator and prometheus-operator which always create pods with the same name, even if CLUO deletes them.

This is generally allowed though, as the Kubernetes documentation states[1] (my emphasis added):

A given pod (as defined by a UID) is not “rescheduled” to a new node; instead, it can be replaced by an identical pod, with even the same name if desired, but with a new UID (see replication controller for more details).

https://kubernetes.io/docs/concepts/workloads/pods/pod/#what-is-a-pod

You should also check if there's a bug upstream already and, if not, file one.


[SMALLFIX]ADD # IN README ##Building applications with Alluxio

In the case of the same official website document, remove an equal sign to make it look more beautiful

Merged build finished. Test PASSed.

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


prepare release 19.3.0

It's March in UTC, so it's going to be release 19.3.0.

The test failures are because typeshed isn't clean under the latest version of flake8. I'm fixing that in python/typeshed#2820 and I'm going to ignore it here for now.


feat(backend,clerk-js,types): Support the new LinkedIn OAuth Provider

Description
LinkedIn has changed the OAuth flow by replacing it with OpenID Connect. We have already added support for this in the backend.
Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[x] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[x] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

This is ready. The new provider's name will be set in dashboard.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Don't upper bound licence headers year

Description
License headers were currently upper bounded by year which often wasn't updated making the license in some ways invalid. After approval found here I'm changing this to only include start year.

For contributor use:

[x] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report

Merging #476 (cd233aa) into master (866aaac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #476   +/-   ##
=======================================
  Coverage   54.99%   54.99%
=======================================
  Files          37       37
  Lines        2002     2002
=======================================
  Hits         1101     1101
  Misses        757      757
  Partials      144      144

Flag
Coverage Δ

unittests
54.99% <ø> (ø)

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

Impacted Files
Coverage Δ

pkg/flowkit/account.go
50.00% <ø> (ø)

pkg/flowkit/arguments.go
25.97% <ø> (ø)

pkg/flowkit/config/account.go
66.66% <ø> (ø)

pkg/flowkit/config/config.go
44.44% <ø> (ø)

pkg/flowkit/config/contract.go
31.03% <ø> (ø)

pkg/flowkit/config/deployment.go
17.39% <ø> (ø)

pkg/flowkit/config/emulator.go
0.00% <ø> (ø)

pkg/flowkit/config/json/account.go
86.30% <ø> (ø)

pkg/flowkit/config/json/config.go
37.50% <ø> (ø)

pkg/flowkit/config/json/contract.go
91.11% <ø> (ø)

... and 27 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 866aaac...cd233aa. Read the comment docs.


add 4d integer reading subroutine to formatter

Added subroutine that reads 4d integer to formatter
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Trivial change (affects only documentation or cleanup)

Checklist:

[ ] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

Wow. 4d!


Investigate replacing Newtonsoft.Json with System.Text.Json

This might be a good idea as System.Text.Json is built into .NET, whereas Newtonsoft.Json is a third party library.
Even better would be if RestAssured.Net can support both, but that would probably be more work.
See https://github.com/eclipse-tractusx/portal-backend/pull/110#issuecomment-1635352855 for the discussion that drives this issue / request.

A big blocker for migrating to System.Text.Json is the lack of support for JSONPath at the moment: https://github.com/dotnet/runtime/issues/31068.
This would make the kinds of verifications and extractions we do in Body() and Extract() very cumbersome, if not unusable.

Given this comment: https://github.com/dotnet/runtime/issues/31068#issuecomment-1743438493
I'm going to close this one for now and stick with Newtonsoft.Json for the time being.

A big blocker for migrating to System.Text.Json is the lack of support for JSONPath at the moment: https://github.com/dotnet/runtime/issues/31068.

I had posted in that issue that I have a fully-compliant (to the upcoming spec) implementation of JSON Path in JsonPath.Net.  Did that not work for you?

@gregsdennis thank you for the comment. I don't know if it works or didn't work, because I haven't tried JsonPath.Net. It looks promising.
What's keeping me from making the migration at the moment is that I'd still be using a third-party library, although less of it as the (de-)serialization part can be handled by System.Text.Json itself. Are there any compelling reasons for making the switch, from your perspective?
Also, is there a specific reason there's no 1.0.0 version of JsonPath.Net (yet)? Just curious.
Happy to reopen this for a while.

Are there any compelling reasons for making the switch, from your perspective?

Well, if you need JSON Path functionality with STJ, then it's perfect.  It fully implements the pending spec.

is there a specific reason there's no 1.0.0 version of JsonPath.Net (yet)?

Yeah, the spec has been pretty much finalized, but it's not ratified into RFC status yet. Once that happens, I'll bump the library to 1.0.0.

Got it, thank you. I'll have a look at it soon (probably early January) and decide whether it's worth the effort. I'd be happy to get rid of Newtonsoft.Json in favour of STJ. Not that I don't like it, but why use a third-party library when there's a built-in one doing the job?
I could even see this as a first step to full removal once STJ supports JsonPath (which at some point they'll hopefully will).
Thank you once again.

To be honest, I'm not sure it will be included given there's a lib that supports it. Maybe.  There's a lot of call for JSON Schema as well (and I have that covered 😁), but the indication from the .net team so far is external support tends to be sufficient until it isn't.

Which library do you mean? Yours? Sorry about the confusion here (hey, it's a Saturday morning ;)

Yes, I was talking about mine, but it's kinda their approach to any new functionality right now. MS needs some hefty reasoning to warrant the resources to build something like JSON Path or Schema.  Just how it is right now.

Gotcha. Thanks. As I said, I'll have a good look at your library and what it would take to implement it.
And thank you, too, for mentioning the JSON Schema capabilities. Not too long ago I moved from NewtonSoft.Json.Schema to NJsonSchema (because of the licensing), I'm not necessarily looking to replace that yet again, but it might be good to have fewer different sources for third-party features.
Which one of your packages would I need there? All I need is the capability to pass in a schema definition as a string or as a typed object (like here: https://github.com/basdijkstra/rest-assured-net/blob/main/RestAssured.Net.Tests/JsonSchemaValidationTests.cs) and check that the actual response in a HttpResponseMessage matches the schema.
See also https://github.com/basdijkstra/rest-assured-net/issues/96

For JSON Schema, you can use the JsonSchema.FromText() method to get a schema instance... or you can define the schema type-safe-like using the builder.  Here's an example.
I have full docs for all my libs at https://docs.json-everything.net.  The main site (https://json-everything.net) is a playground where you can run everything in your browser (Blazor WASM).

Got it, thank you very much. As I said, I'll have a look soon, in the next couple of weeks.

Json Path is now an RFC!
https://www.rfc-editor.org/rfc/rfc9535.html


Backward compatibility breakage

Hi!
I'm not sure about when that occured, but I've updated my perl modules and now the whole minion API seems to be broken. Among the changes I have identified so far:

app->minion->backend->job_info isn't available anymore, have to use list_jobs instead.
app->minion->backend->list_jobs now returns a hash ref (was an array ref not so long ago).

I'm still investigating, but other pieces seem to have been moved. Maybe this is all normal, but I could not find any explanation so far so I'm a bit confused..

Minion version: 8.03
Perl version: (with perlbrew) 5.26.1
Operating system: Linux Mint Debian Edition LMDE 2 Betsy

BTW, thanks for all the good work, Mojo rocks. I've built Alambic on top of it, and your framework has proved great and flawless up to now.

Hello Boris,
Yes there were some breaking changes in the Minion version 8.0 release. Per the project rules breaking changes are allowed at major version releases. While we are sorry that your code is broken, this process has consistently allowed the Mojo project and related projects to improve. In this case the breaking changes allowed for a new Minion Admin UI (Mojolicious::Plugin::Minion::Admin) to be provided, which we hope you'll use and enjoy.
To help you update your code, the changes are always listed in the Changes file:
https://github.com/kraih/minion/blob/0dd0c312cc19886ecc859e1386c5f78800aaaa37/Changes#L15-L24

Hi Joel,
Thanks for the quick and to-the-point answer. Hum. my bad. :-)
As a sidenote, while I fully understand and appreciate this approach, I now realise that it can be brutal.. I had barely seen the specific upgrade of Minion in the cpanm command, even less that it introduced breaking changes. That's probably the price to pay for a always-up-to-date framework.
I will subscribe to the mailing list now..
Thanks, have a great day!

I am not sure if this applies to your situation, but with any Perl production deployment it's recommended to use Carton to pin your dependencies, so you can take care with any version updates. https://metacpan.org/pod/Carton (Note that carton exec is not actually needed, you can simply use the installed local/lib/perl5 library dir in whatever manner is suitable to your application.)


cannot build from multiple package paths

When using package > include in serverless.yml, alongside module: mymodule the package rules are completely ignored, and only the module is packaged up.
I have made a repo to demonstrate this issue
https://github.com/farridav/sls_python
Hope this is enough information to reproduce the issue, shout if not

Update: May be related to https://github.com/UnitedIncome/serverless-python-requirements/issues/168 and a whole bunch of other similar issues, though the linked repo might give more insight than other tickets..

Also, I'm not sure why, but this module is causing sls deploy to use a different artefact, when the original one is exactly what i need, see:
sls package && find .serverless/ -name *.zip -exec unzip -l {} \;

Serverless: Adding Python requirements helper to functions/my_function...
Serverless: Installing requirements of functions/my_function/requirements.txt in .serverless/functions/my_function...
Serverless: Zipping required Python packages for functions/my_function...
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Removing Python requirements helper from functions/my_function...
Serverless: Injecting required Python packages to package...
Archive:  .serverless/functions/my_function-sls-test-dev-my_function.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  2098-01-01 00:00   requirements.txt
       22  2098-01-01 00:00   .requirements.zip
      119  2098-01-01 00:00   handler.py
       34  2098-01-01 00:00   other_file.py
      458  2098-01-01 00:00   unzip_requirements.py
---------                     -------
      633                     5 files
Archive:  .serverless/my_function.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
       40  1980-01-01 00:00   functions/common/utils.py
       22  1980-01-01 00:00   functions/my_function/.requirements.zip
      119  1980-01-01 00:00   functions/my_function/handler.py
       34  1980-01-01 00:00   functions/my_function/other_file.py
        0  1980-01-01 00:00   functions/my_function/requirements.txt
      458  1980-01-01 00:00   functions/my_function/unzip_requirements.py
---------                     -------
      673                     6 files

The second of the two zip packages has everything i need in it, albeit inside an unnecessary functions folder

You are correct that this is a duplicate of #168, as such I'm gonna close this issue, follow the earlier one for any changes (sorry, I'm not likely to get to that anytime soon as I don't use that feature of the plugin and am short on development free time)


add: font-downloader

All the tests will pass, i ran the pre-commit.ci, and everythng was fine. Give it some time

All the tests will pass, i ran the pre-commit.ci, and everythng was fine. Give it some time

The pre-commit CI doesn't run all the checks, like formatting. Run the pre-commit hooks locally on your machine and push.

Any guide link for that? I mean how to do so....

It's in the README: https://github.com/pacstall/pacstall-programs#how-to-setup-the-environment-for-pacscript-development

Do I need to do something else?
 soumyaxubuntu  soumyas-HP-Laptop-15-bs1xx  ../pacstall-programs  font-downloader  pre-commit
trim trailing whitespace.............................(no files to check)Skipped
fix end of files.....................................(no files to check)Skipped
check yaml...........................................(no files to check)Skipped
check for added large files..........................(no files to check)Skipped
file contents sorter.................................(no files to check)Skipped
mixed line ending....................................(no files to check)Skipped
Test shell scripts with shellcheck...................(no files to check)Skipped
Check shell style with shfmt.........................(no files to check)Skipped

To run pre-commit on specific files, use the following command from the project root:
pre-commit run --files packagelist packages/font-downloader/font-downloader.pacscript

Note that this only needs to be done once. pre-commit will handle this automatically in the future, assuming you've installed it using pre-commit install

Yess, because, whenever there'll be some issue, 90% cases, I'll also face that. Also, I  always have a close eye in the repo, So, problem in that also.


[REQUEST] Update Puppeteer to 3.3.X

What would you like to have implemented?
Please update to Puppeteer 3.3.X

Puppeteer 5 pls

Puppeteer 5.1.0 got published 2 days ago

Sorry people, I've been busy. All these versions are now published.


decimate method for Evoked

I just noticed that Evoked doesn't have a decimate method. Should we add it?

YAGNI?

I agree with Eric, decimate is only useful for heavy datasets, evokeds shouldn't be in this category.

that's fine with me, just stumbled across a usecase in the example. simple index is sufficient.


Why does it show yesterdays commits in "Today"?

Seems weird to me that when I open it up in the morning it says I have lots of commits in the "Today" box as well as the today column in the "Commits" box that are from yesterday.
Should the counting of today's commits be by current date instead? Could there be a separate box/column for yesterday? Or if the preferred functionality is the current one, could it be renamed to "Last 24 hours"/"24h" for example?

I thinks the easiest fix would really be to rename the Today into something like "Last 24 hours".
@cvuorinen Maybe you can create a pull request. It was your idea 😉


How to bind to a unix domain socket?

I've saw this example code: https://github.com/hyperium/hyper/pull/1702#issuecomment-437186302 but there is no more serve_incoming method on Http.
Is it still possible to bind to a uds without the use of an additional crate? If yes, how?
I'm using:
tokio = { version = "0.2", features = ["full"] }
hyper = { version = "0.13.1", features = ["stream"] }

I've also tried:
let unix_listener = UnixListener::bind(socket_path)?;
let server = Server::builder(unix_listener.incoming());
server.serve(service).await?;

But unix_listener.incoming is not implementing the Accept trait, required by serve.

@FedericoPonzi there's https://github.com/softprops/hyperlocal but I was not able to get it work with the newest hyper.
I would love it if the authors of hyper would make it a native feature so that it can be kept up-to-date with hyper's ongoing releases.

But unix_listener.incoming is not implementing the Accept trait, required by serve.

You can use hyper::server::accept::from_stream:
let unix_listener = UnixListener::bind(socket_path)?;
let acceptor = hyper::server::accept::from_stream(unix_listener.incoming());
let server = Server::builder(acceptor);
server.serve(service).await?;

By the way, the tokio API changed slightly for 1.0.
use tokio::net::UnixListener;
use tokio_stream::wrappers::UnixListenerStream;

let unix_listener = UnixListener::bind(socket_path).expect("Failed to bind UNIX socket");
let stream = UnixListenerStream::new(unix_listener);
let acceptor = hyper::server::accept::from_stream(stream);
let server = Server::builder(acceptor).serve(make_service);

What about binding to both tcp and uds?


Consider / decide on icon set for standardization

The USWDS recommends using Font Awesome (FA).
Current Issue:
Meanwhile, Login does not have a standardized, default set option to pull from for the Login site/platform. Also, helpful for Login people to pull from for their slide decks.
This task is competed when:

[ ] When Login Design and stakeholders have discussed on the pros and cons of having an icon set

[ ] If merited, then which icon set? Font Awesome? If not FA, then which set?

[ ] When decided, we'll include instructions to the style guide:

On implementation
On accessibility
On usability

[ ] If not merited, then how do we ensure that we have a consistent system of icons?

Update: 18F Design is exploring icon sets to use. When decided, this will help login design team makes a choice.

Please consider the following icon needs for Partner dashboard when selecting an icon set:
icons for navigation [My apps, Admin, Groups, Emails, Reporting, Home, Make new..., Login, Logout, Apps]
icons for status [States for Apps: Active, In Production; Environments status: deploy-success, deploy-error, disabled]
icons for users status [Signed in, Never Signed In, Admin]
Icons for actions [edit, delete, back]

A current feature in progress will need an icon. Could we reopen this discussion?

@karlaturcios Yes — Is this something that could be created with a separate issue / story, or should it be shared in the same issue in this message thread?

@nickttng Probably the same issue. We are looking for an arrow icon which is part of the wish list of standard icons.

Migrated to LG-2637


ttnn.softmax fails with low pcc

Describe the bug
ttnn.softmax fails with low pcc of 0.8602608340954204 in PETR transformer module.
To Reproduce
Steps to reproduce the behavior:

Checkout keerthanar/petr_softmax_low_pcc_issue

Unzip the .pt file in this link and paste it inside tt-metal

Run the following command,
pytest tests/ttnn/unit_tests/operations/test_softmax.py::test_softmax_petr

Test fails as with the following command,
FAILED tests/ttnn/unit_tests/operations/test_softmax.py::test_softmax_petr[device_params={'l1_small_size': 79104}] - AssertionError: 0.8602608340954204

Please complete the following environment information:

WH n150

@keerthana-r-mcw , is this still an issue?

Yes, for the unit test we are getting low pcc, whereas for the whole module, we are getting 0.98 pcc.


Bringup llama3.1 8b on N300 to support 128k context length

I modified models/demos/llama3/demo/demo.py to be able to read in arbitrary context from Gutenberg books and asked it to quote and analyse parts of the first context-length of Frankenstein. 11623 tokens of prompt already produces bad output.

16k sequence length in test_llama_model_prefill.py passes with PCC: 0.968

Can you double check if the prompt is formatted correctly with the chat headers?

Also - just to ensure nobody does redundant work- I found 32k and 64k give bad pcc only because of the SDPA accumulation error that Jack is working on fixing

Can you double check if the prompt is formatted correctly with the chat headers?
Yeah it correctly used the instruct chat headers, I explicitly printed the prompt to check.

Hmm, previously I have seen good outputs even when prefill pcc is as low as 0.92


[POAE7-2412] Support partial avg check with old Cider data format

Gentle ping @yma11 @ZJie1 for review.


add: Lucent Blades

https://discord.com/channels/1044304864903168061/1159055987207053342

Sorry about that! Should have tried building it before


Partially reloading saved queries

Right now every flag from the original query is used when reloaded. It would be nice to be able to reload a query and replace certain flags, for instance, running
sootty file.vcd w "wire1, wire2" -s "time 32" -e "time 48" -S trace1
followed by
sootty -R trace1 -s "time 64" -e "time 72"
should display the same wire but at the new starting/ending time.

Added support for this with the latest commit in sub/YAML.

Fixed in #51.


API projection of the disease entity

Ticket closed as GraphQL API exposing disease index data as part of Alpha release. Further iterations to GraphQL API to be done with upcoming work (e.g. new data sources for phenotypes, driver work, etc.)


Compile-only API dependencies can be declared for JVM libraries

When writing a Java (or Groovy/Kotlin/Scala) library, there are cases where you require dependencies at compilation time which are parts of the API of your library, but which should not be on the runtime classpath.
An example of such a dependency is an annotation library with annotations that are not used at runtime. These typically need to be available at compile time of the library's consumers when annotation processors inspect annotations of all classes. Another example is a dependency that is part of the runtime environment the library is expected to run on, but also provides types that are used in the public API of the library.
This PR lets the Java Library add the compileOnlyApi configuration.
(This is also a follow up to #14240 where compileOnlyApi is already used)

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


There is error message when load the package "Bluetooth-max6675" after load the package "max6675"

Repro steps:
• Navigate to https://makecode.microbit.org/beta
• Click "Add Package" and input "max" in the InputBox of "search"
• Click the "max6675" in the search result
• Click "Add Package" and input "max" in the InputBox of "search"
• Click the "Bluetooth-max6675" in the search result
Expected result:

The package "max6675" could be loaded
The package "Bluetooth-max6675" could be loaded and there is no error message

Actual result:

The package "max6675" could not be loaded
The package "Bluetooth-max6675" could be loaded, but there is error message

Additional information:
If didn't load the package "max6675"  before loading the package "Bluetooth-max6675", the package "Bluetooth-max6675"could be loaded and there is no error message

This is fixed in alpha. Please validate and let me know.


SQLite-Net Missing Features

This is not really an issue, but more of a question I had after reading your README.  Can you provide a list or point me to a resource of missing features that SQLite-Net is missing over SQLitePCL.pretty?

Its been so long since I've looked at SQLite-NET. Off the top of my head, I know that it doesn't support some of the more obscure APIs that raw provides, custom collation functions, progress handlers, query interrupts, scalar and aggregate functions, WAL, blob read/writes using the C# Stream API, backup api, etc. The async API I've implemented supports cancellation tokens which I don't believe SQLite-Net supports.
All that said I think the more fundamental difference is the approach in using the API. SQLite-Net is designed with the use of its ORM in mind. I think the API provided by pretty is more flexible and in a more modern C# style. Its also layered so you can choose to only use the sync API, without brining in the Async dependency. I personally think the way I've implemented Async on top of RX is more powerful, as I allow you to dispatch multiple sql queries in parallel asynchronously and guarantee in order operation due to the use of an asynchronous operations queue (similar to the one used in akavache) vs. blocking a task thread and waiting for lock as is done in SQLite-Net.
I also prefer my take on an ORM. The key difference here, is that my "ORM" is really more of a SQL DSL that is used to generate SQL query strings that can then be prepared. This allows you to reuse prepared statements and cache them yourself for reuse. It also supports the builder pattern, so that your DAO objects can actually be immutable, which is a unique feature across any ORM I've ever used.
Finally, and I think this is the biggest win, I spent a lot of time getting resource management "right". SQLiteDatabaseConnection tracks all its prepared statements, blobs, back ups etc. Though all those interfaces are disposable, when you dispose an IDatabaseConnection you are pretty much guaranteed for it to cleanup everything correctly without throwing exceptions. It even implements a finalizer so if you leak the database connection it will cleanup all the database resources (though I highly discourage that of course).

Oh and of course SQLitePCL.pretty actually has a documented API: http://bordoley.github.io/SQLitePCL.pretty.Documentation/Help/html/R_Project_Documentation.htm

And how could I forget, I support foreign key constraints defined in the ORM table mapping definition. Although constraint is limited to being a long that is the PK value of the column in the other table. See: https://github.com/bordoley/SQLitePCL.pretty/blob/master/SQLitePCL.pretty.tests/OrmTests/QueryTests.Joins.cs

If you do end up using pretty, let me know. I'm definitely motivated to help out with its use.


⚠ Bofrost.be has degraded performance

In 5b05e94, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 851 ms

Resolved: Bofrost.be performance has improved in 2f4fe2d.


Extension point for resource icon

Support for extension point for resource icon
Due Date : 2015.07.17

hold this issue till next milestone


Not Run conda install pyosim -c pyomeca

Not run the command "conda install pyosim -c pyomeca". I can't install pyosim.

@jbarriosmuriel
There is no host of pyosim on conda.. for now, you have to clone the repo and install it by yourself.
cd download_path
conda activate name_of_you_environment
python setup.py install

Please note that on my computer I have to comment, in the file enviroment.yml (using #) the line pyomeca and install it via conda.

Pyosim is indeed on our anaconda repo. You just have to add conda-forge: conda install pyosim -c conda-forge -c pyomeca. We compiled opensim only for Linux OS btw.

That is weird.. I tried to install prior to m my message and it didn't work... I probably made a typo, I'll have another try when I have access to my computer..


ctrl+c still leaves behind stale FIFOs

Need to figure out how to catch signals.

Added in 301b718a48a63b65e02de2503aac1410830eb6f7.


Add Google form for users to give feedback

[ ] Add google form

Is this separate to the contact form we talked about before? What is the purpose of this form?

@philipdickinson yes it will be the one we use for soft launch referenced in #541
we can reconsider and turn this into a custom styled pop up for public launch.

Gotcha

[] Remove "To send us feedback or ideas for new datasets, you can contact us here." from intro copy
[] Change text at bottom of dataset list to: "Don't see the dataset you want? Email us at<EMAIL_ADDRESS>or provide feedback in this <>."  <> will link to Google form.
[] Change last sentence in ABOUT to: "To send us feedback or ideas for new datasets, you can contact us at<EMAIL_ADDRESS>or provide feedback in this <>."  <> will link to Google form.

@viviandien Can you provide a link to the form? Even if not finished yet?

https://goo.gl/forms/5KgujC2h1bw4eoTw2

I'm going to move this ticket off of soft-launch TODOs. We'll be sending out a Google form with more specific questions to this early group of users.
A more generic feedback form can be linked within the App for public launch.


Changes to Stylesheets Not Shown

In short, any changes I make to stylesheets are either not uploaded, or are uploaded but have no effect.
A) changes to application-liquid.css.liquid return: Asset Perform Update to assets/application-liquid.css at host ilf-performance.myshopify.com
Status: 422 Unprocessable Entity
Errors: Cannot overwrite generated asset 'assets/application-liquid.css'.
B) changes to application-liquid.css get pushed, but nothing changes.
Am I missing something? Documentation has not shed light on this thusfar.

FWIW my styles and scripts folders are empty. I've seen indications (and only indications) that .js and .css files should be in these folders under src/, but Slate didn't move them there when executed 'slate migrate'.

Resolved.


WIP: Child scorecard - Nutrition Assessment activity + scorecard mapping updates

#889

@mariano-dagostino please review

Implemented using another approach. Closing.


C#: Consider exposing optional fields as nullable

Is your feature request related to a problem? Please describe.
The way optional fields are implemented in C# is slightly hacky. For Strings, the underlying private field can be null, but the public property raises an exception upon null assignments. For non nullable (value type) fields, the underlying magic is even more scary.
Describe the solution you'd like
Consider implementing optional fields as nullable properties in C#. This has the following benefits:

It takes away the need for using Protobuf's Well Known Types to have fields that translated to nullable C# properties.
It allows you to use optional fields in expressions, such as when projecting EF Core models into protobuf messages. For strings for example, you currently need to create a partial class to add an additional property that exposes the internal private field without the null check.
It exposes info about whether a field has been set in a language natural way, in contrast to the several HasY properties and ClearY methods currently necessary. With the nullable wrapper types, null is considered a real value, whereas with optional fields, null can be considered a way to communicate that the value of an optional field is kept empty.

This is an enhancement request for protobuf, not gRPC (and so it doesn't belong here). Consider filing an issue at https://github.com/protocolbuffers/protobuf/issues.


Separate interpolation from verbatim text

This is the last PR I've had in works, it fixes some long-outstanding issues like this and #119.
I've had to change the embedded engines code a bit, I've made sure that the tests are passing but they may not be covering all use cases so feedback on that is highly appreciated.

:boom:  Thank you @little-bobby-tables and @Rakoth — you guys are awesome 💜


The source code compiles tensorflow off tensorrt is invalid.

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary):
TensorFlow version: master branch
Python version:3.6
Bazel version (if compiling from source):0.24
CUDA/cuDNN version:10.0/7.5
GPU model and memory:12G

When the source code compiles tensorflow, it closes TensorRT through the prompt of ./configure. But still reports: Could not find any NvInfer.h matching version '' in any subdirectory error.
Configure option：
./configure
WARNING: --batch mode is deprecated. Please instead explicitly shut down your Bazel server using the command "bazel shutdown".
You have bazel 0.24.1 installed.
Please specify the location of python. [Default is /home/guangyuan/anaconda3/envs/tfsource/bin/python]:
Found possible Python library paths:
/home/guangyuan/anaconda3/envs/tfsource/lib/python3.6/site-packages
Please input the desired Python library path to use.  Default is [/home/guangyuan/anaconda3/envs/tfsource/lib/python3.6/site-packages]
Do you wish to build TensorFlow with XLA JIT support? [Y/n]: y
XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with OpenCL SYCL support? [y/N]: n
No OpenCL SYCL support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]: n
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: y
CUDA support will be enabled for TensorFlow.
Do you wish to build TensorFlow with TensorRT support? [y/N]: n
No TensorRT support will be enabled for TensorFlow.
Error:
Could not find any NvInfer.h matching version '' in any subdirectory:
''
'include'
'include/cuda'
'include/*-linux-gnu'
'extras/CUPTI/include'
'include/cuda/CUPTI'
of:
'/lib'
'/lib/x86_64-linux-gnu'
'/lib32'
'/libx32'
'/usr'
'/usr/lib'
'/usr/lib/x86_64-linux-gnu'
'/usr/lib/x86_64-linux-gnu/libfakeroot'
'/usr/lib32'
'/usr/libx32'
'/usr/local/cuda-10.0'
'/usr/local/zlib/lib'
Asking for detailed CUDA configuration...

This should have been fixed by this commit: https://github.com/tensorflow/tensorflow/commit/28fc9cccd176a113b9f0401d0c569ca1b9d207c3
Please try pulling the latest code.

Please let us know if you are still facing the problem. Thanks!

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Platform effects for Xamarin.forms Mac apps

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/effects/introduction
Where is Mac support? Xamarin forms for Mac has been in preview for almost 18 months while porting a demo app I was horrified to find out effects are not supported yet. Help please

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

ID: 99bd4dfe-8006-0e7b-9391-4256dcc13a31
Version Independent ID: 0398e3bf-27a2-8a37-0537-c1ae9fa0c7fe
Content: PlatformEffect<TContainer,TControl> Class (Xamarin.Forms)
Content Source: [docs/Xamarin.Forms/PlatformEffect2.xml](https://github.com/xamarin/Xamarin.Forms-api-docs/blob/master/docs/Xamarin.Forms/PlatformEffect2.xml)
Product: xamarin
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Hi @mdonogma this is a question for the team - please raise an issue on the Xamarin.Forms GitHub repo. You can also review the source code there, and visit the roadmap.


Bug in ppo_discrete example

In the ppo_discrete.py file the adapt_actions flag is set to True, when it should be False.

fixed


Dependencies version bump

Going to do a little work on bumping dependencies versions in tox.ini and .travis.yml up to latest.
Here is list of changes I am going to implement in this PR:

bump django  from 1.4.10 to 1.4.18
bump django  from 1.5.5 to 1.5.12
bump django  from 1.6.1 to 1.6.10
add django 1.7.3 to test environments (fix #152)
add django 1.8a1 to test environments (it is on pypi already, why not test it?)
do not include south on django trunk (master) environments (south is not required since 1.7)
add python3.4 environments for django 1.7, 1.8 and trunk  (fix #153)

Awesome, thanks!
While you're working on the tox setup, you could consider also updating to the latest tox.ini syntax using generative environments / factors: http://tox.readthedocs.org/en/latest/config.html#generating-environments-conditional-settings -- I think that could reduce the size of tox.ini quite a lot and make it easier to maintain.
We could also consider trying to use tox on Travis to avoid maintaining separate configs. I don't feel strongly either way about that.

I'll update tox.ini syntax. But I am not sure if I can handle using tox on Travis. I will think about it later.

Sure, whatever you're interested in doing is great. I'm not entirely sure about how to switch to tox on Travis while maintaining parallel builds on Travis anyway.

OK, I know now how to deal with tox on Travis. The main idea is to explicitly tell tox it's environment name and run tox for each environment separately. Take a look at this .travis.yml. I will do that today, if you don't mind.

And also I will mark builds of django 1.8 and trunk allowed to fail as made in example above.

Personally, that .travis.yml file doesn't look easier to maintain to me than manually maintaining separate versions.
Could tox --listenvs be used to shorten it somehow?

I wrote shell script to update envs in .travis.yml. link
I did not find tox --listenvs before. I will now adapt that shell script to use this command instead of tox --showconfig.

Previously you had to maintain both .travis.yml and tox.ini. Now you only need to update tox.ini and run script which will adapt envs in .travis.yml according to changes in tox.ini.

All planned tasks on this PR is done.
Can anybody review this, please?

This looks great to me! Thanks for your work. Merging.
Now I just need to find time to get the tests passing on 1.8/master...


python3Packages.pylitterbot: init at 2021.2.5

Motivation for this change
Python package for controlling a Litter-Robot
https://github.com/natekspencer/pylitterbot
This will become a Home Assistant dependency.
Things done

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

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

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

Depends on https://github.com/NixOS/nixpkgs/pull/112908.

Result of nixpkgs-review pr 114388 at f82a2708 run on aarch64-linux 1

2 packages built:

python37Packages.pylitterbot
python38Packages.pylitterbot

/rebase staging


CUDA is not clang 9+ ready.

Issue:
When using clang as a compiler, the following error is raised:
In file included from /usr/local/cuda-10.1.243/bin/../targets/x86_64-linux/include/cuda_runtime.h:83:
/usr/local/cuda-10.1.243/bin/../targets/x86_64-linux/include/crt/host_config.h:146:2: error: -- unsupported clang version! clang version must be less than 9 and greater than 3.2
#error -- unsupported clang version! clang version must be less than 9 and greater than 3.2

Would it be possible to continue supporting clangdev 8 conda package?

You should be able to grab any version listed with:
conda search clangdev
For your particular issue, conda install clangdev=8

Sure. However, this issue is raised for a different reason. Note that the clangdev package (that currently is based on clang version 9) is updated whenever its dependencies are updated.
However, the clangdev=8 package is not be updated when its dependencies are updated.
This issue is about asking for updates of the clangdev=8 package whenever its dependencies are updated. I am not sure that is the recommended way to do it, introducing clangdev8?

Could you please provide an MRE? I'm not entirely clear the context in which this is occurring currently.
cc @kkraus14

@jakirkham
The current CUDA libraries (versions 10.2.89 and earlier) do not support clang>=9.
So, when using clang 9 (that the current clangdev provides) as the C/C++ compiler in a project that depends on a CUDA library, the build will fail with the message shown in the description.
This issue was reported when omniscidb-cuda-feedstock used clang as the C/C++ compiler. It does not anymore mostly because of this issue. However, this issue remains a problem for other CUDA dependent projects that do need/want to use clang as the compiler (read: then these projects cannot use the latest clangdev providing clang>=9).

Is it that we care about Clang 8.0.0 or 8.0.1?

Is it that we care about Clang 8.0.0 or 8.0.1?

8.0.1 (as I don't know the reasons why 8.0.0 would be preferred).

If you want updates to clang 8.0.1, please send a PR. I don't know what updates you want though.


*: supporting BCSR matrices

I looked into what would entail adding BCSR support to legate.sparse. I'll hold off on putting the actual work into it until we have requests from users that actually want to use the BCSR format and what functions they would like to see implemented. Some notes I have on doing this:

The BCSR format is just CSR, where each CSR entry is a contiguous block of non-zeros, similar to a DSDD format in TACO.
As a result, a similar approach to what we've done for CSR/CSC should work out. An annoying thing about this is that the way DISTAL would represent a DSDD tensor is different enough from how we would want to do this effectively in a SciPy implementation that we won't be able to take DISTAL kernels directly, but they should provide a reasonable skeleton for implementation.
In general, the implementation strategy will need to do a few things for declaring partition alignment using legate sparse. 1) input and output dense tensors will have to be reshaped (using store reshapes) based on the blocksize to have alignments against the blocked pos array. 2) images (on both pos and crd) need to have an affine transform applied to them that scales the values by different components of the blocksize Shape. Since this can't be done right now using Legion, we'll have to approximate this by making temporary copies of the stores.
Format conversions are unfortunately not implemented in pure python, so we'll have to hand-code some of these format conversion routines.
cuSparse has pretty well-rounded support for BCSR matrices that we can exploit. It'll be unclear what to do for operations that cuSparse doesn't support, since the size of the blocks significantly affects the strategy for GPU execution (even for CPU-parallel execution).

An example dot implementation on a BSR matrix might look something like:
def dot(self, x):
  y = cn.zeros(self.shape[0]).reshape(self.R, -1)
  x = x.reshape(self.C, -1)
  task = ctx.create_task(BCSR_SPMV)
  task.add_output(y)
  task.add_input(self.pos, self.crd, self.vals, x)
  promoted_pos = self.pos.promote(y.shape[1], 1)
  promoted_vals = self.vals.reshape(self.crd.shape[0], -1)
  task.add_alignment(promoted_pos, y, 0)
  task.add_image(promoted_pos, self.crd)
  task.add_image(promoted_pos, promoted_vals)
  task.add_image(self.crd, x)
  task.execute()

The tricky part here is handling the images onto these transformed stores, which we can't currently do natively in the image. One way of getting around this is to not transform the stores at all, but create temporary transformed version of the regions that take the correct image.

I realized that another way to do this instead of the nested tensor / big block region is to use fields of size = to the block size. A downside of this is the inability to use legion reductions though


[BOT PR] to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

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

Needs approval from an approver in each of these files:

OWNERS

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

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
eb0766a725ea7c49378657b8211503a9dacaa71e
link
/test istio-unit-tests

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


[Backport v1.1.2] HARVESTER: enhancement upgrade log download

Summary
PR Checklist
~- Is this a multi-tenancy feature/bug?~
~- [ ] Yes, the relevant RBAC changes are at:~
~- Do we need to backport changes to the old Rancher UI, such as RKE1?~
~- [ ] Yes, the relevant PR is at:~

Are backend engineers aware of UI changes?

[x] Yes, the backend owner is: https://github.com/harvester/harvester/pull/3379

Fixes #

https://github.com/harvester/harvester/issues/1926

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@mergify backport master


Add "Display right-to-left" check box for "Special character input buttons"

Also make the text box width 100%

The font size on the buttons should be larger and easier to see.

The buttons in this box should right align when the text is right2left and left align when it is left2right.
Can we choose the Font size as well as the font?

Check this on https://www.webonary.org/dari/.

When R2L characters were added separated by R2L commas, this is what happened.

successful in .org.
Need to research other language commas.


Low Person Class Confidence

When I use CityScape dataset to train,now the mask mAP is about 13,but I find that the person class confidence is very low,and the average of it is only about 0.1,so What is the reason for this?

Perhaps it's not trained enough, or maybe identifying people is really hard? I know in a preliminary test on cityscapes we were able to get 16-17 mAP with the base model, so it's probably the former, but cityscapes is a tough dataset if you don't use the full 1080p images (since without that, the instances are all really small and there are a lot of them).

Thank you for answer this question,maybe the parameter pred_aspect_ratios can cause this problem,because when I resize the image to 550*550,the person in the image has low width/height in common,so I try to change the pred_aspect_ratios value to (1/2,1/4,1).But I don't know whether there is a good result for person class

Oh yeah that's a good idea, and I think it would work. However, YOLACTv1 has a bug where all the anchor boxes are squares (I accidentally made the width and height equal). If you're on my latest / close to latest commit, you can fix this by setting 'use_square_anchors': False in the config's backbone. I have that set to true for backward compatibility.

ok,I will try it

I have tried it for 20000+ iterations and I set the batch_size=16,I find that the loss is lower but mAP is also more lower compare to before at a same time,but the difference is only 'parameter pred_aspect_ratios' value.So,What is the reason?

So it's worse if you set 'use_square_anchors' to false? Maybe it's overfitting? You can also try making the anchor scales smaller, e.g. instead of starting at 24, start at 16 and increase by 2x each time.

Thank you for your reply,I will try it.

@miooooooooooo I'm trying to retrain this on Cityscape dataset. I'm using the code in facebook reasearch team's Detectron Github https://github.com/facebookresearch/Detectron/blob/master/tools/convert_cityscapes_to_coco.py
but this is not working. Can you tell me the way you create Cityscape dataset for yolact please?

oh,I don't use the "convert_cityscape_to_coco.py",I write the code which is very simple,just preserve the annotation about the polgon,bounding box,class and img_id.you can flow the coco annotation and write it quickily.

Since this has been open so long, I'm going to close it. Feel free to reopen if you have any updates.

HI I want to detect persons only. With everything remaining the same what should I do to nullify all the other classes from being detected but persons only. I understand I wouldnt have to make a custom config for this. I tried to change yolact/layers/output_utils.py but it gives out error when theres a frame with no person.


bug: wrong error diagnostic report on contracts

cairo-version: 2.7.0-rc.3
consider the following contract where set (impl) doest not match set(trait)
#[starknet::interface]
trait ISimpleStorage<TContractState> {
    fn set(ref self: TContractState, x: u128);
    fn get(self: @TContractState) -> u128;
}

#[starknet::contract]
mod SimpleStorage {
    use starknet::get_caller_address;
    use starknet::ContractAddress;

    #[storage]
    struct Storage {
        stored_data: u128
    }

    #[abi(embed_v0)]
    impl SimpleStorage of super::ISimpleStorage<ContractState> {
        fn set(ref self: ContractState) {}
        fn get(self: @ContractState) -> u128 {
            self.stored_data.read()
        }
    }
}

Previously the compiler error was
$ scarb cairo-run
   Compiling listing_99_02 v0.1.0 (listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/Scarb.toml)
error: The number of parameters in the impl function `SimpleStorage::set` is incompatible with `ISimpleStorage::set`. Expected: 2, actual: 1.
 --> listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/src/lib.cairo:24:16
        fn set(ref self: ContractState) {}
               ^*********************^

error: Wrong number of arguments. Expected 2, found: 1
 --> listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/src/lib.cairo[contract]:80:5
    SimpleStorage::set(ref contract_state, );
    ^**************************************^

error: could not compile `listing_99_02` due to previous error
error: `scarb metadata` exited with error

Now, it is:
$ scarb cairo-run
   Compiling listing_99_02 v0.1.0 (listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/Scarb.toml)
error: The number of parameters in the impl function `SimpleStorage::set` is incompatible with `ISimpleStorage::set`. Expected: 2, actual: 1.
 --> listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/src/lib.cairo:24:16
        fn set(ref self: ContractState) {}
               ^*********************^

error: Wrong number of arguments. Expected 2, found: 1
 --> listings/ch13-introduction-to-starknet-smart-contracts/listing_02_wrong_impl/src/lib.cairo:11:1
#[starknet::contract]
^*******************^

error: could not compile `listing_99_02` due to previous error
error: `scarb metadata` exited with error

The second part of the error message indicates an error on the #[starknet::contract] attribute. Either this should not be shown at all, because the first part is self-sufficient, or it should point to the correct line

This isn't actually solvable - as the macro happens at the syntax level - it creates code that calls the function, from text only (so not actually trait aware). the second error is actually on the generated wrapper code (that's why it previously pointed at a generated file, and now after the mapping, it points to the cause of generating this code).
so the best that can be done - is pointing to the #[abi(embed_v0)] as this is actually the offending line.
but the error itself is totally correct.

Perhaps the second error can simply be removed? The first is self sufficient

as long as the error obviously points to generated code (and when the LS allows proper macro expansion to see it) - having both seems fine to me, especially as it actually points to different errors - in general catching all likely such duplicates is not going to be a tenable solution.


Make istio works when rbac disabled.

Fixed https://github.com/istio/issues/issues/255
/cc @sdake @linsun @morvencao

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

Needs approval from an approver in each of these files:

install/OWNERS

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

@gyliu513: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
51000508872245fda93ac7be72498176cb37227f
link
/test istio-unit-tests

prow/istio-presubmit.sh
51000508872245fda93ac7be72498176cb37227f
link
/test istio-presubmit

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


Add Fan Control only Without Light on it

Hello!
I would like to add Fan Control only without Light because my fan doesn't have light.
I tried implementing 03-CeilingFanWithLight and it is working well with Light.
Then, I tried commenting LightBulb code from the example below, but then the accessory stops responding.
new Service::HAPProtocolInformation();          // Create the HAP Protcol Information Service
      new Characteristic::Version("1.1.0");           // Set the Version Characteristicto "1.1.0" as required by HAP

  //  new Service::LightBulb();                       // Create the Light Bulb Service
    //  new Characteristic::On();                       // This Service requires the "On" Characterstic to turn the light on and off

  // Now we create the a Fan Service within this same Accessory

    new Service::Fan();                             // Create the Fan Service
      new Characteristic::Active();

Is there a way to Implement only fan to control fan speeds?
Advice and ideas are highly appreciated.
TIA.

Try unpairing and re-pairing the device.  Sometime HomeKit caches setting and won't fully recognize the change to your configuration.

Try unpairing and re-pairing the device. Sometime HomeKit caches setting and won't fully recognize the change to your configuration.

Thank you, mate.
Is there a way to control Air Conditioner? I checked but didn't found.

The HeaterCooler Service would be the best to use for an Air Conditioner.   You can configure it for simple on/off or add the CoolingThresholdTemperature Characteristic for automatic operation.


Unable to compare diff

I can list each app separately but am unable to compare them why am I running into auth issues
ec list app1
=== app1 Config Vars
FOO:   bar

ec diff --all app1 app2
Traceback (most recent call last):
        22: from /Users/nick/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:24:in `<main>'
        21: from /Users/nick/.rvm/gems/ruby-2.6.6/bin/ruby_executable_hooks:24:in `eval'
        20: from /Users/nick/.rvm/gems/ruby-2.6.6/bin/ec:23:in `<main>'
        19: from /Users/nick/.rvm/gems/ruby-2.6.6/bin/ec:23:in `load'
        18: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/exe/ec:6:in `<top (required)>'
        17: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/thor-1.1.0/lib/thor/base.rb:485:in `start'
        16: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
        15: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
        14: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
        13: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:32:in `diff'
        12: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:75:in `heroku_results'
        11: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:75:in `each_with_object'
        10: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:75:in `each'
         9: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:78:in `block in heroku_results'
         8: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/env_compare-0.1.4/lib/env_compare/cli.rb:104:in `config_vars_for_app'
         7: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/platform-api-2.2.0/lib/platform-api/client.rb:1503:in `info_for_app'
         6: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/heroics-0.0.25/lib/heroics/resource.rb:28:in `method_missing'
         5: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/heroics-0.0.25/lib/heroics/link.rb:66:in `run'
         4: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/heroics-0.0.25/lib/heroics/link.rb:111:in `request_with_cache'
         3: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/excon-0.73.0/lib/excon/connection.rb:279:in `request'
         2: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/excon-0.73.0/lib/excon/connection.rb:448:in `response'
         1: from /Users/nick/.rvm/gems/ruby-2.6.6/gems/excon-0.73.0/lib/excon/middlewares/response_parser.rb:12:in `response_call'
/Users/nick/.rvm/gems/ruby-2.6.6/gems/excon-0.73.0/lib/excon/middlewares/expects.rb:13:in `response_call': Expected([200, 201, 202, 204, 206, 304]) <=> Actual(401 Unauthorized) (Excon::Error::Unauthorized)

Authentication... Issues... Figured it out, looks great!


Adds PHP 8 in Travis

This PR adds PHP 8.0 in the Travis matrix.

The build doesn't start because lately, you have to explicitly select Free plan on the Travis settings (at least this is what I had to do). I do not have access to the bcit-ci organization on Travis, but I requested access. Until then, if someone who has access there could select that plan and retrigger the build for this PR, it would be much appreciated.

Travis is setup, but builds won't start for old PRs. I'm not sure if you have access to modify settings if something comes up, but you can ping me.
As for this one - are the changes to CI_Output necessary?

are the changes to CI_Output necessary?

Yes. If not, there is a warning:
Severity:    Warning
Message:     array_shift(): Argument #1 ($array) must be passed by reference, value given

but you can ping me.

Okay, so somehow, I was able to access the bcit-ci organization settings for Travis. I picked the Free plan. Let me know if it looks ok or if we should change something else there. Also, retriggered the build here! :D

Yes. If not, there is a warning

Yep, that's exactly why a test failed. :P
Sorry for the delayed reply.

Pushed other changes:

It seems that the queries from \Mock_Database_Schema_Skeleton::create_tables were failing for PostgreSQL-PDO always, only that it was silently because of a bug described in the next item; checks were added here anyway.
Fixed pdo_pgsql_forge.php's create_table() to work just as it does for postgre_forge.php.

Hi @narfbg,
I'm going to prepare a PR for adding support for PHP 8.1 as well. If there is anything else which we should change on this PR, please let me know.


Phantomjs2

Can't merge this back into master yet as there are some issues with running the newest PhantomJS 2.1 with the phantomjs-node repo.
#https://github.com/amir20/phantomjs-node/issues/345

I'm closing this as we are going to be something different to support PhantomJS 2.


adler32_rvv: Fix two overflow problems

There are currently two overflow problems in adler32_rvv implementation, which can lead to wrong results for some input, and these problems could be easily exhibited when running git fsck with zlib-ng suitituting the system zlib on a big git repository.
These problems and the solutions are the following:

When the input data is long enough, the v_buf32_accu can overflow too. Add it to the modulo code that happens per ~NMAX bytes.
When the remaining data less than vl bytes, the code falls back to a scalar implementation; however the sum2 and alder2 values are just reduced from vectors and could be very big that makes sum2 overflows in the scalar code. Modulo them before the scalar code to prevent such overflow (because vl is surely quite smaller than NMAX).

Summary by CodeRabbit

New Features

Enhanced the Adler-32 checksum calculations to ensure values remain within defined bounds.

Bug Fixes

Adjusted checksum accumulation logic to prevent exceeding limits during calculations.

Added another overflow fix about the reduction from vector to scalar.

For the first problem, I have a 2M random .bin file that can lead to this issue being exhibited when running adler32 on it.
For the second/third problem, I think maybe carefully crafted data is needed, and I currently do not have suitable test data (I tested and found these problems by running git fsck on https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git )

For the second problem (in the commit message now), I think crafting a dataset with very long len - left (well technically this means len / vl * vl, I think), a big enough initial adler32 value (0xFFF0FFF0 ? 0xFFF0 equals to 65520) could make it easily exhibit?
Then for the third, attaching (vl - 1) 0xFF's to a data that will be calculated to very big sum2 and adler may exhibit the problems?
Well these two dataset construction methods both depend on a pre-determined vl ...
(My testing platform is SpacemiT K1, which should have VLEN=256 and the vl is 32 in this situation)

And surely the behavior between QEMU and K1 differs on these problems -- QEMU defaults to VLEN=128 (vl = 16).