Update SymCrypt-OpenSSL to 1.5.0

Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[ ] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary
Updates SymCrypt-OpenSSL to 1.5.0 with bugfixes for TPM2 libraries.
Change Log

Fixes bugs found when using the SymCrypt provider for TPM2 operations

Allow export of ECC key X and Y coordinates, which tpm2-tss needs
Fix the AES-CFB interface to behave the same as the OpenSSL default provider

Does this affect the toolchain?
NO
Test Methodology

Local build, tested on AZL3 Hyper-V VM

New sources: https://github.com/microsoft/SymCrypt-OpenSSL/releases/tag/v1.5.0

Buddy Build - https://dev.azure.com/mariner-org/mariner/_build/results?buildId=622798&view=results


hide price form field

redesign fixes https://spee.ch/8/ScreenCapture2018-4-3-004459.mp4

@seanyesmunt please looked my screen capture

@seanyesmunt if this guys

You still need to get rid of the span change
<span ... >
    <FormFieldPrice ... />
</span>

to
{!daemonSettings.disable_max_key_fee && (
<FormFieldPrice ... />
)}

error compiling sean

@ykris45 can you post the entire error from the console?

@tzarebczan /src/renderer/page/settings/view.jsx
Module build failed: SyntaxError: C:/Users/CHRIS/Documents/GitHub/lbry-app/src/renderer/page/settings/view.jsx: Unexpected token (188:54)
186 |                   postfix={__('Choose limit')}
187 |                 />

188 |                 {daemonSettings.disable_max_key_fee ? && (
|                                                       ^
189 |                 <FormFieldPrice
190 |                   name="max_key_fee"
191 |                   label="Max purchase price"

@ ./src/renderer/page/settings/index.js 21:12-29
@ ./src/renderer/component/router/view.jsx
@ ./src/renderer/component/router/index.js
@ ./src/renderer/component/app/view.jsx
@ ./src/renderer/component/app/index.js
@ ./src/renderer/index.js
@ multi (webpack)-dev-server/client?http://localhost:9080 webpack/hot/dev-server ./src/renderer/index.js "here it is"

@seanyesmunt how to squash via github dekstop guys

@ykris45 please do some research on your own, we cannot help you with these types of questions if you plan to keep contributing.


docs sidebar nav collapse

closes #1739

mind adding a couple screenshots?

@mparke screenshots done

Coverage increased (+0.03%) to 78.273% when pulling e403e9baa684e5b292097d8e96750d7104897fb7 on abemassry:docs-nav-sidebar-collapse into e4f8c4d028f0f965c3711bb26dfa2ed4c32c5a9c on linode:develop.

Coverage remained the same at 78.247% when pulling e403e9baa684e5b292097d8e96750d7104897fb7 on abemassry:docs-nav-sidebar-collapse into e4f8c4d028f0f965c3711bb26dfa2ed4c32c5a9c on linode:develop.

Coverage increased (+0.03%) to 78.273% when pulling aaa9664d081ff5dd39c217a8dd6a3adcda577bac on abemassry:docs-nav-sidebar-collapse into e4f8c4d028f0f965c3711bb26dfa2ed4c32c5a9c on linode:develop.

Why are you removing python.js in this PR? Wasn't it already removed?

Coverage remained the same at 78.343% when pulling a1cb3583dfd844def93960d925f1947832158b0c on abemassry:docs-nav-sidebar-collapse into 3aa2dfb55e94d8f8651d4e352c434d974dbd0cdd on linode:develop.

Coverage increased (+0.05%) to 78.393% when pulling de65ad5b4083a95cdea463a75bced067d2bab7a3 on abemassry:docs-nav-sidebar-collapse into 3aa2dfb55e94d8f8651d4e352c434d974dbd0cdd on linode:develop.

Coverage increased (+0.05%) to 78.393% when pulling 38c591d2a1813b522ceb89590ea727c98af7564b on abemassry:docs-nav-sidebar-collapse into 3aa2dfb55e94d8f8651d4e352c434d974dbd0cdd on linode:develop.

Coverage increased (+0.02%) to 78.367% when pulling 64815d040702107f9bdc421d8d24e085b9dffd10 on abemassry:docs-nav-sidebar-collapse into 3aa2dfb55e94d8f8651d4e352c434d974dbd0cdd on linode:develop.

Coverage increased (+0.03%) to 78.412% when pulling e12bec01c83f7b61887712eee763c30b28402a59 on abemassry:docs-nav-sidebar-collapse into 0badc9214dbe071a05be4f0b4ea2f4c40bac879b on linode:develop.


When merging libraries - only /opt/lib is considered

When running mkXany only libraries in the locations X32/opt/lib and X64/opt/lib are considered.
Ideally - all libraries will be found - and merged, regardless of location.
Quick - add an extra argument to mkXany to specify the build prefix (default is /opt).

Need documentation. In principle - is addressed, just not documented in #7


libffi armv7/armv7s crashing

When using Bowser on armv7/armv7s, the bridge thread segfaults during startup: https://gist.github.com/superdump/996d8550beaf491c99e3
I have tested arm64 and it is only armv7/armv7s that crashes. This basically means that Bowser is currently not usable on devices using CPUs before the A7. That is, devices older than (and including) iPhone 5 / 5C, iPad 4, iPad Mini 2.

I've been trying get Bowser to work on a fourth-generation iPad for a few days (didn't see the above until now), but unfortunately I guess this post definitively makes that impossible. Are there any plans to add support for non-arm64 devices at some point in the future?

Yes. I am slowly working through testing different versions of libffi to try to find something that works so that we can build one version for iOS armv7/armv7s and another for arm64 until this is fixed for all.

Seem like same issue (armv7 + libffi) has been under discussion at here: https://bugs.python.org/issue23670

@jokerttu - what exactly did you do to get it working with that commit? I tried the following:
@@ -46,6 +46,9 @@ class Recipe(recipe.Recipe):
                 dir = 'aarch64-apple-darwin*'
                 arch = 'arm64'
             elif Architecture.is_arm(self.config.target_arch):
+                # armv7 and armv7s
+                self.commit = '20562ac0427c3578250d04c6e34fb0127d4551cf'
+                self.patches = ['libffi/0001-libffi-Don-t-be-smart-about-toolexeclibdir.patch']
                 dir = 'arm-apple-darwin*'
                 arch = 'arm'

But I still get the same crash here. What exactly did you build? Can you make a patch?

@superdump - I have exactly same changes than above; same commit and same patches. But for some reason it did not re-compile it before I changed the version as well.
(I am not so familiar with cerbero build environment, so it might be that I should have cleaned the previous build/cache first).

version = '3.99999'

version = '3.2.1'

After this it started to work on iPad2 which runs over Cortex-A9 (ARMv7-A), and this is only devise I have been working with at the moment; so it might be that this commit does not fix ARMv7s builds, only ARMv7.

@jokerttu - I have tried with the above changes, plus a patch to fake 3.2.1 as 3.99999 on armv7 / armv7s and I get exactly the same crash as noted in the first post in this issue:
2015-06-12 16:54:09.019 Bowser[503:124432] BowserViewController viewDidLoad
2015-06-12 16:54:09.390 Bowser[503:124470] OWR bridge starting...
** Message: Loaded namespace: GLib
** Message: Loaded namespace: GObject
** Message: Loaded namespace: Gio
** Message: Loaded namespace: GIRepository
** Message: Loaded namespace: Owr
0:00:00.007415000   503 0x152b1008 WARN            GST_REGISTRY gstregistry.c:1836:gboolean gst_update_registry(): registry update failed: registry disabled
** Message: ready
2015-06-12 16:54:10.483 Bowser[503:124470] OWR bridge started
2015-06-12 16:54:10.980 Bowser[503:124432] webViewDidStartLoading...
2015-06-12 16:54:10.981 Bowser[503:124432] creating timer
2015-06-12 16:54:11.617 Bowser[503:124432] injecting bootstrap script
(lldb) bt
* thread #15: tid = 0x1e655, 0x198ac190, name = 'owr-bridge-thread', stop reason = EXC_BAD_ACCESS (code=2, address=0x198ac190)
    frame #0: 0x198ac190
  * frame #1: 0x0024578c Bowser`ffi_closure_inner_SYSV(cif=0x0059f451, fun=<unavailable>, user_data=<unavailable>, frame=<unavailable>) + 128 at ffi.c:511

Any updates on a fix for this? and when will it be updated on itunes?

A possible fix was pushed to the Frida fork of libffi yesterday so I'll be testing that today.

How did the testing go, was it able to fix the issue?

Unfortunately not. There is something broken with a closure on armv7.

Due to a bug in cerbero, I was building using the iOS 8.3 SDK. I will try some variants again with the iOS 8.4 SDK when I get time to see if they work.

did 0.4 have this problem? I remember testing Bowser on the iphone 5 before 0.5 came out and it did not have a problem. Maybe we need to revert back to a working version until the current issue is fixed?

0.4 doesn't support 64-bit and so would no longer be allowed on the App Store I think.

I have been told that an armv7 version of libffi can be built using the old build scripts we had. That could help narrowing things down.

@superdump and related experts:
For this issue, have we fixed it now? where can we get the fixed code? thanks.
Another question:
For version of 0.3.1, Bowser cannot support IPhone 6s, and Iphone 6 with IOS9.  If we want to use this bowser, how can we do it? are there any plan for handling the problem for latest IOS 9?

At the moment it doesn't look like upstream libffi is going to address the problem so we may have to go 64-bit only for the next Bowser release. iOS 9 would of course be supported in that and I think it is already fixed to work with iOS 9 in the bowser repository.

Maybe, maybe not: https://github.com/EricssonResearch/bowser/issues/60

Hi, @jokerttu
Based on you info,   build OpenWebRTC with old libffi ('20562ac0427c3578250d04c6e34fb0127d4551cf'), I have build armv7 and armv7s, and run bowser on Iphone 5, Iphone 5 still crash!
I have done the following:
1, clean all ~/cerbero/*.cache
2, modify the following in the file of recipes/libffi.recipe  like @superdump  has done.

           # armv7 and armv7s

           self.commit = '20562ac0427c3578250d04c6e34fb0127d4551cf'

           self.patches = ['libffi/0001-libffi-Don-t-be-smart-about-toolexeclibdir.patch']

2, Bootstrap/rebuild mac os host and iOS armv7/armv7s.
3, Using my build armv7 or armv7s in the project of https://github.com/EricssonResearch/bowser/tree/master/bowser-ios.   run it on my Iphone 5 which will use the default test page of http://demo.openwebrtc.org:38080/.   the the bowser crash and exit.
 :)

This PR seems to fixa this issue, at least on iPhone 6s: https://github.com/EricssonResearch/cerbero/pull/38

Confirmed that Bowser now also works on iPhone 5 (32-bit)!

This should be fixed in cerbero master and so should also be fixed in the next releases of OpenWebRTC and Bowser! \o/

do I have to sideload bower or will the new version soon released on the app store?

@tristan-k we will be releasing this fix as part of a bigger update. You can follow and test it in advance here https://github.com/EricssonResearch/bowser/pull/61#issuecomment-152708380


Encountering Authentication Issues

When I run the start command on docker I get the following error in the data-service container.  Would greatly appreciate guidance on how to fix this issue.
`
data-service
katanaml/data-service
RUNNING
Traceback (most recent call last):
File "main.py", line 19, in
main()

File "main.py", line 15, in main
'http://<IP_ADDRESS>:5001/api/v1/skipper/logger/log_receiver'))

File "/usr/local/lib/python3.7/site-packages/skipper_lib/events/event_receiver.py", line 16, in init
credentials=credentials))

File "/usr/local/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 360, in init
self._impl = self._create_connection(parameters, _impl_class)

File "/usr/local/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 451, in _create_connection
raise self._reap_last_connection_workflow_error(error)

pika.exceptions.AMQPConnectionError
Traceback (most recent call last):
File "main.py", line 19, in
main()

File "main.py", line 15, in main
'http://<IP_ADDRESS>:5001/api/v1/skipper/logger/log_receiver'))

File "/usr/local/lib/python3.7/site-packages/skipper_lib/events/event_receiver.py", line 16, in init
credentials=credentials))

File "/usr/local/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 360, in init
self._impl = self._create_connection(parameters, _impl_class)

File "/usr/local/lib/python3.7/site-packages/pika/adapters/blocking_connection.py", line 451, in _create_connection
raise self._reap_last_connection_workflow_error(error)

pika.exceptions.ProbableAuthenticationError: ConnectionClosedByBroker: (403) 'ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfi`

Hi,
You can ignore this error. RabbitMQ service is not ready yet, when Data service is trying to connect. But Data service will auto restart and the next attempts it will establish connection. Wait around 10 seconds and run docker ps -a, you should see all containers up.

Thanks for the response quick response. There was no issue after it loaded properly. I love this project, thank you and the collaborators for putting it together!

Thanks a lot for your feedback! :) There are future improvements and additions planned. We are using this platform for our own ML products and planning to improve the platform, as we go along.


feat: increased timeout on userFunctions and fetchNotifLogsFunctions

Fetching many logs was hitting the default 3 second limit for lambdas.  Increased timeout to 120 seconds for lambdas that could possibly retrieve large data sets.

I think 2 minutes to wait for a fetch request is too long, but we can try to address that separately.


preserving specific checkpoints

Savers automatically clean up checkpoints and that's lovely.  But there are special points during training that I want to be sure to save (e.g. transitioning from a pre-training phrase to full training), which I can't ensure with the current options (unless I just keep everything, by making max_to_keep & keep_checkpoint_every_n_hours huge).
Two possible approaches:

saver.save(..., preserve=True)
Never clean up this checkpoint.

max_to_keep is defined per save_path
i.e. Whenever I change the save_path argument to save() in the middle of the session, don't clean up the checkpoints with the previous save_path.

This is related to #8658 (with a little book-keeping on the client, you could do #8658 yourself).

@sherrym

I would like to see this implemented. I simply want to retain a permanent checkpoint at the end of each epoch but since each epoch runs for a long time I also need at least one transient checkpoint retained within the current epoch so I can recover from a crash/server eviction efficiently. Saving every checkpoint is inefficient (especially as the "delete checkpoint" code is inaccessible so I can't cause the checkpoints I don't need to be deleted easily) and saving every N hours doesn't enable me to see how the model evolved at consistent epoch boundaries.

Can we close this?


Images are not shown properly for the first view in a tab starter template

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
Ionic:

   ionic (Ionic CLI)             : 4.2.1 (C:\Users\*******\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework               : @ionic/angular 4.0.0-beta.13
   @angular-devkit/build-angular : 0.8.6
   @angular-devkit/schematics    : 0.8.6
   @angular/cli                  : 6.2.6
   @ionic/angular-toolkit        : 1.0.0

Cordova:

   cordova (Cordova CLI) : 8.1.2<EMAIL_ADDRESS>   Cordova Platforms     : android 7.1.1
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 4 other plugins)

System:

   Android SDK Tools : 26.1.1 (C:\android-sdk)
   NodeJS            : v8.11.3 (C:\Program Files\nodejs\node.exe)
   npm               : 5.6.0
   OS                : Windows 10

Describe the Bug
In order to see images properly, I need to enter twice in the tab. First time, the images URL seems to be broken and don't show correctly.
Steps to Reproduce
Steps to reproduce the behavior:

Create a new tab starter
Create some grid with images inside
Run the app to view locally
Images don't show the first time

Expected Behavior
To see the images correctly the first time you open the tab
Additional Context
In the following gif you can see the problem. Until the second time you select the tab, images are not shown properly.

"brand" and "logo" are the class that contain the images.

hey guys, anyone with the same issue? thanks!

Thanks for your issue! Could you please check if this is still an issue in beta.17? That would be very nice :)

Thanks for your response! Could you please ask this question in forum.ionicframework.com or stack overflow? I think you updated the global npm packages instead your package.json


setting crs_uuid for surfaces in voronoi grid test

This is needed for grid to inherit crs.

Codecov Report

Merging #238 (3bf5a36) into master (c7e0ee8) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #238      +/-   ##
==========================================
- Coverage   53.45%   53.45%   -0.01%
==========================================
  Files          53       53
  Lines       25726    25726
==========================================
- Hits        13753    13752       -1
- Misses      11973    11974       +1

Impacted Files
Coverage Δ

resqpy/model.py
67.17% <0.00%> (-0.07%)
: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 c7e0ee8...3bf5a36. Read the comment docs.


new Job-Bug.

Bugreport:
Bug reported by Profxy
Is it a bugreport for the website or for the bot?: bot
What is the title of your bugreport?: new Job-Bug.
How can you reproduce the bug? (Explain in steps): do ?job and take a job which is longer than 2h (for example job 9). ~1h later you can do ?job again!
Which result would normally have to be?: "You have already accepted a job that has not been completed! Please be patient!"
What happens if you do the action now?: same
ReportID: 94

➤ LenoxBot commented:
Approve:
could be reproduced
Dadi

➤ LenoxBot commented:
Approve:
Could be reproduced
Nickkel

➤ LenoxBot commented:
Approve:
can repro
Denarioyt

Should be fixed in the new recode


Updates to support Catchment-CN.4.5 in addition to Catchment-CN.4.0

This PR is linked to GEOSgcm_GridComp PR 368 and GEOSldas PR 326. The objective is to implement modification required to support both Catchment-CN.4.0 and Catchment-CN.4.5. Specific files affected are:
AGCM.rc.tmpl:

added lightning frequency climatology file required by Catchment-CN.4.5

gcm_run.j:

added lightning frequency climatology file (required by Catchment-CN.4.5) for GCMRUN_CATCHCN

cc: @gmao-rreichle , @biljanaorescanin , @rdkoster , @smahanam

Label DNA until conflict with linked PR in GEOSgcm_GridComp (PR 368) is resolved.

Label DNA until conflict with linked PR in GEOSgcm_GridComp (PR 368) is resolved.

This PR is ready for review.


CTF score bug (4/3)

The game didn't stop at the score 3/3. I was able to successfully capture the fourth flag (after that the game ended as usual).

Info for searching logs: CTF server at airmash.online, 5:25-5:27 PM UTC, June 25, 2019

Now all the games are like this, maybe it isn't a bug.


Default CSP doesn't like Ractive's CSS

Description:
While avoiding/pre-compiling expressions avoids the eval-related CSP warnings, CSP does not like inline CSS as well. While you'd think not providing css would avoid this, the initial setup does some inline CSS stuff, tripping warnings.
Proposed fix:

Docs to inform developer that style-src 'unsafe-inline' can be used to bypass the whole thing.
Not providing css shouldn't trip any warnings (fix that CSS setup code).
Maybe an allowCSS that if set to false, totally ignores any CSS provided and doesn't print it too.
To have component-scoped CSS, either

Write the CSS externally to boot. Use BEM or some other naming convention to scope.
For SSR, css can be extracted to a file using Ractive.getCSS() or ractive.toCSS(). Few problems:

ractive.toHTML() doesn't emit scoping ids nor emit the CSS if rendering a document. Related issue: https://github.com/ractivejs/ractive/issues/2706

Thoughts?
Versions affected:
All?
Platforms affected:
All?
Reproduction:
http://plnkr.co/edit/uci3CFljlSJVVoPOIic5?p=info
Code:
<!DOCTYPE html>
<html>

  <head>
    <meta http-equiv="Content-Security-Policy" content="default-src 'self'">
  </head>
  <body>
    <script src="ractive.js"></script>
    <script src="script.js"></script>
  </body>

</html>

Ractive({
  el: 'body',
  append: true,
  data: {
    msg: "Hello, World!"
  },
  template: '{{ msg }}'
})

toHTML will emit scoping ids if there's css that needs to render. If you're gonna use it though, you probably need to set cssId so that it's something stable.
I think just doing a deferred init on the style element will suffice for getting rid of the csp error. It looks like setting up a nonce would be the best way to skirt the unsafe-inline requirement for ractive's css.
I'm not exactly how to approach the injected styles for progressive enhancement. Maybe throw an attribute on the style tag that tells ractive to take it over and then do indexOf checks for each chunk of css that would be added to it to see if it's already there?

As of edge now, the style injection tag will be lazy loaded rather than created immediately during ractive lib init.


Update to gradle 8.6

Quick pre-req for moving release process to jreleaser
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Any particular reason not to upgrade all the way to 8.9?


Remove manual typings, use types infered by Validator

Issue AN-723

Is that ok? Is this the intended state?

Yeah, it looks better to me.


Hi. It keep sleeping at one specific tweet and repeating sleeping...

I have 500 Tweet ids and try to collect 3200 recent tweets from each tweet_id. The below is my code. but the problem is that it doesn't move on but stuck at some tweet that I am trying to collect.. On my termial, It keep iterating and shows me that
"
getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 Rate limit reached. Sleeping for: 600 getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 ...1545 tweets downloaded so far getting tweets before<PHONE_NUMBER>448432127 Rate limit reached. Sleeping for: 644 '''
So I think there must be exception occurered when I am trying to collect tweet from user: halfbare..? but I really don't know how to handle this... Can Anyone help me please?
"
My code is like as below:
`
import tweepy
import csv
def get_all_tweets(screen_name):
consumer_key = *
consumer_secret = *
access_key = *
access_secret = *

#authorize twitter, initialize tweepy
auth = tweepy.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_key, access_secret)
api = tweepy.API(auth, wait_on_rate_limit=True, wait_on_rate_limit_notify=True)

#initialize a list to hold all the tweepy Tweets & list with no retweets
alltweets = []
noRT = []

#make initial request for most recent tweets with extended mode enabled to get full tweets
new_tweets = api.user_timeline(screen_name = screen_name, tweet_mode = 'extended', count=200, include_retweets=False)

#save most recent tweets
alltweets.extend(new_tweets)

#save the id of the oldest tweet less one
oldest = alltweets[-1].id - 1

#keep grabbing tweets until the api limit is reached
while len(alltweets) <= 3200:
    print("getting tweets before {}".format(oldest))

    #all subsiquent requests use the max_id param to prevent duplicates
    new_tweets = api.user_timeline(screen_name = screen_name,tweet_mode = 'extended', count=200,max_id=oldest, include_retweets=False)

    #save most recent tweets
    alltweets.extend(new_tweets)

    #update the id of the oldest tweet less one
    oldest = alltweets[-1].id - 1

    print("...{} tweets downloaded so far".format(len(alltweets)))

    #removes retweets
for tweet in alltweets:
    if 'RT' in tweet.full_text:
        continue
    else:
        noRT.append([tweet.id_str, tweet.created_at, tweet.full_text.encode("utf-8")])

        #, tweet.user, tweet.coordinates, tweet.place

#write to csv
with open('{}_tweets.csv'.format(screen_name), 'w') as f:
    writer = csv.writer(f)
    writer.writerow(["id","created_at","text"])
    writer.writerows(noRT)
    print('{}_tweets.csv was successfully created.'.format(screen_name))
pass

if name == 'main':
#pass in the username of the account you want to download
usernames = ["halfbare","Huw_Merlin"]
#"Fla_Medic","GertvanderHoek",
for x in usernames:
get_all_tweets(x)
`

https://twitter.com/halfbare seems to only have around that many Tweets:
>>> user = api.get_user("halfbare")
>>> user.statuses_count
1550

Once your code reaches their earliest Tweet (which seems to be https://twitter.com/halfbare/status/1117195540448432128), your call to API.user_timeline will return an empty list since there are no older Tweets. Therefore, alltweets remains the same size, under 3200, and your while loop loops infinitely and spams requests to Twitter's GET statuses/user_timeline endpoint.
You should look into using a Cursor object to paginate instead.
See https://tweepy.readthedocs.io/en/latest/cursor_tutorial.html.
For code block usage, see https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks.


Create & manage a VPN gateway tutorial page is missing the required SECOND PUBLIC IP ADDRESS block

Currently, the Tutorial – Create & manage a VPN gateway – Azure portal - Azure VPN Gateway page follows the blade up to the SECOND PUBLIC IP ADDRESS block, which seems to be missing from the tutorial page.

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

ID: a6577bc7-c52a-f290-4864-b3dbd8f58321
Version Independent ID: 51723b3e-3217-a681-3f8e-1585d86f47fc
Content: Tutorial – Create & manage a VPN gateway – Azure portal - Azure VPN Gateway
Content Source: articles/vpn-gateway/tutorial-create-gateway-portal.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@tr-achmea
Thanks for your feedback! We will investigate and update as appropriate.

@tr-achmea
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.
@cherylmc
Can you please check and add your comments on this doc update request as applicable.

Hi! This article isn't intended to create an active-active gateway, thus the 2nd public IP address isn't configured. If you are looking for active-active, see this article: https://learn.microsoft.com/azure/vpn-gateway/active-active-portal#gateway

#please-close


CMake: clang unused argument '-mfpu=neon'

On Apple ARM, I am getting the following compiler warning:
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
Is add_compile_options(-mfpu=neon) in CMakeLists.txt correct?

Yes I think it is needed, let me check. For my understanding what is your compiler version?
We can make it a bit more elaborate:
if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(arm.*|ARM.*)")
    set(IS_ARM TRUE)
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(aarch64.*|AARCH64.*)")
    set(IS_ARM64 TRUE)
endif()

if(APPLE AND (IS_ARM OR IS_ARM64))
    set(IS_APPLE_SILICON TRUE)
endif()

and then:
if(IS_APPLE_SILICON)
    message(STATUS "Detected Apple silicon architecture")

    if(IS_ARM)
        set(ARM_ARCH "arm")
    elseif(IS_ARM64)
        set(ARM_ARCH "arm64")
    endif()

    set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -arch ${ARM_ARCH}")
    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -arch ${ARM_ARCH}")

    # Enable NEON for ARM-based Apple Silicon
    add_compile_options(-march=armv8.2-a+fp16+simd)
endif()

this should also be sufficient.

This doesn't fully work for me. My ${CMAKE_SYSTEM_PROCESSOR} is "arm64", which ends up in the upper branch causing IS_ARM to be set and not IS_ARM64.
My compiler version is:
Apple clang version 14.0.0 (clang-14<IP_ADDRESS>)
Target: arm64-apple-darwin21.6.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Alright,
This seems to work for me, I upgrade my compiler:
if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(aarch64.|AARCH64.|arm64.|ARM64.)")
set(IS_ARM64 TRUE)
set(ARM_ARCH "arm64")
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(arm.|ARM.)")
set(IS_ARM TRUE)
set(ARM_ARCH "arm")
endif()
if(APPLE AND (IS_ARM OR IS_ARM64))
set(IS_APPLE_SILICON TRUE)
endif()
if(IS_APPLE_SILICON)
message(STATUS "Detected Apple silicon ${ARM_ARCH} architecture")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -arch ${ARM_ARCH}")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -arch ${ARM_ARCH}")
# Enable NEON for ARM-based Apple Silicon
add_compile_options(-march=armv8.2-a+fp16+simd)
endif()

This is my full code, also including memory sanitizers if in debug mode:
if(CMAKE_SYSTEM_PROCESSOR MATCHES "^(aarch64.|AARCH64.|arm64.|ARM64.)")
set(IS_ARM64 TRUE)
set(ARM_ARCH "arm64")
elseif(CMAKE_SYSTEM_PROCESSOR MATCHES "^(arm.|ARM.)")
set(IS_ARM TRUE)
set(ARM_ARCH "arm")
endif()
if(APPLE AND (IS_ARM OR IS_ARM64))
set(IS_APPLE_SILICON TRUE)
endif()
if(IS_APPLE_SILICON)
message(STATUS "Detected Apple silicon ${ARM_ARCH} architecture")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -arch ${ARM_ARCH}")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -arch ${ARM_ARCH}")
# Enable NEON for ARM-based Apple Silicon
add_compile_options(-march=armv8.2-a+fp16+simd)
endif()
option(ENABLE_MEMORY_CHECK "Enable memory check with sanitizers (requires DEBUG mode)" OFF)
if(ENABLE_MEMORY_CHECK)
if(NOT CMAKE_BUILD_TYPE MATCHES Debug)
message(FATAL_ERROR "ENABLE_MEMORY_CHECK is only allowed in Debug build mode")
endif()
if(APPLE)
    set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fsanitize=address -O1 -fno-omit-frame-pointer -g")
    set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -fsanitize=address -fno-omit-frame-pointer")
    set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -fsanitize=address -fno-omit-frame-pointer")
    set(CMAKE_EXE_LINKER_FLAGS_DEBUG "${CMAKE_EXE_LINKER_FLAGS_DEBUG} -fsanitize=address")
elseif(UNIX AND NOT APPLE) # Linux
    set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -O1 -g")
    set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -Og -g")
    set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS_DEBUG} -Og -g")
endif()

endif()

Yes, this fixed it for me! Thank you!
Commit here: d8561c52552bc25b77cefcde9321d01b80eb8314.


Refactor Dagger components to use scopes

Tested in an emulator. Would be nice to test in a real device and try some features like login.
Next steps:

Make objects live as long as the component they're in

Component lists with Modules
CoreComponent

CoreDataModule::class

AboutComponent (Doesn’t add CoreComponent)

MarkDownModule
AboutActivityModule

DribbbleComponent (adds Core)
HomeComponent (adds Core)

HomeModule

DataManagerModule::class,

DesignerNewsDataModule::class

ProductHuntModule::class

SourcesRepositoryModule::class

DribbbleDataModule::class

OnDataLoadedModule::class

SharedPreferencesModule

UpvoteStoryServiceComponent (adds Core)

UpvoteStoryServiceModule::class,

DesignerNewsDataModule::class

DesignerNewsDataModule
SharedPreferencesModule

StoryComponent (adds Core)

StoryModule
DesignerNewsDataModule::class,
DataModule::class,
MarkdownModule::class
SharedPreferencesModule::class

LoginComponent (adds Core)

DesignerNewsDataModule::class,
SharedPreferencesModule::class

SearchComponent (adds Core)

SearchModule

DribbbleDataModule::class,

DesignerNewsDataModule::class,

SharedPreferencesModule::class

cc @ZacSweers in case you want to take a look

See my comment on https://github.com/nickbutcher/plaid/pull/650#issuecomment-471946622 for qualifiers :).
In general this is a positive step! I do think subcomponents would be a good use here eventually though, and personally think removing the LocalApi pattern is exposing those providers as a result when the original intent was to use a private annotation that makes it impossible access them from outside that annotation's visibility. I'd also advise against qualifying root types unnecessarily, as that's sort of a default and kind of noisy IMO. Qualifiers should be to differentiate from an existing standard or primitive type, not just to denote if something is coming from a specific scope. That's what scope annotations are for! 🙂


Fix to allow retry from within Xt.update and Xt.modify

I realized that raising Retry.Later from within Xt.update and Xt.modify did not always allow one to wait for changes to the accessed location.  I considered whether it would make sense to consider that illegal, but given that Loc.update and Loc.modify explicitly allow it, I think it is best to support it.

Performance regression seems acceptable:
Benchmark 1: kcas-main/_build/default/test/kcas/xt_benchmark.exe 1 10000
  Time (mean ± σ):       6.8 ms ±   0.2 ms    [User: 5.8 ms, System: 0.6 ms]
  Range (min … max):     6.7 ms …   8.1 ms    441 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas/xt_benchmark.exe 1 10000
  Time (mean ± σ):       6.8 ms ±   0.1 ms    [User: 5.9 ms, System: 0.6 ms]
  Range (min … max):     6.7 ms …   8.1 ms    440 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/xt_benchmark.exe 1 10000' ran
    1.00 ± 0.03 times faster than 'kcas-this/_build/default/test/kcas/xt_benchmark.exe 1 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/xt_benchmark.exe 2 10000
  Time (mean ± σ):      12.9 ms ±   0.1 ms    [User: 11.9 ms, System: 0.7 ms]
  Range (min … max):    12.7 ms …  13.8 ms    234 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas/xt_benchmark.exe 2 10000
  Time (mean ± σ):      13.0 ms ±   0.1 ms    [User: 12.0 ms, System: 0.7 ms]
  Range (min … max):    12.8 ms …  13.7 ms    230 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/xt_benchmark.exe 2 10000' ran
    1.01 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas/xt_benchmark.exe 2 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/xt_benchmark.exe 4 10000
  Time (mean ± σ):      21.7 ms ±   0.2 ms    [User: 20.7 ms, System: 0.7 ms]
  Range (min … max):    21.4 ms …  22.4 ms    139 runs

Benchmark 2: kcas-this/_build/default/test/kcas/xt_benchmark.exe 4 10000
  Time (mean ± σ):      21.9 ms ±   0.2 ms    [User: 20.9 ms, System: 0.7 ms]
  Range (min … max):    21.6 ms …  22.9 ms    135 runs

Summary
  'kcas-main/_build/default/test/kcas/xt_benchmark.exe 4 10000' ran
    1.01 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas/xt_benchmark.exe 4 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 100000
  Time (mean ± σ):      18.8 ms ±   1.5 ms    [User: 30.0 ms, System: 1.6 ms]
  Range (min … max):    17.4 ms …  22.1 ms    169 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 100000
  Time (mean ± σ):      19.1 ms ±   1.7 ms    [User: 30.6 ms, System: 1.7 ms]
  Range (min … max):    17.5 ms …  27.9 ms    141 runs

  Warning: The first benchmarking run for this command was significantly slower than the rest (21.3 ms). This could be caused by (filesystem) caches that were not filled until after the first run. You are already using the '--warmup' option which helps to fill these caches before the actual benchmark. You can either try to increase the warmup count further or re-run this benchmark on a quiet system in case it was a random outlier. Alternatively, consider using the '--prepare' option to clear the caches before each timing run.

Summary
  'kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 100000' ran
    1.02 ± 0.12 times faster than 'kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 100000'

Benchmark 1: kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 200000
  Time (mean ± σ):      35.3 ms ±   3.1 ms    [User: 58.7 ms, System: 2.3 ms]
  Range (min … max):    32.9 ms …  40.2 ms    75 runs

  Warning: The first benchmarking run for this command was significantly slower than the rest (39.8 ms). This could be caused by (filesystem) caches that were not filled until after the first run. You are already using the '--warmup' option which helps to fill these caches before the actual benchmark. You can either try to increase the warmup count further or re-run this benchmark on a quiet system in case it was a random outlier. Alternatively, consider using the '--prepare' option to clear the caches before each timing run.

Benchmark 2: kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 200000
  Time (mean ± σ):      35.8 ms ±   3.1 ms    [User: 59.7 ms, System: 2.3 ms]
  Range (min … max):    33.0 ms …  40.5 ms    89 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 200000' ran
    1.01 ± 0.12 times faster than 'kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 200000'

Benchmark 1: kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 400000
  Time (mean ± σ):      68.6 ms ±   6.2 ms    [User: 116.9 ms, System: 3.4 ms]
  Range (min … max):    63.6 ms …  77.6 ms    46 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 400000
  Time (mean ± σ):      69.8 ms ±   6.5 ms    [User: 119.1 ms, System: 3.4 ms]
  Range (min … max):    64.3 ms …  78.5 ms    46 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/xt_parallel_cmp_bench.exe 400000' ran
    1.02 ± 0.13 times faster than 'kcas-this/_build/default/test/kcas/xt_parallel_cmp_bench.exe 400000'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 90
  Time (mean ± σ):      38.7 ms ±   0.4 ms    [User: 37.4 ms, System: 0.9 ms]
  Range (min … max):    38.5 ms …  41.6 ms    76 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 90
  Time (mean ± σ):      39.1 ms ±   0.1 ms    [User: 37.8 ms, System: 0.9 ms]
  Range (min … max):    38.8 ms …  39.8 ms    76 runs

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 90' ran
    1.01 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 90'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 90
  Time (mean ± σ):      24.3 ms ±   0.2 ms    [User: 44.3 ms, System: 1.2 ms]
  Range (min … max):    24.0 ms …  26.1 ms    123 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 90
  Time (mean ± σ):      24.5 ms ±   0.1 ms    [User: 44.6 ms, System: 1.2 ms]
  Range (min … max):    24.3 ms …  25.3 ms    122 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 90' ran
    1.01 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 90'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 90
  Time (mean ± σ):      15.3 ms ±   0.2 ms    [User: 49.3 ms, System: 1.9 ms]
  Range (min … max):    15.0 ms …  16.7 ms    196 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 90
  Time (mean ± σ):      15.4 ms ±   0.3 ms    [User: 49.8 ms, System: 1.9 ms]
  Range (min … max):    15.1 ms …  17.9 ms    194 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 90' ran
    1.01 ± 0.02 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 90'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 10
  Time (mean ± σ):     221.4 ms ±   0.5 ms    [User: 219.9 ms, System: 1.1 ms]
  Range (min … max):   220.6 ms … 222.2 ms    13 runs

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 10
  Time (mean ± σ):     224.7 ms ±   0.4 ms    [User: 223.2 ms, System: 1.1 ms]
  Range (min … max):   224.0 ms … 225.6 ms    13 runs

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 10' ran
    1.01 ± 0.00 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 1 1_000_000 1000 10'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 10
  Time (mean ± σ):     131.8 ms ±   0.2 ms    [User: 258.3 ms, System: 1.6 ms]
  Range (min … max):   131.6 ms … 132.4 ms    22 runs

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 10
  Time (mean ± σ):     133.8 ms ±   0.3 ms    [User: 262.4 ms, System: 1.6 ms]
  Range (min … max):   133.2 ms … 134.8 ms    22 runs

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 10' ran
    1.02 ± 0.00 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 2 1_000_000 1000 10'

Benchmark 1: kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 10
  Time (mean ± σ):      74.3 ms ±   0.3 ms    [User: 282.9 ms, System: 2.5 ms]
  Range (min … max):    73.8 ms …  75.4 ms    40 runs

Benchmark 2: kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 10
  Time (mean ± σ):      75.1 ms ±   0.3 ms    [User: 286.1 ms, System: 2.5 ms]
  Range (min … max):    74.5 ms …  76.0 ms    40 runs

Summary
  'kcas-main/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 10' ran
    1.01 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas_data/hashtbl_bench.exe 4 1_000_000 1000 10'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 1 10000
  Time (mean ± σ):       3.0 ms ±   0.0 ms    [User: 2.0 ms, System: 0.6 ms]
  Range (min … max):     2.9 ms …   3.4 ms    908 runs

  Warning: The first benchmarking run for this command was significantly slower than the rest (3.3 ms). This could be caused by (filesystem) caches that were not filled until after the first run. You are already using the '--warmup' option which helps to fill these caches before the actual benchmark. You can either try to increase the warmup count further or re-run this benchmark on a quiet system in case it was a random outlier. Alternatively, consider using the '--prepare' option to clear the caches before each timing run.

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 1 10000
  Time (mean ± σ):       3.0 ms ±   0.0 ms    [User: 2.0 ms, System: 0.7 ms]
  Range (min … max):     2.9 ms …   3.4 ms    999 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/benchmark.exe 1 10000' ran
    1.00 ± 0.02 times faster than 'kcas-this/_build/default/test/kcas/benchmark.exe 1 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 2 10000
  Time (mean ± σ):       8.2 ms ±   0.0 ms    [User: 7.2 ms, System: 0.7 ms]
  Range (min … max):     8.1 ms …   8.5 ms    367 runs

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 2 10000
  Time (mean ± σ):       8.2 ms ±   0.0 ms    [User: 7.2 ms, System: 0.7 ms]
  Range (min … max):     8.1 ms …   8.5 ms    367 runs

Summary
  'kcas-this/_build/default/test/kcas/benchmark.exe 2 10000' ran
    1.00 ± 0.01 times faster than 'kcas-main/_build/default/test/kcas/benchmark.exe 2 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 4 10000
  Time (mean ± σ):      13.2 ms ±   0.0 ms    [User: 12.2 ms, System: 0.7 ms]
  Range (min … max):    13.1 ms …  13.5 ms    227 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 4 10000
  Time (mean ± σ):      13.2 ms ±   0.0 ms    [User: 12.2 ms, System: 0.7 ms]
  Range (min … max):    13.1 ms …  13.5 ms    228 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/benchmark.exe 4 10000' ran
    1.00 ± 0.00 times faster than 'kcas-this/_build/default/test/kcas/benchmark.exe 4 10000'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 1 200000
  Time (mean ± σ):      23.1 ms ±   0.1 ms    [User: 22.1 ms, System: 0.7 ms]
  Range (min … max):    22.9 ms …  23.5 ms    129 runs

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 1 200000
  Time (mean ± σ):      23.2 ms ±   0.2 ms    [User: 22.1 ms, System: 0.7 ms]
  Range (min … max):    23.0 ms …  25.8 ms    129 runs

  Warning: Statistical outliers were detected. Consider re-running this benchmark on a quiet system without any interferences from other programs. It might help to use the '--warmup' or '--prepare' options.

Summary
  'kcas-main/_build/default/test/kcas/benchmark.exe 1 200000' ran
    1.00 ± 0.01 times faster than 'kcas-this/_build/default/test/kcas/benchmark.exe 1 200000'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 2 200000
  Time (mean ± σ):     126.8 ms ±   0.3 ms    [User: 125.5 ms, System: 1.0 ms]
  Range (min … max):   126.3 ms … 127.7 ms    23 runs

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 2 200000
  Time (mean ± σ):     126.8 ms ±   0.4 ms    [User: 125.4 ms, System: 1.0 ms]
  Range (min … max):   126.3 ms … 127.6 ms    23 runs

Summary
  'kcas-this/_build/default/test/kcas/benchmark.exe 2 200000' ran
    1.00 ± 0.00 times faster than 'kcas-main/_build/default/test/kcas/benchmark.exe 2 200000'

Benchmark 1: kcas-main/_build/default/test/kcas/benchmark.exe 4 200000
  Time (mean ± σ):     226.2 ms ±   0.3 ms    [User: 224.7 ms, System: 1.1 ms]
  Range (min … max):   225.8 ms … 226.7 ms    13 runs

Benchmark 2: kcas-this/_build/default/test/kcas/benchmark.exe 4 200000
  Time (mean ± σ):     226.3 ms ±   0.3 ms    [User: 224.8 ms, System: 1.1 ms]
  Range (min … max):   225.8 ms … 226.7 ms    13 runs

Summary
  'kcas-main/_build/default/test/kcas/benchmark.exe 4 200000' ran
    1.00 ± 0.00 times faster than 'kcas-this/_build/default/test/kcas/benchmark.exe 4 200000'


The last character is dropped when a string reaches a certain length

This problem is reproducible in a Linux environment with the latest odbc driver 13.1.7 (no such issue with the previous odbc drivers).
The Repro Script
$field_type = 'VARCHAR(386)';
$inValue1 = str_repeat( "A", 385);

$stmt = sqlsrv_query( $conn, "CREATE PROC [TestFullLenStringsOut] (@p1 " . $field_type . ", @p2 " . $field_type . " OUTPUT)
 AS
 BEGIN
   SELECT @p2 = CONVERT(" . $field_type . ", @p1 + 'X')
 END" );
if( $stmt === false ) {
    die( print_r( sqlsrv_errors(), true ));
}

$stmt = sqlsrv_query($conn, "{CALL [TestFullLenStringsOut] (?, ?)}",
     array(
       array($inValue1, SQLSRV_PARAM_IN, SQLSRV_PHPTYPE_STRING(SQLSRV_ENC_CHAR), SQLSRV_SQLTYPE_VARCHAR(386)),
       array(&$outValue1, SQLSRV_PARAM_INOUT, SQLSRV_PHPTYPE_STRING(SQLSRV_ENC_CHAR), SQLSRV_SQLTYPE_VARCHAR(386))));
if( $stmt === false ) {
    die( print_r( sqlsrv_errors(), true ));
}
while( sqlsrv_next_result( $stmt )) {}
echo "strlen: ";
print_r( strlen( $outValue1 ));
echo "\nsubstr: ";
var_dump( substr( $outValue1, -2, 2 ));
var_dump( substr( $outValue1, -10, 10 ));

Output:
strlen: 386
substr: string(2) "A"
string(10) "AAAAAAAAA"

However, using the script above but reduce the length from 386 to 385, the problem goes away. The output is shown below. In fact, there's seemingly some issue with the length 386. This is reproducible with any string that is over 385 characters.
strlen: 385
substr: string(2) "AX"
string(10) "AAAAAAAAAX"

Filed an ODBC issue in connect

The issue is fixed in the latest msodbc 13.1.9


Fix issue #1365: Be able to override default XML parser

Fixes #1365 .
Did you remember to?

[ ] Add test case(s)
[x] Update CHANGES.txt

I was a bit confused by this change until I looked at the implementation of getParser() :)

Can you resolve the conflict in CHANGES?
After that, LGTM.

@cbeust Done


tx pending indicator check + removeNFT

tx pending indicator check
fix removeNFT button

Issue https://github.com/omgnetwork/optimism-v2/issues/446

Codecov Report

Merging #457 (25d15ac) into develop (126e999) will increase coverage by 14.76%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #457       +/-   ##
============================================
+ Coverage    72.41%   87.18%   +14.76%
============================================
  Files           59       34       -25
  Lines         1820     1116      -704
  Branches       279      160      -119
============================================
- Hits          1318      973      -345
+ Misses         502      143      -359

Flag
Coverage Δ

contracts
87.18% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

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

Impacted Files
Coverage Δ

packages/core-utils/src/batches.ts

packages/data-transport-layer/src/utils/index.ts

packages/core-utils/src/common/index.ts

packages/core-utils/src/coders/index.ts

...ices/l1-ingestion/handlers/state-batch-appended.ts

...ckages/data-transport-layer/src/utils/contracts.ts

packages/core-utils/src/common/hex-strings.ts

packages/message-relayer/src/relay-tx.ts

packages/core-utils/src/watcher.ts

.../src/services/l2-ingestion/handlers/transaction.ts

... and 15 more

Continue to review full report at Codecov.

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


sipvicious: refactor

Description of changes

add dependencies
add manpages
use python3.pkgs

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 299467 run on x86_64-linux 1

2 packages built:

sipvicious
sipvicious.dist


Complete the consistency test script

Description
This PR aims to complete the consistency test script PixelSizeConsistency.js.

Instead of using import to load the external packages, require may be a better option since it could eliminate esm as a dependency. Also, since ometiff-tests is an independent repository, it should not rely on dependencies from another repository. In this case, we introduced a package.json and listed two dependencies in this file to make users install all exifreader and xml2js inside this repository.
Added gitignore file.
Updated README file to fit the new features.

Sample output looks like this


Only one directional light possible?

I'm working with a scene that is too dark in shadow---triangles facing away from the sunlight are nearly completely dark.
To fix this, I'd like to add another directional light at a lower intensity than the sun and facing in the opposite direction, so no faces should be lit by both lights.
My understanding of directional lights is that they are initially oriented toward the negative z axis, and are transformed by the orientation of their parent node.  This seems to work fine and I have created a light that always shines in the opposite direction to the provided sunlight.
However, my scene appears to be lit only by at most one light.  If I don't add the second light, I get sunlight as usual.  If I add a second light, it illuminates the triangles I expect but the sunlight appears to be turned off.
Is there a limitation with the current release where only one directional light source is supported?
If so, is there a better way to achieve what I want and increase the amount of ambient or simple global illumination in the scene?  I am adding an emissive component to models at the moment but it is not ideal.
Thanks.

Yes only one directional light is allowed, however you may have up to 256 point and spot lights in the frustum at once.  I would try adding other kinds of light to get more illumination.

The proper solution to this issue is to change the intensity of the IBL or to allow custom IBLs. There should already be a default IBL set.

Thanks both for the advice.  Sounds like we can always fall back to spotlights if need be, but I will pass your comments about image-based lighting on to our modellers and see if we can do something about that with the material parameters.

The problem is that the IBL APIs are not exposed in Sceneform yet :/

No worries, I have a simple point light filling in the shadows for now.  It's only an internal proof-of-concept for the time being and we'll switch over to something more sophisticated as new features become available.

Be aware that Filament GFX engine documentation tells that point lights do not cause shadows


Types inferring works incorrectly in v-for with destruction

Vue version
3.3.4
Link to minimal reproduction
https://play.vuejs.org/#eNqNU8FymzAQ/RUNl7QzNhzSEwOZtJ10Jj20nSa3kAOGta0UJI20Iu5Q/r0rCRPsOJ7ABe3b3ff2reijz0rFnYUojTJTaa6QGUCrWFOKTV5EaIroqhDuxb8K2DfNDd4itCxnfSEYPS6esos11wYvQqgrG0sxYdsV6IfHQgxsrL+DSor6ZAPjocMOBjUXm4MO91uuTzdAhxzWr6RsoBT7BoUgCoMBNek0zMMj+zeT5o8TD51y5jpkSXDI+5ERopoSgU6MZTXvWLdcS02efeidoEVgGT4yLkZCb6VTN6bztXPYDZXn+eRgdMX6PlSwYWBZQsmB5OVrThcyz5N4KD5HFZ8hzJJp2GgR8VZJjcu2VPGTkYJujl9DMQIkIN0vhogtuHMRbRGVSZOkqgWV1dDwTscCMBGqTa4pLdFWIG9hWcv2+jK+jD8Ru8F5OAbTLldaPhvQ1KSIFjOahIId6KUGUYMG/V7ao7I59RH0it6xD3SzyBQ0dHnWfHNkSSVbxRvQPxVyunkH1pRNI5+/+xhqC9Ms1RaqPyfiT2YXZvqlwSubzY+l3gAG+ObuB+zoewJbWdtmXMMb4G8wsrFOY0j7YkVNsmd5Xu2t3zD9kffmZocgzH4oJ9S74fP9Pr6eGf1FLrk9uTj8B3F7hx4=
Steps to reproduce

There are 3 types.
All of them have equal set of fields.
Fields have different types

type FristItem = {     type: 'first'     value: number[] }  type SecondItem = {     type: 'second'     value: string[] }  type ThirdItem = {     type: 'third'     value: boolean[] }

Create a variable of union type of types described above
const values:FristItem[] | SecondItem[] | ThirdItem[] = []

What is expected?
It is expected v-for to work the same way as destructing in loops in TS

What is actually happening?
Use it in v-for with destruction
`

 {{ value }}

`
There is a `v-if` which should filter items but value has type equal to union types of all fields with such name

Use it in v-for without destruction
`

 {{ value.value }}

`
`v-if` works as expected and `value.value` has a coresponding type

System Info
System:
    OS: macOS 13.4.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 1.14 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.6.0 - ~/.volta/tools/image/node/18.6.0/bin/node
    Yarn: 1.22.19 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 8.13.2 - ~/.volta/tools/image/node/18.6.0/bin/npm
    pnpm: 8.2.0 - ~/Library/pnpm/pnpm
  Browsers:
    Chrome: 116.0.5845.110
    Safari: 16.5.2
  npmPackages:
    vue: ^3.3.4 => 3.3.4

Any additional comments?
How it works in vue

The sane code with pure TS

I made a ts issue  #https://github.com/microsoft/TypeScript/issues/55664, expecting resolved. Temporarily your could use value.type and value.value the method you write

@wusiquan but in your example type infers correctly even with destructuring

The upper one, the test 1 code, was used to show that an array is not nested, its type is inferred right by typescript, but when it came to the test code 4 or code 5, its type is not expected.
In fact, the lower one, the template code, is compiled to some codes like test code 5 form in volar.

The issue can no longer be reproduced using the latest version of Vue.
see Playground


rename the file common.go to node.go

Spoke to both Javed and Dave and they both said to go ahead and make this pull request.
The name node.go more explicitly elucidates the node structure defined in this file along
with the fact that all of the receivers in this file directly reference node.
For someone just looking at the file structure it will more clearly tell them what this file is about.
Thanks for making this change.

OK


add 3d shapes

Hi there,
I have started to design my own standalone configurable BMS for 12V Li Batteries (3S LiIon or 4S LiFePO4).
You did a great job and I tried to copy some of your ideas and libs. The symbols and footprints can easily get imported. But the footprints have no 3d shape.
I started with a Würth screw terminal, but realized, the 3d model has the following path and is not included.
${KISYS3DMOD}/LibreSolar.3dshapes/Wuerth_WP-THRBU_74650195.stp
Can you make another repo with the 3d models?
Are there maybe license issues with the models?

Are there maybe license issues with the models?

Exactly. Most vendor 3D models have a proprietary license and I don't want to read the terms and figure out if I'm allowed to publish them. So you will have to download the files from the vendor sides yourself, unfortunately.

@martinjaeger could we document the links for easier download?


Qemu update

changed qemu network from iso to nat
split iso and qemu images

I've adopted the split-out, but not the if-up/if-down scripts, into #235


[joy-ui][docs] Add a marker demo to List page

Got this question from the community and I think it is very common use case.

[x] I have followed (at least) the PR section of the contributing guide.

@zanivan @danilo-leal I wonder if we should make the API a bit easier by introducing a new prop? maybe marker prop:
// e.g.
<List marker="disc">
  ...
</List>

@siriwatknp I think that would be nice! It's way more handy that way, to me! 😃

@danilo-leal Added a new prop called marker to the List component 👉 https://deploy-preview-39313--material-ui.netlify.app/joy-ui/react-list/#markers


cannot visualize trajectory

Hi, when I run the viz python script I got the error:

File "argoverse-api/argoverse/utils/manhattan_search.py", line 90, in find_all_polygon_bboxes_overlapping_query_bbox
overlaps_left = (query_min_x <= bboxes_x2) & (bboxes_x2 <= query_max_x)
ValueError: operands could not be broadcast together with shapes (2,) (4952,)

Is this some error in argoverse api or am I using the wrong commnd by :
python eval_forecasting_helper.py --viz --gt trajectory_predict/const_vel_traj_predict.pkl --forecast trajectory_predict/lstm_social_traj.pkl --horizon 30 --obs_len 20 --features features_pre/forecasting_features_test.pkl

Since they did not provide true forecast trajectory for the test set. Therefore, we need to run eval_forecasting_helper.py on validation set only.
Can you tell me how did computed the true trajectory and the predicted trajectory for the validation set.

Hi, have you solved this error?

You can use something as below to generate the ground_truth pkl file from the generated features.
import pandas as pd
import os
import pickle

df = pd.read_pickle("./forecasting_features/forecasting_features_val.pkl")
save_path = "./ground_truth_data"
if not os.path.exists(save_path):
    os.makedirs(save_path)

val_gt = {}
for i in range(len(df)):
    seq_id = df.iloc[i]['SEQUENCE']
    curr_arr = df.iloc[i]['FEATURES'][20:][:, 3:5]
    val_gt[seq_id] = curr_arr

with open(save_path + '/ground_truth_val.pkl', 'wb') as f:
    pickle.dump(val_gt, f)

@abojja9
Thank you!

@abojja9 Super helpful! thanks mate!


I3D Feature

Each video feature dimension：（2048，X）， Whether the feature dimension of each frame extracted is 2048？ or divide the video into X frames, and then extract all the frames with a special frame (2048, X)?
I3D doesn't seem to be able to extract features from a single frame,  so， I want to know how you extract features from a video.  Can you provide code to extract features? Thank you very much!

I used the features provided by MS-TCN.
You can check how they extract features here: https://github.com/yabufarha/ms-tcn/issues/16.
Although you cannot extract I3D features using a single frame, you can utilize neighbor frames.
For example, to extract a feature representing frame n, we can use a video clip with frames [n-7,n+7].


[Feature] a transform to perform file level de-dupe (exact)

Search before asking

[X] I searched the issues and found no similar issues.

Component
Transforms/universal/ededup
Feature
Current process for dedupe is

running pdf2pq
it processes document content and computes document hashes
then we can run ededupe on the computed hashes

This has some drawbacks

we need to process the documents (extract contents, calculate hashes ..etc) before we have document level hash available.  This can be resource intensive for large pdfs / zips  ..etc.  There is no need to spend resources processing duplicate content if we are going to eliminate it soon after

What I propose is

a new transformation (say file-dedupe)
computes file hashes (no processing content)
eliminates duplicate files and only keeps unique files
can work with any file type

Functionality

write a python version first
parameters: input_dir  and output_dir
the transform create unique files in output_dir .  We don't need to copy the files; just symlink or hardlink when available.
The output dir can be then fed to other stages

Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

@touma-I @daw3rd pls add in your comments and suggestions.

@sujee What is file hash ? how is it calculated? Is it based on file name and size and other metadata without consideration for its content ? Or is it treating the file content as just a stream of bytes and calculating the hash ? It is still not clear to me how you get around reading the file to calculate the hash. Can you please elaborate what the file hash formula is ?

hash is based on file content - treating it as bunch of bytes.
So yes, we do need to read the files.
but no need to process them (no pdf2pq ..etc)
something like this
with open(file_path, 'rb') as file:
    sha1_hash = hashlib.sha1()

    chunk_size = 4096  # Adjust this value based on your needs
    while True:
        chunk = file.read(chunk_size)
        if not chunk:
            break

        sha1_hash.update(chunk)

return sha1_hash.hexdigest()

@sujee how would you treat zip and tar files?

@sujee how would you treat zip and tar files?

For first-version, I plan to treat zip/tar files as ONE file.  So if there are duplicate zip/tar files,  dupes will be eliminated.  I won't 'look inside' the archives.
in the next version,  I can add functionality to extract the archive content,  and perform de-dupe on all.


Problem while making react native to run using npx

Description
I am having problem in setting up react native, previously I was using with expo so was not having problem but I needed to use AsyncStorage so I went to use npx instead.
The screenshots of bug are attached

React Native version:
System:
OS: Linux 5.3 Ubuntu 18.04.4 LTS (Bionic Beaver)
CPU: (4) x64 Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
Memory: 168.68 MB / 7.65 GB
Shell: 4.4.20 - /bin/bash
Binaries:
Node: 10.20.1 - /usr/bin/node
Yarn: 1.21.1 - /usr/bin/yarn
npm: 6.14.4 - /usr/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.6 - /usr/bin/javac
Python: 2.7.17 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
so I created new app using
npx react-native init my_app
and then I entered its directory then I ran
npm install
so that it installs its dependencies from file,  then I created this folder
mkdir android/app/src/main/assets
, then I ran
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
then I started android studio and openned the android folder in the app and it updated its gradle probably, then I ran
adb reverse tcp:8081 tcp:8081
finally I ran
npx react-native run-android --port=8081 .
Build was successful, before running the final command I had my emulator on. It does try to show app but it goes on error.
Expected Results
Expected was it to run properly like it used to in expo.
Snack, code example, screenshot, or link to a repository:
The complete code is in the repo
https://github.com/soberservicesguy/bug_containing_app/tree/master/portfolio_app_1_proper

The error looks like your own defined userToken variable in your project. A quick search of it https://github.com/soberservicesguy/bug_containing_app/search?q=userToken&unscoped_q=userToken
This seem like an issue with your setup, could you create a smaller reproducible demo with an issue coming from core? Closing for now as this is not actionable on our end.


Review and Enhance JavaDocs in Storage Blobs

hey @jianghaolu , is this the same as https://github.com/Azure/azure-sdk-for-java/issues/5187?
Can we close this one as duplicated of that one?  or is there something else you would like for this one to be implemented?

The Javadoc comments for Storage Blobs  do not seem to correspond with the SDK. For example,
in BlobContainerAsynClient getBlobAsyncClient(String) it says, but it should refer to the builder.
/**
 * Creates a new BlobAsyncClient object by concatenating blobName to the end of ContainerAsyncClient's URL. The new
 * BlobAsyncClient uses the same request policy pipeline as the ContainerAsyncClient. To change the pipeline, create
 * the BlobAsyncClient and then call its WithPipeline method passing in the desired pipeline object. Or, call this
 * package's getBlobAsyncClient instead of calling this object's getBlobAsyncClient method.
 *
 *
Code Samples

 *
 * {@codesnippet com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient#String}
 *
 * @param blobName A {@code String} representing the name of the blob.
 * @return A new {@link BlobAsyncClient} object which references the blob with the specified name in this container.
 */


Create 0000-01-02-chongkewu.md

created a branch, created a file and made a commit, and opened a pull request


angular 7 support + new features

Hi,
We are currently working on an Angular 7 project and were wondering if there is going to be a release on new features like in the semantic-react repo. The features we are currently using are from ng2-semantic repo, which are great but not enough.
Do you plan on supporting angular? or the framework support is officially abandoned by you?
thanks.

+1

+1

+1

+1

+1

+1


Nadeko does not restrict users from assigning multiple self-roles in group

I'm not sure if this was supposed to be a feature or not, but it would be a nice one.

Didn't see .tesar in command list first time around. Thanks for your help!


worker/server: update metrics on requeue

worker/server: update metrics on requeue
When requeuing a job the next worker requesting the job would decrement
pending counter, but the pending counter only ever got incremented once,
when the job was first enqueued. Thus make sure to increment the pending
counter when a job is requeued.

It's definitely possible to add unit tests, I'll do that.

Sidenote - I think the running_jobs metric also has some problems (causing it to go below 0) so we could see this in the tests if you can implement them 🥳


Added Contributing guidelines

🛠 Fixes Issue #8

👨💻 Changes proposed(required)

Added contribution guidelines for contributors
And also linked the contribution file in readme.md

✔ Check List (Check all the applicable boxes)(required)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Check this on how to fill a pull request template

Check this on how to fill a pull request template

Sure @Dun-sin

@Dun-sin  this link is redirecting me towards some issue but not a guide on how to fill a pull request template

@Dun-sin this link is redirecting me towards some issue but not a guide on how to fill a pull request template

Well when you were filing the pull request, there were some instructions you didn't follow. The link takes you to what you should have done, if you didn't delete the comments in the pull request template.
Trying reading it again

Ohh ya now I got it, I didn't fill the checkboxes as it was mentioned on the top headline, Sorry

Ohh ya now I got it, I didn't fill the checkboxes as it was mentioned on the top headline, Sorry

So, Now what I have to do is just check all the checkboxes right @Dun-sin ?

Ohh ya now I got it, I didn't fill the checkboxes as it was mentioned on the top headline, Sorry

So, Now what I have to do is just check all the checkboxes right @Dun-sin ?

As well as tell the changes proposed

Ohh ya now I got it, I didn't fill the checkboxes as it was mentioned on the top headline, Sorry

Also the changes proposed part, just letting you know for next time

:tada: This PR is included in version 1.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


use .service on ubuntu

The .deb packages should use .service and systemd instead of deprecated upstart.

Even though I know you're right, those debian files were for a previous version and the internally managed debian files aren't really updated anymore as they do not give a good way of handling multiple targets. differences between the support ubuntu *, debian * etc are far to big to keep that internally managed.

Just FYI the external management of those files is at build.opensuse.org at this point


Increased min hole size 0.2mm to use seeed fab.

This PR is identical to this one, put for the DAQ PCB. If you could have a look for any obvious horrible design infractions due to these changes that would be very helpful. Thanks!

Update: we have assembled these PCBs and the work fine.


update readme

closes https://github.com/langchain-ai/langchain-extract/issues/88

@ccurme head to change the cookie to a header api key called x-key due to some issues with cookies


Add characterEncoding and useUnicode to JDBC properties.

I am proposing the addition of these two properties as part of the example because they required in the DW 1.0 app I am currently working on. It is worth noting that the DB is MySQL, so this is potentially only an issue with MySQL implementations. Omitting characterEncoding and useUnicode does not cause anything to fail but it prevents the app from properly enforcing UTF-8. A simple example includes persisting and retrieving the ™ symbol.

Coverage remained the same at 82.296% when pulling 08069ac70ced016a65649a126e0a4226715f69db on sam-berry:patch-1 into 7295c5faf42840325c161cc82ad4ed1db2bf8419 on dropwizard:master.

@sam-berry Do you know if all JDBC implementations support these options or just MySQL?

@jplock I believe that I've confirmed that this is a MySQL specific issue. According to the Hibernate documentation (see the second to last paragraph about arbitrary connection properties), and the MySQL documentation (see "useUnicode and characterEncoding") these properties appear to be MySQL configuration that Hibernate just passes through.
So, this probably isn't appropriate for the DW docs since the example is using Postgres. I've added a StackOverflow Q&A for this that will hopefully find others who are in the same position.

Thanks for digging into this, Sam. Since these properties don't exist and are not needed for Postgres, modifying the docs to reference these properties in a Postgres example will only confuse others, I'm afraid. This PR and stackoverflow should be enough documentation for mysql users. Googling "mysql java unicode" let's users know they have to specify it as a property 😉
Let me know if you have any questions/concerns about closing this PR.


Area appears to have full coverage of ALFRESCO data, but shows missing viz

https://northernclimatereports.org/report/area/19070502#results
The "things not present" block says "Vegetation change: Provided coordinates or area are not included in coverage".
But the area seems to have full coverage from ALFRESCO output, and the flammability map is shown.  Why isn't the veg class chart shown?

Works now, closing!


Docker build failing in master

https://drone.cernbox.cern.ch/cs3org/reva/2700/1/8
This is because the Nextcloud storage driver depends on a file from the tests/ folder, which is excluded by .dockerignore.
I'll think of a fix.

Should be easy to fix, but it's annoying that this wasn't caught by the PR checks.
I think a docker build would have been enough to catch this bug on the PR, testing that hypothesis now.


FOLSPRINGB-115 : Merge code from FST-56 into folio-spring-support

Purpose
FOLSPRINGB-115 : Merge code from FST-56 into folio-spring-support
Approach
Change login endpoint to /login-with-expiry
Add tokens expiration checks
TODOS and Open Questions

[x] Use GitHub checklists. When solved, check the box and explain the answer.

Learning
Permission update not needed because login endpoints doesn't require one.

I see that new submodule is named "folio-token", but it contains a lot of staff related to system user, so I'd suggest a name like "folio-system-user".
Maybe others have some better suggestions for a name.

I see that new submodule is named "folio-token", but it contains a lot of staff related to system user, so I'd suggest a name like "folio-system-user". Maybe others have some better suggestions for a name.

I agree with @viacheslavkol, that there is more then just token logic. system-user is good option for me. But also I suggest to follow the same pattern for module naming as we already have. Not just folio- but folio-spring-

I see that new submodule is named "folio-token", but it contains a lot of staff related to system user, so I'd suggest a name like "folio-system-user". Maybe others have some better suggestions for a name.

I agree with @viacheslavkol, that there is more then just token logic. system-user is good option for me. But also I suggest to follow the same pattern for module naming as we already have. Not just folio- but folio-spring-

@psmagin we have focused on the login part and not the part that creates the system user. I'm fine with renaming the module to folio-system-user but this leads me to another question.
Do we want to create another public method in SystemUserService that takes 3 parameters, a tenantId, a username and a password? Then modules could decide wether they wanted to take advantage of the system user creation or not. Each module we're integrating with has its own ideas of where to store the credentials and perms. I'm not saying that's a good thing. In fact I would argue that standardizing how we configure these system users the way you have done is a very good thing so maybe that should be in scope for spring modules that want to take advantage of this library.

I see that new submodule is named "folio-token", but it contains a lot of staff related to system user, so I'd suggest a name like "folio-system-user". Maybe others have some better suggestions for a name.

I agree with @viacheslavkol, that there is more then just token logic. system-user is good option for me. But also I suggest to follow the same pattern for module naming as we already have. Not just folio- but folio-spring-

@psmagin we have focused on the login part and not the part that creates the system user. I'm fine with renaming the module to folio-system-user but this leads me to another question.
Do we want to create another public method in SystemUserService that takes 3 parameters, a tenantId, a username and a password? Then modules could decide wether they wanted to take advantage of the system user creation or not. Each module we're integrating with has its own ideas of where to store the credentials and perms. I'm not saying that's a good thing. In fact I would argue that standardizing how we configure these system users the way you have done is a very good thing so maybe that should be in scope for spring modules that want to take advantage of this library.

If in this PR was just the login part, then we will not have questions about naming.
And I think it's okay to have such method

I can't approve the PR until

the module renamed to the suggested name above
README file updated with how to use this new module

@nirmalr-shah and @psmagin - These changes are fine with me.

@psmagin & @steveellis , the module is renamed and README.md file is added.
Please re-review it and provide your approval.


Config differ improvements, Fixes #380, Fixes #381, Fixes #392

Fixes "Accept Remote" button in popup
Admin config differ requires added "/api" URL in a deployed app
Improved JSON diffing
Triggers a reload of underlying config panel on apply remote

Didn't run locally yet to test it out but thank you for getting this in - reading through the code looks good with the one comment above.  Will be great to have this merged shortly.

This is a great set of improvements.
We can (and will) continue to refine how we generate paths.


Print 'None' on PDFs for Employment information if no information is …

…given #312
Added a or_xxx suffix that if the field has no value it prints "xxx"
It will also convert any other '' after the or to ' '.

Extra thanks for all the test cases!


Install Error on OS X (python) using pip

On OS X 10.10, XCode 7.1 installed, python 2.7 and which pip gives:
/Library/Frameworks/Python.framework/Versions/2.7/bin/pip
First tried pip install feather-format and received:
ImportError: No module named Cython.Distutils
So I pip install cython which installed cython-0.24 and tried pip install feather-format again and received the following:
Collecting feather-format
  Using cached feather-format-0.1.2.tar.gz
Requirement already satisfied (use --upgrade to upgrade): cython>=0.21 in /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages (from feather-format)
Installing collected packages: feather-format
  Running setup.py install for feather-format ... error
    Complete output from command /Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python -u -c "import setuptools, tokenize;__file__='/private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-ZIpHT9-record/install-record.txt --single-version-externally-managed --compile:
    running install
    running build
    running build_py
    creating build
    creating build/lib.macosx-10.6-intel-2.7
    creating build/lib.macosx-10.6-intel-2.7/feather
    copying feather/__init__.py -> build/lib.macosx-10.6-intel-2.7/feather
    copying feather/api.py -> build/lib.macosx-10.6-intel-2.7/feather
    copying feather/compat.py -> build/lib.macosx-10.6-intel-2.7/feather
    copying feather/version.py -> build/lib.macosx-10.6-intel-2.7/feather
    creating build/lib.macosx-10.6-intel-2.7/feather/tests
    copying feather/tests/__init__.py -> build/lib.macosx-10.6-intel-2.7/feather/tests
    copying feather/tests/test_reader.py -> build/lib.macosx-10.6-intel-2.7/feather/tests
    copying feather/libfeather.pxd -> build/lib.macosx-10.6-intel-2.7/feather
    copying feather/ext.pyx -> build/lib.macosx-10.6-intel-2.7/feather
    running build_ext
    building 'feather.ext' extension
    creating build/temp.macosx-10.6-intel-2.7
    creating build/temp.macosx-10.6-intel-2.7/feather
    creating build/temp.macosx-10.6-intel-2.7/src
    creating build/temp.macosx-10.6-intel-2.7/src/feather
    /usr/bin/clang -fno-strict-aliasing -fno-common -dynamic -arch i386 -arch x86_64 -g -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -Ifeather -I/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/numpy/core/include -I/private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/src -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c feather/ext.cpp -o build/temp.macosx-10.6-intel-2.7/feather/ext.o -std=c++11 -O3
    In file included from feather/ext.cpp:307:
    In file included from /private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/src/feather/api.h:18:
    /private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/src/feather/buffer.h:19:10: fatal error: 'cstdint' file not found
    #include <cstdint>
             ^
    1 error generated.
    error: command '/usr/bin/clang' failed with exit status 1

    ----------------------------------------
Command "/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python -u -c "import setuptools, tokenize;__file__='/private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-ZIpHT9-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/nm/c61gq67x5qn3251k3k4hsf880000gp/T/pip-build-dyChKd/feather-format/

Any help is much appreciated. Thanks!

I was running into this as well. Even started modifying headers in the source to get it to compile. Then I RTFM'd and found under Mac Notes (https://github.com/wesm/feather/tree/master/python):
export MACOSX_DEPLOYMENT_TARGET=10.10
The installation was successful after that.


Jupyter kernel not restarting

VS Code version: 1.76.2
Jupyter Extension version: v2023.2.1200692131
Python Extension version: v2023.4.1
OS and version: Mac Ventura 13.1 (Apple M1 Max)
Python version: 3.10.5
Type of virtual environment used: conda virtual environment
Jupyter server running: Local

Expected behaviour
When pressing the button restart, the kernel should restart.
Actual behaviour
The kernel fails to restart (roughly 1 in 3 times) and the following pop up window keeps loading.

I can solve the issue by closing the whole window (not just the script that generated the issue) e restarting everything from zero.
Steps to reproduce:
Restart the kernel enough times. Sooner or later it will generate the behavior.

thanks for filling this issue and sorry you are running into this issue
It looks like the kernel is crashing at your end
i suspect you would run into this same issue with classic Jupyter notebooks outside vscode as well
Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

No I do not run into the same issue with the classic jupyter notebook. I turned on the logging and this is what I see:

To get to the Jupyter panel please go into the command palette and use the command ‘Jupyter: Show Output’

Here is the output:
debug 14:48:07.996: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a with 1 output(s)
debug 14:48:07.997: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a with 1 output(s)
debug 14:48:07.998: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a with 1 output(s)
debug 14:48:08.000: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a with 1 output(s)
debug 14:48:08.000: Executing silently Code (completed) = def _VSCODE_getVariable(what_to_get, is_debugging, *args):\n# Query Jupyter server for the info a with 1 output(s)
debug 14:48:08.182: shutdownSession 66956a70-5f5b-48a1-b4e1-63f899c762fc, .envml./Users/nicoloceneda/miniforge3/envs/envML/python./Users/nicoloceneda/miniforge3/envs/envML/python.-m#ipykernel_launcher - shutdown complete
debug 14:48:21.422: Interrupt kernel command handler for /Users/nicoloceneda/Dropbox/Bhamra-Ceneda/research/recovery rates/code/results_card_1.ipynb

The kernel gets stuck roughly 60% of the times I try to restart it.

Permanently stuck in this state:

I calculated: 7 out of 10 times that I have run all cells or restarted the kernel, the kernel has stopped working, requiring to close and re-open the application.

@nicoloceneda

Please could you copy ALL of the output and share that, without the logs its almost impossible to help here.
Are you running into this with all environments? Can you try creating a new environment and see whether the issue replicates there too.
Optionally, please could you try the following (downgrade some packages as described in the comments) https://github.com/microsoft/vscode-jupyter/issues/12775#issuecomment-1447175314

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.


drivers: ethernet: renesas: Support Renesas RA8 Ethernet driver

This PR is to support Ethernet driver for the Renesas RA8 boards
The driver design is based on the using Ethernet and Ethernet PHY FSP driver from hal_renesas to implement.

@decsny , could you help to recheck this PR

@soburi It's in good shape. Please take a look.


Android Build failure with v2.0.4

@hiennguyen92 Build failing with the latest version. Tried invalidating cache and flutter pub cache clean but this keeps popping. Had to revert to v2.0.3.
Running Gradle task 'assembleDebug'...
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:401:31 Unresolved reference: CallkitIncomingActivity
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:479:33 Unresolved reference: TransparentActivity
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:488:29 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:493:29 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:498:33 Unresolved reference: TransparentActivity
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/CallkitNotificationManager.kt:507:22 Unresolved reference: CallkitIncomingActivity
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:98:17 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:111:17 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:120:17 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:131:21 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:154:29 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:180:29 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:220:29 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:238:37 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:245:37 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:266:21 Unresolved reference: CallkitIncomingBroadcastReceiver
e: file:///Users/sagar/.pub-cache/hosted/pub.dev/flutter_callkit_incoming-2.0.4/android/src/main/kotlin/com/hiennv/flutter_callkit_incoming/FlutterCallkitIncomingPlugin.kt:266:54 Variable expected

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':flutter_callkit_incoming:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3m 38s
Error: Gradle task assembleDebug failed with exit code 1

Same here, Any solution guys?

@hiennguyen92 any update on this ??

@sagar1garg @KamalPixi
I run flutter clean and then flutter pub get, and the app can be built successfully.
Please try if this works for you.

@TinhHuynh it worked thanks. If you can let us know about your plans for locked screen callbacks it will be really helpful

@sagar1garg
Hi, I am not the library maintainer :)


[NEXT]Feat: guide

@raisedadead don't worry, I am going to squash commits where I am debugging the build 😆

Pushing to next to enable circleCI