[Feature Request] dont open a Website

I reflected my self about why i do not use Andstatus and the Fediverse more often. Now I got a result. I do not like it that a cklick on something open a Website. To be able to like it using Andstatus, it have to be possible to do all importand and common activities inside the same app.
The most thing I do not like is the change of layout and style. Also the situation that some website are not optimized for mobile using.
The change from a dark them app to a light colored theme from a Website and back is also not that enjoying.

Currently, when you tap (click) a note (tweet), either some web site opens (if you tapped a link) or the note's context menu opens.
@Mannshoch Do you mean that links in a note/tweet should not be "clickable"? If yes then tapping any part of a note will open its context menu.
?!

Sorry. I'm not sur if i understood what you meant wit note and tweet.
What i meant was @USER and #TAG. If i click on them this links should not open in Webbrowser.

So you are telling not about all links, but only about links, which look like:

@user - user mentioned
#TAG - hash tag
AndStatus doesn't create these links: they are automatically created by a server.

As I understand, you propose to add an option to change AndStatus behaviour on clicking these links. What AndStatus should do:

Nothing (i.e. remove these links)
or
Open some view (i.e. "User timeline" for mentioned user and "Search #TAG" timeline for a tag)
?!

I would vote for the second solution.
Andstatus should Open these Links on a new view where I could find posts about #TAG or could find posts from @USER.
OPTIONAL:

For @USER The first Top Post (maybe in a folded status) could be some Profile Information.
Maybe also Interesting if the first Tab of #TAG contain some Information (maybe in a Folded status) about the found posts (how many found, on which servers, possibility to save as favorite, etc)

@Mannshoch Interesting, thank you for the insight.
I will create two separate tickets to implement these features.

Implemented in v.43


Federated api server should validate cluster api server address

 Issue by mwielgus
Sunday Aug 21, 2016 at 10:13 GMT
Originally opened as https://github.com/kubernetes/kubernetes/issues/31074

Currently it is possible to pass just an IP address without any schema/port information (no https://) which leads to connectivity problems.
Also http://kubernetes.io/docs/admin/federation/ should give an example of valid cluster object and tell to include the schema .
Ideally, if FEDERATION=true is passed to kube-up.sh the corresponding cluster.yaml file should be generated automatically.
cc: @quinton-hoole @kubernetes/sig-cluster-federation

 Comment by fejta-bot
Monday Jan 08, 2018 at 18:26 GMT

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

cc @mwielgus


Issues/73

In built tarfile module to get more control

[x] : During compress also try with it.

[ ] During compress also try with it.

[ ] During compress also try with it.

[ ] Remove tar.exr

This branch has some extra changes from what was originally required in #73, need to rebase and merge.


Delay

Hi, I would recommend adding a HitDelay option, example:
HitDelay: 1 #In seconds
Or a similar option that work similar to NoHitDelay plugin, but in this plugin and optimized for 1.9 to 1.12 :)
Can you add this in future?
(i'm italian)

What is the purpose of the hit delay? Is it like issue #19?

That doesn't mean anything, it simply isn't at the top of the list of priorities. For example, old potion effects affect combat more than hit delay and so that's what I'm working on now.
If you have anything you want to add regarding this hit delay, including your interest in its development, do so on issue #19


add create line

add create line
make it inline

#4291
#4290  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @wraeth-eth and the rest of your teammates on  Graphite

Merge activity

Mar 27, 4:52 AM EDT: @wraeth-eth started a stack merge that includes this pull request via Graphite.


Add ModSync support

Add ModSync file
set version number

appreciate the effort, but no, we talked about it.


feat(deal-ticket): enhance for fee discounts

Related issues 🔗
Closes #5244
Demo 📺
With discounts

Without discounts

@bglownia I'm not sure if the total fee in your screenshot is correct?
3.020065 - 19% is 2.44625265 ( and this would round to 2.446253? )
not 2.446254

@bglownia I'm not sure if the total fee in your screenshot is correct? 3.020065 - 19% is 2.44625265 ( and this would round to 2.446253? ) not 2.446254

Calculations are correct. When counting discount values floor function is used. Because  of rounding we get slightly different value, and there is no way to correct it. We can try to calculate factor base on values but this will give factor with lot of decimals
fee
3020065
referral
floor(3020065*0.1)=302006
volume
3020065-302006=2718059
floor(2718059*0.2)=543611
total discount
543611+302006=845618
discount factor calculated from value
845618/3020065=0.2799999337762598

@bwallacee I think in this case using the value directly from the formula is fine, we might get a little rounding but in this case its fine


[bug] Styles not being applied in new nextjs apps

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.0.26
Current Behavior
Trying to render a simple <Box /> componenet does not inject styles in the ppage. Classes on dom nodes are added but not styles are not applied.
Expected Behavior
The components should be styled.
Steps To Reproduce
Code  -
On stackblitz - does not work
On degen Playground -  works
import { Box, Button } from 'degen'

export function Header() {
  return (
    <Box as='header' padding='16' backgroundColor='yellow'>
      <Box padding='16' backgroundColor='black' color='white' fontFamily='mono'>
        <Button>Hello World</Button>
      </Box>
    </Box>
  )
}

Anything else?
No response

Hi, I got the same problem, no style are applied to the components. Have you fix it?

Hi, I got the same problem, no style are applied to the components. Have you fix it?

@CodeAunt Yeah, I realised that I never wrapped the app with the ThemeProvider

Hi, I got the same problem, no style are applied to the components. Have you fix it?

@CodeAunt Yeah, I realised that I never wrapped the app with the ThemeProvider

Sorry for not reading the document carefully. Thanks.

Hi, I got the same problem, no style are applied to the components. Have you fix it?

@CodeAunt Yeah, I realised that I never wrapped the app with the ThemeProvider

sorry, I still fail to apply the styles.
I tried to wrap the root of the App in create-react-app like this but still fail to activate the style.
...
import { ThemeProvider } from 'degen';

ReactDOM.render(
  <ThemeProvider>
    <React.StrictMode>
      <Button>Click</Button>
      {/* <App /> */}
    </React.StrictMode>
  </ThemeProvider>
  ,
  document.getElementById('root')
);
...

And in Next.js
I tried this,
import { ThemeProvider, Button } from 'degen'

const MyApp = ({ Component, pageProps }: AppProps) => {
  return (
  <ThemeProvider>
    {/* <Component {...pageProps} /> */}
    <Button>Click</Button>
  </ThemeProvider>)
}

All of them failed.
And I also added font to them with
yarn add @fontsource/inter
yarn add @fontsource/ia-writer-mono

Could you give me some tips to make this?

@CodeAunt Refer to this stackbltz example.
In your code you seem to have missed importing the styles import 'degen/styles';. ThemeProvide is one of two imports.

@CodeAunt Refer to this stackbltz example. In your code you seem to have missed importing the styles import 'degen/styles';. ThemeProvider is one of two imports.

Oh, When I added this on react and import 'degen/styles'; causes can't resolve error, I manully added the content from style.css to index.css and the components work fine now.
And this line import 'degen/styles'; works fine in next.js. Thanks a lot for your immediate reply ❤


Better examples for static stubs

It is strange to show static method stubbing using an Instance. In my opinion it seems more natural to use className to stub a static method. We could change only one example to show multiple possibilities.
Removed " for ' to avoid variable interpolation for those examples ($foo doesn't exist).

Fair enough :+1:


[Feature Request] absolutely minor: Swate names on top (Core vs. Experts)

Is your feature request related to a problem? Please describe.
When opening both Swate versions in parallel the tabs in the sidebar are both called "Swate".
Describe the solution you'd like
Name the sidebar tabs "Swate Core" and "Swate Experts"

We updated the Swate installation, which will propably fix this issue. Currently only the windows installer is finished but the mac version is in work!


Added installation instructions for Scoop

This PR adds installation instructions for using Scoop on Windows (https://github.com/ScoopInstaller/Main/pull/4231) which should make it nice and easy for anyone on a Windows machine to use this.

@jwillker Scoop keeps the package version up to date by watching the GH releases.

On Windows, you would do "go install" as well. I am not sure of community acceptance of Scoop and why we need to introduce this layer of complexity when "go install" is the standard for installing go packages.

@inferno-chromium that makes the assumption that all end users are expected to have the Go toolchain installed?
Scoop is pretty widely adopted for portable binaries; it adds zero additional complexity for projects and keeps versions up to date. I think it's worth adding to the README as osv-scanner is already available on Scoop.
I've generally found that the more ways there are to install binaries the better the adoption; and package managers which allow versions to be kept up to date are a good thing.

@inferno-chromium that makes the assumption that all end users are expected to have the Go toolchain installed?
Scoop is pretty widely adopted for portable binaries; it adds zero additional complexity for projects and keeps versions up to date. I think it's worth adding to the README as osv-scanner is already available on Scoop.
I've generally found that the more ways there are to install binaries the better the adoption; and package managers which allow versions to be kept up to date are a good thing.

Make sense. I would let @oliverchang @another-rex come back from vacation to comment here. This seems fine, i think you should move it after source section, in a dedicated "Install from package manager section" and underneath it, give bullet point on Scoop. We will be adding more package manager ways soon, so it makes sense there.

@inferno-chromium as the primary installation method in the current README is to downloading the binaries from the releases page wouldn't the package manager options logically follow next with installation from source remaining last?

/gcbrun


fix failing yapf test

https://travis-ci.org/ForensicArtifacts/artifacts/jobs/328929298
likely cause, changes due to new version of yapf

[x] update yapf in GIFT PPA
[x] update yapf in l2tbinaries for win32, win64
[ ] update yapf in l2tbinaries for macos
[ ] updated source https://codereview.appspot.com/339380043/

https://github.com/ForensicArtifacts/artifacts/pull/254

issue with packaged version of yapf https://codereview.appspot.com/339380043/ and newer version of yapf formatting the source differently.

Removed yapf for now, seeing the test was flaky


Mods with option group types "Multi" and "MultiRequired" only have a single option merged, even if multiple are selected

Fixed in https://github.com/TKMM-Team/Tkmm/commit/1062bb6f869a58912ea5f89a633e445227be56c8


EPL-2.0 license

The version 2.0 of the license was  announced in August 2017, and is the version proposed by the GitHub UI when adding a license to a repository. We should still keep version 1.0 as well, as a lot of projects probably haven't yet migrated.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @PyvesB!

  Generated by :no_entry_sign: dangerJS against 996d5fbb4daeb5cc19a2f1dd729fee94825bd9c8


chore(react, rollup, webpack): bump samples to 4.23

Updated deps with ncu -u
Installed @arcgis/core@next
Tested with npm start and the dist from npm run build
Bumped the CDN and npm package to 4.23

LGTM, thanks!


Deploy a CAP Business Application to BTP: The plan hdi-shared could not be found for service hanatrial

Tutorials: https://developers.sap.com/tutorials/cap-service-deploy.html
In Step 3: Deploy using cf push
when I run:
cf create-service hanatrial hdi-shared my-bookshop-db

then I get the error:

Creating service instance my-bookshop-db in org XXXXXXtrial / space dev as<EMAIL_ADDRESS>The plan hdi-shared could not be found for service hanatrial.
FAILED

I would suggest to update the Tutorial so that it contains the current service plan that should be used.

Hint
When I run:

cf marketplace | grep hana

then I get the following service plans:

hana (hdi-shared, sbss, schema, securestore) Manage schemas and HDI containers on an existing SAP HANA database.
hanatrial (securestore) Manage Schemas and HDI Containers on a shared SAP HANA database
hana-cloud-trial (hana, relational-data-lake, hana-cloud-connection) Leverage the in-memory data processing capabilities of SAP HANA in the cloud as one simple gateway to all data.

Hi @PierreFritsch,
Which version of @sap/cds-dk and Node.js are you using? Can you please provide the output of cds -v?
Thanks a lot and best regards,
Iwona

Hi @iwonahahn
Not sure how relevant this is, but here you go:
my-bookshop % node -v
v14.16.1
my-bookshop % cds -v
@sap/cds: 5.0.6
@sap/cds-compiler: 2.1.6
@sap/cds-dk: 4.0.7
@sap/cds-foss: 2.3.0
@sap/cds-runtime: 3.0.9
Node.js: v14.16.1
home: /Users/XXXXXX/Desktop/my-bookshop/node_modules/@sap/cds
my-bookshop: 1.0.0

Probably more interesting:
my-bookshop % cf api
API endpoint:   https://api.cf.eu10.hana.ondemand.com
API version:    3.97.0

Cheers
Pierre

... to connect the dots:
For me, the following command does the trick:
 cf create-service hanatrial securestore my-bookshop-db

Hi @PierreFritsch.
Currently, I'm also getting the same error when I deploy the MTA project.
In my BTP trial account, service SAP HANA Schemas and HDI Containers trial not contain plan hdi-shared.
Did you resolve this error? If yes, could you please share the steps to resolve the issue?
Thanks.

Hi @PierreFritsch,
Sorry for the late reply. I will test it with the latest CAP release and discuss it with the development colleagues and will get back to you latest next Monday (due public holiday in Germany).
Best regards,
Iwona

Hi @PierreFritsch,
the service SAP HANA Schemas & HDI Containers Trial (hanatrial) was removed for newly created trial accounts. You now need to use the trial service on SAP HANA Cloud (hana-cloud-trial) to deploy your application. To avoid confusion we will update the tutorial asap.
Best regards,
Iwona

Hi @PierreFritsch,
the service SAP HANA Schemas & HDI Containers Trial (hanatrial) was removed for newly created trial accounts. You now need to use the trial service on SAP HANA Cloud (hana-cloud-trial) to deploy your application. To avoid confusion we will update the tutorial asap.
Best regards,
Iwona

Hi @PierreFritsch,
the service SAP HANA Schemas & HDI Containers Trial (hanatrial) was removed for newly created trial accounts. You now need to use the trial service on SAP HANA Cloud (hana-cloud-trial) to deploy your application. To avoid confusion we will update the tutorial asap.
Best regards,
Iwona

Hi @PierreFritsch,
I have tested it with a newly created trial subaccount and you are right. For the service SAP HANA Schemas & HDI Containers Trial the plan securestore can be used. It works with cf create-service hanatrial securestore my-bookshop-db in step 3.1. I have updated the tutorial today. Thank you for reporting and testing it :).
@minionbee: In step 3.1 try
cf create-service hanatrial securestore my-bookshop-db
instead of
cf create-service hanatrial hdi-shared my-bookshop-db
This should work.
Best regards,
Iwona


[Python] Add device param to HuggingFacePipelineModelHandler

Fixes #29218

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

CC: @damccorm @kerrydc

Btw pytorch model handlers use CPU as default. It would be good to make that default GPU as well since we are moving in that direction.

Tests are done.. failing test seems to be a timeout issue not related to this PR


Update int types to support 32bit arch builds

This PR fixes issue #10

@afedotov Thank you for your contribution!


All members with edit rights should receive congratulatory email (wishlist feature enhancement)

I created the Apparmor  project on the Best Practices Badge site. I added members of the Apparmor development team to the project's badge application on the site. One of the other team members fixed up the Apparmor documentation and updated the questionnaire to push Apparmor over the line to achieve the passing badge. Unfortunately, I was the only person to receive the Congratulatory email.
Wishlist feature enhancement: send the Congratulatory email to the whole team.

First of all, congratulations. We were very excited to see that passing badge as well.
I like this idea, but how would we know who the team is? If we let random people set an email address for congratulatory messages, I am concerned that the badge application could become a spammer, which we don't want.

In the case where we have additional rights, this would be easy. However it is extremely rare to have additional rights information. We could try to query the repository if it is a GitHub repository and see if we can figure out who the main contributors are, and then see if there's a corresponding user entry in our database.  I'm not sure that would work. I'm not even certain we should, because we really want to maintain people's privacy, and it is not clear that just because they're on a project that they would want the email. But maybe I'm overthinking this, presumably creating an account on the badging application suggests a willingness to receive emails related to badges.

I love the goal, but can't see how to get there. I don't see how we can do this in a useful way without becoming a spammer.  There's no guarantee the other GitHub participants want the emails, and there are so few people in the "AdditionalRights" table that adding the code doesn't seem worth the trouble.
I'm closing for now.  If someone has an idea on how we could do this, let's reopen it or create a new issue.


Mat 5739 link timing element

MADiE PR
Jira Ticket: MAT-5739
(Optional) Related Tickets:
Summary
All Submissions

[x] This PR has the JIRA linked.
[x] Required tests are included
[x] No extemporaneous files are included (i.e Complied files or testing results)
[x] This PR is into the correct branch.
[ ] All Documentation as needed for this PR is Complete (or noted in a TODO or other Ticket)
[ ] Any breaking changes or failing automation are noted by placing a comment on this PR.

DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.

[x] This PR has NO significant security impact (i.e Changing auth methods, Adding a new user type, Adding a required but vulnerable package)
[ ] All CDN/Web dependencies are hosted internally (i.e MADiE-Root Repo)

Reviewers
By Approving this PR you are attesting to the following:

Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
The tests appropriately test the new code, including edge cases
If you have any concerns they are brought up either to the developer assigned, security engineer, or leads

Closing this PR, replaced by the new PR: https://github.com/MeasureAuthoringTool/madie-patient/pull/340


Update .NET 8.0 & packages

@theo-blis please check while you are working on extracting PO, I just updated to .NET 8

@hishamco I didn't want to push you to upgrade ;-) I ran the same test and it still produces the same results. So all is good!

Believe it or not when I created the latest fix I thought to remove it and then allow ignored projects as parameters, please file an issue for easy tracking. I know I might forget this if it's not logged :)

See #83


Fix PT006 autofix of parametrize name strings like '   first, ,  second  '

pytest trims and ignores empty names.
Previously the autofix would be to ('   first', ' ', '    second  ').
Now it's ('first', 'second').

\cc @edgarrmondragon - do you mind taking a quick look whenever you can?


Strict types validation (fix #48)

Resolves #48
Validation is now strict, but query, path and cookie params (that are always strings) attempted to convert to specified type.

Althougth the proposal itself looks valid I suggest to add more tests on HTTP related stuff. Because the problem I see the that, for example, path and query parameters are always strings by the nature of HTTP and how PHP process it. So considering any "number string" or "boolean string" to be string will break these things

Thank you for quick reply
I have implemented deserialization for headers (including multipart POST) and cookies, but not yet for urlencoded post params. There would be significant amount of duplication between QueryArgumentsValidator and yet not existing BodyArgumentsValidator. Also there is similar code in RequestCookieValidator and HeaderValidator. May be a some new class should be introduced, taking array of specs and array of string values?

There would be significant amount of duplication

Well, we have two ways, get working code with duplications to discuss refactoring or just skip this step if you have a plan already in your mind how it should look like

I have implemented deserialization also for POST parameters and added some tests.
If I understand correctly, SerializedParameter now can be also used to deserialize objects in different styles, as mentioned in #2

Actually I think I can fix it by myself

Thanks @m0003r, sorry for long review

@scaytrase Thanks for the great library. I also have thoughts about XML validation (https://swagger.io/docs/specification/data-models/representing-xml/), maybe there will be another pull request sometime in the future :)

Feel free to ping me if I forget to view it


Post-processing error in some Teukolsky runs

When running with the following config file (see below), the following line in bayRing.py produces an error:
os.system('mv {dir}/Algorithm/nschain*.pdf {dir}/Plots/Chains/.'.format(dir = parameters['I/O']['outdir']))

So far I created a branch and commented it out, and everything runs correctly. I believe raynest does not produce the nschain.pdf files, so probably this line should be turned into a try: ... except: ... statement.
This is my config file:
[I/O]

outdir=/does/not/matter
screen-output = 0

[NR-data]

dir=/some/directory/
catalog    = Teukolsky
ID=a_0.2_A_0.0141_w_1.0_ingoing
error      = resolution
res-level=3
pert-order=lin
l-NR=2
m=2

[Injection-data]

[Model]

template=Kerr
QNM-modes=220
QQNM-modes=None
N-DS-modes=1

[Inference]

nlive=64
maxmcmc=128
t-start=0.0
t-end=125.0
dt-scd=18.3402
sampler = raynest
nnest=4
nensemble=8

[Priors]

Fixed here.


orders display < 10

In the admin panel under the Order section, only 10 orders are displayed, Can not access old orders.
The same goes for products.

Fixed in a7a1fadae6e37e5c264549e74d9a8d43dd6dd2bd


Tweak LICENSE file to make it detectable by GitHub

Remove the indention of conditions, so that GitHub can detect it is BSD license.

weird. It seems it's not because the indention that makes GitHub can't detect the license.

Not sure. It detects Flask's, try comparing the two.


Disable name and display name when editing organization

Part 1 of 2 Draft for https://ucsc-cgl.atlassian.net/browse/SEAB-203
The idea is we disable all normal users from editing the approved organization name and display name. In the kind of unlikely case where they want to do so, they'll need to contact Dockstore (us). We would use the exact same endpoint (PUT) in the swagger-ui.
Other PR https://github.com/dockstore/dockstore/pull/3815
Disabled Material input looks like:

Does the tooltip display? I thought there had been an issue where tooltips don't display for disabled controls.
Would be nice for admins and curators to be able to change from the UI; less likely to make a mistake IMHO.

It did have a problem, I had to put the tooltip on the form control instead of input

Not a draft PR anymore, re-requesting review


Update supported_models.md

Aligning model name with excisting schema.

You have to edit the model_schema.json file.
This supported_models.md is auto generated by a github action script, by reading all the existing model_schema.json files.

On a related note. Would it be a good idea to have consistent naming in the docs and in the measuring script to guide users to use the correct terminology? That is, using model id and model name in both places?

On a related note. Would it be a good idea to have consistent naming in the docs and in the measuring script to guide users to use the correct terminology? That is, using model id and model name in both places?

Yes would be a good idea, I am all in for making things as clear as possible.
You may also change that in your PR if you'd like

You have to edit the model_schema.json file.
This supported_models.md is auto generated by a github action script, by reading all the existing model_schema.json files.

Is this a global file or per device file?

Sorry I mean model.json. in each directory is a file


Add nix flake to support building with Nix

Hello!
This PR introduces a nix flake to support people wanting to build this project via Nix.
Notable features are:

Flake for building go and Python
devShell for running the Makefile
CI job to test that the tests run in the devShell
Readme updates describing Nix tooling
Minor changes to accomodate package building via Nix

Perhaps the most controversial change is the last one. The main change is commit the pyproject.toml file so that the Python packaging process can pick it up. It might be possible to not do this; but given that there are other locations where the version is hard-coded in the source (which I think is fine) it didn't seem like too big a crime.
Let me know what you make of it!
Note that I've gone to some effort to maintain backwards compatibility; i.e. this does not break building the project for anyone not using Nix; and indeed the main Makefile is still the preferred way to build. But it does open-up the path for more nixification; and enables nix people to hack on the codebase :)
Trivia/Open questions:

There is a bit of a quirk with the git describe --tags way of getting versions and I'm not 100% sure the CI will work the first time here. On my fork, I had to explicitly override (😱 😱 😱) the v0.0.4 tag; but I think it's a quirk with how Github checks out the repository; I'm 🙏🏻 ing that it will "Just Work" when the Github action runs here on the main repo. But I'll be curious to see.
I realise also that there is cloudbuild.yaml defining CI workflows as well; but perhaps one could move the Nix check there instead; but it doesn't seem terrible to run it via Github Actions. I'm open to ideas here.

I "fixed" the version issue in pyproject.toml; but it comes at a moderate cost.
In investigating it, I realise now that there is something a bit odd in how b6-api reports the version. Note that the version is computed by running git. So it would seem that this will depend on the directory that this command is invoked from? I actually at this point can't quite understand how it even works. I do get different results:
b6 (add-nix +) > ./bin/linux/x86_64/b6-api --version
0.0.5-a.655.ga4cee54
b6 (add-nix +) > cd ..
diagonal> ./b6/bin/linux/x86_64/b6-api --version
0.0.4

Not quite sure what to make of that! Appreciate any insight :)

I suppose the main difference is that when the Makefile builds the pyproject.toml, the version in there is the one from the current revision in the git repo; i.e.
version = "0.0.5a655+ga4cee54"

but the Nix build doen't run b6-api in any git repo; so the version there is 0.0.4.
This isn't a big deal for the time being (given that the nix python build isn't even used directly yet) but is worth noting.

I added a couple of commits to now also build the docker image via Nix.
I haven't tested it extensively, but it seems to do the right thing now, and brings in all the dependencies in a nice way. I had to make a couple of changes to the source; but nothing too controversial I hope (i.e. nothing breaking).

Last commit makes a few code changes to standardise the way test-data is loaded, and default to looking up the go.mod file to find the root directory from which to load tests.
Again, these changes shouldn't break any "normal" go building/testing, but just make it compatible with Nix :)


[GSSOC 2023] Incomplete README Content and Updated Script of CPU TEMPERATURE

The README file for the project currently contains incomplete information, which makes it difficult for other users to understand and use the CPU temperature retrieval script. The previous version of the README lacked important sections such as Prerequisites, Explanation of the Script, Setup Instructions, Output, Compatibility, Contributing, and License.
In addition to the incomplete README, the assistant provided an updated script in the previous interaction, which is missing from the repository. The updated script includes improvements such as better code organization and enhanced error handling.
This issue is raised to request the completion of the README file by adding the missing sections with the relevant information and to include the updated script in the repository. By doing so, it will provide clear instructions, improve the usability of the script, and ensure consistency between the README and the code.
@avinashkranjan  pls assign this issue to me

@avinashkranjan  may you review and check this issue pls

Go Ahead @slayerrr12 , Assigned it to you.


Fix createTrajectoryMessage

@rhaschke The reason this is needed is because the last point in the trajectory is not sampled when the frequency doesn't perfectly align with the trajectory length. For example, if we have a trajectory over the time interval [0, 0.9999] and a frequency of 2 Hz, we want 3 total time points: (0, 0.5, 0.9999). The current version would calculate n_samples=2 and the generated time points would be (0.0, 0.5).
This issue becomes evident when controlling a robot with velocity command interfaces. The trajectories generated are intended to end with zero velocity, but they do not due to the aforementioned issue.
I can see how this change can be implemented in a more concise way to minimize confusion. It may be better to round static_cast<int>(trajectory.getDuration() / time_step) to the nearest whole number to handle the case I mentioned.

I've done this same math recently on moveit_drake and @pac48 's fix looks correct.
https://github.com/moveit/moveit_drake/blob/154e32b8804d240606bc10d56d13a870bb8c43b7/src/ktopt_planning_context.cpp#L185

Regardless of whether or not it's a correct fix, PRs without a proper motivation should really not be approved 1 minute after they are submitted.
It's clear you are in the same company, so likely discussed this approach and both were OK with it, but that's not the point.
MoveIt is still an OSS project as far as we know -- well, these parts are anyway -- so let's try to adhere to the agreed upon workflow.


roboto_medium on windows?

Noob question but I followed doc, copied fonts in native-base\Fonts

and installed Roboto fonts on Windows but I still get error in expo XDE (and device, red screen) when connected to Android 5.1.1 device:
fontFamily 'Roboto_medium' is not a system font and has not been loaded through Exponent.Font.loadAsync.
I needed to adapt async function to EC6 to please Expo XDE, so here's my async load:
async () => {
await Expo.Font.loadAsync({
    'Roboto': require('native-base/Fonts/Roboto.ttf'),
    'Roboto_medium': require('native-base/Fonts/Roboto_medium.ttf'),
  });
}

@j2l Try this at the root level of your appasync componentWillMount() {     await Expo.Font.loadAsync({       Roboto: require('native-base/Fonts/Roboto.ttf'),       Roboto_medium: require('native-base/Fonts/Roboto_medium.ttf'),     });   }

Thanks, but I tried that, it throws an error about missing "=>"

@j2l Then you can raise an issue about this in Expo github repo. As the requirement with NativeBase is to have the Font but loading custom font is something which Expo handles

reading https://github.com/expo/shoutem-example/blob/master/main.js
I see async must be INSIDE the class, it was outside.
May be this is it?


Feature to specify the security group name

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

No 🛑: please wait to file a request until the functionality is available in the AWS provider
Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

I am trying to import an already existing RDS cluster, and I have an attached security group that is not the same as the name of the cluster and also not null. Setting security_group_use_name_prefix to true recreates the security group because of the name_prefix and setting it to false recreates the security group because of the name.
Describe the solution you'd like.

I want to be able to manually specify the security group name for the SG created by this module.
Describe alternatives you've considered.

For now, I am going with the resolution of setting create_security_group to false and creating a separate SG to attach to the RDS.
Additional context

I would suggest either not letting the module create the security group or let the module create the security group and transfer the rules over from the existing security group to the new one (you can have multiple security groups with the same rules to support the transition without interruption)


Fix root prefix init

Since micromamba 1.4.5, https://github.com/mamba-org/mamba/issues/2442 is solved.

This means we can't use old versions of Mamba though

We could still use versions < 1.4.5 but only with init-shell: none.

But yes, before we release this version we should probably add a warning or something like that...

It is a breaking change so warrants a major version update. Or we could make the code backwards compatible.


Build tests

Create a file tests.js in app/static/
Add in index.html only when django.settings.debug=True
Run with window.test.test()

Consider using: https://seleniumbase.com/


regression: SyncLimiter was removed

Right now the latest commit doesn't have SyncLimiter, which requires manually creating a thread for run. Is there a reason why this API was tossed?
Additionally, Handle should use an AtomicUsize and take self for methods, to be thread-safe.

Hi @clarcharr - please see #25 - the SyncLimiter appeared to not enforce any ratelimit. I spent some cycles trying to debug as part of #24 before realizing these as separate issues.
I tried to retain as much of the new API as possible while getting master back to a working state.
For the issue with Handle thread-safety - can you open a new issue elaborating?

okay! I may actually just make a PR for it because I know what to do

Thanks! PR would be welcome!
On Sun, Jul 23, 2017, 2:19 PM Clar Roʒe<EMAIL_ADDRESS>wrote:

okay! I may actually just make a PR for it because I know what to do
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/brayniac/ratelimit/issues/27#issuecomment-317283028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ_jl-aavEmn0rd774122FFx6cGY-nukks5sQ7jjgaJpZM4OgjdF
.


ported to harp

You can use Harp Hook to publish to gh-pages.
site:
http://iceddev.2013.nodeknockout.com/
video:
https://www.youtube.com/watch?v=AXuc6Z17dN8

@sintaxi i gave this a shot this weekend. while i'd love to move off of jekyll, especially after using harp (harp is way faster), i just can't get this to work seamlessly with github pages. the compilation step gives me problems, and debugging them is pretty hard :/

after 5 years im gonna shut this one down... im actually very happy with jekyll and my automated deployment pipeline as-is.


Error in ./upgradeCC.sh 0.2 2 -n 1, from 1 org, after ./startDev.sh -n 1.

Attached are the steps that indicate an error in ./upgradeCC.sh 0.2 2 -n 1, from 1 org, after ./startDev.sh -n 1.
Docker cleanup and start

docker ps

error pointed out:

Fixed on #69


Slightly better description of Bintray usage

@jbaruch Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Return an error when the parsing has failed

Hi maintainers! I encountered an issue while using this library, and tried to fix it.
I'm sorry if this PR doesn't follow some rules, as I'm very new to contribute to OSSes.
Please notify me if there's any missing information 🙏
Thank you!

Currently, probe_from_paths returns empty Version (i.e., 0.0.0) when it fails to guess the OpenCV version from header files.
It causes an "Unsupported OpenCV version" error.
I saw the error because the function could not find version.hpp at the expected location.
The root cause was the misconfiguration of include paths.
Instead, it will be more user-friendly if it explicitly reports an error.

Thanks a lot!

Thank you for merging! 🙏


WIP: Error if disk is already attached

This change addresses #280. If a disk is already attached to another VM, the attack disk will not attempt to attach it to another VM.

[ ] Add integration test

@BeckerMax if the disk is attached to the VM we'll not ask the GCE APIs to attach it again. Do you know if we should still ask the BOSH agent to do its work?

@evandbrown I checked the openstack cpi and we do update the registry in the case of attaching a disk that is already attached. So we let the agent do what you referenced.
In the end I do not think that this is necessary. I assume that the same data that is already in the registry will be written again.

Thanks, @BeckerMax. Reworked a few things to support agent re-attachment if the disk is already attached to the VM. Also, tests+int tests.


Path of browser not changed

Tested versions
v4.4.dev.mono.gh[1c7d7fa8d]
System information
Windows 10 - v4.4.dev.mono.gh[1c7d7fa8d]
Issue description
I can't change the path with typing.
I try to change directory with writing path. But after enter typing true path not applyied in this version.
This issue was not on godot 4.3 stable
Steps to reproduce

Minimal reproduction project (MRP)
Thanks.

Dumb question do you press enter?

Note: This issue is not occurring in Linux v4.4.alpha.custom_build [7894cd1a5].

I cannot replicate this for v4.4.dev.custom_build [5e7e5fc60]

Dumb question do you press enter?

Note: This issue is not occurring in Linux v4.4.alpha.custom_build [7894cd1].

Yes my friend. You can check that. I try to show you in gif. This was worked really well on godot engine 4.3 I hope this issue fix in the future.

Check if it also occurs in Godot 4.4dev please, this issue also sounds like one we inherited.

Dumb question do you press enter?

Note: This issue is not occurring in Linux v4.4.alpha.custom_build [7894cd1].

Yes my friend. You can check that. I try to show you in gif. This was worked really well on godot engine 4.3 I hope this issue fix in the future.

Check if it also occurs in Godot 4.4dev please, this issue also sounds like one we inherited.

Yes, I tried it now. This problem also exists in the latest version of "Godot Engine" (Godot_v4.4-dev3_mono_official [f4af8201b] win_64).

Dumb question do you press enter?

Note: This issue is not occurring in Linux v4.4.alpha.custom_build [7894cd1].

Yes my friend. You can check that. I try to show you in gif. This was worked really well on godot engine 4.3 I hope this issue fix in the future.

Check if it also occurs in Godot 4.4dev please, this issue also sounds like one we inherited.

Yes, I tried it now. This problem also exists in the latest version of "Godot Engine" (Godot_v4.4-dev3_mono_official [f4af820] win_64).

Alright, thanks for the leg work. This pretty much guarantees that it is a bug caused by their work upstream on Godot 4.4dev and means we simply have to wait for them to fix it as well. Unfortunate, but that is the reality. Standby for a stable 4.3 build from us!

I don't think the bug necessarily needs to be closed, just linked to the Godot issue.


Jquery datepicker

Not sure if this is an issue with phantom or jquery but whenever phantom runs into the $.datepicker() the action is terminated with no warnings or errors.

Please upgrade to PhantomJS 2. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2 version.


tests: add ipv6 evasion tests

This is a complete but WIP batch of suricata-verify tests for the ipv6 evasion issue https://redmine.openinfosecfoundation.org/issues/3323.
The ones without rules are skipped.
Some of the ones that trigger, trigger just the IPv6 checksum rule which is not detecting the actual attack.

Please rebase.

@norg, would you have time to revisit this now that most (all?) of these tests are merged ?

@catenacyber the ones that were merged look good, should we close this? since the ones left are mentioned by you in redmine as "todo"


add checks if data is accessible

Hello, I've encountered the following issue:
Whenever im pressing step_over() really fast, I get the following error message:
Rendering failed: ...re/nvim/lazy/nvim-dap-ui/lua/dapui/components/frames.lua:28: attempt to index field 'session' (a nil value)
stack traceback:
        ...io/.local/share/nvim/lazy/nvim-dap-ui/lua/dapui/util.lua:17: in function '__index'
        ...re/nvim/lazy/nvim-dap-ui/lua/dapui/components/frames.lua:28: in function 'render'
        ...e/nvim/lazy/nvim-dap-ui/lua/dapui/components/threads.lua:45: in function 'render_thread'
        ...e/nvim/lazy/nvim-dap-ui/lua/dapui/components/threads.lua:68: in function 'render'
        ...hare/nvim/lazy/nvim-dap-ui/lua/dapui/elements/stacks.lua:27: in function 'render'
        ...hare/nvim/lazy/nvim-dap-ui/lua/dapui/elements/stacks.lua:19: in function <...hare/nvim/lazy/nvim-dap-ui/lua/dapui/elements/stacks.lua:18>
        [C]: in function 'xpcall'
        ...io/.local/share/nvim/lazy/nvim-dap-ui/lua/dapui/util.lua:16: in function <...io/.local/share/nvim/lazy/nvim-dap-ui/lua/dapui/util.lua:12>

I've tried to fix this myself, without looking deep into the code, so if this does not work, hit me up with a different approach and I will change it accordingly.

Thanks for the PR! :smile:


Missing tags for 0.6.x releases

The repo doesn't have any tag for recent released versions, which and tools like Dependabot can't help describing what changed between one version to another

Bundler's docs suggest the gem-release to handle releases and it has gem tag gem bump -t to help with this

The CHANGELOG also only goes up to 0.5.16.


feat(batch): rename AsyncBatchProcessor to default BatchProcessor

Description of your changes
This PR renames AsyncBatchProcessor to BatchProcessor and BatchProcessor to BatchProcessorSync.

Related issues, RFCs

Issue number: closes #1677
Checklist

[ ] My changes meet the tenets criteria
[ ] I have performed a self-review of my own code
[ ] I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my change is effective and works
[ ] The PR title follows the conventional commit semantics

Breaking change checklist
Is it a breaking change?: NO

[ ] I have documented the migration process
[ ] I have added, implemented necessary warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Thanks for the work on this one!!


Override style not working

Hello, I did:
import { setCustomTextInput } from "react-native-global-props";
const customTextInputProps = {
  style: {
    //fontFamily: theme.fontFamily.regular,
    //color: theme.colors.text,

    backgroundColor: "#E0E7FF33",
    borderColor: "#E0E7FF",
    borderRadius: 5,
    borderWidth: 1,
    marginVertical: 5,
    paddingVertical: 7,
    paddingHorizontal: 18,
    fontSize: 14,
    fontFamily: theme.fontFamily.regular,
    //color: "red"
  }
};

setCustomTextInput(customTextInputProps);

If I write:
<TextInput value={code} />

The global styles are applied correctly
But if I try to override one property of the style for a particular TextInput, the global styles dissapear, for example writting:
<TextInput
   value={code}
   style={{color: "red"}}
/>

It only apply the red color, and the rest of the style is gone. No border, no padding, etc.
What I'm doing wrong?
If I do:
<TextInput
   value={code}
   style={[TextInput.defaultProps.style, {color: "red"}]}
/>

It worked as expected... But then... whats the point using this library?
Can you help me please?

This is normal operation. This package doesn't unite values.
The point is that the default values of the given component (in the current case TextInput) can be overwritten globally (so it is unnecessary to overwrite one by one), but it doesn't implement a unique logic.
So if you want to use globally the second version  ( {[TextInput.defaultProps.style, {color: "red"}]} ), then you have to create your own CustomTextInput component to achieve style integration. In many cases this package is useful ecxept when you have to write your own component.

Nop... what I want is to use a general style globally, achieved with:
<TextInput value={code} />

That worked perfectly, borders and padding and the rest of the styles are applied correctly.
But I only want to override the style for some inputs in some specific views (for example change color to red), but having the same borders, padding, and the rest of the "global" styles...
If I do:
<TextInput value={code} style={{color: "red"}} />

The global styles are gone, no border, no padding...
Is this the intended behavior?

No, that seems like a bug. It should merge the style props.

@backendbyyuto  found any solution ?
i have used this in other projects, worked fine !
but now in new project if i give style to components global props does not applies
if it is not applying then what is the point of it !

To anyone experiencing this issue, it seems this only happens when Hermes is enabled. it worked as expected when I disabled Hermes in the project.

Is there any plan to make it work with Hermes please ?

Can confirm @cinnamonpon
In my case, it happens only with Android app and when Hermes engine is enabled.
Any update about it? Is it possible to fix it?

I experienced same problem... I just wanted to use conditional merge, as before i did, but it didn't work,
it only changed to second style, just ignoring first prop list
is this only my mistake or bug? can anyone know this issue?
my code example is like below :
<Text style={([styles.markingText], isMarkingsVisible && {opacity: 0.5})}>


Confused by logic in example Step functions ChoiceRule

In the step function example:
https://github.com/awslabs/amazon-sagemaker-examples/blob/438429411541375b267110d833ab541cab768730/step-functions-data-science-sdk/hello_world_workflow/hello_world_workflow.ipynb#L434
first the variable is defined in a ChouiceRule which is already strange because I would expect the variable to depend only the previous step. Then both steps are chained workflow_definition=Chain([start_pass_state, choice_state]) which is also weird. So I can chain with any step not necessarily the start_pass_state as the ChoiceRule is defined specifically for start_pass_state which is confusing as I would expect the rule to work only on the output of the previous step without having to hardcode anything to which step we are referring to in ChoiceRule.

Hi,
You are right in that the choice state only accepts variables from the previous step. The variable you choose from your previous state's output must be specified in the variable field for the ChoiceRule.
In the case of the Step Functions Data Science Python SDK, we provide placeholders to aid users in passing dynamic values in a workflow, such as the output from a previous step. Here:
rule=ChoiceRule.BooleanEquals(variable=start_pass_state.output()["IsHelloWorldExample"], value=True)
the start_pass_state.output() provides this placeholder of the expected output from the start_pass_state. When we attempt to create the Workflow in the notebook like:
workflow_definition=Chain([start_pass_state, choice_state]

workflow = Workflow(
    name="MyWorkflow_v1234",
    definition=workflow_definition,
    role=workflow_execution_role
)

the Workflow creation step will validate that the placeholder referenced in choice_state is from the output of the start_pass_state. If that isn't the case, the workflow creation will fail.
In the case that you want the rule to work only on the output of the previous step without having to hardcode anything to which step we are referring to, you can use the $.<variableName> format as shown in an example in the Step Functions docs: https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-choice-state.html
For this notebook, the rule would then look like:
rule=ChoiceRule.BooleanEquals(variable=$["IsHelloWorldExample"], value=True) or
rule=ChoiceRule.BooleanEquals(variable=$.IsHelloWorldExample, value=True)
Thanks,
Vaib

thanks for the explanation.


New Italian Translation Progress

Maintainer List

@deblasis
@mattia-sanfilippo

For New Translators
To translate a page:

Check that no one else has claimed your page in the checklist and comments below.
Comment below with the name of the page you would like to translate. Please take only one page at a time.
Clone this repo, translate your page, and submit a pull request!

Before contributing, read the glossary and style guide (once they exist) to understand how to translate various technical and React-specific terms.
Please be prompt with your translations! If you find that you can't commit anymore, let the maintainers know so they can assign the page to someone else.
For Maintainers
When someone volunteers, edit this issue with the username of the volunteer, and with the PR. Ex:

[ ] Quick Start (@tesseralis) #12345

When PRs are merged, make sure to mark that page as completed!
Main Content
To do before releasing as an "official" translation. Please translate these pages first.
Note that each section has an index page, which needs to be translated too.
Learn React

[x] Quick Start (@mattia-sanfilippo) #423

[ ] Tutorial: Tic Tac Toe (@mattia-sanfilippo)
[x] Thinking in React (@SamuelePiazzesi) #421

[x] Installation (@Th3Wall) #422

[x] Start a New React Project (@webdiego) #419
[x] Add React to an Existing Project (@Th3Wall) #425
[x] Editor Setup https://github.com/reactjs/it.react.dev/pull/374
[x] React Developer Tools (@mattia-sanfilippo) #386

[ ] Describing the UI (@Ago95Dev)

[x] Your First Component (@eliamaino-fp) #420
[ ] Importing and Exporting Components (@eliamaino-fp)
[x] Writing Markup with JSX (@Ago95Dev) #424
[ ] JavaScript in JSX with Curly Braces
[ ] Passing Props to a Component
[ ] Conditional Rendering
[ ] Rendering Lists
[ ] Keeping Components Pure

[ ] Adding Interactivity

[ ] Responding to Events
[ ] State: A Component's Memory
[ ] Render and Commit
[ ] State as a Snapshot
[ ] Queueing a Series of State Updates
[ ] Updating Objects in State
[ ] Updating Arrays in State

[ ] Managing State

[ ] Reacting to Input with State
[ ] Choosing the State Structure
[ ] Sharing State Between Components
[ ] Preserving and Resetting State
[ ] Extracting State Logic into a Reducer
[ ] Passing Data Deeply with Context
[ ] Scaling Up with Reducer and Context

[ ] Escape Hatches

[ ] Referencing Values with Refs
[ ] Manipulating the DOM with Refs
[ ] Synchronizing with Effects
[ ] You Might Not Need an Effect
[ ] Lifecycle of Reactive Effects
[ ] Separating Events from Effects
[ ] Removing Effect Dependencies
[ ] Reusing Logic with Custom Hooks

API Reference

[ ] react: Hooks

[ ] useCallback
[ ] useContext
[ ] useDebugValue
[ ] useDeferredValue
[ ] useEffect
[ ] useId
[ ] useImperativeHandle
[ ] useInsertionEffect
[ ] useLayoutEffect
[ ] useMemo
[ ] useReducer
[ ] useRef
[ ] useState
[ ] useSyncExternalStore
[ ] useTransition

[ ] react: Components

[ ] <Fragment> (<>)
[ ] <Profiler>
[ ] <StrictMode>
[ ] <Suspense>

[ ] react: APIs

[ ] createContext
[ ] forwardRef
[ ] lazy
[ ] memo
[ ] startTransition

[ ] react-dom: Components

[ ] Common (e.g. <div>)
[ ] <input>
[ ] <option>
[ ] <progress>
[ ] <select>
[ ] <textarea>

[ ] react-dom: APIs

[ ] createPortal
[ ] flushSync
[ ] findDOMNode
[ ] hydrate
[ ] render
[ ] unmountComponentAtNode

[ ] react-dom/client: Client APIs

[ ] createRoot
[ ] hydrateRoot

[ ] react-dom/server: Server APIs

[ ] renderToNodeStream
[ ] renderToPipeableStream
[ ] renderToReadableStream
[ ] renderToStaticMarkup
[ ] renderToStaticNodeStream
[ ] renderToString

Navigation and UI
We suggest to leave most of the UI translation until the end. We plan to do some invasive changes to the website folder layout and components, so postponing this until your translation is almost complete would make it easier to merge the changes from our side later. It might make sense to translate the homepage above the fold early, but leave the rest for later. As individual pages get translated, you can change the page titles in the corresponding sidebar files. Finally, when you're translating the navigation, make sure to test both desktop and mobile layouts.

[x] Homepage (currently in HomeContent.js) (@deblasis) #417
[ ] Sidebars (currently in src/sidebar*.json)
[ ] Top-level navigation (currently in TopNav.tsx)

When You're Ready...
After everything above is translated, add your language to deployedLanguages in Seo.tsx of the original reactjs/react.dev repository.
Secondary Content
These API pages should ideally be translated too, but they're less urgent and can be done after the others:

[ ] Legacy React APIs

[ ] Children
[ ] cloneElement
[ ] Component
[ ] createElement
[ ] createFactory
[ ] createRef
[ ] isValidElement
[ ] PureComponent

Optional Content
These aren't the main translation targets, but if you'd like to do them, feel free to expand the list to include their subpages:

[ ] Community
[ ] Blog
[ ] Warnings

Thinking in React

Hey 👋  I'm translating "Quick start" :)

Hey 😀 I'm translating "Start a New React Project"

Hey! 👋🏼
I'm translating "Thinking in React"!

Hey! i'm translating "Thinking in React"

@Th3Wall the page seems already took by @SamuelePiazzesi

Hey! i'm translating "Thinking in React"

@Th3Wall the page seems to have already been taken by @SamuelePiazzesi

Oops, sorry @SamuelePiazzesi
I'm going to start from "Installation" page then. Thanks @webdiego 😃

Hello :) I'm translating "Your First Component"

@deblasis Is the current maintainer list up-to-date? If not, would you mind updating it in https://github.com/reactjs/translations.react.dev and removing any inactive members? Thank you!

@deblasis Is the current maintainer list up-to-date? If not, would you mind updating it in https://github.com/reactjs/translations.react.dev and removing any inactive members? Thank you!

@gaearon I have updated the maintainers list on https://github.com/reactjs/translations.react.dev and also this issue above to reflect the changes.

Hey! I have a PR already approved for the "Installation" page.
I would now pick "Add React to an Existing Project" page 😄

hey! it's me again. i can take the JavaScript in JSX with Curly Braces content :D

Hey 👋  I'm translating "Tutorial: Tic Tac Toe" :)

Hey! I'm now translating "Passing Props to a Component" 🙂

Hello! I can proceed to translate Rendering Lists content :)

Hey there! I can start with "Conditional Rendering" 😃

Hi there! I'm taking State: A Component's Memory 😃

Hi translators! 😄
While I wait for the reviews, I'm taking "Responding to Events"

Picking up State: A Component's Memory now 🙂

Hello! I'm translating "State as a Snapshot" :)

I'm going for Updating Objects in State

Hi! I'd love to translate Queueing a Series of State Updates, if nobody is already on it.

Hello everyone 👋🏼  If it's okay for you I would like to contribute by translating the "Updating Arrays in State" 's part

Hello! I'm translating "useId" :)

Hi there! I would like to contribute by translating Reacting to Input with State

Hello! I will go for the  Choosing the State Structure

Hi everyone 👋🏼 I'm taking Sharing State Between Components.

Hello! I'm taking  Preserving and Resetting State.

Hello once again! I'm taking "Extracting State Logic into a Reducer"

Hello! I'm taking "Managing State"

I'm going for Passing Data Deeply with Context 😃

Hello :) I'm taking API Reference -> Hooks ✌🏻

Hello :)
I would like to help you with the translation!

i want to take
Passing Data Deeply with Context

i want to take Passing Data Deeply with Context

Hi, @albim360 this content was already taken by @oxcened with this comment.
Please take another one.
However it seems that this repo is no longer maintained...

Hi guys, sorry for the "latitanza", lots going on, I'll update the repo with main, the translation progress with the corresponding owners and the PRs overall later tonight.
Thanks for your patience and for the nudge 🙏

is  Removing Effect Dependencies avaiable?

I'm takin API Reference -> Hooks -> useDebugValue

Hi guys, I'm translating Queueing a Series of State Updates

Can I translate You Might Not Need an Effect?

Can I translate You Might Not Need an Effect?

Sure! Thanks 🙂

Hi there! I would like to contribute by translating Reacting to Input with State

Hey guys, I can't translate this anymore, so could you remove me from the list? So someone else can translate it

Hi there! I would like to contribute by translating Reacting to Input with State

Hey guys, I can't translate this anymore, so could you remove me from the list? So someone else can translate it

@GiuliaBortone sure, thanks for letting us know!

Hi, me too Unfortunately Il giorno 27 feb 2024, alle ore 09:51, Mattia Sanfilippo @.***> ha scritto:
Hi there! I would like to contribute by translating Reacting to Input with State
Hey guys, I can't translate this anymore, so could you remove me from the list? So someone else can translate it
@GiuliaBortone sure, thanks for letting us know!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hi there, can I take "API Reference > react: Components"

Hi, I'd like to work on Scaling Up with Reducer and Context


Bug: Duplicated generating text from @module

Input
/**
 * The effection like Thanos snapping finger
 * @author imcuttle
 * @module snap-fade-away
 */
// ...

Output
/**
 * The effection like Thanos snapping finger
 * @author imcuttle
 * @module snap-fade-away
 */
declare module "snap-fade-away" { }

/**
 * The effection like Thanos snapping finger
 * @author imcuttle
 * @module snap-fade-away
 */
declare module "snap-fade-away" { }

Haven't seen this before, will take a look when I have some time. If you have time to debug and put in a PR that would be really helpful.

I ran into this issue today where I have the same function name exported in different modules. If there was a duplicate function name, the template would re-write the first definition a second time.
The solution for me was to add explicit module tags in those files to prevent duplicates from being generated. /** @module "@package/path/to/module" */
The quotes part brought up a second issue which I am investigating, but resolved the duplicate function definitions.


Cli config reading improvements

Coverage remained the same at 98.183% when pulling 84461347dc64616a8779536e8a00c8ebc5278780 on cli-config-reading-improvements into eedf439005d98a0e844fd449f4b07257c1e5e8df on master.

Coverage remained the same at 98.183% when pulling 84461347dc64616a8779536e8a00c8ebc5278780 on cli-config-reading-improvements into eedf439005d98a0e844fd449f4b07257c1e5e8df on master.


Does setting min_exposure per player no longer work?

I swear I've done this successfully many times before, but for whatever reason setting min_exposure does not seem to work at all now. I've tested with Site.DRAFTKINGS and Site.FANDUEL with Sport.FOOTBALL
Here's a snippet of my code:
player = optimizer.player_pool.get_player_by_name("Josh Allen")
print(player)
player.min_expossure = 0.5
lineups = list(optimizer.optimize(n=10,max_exposure=0.8))
It builds 10 lineups but Josh Allen is only in one of them.
The print(player) line returns "Josh Allen QB (BUF)", showing that it is finding the player successfully.
The max_exposure for the whole thing is working as no players are in lineups more than 8 times.
Am I not using this right or is there an issue somewhere?

For some reason it doesn't work
On Mon, Sep 23, 2024, 1:38 PM EdCarGoes @.***> wrote:

I swear I've done this successfully many times before, but for whatever
reason setting min_exposure does not seem to work at all now. I've tested
with Site.DRAFTKINGS and Site.FANDUEL with Sport.FOOTBALL
Here's a snippet of my code:
player = optimizer.player_pool.get_player_by_name("Josh Allen")
print(player)
player.min_expossure = 0.5
lineups = list(optimizer.optimize(n=10,max_exposure=0.8))
It builds 10 lineups but Josh Allen is only in one of them.
The print(player) line returns "Josh Allen QB (BUF)", showing that it is
finding the player successfully.
The max_exposure for the whole thing is working as no players are in
lineups more than 8 times.
Am I not using this right or is there an issue somewhere?
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/432, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7U6K7HEUBBLRVGWT4LZYBGX3AVCNFSM6AAAAABOWSGKP6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DGMRVG43TKNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

In the rule.py
Let’s break down potential issues in your MinExposureRule class and go over
the logic step by step to understand why it might not be working as
expected.
Possible Issues and Potential Fixes

Tracking of min_exposure_players:

You are using a dictionary self.min_exposure_players to track how many
lineups each player should be forced into based on their minimum exposure
(player.min_exposure). However, after each lineup result, you're
decrementing this count and deleting the player when the count reaches 0.
Issue: Deleting players from self.min_exposure_players can make the list of
constraints incomplete, especially if you need to apply the rule over
multiple iterations.
Fix: You might want to store the original exposure counts in a separate
structure and avoid deleting players. Instead, you can simply skip players
whose minimum exposure has already been met.
Example Fix:
def apply_for_iteration(self, solver, result):
if not self.min_exposure_players:
return
if result:
for player in result:
if player not in self.min_exposure_players:
continue
self.min_exposure_players[player] -= 1
# Skip players with zero remaining exposure instead of deleting
them
self._create_constraints(solver)

Inconsistent positions Handling:

In the constructor, you initialize self.positions using
get_positions_for_optimizer(). You are passing None as the second argument,
which may not be intended.
Issue: Depending on how get_positions_for_optimizer() behaves, passing None
might result in incomplete or incorrect positions being returned.
Fix: Ensure that the second argument is correctly passed or handled within
the function.
Example:
self.positions = get_positions_for_optimizer(optimizer.settings.positions,
context)

Incorrect Calculation of total_force:

The line that calculates total_force is complex, and there could be a
logical issue.
Issue: The expression total_force = sum(self.min_exposure_players[p] for p
in min_exposure_players) - total_for_positions * (remaining_lineups - 1)
might be leading to incorrect results. Specifically, the subtraction of
total_for_positions * (remaining_lineups - 1) may not always yield a valid
constraint value.
Fix: Simplify the calculation to ensure that it reflects the correct
remaining exposures relative to the number of remaining lineups.
Example Fix:
total_force = sum(self.min_exposure_players[p] for p in
min_exposure_players)
total_force = min(total_force, total_for_positions)  # Simplified to ensure
force is bounded

Handling of remaining_lineups:

Issue: The division ceil(total_force / remaining_lineups) can result in
unexpected constraints if the total_force is close to zero or if
remaining_lineups is incorrectly managed.
Fix: Make sure that remaining_lineups is always positive and that
total_force is correctly normalized for the remaining iterations.

Solver Constraints:

The way you're adding constraints to the solver could be problematic if the
calculation of total_force or variables is wrong.
Fix: Verify that the variables being passed to solver.add_constraint() are
correct and that the total_force is appropriately bounded for the solver.
Example of Simplified Constraint Creation:
def _create_constraints(self, solver: Solver) -> None:
remaining_lineups = self.context.remaining_lineups
for positions, total_for_positions in self.positions.items():
min_exposure_players = [p for p in self.min_exposure_players if
list_intersection(p.positions, positions)]
if not min_exposure_players:
continue
    # Calculate the remaining force to apply the constraint
    total_force = sum(self.min_exposure_players[p] for p in

min_exposure_players) - total_for_positions * (remaining_lineups - 1)
    if total_force > 0:
        variables = [self.players_dict[p] for p in min_exposure_players]
        total_force = min(total_force, ceil(total_force /

remaining_lineups))  # Normalizing the force
solver.add_constraint(variables, None, SolverSign.GTE,
total_force)
for player, total_lineups in self.min_exposure_players.items():
    if total_lineups >= remaining_lineups:
        solver.add_constraint([self.players_dict[player]], None,

SolverSign.EQ, 1)
Summary of the Main Fixes:

Avoid deleting players from self.min_exposure_players. Instead, keep
track of players' exposures but skip players whose minimum exposure is
already met.

Ensure correct handling of positions in the constructor. Make sure the
get_positions_for_optimizer function receives the correct arguments.

Simplify and validate the calculation of total_force. Make sure the
logic of this constraint is sound and that the force is being normalized
correctly.

Check solver constraints. Verify that the constraints being passed are
consistent with the logic and the solver's expectations.

Test the updated logic to see if it addresses the issue you’re facing. If
you need further assistance, feel free to share more details about the
specific problem you're encountering, such as error messages or unexpected
results.
On Tue, Sep 24, 2024, 12:50 AM joseph offen @.***> wrote:

For some reason it doesn't work
On Mon, Sep 23, 2024, 1:38 PM EdCarGoes @.***> wrote:

I swear I've done this successfully many times before, but for whatever
reason setting min_exposure does not seem to work at all now. I've tested
with Site.DRAFTKINGS and Site.FANDUEL with Sport.FOOTBALL
Here's a snippet of my code:
player = optimizer.player_pool.get_player_by_name("Josh Allen")
print(player)
player.min_expossure = 0.5
lineups = list(optimizer.optimize(n=10,max_exposure=0.8))
It builds 10 lineups but Josh Allen is only in one of them.
The print(player) line returns "Josh Allen QB (BUF)", showing that it is
finding the player successfully.
The max_exposure for the whole thing is working as no players are in
lineups more than 8 times.
Am I not using this right or is there an issue somewhere?
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/432, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7U6K7HEUBBLRVGWT4LZYBGX3AVCNFSM6AAAAABOWSGKP6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2DGMRVG43TKNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


How do I combine Synpress with other plugins? Getting errors about promises

Describe the bug
I've successfully set up the Cucumber + Cypress bundle and now trying make Cucumber + Synpress work in a similar way.
However, I'm getting this error:

tasksetupMetamask, Object{5}
CypressError
Cypress detected that you returned a promise from a command while also invoking one or more cy commands in that promise.
The command that returned the promise was:

cy.task()

The cy command you invoked inside the promise was:

cy.then()

Because Cypress commands are already promise-like, you don't need to wrap them or return your own promise.
Cypress will resolve your command with whatever the final Cypress command yields.
The reason this is an error instead of a warning is because Cypress internally queues commands serially whereas Promises execute as soon as they are invoked. Attempting to reconcile this would prevent Cypress from ever resolving. Learn more

Stack trace is not very helpful:
    at cy.<computed> [as then] (http://localhost:53096/__cypress/runner/cypress_runner.js:160660:72)
From Your Spec Code:
    at Context.eval (http://localhost:53096/__cypress/tests?p=cypress\support\e2e.ts:17093:21)

My guess is, something's wrong with my config:
import { addCucumberPreprocessorPlugin } from '@badeball/cypress-cucumber-preprocessor';
import createEsbuildPlugin from '@badeball/cypress-cucumber-preprocessor/esbuild';
import createBundler from '@bahmutov/cypress-esbuild-preprocessor';
import synpressPlugins from '@synthetixio/synpress/plugins';
import { defineConfig } from 'cypress';

export default defineConfig({
  video: false,
  e2e: {
    specPattern: ['cypress/e2e/*.feature'],
    supportFile: 'cypress/support/e2e.ts',
    testIsolation: true,
    async setupNodeEvents(
      on: Cypress.PluginEvents,
      config: Cypress.PluginConfigOptions
    ) {
      synpressPlugins(on, config);

      await addCucumberPreprocessorPlugin(on, config);

      on(
        'file:preprocessor',
        createBundler({
          plugins: [createEsbuildPlugin(config)],
        })
      );

      // Make sure to return the config object as it might have been modified by the plugin.
      return config;
    },
  },
});

More precisely, I suspect that I should combine synpressPlugins(on, config) and await addCucumberPreprocessorPlugin(on, config) in a way so that the second command is only called once the first one finishes. However, await doesn't help with that and generally I'm not sure how to combine them correctly. May be pass the rest as a callback to synpressPlugins as the second argument?
To Reproduce

Clone https://github.com/YakovL/synpress-cucumber,
Run npm init i,
Run npm run test (or just npx cypress open);
Run the only test (in Chrome).

Related repository
https://github.com/YakovL/synpress-cucumber
Expected behavior
The test should run.
Screenshots
The error message and the stack trace covers it all, none informative screenshots.
Desktop (please complete the following information):

OS: Windows 10 x64
Synpress version: 3.7.0

Additional context
#414 looks related

Right, so now that I've defeated several issues, the problem is boiled down to

the cypress run vs open issue;
I have to retest this, but it seems that unlike Cucumber cli, Cypress/Synpress doesn't suggest test boilerplates.

The first one is quite a problem, as it slows down the feedback loop (when writing tests) to an extent that I'd call it "breaks it".
I'll update the repo to make it work as I have it working locally now (haven't done yet).

 The following 2 issues ruin the workflow:

the broken watch mode (i.e. cypress open not working) means that the feedback loop for a change is several minutes, plus some of the info about errors is not available;
the reports don't include on which (Cucumber) step the test failed.

Combined with the fact that some failures are randomly reproduced/not reproduced due to timeouts (I'm dealing with a complex DApp with behavior quirks), I'm getting the following DX problems:

very slow feedback loop, plus Synpress makes it hard to do something in parallel as it grabs focus to its Chrome windows/tabs multiple times per test;
it gives really little info regarding where the error came from (step is unknown, debug info is not available since the window is closed on failure), and I have to put cy.pause() here and there trying to narrow down the issue (combine that with the random reproductivity to imagine the result).

I'll do my best to provide a minimal reproducible example, but for now I'm just outlining the problems and asking to prioritize #417. I'm also looking for a way not to close Cypress window once it fails: this would help determining the step on which the problem occured and do some in-place debugging (like in the watch mode).
PS @kasparkallas I don't really see any connection. Why you think so?

Ok, looks like putting
afterEach(function() {
  if (this.currentTest?.state === 'failed') {
	cy.pause();
  }
});

into a steps definition file is a working approach to beat the "not sure where the failure comes from" problem, as well as to access the sources by the stack trace). This helps a lot.

Another problem, a somewhat complicated one: https://github.com/cypress-io/cypress/issues/27437 – cy.visit fails when using Synpress and Cucumber on a page that uses Chatbase. I'll probably create a separate issue for this here (in Synpress repo) as well, since removing Synpress removes the issue

The reason is that synpress is/was using async/await inside the before hook.
My solution was to copy-paste-modify the original supports file and remove async-await:
before(() => {
  if (!Cypress.env('SKIP_METAMASK_SETUP')) {
    cy.setupMetamask();
  }
});

Thanks @MichalLytek, this cures the complain about a promise indeed, created a PR for this. There are other problems with watch mode though, I'll report those later.


feat(yadm): deprecate

Can you please provide examples of how to handle yadm files now ?

I don't use yadm.


Added warning about grid-accessibility for -f argument

Noted that in example -f /path/to/myfile, /path/to/myfile must be grid-accessible via ifdh.

Hang on - forgot the man page.

Okay - now it's good.
Closes #247


[DEVHAS-67] Add support for private git repos

This PR adds support for private Git repositories to HAS, for Component and ComponentDetectionQuery resources, by using SPI and scm-file-retriever.
Since SPI does not yet support Git clone operations, the token secret created from an SPIAccessTokenBinding resource needs to be passed in to the Component when using private Git repositories, as we need to retrieve the token from the secret.
To use a private Git repo with a Component resource:

Create an SPIAccessTokenBinding for the given Git repository
Create a Component resource for the Git repository, and specifying the Kubernetes secret created from the previous step (Spec.Source.GitSource.Secret)

To use a private Git repo with a ComponentDetectionQuery resource:

Create an SPIAccessTokenBinding for the given Git repository
Create a ComponentDetectionQuery resource for the Git repository, and specifying the Kubernetes secret created from the previous step (Spec.GitSource.Secret)

/test ?

Instructions on setting up SPI w/ HAS https://github.com/redhat-appstudio/application-service/blob/c79a43f53c1c2209c271111e3e7eecb7947bdd75/docs/private-git-repos.md

/retest


#22: fixed wrong types payload input events

Fixes #22
This PR fixed wrong types payload input events

LGTM. Please run yarn prettier:fix and update PR.

Done


Create LICENSE.md

Since the teams branch are not ready, this adds the MIT license.

That has a link to the teams page in it as a list of contributors. That will need changing to https://github.com/elementary/mvp/graphs/contributors

Fixed :-P

Okay, legality time:
Technically, all the code before now has remained the property of the author. They have expressly granted us license to use it, but not necessarily to sub-license it with MIT/GPL/etc.
Do we:
a) The Lawyer Way: Contact each author and get express consent from each of them, replacing any code where the request is declined.
b) The YouTube Way: Assume licensing is allowed until a complaint is filed directly with us.

I prefer the YouTube Way since the author is responsible for his/her code.


Add color prop for checkbox icon

fixes #372

So, I know the AC in the ticket said "regardless of the variant and checkbox color" but I don't think that makes sense when actually trying it (see screenshot from codesandbox)

I would think the color prop would just change the general color of the checkbox (in this case where the green is), and we should be able to override the checkbox color separately

Being able to control both would give us ultimate control
https://user-images.githubusercontent.com/7891559/162487773-bf5ba8f9-1543-4a5f-b1cd-518e0967de92.mp4


Add the possibility to set a list of users to listen to

This fixes issue #2 while extending it to specify multiple users.
Previous functionality is kept if no user(s) is(are) specified.

The suggested changes have been integrated.
However, the merge of v2 in the branch looks quite a bit dirty. If you want, i can close this pr & reopen a cleaner one?

@Jenkyrados Sorry, I went on vacation 😆 Maybe try rebasing it on current master and pushing again? It looks like the PR here picked up a lot of existing changes…

Fixed!
Interesting that force pushing actually doesn't break the PR - good to know :D

I wish I had the bandwidth to make this a tighter feedback loop. I realize this is kind of slow and can be frustrating.
I gave this feature a spin locally. It seemed to filter my own username correctly but not my test account from another instance.
I feel like I need debug flag support so we can trace a few things, e.g. progress hooks and user matching. I have a half-finished branch with that that's not currently working, but can be with a little bit of effort.
So let me get that looked at when I have an opportunity, and then we'll get this in. I really appreciate the effort you've put in!


[dart2wasm] Consider using symbols in function type representations

Currently in dart2wasm, runtime types of functions are represented as:
class _FunctionType extends _Type {
  final int typeParameterOffset;
  final List<_Type> typeParameterBounds;
  final _Type returnType;
  final List<_Type> positionalParameters;
  final int requiredParameterCount;
  final List<_NamedParameter> namedParameters;
  ...
}

class _NamedParameter {
  final String name;
  final _Type type;
  final bool isRequired;
  ...
}

Here the name field can be made Symbol to allow using identical when comparing passed named arguments with the expected named parameters, in Function.apply and dynamic invocations.
However I think doing that will make some operations slower. For example, when checking t <: s when both types are function types, we scan sorted named parameter lists in parallel, and if we see a name in t that is larger than the next name in s (according to compareTo), that means t has an extra named parameter and is not a subtype. (this happens in _TypeUniverse.isFunctionSubtype)
The same kind of check is done in the shape check shown in https://github.com/dart-lang/sdk/issues/50661#issuecomment-1368786674.
We could use Symbol.toString, but that demangles the symbol and allocates a new string.
So we have a few options:

Keep using String: Function.apply and dynamic invocations will use string comparison even in the fast path (when all expected parameters are passed). Slow path will not do any extra string comparisons.

Use Symbol: Function.apply and dynamic invocations will need to intern/canonicalize Symbols in passed named arguments so that identical will work. The fast paths will use identical. When identical test fails, we will need to convert Symbols to Strings and do string comparisons.

Have both a String and a Symbol field for the name: shape and type checks will be as fast as possible (no string comparison in the fast path, no demangling in the slow path), but named arguments in Function.apply and dynamic invocations need to be canonicalized.

Comparing all options, I feel like using String is actually fine.
Any thoughts @askeksa-google?

Here's an idea:

Collect the names of all named parameters and named arguments in the program. This is done already in the ClosureLayouter.
Sort this list of names alphabetically.
Add an extra ordinal field in Symbol objects that stores a constant Symbols index in this list.
When comparing symbols as part of type comparison, just compare these ordinals. This will be much faster than comparing the strings.
Non-constant symbols and constant symbols that are not names of parameters can have -1 as their ordinal value. This also enables a very quick test in Function.apply whether a symbol is already canonicalized.


Create OWNERS.md

Signed-off-by: K Rain Leander<EMAIL_ADDRESS>

Could I get a reviewer on this one so that I can close issue #12 please?

Thx @dustinmiller1337 !! !


Update version from 0.0.90 to 0.0.91

This is an automated update of version in pyproject.toml. This action is performed by publish.yml.

updated version from 0.0.90 to 0.0.91, @SuleyNL pls review


Migrate synchronization_oauths id to UUID

Closes https://github.com/CartoDB/cartodb/issues/3383

@juanignaciosl CR please.
Tested in local (connecting and searching with Dropbox datasource) and works fine.

:+1:

retest this please


when part

Hi
I need to check mulitple facts in the when part of the rule. Is it possible to combine them?
I cannot find any example how to do this for Intellect so I am not sure if it is supported.

+1 on this feature. I'm planning to use Intellect to build an event correlator for alarms in a system. I want to batch alarms so when I receive a new alarm I need to figure out if there is already one of the same type in the system. Do do that I create a Alarm fact and a AlarmFact fact, the first is removed as soon as it is processed and the second has a counter of how many alarms of a certain type has come so far for deduplication.


test example-from-github-pip

I am struggling a bit with the test-*-example-from-github-pip.yml.  I think it can't work always.  Right now it points to a git-repo branch.  So that limits other branches from doing iterative work.
When we get pypi support, there will always be a latency issue.  Even if published, the module available on pypi might not update for 2 hours, or what ever, so if you have edited a core piece of code you want to test, you might not see it in the length of time it takes for the testing to complete, which looks pretty fast, sub 10 minutes.
This test feels like one that should live with the blender-fake-addon repo, and the other one, with the wheel, lives here.
There is potentially a third/replacement test.  One where you just set the PYTHONPATH to the directory with the module lives, or you do a straight python setup install (not with a wheel)
Am I missing something?

Hey this recipe may indeed be strange at first. For the time when the pypi.org project will be set up, that recipe will indeed be meant to keep testing the last stable uploaded online version. So it just tests that installing from pypi.org does work (imagine someone outside of the CI bots pushes broken stuff there), which is non neglectable.
But right now, it is basically attempting a remote pip install from a github URL that has no wheel file built.
The other recipe does a local pip install from a freshly built wheel file.
I do not mind this recipe being either ditched or rename. I personnally have similar recipe on another project and it is like a watcher for me of pypi.org's latest uploaded build's stability.
Up to you :)

This could actually be a nigthly jobs that sends us emails if it fails.. Through your travis toolchain could also do that and duplicate work. I do not care much which CI toolchain should prevail.. as long as the project is stable on pypi.org :) and as I can dedicate time building my blender plugin :)


router: make AddLinkType acquire the DataPlane mutex

Fixes issue #4282.
With this change, the implementation of AddLinkType matches that of the other setters and the comment that precedes it.

This change is

I am aware of the current failure, I will look into it

Good point. By the same token, I guess we can also make AddNeighborIA private and drop the the call to d.mtx.Lock().

...and the same is true in the case of AddLinkType, so my initial objection was wrong. Apologies. I also don't know why the end-to-end test fails, though.

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @jcp19)

No worries, I also missed the fact that they are different mutexes at first 😅

The checks went through this time and it is unclear why. It is strange that they failed before, maybe the timeouts are too tight?

Yeah, something like that: https://github.com/scionproto/scion/issues/4606
On Thu, Sep 12, 2024 at 3:05 PM João Pereira @.***>
wrote:

The checks went through this time and it is unclear why. It is strange
that they failed before, maybe the timeouts are too tight?
—
Reply to this email directly, view it on GitHub
https://github.com/scionproto/scion/pull/4614#issuecomment-2346231435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBLEYOAPK6PRMV7DU3VN3NTZWGGP7AVCNFSM6AAAAABOBMMBDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBWGIZTCNBTGU
.
You are receiving this because your review was requested.Message ID:
@.***>

--
JEAN-CHRISTOPHE HUGLY
Software Engineer
+41 79 455 68 69
@.*** @.***>
scion.org http://www.scion.org/
SCION Association https://www.linkedin.com/company/scion-association/
https://www.scion.org/


CosmosDB x-ms-retry-after-ms header access

CosmosDB can reject the request with 429 status code. Here is the sample response:
ExceptionType : RequestRateTooLargeException
ExceptionMessage : Message: {"Errors":["Request rate is large"]}
According to documentation:
"When a client attempts to exceed the reserved throughput for an account, there is no performance degradation at the server and no use of throughput capacity beyond the reserved level. The server will preemptively end the request with RequestRateTooLarge (HTTP status code 429) and return the x-ms-retry-after-ms header indicating the amount of time, in milliseconds, that the user must wait before reattempting the request."
Is there a way to access header "x-ms-retry-after-ms" in gremlin execute response to handle the retry properly ?
so, basically I'm running
graph.execute("g.E().count()", {}, (err, results) =>{...})

how to get that header from here?

Thanks,

Would be happy to hear an update regarding this issue too.


pickup_drop_off_window always required for areas

Hello everyone,
in the documentation it says start_pickup_drop_off_window	and end_pickup_drop_off_window are

Required if stop_times.stop_id refers to stop_areas.area_id or id from locations.geojson.

To my understanding, this would mean that departures from areas always require an interval.
However, there are indeed on-demand services that run between two areas with fixed departure times.
Here is an example for area relations with fixed departures: https://www.vor.at/fileadmin/CONTENT/Downloads/Folder/Anrufsammeltaxi_Folder/AST_Infoblatt_MOSTI.pdf
I do understand that in reality the vehicle will start picking up passenger from that departure time on, but so do the operators that design there timetables in such a way.
Can someone clarify if this indeed currently not intended in GTFS-Flex or  if I may have simply misunderstood it?
Currently, it would probably have to be solved in such a way that in this case the time window is filled with identical start and end times.
Thank You!

I believe in the design it was assumed that you could not set a fixed departure time with a zone-based service because it would change depending on the location a user wants to be picked up. Any eventual fixed departure time would be generated once the user negotiates with the agency and a trip is booked.
A solution to representing the kind of service you referenced would be to distinguish between business rules and operational behavior when describing the service with Flex. For example, one could set the window to match the timeframe the service operates within de facto even though it only schedules pickups at specific intervals de jure. So for the "from" zone, if you have departure intervals at 05:35, 08:35, 10:35, and 13:35, set the window at 05:35-14:00[or a value representing when you can reasonably expect the last pickup for the "from" zone to take place]. This way, a trip planner can "capture" a users query and link them to this kind of service. You can then include in the message field a note about departures taking place at fixed times so the user is aware that the prospective itinerary they are presented with may differ from actual travel times.

Thank you for the response.
I agree that the actual time will be provided by the booking system and that the journey planner can only give an estimated time as long as the vehicles availability and position are not known. But a journey planner wants to be as close as possible to the actual departure time, considering connections to public transport.
When you use the whole time window instead of fixed departure you will, e.g. in rural areas with only three departures a day, have really bad JP results.
My suggestion is to change the presence requirement for start_pickup_drop_off_window and end_pickup_drop_off_window from Conditionally Required to Conditionally Forbidden.
For example like this:

start_pickup_drop_off_window
Time
Conditionally Forbidden
Time that on-demand service becomes available in a GeoJSON location, stop area or stop. For timebands if stop_times.stop_id refers to stop_areas.area_id or id from locations.geojson.- Conditionally Forbidden if stop_times.arrival_time or stop_times.departure_time are defined.

This will allow to model fixed departure or arrival times and I don't see how it hurts the format.
What do you think?

I can't think of any issues this change would cause on the producer side, but I'd be curious to hear from a consumer or two (@timMillet? @leonardehrenfried)?
Also, as a side note, there would need to be some changes to some documentation MobilityData owns, such as the "is it Flex?" decision tree and the GTFS components spreadsheet should this change go into effect.

I'm on two minds about this. On the one hand it's nonsensical to be claiming to be everywhere in a zone at an exact time. (You've discussed this.)
On the other hand, this is exactly what the operator wants to communicate.
As Weston pointed out, this raises a few questions about what is and isn't flex. As a consumer I would not rush to implement this, as it would make an already complicated implementation even more complex.
I would like to try to convince you that you can achieve a satisfactory approximation of the linked pdf schedule with the tools that the spec already gives:
You could model it as a separate trips where each zone has a short window. It would look like this:

Village A: 8.35-8.40
Village B: 9.00-9.05
...

And then a later trip would have the following times:

Village A: 10.35-10.40
Village B: 11.05-11.00
...
This would mean that we don't need to make the spec more complex and get a result that is close to what the operator claims.

Would this work for you?

We could work with it, but of course we want the best possible solution.
Another point I would like to make. In the data formats NeTEx (VDV462) and HRDF (Version 5.40.72) it is possible to map a service in this way. So if conformity with these formats is the goal, the change would be a step in the right direction.

The entire Flex module is still in proposal stage so the process for getting something change is very informal.
However, getting this into the main GTFS spec is about to start (first videomeeting on Wednesday) and that is a relatively long process of feedback and voting.
If you care about GTFS Flex you should be part of that process. Get in touch with Elias Gino Cripotos from Mobility Data or join #gtfs-flex on the MD Slack.

Thank you. Yes, I will join and am happy to contribute.

Based on the discussions here and in #388, I am closing this ticket.
It is a rare use case and there are ways to model them differently.


MAVEN_OPTS="--add-modules jdk.incubator.jpackage" not working on windows

adding MAVEN_OPTS="--add-modules jdk.incubator.jpackage"  to env on windows does not yield appropriate results when mvn --version is ran.  this is what it produces as output on windows:
Unrecognized option: --add-modules jdk.incubator.jpackage
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
How can this be solved ?

What is the output of running java --version at the command line?

What is the output of running java --version at the command line?

Was able to repro. Don't put the --add-modules jdk.incubator.jpackage inside of quotes in the Windows env variable pane.

Was able to repro. Don't put the --add-modules jdk.incubator.jpackage inside of quotes in the Windows env variable pane.

Let me know if this works. If not, feel free to reopen.

Let me know if this works. If not, feel free to reopen.

Thanks.
This works

Thanks.
This works


Ability to add custom fonts

Thank you for this excellent tool.
As many React Native UI libraries come bundled with custom fonts (or require them to be present), would it be possible to include an easy way to supply the fonts? E.g. a specific folder at the root of the project whose content would be loaded and linked appropriately to the target device?

Hello there! This is possible already using the Expo Font API: https://docs.expo.io/versions/v15.0.0/guides/using-custom-fonts.html - check out an example of it here: https://github.com/brentvatne/custom-font-example
@dikaiosune and I are considering building a version of this that isn't tied to Expo at all so you can eject from CRNA without going to ExpoKit and not have to change your font loading code at all.

Reopening as tracking issue for building this hypothetical font API.

@brentvatne - curious why this issue was closed?  I just ejected from CRNA and expo to regular react native and now all of my fonts are broken.  It would be really handy to have a better solution than "do it all over again once you eject" ... :-)  I can help if you can give me some suggestions!


Test invalid shared settings

Incorporated into https://github.com/ohadschn/letsencrypt-webapp-renewer/issues/28


patch for configs to divide producer and consumer configs

Good day! Thanks for the bundle! It looks really great! 👍
This patch provides a solution to divide configurations between producers and consumers. Without this patch bundle collects all configs for both producers and consumers, which in turn leads to kafka warnings, that sounds like "configuration X parameter is not intended for producer and so will be ignored".

Looks okish but needs at least some test coverage in ConfigurationResolverTest

@mariuszjeruzal Hello, haven’t you managed to run the tests yet and review the merge request?

thanks @OtezVikentiy . Your PR has been merged and new tag and release published: 1.3.0


fluent-plugin-kinesis' dependent gem does not compatible with Fluentd v0.14

How to reproduce
Modify Gemfile as follows:
diff --git a/Gemfile b/Gemfile
index d36cd9c..9720f4a 100644
--- a/Gemfile
+++ b/Gemfile
@@ -16,3 +16,4 @@ source 'https://rubygems.org'

 # Specify your gem's dependencies in fluent-plugin-kinesis.gemspec
 gemspec
+gem "fluentd", github: "fluent/fluentd", branch: "master"

Execute bundle install, then bundler complains unsatisfied dependency:
% bundle install --path vendor/bundle
Fetching git://github.com/fluent/fluentd.git
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/..
Resolving dependencies...
Bundler could not find compatible versions for gem "msgpack":
  In snapshot (Gemfile.lock):
    msgpack (= 0.7.6)

  In Gemfile:
    fluentd (>= 0) ruby depends on
      msgpack (>= 0.7.0) ruby

    dummer (>= 0.4.0) ruby depends on
      fluent-logger (>= 0) ruby depends on
        msgpack (~> 0.4.4) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

It's same with this issue: see fluent-logger-ruby.
https://github.com/fluent/fluent-logger-ruby/issues/51


flutter --verbose should mention $FLUTTER_ENGINE if set

When running with --verbose, we should proactively mention any environment variables that are set that are affecting our behaviour.
(I just spent some time trying to track down a weird behaviour and it was because I had FLUTTER_ENGINE set.)

Closing this. We haven't had a need for this in a long time.