[HOLD for payment 2023-09-27] [$1000] mweb: Green background colour visible when scrolling on the Preference Page

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

Action Performed:
1 Open app
2 Go to Settings > Preference
3 Make a scroll
Expected Result:
When scrolling the colour remains Blue
Actual Result:
Some parts of the screen remain light green.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.44-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/20463c39-0137-46d1-aa12-37277dee6826
https://github.com/Expensify/App/assets/43996225/12dfc816-f6e0-4be9-9343-fa7c16a80e5d
Expensify/Expensify Issue URL:
Issue reported by: @narzullome
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690019575694929
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0135c9358446287985
Upwork Job ID:<PHONE_NUMBER>520570880
Last Price Increase: 2023-09-05
Automatic offers:

0xmiroslav | Reviewer | 26515161
ginsuma | Contributor | 26515162
narzullome | Reporter | 26515167
ishpaul777 | Contributor | 26515517

Proposal
Please re-state the problem that we are trying to solve in this issue.
mweb: Green background colour visible when scrolling on the Preference Page
What is the root cause of that problem?
the background color themeColors.appBG is set for whole view above scrollview not for the view wrap children
https://github.com/Expensify/App/blob/cd851d0fbd901c70a32220472104ffc887639f2a/src/components/IllustratedHeaderPageLayout.js#L42
What changes do you think we should make in order to solve the problem?
remove background color themeColors.appBG from here
https://github.com/Expensify/App/blob/cd851d0fbd901c70a32220472104ffc887639f2a/src/components/IllustratedHeaderPageLayout.js#L42
and add it here  , StyleUtils.getBackgroundColorStyle(themeColors.appBG) for view wrap children here
https://github.com/Expensify/App/blob/cd851d0fbd901c70a32220472104ffc887639f2a/src/components/IllustratedHeaderPageLayout.js#L56
What alternative solutions did you explore? (Optional)

Bug report looks good!

I added their name to the proposal title so it's easy to recognize who the proposal is from - do you think there is an easier way to show that we should have done?

@0xmiroslav - when you get a chance, can you review @ginsuma's proposal?

Hi @0xmiroslav  - this seems as it would be a straight forward fix, can you review this proposal?

@slafortune  HI the same issue on the Workspace screen

#Proposal
Please re-state the problem that we are trying to solve in this issue.
Non-matching background color on IllustratedHeaderPageLayout pages
##What is the root cause of that problem?
The present view component is not placed correctly. It should be placed above the ScrollView.
##What changes do you think we should make in order to solve the problem?

The view should be made one level above here. This is incorrectly set presently.
We can add background colors to the children's content of the page as well as the FixedFooter component
The top can be made as 0 and zIndex as a negative constant because the view should be present behind the ScrollView.

overscrollSpacer: (backgroundColor, height) => ({         backgroundColor,         height,         width: '100%',         position: 'absolute',         top: 0,         zIndex: -height,         left: 0,         right: 0,     }),
After these changes, the views will look like this:
https://github.com/Expensify/App/assets/98523623/cd3ca396-3383-42d6-92fb-92dcea766862
The android and chrome are not affected by this because iOS and Safari native views only support the bouncing effect on overscroll.

Proposal
Please re-state the problem that we are trying to solve in this issue.
on Safari - Green background colour visible when scrolling on the Preference Page and
What is the root cause of that problem?
The overscroller background overlay is not placed properly
What changes do you think we should make in order to solve the problem?
we need to put the overscrollSpacer out of ScrollView component and modify the styles.
<View style={[styles.flex1,]}>
    <View style={styles.overscrollSpacer(backgroundColor, windowHeight)}>
        <View style={[styles.flex1, StyleUtils.getBackgroundColorStyle(backgroundColor)]}/>
        <View style={[styles.flex1, StyleUtils.getBackgroundColorStyle(themeColors.appBG)]}/>
    </View>
    <ScrollView
        contentContainerStyle={safeAreaPaddingBottomStyle}
        showsVerticalScrollIndicator={false}
    >
        <View style={[styles.alignItemsCenter, styles.justifyContentEnd, StyleUtils.getBackgroundColorStyle(backgroundColor)]}>
            <Lottie
                source={illustration}
                style={styles.w100}
                autoPlay
                loop
            />
        </View>
        <View style={[styles.pt5, StyleUtils.getBackgroundColorStyle(themeColors.appBG)]}>{children}</View>
    </ScrollView>
    {!_.isNull(footer) && <FixedFooter style={[StyleUtils.getBackgroundColorStyle(themeColors.appBG)]}>{footer}</FixedFooter>}
</View>

and we need to modify overscrollSpacer flexbox with direction column. and make sure it is below the actual content by setting appropriate index value.
I will add results soon...

@0xmiroslav do you have thoughts on these proposals?

@0xmiroslav Yes, I agree.  I hadn't realized this was iOS natural behavior.

Yeah, I was aware of this and tried to fix it at the time, but ultimately I thought that it was a safari bug – the color of the native overscroll bounce area is supposed to be controlled by meta[name=theme-color] attribute, but found an iOS Safari bug where that attribute updates the status bar color but not the overscroll color.
I later discovered the same bug on iOS native and that's when I implemented the overscroll spacer to fix it.
Anyways, if the solution is as simple as moving the overscroll spacer up out of the ScrollView, then I'm all for it 👍🏼

Issue not reproducible during KI retests. (First week)

@0xmiroslav are you able to reproduce this, or shall we close it?

@slafortune It is reproducible on iOS, Safari.

I'm not able to reproduce at all - On iOS app I can pull down and the blue stays nice - in iOS Safari it doesn't pull down at all and leaves no space
https://github.com/Expensify/App/assets/11725910/b2c1b00c-ab55-4eb2-a215-23b09afb31e7

Ah!  Thanks for that @0xmiroslav  - I see it now!

Hello @slafortune What are your thoughts on my proposal here

I'll defer to @0xmiroslav and @roryabraham for proposal reviews and selection 👍

@0xmiroslav @roryabraham What are your views on my proposal?

@0xmiroslav I did tried that solution, but it didn't worked for me.

@ginsuma It works on Mac/Safari too right?

i tried adding willChange: "transform" sometimes it does not work as expected and requires a reload to work as expected
https://github.com/Expensify/App/assets/104348397/23acd254-332a-47ec-8894-d9bfc8886655

Steps to repro:

reload app while on other screen (without illustration)
navigate to preferences/workspaces.
Scroll up or down as soon as you can.(if wait more than 2-3 seconds, then works as expected).

@0xmiroslav is there a proposal we can move forward with?

Sorry for the delay, fortunately this isn't a very high-priority issue so not a big deal!

Oh, sorry I had missed this comment

Seems like all the solutions that just move the overscroll spacer up in the view hierarchy create the same issue on the bottom, as shown in the videos from this comment

we can play with onScroll Prop on ScrollView to dynamically set the background color. (this may result in performance regression)

Tried this, and it was janky

While not perfect, it seems like @ishpaul777's proposal might be the best we can do. In practice you're right that you'd have to be intentionally over-scrolling with two fingers in order to actually see this bug with this change, so I suppose that's better than what we have now.
I do think it's essentially a safari bug, but since that's out-of-scope for us to worry about fixing I suppose a workaround is the best we can do in this case.

Hello @roryabraham,
I guess both proposals are exactly the same with just a change in height of the background. I am still fine with your review, but just wanted to check with you, if you are aware of this.

@0xmiroslav @roryabraham PR up for review

@0xmiroslav are you able to get to this review?
Reassigning a BZ member, I am out on sabbatical

PR reviewed and approved but intentionally not merged right now, see this comment

waiting on merge

@roryabraham would a bonus be added here based on the PR being intentionally not merged?

@0xmiroslav can you complete the checklist above?

PAYMENTS TO BE MADE:

@narzullome (Reporter) [$250] (reported before price change)

@ishpaul777 (Contributor) [$1000 + 50% bonus]

@0xmiroslav (Reviewer) [$1000 + 50% bonus]

@ishpaul777 payment sent and contract ended - thank you! 🎉
@narzullome I've sent you the $250 reporting payout offer, once accepted I can initiate payment - thanks!

Payment received! Thank you 🎉

@abekkala Offer accepted

waiting on payment for
@0xmiroslav (Reviewer) [$1000 + 50% bonus]
on hold until we determine how payments are to be made

@0xmiroslav are you ready to accept payments via Upwork yet?


Include IP in extra on IpDeniedError

This would be useful when reformatting or filtering errors, or for collecting metrics, by being able to see the denied error in our express error handler as error.extra.ip rather than having to substring it out from the error message

+1


Cut v1.3.0-beta.0

This is a breaking change to the Kubernetes service discovery. This is ok as the Kubernetes SD is in beta status. It requires a configuration change. See prometheus/docs#601 for documentation on the configuration.
@brian-brazil @fabxc @juliusv @grobie @beorn7

I guess we'll wait for https://github.com/prometheus/prometheus/pull/2078#issuecomment-254539237

Yes.
Otherwise, this looks good to me.

Fix is in . Since this is only a beta version, let's go with that.
Perhaps rebase this on top of the fix to avoid confusion.
:+1:

Can we get #2096 in also as it's a bugfix?

Yes, please.
Feel free to merge #2096 .

Will rebase tomorrow, then we'll do the release :)

Rebased and updated the changelog. PTAL @beorn7 @brian-brazil @fabxc

👍

:+1:


  If so a full clean and rebuild might fix it...

Closing this as it's not a bug.  If you want help please hit up the gitter channel.


Chaining semantic actions

Chaining semantic actions such as in ["0-9"]+ > to_string >  to_integer should be possible.

Closing this issue. I don't think it is such a good idea anymore, if two semantic actions are needed, just combine them in a single one...


blosc/bloscpack dependency

Hello,
I was trying to install bloscpack and noticed that setup.py has the following lines...
install_requires = [
    'blosc==1.2.7',
    'numpy',
    'six',
]

However, blosc appears to currently be at version 1.2.9dev0. Using pip/conda I wasn't able to install it either.
Is it safe to just edit the requirements to be blosc>=1.2.7?

You may try this at your own risk. Last time I tried a blosc > 1.2.7 many of the unit and or system tests were failing. However, these are very very picky at times since they check exact binary output and compression ratios -- so you may get away with using 1.2.9. It's hard to say for sure. 1.2.7 is likely to result in a fully passing test-suite. Let me know if 1.2.9 works for you.
On 29 March 2016 16:19:39 CEST, Peter Quackenbush<EMAIL_ADDRESS>wrote:

Hello,
I was trying to install bloscpack and noticed that setup.py has the
following lines...
install_requires = [
   'blosc==1.2.7',
   'numpy',
   'six',
]

However, blosc appears to currently be at version 1.2.9dev0. Using
pip/conda I wasn't able to install it either.
Is it safe to just edit the requirements to be blosc>=1.2.7?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Blosc/bloscpack/issues/46

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Right. I guess the problem is that I am unable to install blosc==1.2.7 on my Windows computer
I have Anaconda 2.5 (Python 3.5.1) with Visual Studio community edition. I can compile and install 1.2.8 (or 1.2.9dev0 from github) with no problems. With 1.2.7, pip install blosc==1.2.7 gives me all this nastiness....
Both 1.2.8 and 1.2.9dev0 seem to work just fine. (I'm using these while playing with castra).
uild\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\inflate.obj
 build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\inftrees.
obj build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\trees.
obj build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\uncomp
r.obj build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\zuti
l.obj /OUT:build\lib.win-amd64-3.5\blosc\blosc_extension.cp35-win_amd64.pyd /IMP
LIB:build\temp.win-amd64-3.5\Release\blosc\blosc_extension.cp35-win_amd64.lib
    blosc_extension.obj : warning LNK4197: export 'PyInit_blosc_extension' speci
fied multiple times; using first specification
       Creating library build\temp.win-amd64-3.5\Release\blosc\blosc_extension.c
p35-win_amd64.lib and object build\temp.win-amd64-3.5\Release\blosc\blosc_extens
ion.cp35-win_amd64.exp
    shuffle.obj : error LNK2001: unresolved external symbol blosc_get_cpu_featur
es
    build\lib.win-amd64-3.5\blosc\blosc_extension.cp35-win_amd64.pyd : fatal err
or LNK1120: 1 unresolved externals
    error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\B
IN\\amd64\\link.exe' failed with exit status 1120

    ----------------------------------------
Command "C:\Anaconda3\python.exe -u -c "import setuptools, tokenize;__file__='C:
\\Users\\PQUACK~1\\AppData\\Local\\Temp\\pip-build-7u774njl\\blosc\\setup.py';ex
ec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'
), __file__, 'exec'))" install --record C:\Users\QUACK~1\AppData\Local\Temp\pip
-rbdprlu1-record\install-record.txt --single-version-externally-managed --compil
e" failed with error code 1 in C:\Users\QUACK~1\AppData\Local\Temp\pip-build-7u
774njl\blosc\

[Anaconda3] C:\Users\pquackenbush\git>

Thanks for reporting. I suggest you open a ticket for this with the python-blosc project. As for installing bloscpack, feel free to clone the source code, remove the lines regarding the dependency and installing it. It should be fine if you just want to play around.
On 29 March 2016 23:01:49 CEST, Peter Quackenbush<EMAIL_ADDRESS>wrote:

Right. I guess the problem is that I am unable to install blosc==1.2.7
on my Windows computer
I have Anaconda 2.5 (Python 3.5.1) with Visual Studio community
edition. I can compile and install 1.2.8 (or 1.2.9dev0 from github)
with no problems. With 1.2.7, pip install blosc==1.2.7 gives me all
this nastiness....
Both 1.2.8 and 1.2.9dev0 seem to work just fine. (I'm using these while
playing with castra).
uild\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\inflate.obj
build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\inftrees.
obj
build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\trees.
obj
build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\uncomp
r.obj
build\temp.win-amd64-3.5\Release\c-blosc/internal-complibs\zlib-1.2.8\zuti
l.obj
/OUT:build\lib.win-amd64-3.5\blosc\blosc_extension.cp35-win_amd64.pyd
/IMP
LIB:build\temp.win-amd64-3.5\Release\blosc\blosc_extension.cp35-win_amd64.lib
blosc_extension.obj : warning LNK4197: export 'PyInit_blosc_extension'
speci
fied multiple times; using first specification
Creating library
build\temp.win-amd64-3.5\Release\blosc\blosc_extension.c
p35-win_amd64.lib and object
build\temp.win-amd64-3.5\Release\blosc\blosc_extens
ion.cp35-win_amd64.exp
shuffle.obj : error LNK2001: unresolved external symbol
blosc_get_cpu_featur
es
build\lib.win-amd64-3.5\blosc\blosc_extension.cp35-win_amd64.pyd :
fatal err
or LNK1120: 1 unresolved externals
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio
14.0\\VC\\B
IN\\amd64\\link.exe' failed with exit status 1120

   ----------------------------------------
Command "C:\Anaconda3\python.exe -u -c "import setuptools,
tokenize;__file__='C:
\\Users\\PQUACK~1\\AppData\\Local\\Temp\\pip-build-7u774njl\\blosc\\setup.py';ex
ec(compile(getattr(tokenize, 'open',
open)(__file__).read().replace('\r\n', '\n'
), __file__, 'exec'))" install --record
C:\Users\QUACK~1\AppData\Local\Temp\pip
-rbdprlu1-record\install-record.txt --single-version-externally-managed
--compil
e" failed with error code 1 in
C:\Users\QUACK~1\AppData\Local\Temp\pip-build-7u
774njl\blosc\

[Anaconda3] C:\Users\pquackenbush\git>

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/Blosc/bloscpack/issues/46#issuecomment-203101977

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@thequackdaddy will close this, feel free to re-open if you have further quetsions.

@esc Thank you. I forgot to open ticket with them. Thanks for reminder!

FWIW this was resolved with bloscpack 0.11


plain_word_vector.py

where can I find this file: ./spacy-dev-resources/training/plain_word_vector.py

https://github.com/explosion/spacy-dev-resources/blob/master/training/plain_word_freqs.py


[Removal]: Funny Concrete Guppy

Hotspot Name
Funny Concrete Guppy
Hotspot b58 Address
1196WdQA1r1EAQ1jr84oyfWbWxNE5Sja89wfo4tmzenKdsRTh8Q
Discord Handle
No response
Hotspot Manufacturer
Bobcat
Removal Reason
-Reason for Demolition: the SM I actually deployed on the balcony was replaced by an online merchant due to the unstable network. If the error is blacklisted for this reason, please help me correct it. Thank you.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information

The problem I fed back is the field deployment. I would like to ask the official how to deal with it. I hope to remove the blacklist as soon as possible. thank you!

We have taken into account this removal request in the next iteration of the denylist. It may take some time before it's processed. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


[live] <= [master] removing CTOs who aren't part of advocacy anymore. cleaning up images

Docs Build status updates of commit 68da0dd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/index.html.yml
:warning:Warning
View
Details

advocates/andrew-harvey.yml
:white_check_mark:Succeeded

advocates/duncan-davidson.yml
:white_check_mark:Succeeded

advocates/lims-wang.yml
:white_check_mark:Succeeded

advocates/map.yml
:white_check_mark:Succeeded
View

advocates/media/profiles/andrew-harvey.png
:white_check_mark:Succeeded

advocates/media/profiles/davis-joseph.png
:white_check_mark:Succeeded

advocates/media/profiles/duncan-davidson.png
:white_check_mark:Succeeded

advocates/media/profiles/gustavo-cordido.jpeg
:white_check_mark:Succeeded

advocates/media/profiles/lims-wang.jpg
:white_check_mark:Succeeded

advocates/media/profiles/munipuli.png
:white_check_mark:Succeeded

advocates/media/profiles/nina-zakharenko.jpg
:white_check_mark:Succeeded

advocates/media/profiles/penina-weiss.png
:white_check_mark:Succeeded

advocates/media/profiles/rong-yu.png
:white_check_mark:Succeeded

advocates/muniraju-pulipalyam.yml
:white_check_mark:Succeeded

advocates/penina-weiss.yml
:white_check_mark:Succeeded

advocates/rong-yu.yml
:white_check_mark:Succeeded

advocates/toc.yml
:white_check_mark:Succeeded
View

advocates/index.html.yml

Line 10, Column 8: [Warning-file-not-found] Invalid file link: './map'.
Line 12, Column 8: [Warning-file-not-found] Invalid file link: './tweets'.

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


Help Wanted: Make team creation workflow easier

Context
The option to create a new Mattermost team isn't always easy to find, and updating the product documentation can help make this feature more discoverable.
Documentation Asks
Source file: collaborate/organize-using-teams.rst
Within the Create a team section, capture 2 new animated GIFs:

GIF 1: Show how to select + and select Create a New Team (GIF doesn't need to show the rest of the team creation flow). Add this image directly below the second paragraph on the page and before the 3rd paragraph.
GIF 2: Show how to select the team name and then select Create a Team. Add this image to the Tip near the top of the page.

In both cases, use existing code on the page as a guide for adding images to this documentation page.

@cwarnermm I would like to work on this. Please assign this to me. Thanks.

Thanks, @Rutam21!!


Add data validity checks after converting data.

Is your feature request related to a problem? Please describe.
Issue #30 showed that additional sanity and validity checks are required.
Describe the solution you'd like
The data should be evaluated for validity. Especially constraints, such as "exactly one ego vehicle is present" should be checked before running the analysis.

Related to #70


Split Cells Limit bypass

I just found a new bug, and I am very very happy .
After you split cells into the limit, then the cells start getting together, you press startbar a lot of times very fast, just before they get together, and they will split again, bypassing the cell limit configuration value .

Due another bug, If player split like that, its impossible to eating him .


Pipeline aggs

closes #1965 .
tried to reduce csproj file changes showing plenty additions and deletions but to no avail.

LGTM.  Thanks for taking this on @jonyadamit, very much appreciated!

With pleasure, you guys rock :sunglasses:

Thanks @jonyadamit as do you! wasn't expecting this PR so rapidly :boom:
I manually merged this in 2,x and master mainly to squash, reformat the changes and adding sigma to extendedstatsbucket
If you install https://visualstudiogallery.msdn.microsoft.com/c8bccfe2-650c-4b42-bc5c-845e21f96328 you'll always commit with our formatting :wink:


v3.24 server

which server should i use.
all the servers i tried are broken or the inventory is full of pvp error. server pls compatible with sql (v3.24)

this is only site bro
you can find your own server in another repo


Check for process object

Fixes #78
It also includes #76 and #77 so please pull those before pulling this and this pull request should automatically be updated to only show the one relevant commit.

Can you base your PRs on master to be able to merge them independently?

If you pull them in order you will be able to merge them independently.
Unfortunately all three have conflicts which is way I opted to do it like this.

Actually, don't pull this one yet! I think that there is a problem we haven't counted with... I think that browserify shims process as a global object and since we are building with that it might not work as intended...
Whatever the reason, the tests fails in the browser for this one, so just hold on for a bit.

Of course I can pull them in order but it defeat the goal of having separate PRs.
The browserify test also fails in master, I have to figure out why.

And I do not think it is a problem that browserify shims process, it won't cause any errors.

You are right, I tested in Safari instead of Chrome :facepunch: :dizzy_face:
The tests passes.
The browserify test won't work until a bug in browserify is resolved, see #66
I understand that it defeats the pull request but if I had did it the other way, then whenever you merged one, the other one would have changed to "unable to automatically merge" because of merge conflicts. So I opted to enforce the order in which they are merged, I hope it's okay :)

Rebased on master

Done and done :+1:


consider renaming the primary branch

following github's default policy and its reasoning, we should consider renaming our primary branch, currently master, to something else, such as main.

👍  main sounds good

[ ] create branch
[ ] update gh settings
[ ] update CI (if necessary)


spacing of \colon

Using the current demo https://mathjax.github.io/mj3-demos/mj3-tex2html-global.html with Firefox/Linux and input \begin{align}x \colon y \to z \\ x : y\to z \end{align} results in:

where in the first line the colon should be closer to the x than to the y like in LaTeX:

or MathJax on math.stackexchange:

see https://tex.stackexchange.com/questions/37789 for further discussion of the difference.

Thanks for the bug report.
@Volker, the \colon macro is supposed to set the tex class to PUNCT, but it does seem to be.  Can you check into this?

Corrected to @zorkow. I'll have a look.


Unneeded dependencies pulled in for dependencies withbrowser property

public-ip has a browser property in package.json which points to browser.js, which currently only includes the is-ip dependency. browserifying that give a lightweight package:
$ browserify browser.js | wc -c
    3355

But if one creates another project that depends on the public-ip package, the got dependency which is not actually used in browser.js (only in index.js) is needlessly included:
$ browserify my-project.js | wc -c
  287709

There is no file browser.js in public-ip:
$ npm i public-ip
$ ls node_modules/public-ip/
index.js  license  package.json  readme.md

I think this file is not found so browserify falls back to using the index.js. This is because package.json includes a "files" property that excludes browser.js:
$ json files < node_modules/public-ip/package.json
[
  "index.js"
]

The "files" property in package.json is not something that I use for this reason, but it seems like browserify is behaving as it should here.


feat: replaceRec

Add a more flexible version of Expr.replace

Requires #237

Ok I think that fixes everything


Demonstration Url

can u provide a online demo?

Its on the roadmap. When I get a server to host it it will be up.
There is not much to show at the moment. However the installation is done already so feel free to test it

ok. i will run in my computer...


smorfam link to Sberro et al. 2019

The "smorfam" column of the output tsv file contains names like "smorfam00946"
How do these families compare to the data in Sberro et al. 2019? Looking at Table S3 from that paper, the first column contains a "family ID" that does not map to the smORFfinder output.
It's also not just the integer order, since the length of the sequences in Table S3 and the hmm file are different.

Hi Ben. There's no direct mapping between them. It's just for your own reference, and can be used to look up families on DBSmORF. I'd recommend searching the Sberro et al. sequences using the HMMs if you'd like to map them to each other.


How can I run the same experimental results？

I fixed the random seeds and set the deterministic to True and still could not get the same result.
After my troubleshooting I found that the input and output of the first batch were the same, but from the second batch onwards the output changed.

I am not sure.

but from the second batch onwards the output changed
Does the input data change from the second batch?

The operations in cpp extensions also brings randomness.


How to configure client for azure

When deployed to Azure app service the client disconnects after a period of idleness.
I saw something that need to keepsockeralive but it is read only in your code and i cant seem to find a way to get it to work on azure.
Anyone know how to configure this?
I have tried in code to connect again of it has disconnected but it just throws and error again.
Neo4j.Driver.ServiceUnavailableException: Failed after retried for 2 times in 30000 ms. Make sure that your database is online and retry again.
---> System.AggregateException: One or more errors occurred. (Failed to connect to any routing server. Please make sure that the cluster is up and can be accessed by the driver and retry.) (Failed to connect to any routing server. Please make sure that the cluster is up and can be accessed by the driver and retry.)
---> Neo4j.Driver.ServiceUnavailableException: Failed to connect to any routing server. Please make sure that the cluster is up and can be accessed by the driver and retry.
at Neo4j.Driver.Internal.Routing.RoutingTableManager.UpdateRoutingTableAsync(AccessMode mode, String database, Bookmark bookmark)
at Neo4j.Driver.Internal.Routing.RoutingTableManager.EnsureRoutingTableForModeAsync(AccessMode mode, String database, Bookmark bookmark)
at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireConnectionAsync(AccessMode mode, String database, Bookmark bookmark)
at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireAsync(AccessMode mode, String database, Bookmark bookmark)
at Neo4j.Driver.Internal.AsyncSession.BeginTransactionWithoutLoggingAsync(AccessMode mode, Action1 action, Boolean disposeUnconsumedSessionResult)    at Neo4j.Driver.Internal.AsyncSession.<>c__DisplayClass37_01.<b__1>d.MoveNext()
--- End of stack trace from previous location ---
at Neo4j.Driver.Internal.AsyncRetryLogic.RetryAsync[T](Func1 runTxAsyncFunc)    --- End of inner exception stack trace ---  ---> (Inner Exception #1) Neo4j.Driver.ServiceUnavailableException: Failed to connect to any routing server. Please make sure that the cluster is up and can be accessed by the driver and retry.    at Neo4j.Driver.Internal.Routing.RoutingTableManager.UpdateRoutingTableAsync(AccessMode mode, String database, Bookmark bookmark)    at Neo4j.Driver.Internal.Routing.RoutingTableManager.EnsureRoutingTableForModeAsync(AccessMode mode, String database, Bookmark bookmark)    at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireConnectionAsync(AccessMode mode, String database, Bookmark bookmark)    at Neo4j.Driver.Internal.Routing.LoadBalancer.AcquireAsync(AccessMode mode, String database, Bookmark bookmark)    at Neo4j.Driver.Internal.AsyncSession.BeginTransactionWithoutLoggingAsync(AccessMode mode, Action1 action, Boolean disposeUnconsumedSessionResult)
at Neo4j.Driver.Internal.AsyncSession.<>c__DisplayClass37_01.<<RunTransactionAsync>b__1>d.MoveNext() --- End of stack trace from previous location ---    at Neo4j.Driver.Internal.AsyncRetryLogic.RetryAsync[T](Func1 runTxAsyncFunc)<---
--- End of inner exception stack trace ---
at Neo4j.Driver.Internal.AsyncRetryLogic.RetryAsync[T](Func1 runTxAsyncFunc)    at Neo4j.Driver.Internal.AsyncSession.<>c__DisplayClass37_01.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Neo4j.Driver.Internal.Logging.DriverLoggerUtil.TryExecuteAsync[T](ILogger logger, Func`1 func, String message)
at Neo4jClient.BoltGraphClient.Neo4jClient.IRawGraphClient.ExecuteGetCypherResultsAsync[TResult](CypherQuery query)
at Memgroups.Providers.Neo.AdminRepository.GetGroupCount() in D:\a\1\s\Memgroups.Providers\Neo\AdminRepository.cs:line 54
at Memgroups.Api.Controllers.NeoAdminController.GetEntityCounts() in D:\a\1\s\Memgroups.Api\Controllers\NeoAdminController.cs:line 55

@mocox
Did you find any solution/workaround for that?

I'm facing the same issue, any update on this?
My current workaround is using the client as a scoped service instead of singleton, but of course this won't be a solution in production environment

@lukacs-peter we are using it as Singleton in an Azure WebApp and solved the timeout issue like this:
           var tryCount = 0;

            if (_rootUri == null)
                SetCredentials();

            TryToConnect:

            try
            {
                tryCount++;

                IGraphClient graphClient;

                if (_useBolt)
                {
                    var driver = GraphDatabase.Driver(_rootUri,
                        AuthTokens.Basic(_username, _password),
                        config => config
                            .WithConnectionAcquisitionTimeout(TimeSpan.FromSeconds(15))
                            .WithConnectionIdleTimeout(TimeSpan.FromMinutes(3))
                            .WithSocketKeepAliveEnabled(true)); // prevent connection timeouts

                    graphClient = new BoltGraphClient(driver)
                    {
                        JsonContractResolver = new Neo4jContractResolver(),
                        DefaultDatabase = Database
                    };
                }
                else
                {
                    graphClient = new GraphClient(_rootUri, _username, _password)
                    {
                        JsonContractResolver = new Neo4jContractResolver(),
                        DefaultDatabase = Database
                    };
                }

                ServicePointManager.ServerCertificateValidationCallback = (obj, certificate, chain, errors) => (true);

                await graphClient.ConnectAsync();

                if (!graphClient.IsConnected)
                    throw new GraphClientException($"graphClient was not able to establish connection to ({_rootUri})!");

                return graphClient;
            }
            catch (Exception ex)
            {
                if (tryCount <= 30)
                {
                    await AiLogger.LogAsync(ex, null, true, false, null, "Trying again in 10 seconds!");
                    Thread.Sleep(10000);
                    goto TryToConnect;
                }

                await AiLogger.LogAsync(ex, null, true, true);

                throw;
            }

Apparently Azure kills any alive connections after 4 minutes, so as @Clooney24 pointed out, you should set the WithConnectionIdleTimeout to a value less than 4 mins.


--tag not working

Expected Behavior
Using the --tag for the docker-slim build command is supposed to result in the optimised image being tagged with that name

Actual Behavior
The final tagged image is still <original_image_name.slim>:latest

Steps to Reproduce the Problem

Use the command to build an optimised image:
docker-slim build --http-probe-off --include-path=/usr/local --continue-after 1 --target eventflow/rfunction:rsi --tag eventflow/rfunction.slim:rsi

Replace it with any of your image target. However, this is what I see for the target image with name eventflow/rfunction:rsi. Final image created is eventflow/rfunction.slim:latest instead of eventflow/rfunction.slim:rsi

Specifications

docker-slim version: linux|Transformer|1.36.0|5dad378523ed9d53f6e5de21f6b98f07da4f7d59|2021-06-13_02:46:04AM
OS:version :: Ubuntu: 18.04.3 LTS (Bionic Beaver)

still trying to repro...

still trying to repro it

@naanunaane do you mind trying 1.36.1 to see if we can get additional info about what's going on (  https://github.com/docker-slim/docker-slim/releases/tag/1.36.1 )

@kcq, this worked after I updated to the 1.36.1 version. Thanks.

nice!


Made misc changes

If test client is windows machine "ping -c" will error out. So modified tests accordingly.
Also fixed few test script issues.

Test Revoke ingress rule after deploy VM ... === TestName: test_02_revokeIngressRule_AfterDeployVM | Status : SUCCESS ===
ok

Ran 1 test in 163.393s
OK


Assume deduce type on arguments where : Ty is ommitted

This should compile and work:
f :: fn a -> *
	a
end

Maybe only do implies void return type and ->

It is possible to implement this partially for only the function parameters. That should be quite easy.

Closed in #542

It's already done


Stricter test for #223

@makabde review please. :)

@marocchino It is all good for me, thanks for correcting my mistakes.

@makabde thanks for your feedback. :smile:


Ensure generated SIRI-VM fields are valid by stripping invalid chars defined in the SIRI-VM schema

This one will need a manual apply and manual integration tests too


[Remote Store] Support refresh level durability

Is your feature request related to a problem? Please describe.

As part of remote store feature that was introduced in OpenSearch 2.3, segments are uploaded to remote store post each refresh.
This means remote segment store contains segments that were part of last refresh.
But the _remotestore/_restore API only supports commit level durability.
This feature will add refresh level durability support to the restore API.

Currently, I am thinking of using the same flow that segment replication uses when replica receives the publish checkpoint.
https://github.com/opensearch-project/OpenSearch/blob/b43e985fa6601a2b44d69a91b138a4462f15fde8/server/src/main/java/org/opensearch/index/store/Store.java#L869-L884

@sachinpkale Why do we need to support refresh level durability here? Could remote store use commit level durability until we implement remote store as the source of replication for segrep?  There is a lot of overlap here with that effor.


New banklink protocol & Liisi implementation

Hi
Yes, this library is important to me and I’ll keep the fork updated anyway! And btw, thanks for the great library!
BR,
Markus
From: Roman<EMAIL_ADDRESS>Sent: Monday, February 26, 2018 7:13 PM
To<EMAIL_ADDRESS>Cc: Markus<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [Inoryy/Banklink] New banklink protocol & Liisi implementation (#11)
This looks great, thank you!
Unfortunately I don't have enough the time to maintain this project anymore. If you'd like to take over, I could make you a collaborator on this repository or you could maintain a fork and I'd link it from the main repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FInoryy%2FBanklink%2Fpull%2F11%23issuecomment-368576142&data=02|01||c571def703754b4d215b08d57d3c42e6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636552620121886521&sdata=N7cKKPkbnpFO1t2PfjKbUwb%2BZ%2FiVhUp8wmtjy7IGmpg%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGFevVmc1dV0apPr4g9SK1_4bkckgS4Oks5tYuY0gaJpZM4SSZFz&data=02|01||c571def703754b4d215b08d57d3c42e6|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636552620121886521&sdata=jYjfVu9yJUsf6jOWSmfqKPgFL0FLMEJohWzAUSKKSog%3D&reserved=0.

@Shmarkus awesome! I've added a link to your fork to the readme file.


[Labeling] Design/Implement cleanlab support

The idea is to facilitate the usage of cleanlab to easily find possible labeling errors. Should be a weak dependency.

[ ] Design
[ ] Implementation

Here is a first simple proposal:
from rubrix.labeling.text_classification import find_label_errors

recs = find_label_errors("my_dataset_name")  # returns a list of TextClassificationRecord

# if you want to inspect the results in the notebook
pd.DataFrame(map(dict, recs))

So find_label_errors would be a light wrapper around cleanlab.pruning.get_noise_indices with following signature:
def find_label_errors(dataset: str, sorted_by: str = "prob_**kwargs) -> List[TextClassificationRecord]:
    """Find potential annotation/label errors in your dataset.

    It will include all records in the given dataset for which a prediction AND annotation is available.
    Make sure the predictions were made in a holdout manner, that is include only records that were not used in the training of the predictor.
    Args:
        dataset: Name of the dataset
        sort_by: One of the two options
            - "likelihood": sort the returned records by likelihood of containing a label error (most likely first)
            - "annotation": sort the returned records by the probability of the annotation (highest probability first)
        **kwargs: Passed on to `cleanlab.pruning.get_noise_indices`

    Returns:
        A list of records containing potential annotation/label errors
    """

**kwargs include parameters like prune_method and other advanced parameters.
@dvsrepo @frascuchon as always, input/suggestions more than welcome!

I don't have much to say on this matter. Go ahead with the proposal

discussion with dani:

Add warning when no record has prediction nor annotation
Add new tutorial (only code) to this PR based on the current cleanlab tutorial:

use agg_news dataset
use a small sklearn model
use x-validation to check training data


Sorting+Limit with AppSync + Elastic Search

With AppSync <-> Elastic Search, according to the docs, it advises you to use filter when searching for a specific term.
https://docs.amplify.aws/cli/graphql-transformer/searchable
If I have a 100 posts and post #1, #2, #100 have my type === 'blog', I expect to get 3 results back if I search by type === 'blog' and limit at 5 with Elastic Search using the following query. But I get back actually 1 result.
If I remove thesort: {direction: desc, field: time} I get back all 3 results.
query MyQuery {
  searchList(sort: {direction: desc, field: time}, limit: 5, filter: {
    type: {
      matchPhrase: "blog"
    }
  }) {
    items {
      id
      type
    }
  }
}

I think the issue is with filter because it searches then filters.
With AppSync <-> DynamoDB, in the schema.graphql you can add the keys attribute to create a GSI, so when you query, you don't need to use the filter key, but in the root of the query specify the attribute you added as a key. This fixes the LIMIT issue in the AppSync <-> DynamoDB scenario.
How do I fix this issue with the AppSync <-> ElasticSearch scenario?

Hi @chantlong
It seems like there is no value with just blog keyword present in your inverted index in ES. Values like blog1 or blog2 wont be fetched using just matchphrase as it will look for blog keyword in your index.
Can you try with matchPhraseprefix?
Let me know if this works for you?

@akshbhu "blog" is just a text example, it can be anything. type has "blog", "business", "finance"...etc.
Anyways it seemed like there was a problem with the resolvers generated by Amplify in that it causes the search, to search the entire Table with the matched text and then filtered by user Id in the resolver. Managed to be fixed with a custom resolver so that it queries results only belong to that user id without filtering needed.


[Suggestion] Add option to change background colours for icons.

Add option to https://revadike.ga/swi/settings/ to let users set the colour of the icon background (line 585 - background: rgba(0, 0, 0, 0.7);) in order to avoid having to manually edit the line just like there's options to adjust any other color on the settings page.

Done! Please check out https://github.com/Revadike/SteamWebIntegration/releases/tag/V1.12.0


Render Issues with More Mob Variants

Minecraft v1.20.1
Forge v47.2.20
Enemy Banner v0.0.4
More Mob Variants v<IP_ADDRESS>
The mod More Mob Variants adds new textures variants to vanilla mobs, but it has render issues when displayed on a banner, with it flashing extremely fast through the variants.
This should be a zombie banner:

The entity model features mod might also be causings limbs to be out of place.

I've found the cause of the flashing textures. It was caused by More Zombie Variants resource pack, which requires the entity model features mod. I've disabled the resourcepack, but limbs of mobs are still not in the correct spots

This is fixed for me now, thanks!


[README.md] bold styling not applied to text

Current State
Currently all points under section: "Join the Meshery community!" have the first word or two italicized and bold styling added. However the third point "Fill-in a community member form to gain access to community resources.", has its first word "Fill-in" italicized, but does not have the bold styling applied.
Screenshots

Desired State
To maintain consistency, add bold styling to the text "Fill-in"
i.e "Fill-in  a community member form to gain access to community resources."

Contributor Guides and Resources

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

/assign

Hello @sandramsc I would like to work on this issue can you please assign it to me.

@xiangpingjiang I have assigned this to you.

@xiangpingjiang  Can you please assign this issue to me !

@WillOfHeaven
Sorry，I have already submited a PR. And I will soon finish it


persistent deprecation message

When running the following command using the latest version of CCT (354ac1aef93eb50a742f3f8a96a8edb1de3a5df9)
l <- CCT::checkCache()

I get the following output
Loading and checking cache file: C:\Users\papsti\AppData\Local\CCT\cct_cache.rda
Check current status of remote files
Joining with `by = join_by(lineage, parent,
children)`
Lineages list differs from cached, updating hierarchies
Overwriting C:\Users\papsti\AppData\Local\CCT\cct_cache.rda with new hierarchies
Returning list of cache objects
Joining with `by = join_by(lineage, parent)`
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."

I'm not sure if this deprecation message is coming from another CCT function or from a dependency.
A secondary issue is that the message is persistent and continues to pop up every time I run a command in the R console after it first appears, whether or not I'm interacting using CCT. For instance, the next command I executed after the above is the following:
> x = 2
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."
[1] "Node$fields will be deprecated in the next release. Please use Node$attributes instead."
[1] "Node$fieldsAll will be deprecated in the next release. Please use Node$attributesAll instead."

The only way I've found to clear this persistent message is by restarting my R session.

Fixed in https://github.com/TheZetner/cct/commit/276c9d20fb22cf57f9828a7c2a2fc1093001517f


Multiple cameras and switching between them

Hi,
I have question if there is more then one camera, is it possible to switch between cameras and choose which one do you want?

Yes we can, like google hangout does it
On Fri, 7 Apr 2017 at 12:09 PM Muhamed<EMAIL_ADDRESS>wrote:

Hi,
I have question if there are more then one camera, is it possible to
switch between cameras and choose which one do you want?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/streamproc/MediaStreamRecorder/issues/124, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABLSMRyWSo5CQNOjePK0KIV_5oDhZj1Sks5rteEogaJpZM4M2iOa
.

--
Thanks & Regards Talal Arshad

Hi @talal7860, thanks for response, can you give me any directions or guideline?

I've the code, I'll share it soon.
On Fri, 7 Apr 2017 at 5:06 PM Muhamed<EMAIL_ADDRESS>wrote:

Hi @talal7860 https://github.com/talal7860, thanks for response, can
you give me any directions or guideline?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/streamproc/MediaStreamRecorder/issues/124#issuecomment-292519358,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLSMf-QMNZxn0OWtR0bpz75sMgmNpuhks5rtia4gaJpZM4M2iOa
.

--
Thanks & Regards Talal Arshad

Thanks @talal7860

You can NOT change camera during an active recording.
AFAIK no spec allows us change audio and/or video tracks during an active recording.
You must stop old recorder and re-initiate with fresh tracks (streams).
Do you want a solution/workaround to change microphones/cameras during a recording? MultiStreamRecorder (WebAudio+Canvas2D+MediaRecorder based implementation) can be a solution or hack.
WebAudio can append new audio streams, stop or mute old audio tracks and so on. (<<----may not work)
Canvas2D based solution can ignore older camera tracks and draw your preferred video-stream on the canvas surface. (<<----should/must work)

how do you choose the camera, if there are multiple, before any streaming begins?
do you have example code you can link to please?
thanks.


Using skeleton in a subdirectory

How would you adjust the .htaccess to make the skeleton work in a subdirectory?
I am writing an API wich resides in /var/www/api
It should be accessed by going to https://www.example.com/api

In this case the Slim basePath must be set to /api.
$app->setBasePath('/api');

Thanks a lot :) Now everything is working.


Fix schnorr test

solves #156
known issues:
randomized test runs very long time tho..

Which test is taking a long time? The bench_ or something else?

test_schnorr_signature_random_valid_inputs

Aha, it is because when you do rng.clone(), it does not change the rng, so for i=1 the rng happens to trigger the while loop in random_schnorr_signature_input and then it just infinite loops.
Also, please run cargo clippy and fix all formatting errors.

nice thanks so much for help take a look, u so smart, i didn't even realize it.

rated in each loo

this time seems right, since i only clone on the top once, and <Secp256k1Affine as CurveAffine>::ScalarExt::random changes internal state of tmp.


[WIP][DO NOT REVIEW] Private Network support for Azure OpenAI on your data

@wangyuantao - Can you take this PR out of draft mode when it's ready for review?

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Included in #248524
#please-close


docs: fix repo links replace material-components-web with material-web

Related to PR #3260 and issue #3252

@asyncLiz if you had a time i'd be glad if you could take a look

@asyncLiz if you had a time i'd be glad if you could take a look

Unfortunately I am swamped right now and don't have cycles to review this 😔
This will also be rendered obsolete very shortly once we get the repo updating again, which is why I'm leaning towards holding off on it.

@asyncLiz There hasn’t been any update in a long time. Is everything ok?

Thanks for this contribution, but with the current state of the repository we're going to close this for now :)


Update release?

It has been a few years and people are still using this library, maybe time to push an update?

Dupe of #47


Error

Why do I always get this on the iOS stickers they work some times then I get this error thing the other times Queued (2907) 🤔💚

Hello, @RickyBush!
There was a problem with converting sticker thumbnails in [@tgtowabot]https://t.me/tgtowabot. Now the issue is resolved (thanks for https://github.com/lovell/sharp/issues/2570#issuecomment-776228960), so the queue should be decreased soon.


Improved Docs

Some improved readme

@AnushKamble I'm marking this PR invalid because it's a low quality PR.
Please consider contributing to Appsmith in a better way by picking from the list of good first issues


docs(sip): add spin build SIP

Signed-off-by: Radu Matei<EMAIL_ADDRESS>

ref #352

This PR also updates the SIP index page and individual SIPs to render properly.
(I can split this into a separate PR if we want, I just thought it might be easier to get away with it 😅)


How to train on untrimmed datasets？

I want to know how to train on untrimmed datasets, such as ActivityNet, Thumos14, especially how to use the temporal annotations?

Thanks for your reply. I know that UntrimmedNet is a weakly supervised framework. I thought the other repository (submission to anet2016) is trained with the temporal annotations, but seems that it only use the temporal annotations to get clipped activity instances and the new aggregation is more important.
Thank you very much.


xsd parsing errors: if to many errors occur the menu to open the flow is not reachable

Describe the bug
if to many errors occur the menu to open the flow is not reachable, you have to click to remove as many errors as possible to shrink the list
Reporter
jjansenvr
Category
Use the following Tags to categorize your bug report

Explorer
Editor
Flow
Pipe options
Palette
Settings

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here. (f.e. ladybug report, console error or test adapter with larva test)

We could make the header appear above the errors, even if it might look weird. Another option is to make the amount of shown errors smaller.

1u

On a 1080p screen, 10 errors would fit, as long as their don't have more than 3 lines of text.

:tada: This issue has been resolved in version 2.19.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Works on Firefox but not on Chrome

It's fixed in chrome 101.


Overwrite link-local address with my own ULA

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
On my server, there are multiple interfaces using fe80:: prefixes (e.g. podman).
I tried to solve that issue by setting a static IPv6 configuration with my own private ULA (fdb0:[...]).
However, I noticed that now I simply get an additional IPv6 address:
    inet6 fdb0:[...]/64 scope global dynamic noprefixroute
       valid_lft 86355sec preferred_lft 14355sec
    inet6 fe80::[...]/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Describe the solution you like
Is there a way to replace the fe80:: address with my own ULA?
Or would it be possible to disable the fe80:: address and set the fdb0:[...] as default gateway?
Describe alternatives you considered
Additional context

Actually the following issue sounds quite similar to mine:
https://github.com/opnsense/core/issues/817

I wouldn't know why you would like to remove the default link-local (it's likely not a good idea), but my best guess is setting the tunable net.inet6.ip6.auto_linklocal to 0 stops assigning one automatically. See also https://man.freebsd.org/cgi/man.cgi?ifconfig(8)

In practice this will likely lead to defunct IPv6 unless you add static valid link-locals to every interface that should speak IPv6.

What I want to reach is to get from the current state:
    inet6 fdb0:[...]/64 scope global dynamic noprefixroute
       valid_lft 86355sec preferred_lft 14355sec
    inet6 fe80::[...]/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

to this state:
    inet6 fdb0:[...]/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

so I can avoid having overlapping link-local addresses.

Link local addresses are local to their link.
Each interface can have fe80::1 and it does not matter since the full link local address is fe80::1%interface for the operating system.
Do not mess with link local if you do not want IPv6 to break.


feat(core): Ability to include/exclude groups and properties from the…

Ability to include/exclude groups and properties from the final results

New configuration options to include or exclude groups and properties from the final document
Samples are extended

Closes #44
Closes #39

The document was a mess. Groups and properties were everywhere, making it hard to read. But then a hero came along and added configuration options to include or exclude them from the final document. Samples were extended and logic was extracted for post processing. Now the document was neat and organized, and everyone was happy.
Created by Commit Teller


Is it possible to reuse memory?

I want to parse multiple HTML files, and I was wondering if between those files, I could reuse the document and collection (instead of creating & destroying each time) for performance reasons?

Hi @SGauvin
Each module in the project is designed to reuse already allocated memory.
It would be complete madness to call malloc/calloc and free every time.
Create document once and use it for all HTML source.
Something like:
document = lxb_html_document_create();

while (html != NULL) {
    status = lxb_html_document_parse(document, html, html_len);

    /* We do anything. */

    lxb_html_document_clean(document);

    html =  "some kind of html"
    html_len = ....
}

lxb_html_document_destroy(document);

There is also more subtle resource and memory management, but I think this is enough in general cases.

@lexborisov Thank you for your quick response :)
I must admit I'm a little bit confused, because this code crashes (reusing allocated memory)
void run(CURL* curl, const char* url, std::string& responseString)
{
    std::deque<std::string> toVisit{};
    std::string currentUrl = std::string(url);

    auto document = lxb_html_document_create();
    auto collection = lxb_dom_collection_make(lxb_dom_interface_document(document), 128);

    do
    {
        responseString.clear();
        curl_easy_setopt(curl, CURLOPT_URL, std::string("https://en.wikipedia.org" + currentUrl).c_str());
        curl_easy_perform(curl);

        {
            auto status = lxb_html_document_parse(document, (const unsigned char*)responseString.c_str(), responseString.size());

            if (status != LXB_STATUS_OK)
            {
                std::cerr << "Error while parsing HTML" << std::endl;
                continue;
            }

            auto body = lxb_dom_interface_element(document->body);
            status = lxb_dom_elements_by_attr_begin(body, collection, (const lxb_char_t*)"href", 4, (const lxb_char_t*)"/wiki", 5, true);

            if (status != LXB_STATUS_OK)
            {
                std::cerr << "Error while parsing HTML" << std::endl;
                continue;
            }

            for (size_t i = 0; i < lxb_dom_collection_length(collection); i++)
            {
                auto element = lxb_dom_collection_element(collection, i);
                const char* link = (const char*) lxb_dom_element_get_attribute(element, reinterpret_cast<const unsigned char*>("href"), 4, nullptr);
                toVisit.insert(toVisit.end(), std::string((const char*)link));
            }

            lxb_dom_collection_clean(collection);
            lxb_html_document_clean(document);
        }

        std::cout << "Visited " << currentUrl << '\n';
        currentUrl = toVisit.front();
        toVisit.pop_front();

    } while (toVisit.empty() == false);

    lxb_dom_collection_destroy(collection, false);
    lxb_html_document_destroy(document);
}

According to GDB:
Thread 1 "wikipedia_parse" received signal SIGSEGV, Segmentation fault.
0x000055555557ce0d in lexbor_array_push ()

While this code doesn't crash (reallocating each time)
void run(CURL* curl, const char* url, std::string& responseString)
{
    std::deque<std::string> toVisit{};
    std::string currentUrl = std::string(url);

    do
    {
        auto document = lxb_html_document_create();
        auto collection = lxb_dom_collection_make(lxb_dom_interface_document(document), 128);
        responseString.clear();
        curl_easy_setopt(curl, CURLOPT_URL, std::string("https://en.wikipedia.org" + currentUrl).c_str());
        curl_easy_perform(curl);

        {
            auto status = lxb_html_document_parse(document, (const unsigned char*)responseString.c_str(), responseString.size());

            if (status != LXB_STATUS_OK)
            {
                std::cerr << "Error while parsing HTML" << std::endl;
                continue;
            }

            auto body = lxb_dom_interface_element(document->body);
            status = lxb_dom_elements_by_attr_begin(body, collection, (const lxb_char_t*)"href", 4, (const lxb_char_t*)"/wiki", 5, true);

            if (status != LXB_STATUS_OK)
            {
                std::cerr << "Error while parsing HTML" << std::endl;
                continue;
            }

            for (size_t i = 0; i < lxb_dom_collection_length(collection); i++)
            {
                auto element = lxb_dom_collection_element(collection, i);
                const char* link = (const char*) lxb_dom_element_get_attribute(element, reinterpret_cast<const unsigned char*>("href"), 4, nullptr);
                toVisit.insert(toVisit.end(), std::string((const char*)link));
            }

            lxb_dom_collection_destroy(collection, false);
            lxb_html_document_destroy(document);
        }

        std::cout << "Visited " << currentUrl << '\n';
        currentUrl = toVisit.front();
        toVisit.pop_front();

    } while (toVisit.empty() == false);
}

What am I doing wrong? Is there documentation I can read somewhere?
Thank you for making this library :smile:

compile with -g3 -ggdb3, and also use valgrind (or asan)

@SGauvin
Logical error was found when clearing the document.
To create collections, the memory from the document was used, and then we cleared it.
Now it works well.
Logical error was found when clearing the document.
To create collections, the memory from the document was used, and then we cleared it.
Now it works well.
Thanks for the report!

@SGauvin
And lxb_dom_collection_destroy(collection, false); --> lxb_dom_collection_destroy(collection, true);
If your object is not on the stack, then it must be destroyed.
Please, close the issue if it is resolved.

@SGauvin
Thank you for using the library and I hope it helps you.
There will be a big code update soon, and after that I will have to think about the documentation. There is a lot of code, few examples, we need to somehow document it.


Host the LeNet example

Host the LeNet example at https://webmachinelearning.github.io/webnn-samples/lenet/

LeNet example is online!


PEO-298 Remove I18n integration

PEO-298
Description
Remove I18n integration
Before submitting the merge request make sure the following are checked

[x] Followed the style guidelines of this project
[x] Performed a self-review of own code
[ ] Wrote the tests that prove that fix is effective/that feature works

@rostikkkk2 what about these files lib/inquisition/config/initializers/autoload.rb and
lib/inquisition/config/initializers/i18n.rb? There is the use of i18n.


Bump omniauth-oauth2 dependency version

This PR updates the omniauth-oauth2 dependency to 1.3.1 to allow using a later version (>0.10) of faraday in konekti. We need to bump faraday in konekti to use the qualtrics_api gem.
I tested creating all oauth services after the dependency bump and everything is working as expected.

Thanks @amandamholl @jasonwc!