Analytics to get various statistics on Web IDE usage

Number of monthly active users
Geography
Which IDE features are most frequently used
???

We are currently using MixPanel for analytics.
Tracked events:

Project Creation
Project Opening
Project Deployment
Test Case Execution

Would you like to add anything else?

Current MixPanel setup is somewhat problematic

There is no SQL support
This is closed-source proprietary technology
Queries of its ES3-based language identify users with some user id that isn't even unique for a user.
Data are mixed from several dozen domains: nujan, web ide, beta versions, local dev servers, local html files and google translated versions of web ide. Nothing in MixPanel interface aids the user to filter and aggregate this kind of data.

While we can use MixPanel for our immediate needs, we should also have a plan to move on with a different tool.

Current MixPanel setup is somewhat problematic

There is no SQL support
This is closed-source proprietary technology
Queries of its ES3-based language identify users with some user id that isn't even unique for a user.
Data are mixed from several dozen domains: nujan, web ide, beta versions, local dev servers, local html files and google translated versions of web ide. Nothing in MixPanel interface aids the user to filter and aggregate this kind of data.

While we can use MixPanel for our immediate needs, we should also have a plan to move on with a different tool.

I'll report later with my proposal for analytics, it takes some planning.

So basically we need exactly what Anton described:

A way to calculate MAU in a way we can be completely sure the number is correct. Maybe MixPanel is fine for this purpose (we don't need anything else anyway), but we should ensure it's calculated only for production version of IDE, and doesn't count bots (at least search bots such as googlebot).
Add two events show and click that can be used to track usage of IDE features, both to know if users actually use them, and to see graphs going down if they ever get broken. I think it's best to log these into wherever our Grafana gets data from.


Upcoming pickups from archived stores are visible in group wall and group pickups page

From foodsharing Poland

upcoming pickups from the archivised stores still visible in the pickup section and on the main page. i had to restore those archived stores, delete old pickup dates and then move them again to the archive. it's no big deal, but i think it's worth fixing

They should be filtered out properly.
It would be better to disable pickup generation in backend if the store is not active. I remember that I didn't do it last time because it would make the code more complicated. Seems worth revisiting.

Is this issue still valid? I've tried to reproduce this behavior, but didn't succeed. I archived the store and don't see its pickups any more. Wasn't the issue closed by yunity/karrot-backend#483?

This is resolved :)


added checkmode support and routes for upload letter of authority pages

Type of change

[X] Breaking change
[ ] Non-breaking change
[ ] Cosmetic change

Description
Jira link: Letter of Authority page should allow Check Mode
Added support for passing the mode through the various controllers.
Cannot manually test via check your answers due to work involved in ARSSTB-352. You have to use the manual route, but that works correctly (see routes added to routes file)
May be worth considering additional unit tests regarding the checkmode route, I leave that to you guys

I have refactored UploadLetterOfAuthorityControllerSpec and added a test in CheckModeNavigatorSpec.


Introduction to Blazor: Index topic

Title: Introduction to Blazor
UID: client-side/blazor/introduction/index
URL: https://docs.microsoft.com/aspnet/core/client-side/blazor/introduction/
http://blog.stevensanderson.com/2018/02/06/blazor-intro/

Moved to https://github.com/aspnet/Blazor.Docs/issues/10


work for vgg or googlenet

wow, great work, visualize model is very important for tunning model.
does this also work for vgg and googlenet?

It should. You will have to make some modifications to the vgg and googlenet proto files to collect the switch variables from the pooling layers and you will have to create the proto file for the DeconvNet, just like the example for AlexNet. After that, it should work.

Thanks for the work, and it works well on AlexNet. So then I replaced the vgg proto file with the following for pooling layer 1 (numbers changed based on layer #). However python will die unexpectedly when I load the modified vgg model (not yet try the inverse net)...Am I doing something wrong here?
...
...
layer {
name: "pool1"
type: "PoolingSwitches"
bottom: "conv1_2"
top: "poolswitches1"
pooling_param {
pool: MAX
kernel_size: 2
stride: 2
}
}
layer {
name: "slice1"
type: "SliceHalf"
bottom: "poolswitches1"
top: "pool1"
top: "switches1"
slice_param {
axis: 0
}
}
...
...

I'm not sure, it looks correct to me. However, it is worth noting that the PoolingSwitches layer and the SliceHalf layer are actually not needed to perform this. I recently discovered that Caffe's Pooling layer will output the switch values when given two tops. All that is really needed is the UnPooling layer. For example:
layer {
  name: "pool"
  type: "Pooling"
  bottom: "conv1"
  top: "pool1"
  top: "switch1"
  pooling_param {
    pool: MAX
    kernel_size: 2
    stride: 2
  }
}

layer {
  name: "unpool1"
  type: "UnPooling"
  bottom: "pool1"
  bottom: "switch1"
  top: "unpool1"
  pooling_param {
    pool: MAX
    kernel_size: 2
    stride: 2
  }
}

I have some updated versions of this code, that I will be pushing soon.

@piergiaj @sunbaigui Hi,I tried to use this for googlenet, but I noticed that googlenet use avg pool rather than max pool, is the switch pool uppooling method fit for the avg pool layer?


Add IP-based ratelimits

Add IP-based ratelimits for ~creating accounts and~ adding new email addresses.
~I set these to 5 per day, which is maybe still high? Should they be lower?~ I set these to 2 per day.

Approach looks good to me. I'd say we could probably go lower if we include an actionable response in the error "Rate limit exceeded for account creation, contact<EMAIL_ADDRESS>if..." so that we can at least hear from folks it impacts.
It would certainly complicate things, but adding and "escape hatch" to allow specific IPs a pass on these strict rate limits may be a good idea for sprints/hackathons/corporations etc.

@ewdurbin Added everything we talked about here, this should be ready for re-review.


chore: update to compatibility with latest version of vm2

Had to adjust the integration a bit because of vm2 interface changes. Adjusted the amount of gas passed to the VM.
With this version vm2 only fails TransientStorage tests. Those opcodes are unimplemented.

Looks like vm2 will need to be public first. Also, I have realized I have to make more changes to the VM's interface to be able to integrate into core, so I think it makes sense to postpone this a bit.

@hedgar2017 I just removed all your commits that were not related to vm2 and the conflicts went away. This is ok because they are in main anyway, right?

@hedgar2017 I just removed all your commits that were not related to vm2 and the conflicts went away. This is ok because they are in main anyway, right?

Yes, I believe the history got broken is some way after merging v1.5.0.
Unfortunately I still can see the conflicts in this PR.


[mongodb] Run Aggregations

Is your feature request related to a problem? Please describe
I'd like to run (non-modifying) aggregation pipelines on MongoDB collections. Currently, only "find" and "count" are available
Describe the solution you'd like
In the "Query Documents" view, in the "operation" drop-down, I'd like to select the option "aggregate" and then enter an aggregation pipeline in the "query" field.
Describe alternatives you've considered
Currently, I open a shell in the mongodb container (also via kobs) and do it on the command line.
Additional context

Hi @jkraml-staffbase, I added this as acceptance criteria to our rework ticket for MongoDB, so that this feature should be available with the next version.

Hi @jkraml-staffbase, this was implemented in #527 and should be available in the next version 🙂


Ensure that there is a syntax error even with lazy parsing.

Without any syntax errors prior to lazy parsing, we'll reject this in valid-parse testing of the new parser. Adding this doesn't change the fundamental nature of this test.

@swift-ci please smoke test


Views counter/ranking

Right now, KodaDot was built mostly to be an on-chain data explorer and being a thin layer. Hence we would like to enhance comfort and are not sure if we should put these numbers like views on-chain as it might get expensive; we would like to provide users/artists some off-chain metrics and close to real-time.
Making a serverless function (worker?) which will be storing this stuff in KV in some efficient way.
Probably each 1k, or 10k we can offload some stores to some remark to store these numbers on-chain to having only small increments off-chain.
This would be helpful for artists, creators and game item designers to have approximate estimation of which item is in demand. Similiar you have plays in Spotify, this would help estimate general audience likeliness of particular artifact
We could collect

load times of item (we should put some filter/captcha to account it was human viewing and not programmatically made or bumping some views)
if it's video play times
if it's 3d, time user has played with item?
if it's downloadable, times user/owner has downloaded it

wyt?
We can then incorporate this into the new v1.1 Gallery item detail

#4403

To start iterating on this, we would like to start showing this views per visit from logged persons.
I think we can still trigger workers somehow and I guess we should split it to counting with logged vs not logged persons with wallet
We can trigger worker from which item was it visited and take it from there?
Using Workers/CF infrastructure would be probably easiest

view and likes?

looks like instagram now lol

👀 nuxt-pageviews

Happy to do it that way

from #901

https://github.com/kodadot/nft-gallery/issues/901#issuecomment-1489996643
backyardcoder.me/posts/implementing-a-page-view-counter

👀 nuxt-pageviews

what's rate limit in case or what are other limits we should consider GA, doesn't need some GA pro plan to work beyond X reqs?

do we want to implement likes at the same time? 👀

what's rate limit in case or what are other limits we should consider GA, doesn't need some GA pro plan to work beyond X reqs?

Don't really know this, but first we'll need to fix GA implementation (maybe issue with plugins & nuxt-bridge)

do we want to implement likes at the same time? 👀

not really since it's not the same kind of features.
Emotes (likes?) are only available on RMRK chain for now.

Emotes (likes?) are only available on RMRK chain for now.

Not an issue to add to other chains.
It's really primitive ^-^

ht @alko89

https://community.cloudflare.com/t/support-increment-decrement-operations-atomic-counters-in-workers-kv/136192

Maybe Mongo would be a valid option for counting views, using $inc?
A free instance on Atlas should be plenty for quite a while if you only intend to use it for view counting and ranking.


WithHooks() can fail in non-obvious ways

Since kgo.Hook is an empty interface anything implements it, even []kgo.Hook. When adding kotel I was surprised when the tracing wasn't firing at all because I didn't inline the slice.
// opps, []kgo.Hooks is valid but implements no hooks
kgo.WithHooks(kotelService.Hooks())
// good
kgo.WithHooks(kotelService.Hooks()...)

I'm wondering if it would be palatable to change WithHooks to inspect the passed in hooks and flatten the slice/s if it detects it was passed something that implements no individual hooks. The inspection would only be done at client construction time.
That way the following invocations are all equivalent.
var xs, ys []kgo.Hook
var someHook kgo.Hook
var all []kgo.Hook
for _, v := range xs {
  all = append(all, v)
}
for _, v := range ys {
  all = append(all, v)
}
all = append(all, someHook)

kgo.WithHooks(all)
kgo.WithHooks(all...)
kgo.WithHooks(xs, ys, someHook)
kgo.WithHooks(xs..., ys..., someHook)

Technically a person can provide a type that is a slice that implements hooks:
type foo []int

func (f *foo) OnBrokerDisconnected(...)

How can the client differentiate?

It can test for it right? If the slice implements one of the available hooks, don't flatten. If it implements no available hooks but the things inside do, it is likely an error right?

That's the same thing I was thinking.

it is likely an error right?

And if things inside do, then flatten, right? That's the proposal? +1 to that.
This can also check that if a type doesn't implement any hook, and if elements of a slice don't implement any hook, return an error.
Also hooks.go should have a large // NOTE at the top to add checking any new hook to the section being added for this proposal.

Sounds good. I can open a PR since it sounds like we're on the same page.
w.r.t. the true error case (passed a thing that implements nothing), how do you envision that returning an error since kgo.WithHooks() is an option? Remember the error and return it from kgo.NewClient?

And yeah to be exhaustive:

If arg implements any hook use it as is
If arg is a slice and implements no hook methods, unpack it
If no passed args implement some hook interface return error

since kgo.WithHooks() is an option
I mean in cfg.validate() at the top of NewClient

any passed thing fails to implement any hook interface
I'd be ok with that, since that's likely a mistake


Node ip is  incorrect in node list

In GitLab by @Robin-Mao on Jul 16, 2019, 10:51
The kubernetes cluster master ip: <IP_ADDRESS>

In GitLab by @sokril on Nov 8, 2019, 08:33
assigned to @sokril

In GitLab by @luotian-github on Dec 31, 2019, 15:16
assigned to @Robin-Mao and unassigned @sokril

In GitLab by @luotian-github on Dec 31, 2019, 15:17
Need more information for this bug, a screenshot

In GitLab by @Robin-Mao on Mar 26, 2020, 01:39
closed

In GitLab by @Robin-Mao on Mar 26, 2020, 01:39
duplicate #154


Workarounds for using BashOnWindows with LTSB?

Are there any known workarounds available?

This is a duplicate, please see #1281 for more detail.


Implement new standard outputs for atomistic models

This PR implements ensembles of energies as a new standard output for atomistic models (#650). It also makes the necessary changes to the ASE calculator to make this property (which is not standard in ASE) available to the user. In addition, the dipole is also registered as a new property and added to the ASE calculator
TODO: actual conversion factors for dipoles
Contributor (creator of pull-request) checklist

[ ] Tests updated (for new features and bugfixes)?
[x] Documentation updated (for new features)?
[x] Issue referenced (for PRs that solve an issue)?

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Download documentation preview for this pull-request

Regarding the tests, it seems that energy and energy_ensemble are being ordered differently on Windows x)

Ok, I will open different PRs

Thx Guillaume & Filippo. Feel free to re-assign me for ASE changes or ensemble stuff. 👍

This looks good. Should we also have a test checking some example model that returns an ensemble of energies?


audit: suggest full formula name only for other taps

Since getdp is in homebrew/science the :linked below should not be printed as full names.
http://bot.brew.sh/job/Homebrew Science Pull Requests/5157/version=mavericks/console
==> FAILED
Error: 1 problem in 1 formula
homebrew/science/getdp:
  * Formulae are required to declare all linked dependencies.
    Please add all linked dependencies to the formula with:
      depends_on "fftw" => :linked
      depends_on "homebrew/science/hwloc" => :linked
      depends_on "homebrew/science/netcdf" => :linked
      depends_on "homebrew/science/parmetis" => :linked
      depends_on "homebrew/science/scalapack" => :linked
      depends_on "homebrew/science/suite-sparse" => :linked
      depends_on "homebrew/science/sundials" => :linked
      depends_on "homebrew/science/superlu_dist" => :linked

CC @xu-cheng

we could probably do this:
diff --git a/Library/Homebrew/extend/os/mac/formula_cellar_checks.rb b/Library/Homebrew/extend/os/mac/formula_cellar_checks.rb
index dd21559..de61fb5 100644
--- a/Library/Homebrew/extend/os/mac/formula_cellar_checks.rb
+++ b/Library/Homebrew/extend/os/mac/formula_cellar_checks.rb
@@ -72,10 +72,11 @@ module FormulaCellarChecks
     end

     if checker.undeclared_deps?
+      undeclared_deps = checker.undeclared_deps.map { |d| d.strip_prefix("#{formula.tap}/") }
       audit_check_output <<-EOS.undent
         Formulae are required to declare all linked dependencies.
         Please add all linked dependencies to the formula with:
-          #{checker.undeclared_deps.map { |d| "depends_on \"#{d}\" => :linked"} * "\n          "}
+          #{undeclared_deps.map { |d| "depends_on \"#{d}\" => :linked"} * "\n          "}
       EOS
     end
   end

Should work but seems a tad indirect :)

I think it's fine as-is but don't feel strongly either way.

@xu-cheng I'd ship it with the change you suggested. Contributors are already spontaneously manually intervening and editing out the tap prefixes, which is less than ideal CX (contributor experience).

As a reference point, in homebrew science, there's currently exactly one:
Josephs-MacBook-Pro:homebrew-science joe$ ag 'homebrew/science'|grep dep
gmtk.rb:13:  depends_on "homebrew/science/hdf5" => :optional

I don't think it makes sense to foist a new convention on them unless it's actually a new policy we're applying everywhere for all dependencies not in core.

This is already causing confusion:
https://github.com/Homebrew/homebrew-science/pull/3836#discussion_r71804255
https://github.com/Homebrew/homebrew-science/pull/3836#discussion_r71829316

I one of the confused contributors :) I would have preferred if brew audit would not have suggested full paths. It looked odd to me but since I did not know all the consequences, I choose to just follow the advice of audit.

@ilovezfs Would do you mind to send a PR? I may not have too much free time recently to work on this.

@xu-cheng Sure. Are you still happy with your proposal above?

Are you still happy with your proposal above?

:+1:

I should fix gmtk. I personally feel that dependencies that are either in core or in the same tap shouldn't have to be fully qualified but I may be missing something.

We dropped :linked.


Use 1.9 hash key syntax in stub suggestions

The build failure appears to be unrelated to my change as it also happens on master both when I run it locally and also @ https://travis-ci.org/tarmo/webmock/builds/182789108

@tarmo nice, thank you!

@tarmo nice, thank you!


Skip event for error line should provide raw data

My csv is created with delimiter "|" but my some columns in few records also contains pipe. Due to this I am having error CSV_RECORD_DONT_MATCH_COLUMNS_LENGTH.
Please help me if this can be resolved
I am currently trying to skip these error lines and want to process these records separately in skip event but I need raw line to be able to process.

Please a complete bug report.

I have provide the description of my problem above

It seems like you could use a combinaison of the relax_column_count, on_record and raw options. I have updated the relax_colunn_count documentation in that regard.
Note, the usage of error like in the example requires the latest version.

It found my mistake. Its Solved
Thanks


v4 🍧

Rebrand v4 🎨 🧩

Task
Story
Design
PR
Done
Breaking
Owner

Colors
ZDS-6
Marvel
https://github.com/zopaUK/react-components/pull/288
✔
✔
@lluia

Buttons
ZDS-2
Marvel
https://github.com/zopaUK/react-components/pull/291
✔
✔
@lluia

Headings
ZDS-3
Marvel
https://github.com/zopaUK/react-components/pull/293
✔
✔
@lluia

Text
ZDS-7
Marvel
https://github.com/zopaUK/react-components/pull/293
✔
✔
@lluia

Links
ZDS-10
Marvel
https://github.com/zopaUK/react-components/pull/293
✔
–
@lluia

Navbar
ZDS-4
Marvel
https://github.com/zopaUK/react-components/pull/422
✔
✔
@raff-r

Footer
ZDS-5
Marvel Marvel
https://github.com/zopaUK/react-components/pull/366  https://github.com/zopaUK/react-components/pull/374
✔
✔
@dfvalero

Cards
ZDS-8
Marvel
https://github.com/zopaUK/react-components/pull/297
✔
✔
@thegrinder

Spacing
ZDS-9
Marvel
https://github.com/zopaUK/react-components/pull/290 https://github.com/zopaUK/react-components/pull/302
✔
✔
@moshie

Icons
ZDS-11
Font Awesome
https://github.com/zopaUK/react-components/pull/333
✔
✔
@lluia

Accordion
ZDS-11
Marvel
https://github.com/zopaUK/react-components/pull/309
✔
✔
@poteirard

Sliders
SHOPDEV-6087
Marvel Marvel
https://github.com/zopaUK/react-components/pull/328  https://github.com/zopaUK/react-components/pull/330  https://github.com/zopaUK/react-components/pull/337  https://github.com/zopaUK/react-components/pull/364
✔
✔
@dfvalero

Badges

https://github.com/zopaUK/react-components/pull/342
✔

@lluia

Rebrand v5 💭
( to discuss whether we include it in this release or not )

Task
Story
Design
PR
Done
Breaking
Owner

Form elements

Progress Bars

@poteirard

Improvements 🏋🏻♀

Task
Story
PR
Done
Breaking Change
Owner

formik integration
–
https://github.com/zopaUK/react-components/pull/289
✔
✔
@thegrinder

Blocking ⏱

[ ] Upgrade all design system to Marvel  👉🏻  Design
[x] Clarify Footer update 👉🏻  Design
[x] Clarify Navbar update 👉🏻  Design
[x] Decide whether we include all rebrand updates on this release  👉🏻  Team

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: poteirard:white_check_mark: dfvalero:white_check_mark: thegrinder:white_check_mark: moshie:x: steedemsYou have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


URL shorteners blocked

For obvious reasons url shorteners like goo.gl and bit.ly should not be blocked as they have many useful applications.

added to whitelist


Fix control character input bug

This makes it possible under Glulx for I7 code to process player-typed commands which have tabs or other control characters in them, by converting into text and then doing some processing (perhaps using regex matches to remove the control characters, etc.).
Currently, any attempt to do such processing throws an error from the I6 veneer code into the target text variable, rendering the original command unrecoverable and making it impossible to process the text of the command.
This is a strict improvement over the previous state.  This became relatively straightforward thanks to Inform now using Unicode input for Glulx.  There remain some other related issues, but I believe this is enough of an improvement to be worth committing.  Passes 'make check' and is faster than the existing code.
It is not possible to add a test case because the intest test suite harness doesn't actually behave the same way as commands typed by the player for this purpose.
Long discussion of the issue here:
https://intfiction.org/t/debugging-the-player-typed-a-tab-problems-in-inform-7-for-glulx/66852/18

The following is a more complete fix, which should be committed in preference:  https://github.com/ganelson/inform/pull/140
However, I'm leaving this pull request here because this one is still a speedup and a code path simplification, and I think it can and should be used as a base for improving snippet handling code anyway; I think I can probably clear out a bunch of other snippet handling bugs using this as a base.

I think this goes further than I want to go just now, but I did accept PR#140, with thanks.

This was in regard to I7-2462


How would you stripe the gridjs table and select different colors?

In the first first table tutorial, the table was striped.
I have been trying to figure out how to add the CSS to make this gridjs table striped, but I am not succeeding.  Any help would be appreciated.
thank you

There are many tutorials that show how to style a table with stripes. First result Google gives me is https://www.geeksforgeeks.org/how-to-create-a-zebra-striped-table-with-css/.

Finally figured it out.  The problem is that gridjs does not allow "tr:nth-child(even)" to pass through it's "style" section.  I don't think "tr" is passed through at all.
The solution is to select the even rows in the page header, and then to modify the td fields in those rows:
`
This SO question solves our problem: https://stackoverflow.com/questions/75501116/how-to-create-different-background-for-my-table-row-nth-child
While you cannot affect the background of TR directly, you can select the TD's of the Even TR's and then apply the color to those TD's as shown in this SO question.  Change the CSS in the page header:
`

Rule Table


New background for landing page

I want to have a black background for the landing page with some cool animations. A snapshot of the current landing page is attached below:

If anyone is interested to help me with this issue.

You mean dark mode ?

You mean dark mode ?

Yes but not for the whole website but only for the landing page.

I want to work on this issue. Will you please assign it to me?

Can you suggest what are your ideas regarding this? Like any particular design you have in mind?

https://user-images.githubusercontent.com/89118388/136507060-ad0be549-a139-4ed1-ae95-1d1043ebd7d2.mp4
Ig dark bg is not looking good the original is better

Do you want animation in your name and "a programmer".I can do that.


Make documentation links clickable

Hi! I have been going through the documentation and thought it might be more convenient to have the links that reference OpenAI's docs be clickable.
I am not sure if this is something that would be good to have but wanted to create the PR in case you found it useful.  I also found some small typos in create_image's docstring, so I took the opportunity to fix them.

LGTM, much appreciated!


Added a preset for amenity=ticket_validator

amenity=ticket_validator (https://wiki.openstreetmap.org/wiki/Tag%3Aamenity%3Dticket_validator) has increased by over 2300 uses by this time, but it din't have a preset yet. I did not open an issue for that, but I can if necessary. So as the usage for this tag seems very clear to me, I thought it would be worth adding preset for it. I used the icon from vending_machine, maybe when you're not okay with it, you can remove it. I hope everything else fits.

Thank you!


Issue#36/orbit tracking

Tool for tracking orbit period for one body around another.
TO DO:

[x] Functional orbit tracker
[ ] Fully tested

Current coverage is 90.82%

Merging #59 into master will decrease coverage by -9.18% as of 88ef597

@@            master     #59   diff @@
======================================
  Files            4       4
  Stmts          158     229    +71
  Branches        28      39    +11
  Methods          0       0
======================================
+ Hit            158     208    +50
  Partial          0       0
- Missed           0      21    +21

Review entire Coverage Diff as of 88ef597

Powered by Codecov. Updated on successful CI builds.


Configurable provider's param.

Can you drop e.g. 1089c99 + dd66ef2 and rebase to make it easier to review?


fix(bus): adjust axios config to properly handle 204 responses

fixes #60

Parsing valid json with 200 status:

forcedJSONParsing: false + silentJSONParsing: true: json body is not parsed (both with and without responseType: 'json' explicitly set) - and this looks like axios new transitional params bug
forcedJSONParsing: true + silentJSONParsing: true : json body is parsed
forcedJSONParsing: false + silentJSONParsing: false: json body is parsed

Current forcedJSONParsing: false + silentJSONParsing: false is not compatible with handling 204 empty body responses, and enabling silentJSONParsing is required to make it working.
But  enabling silentJSONParsing w/o forcedJSONParsing leads to returning bodies as plain text (see p.1).
So both forcedJSONParsing and silentJSONParsing should be enabled as a workaround - or just omitted as true is their default value.


chore: update git-changelog regex pattern for version finding

Description

The task to generate the Changelog is updated:

Now, it does not delete the Changelog everytime before creation
It does the Changelog update inline. -> So that manual editings are not lost.

Additionally the regex to find the current / latest version in the Changelog is updated.
It wouldn't have worked due to changes in the Changelog template (CHANGELOG.md.jinja)

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@borisrizov-zf
Please review

Nonetheless, let's hope that there will not emerge a plethora of ways to communicate a version of MIW.

Hi @SebastianBezold,
can you merge this PR?
Thx

@pmoscode Sebastian is away for 5 weeks, so we'll have to ping someone else.
@scherersebastian can you take a look?

@carslen Hi can you merge this?


Heya

Is there any reason to not using ip-filter directly in the lib/ip-match.js?
Anyway, just to note, I'm going to update it soon.

I'm expecting bool as return and also to generalize bool output in all cases.

You can still do result === null?

@tunnckoCore Cool. Thanks for checking this out.


Improve Clarity of Command Presentation in Contributing.md

What's wrong with the existing documentation
In the contributing.md file, there's a section where the command for creating and checking out to a new branch is provided. However, the presence of "PowerShell" preceding the command might confuse contributors, leading them to question whether it's part of the command or indicating the terminal prompt.
To enhance clarity and prevent confusion, we should revise the presentation of the command to make it clear that "PowerShell" is not part of the command itself but rather indicates the terminal or shell environment. This adjustment will ensure that contributors understand the command structure correctly and can follow the instructions accurately.
Proposed Changes:
Remove "PowerShell" from the command presentation to avoid confusion.
Clearly indicate that the provided command is to be executed in the terminal or shell environment.
By making these adjustments, I aim to improve the clarity of instructions in the contributing.md file, thereby enhancing the overall contributor experience and facilitating smoother collaboration within the project.
Add ScreenShots
No response
Record

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

@nikhil25803 Please assign this issue to me


Minor improvements to regex.list

I would also have suggested blocking subdomains of IDNs (i.e. subdomains of xn--), but I see you had issues with Google Play. What kind of issues did you have and with what domains? The regex would be much better if it at least blocked the www subdomain as well to catch domains like www.ɡooɡle.com (in punycode: www.xn--oole-z7bc.com).

Hi,
What are the reasons for removing underscores and lazy evaluation?
I believe, although I could be wrong, underscores are valid characters especially for subdomains? And the lazy evaluation can save rather a lot of steps in some cases which may save precious processing time.
I didn't personally have issues but I had issues reported presumably from international users where they were experiencing problems with Google play; I can't recall whether they specified if it was general access or downloading apps. I can certainly add the optional www subdomain to these though :-)

As I wrote in the commit message, lazy evaluation is not possible with POSIX extended regex. I don't know how it gets parsed exactly, but it certainly does not do what you think it does.
With regards to underscores, I may be wrong on that front. I did some more reading and although underscore is valid in DNS records, AFAIU it is not valid in hostnames. I can't think of a situation where these regexes would be used to block DNS records that do not point at a web host. However, in case we do want to include underscores, I wonder why they were not included in every regex?

Ah, I see! Apologies I'm on my phone so I didn't go as far as looking at
the commit comments.
I will have to take a look into this as I tested them outside of grep
originally. If this is the case then I shall remove them :-)
I may remove the underscore matching too, as suggested, as tbh now that you
mention it I haven't yet personally come across an example where they're
used. I applied them originally only to those regexps that I thought they'd
be most likely to appear.
I will take a look at this a little later today.

I see you replied via email. I edited my comment after I tested and confirmed that underscores can in fact be used and should be left in.
For reference, this seems to be the line that does regex matching in Pi-hole.

@niklasea take a look through https://github.com/mmotti/pihole-regex/commit/32d97e8cd806164f175cc05167dc39ce23ce9fef. I think it should cover everything in this pull request, in addition to moving the - within the character classes to the end to avoid syntax errors relating to selecting an invalid range.

I think it looks good.

Resolved in https://github.com/mmotti/pihole-regex/commit/32d97e8cd806164f175cc05167dc39ce23ce9fef
Thanks @niklasea


Fix the example soma_radius_fit.py

Current coverage is 100.00%

Merging #97 into master will not affect coverage as of e4640a7

@@            master     #97   diff @@
======================================
  Files           29      29
  Stmts          956     956
  Branches         0       0
  Methods
======================================
  Hit            956     956
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of e4640a7

Powered by Codecov. Updated on successful CI builds.


[BUG] Key issue

Describe the bug
Can't use two list with same value, getting error of unique key.
Expected behaviour
Key should not depend on the value prop.
There should be option for custom value, label like as react select.
  <Select
                          isDisabled={!stateId}
                          options={citiesArray}
                          classNamePrefix="select"
                          getOptionValue={({ id }) => id}
                          getOptionLabel={({ name }) => name}
                          theme={selectThemeColors}
                          className={'react-select'}
                          {...field}
                        />

@kkaplinski Thanks for the quick response.Let me explain the use case.
We will get data from server in following format.
const data1 = [
    { id: 1, name: 'Name1' },
    { id: 2, name: 'Name2' },
]

const data2 = [
    { id: 1, name: 'X' },
    { id: 2, name: 'Y' },
]

These will be assigned to two different Select list.

So, We need to manually process the array to convert in label, value key of the objects.
This will show error for two children with the same key.

A bonus issue : Dynamic option array will not update. ( I have a hook which will fetch data from server but found that option list not updated with the data. I have to trigger the component via a key change.)

Hello @imdkbj. Thank you for the comments. Two lists with the same values/keys should not be a problem - you will have two separate components.
Regarding to loading options async: We are not supporting currently this possibility, but we will think about it. For now you can fetch data from server and show select component after new data arrived.

Hmm, Thanks for the info.


Replacement for setUserAuthToken introduced

What
As part of the new Authentication work, we will be replacing X-Florence-Token which is validated via Zebedee with a new token that uses the Authorization header instead which is validated by the dp-identity-api.
But wait we need a smooth transition! Yes, and so we have a new function for setting authentication header SetAuthToken this will set both the old Zebedee token and the Florence token. There is work in progress to make requests to the dp-identity-api that fail auth to then check Zebedee with the X-Florence-Token. This work is WIP.
You may notice that the serviceAuthToken also uses the header Authorization! Won't there be a collision? - Yes. The idea behind this work is to handle these collisions later, potentially what we will do is check the dp-identity-api to see if it is a user token, if not then check Zebedee to see if it is a service token. This is an interim solution though.
All places that referred to SetUserAuthToken have been replaced with SetAuthToken
Why SetAuthToken instead of SetUserAuthToken, in the distant future service auth tokens will be removed from Zebedee like we are doing currently with user tokens.
How to review
Check the code
Who can review
Anyone except me

I believe this should be ok so long as all usages of Set always set the client first and allow the service token to overwrite (this is the current behaviour within this repo, but we should share with the team so that any repos that pull in this update will know to check the order).
In terms of auth itself. The codebase always takes the user over the service auth by default so our change will be backwards compatible there for now: https://github.com/ONSdigital/dp-api-clients-go/blob/main/identity/authentication.go#L75. We will definitely need to replace this auth implementation later and this is planned work.


Tag image with 'latest-released' or similar during release

When we release, we should apply a Docker tag marking that version as the "latest released".  That way, tests that test what we have out in the wild vs our internal latest/RC won't have to change on each release.

We should really just be using the latest tag for this, and not apply latest to any -rc releases.


Disable the page break before appendix

It could be useful also if the \clearpage added before the appendix could be disabled. (I don't know whether having an option for this is reasonable, or whether there should be a more generic mechanism to configure what gets issued before the appendix starts.)

I have replaced the tentative appendixcol option introduced to fixed #4 for a more flexible approach using a \appendixprelim command that can be redefined. By default this command is defined as:
\newcommand{\appendixprelim}{\clearpage\onecolumn}. Disabling pagebreak, single-column mode, etc., or styling the appendix differently can be done by simply redefining this command with \renewcommand.
Please test, commit cc4f0cb of branch develop.

Works for me, and I think this is a reasonable approach; thanks!


Add rule to forbid className and style being passed to Components

Passing className or style to your Components is a source of much
hidden complexity that can be solved either by using a wrapper to add
styling or by adding props for specific styling. This rule aims at
preventing these props from being passed to your Components, to help
minimize hidden complexity.
The original issue proposed having this rule check propTypes. I
considered that route, but I worry that it won't be as effective for
people who do not have every prop used by the component listed in the
propTypes. Additionally, propTypes seem to have waning interest from the
React team in favor of Flow annotations, so I think in the long run
checking for this at the callsite will be more stable.
More information can be found by reading:
https://medium.com/brigade-engineering/don-t-pass-css-classes-between-components-e9f7ab192785
Also:
https://twitter.com/sebmarkbage/status/598971268403073024
Fixes #314
cc: @janpaul123 @sebmarkbage

@yannickcr @ljharb anything else you'd like to see on this before we merge it in?

I plan to merge this soon unless I hear otherwise.

This rule is nice, but what if we are required by default to pass the className as a prop. Let's take for instance, the react-modal case:
      <Modal
        className="Modal__Bootstrap modal-dialog"
        onRequestClose={this.handleCloseModal}
        isOpen>

Per the info in the OP, you'd simply not use the rule in that case - the idea is that passing a className is an antipattern, and you'd want to avoid it.

Thanks for your reply.
In order to not use it, I have to disable the rule, which in turn may be contra-productive, as I can have in the same function or file other components which should indeed not receive the className or style props.
I propose a different approach. What about introducing an option to tell the rule which components should be ignored.
As in my example, react-modal has always the Modal component. I can specify eslint to ignore any component with the name Modal.
Well, yes this approach has a down-side as I may write in the future components with that name, but I think is less likely.


Add check for 1.28

@GuillaumeGomez Seems I missed something. Why you to do this?

If these files are useless, shouldn't we remove them?

This question about replace stable with 1.28  (while PR title says "add")

It's a discussion we had with @sdroege: gstreamer is supporting 1.28 (giving you context about all those PRs). But yes, it should be called "replace" instead. Replacing all titles (:sob:).


codestyle: Adds clang-format config.

Adds a .clang-format that approximates the prevailing style used in this repo.
This should partially resolve #92

I'd suggest having a look at #96 first to see what kind of changes this introduces, I just wanted to make sure the config file is split out from the application of the config.

#96 re-pushed w/ the results of this review.

I opted to merge #96 instead. Thanks!


Bug: AFCNetClientService::OnServerNotify

In this section, the CreateClusterClient function will never return a successful result.
https://github.com/ArkNX/ARK/blob/7053635f18f5c25408f0c244dd5269693aa5b902/src/plugin/net/src/AFCNetClientService.cpp#L409-L415
This is due to the fact that inside the "CreateClusterClient" there is a similar check "ArkBusRelationType :: BRT_DIRECT"
https://github.com/ArkNX/ARK/blob/7053635f18f5c25408f0c244dd5269693aa5b902/src/plugin/net/src/AFCNetServiceManagerModule.cpp#L157-L164
In other words, our server will not simultaneously have 2 types of connection
Perhaps I don’t understand something?

The first code section means the connection type is BRT_WAIT_NOTIFY, the relation in the configuration file, bus_relation.xml. It's the notify msg process function.
The second section means to start the client that the connection type is BRT_DIRECT.
I think the logic is right.

Can connection_type be both BRT_WAIT_NOTIFY and BRT_DIRECT at the same time?
If not, then you better check this moment

No, just have one type. either BRT_DIRECT or BRT_WAIT_NOTIFY.
I get your point. You wanna let me check more.
But all notify type will not be started in the msg callback function, the msg sender will ensure this.
Don't worry, after using service discovery, you will never see the connection type enum.

this connection type is removed in the new design that using consul as the service discovery center.


custom theme options and overrides for entity star icon

Hey, I just made a Pull Request!
#26434 was closed so this is my PR to fix #26385 as I would like to see this in Backstage. Changes in this PR:

Adds star and unstarred overridable icons. Default icon is the existing star.
Adds entityStarButton.color theme option to override the filled in star color. Default color is the existing yellow color.
Updates existing usage of entity stars to use the new Backstage star and unstarred icons and theme color

There is no visual change when using default (non-themed) Backstage.
Example overriding default star icon to a "favorite" (heart) icon and make the filled color red:
App.tsx
import FavoriteBorderIcon from '@material-ui/icons/FavoriteBorder';
import FavoriteIcon from '@material-ui/icons/Favorite'

const app = createApp({
  apis,
  plugins: Object.values(plugins),
  icons: {
    // Custom icon example
    alert: AlarmIcon,
    star: FavoriteIcon,
    unstarred: FavoriteBorderIcon,
  },
  ...
});

Custom theme
export const apertureTheme = createUnifiedTheme({
  ...createBaseThemeOptions({
    palette: {
      ...palettes.light,
      entityStarButton: {
        color: '#FF5630',
      },
    },
  }),
};

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@stephenglass sorry I think we should have been more clear with the other PR. @callebstrom is gonna create another PR to fix it a different way after we chatted offline for a bit.
It's gonna be similar to this, but I think we're gonna opt for not storing this as a value in the palette. There's already some accent colours we could use in the palette, but unsure of the implications of doing that.
Gonna use something similar to these docs in order to make the colour configurable at the theme level instead.
It's up to you if you wanna keep this open or not, maybe we could close this in favour of @callebstrom's when it lands?

@benjdlambert There might still be value in keeping the AppIcons aspect of this PR actually, as I will only be tackling the color aspects using makeStyles and a custom component. I could utilise the app icons in my custom component to also allow overriding of the underlying icon, but still control the behaviour favorite marking. Wdyt?

@callebstrom yeah, probably makes sense to allow the icon component itself to be overridden too, let's merge your PR first and then @stephenglass if you want to rebase on top and just pick out the AppIcon changes on top? :pray:

Sounds good! 👍

For transparency: here is the PR for the FavoriteToggle component https://github.com/backstage/backstage/pull/26484

PR has been updated to include only the custom icon overrides. Hope it's all good!

Great work with this!


Some entries missing from 3.1.3 changelog

brew config output
HOMEBREW_VERSION: 3.1.3-91-gfb7d19c
ORIGIN: https://github.com/Homebrew/brew
HEAD: fb7d19c6618f90b30c463fa854ae241fb5e0bacc
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/linuxbrew-core
Core tap HEAD: 62a49388cde09c034267c7ee07d5f6bbd6b9b36f
Core tap last commit: 7 weeks ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :1
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: octa-core 64-bit ivybridge
Clang: 6.0 build 600
Git: 2.17.1 => /usr/bin/git
Curl: 7.58.0 => /usr/bin/curl
Kernel: Linux 5.4.0-70-generic x86_64 GNU/Linux
OS: Ubuntu 18.04.5 LTS (bionic)
Host glibc: 2.27
/usr/bin/gcc: 8.4.0
/usr/bin/ruby: 2.5.1
glibc: N/A
gcc@5: N/A
xorg: N/A

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Broken symlinks were found. Remove them with `brew cleanup`:
  /home/linuxbrew/.linuxbrew/lib/ruby/gems/3.0.0/bin/bundle
  /home/linuxbrew/.linuxbrew/lib/ruby/gems/3.0.0/bin/bundler

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I was looking at the GitHub release changelog for 3.1.3 and I noticed some entries are missing. As of this writing, the release notes have the following content:

rubocops/patches: GitLab patches should use .diff (@jonchang)
rubocops/patches: remove autocorrection of some urls (@nandahkrishna)
build(deps-dev): bump html-proofer from 3.19.0 to 3.19.1 in /docs (@Homebrew)
Update maintainers, manpage and completions. (@Homebrew)
bump-cask-pr: add --fork-org flag (@Homebrew)
Update maintainers, manpage and completions. (@Homebrew)
bump-formula-pr: add --fork-org flag (@dawidd6)
Always take latest item in Sparkle strategy. (@reitermarkus)
formula: add -DBUILD_TESTING=OFF to std_cmake_args (@Bo98)
rubocops/patches: Fix quoting of the patch url when autocorrecting (@issyl0)
Revert "dev-cmd/bottle: set uid/gid." (@Homebrew)
dev-cmd/bottle: set uid/gid. (@MikeMcQuaid)
dev-cmd/bottle: revert filename in JSON to use single dash always (@Bo98)
Bottle reproducibility tweaks (@MikeMcQuaid)
brew.sh: add workaround for old auto-updates (@Bo98)
Service: generate systemd unit file (@SMillerDev)
sorbet: Update RBI files. (@Homebrew)
Always take first item in Sparkle strategy. (@reitermarkus)
software_spec: fix bottle domain fallback handling (@Bo98)
build: set SOURCE_DATE_EPOCH (@Bo98)
bin/brew: repair style (@hyuraku)
settings: use quieter system_command! (@MikeMcQuaid)
dev-cmd/bottle: fix INSTALL_RECEIPT appearing in changed_files (@Bo98)

What happened (include all command output)?
I noticed that the 3.1.3 tag points to https://github.com/Homebrew/brew/commit/d89eda09abbeae907eb88bd6d01dc9cde7ff0e19, which is the merge commit for https://github.com/Homebrew/brew/pull/11187, which isn't in the list.
What did you expect to happen?
I thought it would include that pull request.
I'm guessing the brew release command was run to create a draft release before all the pull requests were merged? Perhaps we need to update our release workflow to ensure the changelog is up to date just before publishing the release. It's easy enough to update the release notes after the fact, but I wanted to create this for visibility.
Step-by-step reproduction instructions (by running brew commands)
Running `puts ReleaseNotes::generate_release_notes('3.1.2', '3.1.3', markdown: true)` in a `brew irb` session gives the following:

- [formula: add rpath helper method](https://github.com/Homebrew/brew/pull/11187) (@carlocab)
- [search: properly deprecate `brew search --cask`](https://github.com/Homebrew/brew/pull/11182) (@Rylan12)
- [rubocops/patches: GitLab patches should use .diff](https://github.com/Homebrew/brew/pull/10760) (@jonchang)
- [rubocops/patches: remove autocorrection of some `url`s](https://github.com/Homebrew/brew/pull/11170) (@nandahkrishna)
- [build(deps-dev): bump html-proofer from 3.19.0 to 3.19.1 in /docs](https://github.com/Homebrew/brew/pull/11184) (@Homebrew)
- [Update maintainers, manpage and completions.](https://github.com/Homebrew/brew/pull/11188) (@Homebrew)
- [bump-cask-pr: add --fork-org flag](https://github.com/Homebrew/brew/pull/11181) (@Homebrew)
- [Update maintainers, manpage and completions.](https://github.com/Homebrew/brew/pull/11173) (@Homebrew)
- [bump-formula-pr: add --fork-org flag](https://github.com/Homebrew/brew/pull/11158) (@dawidd6)
- [Always take latest item in `Sparkle` strategy.](https://github.com/Homebrew/brew/pull/11171) (@reitermarkus)
- [formula: add `-DBUILD_TESTING=OFF` to `std_cmake_args`](https://github.com/Homebrew/brew/pull/11159) (@Bo98)
- [rubocops/patches: Fix quoting of the patch `url` when autocorrecting](https://github.com/Homebrew/brew/pull/11169) (@issyl0)
- [Revert "dev-cmd/bottle: set uid/gid."](https://github.com/Homebrew/brew/pull/11166) (@Homebrew)
- [dev-cmd/bottle: set uid/gid.](https://github.com/Homebrew/brew/pull/11165) (@MikeMcQuaid)
- [dev-cmd/bottle: revert filename in JSON to use single dash always](https://github.com/Homebrew/brew/pull/11163) (@Bo98)
- [Bottle reproducibility tweaks](https://github.com/Homebrew/brew/pull/11150) (@MikeMcQuaid)
- [brew.sh: add workaround for old auto-updates](https://github.com/Homebrew/brew/pull/11162) (@Bo98)
- [Service: generate systemd unit file](https://github.com/Homebrew/brew/pull/11133) (@SMillerDev)
- [sorbet: Update RBI files.](https://github.com/Homebrew/brew/pull/11161) (@Homebrew)
- [Always take first item in `Sparkle` strategy.](https://github.com/Homebrew/brew/pull/11146) (@reitermarkus)
- [software_spec: fix bottle domain fallback handling](https://github.com/Homebrew/brew/pull/11157) (@Bo98)
- [build: set SOURCE_DATE_EPOCH](https://github.com/Homebrew/brew/pull/11141) (@Bo98)
- [bin/brew: repair style](https://github.com/Homebrew/brew/pull/11152) (@hyuraku)
- [settings: use quieter `system_command!`](https://github.com/Homebrew/brew/pull/11139) (@MikeMcQuaid)
- [dev-cmd/bottle: fix INSTALL_RECEIPT appearing in changed_files](https://github.com/Homebrew/brew/pull/11145) (@Bo98)

sorry for all the @-mentions

Huh, I thought that commit wasn't included in the latest release tag, which is why I was sitting on https://github.com/Homebrew/homebrew-core/issues/75458. Guess I can go do that now.

If you run brew ruby -rrelease_notes -e 'puts ReleaseNotes.generate_release_notes("3.1.2", "3.1.3", markdown: true)' you'll get what the release notes algorithm woudl output now between those tags. Here it is:
$ brew ruby -rrelease_notes -e 'puts ReleaseNotes.generate_release_notes("3.1.2", "3.1.3", markdown: true)'
- [formula: add rpath helper method](https://github.com/Homebrew/brew/pull/11187) (@carlocab)
- [search: properly deprecate `brew search --cask`](https://github.com/Homebrew/brew/pull/11182) (@Rylan12)
- [rubocops/patches: GitLab patches should use .diff](https://github.com/Homebrew/brew/pull/10760) (@jonchang)
- [rubocops/patches: remove autocorrection of some `url`s](https://github.com/Homebrew/brew/pull/11170) (@nandahkrishna)
- [build(deps-dev): bump html-proofer from 3.19.0 to 3.19.1 in /docs](https://github.com/Homebrew/brew/pull/11184) (@Homebrew)
- [Update maintainers, manpage and completions.](https://github.com/Homebrew/brew/pull/11188) (@Homebrew)
- [bump-cask-pr: add --fork-org flag](https://github.com/Homebrew/brew/pull/11181) (@Homebrew)
- [Update maintainers, manpage and completions.](https://github.com/Homebrew/brew/pull/11173) (@Homebrew)
- [bump-formula-pr: add --fork-org flag](https://github.com/Homebrew/brew/pull/11158) (@dawidd6)
- [Always take latest item in `Sparkle` strategy.](https://github.com/Homebrew/brew/pull/11171) (@reitermarkus)
- [formula: add `-DBUILD_TESTING=OFF` to `std_cmake_args`](https://github.com/Homebrew/brew/pull/11159) (@Bo98)
- [rubocops/patches: Fix quoting of the patch `url` when autocorrecting](https://github.com/Homebrew/brew/pull/11169) (@issyl0)
- [Revert "dev-cmd/bottle: set uid/gid."](https://github.com/Homebrew/brew/pull/11166) (@Homebrew)
- [dev-cmd/bottle: set uid/gid.](https://github.com/Homebrew/brew/pull/11165) (@MikeMcQuaid)
- [dev-cmd/bottle: revert filename in JSON to use single dash always](https://github.com/Homebrew/brew/pull/11163) (@Bo98)
- [Bottle reproducibility tweaks](https://github.com/Homebrew/brew/pull/11150) (@MikeMcQuaid)
- [brew.sh: add workaround for old auto-updates](https://github.com/Homebrew/brew/pull/11162) (@Bo98)
- [Service: generate systemd unit file](https://github.com/Homebrew/brew/pull/11133) (@SMillerDev)
- [sorbet: Update RBI files.](https://github.com/Homebrew/brew/pull/11161) (@Homebrew)
- [Always take first item in `Sparkle` strategy.](https://github.com/Homebrew/brew/pull/11146) (@reitermarkus)
- [software_spec: fix bottle domain fallback handling](https://github.com/Homebrew/brew/pull/11157) (@Bo98)
- [build: set SOURCE_DATE_EPOCH](https://github.com/Homebrew/brew/pull/11141) (@Bo98)
- [bin/brew: repair style](https://github.com/Homebrew/brew/pull/11152) (@hyuraku)
- [settings: use quieter `system_command!`](https://github.com/Homebrew/brew/pull/11139) (@MikeMcQuaid)
- [dev-cmd/bottle: fix INSTALL_RECEIPT appearing in changed_files](https://github.com/Homebrew/brew/pull/11145) (@Bo98)

The two missing entries are both seen in this output which is also what's used to generate the changelog. The brew release command, when run, creates a new draft release and automatically fills in the changelog using ReleaseNotes.generate_release_notes latest_version, "origin/HEAD", markdown: true. My guess is that what's happened here is that brew release was run before those last two PRs were merged so they weren't included in the release notes. By the time the release was published, though, they had been merged (and the changelog had not been updated).

My guess is that what's happened here is that brew release was run before those last two PRs were merged so they weren't included in the release notes. By the time the release was published, though, they had been merged (and the changelog had not been updated).

Sounds about right. Closing and will pay closer attention to this in future.


Fix CNI error when net=host is not used in some podman calls

With 'podman version 1.0.0' on RHEL8 beta the 'get ceph version' and
'ceph monitor mkfs' commands fail [1] with "error configuring network
namespace for container Missing CNI default network".
When net=host is added these errors are resolved. net=host is used in
many other calls (grep -R net=host | wc -l --> 38).
Fixes: #3561
Signed-off-by: John Fulton<EMAIL_ADDRESS>

This might need to wait until https://github.com/ceph/ceph-ansible/pull/3526 gets merged.


add 302-redirect for /http3-explained/

Problem
the https://daniel.haxx.se/http3-explained/ is 404.
at first, i wanted to just update all the links in your blog, but for example the page https://daniel.haxx.se/blog/2019/08/05/first-http-3-with-curl/ is not even in the repo?
plus all the older links from around the web, which will be re-surfacing now that google switched GCP to H/3 by default and firefox got hit by it
proposed Solution
add 302-redirect from /http3-explained/ to https://http3-explained.haxx.se/

That's a good idea!

Thanks

np, kinda strange it wasn't part of the initial transition in https://github.com/bagder/daniel.haxx.se/commit/b591ce08d17a85b700452ac540e65140ecd99db7

just a silly mistake. I wanted to clean up some leftovers when I moved the site over to a new host, and this was just a little detail I've missed to fix since.


How to extract 1-million distractors descriptors

When I extract 1-million distractors descriptors, I find that the revisitop1m.txt file contains more images than the number of images extracted from 100 tar.gz files ( I download the http://ptak.felk.cvut.cz/revisitop/revisitop1m/), so I get an error when running the program（python3 -m solar_global.examples.extract_1m）. I would like to ask how you deal with this problem. Thank you for your reply.

Hi,
Sorry for the delay. Do you mind sharing your directory structure?


Problem: orchestrator cannot build

Revert the dependency upgrade https://github.com/crypto-org-chain/gravity-bridge/pull/50 because it is breaking the build

seems that the vulnerability does not affect us
https://github.com/tokio-rs/prost/issues/438

yes I've tried to do it but it end up breaking too many things. May give a try later (https://github.com/crypto-org-chain/gravity-bridge/issues/216)


Update vue.md

Specify minor versions

Need to understand the reasoning behind this change to see if it is helpful

Setting a changelogTemplate is a good idea
Will splitting into minor versions be actually helpful? the current page already suggests the correct 2 versions to use (3.4.31 or 2.7.16 with commercial support). Adding the extra releases doesn't seem to be helpful.

I found that mentioning only major releases was vague and imprecise

I also often use not only use endoflife.date not only to see if a version has reached EOL but how old it is.
Up to you to decide if you think it is relevant or not.
I don't know why the pipeline has failed, I can't check the logs.

Ok I found:
Product Validator: Invalid releaseDate '2022-07-01' for vue.md#releases#2.7, expecting a value before eoas (2022-03-18).

I also often use not only use endoflife.date not only to see if a version has reached EOL but how old it is.

This is helpful, thanks!
The error log says:
Product Validator: Invalid releaseDate '2022-07-01' for vue.md#releases#2.7, expecting a value before eoas (2022-03-18).

Would be nice to have eol/eoas dates for the minor releases, since the policy is known.

I can't find where does the eoas: 2022-03-18 information come from. It was added in the original commit creating vue.md.

Ok, so every time there is a new minor, the previous minor does not receive any new patch, so I can consider that each EOAS/EOL is actually the release date of the following minor.
The only exception may be 2.7, for which EOAS in uncertain. I decided to consider EOAS to be the same as EOL (2023-12-31). Is it OK for you?

Yes, that sounds good.

I've marked 2.6 as under NES commercial support as well.


No GPU support ?

I have tried the the codes in tf-gpu. But it doesnt seems to work !
Does it not support GPU computation ?

@farshidrayhan Try converting some of the numpy operations into Cupy if you already have native cuda support.

@farshidrayhan this package doesn't support gpu computations.


Create locking mechanism to allow for sequential execs

Create two magic-string args for specifying lock and unlock ops.
Locks are referenced with a string name, additional locks on a
previously locked lock of the same name are ignored.
Signed-off-by: Alex Couture-Beil<EMAIL_ADDRESS>

Is this still ongoing?

Is this still ongoing?

It's on the backburner, but still needs the context-aware lock to unlock if the session is lost/prematurely disconnected.


Scoreboard entries with long names can kick players.

If a score in the sidebar scoreboard has a name greater than 40 characters, the user will disconnect with an error. Sponge should check to make sure a particular string is within that limit, and truncate it if need be.
Mentioning @Aaron1011 cause scoreboards.

Probably best to throw an exception instead of truncating - here's what vanilla does, for reference:
        if (username.length() > 40)
        {
            throw new IllegalArgumentException("The player name \'" + username + "\' is too long!");
        }

Agree with @kashike, truncating could technically allow overlap, and it's a pretty valid reason to throw.

This does leave an unanswered question though. Let's say this does happen. How would I go about truncating a Text object that is too long?

Actually, Objective names apparently have a 36 character limit. An exception should be thrown there too @Aaron1011.

@gravityfox Objective display names are limited to 32 characters, not 36.
As for objective names - they are internally limited to 16 characters:
        if (name.length() > 16)
        {
            throw new IllegalArgumentException("The objective name \'" + name + "\' is too long!");
        }

I meant the display name. xD
Either way my score names and display names have variable length, and if players decided to use ridiculously long world names or foxguard object names then it just sorta explodes. I would like to have it NOT do that.


Developer experience audit from @mntnr

:wave: Hey there! This is the developer experience audit from @mntnr for this repository. I've added in my thoughts below, in the form of a checklist. Looking forward to seeing what you think; let's see if we can resolve all of the open issues and make this repository shine ✨ 💖 ✨
Repository Review: probot/probot.github.io

This is the home of probot documentation, apps, how-to guides and more.

For notes on anything crossed out, look below. Note: I use [~] to mean that I have proposed a fix in a PR. I know it doesn't render properly in Markdown, but it works pretty well otherwise for that purpose. If I think that something is fine, even if it isn't valid according to this checklist, I've checked it off and included a note.
Reviewing the Repository Docs

[x] Is there a README?

[ ] Does it follow standard-readme? More or less
[x] Is it spellchecked?

[x] Is there a Code of Conduct, such as the Contributor Covenant?

[x] Is it mentioned in the Contribute section of the README? (Note: this isn't needed if you mention it in your CONTRIBUTE.md and it is in this repository.)
[x] Does it reference an email address for violations?

[x] Is there a LICENSE file?

[ ] Is the year correct? There's no year or attribution in the file. I'm not sure if that's Ok. Ask your lawyer.

[x] Is there a .github or docs folder?

[ ] Is there an ISSUE_TEMPLATE.md?
[ ] Is there a PULL_REQUEST_TEMPLATE.md?

[x] Is there a CONTRIBUTING.md file?

[x] Does it mention how to make a PR?
[~] Does it mention what sort of issues you'd like?
[~] Does it mention a good first issue label as a starting point?
[ ] Does it mention triaging and bug reports as good starting points? I think this is OK for this repo.
[~] Does it point to a community chat program, like Slack or Gitter?
[~] Does it encourage conversations in issues before opening huge PRs?
[~] Does it specify where to ask questions on process?
[~] Does it explain labels used in the issues?

[ ] Is there a CHANGELOG? _Probably not necessary for this repo.)

[ ] If there isn't, are notes included in the project's releases?

[x] Does this pass alex adequately? Run alex *.md.
[x] Does the repository name itself pass on http://wordsafety.com?

Process

[~] Can I install easily? _I included some directions in the README, and edited the scripts in the script folder to make this easier.
[~] Can I use this easily?

Issues and Pull Requests

[x] Are there an acceptable amount of pull requests?
[x] Are there an acceptable amount of issues?
[x] Are an acceptable amount of issues less than six months old?
[x] Are there useful issue labels?
[x] Are the labels being used? Could be better, though
[x] Is there a good for beginners or good first issue label?
[ ] Is there a waiting on contributor label? Might be useful

Bots
Note: Neither of these are necessary, but they can help with some things. Check out https://probot.github.io/ for some tools.

[x] Are there bots enabled? Stalebot
[~] Are the bots listed in the Contribute or Readme files so that users can expect to interact with them?

Metadata

[x] Is there a description on GitHub?

[ ] Does the description match the README? No, it doesn't. I think that the one in the README is better, because it makes it clear that this is for the website. I would update it on GitHub to: "This is the home of probot.github.io, a website for probot documentation, apps, how-to guides and more."

[x] Are the topics useful?
[x] Is there a website?

[x] Does the website match the project?

TODO
This is generally pretty good! I've added a PR and gone through and fixed the salient issues. I don't think this needs much more scrubbing at the moment.
Generic

[ ] Add a link to your Slack! You want to engage with users there.
[ ] Consider adding ISSUE_TEMPLATE.md and PULL_REQUEST_TEMPLATE.md files to your repository. It looks like you have your PRs well under control, but these may help you in the future. At the least, ask them to run the tests, first, and to read the Usage guides.
[ ] This audit does not cover license dependency. For that, I suggest using either licensee or an external tool like Fossa. Let me know if you want more help here.

Issues

[ ] Considering adding available labels as well as good first issue and help wanted. These can be used to signal that you're looking for community involvement for issues. They can also be configured to display on http://up-for-grabs.net. This will help more people interact with your code, and lead to small, iterative work done by others. It may take some time to set up initially - properly scoping issues for newcomers takes some time - but the payback should be worth it.
[ ] I label pull requests where I am waiting on the Contributor to respond waiting on contributor. This helps alleviate pressure on you to close them.

Contribute back?
This checklist is open source! If you have suggestions or think it could be better, contribute back on mntnr/audit-templates.
Thank you!

Thank you, @hiimbex!


Support for BDD

Thank you very much for this great support for better integration tests!
We appreciate your work and how it fixes many issues the flutter team still needs to tackle.
Our product/team uses BDD for testing because it fits our philosophy of testing in the best way.
Do you have any plans to include this testing strategy and make it compatible with patrol?

Hi @MitkoTschimev, thanks for the kind words :) We're happy that you find Patrol useful.
We don't have plans to add any kind of BDD support to Patrol itself, but we'd be happy to see the community build BDD-related tooling around it. In fact, some time ago, @nonvachara-paloit managed to get flutter_gherkin (one of the most popular BDD packages for Flutter, I think) to work with Patrol. See this discussion to learn more.
I haven't tested it, and because of breaking changes in Patrol, some of the code in that discussion may require a bit of refactoring, but in principle, it works.

Closing since there's no work to be done on our side.


[docs] update README with iOS info

This PR adds a run of the Playbook for iOS

it starts from React Native 0.67.3
it migrates to a nighlty build
it creates a TurboModule
it creates a Fabric Component

:shipit:


Firebase SDK 9 won't build with adapter-static

Describe the bug
When trying to use Firebase SDK 9, as per the recommendations on SvelteKit docs, the library initially will not work. One can make it work by adding vite.ssr.external: ["firebase"]. However, this only works for dev, and trying to run npm run build with adapter set to adapter-static, gives the error described in the logs section below.
Reproduction
To reproduce:

Initialize SvelteKit:

npm init svelte@next firebase-app

Add firebase 9 SDK

npm i<EMAIL_ADDRESS>

In any page or component, try the following:

import { initializeApp, getApps } from 'firebase/app';
import { onAuthStateChanged, getAuth, signOut, signInWithPopup, GoogleAuthProvider } from 'firebase/auth';

Just importing these functions should produce the error, though I'll continue just a bit.
const firebaseConfig = /* config file */

const firebaseApp = initializeApp(firebaseConfig);

const auth = getAuth(firebaseApp);
signInWithPopup(auth, new GoogleAuthProvider());

Try in development...should work, unless I made a silly mistake somewhere above...;)

npm run dev

Try building, should fail.

npm run build

Logs
> Using @sveltejs/adapter-static
> Named export 'GoogleAuthProvider' not found. The requested module 'firebase/auth' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'firebase/auth';
const { getAuth, signOut, signInWithPopup, GoogleAuthProvider, onAuthStateChanged } = pkg;

file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:3
import { getAuth, signOut, signInWithPopup, GoogleAuthProvider, onAuthStateChanged } from "firebase/auth";
                                            ^^^^^^^^^^^^^^^^^^
SyntaxError: Named export 'GoogleAuthProvider' not found. The requested module 'firebase/auth' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'firebase/auth';
const { getAuth, signOut, signInWithPopup, GoogleAuthProvider, onAuthStateChanged } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:179:5)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async prerender (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:80:14)
    at async Object.prerender (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:312:5)
    at async adapt (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/adapter-static/index.js:17:4)
    at async adapt (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:338:2)
    at async file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/cli.js:905:5

Special Note
Trying to follow the advice proviced by the error message doesn't help either:
import * as app from 'firebase/app';
const { initializeApp, getApps } = app;
import * as authPkg from 'firebase/auth';
const { onAuthStateChanged, getAuth, signOut, signInWithPopup, GoogleAuthProvider } = authPkg;

Gives the following:

Using @sveltejs/adapter-static
TypeError: getApps is not a function
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:324:23
at Object.$$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:384:52
at Object.$$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:158:78
at $$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at Object.render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:93:20)
at render_response (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:379:28)
at async respond$1 (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:1187:10)
at async render_page (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:1230:20)
TypeError: getApps is not a function
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:324:23
at Object.$$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:384:52
at Object.$$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:158:78
at $$render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:85:18)
at Object.render (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/.svelte-kit/output/server/app.js:93:20)
at render_response (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:379:28)
at async respond_with_error (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:980:10)
at async respond$1 (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/ssr.js:1199:10)
500 /
Error: 500 /
at error (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:94:11)
at visit (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:176:5)
at async prerender (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:245:5)
at async Object.prerender (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:312:5)
at async adapt (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/adapter-static/index.js:17:4)
at async adapt (file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/chunks/index6.js:338:2)
at async file:///C:/Dev/Commercial/Importadora%20Queara/system/app-web-desktop/node_modules/@sveltejs/kit/dist/cli.js:905:5

System Info
Using the latest version of everything:
- `SvelteKit: next`
- `svelte-adapter: 1.0.0-next.13`
- `node: v16.5.0`
- `npm: 7.19.1`

Severity
blocking an upgrade
Additional Information
Marked as blocking an upgrade because without being able to build, cannot test on deployments or other platforms.

Duplicate of #1850.

@Conduitry
This is actually not the same issue. I didn't include the @firebase/... in the code above, but doing so still doesn;t solve the problem

@Conduitry
This is actually not the same issue. I didn't include the @firebase/... in the code above, but doing so still doesn;t solve the problem

Changing everything form "firebase/" to "@firebase/" should solve the problem because I am working with the same components and it did work for me like I mentioned in #1850

@abdo643-HULK
It would be amazing if it did, but unfortunately it does not. Only one component is currently using firebase, and I'll attach the code below, unfortunately, I am not allowed to share the entire repo. I did, however, find a workaround, that did involve changing all the imports to @firebase/..., though, the exception was auth. What I had to do for auth to work, was as follows:
import * as authPkg from '@firebase/auth'; // Gets around Firebase Vite issue

and then
const { /* auth functions */ } = authPkg;

Once again, just in case, I am using adaptor-static, I don't know if other adapters would work differently in this case, and I am guessing yes, because I am able to npm run dev just fine, only when I npm run build, I have issues.
The full component code is below:
// Backend.svelte

<script lang="ts">
	// Env
	import { dev, browser } from '$app/env';

	// Stores
	import { session } from '$app/stores';

	// Events
	import { createEventDispatcher } from 'svelte';

	// Firebase
	import { initializeApp, getApps } from '@firebase/app';
	import * as authPkg from '@firebase/auth'; // Gets around Firebase Vite issue
	import { useFirestoreEmulator, getFirestore } from '@firebase/firestore';
	import { firebaseConfig } from '$lib/firebaseConfig';
	import { getFunctions, useFunctionsEmulator } from '@firebase/functions';
	import { getStorage, useStorageEmulator } from '@firebase/storage';
	const {
		onAuthStateChanged,
		getAuth,
		signOut,
		signInWithPopup,
		signInWithEmailAndPassword,
		createUserWithEmailAndPassword,
		GoogleAuthProvider,
		useAuthEmulator,
		setPersistence,
		inMemoryPersistence
	} = authPkg;

	// Context
	import { setContext } from 'svelte';

	// Types
	import { FIREBASE_CTX_KEY, BACKEND_CTX_KEY } from '.';
	import type { BackendContext, Session } from '.';

	const firebaseApp = getApps()[0] ? getApps()[0] : initializeApp(firebaseConfig);

	// Get the SDK's
	const auth = getAuth(firebaseApp);
	const firestore = getFirestore(firebaseApp);
	const functions = getFunctions(firebaseApp);
	const storage = getStorage(firebaseApp);

	// Set up emulators
	dev && useEmulators();

	// Listen to user auth changes
	browser &&
		onAuthStateChanged(auth, (user) => {
			if (user) {
				const userSession = {} as Session;

				userSession.name = user.displayName;
				userSession.uid = user.uid;
				userSession.profilePicture = user.photoURL;

				$session.user = userSession;
			} else {
				$session.user = null;
			}
		});

	const cypress = browser && (window as any).Cypress ? true : false;

	const backendCtx: BackendContext = {
		signOut: () => signOut(auth),
		signIn: () => {
			signInWithPopup(auth, new GoogleAuthProvider());
		},
		cypress
	};

	setContext(FIREBASE_CTX_KEY, {});
	setContext(BACKEND_CTX_KEY, backendCtx);

	function useEmulators() {
		useAuthEmulator(auth, 'http://localhost:9099', { disableWarnings: true });
		useFirestoreEmulator(firestore, 'localhost', 8000);
		useFunctionsEmulator(functions, 'localhost', 5001);
		useStorageEmulator(storage, 'localhost', 9199);
	}

	async function signInCypress(email: string, password: string) {
		// Make sure persistence is set to NONE
		await setPersistence(auth, inMemoryPersistence);

		try {
			await signInWithEmailAndPassword(auth, email, password);
		} catch {
			await createUserWithEmailAndPassword(auth, email, password);
		}
	}

	if (cypress) {
		(window as any).signInCypress = signInCypress;
	}
</script>

<slot />

@abdo643-HULK
It would be amazing if it did, but unfortunately it does not. Only one component is currently using firebase, and I'll attach the code below, unfortunately, I am not allowed to share the entire repo. I did, however, find a workaround, that did involve changing all the imports to @firebase/..., though, the exception was auth. What I had to do for auth to work, was as follows:
import * as authPkg from '@firebase/auth'; // Gets around Firebase Vite issue

and then
const { /* auth functions */ } = authPkg;

Once again, just in case, I am using adaptor-static, I don't know if other adapters would work differently in this case, and I am guessing yes, because I am able to npm run dev just fine, only when I npm run build, I have issues.
The full component code is below:
// Backend.svelte

<script lang="ts">
	// Env
	import { dev, browser } from '$app/env';

	// Stores
	import { session } from '$app/stores';

	// Events
	import { createEventDispatcher } from 'svelte';

	// Firebase
	import { initializeApp, getApps } from '@firebase/app';
	import * as authPkg from '@firebase/auth'; // Gets around Firebase Vite issue
	import { useFirestoreEmulator, getFirestore } from '@firebase/firestore';
	import { firebaseConfig } from '$lib/firebaseConfig';
	import { getFunctions, useFunctionsEmulator } from '@firebase/functions';
	import { getStorage, useStorageEmulator } from '@firebase/storage';
	const {
		onAuthStateChanged,
		getAuth,
		signOut,
		signInWithPopup,
		signInWithEmailAndPassword,
		createUserWithEmailAndPassword,
		GoogleAuthProvider,
		useAuthEmulator,
		setPersistence,
		inMemoryPersistence
	} = authPkg;

	// Context
	import { setContext } from 'svelte';

	// Types
	import { FIREBASE_CTX_KEY, BACKEND_CTX_KEY } from '.';
	import type { BackendContext, Session } from '.';

	const firebaseApp = getApps()[0] ? getApps()[0] : initializeApp(firebaseConfig);

	// Get the SDK's
	const auth = getAuth(firebaseApp);
	const firestore = getFirestore(firebaseApp);
	const functions = getFunctions(firebaseApp);
	const storage = getStorage(firebaseApp);

	// Set up emulators
	dev && useEmulators();

	// Listen to user auth changes
	browser &&
		onAuthStateChanged(auth, (user) => {
			if (user) {
				const userSession = {} as Session;

				userSession.name = user.displayName;
				userSession.uid = user.uid;
				userSession.profilePicture = user.photoURL;

				$session.user = userSession;
			} else {
				$session.user = null;
			}
		});

	const cypress = browser && (window as any).Cypress ? true : false;

	const backendCtx: BackendContext = {
		signOut: () => signOut(auth),
		signIn: () => {
			signInWithPopup(auth, new GoogleAuthProvider());
		},
		cypress
	};

	setContext(FIREBASE_CTX_KEY, {});
	setContext(BACKEND_CTX_KEY, backendCtx);

	function useEmulators() {
		useAuthEmulator(auth, 'http://localhost:9099', { disableWarnings: true });
		useFirestoreEmulator(firestore, 'localhost', 8000);
		useFunctionsEmulator(functions, 'localhost', 5001);
		useStorageEmulator(storage, 'localhost', 9199);
	}

	async function signInCypress(email: string, password: string) {
		// Make sure persistence is set to NONE
		await setPersistence(auth, inMemoryPersistence);

		try {
			await signInWithEmailAndPassword(auth, email, password);
		} catch {
			await createUserWithEmailAndPassword(auth, email, password);
		}
	}

	if (cypress) {
		(window as any).signInCypress = signInCypress;
	}
</script>

<slot />

Here is the link to the project I am working on right now https://github.com/abdo643-HULK/LA-MEDITERRANEE

Maybe it's cause of es2015 ? (Saw in your svelte.config.js


Adding creative cloud stage link to stageDomainsMap

Added support to convert links authored with creativecloud.adobe.com to stage.creativecloud.adobe.com on stage environment

Resolves: MWPW-160934
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://cc-stage-link--milo--adobecom.hlx.page/?martech=off

QA:
https://adobecom.github.io/nav-consumer/navigation.html?authoringpath=/federal/dev/blaishram&customlinks=home,discover&navbranch=cc-stage-link

Validation done on the pr on the below url
https://adobecom.github.io/nav-consumer/navigation.html?authoringpath=/federal/dev/blaishram&customlinks=home,apps,discover,file,firefly,benefits,learn,action&navbranch=cc-stage-link
In mobile mode custom links authored is seen pointing to stage

discover link which has authoring is seen pointed to
https://stage.creativecloud.adobe.com/cc/discover?locale=en
Results are added in
https://jira.corp.adobe.com/browse/MWPW-160934


Update README.md

There should be description about the product and store relation because if any guy who is new to rails will not be able to use this example, We should also add more descriptions about the schema of these tables to make it simple for guys who are new to rails.
If any one tries this "tore = Store.create
store.products << Pen.create" it will return an error.

Thanks


suppress statistics warnings

this should prevent errors such as WARNING caught exception during statistics processing: Expecting Object from the statistics during version upgrades

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/1554/


chore(main): release 0.9.4

:robot: I have created a release beep boop
0.9.4 (2023-12-09)
Bug Fixes

fix: Support fetching multiple databases and schemas and their associated tables

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Mause/duckdb_engine/releases/tag/v0.9.4 :sunflower:


Add a link to the icon list.

I had to ask in Discord for this link, this will help people looking for icons in the future.

A link to https://docs.obsidian.md/Plugins/User+interface/Icons would be better.


[WIP]fix: 避免azure uefi重装系统失败

这个 PR 实现什么功能/修复什么问题:
避免azure uefi重装系统失败
是否需要 backport 到之前的 release 分支:

release/3.1

Codecov Report

Merging #6534 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

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


Enable stale Action

Adds stale label after 6 months of no activity and closes after 7 days of adding the label.
Excludes issues with labels breaking-change and Pri1. Any others?
This should not act on PRs because we're not explicitly giving write permissions to PRs.
Also, this initial configuration sets debug-only to true, so it will just do dry runs until that line is deleted/changed to false.

If I understand this correctly, any issue that ages 120 days would get the "needs-more-info" label, and then be closed in an additional 14 days, correct?
I want to make sure I understand its workflow correctly.

If I understand this correctly, any issue that ages 120 days would get the "needs-more-info" label, and then be closed in an additional 14 days, correct?

Yes, that's correct. And that doesn't sound like a good label to use now that you put it that way. Perhaps we do need both the no-response bot (or similar - perhaps FabricBot has this functionality) and the stale bot.

I would strongly discourage the use of a stale bot on Microsoft Docs repos. As an outside user, I've often found the handling delay is the correct Microsoft employee reaching the issue, not the outside user. Perhaps rather than incorrectly closing issues that were never handled by staff, the bot should increasingly aggressively find a stakeholder to address the issue?
At a random selection of old issues on this repo: https://github.com/dotnet/docs/issues/19562 the requestor answered all requests promptly, providing sample code and all, and it took five months after that step, for someone to recommend someone else review it... who just never showed up at all, and now it's been nearly two years.
Which is to say, stale bots should only be used if they're successful in only targeted issue abandonment by outside users, not internal staff.
Note that the above issue has a tag your stale bot will ignore, so... I picked another at random: https://github.com/dotnet/docs/issues/18627 Two years ago, a Microsoft staff member confirmed the issue was valid, and then nothing was done with it. So it's a confirmed actual issue, unaddressed, and I believe this new stale action will close this issue.

@ocdtrekkie Thanks for your input. I totally agree that the handling delay is usually on our side (Microsoft docs), and all that means is that we simply don't have the time to address the issue when prioritized with all the other issues that also need attention. It's definitely not ideal to close out issues that are still relevant simply because they're old, but it does help us to focus on the most important issues. Any issues closed via this automation will include a note that says to reopen it if still deemed important enough - so the hope is that the bot will help to decrease the number of active issues, and also to resurface forgotten issues that shouldn't have been forgotten.
We have a separate "no-response" workflow that deals with issues that require more information from the original poster in order to be actionable. This "stale" workflow serves a different purpose.


README.cn.md doesn't follow naming convention

The spec states that projects supporting I18N should use BCP 47 for language tags.
I don't know Chinese but I do know that cn is not a BCP 47 language tag :smile:
I do know Japanese so am able to recognize some of the characters.
Looking at README.cn.md it appears to be Simplified Chinese which normally uses zh_CN.  I suggest renaming the file.
You might use zh but that is almost guaranteed to upset people in Taiwan who use Traditional Chinese, zh_TW.  This looks different enough that I can usually tell the difference given enough text (even though I cannot really read it).  Actually, there are more variants (some would even be served better by the three letter language tags) for regions with large groups of Chinese speakers, such as zh_HK and zh_SG.

Interesting! Not sure how cn slipped in.
My 2cts is go with zh. We do not know which regions the author(s) came from, but we do know that it is Chinese (hence zh), in the simplified script (trusting your judgement, giving zh-Hans). We can then hopefully stay away from regions. However, Unicode CLDR suggests that zh-Hans is more information that often needed: because Hans is the most used script associated with the macrolanguage zh, zh implies Hans. (They also suggest using pt for Portuguese as spoken in Brazil, en for English as spoken in the USA, es for Spanish in South America).

We don't know about the initial translator but there are a pile of fixes by @bugstop who claims to be from Shenzhen, Guangdong.
Either way, almost definitely mainland China, so I'd go with zh_CN.
My 2 yen :wink:

ok, i will check it later~

OK, i will fix it soon

so now the commits in my PR have updated the correct filename as you guys suggested~

I'm not seeing an open PR. Am I missing something?

Well, cn is a strange convention, but I think just use zh hurts readability because we Chinese might miss it since it's not widely used.
Actually, from my point of view, zh-Hans and zh-Hant better describe the difference between simplified Chinese and traditional Chinese, because we use nearly the same grammar and vocabulary. The writings might look totally different (because we use different sets of characters), but we can read each other's content.
However, for readability, I suggest keep cn in, and zh-CN is a compromise.

@RichardLitt The PR was https://github.com/RichardLitt/standard-readme/pull/115 I believe. I think this can be closed.
To recap my opinion: I feel “zh” or “zh-Hans” would be preferred (per Unicode) over “zh-CN”, although they’re all valid per BCP-47. And cn is nonstandard per both.

Thanks, all. I think what we have works well, if I read this right.


mask_image is black when testing my own picture?

Thank you for your great share! when I tested the net on my own picture, I found that the mask_image was black , so how should I do?

@Keyird The post process can only be used to process tusimple data. You need to modify the post process code to fit your dataset or you could simply add instance segmentation mask on source image:)

Thank you for your great share! when I tested the net on my own picture, I found that the mask_image was black , so how should I do?

I've solved by changing the variables related to postprocessing in the .yaml file under config folder.

@Keyird The post process can only be used to process tusimple data. You need to modify the post process code to fit your dataset or you could simply add instance segmentation mask on source image:)

Thank you for your reply

Thank you for your great share! when I tested the net on my own picture, I found that the mask_image was black , so how should I do?

I've solved the same problem by changing the variables related to postprocessing in the .yaml file under config folder.

Thank you for your reply!

Thank you for your great share! when I tested the net on my own picture, I found that the mask_image was black , so how should I do?

I've solved the same problem by changing the variables related to postprocessing in the .yaml file under config folder.

What procedure did you use in order to determine what parameters work for your dataset? And what parameters did you change? Thanks

Thank you for your great share! when I tested the net on my own picture, I found that the mask_image was black , so how should I do?

I've solved the same problem by changing the variables related to postprocessing in the .yaml file under config folder.

What procedure did you use in order to determine what parameters work for your dataset? And what parameters did you change? Thanks

Hi,
Sorry for really late reply. If you still didn't solve the problem, I have changed the values in

POSTPROCESS:
MIN_AREA_THRESHOLD: 100
DBSCAN_EPS: 0.35
DBSCAN_MIN_SAMPLES: 1000

part. I've read past open and closed issues. I don't remember exact values, but I've set for my own images by trial and error.
Best


Feature request: Support Citation for DocBook

DockBook has citation tag <citation> but Asciidoctor does not support that (yet). Regarding that asciidoctor-bibliography already parse citations it can also add this support.
I do not know if Asciidoc -> DocBook is still common for most of users or not, but Asciidoc -> DocBook -> (Xe)Latex is still the most reliable way of creating Latex document from asciidoc and get the Tex family typesetting quality features.

I think this might be already feasible, @shahryareiv.
We're already had the need to render citations and bibliographies to RFC (essentially XML) when pairing asciidoctor-bibliography with asciidoctor-rfc.
We managed to do that by

defining AsciidoctorBibliography::Databases::RFC to import RFC bibliographic databases and
writing a custom CSL style to render citations and indices (to be used with the passthrough option).

Adapting this to the case of DocBook should be relatively straightforward.


[EventGrid] Regenerate code using the latest rest commit sha

Added API Manangement System Event
and other exsiting events

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here

API changes have been detected in this PR. You can review API changes here


Introduction and Tutorial

Summary
Tutorial from paper and introduction update.

[ ] Unit tests provided for these changes
[ ] Documentation and docstrings added for these changes using the sphinx style

Changes

Intro updated.
Tutorial updated.

Codecov Report

Merging #89 (490e945) into main (d0323ab) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   94.65%   94.65%
=======================================
  Files          34       34
  Lines        1478     1478
=======================================
  Hits         1399     1399
  Misses         79       79

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 d0323ab...490e945. Read the comment docs.