yarn install warnings

When doing a yarn update a few warnings are being emitted for this module. It would be good to clean those up if possible.
lib/module/soundcraft-ui/
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "soundcraft-ui-connection ><EMAIL_ADDRESS>has unmet peer dependency "ws@*".
[4/4] Building fresh packages...
success Saved lockfile.
$ yarn build
$ rimraf dist && yarn build:main
$ tsc -p tsconfig.build.json

package-lock.json should not be present as that is for npm, and companion enforces the use of yarn.
The unmet peer dependency may or may not be something that should be resolved. It probably should, but there could be a reason it has not been

Additionally, the yarn update is generating some yarn.lock changes, so an updated version should be committed

Ah yes, thank you for pointing this out. I used NPM, in fact... 🤦🏻♂
I don't get why the peer dep warning appears since soundcraft-ui-connection has ws installed: https://github.com/fmalcher/soundcraft-ui/blob/main/package.json#L52


CDATA missing stripped in google scripts

Hello,
i noticed, that google remarketing and conversion have CDATA in their scripts. The minify tool strips the CDATA comment Tags and therefor not all browsers have a correct way to use those tags. This is the code that comes from google:
<script type="text/javascript">
    /* <![CDATA[ */
    var google_conversion_id = xxxxxxxxx;
    var google_custom_params = window.google_tag_params;
    var google_remarketing_only = true;
    /* ]]> */
</script>

But after compression there is only this left:
<script type="text/javascript" >var google_conversion_id=xxxxxxxxx;var google_custom_params=window.google_tag_params;var google_remarketing_only=true;</script>

Is there a way to get the missing CDATA fields that are necessary for the googlescripts to work properly?
Thanks in advance.

CDATA declarations aren't necessary unless you're serving XHTML as XML, and almost no one's doing that anymore. If they are, Minify_HTML already handles this: https://github.com/mrclay/minify/blob/2.x/min/lib/Minify/HTML.php#L239
See the constructor option: https://github.com/mrclay/minify/blob/2.x/min/lib/Minify/HTML.php#L64

Maybe it is not necessary but Google Tag Assistan throughout errors about it.
Missing CDATA comments
https://support.google.com/tagassistant/answer/2978937?hl=en#cdata_comments


Added Is Graph Bipartite?

Added Solution to problem 785. Is Graph Bipartite? on LeetCode

I would be glad to contribute my solutions!


Implement Dropdown & DropdownField; Misc. refactoring

Per #71 , this PR implements the Select and SelectField to support composition for a composition demonstrated in the story below.
Select Composition - Collapsed

Select & SelectField Composition - Expanded

Unit Test Status
PASS  src/__tests__/Select.js
PASS  src/__tests__/SelectField.js
...
File                      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
Select.js             |          100 |          100 |          100 |         100 |
SelectField.js     |          100 |          100 |          100 |         100 |

Codecov Report

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

@@          Coverage Diff          @@
##           master   #141   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          31     33    +2
  Lines         276    294   +18
=====================================
+ Hits          276    294   +18

Impacted Files
Coverage Δ

src/Label.js
100% <ø> (ø)
:arrow_up:

src/Banner.js
100% <ø> (ø)
:arrow_up:

src/Card.js
100% <ø> (ø)
:arrow_up:

src/SelectField.js
100% <100%> (ø)

src/Select.js
100% <100%> (ø)

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 fcb154b...54d3dff. Read the comment docs.

@jxnblk,
Thanks for your first round of review. Updated and/or replied your comments. Please review again and see if the updates look okay?

@jxnblk , thanks for the 2nd round of review and suggestion/encouragement for more improvements for Bootstrap pattern & ARIA support. Please review again at your convenience.
The updated PR has taken inspiration of the Bootstrap Single button dropdowns:

Dropdown,

DropdownButton- with more defined tag attributes such as type="button"

DropdownMenu

DropdownItem

ARIA support with aria-expanded, aria-haspopup, aria-labelledby

@BeniCheni @jxnblk
hi, how's it going with this PR? We have plan to use it in this sprint. Any update?

@jinchi2013, I've been allocated to other projects that don't required the Dropdown immediately. So I couldn't spend much time following up my own WIP progress. Please don't depend your sprint plan on this WIP version of the Dropdown. Hope you can find a plan B not to depend on this WIP Dropdown.

@jinchi2013 can you elaborate on the requirement? This PR for the Popover might be close to ship, and I imagine it might eventually be used for the Dropdown component #223

@jxnblk  here is it

@jinchi2013 For the Add a Hotel part, I think that should be the Select component for accessibility reasons. You won't have the same look as the mockup above, but I think that should be fine.
The Dropdown/Popover is more for modal things that break out of the document flow and contain buttons, menus, etc. – like the TravelerSelection or the Calendar components

@jxnblk OK, got you, will discuss this will Jake. Thanks

Since the scope changed in the project that was going to adapt the dropdown component, closing this PR as no further update to complete this WIP PR>


(A.2)review fastapi tutorial and make sure it includes the correct implementation. (include the testing and async testing things)

not completed.


Added support for non-type template support for literals.

Description
This is a fairly minimal, but effective patch to add non-type template support for literals.
Literals include:

Integers
Characters
Booleans
Floating point numbers.

Implementation
The implementation is quite simple, as it adds one new function, analyse_as_template_parameter, which is called rather than analyse_as_type. This function defaults to analyse_as_type, however, for literal values, it is overrided to create a TemplatePlaceholderType containing the resulting C-code. This creates valid code, and adds no major syntax changes.
Example
example.h
template <int N1, int N2>
int function() { return N1 + N2; }

example.pyx
cdef extern from "example.h" nogil:
    int function[N1, N2]()

def test():
    assert function[3, 5]() == 5

General Discussion
Although I wanted to add patches from @insertinterestingnamehere, who added previous patches to allow the use of variables in template parameters and which would work for some non-type template parameters, I was unable to use his patches since Cython fundamentally lacks the concept of constexpr, although it closely mimics it with const. Furthermore, functions and function pointers (CFuncType) cannot be declared const, which would allow the compiler to know they are constexpr.
For example, the following code would be valid on the Cython-end, however, it would produce invalid C++ code without any use-friendly error. Example code is as follows:
example.h
template <int(*p)(int)>
int function(int a)
{
    return p(a);
}

example.pyx
cdef extern from "example.h" nogil:
    int function[T](int)

cdef int p(int a) nogil:
    return a + 2

def test():
    cdef int a = 2
    cdef int(*func)(int)
    func = p
    assert function[func](a) == 2

Since func is mutable, and not constexpr, it cannot be used as a template parameter.
Rationale
This is necessary for some of my patches to add comprehensive C++11 and later support, and adds a simple syntax for basic non-type template support.

I realize this is a fairly large commit, so any comments from @scoder or @robertwb would be highly appreciated for me to ameliorate this pull request. Thank you.

Nice. It seems a bit of an abuse of TemplatePlaceholderType to hold a literal C value. Also, it would be good to type (and typecheck) the parameter (e.g. declare cdef cppclass UnaryPlus[T, T N=*]).

@robertwb Good idea, I could create a type-like class that would be a TemplateParameter rather than a TemplateParameterType and could accept a type as an argument.
Also, great idea on the type signatures, more work, but definitely a useful feature. I'll look at add said functionality.

Also adding a quick reminder for #426.


mobile: Avoid rendering on background

Crashlytics says:

Based on the stack trace displayed here, it looks like new calls triggering OpenGL rendering took place while the app was transitioning to, or from, a background state. If you set up OpenGL drawing in your app delegate's methods, make sure that you only did so in applicationDidBecomeActive:, never in application:willFinishLaunchingWithOptions: or application:didFinishLaunchingWithOptions:. According to some reports, even displaying an FPS indicator for SpriteKit could cause rendering to occur before it is allowed.
External resources

Strategies for Handling App State Transitions
Apple Technical Q&A QA1766
Stack Overflow: OpenGL ES crash on move background, iOS 5.1
Multitasking, High Resolution, and Other iOS Features

There is nothing Ebiten can do, but the example should be improved.

Looks like this error was reported from old iOS machines (e.g., iOS 9)?

This was reported by iOS 10.12


Why C?

Interesting choice to use C to handle building the page. What was the thinking behind it? Why not write all the pages in HTML?

If we write all the content directly in html, we still need to go through all 50 pages to change the navigation, and copy the content over the RSS, and write all the jump links by hand which is a monumental task. So, we decided to automate a few things using C, it was also a pretext to learn the language.

Thanks. I came across the code and was pretty intrigued by th

Exactly, I also use plan9 quite a bit and I wanted to have the option of building the site from it. The only languages supported on the platform at the moment are C and plan9.

What are your thoughts on Go? I started the path to learning C years ago and found Go to be much easier to use. Though, I do like the bare-bones aspect of C. The langauge makes me think. I'm also happy to take this conversation off GitHub.

Go is alright, I like that is abstracts some of the things of C, and make working with strings easier. But the convenience that comes with Go, also has some downside, like you said, you don't have to think as much. Nowadays I mostly do 6502 assembly code, and that really makes me thing and I've learnt to love the pain of having to think again. So I'll stick to C for now, maybe learn some forth in the future :)
This is a fine place, maybe someone else stumbles on this someday looking for the same answers as you.

Nowadays I mostly do 6502 assembly code, and that really makes me think and I've learnt to love the pain of having to think again. So I'll stick to C for now, maybe learn some forth in the future :)

Very cool. I'm sure you don't want to dive too much into C++, as that's a language with too many features and weight behind it, which probably goes against your ethos of simplicity and functionality.


Regenerate non-HRV intermediate Zarr with larger extent (especially on the y-axis)

New Zarrs are being created that have the whole spatial extant, so closing this now.


SpeedTest support config_flow entry

Breaking Change:
SpeedTest Integration now supports config_flow. monitored_conditions are removed and instead entities can be disabled using Entity Registry.
Also minimum scan_interval is set to 1 minute if imported from config.yaml
Description:
Configure SpeedTest through config flow and control added entities using the Entity Registry.
Options include:

Setting Server ID
Change Update Interval (in minutes)
Enable Manual update only

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):
speedtestdotnet:
  scan_interval:
     minutes: 60
  manual: True
  server_id: 2234

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

I have one concern regarding the server_id. Is it possible to set the server_id option to blank if configured as int? This is because if no server_id is configured the SpeedTest integration can detect the best server. But I am not able to save the options form without specifying a value for the server_id.

This PR seems to have gone stale. Closing it.


Implement Fromstd::str::Utf8Error and Fromstd::string::FromUtf8Error

Closes #582

Interesting it broke the staking contract (which seemed to have not specified the error type in update closure). Did that work on master? Odd. It needed to be updated anyway I guess.

Super strange. I try to reproduce locally now. I assume this a caching error that results from the branching and backporting to 0.11.

We can also just merge this into master. I don't need anything more in 0.11, this is all just nice to haves. And if merging into master is easier, let's just do that

Ah, here we go: 8de794f. This change is in our migration guide already. Seems like without converters to StdError, the compiler could infer a few more cases.


Detect When An OS X User Has Launched Atom From A launchd Launched Process

Includes:

Finder
Spotlight
Dock
open

We need to detect this so that we can take action to patch the environment for these users, ideally using their shell's environment.

If PATH is equal to "/usr/bin:/bin:/usr/sbin:/sbin" on OS X 10.10, this indicates Atom was launched from a launchd launched process.

/cc @leedohm.

If PATH is equal to /usr/bin:/bin:/usr/sbin:/sbin on OS X 10.10, this indicates Atom was launched from a launchd launched process.

Is that still the case? Only when I did a fresh install recently the default PATH was prefixed with /usr/local/bin: as cat /etc/paths reveals
/usr/local/bin
/usr/bin
/bin
/usr/sbin
/sbin

and that was before any Homebrew installation.

I know this to be true on my machine and @lee-dohm 's machine. Happy to take reports from others, of process.env.PATH when launched via the Dock, Finder, Spotlight, or open.

Actually I get /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin. Iv'e no idea how/why /usr/local/bin gets moved to the end.
I normally have a bunch of stuff in my ~/.bash[rc/_profile] that sets the PATH which I disabled to test this.
What's the exact goal of this package?
Also looks very similar to env-from-shell.


Be able to remove haxelib project

By accident I added this lib http://lib.haxe.org/p/Bar but I really want it to be removed. How can this be done?

this would indeed be useful to be able to remove things

I would like to do this, or at least be able to flag a library as deprecated/renamed

I think I could implement that, but what's the official position on adding stuff to haxelib? I saw some PRs where @jasononeil and @back2dos were talking about about reworking the architecture before adding new commands, but it's 2015 now and we're still sitting on the same codebase. I'd say, let's just add missing things in the current arch and think about rewriting the whole thing later, when someone comes up who is willing to take the job.

There are no official positions in this project I'm afraid. Mine is that
removing should not be allowed, only hiding from search, etc. Also, the
client code is quite a mess as it is, I prefer adding as little as
possible. The necessity for this feature arises every two months or so.
Generally I have handled this by hand. I don't know how well the site is
moving along, but this kind of administrative stuff should go there.
On Sun, Mar 8, 2015 at 1:43 PM, Dan Korostelev<EMAIL_ADDRESS>wrote:

I think I could implement that, but what's the official position on adding
stuff to haxelib? I saw some PRs where @jasononeil
https://github.com/jasononeil and @back2dos
https://github.com/back2dos were talking about about reworking the
architecture before adding new commands, but it's 2015 now and we're still
sitting on the same codebase. I'd say, let's just add missing things in the
current arch and think about rewriting the whole thing later, when someone
comes up who is willing to take the job.
—
Reply to this email directly or view it on GitHub
https://github.com/HaxeFoundation/haxelib/issues/168#issuecomment-77746786
.

At the moment I've focused on the site providing a better experience for
discovering and learning about projects.
I do intend to add some project management features though.  I was mostly
thinking about password resets, but deprecating projects is probably
important too.  I agree it's probably easier to manage through the web
interface than yet another command on the haxelib client.
On Mon, Mar 9, 2015 at 4:26 AM, Juraj Kirchheim<EMAIL_ADDRESS>wrote:

There are no official positions in this project I'm afraid. Mine is that
removing should not be allowed, only hiding from search, etc. Also, the
client code is quite a mess as it is, I prefer adding as little as
possible. The necessity for this feature arises every two months or so.
Generally I have handled this by hand. I don't know how well the site is
moving along, but this kind of administrative stuff should go there.
On Sun, Mar 8, 2015 at 1:43 PM, Dan Korostelev<EMAIL_ADDRESS>wrote:

I think I could implement that, but what's the official position on
adding
stuff to haxelib? I saw some PRs where @jasononeil
https://github.com/jasononeil and @back2dos
https://github.com/back2dos were talking about about reworking the
architecture before adding new commands, but it's 2015 now and we're
still
sitting on the same codebase. I'd say, let's just add missing things in
the
current arch and think about rewriting the whole thing later, when
someone
comes up who is willing to take the job.
—
Reply to this email directly or view it on GitHub
<
https://github.com/HaxeFoundation/haxelib/issues/168#issuecomment-77746786

.

—
Reply to this email directly or view it on GitHub
https://github.com/HaxeFoundation/haxelib/issues/168#issuecomment-77772161
.

I agree in general a project should not be removable, since it could break projects which already depend on it. Deprecating the project by submitting a new release with deprecation note with a "deprecated" tag should be good enough.
Exceptional cases, like those are pure mistakes and we've high confidence that no one depends on them, can be removed by request.
So, yeah, I've just removed the "Bar" lib.
I'm keeping this open until we document the deprecation/removal process.

I think the develop has the "right" to remove it even it is depended on by other users?
And I think it is really the lib developer's responsibility to communicate with its user about the removal.

I don't think so. All code published on haxelib is published under a free license, whereby the author relinquishes any kind of ownership from which such a right might stem. The author can't tell you to uninstall the library locally. In fact even if the author had the technical means to remove the code from haxelib, they can't stop you from submitting it yourself.
Since we have no obligation to allow authors to remove code from haxelib, I think we can use that to provide a more reliable eco system (than for example NPM, where hell can break lose because one guy doesn't get to be the princess).
Haxelib should be basically insert only and we should follow that through by disallowing to modify existing versions.

by disallowing to modify existing versions

Strongly in favor of that. Being able to re-release the same version again is a recipe for disaster (because then you can't actually tell what version of the version you have...).

So, the conclusion is: don't allow users to remove projects from haxelib. For deprecation feature see #312

Maybe we can do something simple to prevent accidental submissions? A big fat, red warning text saying that a library cannot be deleted once added? Make the user type the full name of the library to confirm?

Yeah, something like confirmation prompt should decrease accidents rate.


Custom name for some props of ValidationProvider while using HOC

Hello,
I'm wondering if maybe we could pass an argument to the withValidation method to rename some of ValidationProvider props.
In my example, i'm wrapping a FieldRadios component that has a "name" property, so, it is overlapping with the "name" property of ValidationProvider.
Maybe we could change the "name" property of ValidationProvider to another property name with some arguments to the withValidation function. I don't know if it's possible and easily feasible so i'm asking.
Something like this :
const VFieldRadios = withValidation(
  FieldRadios,
  {
    name: 'vee-name'
  },
  ({ errors }) => ({
    'error-messages': errors
  })
)

and then i call use my VFieldRadios like that :
<VFieldRadios
  vee-name="veeName"
  name="namePropPassedToFieldRadios"
/>

Thanks !

I add that the "name" property is not even passed to the FieldRadios wrapped component like said in the documentation. Is it a bug, or maybe i did something wrong?

One of the downsides of HoC is props clashing, so I doubt I will change anything about it since it can easily happen to any prop and isn't really a solution.
The props that get passed to your component are:
const props = assign({}, this.$attrs, { [prop]: model.value }, ctxToProps(vctx));

Which translates to: The v-model prop, any props mapped by the ctx fn, and any unidentified Provider props. You can use that to your advantage by letting your component use another name than name and use it.
Alternatively, You could wrap it manually in your component which will allow you to distribute props.


feat: use section instead of column

Fix #135
Test URLs:

Before: https://main--mammotome--hlxsites.hlx.page/en/miroslav/columns
After: https://135-columns-with-cards--mammotome--hlxsites.hlx.page/en/miroslav/columns

Authoring:

after discussions, we have found a simple solution as reflected in https://github.com/hlxsites/mammotome/pull/140 - this PR will not be needed at this time. solution is to use columns and auto-blocking to identify images with an image-cards parenthesis.


wip: compare dev branch to feat/no_build_env

This PR is to keep track of comparing all the examples in this repository with the changes in tauri-apps/tauri#850.  I'll mark the current commit the branch is on when tested.
Legend:

Icon
Meaning

❓
Not tested yet

❔
Won't be tested

❌
Fails to build/run

⚠
Builds and runs, but looks wrong

✔
Everything looks ok

All the examples should match their dev version.  In case of ⚠, if the feat/no_build_env build runs/looks the same, it is fine and will be marked also with ⚠.  In the case that it is broken/looks wrong in a different way,  it will be marked ❌.

Example
dev
feat/no_build_env
Commit/Notes

nodereact/create-react-app
✔
✔
https://github.com/tauri-apps/tauri/pull/850/commits/ab338d0ec254e3431ffb936703ea611319fd51fa

nodereact/gatsby-themed-site
⚠
⚠
https://github.com/tauri-apps/tauri/pull/850/commits/32a007fd996e796331c8fe4c2677fe8a6ec5f3ad Text and styles load fine, but there is a 500 error loading http://<IP_ADDRESS>:8453/page-data/articles/page-data.json from the embedded server on both branches.

nodereact/next.js
✔
✔
https://github.com/tauri-apps/tauri/pull/850/commits/9ab6f040e3774a003ec04285d906b2a795555dd4

nodesvelte/svelte-app
✔
✔
https://github.com/tauri-apps/tauri/pull/850/commits/9ab6f040e3774a003ec04285d906b2a795555dd4

nodevanillajs/monolith
✔
✔
https://github.com/tauri-apps/tauri/pull/850/commits/9ab6f040e3774a003ec04285d906b2a795555dd4

nodevue/nuxt-app
❌
❔
Blank window hangs.  Edge DevTools doesn't detect it as a window yet, cannot debug.  (perhaps too large a payload?)

nodevue/quasar-app
✔
✔
https://github.com/tauri-apps/tauri/pull/850/commits/9ab6f040e3774a003ec04285d906b2a795555dd4 Added build key to Cargo.toml as the file existed but wasn't being referenced.  feat/no_build_env requires a build script to be present so that OUT_DIR env var is set, but this can be changed by changing where the default output directory is for gzipped embedded assets.

nodevue/vue-cli-app
❌
❔
No executable is built, so the build fails when bundling with WiX.  Will come back to this item

rustyew/todomvc
❌
❔
thread 'main' panicked at 'Yew does not allow the `web_sys` and `std_web` cargo features to be used simultaneously

tauricommunication
⚠
⚠
https://github.com/tauri-apps/tauri/pull/850/commits/9ab6f040e3774a003ec04285d906b2a795555dd4 Outdated frontend code still uses window.tauri instead of window.__TAURI__ so the actual application is broken.  It still builds and runs the webview fine in both branches.

transpiledflutter_example
❔
❔
don't have the deps + it's not tested in CI

transpiledmint-tauri-starter
❔
❔
don't have the deps + it's not tested in CI

transpiledreason-react
❔
❔
don't have the deps + it's not tested in CI

the checks pass but there are a number of examples that either I can't build or are broken. I've found no difference of behavior so far though.

closing this cause it's too out of date to be worth merging, and not necessary anymore


Add warning about publicly exposing usernames.

Hi! Awesome work with this plugin, we use it all the time and it works superbe!
I have just one suggestion: add a notice to the top of the readme, wiki and atlassian-plugin-page that warns administrators that by default, usernames will be exposed to the public. Maybe something along the lines of:

Be aware, this plugin publicly exposes some sensitive data by default. The metrics page exposes the username of who last logged in, who last edited issues in every project and some more usernames. You should enable token protection to make sure the public cannot view usernames.

Will do


Removed old modules and pushed them into separate folder

Archived all old modules into a separate "archived" folder for reference. Backend and frontend folders should only house current services and should be clean.

removed that archived folder and tagged them as
https://github.com/egovernments/DIGIT-Works/releases/tag/works-archived-0.1


Youtube playlist search

Describe the bug
If you search youtube playlist that starts with https://www.youtube.com/playlist?... it wont count as playlist

play-dl cant search by links you need to pass playlist id instead of full link
by searching playlist with playdl.search() it cant get all videos in it but it works with playdl.playlist_info()

Reproduction
Try to add youtube playlist
System Info
Binaries:
    Node: 18.7.0 - /usr/bin/node
    npm: 8.15.0 - /usr/bin/npm
  npmPackages:
    discord-player-plus: ^1.1.1 => 1.1.1
    discord.js: ^14.0.3 => 14.0.3

Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Hey, thanks for reporting the issue! Its now fixed. It can now search playlist that starts with https://www.youtube.com/watch and https://www.youtube.com/playlist.
Regarding the number of tracks, note the following: YouTube handles /watch and /playlist links a little bit different, e.g.

https://www.youtube.com/watch?v=89S-RbszwJE&list=PLMC9KNkIncKseYxDN2niH6glGRWKsLtde
https://www.youtube.com/playlist?list=PLMC9KNkIncKseYxDN2niH6glGRWKsLtde

Both playlist are the same but the second one (/playlist) contains all 236 songs while the first one (/watch) only shows 200 by default. If you click on the last song, it will show the remaining songs and the link changes. If you use the updated link when searching with discord-player-plus all songs will the provided. If using the initial /watch link, you will only get 200 songs like on YouTube


OS disk increase method provided for SUSE (SLES 12SP4) not working

[Enter feedback here]
parted package available in SLES 12 SP4 doest have an option called "resizepart" and one of the available option "resize" will work only when the filesystem is un mounted  so please check and change the procedure
parted -s /dev/sda "resizepart 4 -1" quit
SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 4
This file is deprecated and will be removed in a future service pack or release.
Please check /etc/os-release for details about this release.
NAME="SLES"
VERSION="12-SP4"
VERSION_ID="12.4"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP4"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp4"
parted -h
Usage: parted [OPTION]... [DEVICE [COMMAND [PARAMETERS]...]...]
Apply COMMANDs with PARAMETERS to DEVICE.  If no COMMAND(s) are given, run in
interactive mode.
OPTIONs:
-h, --help                      displays this help message
-l, --list                      lists partition layout on all block devices
-m, --machine                   displays machine parseable output
-s, --script                    never prompts for user intervention
-v, --version                   displays the version
-a, --align=[none|cyl|min|opt]  alignment for new partitions
-w, --wipesignatures            wipe superblock signatures when creating partition
COMMANDs:
align-check TYPE N                        check partition N for TYPE(min|opt)
alignment
help [COMMAND]                           print general help, or help on
COMMAND
mklabel,mktable LABEL-TYPE               create a new disklabel (partition
table)
mkpart PART-TYPE [FS-TYPE] START END     make a partition
name NUMBER NAME                         name partition NUMBER as NAME
print [devices|free|list,all|NUMBER]     display the partition table,
available devices, free space, all found partitions, or a particular
partition
quit                                     exit program
rescue START END                         rescue a lost partition near START
and END
resize NUMBER END                        change end sector of partition NUMBER
rm NUMBER                                delete partition NUMBER
select DEVICE                            choose the device to edit
disk_set FLAG STATE                      change the FLAG on selected device
disk_toggle [FLAG]                       toggle the state of FLAG on selected
device
set NUMBER FLAG STATE                    change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]]                   toggle the state of FLAG on partition
NUMBER
unit UNIT                                set the default unit to UNIT
version                                  display the version number and
copyright information of GNU Parted
Report bugs to<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cea4948f-a937-0543-ced0-e8db91ead17c
Version Independent ID: 62ac2429-6d59-8bfb-2731-127eb2aba615
Content: Resize an OS disk that has a GPT partition - Azure Linux Virtual Machines
Content Source: articles/virtual-machines/linux/resize-os-disk-gpt-partition.md
Service: security
GitHub Login: @kailashmsft
Microsoft Alias: kaib

@ajay15283 Thank you for reaching out to us, our team will look into it and get back to you on this.
Also, please note that this channel (the Azure Docs repository) is only for driving improvements related to the Azure documentation

@ajay15283  can you share more details on this ?
we have tested this several times and it works fine

I am using SLES 12SP4 market place image to be specific urn = SUSE:SLES:12-SP4:2019.11.13. when i execute parted it bail out as below
#parted -s /dev/sda "resizepart 4 -1" quit
Usage: parted [OPTION]... [DEVICE [COMMAND [PARAMETERS]...]...]
Apply COMMANDs with PARAMETERS to DEVICE.  If no COMMAND(s) are given, run in
interactive mode.
OPTIONs:
-h, --help                      displays this help message
-l, --list                      lists partition layout on all block devices
-m, --machine                   displays machine parseable output
-s, --script                    never prompts for user intervention
-v, --version                   displays the version
-a, --align=[none|cyl|min|opt]  alignment for new partitions
-w, --wipesignatures            wipe superblock signatures when creating partition
COMMANDs:
align-check TYPE N                        check partition N for TYPE(min|opt) alignment
help [COMMAND]                           print general help, or help on COMMAND
mklabel,mktable LABEL-TYPE               create a new disklabel (partition table)
mkpart PART-TYPE [FS-TYPE] START END     make a partition
name NUMBER NAME                         name partition NUMBER as NAME
print [devices|free|list,all|NUMBER]     display the partition table, available devices, free space, all found partitions, or a particular partition
quit                                     exit program
rescue START END                         rescue a lost partition near START and END
resize NUMBER END                        change end sector of partition NUMBER
rm NUMBER                                delete partition NUMBER
select DEVICE                            choose the device to edit
disk_set FLAG STATE                      change the FLAG on selected device
disk_toggle [FLAG]                       toggle the state of FLAG on selected device
set NUMBER FLAG STATE                    change the FLAG on partition NUMBER
toggle [NUMBER [FLAG]]                   toggle the state of FLAG on partition NUMBER
unit UNIT                                set the default unit to UNIT
version                                  display the version number and copyright information of GNU Parted
Report bugs to<EMAIL_ADDRESS>

will test in my lab and update here

@ajay15283  the latest parted package , resizepart is removed to resize because of this you are not able to resize the partitions.
you can use the below commands which would same work
sgdisk -d 4 /dev/sda
sgdisk -N 4 /dev/sda
reboot the vm and the use the "xfs_growfs /" to resize the file system.
we will be updating the document :)
Thanks for bringing this to our notice.
closing the PR:

#sign-off

@ajay15283 the latest parted package , resizepart is removed to resize because of this you are not able to resize the partitions.
you can use the below commands which would same work
sgdisk -d 4 /dev/sda
sgdisk -N 4 /dev/sda
reboot the vm and the use the "xfs_growfs /" to resize the file system.
we will be updating the document :)
Thanks for bringing this to our notice.
closing the PR:

Thank you . The mentioned steps works perfectly

This topic was removed. Closing this issue. #please-close


added codeql gha for code analysis

This PR Contains

Added Codeql Gha for Code Analysis

cc @Abhijay007 @joewxboy

There is very little / no source code in the docs repo.  Is this needed?

There is very little / no source code in the docs repo. Is this needed?

Yes it is needed because here Ruby and JS is used and the code is little but the code is there that`s why i open this one please review it and merge it


[GOBBLIN-1582] Fill low/high watermark info in SourceState for QueryBasedSource

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-1582

Description

[ ] Here are some details about my PR, including screenshots (if applicable):
Fill low/high watermark info in SourceState for QueryBasedSource
Foe stress test class, add function to make the job always fail

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:
unit tests

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #3436 (22ad917) into master (4a25c88) will increase coverage by 0.10%.
The diff coverage is 26.66%.

@@             Coverage Diff              @@
##             master    #3436      +/-   ##
============================================
+ Coverage     46.46%   46.57%   +0.10%
- Complexity    10251    10321      +70
============================================
  Files          2064     2072       +8
  Lines         80614    80863     +249
  Branches       9004     9024      +20
============================================
+ Hits          37455    37658     +203
- Misses        39686    39730      +44
- Partials       3473     3475       +2

Impacted Files
Coverage Δ

...lin/source/extractor/extract/QueryBasedSource.java
40.37% <0.00%> (-1.79%)
:arrow_down:

.../apache/gobblin/util/test/StressTestingSource.java
82.97% <66.66%> (+14.79%)
:arrow_up:

...he/gobblin/runtime/JobExecutionEventSubmitter.java
100.00% <100.00%> (ø)

...ache/gobblin/runtime/api/FlowSpecSearchObject.java
55.12% <0.00%> (-32.38%)
:arrow_down:

...n/java/org/apache/gobblin/writer/FsDataWriter.java
75.00% <0.00%> (-2.00%)
:arrow_down:

...blin/service/modules/orchestration/DagManager.java
71.22% <0.00%> (-1.74%)
:arrow_down:

...gobblin/service/modules/core/GitConfigMonitor.java
81.35% <0.00%> (-1.70%)
:arrow_down:

...lin/service/FlowExecutionResourceLocalHandler.java
4.67% <0.00%> (-1.05%)
:arrow_down:

.../apache/gobblin/cluster/GobblinClusterManager.java
53.27% <0.00%> (-0.65%)
:arrow_down:

...in/service/modules/core/GobblinServiceManager.java
50.20% <0.00%> (-0.41%)
:arrow_down:

... and 44 more

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 4a25c88...22ad917. Read the comment docs.


merge package template from arlac77/npm-package-template

package.json

chore: update package.json from template

.gitignore

chore(git): update .gitignore from template

Coverage remained the same at 64.49% when pulling 2353cf8b6a57287f8e249aa7a5760f76a54834ca on template-sync-1 into 3a97644c55ed8c4f4831d9ea0d3c949312736a64 on master.

Codecov Report

Merging #347 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #347   +/-   ##
=======================================
  Coverage   69.45%   69.45%
=======================================
  Files           4        4
  Lines         203      203
=======================================
  Hits          141      141
  Misses         62       62

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 3a97644...2353cf8. Read the comment docs.


Restore the JSON diff feature

I remember the old version of OK JSON has such feature.
But it is missing in the current version(2.4 build 111).
Is there any reason to remove it and can we add it back?

It will be back in version 2.6.3 (currently in review).


Add numeric and date fields, gt lt gte lte operators

!!This PR will require a reindex!! POST to /api/reindex after adding some metadata that are numbers or something like 2011-12-12 and the range searches should handle them as expected.
It enables numeric and date detection for new metadata fields and adds < > <= >= operators for that comparison.
Those operators had been disabled when string parsing was the only enabled detection, because that would consider "10" to be less than "9" given the alphabetical order instead of numerical.

Missing changelog entry and message about elasticsearch reindex required.

@bodom0015 thanks for responses. for all of these, make sure you've done a reindex first. if you go to elasticsearch mappings (http://localhost:9200/clowder/_mappings if youre running locally) you should see numeric_detection: true, near the top and nothing about date_detection (which is true by default).
1 - no datepicker implemented yet. you can use search string in date format, but Elasticsearch has some specific date formats it looks for: https://www.elastic.co/guide/en/elasticsearch/reference/current/date.html
I uploaded following metadata:

...first and third were recognized as dates in _mapping but middle one (your example) was not, i think this is consistent with their expected format:

...however, deeper testing with different formats shows that ES validates query string against the date format specified, which means if the field is YYYY/MM/DD and you query YYYY-MM-DD you get an error, and vice versa:
failed to parse date field [2020-01-29] with format [yyyy/MM/dd HH:mm:ss||yyyy/MM/dd||epoch_millis]
So if users mix and match their formatting this is annoying:

This probably merits another week to add a fix. Two that come to mind:
A - when a date field is specified in query, before sending to ES we parse the date in scala and change it into matching format for the field. this would help both GUI and API searches.
B - add a proper datepicker to GUI that appears when you select a date field from autocomplete instead of a text box. But this doesn't help API users or the search box in upper right.
We can discuss more at this week's meeting.

@lmarini i updated the help text for this last week, prior to that everything was working during our testing, can we merge this today if possible?


Fixed KVC remove observer crash for XLTwitterPagerTabStripViewController

Fixed the following issue #86 https://github.com/xmartlabs/XLPagerTabStrip/issues/86
There is a issue caused by the fact that we remove an observer before registering it.
Error :
*** Terminating app due to uncaught exception 'NSRangeException', reason: 'Cannot remove an observer for the key path "frame" from because it is not registered as an observer.'
Added a try catch for the remove observer call in XLTwitterPagerTabStripViewController

:+1:


Issues with final genbank-format file

Hi,
Thanks for the interesting tool. I've tried it out on a de novo assembly of an RSV isolate, but the resulting genbank-format file is incomplete with some minor errors.
Firstly, the file is missing the 'gene' features necessary for a genbank file, as well as some of the qualifiers for the CDS region ('/gene=...', '/product=...'):

Compare to the selected reference:

Secondly, my input sequence was reverse complemented with respect to the reference. In this circumstance, the genbank file should state that the feature occurs on the complementary strand:

If you are still working on this project and have time, could these issues please be fixed?
Cheers,
Charles

My bad re: the gene annotations, I just saw the --all option - somehow missed it previously. I note that the help option still says:

parser.add_argument('--all', action='store_true', help='Use this flag to transfer ALL annotations from reference, this is largely untested')

And the code says:

Experimental code for transferring 'gene' annotations from NCBI reference sequence

Was this ever tested further to consider it stable?
The 'complement' issue still stands though :)

Hi there! I do still work on this as time permits.
I tested the -all argument only with very good input files, so for input sequences that have the expected genes in the expected order it should work. I basically tested it by running sequences that had already been annotated in genbank and making sure that it copied it's own reference correctly. Not very rigorous but it should work.
I don't fully understand the complementing problem, I vaguely recall fixing that issue manually before but never implemented a robust fix.
Could you send me the input file and your reference so I can get a better understanding of what you need? I need to dust the old cobwebs off lol

Thanks for the reply. I'll send it by email if that's okay. Should I use your gmail account from your Github profile?

Yep that email is great!
I also remembered why genes and other features are not annotated by default. The program is designed to output the bare minimum for genbank submission and also to pull unchecked references directly from genbank. Many of these references don't contain gene annotations so instead of checking if they exist or not and then moving the annotations I just chose to ignore them.


Continually re-sync text when free

By re-synchronising the text repeatedly, we can ensure people who lagged or joined late will eventually catch up with the current text.

Implemented in v1.2.2.


[apostrophe-images] Namespace slugs of images and other piece types that aren't truly pagey, so they don't bump true pages to sloppy slugs.

Hmm. In what scenario does this happen? Either the filenames are crap, in
which case they would never conflict with the title of a blog post (for
example), or the filenames are awesome, in which case they... could
conflict if the image is titled "the gang at Marty's" and so is the
article, but still, pretty rare...
The prefix should still be reasonably friendly, in case somebody does
decide to build pieces-pages for images as a gallery.
On Wed, Apr 13, 2016 at 2:17 PM, Jimmy Harrison<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/499

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Thinking about things like people profiles or place show pages. For example, if John Smith has a profile, it's not unreasonable to think someone might upload John Smith.jpg. Both get the john-smith slug, and if the person created the image through the chooser while creating the chooser, the image will nab the first one, and the actual profile page will be something like john-smith1

Yeah, fair enough. I see no harm in your suggestion that there be a prefix.
On Thu, Apr 14, 2016 at 8:48 AM, Jimmy Harrison<EMAIL_ADDRESS>wrote:

Thinking about things like people profiles or place show pages. For
example, if John Smith has a profile, it's not unreasonable to think
someone might upload John Smith.jpg. Both get the john-smith slug, and if
the person created the image through the chooser while creating the
chooser, the image will nab the first one, and the actual profile page will
be something like john-smith1
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/punkave/apostrophe/issues/499#issuecomment-209923494

--
*THOMAS BOUTELL, *DEV & OPS
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

Just realized one other case where this optional prefix could be useful: Users. Since generally, we are aiming to separate users and profiles, but I would say it's likely that a user also could have a profile. Some generalized slug-prefixing-mechanism for pieces could be useful.
Just capturing this thought here to remember it when it comes to implementation.


Only default value of sha1 getting chosen

We are experiencing the problem where the default value of sha1 in parameterized builds (in our case "master") and not the github commit from the PR.
The correct PR/commit status on Github is being set, but the build is always with the commit on default value of sha1.
This however, does NOT happen if sha1 is not parameterized.
Here are 2 sample build logs for the same pr: With sha1 parameterized and Without sha1 parameterized.
As you can see, the github setting status is working correctly. However, the checkout is revising to master on the build with sha1 parameterized.
This was also suggested by a user (zachmccormick) in #415.
Using GHPRB v1.32.2 with Jenkins LTS 1.651.2.

@shehzan10 This seems to be an issue because of the recent security update on jenkins.


Kalidokit interface

https://github.com/yeemachine/kalidokit

@avaer
Can someone else pick this up and modify the PR, make it ready for integration, or is this waiting on a heavy update before it can be merged?

I'm back on it, it needs a bit more work.

I actually think the pose resolution calculations in kalidokit leave a lot to be desired.
That code uses mostly vector math hacks with tons of corner case detection, which has strange singularities, like the pose having a strong tendency to lean to the left.
I think we can perhaps do basic world quaternion pointing with the mediapipe data (which is presented in world XYZ based on what the model thinks) to get a much more accurate avatar pose out of it.

This page really helped me: https://google.github.io/mediapipe/solutions/pose_classification.html
Especially this diagram:

With basic 3d maths you can easily compute the corresponding avatar bones quats.

For posterity, here is the face geometry map: https://raw.githubusercontent.com/google/mediapipe/master/mediapipe/modules/face_geometry/data/canonical_face_model_uv_visualization.png

Example of kalidokit hax/code problems:
https://github.com/yeemachine/kalidokit/blob/505e21e5bcb86771edf96acaa72a0493bd358200/src/utils/vector.js#L243
https://github.com/yeemachine/kalidokit/blob/505e21e5bcb86771edf96acaa72a0493bd358200/src/PoseSolver/calcHips.js#L29

This is almost done.
I rewrote the core to use my own math rather than kalidokit and indeed, it turned out cleaner code and higher quality output. We should probably get rid of kalidokit entirely, porting over the necessary parts.
I also want to optimize this by running the AI pose model in a worker.
Somewhat blocked on https://github.com/webaverse/app/issues/1848, which screws up the main model's posing.

I ended up implementing the isolated origin iframe version of this to take advantage of the strict process separation in that mode.
Note that to make this work, fake RAF is need to make the iframe seem active in 3d. Apparently rendering is not enough to trigger that heuristic in Chrome. If you do not include it you will mysteriously have the iframe tick rate throttled behind time tickets.

This works great so far, but the slowest part is the pixel read back in the iframe. It does not hog the main render loop and therefore does not reduce game FPS, but it does lock up the iframe while it is running.

I wonder if that can be optimized, though I do get similar results in the mediapipe codepen demos so I wonder if it's something else, like camera frame rate...
https://codepen.io/mediapipe/pen/jOMbvxw

Is anyone else available to check the performance characteristics of the mediapipe pose demo on their hardware?
https://codepen.io/mediapipe/pen/jOMbvxw

Constant 30 fps...

hardware specs

I suspect it is a camera driver issue on my end, though if that is true I won't be the only one. I'll play around more, and also order a different camera for testing.

This is working quite performantly after I changed the camera read technique to use an intermediate canvas, from which we source the ImageBitmap. This seems to get around some camera driver GPU fencing that was causing blocks.
I also added support for the full emotion gamut using custom face pose detection math which maps to the VRM shape keys.

This is done enough that someone other than me could take it to the finish line.

[ ] needs to take in inputs from the actual hands, rather than the fakeQuaternion which was being used to test rotation orders (it's an easy switch, the necessary code is already there and commented out)
[ ] needs major cleanup/optimization, mostly for allocations which are everywhere in the face tracking code path. the cleanup is mostly mechanical as the code should be well behaved and abstracted already, the only problem being dead code and cloning.

Device: Dell precision 7710
Nvidia Quadro m5000m 8gb
ram: 16 gb
Ci7 6th gen 2.70 GHz
The PR has issue on my device as it doesn't shows the avatar down the bottom right, instead, it shows ''StandBy''. Meanwhile, the camera is being used. I have attached the log ss.

This has not reached step 1 yet (rebase).


panic: runtime error: index out of range [0] with length 0

Issue description

[ ] This issue is a regression.
[ ] It is unknown if this issue is a regression.

Gemini failed with a panic.
2023-05-15 08:04:00.257: (GeminiStressEvent Severity.ERROR) period_type=end event_id=a174c177-4913-4112-ad26-a08d4df24e96 duration=3h10m38s: node=Node gemini-with-nemesis-3h-normal-2022--loader-node-6a59cbd5-1 [<IP_ADDRESS> | <IP_ADDRESS>] (seed: False) gemini_cmd=/$HOME/gemini -d --duration 3h --warmup 30m -c 50 -m mixed -f --non-interactive --cql-features normal --max-mutation-retries 5 --max-mutation-retries-backoff 500ms --async-objects-stabilization-attempts 5 --async-objects-stabilization-backoff 500ms --replication-strategy "{'class': 'SimpleStrategy', 'replication_factor': '3'}" --oracle-replication-strategy "{'class': 'SimpleStrategy', 'replication_factor': '1'}" --test-cluster=<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS> --outfile /home/centos/gemini_result_0731bd7e-0bf2-4ad0-a7fd-2ee3eb6b1662.log --seed 26 --request-timeout 180s --connect-timeout 120s --oracle-cluster=<IP_ADDRESS>
result=Exit code: 2
Command output: ['}', '{"L":"INFO","T":"2023-05-15T04:53:30.054Z","N":"generator","M":"starting partition key generation loop"}']
errors=['Command error: panic: runtime error: index out of range [0] with length 0\n\ngoroutine 808 [running]:\ngithub.com/gocql/gocql.encBigInt2C(0x7f29c0a18f18?)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/marshal.go:1123 +0x265\ngithub.com/gocql/gocql.marshalBigInt({0xbe91c0?, 0xc014aebdc0}, {0xa90a80?, 0xc0c413fa00})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/marshal.go:575 +0x37f\ngithub.com/gocql/gocql.marshalVarint({0xbe91c0?, 0xc014aebdc0?}, {0xa90a80?, 0xc0c413fa00?})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/marshal.go:678 +0xf7\ngithub.com/gocql/gocql.Marshal({0xbe91c0, 0xc014aebdc0}, {0xa90a80?, 0xc0c413fa00})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/marshal.go:96 +0x485\ngithub.com/gocql/gocql.Marshal({0xbe91c0, 0xc014aebdc0}, {0xaf0780?, 0xc06c36bb80})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/marshal.go:58 +0x1aa\ngithub.com/gocql/gocql.marshalQueryValue({0xbe91c0?, 0xc014aebdc0?}, {0xaf0780?, 0xc06c36bb80?}, 0xc2ad744870)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/conn.go:1056 +0x8c\ngithub.com/gocql/gocql.(*Conn).executeQuery(0xc0000dd680, {0xbe8d60, 0xc026971100}, 0x4850f7?)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/conn.go:1125 +0x10b3\ngithub.com/gocql/gocql.(*Query).execute(0x1?, {0xbe8d60?, 0xc026971100?}, 0x10?)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/session.go:986 +0x2c\ngithub.com/gocql/gocql.(*queryExecutor).attemptQuery(0xc0001911e8, {0xbe8d60, 0xc026971100}, {0xbeb788, 0xc2ae692000}, 0xc0000dd680)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/query_executor.go:29 +0x8a\ngithub.com/gocql/gocql.(*queryExecutor).do(0xc0001911e8, {0xbe8d60, 0xc026971100}, {0xbeb788, 0xc2ae692000})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/query_executor.go:112 +0x1ab\ngithub.com/gocql/gocql.(*queryExecutor).executeQuery(0xc0001911e8, {0xbeb788, 0xc2ae692000})\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/query_executor.go:60 +0xe5\ngithub.com/gocql/gocql.(*Session).executeQuery(0xc0002f8380, 0x0?)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/session.go:446 +0x8c\ngithub.com/gocql/gocql.(*Query).Iter(0xc2ae692000?)\n\t/home/ls/go/pkg/mod/github.com/scylladb/gocql@v1.4.0/session.go:1167 +0x5b\ngithub.com/scylladb/gemini/store.(*cqlStore).load(0xc00006c820, {0xbe8d60?, 0xc026971100}, {0xbe4880, 0xc2ae688d20?}, {0xc2ae119480, 0x5, 0x8})\n\t/home/ls/repos/gemini_upstream/store/cqlstore.go:106 +0x18d\ngithub.com/scylladb/gemini/store.load(...)\n\t/home/ls/repos/gemini_upstream/store/store.go:217\ngithub.com/scylladb/gemini/store.delegatingStore.Check({{0xbe8f58, 0xc000198cd0}, {0xbe8f58, 0xc00006c820}, 0x1, 0xc000063920}, {0xbe8d60, 0xc026971100}, 0x14?, {0xbe4880, ...}, ...)\n\t/home/ls/repos/gemini_upstream/store/store.go:172 +0xde\nmain.validation({0xbe8d60, 0xc026971100}, 0xc00018d740?, 0xc083d59de8, 0xc0002be180?, {0xbe8f90, 0xc000077c80}, 0xc023bd5c80?, {0x2710, 0x0, ...}, ...)\n\t/home/ls/repos/gemini_upstream/cmd/gemini/jobs.go:266 +0x2d7\nmain.ValidationJob({_, _}, _, _, {0xc000186138, 0xc000186140, {0x0, 0x0, 0x0}, 0x1, ...}, ...)\n\t/home/ls/repos/gemini_upstream/cmd/gemini/jobs.go:88 +0x25f\nmain.job.func1()\n\t/home/ls/repos/gemini_upstream/cmd/gemini/jobs.go:155 +0x17b\ngolang.org/x/sync/errgroup.(*Group).Go.func1()\n\t/home/ls/go/pkg/mod/golang.org/x/sync@v0.0.0-20200317015054-43a5402ce75a/errgroup/errgroup.go:57 +0x67\ncreated by golang.org/x/sync/errgroup.(*Group).Go\n\t/home/ls/go/pkg/mod/golang.org/x/sync@v0.0.0-20200317015054-43a5402ce75a/errgroup/errgroup.go:54 +0x8d\n\n']

2023-05-15 08:17:00.397: (TestFrameworkEvent Severity.ERROR) period_type=one-time event_id=28f303ce-458b-4236-b599-2a9806faf48e, source=GeminiTest.test_load_random_with_nemesis (gemini_test.GeminiTest)() message=Traceback (most recent call last):
File "/home/ubuntu/scylla-cluster-tests/gemini_test.py", line 68, in test_load_random_with_nemesis
self.verify_results()
File "/home/ubuntu/scylla-cluster-tests/gemini_test.py", line 127, in verify_results
self.fail(self.gemini_results['results'])
AssertionError: []

Impact
Describe the impact this issue causes to the user.
How frequently does it reproduce?
Describe the frequency with how this issue can be reproduced.
Installation details
Kernel Version: 5.15.0-1035-aws
Scylla version (or git commit hash): 2022.1.7-20230514.f5c8060f16 with build-id 847ca2704d89d74e2f44409d8f3719c20eeb876c
Cluster size: 3 nodes (i3.large)
Scylla Nodes used in this run:

gemini-with-nemesis-3h-normal-2022--oracle-db-node-6a59cbd5-1 (<IP_ADDRESS> | <IP_ADDRESS>) (shards: 2)
gemini-with-nemesis-3h-normal-2022--db-node-6a59cbd5-3 (<IP_ADDRESS> | <IP_ADDRESS>) (shards: 2)
gemini-with-nemesis-3h-normal-2022--db-node-6a59cbd5-2 (<IP_ADDRESS> | <IP_ADDRESS>) (shards: 2)
gemini-with-nemesis-3h-normal-2022--db-node-6a59cbd5-1 (<IP_ADDRESS> | <IP_ADDRESS>) (shards: 2)

OS / Image: ami-09cb8437b7a0a692b (aws: us-east-1)
Test: gemini-3h-with-nemesis-test
Test id: 6a59cbd5-cec6-4b8d-b140-07fc016ccfa2
Test name: enterprise-2022.1/gemini-/gemini-3h-with-nemesis-test
Test config file(s):

gemini-3h-with-nemesis.yaml

Logs and commands

Restore Monitor Stack command: $ hydra investigate show-monitor 6a59cbd5-cec6-4b8d-b140-07fc016ccfa2
Restore monitor on AWS instance using Jenkins job
Show all stored logs command: $ hydra investigate show-logs 6a59cbd5-cec6-4b8d-b140-07fc016ccfa2

Logs:

db-cluster-6a59cbd5.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/6a59cbd5-cec6-4b8d-b140-07fc016ccfa2/20230515_082651/db-cluster-6a59cbd5.tar.gz
monitor-set-6a59cbd5.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/6a59cbd5-cec6-4b8d-b140-07fc016ccfa2/20230515_082651/monitor-set-6a59cbd5.tar.gz
loader-set-6a59cbd5.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/6a59cbd5-cec6-4b8d-b140-07fc016ccfa2/20230515_082651/loader-set-6a59cbd5.tar.gz
sct-runner-6a59cbd5.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/6a59cbd5-cec6-4b8d-b140-07fc016ccfa2/20230515_082651/sct-runner-6a59cbd5.tar.gz
parallel-timelines-report-6a59cbd5.tar.gz - https://cloudius-jenkins-test.s3.amazonaws.com/6a59cbd5-cec6-4b8d-b140-07fc016ccfa2/20230515_082651/parallel-timelines-report-6a59cbd5.tar.gz

Jenkins job URL

I think the issue is already fixed.
Yaron, which Gemini version was used?
@fruch / @dkropachev are we using the latest Gemini docker in SCT?
If so, we probably need to backport it as well.

I think the issue is already fixed. Yaron, which Gemini version was used?
@fruch / @dkropachev are we using the latest Gemini docker in SCT? If so, we probably need to backport it as well.

there a PR with latest tag from gemini:
https://github.com/scylladb/scylla-cluster-tests/pull/6115
but from a few runs I've did it doesn't seem to be more stable, if you want to push and backport blindly like that, be my guest.

'gemini_version': '1.7.8'

@fruch , @roydahan , this particular issue is fixed in 1.8.0

but from a few runs I've did it doesn't seem to be more stable, if you want to push and backport blindly like that, be my guest.

Can I have them ?

this particular issue is not gocql-related, it comes from the fact that gemini was manipulating with data at the same it when it feeds data to the gocql.
But there are other gocql bugs that causes panics on serialization/deserialization, I have created PR to address them.

@dkropachev shouldn't we also bump the gocql driver version we use in Gemini.
Isn't it something very old?

@roy, on the master we have it most modern version - v1.7.3


add a client library test for spring boot application

Example: https://www.codejava.net/frameworks/spring-boot/connect-to-postgresql-database-examples
The test cases can be similar to the one we used in JDBC client library test:https://github.com/risingwavelabs/risingwave/tree/main/integration_tests/client-library/java/src/test/java/com/risingwave

#16233


[firebase_crashlytics]: Crashlytics build step crashes build of a macOS app - upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Crashlytics
Which platforms are affected?
macOS
Description
Whenever you want to build macOS (both for debug and release) with crashlytics in it, it just crashes. This is even after a fresh creation of the project.
Expected result:
FlutterFire: "flutterfire upload-crashlytics-symbols" build step uploads the symbols to crashlytics
Actual result:
FlutterFire: "flutterfire upload-crashlytics-symbols" build step doesn't find the dSYM files.
Reproducing the issue

Create a new flutter project with flutter create --org cz.appelevate coreee and a new firebase project
cd into this project - cd coreee
add firebase into this project:

flutter pub add firebase_core
flutterfire configure

add firebase analytics

flutter pub add firebase
flutterfire configure

add firebase crashlytics

flutter pub add firebase_crashlytics
flutterfire configure

add both to the main.dart file

import 'package:coreee/firebase_options.dart';
import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_crashlytics/firebase_crashlytics.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp(
    options: DefaultFirebaseOptions.currentPlatform,
  );
  FlutterError.onError = (errorDetails) {
    FirebaseCrashlytics.instance.recordFlutterFatalError(errorDetails);
  };
  // Pass all uncaught asynchronous errors that aren't handled by the Flutter framework to Crashlytics
  PlatformDispatcher.instance.onError = (error, stack) {
    FirebaseCrashlytics.instance.recordError(error, stack, fatal: true);
    return true;
  };
  runApp(const MyApp());
}

flutter run -d macos

tadaa you get the error :/

Firebase Core version
3.1.0
Flutter Version
Flutter 3.22.2 • channel stable
Relevant Log Output
Launching lib/main.dart on macOS in debug mode...
Running pod install...                                           1,672ms
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:arm64, id:00006030-000859D11482001C, name:My Mac }
{ platform:macOS, arch:x86_64, id:00006030-000859D11482001C, name:My Mac }
ld: warning: ignoring duplicate libraries: '-lc++'
Unhandled exception:
Exception: 2024-06-23 20:03:52.652 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:53.658 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:54.663 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:55.665 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:56.667 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:57.672 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:58.677 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:03:59.682 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:00.688 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:01.693 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:02.694 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:03.698 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:04.700 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:05.706 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:06.710 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:07.716 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:08.721 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:09.726 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:10.729 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:11.735 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:12.740 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:13.746 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:14.751 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:15.752 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:16.757 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:17.763 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:18.768 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:19.771 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:20.774 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:21.778 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"
2024-06-23 20:04:22.784 upload-symbols[44583:605681] Unable to get file attributes for dSYM file at path "/Users/tom/programming/appe/oh/coreee/build/macos/Build/Products/Debug/coreee.app.dSYM/Contents/Resources/DWARF"

#0      UploadCrashlyticsSymbols.run (package:flutterfire_cli/src/commands/upload_symbols.dart:406:7)
<asynchronous suspension>
#1      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#2      main (file:///Users/tom/.pub-cache/hosted/pub.dev/flutterfire_cli-1.0.0/bin/flutterfire.dart:63:5)
<asynchronous suspension>
Command PhaseScriptExecution failed with a nonzero exit code

/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'nanopb' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'PromisesObjC' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'PromisesSwift-Promises_Privacy' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'PromisesSwift' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'GoogleDataTransport-GoogleDataTransport_Privacy' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'GoogleDataTransport' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'nanopb-nanopb_Privacy' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.11, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'PromisesObjC-FBLPromises_Privacy' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'GoogleUtilities' from project 'Pods')
/Users/tom/programming/appe/oh/coreee/macos/Pods/Pods.xcodeproj: warning: The macOS deployment target 'MACOSX_DEPLOYMENT_TARGET' is set to 10.12, but the range of supported deployment target versions is 10.13 to 14.5.99. (in target 'GoogleUtilities-GoogleUtilities_Privacy' from project 'Pods')
warning: Run script build phase 'FlutterFire: "flutterfire upload-crashlytics-symbols"' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
** BUILD FAILED **

Building macOS application...
Error: Build process failed

Flutter dependencies

Expand Flutter dependencies snippet

Dart SDK 3.4.3
Flutter SDK 3.22.2
coreee 1.0.0+1

dependencies:
- cupertino_icons 1.0.8
- firebase_analytics 11.0.1 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_core 3.1.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 4.0.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]

dev dependencies:
- flutter_lints 3.0.2 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math leak_tracker_flutter_testing async boolean_selector characters collection leak_tracker leak_tracker_testing material_color_utilities meta source_span stream_channel string_scanner term_glyph vm_service]

transitive dependencies:
- _flutterfire_internals 1.3.37 [collection firebase_core firebase_core_platform_interface flutter meta]
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- characters 1.3.0
- clock 1.1.1
- collection 1.18.0
- fake_async 1.3.1 [clock collection]
- firebase_analytics_platform_interface 4.0.1 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.7+9 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins]
- firebase_core_platform_interface 5.1.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.17.2 [firebase_core_platform_interface flutter flutter_web_plugins meta web]
- firebase_crashlytics_platform_interface 3.6.37 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math]
- leak_tracker 10.0.4 [clock collection meta path vm_service]
- leak_tracker_flutter_testing 3.0.3 [flutter leak_tracker leak_tracker_testing matcher meta]
- leak_tracker_testing 3.0.1 [leak_tracker matcher meta]
- lints 3.0.0
- matcher 0.12.16+1 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.8.0 [collection]
- meta 1.12.0
- path 1.9.0
- plugin_platform_interface 2.1.8 [meta]
- sky_engine 0.0.99
- source_span 1.10.0 [collection path term_glyph]
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.7.0 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- vector_math 2.1.4
- vm_service 14.2.1
- web 0.5.1

Additional context and comments
I'm running this on latest macos (14.5 (23F79)) on M3 pro.
Flutter doctor -v:
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale en-US)
    • Flutter version 3.22.2 on channel stable at /Users/tom/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (3 weeks ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/tom/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] VS Code (version 1.90.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.90.0

[✓] Connected device (5 available)
-     **hiden for privacy reasons**

[✓] Network resources
    • All expected network resources are available.

• No issues found!

The fix is to simply Click the allow install builds only in xcode. Please add that to the flutterfire cli

@tpkowastaken Thank you for reporting this issue, and I'm glad that you found a solution for it. I've informed the team about updating the CLI to avoid any issues in the future.

Thank you for your answer I appreciate the quick response.
Hovewer shouldn't you forward it to the dev team instead? It shouldn't take too long to fix this. I believe it's just a simple edit of the Runner.xcworkspace that the flutterfire cli is already editing to put the bugged task in there already.
I wish you luck with resolving the issue internally and thank you for your effort.

@tpkowastaken Can you open this issue again in https://github.com/invertase/flutterfire_cli

My bad I haven't tested releasing the app yet. The script crashes even after that change when you try to release it. There is hovewer an issue already created - https://github.com/invertase/flutterfire_cli/issues/314. I'm going to move the conversation there.


[Feature Request] Reset Multiple Variables (BUT NOT ALL)

Is your feature request related to a problem? Please describe.
I want to have a feature in my game where you can change the nation you're aligned to. However, the missions for these nations share a set of variables. I'd like to be able to specify a range of variables to reset to 0, instead of either having to do them one by one or all of them.
Describe the solution you'd like
Either a range to reset, or at least something like the Dialog option where you can click a plus sign to add another varibale you'd like to reset.
Describe alternatives you've considered
Additional context

You might be able to nest the reset in a conditional where you say "IF a certain variable is FALSE, then reset; ELSE do something else."
I'm not sure how many variables you would like to reset, but before this Event was possible, we had to reset all variables manually (one-by-one) anyway.

I know you can reset one-by-one, but I'm looking to reset ~30-40 variables, so something like a window with a checkbox asking which variables I want to reset would be my ideal solution. It's more of a UX improvement than putting in a new feature.
Here's what the code looks like currently: (sized down to 33%)


Upgrade dom-helpers to prevent duplicate packages

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When building with @material-ui I receive a duplicate packages error for dom-helpers. Attempting to resolve to the latest<EMAIL_ADDRESS>breaks react-swipeable-views which relies on<EMAIL_ADDRESS>Current Behavior

Steps to Reproduce (for bugs)

Install latest react-swipeable-views
Build with webpack and duplicate-package-checker-webpack-plugin

Context

Your Environment

Tech
Version

react-swipeable-views
0.13.3

React
16.8.6

I also have this error, using with MaterialUI v4 cause error in "dom-helpers"

For me react-swipeable-views does not work with shadow-cljs because of this issue.

is this fixed already ?

This should now be fixed with PR #556

Same here, downgrading to 0.12.8 helped solve the issue for now.

You should be able to install the latest without issue

That is true, thank you, works now!


Integration Test - Release - 2018/12/27 01:39:19

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

@PRMergerTest3 : Thanks for your contribution! The author, @v-caxian, has been notified to review your proposed change.


Don't use the term gamma correction in spec or wiki

I just came across the wiki page Gamma-Correction-in-Future-X3D. Please don't refer to it as gamma correction and especially don't make statements like the 'monitor "distorts" the colors even if "distorts" is in inverted commas.
What is happening is the incoming scene data is being encoded/compressed in a way that removes all changes that humans cannot perceive thereby making the signal fit into 8-bit components without banding or losing detail in the darks. The monitor just happens to be a nearly perfect decoder for this encoding as it has the inverse response of the human eye. When you understand that this is what is going on, everything becomes much clearer.
If you have only 8-bits per channel you need this encoding. Since it is an encoding/compression you need to decode (to "linear") before performing any computations - lighting, flitering, blending etc. and re-encode afterward, if you only have an 8-bit framebuffer. If you do not re-encode, i.e. you are doing "linear" rendering then for correct color, assuming an sRGB or similar monitor, the colors in the framebuffer MUST be encoded before presentation to the display to get correct color. This is what hardware "gamma correctors" were doing on early graphics systems. This is all you need to know.
Unfortunately there are many implementations of low-level graphics apis where "linear" framebuffers are not encoded for the display - WebGL is one culprit - which has led to people tuning their colors for the incorrect rendering. Then when rendering IS done correctly they will complain that it looks terrible. WebGL does not currently support sRGB framebuffers so apps that care about correct color rendering have to encode the outputs of their fragment shaders. If blending is being used the result is not 100% correct because the encoded sRGB values rather than linear values are blended.
I recommend Poynton's Rehabilitation of gamma for further detail.

That's a fair point. Talking about sRGB and linear space is more precise way to say what we want. I like how glTF spec avoids saying things like "do gamma correction", it instead nicely says things like "The baseColorTexture uses the sRGB transfer function and must be converted to linear space before it is used for any computations." .
We will indeed want to follow it for X3D spec. I.e. not say "do gamma correction", but say to "perform calculations in linear space", and to clarify when/which textures should be considered in sRGB. I did edits to this document to not forget about it, when we'll get back to this topic in Web3D.
Thanks!
Though in generally the term "gamma correction" is used widely as a synonym for "gamma-correct rendering". So my wiki will continue to talk about it. The confusing term is not my invention -- resources like

https://www.vfxwizard.com/tutorials/gamma-correction-for-linear-workflow.html ,
https://gamedevelopment.tutsplus.com/articles/gamma-correction-and-why-it-matters--gamedev-14466
https://en.wikipedia.org/wiki/SRGB
https://blog.molecular-matters.com/2011/11/21/gamma-correct-rendering/
https://docs.unity3d.com/Manual/LinearRendering-LinearOrGammaWorkflow.html

all do talk about it.
As for "distorts": Agreed, I have changed the term "distorts" into "transforms", and linked more clearly to https://github.com/michaliskambi/x3d-tests/wiki/Gamma-correction-in-X3D-and-glTF , that says what is this "transformation" in practice. The overview on https://github.com/michaliskambi/x3d-tests/wiki/Gamma-Correction-in-Future-X3D is deliberately at attempt at explaining the issue in a bit different way than more developer-oriented https://github.com/michaliskambi/x3d-tests/wiki/Gamma-correction-in-X3D-and-glTF .
As for 8-bits: I do not fully agree with your phrasing, although that's just going into details. But for me it's not about 8-bits or compression. It's about the need to perform calculations in the "linear" space, which is really the right space where the physical light equations make sense. And the fact that typical textures do not store colors in this space (though they could), and monitors do not take colors in this space. The important thing is not mix this with "tone mapping", https://en.wikipedia.org/wiki/Tone_mapping , which deals with "how to represent this infinite range of colors (in reality) on a limited range available on monitors". And tone mapping is independent from gamma correction -- gamma correction is just "how to calculate lighting correctly".
Agreed on sRGB framebuffers. They would be great, if universally available. If a GPU implementation can use the GPU sRGB texture formats, and sRGB framebuffer formats, then it has both an easier job, and can be more correct, as it doesn't have to effectively hardcode operations lik pow(x, 1/2.2) in the shader.

I am well aware of the wide-spread use of "gamma correction" which has origins in the early days of CG. That is no reason to continue using it. Thinking about this issue as "correction" sets one off down the wrong path and helps lead to the widespread confusion surrounding it.

As for 8-bits: I do not fully agree with your phrasing

Which part? Referring to sRGB as an encoding/compression is fact. Saying you need an sRGB framebuffer, if you only have 8-bits is also fact. If you store linear in there you will suffer unpleasant artifacts.
I don't agree with "renderingColorSpace". Rendering should always be done in linear space. It is not wise to provide people ways to do things incorrectly, so rendering in sRGB space should not be allowed. The only discussion/choice should be about whether the framebuffer is in sRGB or linear space. If the latter data should be encoded for the display before it hits the display.


move to starknet-foundry

recently announced, starknet-foundry

we might consider moving once they get 0.4.0 out (it introduces should_panic)


Do check error messages in non-compat integration tests

What should be done?
In #2345, we will remove all checks for error messages in compat tests. We still want to check error messages in tricky cases, and that should be in non-compat integration tests. We also want our tests be consistent. Right now, they have small differences here and there; in particular, some tests include altMessage in their test cases, and some don't.
Let's add altMessage to all non-compat table-driven tests and use it. Let's also try to add at least one test case to tests that don't use it yet.
Where?
Integration tests.
Definition of Done

integration tests added/updated;
spot refactorings done.

Let's add altMessage to all non-compat table-driven tests and use it. Let's also try to add at least one test case to tests that don't use it yet.

What if the original message is the same as altMessage? Should we really add altMessage to all table-driven non-compat tests? I think we have quite a lot of cases where the messages are equal.

What if the original message is the same as altMessage?

if tc.altMessage != ""

Should we really add altMessage to all table-driven non-compat tests?

Yes.

The underlying issue is that all compat tests and non-compat table-driven tests are slightly different for no good reason, and those differences propagate because we create new tests by copy and pasting existing inconsistent tests. They should become more consistent, not less.


Bug: process polyfill causes issues by virtue of being an ES module

Summary
Cross-post of readable-stream #539 (for which a reproducible example was made, also on GitHub Pages)
May be related to #98.
This may not chiefly be an issue with vite-plugin-node-polyfills, but it has been observed that in combination with readable-stream and vite that the process polyfill causes errors due to being used as if it is not an ES module, or conversely, not having its default export properly unwrapped. The purpose of this issue is to hopefully help narrow down the code that could least intrusively be updated to fix this incompatibility, for instance (and not primarily), changing vite-plugin-node-polyfills to export a CJS shim via export = process in addition to a default export¹.
¹ Something like (and attempt to fight the urge to vomit) this:
export = Object.assign(process, { process, default: process })

Any insight, especially on how Vite handles ES module interop in combination with this plugin, would be greatly appreciated. :heart:

Repro: https://stackblitz.com/~/github.com/WasabiThumb/reprex-539


fix: make defaultValue work again

It was from my changes to avoid giving undefined values to formik to suppress it's errors about changing controls from controlled to uncontrolled.
fixes #385

PR Storybook available here


if $subset is not 'all' cast it as array

The $subset arg passed to get_google_font_uri() can be a string ('all') or an array of subsets. So I suggest this fix to keep the array type if $subset is not 'all'.

Here is a quick explanation to be much clear.
I add a control to set choose subsets, as explained in
$controls[] = array(
    'type'     => 'multicheck',
    'setting'  => 'font_subsets',
    'label'    => __( 'Google-Font subsets', 'maera_bs' ),
    'description' => __( 'The subsets used from Google\'s API.', 'maera_bs' ),
    'section'  => 'typo_base',
    'default'  => 'latin',
    'priority' => 22,
    'choices'  => Kirki_Fonts::get_google_font_subsets(),
    'output'   => array(
        'element'  => 'body',
        'property' => 'font-family'
    )
);

Then, in my site html I found the googlefont embed link with this subset arg (decoded for clarity):
&subset=latin,Array
With my fix, the subsets are properly appended:
&subset=cyrillic,devanagari,greek,latin,latin-ext
I hope it helps.

awesome, thanks!


Add rule to unignore the maven wrapper jar

If a project uses the maven-wrapper library (https://github.com/takari/maven-wrapper) the .jar file of the maven-wrapper gets excluded if there is a catch-all *.jar rule in the .gitignore.
I think the un-ignore rule for the maven-wrapper fits best into the normal maven .gitignore.
However, I have noticed that the un-ignore rule is ignored if the catch-all *.jar rule is applied after the one I add. Is it possible to further customize the rule in a way, so the order in which the rules appear in the .gitignore is not important?

However, I have noticed that the un-ignore rule is ignored if the catch-all *.jar rule is applied after the one I add. Is it possible to further customize the rule in a way, so the order in which the rules appear in the .gitignore is not important?

Unfortunately not - order matters here

Are there any plans on merging this or is something still unclear?

FYI - this is affecting some Spring Boot users that generate from http://start.spring.io/ when using the default build tool (which is the Maven wrapper).  If they then use https://www.gitignore.io/ to help generate their .gitignore file, git will end up excluding the wrapper.jar (which is essential to builds).  In my case the downstream impact was a broken build in my CI tool that took me several hours to figure out.
@shiftkey The solution presented here is quite similar to the existing one for the Gradle wrapper (Gradle is an alternative build tool for Java apps).  You can see the rule applied here: https://github.com/github/gitignore/blob/master/Gradle.gitignore
It looks like the rule presented in this patch is even more explicit than that in Gradle in that it checks the full path of the wrapper.jar so it looks fairly safe to apply.  I'm not an expert on the Gradle wrapper so I don't know if there are more possible places that its wrapper.jar could be located which might be why they left it without a folder (the docs seem to indicate it is a know path: https://docs.gradle.org/current/userguide/gradle_wrapper.html#using_wrapper_scripts).

Thanks for commenting @ssherwood!
The solution I present here is indeed directly inspired from Gradle.gitignore. As you have pointed out correctly, this one is actually more restrictive, as it just applies to wrapper jar and nothing else.
Gradle introduced the concept of the wrapper jar to allow users to build their projects without having gradle installed locally. This concept has then been ported for maven. It don't think the will change the location or name of the wrapper jar, as there is absolutely no need for doing so.
PS: I too was stuck with a failing CI build until I realized that the catch-all jar-exclude rule excluded the wrapper jar from my repository.
@shiftkey What would have to be done to actually merge this pull request? Or is there still something unclear that needs to be sorted out?

Thanks for get me involed

@shiftkey Any plans on merging this soon? Are there any issues left which should be discussed / resolved before merging this?

@thomaseizinger no, just wanted to ensure this was a reasonably safe change


Update list.json

[
{
"address": "one10q7eaf8d8epvksja3fp3zrrq6wfqdg20a76y2p",
"name": "Wrapped XRC",
"symbol": "WXRC",
"decimals": 8,
"totalSupply": "1000000",
"website": "https://xrhodium.org",
"description": {
"en": "wrapped xrhodium (WXRC)"
}
}
]

hey there, I assume you don't need that PR so i'll close it but feel free to reopen and tag me if you still need it.


close the server in the version negotiation integration tests

This fixes a race condition.

Codecov Report

Merging #1634 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1634   +/-   ##
=======================================
  Coverage   87.39%   87.39%
=======================================
  Files          98       98
  Lines        6231     6231
=======================================
  Hits         5445     5445
  Misses        560      560
  Partials      226      226

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 dd81dfd...b0d965d. Read the comment docs.


[DC-997] Build conflicts due to nightly builds running on forks

DC-997 Add check for repo for builds on develop (prevents nightly clash)

Thanks @dcampbell-vumc. I will wait to merge this until tomorrow after verifying that the nightly build on my fork is not run.


set up an https self-signed certificate during installation if user desires so

Currently, we have a shortcut to the k8s dashboard in the webportal. However, after the user installs a fresh new openpai cluster, he/she cannot access the dashboard by default. Because it requires he/she set up an https certificate.

we can make openpai generates a self-signed certificate to let the fresh users access the k8s dashboard

After discussion, we think that the self-signed certificate is not safe and it should not be made as a default. So we should add an explicit flag. If user sets the flag, we make the self-signed certificate for him.
Also, the doc needs a re-org.

@hzy46 It is not clear in the guide, I created an https self-signed certificate follow the doc but don`t know how to use it.

Thanks, the doc problem is known. We will fix it recently.

Fixed in #5078 and #5076


Support datetime range query with number

Currently, for a range query on a datetime field, we convert the bounds only if they are defined as an Rfc3339 string.
We could also support integer values (and maybe float?). But for that, we need to define a default unit.
I have a preference for milliseconds:

it's clearly easier from the user's point of view... entering nanoseconds is very boring
milliseconds will be the default format in aggregations too.
(bonus) it's the default format in elasticsearch range query.

And if you need nanoseconds, then you have to express the bounds in Rfc3339 strings.

I prefer SI units: so seconds coupled with support for float to handle subsecond digits. Otherwise, millisecond is ok. We should also support a date parser in range queries.

We should also support a date parser in range queries.

Do you mean by that to allow the user to define a format so that we are able to convert to the right unit internally?

Wouldn't it be cleaner to apply try and parse according to [output] + input_formats (where + stands for concatenation).
The rationale here is that users are more likely to use the format that they see in the output. (and copy paste it)
I also suggest we default output format to the first input_format.