Use relative imports in protocol definitions

Fixup the broken generated code in a postprocessing step.

Backend checklist

[x] Formatted my code by running isort . && black . in app/backend
[ ] Added tests for any new code or added a regression test if fixing a bug
[ ] All tests pass
[ ] Run the backend locally and it works
[x] Added migrations if there are any database changes, rebased onto develop if necessary for linear migration history

Frontend checklist

[ ] Formatted my code with yarn format && yarn lint --fix
[ ] There are no warnings from yarn lint
[ ] There are no console warnings when running the app
[ ] Added any new components to storybook
[ ] Added tests where relevant
[ ] All tests pass
[ ] Clicked around my changes running locally and it works
[ ] Checked Desktop, Mobile and Tablet screen sizes

@kalvdans: are you happy for me to push into this repo to fix this up for the non-python part? Would you prefer mkdir -p or empty dirs with a .gitkeep/.gitignore

@kalvdans: are you happy for me to push into this repo to fix this up for the non-python part?

Yes please!

Would you prefer mkdir -p or empty dirs with a .gitkeep/.gitignore; I'd prefer the latter (to have the right directory structure in git, maybe even a readme that says "the contents of this folder are generated by the protocol buffer compiler...").

An mkdir will give a easier gitignore expression so I think I prefer that. But I'm not going to complain if you let git create the directory.

@kalvdans: fixed now; have a look


[sqlite3] Ability to enable the SOUNDEX() scalar function

This PR adds a configuration for the SOUNDEX() scalar function to the list of configuration options.
Apart from simply rounding out the sqlite3 port, this is useful for two immediate reasons:

sqlite_orm has built-in support for the soundex() function, but programmers who want to use it cannot take vcpkg's sqlite3.
sqlite_orm's codebase tests built-in support for the soundex() function and relies on the vcpkg ecosystem. Tests for soundex() remain unexecuted.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static
x64-linux

Thanks everyone!


added prompt for #443

@the-dagger Please review and merge. Solves #443.
@mariobehling After this the user gets a prompt asking if he wants to download assets. If he says no, then everytime on startup the prompt shows up. When the users selects yes, the prompt doesn't appear the next time he opens the app. Does this look fine?

Sounds good. Please implement the option to "automatically update" or "ask before updates" in the settings.

[Current coverage][cc-pull] is 10.98%

No coverage report found for development at 690cec1.

Powered by Codecov. Last updated by [690cec1...38ba7f2][cc-compare]
[cc-base-branch]: https://codecov.io/gh/fossasia/open-event-android/branch/development?src=pr
[cc-compare]: https://codecov.io/gh/fossasia/open-event-android/compare/690cec1fa0b5ae556a51d92a781178717f48a204...38ba7f214e633329fc2ec4a5b2f03587a7a490ba?src=pr
[cc-pull]: https://codecov.io/gh/fossasia/open-event-android/pull/490?src=pr

Okay great. Will add it to the issue and implement by today itself.

Looks good, merging


Update to pydantic v2

Pydantic provides an automated migration tool that should do the bulk of the work in an automated way, such that we can:

Run the tool.
Run our test suite.
Fix whatever broke.

https://docs.pydantic.dev/latest/migration/
This is worth doing soon, as event-model recently updated to pydantic 2.0.

There is a duplicate issue that I created when we first pinned pydantic back to <2: https://github.com/bluesky/tiled/issues/491


Add a way to get LSP status info

It would be handy to have a way to see if the language-servers are running and responding.
I originally thought it would be a good extension to :ALEInfo.
The more I think about it, the more I think it should be like the :CheckHealth in NeoVim.  Mainly because it may not be "instant" like the :ALEInfo is.
Description of what it would do:

For every language-server that ALE has started (or tried to start):

Check if the process exists.
If there is a "ping" command that can be sent to the language-server, then send that and show if it responded.  I don't see a PING, alas.
Show if the language-server ever finished initialization (initialize/initialized finished).

Great idea 👍 I recommend thinking of two separate use-cases, a command like :CheckHealth that will print out very detailed information that people need occasionally, and an indicator like ale#engine#IsCheckingBuffer(bufnr('')) (with autocommands maybe like ALEJobStarted) for something that most people will always find useful to see in status bar like lightline-ale.

I just realised that #2137 duplicates this.


Request template requiring SLC7 ScramArch

@khurtado Kenyi, this template will create very few jobs and you should see the LogCollect job failing. Please let me know how it goes.
Status
not-tested
Description
TaskChain with a single task using CMSSW_11_x and slc7 ScramArch.
Is it backward compatible (if not, which system it affects?)
Yes
Related PRs
External dependencies / deployment changes

For the record, until I get those fixed, the following templates are broken because the input dataset is invalid and there are no replicas available anymore:
https://github.com/dmwm/WMCore/blob/master/test/data/ReqMgr/requests/Integration/SC_LumiMask_PhEDEx.json
https://github.com/dmwm/WMCore/blob/master/test/data/ReqMgr/requests/Integration/StepChain_ReDigi3.json

All the templates have been tested and samples locked in the usual cmst1 file (~/www/lockedData/lockTestSamples.json).


feat: add components use

Hello, I've added custom component use because in my case I have additional components in different places.

Thanks!


Design Ui For The Program

Design Ui For The Program

can you explain more about the project please ?
what type of UI is needed ,
what data is gonna be rendered on the page ?


rename chart to lowercase and add public charts to public repo

@waseem-h @kahootali Please create a release and tag before and after merging it,
We can maybe write a script then to update all our repos where master is used and use the tag


Implement ComputerSystem for a composed resource

Removes handling of server hardware and put handling to serve profile
Changes unit tests to the new behavior
Adds new mockup files to the new unit tests

Closes #270

I think is missing include the fixed issue on Changelog, right @ricardogpsf ?

@karolcatunda It is because we talked about this before and decided change the CHANGELOG after PRs be merge, at end of "sprint", to avoid merge conflicts and force the rebase to all others PR.


predicate-argument extractor

Hi, do you have a integrated predicate-argument extractor?
Or is there any way to write it easily?

Hi, I think it is possible to write a code to traverse the output logical form of ccg2lambda and collect predicates and their arguments, but no one has tired that yet.
If what you are interested in is so called semantic role labels, how about using EasySRL (https://github.com/uwnlp/EasySRL), which is optimized for that specific task?
By the way, there is a script to convert the logical formula to ones in other formats, e.g. DRS.
You may be able to modify it to obtain what you are expecting...
https://github.com/mynlp/ccg2lambda/blob/master/scripts/nltk2drs.py


Use app_context_processor for context_processors that should be appli…

What does this pull request do?

Switches Blueprint scoped context_processors to app_context_processors.

At this stage all context processors should be applied globally.

Any other changes that would benefit highlighting?

get_gtm_anon_id now uses the function decorator syntax for consistency.

Checklist

[x] Provided JIRA ticket number in the title, e.g. "LGA-152: Sample title"

Thanks Ben, this looks good. Not sure why the gtm_anon_id is blank as I thought that part was done, maybe it wasn't can't remember.

Actually it might just be my browser so ignore me if you can see it.

Thanks Ben, this looks good. Not sure why the gtm_anon_id is blank as I thought that part was done, maybe it wasn't can't remember.

Actually it might just be my browser so ignore me if you can see it.

Hi Jav, I looked into this and this error is happening on my end too. I will investigate the cause of this.


Update JS Fiddle to use the JS SDK

Right now the JS Fiddle is doing the contract calls directly via Soroban SDK.
But now we have a JS SDK, and this task is to update the JS Fiddle to use our Oracle JS SDK instead of Soroban directly.
Current JS Fiddle (you'll need to create a new Fiddle as a clone, then update the link in our documentation):
https://playcode.io/1594911
Oracle JS SDK docs (it has example):
https://github.com/bp-ventures/lightecho-stellar-oracle/tree/trunk/oracle-sdk/javascript

hi I had a look and it would be good to

add documentation on what parameters need to be passed (Testnet, signing key etc)
make it simple so just call get_price
rename the second field to asset soroban contract address and make it bigger

@MuhammadHassanAmin I'm gonna push a few updates to the JS SDK today, please wait until tomorrow before implementing the changes

https://playcode.io/1648807


Resubmission_Group04_2312596_2313097_2311318_2312954 _2312791

Team Members

Full Name
Student ID

Trần Đỗ Đức Phát (Leader )
2312596

Lê Quốc Thái
2313097

Đặng Gia Hưng
2311318

Lê Sĩ Nhật Quang
2312791

Đào Xuân Sơn
2312954

Description of the Policy:
This submission includes the implementation of two policies based on First-Fit and Best-Fit algorithms for solving the two-dimensional cutting-stock problem.
First-Fit Policy:

The algorithm processes the product list sequentially.
Each product is placed into the first stock where it fits, starting from the top-left corner of the stock and moving row by row.
It also considers rotation of the product to maximize space utilization.

Best-Fit Policy:

The algorithm evaluates all available stocks for each product and places the product in the stock that leaves the least unused area after placement.
This approach prioritizes minimizing fragmentation in the stock and optimizes space utilization globally.

Implementation Details:
First-Fit Algorithm:

Iterates through the list of products in their given order.
For each product:
Checks every stock, starting with the first one, to find a valid position where the product fits.
Places the product into the stock as soon as a valid position is found.
Includes rotation to check both orientations of the product.

Best-Fit Algorithm:

Iterates through the list of products in their given order.
For each product:
Evaluates all available stocks to find the one where the remaining unused area (after placing the product) is minimized.
Considers both rotated and unrotated orientations to ensure optimal placement.

Results on Test Data:
(Using seed=24 )

Filled-ratio
Trim-loss

First-Fit Policy
0.2
0.25

Best-Fit Policy
0.23
0.18

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.

Last chance to revise the PR until the end of Dec 17.

Dear mr Martin!
We are so apologize for this


It's just completely broken on crunchyroll

I try to go to any video on crunchyroll and it just doesn't work. The prompt to select a subtitle shows up but clicking it does nothing. Even more interesting is how the video continues to play but won't let you go fullscreen.

Hmm, I just tested it out and didn't have any problems. Was it working before? Are you using the Crunchyroll beta? What browser are you using? Are you using any other tampermonkey scripts or browser extensions on Crunchyroll? When you hover over the prompt button does the button's background get lighter? Can you interact with any of the video player controls other than fullscreen?

Hmmm, that is really weird. Just tried it in Chrome and it's still working for me there. Can you open the browser devtools and see if there are any errors in the console, particularly when you click on the button?

Nothing when I click the button, but I do get this when first loading the video:
(Various other errors are present but they match those of a functional version of crunchyroll)

Refused to frame 'https://bid.g.doubleclick.net/' because it violates the following Content Security Policy directive: "default-src 'self' data: *.betrad.com *.evidon.com *.evidon.com api.segment.io bam.nr-data.net beta-api.crunchyroll.com cdn.cookielaw.org cdn.segment.com cdn.shopify.com cdnjs.cloudflare.com customer.iad-03.braze.com eec.crunchyroll.com fy.v.vrv.co geolocation.onetrust.com img1.ak.crunchyroll.com js-agent.newrelic.com ll.v.vrv.co pl.crunchyroll.com privacyportal-eu.onetrust.com sa.etp-prod.com sso.crunchyroll.com static.crunchyroll.com static.vrv.co v.vrv.co www.crunchyroll.com www.google.com www.gstatic.com bs.serving-sys.com connect.facebook.net fonts.googleapis.com fonts.gstatic.com googleads.g.doubleclick.net marketingplatform.google.com ssl.google-analytics.com www.facebook.com www.google-analytics.com www.googleadservices.com www.googletagmanager.com". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.

hero-king-gazel-dwargo:4 Refused to frame 'https://bid.g.doubleclick.net/' because it violates the following Content Security Policy directive: "default-src 'self' data: *.betrad.com *.evidon.com *.evidon.com api.segment.io bam.nr-data.net beta-api.crunchyroll.com cdn.cookielaw.org cdn.segment.com cdn.shopify.com cdnjs.cloudflare.com customer.iad-03.braze.com eec.crunchyroll.com fy.v.vrv.co geolocation.onetrust.com img1.ak.crunchyroll.com js-agent.newrelic.com ll.v.vrv.co pl.crunchyroll.com privacyportal-eu.onetrust.com sa.etp-prod.com sso.crunchyroll.com static.crunchyroll.com static.vrv.co v.vrv.co www.crunchyroll.com www.google.com www.gstatic.com bs.serving-sys.com connect.facebook.net fonts.googleapis.com fonts.gstatic.com googleads.g.doubleclick.net marketingplatform.google.com ssl.google-analytics.com www.facebook.com www.google-analytics.com www.googleadservices.com www.googletagmanager.com". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback.

There is also this:

Some resources are blocked because their origin is not listed in your site's Content Security Policy (CSP). Your site's CSP is allowlist-based, so resources must be listed in the allowlist in order to be accessed.
A site's Content Security Policy is set either as via an HTTP header (recommended), or via a meta HTML tag.
To fix this issue do one of the following:
(Recommended) If you're using an allowlist for 'script-src', consider switching from an allowlist CSP to a strict CSP, because strict CSPs are more robust against XSS . See how to set a strict CSP .
Or carefully check that all of the blocked resources are trustworthy; if they are, include their sources in the CSP of your site. ⚠Never add a source you don't trust to your site's CSP. If you don't trust the source, consider hosting resources on your own site instead.
AFFECTED RESOURCES
1 directive
Resource: https://bid.g.doubleclick.net
Status: blocked
Directive frame-src

^ under issues as a page error

Those shouldn't have anything to do with Jimaku Player, it doesn't load any external resources or ads. Do you know what version of it you're using and what version of Chrome you have?

Just to be sure, have you tried completely closing and reopening Chrome too?

Jimaku: 0.6.9
Chrome: 99.0.4844.51 (Official Build) (arm64)
I will quickly try restarting chrome

HMMMMMMMMMMM... DEEP BREATHS EVERYONE
Short: it works
Long: I did a tech granny and didn't even think to restart chrome (I even had tried reinstalling Jimaku).
Thanks for your patience

Ok that's great! :sweat_smile:
No worries, it wasn't my first thought either, just happened to see people on Stack Overflow say that fixed similar sounding issues. Glad it's not a more widespread problem!
Let me know if you have any other problems anytime!

Yes! And thank you again for making this in the first place, it has done wonders for my Japanese entertainment

Nice! I love hearing that!


Added DB type double (type B) + ability to convert from different encodings

Some minor changes:

added support for column type B (double)
added 3rd option to Table constructor method to convert data from different encodings to UTF8

This will fix problem

@hisamu Sure. Just give me some time :)

have to close it


s/Run/Vet/ in Contravariance example.

Good catch, thanks :)

My pleasure. Thanks for the great content.


Re-factored qualified name extraction logic for golang to make it consistent with the java analogous lib. [phab:D2165]

Created by craigbarber at 2018-02-02 23:20:08:

schroederc commented inline (context lost during migration) at 2018-02-02 23:22:51:
I think you might want delim instead of ctx.PostChildText.

schroederc commented inline (context lost during migration) at 2018-02-02 23:32:18:
Please add a test for an empty PostChildText if you meant delim here.

schroederc accepted this revision at 2018-02-02 23:32:18

craigbarber commented inline (context lost during migration) at 2018-02-02 23:34:46:
It's counter-intuitive, but using PostChildText here is intentional. delim is only used for the package name join. Whereas if no postChildText is specified, (as is the case for process nodes), we don't want to use a default delim. This is consistent with the Java lib as well.

craigbarber commented inline (context lost during migration) at 2018-02-02 23:36:43:
There are two existing test cases with empty PostChildTexts.

fromberger commented inline (context lost during migration) at 2018-02-03 01:12:41:
if got := RenderQualifiedName(&ms); !proto.Equal(got, test.want) {

It's not safe to compare protos by value (though in this case it will probably work most of the time) because the generated code includes details that affect the form but not the meaning.
You don't need to check for nil. It's fine to compare to a nil of a message type, it behaves as an empty message of the type.

fromberger wrote at 2018-02-03 01:12:41:
I'm still not fond of using a proto for this, but now that we've already defined it, I guess we might as well use it consistently.

craigbarber wrote at 2018-02-05 17:48:02:

incorporated CL feedback

fromberger commented inline (context lost during migration) at 2018-02-06 05:29:06:
Dead now?

fromberger commented inline (context lost during migration) at 2018-02-06 05:29:06:
Since you always want a pointer anyway:
info := &cpb.SymbolInfo{BaseName: id.PreText}

then the below can simply be
return info

fromberger commented inline (context lost during migration) at 2018-02-06 05:29:06:
Another option you can consider is to always return a non-nil value, even if it's otherwise empty:
return new(cpb.SymbolInfo)

They're equivalent as proto values (i.e., they report equal under proto.Equal) but always returning a value can sometimes make it easier for the caller who doesn't have to check if they want to override the value. But it's up to you.

craigbarber wrote at 2018-02-06 17:41:10:
incorporated CL feedback

craigbarber commented inline (context lost during migration) at 2018-02-06 17:43:00:
What's the recommended approach for testing equality of protos?

fromberger commented inline (context lost during migration) at 2018-02-06 17:48:18:
What you have here works fine: proto.Equal
The https://godoc.org/github.com/google/go-cmp/cmp package also affords some support for diffing, though in this case the messages are small enough it's simpler to just print them.

fromberger accepted this revision at 2018-02-06 17:48:18

craigbarber closed via commit 4bcd3a3b947b75e2f09a81ecd6b79e903fcd4cd4 at 2018-02-06 20:42:06


Fix PyLint

We need to have a deep look at the pylint issues and get the code at 10/10.
Once this is fixed, we'll be able to have the linting as a quality gate for approving new PRs, which will help us in maintaining new code.

Thanks @TeddyCr for picking this up 🙏 🚀 ❤

@pmbrull is there any thing else need to be done in this ticket, if not lets close it out

We're still at 8.52/10, but I'll break this down into smaller issues otherwise it is hard to tackle. Thanks!


Cell height is not matching with row header and separator not visible

I have dynamic content for row headers where in some cases content can be longer than screen size. I saw in a sample where height & content is predefined.

Is there any way where cell height can be the same as row header?
divider for row header and column header are not visible, did I missed anything?

following is the screenshot of current UI I have implemented.

@naushad-madakiya I think row height is set with layout_height inside your row_header and cell layouts. So make sure the heigh of row_header and cell layout match.
In addition, given you layout, you should consider setting a larger RowHeader width. this can be done in your layout with layout_width, or dynamically in the code with getTableView().setRowHeaderWidth()

Hi @naushad-madakiya,
In TableView, there is no any control to checks the cell height of both of row headers and centre cells. I
So, as @sonique6784 said, you have to be sure they have the same size.
So, you have 2 options that I've just come to my mind;

The TextView of the Row Header will not wrap the text. using this android:maxLines="1"and set much larger width.
You will set the same height value for both cell items of Row Headers and Centre Cells.

after setting up fix values for  row_header_width and column_header_height cell width was matching to column header but cell height is not matching with row header as row header has more content than column header.
I applied the following to make  cell height and width dynamic
    @Override
    public void onBindCellViewHolder(AbstractViewHolder holder, Object cellItemModel, int columnPosition, int rowPosition) {

        // It is necessary to remeasure itself.
        View columnHeaderView = columnHeaderLayoutManager.findViewByPosition(columnPosition);
        View rowHeaderView = rowHeaderLayoutManager.findViewByPosition(rowPosition);

        // set dynamic height and width to cell view
        holder.itemView.getLayoutParams().width = columnHeaderView.getWidth();
        holder.itemView.getLayoutParams().height = rowHeaderView.getHeight();

        holder.itemView.requestLayout();
    }


Append information

I would love to have two more information for the table:
Is the wallet cloud based or edge based. In case of organization based wallets I would prefer a cloud one. Or maybe even as a human being I prefer a cloud one with for example confidential computing.
Another point would be links to the projects, especially when they are open source
Great work @maaikevanleuken and your team! :)

Thanks @cre8 for your suggestions. This issue will be resolved once PR3 is resolved.

There are solutions to run a docker container in a confidential computing environment, see https://kubernetes.io/blog/2023/07/06/confidential-kubernetes/ I don't know any specific wallet that is advertising to have build in confidential computing, but with this approach every cloud wallet should work with this with solutions like this: https://github.com/edgelesssys/constellation


Unable to connect to more than ~48 peers when running crust_peer example on OS X

Running crust_peer on OS X 10.11 with a crust_peer.crust.config file containing endpoints of 64 droplets all running crust_peer yields the following error:
Connected to peer at Tcp(V4(<IP_ADDRESS>:5483))
Connected node count: 48
    [0] Connection(Tcp V4(<IP_ADDRESS>:55073) -> V4(<IP_ADDRESS>:5483))
    [1] Connection(Tcp V4(<IP_ADDRESS>:55074) -> V4(<IP_ADDRESS>:5483))
    [2] Connection(Tcp V4(<IP_ADDRESS>:55075) -> V4(<IP_ADDRESS>:5483))
    [3] Connection(Tcp V4(<IP_ADDRESS>:55076) -> V4(<IP_ADDRESS>:5483))
    [4] Connection(Tcp V4(<IP_ADDRESS>:55077) -> V4(<IP_ADDRESS>:5483))
    [5] Connection(Tcp V4(<IP_ADDRESS>:55078) -> V4(<IP_ADDRESS>:5483))
    [6] Connection(Tcp V4(<IP_ADDRESS>:55079) -> V4(<IP_ADDRESS>:5483))
    [7] Connection(Tcp V4(<IP_ADDRESS>:55080) -> V4(<IP_ADDRESS>:5483))
    [8] Connection(Tcp V4(<IP_ADDRESS>:55081) -> V4(<IP_ADDRESS>:5483))
    [9] Connection(Tcp V4(<IP_ADDRESS>:55082) -> V4(<IP_ADDRESS>:5483))
    [10] Connection(Tcp V4(<IP_ADDRESS>:55083) -> V4(<IP_ADDRESS>:5483))
    [11] Connection(Tcp V4(<IP_ADDRESS>:55084) -> V4(<IP_ADDRESS>:5483))
    [12] Connection(Tcp V4(<IP_ADDRESS>:55085) -> V4(<IP_ADDRESS>:5483))
    [13] Connection(Tcp V4(<IP_ADDRESS>:55086) -> V4(<IP_ADDRESS>:5483))
    [14] Connection(Tcp V4(<IP_ADDRESS>:55087) -> V4(<IP_ADDRESS>:5483))
    [15] Connection(Tcp V4(<IP_ADDRESS>:55088) -> V4(<IP_ADDRESS>:5483))
    [16] Connection(Tcp V4(<IP_ADDRESS>:55089) -> V4(<IP_ADDRESS>:5483))
    [17] Connection(Tcp V4(<IP_ADDRESS>:55090) -> V4(<IP_ADDRESS>:5483))
    [18] Connection(Tcp V4(<IP_ADDRESS>:55091) -> V4(<IP_ADDRESS>:5483))
    [19] Connection(Tcp V4(<IP_ADDRESS>:55092) -> V4(<IP_ADDRESS>:5483))
    [20] Connection(Tcp V4(<IP_ADDRESS>:55093) -> V4(<IP_ADDRESS>:5483))
    [21] Connection(Tcp V4(<IP_ADDRESS>:55094) -> V4(<IP_ADDRESS>:5483))
    [22] Connection(Tcp V4(<IP_ADDRESS>:55095) -> V4(<IP_ADDRESS>:5483))
    [23] Connection(Tcp V4(<IP_ADDRESS>:55096) -> V4(<IP_ADDRESS>:5483))
    [24] Connection(Tcp V4(<IP_ADDRESS>:55097) -> V4(<IP_ADDRESS>:5483))
    [25] Connection(Tcp V4(<IP_ADDRESS>:55098) -> V4(<IP_ADDRESS>:5483))
    [26] Connection(Tcp V4(<IP_ADDRESS>:55099) -> V4(<IP_ADDRESS>:5483))
    [27] Connection(Tcp V4(<IP_ADDRESS>:55100) -> V4(<IP_ADDRESS>:5483))
    [28] Connection(Tcp V4(<IP_ADDRESS>:55101) -> V4(<IP_ADDRESS>:5483))
    [29] Connection(Tcp V4(<IP_ADDRESS>:55102) -> V4(<IP_ADDRESS>:5483))
    [30] Connection(Tcp V4(<IP_ADDRESS>:55103) -> V4(<IP_ADDRESS>:5483))
    [31] Connection(Tcp V4(<IP_ADDRESS>:55105) -> V4(<IP_ADDRESS>:5483))
    [32] Connection(Tcp V4(<IP_ADDRESS>:55107) -> V4(<IP_ADDRESS>:5483))
    [33] Connection(Tcp V4(<IP_ADDRESS>:55109) -> V4(<IP_ADDRESS>:5483))
    [34] Connection(Tcp V4(<IP_ADDRESS>:55111) -> V4(<IP_ADDRESS>:5483))
    [35] Connection(Tcp V4(<IP_ADDRESS>:55113) -> V4(<IP_ADDRESS>:5483))
    [36] Connection(Tcp V4(<IP_ADDRESS>:55115) -> V4(<IP_ADDRESS>:5483))
    [37] Connection(Tcp V4(<IP_ADDRESS>:55117) -> V4(<IP_ADDRESS>:5483))
    [38] Connection(Tcp V4(<IP_ADDRESS>:55119) -> V4(<IP_ADDRESS>:5483))
    [39] Connection(Tcp V4(<IP_ADDRESS>:55121) -> V4(<IP_ADDRESS>:5483))
    [40] Connection(Tcp V4(<IP_ADDRESS>:55123) -> V4(<IP_ADDRESS>:5483))
    [41] Connection(Tcp V4(<IP_ADDRESS>:55125) -> V4(<IP_ADDRESS>:5483))
    [42] Connection(Tcp V4(<IP_ADDRESS>:55127) -> V4(<IP_ADDRESS>:5483))
    [43] Connection(Tcp V4(<IP_ADDRESS>:55129) -> V4(<IP_ADDRESS>:5483))
    [44] Connection(Tcp V4(<IP_ADDRESS>:55131) -> V4(<IP_ADDRESS>:5483))
    [45] Connection(Tcp V4(<IP_ADDRESS>:55133) -> V4(<IP_ADDRESS>:5483))
    [46] Connection(Tcp V4(<IP_ADDRESS>:55135) -> V4(<IP_ADDRESS>:5483))
    [47] Connection(Tcp V4(<IP_ADDRESS>:55137) -> V4(<IP_ADDRESS>:5483))
Udp socket count: 0

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 35, message: "Resource temporarily unavailable" } }', ../src/libcore/result.rs:736
stack backtrace:
   1:        0x10fd16a58 - sys::backtrace::tracing::imp::write::h7ae3fb30e3d277c5yZs
   2:        0x10fd1852f - panicking::log_panic::_<closure>::closure.38948
   3:        0x10fd17fd9 - panicking::log_panic::h2463655e45799b7bJOw
   4:        0x10fd055c6 - sys_common::unwind::begin_unwind_inner::h1e0a110fc6710e2561r
   5:        0x10fd059ae - sys_common::unwind::begin_unwind_fmt::hde354428d7b06c2ec1r
   6:        0x10fd160e7 - rust_begin_unwind
   7:        0x10fd39770 - panicking::panic_fmt::hb9f15bd9c64410c4kMK
   8:        0x10fba0905 - result::_<impl>::unwrap::unwrap::h4507272197241775999
   9:        0x10fc2c51c - asynchronous::_<impl>::process_parallel::_<closure>::closure.23051
  10:        0x10fc29a76 - boxed::_<impl>::call_box::call_box::h6204665560060982022
  11:        0x10fb79572 - sys_common::unwind::try::try_fn::try_fn::h8694432854930233049
  12:        0x10fd15f28 - __rust_try
  13:        0x10fd133ee - sys_common::unwind::try::inner_try::h01d33f1b9d169bb6EYr
  14:        0x10fb79717 - boxed::_<impl>::call_box::call_box::h7455542894398686131
  15:        0x10fd178fd - sys::thread::_<impl>::new::thread_start::h68e6f797e733185eZlw
  16:     0x7fff9c8219b0 - _pthread_body
  17:     0x7fff9c82192d - _pthread_start
thread 'State::bootstrap_off_list' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError', ../src/libcore/result.rs:736
stack backtrace:
   1:        0x10fd16a58 - sys::backtrace::tracing::imp::write::h7ae3fb30e3d277c5yZs
   2:        0x10fd1852f - panicking::log_panic::_<closure>::closure.38948
   3:        0x10fd17fd9 - panicking::log_panic::h2463655e45799b7bJOw
   4:        0x10fd055c6 - sys_common::unwind::begin_unwind_inner::h1e0a110fc6710e2561r
   5:        0x10fd059ae - sys_common::unwind::begin_unwind_fmt::hde354428d7b06c2ec1r
   6:        0x10fd160e7 - rust_begin_unwind
   7:        0x10fd39770 - panicking::panic_fmt::hb9f15bd9c64410c4kMK
   8:        0x10fc12846 - state::_<impl>::bootstrap_off_list::_<closure>::closure.22314
   9:        0x10fc0d896 - boxed::_<impl>::call_box::call_box::h5903651598099049785
  10:        0x10fb79572 - sys_common::unwind::try::try_fn::try_fn::h8694432854930233049
  11:        0x10fd15f28 - __rust_try
  12:        0x10fd133ee - sys_common::unwind::try::inner_try::h01d33f1b9d169bb6EYr
  13:        0x10fb79717 - boxed::_<impl>::call_box::call_box::h7455542894398686131
  14:        0x10fd178fd - sys::thread::_<impl>::new::thread_start::h68e6f797e733185eZlw
  15:     0x7fff9c8219b0 - _pthread_body
  16:     0x7fff9c82192d - _pthread_start

The example continues to run, and is usable (i.e. sending/receiving messages from connected peers succeeds), but the bootstrap event is not reported.
Further connections cannot be made using the connect option (although again, the tool continues to run after the panic).  These yield errors like:
> connect Tcp(<IP_ADDRESS>:5483)
Connecting to Tcp(V4(<IP_ADDRESS>:5483))
> thread 'Service::connect' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 35, message: "Resource temporarily unavailable" } }', ../src/libcore/result.rs:736
stack backtrace:
   1:        0x10f687a58 - sys::backtrace::tracing::imp::write::h7ae3fb30e3d277c5yZs
   2:        0x10f68952f - panicking::log_panic::_<closure>::closure.38948
   3:        0x10f688fd9 - panicking::log_panic::h2463655e45799b7bJOw
   4:        0x10f6765c6 - sys_common::unwind::begin_unwind_inner::h1e0a110fc6710e2561r
   5:        0x10f6769ae - sys_common::unwind::begin_unwind_fmt::hde354428d7b06c2ec1r
   6:        0x10f6870e7 - rust_begin_unwind
   7:        0x10f6aa770 - panicking::panic_fmt::hb9f15bd9c64410c4kMK
   8:        0x10f53a659 - tcp_connections::upgrade_tcp::h47a09dd6721c4412XQc
   9:        0x10f50509f - state::_<impl>::connect::h36b16da45e55b841Fce
  10:        0x10f503c73 - boxed::_<impl>::call_box::call_box::h16820619058248378462
  11:        0x10f4ea572 - sys_common::unwind::try::try_fn::try_fn::h8694432854930233049
  12:        0x10f686f28 - __rust_try
  13:        0x10f6843ee - sys_common::unwind::try::inner_try::h01d33f1b9d169bb6EYr
  14:        0x10f4ea717 - boxed::_<impl>::call_box::call_box::h7455542894398686131
  15:        0x10f6888fd - sys::thread::_<impl>::new::thread_start::h68e6f797e733185eZlw
  16:     0x7fff9c8219b0 - _pthread_body
  17:     0x7fff9c82192d - _pthread_start

This is repeatable - every attempt so far has had similar results with only the actual number of successful connections varying slightly.
Running ulimit -a yields:
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 512
pipe size            (512 bytes, -p) 1
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 709
virtual memory          (kbytes, -v) unlimited

Should be fixed by this PR


S3FileSystem generates a significant amount of redundant requests

Describe the bug, including details regarding any error messages, version, and platform.
I am using the S3 Filesystem abstractions to process a large Parquet dataset. The job reads data in batches and incrementally produces a new set of Parquet files. During the execution it checkpoints it's work.
The checkpointing code is fairly rudamentary: we incrementally write a Parquet file to the checkpoint/ prefix, and periodically copy it to the output/ directory using fs.move(). We then write a .json file to the checkpoint directory detailing the current progress. Not perfect, but works well enough for our needs.
After implementing this I analyzed the requests to the bucket and found a surprising number of requests where being made. For one job, 520,752 requests where made to the checkpointing/ prefix in S3, whereas only 74,331 requests where made to read + write the dataset. This is a significant discrepency - nearly 7x the number of requests!
The following is a table of requests to the checkpoint prefix broken down by type:

operation
total

REST.GET.OBJECT
91871

REST.POST.UPLOADS
84285

REST.PUT.PART
84262

REST.POST.UPLOAD
84261

REST.COPY.OBJECT
42131

REST.COPY.OBJECT_GET
42131

REST.PUT.OBJECT
42129

REST.DELETE.OBJECT
42129

REST.HEAD.OBJECT
7553

I've dug into this and here are the reasons why:
126,388 of the REST.PUT.PART, REST.POST.UPLOADS and REST.POST.UPLOAD requests are made while writing the small .json checkpoint files. Due to this issue, despite being less than 1kb in size and few in number each creation of the .json checkpoint files requires 3 requests to S3.
A further 126,420 requests are also multipart uploads, whilst creating Parquet files. Looking at the statistics, ~50% of the multipart upload requests could have been avoided with an initial 30 megabyte buffer before initiating a multipart upload.
The 42,129 requests with the type REST.PUT.OBJECT are due to the implementation of move() and delete(): it currently attempts to re-create the parent directory after a copy or delete - this is because if there is only a single file in the prefix and we move/delete it, then the prefix will no longer exist. The workaround as implemented is to create a 0-sized object with the name of the prefix, ensuring that it still "exists".
The 7,553 requests with the type REST.HEAD.OBJECT comes in part from from the implementation of DeleteObject, where we make a HeadObject request before deleting a key.
Performance with versioned buckets
While it's noble to attempt to create a proper "filesystem" facade over S3, there are inherent issues with this in terms of cost and performance.
One major thing that worries me is the EnsureparentExists() that is called from DeleteDir, DeleteFile and Move methods. In a versioned bucket, this will repeatedly create empty keys to mimic a directory.
Given a pathalogical case where you do something like this from multiple processes/threads:
sfs = fs.S3FileSystem()

for _ in range(10000):
    path = f"a_bucket/some_directory/{uuid.uuid4()}"
    with sfs.open_output_stream(path) as fd:
        fd.write(b'hi')
    sfs.move(path, f"a_bucket/some_other_directory/{uuid.uuid4()}")

Then we will end up with many tens of thousands of versioned objects with the key some_directory/.
One lesser-known thing about S3 versioned buckets is that list_objects_v2 (and list_objects) calls have to skip over deleted/noncurrent versions of objects. While this is fast, it can get very slow - I've seen prefixes take over a minute to list objects due to the number of noncurrent/deleted objects within those prefixes (i.e listing an outer "directory" takes longer if there are many deleted/noncurrent children within sub-directories). Obviously lifecycle policies can clean these out, but that only happens once a day or so.
You will also almost certainly run into S3 request limits when you repeatedly call PutObject on a single key at high volume - requests limits in aggregate are very high for S3, but for a single key they can be much lower.
Component(s)
C++, Python

Then we will end up with many tens of thousands of versioned objects with the key some_directory/.

The solution here may be just checking that the empty dir marker exists instead of re-creating it unconditionally.

Then we will end up with many tens of thousands of versioned objects with the key some_directory/.

The solution here may be just checking that the empty dir marker exists instead of re-creating it unconditionally.

That’s no guarantee though, and would generate a lot of redundant requests.
Another idea would be to stop trying to emulate directories on S3. This would need to be feature gated in some way as there may be conditional code that relies on the existence of a directory, but if the feature is enabled (via a flag or a s3 filesystem subclass) then the “directory exists” function always returns True?
I think it’s a fare trade-off if you know you want it?

... then the “directory exists” function always returns True?

I suggested something like this months ago while implementing AzureFileSystem but quickly learned that these "simplifications" break a lot of the invariants arrow::FileSystem interface is supposed to guarantee. The reason S3 and other blob stores don't offer FS semantics is efficiency and ability to distribute the system without breaking the filesystem invariants.
The true fix would be to have datasets loaded from an arrow::ObjectStore abstraction that is emulated on local-filesystem instead of going through an arrow::FileSystem abstraction that is emulated on top of object storage systems like S3.


Add request timeout support for msnodesqlv8 queries.

Hello,
My project is utilizing the node-mssql library with the msnodesqlv8 driver. We chose msnodesqlv8 since we need support for features like Windows Authentication and Azure Active Directory Authentication (internal company application). Recently, we've noticed that requestTimeout option for mssql doesn't seem to be respected when using the msnodesqlv8 driver. We have just completed an effort to upgrade our application to node 6 (from node 0.10.x!) and upgraded our node libraries in the process. We had previously been using a very old version of this library, using msnodesql (not v8) driver that didn't seem to have this problem (or, if it did, we never noticed). After looking into it, it seems like this is due to the issue you brought up here: https://github.com/TimelordUK/node-sqlserver-v8/issues/9, regarding lack of request cancellation support in msnodesqlv8.
Our application is being hampered by occasional long-running queries, and so I've implemented a solution for our purposes built on top of the query timeout API of node-sqlserver-v8. I know you're still waiting on request cancellation, but do you think this would be a "good enough" solution for now to pull into the main branch?

Looks nice, thank you for your contribution.

nice work.   As it happens, I have started to look at cancel and will let you know my progress.   I am glad you have found use for msnodesqv8 via the excellent node-mssql.


Proposed SIG-Simulation meeting agenda for 2023/01/05 (replacing the meeting on 2022/12/29)

Meeting Details

Date/Time: 2023/01/05 (instead of 2022/12/29) @ 16:30 (24-hour) UTC due to the holiday season
Location: Discord SIG-Simulation Voice Room

The SIG-Simulation Meetings repo contains the historical past calls, including a link to the agenda, recording, notes, and resources.
SIG Updates
What happened since the last meeting?
Meeting Agenda
(see info from last meeting - https://github.com/o3de/sig-simulation/issues/30#issuecomment-1334073465)
Discuss agenda from proposed topics

Discuss sig-simulation planning for 2023
Review this issue in case it has not been addressed by the time of the meeting - https://github.com/o3de/sig-simulation/issues/33
Notify sig-simulation about movement of Blast Gem for those who don't already know about it (see https://discord.com/channels/805939474655346758/1050089862583287898 for info)
Review https://github.com/o3de/sig-simulation/issues/31

Outcomes from Discussion topics
Discuss outcomes from agenda
Action Items
Create actionable items from proposed topics
Open Discussion Items
List any additional items below

https://github.com/o3de/sig-simulation/issues/33 was approved
PhysX 5 support is coming to O3DE and a fork of PhysX 5 has been created under the o3de organization
The simulation roadmap planning project board is now public at https://github.com/orgs/o3de/projects/23


chore: unused dependency

Codecov Report

Merging #154 (21fb7cf) into main (8b8c2ee) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #154   +/-   ##
=======================================
  Coverage   91.08%   91.08%
=======================================
  Files          66       66
  Lines        1424     1424
=======================================
  Hits         1297     1297
  Misses        127      127


fix: typescript codegen with strict settings

WARNING: I couldn't find how to test this changes. yarn test in noir-compiler folder doesn't seem to do anything.
Closes #4152. Also, prepends all type imports with type keyword, so generated files in projects with "verbatimModuleSyntax": true in tsconfig.json will typecheck properly.

We do public override methods so not an issue anymore


phasedDiagram0

Chris and I were a little tripped up a little by some of the labeling on this new diagram. The matrix layout with the labels for force and dampening were getting confused for labels of the axis, which are actually velocity and position.
Here's the original diagram:

Here's a proposed reworking of this diagram (ignore the color shifts):

The horizontal layout, while sacrificing some of the matrix comparisons, removes the confusion of axis labels and is a little more readable on smaller laptop screens that have short vertical height.
This next point is minor: I dropped the formulas, because the formula is shown one paragraph previous. When I first was reading through it I thought these were entirely new formulas, not just the same formula repeated with values filled in. Just felt like a little more work than was necessary.

Here's another idea too:


 loading indicator overlays button text

The text should hide while the indicator shows.

Closed by https://github.com/silverstripe/silverstripe-framework/issues/5958


Agent auto-register timeout at Elastic Agent Profiles level

Hi Guys
Thank you for the awesome plugin.
Can I request a feature - for having the Agent auto-register timeout
at Elastic Agent Profiles.
We are planning to have different agents - java, node ,Golang etc
and each of the agents could have different up time.
I can contribute if needed
Thanks
Saif

@saifally - I think you mean the timeout before which the agent is killed. That's what I understood from up time. Do you mind telling why you require different up times for these? Each elastic agent that comes up, even if it stays idle, without dying, it won't be used for the next job.

Yes, that what I meant.
Our requirement is to have different type of agents - some for build - java code compile etc,some for integration tests that would have longer up time. The agents and their pods are up until this timeout is reached  and that reduces the capacity on the kubernetes cluster

This is not relevant with single-shot agents in EAv3. To reconsider relevance when/if agent reuse is introduced, e.g via https://github.com/gocd/kubernetes-elastic-agents/pull/355


SDM@K metric setting question etc.

Hi,
Thank you for sharing this excellent work. I have a few questions regarding the use of the dataset for my own research:

Why is the threshold in the SDM@K calculation set to 0.001? Is this value adjustable, or is it purely based on empirical findings?

I noticed that the project includes preparation code for the Visloc dataset, but I did not find any experimental results on the Visloc dataset in the paper. Could you clarify this discrepancy?

Could you provide details about the hardware configuration used for sampling the dataset?

Looking forward to your response.
Best.

Thanks for your interest in our work.

Yes, it is purely based on empirical findings. The original definition of SDM@K from DenseUAV sets $s=5\times 10^3$. However, since the original definition is for lat. and lon. calculations, and here it is applied to meter-level distances, we empirically set this value to 0.001 to have a better numerical distinction.
The preparation codes are for public UAV-VisLoc dataset, and we do have experimental results on Table.4. Since we did not conduct thorough selection and inspection on this dataset and only used a portion of it for the extension and validatino of our experimental setup, this part of the work has not been well organized yet and only serve as a reference.
Do you mean the GTAV simulation? This will not lead to significant resource consumption, and I believe a standard Windows PC can handle it.

Thank you for your prompt response. Your answer has cleared up my doubts, and I apologize for overlooking the evaluations on the Visloc dataset in Table 4.
Another question:
I was wondering if it would be possible to extend the dataset to include variations under different illumination and weather conditions, and use it as a test set to evaluate generalization performance. Would it be practical to modify these settings within the simulation?
Thank you!

That's an interesting idea. And yes, it's feasible.
Maybe we could work on it together :)

Okay, i have sent the contact info to your email.


Cloud Engineering Summit content

This PR adds all the content from the Cloud Engineering Summit on the website and lists them on the /resources page. This PR also introduces a podcast rss.xml feed so we can list our content on Spotify, Itunes, etc. In addition to an RSS feed, there is also a listing page for Podcasts that was created for mostly SEO purposes. One issue is that we cannot currently link to the Podcast listings on the site because we need the RSS feed to exist before we can wire up the links. So there will be a follow-up PR once our Podcast channels are created.

Purely on the surface, I think we should store these files outside the repository and just check the links to them. There's no need to check them into Git.

@cnunciato @justinvp I removed all the podcast stuff so this is ready for review.


Escape SQL like

Signed-off-by: Dan Kohn<EMAIL_ADDRESS>

From Rails console:
irb(main):021:0> Project.text_search 'hello'
  Project Load (1.6ms)  SELECT "projects".* FROM "projects" WHERE (("projects"."name" ILIKE 'hello%' OR "projects"."homepage_url" ILIKE 'hello%') OR "projects"."repo_url" ILIKE 'hello%')  ORDER BY "projects"."created_at" ASC
=> #<ActiveRecord::Relation []>
irb(main):022:0> Project.text_search 'hello%%'
  Project Load (1.5ms)  SELECT "projects".* FROM "projects" WHERE (("projects"."name" ILIKE 'hello\%\%%' OR "projects"."homepage_url" ILIKE 'hello\%\%%') OR "projects"."repo_url" ILIKE 'hello\%\%%')  ORDER BY "projects"."created_at" ASC
=> #<ActiveRecord::Relation []>


Committing an object deletion to master erases object from all commits to master - #997

fixed in regular and by prefix listing

Also, can we retitle this?  AFAICT it does not "erase the object from all commits from master", see my comments on #997 where I reproduced.  The objects are deleted from the listings, but they still exist.  We should avoid misinformation.

Codecov Report

Merging #1000 (b40208a) into master (b1b3858) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1000   +/-   ##
=======================================
  Coverage   44.26%   44.26%
=======================================
  Files         140      140
  Lines       11570    11570
=======================================
  Hits         5121     5121
+ Misses       5799     5798    -1
- Partials      650      651    +1

Impacted Files
Coverage Δ

catalog/mvcc/cataloger_list_entries.go
85.21% <100.00%> (-0.32%)
:arrow_down:

catalog/mvcc/views.go
100.00% <100.00%> (+2.98%)
:arrow_up:

catalog/mvcc/cataloger_commit.go
74.28% <0.00%> (-5.72%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
62.96% <0.00%> (+3.70%)
: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 b1b3858...b40208a. Read the comment docs.

This comment (missed in the commits) needs to be addressed immediately:

Also, can we retitle this? AFAICT it does not "erase the object from all commits from master", see my comments on #997 where I reproduced. The objects are deleted from the listings, but they still exist. We should avoid misinformation.

The title of this PR is simply the title of issue #997.  That issue was titled without a root-cause analysis, since it came from outside (thanks again, @tsykes-2020, for a really good catch!).   To limit further fallout I am changing the PR title unilaterally.  @tzahij  and others: please feel free to correct the title further as needed!


c_glib: Compiler: Omit processing-function defs for empty services

With this change the compiler omits the processing-function-definition array for a service with no methods, corresponding to the checks on lines 2555 and 2562 that omit the code that would use this array under the same condition.

Committed as part of THRIFT-3284


Feature/support awss3

AWS S3 support has been added and a complete redesign of the script architecture has been carried out


Dev

metadata scraping updates. Long awaited itunes fix. Seems to work alright.

This should fix #3 too, right? I'm satisfied with the new changes btw, let's see if anyone else chimes in


Microsoft.Build.Sql: does not work with NuGet centralized package management

SqlPackage or DacFx Version: 0.1.10-preview
.NET Framework (Windows-only) or .NET Core: .NET 7.0
Environment (local platform and source/target platforms): Windows, GitHub Actions on Ubuntu / Windows agents

Steps to Reproduce:
Using the following config in Directory.Packages.props:
<Project>
  <PropertyGroup>
    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
  </PropertyGroup>
  <!-- SQL Build Tools -->
  <ItemGroup>
    <PackageVersion Include="Microsoft.Build.Sql" Version="0.1.10-preview" />
  </ItemGroup>
</Project>

And the following .sqlproj schema, created using the dotnet new sqlproj template:
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build">
  <Sdk Name="Microsoft.Build.Sql"/>
  <PropertyGroup>
    <Name>Sdkbin.Database</Name>
    <DSP>Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider</DSP>
    <ModelCollation>1033, CI</ModelCollation>
  </PropertyGroup>
</Project>

And the following global.json:
{
  "sdk": {
    "rollForward": "latestMinor",
    "version": "7.0.100"
  },
   "msbuild-sdks": {
        "Microsoft.Build.Sql": "0.1.10-preview"
    }
}

Running dotnet build -c Release produces the following error:
C:\Repositories\project\MyApp.Database.sqlproj : error NU1008: Projects tha t use central package version management should not define the version on the PackageReference items but on the Package Version items: Microsoft.NETFramework.ReferenceAssemblies.
    0 Warning(s)
    1 Error(s)

I tried working around this by updating Directory.Packages.props to:
<Project>
  <PropertyGroup>
    <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
  </PropertyGroup>
  <!-- SQL Build Tools -->
  <ItemGroup>
    <PackageVersion Include="Microsoft.Build.Sql" Version="0.1.10-preview" />
    <PackageVersion Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" />
  </ItemGroup>
</Project>

But I still get the same build error.
Did this occur in prior versions?  If not - which version(s) did it work in?
Haven't used this tool before and this is a greenfield project, so I don't know.

As far as I understand NuGet expects PackageReferences and FrameworkReferences inside of Sdks to have IsImplicitlyDefined="true" set. A PackageVersion would not be needed then as well.
Just thinking out loud: maybe this issue should not happen, because it's a side effect of importing Microsoft.Common.props, which is part of the .Net build. So not settings the target framework etc. makes it fall back to .Net Framework and complain.

I was able to work around this by adding a new Directory.Packages.props file into the folder where just my DacFx project lives:
<Project>
  <PropertyGroup>
    <ManagePackageVersionsCentrally>false</ManagePackageVersionsCentrally>
  </PropertyGroup>
  <!-- SQL Build Tools -->
  <ItemGroup>
    <PackageVersion Include="Microsoft.Build.Sql" Version="0.1.10-preview" />
    <PackageVersion Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" />
  </ItemGroup>
</Project>

Disabling centralized NuGet package management there did the trick.

I'm suggesting you to change it to this form:
<ItemGroup>     <PackageVersion Update="Microsoft.Build.Sql" Version="0.1.10-preview" />     <PackageVersion Update="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" />   </ItemGroup>
Notice the change from Include to Update. You use Include form in the projects and Update+Version attributes at central place.


DEP: Closes #18577

Reference issue

Closes #18577
What does this implement/fix?
.
Deprecates the positional arguments in sparse.linalg.gmres method.
Additional information

I am a first time contributor to SciPy. Do I need to write some documentation in /doc folder?

Thanks for the contribution! I will let @h-vetinari confirm what he had in mind here, but we cannot do this directly as it is not backwards compatible.

Thanks for your contribution @bathongor, in this case, I chose to merge @h-vetinari PR as it tackled all the iterative solvers at once however your contribution is still very much valued even if it didn't end up being merged.


fix(Dropdown): keep dropdown open when closeOnChange is set to false

Root cause: When options prop is used, clicking on the dropdown item will trigger handleItemClick which will utilize closeOnChange properly.
When options prop is undefined(using children), clicking on the dropdown item will trigger handleClick instead which will use toggle(if search prop is falsy) instead of closeOnChange.
Fix: Replaced this.close(e) in toggle with this.closeOnChange(e) to keep dropdown open when closeOnChange is set to false.
issue: Dropdown: ignores closeOnChange if it has children and isn't a search #2041

Codecov Report

Merging #2074 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #2074   +/-   ##
=======================================
  Coverage   99.76%   99.76%
=======================================
  Files         149      149
  Lines        2588     2588
=======================================
  Hits         2582     2582
  Misses          6        6

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
100% <100%> (ø)
: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 164b338...0cb7433. Read the comment docs.

I'm hesitant on this.  We don't support state management when there are children in the Dropdown, the user needs to manage state in that case.

The fact that the click event is bubbling to the top level handleClick is due the user not handling the click themselves.  This subcomponent Dropdown API will likely be removed in favor of shorthand props only, see #1757.
The main issue I have is that the toggle() method should simply toggle the Dropdown, without regard to any other state or conditions.  Currently, changing toggle to use closeOnChange works only by happenchance.  However, if toggle is called in a case where it should absolutely toggle irrespective of a change event, it will fail.
I'm leaning toward not moving forward on this change, but it would be great to get some feedback.

it's good to know the API changes for Dropdown.
You're spot on regarding the issue and toggle(). Currently, using closeOnChange() in toggle() simply checks if either multiple is true or closeOnChange is false in addition to calling this.close(). However, I can understand this may be confusing when toggle() is being used more often in the future than just handleClick() and handleIconClick() rightnow.
My opinion on the shorthand only is I'm afraid it may lose some flexibilities, but I might be wrong.
If not moving forward with the PR, my suggestion is to let users know that they need to use the onClick prop with e.stopPropagation() on children in order for closeOnChange to work properly.

OK, we'll close this for now then.

My opinion on the shorthand only is I'm afraid it may lose some flexibilities, but I might be wrong.

I would be interested to see the use cases you are concerned with over at #1757.  My thinking is that JSX components have the ability to map 1:1 to JS objects, making all scenarios possible.

If not moving forward with the PR, my suggestion is to let users know that they need to use the onClick prop with e.stopPropagation() on children in order for closeOnChange to work properly.

I don't want to begin telling users what they'd need to do to get subcomponents working as in the future we will not have support for them.  Also, to get them working properly, they'd actually need to rewrite the all dropdown logic surrounding options :)  This is largely why we're not supporting them, it isn't really practical for users to try to rewrite the state management for options.


Kubernetisation Rework

Removed ETCD
Cleaned up
Improved docker-compose.yml
Fixed Dockerfile to support npm run build
Improved docs
Added VSCode docker debug setup

WARNING Contains BC so merge considering related projects state

Ok guys I hope you have reviewed it.


Error when importing images using aliases

Hello all,
Recently I have updated my project and my eslint has started complaining when I import an image using an alias (extraneous dependency error). In order to get rid of this error I added:
"import/ignore": ["/*.png/", "/*.jpg/"]
Which made my webpack build is ok as expected. However, VSCode highlights my "import myimage from @Images/my_image.png" as red due to "import/no-extraneous-dependencies".
On the other hand if I have:
"import/ignore":["*.png", "*.jpg"]
Then the highlight red error from VSCode goes away but my webpack build throws:
ERROR in Invalid regular expression: *.png: Nothing to repeat
Occurred while linting blabla\index.js:2

It looks like VSCode ESLint plugin and webpack eslint stuff do not use the same patterns for import/ignore.
I have created the following repo where I get the same result:
https://github.com/javierguzman/eslint-error
You may need to do npm install --force for the node_modules.
In order to reproduce the error:

Open Header.tsx and you will see no error highlights
Run "npm run build:production"
You get the invalid regular expression
Change the expression of import/ignore
Run "npm run build:production" and it is ok
However if you go to Header.tsx you will see the import marked as red due to extraneous dependencies

I hope my configuration is not that bad :smile: I have two eslint configuration, one for development and one for production. build:production as well as vscode uses the production es lint configuration. This can be seen in the vscode configuration folder under the repository I have created.
Please, let me know if you need something else from me.
Thank you in advance for the help and regards
p.s. the lint configuration to be looked at is .eslintrc.json, ignore the development one

Why is webpack running eslint at all? The build process should be entirely separate from testing.

I’m also very confused why you’d have two linting configurations. Production code is the build output, this is never linted.

I come from embedded software and I have learned everything about web apps, etc. on my own so I might not be doing stuff properly.
Having said that, the package called "eslint-webpack-plugin" has 2m downloads on npm and if I am not mistaken its purpose is to run eslint when running webpack, if I have not missed anything, I am not the only one. Or am I mistaken?
I have two configurations because when I am in develop mode I am more flexible as I usually play around a ton. But let's stick with .eslintrc.json as is the one I am using when calling build:production and the one used in the vscode configuration. I think I forgot to mention that.

You’re not the only one, of course, but that doesn't mean it’s the right way to do it :-)
So with the production config, which theoretically runs in the cli, vscode, and así webpack, you’re getting different results? Note that the CLI is the source of truth.

Yes, that makes perfect sense to me.
to run eslint directly, make sure it’s installed as a dev dep (it shouldn’t ever be global), and then run npx eslint .. You can put eslint . in an npm run-script as well - i usually make one called “lint” and then another called “pretest” that runs npm run lint.

This is interesting, I got the same "webpack" error while running eslint cli:
❯ npx eslint ./src/* -c ./config/.eslintrc.json

Oops! Something went wrong! :(

ESLint: 7.32.0

SyntaxError: Invalid regular expression: /*.png/: Nothing to repeat
Occurred while linting MYHIDDENPATH\client\src\index.js:2
    at new RegExp (<anonymous>)
    at ignore (MYHIDDENPATH\client\node_modules\eslint-module-utils\ignore.js:47:19)
    at Function.ExportMap.for (MYHIDDENPATH\client\node_modules\eslint-plugin-import\lib\ExportMap.js:739:31)
    at Function.ExportMap.get (MYHIDDENPATH\client\node_modules\eslint-plugin-import\lib\ExportMap.js:734:463)
    at checkSpecifiers (MYHIDDENPATH\client\node_modules\eslint-plugin-import\lib\rules\named.js:42:46)
    at MYHIDDENPATH\client\node_modules\eslint\lib\linter\safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (MYHIDDENPATH\client\node_modules\eslint\lib\linter\safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (MYHIDDENPATH\client\node_modules\eslint\lib\linter\node-event-generator.js:293:26)
    at NodeEventGenerator.applySelectors (MYHIDDENPATH\client\node_modules\eslint\lib\linter\node-event-generator.js:322:22)

ok, that's great - it means it's reproducible.
What are the contents of that eslint config?

Did you miss my link in my first message? I thought you knew already it was reproducible as I created a repository having the same issue.  The content of the eslint config is in that repository:
https://github.com/javierguzman/eslint-error/blob/main/client/config/.eslintrc.json

oh sorry, i'll try to use that repo.

@javierguzman so, there's no eslint config in that repo, and no lint script, and npx eslint . fails - which means you're only linting with webpack in there. Can you come up with a repro that uses the CLI? That way we're sure it's not webpack or an IDE or something causing the problem.

got it reproduced, thanks :-)

@javierguzman ok so turns out import/ignore is actually a regexp pattern, and "*.png" isn't a valid one because of both the star and the dot. Changing it to ["\\.png$", "\\.jpg$"] seems to make it correctly produce a lint warning.

yes, I got that behavior using  "import/ignore": ["/*.png/", "/*.jpg/"] However, if you open Header.tsx file you should get a red line over import LOGO from<EMAIL_ADDRESS>https://github.com/javierguzman/eslint-error/blob/main/client/src/Features/Header/Header.tsx
So if the correct one is a regexp, then it is the vscode eslint plugin the one not behaving properly...as it hightlights the import of a png file as red when we have specified to ignore those ones.

["/*.png/", "/*.jpg/"] is incorrect as well, since new RegExp strings are not supposed to be bounded by forward slashes.
Change it to ["\\.png$", "\\.jpg$"] and it should be fine.
The current warning is because it thinks @Images/facebook.png is a package - because that's a valid package name. While aliases are best when they can't be a valid package name, either way, you need a custom resolver to be able to resolve @Images/ so that this plugin can know where it points.

Then that is a bug, isn't? I mean if I use ["/*.png/", /*.jpg/"]  the behavior I see is the same as with ["\\.png$", "\\.jpg$"]
On the other hand, I resolve my images in the webpack-common.js file:
https://github.com/javierguzman/eslint-error/blob/main/client/config/webpack-common.js
Here I have:
const resolve = {
    modules: [srcPath, 'node_modules'],
    alias: {
      '@Header': path.resolve(srcPath, 'Features', 'Header'),
      '@Common': path.resolve(rootPath, '..', 'common'),
      '@Images': path.resolve(rootPath, '..', 'common', 'assets', 'images')
    },
    extensions: ['.ts', '.js', '.tsx', '.jsx'],
    fallback: { path: false }
  };

no - /*.png/ in a regex means "a slash, 0 or more times, then any character, then png, then a slash".
If you're resolving those with webpack, then you must use the webpack resolver for eslint-plugin-import: https://github.com/import-js/eslint-plugin-import#resolvers

Oh I see, I thought you were saying ["/.png/", /.jpg/"] is not a valid regex, but you meant it is a valid regex but not the one I was looking for 😄
I have the webpack resolver as well:
"settings": {
        "import/resolver": {
            "node" : {},// due to https://github.com/benmosher/eslint-plugin-import/issues/1396
            "webpack": {
                "config" : "config/webpack-prod.js",
                "extensions": [".js", ".jsx", ".ts", ".tsx"]
            }
        }

You should always have the node resolver - not just due to that closed issue - but the webpack resolver should be listed first.

I had always node first and it has been working fine. Just in case I have placed webpack stuff first and eslint becomes "crazy" as it tries to look for webpack-prod.js under the node_modules, I guess tue to the filepath.toLowerCase message ( I have even restarted eslint server & vscode without success):
[Info  - 8:37:45] ESLint library loaded from: blabla\client\node_modules\eslint\lib\api.js
[Info  - 8:37:48] filepath.toLowerCase is not a function Occurred while linting blabla\client\config\webpack-common.js:1
Error resolving webpackConfig Error: Cannot find module 'blabla\client\node_modules\react-bootstrap\config\webpack-prod.js'
Require stack:
- blabla\client\node_modules\eslint-import-resolver-webpack\index.js
- blabla\client\node_modules\eslint-module-utils\resolve.js
- blabla\client\node_modules\eslint-plugin-import\lib\rules\no-unresolved.js
- blabla\client\node_modules\eslint-plugin-import\lib\index.js
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- blabla\client\node_modules\eslint\lib\cli-engine\cli-engine.js
- blabla\client\node_modules\eslint\lib\cli-engine\index.js
- blabla\client\node_modules\eslint\lib\api.js
- c:\Users\javie\.vscode\extensions\dbaeumer.vscode-eslint-2.1.25\server\out\eslintServer.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:934:15)
    at Module._load (internal/modules/cjs/loader.js:779:27)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:1006:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.exports.resolve (blabla\client\node_modules\eslint-import-resolver-webpack\index.js:86:25)
    at v2 (blabla\client\node_modules\eslint-module-utils\resolve.js:117:23)
    at withResolver (blabla\client\node_modules\eslint-module-utils\resolve.js:122:14)
    at fullResolve (blabla\client\node_modules\eslint-module-utils\resolve.js:139:22)
    at Function.relative (blabla\client\node_modules\eslint-module-utils\resolve.js:84:10) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'blabla\\client\\node_modules\\eslint-import-resolver-webpack\\index.js',
    'blabla\\client\\node_modules\\eslint-module-utils\\resolve.js',
    'blabla\\client\\node_modules\\eslint-plugin-import\\lib\\rules\\no-unresolved.js',
    'blabla\\client\\node_modules\\eslint-plugin-import\\lib\\index.js',
<EMAIL_ADDRESS><EMAIL_ADDRESS>    'blabla\\client\\node_modules\\eslint\\lib\\cli-engine\\cli-engine.js',
    'blabla\\client\\node_modules\\eslint\\lib\\cli-engine\\index.js',
    'blabla\\client\\node_modules\\eslint\\lib\\api.js',
    'myuser\\.vscode\\extensions\\dbaeumer.vscode-eslint-2.1.25\\server\\out\\eslintServer.js'
  ]
}

Try ./config/webpack-prod.js? (note the leading dot)

It seems better but the message "[Info  - 9:32:30] filepath.toLowerCase is not a function Occurred while linting " still appears and makes no difference in the whole behavior. The alias image import is still hightlighted as red. Bear in mind other imports do not have this problem. Right now, it is like the import/ignore is not read properly by vscode eslint plugin. I am going to open an issue in plugin repo as well to check if they can add something.

I have run again npx eslint ./src/features/Header/Header.tsx -c ./config/.eslintrc.json  and still complains about the extraneous dependency, so it is not the plugin I believe.

Hello @ljharb do you any other ideas? I am still facing the same issue. When I mentioned before "is not the plugin I believe" I meant the VSCode plugin.

I don't yet have any other ideas; I'll keep playing with the repo.

Any news about this @ljharb ?

I have continued looking at this and I believe the problem could be summarized to "How to make an alias to an outside project folder".
If I import a TS file from @Common then I get a similar error. However, if I remove the alias and use relative paths ( a ton of ../../) then it works ok.
From the tests I have made, I think the trick is to have properly webpack configuration resolve.alias section (https://github.com/javierguzman/eslint-error/blob/main/client/config/webpack-common.js)  AND tsconfig.json(https://github.com/javierguzman/eslint-error/blob/main/client/tsconfig.json). However, for now I have not discovered what it is missing.
If someone can spot the problem I am all ears.

Yes, webpack aliases should work if you’re using the webpack resolver and webpack is configured correctly. If you’re using TS then tsconfig also has to have the same info.

from https://github.com/import-js/eslint-plugin-import/issues/2230#issuecomment-924632968

I got this error on my project too. On my project, we have an Express server file inside React project and we didn't separate eslint config. So, when we run Webpack will use client-side config, which uses the fallback value for some packages that don't exist on the client-side e.g. fs. And we've set the fallback of fs to be false which breaks that line of eslint-module-utils (causes an error filepath.toLowerCase is not a function).
The quick win solution is to update Webpack config resolve.fallback.fs to be null.
Hope this help.

@ilumin a proper solution is using overrides so that the client and server code have slightly different eslint configs - so the server code doesn't use the webpack resolver at all.


フォロー+フォロワー関係の追加 Close #75

関連するIssue
Close #75
修正の程度

[ ] 破壊的で刷新的な新機能
[x] 軽微な新機能
[ ] バグ修正
[ ] 軽微な修正

概要
UserテーブルにFF関係の列を追加した
変更点

[x] 多対多テーブルの追加
[x] TL画面の雛形作成

Codecov Report

Merging #77 into develop will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #77      +/-   ##
===========================================
+ Coverage    94.05%   94.07%   +0.02%
===========================================
  Files           16       16
  Lines          572      574       +2
===========================================
+ Hits           538      540       +2
  Misses          34       34

Flag
Coverage Δ

#unittests
94.07% <100.00%> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

api/src/app/database/models.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


proc-macro panicked: ParseFloatError { kind: Invalid }

I think I stumbled upon a rust-analyzer bug. Upon trying to make YouCompleteMe work with latest nightly of rust-analyzer, it panicked with the following error message:
proc macro returned error: proc-macro panicked: called Result::unwrap() on an Err value: ParseFloatError { kind: Invalid }
But "cargo build" succeeded using the same nightly toolchain. The code that fails is this one (very small, just one file): https://github.com/lvella/bastroblasto
The offending version: rust-analyzer 3022a2c 2021-05-28 dev

Duplicate of #8928. As a workaround you can use the stable toolchain or disable proc macro support.


[openconnect] move interface changes from start/stop to vpnc script's hooks

This changes allow to change the interface names created from openconnect even if the connection was drop by server and not only by client. It uses standard hooks provided by vpnc-script.
It's related to this issue  #4050

@fichtner Can we get a review on this please? This is a serious issue and causes me to have to manually ssh into the machine everytime this happens to fix it.

@alexyao2015 did you test this PR on your end? it might help to getting this merged if someone else tested the change as well (we don't test these)

@mimugmail needs to take a look, I also cannot verify this

@alexyao2015 did you test this PR on your end? it might help to getting this merged if someone else tested the change as well (we don't test these)

I'm actually using this solution on my router without troubles... every 8h the vpn drops and with a monit it automatically restart the connection with no errors


chore(deps): update dependency typescript to ~5.6.0

This PR contains the following updates:

Package
Type
Update
Change
Pending

typescript (source)
devDependencies
minor
~5.5.0 -> ~5.6.0
5.7.2

Release Notes

microsoft/TypeScript (typescript)
v5.6.3: TypeScript 5.6.3
Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.6.0 (Beta).
fixed issues query for Typescript 5.6.1 (RC).
fixed issues query for Typescript 5.6.2 (Stable).
fixed issues query for Typescript 5.6.3 (Stable).

Downloads are available on:

npm
NuGet package

v5.6.2: TypeScript 5.6
Compare Source
For release notes, check out the release announcement.
For the complete list of fixed issues, check out the

fixed issues query for Typescript 5.6.0 (Beta).
fixed issues query for Typescript 5.6.1 (RC).
fixed issues query for Typescript 5.6.2 (Stable).

Downloads are available on:

npm
NuGet package

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (~5.6.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Cross-compiling CLI on Linux fails for MacOS due to docker-credential-helpers

Using the following command on master branch:
VERSION=${1:-develop}
KUBE_CONSTRAINTS=">=1.14, <=1.19"

echo "Building Keptn CLI for OSX"
env GOOS=darwin GOARCH=amd64 go mod download
env GOOS=darwin GOARCH=amd64 go build -v -x  -ldflags="-X 'main.Version=$VERSION' -X 'main.KubeServerVersionConstraints=$KUBE_CONSTRAINTS'" -o keptn

fails with
build github.com/keptn/keptn/cli: cannot find module for path github.com/docker/docker-credential-helpers/registryurl

This is blocking us from switching from MacOS driven builds to Linux driven builds. In addition it means that we can NOT cross-compile for MacOS.
This is caused by the docker-credentials-helper and is a known-issue for several months: https://github.com/docker/docker-credential-helpers/issues/176

MacOS builds are failing due to a build-env problem on GitHubs side, which blocks our release process for 0.8.2.

MacOS builds have been re-enabled in https://github.com/keptn/keptn/pull/3899
We should up the priority on this issue though, such that we can cross-compile the CLI for MacOS on Linux.


Get top and similar tracks

This does some refactoring to the search controller and results class to handle the concept of not just searches, but other lists of tracks returned by the server. It's a little gross at times because it has to interface Swift's enums with the Objective-C side. I'm not sure if this is the best strategy, but it does seem to work for now; we can split out the new stuff into a separate controller if needed..
Note that the "quality" of the returned tracks is highly dependent on server configuration; Subsonic and Navidrome at least rely on last.fm for anything more intelligent than returning starred tracks.
Fixes GH-108 and GH-109.

@SevereOverfl0w Sorry your feature requests came late. If you (want to) try this, let me know.

I just tried to download the artifact from the build but it's giving me:

You can’t open the application “Submariner.app” because it may be damaged or incomplete.

But, happy to help if it helps you test this out!

Looks like I need to fix the CI setup sometime; you should get a signing issue (I don't sign CI builds), but it should at least work. Here's a signed build for your trouble:
Submariner-e93717757a2e7fdc1645e54c24cbf7aceb0345ac.zip

Generally is working, thanks!  It wasn't clear to me how to go from "Similar Tracks" back to my library though if I changed my mind.  I don't see a "back" button, and clicking on my Server doesn't work because it's already focused.

There is a back/forward pair in the menu, which can be added to the toolbar, but it's not there by default. It should probably be made more obvious. You can also use the trackpad back/forward gestures like in Safari as well.


Auto-update dockerhub readme with readme changes

https://hub.docker.com/r/vegaprotocol/ethereum-event-forwarder has the README contents, but it is manually synced. This could be done by a build step so it doesn’t get out of sync
Tasks

[ ] Add github action to publish README when pushing image

This project is deprecated and no longer supported, because it is now part of the Vega core node.


Added ALT Tags for integrations/cloud-personal-access-tokens.rst

/check-cla

Hello @jaskiratsingh2000,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Closing this PR since the source file has been archived.


Request-Line change request in SRF

Hello Dave,
I was trying to generate a SIP NOTIFY event using srf.request() function.
Since I am working in local setup (i.e. both clients and servers are reachable via IP Addresses only), the "uri" parameter in srf.request has to be an IP Address.
For example:
srf.request('sip:<IP_ADDRESS>:45456;transport=udp', {
        method: NOTIFY,
  headers: {
            'From'<EMAIL_ADDRESS>            'To'<EMAIL_ADDRESS>

This generates the NOTIFY as
NOTIFY sip:<IP_ADDRESS>:45456;transport=udp SIP/2.0
Via: SIP/2.0/UDP <IP_ADDRESS>: 45456;rport;branch=z9hG4bKFFF2BNKKjZptm
Max-Forwards: 70
From: <sip:test-server@test.in>;tag=eQj2te2c007cK

Although this event is formed correctly and is reaching the client, my understanding is that it does not exactly satisfy the RFC3261.According to RFC 3261, the request line should be of following grammar:
Request-Line  =  Method SP Request-URI SP SIP-Version CRLF
This in my understanding indicates that the uri present in NOTIFY packet – i.e. sip:<IP_ADDRESS>:45456;transport=udp – is not correct.
The question here is as follows:
Is it possible to update the REQUEST line of new event generated via srf.reqest() method where we can specify a SIP URI along with corresponding IP address/port so that the resulting event reaches the intended client as well as complying with Request line related rfc.
Thanks

I think you are incorrect about the uri being invalid
NOTIFY sip:<IP_ADDRESS>:45456;transport=udp SIP/2.0

is a valid request line.
Beyond that, I do not understand the change that you want to see.  Perhaps you can give an example of what you want the message to look like

Hello Dave,
Thanks for the reply. What we want the message to look like is:
NOTIFY<EMAIL_ADDRESS>SIP/2.0

Let's be clear first of all that there is no violation of RFC 3261.
Secondly, the uri appears exactly as you formatted it in the srf.request command


Rewrite using Browser.element

Any chance this can be rewritten using Browser.element instead of Browser.application?
I'm starting my journey into the realm of Elm and I was hoping to use this as a reference but I didn't have to dig deep in my background check to find some issues with a core concept used in this repo.
Browser.application is, as far as I can tell, a naive implementation that doesn't work out in the wild. Due to it taking direct control of the body tag it doesn't play along well with some extensions (1) (2). And the sole purpose if this repo is to demonstrate how you would go about building a "real" elm app.
[1] Discussion on discourse
[2] https://github.com/elm/browser/issues/66

I don't think that's an option--SPA needs access to URL among other things, which isn't available in Browser.element.

Actually it is possible, you just have to wire it up yourself as mentioned in Navigation in elements
I even managed to get a proof of concept working with state splitting across pages in this Ellie.
Anyway, I'm closing this issue since I got it working and I'll be able to extract any bits and pieces I might require.

Right...I don't really consider using ports to be the same thing. 😄


Selected options are not removed from the dropdown menu

I'm using a component with multi={true}. The options in the groups are not being removed from the list when selected. (Top-level options, i.e. outside of the groups, are removed just fine, though.)

@clbn Thanks for reporting this!


Housing.com web scraper

Describe the feature
I'd add a web scraper for housing.com website, which is one of the most popular property listing websites of India.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC 23 contributor
[X] I want to work on this issue

@nikhil25803 please assign me this

Note

Create a separate module for this, as per the folder and project structure
Do not use the `selenium web driver as it is incompatible with all devices and cloud platforms.
Before making any changes, please check whether the module you want to add exists. If yes, then you can just add your functionality as a method only make a separate module and class for it.

All the best 👨💻


Take into account the satisfactory boolean on the semester

This was removed (it was never parsed), so this is irrelevant.


Can't resolve dependencies for Gensim / smart-open / botocore

Issue description
pipenv install gensim fails to create Pipfile.lock because of incompatible required versions in smart-open of botocore.
Expected result
It should install without conflict ... somehow
Actual result
pipenv graph gives this:
gensim==3.5.0
  - numpy [required: >=1.11.3, installed: 1.15.1]
  - scipy [required: >=0.18.1, installed: 1.1.0]
    - numpy [required: >=1.8.2, installed: 1.15.1]
  - six [required: >=1.5.0, installed: 1.11.0]
  - smart-open [required: >=1.2.1, installed: 1.7.0]
    - boto [required: >=2.32, installed: 2.49.0]
    - boto3 [required: <1.8.0, installed: 1.7.84]
      - botocore [required: >=1.10.84,<1.11.0, installed: 1.10.84]
        - docutils [required: >=0.10, installed: 0.14]
        - jmespath [required: >=0.7.1,<1.0.0, installed: 0.9.3]
        - python-dateutil [required: >=2.1,<3.0.0, installed: 2.7.3]
          - six [required: >=1.5, installed: 1.11.0]
      - jmespath [required: >=0.7.1,<1.0.0, installed: 0.9.3]
      - s3transfer [required: >=0.1.10,<0.2.0, installed: 0.1.13]
        - botocore [required: >=1.3.0,<2.0.0, installed: 1.10.84]
          - docutils [required: >=0.10, installed: 0.14]
          - jmespath [required: >=0.7.1,<1.0.0, installed: 0.9.3]
          - python-dateutil [required: >=2.1,<3.0.0, installed: 2.7.3]
            - six [required: >=1.5, installed: 1.11.0]
    - botocore [required: <1.11.0, installed: 1.10.84]
      - docutils [required: >=0.10, installed: 0.14]
      - jmespath [required: >=0.7.1,<1.0.0, installed: 0.9.3]
      - python-dateutil [required: >=2.1,<3.0.0, installed: 2.7.3]
        - six [required: >=1.5, installed: 1.11.0]
    - bz2file [required: Any, installed: 0.98]
    - requests [required: Any, installed: 2.19.1]
      - certifi [required: >=2017.4.17, installed: 2018.8.24]
      - chardet [required: >=3.0.2,<3.1.0, installed: 3.0.4]
      - idna [required: >=2.5,<2.8, installed: 2.7]
      - urllib3 [required: >=1.21.1,<1.24, installed: 1.23]

Specifically, please note these three lines inside smart-open:
- botocore [required: >=1.10.84,<1.11.0,  installed: 1.10.84]
- botocore [required: >=1.3.0,<2.0.0,     installed: 1.10.84]
- botocore [required: <1.11.0,            installed: 1.10.84]

This may be a problem with smart-open rather than pipenv but I can't tell. I posted the issue on smart-open but I don't know enough to decide who needs to adjust what: https://github.com/RaRe-Technologies/smart_open/issues/227
Steps to replicate
pipenv install gensim
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
pipenv --support:
$ pipenv --support
Pipenv version: '2018.7.1'
Pipenv location: '/usr/local/Cellar/pipenv/2018.7.1/libexec/lib/python3.7/site-packages/pipenv'
Python location: '/usr/local/Cellar/pipenv/2018.7.1/libexec/bin/python3.7'
Other Python installations in PATH:

2.7: /usr/local/bin/python2.7

2.7: /usr/local/bin/python2.7

2.7: /usr/bin/python2.7

3.6: /Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6m

3.6: /Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6

3.6: /usr/local/bin/python3.6

3.7: /Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7m

3.7: /Library/Frameworks/Python.framework/Versions/3.7/bin/python3.7

3.7: /usr/local/bin/python3.7

2.7.15: /usr/local/bin/python

2.7.10: /usr/bin/python

2.7.15: /usr/local/bin/python2

3.7.0: /Library/Frameworks/Python.framework/Versions/3.7/bin/python3

3.6.4: /Library/Frameworks/Python.framework/Versions/3.6/bin/python3

3.7.0: /usr/local/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.7.0',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '17.7.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT '
                     '2018; root:xnu-4570.71.2~1/RELEASE_X86_64',
 'python_full_version': '3.7.0',
 'python_version': '3.7',
 'sys_platform': 'darwin'}

System environment variables:

PATH
TERM_PROGRAM
NVM_CD_FLAGS
TERM
SHELL
TMPDIR
Apple_PubSub_Socket_Render
TERM_PROGRAM_VERSION
ZSH
NVM_DIR
USER
SSH_AUTH_SOCK
__CF_USER_TEXT_ENCODING
PAGER
LSCOLORS
_
PWD
LANG
XPC_FLAGS
XPC_SERVICE_NAME
SHLVL
HOME
LESS
LOGNAME
LC_CTYPE
NVM_BIN
DISPLAY
COLORTERM
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/Cellar/pipenv/2018.7.1/libexec/tools:/usr/local/opt/opencv3/bin:/Users/byakubchik/.nvm/versions/node/v8.11.2/bin:/Library/Frameworks/Python.framework/Versions/3.7/bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:~/.composer/vendor/bin:/Library/TeX/texbin:/usr/local/go/bin:/opt/X11/bin
SHELL: /bin/zsh
LANG: en_US.UTF-8
PWD: /Users/byakubchik/Desktop/temp

Contents of Pipfile ('/Users/byakubchik/Desktop/temp/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
gensim = "*"

[dev-packages]

[requires]
python_version = "3.7"

It looks like pipenv is doing its best, but the versions are simply incompatible -- two dependencies want two different versions of sub-dependencies:
smart_open wants
        'boto3 < 1.8.0',
        'botocore < 1.11.0'

https://github.com/RaRe-Technologies/smart_open/blob/master/setup.py#L54
While boto3 wants
    'botocore>=1.12.6,<1.13.0',

https://github.com/boto/boto3/blob/develop/setup.py#L17

Looks like the issue will be resolved on the smart-open end: https://github.com/RaRe-Technologies/smart_open/issues/227#issuecomment-422822565
I believe that npm and yarn manage to handle different version requirements somehow (e.g. package A wants sub-dependency C at version 1.0 while package B wants sub-dependency C at version 2.0 -- and they make it work in the same project). But this is a tall order, possibly enormously difficult to have pipenv install two different versions and hook up them up to corresponding packages (don't know enough inner workings here). 😅

@whyboris - what version of Python are you requiring in your Pipfile?
I seem to be seeing this issue only with a Python 3.6 venv, whereas in a Python 3.7 venv, everything works fine. I'm curious if this is reproducible.
pipenv install gensim --python 3.6 (in an empty directory) fails, whereas pipenv install gensim --python 3.7 (in an empty directory) succeeds.
For my use case, I have to have 3.6 for AWS, but it's very interesting that it seems to work in 3.7.

The issue was fixed very swiftly at smart_open with a new release that unpins the required dependency.
https://github.com/RaRe-Technologies/smart_open/issues/227#issuecomment-422859000
I believe the issue I raised is an instance of an inevitable problem when package A wants sub-dependency C at version 1.0 while package B wants sub-dependency C at version 2.0 -- I'm rather surprised you didn't run into a problem.
@petergaultney - I was unable to replicate the error now that the package has been updated, but I too am curious why you experienced different behavior between the two versions of Python.

i can still replicate it with pipenv install smart_open==1.7.0 gensim --python 3.6 in an empty directory.

@petergaultney -- thanks for that command -- I was able to replicate the problem with
pipenv install smart_open==1.7.0 gensim --python 3.6
but the problem occurred with python 3.7 too in an empty directory:
pipenv install smart_open==1.7.0 gensim --python 3.7
I suspect what you experienced before was a fluke 🤷♂

Thanks for trying. It doesn't make any sense to me, but weirdly enough I can still get pipenv install smart_open==1.7.0 gensim --python 3.7 to pass cleanly, simply running in an empty directory. A ghost in the machine, I suppose? It doesn't enhance my confidence in the Python packaging ecosystem, unfortunately...

Try pipenv lock —clear to purge the resolution cache.

that does indeed cause the error as expected.  Are there different caches per Python version?

Yes, the cache is partitioned by version.


Incorrect hash definition syntax for Ruby

/Users/oliver/.rvm/gems/ruby-2.1.8@datawire/gems/quark-1.0.406/lib/quark.rb:3:in `require_relative': /Users/oliver/.rvm/gems/ruby-2.1.8@datawire/gems/quark-1.0.406/lib/datawire-quark-core.rb:146: syntax error, unexpected ':', expecting => (SyntaxError)
      result.value = File.read(path, {"encoding": "UTF-8"})
                                                 ^
/Users/oliver/.rvm/gems/ruby-2.1.8@datawire/gems/quark-1.0.406/lib/datawire-quark-core.rb:146: syntax error, unexpected '}', expecting keyword_end
      result.value = File.read(path, {"encoding": "UTF-8"})

Seems like it could actually be an error in the Quark compiler, but I had a quick look and couldn't spot anything obvious in master (to me at least).

Actually I think the bug is indeed in datawire/quark:
https://github.com/datawire/quark/blob/5a150065e569a4666bfed8a447e9aaab0fa10240/quarkc/lib/datawire-quark-core.rb#L146

Hi,
Sorry you're getting errors, and thanks for looking a bit more into it.
We only support Ruby 2.3 at the moment, so we don't test with older versions. Could you try with Ruby 2.3 and see if it works?
Thanks,
-Itamar

Indeed, seems to work as expected with Ruby 2.3.