Support for JSON schema cross-file references.

AFAIK This is valid JSON schema references:
definitions: { '$ref': 'another-file.json#/definitions' }

This should be supported in go-swagger. Not sure how much effort is needed tho. This allows multiple schema to share definitions or for splitting large schema into smaller files, for example.

I can't find it here as being supported: https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#definitionsObject
I'll ask though and see if perhaps it should be.

Its part of JSON Schema, which I think is what the swagger spec defers to. Not sure if the extent is specified in the schema, I'll dig up something. It does enable a lot of interesting use cases for the specs that we want to use, though.

This is from the spec on the swagger.io site. So, yeah it is officially recommended :-)

I'll see if I can help you with a PR

There has been a bunch of discussion on these things in the swagger-spec repo. But as things stand, while json schema supports it, it's not supported for swagger at this point.
The markdown document linked to earlier is the source of truth for the swagger 2.0 spec definition.
it wouldn't be hard to support it, but swagger currently doesn't allow for it.
@webron  can you confirm that what I wrote here is the actual state of affairs

People tend to confuse the structure of the Swagger spec with JSON Schema, because there are similarities between the two. That said, just because we have definitions in the Swagger spec, doesn't mean it's the same definitions as defined by JSON Schema. We use the same name, but it's not exactly the same thing. Right now, we do not allow referencing the entire definitions to an external source.

@casualjim @webron the markdown you linked contained the exact same text. https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#file-structure

However, parts of the definitions can be split into separate files, at the discretion of the user. This is applicable for $ref fields in the specification as follows from the JSON Schema definitions.

I'm not confusing swagger with JSON Schema, but this is in the spec. So if this shouldn't be supported, why is it still in the spec? Should it be removed?

As I stated earlier though, the spec files gets large pretty quickly as we're adding features. The ability to compose them up from smaller files will be a very crucial feature for us soon.

But you can reference to URL's not just to local files wherever you would reference the definition.
Things don't need to be defined in 1 file, but you also don't strictly need to import global definitions. You can just reference remote entities
{ "$ref":  "http://someurl.somewhere.example/#definitions/Person" }

So re-posting from the chat, in case anyone else's searching for this issue: Per-model reference works. Referencing the whole definitions key does not.


::first-letter and ::first-line pseudo-elements are now printed in black

These styles come from the H5BP project, so you should check to see if those folks want these changes there and we can then pull them in. Thanks!


"true" in console

this is showing when I open a crate with a physical key, doesn't matter the crate

Which version of CC?

https://github.com/badbones69/Crazy-Crates/releases/tag/v1.9.9

I am also experiencing this.

Build version from here doesn't have the true in console.
Some commit from the last release to now fixed it.


[ENG-1578] Updated Method for Registration View-Only Link

Ticket: ENG-1578
Feature flag: n/a

Purpose
The purpose of this change was to redirect the user from the read only version of the registration to the Dashboard. The guidance for this change may be found here: https://guides.emberjs.com/release/routing/redirection/.
Summary of Changes
The stopViewOnly() method was modified to include the Ember transitionTo() method. Also, the unused WindowLocation import was deleted. Both changes involved the following file:
-lib/osf-components/addon/components/banners/view-only-link/component.ts
Side Effects
Should the fix not work, then the user will not be redirected to the Dashboard and the view-only link banner will not be removed.
Test Plan
-Login to the staging2 Development OSF.io portal on either Chrome, Firefox, or Edge at: "https://staging2.osf.io/profile/".
-Create a Registration with a view-only link where one user is an Admin and the other has only read permissions
-Log out of the Admin after successful creation, log in as the read-only user
-Navigate to the Registration with the VOL link and click 'Leave the View'
-Verify that the redirect does indeed occur to the Dashboard and that the banner notification is removed
-Optional but recommended: Verify changes in alternative browsers, including Incognito mode.

@adlius Ok, tests are now passing.

@adlius Ok, let me check. Node-license had been a previous blocker.

@adlius view-only-link template now includes the {{on 'this.click}} modifier for both this.stopViewOnly to stop the view only and for @manager.cancel to remove the button. I need to verify if the node-license ticket is still a blocker so I can create a new Registration to fully test locally. In the meantime, if there is an alternative way of testing Ember changes within the browser I would be happy to pair on that.
Also, "this.click" was recommended by ember-template-lint but we currently use "click". I only saw "click" on the Ember documentation shared. In this case, would you prefer me to follow the linting instructions or Ember/OSF guidance?

All changes have been completed and checks pass.

Could we update tests to ensure the alert disappears after the Leave this view button is clicked?

Could we update tests to ensure the alert disappears after the Leave this view button is clicked?

Hey @fabmiz this was brought up during the development process and again during testing. Until the current blocker of local development is up, this is not feasible. If you like, I can create a (development) testing ticket and pick it up for this upcoming sprint.


De-dot labels

Labels are supposed to be simple key/value pairs. If they contain dots, it creates a nested object structure. So for all non-top-level labels, the dots should be replaced with underscores.

MDC is not mapped to labels anymore, but to the top-level. If users want to add a label via MDC, they can do MDC.put("labels.foo", "bar");. They are then responsible for not adding another dot in the field name.


[BUG] Import  Error:  Start row (2) is beyond highest row (1)

I have set headingRow to 1
bug still error : Start row (2) is beyond highest row (1)
version 3.1

Please create a new ticket with the issue template filled. The issue template is required for us to be able to help you and is automatically available for you when opening a new issue, please do not remove the contents of the issue template.


Receiving this error often Error: MessageRaw validation failed: source: unknown is not a valid enum value for path source

ERROR:  Error: MessageRaw validation failed: source: unknown is not a valid enum value for path source.
at ValidationError.inspect (/codechat/node_modules/mongoose/lib/error/validation.js:50:26)
at formatValue (node:internal/util/inspect:805:19)
at inspect (node:internal/util/inspect:364:10)
at formatWithOptionsInternal (node:internal/util/inspect:2298:40)
at formatWithOptions (node:internal/util/inspect:2160:10)
at console.value (node:internal/console/constructor:342:14)
at console.log (node:internal/console/constructor:379:61)
at console.log (/codechat/node_modules/@sentry/utils/cjs/instrument/console.js:38:20)
at MessageRepository. (/codechat/src/whatsapp/repository/message.repository.js:53:25)
at Generator.throw () {
errors: {
source: ValidatorError: unknown is not a valid enum value for path source.
at validate (/codechat/node_modules/mongoose/lib/schemaType.js:1385:13)
at SchemaType.doValidate (/codechat/node_modules/mongoose/lib/schemaType.js:1369:7)
at /codechat/node_modules/mongoose/lib/document.js:3042:18
at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
properties: [Object],
kind: 'enum',
path: 'source',
value: 'unknown',
reason: undefined,
[Symbol(mongoose#validatorError)]: true
}
},
_message: 'MessageRaw validation failed'

Not enough context to understand your issue.
Reopen your issue here.


docs(ts): adapt some invalid imports

Description

Type of change

[x] Documentation change (pure documentation change)

What's Changed

#626


Fix invalid formatting and autogenerate examples

Looks like installation of dependencies has broken:
  File "/home/runner/.local/lib/python3.6/site-packages/pipenv/vendor/requirementslib/models/requirements.py", line 577, in parse_extras
    self.line, extras = pip_shims.shims._strip_extras(self.line)
TypeError: 'NoneType' object is not callable

Sorry for late update, I've addressed the points from previous review.


Third Maximum number

Can you please assign this to me, I would like to do it!

You can start working on this issue. All the best!

Hey, can I take up this issue? I'll do it in Java


chore: add keyword

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


transfer of mina points to the wrong account

mina, two accounts opened in my name appear on the panel. But I have an account. The 3750 points that appear here are my original account. But my duties have been transferred to an account with 2600 points. I request that these accounts be merged and transferred to my main account, Eray#1382.

I'm waiting for your return

I'm waiting for your return

Closing this issue as it is stale for a long time.


Online-849 Adds link to course page URL for Basket Item title

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Fixes https://github.com/mitodl/mitxonline/issues/849
What's this PR do?
Adds course page link if any to the basket item title URL.
How should this be manually tested?

Add a course to the cart.
Visit cart.
Click on the course title. It will redirect to the product page.

Screenshots (if appropriate)
https://user-images.githubusercontent.com/52656433/184867180-f7378bcb-9926-4274-9864-4dcbf78048ec.mov

Completely up to you, but I'm wondering if we should open the course page in a new browser tab or remove target="_blank" and open the course page in the current tab?
Other than that thought, this looks good. Thank you!

Not sure. I am also confused on this one. At first, I was about to remove it :)
@pdpinch What's your say on this one?

This issue is fixed under https://github.com/mitodl/mitxonline/pull/877 by @collinpreston. Closing this PR.


About the invalid parameter

What the principle of the invalid, it seems not clearly, if I have a courseid = 'CS307', we know this is valid, But if it is courseid = '307CS', maybe it is invalid? Other value are the same, it seems no simple to judge valid and throw out some parameter.

A courseId is valid if it has been added to the system with CourseService#addCourse().


Graphql testnet crashed

https://sui-testnet.mystenlabs.com/graphql
RT.

Thanks for your report! Should be fixed today and I will update it here.

This should now be fixed.
{
  "data": {
    "checkpoint": {
      "sequenceNumber": 38189304,
      "timestamp": "2024-05-20T22:51:19.026Z"
    }
  }
}


The function 'getAccountMetadata' can't get account metadata.

I got an empty response when the getAccountMetadata() parameter is address.
By modifying the parameter from address.plain() to publickKey, I was able to correctly receive the metadata entered in the account.
getAccountMetadataByKey() and getAccountMetadataByKeyAndSender() have the same problem.
https://github.com/nemtech/nem2-sdk-typescript-javascript/blob/master/src/infrastructure/MetadataHttp.ts
This is the code that worked correctly.
/**
     * Returns the account metadata given an account id.
     * @param account - Account address to be created from PublicKey or RawAddress
     * @param queryParams - Optional query parameters
     * @returns Observable<Metadata[]>
     */
    getAccountMetadata(account, queryParams) {
        return rxjs_1.from(this.metadataRoutesApi.getAccountMetadata(account.publicKey, this.queryParams(queryParams).pageSize, this.queryParams(queryParams).id, this.queryParams(queryParams).order)).pipe(operators_1.map((response) => {
            const metadataEntriesDTO = response.body;
            return metadataEntriesDTO.metadataEntries.map((metadataEntry) => {
                return this.buildMetadata(metadataEntry);
            });
        }), operators_1.catchError((error) => rxjs_1.throwError(this.errorHandling(error))));
    }

This was the rest issue as not handling address properly. It seems this has been resolved in new rest pushes


RuntimeError: CUDA error: named symbol not found

I am trying to quantize the llama-2-7b-chat-hf using the gpt fast using:-
python quantize.py --mode int4 --groupsize 32
on Kaggle using Kaggle T4*2 GPU.
I  have installed pytorch nightly using:-
pip install torch==2.3.0.dev20240117+cu121 --index-url https://download.pytorch.org/whl/nightly/cu121
I had even tried changing dtype from torch.bfloat16 to torch.flat32. But got the same error again.
However, I get this error message:-
Loading model ...
Quantizing model weights for int4 weight-only affine per-channel groupwise quantization
linear: layers.0.attention.wqkv, in=4096, out=12288
linear: layers.0.attention.wo, in=4096, out=4096
Traceback (most recent call last):
File "/kaggle/working/quantize.py", line 605, in
quantize(args.checkpoint_path, args.mode, args.groupsize, args.calibration_tasks, args.calibration_limit, args.calibration_seq_length, args.pad_calibration_inputs, args.percdamp, args.blocksize, args.label)
File "/kaggle/working/quantize.py", line 552, in quantize
quantized_state_dict = quant_handler.create_quantized_state_dict()
File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/kaggle/working/quantize.py", line 416, in create_quantized_state_dict
weight_int4pack, scales_and_zeros = prepare_int4_weight_and_scales_and_zeros(
File "/kaggle/working/quantize.py", line 348, in prepare_int4_weight_and_scales_and_zeros
weight_int32, scales_and_zeros = group_quantize_tensor(
File "/kaggle/working/quantize.py", line 131, in group_quantize_tensor
scales, zeros = get_group_qparams(w, n_bit, groupsize)
File "/kaggle/working/quantize.py", line 66, in get_group_qparams
assert torch.isnan(to_quant).sum() == 0
RuntimeError: CUDA error: named symbol not found
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

Did u figure out this question? I also has this question

Did you figure out this question? I also has this question

Did you figure out this question? I also has this question

try another gpu


Running Cartographer in container and simulate results

Hi!
For my thesis project I'm working with both AMCL and Cartographer in a containerized environment. Luckily for me, Cartographer has an already built Dockerfile and I was able to create a docker image using ubuntu bionic. My question is: where can I find some documentation (if it exists) on how to run the pure localization algorithm inside a docker container? And as an additional question, is there a way to easily simulate the input without using simulators?
Thank you!

I usually double and triple check before posting a question about something and the one time I don't... I've been consistently watching cartographer_ros but cloning the non-ros version of cartographer.


search starting from . (dot ) does not work properly

When we try to search starting from . (dont) it does not show reseults properly and also when press escape after searching with . (dot) page becomes clumsy...

This is fixed. Check out v1.0.1


Embedded Firebird ??

Hi,
Does HikariCP works with embedded Firebird? As much as I know (mentioned in Jaybird Documentation) "only one jvm" can connect to embedded database. Does this mean that one jvm can create any count of connections to embedded database? If yes, is there any configuration for setup.

Should work fine.  Configuration should be as simple as the correct connection URL.


Add support for custom emoji template

Hi,
While using twemoji, we wanted to let user select parsed emojis like normal text, however, we are unable to achieve this by styling the img tag alone because we need:

pointer-event: none to let user select image like normal text
cursor: text to change cursor for UX

However pointer-event: none clashes with cursor: text on the same element, we needed to create a container that wraps the emoji element in order to achieve what we want.
We are creating this PR hoping twemoji could implement built in support for such functionality.
Usage with the new template option:
twemoji.parse(htmlText, {
  template: (emoji) => {
    return `

        ${emoji}

    `
  },
})

Will have a look next week (now abroad) thanks

there is one bit I don't like too much:
// template function for custom emoji wrapping

a tempalte for wrapping doesn't sound congruent with the names chosen to add wrapping functionality.
The current emoji template is already the image with a custom src or a className.
That means that you can inject the parsed string and right away do the following:
// DOM4 + ES6
twemoji.parse(container);
container.querySelectorAll('img.emoji').forEach(img => {
  const div = img.ownerDocument.createElement('div');
  img.replaceWith(div);
  div.append(img);
})

If you are generating emoji on the server you can obtain similar results through a RegExp that catches //g and replace with surrounding div.
As Summary
I'm not sure this functionality is really needed in core but we might just bring it in as long as:

there are tests that shows this functionality actually works with both strings and DOM nodes. Current proposal assumes people uses strings when actually most developers use DOM and this will break.
the changes are done to the correct file which is the generate file, not the lib itself.
the name is not actually template because we are talking about a wrap and it could be either for strings or DOM nodes (the logic should be compatible with DOM too, the ret = template(ret) is not going to work here)

Hi @WebReflection,
Thanks for the feedback and suggestion, much appreciated.
We are already using a similar approach to your suggestion for production. We ran some benchmarks and the results shows that in order to achieve what we want, DOM parsing is up to about 4 times slower than our proposal.
We believe that this new option provides a simpler way for users who wants to apply container elements to the emoji or modify the emoji element, with the benefits of better performance and less code required.
We agree that 'template' might not be the best name, we are open to any name suggestions.

beside the name, the logic is not compatible with current API because it accepts both strings and DOM nodes.
The template-but-not-really method should not just return a string but a DOM node when DOM is used instead of strings, which is the most secure way to use twemoji, hence the preferred/suggested one.
Summary
the follwing:
twemoji.parse(htmlText, {
  template: (emoji) => {
    return `

        ${emoji}

    `
  },
})

should work also via DOM input
twemoji.parse(htmlText, {
  template: (emoji) => {
    var div = emoji.ownerDocument.craeteElement('div');
    div.className = 'emoji-container';
    emoji.parentNode.replaceNode(div, emoji);
    div.appendChild(emoji);
    return div;
  },
})

or something similar.
Long story short, this PR is incomplete and incompatible with current API as it is.

P.S. we've tested DOM vs strings too and if you pass all nodes at once you shouldn't have that bad performance. The key is to pass incremetally all new nodes instead of hwole document and you could use a document fragment for that. Anyway, let's try to adress outstanding issues first and see if we can put this in

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


Arrow keys are not working with initialSlide

Hi
I am using slick slider from https://kenwheeler.github.io/slick/. It is working fine unless I add the initialSlide : 8 in the js.
Yes, it is taking me to the 8th slide, but navigation keys(Please ignore the visibility of these arrow keys) on both sides have stopped working.
Please see the code in https://jsfiddle.net/Lx5nzath/
Please help

Reference to #2927
set infinite: true

Thanks @agustinl for the reply.
2 issues :

I do not want the carousel to be repeated. I want to finish this carousel on both sides when they reach the end of values.

All the "cloned slides" have removed the id's from their inside div's. Please see, all the inside div's now have the empty id's.

Thanks

Hi @nitinsinghal123
You set infinite: false and your slider have 12 slides.
You show 6 sliders slidesToShow: 6 and start in the position 8 initialSlide : 8 (9 really because the first slide is 0), so you have 3 sliders in the right to complete the twelves (9 + 3 = 12). You can never move to right because not have more sliders to show.
So, I dont know what the slider it does not allow to move to left.
btw, If you set infinite: false and a slidesToShow: 5 the slider works fine.
Maybe its a javascript core code issue, and not a configuration problem, but this quick fix help you.
$('.center').slick({
  infinite: false,
  slidesToShow: 5,
  slidesToScroll: 1,
  swipeToSlide : true,
  draggable : true,
  arrows: true,
  initialSlide : 8
});```

Thanks, @agustinl for the quick fix.
But in my slider, "Number of slides" & initialSlide are dynamic. It depends on the SQL query results that how many days should be in the slider & which one would be the first slide to be active.
Okay, I will tell you the basic explanation: Normally SQL returns 7-12 days in the query. Then I will set slidesToShow as "7" & initialSlide would be today's date. I hope this will clarify more.
So for that reason, I can not fix initialSlide & I want infinite to be set as false.

@nitinsinghal123
But you know both options, initialSlide and slidesToShow. You get this value from the query result.
So, you can init your slick slider with these options from the SQL query result.
I think you will have to mix php and javascript in your code.
Try create a example in codepen, I dont know why jsfiddle doesnt load slick in your example.

@agustinl: Thanks for the reply. Sorry for the delay. I got busy with another project last week. Now I am back with this.
Yes, I am also initializing my slick slider with these options from the SQL query result.
As you said, I have also created a very simple & same example in codepan. Please see https://codepen.io/hello12345678/pen/YzyRWNd
But this is also creating the same problem. I think if I find out1 what is wrong with this example, I may be able to solve my issue as well.
Please help.

Hi @nitinsinghal123
I think the problem is if you start the carousel with the same number of slides you have.
If you change the slidesToShow to 6 it displays correctly.
I think maybe it is some "problem" of the plugin but If it showed all the slides at the same time, it would stop being a carousel, right?

Hi @agustinl, Thanks for the reply.
"I think the problem is if you start the carousel with the same number of slides you have." -> Actually I want to show one-week ACTIVE results & the rest of them would be in NON-ACTIVE mode. So if the query has return 9 days, then 7 days would be in the first fold & rest 2 would be in the slider. Sometimes it happens that there are only 7 days to show. So how would I solve this problem ?
"but If it showed all the slides at the same time, it would stop being a carousel, right?" -> But there has to an option in the carousel, when it can show all the slides at the same time. Like in my case, sometimes it happens.
Also, I would prefer infinite: false ... is this possible with above conditions ?

About you first question, the only way that I can think, it's initialize the slider depends of slides length.
If is more than 7, use slidesToShow: 7. If is less than 7, dont initialize the slider, and create a "fake" css to simulate the same style.
About the second question, apparently there is no utility for a slider that displays the same number of slides as there are.
Here are a pull request from someone, that I can think have the same problem of you #2822
And on the third question, I think infinite: true is mandatory for sliders with multiple slides.


How to setup correctly

Hi, i have two questions regarding this library.

In order to use this library do I still need to put the script below on my AMP page?

<script async custom-element="amp-analytics" src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js"></script>

How can we use this library if I have GTM setup with GA4 ?

Really appreciate to anyone who can respond to my question.
Thank you

Yep, you still need the analytics library, and this meant to be a native GA4 tracking for AMP. I don't think GTM AMP currently supports GA4 tags.


Add patches to resolve CVE-2024-24786 in external-snapshotter

Description of changes:
Fixes CVE-2024-24786
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Users unable to send ATOM of Osmosis

Overview
Every time you try to send ATOM on Osmosis you get and error in the log "message
:
"failed to broadcast transaction: codespace: sdk, code: 19, description: tx already in mempool"
Thought I'm able to other tokens on osmosis network without any issues at all.
Side Note: When I had a successful send my amount my ATOM on Osmsosis didn't update on app.shapeshift.com
Recreations Steps:

Have a native account with osmosis and ATOM on Osmosis
. Attempt to send ATOM on Osmosis to an address. (If it works at first, then try another send after)
Notice you get a error message everytime you try to sign the message

References and additional details

Acceptance Criteria
Users should be able to send ATOM on Osmosis
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

Was able to send but same issue as #4967

Send modal shenanigans to be tackled in https://github.com/shapeshift/web/issues/5001


How does Github choose the colors?

Does anyone know how Github chooses the color for each language? Your page looks pretty close to a random sample of colors, but there are some coincidences:

Ruby is dark red
Rust is brown (but too light)
Dogescript is doge-colored
Java is coffee-with-milk-colored
Python is close to the blue in the Python logo
Red is red
Rouge is pinkish-red
RUNOFF is sewage-colored
Vimscript is close to the green in the Vim logo
C is grey because it's too serious for colors

On the other hand:

Chapel is not colored like any building material
Elm is not tree-colored
Emberscript is not red/orange
Neither Javascript nor Coffeescript are coffee-colored

If this information is published somewhere (I couldn't find it), it would be interesting to include it in your readme.

Nevermind, I found: https://github.com/github/linguist/pull/2298#issuecomment-90150424
It appears that they are manually chosen, and the logo-related colors are done on purpose.


go.dev is down

go.dev is giving TLS errors. It should be back shortly.
Pinning this issue to avoid duplicate reports.

Mostly back.

Fully back. Apologies for the interruption. Now back to your regularly scheduled programming.

..aand down again 🤷🏻


complex support for vectorized ufunc

import numba, vectorize
@vectorize([numba.complex128(numba.complex128)])
def f(a):
        return a**2 - 1.0

Assertion failed: (isValidElementType(EltTy) && "Invalid type for pointer element!"), function get, file Type.cpp, line 731.
Illegal instruction: 4

Just a note: There is still a problem with math support (operations like a**2 which call pow() are problematic.  What works is:
import numba, vectorize
@vectorize([numba.complex128(numba.complex128)])
def f(a):
        return a*a - 1.0

A new release of Accelerate is coming soon.


Mabey a better way to give insider builds out

Is your feature request related to a problem?
Currently it's kind of a hassle to get insider build. Users have to open the forum, enter the information, wait a few days and sometime manually check for updates to get it. I'm sure it also an annoying task for the one who puts the emails in too. It can also be annoying to switch back to the stable build if the user changes there mind (doesn't seem to have an official way of doing so in documentation) or just want both it compare it or something else.
Describe the solution
Why not making it like how Microsoft (e.g. Windows Terminal) does it they have a separate app with preview text added to the title and a "Pre" text added to the icon. Then users can just download the one they want instantly and without the extra steps of going in and out of preview builds.

There are a couple of reasons we don't but the main one is because of the approval process. Files uses restricted permissions in the store and it's not very simple to get them approved again.


@juvtib Feedback

Summary of the new feature / enhancement
I am responding to the call for feedback on the PowerShell blog.
This project does not make sense to me. And I do not plan on using it in its current form.
I am comfortable referencing Microsoft Docs and the GitHub release notes for updated information on PowerShell.
I think a basic module which simply linked to those resources in the pwsh "logo" or message of the day would add value by increasing the visibility and accessibility of changelog information.
Basically, I'm afraid the WhatsNew module will add lag and errors to the changelogs without adding any compelling automation.
In part, I'm concerned that issues like #10 make it seem that WhatsNew will be an authoritative source of information. And companies might use the results from WhatsNew to justify cutting costs during upgrades. In this scenario, I do not think there is a substitute for reading the changelogs and testing software.

My challenge is for someone to reply with an example PowerShell session that proves me wrong and shows how the WhatsNew module adds value over the existing changelog sources.
Make whatever assumptions you would like including unlimited developer resources and the following feature requests:

The module is built-in to PowerShell.
The module is always up-to-date.
The module has all formatting magic like links, color, word wrap ...
The module provides additional tags on each line like [breaking] for breaking changes.

For example:

The PowerShell WhatsNew module helps me collect all the "breaking changes" in one place which is something I do manually now.
PowerShell 7.2.6
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.
Type 'whatsnew' for changes in this version.

PS /home/michael> whatsnew

...

PS /home/michael> Get-WhatsNew -Heading "breaking changes", "engine updates" -Version "7.2.6", "6.0.0-rc.2"

## Breaking changes

* \[breaking\] Skip null-element check for collections with a value-type element type ([#5432](https://...))

...

## Engine updates and fixes

...

* Fix ForEach-Object -Parallel when passing in script block variable ([#16564](https://...))

I think the WhatsNew module can be made stronger by addressing these concerns.
Regards,
Proposed technical implementation details (optional)
No response

@juvtib - Thank you for the feedback.

@juvtib -- thank you for the feedback. In reference to your post: "My challenge is for someone to reply with an example PowerShell session that proves me wrong and shows how the WhatsNew module adds value over the existing changelog sources." -  We developed Get-WhatsNew, not to replace the existing sources, but to add a local version that folks could explore or setup as a MOTD.  Some folks may not find this format useful and prefer the existing web resources like Microsoft Docs.
My hope is that folks that don't find Get-WhatsNew very helpful to them today, might offer suggestions and additional scenarios, which we could learn from to improve the overall usefulness for everybody.
As an example,

It may be helpful to include other major updates to PowerShell related products like Azure PowerShell
It might be helpful if we included a cmdet that also provide detailed changelog information.

I appreciate your feedback and welcome ideas/scenarios that we could learn from and improve the experience.

Thanks for writing to me.
My mind reels a bit when thinking about what might and might not be included. For example, I found myself giving some impromptu help on the AppX thread. The fact that AppX stopped working in some version of PowerShell sounds like it pertains to an upgrade decision. But the issue doesn't appear in any changelog, commit message, or Microsoft Doc. So, it wouldn't get picked up by WhatsNew. This is an example of why I am nervous about people relying on WhatsNew to make decisions.
Turning to the overall project, it seems like the main work is web scraping. So, if I were working on this, I would try to separate the code for the types of input:

Git Commit Messages
Microsoft Docs
Release Notes

... from specific projects:

Microsoft PowerShell
Azure
...

Then you could keep the idiosyncrasies of specific projects (what headings are used in the release notes) separated from basic scraping issues (WhatsNew can't ingest commit messages).
Finally, I believe the module should ask for updates if the computer is online. An easy way for WhatsNew to fail would be for its users to fail to update before they begin their research. It would be helpful to give a specific command: Update-Module -Name Microsoft.PowerShell.WhatsNew I find Microsoft.PowerShell.Core, PowerShellGet, and PackageManagement confusing. And I use PowerShell every day.
Hopefully, others can come and present the cases you are looking for.
Take care,

I was thinking about this more. Maybe part of my issue is cultural. The phrase "make upgrade decisions" means more to me than a fun, message of the day app. Maybe I think WhatsNew is a more serious project than what you intended.

Maybe a good idea would be to invite the community bloggers to contribute bite-sized messages.


ARROW-8426: [Rust] [Parquet] Add support for writing dictionary types

In this commit, I:

Extracted a build_field function for some code shared between
schema_to_fb and schema_to_fb_offset that needed to change

Uncommented the dictionary field from the Arrow schema roundtrip test
and add a dictionary field to the IPC roundtrip test

If a field is a dictionary field, call add_dictionary with the
dictionary field information on the flatbuffer field, building the
dictionary as the C++ code does and describe with the
same comment

When getting the field type for a dictionary field, use the value_type
as the C++ code does and describe with the same
comment

The tests pass because the Parquet -> Arrow conversion for dictionaries
is already supported.

Aaaand I see now that the ticket includes writing the dictionary data, while this PR only writes the dictionary schema. Well, this is part of the work needed anyway... getting to the rest of it now 🤦♀

Oops, I... thought I knew what I was doing a little bit, and I clearly don't at all 😅
I think I went down this path because rust/parquet/src/arrow/schema.rs had the commented-out dictionary field that was added to this branch in this test:
#[test]
    fn test_arrow_schema_roundtrip() -> Result<()> {
        // This tests the roundtrip of an Arrow schema
        // Fields that are commented out fail roundtrip tests or are unsupported by the writer

and I thought "the writer" in this comment and exercised by this test meant the Arrow -> Parquet writer. But it's the changes in rust/arrow/src/ipc/convert.rs that get this test to pass, so I'm not sure where I got turned around...
Am I at least correct that adding dictionary support will involve adding support for the dictionary schema as well as the dictionary data? And that neither of those are done yet?
I'm also unclear about what I should do with this PR based on your comment; should I close it for now or fix the signed index type issue and reopen it against master?

Am I at least correct that adding dictionary support will involve adding support for the dictionary schema as well as the dictionary data?

Ok well I just found https://github.com/apache/arrow/compare/rust-parquet-arrow-writer#diff-b1d078f4cb4841c220e8a274543ef616R356-R360 which seems to indicate no, there isn't actually schema conversion that needs to be done :(

@nevi-me Regarding

We might not be merging the changes on this branch into the main branch in time for 2.0.0 (est October 9)

How can I best help with getting the rust-parquet-arrow-writer branch ready to be merged into master? I see you're concerned about test coverage, and I think writing more tests would help me to understand all the things I clearly don't 😅 What parts need test coverage the most, in your opinion?

Hi @carols10cents, my apologies for the delay.

Am I at least correct that adding dictionary support will involve adding support for the dictionary schema as well as the dictionary data? And that neither of those are done yet?

The Parquet format's dictionary semantics are in my understanding different to Arrow, in that we could have a StringArray in Arrow that gets saved with Parquet's dictionary encoding. I'm still going through the rest of the Rust Parquet codebase though, so I'm not speaking from any authority.
My comment was more in passing, and generally around dictionary support in IPC, in that beyond serializing an arrow::datatypes::Schema to arrow::ipc::Schema, there might be little in relation between the file formats.

How can I best help with getting the rust-parquet-arrow-writer branch ready to be merged into master?

The main blocker right now is computing nested definition and repetition levels for deeply nested arrays (see https://github.com/apache/arrow/tree/master/cpp/src/parquet/arrow for the CPP implementation). I've been working on that on and off, due to time constraints (and the need to spend a good chunk of time per session; which I haven't had much of).
Perhaps I can commit my work so you can have a look at that. I'll also open more JIRAs for work I believe we'd need to cover.
Writing more test cases will also def help us.

Merged


IPv4 link local packets are not sent with ARP ethernet type

When testing IPv4 link local address configuration with SAM E70 Xplained board, it was found that the five first packets where Zephyr announces its intended link local address are sent with ethernet type 0x0800, which means IPv4. The packets should instead be sent with ethernet type 0x0806, which is ARP. Wireshark thus sees five bogus IPv4 packets and complains that the IP version in the IPv4 header is zero, but must be 4.
Setting type 0x0800 probably happens in ethernet_send() in subsys/net/l2/ethernet/ethernet.c, since the net_pkt_family(pkt) is AF_INET. Now the problem is that while the called ethernet_ll_prepare_on_ipv4() function correctly checks for net_pkt_ipv4_auto(pkt), ethernet_send() is also used when sending regular IPv4 packets and ARP ones if necessary, which means that changes to the logic handling also IPv4 link local ARP messages seems to get a bit tricky in that function. ~Thus only a bug report and no patch.~
It also seems that the IPv4 link local packets are all ARP requests, but the latter ones are not ARP announcements, since the packets always have the same content and do not change the sender IPv4 address from <IP_ADDRESS> to the selected IPv4 interface address, see https://tools.ietf.org/html/rfc3927#section-2.4.
This is the hex dump from wireshark, notice the ethernet type 0x0800 in the 13th byte and the all zero sender address at the 28th byte:
0000   ff ff ff ff ff ff fc c2 3d 12 f3 ab 08 00 00 01
0010   08 00 06 04 00 01 fc c2 3d 12 f3 ab 00 00 00 00
0020   00 00 00 00 00 00 a9 fe 19 00 00 00 00 00 00 00
0030   00 00 00 00 00 00 00 00 00 00 00 00

As it is now, IPv4 link local addresses can't work reliably, as they are not recognized by hosts on the link.

Only one assignees at a time please, otherwise it can be unclear who will start to look at the issue.

BTW, there is net_pkt flag for storing necessary info. It is called ipv4_auto_arp_msg, it seems that it is not set or checked properly in the code.

PR #15433 is now fixing the ARP packet type and address issue. There seems to be an excess of 18 bytes attached to the ARP packets as well.

There seems to be an excess of 18 bytes attached to the ARP packets as well.

Fixed also.

There seems to be an excess of 18 bytes attached to the ARP packets as well.

Fixed also.

Fix did not work, but the extra padding has its own issue #15522

The original issue was already fixed and merged to master -> closing.


Small improvements that allow to run the project

I've updated GWT version related to the one needed by Errai 4 beta.
I've also added default page since lack of it leads to an error: "No @Page classes have role = DefaultPage".

Hi @baldram Thank you very much for your contribution.


Cannot read property 'connection' of undefined in client.connect()

Actual behaviour:
Using node-webkit v0.12.3 (Chromium 41.0.2272.76), when trying to use client.connect() after creating the client object with a set of options, an error is thrown - "Cannot read property 'connection' of undefined"
Expected behaviour:
IRC client should connect without error
Error log:
var irc = require('tmi.js');
$scope.client = new irc.client({
	options: {
		debug: true
	},
	identity: {
		username: $scope.username,
		password: $scope.password
	},
	channels: [$scope.channel]
});
$scope.client.connect().then(function(data){
	console.log('connection data...');
	console.log(data);
}).catch(function(err){
	console.log('connection error...');
	console.log(err);
});

...
connection error...
Cannot read property 'connection' of undefined

Server configuration

Operating system: Windows 7 x64
Node version (if applicable): 5.8.0
NPM version (if applicable): 3.7.3
tmi.js version: 1.08

I've considered the possibility that it's some sort of ECMA 6 problem because I had to actually edit your source to remove all the instances of the () => {} function syntax because nwjs v0.12.3's version of chromium isn't fully compatible with ECMA 6 yet. I can't seem to find any ECMA 6 functionality that could otherwise be causing this problem, but it's a thought I had.

Could be, I will investigate this issue and see what I can do, I use Electron and I have no problem with ES6 or whatsoever, I will give node-webkit a try this week and see what's going on.
Thanks!

I can't believe that I forgot to test this issue.. is it still an issue for you @xingped ? Like I said, I know for a fact that tmi.js works fine with Electron..

Haha, I forgot about it too! I actually did switch my project over to Electron a couple weeks ago and it worked perfectly without any modifications. Electron just seems a lot nicer than node-webkit anyways and doesn't crash as much. So it isn't an issue for me anymore!

Awesome :+1: Yeah it's a lot better :smile:


Split /role-list messages

There are too many colour roles to display on command, message should be split to account for the character limit.

Fixed in last set of commits


Is it possible to disable socket calls ?

Hi ,
we have developed an UI from scratch from our but currently not using socket functionality and want to disable the calls from the client. Is there a flag by which we can disable it ?

@netchampfaris I asked about this in Frappeverse webinar and you said it's possible but I am unable to figure out how. If possible can you revert?

app.use(FrappeUI, { socketio: false })

Than you @netchampfaris this helps . It doesn't seems to be working on the released version 0.0.31 but works well on tags 0.0.44. You can close this appreciate your support.


Sending multiple images at once

Is it possible to send multiple images at once through this library?

+1


Upgrade the org.jacoco:jacoco-maven-plugin from 0.8.2 to 0.8.6

Task Description
We need to upgrade the org.jacoco:jacoco-maven-plugin from 0.8.2 to 0.8.6.
Tasks
The following tasks will need to be carried out:

[ ] Update the version in the strongbox-parent project.
[ ] Test and confirm that there are no issues with the core projects (strongbox, strongbox-web-integration-tests, etc) after upgrading.

Help

Check our article on how to upgrade dependencies and plugins.
Our chat
Points of contact:

@carlspring
@sbespalov
@steve-todorov

I can take care of it

@cunhazera ,
Thanks for offering to help!
This particular task is mainly for an event that we're hosting today with the Grace Hopper Celebration Open Source Day. Would you mind holding off for day (if no one picks it up during the event, it's yours), (or picking a non-dependency/plugin upgrade task)? For more details, you can join our chat channel where we can discuss what other tasks might be of interest to you. Thanks! :)

@carlspring thanks for the response. No worries at all :)
Maybe this one (https://github.com/strongbox/strongbox/issues/1873) would be better?

I am a GHC OSD participant. I would like to work on this task

Hi @tanvimehta ,
Yes, please! Go for it! :)

@carlspring thanks for the response. No worries at all :)
Maybe this one (#1873) would be better?

Join our chat channel and we'll find you something! :)

I see there is a merge (Issue#1878) , is it still open for work ??


non-admin installation requires password when installing patch

...
Installed /Users/mabru/miniconda/lib/python2.7/site-packages/nibabel-2.0.0-py2.7.egg
Processing dependencies for nibabel
Finished processing dependencies for nibabel

Create links to python scripts...
>> /Users/mabru/code/spinalcordtoolbox/install/create_links.sh -a
/Users/mabru/code/spinalcordtoolbox/install/create_links.sh -a

Checking for available patches...

Installing patch_2.0.2...
>> unzip -d temp_patch patch_2.0.2.zip
>> python install_patch.py -a
python install_patch.py -a
Password:

Issue comes when creating links:
Update links...
${SCT_DIR}/install/create_links.sh
Password:

tested it on v2.0.6 and it was not fixed. The following line should be changed from:
    # re-create links
    print 'Update links...'
    sudo_links = ''
    if issudo != "":
        sudo_links = ' -a'
    status, output = sct.run('${SCT_DIR}/install/create_links.sh'+sudo_links)

to:
    # re-create links
    print 'Update links...'
    sudo_links = ''
    if issudo == "":
        sudo_links = ' -a'
    status, output = sct.run('${SCT_DIR}/install/create_links.sh'+sudo_links)


Conv3d patch for 1.3 release

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

Do we also need to disable all the conv3d tests due to #1445?

I think we only need to disable the kernel_size 1 test. This should be disabled in both PRs

The test failed for groups=3 and kernel=1 but other tests with kernel=1 look good. https://github.com/pytorch/TensorRT/blob/master/py/torch_tensorrt/fx/test/converters/vanilla/test_convolution_vanilla.py#L79-L83
Just curious, is the kernel=1 be the reason or groups=3 be the reason? @peri044

The test failed for groups=3 and kernel=1 but other tests with kernel=1 look good. https://github.com/pytorch/TensorRT/blob/master/py/torch_tensorrt/fx/test/converters/vanilla/test_convolution_vanilla.py#L79-L83 Just curious, is the kernel=1 be the reason or groups=3 be the reason? @peri044

This error happens when this is true  -  is_3d_conv && filter.depth == 1 && (input.depth != 1 || output.depth  != 1)
We have an internal fix for this issue and this will probably land in the next minor or patch release.

redirect this PR into #1485 and use that PR to get it into release/1.3, that way we can show correctness for both PRs

Closing this since it is merged in #1485


[WIP] Support CN for server cert selection

[WIP] Support CN for server cert selection
After this change, s2n will use the CommonName entry from the Subject of
to select from certificates added to s2n_config. Usage of CN has been
deprecated since RFC2818 in favor of SAN. This change only uses the CN
if no valid SANs are available in the cert.
Specifics:

Multiple CommonNames are supported, though practically usage should be
very rare. A CAB thread on dropping support for it:
https://cabforum.org/pipermail/public/2016-April/007242.html .

TODO:
[x] Convert SAN storage to s2n_array and kill the x509_cert handle
[] Update fuzz test to cover CN
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

:exclamation: No coverage uploaded for pull request head (cert_by_name_cn@90ddd1c). Click here to learn what that means.
The diff coverage is n/a.

Since this is the next iteration of server cert selection, pushed https://github.com/awslabs/s2n/pull/1034 to a feature branch and the diff here is compared to it.
will change this PR to have master as destination once that PR is merged.

Moved base branch to master now that #1034 was merged


pytypeinfo: rename is_instance to check

While working on #1276 I realised that PyTypeInfo::is_instance is actually a bit misleading.
The default implementation of it uses PyObject_TypeCheck, which is similar to isinstance() but doesn't call the __isinstance__ hook.
So I think it's better to make this name clearer. I went for check and check_exact, inspired by PyObject_TypeCheck.
This is a little breaking, but I think in practice this should only affect people who are manually implementing PyTypeInfo (hopefully very few users).

What do you think about type_check and type_check_exact?

Yeah that's probably even clearer!

I understand the motivation, but I still prefer the is_ prefix.

I understand the motivation, but I still prefer the is_ prefix.

I do agree is_ is nicer. I'd really like to move away from is_instance now that I'm aware this is subtly different to the other is_instance functions. Otherwise I think we're asking for people to write bugs by accident!
How about T::is_type_of and T::is_exact_type_of ?
I think that reads quite naturally - e.g. PyList::is_type_of(list) compared to the original PyList::is_instance(list).

Changed to is_type_of and is_exact_type_of. @kngwyu would you be ok with these names?


Create model and API endpoints to manage shared live media resources

Purpose
During a Webinar, an instructor wants to share Media with student. The media can be a PDF or any office document.
The instructor needs in a first time to upload these documents and once the convert process applied the document can be shared with students.
In this first PR we create the corresponding model and all the endpoints needed to manage shared live media resources
Proposal

[x] create the model and the associated migration
[x] create the API endpoints to manage shared live media resources

@sampaccoud @kernicPanel While you were netpicking on naming things I pushed some few fixup. I just forget all the tests on the initate-upload endpoint. It's fixed. Happy review

@sampaccoud @kernicPanel ready for a new review


Exploring the Potential of Dynamic Quantisation for Variable-Length Inputs in AutoAWQ

Dear AutoAWQ Maintainers,
I trust this message finds you well. I am writing to you today to broach a subject that I believe could significantly enhance the utility and efficiency of the AutoAWQ framework, particularly in scenarios involving variable-length inputs.
Having perused the documentation and experimented with the current capabilities of AutoAWQ, I've observed that the quantisation process is static, with a fixed quantisation configuration applied across all inputs. While this approach is undoubtedly effective for a majority of use cases, it may not be optimally efficient for variable-length inputs, which are commonplace in natural language processing tasks.
The crux of my proposal is the introduction of dynamic quantisation strategies that adapt to the length of the input sequences. The rationale behind this suggestion is twofold:

Resource Optimisation: By tailoring the quantisation granularity and precision to the input length, we could potentially reduce the computational overhead for shorter sequences, thereby conserving valuable processing resources.

Performance Consistency: For longer sequences, a more aggressive quantisation could be employed to maintain a consistent inference speed without exceeding memory constraints, especially on devices with limited VRAM.

I envisage a system where the quantisation parameters are not static but are dynamically selected based on the input sequence characteristics. This could involve a heuristic or a learned model that predicts the optimal quantisation configuration for a given input.
I am keen to hear your thoughts on this concept and whether such a feature aligns with the roadmap for AutoAWQ. I believe that incorporating dynamic quantisation could be a substantial step forward in making the framework even more versatile and performance-conscious.
Thank you for your time and for considering this proposal. I am looking forward to the possibility of engaging further on this topic and contributing to the development of AutoAWQ.
Best regards,
yihong1120

Dear @yihong1120,
Thank you for your proposal. AWQ is incredibly robust independent of your dataset and length of samples. This is different from GPTQ or GGUF which may have high sensitivity to the data you provide.
I have always wanted to explore how we can best spend our resources. For example, how can we spend more resources quantizing the layers that are highly sensitive to being quantized?
One way to measure which layers are highly sensitive to quantization is to compare the loss history. I have not yet figured out how to use this information to dynamically adjust the scales.
https://github.com/casper-hansen/AutoAWQ/blob/5b9f3c47c68a3aa632196a9d909290d0b8d26add/awq/quantize/quantizer.py#L236-L239


Centralized guess dim order

          Just curious. I think this may be the third time we have this code in multiple places? (Base) TiffReader, this one, and somewhere else?? Should we centralize this to a standard function that is called `guess_dims_from_shape` that all of these different Readers call?

Originally posted by @evamaxfield in https://github.com/bioio-devs/bioio/pull/47#discussion_r1666999390

Looking back on this is this still something we want to do? I think I am against it because there is a certain precedent that comes with the specific file types where the logic is present that is not necessarily generalized. @evamaxfield

I just did a quick search through all the plugins. The guess_dim_orders are all different throughout. Closing!


What shoud a lottery smart contract do?

A lottery smart contract should perform several key functions to ensure the fairness and transparency of the lottery process. Here are some of the things a lottery smart contract should do:

Ticket Purchase: The smart contract should handle the process of ticket purchase. It should allow users to buy tickets by sending a specified amount of cryptocurrency to the contract.

Ticket Validation: The smart contract should validate the tickets purchased by users, ensuring that the tickets meet the required criteria, such as the correct format, valid numbers, or any other specific rules defined for the lottery.

Random Number Generation: The smart contract should generate random numbers to determine the winning numbers. It should use a secure and unbiased method to ensure the randomness of the number generation process.

Prize Distribution: Once the winning numbers are determined, the smart contract should distribute the prizes to the winners automatically. The contract should calculate the prize amounts based on predefined rules and distribute them to the respective winners' addresses.

Security and Transparency: The smart contract should incorporate security measures to protect against potential attacks or vulnerabilities. It should also ensure transparency by making the contract code publicly accessible and allowing users to verify the fairness of the lottery process.

Deadline Enforcement: If the lottery has a specific deadline for ticket purchases, the smart contract should enforce this deadline and prevent ticket purchases after the cutoff time.

Refunds: In certain cases, such as if the minimum number of tickets required for the lottery is not reached, the smart contract should handle the refund process by returning the funds to the participants.

Event Logging: The smart contract should log important events, such as ticket purchases, number generation, and prize distribution. This logging can be used for audit purposes and to provide transparency to participants.

It's important to note that the specific implementation of a lottery smart contract may vary depending on the requirements and design choices. However, these functions generally form the core features of a lottery smart contract, ensuring the integrity and reliability of the lottery process on the blockchain.

from chatgpt 3.5

A lottery smart contract should perform several key functions to manage the lottery game fairly and transparently. Below are the essential tasks a lottery smart contract should handle:

Ticket Purchase:
The smart contract should allow participants to purchase lottery tickets. Participants can choose their desired numbers or rely on random number generation to buy tickets. Each ticket purchase should be recorded and associated with the participant's address.

Prize Pool Accumulation:
The smart contract should keep track of the total prize pool, which is the sum of all ticket sales minus any fees or expenses. The prize pool is the amount that will be distributed among the winners.

Random Number Generation:
For the lottery drawing, the smart contract should have a secure and unpredictable method to generate random numbers. A widely-used approach is to use the block hash of a specific block as the source of randomness. This ensures that no one can predict or manipulate the winning numbers in advance.

Lottery Drawing:
After the lottery ticket sales period ends, the smart contract should automatically trigger the lottery drawing. It will use the generated random numbers to determine the winning ticket(s) or numbers. The drawing process should be transparent and publicly verifiable.

Winner Selection and Reward Distribution:
The smart contract should identify the winning ticket(s) or numbers based on the random drawing. Once the winners are determined, it should distribute the prize pool among the winning participants. The distribution process should be fair and automated.

Handling Unclaimed Prizes:
If there are any unclaimed prizes after a certain period, the smart contract should handle them according to predefined rules. This may involve redistributing the unclaimed portion to future lottery games or using it for charitable purposes.

Security and Auditing:
A lottery smart contract should be thoroughly audited for security vulnerabilities to ensure the integrity of the game. Smart contract code audits are crucial to identify and fix potential issues that could lead to unfair advantages or financial losses.

Transparency and Public Verification:
Transparency is crucial in a lottery. The smart contract should allow participants and the public to verify the lottery drawing process and the distribution of prizes. All critical functions should be open and visible on the blockchain.

Administrative Functions:
The smart contract may include administrative functions for setting parameters such as ticket prices, maximum number of tickets per participant, or the duration of the ticket sales period. These parameters should be adjustable but transparent.

Overall, a well-designed and secure lottery smart contract ensures that the lottery game is conducted fairly, transparently, and without any centralized control. It should instill trust among participants and provide a straightforward, enjoyable experience for all players

from other chatpgt 3.5

Contract Initialization:
Define the contract state, including variables such as the ticket price, lottery duration, maximum number of tickets, and other relevant parameters.
Set the initial state of the contract.

Ticket Purchase:
Implement a function that allows users to purchase tickets by sending the required amount of cryptocurrency to the contract.
Validate the ticket purchase, ensuring that the user's payment matches the ticket price and that the maximum number of tickets has not been exceeded.

Random Number Generation:
Implement a secure random number generation mechanism to determine the winning numbers.
You can use external oracles, such as Chainlink oracles, to fetch random numbers from trusted sources.

Prize Distribution:
Determine the winning tickets based on the generated random numbers and the tickets purchased by participants.
Calculate the prize amounts according to the predefined rules, such as allocating a percentage of the total ticket sales to each prize tier.
Distribute the prize amounts to the respective winners' addresses.

Security and Transparency:
Implement security measures to protect against potential attacks, such as input validation and secure random number generation.
Make the contract code publicly accessible and auditable to ensure transparency.
Consider implementing mechanisms to prevent front-running or other types of manipulation.

Deadline Enforcement:
Implement a mechanism to enforce the lottery's deadline for ticket purchases.
Prevent ticket purchases after the cutoff time and initiate the random number generation and prize distribution processes.

Refunds:
Handle scenarios where the minimum number of tickets required for the lottery is not reached.
Implement a refund mechanism to return funds to participants in such cases.

Event Logging:
Log important events, such as ticket purchases, number generation, and prize distribution.
Emit events that can be easily tracked and audited by participants.

Design：
Definition: A Lottery is a programmable asset, an alternative CW721 smart contract. Lottery is a contract that can hold prizes, where the initial prize is the money from users buying tickets (later, sponsorship or other rewards may be considered).
Lottery categorization by periods: Hourly, Daily, Weekly, Monthly, Yearly.
Lifecycle: Lotteries are automatically created by a platform or DAO contract. Lotteries can be purchased until the deadline. After the deadline, the lottery is drawn, and once claimed by the winners, it can be traded as a proof of ownership, akin to a typical NFT.
Actions: Buy, Draw, Send, QueryPrize.

Lottery is also a NFT contract，the owner can use the standard cw721 functions.
When a user buy a ticket of the Lottery，user will get a nft ticket

Hi @lshoo , I am a rust & blockchain beginner. Would like to help you on this project. Let me know, how can I approach !

Hi @lshoo , I am a rust & blockchain beginner. Would like to help you on this project. Let me know, how can I approach !

Thank you for your interest in this project, and welcome to submit a pull request (PR).
How do you plan to get started? Have you worked on CosmWasm-related code before?

No, I have not.

No, I have not.

How would you like to begin, and how can I assist you?

No, I have not.

How would you like to begin, and how can I assist you?

I really don't know. maybe, documentation, small issues which I can fix using chatgpt.
My Discord: arka.poddar, I would like connect with you


Removing the equals character from the Command Prompt Example

Removing the "=" from the Command Prompt examples to fix issue #399.

@elbuhofantasma : Thanks for your contribution! The author(s) have been notified to review your proposed change. @RogPodge

@elbuhofantasma : Thanks for your contribution! The author(s) have been notified to review your proposed change.


More single pages

Pivotal Card 1 - Candidate Page
Pivotal Card 2 - Locality Page
This PR connects the above two pages to the postgres database.

LGTM!


Editor sometimes crashes when selecting meshes with materials in the 3D viewport

Godot version
v4.0.beta.custom_build (1ac7e5a3343ef9f4ecc7c494f7212b7c718520c8)
System information
archlinux; nvidia RTX 3060 video card (proprietary drivers);
Issue description
When switching tabs to a tab that has the material editor open and is showing a material that has 'toon' specular shading, the editor crashes.
$ godot.linuxbsd.editor.x86_64 project.godot
Godot Engine v4.0.beta.custom_build.1ac7e5a33 - https://godotengine.org
Vulkan API 1.3.224 - Using Vulkan Device #0: NVIDIA - NVIDIA GeForce RTX 3060 Laptop GPU

WARNING: Blend file import is enabled in the project settings, but no Blender path is configured in the editor settings. Blend files will not be imported.
     at: _editor_init (modules/gltf/register_types.cpp:61)
WARNING: FBX file import is enabled in the project settings, but no FBX2glTF path is configured in the editor settings. FBX files will not be imported.
     at: _editor_init (modules/gltf/register_types.cpp:85)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.beta.custom_build (1ac7e5a3343ef9f4ecc7c494f7212b7c718520c8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib/libc.so.6(+0x38a00) [0x7f792495ea00] (??:0)
[2] godot.linuxbsd.editor.x86_64(+0x4d40a8d) [0x556ccf212a8d] (??:0)
[3] godot.linuxbsd.editor.x86_64(+0x22dc7c5) [0x556ccc7ae7c5] (??:0)
[4] godot.linuxbsd.editor.x86_64(+0x1ccfe38) [0x556ccc1a1e38] (??:0)
[5] godot.linuxbsd.editor.x86_64(+0x4a241b6) [0x556cceef61b6] (??:0)
[6] godot.linuxbsd.editor.x86_64(+0x475dfd7) [0x556ccec2ffd7] (??:0)
[7] godot.linuxbsd.editor.x86_64(+0x4a1f969) [0x556cceef1969] (??:0)
[8] godot.linuxbsd.editor.x86_64(+0x4a1fcac) [0x556cceef1cac] (??:0)
[9] godot.linuxbsd.editor.x86_64(+0x2b9609f) [0x556ccd06809f] (??:0)
[10] godot.linuxbsd.editor.x86_64(+0xae0f3b) [0x556ccafb2f3b] (??:0)
[11] godot.linuxbsd.editor.x86_64(+0xa89431) [0x556ccaf5b431] (??:0)
[12] godot.linuxbsd.editor.x86_64(+0xa7b8e9) [0x556ccaf4d8e9] (??:0)
[13] /usr/lib/libc.so.6(+0x23290) [0x7f7924949290] (??:0)
[14] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f792494934a] (??:0)
[15] godot.linuxbsd.editor.x86_64(+0xa87725) [0x556ccaf59725] (??:0)
-- END OF BACKTRACE --
================================================================
Aborted (core dumped)

Steps to reproduce

Open the minimal reproduction project (or create a new project with 2 scenes: a main and a MeshInstance3D that is placed in the main. The MeshInstance3D should have its own embedded mesh, which should have an embedded standard material where the specular shader is set to 'toon').
Open the scene fo the MeshInstance3D.
Select the mesh in the node editor on the right
Select the material
Go to the Main scene and select a node
Go back to the MeshInstance3D scene
The editor will now crash

After crashing once it might crash immediately when starting the editor. Removing the .godot folder seems to prevent that
Minimal reproduction project
tooncrash.zip

I think the node selection is the issue, not the toon material part. I've had numerous crashes when clicking meshes in the 3D editor viewport in 4.0.beta f692b4768 (a good dozen or so at this point).

I just checked and the crash happens indeed when no shader is selected.
It just crashes when going to the tab of a scene where the (standard) material editor is opened.

I'm also getting reproducable crashes every time I'm clicking meshes (simple plane meshinstance3d with a shader material) to select them in the viewport on 4.0.beta8 on macOS 13. However, clicking the same meshes in the node tree to select them works fine, so at least in my case it's something to do with viewport click selection rather than node selection in general.

Can you reproduce this in any of the earlier 4.0 betas to determine when the regression started?

Just tried it now on 4.0.beta7 and it didn't crash there selecting a mesh that crashes if I click it in beta8

Tried it now in beta 9 and it doesn't crash clicking the mesh in the viewport. So maybe it was just in beta 8?

Confirmed, the MRP crashes in beta 8 but doesn't crash in beta 9, so it seems this was fixed.


Adapts to Strapi v4

(Duplicates #4, but I messed up when pushing updates. So I had to open this one)
Due to an update to Strapi v4 the API has changed.
This commit adapts the current code to work with the new graphql schema.

Both of your comments in #4 are fixed now. I had to change the datatype of the variable to work.

Thanks!

Damn it, we forgot to update the tests. If you have the time to do this, it would be amazing! Just pass a fixture or two from the API's responses into parseAction().


SDK: Trace spans black boxing

Internally we have a use case of not exposing sub spans when we're in context of specific trace span.
e.g. when in context of AWS SDK span we do not want to expose underlying HTTP request with extra span. So far we mitigated that with a primitive approach, where we were assuming that HTTP request is initialized in sequence synchronously and we were marking given HTTP request to not be instrumented.
This doesn't work for case where AWS SDK approaches temporary network issue and implies a retry, as then following HTTP request happens async and appears as reported, which is not wanted. Very occasionally we observed integration test failures due to that (e.g. https://github.com/serverless/console/actions/runs/4810414588/jobs/8563030944)
This PR introduces an internal concept of black box trace spans. Where we can mark span as black box and that way ensure no child spans of it will be exposed. Even if some logic will add spans to such black box span (which is not prevented in any way), they will not be exposed in final trace report, or propagated to dev mode

Additionally removed debug logs, which were added to help investigate the issue of HTTP spans being exposed when run in context of AWS SDK request

@medikoo But if you use esbuild and your service is not configured correctly to let our SDK know that you are using esbuild the only span you will see are the underlying http requests to the AWS services.
So I am curious if we black box these http request spans does that mean that these traces (with the misconfigured sdk) will have no captured spans or will the http requests not be black boxed because we don't know they are using the AWS SDK?
Here is a sample trace where I am using esbuild and not configuring our sdk manually to know I am using the AWS SDK 👇

Would this trace not include the node.https.request span?

@Danwakeem, nothing will change in this case.
This PR is an improvement to how we black box AWS SDK spans. Note that we black box them already, but with a primitive method, which in a very rare scenario fails. This patch ensures that in this very rare scenario, it'll work as expected.
HTTP spans are black boxed only in context of AWS SDK spans. if there are no AWS SDK spans, there's no black boxing implied (this logic is initiated by AWS SDK instrumentation) So in case of ESBuild when AWS SDK instrumentation doesn't pick up, obviously HTTP spans will appear as they appear now.

Got it, thanks for the clarification 👍


Ignore .DS_Store file

Codecov Report

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

@@           Coverage Diff           @@
##           master      #68   +/-   ##
=======================================
  Coverage   79.87%   79.87%
=======================================
  Files           2        2
  Lines         154      154
=======================================
  Hits          123      123
  Misses         31       31

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 c99524e...d846fc5. Read the comment docs.

@tisnik Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-68


BigWarp: add an image

and other small edits

@bogovicj Thanks for updating the BigWarp page, and for adding the HDF5 file type tag! I've updated the project template to reflect these updates. I've also added BigWarp to the ImgLib2 software ecosystem page.


Update build_steps.sh to pin conda-build to 3.28.4

Pinning conda-build to 3.28.4

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Top of the build.sh file says
# PLEASE NOTE: This script has been automatically generated by conda-smithy. Any changes here
# will be lost next time ``conda smithy rerender`` is run. If you would like to make permanent
# changes to this script, consider a proposal to conda-smithy so that other feedstocks can also
# benefit from the improvement.

So, we can merge this to solve for now but this will get overwritten the next time we re-render.
Hopefully the conda-build issue is resolved upstream soon so we don't need this.


Export Functionality: Preview Data

As an ECMPS user, I want the ability to preview data based on my selections for export so that I can make any updates before I download the file(s)
Acceptance Criteria:
Given a user makes the selection for 'Year', 'Quarter'
And selects one or more options from Monitoring Plan, QA & Certifications, and Emissions
When they click on 'Preview'
Then they see data displayed based on their selections
Given a user has made selections for Year and Quarter
When they only select Monitoring Plan from the 3 available options
Then the 'Preview' option is disabled
Reference Links:
Zeroheight: https://zeroheight.com/37f47ceee/p/81a343-easey-design-system
Invision: https://projects.invisionapp.com/freehand/document/TdahPfbEb
USWDS: https://designsystem.digital.gov/components/overview/

Hey team! Please add your planning poker estimate with ZenHub @addisgmichael @cw-cvp @fanwari1 @JanellC @jeffreyaggrey @mosesdeeCVP @Qb10 @subrataroyCVP

Test Passed


Migrated null safety

Thank you so much for taking your time to help with the library, but I already migrated it to null safety you can have the null safety version on 1.0.0-nullsafety.1 and the null safety is on a separate branch, for the fixed bug can you tell me how to reproduce the bug ?

now we have a stable version with null safety


Handle the case where date may be 0 in Date constructor.

Fixes #10.

Thanks for this.  Published on npm @2.0.2


WIP: Move tests with common setup together to speed up testing time

Please provide a description for what this PR is for.
This PR moves few (security) tests with common (default) setup together to reduce test setup overhead (installing Istio and test backends). It could be more than 3 minutes each, so hopefully we gain ~12 min with this PR.
Future works should organize the rest of the security test cases into fewer unique setup groups.
Issue:
https://github.com/istio/istio/issues/17512
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[X] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@diemtvu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-local-tests_istio
25edba8ee03da5e6dd3f24c41bec769253fe6f19
link
/test integ-security-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@diemtvu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-local-tests_istio
25edba8ee03da5e6dd3f24c41bec769253fe6f19
link
/test integ-security-local-tests_istio

gencheck_istio
25edba8ee03da5e6dd3f24c41bec769253fe6f19
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@diemtvu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-security-local-tests_istio
25edba8ee03da5e6dd3f24c41bec769253fe6f19
link
/test integ-security-local-tests_istio

integ-istioctl-k8s-tests_istio
041c77130e26f626436d34f7984b9505395a2da5
link
/test integ-istioctl-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@diemtvu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
041c77130e26f626436d34f7984b9505395a2da5
link
/test integ-istioctl-k8s-tests_istio

integ-security-local-tests_istio
041c77130e26f626436d34f7984b9505395a2da5
link
/test integ-security-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@diemtvu: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-istioctl-k8s-tests_istio
041c77130e26f626436d34f7984b9505395a2da5
link
/test integ-istioctl-k8s-tests_istio

integ-security-local-tests_istio
041c77130e26f626436d34f7984b9505395a2da5
link
/test integ-security-local-tests_istio

gencheck_istio
ab6be81abd0a4599790a245ed18fa190e67558ce
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for working on this!

looks right to me. Is this ready for review?

It is now (just want to make sure all the tests run correctly). We save about 7 min (out of ~50 for integ-security-k8s) btw.

@diemtvu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
6e835ac834e3ac96ff7bc19a1677ca31155b1d4a
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Adding option to specify a conda channel alias during conda-build

If there are 404 errors for the channels nvidia or rapidsai, then the conda-build scripts can fail. This adds the option to specify CONDA_CHANNEL_ALIAS before calling ./ci/conda/recipes/run_conda_build.sh.
Since we are currently getting these errors, the option has been enabled by default in the docker container builds but will not be used unless manually specified.

Looks fine for now, so long as we circle back on the conda package build commands.


There is a problem with the character translation of the Chinese version

Microsoft PowerToys version
0.59.1
Running as admin

[X] Yes

Area(s) with issue?
Always on Top, ColorPicker, FancyZones, Mouse Utilities, PowerToys Run, Shortcut Guide, Video Conference Mute
Steps to reproduce
The icon when setting the shortcut key and switching order is incorrectly replaced with a character

✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Thanks for your message. This is a Duplicate of another issue: /dup #18055

@niels9001 i see something strange here: the two up & down icons.
The first is coded with Icon="Up" and the second one is <FontIcon Glyph="" />. The result (icon versus characters) is the opposite of what one would expect based on my recent "conclusion".


dont double-add CRYPTOPP_COMPILE_DEFINITIONS

Otherwise, if you run
cmake -D DISABLE_ASM=ON . && make VERBOSE=1
you will get a compiler invocation like
/usr/bin/c++  -DCRYPTOPP_DISABLE_ASM  -O2 -g -DNDEBUG -fPIC   CRYPTOPP_DISABLE_ASM -o CMakeFiles/cryptopp-object.dir/cryptlib.cpp.o -c /path/cryptopp/cryptlib.cpp
with "c++: error: CRYPTOPP_DISABLE_ASM" file not found (it is twice in the command line options, once with -D and once without it).
This should fix it.

Thanks @lawidog.
Would it be better to fix the cause of CRYPTOPP_DISABLE_ASM (instead of -DCRYPTOPP_DISABLE_ASM)?

I am not sure I understand your question. I believe that the list CRYPTOPP_COMPILE_DEFINITIONS is correctly filled (just a list of options without -D prefix). That means it can be added used with add_compile_definitions(). But it must not be added using add_compile_options(), as that would require to add the prefix -D to each option beforehand.

This should be fixed in the latest master branch - please check.


Musixmatch no longer returning hits

Steps to reproduce

Remove all sources except for Musixmatch
Search for any title that does find results from Musixmatch on other apps
No hits

Expected behavior
Lyrics should be returned but are not, even though they ARE found at Musixmatch by Foobar 1.6.16 using LSP-3 and MultiSource, and by MusicBee using LyricsReloaded.
The Authentication Token in use is the same one that does produce results with the alternate player.
Versions

foobar2000 version: v2.0 64-bit
OpenLyrics version: 1.6

Additional information

I can add this additional information:

The search failure from Musixmatch happens only with an automatic, not a manual search, and only with tracks that contain no album title metadata (i.e., 99% of all radio streams).
The failure on automatic in the above environment seems to affect only Musixmatch; tracks with no album name return auto results fine from Genius, AZLyrics, etc.

Can you please:

Enable debug logging for openlyrics (Preferences -> OpenLyrics-> Display -> 'Debug logging enabled')
Open the console (View -> Console), clear it (button in the bottom-left)
Reproduce the issue
Post the contents of the console window here

Here are the console contents for the automatic search.  The file used has only the Artist, Track Title, and Date field embedded.  The only search source selected was Musixmatch.  I have also attached an image file showing the results for the same file using a Manual search, clearly showing that Musixmatch does indeed have the lyrics.
Opening track for playback: "E:\New Mx\harry-nilsson-coconut.mp3" Resampler (SRC): 44100 Hz sample rate is excluded INFO-OpenLyrics: Failed to read search-avoidance info: Unsupported format or corrupted file INFO-OpenLyrics: Searching for lyrics for artist='Harry Nilsson', album='', title='Coconut'... INFO-OpenLyrics: Searching for lyrics in tag: 'LYRICS' INFO-OpenLyrics: Searching for lyrics in tag: 'SYNCEDLYRICS' INFO-OpenLyrics: Searching for lyrics in tag: 'UNSYNCED LYRICS' INFO-OpenLyrics: Searching for lyrics in tag: 'UNSYNCEDLYRICS' INFO-OpenLyrics: Failed to retrieve lyrics from source: Metadata tags INFO-OpenLyrics: Querying for track ID from https://apic-desktop.musixmatch.com/ws/1.1/track.search?user_language=en&app_id=web-desktop-app-v1.0&subtitle_format=lrc&q_artist=Harry%20Nilsson&q_album=&q_track=Coconut&usertoken= INFO-OpenLyrics: Rejected Musixmatch search result Harry Nilsson//Coconut due to tag mismatch: Harry Nilsson/Nilsson Schmilsson/Coconut INFO-OpenLyrics: Rejected Musixmatch search result Harry Nilsson//Coconut due to tag mismatch: Harry Nilsson/Nilsson Schmilsson/Coconut (Remastered 2004) INFO-OpenLyrics: Rejected Musixmatch search result Harry Nilsson//Coconut due to tag mismatch: Harry Nilsson/Nilsson Schmilsson/Coconut - Demo INFO-OpenLyrics: Rejected Musixmatch search result Harry Nilsson//Coconut due to tag mismatch: Harry Nilsson/Let Me Get This Straight (Live)/Coconut - Live 1971 INFO-OpenLyrics: Rejected Musixmatch search result Harry Nilsson//Coconut due to tag mismatch: Harry Nilsson/Nilsson Schmilsson/Coconut (Remastered) INFO-OpenLyrics: Failed to retrieve lyrics from source: Musixmatch INFO-OpenLyrics: Save file name format '[%artist% - ][%title%]' with directory class 'ConfigDirectory' evaluated to 'file://C:\foobar2000-x64_v2\profile\lyrics\Harry Nilsson - Coconut' INFO-OpenLyrics: Querying for lyrics in file://C:\foobar2000-x64_v2\profile\lyrics\Harry Nilsson - Coconut.lrc... INFO-OpenLyrics: Querying for lyrics in file://C:\foobar2000-x64_v2\profile\lyrics\Harry Nilsson - Coconut.txt... INFO-OpenLyrics: Found 0 lyrics in local files: file://C:\foobar2000-x64_v2\profile\lyrics\Harry Nilsson - Coconut INFO-OpenLyrics: Failed to retrieve lyrics from source: Local files INFO-OpenLyrics: Parsing lyrics text... INFO-OpenLyrics: Parsing LRC lyric text... INFO-OpenLyrics: Failed to read search-avoidance info: Unsupported format or corrupted file INFO-OpenLyrics: Lyric loading complete INFO-OpenLyrics: Received empty lyric update, ignoring... ![manual](https://github.com/jacquesh/foo_openlyrics/assets/130251824/43495997-2a14-46ca-9e53-3991048a70e9)

Wanted to add that as Musixmatch never produces results from a radio stream due to this glitch, and the other sources do, the one thing streams have in common is that there is never an "Album Title" field sent, only track title and artist.  It could be that in the case of this one site it is reacting to an absent field it should not be considering.

Ah, looks like it's rejecting results that "don't match" because the tags don't contain an album name. I thought I'd specifically handled that but maybe not (or maybe only from the retrieved lyrics side).
I'll look into it, thanks

Auto- and manual-search do the same search underneath. The difference is that manual search gives you back all the results (so you can choose what to do with them) while auto-search needs to (by definition) automatically pick just one, and in an effort to do so sensibly, will filter out results whose metadata (artist/album/title) is sufficiently different from what fb2k has locally.

Ah, looks like it's rejecting results that "don't match" because the tags don't contain an album name. I thought I'd specifically handled that but maybe not (or maybe only from the retrieved lyrics side).
I'll look into it, thanks

Thanks jacquesh for looking into this, much appreciated.  As I mentioned, the way Genius and AZLyrics are handling the no-album for radio streams works fine.


Search Head Cluster Logic missing for autoscaling

Even though the ELB has an autoscaling configuration, mapped to an image/AMI. The Search-Head cluster configuration is still needed, when a  node is added/removed.
Otherwise the replication bundle between search-heads will not occur, causing out of sync configurations as user sessions connect through the ELB.
Factor 2 needed.
With a Minimum of 3 Instances to keep HA.

Did not think anybody was using it. Feel free to create a PR from your fork if you have a fix. Anyway it's opensource licence now.

Issue won't be solved unless someone is willing to patch it for me. Anyway it's open license now


API Rescue Master Branch PR: Only expose public extension methods

Rescues https://github.com/silverstripe/silverstripe-framework/pull/7752 and https://github.com/silverstripe/silverstripe-framework/pull/7879
Also strongly types Extensible and CustomMethods as per https://github.com/silverstripeltd/product-issues/issues/583 - easier to do it here while I'm already changing things than to do it as a follow-up PR, though I can happily remove that commit if the reviewer doesn't want them in the same PR.
Depends on

https://github.com/silverstripe/silverstripe-cms/pull/2764

Needs this to be merged before CI will be green.

Parent issues

https://github.com/silverstripe/silverstripe-framework/issues/10350
https://github.com/silverstripeltd/product-issues/issues/583

PR is currently combination of 2x different things

rescuing a master branch commit
adding strong typing

These are two different things and should be done in separate PRs
Cheers

Strong-typing commit has been removed.
I probably won't be creating a new PR for it though since I'd have to wait for this to be merged and create a new PR from that point to avoid merge conflicts - we'll just have to live without.


axiswise normalization does not work if type is not specified

Hi,
If I do:
import pandas as pd
import holoviews as hv
hv.extension('bokeh')
df_1 = pd.DataFrame({'x':[1,2,3], 'y':[1, 2, 3]})
df_2 = pd.DataFrame({'x':[1,2,3], 'y':[10, 20, 30]})
(
hv.Curve(df_1, kdims=['x'], vdims=['y']) +
hv.Curve(df_2, kdims=['x'], vdims=[('y', 'not y')])
).options(axiswise=True)

It does not apply the axiswise property, although the FAQ https://holoviews.org/FAQ.html says it should:  your_layout.options(axiswise=True).
If I specify .options('Curve',  axiswise=True) it works as intended.

There are 2 things that I don't like in this behavior:

I need to specify 'Curve' although I feel like the axiswise property belongs to the Layout and not the Curve
I have specified an alias for y in the second plot. This has the effect, that y axis are not linked. However they still get normalized together. This behavior does not make much sense, imho, if renaming avoids linking the axis, this should also apply to normalization.

What do you think? Thanks!

I just spent a day fighting this so thank you for documenting the solution. I agree that the docs don't accurately explain how to apply axiswise normalization.

Agreed, the docs on normalization seem to have gotten lost almost entirely when we reorganized the user guide.

Oh, the FAQ is also definitely wrong, I don't think that ever worked.

D'oh! You and I both reviewed that and didn't catch it.  That should work, and makes much more sense than what one actually has to do; I really think we should just make it work!

Just merged which made shared_axes on layout plots consistently supported which does what you want.


how do I add the information and how do I activate the bot?

Good afternoon! I'm having trouble using the bot, I have no experience in handling this advanced programming.
I don't know where in the code I add the information like: tennis link, tennis size, my login and my credit card. I also don't know how to run / activate the bot ... If you can explain to me how the bot works I appreciate it!

People have been updating the README to help you out (another PR is open for this as well).


WIP: Fix mpl

Probably won't fix CIs but could give us more information.

Okay I'm a bit sad I've wasted so much time on this -- they just released mpl 3.0.1 with:
 - Fix failure to import bug when on Python 3.6.7 and 3.7.1

So I'll close this and we'll just have to be a bit patient


Allow configuring strokeDashArray of now marker

Checklist

[x] I am running the latest version of the card
[x] I checked if there isn't another feature request opened with the same request
[x] I checked that the feature is not already available in the dev branch

Currently the now marker creates an annotation with a hard coded strokeDashArray of 3. I'd like this to be exposed as an option to allow reconfiguring this.

no stale


Updated Estonian translations

There might be an error in the English translation on line nr 88, I believe it should be move % at speed % instead of move %% at speed.

There might be an error in the English translation on line nr 88, I believe it should be move % at speed % instead of move %% at speed.

No, because the first % corresponds to the motor name, and the second correspond to its direction.
Like this:


Option got nil in nested schema

Sounds similar to #200
Here is my spec:
RSpec.describe Dry::Validation do
  describe "simple schema" do
    let(:schema) do
      Dry::Validation.Schema do
        configure do
          config.messages_file = "#{PROJECT_ROOT}/config/dry-errors.yml"
          option :my_id

          def eql_my_id?(value)
            my_id == value
          end
        end

        required("id").filled(:eql_my_id?)
      end
    end
    let(:params) do
      { "id" => 1 }
    end
    subject(:result) { schema.with(my_id: 1).call(params) }

    it { expect(result.success?).to be(true) }
    it { expect(result.output).to eq("id" => 1) }
    it { expect(result.messages).to eq({}) }
  end

  describe "nested schema" do
    let(:schema) do
      Dry::Validation.Schema do
        configure do
          config.messages_file = "#{PROJECT_ROOT}/config/dry-errors.yml"
          option :my_id

          def eql_my_id?(value)
            puts "my_id = #{my_id.inspect}"
            my_id == value
          end
        end

        required("data").schema do
          required("id").filled(:eql_my_id?)
        end
      end
    end
    let(:params) do
      { "data" => { "id" => 1 } }
    end
    subject(:result) { schema.with(my_id: 1).call(params) }

    it { expect(result.success?).to be(true) }
    it { expect(result.output).to eq("data" => { "id" => 1 }) }
    it { expect(result.messages).to eq({}) }
  end
end

And result:
Dry::Validation
  nested schema
my_id = nil
my_id = nil
    should eq {} (FAILED - 1)
my_id = nil
my_id = nil
    should equal true (FAILED - 2)
my_id = nil
my_id = nil
    should eq {"data"=>{"id"=>1}}
  simple schema
    should eq {"id"=>1}
    should equal true
    should eq {}

Failures:

  1) Dry::Validation nested schema should eq {}
     Failure/Error: it { expect(result.messages).to eq({}) }

       expected: {}
            got: {"data"=>{"id"=>["Id doesn't match"]}}

       (compared using ==)

       Diff:
       @@ -1 +1,2 @@
       +"data" => {"id"=>["Id doesn't match"]},

     # ./spec/api/use_cases/example_spec.rb:56:in `block (3 levels) in <top (required)>'

  2) Dry::Validation nested schema should equal true
     Failure/Error: it { expect(result.success?).to be(true) }

       expected true
            got false
     # ./spec/api/use_cases/example_spec.rb:54:in `block (3 levels) in <top (required)>'

This is because we don't pass options to nested schemas I believe. I'll look into that.


Changed SELinux/semanage error to fatal

If the install errors out on semanage not found, an error is
thrown as a 'file not found' for error. Updating to 'fatal' resolves
this as the script then exits as intended and throws an 'error'.
Actual output (before):
sh: line 347: error: command not found
Output (after):
[ERROR] SELinux is enabled but semanage is not found

Thanks @ibuildthecloud :)
(I wasn't sure what to do with that particular CI failure 😨 )

how to solve

@13567436138 You would need to have policycoreutils-python or similar installed on your machine (CentOS/RedHat)
try yum install policycoreutils-python
:)


MessageStream error in window

I run in Anaconda environment in window, and I got this Traceback.
How can i fix it??
Traceback (most recent call last):
  File "test.py", line 63, in <module>
    for step, data in tqdm(enumerate(data_loader)):
  File "C:\Anaconda3\envs\one\lib\site-packages\tqdm\_tqdm.py", line 1017, in __iter__
    for obj in iterable:
  File "C:\Anaconda3\envs\one\lib\site-packages\torch\utils\data\dataloader.py", line 336, in __next__
    return self._process_next_batch(batch)
  File "C:\Anaconda3\envs\one\lib\site-packages\torch\utils\data\dataloader.py", line 357, in _process_next_batch
    raise batch.exc_type(batch.exc_msg)
OSError: Traceback (most recent call last):
  File "C:\Anaconda3\envs\one\lib\site-packages\torch\utils\data\dataloader.py", line 106, in _worker_loop
    samples = collate_fn([dataset[i] for i in batch_indices])
  File "C:\Anaconda3\envs\one\lib\site-packages\torch\utils\data\dataloader.py", line 106, in <listcomp>
    samples = collate_fn([dataset[i] for i in batch_indices])
  File "C:\Users\전호범\Desktop\notebook\One_Shot_Face_Reenactment\loader\dataset_loader_demo.py", line 88, in __getitem__
    img_src = self.warp(img_src, pt_src, np.vstack([pt_dst[:33], pt_src[33:]]))
  File "C:\Users\전호범\Desktop\notebook\One_Shot_Face_Reenactment\loader\dataset_basic.py", line 52, in warp
    return warper.warping(img, srcPt.reshape(-1, 2), dstPt.reshape(-1, 2), (self.imgSize, self.imgSize))
  File "C:\Users\전호범\Desktop\notebook\One_Shot_Face_Reenactment\utils\warper.py", line 17, in warping
    res = warp_image(img, src_bound, dst_bound, size)
  File "C:\Users\전호범\Desktop\notebook\One_Shot_Face_Reenactment\utils\warper.py", line 106, in warp_image
    delaunay = spatial.Delaunay(dest_points)
  File "qhull.pyx", line 1813, in scipy.spatial.qhull.Delaunay.__init__
  File "qhull.pyx", line 266, in scipy.spatial.qhull._Qhull.__init__
  File "messagestream.pyx", line 36, in scipy._lib.messagestream.MessageStream.__init__
OSError: Failed to open file b'C:\\Users\\\xec\xa0\x84\xed\x98\xb8\xeb\xb2\x94\\AppData\\Local\\Temp\\scipy-sme_thdh'

Maybe you can try to reinstall scipy. And it looks like there is something wrong with your path.

I tryed reinstall scipy, but it seems to be a problem on my path.
I also tryed with my ubuntu laptop(but using cpu) and it works well, Thanks a lot.


v1.15 Backports 2024-05-24

[x] #30809 (@viktor-kurchenko)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 30809

/test-backport-1.15