[Bug]: Trying to save the signature to database but failed

What happened?
Is their any way to save the signature in to database
How to reproduce the bug
I'm trying every possible way i know to save the signature
Package Version
2.0.0
PHP Version
8.2.0
Laravel Version
10.0.0
Which operating systems does with happen with?
Linux
Notes
No response

I have solved that by creating a hidden field
` SignaturePad::make('signature_pad')
                                            ->label('Signature')
                                            ->clearable()
                                            ->disabled(fn ($state) => !empty($state))
                                            ->downloadable(false)
                                            ->undoable()
                                            ->live()
                                            ->visible(fn ($get) => empty($get('signature')))
                                            ->afterStateUpdated(fn ($state, $set) => $set('signature', $state))
                                            ->confirmable(false),

                                        Hidden::make('signature'),

                                        ViewField::make('signature')
                                            ->visibleOn('edit')
                                            ->visible(fn ($state) => !empty($state))
                                            ->view('filament.forms.components.image'),

`

It should just work. I'm using it.
Would you mind creating a reproduction repo?

@nourdar  please share full details the view file how it looks like and the signature column type in DB?

@saade @abhi051002 Maybe it helps
Concept

Set Signature
Convert base64PNGencode to File
Save to Livewire Temporary File with afterStateUpdate and
Auto Passing to Filament FileUpload Forms so you can upload to S3 or whatever you want
File Upload in the background with AlpineJS help
Hint Action to Delete
a. If save to DB then delete file from storage and set back record to NULL
b. Else delete file from livewire-tmp then you can re-assign signature

Reference
Credit to silvanhagen
Video https://www.youtube.com/watch?v=sIsxq7j_4vY
Code Snippet https://silvanhagen.com/writing/background-file-upload-in-filament-forms/
Implementation
    public function form(Form $form): Form
    {
        return $form
            ->schema([
                SignaturePad::make('signature')
                    ->label(__('Sign here'))
                    ->downloadable(false)
                    ->undoable()
                    ->live()
                    ->visible(fn($get) => empty($get('ttd')))
                    ->confirmable(true)
                    ->afterStateUpdated(function ($state, $livewire) {
                        if ($state) {
                            $base64_string = substr($state, strpos($state, ',') + 1);
                            $image_data = base64_decode($base64_string);
                            $file_name = Str::random(40);
                            $file = self::createTemporaryFileUploadFromUrl($image_data, $file_name);
                            $livewire->dispatch('test', $file);
                        }
                    })
                    ->columnSpan(4),

                Forms\Components\FileUpload::make('ttd')
                    ->label('Signature Result')
                    ->downloadable()
                    ->disabled()
                    ->dehydrated()
                    ->directory('abc')
                    ->required()
                    ->hintAction(
                        Action::make('Delete')
                            ->icon('heroicon-m-trash')
                            ->visible(fn($state) => filled($this->user['ttd']) || $state)
                            ->requiresConfirmation()
                            ->action(function ($state, $set) {
                                if (!empty($this->user['ttd'] ?? null)) {
                                    Storage::disk('public')->delete($this->user['ttd']);
                                    $this->user['ttd'] = null;
                                    $this->user->save();

                                    return redirect(request()->header('Referer'));
                                } else {
                                    $file = reset($state);
                                    if ($file instanceof \Livewire\Features\SupportFileUploads\TemporaryUploadedFile) {
                                        Storage::delete($file->getPathName());
                                        $set('ttd', null);
                                    }
                                }
                            })
                    )
                    ->extraAlpineAttributes([
                        'x-on:test.window' => '
                                    const pond = FilePond.find($el.querySelector(".filepond--root"));
                                    setTimeout(() => {
                                        pond.removeFiles({ revert: false });
                                        pond.addFile($event.detail);
                                    }, 750);',
                    ])
                    ->image()
                    ->columnSpanFull(),
            ])
            ->statePath('data');
    }

    public static function createTemporaryFileUploadFromUrl($favicon, $filename): string
    {
        // Step 1: Save the file to a temporary location
        $tempFilePath = tempnam(sys_get_temp_dir(), 'upload');
        file_put_contents($tempFilePath, $favicon);

        // Step 2: Create a UploadedFile instance
        $mimeType = mime_content_type($tempFilePath);
        $tempFile = new UploadedFile($tempFilePath, basename($filename), $mimeType);
        $path = Storage::put('livewire-tmp', $tempFile);

        // Step 3: Create a TemporaryUploadedFile instance
        $file = TemporaryUploadedFile::createFromLivewire($path);

        return URL::temporarySignedRoute(
            'livewire.preview-file',
            now()->addMinutes(30)->endOfHour(),
            ['filename' => $file->getFilename()]
        );
    }

Video Preview
https://github.com/user-attachments/assets/cac6d671-979e-44eb-9608-d10a6a0845b9


Set animateChanges on observer during initialisation

The animateChanges parameter that was passed to the fetched data source during initialisation was never used. This pull request fixes that by passing animateChanges to the observer.

Good catch. I'd move these into the init calls though (of each observer and the parent observer type).
While we're at it, I'd also remove the default value here: https://github.com/djbe/FetchedDataSource/blob/master/Source/FetchedResultsObserver.swift#L14, and make the var isVisible = true into private(set) var isVisible = true.

I moved animateChanges to the init call, and made the isVisible setter private.


refactor(typings): add types folder icon

I promise this is the last one for today
Changes proposed:
Add types to the typings folder icon

😁 No problem @sasial-dev! Thank you for your hard work. I won't have time today for reviewing more PRs. I expect to have more time during the week. I'm going to make a release with what we have already merged and prepare a new one for this week (hopefully).

Why did you chose the green typings icon over the regular blue TypeScript folder icon for types?
I think a folder named 'types' contains regular exported types and interfaces for TypeScript in .ts files.

Why did you choose the green typings icon over the regular blue TypeScript folder icon for types?
I think a folder named 'types' contains regular exported types and interfaces for TypeScript in .ts files.

I believe that blue TypeScript icons are for source files, where is the actual code stored (.ts). And green ones are made specifically for types (folders and .d.ts files). So that could be easy to tell them apart without reading the file extension.


Add more directives

Markdown in directives/blocks like {margin} and {admonition} does not get rendered
Would it be sufficient to add |margin|admonition in this line in the syntax file?

Ah, seems like those should rather be added to templates/directives.yaml

closing, as #45 is now merged


Qn: Wiring diagram for this library...

Hello,
Thanks for writing this library - I wasn't looking forward to hand cranking it myself. It doesn't seem to work for me though. I assume I've not wired my Arduino Pro Mini to the Zeta chip correctly, or it's because I've got the 433 MHz chip.
Could you please add to your repository anything that may help me. E.g. photo of a correctly wired up module to an Arduino, wiring diagram, or guidance around 433 MHz settings.
I'm working on a data radio project for a youth group I work with.
Thanks very much in advance.

Hello,
You're welcome, it's a quite nice little rf module :-)
The problem you have is because the library, by default, is configured for 868MHz (config header). I will have to add an option to change that...
To fix that it should be as easy as changing the central frequency using WDS (Wireless Development Suite) and the config xml I provided (si4455_revb1_bidir_fixed_crc_pre10_sync4_pay8.xml), to generate the right config header for the 433MHz module.
I just generated one (had to zip it to upload it here), please try it (replace the existing one) and let me know if it works :
radio_config_fixed_crc_pre10_sync4_pay8.h.zip
The 433MHz module should have the same hardware pretty much I think (same XTAL), so it should work. Otherwise I will look into that a bit more later.

Hi,
Thanks for the quick reply. I'd just generated a 433 MHz header based on your existing one myself. I also introduced a new FREQ_433 define to switch which WDS include I use. I still have problems though.
The waitCTS() function appears to never exit - it doesn't seem to receive the interrupt from the Zeta chip. This is why I think I've got some wiring issues.
I've uploaded a diagram of my wiring (Twitter was just the easiest way to do it...) https://twitter.com/adamfowleruk/status/842445225469579264
If you could please take a quick look - I imagine it's a really simple fix.
Once I have it working I'll test both the variable and fixed packet configurations on the 433 MHz and send you a pull request for these two new header files, the #define for FREQ_433, and an updated README.
Thanks very much for your time.

I see, I'm pretty sure you inverted MISO and MOSI on your wiring. SDO should be connected to MISO (Master In) and SDI to MOSI (Master Out).
Be aware that the variable packet config is not very reliable at the moment, I had troubles with it and didn't had time to do more testings. It might be due to the packet config (preamble, etc) which are optimized for a very low latency (a few milliseconds) and not reliability... I might provide other configs one day.
But I'm interested if you can test it, maybe you'll have other results.
I also made some changes that I need to push, like a timeout in the waitCTS(). Will do that soon.

Hello,
Thanks for the advice. I had connected the Arduino as you said, but given the Arduino is acting as the master and not the slave I swapped the MISO and MOSI wiring around - and it worked!
I also commented out my changes (using delay instead of CTS) to sendMessage, and can confirm that this works on the 433 MHz version... at least when you wire up the project correctly!
I've not tested the variable length piece though.
I'll write up a quick blog entry, then I'll generate the relevant 433MHz configurations, add the FREQ define, and send you a pull request.
As I build my project I'll continue testing and sending you any modifications I need to make.
Thanks again for all your help, and providing this excellent library!

Always better when the wirings are correct :-p Glad it works!
Good to know the 433MHz module is supported as well, I may use one in the future. Somebody to test the 915MHz one? :-D
I just pushed some modifications, CTS timeout included, may be useful to you.
I'll merge your push request to add support to the 433MHz module then.
Good luck with your project, let me know if you run into any trouble with the lib or if something is missing!


Release Prod and Dev on t3desk

see title; also removed hacky chroma fix for submit06 machine

Merging to main b/c I tested dev release on my feature branch.


Port Tier 0 backend/legacyapi components over to the ooniapi services pattern

[ ] Probe Services (collector specifically)
[ ] Fastpath (part responsible for storing post-cans)
[x] DNS configuration
[ ]  Monitoring
[ ] OONI bridges
[x] Web Connectivity test helpers
[ ] Code signing

We will spin up individual issues for this when we get to this work


fix(TDI-46070): load resource from URL

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
https://jira.talendforge.org/browse/TDI-46070

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:


Add Twitter Dashboard

This pull request adds the Twitter tool: Twitter Dashboard.
Current issue: #124

PSA:

Goodbyes are never easy
Twitter Dashboard will be closing down in January. In the future, we hope to bring the best features from Dashboard to the broader Twitter community. Thanks for making Dashboard part of how you use Twitter. 💚, the @dashboardapp team

Ok, thank you very much for informing me about that.
@gingerbeardman


always true | false check with TypePredicate

Search Terms
TypePredicate

Suggestion
call a function with TypePredicate with an obviously true or obviously false argument is always useless,
and that maybe get a incorrect type guard, could we check this case or another limit set?

Use Cases

Examples

interface Node {
  //...
}
interface Identity  extends Node {
  //...
}
interface WTFIdentity extends Identity {
  //...
}

function isIdentity(node: Node) node is Identity {
    // ...
}

function isWTFIdentity(node: Node) node is WTFIdentity {
  // ...
}

declare const a: Identity;
declare const b: Identity || StringLiteral;
declare const c: StringLiteral;

isIdentity(a); // obviously true
isIdentity(b); // normal behavior
isIdentity(c); // obviously false
isWTFIdentity(a);  // normal behavior
isWTFIdentity(b);  // normal behavior
isWTFIdentity(c);  // obviously false

Checklist
My suggestion meets these guidelines:

[] This wouldn't be a breaking change in existing TypeScript / JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. new expression-level syntax)

I am not sure about the "obviously false" cases.. Types in TS are open, and we also have intrersection type, so do not see why you can not have a value that is both StringLiteral and WTFIdentity.
For the always true ones, i think this falls in the same category as the unneeded type assertion in tslint: https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/

I would recommend adding this check to https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/

I'm already planning to implement such a lint rule: https://github.com/fimbullinter/wotan/issues/127
Unfortunately this is not as easy as it seems.
The always true case might be pretty straightforward, but the always false case requires checking all nested properties of the resulting type for impossible intersections.
Currently this is not really possible to implement, because there is no way to create an IntersectionType using an API.
I remember that this was part of a PR that exposed type relationship APIs (or at least it was discussed there). Unfortunately it didn't get merged. @mhegazy is there anything blocking the addition of 2 new methods on TypeChecker: createIntersectionType and createUnionType? Maybe missing type factories? Should I open a new issue to discuss that further?


[sitecore-jss-nextjs/react][nextjs/react][v20] Update next to v13, react to 18

[x] This PR follows the Contribution Guide
[x] Changelog updated
[ ] Upgrade guide entry added

Description / Motivation
This PR updates nextjs to version 13. In addition to this:

Update to react v18
Update typescript to 4.9

Testing Details

[ ] Unit Test Added
[x] Manual Test/Other:

nextjs app builds, runs in connected, disconnected, prod modes
react app builds, runs in disconnected, connected modes
react forms work in connected mode
more testing to be done once canaries are published

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] Chore

Is this backwards compatible for people who are not yet in a position to run React 18 and Next 13?


\href{} Produces Huge number of elements (1 per character)

Katex is producing huge number of  elements when wrapping text within the \href{} directive. I can't see any immediate reason to suddenly produce 1 span per character, rather than just simply wrapping the range of identically styled characters in the  tag.
jsfiddle
I am generating a lot of text, and don't want the overhead of adding hundreds of spans for each link.
(La)TeX code:
\text{\href{https://google.com}{abcdefghijk}}

Expected behavior:

Environment (please complete the following information):

KaTeX Version: 0.10.2
Device: Desktop
OS: macOS 10.13.6
Browser: Chrome
Version: 76

@Pugio Thanks for the report. For reference, here is the current generated HTML:

Looking at the code, it seems we call buildCommon.tryCombineChars only in the outermost \text functions.  So e.g. \text{\href{https://google.com}{\text{abcdefghijk}}} generates the desired code, but e.g. \text{\href{https://google.com}{{abcdefghijk}}} doesn't.  I think ideally every group in text mode (and not just the calls to \text...) should call buildCommon.tryCombineChars.

Thank you for responding to this so quickly. The PR you created looks good (though I don't possess enough project knowledge to comment much) – I've wrapped my code in an extra inner \text{} and it looks good now, thank you!

#2080 is a partial fix for this.  There are still some spans that could potentially be combined but aren't because of the italics correction.  I'll open a separate ticket for the remaining work.


fix(deps): update terraform ibm to latest for deployable architectures

This PR contains the following updates:

Package
Type
Update
Change

ibm (source)
required_provider
minor
1.72.2 -> 1.73.0

Release Notes

IBM-Cloud/terraform-provider-ibm (ibm)
v1.73.0
Compare Source

Support for Db2 SaaS

Datasources

ibm_db2_connection_info
ibm_db2_whitelist_ip
ibm_db2_autoscale

Enhancements

feat(Cloud Databases): Update Database Password Complexity Validation (5701)

BugFixes

fix(Cloud Databases): Key protect revert fix (#5870) (5870)
fix(Cloud-Databases): RR & PITR Groups Attribute is Fixed for Source Formations with Multiple Members (5871)
fix(Cloud Databases): send host flavor with scaling requests (#5874) (5874)
Added 100 default capacity to the volume when no attributes is set (5865)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v3.20.3

Your semantic-release bot :package::rocket:


Double check implementation?

Using this tool: https://cryptii.com/pipes/crockford-base32

But the tests for the same input shows:
https://github.com/jetpack-io/typeid-ts/blob/091938da886f4d944a685158f9ea4fbcbfdbe1e0/test/typeid.test.ts#L114-L117
I was porting the code to Elixir using https://hex.pm/packages/crockford_base32 and the result from the library matches the online tool but does not match the Typescript implementation.
test "encode" do
  assert Typeid.encode("user", "01889c89-df6b-7f1c-a388-91396ec314bc") == {
           :ok,
           "user_0649s2ezddzhs8w8j4wpxgrmqg"
         }
end

Hi @cabello,
Thanks for reporting – I've added a ton of tests at this point, so I'm pretty certain the current implementation is "correct" (but it of course depends on what we define correct to be).
The encoding question has come up a few times and here's what we've learned:

Due to padding, there's different ways to implement a base32 encoding.
I've formalized the way TypeID implementations should do it in this document https://github.com/jetpack-io/typeid/tree/main/spec#base32-encoding
What it means in practice is that we implement the encoding the same way ulid does (so if you're looking to check your work against an online example, you're better off checking with something https://www.ulidtools.com/). It also means that we use crockford's alphabet in our encoding, but not the full set of Crockford rules.

You might ask, why do it the ulid way and not the default base32 encoding way? The reason is so that the typeid representation and the uuid representation align with each other in the following way:

prefix_00000000000000000000000000 <=> 00000000-0000-0000-0000-000000000000
prefix_00000000000000000000000001 <=> 00000000-0000-0000-0000-000000000001
prefix_0000000000000000000000000g <=> 00000000-0000-0000-0000-000000000010

To make this all easier to implement I've also added testdata to the spec, that people can use to test their implementations:

https://github.com/jetpack-io/typeid/blob/main/spec/valid.yml for data that should be considered valid
https://github.com/jetpack-io/typeid/blob/main/spec/invalid.yml for data that should be considered invalid

Hope that helps!

@loreto I found the spec today and it was quite useful, turns out the tool is also wrong, I mean wrong in terms of interpretation bytes vs text, etc.
I found a way around the dependencies that I am using that match the implementation specially the basic ones that makes total sense, e.g. test cases one, ten, sixteen.
Closing for now. Thank you


Add icons for playing/paused state for waybar

This can be enabled via config as shown in the readme.
I did not look at expanding the functionality to polybar because I do not use it but it shouldn't be hard to implement.
Happy to make changes if requested.

I decided to rework this in a much better way and will submit a different PR


Pull updates from idl repo

What changed?
Pull updates related to zonal isolation from idl repo

Why?

How did you test it?
existing tests

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 0187edcf-a510-4489-87b6-2408539daad1

0 of 0   changed or added relevant lines in 0 files are covered.
75 unchanged lines in 12 files lost coverage.
Overall coverage increased (+0.01%) to 57.215%

Files with Coverage Reduction
New Missed Lines
%

service/history/queue/transfer_queue_processor_base.go
1
77.62%

common/peerprovider/ringpopprovider/config.go
2
81.58%

common/task/weightedRoundRobinTaskScheduler.go
2
88.6%

common/util.go
2
52.61%

common/persistence/statsComputer.go
3
94.64%

common/persistence/serialization/parser.go
4
63.91%

common/persistence/serialization/thrift_decoder.go
4
57.14%

service/history/task/fetcher.go
4
91.24%

common/task/fifoTaskScheduler.go
5
82.47%

common/persistence/sql/workflowStateMaps.go
12
82.97%

Totals

Change from base Build 0187ed01-61d1-4c58-8372-cd5009e3cb51:
0.01%

Covered Lines:
85754

Relevant Lines:
149881

💛  - Coveralls


Changed to vertical scroll and added Park&Ride

Description
Modified to vertical scroll and added logo
Copilot

copilot:all

Thanks for the PR. There are some conflicts here that need to be resolved before merging. Could you rebase the PR? Alternatively, create a new fork of the community repo, reapply the changes there and cut a new PR?

I have read the CLA Document and I hereby sign the CLA

recheck

How to fix this:
git checkout 69c720291f50522cb2f70ecbdfec01593f442513 #  after your first few commits - you'll end up in headless mode
git checkout -b park-and-ride  # switch to a branch
git cherry-pick cd0f88b63d30b949b6ee046018fc3324e14b5e2a  # add the commits that you did later
git cherry-pick 22fb49dab7199d7254fefb1b62be95e2a53196d6
git cherry-pick 647ceff2abecd87b0296dcc12fb40d0965f8e512
git push origin park-and-ride  # push that new branch to your forked repo

Then either recreate a new PR from derekllaw:park-and-ride or fix main somehow (this is slightly sketch, but something like this should work: git branch -D main, git checkout main [should pull from origin], git merge park-and-ride)


Remove mutable_args restriction in get_model API

I think we can remove the check of mutable_args in the get_model API for BERT, GPT, Language model and transformer. We can introduce a separate flag "allow_override" if users want to override any configuration. Otherwise overriding any configuration is forbidden.

Hi @eric-haibin-lin, can I take this issue?

Contribution is welcome!

Hey @eric-haibin-lin,
just to clarify:
currently the mutable_args of the BERT model for example are ['use_residual', 'dropout', 'embed_dropout', 'word_embed']. Non mutable arguments of the bert_12_768_12 model are for example 'hidden_size', 'num_heads' or 'num_layers' (from looking at bert_12_768_12_hparams in model/bert.py). The goal of this fix is to allow calling nlp.model.get_model for example as follows:
nlp.model.get_model('bert_12_768_12', dataset_name='book_corpus_wiki_en_uncased', use_classifier=False, use_decoder=False, allow_override=True, num_heads=13);
So instead of allowing the user to modify only the parameters in mutable_args, we allow the user to modify any parameter in bert_12_768_12_hparams as long as he passes in the parameter use allow_override=True. Is this correct?

yes

@eric-haibin-lin I created a PR for this: https://github.com/dmlc/gluon-nlp/pull/1207
I asked a question in that PR. Also found the Jenkins test to be failing for what seems to be unrelated to the codebase. Would appreciate any feedback to get started with this codebase. Thanks!


SNOW-709591: function get should accept integers

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #636

Fill out the following pre-review checklist:

[x] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Please write a short description of how your code change solves the related issue.

Codecov Report

Merging #671 (36a1a36) into main (9c95990) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #671   +/-   ##
=======================================
  Coverage   98.71%   98.71%
=======================================
  Files          49       49
  Lines        7959     7959
  Branches     1347     1347
=======================================
  Hits         7857     7857
  Misses         40       40
  Partials       62       62

Impacted Files
Coverage Δ

src/snowflake/snowpark/functions.py
99.57% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


@reach/rect error

Hello!
Within the past week, when redeploying our HULL-adapted project with Vercel we encountered this error:
Could not resolve dependency: npm ERR! peer<EMAIL_ADDRESS>|| 17.x" from<EMAIL_ADDRESS>I checked your base files and they are the same<EMAIL_ADDRESS>/<EMAIL_ADDRESS>It's odd as previously worked fine. For now we have just applied the overide in the package,  but good to know if anyone else is experiencing this or has used a different package.

Seems like something has degraded with this package, and unfortunately, it's no longer maintained.
I've switched to using @wellyshen's package for measuring refs: https://github.com/wellyshen/react-cool-dimensions
It's a quality package that is suited to replace most instances of @reach/rect 🤘
Hopefully that helps! And as a friendly reminder– I'm working on a new version of HULL (largely a rewrite), and as a result not actively updating the current version unfortunately. Stay tuned!

Overwritting the npm install to yarn install did the build for me


Index "is native"

Problem or new feature
It's not indexed, although it's described in the NativeCall tutorial
Suggestions
Index it, and maybe provide its own independent page.

Provide, if possible, several paths in, like indexing it as a trait.


[Question/Feedback]: Azure Advisor Alerts/Digests

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description
Any plans to include Azure Advisor Alerts and Digests?

@birdnathan could you elaborate on what you are looking for here? Are you looking for a Policy to achieve this?

We've had this ask previously and the Advisor team needs to create a policy alias to allow us to create a policy to do this but to date this request has not received funding so we aren't able to achieve this via policy, looping in @JoeyBarnes for comment on alternative options.

Assigning it to @JoeyBarnes for the proper visibility and action if required.


bitc.py timecode error fix

Original code: timecode_option = "drawtext=...:timecode=%s:...
Error found:
[Parsed_drawtext_0 @<PHONE_NUMBER>e9b480] Unable to parse timecode, syntax: hh:mm:ss[:;.]ff
[AVFilterGraph @<PHONE_NUMBER>553a40] Error initializing filter 'drawtext' with args 'fontfile=C\:\\Windows\\Fonts\\arial.ttf:fontcolor=white:fontsize=20.0:timecode=01:00:00:00:rate=15/1:boxcolor=0x000000AA:box=1:x=(w-text_w)/2:y=h/1.2'
Error reinitializing filters!
Failed to inject frame into filter network: Invalid data found when processing input
Error while processing the decoded data for stream #0:0

Solution - add quotes for timecode value: timecode_option = "drawtext=...:timecode='%s':...
ref commit 621ae4a

Error found: #75 'bitc broken on mac?'
Solution - move quotes to timecode_test for win32
elif sys.platform == "win32":
            timecode_test = '\'01\:00\:00\:00\''
......
if not timecode_test_raw
            timecode_option = "drawtext=...:timecode=%s:...

While for timecode_test_raw section, I ran the cmd of ffprobe but find nothing returned. So I didn't touch that part.

This has been tested on
Mac OS Sonoma 14.0
Windows 11
Windows 10
all with ffmpeg 6.0

This is Courier
https://github.com/Irish-Film-Institute/IFIscripts/assets/1127102/031a338f-00b8-4b0b-9eae-ae973ee64509
vs the font in the current PR
https://github.com/Irish-Film-Institute/IFIscripts/assets/1127102/8d9d2eb7-1fdd-461a-8e22-6f687dedb584

Thanks - I found this but I didn't think as a problem! Also have checked font files in dir /System/Library/Fonts/ for several versions Mac OS, and looks like Courier.dfont can stand out among the rest (though it doesn't show digits in the preview).

New font looks great, thanks for the fix!


Fix type instabilities

This fixes a whole number of perf problems on Julia 1.7 and 1.8.

@davidanthoff this all looks good to me. I’d like to just rerun the test notebooks that don’t run automatically with CI to be completely sure, then I’ll approve. Will be fine first thing Monday.


Support repository-wide guardrails

Make it possible to associate functions with package repositories so that they are automatically evaluated on packages in the repository every time those changes.

We could dedupe this with #3279


Update golang version

golang version up to 1.5
Working on my project, I'd be glad to see the version bump on the main repo!
Great container, thank you !

didnt see the previous PR, closing this one then !


Ambassador documentation paths broken

Getting started document suggests that users to use existing docker images defined by yaml files to created kubenetecs pods. Yet, building ambassor image will be stoped when version checking returned nothing.
However, the commands or resources in document do not work:
Wangs-MacBook-Pro:ambassador wangyi$ kubectl apply -f https://raw.githubusercontent.com/datawire/ambassador/master/demo-qotm.yaml
error: unable to read URL "https://raw.githubusercontent.com/datawire/ambassador/master/demo-qotm.yaml", server reported 404 Not Found, status code=404
Wangs-MacBook-Pro:ambassador wangyi$ kubectl apply -f https://raw.githubusercontent.com/datawire/ambassador/master/ambassador-http.yaml
error: unable to read URL "https://raw.githubusercontent.com/datawire/ambassador/master/ambassador-http.yaml", server reported 404 Not Found, status code=404
Wangs-MacBook-Pro:ambassador wangyi$ kubectl apply -f https://raw.githubusercontent.com/datawire/ambassador/master/ambassador.yaml
error: unable to read URL "https://raw.githubusercontent.com/datawire/ambassador/master/ambassador.yaml", server reported 404 Not Found, status code=404
Wangs-MacBook-Pro:ambassador wangyi$

For me, source codes are more verbose compared to concepts. So how should I use Ambassor instead traditional sds coding. What Ambassor really abstract for users?

Fixed, I think, with 84884c066babb0e3adc41bef7a37231a95be54d0

Thanks to @kflynn. The problem fixed! Cheers!

By reading the makefile, the compilation procedure is:

first check the version difference by calling "python scripts/versioner.py --verbose". Logics in versioner implements version calc by reading the repository as a git repo object. In "next_version" if there is no commit, a none returned by ReleaseDelta on behalf of VersionedRepo.
then check docker repository name to build docker images.
docker images building implements in "docker_build_maybe_push":
Proposed logics: if no commits, nothing happens. But if user uses his own repository, nothing hurts when user build his own images.

If triggered by circumventing version checking scripts

make versions
I got

Wangs-MacBook-Pro:ambassador wangyi$ make versions
no changes since 0.10.7
no changes since 0.10.7
Building
for file in actl ambassador; do \
	    sed -e "s/{{VERSION}}//g" < VERSION-template.py > $file/VERSION.py; \
	done

This

sed -e "s/{{VERSION}}//g" < VERSION-template.py > $file/VERSION.py;
, followed by

 docker build -q -t "${DOCKER_REGISTRY}${NAME}:${VERSION}" "${TARGET}"

which takes long time to build.
the version replacement makes no sense to me.

Besides:
1)
kubectl apply -f http://www.getambassador.io/yaml/ambassador/ambassador.yaml
error: unable to read URL "http://www.getambassador.io/yaml/ambassador/ambassador.yaml", server reported 404 Not Found, status code=404

info in other webpages has not been updated yet.
https://www.datawire.io/guide/traffic/envoy-as-api-gateway/

Reopening since @yiakwy is still having trouble.

Build issues moved to #86.


Bad error messaging when opening multiple existentials

Describe the bug
The following code is invalid because the two opened existentials may have different types, but the error message does not explain that well:
func equals(_ lhs: Any, _ rhs: Any) -> Bool? {
  func open<A: Equatable>(_ lhs: A, _ rhs: A) -> Bool {
    lhs == rhs
  }

  guard
    let lhs = lhs as? any Equatable,
    let rhs = rhs as? any Equatable
  else { return nil }

  return open(lhs, rhs)
}

🛑 Type 'any Equatable' cannot conform to 'Equatable'

Expected behavior
A better error message that lets the user know it's not possible to open multiple existentials.
Environment

OS: 12.4 (21F79)
Xcode Version/Tag/Branch: Version 14.0 beta 2 (14A5229c)

Great idea for a tailored error message, thanks!


Missing trips

There seem to be trips missing from the new map overlay. Here is what one of our beta testers reported:

Hi Martin I've noticed you updated the website, but there are a lot of tracks missing(and yes I cleared my cache), I've waited a long time and they still dont show up. Is this because you are reprocessing the files that have been processed to match them to the roads as you said in the beta news letter?
Example what's highlighted in yellow should have imagery(from what I recall and a quick pass over) :

I am seeing this same thing (user: tekim).  I uploaded a sequence nearly 24 hours ago and it is not showing up.

Also sometimes they do appear but only partially, see highlighted areas

Same for me, in my case this track http://openstreetview.org/details/10400/1

There's also roads that say I've passed on like this track: http://openstreetview.com/details/8745

The road surrounded in red is a place I did not pass, but the website says I did (and I doubt any other people drove there)

I think the missing trips were the result of initial catching up that the production server needed to do. Closing this now but feel free to file a new bug or add your experience to #35 or #36


Better handling of Cloud SDK version parse error

fixes #2259
Will wait to merge until appengine-plugins-core is released with this change: https://github.com/GoogleCloudPlatform/appengine-plugins-core/pull/709
Details:
https://github.com/GoogleCloudPlatform/appengine-plugins-core/pull/709 updated the generic Cloud SDK validation logic to not throw an exception on version parsing errors.
This PR updates the SDK plugin-side validation by doing the following:

Adds a new Cloud SDK notification when there is an error parsing the version file. It does this by calling CloudSdk#getVersion instead (which will still throw an exception). The notification looks like this:

Note: This will not block the operation (like deployment): once the core lib PR is merged, deployment will continue and succeed if the Cloud SDK installation has no other problems
Catches the CloudSdkOutOfDateException during deployment: previously when the SDK was out of date, the notification would be shown and then an IDE error would occur (because the core library throws an exception downstream when the minimum version is not met). Now the behavior is that the warning will be shown, but the IDE won't blow up.

TODO:

Consider doing an analytics ping when there is a version parsing error (since now we would have no other way to be notified)

:+1:

I added a ping when there is an SDK read error. I want to have the actual version in the ping - I'm trying to figure out the best way to do this now.

I want to include the exception message contents together with the sdk version analytics ping:
i.e. java.lang.IllegalArgumentException: Pattern "<IP_ADDRESS>.1" is not a valid CloudSdkVersion.
wdyt about updating CloudSdkValidation result so that it can also hold an exception message? Something like:
class CloudSdkValidationResult {
  private final ValidationMessage validationMessage;
  private final String exceptionMessage;

  ...

  public enum ValidationMessage {
   // same enum as before, but now an inner enum
  }
}

hmm on second thought that could get kinda messy. thinking of a better approach

I agree, could be a bit messy to carry around dynamically changing message inside of an enum?

well it wouldnt be inside of the enum as I described there. the enum would just be part of CloudSdkValidationResult (and so would the exception message).

I think maybe the best approach is in notifyIfVersionParseError instead of using SdkValidator and getting back a CloudSdkValidationResult to just call CloudSdk#getVersion directly. Then I can catch the exception there and do whatever I want with the exception message.

eh. but then I have to build the CloudSdk again manually... theres a better way here somewhere, I can feel it..

Good option and easier to understand probably.

@ivanporty ptal at the last commit. I updated the analytics ping to send the exception message as well (so we can see the version number that cause the error, for example).

Last update LGTM, thanks

Updated the notification wording:

We continue the operation even if the version could not be parsed so I softened the wording (got rid of "error").


[Feature Request] Send random numbers to REST interface

Just found that awesome REST client and testing my most recent "project" with that. As my backend has some database restraints, the option with the current timestamp is awesome. I'm pushing time-tagged values to an endpoint, and the database has a UNIQUE key on the timestamp, as I only want to have one value per second.
Now, it's a bit annoying that I've got dozens of numbers in my database with all the same value, just being different on the last place of the timestamp. It would be awesome for testing purposes if I could simulate real measured values, so I wanna throw this one as a feature request into the ring :)
Easiest way should be a placeholder like [DIGIT] where there's a number 0..9, so I could just do [D][D][D][D] (should cover most use cases), the more complicated one with values (like "between 5 and 13"), but for this I cannot come up with a real case right now :)

@e7o-de This already exists, you just need to install the insomnia-plugin-randomnumber plugin. You can then use a random number both in the URL and the request body

Awesome, thx. Now I'll figure out what "Yarn error /snap/insomnia/30/insomnia: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory" means (guess I'll drop that stupid snap thing and switch to the repo) :)


Painting 3D models in Blender

In order to make the 3D models more attractive, we need to "dress" them, adding materials to the model.We can do it creating a texture paint for the 3D models (a 2D image painted into Blender, or other painting tool like GIMP or Krita, using UV coordinates that will cover the 3D model).

The way to do it in Blender is:

Create the 3D model
Create the 2D UV mapping (unwrapping 3D to a 2D image) using the Smart UV Project option and its default values
Add a texture to the 3D model of Image type (this image will be the image including the UV model)
Paint in this image using the Texture Paint view
Create a new material for the 3D models, use the UV image created as the Base color image

When painting you can use the symmetric tool to paint at the same time both sides (x mirror) or/and front/back (y mirror). And it is really funny to paint model using this approach.
And it is pretty quick to add a new Texture Image Layer to start experimenting from scratch without loosing your current texture paint. So funny to play with and it will be pretty useful for the workshop!

Let's review this process because it is not so intuitive.
We have two views in Blender involved in painting and texturing 3d models:

UV Editing
Texture Paint

And also related to it is Shading, but this is for adding materials in a more advanced way.
Painting a 3d model us just adding a material (basically the texture for it) where we can paint. But let's explore the process

The simplest way to start painting a 3D model is:

Create the model
Go to Texture painting
Add a new texture Base Color
Press in "+ Add Simple UVs"
The 3D model will appear as black and you can start painting


Login Error 401 / Authorization error

I use the Adapter version 2.2.0
Since a time I get an Login Error.
The same problem is here descriped an resolved.
https://github.com/Hacksore/bluelinky/issues/199
Please check and update the ioBroker adapter.

please check next release, i update the bluelinky lib


Query: groupjoin projecting and composing on grouping (not flattening) doesn't get translated

Example:
from l1 in ctx.LevelOne
join l2 in ctx.LevelTwo.Where(x => x.OneToOne_Optional_FK2.Name != "Foo") on l1.Id equals l2.Level1_Optional_Id into grouping
from l2 in grouping.DefaultIfEmpty()
select new { l1, l2, grouping };

Note from triage: @smitpatel to write down an explanation of why we don't support this.

Since a "group" (coming out of GroupJoin or GroupBy) cannot be represented in SQL. Above query has to do client eval after GroupJoin (which has SelectMany with DefaultIfEmpty). As we don't support client eval going forward, above query cannot be translated to server fully. We will throw exception. Using AsEnumerable will allow the query to generate groupings in EF and then do rest of processing on client side outside of EF.


CarrierService callback and auth.shopify middleware don't play together

Expected Behavior
When Shopify calls my callback, the middleware should fill in with the correct shop for the user.
Current Behavior
Right now it fails with MissingShopDomainException.
Failure Information
The information is in the header, but auth.shopify does not look at the correct header information.
The headers Shopify sends looks like this for me (in the callback):
array (   'host' =>    array (     0 => 'my-app-server.com',   ),   'user-agent' =>    array (     0 => 'Ruby',   ),   'content-length' =>    array (     0 => '766',   ),   'accept' =>    array (     0 => '*/*',   ),   'accept-encoding' =>    array (     0 => 'gzip;q=1.0,deflate;q=0.6,identity;q=0.3',   ),   'content-type' =>    array (     0 => 'application/json',   ),   'x-forwarded-for' =>    array (     0 => '**.***.***.*',   ),   'x-forwarded-proto' =>    array (     0 => 'https',   ),   'x-shopify-hmac-sha256' =>    array (     0 => 'hmac-key',   ),   'x-shopify-shop-domain' =>    array (     0 => 'my-dev-store.myshopify.com',   ),   'x-shopify-timeout' =>    array (     0 => '10000',   ), )
But in the code in 'auth.shopify' it looks for this:
$shop = $request->header('X-Shop-Domain');
Basically all the header lookups in auth.shopify are wrong here? Does it differ when shopify uses the callback?
This callback is for the CarrierService rest-api which fetches the shipping rates I have available.
I tried the JWT auth.token middleware but I'm not sure I understand it correctly. Either way shopify doesn't seem to send me any token for it to work. I assume I might need to get JWT to work to also get my app to work later on? I have allowed shopify cookies in my browser so I can work on it with the auth.shopify middleware.
Not sure JWT works in this scenario either?
The app uses the TALL-stack (Tailwindcss, Alpine.js, Laravel, Livewire) so I don't really have any frontend javascript framework, it's all backend.
Steps to Reproduce

Setup CarrierService and point to an API-endpoint of your choice under routes/api.php
Set 'auth.shopify' as middleware for the API-endpoint in your app.
Try to load the checkout in your dev store. You won't get any results from your callback since it fails as described here.

Context

Package Version: v15.0.0
Laravel Version: v8.16.1
PHP Version: 7.4.12
Using a toolset (Docker, Laradock, Vagrant, etc.): just 'artisan serve' and ngrok

Failure Logs
Nothing more than the exception because it misses the piece in the header which actually contains it.
edit: Updated version to v15.0.0 which released yesterday. Still the same issue though. And updated laravel version.

Logic tells me auth.* should not be used for callbacks. So I've removed it and am manually fetching the correct header for the shopify domain. Then I use the ShopSession to have the correct shop logged in so I can fetch right data.
Is this the proper way to do it? What about all other callbacks from Shopify to my app?

You wouldn't use middleware for the carrier service or anything frontend facing for API. Get the shop info from headers, and do what you need this way.


Rust: Finish Lane to OSM Tags

Next up: upgrade the web version with this.

I fixed up the merge conflicts here: https://github.com/a-b-street/osm2lanes/tree/rust_lanes_to_tags_v2
But didn't want to force push here and clobber everything. Does this merge look correct to you?

I fixed up the merge conflicts here: https://github.com/a-b-street/osm2lanes/tree/rust_lanes_to_tags_v2 But didn't want to force push here and clobber everything. Does this merge look correct to you?

https://github.com/a-b-street/osm2lanes/commit/09b9be63cd9263180ec0260be3db07923ace5c40
That looks good :), clobber away

Ah, the diff in tests.json is weird; fields reordered and typos reintroduced.. Also, some tests fail now. :(
I can take a look later night, or handover to you if you don't mind

(But the web deployment looks better with this; the normalized tags are way improved for the starter example)


chore: improve test names in qf/assignment_test.go

In qf/assignment_test.go we use test naming like this:
name:       "Assignment:ScoreLimit=90:AutoApprove:IsGroupLab,Submission:UserId=15:Status=NONE:OldScore=0,NewScore:95",

We should replace this naming style with the Go test convention to use / instead of :. We could possibly use the new qtest.Name() function. This convention is also used by certain tools, so it could be helpful in the future, even if there is no immediate need to do this.
I'm sure there are other places where we do not follow this convention, and we should fix those too, but let's create a separate issue for that, or expand on this issue with additional details if we decide to do it across the codebase in one PR.

Already fixed in #1143


Upgrade all packages

Same as: https://github.com/iterative/dvc.org/pull/4241#issuecomment-1396827563


Minor UI updates

Tested it out locally, the pieces for the URL-based query params are sometimes a little funky, but I think I got all the edge cases.


Recommendation to add all Data Collection Stages to 'Enrollments' endpoints

Enrollments: To match the HUD Data Dictionary, the Update/Occurrence Point, Annual Assessment and Post-Exit data collection stages should be added for get/post/put.

Thanks @DavidTweedieWellSky. This is a part of a larger conversation that we're anticipating facilitating regarding data validation. If there are any outstanding concerns after that conversation, please feel free to flag here.


Native select: Write guidelines for usage

Status 21. March: Not yet documented - waiting for reply from @mrosvik  to question in Slack

File shared with @Febakke who will check and co-author this description.


TextInput keyboard getting dismissed automatically

Description
When a TextInput is wrapped with a View, and the View is given conditional styles based on the focus state of the TextInput, the keyboard gets dismissed as soon as it is tapped to gain focus. So, as soon as onFocus is called, onBlur is triggered automatically. Note that this is not happening for all style keys, but I have encountered it only for "elevation" and "shadowColor" properties till now.
The issue is only happening when new architecture is enabled on both android and ios.
Steps to reproduce
Here is a minimum reproducible example for the issue: https://github.com/1880akshay/RN_NewArch_TextInput
React Native Version
0.74.3
Affected Platforms
Runtime - Android, Runtime - iOS
Areas
Fabric - The New Renderer
Output of npx react-native info
System:
  OS: macOS 13.6.7
  CPU: (10) arm64 Apple M1 Max
  Memory: 204.98 MB / 64.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.19.0
    path: ~/.nvm/versions/node/v18.19.0/bin/node
  Yarn:
    version: 1.22.21
    path: ~/.nvm/versions/node/v18.19.0/bin/yarn
  npm:
    version: 10.2.3
    path: ~/.nvm/versions/node/v18.19.0/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - visionOS 1.0
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10406996
  Xcode:
    version: 15.2/15C500b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 3.3.0
    path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: true

Stacktrace or Logs
-

Reproducer
https://github.com/1880akshay/RN_NewArch_TextInput
Screenshots and Videos
https://github.com/user-attachments/assets/7a70be20-4d74-4da1-9b07-aae8472f0a60

Hey, I can check this out.

The issue is that after clicking on TextInput one of the styles, that is added to the container, prevents flattening which causes adding remove and insert mutation on TextInput in differentiator. On the remove mutation, the TextInput loses focus, so the onBlur is triggered immediately after that. This will also happen on other styles, for instance setting opacity < 1, transform or any other style that would add FormsStackingContext trait on this view, which are defined here. It won't update areChildrenFlattened in differentiator to true, so the recursion will stop and the TextInput won't be added here to the list. It will cause differences in returned trees and it will generate above-mentioned mutations.
For the quick fix, you can add collapsable={false} to the View component:
<View collapsable={false} style={[styles.shadowBox, focus && styles.shadowBoxFocused]}>
  <TextInput
      placeholder="Text"
      style={{height: 60, width: 300, borderColor: 'black', borderWidth: 1}}
      onFocus={() => setFocus(true)}
      onBlur={() => setFocus(false)}
   />
</View>

The problem is that we cannot perform remove and insert mutations on something that needs to hold focus. I am not sure if searching for a solution that will work only for TextInput is a good idea. Is it good enough solution for now or should I proceed with something that will work in a broader scope?

@coado thanks for the prompt replies. I'll test this out (collapsable=false) and let you know if it works.
Meanwhile, I am curious as to why this worked in old architecture and the issue is only happening with new architecture?

The issue seems to be related to view flattening which was introduced in the new architecture. You can read more about it here

Thanks for the clarification @coado . Also, collapsable = false fix is working fine! I also wanted to know, that collapsable property exists on android even in old architecture and it did flatten the view hierarchies, I wonder how it used to work earlier.

As far as I know, the previous flattening was way simplified and worked only on Android like you said. Unfortunately, I am not too educated how it worked on the old arch and docs are also not too comprehensive about that 😕


Remove 'SFML_DEPRECATED' and replace internal usages with '[[deprecated]]'

Description
This PR removed SFML_DEPRECATED and changes all its internal usages to the C++14 standard [[deprecated]] attribute. This is technically an API-breaking changes as SFML_DEPRECATED was externally exposed, however:

I've gone through around 50 pages of GitHub search results for SFML_DEPRECATED, and all of them were SFML/Config.hpp being copy-pasted into some project's repository.

If someone upgrades their project to use SFML 3.x, that implies that they have access to C++17. Therefore, all they have to do is literally a find-replace s/SFML_DEPRECATED/[[deprecated]]/g, which I think is a very reasonable amount of work for a breaking change.

Tasks

[ ] Tested on Linux
[x] Tested on Windows
[ ] Tested on macOS
[ ] Tested on iOS
[ ] Tested on Android

How to test this PR?
CI is enough.

SFMLBuildMaster: Build this please.

SFMLBuildMaster: Build this please.


Clean up sprites

This removes excess comments, multiple doctype declarations and  tags from sprites before creating the spritesheet.
I know this is an old repo but it works perfect with this update.
Hopefully I'm doing it right, this is my first pull request.

Do tests pass? Also, can we add new tests to cover these?


Please consider incorporating SCReAM algorithm

On a brief look at your codebase, it seems you might benefit from incorporating the SCReAM algorithm.
its main implementation is as a C++ library, that you might link against - rather than forking, where you might miss future tuning of the algorithm: https://github.com/EricssonResearch/scream.

thanks for the info, we'll consider it in the future.


Python: Allow runtime scope to apply to "private" functions.

Fixes the regression documented in #3300.
As we are currently applying this scope to all non-"private" functions, I don't expect this to have a major impact on the accuracy of our analysis (apart from the obvious fact that we won't be ignoring all of the "private" functions!).
Still, we should run a performance test just to make sure.

In terms of performance, there's not much to worry about here. In terms of results, however, I'm not filled with confidence at the changes I'm seeing: https://git.semmle.com/gist/taus/6d02238df99db4b4cbf81ecdc909d723 :disappointed:

I agree. It's not a clear improvement :thinking:

:+1: for saying that we should be using with here

:-1: for thinking that snapshot_id may be used before it is initialized, when is always set when is_shelved is true.

Closing this for now, as I don't think it's likely to be relevant in the near future.


Support x-ms-header-collection in requests & responses

Spec: https://github.com/azure/autorest/tree/master/docs/extensions#x-ms-header-collection-prefix

It looks like only request support was added. Could we also get response support added please?

It looks like only request support was added. Could we also get response support added please?


nixos-anywhere: update owner to nix-community

Reflect the repo being moved to nix-community/nixos-anywhere
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

cc @Mic92 @Lassulus @phaer @zimbatm

Add a :+1: reaction to pull requests you find important.

Seems nothing blocking this from release-24.05

@NixOS/nixpkgs-merge-bot merge


purchaseUpdatedStream offline crashing app exception

Steps to Reproduce

Listen to purchaseUpdatedStream stream in code while app is building up.
Try to build app offline
even if the purchaseUpdatedStream.listen() has an onError block, the app crashes with an exception.

Logs

Building in release then returning to debug mode fixed it! 🤷🏻♂


t2 restore bricks tessel

Summary: After rebooting from  t2 restore, the tessel will have a steady green led and fading in/out blue led. t2 list will not detect the board but you CAN still run t2 restore (still reboots to bricked state)
Workaround: reflash to firmware 0.0.12 using flash.py followed by t2 update

Using OS X 10.10.5 and node v4.4.3
t2 restore

INFO Looking for your Tessel...
INFO Connected to your Tessel.
INFO Downloading files. This may take a few minutes...
Downloading [====================] 100% 0.0s remaining
INFO Download complete!
INFO Restoring your Tessel...
INFO Bulk Erasing Flash Memory...
INFO Writing U-Boot...
INFO Writing MediaTek factory partition...
INFO Writing OpenWRT SquashFS (this may take a few minutes)...
INFO Restore successful. Please reboot your Tessel

t2 list --usb --loglevel=debug

INFO Searching for nearby Tessels...
DEBUG (discovery) Will scan for USB devices
DEBUG (discovery:usb) Device found.
DEBUG (discovery) Error opening device. Error: LIBUSB_ERROR_PIPE
WARN Detected a Tessel that may be booting.
DEBUG (discovery) Timeout hit! Waiting for pending to finish
DEBUG (discovery) Done! Stopping.
WARN No Tessels Found.

Used workaround to restore tessel to operational state
Repeated t2 restore on Linux machine (node v4.5.0)
Tessel rebooted to bricked state
t2 list --usb --loglevel=debug

INFO Searching for nearby Tessels...
DEBUG (discovery) Will scan for LAN devices
DEBUG (discovery) Will scan for USB devices
DEBUG (discovery:usb) Device found.
DEBUG (discovery) Connection opened: undefined
DEBUG (discovery) Fetching name: undefined
DEBUG (commands:usb<EMAIL_ADDRESS>DEBUG (usb-process) Opening process for<EMAIL_ADDRESS>ERR! Detected CLI crash { [Error: LIBUSB_TRANSFER_ERROR] errno: 1 } Error: LIBUSB_TRANSFER_ERROR
ERR!     at Error (native)
INFO Crash Reported: http://crash-reporter.tessel.io/crashes?fingerprint=0x1032aff9
DEBUG (discovery) Timeout hit! Waiting for pending to finish

Checking out cbd6b3fc85395b729a1641fd3eea848d56b3d1e9 also fixes issue

This issue has been fixed in the release of v0.0.26.


Initial implementation for the JIRA's comment

Man, take a look, we still have some fixes to do, but it is a start :v:

Why did you close this issue without opening a Merge Request? LOLLLLLLLLLLLLLL


add dokuwiki

What this PR does / why we need it:
Add DokuWiki, an Open Source wiki that doesn't require a database
Any other useful info:
Simple to use. Allows edits of content files directly. Used as a personal wiki for notes.

Testing the PR in my fork. Closing. Will update my master from the original.


Update port-manager extension

Description

Improved menu bar commands
Removed the preference to use sudo for listing and killing processes
Added the "named ports" feature (special thanks to @Sheraff)
Made command names more concise

Screencast
https://github.com/raycast/extensions/assets/45899273/bc6c5a7e-4af1-431f-ad60-4c8d43132fcc

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

It seems like there is something with the isLoading prop in the menubar command, for some reason I can't debug it at the moment, can you take a stab? It's like its not unloading correctly @lucaschultz

@lucaschultz @pernielsentikaer Should I try and take a stab at it? I don't think I'll be able to commit to the repo but maybe I can find the issue and we can finally merge this?

@lucaschultz @pernielsentikaer Should I try and take a stab at it? I don't think I'll be able to commit to the repo but maybe I can find the issue and we can finally merge this?

@Sheraff, sorry, I'm a bit short on time at the moment. Thank you for your patience and for keeping the issue alive.

It seems like there is something with the isLoading prop in the menubar command, for some reason I can't debug it at the moment, can you take a stab? It's like its not unloading correctly @lucaschultz

@pernielsentikaer, I used to use a hack (1-second timeout) to give the processes enough time to load. This might have created a race condition. I refactored the process retrieval to use the useCachedPromise hook and am now utilizing the isLoading property of the hook. Does this solve the problem?

Much better 🙂

Is the prettier check preventing a release? It doesn't seem to have been updated in the store and there wasn't a slack notification

@pernielsentikaer can we do anything to get this released to the store?

@pernielsentikaer can we do anything to get this released to the store?

It actually got released today at some point.

I manually ran it @Sheraff 🙂


⚠ Bofrost.si has degraded performance

In 078d2f7, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 1628 ms

Resolved: Bofrost.si performance has improved in 87598bd after 1 day, 7 minutes.


Staging Deployment: retry rsync

Coverage remained the same at 86.953% when pulling 9de14263e9e2901b4b4857a7f66eed0401034a2f on staging-deploy-retry-rsync into afe3c82a1abadbcf837ada1f712f743f594ff5b1 on main.


Configure ORM for fantasy-f1-service #6

Connected the fantasy-f1-service to the infra database and configured the physical naming strategy. (issue #6)
Refactored generated ExampleResource
Added Quarkus Main
Added jax-rs Application for OpenApi definition

resolve #6


Fixed dh issue by modifying get_bbox()

pyCSEP Pull Request Checklist
Please check out the contributing guidelines for some tips
on making pull requests to pyCSEP.
Fixes issue #(please fill in or delete if not needed).
Type of change:
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (this pull request adds no new code)
[ ] Unpublished science feature (This may require a science review)
[ ] This change requires a documentation update

Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Codecov Report

:exclamation: No coverage uploaded for pull request base (v0.6.0-rc@962dd6a). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             v0.6.0-rc     #175   +/-   ##
============================================
  Coverage             ?   54.96%
============================================
  Files                ?       20
  Lines                ?     3495
  Branches             ?      552
============================================
  Hits                 ?     1921
  Misses               ?     1453
  Partials             ?      121

Continue to review full report at Codecov.

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

@khawajasim looks good! i made a couple comments about some comments. other than that it looks good to go! this pr fixes #166

Thanks for the merge. When is it going into the master branch now?
I would like to add a few more functions in the coming days, mainly related to forecast mapping from one grid to another. Although, those functions will not be part of the QuadtreeGrid2D class. But generally part of region.m file. I want to see this through first and then add further.
Cheers,


storage: Support a storage emulator

It would be very useful to have a storage emulator for testing Go projects without needing to use a real storage server.

Hello Cole :D Actually I added this some weeks ago :D
You should be able to use Azure Storage Emulator with some lines like this ones...
client, err := storage.NewBasicClient(storage.StorageEmulatorAccountName, storage.StorageEmulatorAccountKey)


X-Forwarded-For behaviour is not configurable.

Right now the this layer automatically parses X-Forwarded-For and takes the leftmost value in there... or takes the TCP connection address if no header is present. This means that anyone can spoof client IP addresses by adding a X-Forwarded-For header.
It should be possible to disable looking at X-Forwarded-For, or to take the rightmost value from X-Forwarded-For instead (the one added by the latest load balancer...). For discussion on these things... see: https://crates.io/crates/axum-client-ip

Thanks for the information and the link. PR is welcome (I'll not have too much time to work on this crate before some days)

Comment (to myself for memory):
From https://github.com/open-telemetry/semantic-conventions/blob/main/semantic_conventions/trace/http.yaml

The IP address of the original client behind all proxies, if
known (e.g. from Forwarded,
X-Forwarded-For, or a similar header).
Otherwise, the immediate client peer address.

Notes: this attribute was removed with release 0.12 (but it come back with future release, if I don't forgot)


Fix 808 frontend fixes

improves the error page layout and error messaging (including a corgi) on non reaching backend and 404 pages.


fix(checkbox): 修复checkbox label为0时不显示bug

PR
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our Commit Message Guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@all-contributors please add @gimmyhehe for code


can this be composed with gitignore based filter?

I'd like to have an explicit whitelist specified with nix-filter combined with a blacklist based on .gitignore. Can I compose nix-filter somehow with, for example: https://github.com/hercules-ci/gitignore.nix? Thanks!

Bump

It would take a few days of work to properly assess and come up with a composable design. It's not something I planned to address, unless it comes up as a need in our consulting work.

I recently developed a safer and easier-to-use abstraction for source filtering in a PR to Nixpkgs, please take a look, try it out, and give feedback! https://discourse.nixos.org/t/easy-source-filtering-with-file-sets/29117
Along with basic combinators allowing you to add/remove files, it also comes with a lib.fileset.fromSource function, which can turn lib.source-based values, such as pkgs.nix-gitignore or gitignore.nix into a value that can be composed easily, like this:
let
  fs = lib.fileset;
in
# Remove all `./tests` files from non-gitignored files
fs.difference
  (fs.fromSource (gitignoreSource ./.))
  ./tests

This fixes the problem in this issue!


[Bug] [Master] TaskInstance set TimeoutFailed will not be killed when timeout

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
When we set the timeout flag to TimeoutFailed, the taskInstance will go to failed after timeout, but it will still running at worker side.
What you expected to happen
The TaskInstance will be killed when timeout.
How to reproduce
x x
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Closed by already solved.


DO NOT MERGE! Fast Forward stable to c6403ea8304df2f25525855cb302903795bdc51b.

This PR will be merged automatically once checks are successful.

Jenkins job manager/postsubmit passed

Jenkins job manager/e2e-suite passed


Memeory leak

Microsoft PowerToys version
0.56.2
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce
Running the application
✔ Expected Behavior
Normal memory and cpu usage
❌ Actual Behavior
Using 96% of memory and 35% of cpu running in background.
Other Software
Running without other apps

Could you tell us which module is causing this on your computer? You can just simply post a screenshot of Task Manager. /needinfo

I’ve got a screenshot below, however since unchecking ‘run at startup’ and rebooting then restarting powertoys, the issue has not returned and I cannot replicate it again. Hopefully it won't return.

Seems like #17173
cc: @jaimecbernardo
/bugreport

PowerToysReport_2022-03-28-12-17-01.zip

As an update, I have not encountered this issue since


Add issue template for nightly build

Overview
Closes #3284 .
There was no action needed to resolve #3284, except for verifying that these things did indeed happen. I'm adding an issue template so we can handle these more smoothly in the future!
Testing
How did you make sure this worked? How can a reviewer verify this?
I'm not actually sure how to test if issue templates are properly formatted, but we can verify this once merged by trying to create an issue!
# To-do list
- [ ] verify post-merge

Updated this to hopefully be a bit clearer on what to do.


v0.1.3

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/57210
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.3 -m "<description of version>" 1d4dd10ddda2920e4f20091a928302f95bfe8ff1
git push origin v0.1.3


WIP: über-config script

[ ] Update README & other docs

Did you change any of the scripts or just reorganize them?

Yep, some new arguments, setup-riak can configure a packaged installed Riak as well as a rel build.

👍


ExDoc now uses Makeup for syntax highlighting

By default, ExDoc uses a Javascript library for syntax highlighting
of code examples. The syntax highlighting is bad in general,
and particularly bad in some specific cases, like structures.
Makeup fixes many cases that were broken in the Javascript version,
and adds some niceties of its own, like highlighting matching delimiters
on mouseover.
Besides, except for the matching delimiters, Makeup doesn't require
Javascript, and the code is rendered into static HTML and CSS.
To build the docs:
MIX_ENV=docs mix docs

Is you want, I can change it so that you don't need to set MIX_ENV=docs, I only did it like this because you already have a config/docs.exs file.

Good point!

Please don't merge this right now. Makedown has a nasty bug when highlighting code that's not elixir code (i.e. HTML, drab templates, etc). I'll fix it as soon as possible.

Good point!

So you prefer dev?

So you prefer dev?
Yes, as @OvermindDL1 mentioned, I publish to hex in dev.

Ok. On the other hand, I've submitted a PR just like this to ecto, and @josevalim is worried about the fact that this has a large number of dependencies: https://github.com/elixir-ecto/ecto/pull/2264#discussion_r142973392
As I explain in that discussion, highlighting Elixir code well takes a lot of code, and there is really no way around it (doing it in Javascript, as ExDoc's doing now is just sweeping the problem under the rug). I think Makeup is realy much better than the Javascript at highlighting the code, and I think the extra dependencies are worth it.

Fixed upstream bug.

Meanwhile, you can browse the docs rendered by makedown here: https://tmbb.github.io/drab/Drab.html

Looks good at the first, very quick, glance, the only what I don't like is how it treats EEx injections with <%= %> - it is coloring the percent sign differently.
I will put it on hold for the same reason as here.

he only what I don't like is how it treats EEx injections with <%= %> - it is coloring the percent sign differently.

That's not a problem with Makwdown, it's a problem with your docs ;) You didn't specify a programming language for those code blocks, so Makedown assumes Elixir. They are actually EEx, and as such Makedown "fails" spectacularly. The default JS highlighter, highlight.js, assumes Elixir too, but because it color operators in black (Makedown's them colors them orange) and is generally crappy, you don't notice.
There is an HTML lexer for Makeup that might give you better results. You can also tag those code blocks as HTML so that they are handled by highlight.js.
I plan on having a Makeup lexer for EEx HTML templates relatively soon (about two months, I guess?), and I plan on shipping the documentation tool by default with support for Elixir, EEx and HTML (probably not CSS and probably not JS). For other languages, as long as you tag the block with the corresponding pogrammin language, highlight.js will try its best.

There is now a new package named ex_doc_makeup that simplifies the process considerably. It also has no dependencies besides ex_doc, ex_spirit and makeup (and makeup_elixir, of course). I'd submit a PR but actually I prefer you add it yourself to see if the docs are clear.

PS: It'll make the HTML and EEx in the docs look worse unless you explicitly tag them as HTML

Still not convinced. You should rather try to change the ExDoc, so you library would be standard for all docs.
Closing.

Still not convinced. You should rather try to change the ExDoc, so you library would be standard for all docs.

Excluding this PR, in ex_doc itself it by default uses markdown, you really need to tag the type of the text fields properly or color highlighting will fail in other modes too.  ^.^


SecurityFilters.groovy bug in updateUserGroups function

After integrating OWF with LDAP, the SQL statement here is not executing:
def addQuery = "INSERT INTO owf_group_people (person_id, group_id) VALUES (?, ?)"
in SecurityFilters.groovy
After inspection of the database, the record simply is not inserted.
When the SQL statement is run manually, the user is added to the group as expected.
The groups show up correctly, the users show up correctly.  But the groups do not have any users, even after an explicit user log in (I believe that process is dynamic).
After a user logs in, they should belong to the group, but the user count is still 0.
If I manually add the user to the group via the OWF admin tool, the user shows up in the group, but the desired functionality is automatic (since the user already belongs to the group in LDAP).
Any ideas?
Thanks,
Dan

This seems to only be an issue with OWF 7.17, will add a new issue with steps to recreate.


TerminalApplicationDelegate

Hi There,
I'm not sure if I'm missing something, but when I open the Sample app (which has a nuget reference to the built stripe bindings projectXamarin.Stripe.Terminal.Android) I can't find the TerminalApplicationDelegate, which I think I need to call in my Application file to notify the SDK about lifecycle events.
For example, I'm expecting to put something like this in my code:
namespace Xamarin.Stripe.Terminal.Android.Demo
{
    public class StripeTerminalApplication : Application
    {
        public override void OnCreate()
        {
            base.OnCreate();
            TerminalApplicationDelegate.OnCreate(this);
        }
    }
}

But I can't see where this is defined in the Xamarin.Stripe.Terminal.Android nuget package I've referenced.
I'm sure I'm missing something blindingly obvious... but I can't see what it is!
Any help would be very gratefully received!
Cheers,
Chris

The sample app hasn't been updated. I only updated the bindings. @davidsonblake might be able to tell you if he plans to maintain the sample app.

Oh, OK. Thanks for getting back!

I'm working on the 2.9 bindings right now. I should have those done in about 2 weeks.


fix: install: get infra-deployments branch, org

Description
fix a bug in installation when the infra-deployments branch and org is not identified correctly
Issue ticket number and link
N/A
Type of change

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

How Has This Been Tested?
in CI
Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("[test_id:01] DEVHAS-62 devfile source")
[ ] I have updated labels (if needed)

/retest

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e


Add a cli?

Would it be cool to have a Cli?
npm install deckdeckgo-cli
deckdeckgo init my-presentation

or something à la stencil?
goal -> with the help of a cli the user could be prompted to enter projects' name, description etc. and these information could be use to create the meta tags, manifest file etc. per default

There is now a cli https://github.com/fluster/create-deckdeckgo
npm init deckdeckgo


docs: add opengraph metadata tags

Summary
Adds sphinxext-opengraph to generate Open Graph metadata on all docs pages.
As an example, the resulting Discord embed looks like this:

Depends on https://github.com/wpilibsuite/sphinxext-opengraph/pull/86 for now, but we're in no rush to add this anyway.
Checklist

[ ] If code changes were made, then they have been tested

[ ] I have updated the documentation to reflect the changes
[ ] I have formatted the code properly by running task lint
[ ] I have type-checked the code by running task pyright

[ ] This PR fixes an issue
[ ] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[x] This PR is not a code change (e.g. documentation, README, ...)

Since the upstream PR this is waiting on has been stalled for a while now, I've decided to go with the slightly more fun complicated way of patching the event directly for now, adding on to the pile of sphinx hacks that are already there :p
If (and that's a big if, I'd understand if the maintainers don't want to add this feature) the other PR gets merged at some point, we can always update to that.

blocked by #722

would you please rebase on master and resolve conflicts?

I've changed it to generate more concise descriptions, by only taking the first section into account.
The :ogp_disable: logic was also removed for now, as #722 changed things up quite a bit - should opengraph metadata be disabled for API reference pages again?
Since a common use-case is linking to specific items on those pages, and opengraph obviously doesn't account for that, those embeds aren't all that useful right now:

Perhaps we can launch it on all pages, and remove it from API reference pages if it turns out to not work too well. (We won't know unless we try it)

Perhaps we can launch it on all pages, and remove it from API reference pages if it turns out to not work too well. (We won't know unless we try it)

Sound good to me, then.


Change Config of Existing MCS Controller

From: TA2
Priority: Backlog
Components: Python API
Blockers: None
Currently you pass a config file as an argument to create_controller. However, it would be nice if I could change the config of an existing controller, so I don’t have to recreate it. This would be especially helpful for the integration tests which currently have to create a new controller to test each metadata tier.
TA2 internal JIRA ticket: https://nextcentury.atlassian.net/browse/MCS-552

Thanks @ThomasSchellenbergNextCentury.  Here are a couple more feature requests that are orthogonal to the above but fall under the umbrella of "change config":
Currently, the environment variable $MCS_CONFIG_FILE_PATH overrides the explicit config argument passed to create_controller(...).  This was the cause of a substantial joint debugging session with @deanwetherby over Slack.  If the environment variable stays part of the design, I think the order of precedence should definitely be reversed, interested to hear if you agree/disagree.
It would also be nice to be able to pass in a config object (could be just a dict with certain documented keys) rather than the path to a file -- as a caller I've always been just writing a temp file every time a create a controller.

Closed by #400


Fix markdown format issue in README.md

Before:
**[HELP WANTED!]**
After:
[HELP WANTED!]

Thanks!


*: bump to hyperkube v1.0.7

Corresponding coreos-overlay PR for the kubelet in CoreOS here: https://github.com/coreos/coreos-overlay/pull/1618

LGTM


fixed memory leak caused by illegal memory access

==26213== 880,176 bytes in 14 blocks are definitely lost in loss record 15 of 15
==26213==    at 0x4844C2C: malloc (vg_replace_malloc.c:299)
==26213==    by 0x4A2EB1B: cv::fastMalloc(unsigned long) (alloc.cpp:64)
==26213==    by 0x4A30DB3: cv::Mat::create(int, int const*, int) (matrix.cpp:215)
==26213==    by 0x4B94CF: cv::Mat::create(int, int, int) (mat.hpp:353)
==26213==    by 0x4B9527: cv::Mat::create(cv::Size_<int>, int) (mat.hpp:358)
==26213==    by 0x4FB187: CV_Remap_Test::generate_test_data() (test_imgwarp_strict.cpp:668)
==26213==    by 0x4FD057: CV_WarpAffine_Test::generate_test_data() (test_imgwarp_strict.cpp:993)
==26213==    by 0x4F8433: CV_ImageWarpBaseTest::run(int) (test_imgwarp_strict.cpp:217)
==26213==    by 0x54FEEB: cvtest::BaseTest::safe_run(int) (ts.cpp:214)
==26213==    by 0x4FEECB: Imgproc_WarpAffine_Test_accuracy_Test::TestBody() (in /home/nvidia/build_opencv/bin/opencv_test_imgproc)
==26213==    by 0x577ADF: void testing::internal::HandleSehExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) (ts_gtest.cpp:3578)
==26213==    by 0x5721AF: void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) (ts_gtest.cpp:3614)
==26213==
==26213== LEAK SUMMARY:
==26213==    definitely lost: 880,176 bytes in 14 blocks
==26213==    indirectly lost: 0 bytes in 0 blocks
==26213==      possibly lost: 4,676 bytes in 83 blocks
==26213==    still reachable: 131,780 bytes in 788 blocks
==26213==         suppressed: 0 bytes in 0 blocks

:+1:


为什么不增强错误提示

使用了https://pub.dartlang.org/packages/stack_trace这个扩展后,错误信息定位更强大了. 为什么dart不默认实现这个功能?

Hi, please describe your Problem in English so that we can help you.
Is this still a problem?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Android in portrait mode have less fps than in landscape mode

Hi guys,
I'm doing some tests using the RESIZE scale mode and I noticed something strange happens in Android. When you have the mobile in Landscape, the performance is very good like in iOS (~60 fps), but in Android when you change to Portrait, the fps is very bad (~8 fps).
It is very strange :/

+1

that's quite interesting.
@jdnichollsc how are you using phaser in android, I am curious. Are you using cordova? or cordova + crosswalk?

both, I am creating an integration with Phaser :)

Does this only occur under 'RESIZE'? What about any mode if there is a scaling applied?

Yes, only in RESIZE scale mode. Using Phaser.ScaleManager.EXACT_FIT works good.

Any news about this error? =)

yo Juan ... Dave
its marzy
that u/>/?
On Thu, Oct 29, 2015 at 9:50 PM, Juan David Nicholls Cardona <
<EMAIL_ADDRESS>wrote:

Hi guys,
I'm doing some tests using the RESIZE scale mode and I noticed something
strange happens in Android. When you have the mobile in Landscape, the
performance is very good like in iOS (~60 fps), but in Android when you
change to Portrait, the fps is very bad (~8 fps).
It is very strange :/
—
Reply to this email directly or view it on GitHub
https://github.com/photonstorm/phaser/issues/2181.

--
From Marsden Seneca Hayward-Rope
<EMAIL_ADDRESS>https://www.planitmarz.yolasite.com
<EMAIL_ADDRESS>

@MARSDEN what? I don't understand
See my facebook: https://www.facebook.com/jdnichollsc

I can't see how it'd make any difference at all about the orientation, unless Android was doing something quirky under the hood.
Perhaps resize is being hammered? Try this: in your States 'resize' function, just log it out each time it's called (it gets sent width / height  parameters, so log those). Perhaps resize is being slammed for some reason. Worth testing anyway.

@txchen see my example :D http://market.ionic.io/plugins/ionphaser

Sorry, my cellphone was a troll with me, @photonstorm ley me try, thanks! :)

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.
This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.
If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.


Handle thread names with spaces when parsing /proc//stat

GetCumulativeCpuTimeFromProcess and GetThreadState parsed the content of
/proc/<pid>/stat by splitting on spaces, but didn't consider that the thread
name enclosed in parentheses could contain spaces itself.
Bug: http://b/170073156
Test: Start a process with one/two/three spaces in its name and check that its
displayed CPU utilization is correct. Update test for GetThreadState.

#1337, LEET!

#1337, LEET!

Hehe I didn't want to say it!


example-app: Move to examples/instrumentation; Added Native Histograms.

This is done for 3 reasons:

Enables adding more examples - we already have planned client-server one ("pinger")
To separate core components with example applications
example-app naming was confusing. It is used for both this app as well as examples/example-app.yaml referenced by the public docs. Let's be specific now.

I plan to also add more synthetic metrics and tests later on.

This will hopefully work seamlessly with our CI image pipeline, just instead of gcr.io/gke-release/prometheus-engine/example-app:<tag> to gcr.io/gke-release/prometheus-engine/go-synthetic:<tag>
Will fix internal playbooks later on to accommodate this.


How to SELECT "col" IS NOT NULL AS "alias" ?

Is there a way to alias a boolean expression in the select column list?
I think what I want is basically:
db.From("foo").Select(goqu.I("foo.bar").IsNotNull().As("have_bar")

But type exp.BooleanExpression does not implement As(). I can work around it using a functional expression. This generates the correct SQL, though with extra parenthesis:
Select(goqu.Func("", goqu.I("foo.bar").IsNotNull()).As("have_bar"))

...but I'm hoping there's prettier way that doesn't involve abusing Func()...

@makholm hi, try this
goqu.From("foo").Select(
		goqu.L(`foo.bar IS NOT NULL`).As("some_field"),
	)


Add hover over effects to buttons

when clicking button the user has to identify that he is clicking the button
therefore adding of hover over effects will give the user sign of clicking on the button which can give the user Best UI experience

please assign me this issue.

@Priyaaa1  Can you assign this issue to me?

@mehrun171 @imvish21 @Riyasharma1311  this has been already done.


Management Functions should support depends tags

App notes for Management Functions often specify when the Function must be included, but there is no way to enforce this.

This is folded into issue #109.


Switch to using async SQLAlchemy

Is your feature request related to a problem? Please describe.
At the moment, we use the synchronouse SQLAlchemy interface. FastAPI is async, though.
Describe the solution you'd like
Switch to the async variation. Needs to work with sqlite and postgres.
Describe alternatives you've considered
N/A
Additional context
N/A

#82


toy-block icon

Icon name: toy-block
Use case: Used for plugins, add-ons
Contributes to #651
similar icons:

Design proposal:

100%

Looks nice, but I think we can easily go with square's full height as well as the full 2px rounding and still have it completely legible.


black bar appear when zoom

First of all, thanks for the great library that ease the map implementation on native platform. ( I have tried WebView but the process is terribly slow).
I has been using TileView since the release of v2 and i am happy with the amazing performance. However, recently I encountered some weird problem where certain part of the map will turn black

Whenever the black bar appear, i got this error in the log:
E/OpenGLRenderer: GL error:  GL_INVALID_OPERATION
my code snippet :
tileView = new TileView( this,combinedPoints,"" );
tileView.setSize(7677, 7677);  // the original size of the untiled image
  tileView.addDetailLevel(0.0125f, "maptiles/1/%d/%d.png");
    tileView.addDetailLevel( 0.2500f, "maptiles/2/%d/%d.png");
    tileView.addDetailLevel(0.5000f, "maptiles/3/%d/%d.png");
    tileView.addDetailLevel(1.0000f, "maptiles/4/%d/%d.png");

setContentView(tileView);
please let me know if you need further information

the only thing that's immediately obvious is that it should be instanced programmatically using just a context: new TileView(this);
other than that, there's nothing that stands out - the error is from some graphic library operation.  maybe implement your own BitmapProvider and log out exceptions...


Added support for empty response bodies

Fixes https://github.com/javorosas/react-native-rest-client/issues/3
Useful for HTTP responses which typically contain no data, for instance:

HTTP 201 Created
HTTP 202 Accepted
HTTP 204 No Content

and so on.
I bumped the version because I changed the signature of _fetch

In my opinion adding a flag for "tolerating an empty response" is a flaw in the design. If there's no body, we should just spit an empty object. As you said, in HTTP 204 there's basically no data (through 201 can return the entity just created but that's an other discussion), so we should just expect it.
What would be interesting would be to throw a Malformed JSON Exception when the body is, well, malformed :)

Ok I think empty responses should just be mapped to {} by default, do you agree?

I agree yes !

I've updated the pull request. Slight change from what was discussed above, I think undefined makes more sense than an empty object, but I'd be open to changing this to {}

Hi all. Sorry for the long absence and thank you for your interest. I'm glad to hear this is useful for someone 🙂
I see your point and agree that the response should not throw an error, but I don't think it should return an empty object, that would be misleading. I like the idea of returning undefined, it makes a lot of sense. After all you're receiving an empty body response. There's literally nothing there.


Improve tooltips

Tooltips (text that appears on mouseover) can be helpful when learning new software. Current tooltips in the GUI are as follows:

Window
Tooltip

Navigator
—

Coordinates
This is a CoordinateViewer window

Properties
Properties

Visualizer Window
This is a Visualizer window

Messages
This is a message window

ScriptingShell Window
This is a ScriptingShell window

I also suggest updating the tooltips for the buttons in the top-left corner of the Visualizer Window. "Front" should be something like "Front view" or "Move camera to front", etc.

Totally, @tkuchida I can point you to the file where these tooltips are set so you can try making the text change and open a PR when satisfied. Thank you.


NTI warnings about templates can be confusing

Using NTI (new type inference) compiler I get warnings like this:
src/lab/model/SimListStandard.js:206: WARNING - Could not instantiate type
function(T,number,?):boolean|null with
function(myphysicslab.lab.model.SimObject,?=,?=):boolean.
      function (/** !myphysicslab.lab.model.SimObject */obj, index, array) {
      ^

This is on the following code
SimListStandard.prototype.get = function(arg) {
  if (goog.isNumber(arg)) {
    if (arg >= 0 && arg < this.elements_.length) {
      return this.elements_[arg];
    }
  } else if (goog.isString(arg)) {
    /** @type {!myphysicslab.lab.model.SimObject} */
    var e = goog.array.find(this.elements_,
      function (/** !myphysicslab.lab.model.SimObject */obj, index, array) {
        return obj.getName() == arg;
      });
    if (e != null)
      return e;
  }
  throw new Error('SimList did not find '+arg);
};

where this.elements_ is defined by:
/** @classdesc The standard implementation of a [SimList]{@link myphysicslab.lab.model.SimList}.

Part of module [myphysicslab.lab.model](myphysicslab.lab.model.html)

* @constructor
* @struct
* @extends {myphysicslab.lab.util.ConcreteSubject}
* @implements {myphysicslab.lab.model.SimList }
*/
myphysicslab.lab.model.SimListStandard = function() {
  ConcreteSubject.call(this);
  /** The {SimObjects}s that this {SimList} contains.
  * @type {!Array.<!myphysicslab.lab.model.SimObject>}
  * @private
  */
  this.elements_ = new Array(0);
  /**
  * @type {number}
  * @private
  */
  this.tolerance_ = 0.1;
};

Confusing to me is T in the message.  I understand it's one of the template variables in goog.array.find.  But the message says nothing about what type the compiler thinks T is or should be.  Or whether the compiler can't figure out what type T is.  (this is related to issue #855)
Another example is the EVENTOBJ template variable in goog.events.listen as shown in issue #962.

Another example is in a comment on issue #855 where the message is
src/lab/engine2D/Polygon.js:1260: WARNING - Cannot access property distanceToLine of
non-object type T.
      return e.distanceToLine(p_body) > 0;
             ^

Again, if the compiler has some concept of what T is, it would be helpful to know.


Example vtsd.conf file?

I'm trying to find a sample vtsd.conf file, but it doesn't look like there are any in this repo.

Fully documented and working vtsd config is in the vts-backend: vtsd.conf.
I'll update the doc here.