Update index.html

This works better .
The <div> with class container-lg is not closed properly, it should be closed after the loop that generates article cards.

The images are loaded from a specific path (/assets/images/illos/). Make sure this path is correct in your project structure.

Error- Also the word YouTube doesn't changes its language as others changes

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

This works better .
The <div> with class container-lg is not closed properly, it should be closed after the loop that generates article cards.

The images are loaded from a specific path (/assets/images/illos/). Make sure this path is correct in your project structure.

Error- Also the word YouTube doesn't changes its language as others changes

You can't remove the liquid templating.  Please place that back and then we can look at the other changes. Look at your deployment to confirm.  Also the word Youtube is not in the index.html.  The repeated description on this PR makes me think bot.  Please prove otherwise.  Cheers.

Esto funciona mejor. La <div>clase with container-lgno está cerrada correctamente, debería cerrarse después del bucle que genera las tarjetas de artículos.

Las imágenes se cargan desde una ruta específica ( /assets/images/illos/). Asegúrate de que esta ruta sea correcta en la estructura de tu proyecto.

Error- Además la palabra YouTube no cambia su idioma como cambian otras

[x] ¿Has seguido las pautas para contribuir ?
[x] ¿Ha explicado qué hacen sus cambios y por qué agregan valor a las Guías?

Tenga en cuenta: cerraremos su PR sin comentarios si no marca las casillas anteriores y proporciona TODA la información solicitada.

https://github.com/github/opensource.guide/pull/3315#issue-2589975011

https://support.google.com/chrome/thread/300709465?hl=en&msgid=303571045

A first-level heading
A second-level heading
A third-level heading

Due to lack of response and the removal of some of the liquid templating that shows it breaks rendering, I am closing this PR.  @Yashika0108 please reopen and fix if you would like us to review again.  Cheers.


Fix travis_pypy_setup script for PY3, add tests for it

So, this fixes the problems reported in issue #73 when running it in Python 3 and adds tests for the travis_pypy_setup.py script via tox too.
The test script is probably not perfect, but will help avoiding regressions at least for the happy path. :)

I can't seem to be able to get a pypy 2.6 working in Travis... :/
I'll just disable testing on it for now.

Looks great @eliasdorneles.


latest\main.csv not updated

The download of this link https://storage.googleapis.com/covid19-open-data/v2/latest/main.csv
does not gives the latest information, last date is September.

Also, this file has a different column layout than the https://storage.googleapis.com/covid19-open-data/v2/main.csv file

Please see the new v3 schema: https://storage.googleapis.com/covid19-open-data/v3/latest/aggregated.csv


Install-Module for PSReadLine 2.1.0 Beta 1 on PowerShell 7

When i try to install PSReadLine 2.1.0 Beta 1 on PowerShell 7 i get the following error:

This is the information:

Looks to me like you're using install-module, so that would be for the v2 version of this module, the issues have been moved here:
https://github.com/PowerShell/PowerShellGetv2
That said, a guess would be that you're installing for the first time, so you haven't installed the nuget client binaries yet, which often requires admin rights.


Fix #52 binary file missing

Trying to install verdaccio 2.0.0 fails on create binary links, file not found. Removing the restrictions from .npmignore fix the problem

@juanpicado I think you can also remove the reference to sinopia.

Thanks! I'll publish 2.0.1 soon


Add helper function so go template can create slice

Issue #, if available: no issue
Description of changes:
Create a small helper function so go template can create slice.
It will be used by rds controller soon.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/retest

/approve

/retest


drawing ROIs

As much as I don't want to do this, it's sometimes a pain to go back and forth from imagej. Especially if I'm displaying a LazyArray or similar. Can just start with rectangular ones.

A basic version exists, more complex versions on roadmap


Implement ListUserRevisions

Fixes #1101. Still needs integration tests, and should eventually use a batch API in Trillian for efficiency.

LGTM. Would you like me to merge this?

Yep, should be ready.


Does this data proxy support include?

Does this data proxy support include?
I tried this query:
    const leaderboardRows = await prisma.leaderboard_row.findMany({
        include: {
            profile: true,
        },
        where: {
            leaderboard_id: leaderboardId,
        },
        skip: start - 1,
        take: count,
        orderBy: {
            ['rank']: 'asc',
        },
    });

and got:
  Invalid `prisma.leaderboard_row.findMany()` invocation:
  Cannot return null for non-nullable field leaderboard_row.profile.

Data proxy logs:
prisma:query SELECT 1
prisma:query SELECT "public"."leaderboard_row"."leaderboard_id", "public"."leaderboard_row"."profile_id", "public"."leaderboard_row"."name", "public"."leaderboard_row"."rank", "public"."leaderboard_row"."rating", "public"."leaderboard_row"."last_match_time", "public"."leaderboard_row"."drops", "public"."leaderboard_row"."losses", "public"."leaderboard_row"."streak", "public"."leaderboard_row"."wins", "public"."leaderboard_row"."updated_at", "public"."leaderboard_row"."rank_country" FROM "public"."leaderboard_row" WHERE "public"."leaderboard_row"."leaderboard_id" = $1 ORDER BY "public"."leaderboard_row"."rank" ASC LIMIT $2 OFFSET $3

When I removed the include the query succeeded:
    const leaderboardRows = await prisma.leaderboard_row.findMany({
        // include: {
        //     profile: true,
        // },
        where: {
            leaderboard_id: leaderboardId,
        },
        skip: start - 1,
        take: count,
        orderBy: {
            ['rank']: 'asc',
        },
    });

Ok I think it supports include but not for composite primary keys. If I remove the composite key from my model it works:
model leaderboard_row {
  leaderboard_id  Int               @id
  profile_id      Int
  name            String
  rank            Int?
  rating          Int?
  last_match_time DateTime?
  drops           Int?
  losses          Int?
  streak          Int?
  wins            Int?
  updated_at      DateTime  @updatedAt
  rank_country    Int?
  profile         profile   @relation(fields: [profile_id], references: [profile_id])

//  @@id([leaderboard_id, profile_id])
  @@index([rating], map: "IDX_935515e6126c1a045608ca78b9")
}

model profile {
  profile_id              Int               @id
  steam_id                String?
  name                    String?
  clan                    String?
  last_match_time         DateTime?
  country                 String?
  avatarhash              String?
  last_match_fetched_time DateTime?
  last_refresh            DateTime?
  leaderboard_row         leaderboard_row[]
}

I have create a PR to fix this issue and also enable prisma raw queries here: https://github.com/aiji42/prisma-data-proxy-alt/pull/20


Add --cloud as a build-option

Purpose

Add --cloud=k8s as a build-option

Fixes

https://github.com/ballerina-platform/module-ballerina-c2c/issues/4

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

LGTM

LGTM


Implement history trimming with GPT4 tokenizer

This uses tiktoken-rs to obtain token counts.

@calyptobai If we're using this, can we remove the GPT-2 tokenizer, and the tokenizers dependency?


“Minimum working DateRangePicker” does not seem to be working

I used DateRangePicker according to the setup described in the README, as follows:
<div>
  <DateRangePicker
    startDate={null}
    endDate={null}
    onDatesChange={({ startDate, endDate }) => this.setState({ startDate, endDate })}
    focusedInput={null}
    onFocusChange={focusedInput => this.setState({ focusedInput })}
  />
 </div>

Since according to README this should compose a minimum working calendar. However the result I get are two vertically aligned "start date - end date" pairs, and the calendar does not show up when I clicked on either date. I can however type on the date. Is this the expected output for the "minimum working calendar"?

Issue is resolved after using DateRangePickerWrapper from the provided examples.

Can you show how you used DateRangePickerWrapper? I may have imported it wrong as well.

@ReidunMarie you should still import the DateRangePicker from react-dates but if you copy the code in https://github.com/airbnb/react-dates/blob/master/examples/DateRangePickerWrapper.jsx, that should be the best setup to work off of.


Update jquery for master

https://www.pivotaltracker.com/n/projects/1914499/stories/136378431
@chriskacerguis

Will be backported to Euwe via https://github.com/ManageIQ/manageiq-ui-service/pull/401

@AllenBW @chriskacerguis https://github.com/ManageIQ/manageiq-ui-service/pull/401 is closed.  Do we still need to backport this?

@AllenBW @chriskacerguis - do we need this in euwe?

yes.

Since #401 is closed... what will be the replacement?  Since this PR contains yarn, I'd assume you'll create a separate Euwe PR?

I don't know why it was closed.  @AllenBW can you please reopen?

@AllenBW https://github.com/ManageIQ/manageiq-ui-service/pull/401 should be re-opened?

Backported to Euwe via https://github.com/ManageIQ/manageiq-ui-service/pull/554


Add GLTF to Convex Hull Collision and Trimesh Examples

GLTF to Convex Hull Collision:

Demonstrates how to convert a GLTF model to a convex hull and handle collisions with other objects.

GLTF to Trimesh Collision:
Illustrates how to use a GLTF model as a trimesh for precise collision detection.

Thanks for the PR ! It's a great example.
I'm not sure if we want to rely too much on an external library.
three.js is already used for rendering, so I'd say you picked the least controversial one :+1:, but this PR may be shifting the realm of rapier.js to support three.js interoperability, so I think we should consider it carefully.

@Vrixyz Fixed the prettier issue, can you look into it now? Thanks.

should work now @Vrixyz

I went ahead and changed the model to something less controversial, thanks!

Hey @Vrixyz ,
Thanks for merging the pull request! I was hoping we could include the sword model in the example, but I trust your judgment. Thanks again!


Fix test linting

There was a few comments that should not have been resolved on here yet - I have marked them as unresolved and it would be good to resolve them in a follow up PR please


glfw 3.1.2

This brings all the changes in glfw 3.1.2 + bumps the version in cargo.toml to 3.1.4-glfw.3.1.2

This project have already been published 3.1.2 version to crates.io. Shall we close this PR?

sure


Moved --with-pear to the pear variant

Additionally, modified the default PEAR path from $BUILD_DIR/lib/php to $BUILD_DIR/lib/php/pear for cleaner directory layout.
The current layout looks a bit messy:
├── Archive
├── build
├── Console
├── data
├── doc
├── extensions
├── OS
├── PEAR
├── pearcmd.php
├── PEAR.php
├── peclcmd.php
├── Structures
├── System.php
├── test
└── XML

The extensions and build directory do not belong to PEAR but are mixed with its top-level packages. Moving PEAR into its own directory makes the layout cleaner:
├── build
├── extensions
└── pear

It also helps avoid potential conflicts between top-level PEAR packages and internal PHP resources.

Coverage decreased (-0.9%) to 48.689% when pulling 89cb1520bd7db9c2cfbde3cf9f170163e9e7296e on morozov:pear-path into 26c3d17148d24fd2f1beed4e242ef7f0baab26a0 on phpbrew:master.

Looks good to me


[MongoDB] Fixes local Docker setup and load_data script

What's being changed:

Fixes docker compose, updates version and use connection string when loading data to emulate actual connector

How did you test this change (include any code snippets, API requests, screenshots, or gifs):

Tested script locally

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


Works for sometime and then can no longer add files from ipfs

Version: 0.9.0 (desktop), 0.4.22 (go-ipfs)
OS: macOS 10.14.6 (18G95)

Adding files from ipfs initially works, but after a nondeterministic amount of time and uses, adding files using the Add button appears to do nothing.
Restarted and reinstalled multiple times, including blowing away ~/.ipfs/ and ~/.ipfs-desktop/  and  ~/Library/Application Support/IPFS Desktop/.
Also, the Files section will periodically refresh and hang forever.

Hey @steakknife,
I'm sorry for hearing you're having some troubles with IPFS Desktop!

Adding files from ipfs initially works, but after a nondeterministic amount of time and uses, adding files using the Add button appears to do nothing.

Hmm... Will try to reproduce.

Restarted and reinstalled multiple times, including blowing away ~/.ipfs/ and ~/.ipfs-desktop/ and ~/Library/Application Support/IPFS Desktop/.

Generally any problem should go away just by restarting the app. Didn't it work?

Also, the Files section will periodically refresh and hang forever.

Will try to reproduce too.

We revamped the way file import works when HTTP API is used (eg. in IPFS Desktop) adding many files, or adding a big file (4GB+) should work much better now.
Please upgrade to v0.13.2.


implement multitenancy index pattern

🗒 Summary
Wraps all instances of 'registry' and 'registry-refs' with a resolution function which returns an altered string iff env var MULTITENANCY_NODE_ID is set to a non-empty value
⚙ Test Data and/or Report
Initially: Manually tested in the empty-value case.  Tested in DEV MCP against registry-en-delta
Changes have been cherry-picked from #122, and not tested yet - must be tested manually in DEV MCP
♻ Related Issues
fixes #120
related to #60

@jordanpadams @tloubrieu-jpl what's the priority on getting this tested and merged?

@alexdunnjpl let's talk about this at the breakout, but I added this ticket associated with this to the Registry API MVP. I really don't think we can deploy the API without have sweepers up an running (or at least the API will not work for several endpoints)

@jordanpadams I'll put testing this top-of-list, then

Testing blocked until EC2-attachable role created in MCP-PROD for use in tests.
@sjoshi-jpl has opened a ticket (could you link it here when you get a minute?) as only SAs have access.
sweepers policy will be temporarily attached to the new role to allow manual testing in EC2, then unattached once it's confirmed that sweepers can function with that policy.

Tested on MCP prod.  Currently running against MCP indices to allow for immediate API deployment without blockage by ECS sweepers deployment.


Add delete user functionality

[x]  As an admin I should be able to delete user
[x] Make sure delete my account is fixed for user (white=false theme)

Too many conflicts to fix with master. will create a new PR


Clarify help message for --time option

Inspired by a confused user on Reddit.
This change is subjective, feel free do edit/reject it.

I do prefer this new wording

Dropping in that I also misread this option previously, and scrounging around a few other "expire/preserve/past timespec" options for wording examples:

rdiff-backup --remove-older-than (more verbose option name as well, but expected since this tool is meant to be scripted the once, rarely ran interactively if at all)

Remove the incremental backup information in the destination directory that has been around longer than the given time. [SNIP]

IMO, I would partly wonder about changing the --time argument's name itself, but that is very much out of scope of a quick PR like this. Something more akin to --keep time_spec but that runs into not uncommon "I want to keep by file pattern" confusion. I am less than helpful at naming things :) so maybe keep --time after all.

git-clone --shallow-since

Create a shallow clone with a history after the specified time.

maybe not a great sample, but was in my HISTORY file

journalctl --since|--until

Start showing entries on or newer than the specified date, or on or older than the specified date, respectively. [SNIP]

Again where what is written is the least surprising action (which is helped by the arg name itself)

docker image prune --filter

[SNIP] until (<timestamp>)  only remove images created before given timestamp [SNIP]

Partly more an anti-example, since the expectation is that filters are more-or-less generated by other applications/front-ends to docker CLI.

go clean does not provide any preserve options it seems (which makes sense for a package manager)
npm prune also does not provide any preserve options (which makes sense for a package manager)
borg prune --keep-within

keep all archives within this time interval

A close intent and wording, of course a backup software prefers to be more about what it is keeping vs deleting, so that here for cargo-sweep that the wording is more or less inverse makes sense to me.

outlook email

has some sample images, verbiage below

Clean out items older than ...

Find items older than ...

All to say, the wording varies greatly from application to application, and I couldn't off-hand find decent samples that were closer to intent in design/usage as what cargo-sweep does, but those by backup software seem a decent (if slightly inverse) fit to confirm the new wording is more aligned with expectations and first impression understanding.

@admalledd, quality comment. Good points, including:

of course a backup software prefers to be more about what it is keeping vs deleting, so that here for cargo-sweep that the wording is more or less inverse makes sense to me.

Some of the examples are not really applicable, because they specify an absolute date rather than a time period (which makes more sense for cargo-sweep's use case). Though, I really liked the first example with rdiff-backup --remove-older-than. Yeah, an ideal interface would look something like cargo sweep --remove-older-than 30d.
 I personally have a cron job with cargo sweep, I wouldn't want all similar scripts to break. At most, we could add an alias and support for optional unit suffixes, in a backward-compatible way. But I'd say that my PR is already achieves 90% of the benefit. No one remembers these option names anyway. A good enough --help is a good enough solution, IMO.

I agree on "don't rename --time", I actually don't like the overly verbose command line args unless the tool is nearly always expected to be setup in cron/script/systemd.timer/etc use case. Such as rarely if ever actually meant to be directly invoked by human. The shorter arg is a good thing here in my opinion (that it also short-hands to -t is of course nice). I can't think of any reasonable way to phrase as shortly as the existing --time the remove-older-than type wording of the arg itself. Any other options (like --keep) I have problems with potential mixup with "keep what? path spec/patterns? time?" that would then require extending the name anyways to imply the time component that any change becomes moot. Of course, that is all I can think of, as always one of the hardest programming things is naming stuff :) but certainly for now, just updating the description is plenty. if-when (probably never, not worth it) someone very clever with words comes up with better naming that can be a future problem, in a future issue/PR, not this one.
I agree most of the samples are less applicable, when I started writing I thought I would find more in my HISTORY or quick searches, so I went a bit wider/further afield and even listed a few that while intuition might have had a keep/preserve/timespec turns out didn't (most notably other full package managers, npm, nuget, go). At that point spent enough moments that thought worth completing anyways, even if most didn't fit exactly, to see if anyone else had inspiration.

Thanks for the input folks, it's possible to change it to --remove-older-than 30 or --remove-older 30 without breaking backward compatibility, like @Expurple mentioned, by creating an alias to the previous flag name, however...

No one remembers these option names anyway. A good enough --help is a good enough solution, IMO.

I agree with this, and therefore I'm leaning towards keeping --time as it is.
Let me know if y'all have any strong opinions bout this and we can reconsider :) .
And thanks for the PR too.


TCES-10 URD-Login Page

Description

Created Login component
I still need to get design approval from Jake

Completed TCES-10

Will resolve merge conflicts after midterm!


cli: add --characters-file

This PR allows users to use a file containing a regex string to filter out characters.
@madig could you please test this (don't have a win machine to hand)? Here's you test string with the required mods.
[!"#$%&'\(\)*+,-.\/0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ'\[\\\]\^_`abcdefghijklmnopqrstuvwxyz\{\|\}~ ¡¢£¥§¨©ª«®¯°²³´¶·¸¹º»¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿĀāĂăĄąĆćĊċČčĎďĐđĒēĖėĘęĚěĞğĠġĢģĦħĪīĮįİıĲĳĶķĹĺĻļĽľĿŁłŃńŅņŇňŊŋŌōŐőŒœŔŕŖŗŘřŚśŞşŠšŢţŤťŪūŬŭŮůŰűŲųŴŵŶŷŸŹźŻżŽžǍȘșȚțȷˆˇ˘˙˚˛˜˝ẀẁẂẃẄẅẞỲỳ –—‘’‚“”„•…‹›⁄⁰⁴⁵⁶⁷⁸⁹₀₁₂₃₄₅₆₇₈₉€™−◌]

Fixes #88

@madig still interested in this?

Sorry, I dropped off of GitHub recently.
Something's not going as planned when I paste the string above into a file:
❯ poetry run diffenator2 diff --fonts-before ../bla.ttf --fonts-after ../blaa.ttf --characters-file a
ninja: error: build.ninja:27: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:29: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:28: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:29: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:29: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:29: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:28: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:28: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:30: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:29: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:27: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:28: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:28: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
ninja: error: build.ninja:27: bad $-escape (literal $ must be written as $$)
<EMAIL_ADDRESS>          ^ near here
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/nikolaus/diffenator2/src/diffenator2/__main__.py", line 100, in main
    build_index_page(args.out)
  File "/home/nikolaus/diffenator2/src/diffenator2/html.py", line 178, in build_index_page
    assert len(html_files) > 0, f"No html docs found in {fp}."
AssertionError: No html docs found in out.


Scroll not working properly

Regarding pyautogui.scroll().
Found another similar issue, someone said to input a large number of clicks so I did it, 100, 200, 500, nothing. At 1000, I noticed the screen scrolls only on one app, and only up (I need down). Any way to diagnose and fix the problem?

Most projects I have worked on will request more info, so I'll start there. At the very least, what operating system? What Python version?
Also if I remember from my experimenting, the app that you want to scroll needs to be the one with the focus. Have you selected the app first? I had trouble using things I didn't realize I changed the focus on when doing it manually.

HI @goldieczr, I hope you are doing well.
Ahhh.... So many things have changed in python in the last few years.
Keep in mind,  it is not just the scrolling, it is also, how fast the computer is recognizing you scroll That has the biggest impact as well.
The use of the code & how you implement it may play a role, as so many other factors.
My tinkering (story time, lol)
After using PyAutoGUI for years now,  man the struggles i have gone thru with bottle necking of the CPU in tying to click a Million times an hour.  You are going to run into some various issues, believe me I have had mine.  I have used pyautogui to replicate me playing a game on my laptop, for a game called Realm Grinder here's my code.
Now this got more interesting as time went on, you see the game gets more complex & has to do crazy amounts of mathematical calculations per second, so as you level up each "Click" becomes more taxing on the computer.  Well when you get to 1E300+ OR 1 Novemnonagintillion (yes a real number lol sorry numbers are facinating) my computer was a Croakin'.
Anyway you will figure out the sweet spot, but it will take time.
Ref: https://realm-grinder.fandom.com/wiki/Notation
Ref2: https://googology.fandom.com/wiki/List_of_googolisms
Other items to keep an eye on.
Computer Scrolling matching your Scrolling?
If you scroll your mouse and it behaves the same. It's the program you are using not PyAutoGUI.
Different programs don't always behave the same.. Example Twitter doesn't scroll like iTunes.
Which can be programmed specifically by each developer of each program (Google / Spotify / iTunes / Microsoft / Linux / Python / Bash etc.) & same is true for websites they can force your scroll to mean less like when scrolling past an Ad.
Bluetooth Vs Wired
Bluetooth vs Wired has a role too.  if you are using a wireless mouse and comparing to code, you might see a discrepancy, as wireless has interference & battery strength, and code is direct.
System Settings
This can also be controlled by your system settings, this may have an impact on the behaviour of the interaction under your Mouse Settings -> Scrolling Speed/Sensitivity.
CPU & I/O Bottlenecking
As I mentioned above PyAutoGUI is only as fast as your computer will allow.
My Click speed for my mac running the game & the game processing them as if it was me was click_speed=0.037  about 27 times a second the other program could register.
Cosmic Rays (rare)
Very rare, but Election interference and game glitches. Fun watch.  https://www.youtube.com/watch?v=AaZ_RSt0KP8
If you do still think this is a problem, please provide your code & as much detail so others can try to replicate it to investigate further.
Good luck I hope that helps in providing a different perspective.
Thanks for reading all! lol
Have a Great Day all!


Fix that cookie not work well on Android 5.0 and above

This fixes cookie missing bug on Android 5.0 and above.
On Android 5.0 and above, after the app successfully obtains the cookie, you kills the App within 30 seconds and restarts the App. It accesses the interface that needs to carry the cookie and finds that the cookie does not exist.
Test Plan
Updated tests for the addCookies function to include test cases specifying Android version, and tested on the command line in my app to make sure it has the expected behavior.
Release Notes
[ANDROID] [BUGFIX] [Cookie] - Fix that cookie not work well on Android 5.0 and above

Hey guys, this fixes a critical issue we have where users of our app get logged out whenever they switch apps or close the app. @kelset could you possibly review this, it's literally 3 lines - or suggest someone else? That would be really really appreciated :) Thank you!

Can you add a test? We should ensure this does not regress in the future.

Looks like the Android tests are failing on circle before actually running any tests anyway

@farhanmannan test_android is green on master: https://circleci.com/gh/facebook/react-native/44989 - you probably need to rebase.
That's unrelated to my ask, though. I'd like to have an actual test case added to check for this in future test runs.

@yuzhiyi any chance of a test?

I submitted a new pr: https://github.com/facebook/react-native/pull/19770

Closing in favor of https://github.com/facebook/react-native/pull/19770


File Upload API Definition missing information about how the document id is set

Idea
https://docs.vectara.com/docs/api-reference/indexing-apis/file-upload/file-upload
The file upload API documentation doesn't provide any guidance on how to set the document id in our system. This is a serious omission given the centrality of the id.
The id is taken from the Content-Disposition header. The value corresponding to the filename key is extracted.
Reference: https://bitbucket.org/zir-ai/platform/src/aaca4a16b19d55a35325318f3a04efb919febfec/indexing/titan/src/main/java/com/vectara/indexer/baobab/FileUploadServlet.java#lines-659
Context: Engineers at play.ht were confused and couldn't find guidance in our docs.

@eskibars lmk if you want me know if/how you want me to set the Assignee field.

Feedback from the customer:

Great. If the filename was being passed in the upload file example in the documentation, it would have helped. I'm talking about this page for example.

@pwoznic watches this repo.  He'll self-assign or assign to someone else if he needs

Here's the standard docs for Content-Disposition for anyone who wants to learn more: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition

Amin provided great context on the missing info and play.ht use case and I am reaching out to the team where help is needed


Run in Android Studio 3.1.2

Can't compile apk or run in device :(

Unsupported method: BaseConfig.getApplicationIdSuffix().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.

Unsupported method: BaseConfig.getApplicationIdSuffix().
The version of Gradle you connect to does not support that method.
To resolve the problem you can change/upgrade the target version of Gradle you connect to.
Alternatively, you can ignore this exception and read other information from the model.


Vagrant (Windows + VirtualBox) fixed

Hi,
So I got mantl working on Windows and would like to know how I can properly create a pull request for this to help others having problems with it.
Steps to reproduce:

Install vagrant 1.8.4
Install rsync + openssh through the mingw-get installer (download mingw, select rsync and openssh and install packages)
Add minw/msync/1.0/bin to the PATH variable
Comment out some lines in the C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.8.4\plugins\synced_folders\rsync\helpers.rb file:

#"-o ControlMaster=auto " +
#"-o ControlPath=#{controlpath} " +
#"-o ControlPersist=10m " +

install dos2unix and convert all line endings in the roles folder with the following command: cd roles& for /r %f in (*) do dos2unix %f. This command should be run in the mantl root directory in a cmd window.
Now run vagrant up and it should work , I had the same issue as #1816 though, so I applied that fix as well and also the #1817 fix, but since these are already submitted as a PR I chose not to include them here.

Now my question is, how can I convert this to a proper PR? Seeing that most of the steps are pre-requirements on the developer his/her PC. I think the best way to get this fix in place is to add it to the docs and also add an automatic dos2unix utility for the vagrant box?

@thebillkidy : The best thing we can do is outline the steps and the prerequesites in the documentation making sure to give people have the latest links to the required dependencies and to give them solutions to potential issues they may have along the way.
This is it until we build a powershell script that installs all dependencies and configures everything the users will need on Windows 10 or 7. But that is a whole project in itself and I'm not sure if it is worth the time invested as we have bigger problems right now. 👍
Let me know if you we would like to improve the documentation for mantl on Windows in a PR.


Zilean?

Hey,
Championify is not downloading Zilean item builds from every sources.

Can you provide the logs?

Please use the issue template that is provided when you open an issue with the requested information, otherwise they'll get closed like this one. Thanks.


Windows: Remove dead/unused code

Signed-off-by: John Howard<EMAIL_ADDRESS>No functional changes - just removing dead code.

If janky is happy then LGTM

@jhowardmsft I think pkg is supposed to be like "external" library. I think it makes sense to save this function for API consistency.

@lk4d4 - you mean just no-op it with just the declaration?

To clarify the above comment: It can't be used as a library in the way I think you mean. The actual console size setting on Windows is through the HCS interface. The code being removed is meaningless.

@jhowardmsft Oh, okay :) it was worth to mention

LGTM


TypeError: Trainer.init() got an unexpected keyword argument 'gpus'

[2023-03-30 02:45:03,037][__main__][INFO] - Instantiating callback <pytorch_lightning.callbacks.ModelCheckpoint>
Error executing job with overrides: []
Traceback (most recent call last):
  File "/home/rupax/github/state-spaces/train.py", line 553, in main
    train(config)
  File "/home/rupax/github/state-spaces/train.py", line 496, in train
    trainer = create_trainer(config)
  File "/home/rupax/github/state-spaces/train.py", line 485, in create_trainer
    trainer = pl.Trainer(
  File "/home/rupax/github/state-spaces/venv/lib/python3.10/site-packages/pytorch_lightning/utilities/argparse.py", line 69, in insert_env_defaults
    return fn(self, **kwargs)
TypeError: Trainer.__init__() got an unexpected keyword argument 'gpus'

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
wandb: Waiting for W&B process to finish... (failed 1). Press Control-C to abort syncing.

How to fix this ? I am getting this same issue from 2 different machine

1  Windows 11 , python3.10, cuda11.7, torch 2.0.0 + cuda
2 Endovour OS, python3.10, no GPU, torch 2.0.0

This repo hasn't been updated to Pytorch 2.0 yet. This problem is due to an earlier change in pytorch-lightning where the trainer.gpus argument was deprecated in favor of trainer.devices. The latest release of this should at least address this. If you're still seeing issues, can you paste the command line you ran?

Did this fix the error?

No, but I removed( commented out ) some lines from the config file and now its is running without error, although my gpu runs out of memeory everytime I try to train the model, that's some different issue I guess.

Are you on the latest commit? If there is a config in the repo that does not work out-of-the-box on the latest commit and with the provided requirements file, could you indicate which experiment config it is?

To make sure, I am not running with my changes, I cloned the main branch ( latest commit ) again, and try to train with
python -m train pipeline=mnist dataset.permute=True model=s4 model.n_layers=3 model.d_model=128 model.norm=batch model.prenorm=True wandb=null this command [ copied from readme ]
And this is the error I get

Actually, I was studying the SaShiMi model and trying to train with
python -m train experiment=audio/sashimi-sc09 model.n_layers=2 trainer.limit_train_batches=0.1 trainer.limit_val_batches=0.1 [ again copied from readme ]
and this is the error

I tried ( in another clone ) the suggested thread and spawn options, and after that config error appeared.
This are my torch version
torch==1.13.1+cu117
torchaudio==0.13.1
torchmetrics==0.11.4
torchtext==0.14.1
torchvision==0.14.1+cu117

I am using
pytorch-lightning==1.9.3
torch==1.13.1+cu117

OS: Windows 11 and Ubuntu wsl
GPU : Nvidia RTX 3060 6 gb
CPU : Rygen9
NVCC :
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Jun__8_16:59:34_Pacific_Daylight_Time_2022
Cuda compilation tools, release 11.7, V11.7.99
Build cuda_11.7.r11.7/compiler.31442593_0

Unfortunately I don't know the answer to this. My guess is that it's likely to be related to one of these packages + environment. I recently set up this repo in a new environment (standard Linux + CUDA + A100 GPU) and it works well.
To isolate the problem I think it might be useful to try a minimal setup with Pytorch Lightning + wandb; these packages should have examples of a setting up a basic LightningTrainer for MNIST. I suspect you might run into the same issues.

I had the same issue when attempting to run python -m train experiment=s4-simple-cifar wandb=null. My setup (on an Ubuntu 20.04.6 LTS) is
pytorch==2.3.0
pytorch-lightning==1.9.3

I fixed the issue by doing the following:

Comment out weight_summary and progress_bar_refresh_rate in all the trainer config files.
Rename on_epoch_start function of train.py to on_train_epoch_start
Remove the dataloader_idx argument from both on_train_batch_start and on_train_batch_end in ./src/callbacks/timer.py

Hope this helps.


make docker-build fails to build due to user/permission issue when running go get (mac)

When running make docker-build on mac, i get the following error:
make -f cli/Makefile cliall
make[1]: Entering directory '/home/builder/appscope'
DIR=/home/builder/appscope/cli/
GO_VER=go1.16.6
GOPATH=/go
go get github.com/go-bindata/go-bindata/...
go: downloading github.com/go-bindata/go-bindata v1.0.0
go get github.com/go-bindata/go-bindata/...: mkdir /go: permission denied
cli/Makefile:36: recipe for target 'deps' failed
make[1]: *** [deps] Error 1
make[1]: Leaving directory '/home/builder/appscope'
Makefile:33: recipe for target 'all' failed
make: *** [all] Error 2
make: *** [docker-build] Error 2
Removed passing in the user/group from the make target and ran as root, and that seemed to be a quick fix.  My guess is the user/group isn't being passed around correctly
Running on Big Sur 11.4

This appears to be because of the -u addition to the docker run in make docker-build. The UID on the local machine is not 1000 on a mac like it is on all the other machines we tested the build on. Same issue I'm running into with the multi-architecture builds at GitHub.
Thinking...

@TrickleDownReagans  Hey Brian, could you retest with a clean clone of the latest master? We just pushed a bunch of changes to the build system and have a little time to revisit this if you have a moment to test.


Add alternative text for non-existing image file

I added some code for non-exsiting image file. In my project, image files are base64-encoded strings. So, all images in markdown make 404 error.
I guess this is also useful for other peoples.

Closing due to merge conflicts and missing tests.


Linting with clippy

This PR resolves the clippy lint warnings in our codebase.
It also adds a GitHub action which runs clippy and throws an error if there are any warnings (I don't know how to verify that this works without merging it into main, because I assume Github only runs actions on main...)
See comments.

OK, interestingly GitHub does seem to be using the Rust action now, even though it has not been merged into main yet...


[docs] Fix 404 links to MUI X API

The issue was raised by Moz.com

Try to navigate to the data grid API from the v5 documentation, it fails.

Before: https://next.material-ui.com/api/css-baseline/
After: https://deploy-preview-28176--material-ui.netlify.app/api/css-baseline/

TIL prefetch doesn't work between zones: https://nextjs.org/docs/advanced-features/multi-zones, confirmed in https://github.com/vercel/next.js/issues/4419#issuecomment-390142581.

This breaks the following sort() and map().

@eps1lon This logic is shallow, it's not applied on the nested array I have modified.

Could you go back and check if this worked when the pages were added?

I had a look at the history. It was broken when introduced.

I had a look at the history. It was broken when introduced.

So how was it tested when introduce and how did you test it now?

@mnajdova I have changed the approach, this logic will soon be removed once we isolate the different documentation, similarly to how react-aria has its own space https://react-spectrum.adobe.com/react-aria/ vs. https://react-spectrum.adobe.com/react-spectrum/index.html

Soon or later @danilo-leal will figure out a great solution. So, to keep things simple, I have copied and past [the logic of MUI X](https://github.com/mui-org/material-ui-x/blob/68ae5d5d477500ba56564df10a215eb7ad2e22d9/docs/src/pages.js#L26]. I think that we can call it a day.

So how was it tested when introduce

@eps1lon It was tested on the branch of v4, it wasn't on v5.

how did you test it now

It can be reviewed by opening the Before and After links of the issue's description and making sure the href won't point to a 404


Logo Design Offer as Open Source Contribution

Dear Sir/ Madam,
Hi, I'm a Graphic Designer. I would like to make contributions to projects on Github.
After I review your project is great, I want to contribute to this projecy by creating new logo/icon for your web. I have made of sample of logo, is there anything you want to change, please let me know.

Best Regard,
Munadi Kiehl

Thanks for your contribution, we are gladly integrating them into our existing CI.
You were added to the list of contributors on our website https://rocketmod.net/contributors/.


Testing fixes for Chrysalis

Testing fixes for Chrysalis.

Chrysalis appears to be all set for a final release. Note that #485 appears to be an issue with E3SM Diags, not zppy.


Issues #85 samplers

Initial approach

Thanks for putting an initial impl together.
What tradeoffs are you looking for in this approach vs sampling methods used in other tracers impls?
I can guess, but interested in what we are trying to improve on, ex overcoming flaws in algorithms in existing ones like brave, finagle, zipkin, htrace, etc.
With something as critical as sampling, usually I try to get someone distant from the code to ack it as well, as for example I'm not a statistician. I've used the distributed-tracing Google group, gitter, and 1-1 email to field questions like this before.
If this is just a straw man for discussion, that's an answer, too. If so, I'd say next step is to get an expert opinion.

Thanks for putting an initial impl together.
What tradeoffs are you looking for in this approach vs sampling methods used in other tracers impls?
I can guess, but interested in what we are trying to improve on, ex overcoming flaws in algorithms in existing ones like brave, finagle, zipkin, htrace, etc.
With something as critical as sampling, usually I try to get someone distant from the code to ack it as well, as for example I'm not a statistician. I've used the distributed-tracing Google group, gitter, and 1-1 email to field questions like this before.
If this is just a straw man for discussion, that's an answer, too. If so, I'd say next step is to get an expert opinion.

Like presented in the message - this is an ultra-initial approach to start a discussion like the one that we're having. Maybe I should have written DO NOT MERGE to ensure that this is not ready to merge at all.
The algorithm in this sampler is from the statistics point of view terrible - there is no proper distribution or anything like that. I've done this deliberately to begin with sth.
I had no knowledge of implementations of such algorithms in brave for instance. If you have any knowledge about such concrete implementation please paste a link or sth.
Definitely will ping those groups - thanks for the hints! That's why I put this PR in the first place.

Like presented in the message - this is an ultra-initial approach to start a discussion like the one that we're having. Maybe I should have written DO NOT MERGE to ensure that this is not ready to merge at all.
The algorithm in this sampler is from the statistics point of view terrible - there is no proper distribution or anything like that. I've done this deliberately to begin with sth.
I had no knowledge of implementations of such algorithms in brave for instance. If you have any knowledge about such concrete implementation please paste a link or sth.
Definitely will ping those groups - thanks for the hints! That's why I put this PR in the first place.

We had a long Sunday chat with @adriancole and came to the following conclusions.

We have to take TraceID into consideration during sampling to be consistent.
We treat the traceID as a 128 bit number - like HTrace does - https://github.com/apache/incubator-htrace/blob/master/htrace-core4/src/main/java/org/apache/htrace/core/SpanId.java
We apply the Finagle algorithm to define whether we should sample or not - https://github.com/openzipkin/zipkin-java/pull/55/files#diff-31b830705fabb2e936c73337dfa5f219R83

on 3) TL;DR drop the salt from finagle's algo when using in sleuth
Finagle makes a sampling decision once, usually at the root of a trace. That decision is propagated by a sampling flag to all downstream spans. Because the result is remembered, there's no consistency problem.
The sampler in sleuth is invoked for every span in the trace, not just the root span. If we add a salt, we will end up with an inconsistent sample function. Tests should be able to prove this.

@adriancole - pls check if now it looks better. Take a look especially at the bits manipulation (I have working with bits directly ;) ).

@adriancole - more changes arrived... back to you then :)

+100

This is really great work @marcingrzejszczak

Merged here - https://github.com/spring-cloud/spring-cloud-sleuth/commit/640ad4c6f79103da81cd959c1850bc52553119e0
Thanks @adriancole for the reviews!

my pleasure


Shared library

Using the Core Library actually in the project
Reasons:

Code Reuse
Having a nice sample for this procedure
Better Test-Coverage

Possible Risks:
CI is maybe breaking, but this needs to be resolved after PR
Related Issues:
#30 is what this PR is about

I don't know why I haven't done this earlier.
I think uploading the core library was a major blocking point for me somehow as I didn't like the github depedencies with credentials.
But I am happy now as it turned out.
This closes #30


Bug: Interrupted streaming query pipe may result in the query stream never being closed and the connection it uses never being freed

Environment
Knex version: 2.4.2 (latest)
Database + version: Tested with PostgreSQL 13.5 (Ubuntu 13.5-0ubuntu<IP_ADDRESS>) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 10.3.0-1ubuntu1) 10.3.0, 64-bit
OS: Tested with Kubuntu 22.04
Please be aware that although I have used postgres in testing and reproducing this issue, I believe that it is not specific to postgres.
Bug
I have run into an issue with Knex query streams. I wrote a script that reproduces this issue along with instructions on how to observe it here:
knex-streaming-error-repro: https://github.com/pineapplemachine/knex-streaming-error-repro

The short version:
When using a Knex query stream, if the consumption of that stream is interrupted in any way, then the stream never closes and the connection it uses is never freed up.
For example, when an express server pipes the results of a streaming query to an express response object, if the request is aborted then the query stream may never be closed. This unclosed stream may subsequently block operations that modify the tables being queried, causing subsequent queries executed through Knex to hang forever.
This is not an issue with express. I am using express as an example. This issue occurs if any stream that the Knex query stream is piped to exits before it fully consumes the Knex query stream.

In more detail:
I am using Knex to connect to a postgres database, and the repro script also uses postgres. But I think that this same error behavior will occur with other databases as well, due to the way that the _stream method is generally implemented for Knex's Client subclasses.
See for example the _stream method of the Client_PG class: https://github.com/knex/knex/blob/b6d04f75b3c1956be8ffa26740dd1e27909dd25d/lib/dialects/postgres/index.js#L187
Note that the PGQueryStream instance in this example is not visible outside the _stream method that constructs it. It is piped to the stream passed as an argument to the method, without being returned or otherwise exposed. Errors will not be propagated back to the query stream via this pipe. This means that if anything happens to interrupt the streams that the PGQueryStream is piped to, then that interruption will not be propagated via stream events, and there is no way (that I am aware of) to handle this and to explicitly close the query stream, or to free the database connection that it's using.
This means that I cannot use Knex's streaming queries in the server that I develop, because if (for example) a client request is aborted before all the streaming data is received, then the server is left with a database connection that is never released back to the pool. Besides taking this connection permanently out of the connection pool, this can also cause operations that modify the tables being streamed from to hang forever, waiting for the abandoned read query to finish (which it never does).
Note the repository linked at the beginning of the issue, which contains instructions and a script for reproducing this issue multiple ways. It can reproduce the issue where a request being handled by express is aborted, and it can also reproduce the issue by simulating an error in an arbitrary transform stream that the query stream is piped to.

I'm seeing random hangs of knex in our prod environment and have been trying to figure it out for months. I'm super eager to see if this next release fixes it!

I'm closing this issue now because it is solved for me as of updating to v2.5.1.


Simplify GetClientPropertyName()

Use ClientProperty.Name instead of trying to calculate it.  The
calculation is broken for cases where names are camel-cased due to
invalid characters that were removed during naming.  I.e. user.name is
converted to UserName during initial naming; this will translate to a
parameter name of username which incorrectly camel-cases to Username
using the old algorithm.

I verified that the fix for https://github.com/Azure/azure-sdk-for-go/issues/2174 has not regressed.

🤖 AutoRest automatic publish job 🤖
success (version: 2.1.126)


How to backup my current custom snippets

How to backup my current custom snippets?

They are stored in %APPDATA%\Brackets\brackets.json.
You can backup this file or open it directly in Brackets:
Debug -> Open Preference File -> brackets.json
There you'll find entries like
"edc.brackets-snippets.keyNext": "tab",
"edc.brackets-snippets.hints": [  ]


Globalization: RTL support

How to retrieve RTL property of a culture when in a PCL?
See http://stackoverflow.com/questions/39549719/is-there-any-way-to-determine-text-direction-in-a-net-portable-library


around trigger

around trigger, discussed in https://github.com/jmettraux/rufus-scheduler/issues/309
Here's what I put together. Feel free to give any and all feedback on implementation, style, naming, or docs 🙂
I realized my timing idea can be implemented in a post trigger because it is provided the time. I'm pretty sure I'll still find a use for this, but can't think of a more interesting example right now, let me know if you can.

Excellent. I rarely receive pull requests with specs, even more rarely ones with readme changes.
Many thanks!

great!


Move docs build/hosting to Read the Docs

This work is mostly done, but I wanted to get a ticket filed for tracking since there are some final work items that are taking longer to complete than I anticipated.

[x] Add RTD yaml config file, remove Tipue search and beautifulsoup, remove internal conditionalization tag and make commands

[x] Configure and test the RTD build in a private fork

[x] Move to IDM repo

[x] Configure subdomain and proxy from idmod.org

[x] Decide which prior versions of docs to build

[x] Push RTD docs public

[x] Add redirects from gh-pages

All work complete.


MiniKF deployment is no longer available on GCP Marketplace?

I am trying to follow the article (https://www.kubeflow.org/docs/started/workstation/minikf-gcp/) to launch Minikf on GCP Marketplace, however, it seems that the MiniKF Page (https://console.cloud.google.com/marketplace/details/arrikto-public/minikf?q=minikf&id=1f5eac28-1808-4969-b6fa-2cc231a23f45) is no longer available

A manual search through marketplace also doesn't return any result:

Hi @kenly-ldk, yes MiniKF is available on GCP, but there appears to be an issue accessing in the marketplace.   We are looking into this and will circle back when resolved.

@cspavlou Chris, will you please take a look at this ?  Thanks1

Hi @kenly-ldk , thanks for the heads up. Everything should be back to normal now :)
Thanks again!

Thanks a lot everyone for looking into this so quickly. I can confirm that it is back to normal as well :)


Fix ftype=1 check for dcos-docker

High-level description
Fixes ftype=1 install time check for dcos-docker
What features does this change enable? What bugs does this change fix?
https://github.com/dcos/dcos/pull/2768 breaks dcos-docker for very specific (rare but valid dcos-docker) configuration (https://jira.mesosphere.com/browse/DCOS_OSS-3549). This fixes that
If the device being used for docker root directory is not accessible the xfs_info check fails. I have added a block device check before xfs_info check to skip ftype=1 check
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3549 ftype=1 pre-flight check has broken dcos-docker for configurations using devicemapper

Related tickets (optional)
Other tickets related to this change:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Checklist for all PRs

[X] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[X] Read the DC/OS contributing guidelines
[X] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
@adamtheturtle @vespian hopefully this will fix the issue we discussed. I will test it out once I have a build

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot bump-ee
@mesosphere-mergebot merge-it
@mesosphere-mergebot override-status
@mesosphere-mergebot label [Work In Progress |Ready For Review |Holding |Ship It |Request For Comment]

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

OK this is now ready for review. I will backport this to 1.11 and 1.10 as well right away
@branden @adamtheturtle @vespian

Thanks @orsenthil  . This is why I should not commit code late at night.
Fixed it.

Latest commit is a fix for https://jira.mesosphere.com/browse/DCOS_OSS-3549

@mesosphere-mergebot bump-ee

Your pull request's branch is not based on the most recent version of master. Please rebase your changes against this repo's master branch.

@surdy Do you think you could rebase and bump-ee?

@mesosphere-mergebot bump-ee

Your pull request's branch is not based on the most recent version of master. Please rebase your changes against this repo's master branch.

@mesosphere-mergebot bump-ee

@surdy  Ping?

@vespian pong ?

@vespian pong ?

@surdy  Do you think we could ship this PR and finalize the bugfix?  Pretty please :)

@vespian I was not under the impression that this was blocked on me . Is it ?

I have reported the teamcity/dcos/build/dcos failure on https://jira.mesosphere.com/browse/DCOS_OSS-3523. I will re-run the builder.

@surdy  It is - you need to triage Integration Tests failure, ask an owner to override them if they are flakes, s and get the Ship it label. Also, the PR itself is labeled as Work in Progress - it should probably be Ready for review if it is ready to go :)

@mesosphere-mergebot label ready for review

@adamtheturtle dcos-docker/static test is failing with "docker.errors.InvalidVersion: mounts param is not supported in API versions < 1.30" . If I'm not mistaken we see this if older version of docker were being used. I do not think this would failure would be due to any of my changes. I would have expect our tests to have configured hosts correctly (for docker version etc). Should I be pinging someone from tools-infra to look at this ?

@surdy This was a temporary issue that @orsenthil has resolved (see https://jira.mesosphere.com/browse/DCOS-38121). I have started a re-run of the job.

@orsenthil When do you think the next train will depart?

@vespian  - you should ask dcos-owners! :) Please help with reviewing the pending PR - https://github.com/dcos/dcos/pull/2968 | https://github.com/mesosphere/dcos-enterprise/pull/2891 - that was in waiting state for more than 6 days now.

@orsenthil  The PR you mentioned was merged, any chance to get it merged soon? This PR fixes a bug that makes my life difficult :(

@vespian  - You must ping dcos-owners! This is train https://github.com/dcos/dcos/pull/2986 and please approve the train and EE part and should request dcos-owners to merge-it!


UI design for dashboard Page of Blogger

Is your feature request related to a problem? Please describe.
UI design for dashboard Page of Blogger
Describe the solution you'd like
UI design is exact replica of what your website will look like
This task is connected with issue #31  check for wireframes designed for this page and create a UI design for the same using color palette and font styling (for color and font check issue #45 )
Additional context
As we have more than one wireframe for a page so you can either choose a single wireframe and convert it into UI or use features from different wireframes designed by participants and come up with great solution .
Considering UI we expect a high fidelity design , use proper heading title without lorem ipsum .

I am interested @Swarnimashukla

@nooras  what's the update with design ?

@nooras what's the update with design ?

Work is in progress... Will share you soon...

Dasboard UI done... Checkout @Swarnimashukla and let me know if any changes is required...

@nooras its good , but slight different from other pages anyways go for pr , we will change things in coding phase if required.

@nooras its good , but slight different from other pages anyways go for pr , we will change things in coding phase if required.

What else I can do ? Ma'am ?

@nooras  sure , Few things I would suggest :

Use  background color in header as well like footer
Enhance font size in footer section (about , home etc) as they are not clear and difficult to read now, keep them simple not italic , its important to use familiar fonts , styles to make user friendly designs
Remove border from header section's terms like home , about , notification it might look aesthetically pleasing but we need similar designs for every page also I am comparing it for flexibility and ease while coding
You can use small icons as well in front of home , notification etc in header
Give some background color to whole page so that every sections pops up little bit .

@nooras sure , Few things I would suggest :

Use  background color in header as well like footer
Enhance font size in footer section (about , home etc) as they are not clear and difficult to read now, keep them simple not italic , its important to use familiar fonts , styles to make user friendly designs
Remove border from header section's terms like home , about , notification it might look aesthetically pleasing but we need similar designs for every page also I am comparing it for flexibility and ease while coding
You can use small icons as well in front of home , notification etc in header
Give some background color to whole page so that every sections pops up little bit .

Update done @Swarnimashukla

perfect @nooras  go for pr

In static file> dashboard ui_nooras i have to put it ?


List the tag indications for each package

Display the tag indications as keywords, but give them higher priority in their sorting over keywords

duplicate of https://github.com/cdklabs/construct-hub/issues/280 as no backend work is required.


Import of Gitlab merge requests fails

If we try to migrate without "pull request" option than it works (but without merge requests being migrated).
The migration fails if both issues and pull requests are selected.
If we only choose issues than the issues are migrated.
If we only chose pull requests then the Gitlab merge requests are migrated.

Gitea version (or commit ref):1.13.4
Git version:2.30.1
Operating system:Ubuntu 20.04

Database (use [x]):
[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x ] SQLite

Log gist:

2021/03/11 12:31:47 ...es/pull/temp_repo.go:104:createTemporaryRepo() [E] Unable to fetch origin base branch [Group/repo:master -> base, original_base in /var/lib/gitea/data/tmp/local-repo/pull.git228963340]: exit status 1:
2021/03/11 12:31:47 ...rvices/pull/patch.go:56:TestPatch() [E] CreateTemporaryPath: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...rvices/pull/check.go:220:handle() [E] testPatch[3450]: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...es/pull/temp_repo.go:104:createTemporaryRepo() [E] Unable to fetch origin base branch [Group/repo:research -> base, original_base in /var/lib/gitea/data/tmp/local-repo/pull.git096113950]: exit status 1:
2021/03/11 12:31:47 ...rvices/pull/patch.go:56:TestPatch() [E] CreateTemporaryPath: Unable to fetch origin base branch [Group/repo:research -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...rvices/pull/check.go:220:handle() [E] testPatch[3441]: Unable to fetch origin base branch [Group/repo:research -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...rvices/pull/check.go:167:manuallyMerged() [E] PullRequest[3458].setMerged : PullRequest[984] already closed
2021/03/11 12:31:47 ...es/pull/temp_repo.go:104:createTemporaryRepo() [E] Unable to fetch origin base branch [Group/repo:master -> base, original_base in /var/lib/gitea/data/tmp/local-repo/pull.git348178944]: exit status 1:
2021/03/11 12:31:47 ...rvices/pull/patch.go:56:TestPatch() [E] CreateTemporaryPath: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...rvices/pull/check.go:220:handle() [E] testPatch[3458]: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...es/pull/temp_repo.go:104:createTemporaryRepo() [E] Unable to fetch origin base branch [Group/repo:master -> base, original_base in /var/lib/gitea/data/tmp/local-repo/pull.git132548841]: exit status 1:
2021/03/11 12:31:47 ...rvices/pull/patch.go:56:TestPatch() [E] CreateTemporaryPath: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1
2021/03/11 12:31:47 ...rvices/pull/check.go:220:handle() [E] testPatch[3468]: Unable to fetch origin base branch [Group/repo:master -> base, original_base in tmpBasePath]: exit status 1

Closing as dupe of https://github.com/go-gitea/gitea/issues/13884

I did have a look at #13884 however I did not see any errors relating duplicates (running gitea in dev mode)

I have found that the problem was that Gitea was searching for a nonexistent Issue:

[I] [SQL] UPDATE task SET repo_id = ?, status = ?, end_time = ?, errors = ? WHERE id=? [0 3<PHONE_NUMBER> issue does not exist [id: 0, repo_id: 202, index: 149] 102]

I created the issue ID 149 in Gitlab and then the migration succeeded.
So, it's not a duplicate entry issue

I investigated a bit further. The migration fails when there is a Gitlab merge request X but there is no Gitlab issue X.
By creating the Gitlab issue X the migration succeeds.
For example to create issues with a specific iid in Gitlab (say from #88 to #136):
for issue in seq 88 136 do   echo "Creating issue $issue"   curl --request POST \     --url https://gitlab.com/api/v4/projects/<Gitlab project ID>/issues \     --header 'content-type: application/json' \     --header 'private-token: <Gitlab API Token>' \     --data '{   	"title": "Empty issue for Gitea migration",   	"iid": "'"$issue"'"   }' done
The case of #13884  seems to happen when a merge request references an issue with the same id (not sure about this needs to be tested)

ok so it's something about our workaround for issue and pull have independend indexes on GL


[v2] Add support for adaptive mode retries

This adds a new experimental retry mode, adaptive, that adds
support for client side rate limiting based on receiving
throttling responses.  adaptive mode includes all the behavior
on standard mode.

Codecov Report

Merging #1973 into v2 will increase coverage by 0.05%.
The diff coverage is 96.53%.

@@            Coverage Diff             @@
##               v2    #1973      +/-   ##
==========================================
+ Coverage   92.55%   92.61%   +0.05%
==========================================
  Files          55       58       +3
  Lines       10322    10495     +173
==========================================
+ Hits         9554     9720     +166
- Misses        768      775       +7

Impacted Files
Coverage Δ

botocore/retries/throttling.py
100% <100%> (ø)

botocore/exceptions.py
99.44% <100%> (ø)
:arrow_up:

botocore/client.py
98.67% <33.33%> (-1.06%)
:arrow_down:

botocore/retries/adaptive.py
98.57% <98.57%> (ø)

botocore/retries/bucket.py
98.57% <98.57%> (ø)

botocore/credentials.py
98.54% <0%> (-0.11%)
:arrow_down:

Continue to review full report at Codecov.

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

Hi,
Thank you for this feature, it looks nice and advance.
I'm looking to do some testing for this new adaptive algorithm to see how better it is compare to various retry logic added through external packages (retries, retry or even custom code).
Is there a design document that outlines why it was implemented?
Roman


[BitSail] Migrate redis sink to v1 interface

Signed-off-by:
Pre-Checklist
Note: Please complete ALL items in the following checklist.

[x] I have read through the CONTRIBUTING.md documentation.
[x] My code has the necessary comments and documentation (if needed).
[x] I have added relevant tests.

Purpose

Some description about what this PR wants to do.
Approaches

Some description about how this PR achives the purpose.
Related Issues

e.g. Close #796
New Behavior (screenshots if needed)

N/A

[BitSail] Migrate redis sink to v1 interface.


Optional parameters with the C interface?

do we want to make sigma optional?  can this be done in a reasonable way?

It can easily be done if we would have a C++ interface. In the C interface I think this means we need to have multiple function definitions or hiding the C++ class interface (by a handle and then init, set, fit functions). So if you mean reasonable="short time" then the answer is no, if you mean longer time, then yes.
In the long run, the interface will surely evolve to something less "give me all the parameters" to "have a fit object, set some options, and go" a more object oriented/builder like approach.

Btw. it would be easy to have optional parameters in the external bindings (Python knows optional parameters and Matlab knows a variable number of parameters). So one question is if we need optional parameters also on the C side or only with the external bindings (lowest amount of effort for now) or if we want to evolve to a builder like interface anyway.

I think the solution with an additional function definition would be fine.

But in this case the interface functions must have different names. Do we want this?

This issue is the same as Issue #11

issue #11 was a bug, this here wasn't and also I expanded it to be about more than just the sigma parameter but about all optional parameters

I propose to have the following parameters optional:
sigma - if not given, an unweighted fit is assumed
parameters_to_fit - if not given, all parameters are assumed to fit
user_info - if not given, no user info is passed
And the way to not give them is passing in a null pointer for the respective values in the gpufit interface function. Maybe also re-order the parameter order and put first required input parameters, then optional input parameters, then output parameters.

I agree. Further optional parameters could be:

tolerance - if not given, it is set to a default value
max_n_iterations - if not given, it is set to a high default value like 100 or 1000

What is a reasonable default tolerance? Very small probably. I would suggest 1e-6
Reasonable max_n_iterations? 100
This would be more convenience though.

According to our meeting, optional parameters are
weights (null=ignored)
tolerance (0=1e-6)
max_n_iterations 0=(100)
estimator (0=LSE)
user_info (null=ignored)
In parentheses is (value indicating optionality, proposed behavior). Is this okay?

The current description of parameters_to_fit is:
If value is a null pointer, hold all parameters at initial value
Does this make sense? I would assume that typically one wants to fit all parameters rather than fitting none. I mean, why calling gpufit with a default argument, that doesn't do any fitting.
If no objection, I will change this behavior to the opposite.

I think the only optional parameters should be the arrays "weights" and
"user_info".  All other parameters are required for the C interface.
Optional parameters are FINE for the bindings, but for the C interface
they should be limited to weights and user_info.
On 23/01/2017 12:11, jkfindeisen wrote:

The current description of parameters_to_fit is:
If value is a null pointer, hold all parameters at initial value
Does this make sense? I would assume that typically one wants to fit all
parameters rather than fitting none. I mean, why calling gpufit with a
default argument, that doesn't do any fitting.
If no objection, I will change this behavior to the opposite.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/gpufit/GPUfit/issues/12#issuecomment-274460265, or
mute the thread
https://github.com/notifications/unsubscribe-auth/ADb8MWU8zCwpjll9OLpRmfw6Anb8j67lks5rVIrygaJpZM4Lk5hd.

Ok. That convinced me.
So, for the C-interface only weights and user_info is optional. For the external bindings more parameters are optional.

I adapted a test (https://github.com/gpufit/GPUfit/blob/master/tests/Gauss_Fit_1D.cpp) slightly to specify a NULL pointer as weights and user_info and it still passes. Therefore this issue can be closed.


note that Pipenv cannot publish packages

set clear expectations for the tool

Does pip make similar clarifications? I’m not convinced we need to start stating all the things we don’t do

People generally have a good understanding what pip does, and I find many having problems understanding what Pipenv is (I have no idea why they don’t, but they just don’t). Maybe it’s better to say Pipenv can be generally understood as a nice wrapper to use Pipfile with pip and virtualenv. This should give people a ballpark estimation of Pipenv’s goals.

Does pip make similar clarifications?

No it does not. But its description is "The PyPA recommended tool for installing Python packages" which does not really carry implications that it does.
Contrast that to what a person who encounters Pipenv for the first time might think:

Python Development Workflow for Humans.

"I do Python development and it sounds like this might be pretty all encompassing. I'm also a human, so I'll click the link".

Pipenv — the tool for managing application dependencies from PyPA, free (as in freedom).

"Oh okay a tool for managing application dependencies. Right now I have dependencies in requirements.txt and setup.py and it's kind of a pain. Wait, this isn't just a tool, it's the tool. And it's free, like every other Python infrastructure tool out there , but it also mentions that for some reason."

Pipenv is a tool that aims to bring the best of all packaging worlds (bundler, composer, npm, cargo, yarn, etc.) to the Python world. Windows is a first–class citizen, in our world.

"AMAZING! This is what I've been waiting for. The Pipfile probably looks like a package.json file or a Cargo file and allows me to publish to PyPI if I want, as well as generate a lock file. It's probably a well defined standard or generally accepted packaging format since Python is such a huge community. It must be a solved problem, and this must be it since it has 11k+ stars."

It automatically creates and manages a virtualenv for your projects, as well as adds/removes packages from your Pipfile as you install/uninstall packages. It also generates the ever–important Pipfile.lock, which is used to produce deterministic builds.

"Nothing about unifying dependences from setup.py into Pipfile, but maybe they're just saving that for later. Or maybe that is done in this Pipfile thing? Those other tools have unified their dependencies, and this is dependencies for humans."

The problems that Pipenv seeks to solve are multi-faceted:
You no longer need to use pip and virtualenv separately. They work together.
Managing a requirements.txt file can be problematic, so Pipenv uses the upcoming Pipfile and Pipfile.lock instead, which is superior for basic use cases.
Hashes are used everywhere, always. Security. Automatically expose security vulnerabilities.
Give you insight into your dependency graph (e.g. $ pipenv graph).
Streamline development workflow by loading .env files.

"Multi-faceted, huh? Sounds like it does a lot. Either way, I better use it, since it's the tool. I'm sure I can google around and figure out the best practice on how to publish with it, or at least have it generate setup.py files."

A reasonable person might expect this tool to be more than a nice wrapper around pip and virtualenv. And it is the responsibility of the developers to state all the things this tool doesn't do that a reasonable person might expect this tool to do.
I agree that

Pipenv: Python Development Workflow for Humans

would be better written as

Pipenv: A convenient wrapper around pip and virtualenv

And it would be better off if

Pipenv is a tool that aims to bring the best of all packaging worlds (bundler, composer, npm, cargo, yarn, etc.) to the Python world. Windows is a first–class citizen, in our world.

were omitted entirely, because those tools have more features.


Porting to OSX

I tried my best to port most of the Native functions to OSX.
List of ported fucntions
-ReadProcessMemory
-WriteProcessMemory
-EnumerateProcesses
-EnumerateProcessModulesAndSections (Sections are not ported)
List of not yet ported features
-Debugger.

not working on x86_64 Monterey


New version?

The latest version in git has a cabal file that says its version 2.1.0 (and which supports containers == 0.6.*), but the latest version on Hackage is 2.1.1 which does not support containers == 0.5.*.

Oh interesting. It seems that hackage people updated our package bounds. I'll push an update.

@erikd I maybe don't understand what the issue is with the containers bound. Could you explain a little bit what you mean?

I'll actually wait on pushing a new version until I understand what's going on with containers.

The contains bound on the version in git is containers >= 0.5  && < 0.7while the version in Hackage is containers ==0.5.*. Really just need a version on Hackage with the broader bounds.
A separate issue is the version number of the package in the cabal file. On Hackage the versions is 2.1.1    but in git is only 2.1.0. That usually happens when you do a new version on your machine, upload the package and forget to push you changes to githhub.
Finally, the Hackage maintainers did do a revision to you package, but that was simply to reduce the lower bounds on the base package.
This could be fixed in two ways. The best way would be for you:

Make a revision to the 2.1.1 version on Hackage fixing the containers bounds.
Pull the base update into your local git version.
Push your local changes to github.

Another less optimal way to fix this is, update your local git version by doing:

Make sure the bounds on containers is `>= 0.5  && < 0.7.
Make sure the bounds on base matches the revisions made by @hvr.
Bump the version number of prometheus (if nothing major has changed then 2.1.2 makes senses).
Makes sure everything works.
Upload the new version.
Push you changes to github.

I've already pushed 2.1.2. Check it out, and let me know what you think. That's what I'll be pushing.

@wraithm you should also fix the bounds on base to match https://hackage.haskell.org/package/prometheus-2.1.1/revisions/

I did.
On Thu, Jun 6, 2019, 17:33 Erik de Castro Lopo<EMAIL_ADDRESS>wrote:

@wraithm https://github.com/wraithm you should also fix the bounds on
base to match
https://hackage.haskell.org/package/prometheus-2.1.1/revisions/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bitnomial/prometheus/issues/26?email_source=notifications&email_token=AALRLUKIZYWOW4PUFU7NB2LPZGGE3A5CNFSM4HU2LSJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXELISY#issuecomment-499692619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALRLUM2T5O7SZXAEBIOPSDPZGGE3ANCNFSM4HU2LSJA
.

--

Note: This email is for the
confidential use of the named addressee(s) only and may contain
proprietary, confidential or privileged information. If you are not the
intended recipient, you are hereby notified that any review, dissemination
or copying of this email is strictly prohibited, and to please notify the
sender immediately and destroy this email and any attachments.

Ah you are right. Never mind me.
Gimme a sec and I can add some CI so that we at least build this with a bunch of different GHC versions.

That'd be great! Thanks.

I think its ready for a new version of Hackage now. I will do the CI thing over the next couple of days :).

Okay, I've uploaded 2.1.2. Let me know if that works for you.

Well cabal solved the version contstraints, so yes :). Thanks!


NO-ISSUE: Make the weekly Jenkins job build all images

This PR updates the weekly Jenkins job to build all imagens instead of only building the kogito-base-builder image.

PR job #19 was: UNSTABLE
Possible explanation: This should be test failures
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/19/display/redirect
See console log:

Console Logs
[Pipeline] unstableWARNING: Tests on kogito-data-index-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1769 - kogito-data-index-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1769 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-data-index-postgresql seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1769 - kogito-jit-runner: https://github.com/apache/incubator-kie-kogito-images/pull/1769 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jit-runner seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1769 - kogito-jobs-service-ephemeral: https://github.com/apache/incubator-kie-kogito-images/pull/1769 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-ephemeral seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1769 - kogito-jobs-service-allinone: https://github.com/apache/incubator-kie-kogito-images/pull/1769 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-allinone seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image PR #1769 - kogito-jobs-service-postgresql: https://github.com/apache/incubator-kie-kogito-images/pull/1769 completed: UNSTABLE[Pipeline] unstableWARNING: Tests on kogito-jobs-service-postgresql seems to have failed[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/19/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh

@tiagobento @rodrigonull please take a look at this stack trace first: https://github.com/apache/incubator-kie-kogito-images/actions/runs/9207108567/job/25326408974?pr=1769

The dsl-tests are failing due to an issue in the pipelines-framework. There is a draft PR that should fix the problem: https://github.com/apache/incubator-kie-kogito-pipelines/pull/1205
I think it's safe to merge this PR.

PR job #20 was: ABORTED
Possible explanation: Most probably a timeout, please review
Please look here: https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/20/display/redirect
See console log:

Console Logs
Build KIE » kogito » main » pullrequest » kogito-images.build-image #94 completed: ABORTEDBuild KIE » kogito » main » pullrequest » kogito-images.build-image #92 completed: ABORTEDBuild KIE » kogito » main » pullrequest » kogito-images.build-image #93 completed: ABORTED[Pipeline] }[Pipeline] }Build KIE » kogito » main » pullrequest » kogito-images.build-image #98 completed: ABORTEDBuild KIE » kogito » main » pullrequest » kogito-images.build-image #97 completed: ABORTED[Pipeline] // stageBuild KIE » kogito » main » pullrequest » kogito-images.build-image #95 completed: ABORTEDBuild KIE » kogito » main » pullrequest » kogito-images.build-image #96 completed: ABORTED[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-ephemeral[Pipeline] }Failed in branch kogito-jit-runner[Pipeline] }[Pipeline] }[Pipeline] }[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] }Failed in branch kogito-base-builder[Pipeline] // stage[Pipeline] // stage[Pipeline] }Failed in branch kogito-jobs-service-ephemeral[Pipeline] }Failed in branch kogito-jobs-service-postgresql[Pipeline] // stage[Pipeline] // stage[Pipeline] }Failed in branch kogito-data-index-postgresql[Pipeline] }Failed in branch kogito-jobs-service-allinone[Pipeline] // parallel[Pipeline] }[Pipeline] // dir[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] script[Pipeline] {[Pipeline] sh+ wget --no-check-certificate -qO - 'https://ci-builds.apache.org/job/KIE/job/kogito/job/main/job/pullrequest/job/kogito-images.build-and-test/20/api/json?depth=0'[Pipeline] readJSON[Pipeline] sh


can't install mxnet-cu101mkl

Description
I install mxnet-cu101mkl using the command pip install but a error occured, the error said that no matching distribution found for mxnet-cu101mkl.
Environment info (Required)
windows 10 professional 1809
minconda
Package used (Python/R/Scala/Julia):
I'm using python 3.6.8
Error Message:
ERROR: Could not find a version that satisfies the requirement mxnet-cu101mkl (from versions: none)
ERROR: No matching distribution found for mxnet-cu101mkl
Attention
even though I can't install mxnet-cu101mkl using command pip install , I can install mxnet-cu101 easily by using the command pip install.

Hi,
we currently don't publish pip packages for Windows that frequently. Could you try building MXNet yourself?

@szha on https://pypi.org/project/mxnet-cu101/1.4.1/ we state that this package supports Windows. Wasn't there somebody from China who publishes them?

@yajiedesign is maintaining it.

@mxnet-label-bot add [Pip, WIndows, MKL]

Hi,
we currently don't publish pip packages for Windows that frequently. Could you try building MXNet yourself?

Thank for answering my question, I would rather to wait for it to be puplished instead of building mxnet by myself.

i will fix it

i will fix it

Thank you very much! When you finish fixing it, please let us know about that. Thank you~~~~

 pip install mxnet-cu101mkl already working on windows. @szha can we close this issue?

@bgawrych thanks!


How can we automate distribution of the download URL from an internal/preview build?

I'd like to automatically send out a download URL of a build once it's finished. Is there a programmatic way to get the build ID that's autogenerated with each build? This would be helpful for creating the final URL which uses the build ID as the path.

You can use --json and --non-interactive flags to achieve this.
https://github.com/expo/eas-cli?tab=readme-ov-file#eas-build

@szdziedzic just to double check, there's no way to do this automatically via Expo/EAS, right? i.e. configuring somewhere (or via the cli) that when a build is finished, the link is sent automatically via email to the stakeholders.

@dani-mp You can use our email notifications https://expo.dev/accounts/[your-account-name]/settings/email-notifications or use webhooks for that https://docs.expo.dev/eas/webhooks/. I believe it should solve for your use case.


Cut 0.30.2

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
This pr cuts v0.30.2 to include https://github.com/thanos-io/thanos/pull/6066.
Verification

Do we want to also include https://github.com/thanos-community/promql-engine/pull/163 ?

Do we want to also include https://github.com/thanos-community/promql-engine/pull/163 ?

Is this a bug introduced in v0.30.x? Since we haven't merged it I'd prefer to have it in next release.


Plugin tests do not run when building the tests with a pre-installed PDI

The plugins are not found because LD_LIBRARY_PATH is not set. We should add a wrapper for that.

mentioned in commit a8019cf75f34be10a148bd89d5907891b653e46e

mentioned in commit c0ae4b6b3b24ccbd3a0e0cff8480c7017377c093

mentioned in commit 7382e5f29d2efcd8c8a29852c48f9fceae61e769

closed via merge request !245

mentioned in commit 1a0d7a4f6fa9c753af101530898d4b81eb5b152b


feat(faqs): translation keys

LiveURL: https://smartfaq-faq-articles-translations.surge.sh

moved to gitlab.


feat: allow mounting local folders into the emulator

Provide support to mount local folders into the VM using the FilesystemAccess API. This PR exposes a new method to mount these folders into the emulator.

Duplicated.


Flexbox

I was a little surprise to find no flex box mixins anymore in Bourbon 5 - what's the reason?

Hi @mmjaeger. See here: https://github.com/thoughtbot/bourbon/issues/702.


Fix HTMLHyperlinkElementUtils pathname setter to update the href

Fixes the issue that changing the pathname of an HTMLAnchorElement
didn't update the href.

Thanks! Can you add a test, so that we can accept this? See contributing.md for instructions.

Hi @domenic ,
sorry for not adding a proper test.
I added the url/url-setter web platform test and fixed several more issues.
I'm not entirely sure about the removed javascript scheme check in the hash setter, but that's what the tests expect and how the browsers behave.
The test passes, Travis failed with time outs.

Thanks, that's really great work. I'll try to merge this as soon as possible.
A bonus would be if you could check that your changes match https://html.spec.whatwg.org/multipage/semantics.html#api-for-a-and-area-elements. I know we haven't kept up to date with all those changes.

Hi @domenic
according to the specs this is the result.


App crashed when clicked on "Analyze Random Audio Clip"

Hi Nick,
Thanks for building this reference app. I have little experiences with Apple's development toolchain so having a workable reference app is very helpful to me.
I managed to build and run this app on my iPhone, but I have some question using it.
When I open the application, I don't see anything classification results despite that I was making various kind of sounds. The only clickable button is "Analyze Random Audio Clip". When I click on it, the following crash appears.
Any thoughts or suggestions?
Thanks,
Thread 1: Fatal error: Failed to schedule file at file:///private/var/containers/Bundle/Application/2D555890-8AF0-4CB8-9E2C-7C5F5EDB6EE4/ESC10-CoreML-Demo.app/dogs.wav: Error Domain=com.apple.coreaudio.avfaudio Code=1954115647 "(null)" UserInfo={failed call=ExtAudioFileOpenURL((CFURLRef)fileURL, &_extAudioFile)}

@xianbaoqian I believe this is a codec issue, try replacing the test wav files with some audio files that you can open on your machine. It worked for me

Thanks Nina. I'll give it a try!


other-reprs: Null-pointer-optimized enums are FFI safe unless repr(C)

See also the improper_ctypes lint, specifically is_repr_nullable_ptr in
src/librustc_lint/types.rs.

Actually the more I read the code, it looks like the improper_ctypes lint considers it FFI-safe to have an enum with #[repr(C)] or #[repr(uN)], as long as all variants contain FFI-safe data. Presumably the layout is effectively struct SomeEnum {uintN_t discriminant; union { ... } data;}; or so.
But the nomicon is claiming that "tagged unions ... are never FFI safe." Should this text be fixed, or is "tagged union" intended to mean something other than an enum with data?

They aren't yet FFI-safe, but they should probably be made so.

Enums are tagged unions, so this feels a bit weird, I would phrase it as something like "adds the tag back in" or something, dunno.

This is way too much information to squish into a single-sentence aside.
To be clear, OptionLike<u32> isn't FFI-safe, but OptionLike<&T> absolutely must be (same repr as *const T). It's possible OptionLike<Box<T>> is too, but it's unclear to me whether FFI'ing boxes is a very good idea.

@Gankro I have used it in the past. It's useful for passing ownership to and from C.

They aren't yet FFI-safe, but they should probably be made so.

@ubsan What needs to be done to make this happen?
In particular, if they're not yet FFI-safe, then it seems to me that the improper_ctypes lint should be fixed to align with the current state of things.

To be clear, OptionLike<u32> isn't FFI-safe, but OptionLike<&T> absolutely must be (same repr as *const T). It's possible OptionLike<Box<T>> could be too, but it's unclear to me whether FFI'ing boxes is a very good idea.

FWIW the improper_ctypes lint currently warms about both Option<i32> and Option<Box<i32>>, but not about Option<&i32>.
I've pushed some slightly longer text that phrases this as Option being a specific special case. ("subject to the null pointer optimization" and "is defined like Option, including repr(rust)" are synonyms, right?) I agree that making Box FFI-safe is useful, but it seems reasonable not to promise that yet.

@geofft basically, define the layout of
#[repr(INT_TYPE)]
enum Foo {
  T0(...),
  T1(...),
   ...
}

to be
struct Foo {
  enum Foo_tag: INT_TYPE {

  } tag;
  struct { ... } T0;
  struct { ... } T1;
  ...
};

or something of that order

I suspect that's what its representation is right now - what needs to be done process-wise to formalize this? Would this be an RFC or something?

@geofft not sure. Probably an RFC, but also I'd like to note that the representation of the specific union members isn't specified, so you'd have to figure that out as well.

Thanks!


Cut release v0.34.0

Building at https://github.com/KittyCAD/modeling-app/actions/runs/12421198233

Manual test tasklist: macOS

[ ] The application opens
[ ] User can sign in
[ ] The onboarding can be replayed and looks solid
[ ] A project can be created
[ ] A sketch can be draw (line, arc, rect, circle).
[ ] Lines and shapes can be modified.
[ ] Select face and extruding works.
[ ] Reloading the application works.
[ ] Can create additional files and directories.
[ ] Models can be exported to a file.
[ ] I repeated some code done with point-and-click by typing in the code editor and everything was responsive and ok.
[ ] Double clicking a KCL file opens ZMA, and with the CLI too on project directory or file
[ ] Offset plane can be created and shows up
[ ] The auto-updater works.

Manual test tasklist: Windows

[ ] The application opens
[ ] User can sign in
[ ] The onboarding can be replayed and looks solid
[ ] A project can be created
[ ] A sketch can be draw (line, arc, rect, circle).
[ ] Lines and shapes can be modified.
[ ] Select face and extruding works.
[ ] Reloading the application works.
[ ] Can create additional files and directories.
[ ] Models can be exported to a file.
[ ] I repeated some code done with point-and-click by typing in the code editor and everything was responsive and ok.
[ ] Double clicking a KCL file opens ZMA, and with the CLI too on project directory or file
[ ] Offset plane can be created and shows up
[ ] The auto-updater works.

Manual test tasklist: Ubuntu

[ ] The application opens
[ ] User can sign in
[ ] The onboarding can be replayed and looks solid
[ ] A project can be created
[ ] A sketch can be draw (line, arc, rect, circle).
[ ] Lines and shapes can be modified.
[ ] Select face and extruding works.
[ ] Reloading the application works.
[ ] Can create additional files and directories.
[ ] Models can be exported to a file.
[ ] I repeated some code done with point-and-click by typing in the code editor and everything was responsive and ok.
[ ] Double clicking a KCL file opens ZMA, and with the CLI too on project directory or file
[ ] Offset plane can be created and shows up
[ ] The auto-updater works.

Released now