Investigate why timezone formatter sometimes fails

This is partly my fault as I missed rerunning travis before merging in #391 resulting in the build failing. I'll make sure to rerun tests on old PR's in the future.
The line that causes problems is https://github.com/crsmithdev/arrow/blob/master/tests/formatter_tests.py#L125
Something has clearly changed between now and when the tests first passed.
@rafaelsierra any ideas on this?

Few examples.
>>> dt = arrow.get("2018-03-19 13:55:44 US/Pacific", "YYYY-MM-DD HH:mm:ss ZZZ")
>>> dt
<Arrow [2018-03-19T13:55:44-07:00]>
>>> dt.format("YYYY-MM-DD HH:mm:ss ZZZ")
'2018-03-19 13:55:44 PDT'

>>> dt = arrow.get("2018-03-19 13:55:44 America/Sao_Paulo", "YYYY-MM-DD HH:mm:ss ZZZ")
>>> dt
<Arrow [2018-03-19T13:55:44-03:00]>
>>> dt.format("YYYY-MM-DD HH:mm:ss ZZZ")
'2018-03-19 13:55:44 -03'

>>> arrow.now().format('ZZZ')
'GMT'


@W-14139572 - Show discount price on pdp

Description
This PR created a DisplayPrice component to show discount count price and strighthrough baseprice if applicable. This comp is currently used in PDP and AddToCartModal

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

use-derived-product.js
pages/product-details/index.jsx
product-view/index.jsx

How to Test-Drive This PR

npm start on retail app
Go to this product: http://localhost:3000/global/en-GB/product/25695436M?color=JJP49XX&size=9SM&pid=701644154707M
Discount price should show up with basePrice is being strikethrough

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

Does the change already reflect the price change on these pages?
Cart page:
https://github.com/SalesforceCommerceCloud/pwa-kit/blob/71c8cceeb4345af233061639e971424db007fea7/packages/template-retail-react-app/app/pages/cart/index.jsx#L201
Confirmation page:
https://github.com/SalesforceCommerceCloud/pwa-kit/blob/71c8cceeb4345af233061639e971424db007fea7/packages/template-retail-react-app/app/pages/checkout/confirmation.jsx#L299
Order detail page:
https://github.com/SalesforceCommerceCloud/pwa-kit/blob/71c8cceeb4345af233061639e971424db007fea7/packages/template-retail-react-app/app/pages/account/order-detail.jsx#L59

For cart page, yes it does since it uses the same ProductView that got the change.
Checkout Summary and Order detail already show discount price if applicable


Add integration with CircleCI

We need to add the option to integrate the app with MarsBased CircleCI

Hi @oriolbcn I think we are finish this issue in #68.
Can we close this issue?

Yes! We can close this 🚀


Error: timeout of 5000ms exceeded

hi @joaostroher ,
thanks for such a great plugin you've made. really loved it but i just got timeout error that's quite disturbing while syncing my long list of endpoints and figured it out by commenting your timeout in the createGitHubApi function.
function createGitHubApi(token) {
  return axios.create({
    baseURL: 'https://api.github.com/',
    //timeout: 5000,
    headers: { Authorization: `Bearer ${token}` },
  });
}

i think this plugin would be super awesome to have for everyone out there.
thanks!

Hey @wakjoko, thanks. I'am workin on a new version with some improvments. But i will fix it on current version. Thanks

Fixed on #4 .


Add prettify-ts-plugin

This is rather rudimentary at the moment. Here's things that need to be explored further before it stops being a draft:

Actual reimplementation of prettification rather than a mostly faithful reproduction of what tsserver is doing.
An actual monorepo setup. As it's currently set up, it's basically two separate packages.

Hey @LukeAbby - this draft looks great so far. I've been learning about TS LSP's a bit over the past week and attempted to add the prettification myself as well, but ran into the same issue you mentioned where it gets complicated. However, I agree that ts-morph is probably doing too much. I'm really excited to see where you go with this, I absolutely believe this is the future of this project 🥳

Closing due to other PR which introduces TS LSP


Firefox shows "This site is not monetized" in private windows

I noticed that when browsing in private mode on firefox, with the coil extension installed but not logged in, the extension will incorrectly say "This site is not Web-Monetized" for any site. Even web monitized sites like cinnamon.
It also seems to do this when you are logged in.

Will look into it, but it's likely the "private" mode being truly private and the content script not having privileged access to the page.

https://www.ghacks.net/2019/02/01/firefox-will-soon-disallow-extensions-in-private-mode-by-default/


docs: fix typos in Unspaced 1.0.0.mdx

This PR fixes some minor typos in the Unspaced documentation.

thanks!


pouchdb-adapter-asyncstorage is outdated. Is project abandoned, what to expect?

What doesn't work (on top of already stated almost useless attachments):

queries + replication
.query: once db with updated docs replicated from couchdb server to RN .query starts to return only the last updated doc (while others are presented in localDB as well)
.find: after any(!) replication stops to return any results at all
The most critical issue. The only available workaround is to get allDocs and then apply js filtering, which is VERY costy in case of lots of relatively heavy docs in DB.

keys filter in allDocs isn't respected

doc_ids in replicate isn't respected (could be resolved by upgrading underlying PDB components to 7.0.0)

Since pouchdb-adapter-asyncstorage is core and the only specific part of pouchdb-react-native itself, that's the question:
is there any plans to update pouchdb-adapter-asyncstorage in order to support recent changes in couchdb replication?
changes or keys part of pouchdb-adapter-asyncstorage can be suspected but for sure maintainer knows better)
Understanding of possible project future for all of us is quite critical, please let us know what to expect.
And thank you.

please try
npm install pouchdb-react-native@next --save
if all ok, I'll update to version 7.0

Great news! Thank you.
At first glance importing .find plugin brings errors while accessing indexes.
Let me try it with .query - I have to revert to old code which used it.

Seems that replication is broken now. My code, which worked fine with old PDBRN (or bundle of old pouchdb-adapter-asyncstorage + PDB 7.0 core+plugins)
localDB.replicate.from(remoteDB)
now replicates no docs from same remote db
{ ok: true,
docs_read: 0,
docs_written: 0,
doc_write_failures: 0,
errors: [],
status: 'complete' }

I can pull one doc but then saving it (with rev removed, off cause) gets strange result:
' !!! PDB _saveDoc ERR localDB.put: ===== ', []
From code:
return localDB.put(doc)
      .then((result)=> {
        if (result.ok) {
          return resolve('doc_saved')
        } else {
          console.log(' !!! PDB _saveDoc ERR localDB.put: ===== ', result)
          return reject(result.status)
        }
      })

Thanks @greenais for the comments which helped me at least not to keep hitting my head in the wall.
were you able finally to get a stable mix of working PouchDB especially with Find plugin?
Because after investing time and effort in PouchDB I am considering abandoning it to Realm

@sheva007 No, .find doesn't work yet for me.
In my current project I use "old" pouchdb-adapter-asyncstorage in conjunction with the most recent (7.0) PDB plugins:
import PouchDB from 'pouchdb-core';
PouchDB
.plugin(require('pouchdb-adapter-asyncstorage').default)
.plugin(require('pouchdb-adapter-http'))
.plugin(require('pouchdb-replication'))
.plugin(require('pouchdb-authentication'))
const localDB = new PouchDB(localDBname, {adapter: 'asyncstorage'});

I really like CounchDB approach on server side - the key part is replication, sure, so I didn't consider Realm as an option as I see no point in reinventing weel with authentication/replication/version control etc. But if you don't need it - why not?

Thanks for the reply, were able to use any kind of filtering in Pouch DB? Getting all docs then filtering in code is hitting the performance hard

Shure it does.
.query works just fine until you replicate some changed docs from CouchDB - then it returns the last changed doc only.

.find works as well fine until replication, afer - zero results

Any updates from mantainer, perhaps?

Interestingly, taking out pouchdb-adapter-asyncstorage and instead using pouchdb-adapter-react-native-sqlite results in the exact same problem in the OP.   So it's not a pouchdb-adapter-asyncstorage problem, but something to do with one of the other core components?

That's right, the issue is around the fact that PDB is designed to work in modern browsers environments (with V8 mostly) while RN uses JS Core - where several core functions (btoa i.e.) are implemented differently. That's why PDB guys just don't try to bother with RN issues - "it wasn't designed for RN, sorry".
It means that PDBRN support involves quite deep substitutions/shims to new versions of PDB, which is much harder than just drop-in new PDB


[PROPOSAL] Manage inotify limit better

Suddenly the following appeared, without me doing anything strange:

Why this windows appeared out of the blue?
Where does "524XXX" comes from? That variable was set to 100000 previously
Can we change that variable when we install Maestral?

It appeared again .. to I have to restart my PC after the change?

Why this windows appeared out of the blue?

Because now that you have everything synced, you have a lot of items that need to be watched.

Where does "524XXX" comes from? That variable was set to 100000 previously

To be fair, this error message should be improved. 524288 is a decent number because it is larger than most Dropbox folder sizes. But really the message should say: set fs.inotify.max_user_watches to a value exceeding the number of items in your Dropbox folder...

Can we change that variable when we install Maestral?

No. Changing it will fiddle with the system settings and requires elevated privileges. Neither should be done automatically at install time but deliberately by the user or admin. Some people will want to reduce the number of allowed inotify watches, for instance on embedded systems with very little memory.

It appeared again .. do I have to restart my PC after the change?

Yes! Another info missing from the message...

But really the message should say: set fs.inotify.max_user_watches to a value exceeding the number of items in your Dropbox folder...

Honestly it wouldn't be so straightforward for my use case.
I would have 10k files, set that setting to 10001, then it is sufficient for me to include another folder, or for a college to add a file to exceed the limit again.
And then when I include another folder to download in local, I would need to remember to update that system setting again.

Can we change that variable when we install Maestral?

No. Changing it will fiddle with the system settings and requires elevated privileges. Neither should be done automatically at install time but deliberately by the user or admin. Some people will want to reduce the number of allowed inotify watches, for instance on embedded systems with very little memory.

Can we change it at runtime? For instance, can that message box change it for me?
The message could end with something like: "Do you want Maestral to update this setting for you?". And if I click yes it would run "sudo sed ...." or something like that (asking for my password)

I am still getting this message even if I did what Maestral asked me to do
2021-02-08 12:46:34 maestral.sync ERROR: Unexpected error: Please restart to continue syncing
Traceback (most recent call last):
  File "/home/raffaele/.local/lib/python3.8/site-packages/maestral/sync.py", line 3776, in start
    self.local_observer_thread.start()
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/api.py", line 256, in start
    emitter.start()
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/utils/__init__.py", line 93, in start
    self.on_thread_start()
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify.py", line 117, in on_thread_start
    self._inotify = InotifyBuffer(path, self.watch.is_recursive)
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify_buffer.py", line 35, in __init__
    self._inotify = Inotify(path, recursive)
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 198, in __init__
    self._add_dir_watch(path, recursive, event_mask)
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 395, in _add_dir_watch
    self._add_watch(full_path, mask)
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 409, in _add_watch
    Inotify._raise_error()
  File "/home/raffaele/.local/lib/python3.8/site-packages/watchdog/observers/inotify_c.py", line 421, in _raise_error
    raise OSError(errno.ENOSPC, "inotify watch limit reached")
OSError: [Errno 28] inotify watch limit reached

My folder is ~190k files and I have set that variable to the suggested ~500k

Hm, that is strange.  Can you verify that the max_user_watches really has been increased? The following terminal command will give you the current value:
sysctl fs.inotify.max_user_watches

You can also increase the number of watches directly with:
sudo sysctl fs.inotify.max_user_watches=524288

This will increase the max number of watches immediately but will be reset after a reboot.

Now it is asking me to set that variable to 512, which is lower than before and lower than the current number:

$ sysctl fs.inotify.max_user_watches
fs.inotify.max_user_watches = 524288

Where does all these numbers come from?

Ok, increasing max_user_watches worked! But it appears that you are also running our of inotify instances, which is surprising. Again, 512 just is a best guess of what should be sufficient and not really based on data. The number are all powers of two. Does increasing max_user_instances solve the issues?
Also, do you have any other programs running which are monitoring the file system vs inotify? In this case, the new limits might not be high enough.
You can get the number of files being watched by all processes, you can use:
lsof | grep inotify | wc -l

max_user_watches should be set to something quite a bit higher, to give a bit of flexibility.
To see all processes using inotify, order by their number of instances:
for foo in /proc/*/fd/*; do readlink -f $foo; done | grep inotify | sort | uniq -c | sort -nr

This will give output looking like:
      4 /proc/9370/fd/anon_inode:inotify
      2 /proc/2942/fd/anon_inode:inotify
      1 /proc/2570/fd/anon_inode:inotify
      1 /proc/2524/fd/anon_inode:inotify

where the number is the PID.
You can find a good writeup about this at https://transang.me/enospc-inotify-in-ubuntu/.

A Wiki page about this is probably a good idea.

I've added a section in the docs about adjusted inotify limits: https://www.maestral.app/docs/inotify-limits.
I might also add a link to this help page in the error message. This should hopefully be enough documentation to help users out.

Most if this has been done in v1.4.4. I have not included any automatic adjustments to inotify limits, just because the potential of things going wrong and the number of corner cases with Linux is too large.


Initial load tests on EPP

Description
To understand load and performance characteristics for launch, we should do some initial load testing and get an understanding of what load we can expect to serve
Note: we expect the journal infrastructure to add a layer of caching, so overall load after going live should be quite manageable.
Tasks

[ ] Perform an initial test (using ab or similar)
[ ] Report performance to team and decide if any further action is required

Definition of Done

[ ] Performance understand
[ ] Follow on action tickets (if required) are created and prioritised

Initial load testing at 25 concurrency, about 50 requests in the service starts to 500 error. The culprit seems to be the hypothesis load on society, something they warned us about (see https://github.com/elifesciences/enhanced-preprints-server/issues/413)
Due to the slowness of those API requests, each page load is > 1s

After adding caching to both EPP and Sciety, reran the test and didn't hit the 500 error wall again.
At higher concurrency, we seem to have an issue with the client dropping connections to APIs, like so
FetchError: request to http://epp-server:3000/api/reviewed-preprints/10.1101/2<IP_ADDRESS>7502/reviews failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/opt/epp-client/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)
    at ClientRequest.emit (node:events:513:28)
    at Socket.socketErrorListener (node:_http_client:481:9)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET'
}

At first I thought this was because the server was restarted as the extra load made the readiness probe fail and k8s would restart the pod. Giving this a longer timeout however didn't help.
I've increased the number of client replicas and it seems to allow for higher concurrency without as many failures, but is still quite intermittent. Additionally the cluster's seems a bit full, so we might need to consider increasing the nodes available in the cluster.
Going with 3 client instances for launch.
I've also increased the number of nodes available to allow us to scale up the number of client-servers if/when we need it.


about pretrained embeddings

Hi,
I have a little question about file 08.CNN-for-Text-Classification.ipynb, [96], line 4: pretrained.append(model[word2index[key]]).
word2index[key] means to find key's index, then you should find its pretrained embedding in GoogleNews-vectors-negative300.bin. But the index in this bin file should be different from the index generated from TREC dataset, i.e. model[key's index] may not be this key's (word's) embedding.
Thanks!

Hi,
Yeah you're right. There are some bugs in this project..
However, I don't have enough time to deal with issues in ad-hoc manner.
So I'm preparing version-up of this repo.
Thank you


EndPoint, Endpoint_Wrapper

Codecov Report

Merging #414 into master will decrease coverage by 0.13%.
The diff coverage is 98.05%.

@@            Coverage Diff             @@
##           master     #414      +/-   ##
==========================================
- Coverage   97.92%   97.79%   -0.14%
==========================================
  Files          32       32
  Lines        1976     1947      -29
  Branches      129      127       -2
==========================================
- Hits         1935     1904      -31
- Misses         27       29       +2
  Partials       14       14

Impacted Files
Coverage Δ

...bstraction/test_NorthBoundControllerAbstraction.py
100% <100%> (ø)
:arrow_up:

poseidon/poseidonMonitor/poseidonMonitor.py
100% <100%> (ø)
:arrow_up:

...r/NorthBoundControllerAbstraction/proxy/bcf/bcf.py
87.19% <100%> (+0.07%)
:arrow_up:

poseidon/poseidonMonitor/test_poseidonMonitor.py
99.4% <94.73%> (-0.6%)
:arrow_down:

...rthBoundControllerAbstraction/UpdateSwitchState.py
98.69% <98.33%> (-0.04%)
:arrow_down:

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 f1de595...2e4c150. Read the comment docs.


Routes of modules are loaded after main app routes

If my main app in web.php i have this Route:
 Route::get('{any}', [PagesController::class, 'any'])->where('any', '.*')
And a  module, in web.php have route:
 Route::get('/admin', [Admin::class, 'index'])->name('admin');
Then the /admin will fire PagesController action.
I think it happens because the routes for the module are loaded after the main application.

Hi,
This package can't control this as routes are loaded via laravel.
I would suggest to not put this wildcard route in the application routes, but in your module with a high order.

Hi,
Thank you for your response.

You can actually just create a module route called "website" and add that route there. The system looks for the modules names in alphabetical order. So any modules you add above will work fine because website is called last. Unless you have a module that starts with anything lower than W.

If my main app in web.php i have this Route:
 Route::get('{any}', [PagesController::class, 'any'])->where('any', '.*')
And a module, in web.php have route:
 Route::get('/admin', [Admin::class, 'index'])->name('admin');
Then the /admin will fire PagesController action.
I think it happens because the routes for the module are loaded after the main application.

Also this type of route is also better because it will check if the route is edit or create
''' Route::get('/{slug?}', [pagesController::class, 'index'] )->where(['slug' => '^(?!((./edit$)|(create$))).\D+.*$']);'''
not sure if slug? or any is better but hey it works.


fix: quote meta slash error

Summary
Fix eco ci error, align with webpack https://github.com/webpack/webpack/blob/651b3d66d10d54da31d4cb7123ea74d10f1f5456/lib/util/compileBooleanMatcher.js#L12
Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

!eco-ci

!canary

!eco-ci


Merge 1.17.0 branch into develop

What does this PR do?
Conflicts are resolved.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1254 (5cc3d82) into develop (f209d3c) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #1254      +/-   ##
===========================================
+ Coverage    82.01%   82.02%   +0.01%
===========================================
  Files          361      361
  Lines        12832    12832
  Branches      2149     2149
===========================================
+ Hits         10524    10525       +1
+ Misses        1655     1652       -3
- Partials       653      655       +2

Impacted Files
Coverage Δ

.../datadog/android/sessionreplay/utils/ThemeUtils.kt
83.33% <0.00%> (-16.67%)
:arrow_down:

...d/v2/core/internal/storage/FileEventBatchWriter.kt
94.74% <0.00%> (-2.63%)
:arrow_down:

...in/com/datadog/android/log/internal/LogsFeature.kt
83.08% <0.00%> (-2.31%)
:arrow_down:

...droid/rum/tracking/ActivityViewTrackingStrategy.kt
86.54% <0.00%> (-1.92%)
:arrow_down:

...ain/java/com/datadog/opentracing/PendingTrace.java
59.48% <0.00%> (-0.86%)
:arrow_down:

.../android/rum/internal/monitor/DatadogRumMonitor.kt
90.81% <0.00%> (-0.54%)
:arrow_down:

...android/v2/core/internal/net/DataOkHttpUploader.kt
94.94% <0.00%> (ø)

.../android/rum/internal/domain/scope/RumViewScope.kt
95.63% <0.00%> (+0.18%)
:arrow_up:

...id/rum/internal/ndk/DatadogNdkCrashEventHandler.kt
90.00% <0.00%> (+1.00%)
:arrow_up:

...ndroid/telemetry/internal/TelemetryEventHandler.kt
74.22% <0.00%> (+1.56%)
:arrow_up:

... and 1 more


FilterIntegrationTest.AltSvcCachedH2Slow is flakey

I've seen this test flake from time to time in CI. Here's a recent example:
https://dev.azure.com/cncf/envoy/_build/results?buildId=161250&view=logs&jobId=767be981-567e-57d8-68c3-2140ede0a0bd&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=2181edf2-f610-59f2-c43a-04bb9d0bca00
@abeyad
@alyssawilk

This flaked for me in an unrelated PR. Revert for now?
https://dev.azure.com/cncf/envoy/_build/results?buildId=164249&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=2181edf2-f610-59f2-c43a-04bb9d0bca00
2024-03-06T20:24:18.6721900Z [ RUN      ] Protocols/FilterIntegrationTest.AltSvcCachedH2Slow/IPv6_Http2Downstream_Http3UpstreamHttpParserNghttp2WithDeferredProcessingLegacy
2024-03-06T20:24:18.6723371Z ./test/integration/server.h:455: Failure
2024-03-06T20:24:18.6724597Z Value of: TestUtility::waitForGaugeEq(statStore(), name, value, time_system_, timeout)
2024-03-06T20:24:18.6726361Z   Actual: false (timed out waiting for cluster.cluster_0.circuit_breakers.default.remaining_cx_pools to be 100, current value 99)
2024-03-06T20:24:18.6727727Z Expected: true
2024-03-06T20:24:18.6728283Z Stack trace:
2024-03-06T20:24:18.6729250Z   0xaec5fc: Envoy::(anonymous namespace)::FilterIntegrationTest_AltSvcCachedH2Slow_Test::TestBody()
2024-03-06T20:24:18.6730644Z   0x1d5eec8: testing::internal::HandleExceptionsInMethodIfSupported<>()
2024-03-06T20:24:18.6731596Z   0x1d5ed64: testing::Test::Run()
2024-03-06T20:24:18.6732399Z   0x1d5ff84: testing::TestInfo::Run()
2024-03-06T20:24:18.6733088Z ... Google Test internal frames ...
2024-03-06T20:24:18.6733567Z
2024-03-06T20:24:18.6734954Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_enable_universal_header_validator to: false
2024-03-06T20:24:18.6737303Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_http1_use_balsa_parser to: true
2024-03-06T20:24:18.6739581Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_no_extension_lookup_by_name to: true
2024-03-06T20:24:18.6741870Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_runtime_initialized to: false
2024-03-06T20:24:18.6744178Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_quic_always_support_server_preferred_address to: true
2024-03-06T20:24:18.6746451Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_http2_use_oghttp2 to: true
2024-03-06T20:24:18.6749185Z [external/com_google_absl/absl/flags/internal/flag.cc : 115] RAW: Restore saved value of envoy_reloadable_features_defer_processing_backedup_streams to: true
2024-03-06T20:24:18.6752775Z [  FAILED  ]

sorry just saw this, yes I'm noticing it flaked again too in other runs of CI, I'll revert the PR

@alyssawilk this test flakes with this error:
[ RUN      ] Protocols/FilterIntegrationTest.AltSvcCachedH2Slow/IPv4_Http2Downstream_Http3UpstreamHttpParserNghttp2NoDeferredProcessingLegacy
./test/integration/server.h:455: Failure
Value of: TestUtility::waitForGaugeEq(statStore(), name, value, time_system_, timeout)
  Actual: false (timed out waiting for cluster.cluster_0.circuit_breakers.default.remaining_cx_pools to be 100, current value 99)
Expected: true
Stack trace:
  0xaebfbc: Envoy::(anonymous namespace)::FilterIntegrationTest_AltSvcCachedH2Slow_Test::TestBody()
  0x1d5e3f8: testing::internal::HandleExceptionsInMethodIfSupported<>()
  0x1d5e294: testing::Test::Run()
  0x1d5f4b4: testing::TestInfo::Run()
... Google Test internal frames ...

For example: https://dev.azure.com/cncf/envoy/_build/results?buildId=164325&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=2181edf2-f610-59f2-c43a-04bb9d0bca00
I can't reproduce it locally after 1000 runs.
It's happening on this line in the test: https://github.com/envoyproxy/envoy/blob/b7bc42064b030c6bae4998e3b1568bb0023562b9/test/extensions/filters/http/alternate_protocols_cache/filter_integration_test.cc#L325.
We don't set a timeout in our waitForGaugeEq call, so the DEFAULT_TIMEOUT of 10s is used: https://github.com/envoyproxy/envoy/blob/b7bc42064b030c6bae4998e3b1568bb0023562b9/test/integration/server.h#L454.  That should be enough for the pool to tear down.

Just observed another test flake failure, but maybe it is of a different nature:
[ RUN      ] Protocols/FilterIntegrationTest.AltSvcCachedH2Slow/IPv4_Http2Downstream_Http3UpstreamHttpParserOghttp2WithDeferredProcessingLegacy
[mutex.cc : 1959] RAW: Check (v & (kMuWait | kMuWrWait)) != kMuWrWait failed: Lock: Mutex corrupt: waiting writer with no waiters: 0x67efe291e60
[2024-04-18 11:09:45.770][28517][critical][backtrace] [./source/server/backtrace.h:104] Caught Aborted, suspect faulting address 0x3e900006c1c
[2024-04-18 11:09:45.770][28517][critical][backtrace] [./source/server/backtrace.h:91] Backtrace (use tools/stack_decode.py to get line numbers):
[2024-04-18 11:09:45.770][28517][critical][backtrace] [./source/server/backtrace.h:92] Envoy version: 0/1.29.4-dev/test/RELEASE/BoringSSL
[2024-04-18 11:09:45.770][28517][critical][backtrace] [./source/server/backtrace.h:96] #0: __kernel_rt_sigreturn [0xffffb41d38fc]
[2024-04-18 11:09:45.770][28517][critical][backtrace] [./source/server/backtrace.h:96] #1: abort [0xffffb3f48aac]
[2024-04-18 11:09:45.780][28517][critical][backtrace] [./source/server/backtrace.h:96] #2: absl::lts_20230802::raw_log_internal::RawLog() [0x1dc3944]
[2024-04-18 11:09:45.790][28517][critical][backtrace] [./source/server/backtrace.h:96] #3: absl::lts_20230802::Mutex::LockSlowLoop() [0x1d9c404]
[2024-04-18 11:09:45.801][28517][critical][backtrace] [./source/server/backtrace.h:96] #4: absl::lts_20230802::Mutex::LockSlowWithDeadline() [0x1d9b568]
[2024-04-18 11:09:45.811][28517][critical][backtrace] [./source/server/backtrace.h:96] #5: absl::lts_20230802::Mutex::LockSlow() [0x1d9b364]
[2024-04-18 11:09:45.821][28517][critical][backtrace] [./source/server/backtrace.h:96] #6: absl::lts_20230802::Notification::WaitForNotification() [0x1d9e010]
[2024-04-18 11:09:45.831][28517][critical][backtrace] [./source/server/backtrace.h:96] #7: Envoy::Event::DispatcherImpl::runPostCallbacks() [0x1742418]
[2024-04-18 11:09:45.840][28517][critical][backtrace] [./source/server/backtrace.h:96] #8: event_process_active_single_queue [0x1bea698]
[2024-04-18 11:09:45.850][28517][critical][backtrace] [./source/server/backtrace.h:96] #9: event_base_loop [0x1be91dc]
[2024-04-18 11:09:45.860][28517][critical][backtrace] [./source/server/backtrace.h:96] #10: Envoy::FakeUpstream::threadRoutine() [0xbadad0]
[2024-04-18 11:09:45.870][28517][critical][backtrace] [./source/server/backtrace.h:96] #11: Envoy::Thread::ThreadImplPosix::ThreadImplPosix()::{lambda()#1}::__invoke() [0x1be1b84]
[2024-04-18 11:09:45.870][28517][critical][backtrace] [./source/server/backtrace.h:96] #12: start_thread [0xffffb40a2624]

Original details here:
https://dev.azure.com/cncf/envoy/_build/results?buildId=168331&view=logs&j=767be981-567e-57d8-68c3-2140ede0a0bd&t=2181edf2-f610-59f2-c43a-04bb9d0bca00&l=289


chore(fixes #2801): use function default parameters

chore(fixes #2801): use function default parameters instead of defaultProps

[x] Bug fix
[ ] New feature
[x] Chore
[ ] Breaking change
[x] There is an open issue which this change addresses
[x] I have read the CONTRIBUTING document.
[x] My commits follow the Git Commit Guidelines
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] My change requires a change to Typescript typings.

[ ] I have updated the typings accordingly.

[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@illiteratewriter please check these changes.

Please, update all the components that use defaultProps.

LGTM

What is the reason for not using Javascript default props?

What is the reason for not using Javascript default props?

Ah, because even undefined props are set (by the prop types?) to undefined and would override the default props.

I'm still seeing this issue with v9.2.3 on the Popover component
console.js:288 Warning: Popover: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.     at Popover (http://localhost:3000/static/js/bundle.js:503660:95)

I'm still seeing this issue with v9.2.3 on the Popover component
console.js:288 Warning: Popover: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead. at Popover (http://localhost:3000/static/js/bundle.js:503660:95)

same for tooltip and popover component...


Youtube.com - ERROR: Unable to extract uploader id

You want me to report!? Don't give me orders, here is your verbose output as you requested:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=sxnTSKef47U']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.11.2 (CPython) - macOS-13.2-x86_64-i386-64bit
[debug] exe versions: rtmpdump 2.4
[debug] Proxy map: {}
[youtube] sxnTSKef47U: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
^^^^^^^^^^^^^^^
File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.11/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/Cellar/youtube-dl/2021.12.17/libexec/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Same prob here I've got to know that there is a fix that already has been found
https://github.com/ytdl-org/youtube-dl/issues/31530#issuecomment-1433470254
however since I am workin on replit I really don't know how I'm gonna edit the damn youtube.py file

I fix it manually with   'uploader_id': self._search_regex( r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id', fatal=False) if owner_profile_url else None,
Now have Warning only.

No, follow the issue template, search for the problem, see that it has been fixed and how to patch it.
Duplicate of #31530.


Chore bump typescript, prettier and lint

Proposed Changes

Bumped typescript version to 3.7 and other side dependencies
Bumped the prettier version
Added a lintfix command on the package.json at the root
Run the linfix command

Potential Breaking Changes
None expected
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Codecov Report

Merging #1334 into master will decrease coverage by <.01%.
The diff coverage is 100%.

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


Added HTML debug for MNIST NN

I've added some visualization on the NN status and predictions. I was inspired by this article on ML4A.
Also, I've reduced strokeWeight since it will provide a better result (when downscaling to 28x28, if the stroke is too high, it will produce a weird image).

Awesome stuff! Can you post a link to this running in the browser? It makes it easier to review. (You can create one via your fork and github pages. If you need help, let me know!)

@shiffman never did GitHub pages, any help will be appreciated! Maybe a YouTuber made a video about this ;)

BTW, I see that in README.md there's already a link to the examples on a GitHub pages fashion...

Yes, so if you go to the settings of your fork:
https://github.com/CodingTrain/arisanguinetti/
and enable github pages for the "visualize" branch then I'd be able to see it at:
https://arisanguinetti.github.io/Toy-Neural-Network-JS/examples/mnist/

@shiffman I'm not able to add GitHub pages to branches other than master... I might be able to merge visualize into master, but then I'll have to keep it up to date, right?

Oh that's right. . .since it's your fork it's ok to have the proposed changes be in master. But maybe someone who has a better idea can weigh in. Also, maybe I'm just being lazy, I can pull your branch and look on my computer locally!

@shiffman I'm trying to keep my master in sync with the master of the repo, so If I want to collaborate, I just add a new branch based on the master... I think I can merge the visualize branch into master, and use another branch to keep it in sync with upstream repo...

Well after this back and forth I think the simplest for you to be able to review it should be me merging the branches, so here it is:
https://arisanguinetti.github.io/Toy-Neural-Network-JS/examples/mnist/
Once you approved the pull request, I can get it back in sync with the upstream ;)


Use document environment to determine root file

Type of JetBrains IDE (IntelliJ, PyCharm, etc.) and version
IntelliJ 2018 2.2
TeXiFy IDEA version
Beta 0.6.1
What I did (steps to reproduce)
I have my \usepackage{amsmath} in a preamble file read in using \input to read it into my main file.
Just after writing this I realised that it was also mentioned in #741, and the issue seems to be coming from the fact that I write \documentclass in my preamble file:

main.tex
\input{preamble}
\begin{document}
    $\text{if}$
\end{document}

preamble.tex
\documentclass[11pt]{article}
\usepackage{amsmath}

Expected behavior
No error
Actual behavior
Command requires amsmath package
But it compiles with no errors
Also causes \amsmath to be auto imported, when writing $\text{hey}$ or the like, if not already in the document, which I really don't like in general, since the same thing can be done while solving problems with alt+enter

If you can't even reproduce the problem yourself, I have no idea what the problem is. So you have a big project with error, and a small project without error. To find what causes the problem, you could copy the big project completely and then remove parts until it works again - then please post the minimal example which includes the lines which cause the error.
Also take a look here https://github.com/Ruben-Sten/TeXiFy-IDEA#what-should-my-document-structure-look-like
And if you want your \usepackage in a separate file, it would make more sense to use a package .sty file or a class .cls file.

I updated the original post with a minimal example for reproducing the error, but I can also see that this does not comply with 'How should my document structure look like?' since I place \documentclass in a preamble file, but I can also see that I'm not the only one who thought it a problem.

I was just thinking the same. I agree, except for one thing: I'm not sure how many people have their document environment in an included file?
I still think we should discourage putting \documentclass in an included .tex file, but creating errors is not the right way, it should at most be a warning (but it's probably easier not to do that).

My use case is that I create different files but want to use the exact same preamble, so having to write the same documentclass line in each document seems a bit stupid, when it could be grouped with the preamble, since it's imported as the first thing anyways.
What I understand is that to solve this another way of defining the root would have to be defined, maybe assuming that a file that is never in an \input or include in another file would be the root  file?
Or maybe using the file chosen as a main file to compile as the root?

The issue is mostly finding a resource effective way to do it. Because file set determination is used almost everywhere. Halving its efficiency almost means halving the plugin's.
I think assuming the root file to contain the document environment is reasonable. Also because we already use it for compilation gutter icons.

Another option is to leave the file set determination as it is, and then provide an optional manual override in the settings where you can specify the root document.

The true root document should have both \documentclass and \begin{document}..\end{document}.
Both commands might be within of \input. It seems reasonable to have two transitive properties for each .tex file: hasDocumentClass and hasDocumentEnvironment which would be true if it has \documentclass / \begin{document}..\end{document} or includes file which has this property set to true.
Since \documentclass is very first statement of true root document and \end{document} is very last this approach should cover all possible scenarios.

For now I'd suggest keeping \documentclass as document root.
Later, when magic comments get introduced, you'd be able to use something like %! DocumentRoot in your file to denote it's the document root. Related to #101.


Wait for all notebook models to load before shutting down active sessions during python upgrade

This PR fixes https://github.com/microsoft/azuredatastudio/issues/17606

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/models/notebookInput.ts
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.0005%

Covered Lines:
27179

Relevant Lines:
59208

💛  - Coveralls


[🐞] Getting started issues

Which component is affected?
Starters / CLI
Describe the bug
I created an empty dir, changed into it and ran pnpm create qwik@latest
This failed, because pnpm didn't see a package.json in the directory.
Then I did npm create qwik@latest. This launched the wizard.
Then it asked where to put it, and said I could use . or ./ for the current directory. I did ..
Then it said that the directory . already existed and wasn't empty. I told it to remove and create.
That installed everything but afterwards I was still in the deleted . directory, and I had to do cd $PWD to go into the new directory
Reproduction
about:new
Steps to reproduce
No response
System Info
System:
    OS: Linux 5.15 NixOS 22.11 (Raccoon) 22.11 (Raccoon)
    CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
    Memory: 5.42 GB / 15.20 GB
    Container: Yes
    Shell: 5.1.16 - /run/current-system/sw/bin/bash
  Binaries:
    Node: 18.15.0 - ~/.nix-profile/bin/node
    Yarn: 1.22.15 - ~/bin/yarn
    npm: 9.5.0 - ~/.nix-profile/bin/npm
  npmPackages:
    @builder.io/qwik: ^1.1.1 => 1.1.1
    @builder.io/qwik-city: ^1.1.1 => 1.1.1
    undici: 5.22.0 => 5.22.0
    vite: 4.3.5 => 4.3.5

Additional Information
No response

Would you be able to copy and paste the entire interaction? I'd like to make sure I understand the incorrect flow. Thanks

pnpm in an empty dir fails:
🍀 🐚  Sat May 13 00:18:37 ~/Projects/sync-ui-qwik
13748 $ pnpm create qwik@latest
 ERROR  No package.json (or package.yaml, or package.json5) was found in "/home/wmertens/Projects/sync-ui-qwik".

this is with npm:
◇  Where would you like to create your new project? (Use '.' or './' for current directory)
│  .
│
●  Creating new project in  /home/wmertens/Projects/sync-ui-qwik  ... 🐇│
◇  Directory "./" already exists and is not empty. What would you like to do?
│  Overwrite and replace this directory
│

[...]

○  Result ────────────────────────────────────────────────╮
│                                                         │
│  🦄  Success!                                           │

[...]

└  Happy coding! 🐇
direnv: error LoadConfig() Getwd failed: getwd: no such file or directory
🍀 🐚  Fri May 12 16:47:56 ~/Projects/sync-ui-qwik
13747 $ npm i
/nix/store/njh6p007ymbmcgas5l7sqqxfmm394zx1-nodejs-18.15.0/lib/node_modules/npm/lib/cli.js:48
    throw err
    ^

Error: ENOENT: no such file or directory, uv_cwd

[...]

🍀 🐚  Fri May 12 16:48:30 ~/Projects/sync-ui-qwik
13749 $ cd $PWD
🍀 🐚  Fri May 12 16:48:36 ~/Projects/sync-ui-qwik on master
13750 $ npm i

added 310 packages, and audited 311 packages in 4s

Hey @wmertens, thanks for opening this issue, I saw that this steps are working with the latest version of Qwik, btw a lot of things happened during this months. 🚀
So I'm closing this issue for now, feel free to re-open it if it's still an issue for you.


Migrate from discord.py to py-cord

I suggest changing the requirement from discord.py to py-cord as d.py is no longer being maintained.
Note: py-cord is close to releasing a 2.0 version which has breaking changes, but their current PyPi version should be a drop-in replacement for d.py

Not everyone use pycord. Some uses nextcord. So if you want pycord instead of discord.py then you can create a fork > modify files and install from your fork

Why not use extras to allow people to use any of the three?

From: Md Shahriyar Alam @.>
Sent: Wednesday, December 29, 2021 5:48:41 AM
To: jnawk/Quart-Discord @.>
Cc: williamhatcher @.>; Author @.>
Subject: Re: [jnawk/Quart-Discord] Migrate from discord.py to py-cord (Issue #19)
Not everyone use pycord. Some uses nextcord. So if you want pycord instead of discord.py then you can create a fork > modify files and install from your fork
—
Reply to this email directly, view it on GitHubhttps://github.com/jnawk/Quart-Discord/issues/19#issuecomment-1002556534, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF3WBO2BYJVUXLCBRJ4GCRTUTLYRTANCNFSM5K3GHY4Q.
You are receiving this because you authored the thread.Message ID: @.***>

Feel free to submit a PR.   In the 30 seconds I had to take a look, it could probably be done, but it'll take more than 30 seconds to figure out.


Fix bug where x-forwarded-for header is ignored

See issue https://github.com/creativelive/hapi-ratelimit/issues/24

Whilst this solution seems correct, the problem with using the first entry in the X-Forwarded-For header is that it can be spoofed. The typical solution for this is to use the last entry in the list. I'd be in favor of that approach. From what I can tell we were late to the show for you and as such you've deleted your fork. I'm going to close this PR in favor of a better solution (as the one I listed above.). Feel free to reply to #24 if you're still interested in a solution.


Error: Warning! Status check on the deployed lambda failed. A GET request to '/' yielded a 502 response code.

Context
When im trying to deploy using zappa update dev im getting this error:
Error: Warning! Status check on the deployed lambda failed. A GET request to '/' yielded a 502 response code.
Expected Behavior
Could not get a valid link such as https://**********.execute-api.us-west-2.amazonaws.com/dev such as this
Actual Behavior
{'message': 'An uncaught exception happened while servicing this request. You can investigate this with the zappa tail command.', 'traceback': ['Traceback (most recent call last):', ' File /var/task/handler.py, line 540, in handler with Response.from_app(self.wsgi_app, environ) as response:', ' File /var/task/werkzeug/wrappers/base_response.py, line 287, in from_app return cls(*_run_wsgi_app(app, environ, buffered))', ' File /var/task/werkzeug/wrappers/base_response.py, line 26, in _run_wsgi_app return _run_wsgi_app(*args)', ' File /var/task/werkzeug/test.py, line 1119, in run_wsgi_app app_rv = app(environ, start_response)', TypeError: 'NoneType' object is not callable]}
when im trying to access any endpoint from my application
Your Environment

Zappa 0.54.1
Python version 3.7
Zappa settings
{
"dev": {
"app_function": "app.app",
"aws_region": "us-west-2",
"profile_name": "default",
"project_name": "******",
"runtime": "python3.7",
"s3_bucket": "zappa-"
}
}

@mathsmtnx what spits out your logs if you run zappa tail dev --since 5m (shortly after a failed deployment)?

Hello @kulor, thanks for the answer.
i was getting the following error
[1612507108211] Instancing..
[1612507108215] Failed to find library: libmysqlclient.so.18 ...right filename?
and thats weird cause i was able to deploy my flask app with the same virtual enviroment a couple days before facing this error.

@mathsmtnx  I faced similar issues with MySQL as I don't think the lib is bundled in the image any longer. I reluctantly resorted to using pymysql.
Switchover from libmysqlclient was fairly easy. Install pip install pymysql and add this to your appname/__init__.py:
import pymysql
pymysql.install_as_MySQLdb()

Let me know if this works as I have fought my fair share of MySQL related Zappa issues?

Please close this issue as this is not something the Zappa Team can solve.
You're sadly limited to the binaries included on AWS Lambda.

closing issue.


Minor changes needed to adhere to tekton-provenance format

Modify name of literals to "automatically" have Tekton Chains push signatures and attestation.
See format.

Modify shp-output-image to *IMAGE_URL
write out IMAGE_URL to a result ( update to step generation )
modify result named shp-image-digest to *IMAGE_DIGEST

Here's how the diff looks like:
https://www.diffchecker.com/S6oLSCE0
I was successful upon making the above changes manually.

/kind feature

Tekton Chains looks for results, shp-output-image is a param.

Marking this as needing a SHIP, since this will impact how build strategy implementations.


[wrt]Add auto csp test for linux

There are two wrt test issues for testskit in deepin:
For type=wrt, it run succussful, but testkit get the
test result as N/A, even if the test run PASS.
In my deepin. every tests will be launched twice,
but the test num in result xml is correct.

Impacted tests(approved): new 5, update, 0, delete 0
Unit test platform: [Linux]
Unit test result summary: pass 0, fail 0, block 5

@yinhaichao @haoxli CSP auto test cases should be in tct-csp-w3c-tests which type='js' i think? http://otcqa.sh.intel.com/wiki/Crosswalk_on_Linux_Desktop_Test_Plan#Crosswalk_on_Debian_and_other_Linux_Distributions
For any test suites leveraged from web api, keep the web api test suites.

@yinhaichao @haoxli Please double check if the type='wrt' here is correct, if you are using testharness.js, it should be 'js'.


Persistent pause state on navigation

The pause/unpause button state is reset on navigation.
We could make a global state of this functionality.

Does Grafana do it? 🤔

Maybe you meant to comment on #110 :)
It would be nice, but I meant something more simple, the idea is to display graphically the data that is already exists in the UI


Update az_k8sconfig_aks_hci.ps1

got "argument --cluster-name/-c: expected one argument", cause variable "$arcClusterName" is empty

Thank you @masyanru it LGTM I also updated the helm version https://github.com/microsoft/azure_arc/pull/857 and aligned variables names


missing ratio for SKUs

Hi.
The linked document (https://isfratio.blob.core.windows.net/isfratio/ISFRatio.csv) is missing ratios for

EDSv5-Type1
Standard_D32plds_v5
Standard_E2pds_v5
Standard_E8pds_v5 SKUs.

Checking on the Azure portal, it seems like instance size flexibility is applicable for those. Can you please update the CSV file?

@Naveenommi-MSFT
https://learn.microsoft.com/en-us/azure/virtual-machines/dplsv5-dpldsv5-series
https://learn.microsoft.com/en-us/azure/virtual-machines/epsv5-epdsv5-series
https://learn.microsoft.com/en-us/azure/virtual-machines/dedicated-host-memory-optimized-skus

@noahwood28
Can you please check and add your comments on this doc update request as applicable.

@ManoharLakkoju-MSFT I need some more context. Where is https://isfratio.blob.core.windows.net/isfratio/ISFRatio.csv coming from?

I see, so the question is about missing ISF ratio here: https://learn.microsoft.com/en-us/azure/virtual-machines/reserved-vm-instance-size-flexibility. @mimckitt I don't have required expertise to update this csv. Can you loop in the RI folks?

@mimckitt is there any update from your side?
@noahwood28

This case has been resolved
#please-close


fix: Product detail product:price meta tags for OpenGraph

1. Why is this change necessary?
According to the OpenGraph specification there is no product:price meta tag, only product:price:amount and product:price:currency exist.
2. What does this change do, exactly?
Changes the meta tags.
3. Describe each step to reproduce the issue or behaviour.
Look at the meta tags of the product detail page.
4. Please link to the relevant issues (if any).
-
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-17694
Please use this issue to track the state of your pull request.

Thanks for your contribution! :blue_heart:
We've just set your PR to "Scheduled".
This means our initial screening is passed.
Your PR will now be reviewed and tested before being put through our internal extended test suite and review process.
We will keep you informed whether something has to be done by you or when the PR is merged 🙂
If you have any questions, feel free to ask.


Invalid Database

While trying to run the config tool, the connection dialog connects to the db without issue, but once selected it always just says "invalid database" when I hover the X that appears on the plug button. The destination server is SQLServer 2016 SP3.

Hi, the destination database needs to be either:

An empty database
If any objects are detected the schema won't deploy.  This validation is to prevent you from overwriting the schema of another database by mistake.  If you created a new DB, maybe it already has objects in it.  Check the model database.
An existing DBA Dash repository database with the schema deployed previously.
If you have deployed previously it's possible it failed for some reason and this prevents the validation check.  It might be worth deleting it and re-creating it
Doesn't exist
The database will either be created when the service starts or when you click Deploy/Update Database.

I would suggest removing the database and allowing the tool to create the database.
Hope this helps - let me know if you need some more assistance.
For reference, this is the validation check that is used:
IF EXISTS(
	SELECT * FROM sys.extended_properties
	WHERE major_id=OBJECT_ID('DBVersionHistory')
	AND name = 'AppID'
	AND value='74F9FD8A-DF22-4355-9A7A-6E1F4AE712B9'
)
BEGIN
	SELECT TOP(1) Version
	FROM dbo.DBVersionHistory
	ORDER BY DeployDate DESC
END
ELSE IF NOT EXISTS(SELECT *
			FROM sys.objects
			WHERE type NOT IN('S','IT','SQ')
            )
        AND DB_ID()>4
BEGIN
	SELECT '<IP_ADDRESS>' AS Version
END
ELSE
BEGIN
	RAISERROR('Invalid database',11,1)
END

Ok got it thank you. It was not clear that the database had to be empty. Perhaps that would be helpful in the quick start guide to mention.

Thanks for the feedback - I'll look to improve the documentation.  Hope you find DBA Dash useful.

Documentation has been updated


Release 2019.8.20

👏

The classifier change was long overdue. We were stable when I switched to
calver.
On Tue, Aug 20, 2019 at 1:38 PM Danny Hermes<EMAIL_ADDRESS>wrote:

@dhermes commented on this pull request.
In setup.py
https://github.com/theacodes/nox/pull/239#discussion_r315892052:

 description="Flexible test automation.",

 long_description=long_description,

 url="https://nox.thea.codes",

 author="Alethea Katherine Flowers",

<EMAIL_ADDRESS>
 license="Apache Software License",

 classifiers=[

   "Development Status :: 4 - Beta",

   "Development Status :: 5 - Production/Stable",

😮
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/theacodes/nox/pull/239?email_source=notifications&email_token=AAB5I4Y7JNXMJOUZN2XSCOTQFRI55A5CNFSM4IN4HAI2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCCES6FI#pullrequestreview-277425941,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB5I46Z4LZH3W3TQYWISZLQFRI55ANCNFSM4IN4HAIQ
.

Totes. Congrats all!


chore: turn SQL templating off by default

SUMMARY
Use a new feature flag to make it possible to enable/disable SQL templating.
Note:
Setting is off by default
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[X] Removes existing feature or API

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3d7b805). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master   #11172   +/-   ##
=========================================
  Coverage          ?   60.58%
=========================================
  Files             ?      391
  Lines             ?    24478
  Branches          ?        0
=========================================
  Hits              ?    14829
  Misses            ?     9649
  Partials          ?        0

Flag
Coverage Δ

#python
60.58% <100.00%> (?)

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

Impacted Files
Coverage Δ

superset/config.py
90.07% <ø> (ø)

superset/jinja_context.py
81.81% <100.00%> (ø)

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 3d7b805...0178361. Read the comment docs.

@dpgaspar I think it's OK to merge this once conflicts are resolved


[Bug]: Operation is not valid due to the current state of the object. - Updating Site

Contact Details
<EMAIL_ADDRESS>What happened?
I am currently dealing with an issue where I have ~300 sites in Halo that are missing the property of 'name'.  With HaloAPI I've been able to create a list of all of these problem sites and am attempting to create the property of 'name' for each objects, set the name to be the same as the site ID and then push that modified object back into Halo.
Shown in the image below is the test site I am using.  It was originally missing the property of name. Using the Add-Member cmdlet I added a 'name' with a value of '1323'.  When using Set-HaloSite I get the error.  I've looked around for some examples of Set-HaloSite but I haven't been able to find a utilization of this command.  Also my powershell-fu is weak so I may be missing something obvious.  From what I've looked through it seems like I should be passing the command an object that contains the site ID and whatever other fields I want to update.

Version
1.20.0
Which operating systems have you tested on?

[X] Windows 10
[ ] Windows 11
[ ] Mac OS
[ ] Linux

What PowerShell version are you running?
7.4.1
Halo Product
Halo PSA
Halo Version
2.132.54
What command did you run?
Set-HaloSite $test

What was the output of the command?
Exception: C:\Users\Username\OneDrive\Documents\PowerShell\Modules\HaloAPI\1.20.0\Private\New-HaloError.ps1:65
Line |
  65 |          throw $ErrorRecord.Exception.Message
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Operation is not valid due to the current state of the object.

This should have been resolved now - it was an issue in the background with Halo vs PowerShell 7.4.0


To the new engine!

Alter the code to access not the old engine, but the new engine until multi-tenancy is introduced.

Splitting into different issues. Still accessing the NPE, but will also use Manifold as a way to test wrangler.


Amalgamated headers on netlify not working on Godbolt (compile to WebAssembly)

Please see https://godbolt.org/z/asfaPs7KE
https://simde.netlify.app/amalgamated/arm/neon.h:37573:24: error: use of undeclared identifier 'fmaxf'
        r_.values[i] = fmaxf(a_.values[i], b_.values[i]);

Think maybe the hosted version just needs to be updated?

Hm, maybe this is a godbolt thing, math.h is provided by emscripten, and I think godbot uses plain clang++ without any emscripten.

On the other hand, we have detections like:
https://github.com/simd-everywhere/simde/blob/bdc869813d2d49ee45d28c1bd367b3b9a5982ff0/simde/arm/neon/maxnm.h#L49
that doesn't seem to be working when on godbolt.

Hm, ti looks like that call is missing the simde_math_ prefix, so it's trying to use fmaxf instead of __builtin_fmaxf.  Also, the simde_math_f{min,max}{,f} macros are messed up, they should take two parameters not three.
I'm testing a fix right now, though since I don't have a good way to test this locally it might take a few tries…

It's working now. Thanks for the report!


Enable Indication into Client Characteristic Configuration

I would like to enable DFU mode of my nordic device.
In order to perform this, I have to subscribe to a characteristic with Indications enabled.
To do it, I have modified your code as followed :
status = co_await characteristic.WriteClientCharacteristicConfigurationDescriptorWithResultAsync(GattClientCharacteristicConfigurationDescriptorValue::Indicate);
Unfortunately, indications do not seem to be enabled.
Could you please help me ?

The solution was that I need to Write to Characteristic with GattWriteOption::WriteWithResponse option and not GattWriteOption::WriteWithoutResponse...
auto status = co_await characteristic.WriteValueAsync(buffer, GattWriteOption::WriteWithResponse);


updated the flow according to v1

Updated flow for v1 using centralized approach for managing key shards
adjusted key sharding for that only
Key sharding has reached only milestone 1 will be working on it mean while
@cb7chaitanya please have look at the code just in-case

@axatbhardwaj are we spliting the keys into 3 parts instead of 4 now ?and 2 of them will be stored in kms?

correct

Seems good @axatbhardwaj


When I drag and drop input files to a project in the webui, do not replace previous files

When I drag and drop input files to a project in the webui, the behaviour is that a second drop will overwrite and replace the first drop. I would like the second and further drop to add the new dropped files and not replace previous files

Fixed in https://github.com/nexB/scancode.io/pull/751


fix: spelling README.md

:)

It's also in the scratch.nvim repo too btw, maybe others, too lazy to check.

Thank you for pointing out


analyze only a given file list

The analyze command requires a compilation command json file and will run the analysis on
all of the files in it right now.
With an extra parameter a file list could be given to the analyze command so only the files in that list will be analyzed if the corresponding compilation command was found.

Is this file list in a text file? Or an arbitrary-long argument vector handled by argparse itself? If it is a file, what will be its format?

It thought about a simple text file. Which can be easily generated with a git command for example.
main.cpp
lib1/lib1.cpp
libb2/lib2.cpp

I think the skipfile is a solution for this issue. Please, reopen if the feature request is still relevant.


first release

@rultor release, tag is 0.1.0

@rultor release, tag is 0.1.0

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.1.0

@yegor256 Oops, I failed. You can see the full log here (spent 33min)
[INFO]  * Remote staging into staging profile ID "33927022b5669b"
[INFO]  * Created staging repository with ID "orgeolang-1121".
[INFO]  * Staging repository at https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121
[INFO]  * Uploading locally staged artifacts to profile org.eolang
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.pom.asc
Progress (1): 833 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.pom.asc (833 B at 3.9 kB/s)
Downloading from oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/maven-metadata.xml
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/maven-metadata.xml
Progress (1): 295 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/maven-metadata.xml (295 B at 512 B/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-sources.jar.asc
Progress (1): 833 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-sources.jar.asc (833 B at 4.3 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-javadoc.jar
Progress (1): 4.1/420 kB
Progress (1): 8.2/420 kB
Progress (1): 12/420 kB
Progress (1): 16/420 kB
Progress (1): 20/420 kB
Progress (1): 25/420 kB
Progress (1): 29/420 kB
Progress (1): 33/420 kB
Progress (1): 37/420 kB
Progress (1): 41/420 kB
Progress (1): 45/420 kB
Progress (1): 49/420 kB
Progress (1): 53/420 kB
Progress (1): 57/420 kB
Progress (1): 61/420 kB
Progress (1): 66/420 kB
Progress (1): 70/420 kB
Progress (1): 74/420 kB
Progress (1): 78/420 kB
Progress (1): 82/420 kB
Progress (1): 86/420 kB
Progress (1): 90/420 kB
Progress (1): 94/420 kB
Progress (1): 98/420 kB
Progress (1): 102/420 kB
Progress (1): 106/420 kB
Progress (1): 111/420 kB
Progress (1): 115/420 kB
Progress (1): 119/420 kB
Progress (1): 123/420 kB
Progress (1): 127/420 kB
Progress (1): 131/420 kB
Progress (1): 135/420 kB
Progress (1): 139/420 kB
Progress (1): 143/420 kB
Progress (1): 147/420 kB
Progress (1): 152/420 kB
Progress (1): 156/420 kB
Progress (1): 160/420 kB
Progress (1): 164/420 kB
Progress (1): 168/420 kB
Progress (1): 172/420 kB
Progress (1): 176/420 kB
Progress (1): 180/420 kB
Progress (1): 184/420 kB
Progress (1): 188/420 kB
Progress (1): 193/420 kB
Progress (1): 197/420 kB
Progress (1): 201/420 kB
Progress (1): 205/420 kB
Progress (1): 209/420 kB
Progress (1): 213/420 kB
Progress (1): 217/420 kB
Progress (1): 221/420 kB
Progress (1): 225/420 kB
Progress (1): 229/420 kB
Progress (1): 233/420 kB
Progress (1): 238/420 kB
Progress (1): 242/420 kB
Progress (1): 246/420 kB
Progress (1): 250/420 kB
Progress (1): 254/420 kB
Progress (1): 258/420 kB
Progress (1): 262/420 kB
Progress (1): 266/420 kB
Progress (1): 270/420 kB
Progress (1): 274/420 kB
Progress (1): 279/420 kB
Progress (1): 283/420 kB
Progress (1): 287/420 kB
Progress (1): 291/420 kB
Progress (1): 295/420 kB
Progress (1): 299/420 kB
Progress (1): 303/420 kB
Progress (1): 307/420 kB
Progress (1): 311/420 kB
Progress (1): 315/420 kB
Progress (1): 319/420 kB
Progress (1): 324/420 kB
Progress (1): 328/420 kB
Progress (1): 332/420 kB
Progress (1): 336/420 kB
Progress (1): 340/420 kB
Progress (1): 344/420 kB
Progress (1): 348/420 kB
Progress (1): 352/420 kB
Progress (1): 356/420 kB
Progress (1): 360/420 kB
Progress (1): 365/420 kB
Progress (1): 369/420 kB
Progress (1): 373/420 kB
Progress (1): 377/420 kB
Progress (1): 381/420 kB
Progress (1): 385/420 kB
Progress (1): 389/420 kB
Progress (1): 393/420 kB
Progress (1): 397/420 kB
Progress (1): 401/420 kB
Progress (1): 406/420 kB
Progress (1): 410/420 kB
Progress (1): 414/420 kB
Progress (1): 418/420 kB
Progress (1): 420 kB

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-javadoc.jar (420 kB at 437 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-jar-with-dependencies.jar
Progress (1): 0.1/15 MB
Progress (1): 0.3/15 MB
Progress (1): 0.4/15 MB
Progress (1): 0.6/15 MB
Progress (1): 0.7/15 MB
Progress (1): 0.9/15 MB
Progress (1): 1.0/15 MB
Progress (1): 1.1/15 MB
Progress (1): 1.3/15 MB
Progress (1): 1.4/15 MB
Progress (1): 1.6/15 MB
Progress (1): 1.7/15 MB
Progress (1): 1.9/15 MB
Progress (1): 2.0/15 MB
Progress (1): 2.2/15 MB
Progress (1): 2.3/15 MB
Progress (1): 2.4/15 MB
Progress (1): 2.6/15 MB
Progress (1): 2.7/15 MB
Progress (1): 2.9/15 MB
Progress (1): 3.0/15 MB
Progress (1): 3.2/15 MB
Progress (1): 3.3/15 MB
Progress (1): 3.4/15 MB
Progress (1): 3.6/15 MB
Progress (1): 3.7/15 MB
Progress (1): 3.9/15 MB
Progress (1): 4.0/15 MB
Progress (1): 4.2/15 MB
Progress (1): 4.3/15 MB
Progress (1): 4.4/15 MB
Progress (1): 4.6/15 MB
Progress (1): 4.7/15 MB
Progress (1): 4.9/15 MB
Progress (1): 5.0/15 MB
Progress (1): 5.2/15 MB
Progress (1): 5.3/15 MB
Progress (1): 5.4/15 MB
Progress (1): 5.6/15 MB
Progress (1): 5.7/15 MB
Progress (1): 5.9/15 MB
Progress (1): 6.0/15 MB
Progress (1): 6.2/15 MB
Progress (1): 6.3/15 MB
Progress (1): 6.5/15 MB
Progress (1): 6.6/15 MB
Progress (1): 6.7/15 MB
Progress (1): 6.9/15 MB
Progress (1): 7.0/15 MB
Progress (1): 7.2/15 MB
Progress (1): 7.3/15 MB
Progress (1): 7.5/15 MB
Progress (1): 7.6/15 MB
Progress (1): 7.7/15 MB
Progress (1): 7.9/15 MB
Progress (1): 8.0/15 MB
Progress (1): 8.2/15 MB
Progress (1): 8.3/15 MB
Progress (1): 8.5/15 MB
Progress (1): 8.6/15 MB
Progress (1): 8.7/15 MB
Progress (1): 8.9/15 MB
Progress (1): 9.0/15 MB
Progress (1): 9.2/15 MB
Progress (1): 9.3/15 MB
Progress (1): 9.5/15 MB
Progress (1): 9.6/15 MB
Progress (1): 9.7/15 MB
Progress (1): 9.9/15 MB
Progress (1): 10/15 MB
Progress (1): 10/15 MB
Progress (1): 10/15 MB
Progress (1): 10/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 11/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 12/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 13/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 14/15 MB
Progress (1): 15 MB

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-jar-with-dependencies.jar (15 MB at 6.2 MB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-jar-with-dependencies.jar.asc
Progress (1): 833 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-jar-with-dependencies.jar.asc (833 B at 4.4 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-javadoc.jar.asc
Progress (1): 833 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-javadoc.jar.asc (833 B at 4.3 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.jar.asc
Progress (1): 833 B

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.jar.asc (833 B at 4.3 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.jar
Progress (1): 4.1/24 kB
Progress (1): 8.2/24 kB
Progress (1): 12/24 kB
Progress (1): 16/24 kB
Progress (1): 20/24 kB
Progress (1): 24 kB

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.jar (24 kB at 42 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.pom
Progress (1): 4.1/7.3 kB
Progress (1): 7.3 kB

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0.pom (7.3 kB at 13 kB/s)
Uploading to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-sources.jar
Progress (1): 4.1/27 kB
Progress (1): 8.2/27 kB
Progress (1): 12/27 kB
Progress (1): 16/27 kB
Progress (1): 20/27 kB
Progress (1): 25/27 kB
Progress (1): 27 kB

Uploaded to oss.sonatype.org: https://oss.sonatype.org:443/service/local/staging/deployByRepositoryId/orgeolang-1121/org/eolang/speco/0.1.0/speco-0.1.0-sources.jar (27 kB at 47 kB/s)
[INFO]  * Upload of locally staged artifacts finished.
[INFO]  * Closing staging repository with ID "orgeolang-1121".

Waiting for operation to complete...
................

[INFO] Remote staged 1 repositories, finished with success.
[INFO]
[INFO] --- nexus-staging-maven-plugin:1.6.13:release (jcabi-deploy-to-sonatype) @ speco ---
[INFO]  + Using server credentials "oss.sonatype.org" from Maven settings.
[INFO]  * Connected to Nexus at https://oss.sonatype.org:443/, is version 2.15.1-02 and edition "Professional"
[INFO] Releasing staging repository with IDs=[orgeolang-1121]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.thoughtworks.xstream.converters.reflection.FieldDictionary (file:/home/r/.m2/repository/com/thoughtworks/xstream/xstream/1.4.19/xstream-1.4.19.jar) to field java.util.AbstractCollection.MAX_ARRAY_SIZE
WARNING: Please consider reporting this to the maintainers of com.thoughtworks.xstream.converters.reflection.FieldDictionary
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Waiting for operation to complete...
........

[INFO] Released
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  17:30 min
[INFO] Finished at: 2023-04-17T07:20:57Z
[INFO] ------------------------------------------------------------------------
\u001b[0m\u001b[0m+ mkdir /tmp/objectionary
+ cp -R src/main/eo /tmp/objectionary/objects
cp: cannot stat 'src/main/eo': No such file or directory
container cbddfd3fecfe213a2004de711a8963547b08aeb32ef75b17a5f5e4500bbdfb54 is dead
Mon 17 Apr 2023 09:21:46 AM CEST

@rultor release, tag is 0.1.1

@rultor release, tag is 0.1.1

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 0.1.1

@yegor256 Done! FYI, the full log is here (took me 35min)


BUG: BNB chain data not updating in Paloma. Account Sequence mismatch Error. Validator jailed

What is happening?

Section description
Provide as much context as you can. Give as much context as you can to make it easier for the developers to figure what is happening.

time="2022-10-05T09:06:18+02:00" level=info msg="sending account info to paloma" acc-address=0x6dc59EE4bdFa2C791229004f29b08F783491a934 chain-reference-id=bnb-main chain-type=evm
time="2022-10-05T09:06:18+02:00" level=info msg="sending account info to paloma" acc-address=0x6dc59EE4bdFa2C791229004f29b08F783491a934 chain-reference-id=eth-main chain-type=evm
time="2022-10-05T09:06:25+02:00" level=error msg="couldn't update external chain info. Will try again." err="rpc error: code = InvalidArgument desc = account sequence mismatch, expected 76, got 75: incorrect account sequence: invalid request"
time="2022-10-05T09:06:58+02:00" level=error msg="couldn't broadcast signatures and process attestation" error="context canceled" message-ids="[78]" queue-name=evm/eth-main/evm-turnstone-message signed-messages="[map[id:78]]"
Paloma and pigeon versions and logs

Section description
Write down paloma version.
Write down pigeon version.
Copy and paste pigeon config file as well as relevant ENV variables.

name: paloma
server_name: palomad
version: v0.10.2
commit: 0a754c6a0d8420adac5d8018b79f8502caecd168
App version: v0.9.1
commit: f6f4a62cd5d217067f7177bf683807eb287bda98
paloma gas-adjustment: 1.5 on .pigeon/config.yaml
How to reproduce?

Section description
Please write detailed steps of what you were doing for this bug to appear.

Pigeon attestation on BNB chain fails
What is the expected behaviour?

Section description
If you know, please write down what is the expected behaviour. If you don't know, that's ok. We can have a discussion in comments.

BNB chain attestation should work and tx inserted into block so validator is not jailed.

The main error here is: account sequence mismatch, expected 76, got 75: incorrect account sequence: invalid request. Do they have any script running in the background which is writing txs in favour of the validator? (e.g. increase stake every 5 minutes or something like that). Or do they have an older pigeon running in the background? Or they node is really lagging behind so that the account sequences cannot be synced.

@verabehr you are having this issue.

On mobile. Someone can try sshing to zenaida-0, then do tmux a then
ctrl-c and that will stop my script. It doesn't interface with this other
account but we can try it.
On Fri, Oct 7, 2022, 15:19 Taariq Lewis @.***> wrote:

@verabehr https://github.com/verabehr you are having this issue.
—
Reply to this email directly, view it on GitHub
https://github.com/palomachain/paloma/issues/523#issuecomment-1272095135,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY7NYYJKNBAWKVUXXP3P5F3WCCHXFANCNFSM6AAAAAAQ5I2NPY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

We will need new signing key for relayer-validators. Clsoing for now.


[NowVideo] Extractor AttributeError: 'NoneType' object has no attribute 'to_screen'

URL: http://www.nowvideo.li/video/7c345049b9419
OUTPUT:
Traceback (most recent call last):
File "info.py", line 39, in
NowVideoIE().extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 275, in extract
return self._real_extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\novamov.py", line 45, in _real_extract
'http://%s/video/%s' % (self._HOST, video_id), video_id, 'Downloading video page')
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 426, in _download_webpage
res = self._download_webpage_handle(url_or_request, video_id, note, errnote, fatal, encoding=encoding)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 333, in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 312, in _request_webpage
self.to_screen('%s: %s' % (video_id, note))
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 483, in to_screen
self._downloader.to_screen('[%s] %s' % (self.IE_NAME, msg))
AttributeError: 'NoneType' object has no attribute 'to_screen'
I tried to reproduce the error and debug it step by step, but I couldn't give any valid msg argument in line 483 to extractor/common.py
Thank you for your help in advance!
Mauro

Post the full output of youtube-dl when run with --verbose option.

Hi dstftw,
I reduced the script to the minimum to make it easier to debug:
[in]
from youtube_dl.extractor import NowVideoIE
url = "http://www.nowvideo.li/video/7c345049b9419"
NowVideoIE().initialize()
NowVideoIE().extract(url)
[out - from cmd shell using --verbose]
D:>python nowvideo.py --verbose
Traceback (most recent call last):
File "nowvideo.py", line 6, in
NowVideoIE().extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 275,
in extract
return self._real_extract(url)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\novamov.py", line 45,
in _real_extract
'http://%s/video/%s' % (self._HOST, video_id), video_id, 'Downloading video
page')
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 426,
in _download_webpage
res = self._download_webpage_handle(url_or_request, video_id, note, errnote,
fatal, encoding=encoding)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 333,
in _download_webpage_handle
urlh = self._request_webpage(url_or_request, video_id, note, errnote, fatal)
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 312,
in _request_webpage
self.to_screen('%s: %s' % (video_id, note))
File "C:\Python34\lib\site-packages\youtube_dl\extractor\common.py", line 483,
in to_screen
self._downloader.to_screen('[%s] %s' % (self.IE_NAME, msg))
AttributeError: 'NoneType' object has no attribute 'to_screen'
============================================================
Was it more helpful? May I do anything to make the investigation about this issue easier?
Thank you again!
Mauro

What are you trying to achieve? For embedding youtube-dl you should use it like that.

I was trying to download this video from nowvideo.
The idea it was to integrate this part of the code in another that is using selenium and lxml to collect the links to the episodes of a tv show.

Extractor are not designed to be used standalone, you can just do:
import youtube_dl

ydl_opts = {}
with youtube_dl.YoutubeDL(ydl_opts) as ydl:
    info = ydl.extract_info(URL, download=False)


Clear inlinee callinfo from the catch of OP_TryFinally as well

When we hit an exception and we have a try finally within a try catch. We will execute finally code by calling BailOnException.
Since we inline into functions with try now, we will end up in inconsistent inlinee callinfo when we call the bailout code from finally.
So add the walker and clear inlinee callinfo.
Also move tryCatchAddr ctor inside a scope, so that it executes before user catch code.
Fixes OS#14336922

Reopened against release/1.8. Addressed review comment

How did you address @LouisLaf 's concerns from the previous PR?

https://github.com/Microsoft/ChakraCore/pull/4051#issuecomment-340137999 was regarding the use of the isInlineeCleared Boolean that I used to avoid do the stack walk and clear when there is a try catch/try finally nesting. The suggestion was to use a stack to restore previous state correctly. My 2nd commit in the PR addresses this.
I had added isInlineeCleared bit to mark when we have cleared inlinee frames's callinfo count on an exception within a try finally enclosed in some try catch.
I later checked this bit in the enclosing OP_TryCatch to make sure we don't walk the stack to clear info again.
This was unnecessary, because if there was an expection within try finally, then we will bailout and never exercise the code in OP_TryCatch


Provider errors upgrading from 0.27.0 to 1.0.0

Describe the bug
I'm using a modular approach to defining my pipelines and I'm getting a high number of errors for instances of the module when I move my provider version from 0.27.0 to 1.0.0 and follow the upgrade steps.
On plan, for each instance of the module, I see:
│ Error: Invalid attribute value
│
│   with buildkite_pipeline.pipeline["persona-identity"],
│   on main.tf line 1, in resource "buildkite_pipeline" "pipeline":
│    1: resource "buildkite_pipeline" "pipeline" {
│
│ Invalid use when repository is: git@bitbucket.org:persona-id/persona-identity.git

And:
│ Error: Invalid Attribute Value
│
│   with buildkite_pipeline.pipeline["persona-identity"],
│   on main.tf line 1, in resource "buildkite_pipeline" "pipeline":
│    1: resource "buildkite_pipeline" "pipeline" {
│
│ Attribute provider_settings.pull_request_branch_filter_enabled true, got: false

In the plan output. I get both errors for every instance of the module.
To Reproduce
Here is my modular definition block:
resource "buildkite_pipeline" "pipeline" {
  # See: https://registry.terraform.io/providers/buildkite/buildkite/latest/docs/resources/pipeline
  for_each = local.pipelines

  # Required settings
  default_branch = each.value.default_branch
  description    = each.value.description
  name           = each.key
  repository     = each.value.repository

  # Immutable settings
  steps = lookup(each.value, "custom_steps", lookup(each.value, "deflake_mode", false) ? file("./deflake-steps.yaml") : file("./default-steps.yaml"))

  # Optional settings
  allow_rebuilds             = lookup(each.value, "allow_rebuilds", true)
  branch_configuration       = lookup(each.value, "branch_configuration", "")
  default_timeout_in_minutes = lookup(each.value, "default_timeout_in_minutes", 0)
  maximum_timeout_in_minutes = lookup(each.value, "maximum_timeout_in_minutes", 0)
  tags                       = lookup(each.value, "tags", [])

  skip_intermediate_builds                 = lookup(each.value, "only_build_latest_branch", lookup(each.value, "skip_intermediate_builds", true))
  skip_intermediate_builds_branch_filter   = lookup(each.value, "only_build_latest_branch_filter", lookup(each.value, "skip_intermediate_builds_branch_filter", ""))
  cancel_intermediate_builds               = lookup(each.value, "only_build_latest_branch", lookup(each.value, "cancel_intermediate_builds", true))
  cancel_intermediate_builds_branch_filter = lookup(each.value, "only_build_latest_branch_filter", lookup(each.value, "cancel_intermediate_builds_branch_filter", ""))

  provider_settings = {
    build_branches                           = lookup(each.value, "build_branches", true)
    build_pull_requests                      = lookup(each.value, "build_pull_requests", true)
    build_tags                               = lookup(each.value, "build_tags", false)
    filter_condition                         = lookup(each.value, "filter_condition", "")
    filter_enabled                           = lookup(each.value, "filter_enabled", false)
    publish_commit_status                    = lookup(each.value, "publish_commit_status", true)
    publish_commit_status_per_step           = lookup(each.value, "publish_commit_status_per_step", false)
    pull_request_branch_filter_configuration = lookup(each.value, "pull_request_branch_filter_configuration", "")
    pull_request_branch_filter_enabled = lookup(each.value,
    "pull_request_branch_filter_enabled", false)
    skip_pull_request_builds_for_existing_commits = lookup(each.value, "skip_pull_request_builds_for_existing_commits", true)
  }
}

And here are my variables.tf for one instance of the module:
locals {
  pipelines = {
    "persona-identity" = {
      repository     = "git@bitbucket.org:persona-id/persona-identity.git"
      description    = "Persona Identity Service"
      default_branch = "master"
    },
}

Expected behavior
Following the upgrade guide, I was expecting a fairly straightforward upgrade to 1.0.0 from 0.27.0. I didn't think any of our structure here was really pushing limits.
Additional context
Since we're not actually overriding the default value of pull_request_branch_filter_enabled in this instance of the module, I deleted it to see if I could get it to plan/apply. Terraform just complains about one of the other settings in the provider_settings block when I do that. Feels like it is not so much about the setting, and more that we're doing a lookup with a default  value for the setting in our case.

Thanks @ianchesal I got you to move this but now this does seem more related to #409 than I originally thought. That's okay though, we'll keep you updated here as well.
I think this comment also applies then: https://github.com/buildkite/terraform-provider-buildkite/issues/409#issuecomment-1742862386

Hi @ianchesal, we've released v1.0.2 with a fix for this. Can you give it a shot and let us know if it still doesn't work or raise a new issue if some other bug comes up

I'm still seeing invalid attribute value errors for attributes in the provider_setting block when I run terraform refresh during the upgrade.
For the example above it's:
╷
│ Error: Invalid Attribute Value
│
│   with buildkite_pipeline.pipeline["persona-identity"],
│   on main.tf line 1, in resource "buildkite_pipeline" "pipeline":
│    1: resource "buildkite_pipeline" "pipeline" {
│
│ Attribute provider_settings.filter_enabled true, got: false
╵
╷
│ Error: Invalid Attribute Value
│
│   with buildkite_pipeline.pipeline["persona-identity"],
│   on main.tf line 1, in resource "buildkite_pipeline" "pipeline":
│    1: resource "buildkite_pipeline" "pipeline" {
│
│ Attribute provider_settings.pull_request_branch_filter_enabled true, got: false
╵

Based on the docs, filter_enabled seems like it should be fine to use here. We're BitBucket, not Github, so trigger_mode = "code" shouldn't apply.
For pull_request_branch_filter_enabled -- docs say it's only valid if build_pull_requests = true but does that mean I can't include this if build_pull_requests = false? Would seem odd to not be able to have it there even if it's redundant.
These problems should be reproducible with the example I provided in the first post on this thread.

Oops I see we have missed a piece of validation in the logic. I'll create a release a fix for that

For pull_request_branch_filter_enabled -- docs say it's only valid if build_pull_requests = true but does that mean I can't include this if build_pull_requests = false? Would seem odd to not be able to have it there even if it's redundant.

That's correct, unless build_pull_requests is set and set to true, you cannot specify the filter enabled and by extension the filter condition

@ianchesal We've discussed as a team and opted to remove the validation on the provider_settings attribute. It was not working correctly and quite complex to get it correct. It's been released as 1.0.3 so you should be able to try that out now

@jradtilbrook thank you! I'll give 1.0.3 a go. I like the thought of doing pre-API call validation, but branching logic is ugly-hard in Terraform so I appreciate you helping me avoiding having to attempt that in my module.

@jradtilbrook 1.0.3 seems to be working for me! Thanks!


Token brightSight recorded as string

As per title, not much else to it. They should be numbers instead.
Should be easy fix, just wrap those in parseInt(value, 10)
Offending code:

https://github.com/Lavaeolous/PF1-StatBlock-Converter-Module/blob/10907f24faeeb5046a0b2c6fd498d4adf7411291/statblock-converter/scripts/sbcParsers.js#L794-L795
https://github.com/Lavaeolous/PF1-StatBlock-Converter-Module/blob/10907f24faeeb5046a0b2c6fd498d4adf7411291/statblock-converter/scripts/sbcParsers.js#L822-L823

There might be other instances.

Fixed in 3.3.3


[DC-1274] Running Unit tests upgrade

Added quotes around shell variables in unit tests script, and updated README.

@nishanthpp93 I closed this pull request and created an identical one for a branch in the upstream repo (not my fork).

@nishanthpp93 fyi I advised @jp3477 to re-issue the pull request using our typical developer workflow now that he has been added to all-of-us. I will just approve it since you approved this one.


0.2.2 is a breaking change

When using pipenv, when installing a new dependency or removing an old one, there's a chance you'll install this version instead of 0.2.1. This will inexplicably break your existing middleware configurations without any sort of useful error message other than a generic TypeError: __init__() takes 1 positional argument but 2 were given coming out of application = get_wsgi_application() when self.load_middleware() is called.
This is a breaking change. It should definitely not be considered a patch update.
Please consider adding documentation around this, or introducing a new patch version that handles this error case more gracefully.

Hey @relwell ,
Django Middleware is deprecated, add JSONWebTokenMiddleware middleware to your GRAPHENE settings:
GRAPHENE = {
    'SCHEMA': 'mysite.myschema.schema',
    'MIDDLEWARE': [
        'graphql_jwt.middleware.JSONWebTokenMiddleware',
    ],
}

I close the issue, if you have any questions please let me know.


 When I updated go to 1.12.7, the compiled binary is still looking at the old path:
could not import errors (cannot find package "errors" in any of:
	/usr/local/homebrew/Cellar/go/1.12.6/libexec/src/errors (from $GOROOT)

Looks like the only solution is recompile gobfuscate, was it a bug?

Confirmed. Recompiled gobfuscate and it no longer shows errors mentioned above.


Disallow running mutants on lines containing a specific pattern

Is your feature request related to a problem? Please describe.
Kindof, in my code, I know that some parts of my code are not tested as they are messages that I don't really care that much of, and testing them would be more hassle than what's worth.
Specifically, my code is like this :
// App code
function throwXmlInvalid(content, offset) {
	const err = new XTTemplateError("An XML file has invalid xml");
	err.properties = {
		id: "file_has_invalid_xml",
		content,
		offset,
		explanation: "The docx contains invalid XML, it is most likely corrupt",
	};
	throw err;
}
// Test code
try {
    throwXmlInvalid("abc", 10);
} catch (e) {
   myError = e;
}
expect(myError.id).to.equal("file_has_invalid_xml");
expect(myError.content).to.equal("abc");

I don't really care that my test will still succeed if the code is mutated to the following :
function throwXmlInvalid(content, offset) {
	const err = new XTTemplateError("An XML file has invalid xml");
	err.properties = {
		id: "file_has_invalid_xml",
		content,
		offset,
		explanation: "",
	};
	throw err;
}

Describe the solution you'd like
It would be cool to be able to disallow to aplly mutations on lines matching a given pattern.
Ideally, one could write :
module.exports = {
	ignoreLines: [/explanation:/],
}

We're currently implementing the ignore proposal: #1472
Would you be helped by that?

Yes, more specifically the third point from there :

// stryker-mutator disable next or /* stryker-mutator disable next */: this would disable all mutators Stryker on the next AST node (statement)
// stryker-mutator disable next ['StringLiteral'] or /stryker-mutator disable next ['StringLiteral']/: this would only disable the StringLiteral mutator for the next AST node (statement).
3. We might also want to allow people to exclude some patterns via stryker configuration. First, we would need to implement basic ignoring.

Because I have this "explanation:" part for about 50 times, and I don't want to add /* stryker-mutator disable next */ 50 times in the same file.

I'm closing this since this is really the same as : https://github.com/stryker-mutator/stryker-js/issues/2966


fluview & fluview_clinical data stale?

Is there a known data outage for these two data sets? Per https://delphi.cmu.edu/epidata/fluview_meta/, fluview data has not been updated since 2022-09-09.

The ILINet metadata claims the most recent epiweek available is 2022w38, which included the week from 2022-09-18--2022-09-24.
Our logs show that we pulled that very epiweek in as recently as this afternoon, but added no rows to the database as a result (which seems wrong) or possibly added negative rows (which seems worse).
I suspect something funky with the change in database platforms -- @neul3 @korlaxxalrok, can you combine your powers and dig into this? The FluView pipeline predates the pandemic so I'm afraid none of us are experts on the code, but I can give you what I've managed to unearth so far:
The relevant logs from this morning's run are on primary at
$ sed -n '/Starting step .id=157480/,/Success/p' ~automation/automation_20220914_125347.log

The relevant acquisition pipeline starts and ends in fluview_update.py, but pulls its meta data using routines in fluview.py. There's also a rough overview in the directory README.
It stores its intermediate files on primary at ~automation/driver/flu_data (careful, that directory has thousands of files in it). There are .zip files from today, which acquisition seems to be able to read without unzipping them first.
The tables you want are epidata.fluview* but there's not much there that we don't already know: last touched on Sept 9.
mysql> select max(issue) from fluview;
+------------+
| max(issue) |
+------------+
|     202235 |
+------------+
1 row in set (0.01 sec)

mysql> select max(release_date) from fluview;
+-------------------+
| max(release_date) |
+-------------------+
| 2022-09-09        |
+-------------------+
1 row in set (0.00 sec)

Note that this outage also affects ILI-Nearby (nowcast), which should be one week ahead of fluview.  It also likely affects the fluview_public data (although I'm not sure this was ever surfaced as an API endpoint).

@ian-bury-kinsa Hey, this issue has been resolved. Thank you for reporting once again!