Is the memory not released?

Thank you for releasing this excellent plug-in, but  when i use this, I found that the memory of the application increased exponentially when  used avifimage.  Any idea?
I using encode avif convert a list of webp image to avif saved to local,
Then start the app to load webp and avif respectively, and find that avif occupies too much memory.

Even if only one image, the memory using have a big gap

For the  image list problem  maybe u should dispose the codec when AvifImage disposed ?

I think having the sample code resulting in the memory rise would be a good start to investigate the issue.

I found in some cases the decoder might not get disposed even if the image is evicted from the cache. c9acfc7340b03296c2cb756c127d63d2b6857a44 addresses this issue. The issue would only happen if your image cache is full (1000 files, or 100MB) or if you manually evict your cache. So the fix might not solve your problem.
I tried a list of 50 animated avif files and the memory usage was around 530MB. With just 1 file it was around 180MB. So if you can show me a way to replicate your problem, I can investigate further.

Thanks, I uploaded the test pic and sent you  as an email.

Seems after you call dispose there were some errors on rust side :
thread '<unnamed>' panicked at 'called Result::unwrap()on anErr value: RecvError', src/api.rs:63:53

Thanks, I was able to reproduce the issue. It seems that high memory usage is only on android. I found that android binaries were built with an older version of libavif so I updated them with same version as other platforms. Can you test 1.2.1-dev release to see if your memory usage gets lower?

Thanks but seems still  takes up a lot of memory

I think this problem may  not related with the platform. I run on the MacBook to check that the memory usage is consistent with Android side .

Interesting. With 1.2.0 I get around 1.2GB memory usage with the files you sent.

With 1.2.1-dev I get around 0.6MB

Just to confirm, your are using version 1.2.1-dev and not pulling directly from git main branch right?

I tried it all, and the result was still the same.  very confused.

Are you using a simulator? I ran on  real machine, pixel 6 pro with android14 and  oneplus 7t pro  with android13 the result is same

Seems after you call dispose there were some errors on rust side : thread '<unnamed>' panicked at 'called Result::unwrap()on anErr value: RecvError', src/api.rs:63:53

Could it be that the rust code dispose failed ?

I think you are receiving that error because with c9acfc7340b03296c2cb756c127d63d2b6857a44 I am disposing decoder while it is still in use. I will try to come up with a better solution.
I tried version 1.2.1-dev both on simulator and a real device. I can see a reduction in memory usage in both of them. I will try a couple of different devices over the weekend.

Can you try 1.3.0-dev? It uses dav1d instead of libaom as the decoder.

Thank you very much. I didn't bring my computer on vacation this week. I'll try it next week.

1.3.0-dev is a significant improvement over stable 1.2.0, I'm saying that because in stable the app could not handle 30 avif network images of the combined size of about 6MB, and crashed the app after loading all images.
1.3.0-dev

not sure about RSS Memory & why it's about 1.4 Gb.

Seems the memory still continue to grow when scroll avif image list or switch to another,  When the view is dispose, the memory is not released.

why is the decoder still attached even after finishing its job, that is to decode avif format?
it should only call native modules once there is a need for decoding from a string or from a network etc and detach itself after it's a job, am I missing something, how can we implement this, is there some brief doc explaining how it's implemented, so we can plan the changes?

Remove this code the memory would be normal, Otherwise, the memory will increase infinitely.

 Remove this code the memory would be normal, Otherwise, the memory will increase infinitely.

I don't think memory will increase infinitely. Because the decoder will be disposed once it is released from the image cache. You can also clear the cache manually by importing flutter/painting.dart library and calling imageCache.clear();

why is the decoder still attached even after finishing its job, that is to decode avif format?
it should only call native modules once there is a need for decoding from a string or from a network etc and detach itself after it's a job, am I missing something, how can we implement this, is there some brief doc explaining how it's implemented, so we can plan the changes?

Decoder keeps attached because animated images are decoded frame by frame. But for single frame images, you are right, we can dispose the decoder after getting the first frame.
PR you sent might cause problems with animated images. I am trying a possible solution at single_frame_codec branch.

Indeed, it is better to process single-frame images separately.

I have published v1.3.0 with the single frame codec. Memory usage of the images you sent reduced from 1.2GB with v1.2.0 to around 250MB with v1.3.0. So I am closing the issue as completed. Feel free to reopen the issue if you still have memory issues.


Dark theme

Would be good to have for accessibility and style purposes.

I should've asked when you opened the issue but, do you have any suggestions for the colors we should use? or should they just be inverted?

addressed by 75904e3b7bf843a795f30ed44cfe5bfca96b6c82


Simplify the interface of the PartFileWriter

The Path is not being used, so no sense in including it in the interface
Reporter: Fokko Driesprong / @Fokko
Assignee: Fokko Driesprong / @Fokko
Note: This issue was originally created as PARQUET-1564. Please see the migration documentation for further details.

Fokko Driesprong / @Fokko:
Wrong project


Set dnsConfig and dnsPolicy

Hello!
We have a problems with a heavy dns qps load from our logging layer. Is it possibly to set custom dnsConfig and dnsPolicy for logging-operator controlled fluent-bit daemonset and fluentd statefulset? Or configure dns options (like a caching) for fluent-bit app?

Thank you!

I found propertie nodeAgentFluentbit in Loggings CRD spec, put dnsConfig and dnsPolicy in corresponding spec, but they don't have positive effect (now Operator try to reconsile Logging resource, throw error and crash)

@RaSerge Thanks for the report! I'll look into this


kne instead of kne_cli

Hi @marcushines @alexmasi
This proposal is to retire usage of kne_cli as a binary name of a kne CLI in favor of just kne.
From my experience, and what seems to be in line with opinionated cli guidelines, a good CLI name must be short, consice and easy to type -  https://clig.dev/#naming.
kne in that regard is better than kne_cli as it is 4 chars shorter, doesn't force you to use SHIFT and is as expressive in what it does.
I know this might be a bit too intrusive, but I am afraid if we don't do this early on, it might be harder to change it in the future.
I will leave a few inline comments over the certain code lines which I feel deserve a bit of explanatoin

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 53.896%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1916

Relevant Lines:
3555

💛  - Coveralls


Remove-SPOUserInfo vs Remove-SPOUser

Not clear when one or the other should be used.
Also, Remove-SPOUserInfo has an additional parameter - RedactName, that does not show up here and has no explanation.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f3aaa97d-31e1-e3bf-ee54-389491b2f103
Version Independent ID: c0d774e4-de11-bcaf-612d-45154791f8b3
Content: Remove-SPOUserInfo (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOUserInfo.md
Service: sharepoint-powershell
GitHub Login: @trent-green
Microsoft Alias: trgreen

@officedocsbot assign @yogkumgit

@BLalanda
I think the use of Remove-SPOUser is clear, removes a SharePoint Online User from a SC or group.
I tried Remove-SPOUserInfo and I could not identify what was being removed, I could guess "user information", but after running it I could also run Export-SPOUserInfo and get the same information.
@trent-green Can you help us here understading the use cases of -SPOUserInfo cmdlets? Thank you

@tseward Trevor, do you maybe have the missing information here? Thanks

@get-itips this is being looked into.

@get-itips this is being looked into.

@get-itips this is being looked into.

Thanks

@get-itips this is being looked into.

Thanks

@tseward


Upgrade thrift package dependcy to reduce security risk

Upgrade package dependency for thrift as the current version in use (0.12.0) has a high severity security vulnerabilities (out of bound read, loop with unreachable exit condition - possible infinite loop)
Latest version is 0.13.0: http://thrift.apache.org/

Incorrect project.  Closing


Fill in README

Add an explanation of the name, and a paragraph explaining the project.

Check out the Github markdown for writing the README:
https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet


Is this repo still active?

While looking for java buildpack, this also shows up in the results. There's been no activity since 2013.
Should this repo be retired?

Hi, no it's not active. I would guess this is the original fork from Heroku before we decided on a complete redesign. I have no idea how to get a repo retired though. I will bring it up in our team meeting and comment back here.

Ah, that makes sense. @MarkKropf helped the buildpacks team through some repo migration stuff, perhaps he can give advice as well.

Yes, this should probably be moved to the CF attic. Validating that assumption now.

repo archived in the CF attic  thanks @jchesterpivotal @cgfrost


Release version 0.7.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] 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)
[ ] Verify if the release channel is correctly set to main, geofileops_rc or geofileops_dev (depending on stable, rc or dev version), especially after rerender changed files!
[ ] If rerender changed files, verify if .github/PULL_REQUEST_TEMPLATE.md is still present. If not, copy it again from the backup directory.

@conda-forge-admin, please rerender


After adding a custom resource, lambda layer is breaking push

Describe the bug
I've added a custom resource and for some reason (should have committed changes to see the diff) but my lambda layer is now breaking my amplify push deployment.
UPDATE_FAILED      functionresourcesHubHelpers                    AWS::CloudFormation::Stack Thu Feb 18 2021 10:26:06 GMT+0000 (Greenwich Mean Time) Parameters: [s3Key, deploymentBucketName] must have values

Looks like it's missing some parameters out of the blue. This has been deployed already and I've not touched anything to do with this lambda layer. Strange.
Amplify CLI Version
4.41.2
To Reproduce
To be confirmed.
Expected behavior
An unrelated stack template to not break when adding a custom resource.
Additional context
I'm going to remove this layer and re-add it to see what has changed.

Appears to have been related to https://github.com/aws-amplify/amplify-cli/issues/6666

Looks like the amplify env checkout develop command is removing these variables used by my lambda layer...
			"deploymentBucketName": "amplify-resourceshub-dev-xxxx-deployment",
					"s3Key": "amplify-builds/resourcesHubHelpers-build.zip"

Why should running  amplify env checkout develop (in order for amplify cli to recognize custom cloudformation resources), break my deployments?

@kylekirkby
A few questions here

Do you have layer-runtimes.json file in your project?
Do these values appear in your team-provider-info.json` file?

@SwaySway ,

I have a layer-runtimes.json file in my lambda layer folder
They do appear in team-provider-info.json.

Since upgrading to the latest version of the CLI  - 4.44.0 - this issue seems to have stopped occurring.


[Refactor] PluginMgr support serialized and deserialized with JSON FORMAT

Problem Summary:
Fixes # (issue)
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[x] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 0 / 19 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
0
1
00.00%
[1415]

:large_blue_circle:
com/starrocks/plugin/PluginMgr.java
0
18
00.00%
[363, 365, 366, 367, 368, 369, 370, 372, 373, 376, 378, 379, 380, 381, 383, 384, 386, 388]


Command task to resort macros into classes

For macros with a Valid SpecID in GSELibrary[0] add a command to put them back into their correct classes.

/gs movelostmacros


Uncaught TypeError: Cannot read properties of null (reading 'value')

strawberry
        banana
        apple

<script>
    function change(){
       let found = null;
        let kfruit = document.getElementsByName("fruit");
        let img = document.getElementById("fruitimg");

        for (let i=0; i<kfruit.length;i++){
            if(kfruit[i].chekced ==true)
           found = kfruit[i];
       }
        img.src = found.value;
    }
</script>

I've checked many of the same issues and they usually say to check the mistakenly put space for the id
but I can't figure out what's wrong.. could anyone please help..?

How is this related to CodeMirror?

did the CodeMirror tpyeerror solved ? @marijnh

if so, how? can please provide the solution.

I had the error and removed blackbox extension and it did work

I had the error and removed blackbox extension and it did work
Tysm, I was using Draw.io when this problem happened

Removing Blackbox extension also works for me too. thanks @Marium-dotcom


addArrangedSubview requires 10.11

This prevents cedar from running on 10.9

Thanks for the find. I'll take a look and find an equivalent implementation that will support more than 10.11+.


3688 error handling

Checklist:
[x]I have performed a self-review of my own code,
[x]I have commented my code, particularly in hard-to-understand areas,
[x]I have made corresponding changes to the documentation,
[x]I have added tests that prove my fix is effective or that my feature works,
[x]New and existing unit tests pass locally with my changes ("bundle exec rake"),
Resolves #3688
Description
Re-worked error message related to Storage Location, and refactored error handling into a private method with a custom error message to clearly convey to the user what the error is.  Re-labeled the 'From Storage Location' field to 'Storage location', and re-named the error associated with the field.
List any dependencies that are required for this change. (gems, js libraries, etc.)
Include anything else we should know about. -->
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Tested in the audit_request_spec.rb This test ensures that the correct template is rendered if no Storage location is selected, and that the flash message is rendering the custom error message.
Provide instructions so we can reproduce.
Do we need to do anything else to verify your changes?
If so, provide instructions (including any relevant configuration) so that we can reproduce? -->
To reproduce the rendered error messages. Log in to the application as a Bank User - Organization Admin, begin a new audit without selecting a storage location, save the audit, and the custom error messages will be displayed.
Screenshots

Nice, thanks!


Support embedded objects

An entity should be able to hold nested objects. There are different strategies for the implementation of this. One is, to embed all fields of the nested object in the surrounding object table.

Hola, de ante mano agradecer el gran trabajo que estás haciendo, en la librería room de Android siempre tuve un descontento y es que no se pudiera colocar usar variables solo para cargar dato de la consulta, ya que se debía colocar como un campo para que en la consulta lo tomará, esto es para el caso un join con otra tabla, no en todos los casos es necesario todo el objeto de otra clase, sería bueno que se agregara una opción al columnInfo que permita usar la variable para solo consulta.

Hi @willgsoft! I'm happy to see your interest in the library and would like to help. Unluckily, my Spanish skills are mediocre and Google Translate didn't help this time.
I think it would be beneficial for me and others to keep the conversation in English.

#328

I've just run into an issue which I think relates to this.  I have a "Day" entity, each of which has several "Temp" fields.  The "Temp" object is a custom object which has 2 fields of its own - a double and a bool.  I wrote a Type Converter so Floor will manage the Temp objects, but when I call an update method for a Day, the bool field of the Temp is not getting updated in the database.  My theory is that the database does not recognize the change, as the Day still has the same Temp object - it doesn't "see" the change to the Temp object's property.  I could be wrong though, I'm not sure I completely understand how Floor and Sql work.  Any help would be appreciated.


Revert pull_request field change.

The change to the pull_request field in #1646 is causing way more trouble than it is worth. If GitHub sometimes populates this field, then it is useful to know if it is a pull request or not.
Fixes #1651.

For future notice, should this codepath will be changed: #1646 also was breaking the T-compiler agenda generation (specifically commit 3cde23dfb9a6b2e724d0c5e4257aae6cf6276eee) when running the triagebot command cargo run --bin prioritization-agenda.
Just mentioning this because some dependencies are not always apparent with this codebase. A good strategy could be to run all three CLI binaries of the triagebot (compiler,lang,prioritization-agenda) for a quick sanity check.
Anyway, no problem, this patch reverts the breaking change :)


Use PackedSequence for ConvRNN

Zero-padding is technically incompatible with the recurrent layers, since the hidden outputs would still be altered. Using PackedSequence is the correct way to deal with this issue. Thus, I've invalidated the past results and will report the current ones as soon as the model finishes training.

By the way please migrate to SST1 in the common datasets module when you get a chance?

LGTM. Might merge after you push some reasonable results to ensure it works well.

@tuzhucheng Sounds good, I'll do that in a future PR.

Also, I've added results using the default hyperparameters specified in the paper. They're around 2.7 points off.


Verify behavior of GRANT/REVOKE during database creation

https://github.com/influxdb/influxdb/pull/2763#discussion-diff-31739854

closed in favor of https://github.com/influxdb/influxdb.com/issues/37


Eas 1342 security key registration content fix

Replacing instances of "Notify" with "Emergency Alerts" for the security key flow, plus fix of the error message appearing on screen even when there was a success by splitting out errors into conditional error summary components.

Re-ran the PR checks because they got a 500 from the Node software repo. That’s happened a few times recently, strange...


allow for .Net 4.5

Expanding the accepted range of .Net installations to include .Net 4.5

:+1:

I take it this module won't work with 4.6?

@juniorsysadmin To be honest, I don't know about .NET 4.6 compatibility-- the box we're interested in adding this to is on 4.5.


Package as package?

It would be helpful if this project included a little more packaging so that people could do something like
pip install 'gc-finance @ git+https://github.com/wolfsblu/gc-finance'

rather than manually downloading, installing dependencies, and running the scripts.  This would probably involve just creating a setup.py or pyproject.toml, moving the code files into a module directory, and putting the main.py in a scripts/ directory (probably renaming to something like gc-finance).

That's a good idea, I will get on it as soon as I find some spare time. Thank you!

Solved with 37473ee


Added link to npm configuration documentation

Hi @mettacrawler, shouldn't regular npm login work just fine?

I've tried a number of different ways and I've never gotten anything other than basic auth to work.
Have you succeeded with npm login?
If I try npm login --registry=https://my-nexus/repository/npm-proxy with no ~/.npmrc I get:
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Sonatype Nexus Repository Manager"


Error: "cannot create a file when that file already exists"

I have the latest version of youtube-dl (2019.07.16).  Even in previous versions I would frequently get this error when downloading playlists from youtube.  "cannot create a file when that file already exists", though no such files were there. It was a fresh download.  I'm left with a file ending with TEMP in the filename, then the playlist download process is stopped because of that error.   Any way to fix that?  Thanks

At least provide an explanation why the thread is closed and what do next.
What you are doing is not very helpful to new users.
On Thu, Jul 25, 2019 at 4:17 PM Sergey M<EMAIL_ADDRESS>wrote:

Closed #21897 https://github.com/ytdl-org/youtube-dl/issues/21897.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ytdl-org/youtube-dl/issues/21897?email_source=notifications&email_token=AKSVAFTZE63GE62JDICLGQDQBIJ7PA5CNFSM4IG6O23KYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSWUJCYY#event-2510852451,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKSVAFS27YF2Z7RC6PYSJX3QBIJ7PANCNFSM4IG6O23A
.

Bother to read new issue template.


Create Documentation Site

Leverage Docusaurus and move the docs out of a single README and into a proper docs site on Github Pages.

Not going to use Docusaurus, but I did move all the docs into /docs

Reopening this because I want to create a separate docs site and use Algolia to search.
Maybe Docusaurus will work after ripping out all Tailwind stuff in #26?


docs.rs documentation isn't searchable

I was reading the IndexMap docs and wanted to try to find some information on its support for serde. I tried searching like I do for other docs on docs.rs but typing in the box doesn't bring up the results like for other crates, and pressing enter to manually search doesn't produce any results. I checked my browser console and I see an error that https://docs.rs/crates-20210304-1.52.0-nightly-45b3c2851.js returns a 404. This isn't an issue with my browser / internet / configuration, as docs for other crates (e.g. serde) work properly.

I've done some more testing with this and it only seems to be broken on the docs index page. If I go to a page within the docs, searching works.

Thanks for the info. This must be a bug on the docs.rs end, but it's good to know.

fixed in current version


Add support for list service keys

[#87057920]

@shalako this PR is pending on CC and was submitted yesterday and adds the listing of service keys API behavior.

@maximilien story to review has been prioritized

Hi @jeffh , this is Edward and Tom from IBM Beijing team, thanks for your review. We have resubmitted this PR by refining the code according to your comments. Please take a look, thanks

Thanks @xingzhou. Merged. :+1:


Card drag and drop problem while using sorting

Hi,
I am facing issue during drag and drop of card. While dropping card at different location, card other then dragged card is dropped. It is because "this.state.Result" has data in different sequence and after applying sort "laneSortFunction" result is sorted on view only and on "this.state.Result" it remains in unsorted form. So, dropped card is the card which is at that position in "this.state.Result".
What changes I should made to make my code work as expected.
laneSortFunction(card1, card2){
        if (card1.Amount > card2.Amount)
          return -1;
        if (card1.Amount < card2.Amount)
          return 1;
        return 0;
    }

                <Board
                        data={this.state.Result}
                        customCardLayout
                        draggable={this.state.draggable}
                        laneSortFunction={this.laneSortFunction}
                        handleDragEnd={this.handleDragEnd}
                        handleDragStart={this.handleDragStart}
                        laneDraggable={false}>
                         <CustomCard />
                     </Board>;

Desktop

Linux
Chrome

Data represented on the front-end is saved on the backend (well, technically still front-end, since React is JS), so you simply want to grab the output of laneSortFunction and save it to this.state.Result. This should lead to congruency between what you are seeing and the actual state of the app.

@prachi0708 If you pass laneSortFunction as props, you are telling the Lane component that the cards must be sorted in a specific way. So, this applies to newly dragged cards to the lane as well and they will be sorted using this logic after they are dropped.
Either you can reuse the laneSortFunction to calculate state again and subscribe to onDataChange which will publish the lane data in the new order as rendered on the UI.

Hi @rcdexta
I just faced the same issue as @prachi0708
I tested but can't verify this statement:

Either you can reuse the laneSortFunction to calculate state again and subscribe to onDataChange which will publish the lane data in the new order as rendered on the UI.

While cards are correctly sorted on the UI after the laneSortFunction has been applied, I get notified by onDataChange but they remain in the in the initial order in the resulting data.
Is there something I'm missing?
Thanks in advance,


Investigate issue with TimeTagHelper

After 2.0.0 upgrade the TimeTagHelper was presenting strange issues and appeared to be invoked for the head and body tags which led to malformed output.
A workaround was put in to prevent this - see https://github.com/HTBox/allReady/blob/master/AllReadyApp/Web-App/AllReady/TagHelpers/TimeTagHelper.cs#L35
We should investigate the root cause and look to fix this. Copying the tag helper code into a clean project it seemed to work correctly, so this appears to be something specific to the allReady code base.

Tried to have a look at this and it appears to be a problem with Autofac and more precisely:
containerBuilder.RegisterAssemblyTypes(typeof(Startup).GetTypeInfo().Assembly).AsImplementedInterfaces();
To test this create a new Asp.net core 2.0 web app. Create the tag helper and register it. Then add the following code to the end of ConfigureServices in Startup.cs:
        var containerBuilder = new ContainerBuilder();
        containerBuilder.RegisterAssemblyTypes(typeof(Startup).GetTypeInfo().Assembly).AsImplementedInterfaces();
        containerBuilder.Populate(services);

        this.ApplicationContainer = containerBuilder.Build();
        return new AutofacServiceProvider(this.ApplicationContainer);

If the containerBuilder.RegisterAssemblyTypes... row is commented out it will work, otherwise crash.
I haven't been able to figure out why this causes the app to crash yet, but will try to investigate further.


User registration/password setting broken

Version:
latest
Describe the bug
User registration, especially setting a password seems broken, got the same issue using the latest docker development setup on different docker environment test setups. Registration of a new admin user, by the provided docker exec instruction works. However, the login afterwards with the provided registration details fails. According to the users page within the WebUI it seems the user was successfully created. There is one change I had to add to the docker-compose.yml provided by you. I added DB_AUTO_UPGRADE=True to the environment of the natlas-server service, to get the service successfully up.
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/natlas/natlas.git
Add DB_AUTO_UPGRADE=True to docker-compose.yml within 'environment' of natlas-server service
docker-compose up -d
docker exec -e SERVER_NAME=example.com -it $(docker ps | grep natlas-server | cut -d' ' -f1) flask user new --admin
Register a new admin with the token URL provided by step 4
Logout and try logging in with the user just created. Fails.

Hey there. I'm not actively working on this project very much at the moment but to help debug, could you capture the Network tab in dev tools when you try to login? What does the failure look like? Is it just a login error saying username/password invalid? Or a 500 error? Or redirecting to the wrong URL?

POST to /auth/login is answered with
HTTP/1.0 302 FOUND
Content-Type: text/html; charset=utf-8
Content-Length: 229
Location: http://xxxremoved.tld:5000/auth/login
Set-Cookie: remember_token=; Expires=Thu, 01-Jan-1970 00:00:00 GMT; Max-Age=0; Path=/
Vary: Cookie
Set-Cookie: session=eyJfZmxhc2hlcyI6W3siIHQiOlsiZGFuZ2VyIiwiSW52YWxpZCBlbWFpbCBvciBwYXNzd29yZCJdfV0sImNzcmZfdG9rZW4iOiI5YTk2MDk1NGFmODFiNWNiNzU1ZjAxMzNmNDBkN2FlZGUxZGIxNDUzIn0.YDp9_g.mS8JKXm7oj3848fhUYMCexc_WdQ; HttpOnly; Path=/
Server: Werkzeug/1.0.1 Python/3.8.8
Date: Sat, 27 Feb 2021 17:14:38 GMT

Invalid email or password

When I got to step 4 above, I ran into some issues as well.
I solved this by using docker desktop and opening the CLI for natlas_server1 ( your naming may be different ).
Once I got the # prompt I did an export SERVERNAME=localhost:5000
followed by:   flask user new --admin
no idea if this will persist yet as I'm brand new to containerization, but I have no issues logging out or logging back in to the application by doing this.


dojo share button

I couldn't edit the PR in #190, so here we are. This closes #190.

Overall, I like the idea, just refactored it slightly. Thanks!


[JS] Topic: Functions

Description 📜
Created a document on JavaScript functions.
Fixes #247

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] JavaScript

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@paramsiddharth sir, please review this

@sushovanb02 Looks really nice, Sushovan! Please preserve the document, we might have to merge Siddhi's PR for this issue, but the information you added in this document will be needed. I'll ask you to do another PR, updating the README that Siddhi created, and add your own data to it and name to the contributors' list.

ok so sir my query is that if this PR doen't get merged will this be counted in contribution? @paramsiddharth sir

ok so sir my query is that if this PR doen't get merged will this be counted in contribution? @paramsiddharth sir

Of course it will be! If this PR of yours doesn't get merged and your contribution looks good, I'll ask you to make another PR updating the existing contribution.

@sushovanb02 Please pull the updates to the Javascript branches, add more information to the documentation-based contribution, and create a new PR with the title prefixed with [JS] Other:.

OK @paramsiddharth sir noted but add more information means that I shall write more about functions topic?

OK @paramsiddharth sir noted but add more information means that I shall write more about functions topic?

Yes! It means you can add more content, including that which was in your PR but not in the one that was merged.


Update registering-calling-bot.md

Call Controller Flighting Proxy do not support special characters on Azure Bot Display Name: https://portal.microsofticm.com/imp/v3/incidents/incident/521936057/summary

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/calls-and-meetings/registering-calling-bot.md
88
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

@diegoriera, please let us knwo if you have any queries.

Hi @diegoriera, a gentle reminder.


Use shorter working directory path on Windows runners

Description
This is not so much a bug per se, but a suggested improvement to work around Windows long path limitations.
Despite app-specific workarounds like git longpaths, and despite Windows kind of supporting long paths for a while (and this being enabled in the runner image), there are still some apps that'll break in various ways with long (>260 character) paths. Thus, every letter counts, especially since the repository name is also added to the path, twice. My suggestion is to make the working directory's path under Windows as short as possible.
Now, today long paths shouldn't be an issue for any app out of the box, but decades of the path limitation being in place caused the ecosystem to also rely on it.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[X] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
20221002.2
Is it regression?
No
Expected behavior
The working directory has a path as short as possible, like D:\a.
Actual behavior
The working directory's path includes the repository's name, twice, making it potentially really long.
This is a real pain if you have a repository name like https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions. Here, the working directory will be D:\a\Open-Source-Orchard-Core-Extensions\Open-Source-Orchard-Core-Extensions (or under the C drive on larger runners). This leaves us with 183 characters to work with, to stay on the safe side of the 260-character limit. After our prior tests, it seems that pretty much the only option is changing the repo name (what we'd like to avoid).
Repro steps
This is not specific to one build or app. Two examples that I've bumped into:

Git checkout failing. Can be worked around with git longpaths.
SQLite operations failing from under .NET with "SQLite Error 14: 'unable to open database file'".

This issue is not related to Windows runners. You should open an issue at the repo - https://github.com/actions/checkout


decimalv2 add config to allow invalid decimalv2 literal

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Lack of back button on product page (test&next environment)

Current behavior
There is no back button on product page on the latest version.
Compare demo environment with next
https://demo.storefrontcloud.io/p/WS09/tiffany-fitness-tee/WS09
→
https://next.storefrontcloud.io/women/tops-women/tees-women/tees-25/tiffany-fitness-tee-1513.html?childSku=WS09
Back button is replaced withhamburger menu.

Expected behavior
There should be back button.
Steps to reproduce the issue

Open any product page on https://next.storefrontcloud.io/
Look at the header
Try to Find back button (arrow)

Repository

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[ ] This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser:
OS:
Node:
Code Version:

Additional information

@patzick i belive we should maybe include this one in 2.9 - it’s probably related to url dispatcher changes (?)

I'm not sure if i remember it correctly, but this might be done intentionally. Because for example when you're going to product page and want to change category you wouldn't have this possibility. You can always go back through breadcrumbs, menu also is kept in current category so you can also easily change subcategories. In my opinion menu should be accessible for user.
What do you think @alinadivante, @pkarw , @filrak ?

You’re right I remember there was such a change introduced during one of the jackafhona
To keep the proper UX we should display this arrow only in the situation when user entered the product page from category (with filters set etc) and would like to get back to check another product for the filtered list. For sure it shouldn’t be there when just clicking between individual products
@StasiekDivante to be asked and to propose solution - @alinadivante yoire an owner of this change please make sure the UX is at the proper level

@patzick  I didn't know about this, but yes, I agree with you @patzick and @pkarw it makes sense!

@pkarw @alinadivante we should always keep the arrow, as we want to build experiences as close as possible to the native applications. I would keep both, the back arrow and the hamburger menu upon entering from any path

Probably it is the best solution. Could you show us design with two buttons, @StasiekDivante ?

@StasiekDivante Can you take care of it?
Because now we have again problem with this issue #2732

here you go @alinadivante

@StasiekDivante okay, but please change the order of the buttons :)

I wouldn't to that, this order is the standard

We discussed with @patzick about this idea and for now... I close this ticket : D


id < this->size():Error:Assert failed:in file unicharset.cpp, line 278

Tesseract Open Source OCR Engine v3.05.00dev with Leptonica
row xheight=132.409, but median xheight = 101.7
row xheight=126.5, but median xheight = 101.7
row xheight=126.5, but median xheight = 101.7
row xheight=119, but median xheight = 101.7
row xheight=86.6667, but median xheight = 101.7
row xheight=76.6667, but median xheight = 101.7
row xheight=246, but median xheight = 101.7
id < this->size():Error:Assert failed:in file unicharset.cpp, line 278
zsh: segmentation fault (core dumped)  tesseract de.elab.exp0.png de.elab.exp0.box box.train
boxfile: @https://gist.github.com/CDanU/e14b3b1c0ba3a3502fb86a55bad0a30d
img: https://cloud.githubusercontent.com/assets/15148226/18413673/1edce808-77af-11e6-9ba4-94524dcf2243.png
Maybe the image is too big ? If that is the case it would be nice to get a better message.
tesseract 3.05.00dev
leptonica-1.73
libgif 5.1.2 : libjpeg 8d (libjpeg-turbo 1.4.2) : libpng 1.6.25 : libtiff 4.0.6 : zlib 1.2.8 : libwebp 0.5.1

There are clear instruction for training and how to generate training images. Other approaches are not supported.


Register account through app has no 50 character limit for account name, while the website does.

Repro steps

Register on the app, using a very long account name
Finish the registration

Expected Result
Unable to enter an account name longer than 50.
Actual Result
Will give issues for really long names, for example when verifying the account this is done through a URL parameter.

System Info
Type: Local
Git user: Mathias De Weerdt
Git hash: ff7ec3e
Time: 10:26:15 13.01.2020
Message:

app validation has 100 max length, backend throws error as a result.
Please update the 100 limit in app to 50.

@MathiasDeWeerdt

Changed to 50.


Duality v4.0 Release Schedule

Summary
This is an aggregate issue to reflect what still needs to be done before Duality v4.0 can be released, intended to roughly list points that did not make it into their own issues yet. Some of these points may already be done partially or fully and are listed to verify their current state.
The intent of this is to answer and evolve the question "where are we on this?", and act as an internal roadmap and discussion platform for v4.0.
Analysis

Move the DualityProjectTemplate that we'll bundle in the download .zip to somewhere inside this repo.

Consider adding an automated .zip pack step in some .csproj, like it was done for the now obsolete embedded GamePluginTemplate, so it doesn't need to be zipped manually for release.
Remove the now obsolete "package .zip" build step from NightlyBuilder.

Do some extended testing with the template to make sure everything works and is reasonably polished.

Consider releasing a set of 4.0-beta pre-release packages and a 4.0-beta download .zip that can be used by developers and the community early adopters for testing prior to release.

Update the download link subdomain to always point to the latest release download, see here.
Add a v4 docs folder including any required page updates and a new changelog page, see issue #799 for that.
Consider to also do and bundle any other (breaking) changes that would require a major version step, preferably those that would benefit from the netstandard 2.0 / C# 7.3 upgrade.

We don't have an issue for that yet, but RawList<T> for example could use an API upgrade with a ref-return indexer, and so on.
Nothing specific required here, but it would be a good opportunity. Also, this should probably be in beta for a while, and if we're waiting for release anyway, why not do something useful with the time 😄

Eventually, when all is tested and done, bump all package versions to 4.0 and merge into release.

Might have to update the version updater behavior to deal with previous pre-release beta versions properly when used with ApplyGlobalUpdate=Major as a command line parameter. Right now, it doesn't really support pre-release versions or considers them at all.
Alternatively, just do it manually - it's "all packages or none" anyway.

Feel free to move any of those into their own separate milestone issue, then comment here with an updated list that links to it, or crosses it off.

Consider adding an automated .zip pack step in some .csproj, like it was done for the now obsolete embedded GamePluginTemplate, so it doesn't need to be zipped manually for release.

I think it would be best to make a separate project for this in the solution. Maybe in the future we might add more involved build steps here (dotnet new template etc?) so better to keep it separate.

Do some extended testing with the template to make sure everything works and is reasonably polished.

Yeah 100% agree we should test this thoroughly and involve the community in this as well. They might give us some usability feedback as well.

Consider to also do and bundle any other (breaking) changes that would require a major version step, preferably those that would benefit from the netstandard 2.0 / C# 7.3 upgrade.

Agree, this will help reduce the amount of breaking releases we will do in the future.

Eventually, when all is tested and done, bump all package versions to 4.0 and merge into release.

Easiest is to just do a string replace. All versions are already set to 4.0.0-alpha anyway so this is really easy and fast to do.

Totally agree. There's a bunch of issues I saw around that should be easy to tackle if I'm not mistaken.. I will make a list and see what you think about the eventual priorities

Oh, and don't forget to bring any new v.3 fix in v.4's branch

Move the DualityProjectTemplate that we'll bundle in the download .zip to somewhere inside this repo.
Made a issue for this: https://github.com/AdamsLair/duality/issues/824

Updated the generic download link (https://get.duality2d.net/) that is used on the website and potentially everywhere else from redirecting to the v3 download to this:
https://github.com/AdamsLair/duality/releases/latest/download/Duality.zip
which will always redirect to the latest release on the GitHub repo.

With the template PR #825 merged I believe it is now possible to do a actual alpha/beta release of duality 4.0.0.
If we want we could invite some users to test it out. Also we could upload the dotnet new template pack to nuget so that we can test that as well.

Checked out the latest commits, looks pretty good.
One thing I noticed though is that the current template is a bit confusing: When I extract the .zip, I get a directory build props file and a Source subfolder, leaving me a bit stumped. Can we move the solution file to the root folder? That way, it will provide a clear installation hint to new users:

Got a .zip - let's extract that.
Ah, there's a .sln - let's build that.
Oh, there's binaries now and two "launcher" projects - let's run that.

Without the .sln, that installation flow is less intuitive, because you have to (albeit very briefly) start digging to discover it. This one thing is what I'd address before the alpha release - other than that I'm giving this a go 👍

Also we could upload the dotnet new template pack to nuget so that we can test that as well.

Can we flag that one as alpha as well? If yes, then I'm all for it 👍
Since this is a first time package upload, we'll need to set up AdamsLair organization ownership on NuGet. Feel free to upload one yourself, but please transfer ownership to AdamsLair and AdamsLairBot afterwards. I should get an e-mail automatically to confirm the transfer and will know what's up.
For the future, the CI build should pick up on the project and release the package as well. One way to achieve this would be to add a .nuspec to the Build/NuGetPackageSpecs folder, in which case the NightlyBuilder will pick it up. Alternatively, you can configure the project so that a regular build will create a .nupkg that ends up in Build\NightlyBuild\NuGetPackages, which is where the CI script gathers build artifacts.

Without the .sln, that installation flow is less intuitive, because you have to (albeit very briefly) start digging to discover it. This one thing is what I'd address before the alpha release - other than that I'm totally giving this a go 👍 Really looking forward to this.

Makes sense, I just put it in source so all source files are there but having the sln in the root does make commandline usage easier (can just run dotnet build from the root without any path).

On that note, I don't think we ever tested the NightlyBuilder with pre-release versions. Just to be sure, before merging into release, please do a full local re/build and then locally run the Build\Scripts\Package Binary CI Script.bat script on your machine first, and ensure all packages are built as expected.

We have been testing locally with 4.0.0-alpha for a while now on master and seems to work just fine after I fixed it in https://github.com/AdamsLair/duality/commit/7af3efcd75ceb873bf5243e6656b1911a3f66b11

Can we flag that one as alpha as well? If yes, then I'm all for it 👍

Ofcourse in the end its just another nuget package.

For the future, the CI build should pick up on the project and release the package as well. One way to achieve this would be to add a .nuspec to the Build/NuGetPackageSpecs folder, in which case the NightlyBuilder will pick it up. Alternatively, you can configure the project so that a regular build will create a .nupkg that ends up in Build\NightlyBuild\NuGetPackages, which is where the CI script gathers build artifacts.

I can turn generate package on build on and let it output to Build\NightlyBuild\NuGetPackages.

Oh, and one more thing. Even if that's just for my personal peace of mind, after the v4.0-alpha pre-release, please do a brief test whether the existing v3.x binary release still works with a fresh install + DualStickSpaceShooter via builtin package manager.

Since the 3.x package manager completely ignores prerelease packages anyway its not even possible to install 4.0.0-alpha even if you really wanted to :P.

Makes sense, I just put it in source as all source files are there but having the sln in the root does make commandline usage easier (can just run dotnet build from the root without any path). DONE

Ah, that's super neat as well 👍

I can turn generate package on build on and let it output to Build\NightlyBuild\NuGetPackages. Its the easiest way to do it. DONE

Great, that means the release can now take place with the regular "merge master into release" mechanism 🙂
I think we're all set then. I'm going to keep myself in the background for the alpha release stuff, proceed as you see fit. If you want, we can set a date and time for it where I'm available as a backup just in case something in the CI or so acts up, but I'd leave this to you guys.

With https://github.com/AdamsLair/duality/pull/852 merged the last thing to do is to think of better naming for the settings (while at it we might also do some improvements to the settings) in https://github.com/AdamsLair/duality/issues/855. Since this will potentially break projects we should do it before releasing 4.0.
After this we can do another alpha release, test it and when we find it satisfactory start a beta where other ppl of the community can try out duality.

Sounds good 👍

As a general note, while doing some tests reviewing and merging #878, I found a few previously unnoticed issues, such as the new launcher never loading the starting scene or the lack of any quickly usable testing environment for core devs.
Them going unnoticed despite their impact highlights the lack of a closed dev loop and user feedback right now, so for practical, QA and safety reasons, I honestly think v4.0 should not leave the alpha preview state until that changes. Small steps until then.


jsep is undefined fix

Fixes #5593
Fixes the jsep is undefined error that was occurring when using webpack. Tested using the configuration @lucastheisen provided in #5593
@lilleyse Can you review please?

@ggetz please update CHANGES.md.
@lucastheisen can you confirm that this fixes your issue?

This fixes the Node issues I was having. 👍

Updated CHANGES.md

My test would be using the example that @ggetz mentioned she confirmed this fix with.  However, I would be happy to also test against my real project if there is a relatively straightforward path to doing so...  Do you guys have a CI build that would allow me to point to this fix?  Or do I need to build from from the pull request source branch and build myself?  I'll do the legwork, just curious as to the best approach...

As far as I can tell, the jsep stuff gets embedded into the cesium js files during the build (in the build folder there is no jsep under ThirdParty).  This means i cant just swap out a file to test, so I need to build.  However, my corporate environment is a major pain in the neck...  the npm install fails due to our wonky ssl inspection stuff...  I'll keep trying, and let you know if i am able to get this going.

Okay, after an RTFM moment, I checked out the @ggetz branch, then ran npm install; npm run release.  Next I updated my package.json to use a local dependency, and was able to verify that I no longer get a jsep error.  That said, now i get this one again:
18:41:46.831 Error: Cesium missing ThirdParty/pako_inflate 1 app.js:4383:27
	main http://localhost:8080/app.js:4383:27
	callDep http://localhost:8080/app.js:4245:13
	main http://localhost:8080/app.js:4378:31
	req http://localhost:8080/app.js:4452:13
	<anonymous> http://localhost:8080/app.js:228984:1
	<anonymous> http://localhost:8080/app.js:4069:2
	<anonymous> http://localhost:8080/app.js:4047:29
	__webpack_require__ http://localhost:8080/app.js:20:12
	<anonymous> http://localhost:8080/app.js:3844:1
	__webpack_require__ http://localhost:8080/app.js:20:12
	<anonymous> http://localhost:8080/app.js:234662:18
	__webpack_require__ http://localhost:8080/app.js:20:12
	<anonymous> http://localhost:8080/app.js:66:18
	<anonymous> http://localhost:8080/app.js:1:11

Which appears to have reared its ugly head again in 1.34.  Guess I will wait for a patch for that and try again...
Thanks for getting this one sorted out!

We should avoid directly modifying third party files.  It can be a pain when we go to update that file in the future.  @mramato do you have any suggestions for working around this in a different way?

Thanks for testing this out @lucastheisen, hopefully we can get #5417 sorted soon.
@hpinkos I beleive @lilleyse said we already have modified this file, if that changes anything at all.

See this PR: #5365
I'm fairly certain that stripping out this code is not the right solution here based on the changes @mramato made in that PR

Would a better fix maybe be to define jsep.noConflict for node environments as well?

I think the correct fix is to put all of the old code back and only call jsep.noConflict() at the end if (typeof jsep.noConflict === 'function)

Updated

The recent changes don't work from the Node side because jsep itself is undefined.
$ node -e "var test = require('gltf-pipeline');"
C:\Users\slilley\Desktop\asdf\node_modules\cesium\Source\ThirdParty\jsep.js:683
    if (typeof jsep.noConflict === 'function') {
               ^

ReferenceError: jsep is not defined
    at C:\Users\slilley\Desktop\asdf\node_modules\cesium\Source\ThirdParty\jsep.
js:683:16
    at Object.execCb (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r
.js:1946:33)
    at Object.check (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r.
js:1133:51)
    at Object.enable (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r
.js:1426:22)
    at Object.init (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r.j
s:1038:26)
    at callGetModule (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r
.js:1453:63)
    at Object.completeLoad (C:\Users\slilley\Desktop\asdf\node_modules\requirejs
\bin\r.js:1840:21)
    at Function.req.load (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\b
in\r.js:2613:17)
    at Object.load (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r.j
s:1935:21)
    at Object.load (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r.j
s:1084:29)
    at Object.fetch (C:\Users\slilley\Desktop\asdf\node_modules\requirejs\bin\r.
js:1074:66)

@mramato Is exports.parse = jsep; supposed to be exports.jsep?

@mramato Is exports.parse = jsep; supposed to be exports.jsep?

That branch should never be executed the exports = module.exports = jsep; is what should be getting executed.
@lilleyse what do I need to do to reproduce this in gltf-pipeline?

I am preparing a gltf-pipeline release with npm pack npm install --production <tarball> and calling node -e "var test = require('gltf-pipeline');"

Thanks, I can reproduce without the pack and install parts by just requiring in gltf-pipeline.
I see what the problem is:

jsep gets declared as a local in the IIFE
In the browser, this also becomes a global, and noConflict removes the global.
In Node, the global is never created so jsep is undefined, leading to an except even checking for its existence.

What's even weirder is that in some cases, jsep is defined, even in node, and has the noConflict function.  I think there's some odd side-effects going on here with loading jsep via requirejs in Node and that's the root cause of the issue.  I think the above suggested changes should resolve things on the Node side for now (not sure about webpack).
When we to ES6, we'll have to revisit our strategy for how we wrap/use third party libraries.

Doc is failing, which is why travis is failing, but it doesn't appear to be related to this branch.  @lilleyse can you test this out.  Thanks.

I tested with webpack and it works. I'm not sure why the build is failing on makeZipFile though, the command runs without error locally.

The latest changes work for me.

Thanks @ggetz!


PhantomJS scrape not returning visible page contents

Let me start by saying I don't think this isn't any sort of bug, but more likely just a configuration issue on my end that I haven't been able to solve - and I'm not sure where else to ask the question. If this isn't an appropriate place, please let me know and I will gladly do that instead.
I started using PhantomJS last month with great success, and love how easy it was to get it working for the first application I set up. I then tried writing a simple PHP script to scrape data from my Garmin Connect account, and have been running into issues.
The first problem I had was with the HTTPS connection, but I found the "addOption('--ssl-protocol=any')" to get that working and began getting a valid status returned.  However, the data that actually comes back in the scrape doesn't contain most of what's display on the page.
Here's an example: https://connect.garmin.com/modern/activity/1157027243
The "calories" display, for example (365 C) does not appear anywhere in the content that's returned. I don't know enough about how that garmin page is set up to know where to look next (Like, I'm not sure if its not pulling that data because of the way it's being rendered, or because it's part of some frame element or something - the bulk of my web knowledge is a bit out of date.)
Any direction that could be provided to know how I might work around this would be much appreciated, and thanks again for this great tool!

A few people have had the same issue and it is due to the request not waiting until all the elements on the page are loaded before returning the response.
A temporary work around is to add a delay to the page load:
$delay = 5; // In seconds

$request = $client->getMessageFactory()->createCaptureRequest('http://jonnyw.me');
$request->setDelay($delay);

Documentation
There is an issue relating to this issue that has some other suggestions you could try.
I am looking into a more elegant solution to this.

Thank you so much, that is working for me!

Hi @jonnnnyw I'm trying to not to open a new issue so hope you can lend me a quick help.
I have tried applying the delay and make a screenshot. It is working, your website fully loaded in the screenshot
http://i.imgur.com/dXf2566.jpg
But whenever I echo the content, I got this
http://i.imgur.com/zjF2Hp1h.jpg
This is my code
<?php
    require("vendor/autoload.php");
    use JonnyW\PhantomJs\Client;

    $client = Client::getInstance();

    $delay = 5;

    $request = $client->getMessageFactory()->createRequest();
    $request->setMethod('GET');
    $request->setUrl('http://jonnyw.me');
    $request->setDelay($delay);

    $response = $client->getMessageFactory()->createResponse();

    $client->send($request, $response);

    if($response->getStatus() === 200) {
        echo $response->getContent();
    }


Cannot locate %userprofile%\AppData\Local\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState\ in windows. help?

If you're reporting an UI issue, make sure you take a screenshot that shows the actual bug.

having same issue


Promisify all public api.

Using bluebird to make using all public api as a promise & yield-able.

Closed due to duplicated changes, reopened at #17 . :sweat_smile:


What is USE_OPTIMIZED_BLAS used for?

This is not a bug but merely a question. I'm quite new to BLAS and LAPACK, and while I understand the basic concept what they are useful for, there are a number of things that I do not fully grasp.
One such question is why OpenBLAS would have the USE_OPTIMIZED_BLAS option. Is this only for benchmarks against another BLAS library, or does OpenBLAS actually support falling back to another BLAS library? What would that be used for?
I was thinking that it would be really cool if OpenBLAS could at runtime check which of a number of BLAS libraries is faster for a specific method and bind that dynamically. But that is not whats happening here, no? Do such wrapper libraries exist?

This option is only present in the build files of the LAPACK source that OpenBLAS imports from the reference implementation (Reference-LAPACK here on github, otherwise known as "netlib"), and is not actually used when building LAPACK as a part of OpenBLAS. In the original context of Reference-LAPACK, the option makes sense as the reference implementation also contains the unoptimized reference BLAS, and by default compiles and links LAPACK against it. Within OpenBLAS, the BLAS
references are naturally satisfied using OpenBLAS code (and some LAPACK routines are replaced with optimized versions as well).
I am not aware of a wrapper that does runtime checks to select the best implementation on the fly, and I question its practicability.

Thanks a lot @martin-frbg , that's a very helpful answer. I'm closing this issue then.


Filter Saturated Lines in COMP Lamps

Do not confuse this with filtering out COMP lamps that have saturated pixels. Only files that should be filtered out are FLATs

Could be useful but not worth the effort now, also this issue is almost ~ 3.5 Yrs old


Handle both ‘writers_schema’ and ‘writer_schema’ from a DatumReader

The Py2 version of a DatumReader has an attribute writers_schema which contrib/bigquery_avro.py references.  The Py3 version calls the same thing writer_schema, dropping one s.  We (Spotify) had trouble with a program (bq-load) built on Luigi which loads avro files into bigquery, because of this problem.
https://github.com/apache/avro/blob/master/lang/py/src/avro/io.py#L634-L641
https://github.com/apache/avro/blob/master/lang/py3/avro/io.py#L421-L428
This PR adds machinery to handle both versions.  It checks for one attribute then the other.   (As opposed to, say, branching on language version)
Unfortunately there aren't any tests for bigquery_avro, and I don't know enough to write them.
I did, at least, run bq-load with this version of Luigi and confirm that it solved my particular problem.

Is this a duplicate of #2827 ?

I believe so, and I prefer the solution in #2827.

@bardb Do you agree? Shall we close this PR and follow up in #2827 ?

Either way.
I definitely like  #2827 https://github.com/spotify/luigi/pull/2827 's
tests.
I wrote mine as "use whichever attribute is available" rather than "use
writers for py2, writer for other py" because I don't 100% trust Avro not
to come up with a py2 release which uses writer, or even a py3 release
which goes back to writers.
But that's not very likely, with Py2 going away and all.
So sure, whichever.
On Fri, Nov 15, 2019 at 5:05 AM Honnix<EMAIL_ADDRESS>wrote:

@bardb https://github.com/bardb Do you agree? Shall we close this PR
and follow up in #2827 https://github.com/spotify/luigi/pull/2827 ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spotify/luigi/pull/2828?email_source=notifications&email_token=ALC7XJIQLRI725V42NGJA2TQTZX6TA5CNFSM4JNQ2Y4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEE6MWA#issuecomment-554296920,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALC7XJPF7N4LDSZ6F5PP333QTZX6TANCNFSM4JNQ2Y4A
.

(Closed because https://github.com/spotify/luigi/pull/2827)


Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description

Brief Issue Summary
For a while now (at least 3 months), the cmake-tools extension has been spamming the shared log with the warning message reproduced below. This happens on startup, and then periodically throughout the session, regardless of whether or not anything cmake-related is open or running; the presence of the installed extension is sufficient to reproduce. Changing the logging level to debug doesn't affect anything in any direction.
This is with vscode-cmake-tools v1.17.16 running on the latest MS-published vscode build (1.86.2) on Linux (repros on Ubuntu noble daily, Ubuntu jammy, Ubuntu bionic with the older still-compatible vscode 1.85.whatnot). No idea about other OS-es, sorry.
The locale environment is LANGUAGE=en_US and LANG=en_US.UTF-8 and it also reproduces with LANG=C .
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.606 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.607 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.607 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.607 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.
2024-02-27 13:42:56.607 [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description.

CMake Tools Diagnostics
I'd love to be able to provide this, but I can't seem to find this command at all.

Debug Log
No response
Additional Information
No response

It looks like the correct key is cmake-tools.configuration.cmake.options.advanced.statusBarLength.markdownDescription.  Needs to be updated in package.json.

@mihailim @bobbrow Thanks for pointing this out, I have a PR open here: #3618

How do I resolve the issue if I don't have a package.json file?

@IkeCuizhihui If you don't want to wait for the next extension release and it bothers you that much, you can switch to the prerelease version of the extension -- open the extension's page (go to Extensions and click on CMake Tools) then click the "Switch to Pre-Release Version" button under the extension description, next to the "Disable" and "Uninstall" buttons. Then after it switches, click Reload, and then you may need to close and reopen vscode once to fully get rid of the warning spam.
But, to be honest, I wouldn't risk it if it's a prod environment you need to be sure the extension is stable and working. After all, it's not that big of a deal, more or less an aesthetic annoyance.

It's been two months since this was merged.
Any chance someone can cut a release that includes this?

I'm seeing this as well - can we have a new release, please? :)

This went out with microsoft/vscode-cmake-tools#v1.18.41 so there's no need to run pre-release anymore. Thanks all.

Any updates on it? Release version v1.18.44 and pre-release v1.19.40 both have this problem too.

@zhongxiang117 This has been fixed for a while. You may be referring to the similar but different issue with [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.deleteBuildDirOnCleanCconfigure.description which is issue #3865 . That one isn't released yet, annoyingly.

@mihailim thanks for your reply, it is the same issue.

Also, another version:

You're right, my apologies. I can confirm it's happening with the pre-release version v1.19.40, but not with the release version v1.18.44. On the other hand, the release version suffers from the #3865 issue, but not from this issue. So the fix for this issue was probably lost for the pre-release version, and currently both of them are annoying for different reasons :)

@mihailim , OK, I will switch back to v1.18.44. Also, my apologies for the wrong screenshot, I was using the same picture for twice (as you will see the time stamp are the same).

For version v1.18.44, this issue is gone, thanks for that!

@mihailim @zhongxiang117 I'm not sure I fully understand from your comments, which error is happening where?

With a quick test and viewing the source code, these issues are fixed in the most recent code. If you could tell me any steps you take to see this output, it'd be great so that I can test and see for myself. Thanks!

@zhongxiang117 Are you doing anything specific to get this output? I'm opening the extension on the most recent release and I don't see the issue

Quick question, is cmake-tools has any dependencies? Like this extension CMake?

@zhongxiang117 Are you doing anything specific to get this output? I'm opening the extension on the most recent release and I don't see the issue

Could you provide any steps? Are you using any other display language than English?

Quick question, is cmake-tools has any dependencies? Like this extension CMake?

Yes, currently there is an extension dependency on the one that you have in your screenshot. We hope to remove that at some point as we implement and improve our own language services for CMake files.

@gcampbell-msft it's not actually a dependency. It is just bundled with this extension. Anyone can uninstall it if they want to use a different language server for CMakeLists.txt.

@bobbrow Good clarification, you are correct, it's not a dependency but a bundle. Thanks. I'll update my comment as well

Yeah, the top-level readme has a link to another language server extension.

@zhongxiang117 This has been fixed for a while. You may be referring to the similar but different issue with [warning] [cmake-tools]: Couldn't find message for key cmake-tools.configuration.cmake.deleteBuildDirOnCleanCconfigure.description which is issue #3865 . That one isn't released yet, annoyingly.

@mihailim We have released this in the most recent pre-release. Additionally, we no longer use the key cmake-tools.configuration.cmake.deleteBuildDirOnCleanCconfigure.description, as it has a typo, it was fixed to be cmake-tools.configuration.cmake.deleteBuildDirOnCleanConfigure.description.

OK, I got it, thanks for you two.
The steps is: I installed v1.19.40 and then removed CMake extension, then happened to have this issue.
Now, it seems I cannot reproduce them, v1.19.40 and v1.18.44 both work well.


Link up the Portable DirectRunner

This can execute pipelines via the Portability APIs, but here only via
the InProcess channel.
Interface and dead code cleanups are also included here.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

CC: @herohde


Date picker input tabindex

Is there a way to add the tabindex attribute to the datepicker input element?

I guess not then, I'll submit a pull request sometime soon.

PRs appreciated!


chore: Update lint command to use apiclient. See #2116

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[x] Optional. I've added My organization is added to the README.
[x] I've signed the CLA and required builds are green.

Depended on by #2116

Thank you @sarabala1979


Merge InvenTree/InvenTree master

Pull Request Test Coverage Report for Build 942434816

8 of 21 (38.1%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 73.14%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

InvenTree/part/templatetags/inventree_extras.py
2
3
66.67%

InvenTree/build/models.py
0
12
0.0%

Totals

Change from base Build 909023169:
-0.03%

Covered Lines:
14100

Relevant Lines:
19278

💛  - Coveralls


add view count with eye

Oops, accidentally created this issue from a task list ... was trigger-happy


Image component deprecation of resizeMode not wired through to react-native-web properly.

Current Behavior
The Image component deprecates resizeMode, but doesn't pass objectFit through to the resizeMode prop in the web platform. Since react-native-web doesn't support objectFit prop directly yet, this ends up breaking functionality unless you override / ignore the deprecation.
Expected Behavior
Pending proper support of the prop at the react-native-web layer, I would recommend / expect that the Tamagui layer should forward the objectFit prop value to the resizeMode prop on the underlying Image element inside a conditional check for the web platform.
I think it is debatable that this should, perhaps, additionally be filed as a bug against react-native-web, but I think a better intermediate developer experience is for Tamagui to own this since Tamagui is choosing to own the deprecation in its own code (thus potentially misleading developers into expecting it to work, where it clearly won't as-is).
Tamagui Version
1.100.3

Platform (Web, iOS, Android)
Web

Reproduction
<Image
	source={someImage}
	width="100%"
	height="100%"
	aspectRatio={1}
	objectFit="contain"
/>

will not work as expected and will still end up assigning cover (the default value) to the background image on web.
Changing it to:
<Image
	source={someImage}
	width="100%"
	height="100%"
	aspectRatio={1}
	objectFit="contain"
	resizeMode="contain"
/>

Works as expected, but incurs the deprecation warning.

### System Info

_No response_

Good catch, fixed in 3c12cbfe5e1861a0799977a60573d843551b6330
Note we have a new @tamagui/image-next that will be the default in v2, coming soon, but can be used now. Much faster.


Updated cosmos emulator yml script

Updated cosmos emulator yml script to remove the existing installation, install latest version and run emulator with latest version

@weshaggard do you have an idea why check-enforcer seems to be stalling here?

/check-enforcer evaluate

/azp where

There appears to be some github/devops status check issues going on. It looks like the PR job was triggered https://dev.azure.com/azure-sdk/internal/_build/results?buildId=715315&view=results but it failed. We need to make sure we get that job passing and that we follow the workflow for testing and syncing these eng/common changes.

There appears to be some github/devops status check issues going on. It looks like the PR job was triggered https://dev.azure.com/azure-sdk/internal/_build/results?buildId=715315&view=results but it failed. We need to make sure we get that job passing and that we follow the workflow for testing and syncing these eng/common changes.

I see that job is failing because of some timeout / clone issues - https://dev.azure.com/azure-sdk/internal/_build/results?buildId=715315&view=logs&j=96791242-dbf3-587e-3a06-ae5af5c1a705&t=8506b04f-b021-528c-7be1-2b21c2d1a67b&l=159

@chidozieononiwu can you please take a look at https://dev.azure.com/azure-sdk/internal/_build/results?buildId=715315&view=logs&j=96791242-dbf3-587e-3a06-ae5af5c1a705&t=bb13a226-9801-467d-b787-35f80b72d45b to see if you can figure out what is happening there.
@kushagraThapar as for the pipeline checks not updating here I'm on an ICM call with DevOps right now about that issue, it may or may not be related to the issue we are seeing in the build pipeline.

@chidozieononiwu can you please take a look at https://dev.azure.com/azure-sdk/internal/_build/results?buildId=715315&view=logs&j=96791242-dbf3-587e-3a06-ae5af5c1a705&t=bb13a226-9801-467d-b787-35f80b72d45b to see if you can figure out what is happening there.
@kushagraThapar as for the pipeline checks not updating here I'm on an ICM call with DevOps right now about that issue, it may or may not be related to the issue we are seeing in the build pipeline.

Thanks @weshaggard , appreciate your effort on this. As mentioned earlier, this is a blocking issue for us right now, since we can't get anything checked in. So let me know if you need more justification for the ICM just in case.

@kushagraThapar I'm actively on the ICM bridge I don't think we need more justification. There is a teams thread in our EngSys Team channel we are keeping updated based on this information.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

@kushagraThapar the devops issue has been resolved now you need to follow the eng-common workflow to finish up this PR. I suggest we verify that the cosmos pipelines work in each of the 4 languages and we address any feedback in the inline PS code before going to the next stage of the workflow which creates the sync PRs. If you need help please ping me and I will assist.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

This looks like a good starting point. As we talked offline it would be good if we can get the inbox emulator modules to support running different versions (i.e. by-pass the registry lookup and just run the emulator next to where the module).

Makes sense, not sure if it is possible though, I will let @milismsft  comment on that :)


API errors not working

To recreate this simply open the api route to an item and pass an invalid id, e.g. a row that doesn't exist.
In the show function in the generated API Controller, in the case of the record not found the JSON response is not returned. Instead the default "sorry" web page is shown. This is because the find method of the repository does a findOrFail fails and throws an exception. This exception is then rendered to a web page in the Exceptions/Handler.php render method.
Although this could be fixed by changing the find on the repository to findWithoutFail I believe a better design for API error handling is to render any exception like a find failing to JSON in the Handler class if the route is an API one. This way all errors caused by exceptions can be rendered to JSON rather than by manually creating error responses in controllers which obviously is very error prone as in the example above. Search for the render method in this page for what I mean:
https://laracasts.com/discuss/channels/code-review/best-way-to-handle-rest-api-errors-throwed-from-controller-or-exception

I have a solution to the problem by creating Exceptions/APIHandler and updating the singleton in the api_routes.php. This enables rendering of exceptions to JSON for only API routes without any modifications to the existing Handler class. Happy to do a pull request.

thanks @malhal. I will take it in a queue to support a custom exception handler.

Also I think findWithoutFail is unnecessary. If find does fail then the built in exception handling happens which is what most people would want. The exception might not always be not found and null returned which is what the controllers are assuming. Best just less it fail, exception, thrown, handler generate output.

Issue fixed in the latest version and removed Presttus repository pattern.


Update openapparel.org references

Overview

Adds .opensupplyhub.org to the ALLOWED_HOSTS list in settings.py
Changes DEFAULT_FROM_EMAIL in settings.py
Adds opensupplyhub to CORS_ALLOWED_ORIGIN_REGEXES in settings.py
Updates reports that exclude OAR emails with AND NOT u.email LIKE '%openapparel.org%' to also exclude opensupplyhub.org email addresses.
Replaces openapparel.org with opensupplyhub.org in some tests and management commands, when seemed appropriate

Connects #2277
Testing Instructions

Run ./scripts/test
Go to /admin/reports and view api_request_by_user, api_requests, average_matches_per_facility_by_type, contributor_first_appearance, contributors_with_active_facilities, countributors, facility_list_items_uploaded, facility_lists_uploaded, industry_data_vs_oar_data, industry_data_vs_oar_data_cumulative, mailing_list_recipients, non_public_contributors, percent_data_by_contributor_type, percent_data_by_contributor_type_cumulative, public_contributors, unique_contributor_count_by_type, and unique_public_list_count. Confirm they behave as expected.

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[ ] This PR is targeted at the correct branch (develop vs. ogr/develop)
[ ] If this PR applies to both OAR and OGR a companion PR has been created

Looking at this now.

Thank you for reviewing!


GAMS executable not found in PATH

ixmp show-versions returns the message "GAMS executable not found", while GAMS has been added to the path, both for system-wide and user-specific environments. Per discussions in Slack, an older version of GAMS (<40) was installed, but the problem exists. Are there any specific system requirements when ixmp looks for GAMS in the path and throws an error if not found?

Is this possibly related to install issues on macOS? If so, might it be answered by iiasa/ixmp#473?


Browser Back / Forward Button Click changes the URL, but actual navigation does not happen and Previous or Next page does not get loaded.

Describe the bug
Browser Back / Forward Button Click changes the URL, but actual navigation does not happen and Previous or Next page does not get loaded. This seems to be the issue only when filtering assets. When you navigate to details page and then click browser back button (not the back UI button in the details page) - the previous page does get loaded. This is not the case whit filter urls.
Environment
aem.enablementadobe.com
also
AEM Version: AEMaaCS 2023.12.14538.20231205T165334Z-231100
Asset Share Commons Version: 3.8.4
both, also local
To Reproduce
Steps to reproduce the behavior:

Go to demo light page for Asset Share ( https://aem.enablementadobe.com/content/asset-share-commons/en/light.html )
Click on right side filter TYPE > VIDEO (once clicked - results grid will update.
Click browser BACK button.
URL changes to previous url (home page) but the previous page does not load (the page content remains the same as when TYPE > VIDEO filter was applied).
the same happens when any other filters are applied.
for example - you can click again on the TYPE>VIDEO filter and then add another filter TYPE>IMAGES.
the results grid will be updated with new results.
click on the Browser back button once and then once more.
url changes once and then once more - but previous pages do not get loaded - the page with 2 filters applied is shown to the user.

Expected behavior
Click on the browser button should change url to previous url AND also load the previous page. The url change should also navigate to that particular page / url.
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/adobe/asset-share-commons/assets/129842971/cf03268c-4111-4061-b5e0-0ebe4495ea2f
Additional context
nothing to report here

This should fix it: https://github.com/adobe/asset-share-commons/pull/1120


invalid number of codes - SIGSEGV (Address boundary error)

encodec_build_graph: invalid number of codes
fish: Job 1, './bark/build/examples/main/main…' terminated by signal SIGSEGV (Address boundary error)

./bark/build/examples/main/main -m ./ggml_weights_q4/ -p "this is an audio"

Hi @acheong08 ! This should be fixed with #139 . Could you give it another try?


Boundaries and stepper size for numerical edit field

Is your feature request related to a problem? Please describe.
Users don't like th click the stepper per 1 (minute) when entering the duration of a meeting event, per 15 or 30 would be much easier...
Describe the solution you'd like
Define the min/max boundaries and stepper size of a numerical edit field
Describe alternatives you've considered
Checking boundaries could be in an onChange trigger
Additional context

Any idea if and when this could be realized? Would be really usefull for making user friendly interfaces


[video_player] Add Fullscreen for Web

Add Fullscreen for Web

/cc @ditman

This feature is not available in any of the platforms, according to this:
https://github.com/flutter/flutter/issues/58114

@ditman if I change the parameter to make controls = true fullscreen works great.
video_player_web.dart line 157
videoElement = VideoElement()
..src = uri
..autoplay = false
..controls = true
..style.border = 'none';

@Bilonik I understand that that can be done, however, the plugin needs to run consistently across all platforms. (Ideally we should think on how to add the full screen feature to all platforms, that's why I linked the global issue)

This works for web, but not the other platforms, right?

Any updates?

Waiting for results

@ditman I believe this feature should only be available on the web, as developers may want to include custom transitions and animations on other platforms, but that is not possible on the web due to restrictions in browsers like Apple's WebKit. Additionally, the web is currently the only platform where packages built on top of video players cannot utilize the enter functionality, as the VideoElement implementation is hidden.


build-bazel-package: switch hash mode to “flat”

flat hashes can be substituted through hashed-mirrors, while recursive
hashes can’t. This is especially important for Bazel since the bazel
fetch dependencies can come from multiple different methods (git,
http, ftp, etc.). To do this, we create tar archives from the
output/external directory, which is then extracted to build. All of
the Bazel hashes are all updated.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Should this be mentioned in the change log?

flat hashes can be substituted through hashed-mirrors, while recursive
hashes can’t.

Can you elaborate more on this? I'm not sure that I know the difference aside from file vs directory.

Yes, happy to elaborate, as this is something I've spent a lot of time looking at! I've been meaning to write up some more documentation about hashed mirroring, its advantages, and its limitations, but alas somehow one never finds the time to write docs ... anyways.
Currently, we of course have cache.nixos.org, which is the full Hydra binary cache. It has both source packages and binary packages, since it has everything Hydra needs.
We also have tarballs.nixos.org, which just has source packages mirrored. One constraint is that it is just holds simple content-addressed files, like those grabbed by fetchurl. The structure looks like:
https://tarballs.nixos.org/<hash-type>/<hash>

where <hash-type> is something like sha256, and the hash is the actual hash of the file in the server at that location.
Concretely:
$ wget tarballs.nixos.org/sha256/0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i

$ nix-hash --type sha256 --flat --base32 0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i
0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i

In our nix expressions, we actually reference 0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i directly in the package expression, like so:
https://github.com/NixOS/nixpkgs/blob/84cf00f98031e93f389f1eb93c4a7374a33cc0a9/pkgs/applications/misc/hello/default.nix#L9
This makes it trivially simple to substitute in an alternate fetcher that's just a basic S3 bucket or webserver with a directory of tarballs addressed by their hashes in a straightforward manner, and the fetchers will look there first. You can see that what we have there does in fact have this hash:
$ nix-build -A hello.src
/nix/store/3x7dwzq014bblazs7kq20p9hyzz0qh8g-hello-2.10.tar.gz

$ nix-hash --type sha256 --to-base32 $(sha256sum /nix/store/3x7dwzq014bblazs7kq20p9hyzz0qh8g-hello-2.10.tar.gz | awk '{print $1}')
0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i

This is great for mirroring, because it's simple, secure, efficient, and easy. Moreover, even users who are not using the Hydra binary cache or who are building nix stores at different store prefixes can still use tarballs.nixos.org or mirror it directly onto their own enterprise FTP servers/Artifactor/Nexus/etc., without a hash change.
While it is certainly possible to setup a spoofing mechanism by which tarballs are addressed both by their direct hashes and by the hash that they would have if you were to unpack them and recursively hash the directory, NixPkgs currently has no real mechanism for doing this, and it's a little dubious, since you pollute your hashed mirror with things that are addressed not by their direct content but by a proxy of content. The Software Heritage has a notion of "cooking" a tarball where you ask for something and they see if they have something that could satisfy that with some mutation, but it's a more complicated process and a little harder for users to understand/verify themselves.

That said, there are many other advantages to using a flat tar.gz file for the source package, enough so that even if the above were solved [1] we'd still want to go this route regardless. I've recently updated all of the cargo fetchers this way in #79975.
All six points at the top of that PR description are just as relevant for Bazel (if not moreso). For instance, I have some remote builders on AWS, and right now they completely choke while they replicate the tensorflow Bazel dependency src dir back and forth! When it's compressed the source directories are 80-90% smaller, which saves a ton of network traffic and builder time, resulting in a much more pleasant experience.
[1] I'd argue solving the above is a case where the cure is worse than the disease, because you end up with more complicated infra that's harder to reason about, but reasonable minds may disagree.

Note you'll have to manually trigger the builds for the derivations that use buildBazelPackage to make sure they all build correctly.

Note you'll have to manually trigger the builds for the derivations that use buildBazelPackage to make sure they all build correctly.

Yes - this is an annoying part of Nix's caching mechanism. I think we can do something to make this better by validating the hash afterwards. Something similar is done in buildRustPackage:
https://github.com/NixOS/nixpkgs/blob/4d66a37dd5c76996f8068b84ff4c32e75bb81cc8/pkgs/build-support/rust/default.nix#L105-L142


Merge latest changes into 'Step 1-5'

Merge latest fixes from step-6 into step-1-5 branch.
This will make it easier to merge changes from final through to all branches in the future. Unfortunately due to the way existing changes were cherry-picked into the previous branches, this leads to some commit duplication. However, this it's going to make it much easier to merge changes in the future.

LGTM, fyi see my comment in #32


Add reactor Bindings

Is your feature request related to a problem? Please describe.
In order to integrate with reactive apps, you have to either execute blocking calls using Mono.fromCallable or create an implementation based on WebClient.
Describe the solution you'd like
A reactive binding of google-auth-library based on WebClient. The implementation would be re-usable for other cloud component's apis. The authentication token generation and the api call creation could be used to make more functionalities reactive.
Describe alternatives you've considered
quarkus
Additional context
This is related to an issue and PR on the spring-cloud-gcp projec
https://github.com/GoogleCloudPlatform/spring-cloud-gcp/issues/2027
https://github.com/GoogleCloudPlatform/spring-cloud-gcp/pull/2028

Figured I would add this to further emphasize how valuable I believe this issue/request is. From the cloud run docs https://cloud.google.com/run/docs/tips/java#write_non-blocking_reactive_code_to_optimize_memory_and_startup:
To truly reduce the number of threads, consider adopting a non-blocking reactive programming model, so that the number of threads can be significantly reduced while handling more concurrent requests. Application frameworks like Spring Boot with Webflux, Micronaut, and Quarkus support reactive web applications.
This is ironic to me - the docs themselves suggest using reactive code yet there is very little reactive support across the java google libraries.

@gkatzioura @brianmaresca Thanks for raising the issue and proposal. We will take a look.

Relevant pr
https://github.com/googleapis/google-auth-library-java/pull/1297


How to auto hide scroll and show scroll?

How to auto hide scroll and show scroll  when user will scroll / hover element?

currenctly scroll always show. i want to hide and only show scrollbar when user will scroll.
How to do it?
Thanks

You could try overflow-y-hidden hover:overflow-y-auto.

This is a fairly common question, so I included this in the README a while back:

NB: This plugin styles scrollbars; it does not force them to appear. Use typical CSS techniques to force content to overflow and trigger a scrollbar.

@RVxLab's solution is what you're looking for. :)

You could try overflow-y-hidden hover:overflow-y-auto.

won't work for touch screen

Touch screen devices typically don’t have scroll bars. It’s not needed there.


Plugin ecosystem / discoverability

As discussed in https://github.com/vuejs/vite/issues/34, plugins could be named vite-plugin-xxx.
I published vite-plugin-proxy, because it's something I missed from webpack-dev-server.
Maybe it's useful to mention this in readme so users can discover / find such plugins. Would you take a PR that adds this into vite's README?

 For now I think it's best to keep it undocumented.

Makes sense. Also makes sense to wait for config file too. One note, currently when passing a plugin all output from vite is suppressed.


pencil: 2.0.15 -> 2.0.18

Fixes issue #13755

Please properly name commit to follow our guides in CONTRIBUTING.md.

Works for me

@uralbash will you please also change the subject of the commit itself?


Project level mirroring

We have large project with several thousands repositories. We have remote CI infrastructure on gitlab. To avoid hook configuration at repository level, repository remote url interpolation is introduced. This allows project level hook configuration. Repository hook configuration is inherited from project (I don't know since when it is supported in bitbucket).
Also notice ClassCastException workaround in pushExecutor after each plugin upgrade.
Please review if this makes sense for Your mainstream project.

Added form for manual mirror triggering and deleting from remote host

Project level configuration of mirroring would be very useful!

This would be a very useful feature for us. Any idea when it is going to be merged to main?