KeyError: 'nodeSpacing'

When I run Grid Example.ipynb or Labels example.ipynb I get:
Traceback (most recent call last)
<ipython-input-5-36fb9ff467a6> in <module>
----> 1 cytoscapeobj.set_layout(name='grid')

~/miniconda3/lib/python3.7/site-packages/ipycytoscape/cytoscape.py in set_layout(self, name, nodeSpacing, edgeLengthVal, animate, randomize, maxSimulationTime, padding)
    119             dummyDict['nodeSpacing'] = nodeSpacing
    120         else:
--> 121             dummyDict['nodeSpacing'] = self.cytoscape_layout['nodeSpacing']
    122         if edgeLengthVal != None:
    123             dummyDict['edgeLengthVal'] = edgeLengthVal

KeyError: 'nodeSpacing'

Hum! I know this issue.
I thought I had fixed it before, but this is happening because of bug on a library we use, traitlets. Because of this bug you can't change individual key/values of a dictionary, you have to change it all over again, so I think the Labels example is doing something like this:
cytoscapeobj.set_layout(name='grid')

When it should actually be doing something like this:
cytoscapeobj.set_layout(name='grid', nodeSpacing=10, edgeLengthVal=10)

The new version I'm working now makes this issue goes away =) It should be ready by some point in this week.
For now what you can do is pass all of these three arguments every time you want to change the layout, sorry!

This is fixed and can be found on the master branch in this repo, or in the version 0.2.0 that will be released soon. I decided to postpone the new version because I wanted to add some functionalities for a project I'm contact with.
If you need help building stuff directly from git, don't hesitate to ping me here.


Automatic removal of trailing whitespaces

Hello,
While doing a pull request, i found out spf13 automatically removes trailing whitespaces. Is it possible to disable this? I couldn't figure out how.
Thanks
David

hey! that also bother me
And now i found switch on let g:spf13_keep_trailing_whitespace = 1 in ~/.vimrc.before helped
:laughing:

Hey thanks a lot! I will try this :)
On Mon, May 22, 2017 at 10:11 AM 叶萧(Rain<EMAIL_ADDRESS>wrote:

hey! that also bother me
And now i found switch on let g:spf13_keep_trailing_whitespace = 1 in
~/.vimrc.before helped
😆
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/spf13/spf13-vim/issues/990#issuecomment-303029785,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3F8O17YFx8CQ4EBeXpjYhr34x3jJRoks5r8UMTgaJpZM4LClF3
.


Fixing issue with menu been non reposnsive

Fixing the issue with the menu not been responsive when the navigation controller isn't the root view controller

I remember this had some side effects depending on how the menu is used. Can you let me know what your setup is (maybe a demo) along with how exactly is it not responsive? thnaks


[cairo] update port

Bump version to 15.4 (15.x branch is officially a "snapshot" branch but GTK+ won't build on Windows with 14.x series (see here)... msys2 also uses 15.4 by default)
Additional font support (fontconifg + freetype)
GObject support (required for GNOME libraries like pango)

Thanks very much for the background info w.r.t. msys2, saves us a lot of legwork 👍 .

Thanks!


Add test for 'stats' method and further document it.

The new stats() method introduced in #584 was (automatically) documented in
the v2 reference documentation, but because of the way v1 documentation is
organized it had to be manually added there.
Also, while I was here I added a unit test for stats().

Just a bit slow to the party here.  Had 3-hour call today training someone on the hklpy code.  Very successful, most questions answered.


[BUG] tar does not resolve when extracting a tarball including multiple symlinks that point at the same file

What / Why
When extracting a tarball that includes multiple symlinks that point at the same file, tar will never resolve (or call the callback).
This only occurs when running on Windows and symlinks cannot be created (i.e. not running as an administrator or with developer mode enabled). However, the EPERM failures are not fatal errors so I would consider what's occurring here a bug. This works fine on<EMAIL_ADDRESS>and looks to have appeared around 5.X
In larger tarballs when this situation occurs this causes the extraction to finish and the extracted folder to be incomplete and invalid.
When

tar: 5.0.5, 6.0.5

Node.js: 10.23.0, 12.20.0

n/a

Current Behaviour
In step 3 done! is never logged
Steps to Reproduce

Download output-with.tar.gz and
output.tar.gz
Run the below code in a node repl from the same folder as the tar.gz file (this is the tarball that works fine)

require('tar').x({file: 'output.tar.gz'})
    .then(() => console.log('done!'))
    .catch((err) => console.log(err));

Run the below code in a node repl from the same folder as the tar.gz file

require('tar').x({file: 'output-with.tar.gz'})
    .then(() => console.log('done!'))
    .catch((err) => console.log(err));

Expected Behavior
At step 3, done! is logged and extraction is completed

Curiously, when passing sync: true this doesn't occur

Can you test this again?  I can't seem to reproduce on the latest v6.

I can still repro this issue on tar 6.1.3/Node.js 14.17.4
Do you have symlink creation disabled? mklink foo package.json should fail with You do not have sufficient privilege to perform this operation.. If you have Developer Mode enabled then disabling it should disable symlink creation


Flows activity/metrics

Charts library could be better, I did not find a way to configure time-series min/max value or step,  formatting Y axis is not trivial too, but for an early feature this should do the job:

@jamilbk pushed CSV export and made visualization 3x smaller. The screen you referred to is already there and was merged in #2166:

@AndrewDryga Gotcha. Were you thinking that we'd just not list the /flows route in the sidebar then in order to keep it hidden for now?

@jamilbk sure, without connlib changes it doesn't make sense to show it - we can do that before public release (probably by adding some config so that we can still see it locally), there are plenty of features to hide in the UI anyways


Optimize the startup time

Resolved in https://github.com/LitoMore/simple-icons-figma/commit/014ebaff95f6f48d63604d2353e0fd25d81435db.


Abort / log an error if Trunk.toml is malformed

Currently trunk will silently ignore typos in Trunk.toml, even when running in --verbose mode. This makes it very difficult to even realize that there's an issue, let alone determine what the issue is and fix it.
For example, we had [server] instead of [serve] in our Trunk.toml and all the configs in that section were not working, but we didn't know why.

Yes, I can understand that.
The problem might be that serde doesn't support that easily: https://serde.rs/container-attrs.html#deny_unknown_fields
When using flatten (which IIRC we do) then this won't work. I am not really sure how to tackle this.


In the daemon protocol, we should separate out progress messages from app.log

app.log currently handles both stdout from the app and progress start/stop messages. We should separate this out into app.log and app.progress events - it's slightly more hygienic, and we'll be relying on the progress messages a bit more from IntelliJ.

We should also let progress messages have semantic IDs, so that tools can take action based on them.


[Question] The Huddle tool cannot connect to the graph database.

Problem Type (问题类型)
None
Before submit

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

Environment (环境信息)

Server Version: 1.x.x
Toolchain Version: 1.x.x
Data Size:  xx vertices, xx edges

Your Question (问题描述)

I am unable to use the Huddle tool to connect to the graph database, and the specific error message is shown in the figure. Can you tell me what to do?
Vertex/Edge example (问题点 / 边数据举例)
No response
Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构)
No response

try to use docker-compose way (already provided a configuration file that you can find on the doc)

what's jdk version use?


Add lyftColor to the game 💯

Because the branding matters 😛

LGTM

Codecov Report

Merging #4682 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #4682      +/-   ##
=========================================
+ Coverage    71.4%   71.4%   +<.01%
=========================================
  Files         190     190
  Lines       14934   14935       +1
  Branches     1102    1102
=========================================
+ Hits        10663   10664       +1
  Misses       4268    4268
  Partials        3       3

Impacted Files
Coverage Δ

superset/assets/javascripts/modules/colors.js
77.08% <100%> (+0.48%)
:arrow_up:

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 00cab7e...e80a502. Read the comment docs.


fix: fixed release naming in README.md

Q
A

Branch?
master

Bug fix?
yes

New feature?
no

Deprecations?
no

Tickets
-

License
MIT

Doc PR
no

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


Investigate Streams API wrt to Service Workers

Ref : https://jakearchibald.com/2016/streams-ftw/?utm_source=html5weekly&utm_medium=email

can we leverage this for the greater good?
what does it entail?
can we change @jakearchibald's mind on SPAs?
are there things we can do in core to take advantage of this?

Wouldn't we need access to the streaming parser from the page to fix this? (Or reimplement the streaming parser, which may be big & slow)
I'm really hoping we can create something like a streaming document fragment that can be added to a page and have a writable stream.

@jakearchibald writable fragment sounds like an interesting idea. We're obviously somewhat constrained by the SPA structure, but we love the app shell idea and we're on board the service worker hype train. We want to accomplish first render and interaction ASAP, so all ideas welcome.


Compilation error not shown when using conditional expressions within logical expressions

Description:
When attempting to replace an expression within a logical expression with a conditional expression, the compiler does not give a compilation error, rather gives the output of the conditional expression. However when written within parenthesis the compilation error is shown.
Steps to reproduce:
public function main() {
    string a = "text";
    io:println(true && a == "text"? 2 : 1);
    io:println(false && a == "text"? 2 : 1);
    io:println(true || a == "text"? 2 : 1);
    io:println(false || a == "text"? 2 : 1);
}

The output for the above seems to be correct.
2
1
2
2

@suleka96 according to the operator precedence table in the spec,
x && y and x || y have higher precedence over x ? y : z.


fix(protocol): decide a block's min tier in the next block

This PR addresses a vulnerability identified in previous audits regarding the manipulability of min-tier selection by block proposers. The new approach leaves the min-tier undecided until the next block proposal. This change mitigates direct manipulation by current block proposers and introduces a delay mechanism in min-tier selection. While some manipulation risk remains when consecutive blocks are proposed by the same entity, this solution reduces overall vulnerability compared to the current implementation.
TODO:

[ ] fix tests
[ ] modify TierRounter in test to return either ITierProvider or ITierProviderV2

Seems problematic to postpone it till the next block because the proposer now does not know that the block it is proposing is profitable?
From a UX perspective, I still think any randomness is problematic because of the spike in fees (and if there is no need for a fee increase the proof should always be required because cheap enough).

Seems problematic to postpone it till the next block because the proposer now does not know that the block it is proposing is profitable?

It can be an issue, but may be minor.
A similar issue in the current protocol is that blocks are verified in a batch triggered by proposeBlock and proveBlock, if a proposer is unlucky, he will spend more gas on L1 to verify 16 block (fee spikes). In theory, when base fee and tips are both small, even the biggest block cannot yield enough fees to cover the gas cost on L1. In world where all proposers are perfectly rational, nobody will propose the next block, until more block can be constructed whose fees, combined with all previous block's fees, can cover all the gas cost of all these blocks on L1. One way to solve this is to ask each proposers to deposit some ETH in the protocol and when his block is verified, we simply deduct some Ether from his account, so all verified blocks' proposers share the settlement cost. But these operation will increase the over all gas cost, so this is not a good idea.
I think these are minor issues if we believe the cost of different possible proofs are very small compared to L2 fees to be collected in a block.

Given that the benefit of these changes is unknown, I'm dropping this PR.


command line - playlist name

if playlist name exists in command line args, generate & open that playlist and quit directly - without showing any gui.

when finished, keremkoseoglu/Guitar-Training-Remote#84 can continue

when finished, update readme accordingly


Problems with image transparency display at any zoom level

Describe the bug
Hello!
When trying to overlay 2 RGB images on top of each other (images are produced using bioformats2raw - raw2bioformats pipeline), we encounter bug with transparency of overlayed top image, some regions are opaque, provided screenshot can describe situation clearly:

This behavior happens at all opacity slider settings.
To Reproduce
We have build vitessce exactly as described in documentation:
pnpm install
pnpm run build # for @vitessce/icons and @vitessce/workers
pnpm run start-demo

Expected behavior
Overlayed image should be transparent with "Zero transparent" flag set to True
Environment:

Release or git hash: commit 3bbff2ea87cebbc237abec29059b750b39b97f3d
Browser: tested both on Firefox 107.0 and Chrome 107.0.5304.107

Older vitessce version (1.1.15) displays everything correctly like so:

But we decided to move to Zarr in our work, so vitessce require update in order to support new configuration.

Can you share the JSON configuration? http://vitessce.io/docs/troubleshooting/#what-is-the-current-view-config
Also v1.1.15 was released september 2021 and there have been many changes since then. To help us narrow down the commits that might have resulted in the behavior change, would you be able to try the same configuration with the release demos after v1.1.15 which can be found at https://github.com/vitessce/vitessce/blob/main/DEMOS.md

Thank you for prompt response!
Config we use is in attachment, images are served locally. If needed i can generate example image to reproduce error.
example_config.txt
I will try other demos to see which version is last compatible, thank you!

Hello @ilan-gold !
I`ve prepared small image examples which can reproduce this error, where it would be convenient for you to upload this files?

@ilan-gold , i have also tested #1343, and it works, thank you very much!
Before:

After:

Now all artifacts are gone.

Excellent, I was just answering you anyway.  So we'll get that merged and fixed in the next release. Thanks!


Specify browsers supported for live demo

In the readme, say which browsers can be used for the live demo. Alternatively, say which aren't supported?
Someone reported that it wasn't working on Firefox. That should be confirmed.

I tried the demo and tried for the browser with firefox. it works!

Closing since I don't think this needs to be specified unless the demo can't work on a commonly used browser (ex. Chrome/Chromium, Firefox, Safari).  If someone reports the demo doesn't work on a popular browser and the problem won't be fixed quickly (ex. not a priority, complicated to fix), then this issue can be reopened.


mobile/docs: Publish outside of build container

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

this has been tested pretty thoroughly - successful test commit here https://github.com/phlax/envoy-mobile.github.io/commits/master


Added a parameter for getting stdout from tests easily

For tests that give insufficient error messages.

Coverage remained the same at 74.376% when pulling 8ceb5ceecb7db813413091e7b038a528df0a25d9 on Heliozoa:stdout-tests into b9bd6b938441f7fc583c51c1299344ee94817c77 on tdd-pingis:master.


identityClient is deprecated.

Several instances of using deprecated APIs including the following:

https://github.com/aws-samples/amazon-cognito-developer-authentication-sample/blob/master/src/main/java/com/amazonaws/cognito/CognitoDeveloperIdentityManagement.java#L35
https://github.com/aws/aws-sdk-android/blob/master/aws-android-sdk-cognitoidentityprovider/src/main/java/com/amazonaws/mobileconnectors/cognitoidentityprovider/CognitoUserPool.java#L168

Please update the documentation to not use deprecated functions.

No Solution Stack named '64bit Amazon Linux running Tomcat 7' found. (Service: AWSElasticBeanstalk; Status Code: 400; Error Code: InvalidParameterValue; Request ID: 4ac44532-e364-4809-a54e-71d78b888006)
is what CloudFormation says when using the S3 copy so this seems very outdated. Please update or get rid of this

@vegetabill Hi, I met the same error. Would you please share  the sample code which is workable? Thanks.


Which version to use? Latest release or master branch?

Hello.
I look forward to trying your boilerplate.
I noticed there are a lot of commits since the last tagged release from April last year.
Do you recommend I use your master branch or your latest tagged release?
Thanks much.

Master updates much faster. We still need to update all the documentation to reflect the changes since the last release before pushing the new release. I would recommend master for now


modified poll_oneoff to make it interruptible

[wip]

@wenyongh can we merge main into dev/wasi_threads once this PR is merged?

@wenyongh can we merge main into dev/wasi_threads once this PR is merged?

Sure, will do that soon.


v1.9.4

Bugfixes:

Only last transaction in the list shows execute button (https://github.com/gnosis/safe-react/pull/750)
Fix invalid values displayed for ERC20 token transfers (https://github.com/gnosis/safe-react/pull/748)
Fix decoding threshold change threshold (https://github.com/gnosis/safe-react/pull/749)

Travis automatic deployment:
https://pr754--safereact.review.gnosisdev.com/app


Insert into new static series

select ... into foo starts a new continuous query (see issue #910 about that being confusing). It'd be nice with an explicit feature to basically just copy data.
Use case:
When exploring the data you can make a small data set much smaller by filtering it on a list of attributes and then do follow-up queries on the smaller data set.

closing in favor of #1493


tmux + vim isn't working anymore :(

You can't navigate between vim and tmux terminal sessions with C-l & C-h

@scssquatch I've previously added vim-tmux-navigator in this commit a4a1f7aa2444dcf8e7186a2fbb380cf144ae1ca9. But this has since been removed. Should we add it back?

Yeah, sure!
On Sun, Feb 22, 2015 at 5:30 AM, Alan Yeo<EMAIL_ADDRESS>wrote:

@scssquatch I've previously added vim-tmux-navigator in this commit a4a1f7aa2444dcf8e7186a2fbb380cf144ae1ca9. But this has since been removed. Should we add it back?
Reply to this email directly or view it on GitHub:
https://github.com/neo/vim-config/issues/40#issuecomment-75429038


Add AssetPath::to_ref

What problem does this solve or what need does it fill?
AssetServer::load accepts AssetPath only by value and uses to_owned internally. So in order to avoid extra allocation I need to write the following:
asset_server.load(AssetPath::new_ref(
    scene_path.path(),
    scene_path.label(),
));

What solution would you like?
asset_server.load(scene_path.to_ref());

What alternative(s) have you considered?
It would be great to be able to do it like this:
asset_server.load(&scene_path);

But it's probably should be a part of a separate issue. The suggested helper AssetPath::to_ref will be re-used for it anyway.

Realized that .clone() actually creates a borrowed AssetPath.


communication with Document Server - Command url: Error: ConnectFailure (Connection refused),[object Object]

hi everyone,
OO community Server is installed on debian with apt command with the latest version
OO Document Server is installed on another debian server with apt command with the latest version (5.1.4)
From a nextcloud server we can use Document server for edit AND modify document.
But From OO community server, we just can edit Document, we can't modify documents.
in parameters panel of OO Community Server, in section "Document Service", we configure URLs to get access to document server and the URL to get back and save/store document on the community server. when we save settings, we got this message : "Command url: Error: ConnectFailure (Connection refused),[object Object]"
a trace with tcpdump, shows that HTTPS is initiated from Document Server to Community Server, but reset from Community Server without reason.
can someone help us to find a way so that it could work .....
thank you in advance

we just can edit Document, we can't modify documents.

Please specify what do you mean by "modify"

we configure URLs to get access to document server and the URL to get back and save/store document on the community server.

Please make sure that the address of the Document Server is available from the Community Server.

oh modify means :  save the modification of a document
Document Server is available for Community Server. In fact, the problem is in the other way, from DS to CS.
i add some configuration in file "web.appsettings.config" as documentation at this url specify !!
wget from Document Server to Community Server works !
the only message is when i save settings in panel parameters -> 'Document Server", the error is in object of this issue : Command url: Error: ConnectFailure (Connection refused),[object Object]

sorry for disturbing the crew. bu tin fact, configuration in file "web.aapsettings.config" was wrong.
everything is OK now.


修改获取内网ip方式，修复登陆失败问题

校园网登陆字段：wlan_user_ip=<IP_ADDRESS>
原来通过生成UDP包，然后从中获取的ip为：wlan_user_ip=<IP_ADDRESS>
导致返回
[INFO ] Sign in as 168xxxx@cmcc <IP_ADDRESS>(000000000000) linux-firefox ...
[INFO ] Attempt (1/3): {"result":"0","msg":"","ret_code":1}
[INFO ] Attempt (2/3): {"result":"0","msg":"","ret_code":1}
[INFO ] Attempt (3/3): {"result":"0","msg":"","ret_code":1}

所以改用通过主机名获取内网ip为：wlan_user_ip=<IP_ADDRESS>
符合登陆预期
[INFO ] Sign in as 168xxxx@cmcc <IP_ADDRESS>(000000000000) linux-firefox ...
[INFO ] Attempt (1/3): {"result":"1","msg":"\u8ba4\u8bc1\u6210\u529f"}
[INFO ] Attempt (2/3): {"result":"0","msg":"","ret_code":2}
[INFO ] Succeed. Have fun :)

感谢解答


Modify a typo at "Adaptive real time tuning".

I think "Adaptive real time tuning" is a DDoS Standard function, so i modify  a typo from Basic to Standard.

@mattu0119 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mattu0119 - Hi! Thank you for the feedback and you are correct. The article you found is outdated and should have been archived. I'll make sure the article gets archived. Please reference this article for DDoS best practices: https://docs.microsoft.com/en-us/azure/ddos-protection/fundamental-best-practices.
#please-close


availabilityStartTime not constant for dash streaming

I initially thought this was a client-side issue, so I opened up https://github.com/Dash-Industry-Forum/dash.js/issues/497, but from that thread I'm lead to believe the issue is on the server-side.
Essentially they client is able to successfully stream a dash stream up until a certain point when the mpd files start having increasing availabilityStartTimes, at which point the client starts repeating the last few parts it received. According to that thread the availabilityStartTime is supposed to be constant. Is that true? And if so is this a bug on the module's end?

I am having the same problem. I made a fork here: https://github.com/codenoise/nginx-rtmp-module.
I am still having the same problem described, but less so. Now the timeshiftBufferDepth is 30 seconds and the availabilityStartTime is constant through the session. Can you test and see if it changes your results? If not, perhaps the dash.js issue needs to be reopened.

Thanks so much for the help! :) unfortunately your fork didn't work for me, the dash.js player plays for a few seconds then starts looping over the same spot over and over. I noticed that the startAvailabilityTime starts increasing after a bit still, even with your fork, so maybe that could be a reason? A kind of agree though, I feel like this issue is on dash.js, it doesn't make sense to me that availabilityStartTime shouldn't shift, it seems to me like that value describes the time range for which there is available "footage", and that will change over time as nginx cleans up old parts.

Interesting. How much time passes before the startAvailabilityTime changes? I have a 10 minute stream that I play, and it stays constant for me. I agree with you that it would seem the startAvailabilityTime should change to match the window of availability for the chunks in the manifest.

I would guess no more than 10-15 seconds. I'll double check when I get
home. I'm doing an "endless" desktop stream using obs, if that effects
anything.
On Thu, Apr 23, 2015 at 1:17 PM, Joe Fox<EMAIL_ADDRESS>wrote:

Interesting. How much time passes before the startAvailabilityTime
changes? I have a 10 minute stream that I play, and it stays constant for
me. I agree with you that it would seem the startAvailabilityTime should
change to match the window of availability for the chunks in the manifest.
—
Reply to this email directly or view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/614#issuecomment-95659702
.

I am also facing the same issue with Dash.js player. The stream will stop after 5-10 seconds and it won't play after that. As #mediocregopher  mentioned - I thought it was a client side issue (dash.js) too ; as stream was playing fine on bitdash player. But I came to know from dash forum that it's because of the "availabilityStartTime". I thought to look for available solution before I start digging the code to create a patch, so ended up on the forum.
Let us know if we have a patch in progress for the issue, else I am planning to write a patch not to update the "availabilityStartTime".
Cheers,
Shishir

Any progress with this issue? I'm having the same problem.

I decided to try to fix it myself. I created a patch that freezes availabilityStartTime and adjusts timeShiftBufferDepth. It seems to fix the problem for live streams in my case. Feel free to test and use it.
https://github.com/mattpepin/nginx-rtmp-module/commit/c078a7c3e08b5b2cbe74f4694e48e5a1ff372fb3

@mattpepin That is a great commit! Thanks for doing that! It solved our streaming problem.

I'll go ahead and close this, sounds like the problem has been solved. Thanks mattpepin!


Add PCRE2 support to ModSecurity v2

The legacy PCRE implementation (more recently referred to as PCRE1) is no longer being updated, with v8.45 (from June 2021) expected to be the final version.
Also, Apache HTTP Server recently (as of 2.4.53) changed to support PCRE2.
Given the above, ModSecurity v2.9.x should be updated to support PCRE2 (as has already been done for the ModSecurity v3 branch via #2668 ).

That would be highly welcome. We are observing the way PCRE1 becomes obsolete and would welcome a shift to PCRE2 for ModSec 2.9.

The legacy PCRE implementation (more recently referred to as PCRE1) is no longer being updated, with v8.45 (from June 2021) expected to be the final version.
Also, Apache HTTP Server recently (as of 2.4.53) changed to support PCRE2.
Given the above, ModSecurity v2.9.x should be updated to support PCRE2 (as has already been done for the ModSecurity v3 branch via #2668 ).

@martinhsv , Could you give us a tentative date for this undertaking?
Is just merging #2668 to v2 branch enough to add support of PCRE2?
Regards,
Vinay

Hello @vinaykumarlaxman ,
This item is considered to be fairly high priority. However, providing a precise date is not possible. I expect to work on this soon, but all items are potentially subject to higher-priority items arising.
No, it is not a simple matter of merging the v3 changes. For one thing, ModSecurity v3 is written in C++, while ModSecurity v2 is written in C.

The PCRE2 functionality for ModSecurity v2 with Apache is now available for use.
The configure step by default will still attempt to use the legacy pcre1. If you wish to build with pcre2, you can use
./configure --with-pcre2

Note that implementation work so far includes the main functionality as well as mlogc, but so far not:

the optional PCRE2 Jit functionality
build infrastructure for ModSecurity for IIS
the separate alp2 audit parser lib (Is anybody still using this? It looks obsolete?)


More catalog

Clear catalog store on cluster change
No shortcuts if there's a form on screen
Fix checkbox, click entire container, no nested labels, keyboard events
Upgrade auto-install charts on update, requires chart support, auto-version by name support
Button & font size consistency
Chart colors
Repo detail page
Faster container logs rendering

Depends on rancher/rancher#28733

Merging in tandem with https://github.com/rancher/rancher/pull/28733


After Installtion Problem

After installation become this error message:
#> HmcRestClient
Traceback (most recent call last):
  File "/bin/HmcRestClient", line 9, in <module>
    load_entry_point('HmcRestClient==1.0', 'console_scripts', 'HmcRestClient')()
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 378, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2566, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2260, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/usr/lib/python2.7/site-packages/HmcRestClient-1.0-py2.7.egg/src/main/Main.py", line 18, in <module>
    from src.main.HmcRestClient import *
  File "/usr/lib/python2.7/site-packages/HmcRestClient-1.0-py2.7.egg/src/main/HmcRestClient.py", line 21, in <module>
    from src.generated_src import UOM
  File "/usr/lib/python2.7/site-packages/HmcRestClient-1.0-py2.7.egg/src/generated_src/UOM.py", line 24, in <module>
    raise pyxb.PyXBVersionError(_PyXBVersion)
pyxb.exceptions_.PyXBVersionError: 1.2.4

Can you help me?

Install using the correct pyxb version.
# pip install pyxb==1.2.4
Collecting pyxb==1.2.4
  Downloading PyXB-1.2.4.tar.gz (8.7MB)
    100% |████████████████████████████████| 8.7MB 123kB/s
Installing collected packages: pyxb
  Running setup.py install for pyxb ... done
Successfully installed pyxb-1.2.4


android scanning code128 barcode decodes to something different

Hi guys, I'm liking the package so far but I'm struggling with something. While using a CS6080 scanner as an HID keyboard via BT, I'm scanning a CODE128 barcode:

The barcode should decode to: 3BE9604F-9E76-42F8-A584-288AD1B7D087
When I scan this barcode on a notes app on both android and iOS it scans the whole barcode correct, so the scanner is working as expected. But on my flutter android app it decodes to: #Be960$f-(e76-4@f8_a584-28*Ad!b&d087
I've tried debugging the package a little and it looks like it might be because of a shift key or something like that.
On iOS however it seems to be working perfectly.
Can you guys possibly help me out? Feel free to reach out so I can help further.

I am having the same issue, did you find a solution ?

No, the problem seemed to be in the way keys are pressed on the different OS. From what I can remember shift keys were the problem. I didn't have the time to figure out a solution for this issue, I guess the best thing you can do is make sure barcodes are simple...

No, the problem seemed to be in the way keys are pressed on the different OS. From what I can remember shift keys were the problem. I didn't have the time to figure out a solution for this issue, I guess the best thing you can do is make sure barcodes are simple...

With shift keys you mean to avoid sending any symbols like -{,:"}@ ?

No, my scanner was acting like a keyboard. A capital letter a would be Shift + a . That would give me issue, you can always log or debug the package to learn what exactly happens to the barcode that you scan.

I have same issue. Outside the app, the barcode is recognized correctly. Just using this package I get incorrect decodings.
For example, barcode 4000_TRA_TRAILER01 decodes as 400)_TRA_TRAILEr01. Any ideas?

I have had the same problem. Enable flag useKeyDownEvent did work for me.
BarcodeKeyboardListener(
    useKeyDownEvent: true,
    bufferDuration: const Duration(milliseconds: 2500),
    onBarcodeScanned: (barcode) async {},
)


Semi-optional CancellationToken

Whilst I can get it to work in C# without the Token, it seems that it is necessary in VB.

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

ID: ddcbc767-2ed7-b376-51fe-34c13fe7b391
Version Independent ID: 86e0dc6a-aea6-5baa-c6a2-d016ffd7445a
Content: BlobContainerClient.Exists(CancellationToken) Method (Azure.Storage.Blobs) - Azure for .NET Developers
Content Source: xml/Azure.Storage.Blobs/BlobContainerClient.xml
Service: azure
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

@DavidCameron33 We are looking into it and get back to you for any additional information.

Hello @DavidCameron33 Thanks for the info!
Please add more information on the VB, if any snippets or logs showing the error?
Routing to the Service team for further action!

@DavidCameron33, we have overloads for every Storage SDK API where CancellationToken is option.  For example - https://github.com/Azure/azure-sdk-for-net/blob/f0d1a30fc0164389c137b8c782901cb214c3c623/sdk/storage/Azure.Storage.Blobs/src/BlobContainerClient.cs#L1573


Interested in passing custom data to the Team Invite

Would yall be interested in accepting a PR that will allow custom data to be stored on the Team Invite?
I want to be able to invite someone with a specified role that can be attached when they sign up.

If you create a PR I'll take a look at it.

+1


Revert PR #5037

This PR reverts changes made here https://github.com/Expensify/App/pull/5037
Details
Fixed Issues
$ https://github.com/Expensify/App/issues/5285
Tests
None
QA Steps
None.
Tested On

[ ] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

🚀 Cherry-picked to staging by @luacmartins in version: 1.0.99-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @Jag96 in version: 1.1.0-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


cmd/compile: branchelim broke golang.org/x/exp/shiny/ on amd64

Reported at https://go-review.googlesource.com/c/go/+/98695
go get -u golang.org/x/exp/shiny/iconvg
results in
../../gopath/src/golang.org/x/exp/shiny/iconvg/buffer.go:190:19: internal compiler error: Flag* ops should never make it to codegen v16 = FlagLT_ULT <flags>

goroutine 4 [running]:
runtime/debug.Stack(0x0, 0x0, 0x0)
        /localdisk/itocar/mainline_golang/go/src/runtime/debug/stack.go:24 +0xa7
cmd/compile/internal/gc.Fatalf(0xc5409c, 0x2c, 0xc001096670, 0x1, 0x1)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/subr.go:182 +0x1f7
cmd/compile/internal/gc.(*ssafn).Fatalf(0xc0007cdbf0, 0xae2300000194, 0xc5409c, 0x2c, 0xc001096670, 0x1, 0x1)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/ssa.go:5326 +0x67
cmd/compile/internal/ssa.(*Value).Fatalf(0xc00092c700, 0xc5409c, 0x2c, 0xc001096670, 0x1, 0x1)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/ssa/value.go:268 +0x77
cmd/compile/internal/amd64.ssaGenValue(0xc001154540, 0xc00092c700)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/amd64/ssa.go:1029 +0x4dca
cmd/compile/internal/gc.genssa(0xc000b7b400, 0xc0003960a0)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/ssa.go:4681 +0x425
cmd/compile/internal/gc.compileSSA(0xc0003a1500, 0x0)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/pgen.go:267 +0x176
cmd/compile/internal/gc.compileFunctions.func2(0xc00091afc0, 0xc0003c3f30, 0x0)
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/pgen.go:309 +0x49
created by cmd/compile/internal/gc.compileFunctions
        /localdisk/itocar/mainline_golang/go/src/cmd/compile/internal/gc/pgen.go:307 +0x11a

on master.
It was bisected to CL 98695

/cc @eliasnaur  @rasky

Disabling branchelim pass on amd64 breaks a bunch of codegen tests. Should we revert CL for now?

If a CL broken branchelim I would revert the CL, not disable branchelim. Or what you mean is that the CL is actually correct but it exposed a latent bug in branchelim, so it's branchelim that is at fault and it should be disabled?

I remember that for some broken optimization, instead of reverting commit, we added something like
return // disabled until issue... is fixed

cc @randall77 @cherrymui for decision.

The CL was reverted (see 199755), and there is no evident that the whole pass is at fault, so I think we can close this.

Sorry for that, I'll look into it.
Does breaking shiny qualify as "breaking the build"? What should I test in future to make sure that, if it passes, the CL doesn't get reverted but instead a bug is opened for followup fixes?

"Breaking the build" in general means builders (https://build.golang.org) failures... but for codegen CLs the compiler crashing on any kind of valid Go code is pretty much "breaking the build", I fear.

make sure that [..] the CL doesn't get reverted but instead a bug is opened for followup fixes

Compiler crashes on any valid Go code almost always get reverted, unless the issue is obvious and can be fixed immediately in a follow-up CL.

Compiler crashes on any valid Go code almost always get reverted

That's quite aggressive, especially since we're very early in the development cycle. The issue was obvious to me in this case. Anyway, I just mailed the CL (https://go-review.googlesource.com/#/c/100935/).
BTW, for everybody's entertainment, this bug actually highlighted a bug in the shiny's code :) I've sent a CL for that as well.

That's quite aggressive, especially since we're very early in the development cycle.

The problem is that there are many people working on the repository daily, and no one wants to work with a compiler that is known to be subtly broken. Even more so if you consider that the tip compiler compiles itself and then everything else in the repository. That's why CLs that have demonstrably broken the compiler usually get reverted very quickly.

Does breaking shiny qualify as "breaking the build"? What should I test in future to make sure that, if it passes, the CL doesn't get reverted but instead a bug is opened for followup fixes?

Unfortunately, there's no easy way to detect this beforehand, as shiny isn't compiled by all.bash.  Our test suite will never be perfect, and as in this case bugs will be detected post-checkin through some ad-hoc process.

That's quite aggressive, especially since we're very early in the development cycle. The issue was obvious to me in this case. Anyway, I just mailed the CL (https://go-review.googlesource.com/#/c/100935/).

If you can make a fix in a timely manner, that's ok also.  You just have to beat the reverters to it.  It's ok to say "hold up on that revert, I have a fix coming in the next hour".
Don't get too hung up on having to revert.  It happens to the best of us.  Lord knows I've reverted quite a few of my changes.  It's a bit more work but it reduces the window where someone else synced to a broken compiler, tried to do some work, and got failures than ended up unrelated to the work they were doing.


[20.09] pythonPackages.mock-open: 1.3.1 -> 1.4.0

Motivation for this change
backport of #98313

ZHF: #97479 (1.3.1 -> 1.3.2) e3aa742

mock-open 1.3.1 had failing tests on Python ≥ 3.7 (nivbend/mock-open#7) that were fixed with 1.3.2 (nivbend/mock-open@2da5008fa55997d5fbf4aff5ec4679a548a587ec)

upgrade to latest upstream release (1.3.2 -> 1.4.0) f19d0ea

requires patch from nivbend/mock-open#10 for Python 2.7

Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)

(there are none)
(smoke-tested the resulting python lib on Python 2.7, 3.7, 3.8 instead)

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

:x: meta.maintainers is not set

Result of nixpkgs-review pr 98347 1

3 packages built:

python27Packages.mock-open
python37Packages.mock-open
python38Packages.mock-open


Update esp_wifi.rst (IDFGH-4634)

Fixed typo

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @maya2003 , thanks for point out the typos. We will add this fix with some others documentations update within one commit, so this PR will probably not be merged.


core-js should be listed as a dependency

When trying to run through apollo-server I get this error.
Error: Cannot find module 'core-js/modules/es7.object.entries'     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)     at Function.Module._load (internal/modules/cjs/loader.js:507:25)     at Module.require (internal/modules/cjs/loader.js:637:17)     at require (internal/modules/cjs/helpers.js:20:18)     at Object.<anonymous> (/Users/fleveillee/Projects/yuAPI/node_modules/apollo-upload-server/lib/middleware.js:14:1)     at Module._compile (internal/modules/cjs/loader.js:689:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)     at Module.load (internal/modules/cjs/loader.js:599:32)     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)     at Function.Module._load (internal/modules/cjs/loader.js:530:3)     at Module.require (internal/modules/cjs/loader.js:637:17)     at require (internal/modules/cjs/helpers.js:20:18)     at Object.<anonymous> (/Users/fleveillee/Projects/yuAPI/node_modules/apollo-upload-server/lib/index.js:19:19)     at Module._compile (internal/modules/cjs/loader.js:689:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)     at Module.load (internal/modules/cjs/loader.js:599:32)
Does not happen to me in dev since I use babel, that requires core-js only if I run yarn --production
Workaround: Temporarily adde 'core-js' as a prod requirement
/lib/middleware.js line 14
require('core-js/modules/es7.object.entries')

This is a duplicate of #103. @jaydenseric even though this is fixed, perhaps we should publish a v5.0.1 which is identical to v5.0.0 but specifies this as a dependency?

This issue is fixed in the last two published releases. As mentioned, this issue duplicates https://github.com/jaydenseric/apollo-upload-server/issues/103 so lets focus discussion there 🙏

Thanks a lot for the prompt response!


Alternative to sudo, for remote podman

When transitioning from the sudo varlink bridge to the new rest API, is there an alternative to logging in as root with ssh ?
Like adding a "podman" root-equivalent group, or starting the "podman.sock" socket as some other privileged user* perhaps.
* I think CoreOS is doing this (for the core user) ?
Running rootless isn't the question here, it's about root.

Basically wondering what to use for the CONTAINER_HOST
Here is how they are using DOCKER_HOST (i.e. for docker):

If you have ssh login for root on the remote machine set export<EMAIL_ADDRESS>(may be considered bad security practices)
To use a non-root user user set export<EMAIL_ADDRESS>after adding user to the docker group using sudo usermod -aG docker user. (tested on Ubuntu 18.04)

Also enquiring about the usual approach to run local podman, currently using passwordless sudo to do it (sudo -n podman)

@afbjorklund we talked about this just last week.  Probably still looking for a solution here.  What are your thoughts or what do you favor.

I think root logins might be disabled by default, so I would need to enable them
PermitRootLogin prohibit-password
And then copy the authorized keys during boot, from the user to the /root dir.
mkdir /root/.ssh
chmod 700 /root/.ssh
cp /home/docker/.ssh/authorized_keys /root/.ssh/
chmod 600 /root/.ssh/authorized_keys

I'm not sure what the implications of chown'ing the podman.sock is, or how you do it.
For dockerd I think it just uses the default settings, which uses the docker group.
  -G, --group string                            Group for the unix socket (default "docker")

Would you edit the user (or group) in the systemd unit somewhere perhaps ?
[Socket]
ListenStream=%t/podman/podman.sock
SocketMode=0660

https://www.freedesktop.org/software/systemd/man/systemd.socket.html

SocketUser=, SocketGroup=
Takes a UNIX user/group name. When specified, all AF_UNIX sockets and FIFO nodes in the file system are owned by the specified user and group. If unset (the default), the nodes are owned by the root user/group (if run in

For minikube/machine, there is a user called "docker" who is part of group "docker".
It's also a member of the group "wheel", which will enable it to use sudo at will...
/etc/sudoers
root ALL=(ALL) ALL
%wheel ALL=(ALL) NOPASSWD: ALL

The group might also be called "sudo" (in Ubuntu), but it works the same way.

Currently we are using this, to run sudo varlink bridge to activate io.podman socket
And then we prefix all commands that are run over ssh, like: sudo -n podman load.
It would probably have been easier to add a "podman" root group, but it seemed undesired ?
All the podman documentation refers to running "sudo podman" (unlike running just "docker")

Currently, if I run the new podman-remote (2.0.1) it will silently fall back to building the images locally instead. :-(
The previous versions (2.0.0) would give an error, after trying to contact a local socket - rather than use the varlink...
Error: Get http://d/v1.0.0/libpod../../../_ping: dial unix ///run/user/1000/podman/podman.sock: connect: no such file or directory
So one either has to use old podman-remote (1.9.3, since 1.8.x hangs) or we need to add support for this new socket.

I am fine with creating a podman group and adding write access to the socket, but not by default,  This would have to be configured in the containers.conf with strong words about how dangerous this is.
Setting up podman group access to the root running podman, is equivalent to giving sudo without password access to root, and potentially worse.
Is there something we could do as an alternative with systemd?  IE I turn on the systemd podman.sock socket for a particular user and it sets up permissions for just this user.
Bottom line, I would want this to be specific to the remote service over ssh rather then something local users of a linux system start doing.

It seems to work, if starting the socket manually and changing the owner (also on the directory, not only the socket)
But one has to add the --remote (even to podman-remote), and one has to add the path and the param.
And it seems like $CONTAINER_HOST stopped working, so have to use --url "$CONTAINER_HOST" for it to work.
podman-remote --remote --url $CONTAINER_HOST version

The non-working podman-remote and the missing podman.socket was due to the Ubuntu 20.04 packaging (not using make)
When building from source, both are OK. That is, the binary does have the buildflags and the APIv2 services do get installed...

@jwhonce
Now that podman-machine doesn't work anymore, here is how to do the set up with vagrant:
Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "fedora/32-cloud-base"

  config.vm.provider "virtualbox" do |vb|
    vb.memory = "1024"
  end

  config.vm.provision "shell", inline: <<-SHELL
    yum install -y podman

    groupadd -f -r podman

    #systemctl edit podman.socket
    mkdir -p /etc/systemd/system/podman.socket.d
    cat >/etc/systemd/system/podman.socket.d/override.conf <<EOF
[Socket]
SocketMode=0660
SocketUser=root
SocketGroup=podman
EOF
    systemctl daemon-reload
    echo "d /run/podman 0770 root podman" > /etc/tmpfiles.d/podman.conf
    sudo systemd-tmpfiles --create

    systemctl enable podman.socket
    systemctl start podman.socket

    usermod -aG podman $SUDO_USER
  SHELL
end

This installs podman, and adds a "podman" system group with socket access (like docker).
Then one can use vagrant up to boot it, and vagrant ssh-config to get the configuration.
Important variables from ssh_config:
Host default
  HostName <IP_ADDRESS>
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile $PWD/.vagrant/machines/default/virtualbox/private_key
  IdentitiesOnly yes
  LogLevel FATAL

Then we export CONTAINER_HOST=ssh://vagrant@<IP_ADDRESS>:2222/run/podman/podman.sock
and export CONTAINER_SSHKEY=$PWD/.vagrant/machines/default/virtualbox/private_key
Which enables us to access it remotely (unfortunately --remote is still broken and --url required)
But if we make sure to use the old special binary and pass explicit parameters as a workaround:
$ podman --remote version
Version:      2.0.2
API Version:  1
Go Version:   go1.14.2
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64
$ podman-remote version
Error: Get "http://d/v1.0.0/libpod../../../_ping": dial unix ///run/user/1000/podman/podman.sock: connect: no such file or directory
$ podman-remote --url "$CONTAINER_HOST" --identity "$CONTAINER_SSHKEY" version
Client:
Version:      2.0.2
API Version:  1
Go Version:   go1.14.2
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

Server:
Version:      2.0.2
API Version:  0
Go Version:   go1.14.3
Built:        Thu Jan  1 01:00:00 1970
OS/Arch:      linux/amd64

The vagrant .box is about the same size as the fedora .iso (250% boot2podman)
290M    Fedora-Cloud-Base-Vagrant-32-1.6.x86_64.vagrant-virtualbox.box

For linux users it is also possible to use the libvirt/kvm box instead of virtualbox.
See https://vagrantcloud.com/search and https://alt.fedoraproject.org/cloud/

Full example here: https://boot2podman.github.io/2020/07/22/machine-replacement.html
It looks like the "tmpfiles.d" was the missing piece, when it came to changing the group...

@ashley-cui PTAL

For what it is worth, the systemd units are still missing in podman 2.0.6~1 as well.
It only has the varlink units:
/usr/lib/systemd
/usr/lib/systemd/system
/usr/lib/systemd/system/io.podman.service
/usr/lib/systemd/system/io.podman.socket
/usr/lib/systemd/user
/usr/lib/systemd/user/io.podman.service
/usr/lib/systemd/user/io.podman.socket

Gives error: Failed to enable unit, unit podman.socket does not exist.

You mean they are not shipped within an RPM?

@lsm5 PTAL

@afbjorklund 2.0.6~2 fixes the issue of unitfiles. https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/podman . PTAL.

Thank you, works now.
    default: Created symlink /etc/systemd/system/sockets.target.wants/podman.socket → /lib/systemd/system/podman.socket.

We now have two working solutions, either connect as root@ and use the default - or change the group and use<EMAIL_ADDRESS>I'm not sure if you want to document it anywhere on podman.io, but now we have a solution to replace the sudo varlink:
export PODMAN_VARLINK_BRIDGE="/usr/bin/ssh -F /dev/null -o ConnectionAttempts=3
-o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet
-o PasswordAuthentication=no -o ServerAliveInterval=60 -o
StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null<EMAIL_ADDRESS>-o
IdentitiesOnly=yes -i /home/anders/.minikube/machines/minikube/id_rsa -p 34749
-- sudo varlink -A \'podman varlink \\\$VARLINK_ADDRESS\' bridge"

export CONTAINER_HOST=ssh://docker@<IP_ADDRESS>:34749/run/podman/podman.sock
export CONTAINER_SSHKEY=/home/anders/.minikube/machines/minikube/id_rsa

So you can close the ticket...
But I think we will wait for 2.1.

Note that in the case of minikube we are using podman to load images for crio, that is why the root requirement here...
There's  also some missing pieces in the minikube OS, in order to run rootless containers (mainly because it wasn't needed)
docker@minikube:~$ podman pull busybox
Trying to pull docker.io/library/busybox...
Getting image source signatures
Copying blob df8698476c65 done
Copying config 6858809bf6 done
Writing manifest to image destination
Storing signatures
ERRO[0004] Error while applying layer: ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 65534:65534 for /home): lchown /home: invalid argument
  ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 65534:65534 for /home): lchown /home: invalid argument
Trying to pull quay.io/busybox...
  error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>404 Not Found</title>\n
Not Found
\n
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
\n"
Error: unable to pull busybox: 2 errors occurred:
	* Error committing the finished image: error adding layer with blob "sha256:df8698476c65c2ee7ca0e9dbc2b1c8b1c91bce555819a9aaab724ac64241ba67": ApplyLayer exit status 1 stdout:  stderr: there might not be enough IDs available in the namespace (requested 65534:65534 for /home): lchown /home: invalid argument
	* Error initializing source docker://quay.io/busybox:latest: Error reading manifest latest in quay.io/busybox: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>404 Not Found</title>\n
Not Found
\n
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
\n"

But we do allow the user to run containers with podman, mostly to avoid them having to run two VMs (1 podman, 1 k8s).

@afbjorklund looks like you've found working solutions, so i'm going to close this issue. Re-open if there's more to be done here.

@ashley-cui : yes, the only thing remaining is to actually do it (code). Should have podman support back for next major release.


Implement VerifySlantAlphaOnPTLD2

https://github.dev/neilenns/PlanVerifier/blob/694b0a65d0a7b99b54a3216007f8e48deab2d938/PlanVerifier/Verifiers/VerifySlantAlphaOnPTLD2.cs#L1

This isn't needed, there's a jetsOnlyOnRNAV test that covers the same ground.


How delete unused/old images

Hi
I install Portus using docker-compose and I use version 2.4.0-dev
From GUI I can only remove tags but I can't remove image and clean disk.
It is normal ? How can I remove old images ?
In config.yml in registry directory I have this:
storage:
filesystem:
rootdirectory: /var/lib/registry
delete:
enabled: true
What is "delete" option ?

I think that this is better explained on the documentation.
First of all, from the Portus point of view you have a delete option. This option adds the UI for removing namespaces, repositories, tags, etc. At the same time, you have to have the delete option enabled from the registry point of view (as you have on your configuration). This way, the registry will allow Portus to remove manifests from the registry. This way, when performing a delete action from Portus, the repository or tag that you decided to delete won't appear in Portus.
That being said, the blobs won't be removed from the registry.
Hope that I've clarified things for your :smile:


Django Rest framework swagger base url Https

I have successfully running my rest framework swagger on localhost.. These was my rest framework swagger localhost screenshoot. It has run successfully.

Now i want to deploy it on server testing. These is the screenshot result of my testing deployment.

As you can see the base path changed and served from localhost, the schemes read the right configuration which is https schemes, and the application run in the right domain which is api.executivemafia.com, so that's not problem. The problem come when I want to try the API. The server point is localhost. So it's make my endpoint request become 'https://<IP_ADDRESS>:8000/instagram/hello".
My questions are:
Why the rest framework swagger still read localhost although my application already served in https://api.executivemafia.com/docs/? Fyi, I set the proxy pass nginx to locahost:8000 because my gunicorn run on localhost:8000.
Can the base url rest framework swagger testing server using my testing server domain end point ? If it's able to, how to do it?
Any help and reference will be appreciated.
I am using django-rest-swagger version 2.2.0
Thank you Guys!!
Regards,
Meikelwis Wijaya

Solved by adding these line in my nginx configuration
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
# we don't want nginx trying to do something clever with
# redirects, we set the Host: header above already.
proxy_redirect off;

Have you solved this problem?


detect_intent_texts gives empty list_value

"detect_intent_texts" method returns empty list_value in "response.query_result.parameters"

I have seen this happening when the agent is created thru api. You may do one of the two below as a work around:
Option 1. Open the intent that is returning empty parameters and just save the intent once. Agent will start the training and after a few seconds will complete training
Option 2: Make the parameter mandatory (especially if you are creating the intent/agent thru api call) in the Action and Parameter session while creating the intent

This appears to be answered, if not, please feel free to re-open.
Thanks! :)

I have seen this happening when the agent is created thru api. You may do one of the two below as a work around:
Option 1. Open the intent that is returning empty parameters and just save the intent once. Agent will start the training and after a few seconds will complete training
Option 2: Make the parameter mandatory (especially if you are creating the intent/agent thru api call) in the Action and Parameter session while creating the intent

@babujipa thanks, #1 seems to work. Is there any workaround that can be done through code though ?

Yes. If you are generating the intent thru code , make that parameter mandatory and it will work

@babujipa Could you please give me pointers on how to make parameter mandatory through code, I couldn't find any example.  Do we do it through the intent call itself ?
This is my intent creation call
dialogflow_v2.types.Intent(         display_name=display_name,         training_phrases=training_phrases,         messages=[message])
I see that this has a parameter called "parameters".
parameters:         Optional. The collection of parameters associated with the         intent.
I tried inserting a dictionary here but it has some protobuf error. Is this the correct direction ?

You may have modify the code below to fit into your program
############################
name = intent.name
myintent = intents_client.get_intent(name,intent_view=dialogflow.enums.IntentView.INTENT_VIEW_FULL)
myintent.Parameter.mandatory = True
lang='en'
response  = intents_client.update_intent(myintent, lang)
###########################


fix(backgroundEvents): clamp background event start and end to dayBoundaries

closes #827
all 999 (nice) unit tests pass and desired functionality described in #827 works. Tested on chrome and firefox.
having a combination of backgroundEvents and dayBoundaries now works as expected (see gray bars at the start and end of days, these are background events, showing "out of office" hours):

this is how it looks without the fix - the starts of backgroundEvents are not rendered correctly (see missing gray bars at the top of each day, and completely missing full day gray bars at the weekend)

the reason this happened was because getYCoordinateInTimeGrid() and getEventHeight() functions used backgroundEvent.start and backgroundEvent.end times. Whereas when dayBoundaries are used, we should use start/end of the dayBoundary and not of the backgroundEvent.
as i'm very fresh to the codebase, something might have been missed!

Awesome, works nicely!
I removed the adjustment of the end time, because the event overflowing is a trade-off I accept for saving some complexity. The complexity that would have had to be added, is to check first if the dayBoundaries create what I call a "hybrid day", e.g. 18:00-06:00, and then handle the clamping differently depending on whether it is such a hybrid day or not.


I want to use 'cmd+shift+/' to switch the block comment, but I find the key is bound to the help menu and can't be unbound,  what should I do?

VSCode Version: Code 1.17.2 (b813d12980308015bcd2b3a2f6efa5c810c33ba5, 2017-10-16T13:47:41.889Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

bracket-pair-colorizer
Coe
0.10.9

html-snippets
abu
0.1.0

vscode-caniuse
aka
0.5.3

project-manager
ale
0.22.0

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-npm-script
eg2
0.3.1

smarty
imp
0.2.0

vue
jcb
0.1.5

vetur
oct
0.10.1

vscode-icons
rob
7.16.0

svg-snippets
sid
1.0.1

open-in-browser
tec
1.1.0

Steps to Reproduce:

Reproduces without extensions: Yes/No

@DaleHe which keyboard layout are you using?

This is a built-in feature of mac applications, showing up in Google Chrome, VS Code and Parallels from the applications I have tested:

Please search online for how to disable this feature in your OS.

fyi @bpasero

@alexandrudima Yes, you are right! The key is bound by my mac. I changed my system's keyboard settings, and then, it works! Thank you so much!


Week 8 : set up ci  tool

use github actions to set the pipeline up for github actions and use quay.io as the container registry

set up github actions for continous integration with quay.io as the container registery


Fix HTTP/2 disablement

In commit 4371417 we disabled HTTP/2 by default as a remediation for CVE-2023-39325. An HTTP connection test using curl suggested at the time that the server only accepted HTTP/1.1 even though the client offered h2 and HTTP/1.1:
$ curl --http2 https://localhost:8443 2>&1 | grep -i alpn
* ALPN: offers h2,http/1.1
* ALPN: server accepted http/1.1

It so happens that the peers can still negotiate h2:
$ openssl s_client -connect localhost:8443 -alpn "h2"
[...]
ALPN protocol: h2
[...]

This commit fixes this issue, completely disabling HTTP/2 for good now:
$ for PROTO in h3 h2 http/1.1 http/1.0; do openssl s_client -connect localhost:8443 -alpn "${PROTO}" 2>/dev/null | grep -i alpn; done
No ALPN negotiated
No ALPN negotiated
ALPN protocol: http/1.1
No ALPN negotiate

@adrianchiris please take a look.


Enhancing Prometheus metrics for BW consumption

As part of https://github.com/celestiaorg/celestia-app/issues/2197, in order to be able to calculate the breakdown of BW consumption per chain ID and reactor, we would like to use to the existing Prometheus metrics in cekestia-core. However, it is not clear whether the current metrics are sufficient and whether we may require additional metrics to accomplish the task.
This issue intends to track the progress of this effort.

Currently, Prometheus collects the sent and received BW, however, they lack two major labels: Channel id and the reactor. So we need to integrate these two.

In the existing implementation, there is a single reactor associated with each channel ID. Therefore, we can deduce the reactors based solely on the channel ID label. Given this, our approach will involve appending only the channel ID label to each metric.
References:
https://github.com/celestiaorg/celestia-core/blob/2f93fc823f17c36c7090f84694880c85d3244764/node/node.go#L633-L637
https://github.com/celestiaorg/celestia-core/blob/2f93fc823f17c36c7090f84694880c85d3244764/node/node.go#L690
https://github.com/celestiaorg/celestia-core/blob/2f93fc823f17c36c7090f84694880c85d3244764/node/node.go#L153-L158

In the existing implementation, there is a single reactor associated with each channel ID.

Is this guaranteed for future modifications to CometBFT? Is there a downside to including two labels?

Is this guaranteed for future modifications to CometBFT?

The 1:1 correspondence between reactors and channel IDs is not strictly enforced by the current implementation, as custom reactors can be added to switches on any channel ID. However, it is probable, based on past trends, that the one-to-one mapping will continue to be maintained in the future (although not guaranteed with 100% certainty).

Is there a downside to including two labels?

Thank you for your suggestion. Our current implementation, which tracks channel ID, adequately addresses the requirements of this issue. Adding an extra label could introduce redundancy and complexity without a significant improvement in observability.
Our initial goal was to minimize modifications to the existing Prometheus metrics. Currently, we monitor sent and received bytes at the peer level, the central point of communication with peers. Extending this observability to specific reactors would require changes at higher levels, increasing the scope significantly. The reason is that in the peer level there is no observability into the reactors to which/from which the message sent. Identifying the exact reactor needs to be done in higher level components, and the surface would much larger.
While enhancing observability by identifying reactors is possible,  the current approach was opted to maintain simplicity and efficiency while meeting the objectives of this issue.

apparently, no two reactors can share the same channel ID as suggested in https://github.com/celestiaorg/celestia-core/blob/3f3b7cc57f5cfc5e846ce781a9a407920e54fb72/p2p/switch.go#L166

if I recall correctly, I've been able to determine the bandwidth used before via channel ID, but would have to dig through the metrics. Will hopefully be able to do that later today depending on if I can get the network tests working again

if I recall correctly, I've been able to determine the bandwidth used before via channel ID, but would have to dig through the metrics. Will hopefully be able to do that later today depending on if I can get the network tests working again

[Reiterating the findings from our discussion in #1078], it has been clarified that the metrics in question are peer_send_bytes_total and peer_receive_bytes_total. Although these metrics include channel IDs, they are presently missing a message type label, rendering them insufficient for providing the desired level of granularity. Nevertheless, the decision reached that we could use them to cross-check results extracted from message_receive_bytes_total and message_send_bytes_total.

closed by https://github.com/celestiaorg/celestia-core/pull/1091


Reduce amount of API Call when switching payment methods

What is currently happening?
Whenever I switch payment methods in the frontend, the Mollie Profile and Methods APIs are called.

What should be happening?
The content of the API calls is fairly static and can safely be cached, at least within one checkout session. The API should not be called that often.

huch? that is not known :D
nice finding, we should fix that

This issue got worse after the POS payment method has been introduced. Now /v2/methods/ideal and /v2/terminals are called for every payment method selection screen, even when those payment methods are turned off.

It is live now and we should have see less requests


Remove steward

This looks wrong to me, it can't be an error since it's this word has polysemy.

https://www.merriam-webster.com/dictionary/steward

If you want to use this word without generating an error, you can

Add the word to a vocabulary;
lower the severity of the rule: Google.GenderBias = warning; or
disable the rule entirely: Google.GenderBias = NO.

That said, I think the word makes sense within the context of this rule. It's not about what you're using the word to mean (i.e., its polysemy nature), but the fact that it's generally considered to be gendered language (see stewardess).
I'm sure it's possible that you disagree, but my hope is that Vale is configurable enough to allow you to make these decisions in your own configuration.

I went with option 3. I disabled the rule, it seems simpler, maybe we will refine this down in the future.
There are more on the list that feel wrong, e.g. mankind, landlord shouldn't be here. Now waitress, lady lawyer, man enough, yes, they makes ton of sense.

There are more on the list that feels wrong, e.g. "mankind", "landlord" shouldn't be on this list. Now "man enough", yes, this makes a lot of make sense to me.

With all due respect, I don't think you understand the intent of the rule. I linked to the source material in my first comment, which specifically includes "mankind" as an example of a term that shouldn't be used (according to the style guide):

Not recommended: This API might be just what your globally conscious company needs to help all of mankind.

My sole intent when maintaining an implementation of a third-party style is to align with their guidance; independent of how you, I, or anyone else feels about it.

@jdkato I think we are good:

steward was about removing words that have meaning unrelated to gender.
second comment was about documenting why option 3. Why MUI isn't using this Google rule. It fels like it's making this worst, encouraging to give gender neutral word a gender.

Nitpick, mankind's closest alternative sound to me is humankind, not humanity, not the same meaning.


[netcore][14.nlp-with-dispatch] Fix typos and minor style tweaks

Proposed Changes
Fix broken links in readme.
Fix typos in code files.
Minor style tweaks in readme and code.
Testing
Code behavior was not modified.

Closed due to Microsoft#776


Apply some basic code-style rules

Try not to exceed 80 characters in one line.
if(blabla) –> if (blabla)
for(blabla) –> for (blabla),
Do not return something in else.

Thanks for the PR. I don't prefer this style. Not because it's better or worse, just personal taste.
Cheers.


Bar polar app

Adding a polar chart app.

Hi @pierreolivierbonin Thanks for adding the differenced-time-series app, but could you put it in a separate pull request?

Thanks for this app @pierreolivierbonin   The Bar Polar is a cool figure.  I'd like to suggest making the default Logarithmic just to make it look prettier in the gallery:

Thanks so much for your suggestions. Those were very thoughtful and I've learned a lot. Let me know if there's anything else :)

Thank you P-O for creating this app, and thank you Ann for the guidance. Here is the Pages code. It can now be merged and an image created.
import dash

from lib.code_and_show import example_app

dash.register_page(
    __name__, description="This app connects between the dropdown, the radio button, and the bar polar chart. It has a top-bottom layout and a regular-callback."
)

filename = __name__.split("pages.")[1]

notes = """
#### Dash Components in the App:
- [RadioItems](https://dash.plotly.com/dash-core-components/radioitems)
- [Dropdown](https://dash.plotly.com/dash-core-components/dropdown)

#### Plotly documentation:
- [Polar Bar Charts](https://plotly.com/python/wind-rose-charts/)

##### Contributed by:
This example app was contributed by [Pierre-Olivier](https://github.com/pierreolivierbonin)

"""

layout = example_app(filename, notes=notes)

Thanks @pierreolivierbonin  and @Coding-with-Adam I'll add the pages file, image and format with black after it's merged


Feature request - Add ability to "skip" adding all columns to models

The default feature of adding all columns to models is great but it can generate a huge diff in the YML files.
I think it would be useful to provide an option where documented columns are "pushed down" to downstream models but where non-documented columns are not added. I see it as a potentially first step in getting better docs without being to overwhelming..

This is added in latest release via a flag called --skip-add-columns
Version 0.11.19
https://github.com/z3z1ma/dbt-osmosis/releases/tag/v0.11.19


JS implementation

@dignifiedquire @diasdavid do you think multigram in JS would be useful right away? We can get proper (limited) datagram sockets via browser addons for firefox and chrome. We can also use these to make a case for a WebUDP/WebDatagram/WebMessage standard.
https://www.npmjs.com/package/firefox-dgram (for addons)
https://www.npmjs.com/package/chrome-dgram (for chrome packaged apps)
Are there any good UDT/uTP/QUIC implementations in JS that we could use on top?

@dignifiedquire @diasdavid do you think multigram in JS would be useful right away?

Right away depends on the use case that currently is not possible. I feel it is more important to make it part of the IPFS network, otherwise it will be always hidden behind a flag in js-ipfs. Nevertheless, I do believe js-ipfs might be a better sandbox to test and develop multigram to get a better feeling for it.

Are there any good UDT/uTP/QUIC implementations in JS that we could use on top?

There is only the uTP bindings to the C library.

LMK if you want me to rev up github.com/ipfs/xtp work


v1.15.0 fails with allow_choice_duplicates

Issues were reported at https://forum.opendatakit.org/t/error-allow-choice-duplicates/21440 and https://github.com/opendatakit/xlsform-online/issues/26.
Likely PR that caused this is at https://github.com/XLSForm/pyxform/pull/310. This was released in v1.14.1, but we've been on v1.14.0 on XLSForm Online, just upgraded to v1.15, and started seeing reports.

Been able to dig more here and can confirm that this isn't the root cause. https://github.com/XLSForm/pyxform/issues/355 is the issue folks are running to.


Every video set to Made for Kids

In my youtube audience settings I have it set for "not made for kids", however, whenever I upload any video, it is immediately set to "made for kids" and I have to manually undo this after it is posted.
I'm sure all this reverting does not help my channel grow, so a fix or help with this would be great.

Actually, I found a fix, when creating your video obj, include isNotForKid as true.
Ex.)
const video = {
path: vid_path,
title: new_title,
description: new_description,
isNotForKid: true
};


Dependent target fails to add files from earlier target

Describe the bug
I am adding some code generation in my project that involves two phases where the output of one phase is supplied to a second phase. When I build the targets one by one in sequence, I get the output I expect (two files, target_1_output.txt and target_2_output.txt, but when I build them together the second target fails to add the input of the first.
Expected behavior
The same output as when building the targets together: two output files, build/target_1_output.txt and build/target_2_output.txt.
Error output
warning: cannot match target(target_2).add_files("build/target_1_output.txt") at .\xmake.lua:25
Related Environment
Create a file target_1_input.txt with any contents, and then build with the following xmake setup:
set_policy("build.across_targets_in_parallel", false)

rule("target_1_rule")
	set_extensions(".txt")
	before_buildcmd_file(function (target, batchcmds, sourcefile, opt)
		io.writefile("$(buildir)/target_1_output.txt", "")
	end)

rule("target_2_rule")
	set_extensions(".txt")
	before_buildcmd_file(function (target, batchcmds, sourcefile, opt)
		io.writefile("$(buildir)/target_2_output.txt", "")
	end)

target("target_1")
	set_kind("binary")
	add_files("target_1_input.txt", { rule = "target_1_rule" })
	-- override link step since this target doesn't produce object files
	on_link(function(target) end)

target("target_2")
	set_kind("binary")
	add_deps("target_1")
	add_files("$(buildir)/target_1_output.txt", { rule = "target_2_rule", always_added = true})
	-- override with no-op link step since this target doesn't produce object files
	on_link(function(target) end)

Then run xmake to reproduce the issue.
If you delete the build contents and manually build the targets in the correct order both output files will be produced.
xmake b target_1
xmake b target_2

xmake version: xmake v2.5.6+202107260800
os: Version 10.0.19043
target platform: Windows

Additional context
Perhaps a separate issue, I am unsure what the appropriate target kind is for running tools like this when there is a dependency chain and it is insufficient to specify them as prebuild steps for some other target. I wound up using binary with an overridden link step (otherwise the linker will fail) instead of objects (which seemed like it would skip the link step to begin with, but produces the error error: no suitable linker for object.{} when generating a visual studio project using xmake project -k vsxmake). phony seems to not be intended for this either.

I have fixed it on dev. please run xmake update -s dev and try it again.

Can confirm this solves the issue. Thank you!


or-tools in a windows docker container

What version of OR-tools and what language are you using?
Version: master/v7.3/v7.2 etc.
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
Windows 10
What did you do?
Steps to reproduce the behavior:
I am trying to wrap my api that leverages or-tools in a windows based docker container.
In my container I install the full suite of VS build tools.
However, no matter what I try I can't get this command to pass "python -c "from ortools.linear_solver import pywraplp".
The error that I get is "DLL load failed while importing _pywraplp: The specified module could not be found." which I know is related to "not" having the C++ build tools installed.
Are  ideas on other avenues to try? or an active or-tools based docker container for windows?
Anything else we should know about your project / environment
Below is my Dockerfile
FROM mcr.microsoft.com/windows/servercore:ltsc2016

SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"]

RUN (New-Object System.Net.WebClient).DownloadFile('http://download.microsoft.com/download/5/f/7/5f7acaeb-8363-451f-9425-68a90f98b238/visualcppbuildtools_full.exe', 'visualcppbuildtools_full.exe') ; \
    Start-Process .\visualcppbuildtools_full.exe -ArgumentList '/NoRestart /S' -Wait ; \
    rm visualcppbuildtools_full.exe

# Python image
FROM python:3.8.2-windowsservercore

# Set the working directory
WORKDIR /MyProject

COPY . /MyProject

# Install required packages
RUN pip install --upgrade pip
RUN pip install -r requirements.txt

I was able to figure it out. They key is to use the latest microsoft/dotnet-framework docker container and manually install python into the container instead of calling on the pre-built docker container.
Here is an example DockerFile
# Use latest .NET Framework as base
FROM microsoft/dotnet-framework

# Install Microsoft Visual C++ Redistributable for Visual Studio 2019
ADD https://aka.ms/vs/16/release/VC_redist.x64.exe VC_redist.x64.exe
RUN C:\VC_redist.x64.exe /quiet /install

# Install specific version of python required and add to PATH
ADD https://www.python.org/ftp/python/3.8.2/python-3.8.2-amd64.exe /python-3.8.2-amd64.exe
RUN C:\python-3.8.2-amd64.exe /quiet /install PrependPath=1

# Rest of DockerFile

``
Hope this helps anyone searching for this as well.

Maybe the default python is a 32bit one?

Many Thanks for the feedback !


To mesosphere

Per offline discussion with the mesos project maintainers, this project will no longer live under the mesos organization on github. Instead, it will live under the Mesosphere organization and be linked to by the mesos project.

Fixes #30

@cruhland Can you do a quick review before I squash and merge?

javadoc build error is fixed in #32

Ship it :+1:


Prompts get misaligned after resizing the window.

I just noticed on resizing the window left and right prompts get misaligned as shown in the screenshot below

Is any one experiencing the same problem?
Let me know if you guys need any other informations.

@haccks what terminal are you using? iTerm?
@bhilburn This looks like a duplicate of #881?
If so, I understand this isn't an issue with P9K, but given your comment on that issue you seem to know the details of why this is happening... could you please elaborate? So that we can look for a solution in the right direction. :smiley:
I tried with only one prompt element, static (no changing content), text only (no icons, separators or new lines), and no right prompt. All in a newly launched terminal. This is still happening, although it's less chaotic of course.
I tried with a different oh-my-zsh theme, still happening.
I tried this resizing tmux panes instead of the whole terminal window, still happening.
However, I did every kind of terminal resize and movement I could think of for an embarrassingly long time with bash instead of zsh, and this never happened.
So, is this a zsh issue?
I see that it does re-print the prompt on every resize event, so perhaps it's an issue with zero-size control characters when deleting the old prompt to re-print the new one, maybe?
Or a race condition? Basically zsh not being fast enough to delete the existing prompt and replace it with the updated one before the next resize event causes a new delete+print cycle? So you end up with only a half-deleted old prompt.
Btw, I'm on Linux and I can just as easily reproduce this with gnome-terminal, terminator and even xterm (which doesn't show the patched font's icons).
Thanks!

@fgallardograzio I am using iTerm2 (Build 3.2.4beta4). And seriously don't know why this is happening but one thing I know is this is making me sick!

This is indeed a duplicate of #881, as @fgallardograzio points out. Unfortunately, this isn't anything that can be addressed in P9k or fonts, as this is simply how your terminal emulator is re-drawing prompts with ZSH.
I don't know the hard details of why emulators do this, but I'm sure there is a good design reason for them to have been written this way as they all seem to follow the same pattern. What you are seeing is the emulator+ZSH attempting to re-draw at different intermediate stages of your resize, rather than just doing it once at the end. Additionally, when the emulator re-draws the prompt, it seems like the size that ZSH is drawing to doesn't match the actual emulator size - which is why you see it staggered all over the screen.
To be clear, it might not be the above -- that's just me speculating based on having seen this for many years with ZSH. I'm sure other people with deeper knowledge of ZSH and/or terminal emulators would have much more to say.


feat: add initial version of version manager

Could you add an empty README.md and a blank test in the example app. So that when I run flutter create . in the example folder I don't have any changes


Added support for wasm32-wasi target

Hi!
I'm currently on my way to make SQLite work with wasm32-wasi.
So, one of the blockers was OpenSSL in general since SQLite depends heavily on it.
Here's my shot at it:

Introduces no new dependencies
Small alteration of the docker test harness to:

install wasmtime & set it up as test runner
install & setup wasi-sdk

Compatible with all versions of OpenSSL (1.1.x and 3.x.x were tested).

This should be the first step in closing https://github.com/sfackler/rust-openssl/issues/1016
Should also supersede #113
Please give me any feedback! I'll tend to it ASAP.

Ah ok sorry I didn't realize that this wasn't passing CI, I'll take another look when CI is passing for wasm32-wasi

Looks good to me, thanks!


Ignore without range should not attempt a check

The github integration currently doesn't support private packages for Elixir and Hex.pm. After adding ignore statements for the private packages in our mix file, the check still fails as Dependabot appears to apply ignores after checking for updates.
If a package is marked to be ignored completely (no range) then Dependabot should simply skip any checks for that dependency.
https://github.com/dependabot/dependabot-core/issues/2778
https://github.blog/changelog/2020-12-02-dependabot-version-updates-from-private-github-repositories/

Yeah, makes sense.
This is an ecosystem-by-ecosystem change... we could fix for top-level dependencies in most ecosystems, but this will likely continue to happen with indirect deps... ie, we prefer to shell out to the native package manager wherever possible so it may see that a top-level dep requires an indirect dep on a private registry... and we don't have an easy way to stop that.
Also, we recently shipped support for private hex repos: https://github.com/dependabot/dependabot-core/pull/5043#issuecomment-1325631034
So I'm going to close because even though we didn't fix the underlying issue, we fixed the symptom and the underlying issue will vary depending on the ecosystem. As we encounter it we can fix it.


Refactor generate_queries devops case to use errs

Previously the devops use case generation code used a call to
log.Fatalf when something went wrong. This makes it awkward to test
error conditions when generating queries from other packages, since
we need a way to (a) replace the unexported call to log.Fatalf and
(b) prevent the runtime from actually quitting.
It is better for the library to actually return errors on calls
that can fail, rather than either fataling or panicking. Now other
packages can handle the errors themselves and also test error
conditions in their packages as well.
This refactor was pruned a bit to bubble the 'panic' up one level
for now. When the actual generation code encounters the error
during normal execution, it will panic. But these are easier to
test for and don't require adding hooks to replace the 'fatal'
path in the original package.

Codecov Report

Merging #77 into master will decrease coverage by 0.31%.
The diff coverage is 49.49%.

@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
- Coverage   57.13%   56.82%   -0.32%
==========================================
  Files          76       76
  Lines        3719     3757      +38
==========================================
+ Hits         2125     2135      +10
- Misses       1570     1592      +22
- Partials       24       30       +6

Impacted Files
Coverage Δ

...bs_generate_queries/databases/clickhouse/devops.go
10.1% <20%> (+0.16%)
:arrow_up:

...sbs_generate_queries/databases/cassandra/devops.go
25.55% <28.57%> (+0.86%)
:arrow_up:

...d/tsbs_generate_queries/databases/influx/devops.go
32.14% <28.57%> (+0.14%)
:arrow_up:

...d/tsbs_generate_queries/databases/siridb/devops.go
27.58% <28.57%> (+0.66%)
:arrow_up:

...s_generate_queries/databases/timescaledb/devops.go
97.41% <87.5%> (-1.2%)
:arrow_down:

cmd/tsbs_generate_queries/uses/devops/common.go
92.85% <90.47%> (-3.97%)
: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 3cfaae0...70ddcb7. Read the comment docs.


parser does not decode appearance of "escaped" quote_char within individual cells

The project allows for quoting of individual cell contents (via quote_char) but does not provide for the recognition of embedded, quote_char  characters within quoted cell value strings. Ideally the project should at least support RFC 4180 encoding or, better, the ability to specify escape character (e.g., quote_escape_char) to be used with literal appearances of quote_char in the quoted cell string. The latter will enable support for both RFC4180 encoding rules (quote_char = " and quote_escape_char = " )and the non-standard, but often used backslash escaping used by various database table exports (quote_char = " and quote_escape_char = \ ).

The project allows for quoting of individual cell contents (via quote_char) but does not provide for the recognition of embedded, quote_char characters within quoted cell value strings.

I couldn't follow the issue. Could you please provide more details? Hasn't this already been addressed in the code? (except for specifying the quote_escape_char) https://github.com/ashtum/lazycsv/blob/844e3f318af2d9ede96039dd9f57ebf4cad59ce2/test/main.cpp#L131


[Emu]: Potential fix for Windows/Linux/Mac/Android address issues.

Move all primitive list adding code for SPEC_PSXPC_N to macros, modify poly structs to allow 32-bit pointer size as address and 8 bit code separately. Make LIBGPU make use of getter macros for the new system (preferably implement this first).
This should allow us to run the game in 32-bit mode easily across all platforms. Also, Linux/Mac versions won't need the virtual memory allocation anymore.

A fix is work in progress and should be part of PR: #225

Fixed in: https://github.com/TOMB5/TOMB5/commit/09e7d3fda5e89e66fb8bb9a79d3981f2e6834996


CNV-41846: Fix customize IT yaml

📝 Description
Yaml tab was looking for data from the VM store instead of signal. Changed to the right location.
🎥 Demo

Please add a video or an image of the behavior/changes

/lgtm

/retest

/cherry-pick release-4.16


Unknown error - Script error (stats.pusher.com)

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Upon opening my diagrams which contain 6 pages, I get an "Unknown error - Script error"
dev tools tell me Uncaught TypeError: Cannot read properties of undefined (reading 'receive') at stats.pusher.com/timeline/v2/jsonp/1?
To Reproduce
Steps to reproduce the behavior:

Go to https://app.diagrams.net/#G1vnJ6jy3Fle7L42OBC934Zte4UyRoJZ3y
Click on '....' (error pops up here before clicking anything)
Scroll down to '....' (NA)
See error

Expected behavior
No error message
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 16.0.2

Desktop (please complete the following information):

OS: Windows 10
Browser Chrome
Version 96.0.4664.110

Smartphone (please complete the following information):
N/A
Additional context
It seems that an adblocker prevents this issue. Using Brave browser helps as well which I assume is due to it's built in adblock

Fixed in 16.0.3


Verification email gives me a wrong url

Description
The link the user receive on the verification email sends the user to a a url like this "https://localhost/register/verify/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoienptbnQiLCJlbWFpbCI6Im1lbm90aW1maWxob0BnbWFpbC5jb20iLCJpYXQiOjE2OTUwNjQ4NzgsImV4cCI6MTY5NTE1MTI3OH0.MDnUbgid0m5SdrS2OBXo8dKdjyS1SqWQgF-u3VhtnWk" which won`t work since its a localhost
Screenshots
No response
Additional information
No response

Nice, catch. working on a fix :)

@MenotiFilho Fixed, please register again 👑


Parse search strings as byteseek regexes, or just convert to byte arrays?

Search algorithms usually provide a String constructor.
Currently, that just lets us match the sequence of bytes encoded by that string (either in the default Charset, or one that's provided).
But since byteseek is byte oriented, a hex string (or full byteseek regex syntax) might be more useful.  One person has already asked whether they can pass in hex string  bytes directly to the search algorithms.  I had to say that wasn't true, and they needed to use the SequenceMatcherCompiler to create a SequenceMatcher for the search algorithm to look for.
The same search algorithms also have a byte[] array constructor, if you want to explicitly search for a byte pattern.  It's easy to convert a string to a byte array if that's what needs to be searched for.
So I guess the string constructor is essentially redundant - unless we support byteseek regex construction directly, just get rid of those constructors.
If we did support byteseek regex syntax in the search algorithm String constructors, what do we do with Compiler / Parse Exceptions?

I guess those constructors just throw CompileExceptions.  It only affects you if you use those constructors - as it should.

This is essentially a convenience constructor.   Either a string is a byte array, or it's a regex.  In either case we already have constructors for the outputs (SequenceMatcher or byte array).  And the byte array can also be modelled by e a SequenceMatcher.
What gives the best convenience?

So - SequenceMatcher constructor is the only general constructor for SequenceSearch algorithms.

Downside of making String constructors for search algorithms process regexes, is it creates a hard dependency on all search algorithms to the byteseek sequence matcher compiler and regex parser.

Currently, matchers and searchers don't depend on the parser and compiler in any way.

The only excuse for such a higher level dependency is convenience - which is what this is.
Is the convenience of instantiating hex string (or more complex syntax) searchers directly worth the dependency it creates?

I don't think a hard dependency between the Searcher and Compiler package will really hurt anything.
It's a general design principle to try to keep them as cleanly separated as possible, but this is a case where we already had a support question raised by a user.  They expected (or wanted) to be able to do this.

I'm going to explore using SequenceMatcher compilers directly in the SequeneSearcher String constructors.


Fixed https://github.com/javascript-obfuscator/javascript-obfuscator/…

…issues/210

Coverage decreased (-0.03%) to 98.172% when pulling 0c088af2185f189e27a958201eeea4768883943b on esprima-parse-module into b971dc6e568ef08a5d3a94c706941b80fbc32e4c on master.


Fix for e2e tests

Fixes some bugs found while implementing the e2e test that checks Cowbird and Jupyter usage on birdhouse (see PRs #131  and #404):

The FileSystem handler now creates the WPS outputs data folder if it doesn't exist so that monitoring is setup
properly.
User permissions are set explicitly after creating his datastore folder to make sure the user can create and modify
files in it.

@fmigneault Fixed some check and test errors, need reapproval before I can merge.


Feature Request: Persistent mute icon

An option to set mute icon OSD as persistent, i.e no fadeout.
Edit: Could also apply to other OSD elements.

Use option AlwaysShowElements in config.ini (fast access by pressing "Open Config File" in context menu of the tray icon)

I saw this option, but I wasn't quite what I was looking for. Maybe there is no easy way to do this tho. I was thinking it would be nice if the mute element would stay on the screen for the duration of the mute. I.e. stay there until it's unmuted.

@A-tG, could this be achieved by setting fadeout timer individually per OSD element in the config? I'm not asking you to do this, because it seems sub-optimized and not very user-oriented and frankly just plain ugly, but just curious if it could be possible.

Every config option have to be implemented with some coding. I don't think this feature worth implementing.

Yeah, I agree with you too. This is becoming my favourite tool since the last two days. Absolutely excellent.