obs-do: 0.1.1 -> 0.1.5

Things done
Diff: https://github.com/jonhoo/obs-do/compare/refs/tags/v0.1.1...v0.1.5
Fixes #366164

Built on platform(s)

[x] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366165

x86_64-linux

:white_check_mark: 1 package built:

obs-do

aarch64-linux

:white_check_mark: 1 package built:

obs-do

x86_64-darwin

:white_check_mark: 1 package built:

obs-do

aarch64-darwin

:white_check_mark: 1 package built:

obs-do


Fix vi partial accept

Cf https://github.com/zsh-users/zsh-autosuggestions/issues/188

Please use double square brackets ([[ ]]) for code consistency.

Thanks for fixing this! Can you add a test?

Code style fixed, I'll look into making a test.

@ericfreese, I can't get the already existing tests to pass :
rspec ./spec/integrations/wrapped_widget_spec.rb:15 # a wrapped widget initialized before sourcing the plugin executes the custom behavior and the built-in behavior rspec ./spec/integrations/wrapped_widget_spec.rb:32 # a wrapped widget initialized after sourcing the plugin executes the custom behavior and the built-in behavior
This happens both on this branch, on develop, and on master.
Is this a known issue ? Is something wrong in my test environment ? Should I just ignore these errors and go ahead adding a test ?

Here is a test, I don't know if it seems clean enough, though.

Thanks @toadjaune! I will take a look at this soon.

I've added an additional test to the new fixes/vi-partial-accept branch that tests a behavior that seems intuitive to me: not accepting the first character of the next word when using vi-forward-word to partially accept a suggestion.
With the proposed patch, the new test fails with:
  expected: "foobar baz"
       got: "foobar fbaz"

What do you think about this case? What do you think would be the most intuitive behavior?
I'm not sure the most elegant way to include the char under the cursor for vi-forward-word-end, but not include it for vi-forward-word. Ideally both of these tests will pass.

The more I think about this, the more I think it would be ok for vi-forward-word to accept the first char of the next word. You could still accept to just before it by using f<space> (which makes me realize I need to add vi-find-next-char and vi-find-next-char-skip to ZSH_AUTOSUGGEST_PARTIAL_ACCEPT_WIDGETS

In my opinion, the vi widgets should move the cursor like they usually do, so it should be ok to accept the first character of a new word if necessary. In that case, the user can still press C do delete this one character and change to insert mode.

Ok I've applied a similar patch with https://github.com/zsh-users/zsh-autosuggestions/commit/393f7b8bb9d83aef1847d39ad20c6a73849917b8 that should fix issue #188. It's been merged to develop branch and will be included in the next release.
Thanks @IngoHeimbach and @toadjaune for your effort on this!

Thanks everyone for your work! :+1:

I think that we should probably simply let widgets such as vi-forward-word do their job normally, and don't try to change their behavior in any way.
It would be a surprising (and pretty terrible) experience to have the cursor behaving differently depending on whether we're moving through the beginning of the command or through the suggestion. Same goes about behaving differently with and without zsh-autosuggestions.
Therefore, since in vicmd keymap, the cursor can never be after the last character, and since vi-forward-word will usually bring it on the first letter of a word, I agree that the sanest thing to do here would be … nothing specific (ie let it accept the first letter)

Oh, I had not reloaded my tab, missed the two latest messages, sorry ^^'
Your solution is probably more elegant than mine, I tried to make something similar but couldn't get it to work.
However, I'm a bit worried that we might encounter issues down the road, by not using $LBUFFER and $RBUFFER, in some weird edge case.
Anyway, thanks everyone, that's a good needle out of our foot :)


[Feature request] Drag & Drop to open a file

It would be greate to have a drag & drop feature to open a file
Additional context

Isn't it already supported by Notepads?

Seems like it isn't.
Here is an example:

@0x7c13
Any thoughts? Maybe it's only on my machine such problem?

What's the version of the app?


Fails to compile on GHC 9.0.2

The command issued was stack install uncertain.
uncertain           > configure
uncertain           > Configuring uncertain-<IP_ADDRESS>...
uncertain           > build
uncertain           > Preprocessing library for uncertain-<IP_ADDRESS>..
uncertain           > Building library for uncertain-<IP_ADDRESS>..
uncertain           > [1 of 6] Compiling Data.Hople
uncertain           > [2 of 6] Compiling Numeric.Uncertain
uncertain           > [3 of 6] Compiling Numeric.Uncertain.Correlated.Internal
uncertain           >
uncertain           > /tmp/stack-2d776474f014098e/uncertain-<IP_ADDRESS>/src/Numeric/Uncertain/Correlated/Internal.hs:187:40: error:
uncertain           >     • Couldn't match type: forall t1.
uncertain           >                            M.IntMap (AD t1 (Sparse a1)) -> AD t1 (Sparse a1)
uncertain           >                      with: M.IntMap (AD t (Sparse a1)) -> AD t (Sparse a1)
uncertain           >       Expected: CVar s1 a1
uncertain           >                 -> M.IntMap (AD t (Sparse a1)) -> AD t (Sparse a1)
uncertain           >         Actual: CVar s1 a1
uncertain           >                 -> forall t. M.IntMap (AD t (Sparse a1)) -> AD t (Sparse a1)
uncertain           >     • In the first argument of ‘flip’, namely ‘cVarToF’
uncertain           >       In the first argument of ‘(<$>)’, namely ‘flip cVarToF us’
uncertain           >       In the first argument of ‘f’, namely ‘(flip cVarToF us <$> cs)’
uncertain           >     • Relevant bindings include
uncertain           >         us :: M.IntMap (AD t (Sparse a1))
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:187:27)
uncertain           >         cs :: f (CVar s1 a1)
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:187:23)
uncertain           >         f :: forall t. f (AD t (Sparse a1)) -> AD t (Sparse a1)
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:187:21)
uncertain           >         cVarToF :: CVar s1 a1
uncertain           >                    -> forall t. M.IntMap (AD t (Sparse a1)) -> AD t (Sparse a1)
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:185:9)
uncertain           >         cv :: CVar s1 a1
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:180:13)
uncertain           >         getCVar :: CVar s1 a1 -> M.IntMap (Uncert a1) -> Uncert a1
uncertain           >           (bound at src/Numeric/Uncertain/Correlated/Internal.hs:180:5)
uncertain           >     |
uncertain           > 187 |         cVarToF (CF f cs) us = f (flip cVarToF us <$> cs)
uncertain           >     |                                        ^^^^^^^

Still a problem to compile latest release with current stackage nightly set:
/home/andreas/stackage/stackage/tmp.xfaM/uncertain-<IP_ADDRESS>/src/Numeric/Uncertain.hs:249:22: error: [GHC-88464]
    Variable not in scope:
      foldl' :: (H3 a0 -> a0 -> H3 a0) -> H3 a1 -> c
    Suggested fixes:
      • Perhaps use one of these:
          ‘foldl’ (imported from Prelude.Compat),
          ‘foldl1’ (imported from Prelude.Compat),
          ‘foldr’ (imported from Prelude.Compat)
      • Add ‘foldl'’ to the import list in the import of ‘Data.Foldable’
        (at src/Numeric/Uncertain.hs:60:1-29).
    |
249 |     foldStats = flip foldl' (H3 0 0 0) $
    |

Thanks, @alaendle , hope it should be working now on <IP_ADDRESS>, just confirmed! For some reason it was building for me on 9.8.2, i'm really confused now.


Update Shared Experiences doc page

Cleaned up markdown
Fixed some broken URLs and added some additional ones
Added note sections

Docs Build status updates of commit 79c4cf6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/shared-experiences-in-mixed-reality.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How to access the child page view content?

The following line in the code is preventing me from tinting the color of my icons. Is there a workaround to accessing the child page view controllers?
Thanks!
    fileprivate var container: AlertPageViewController!

Not really, what do you want to do exactly ?

My pull request #28 includes an optional delegate method callback for this. If you implement it, that method will be called when the view controller is displayed, to perform any animations or manipulations, etc.


Service models required for container deployment automation

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1356623

@mkanoor @gmcculloug Hey, could you review?

depends on : #9228

@miq-bot add_label wip

depends on : https://github.com/ManageIQ/manageiq/pull/7517
failure is caused by dependency.

few nits, but what is most important, using #9230, #8753 and #7517, I am able to deploy working all-in-one OpenShift. So :+1:

@yaacov @moolitayer @zeari @dkorn @enoodle
Review it please guys

Looks better :+1:  Added some more suggestions.
I'm strongly in favor of merging sooner and iterating by PRs that leave a history trail.

I'm strongly in favor of merging sooner and iterating by PRs that leave a history trail.

@alongoldboim please address the outstanding comments and then we'll move this into the merging queue. Thanks.

LGTM.

@simon3z Could you have another look?

@simon3z any more comments?

@miq-bot add_label darga/

@gmcculloug @bdunne @mkanoor I think all of the problems are now resolved, please have another look.

@miq-bot assign @gmcculloug

@chessbyte @gmcculloug this seems ready :+1: . Can you merge?


Problem with wildcard certificate used several times

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[X] No

What did you do?
We are using a single wildcard certificates for numerous kubernetes ingresses. There seems to be a corner case when we want to test the renewal of the certificate on a single ingress.
Unless I'm mistaken Traefik seems to cache certificates by CN and does not add a certificate when it already knows it.
This makes it impossible to use a new version of a wildcard certificate on a limited number of ingresses. You have to apply the new version of the certificate on all ingresses which use it so that Traefik accept to replace it.

@sylr you did not specify what version of Traefik you are using, which matters for the answer we're going to give you.

1.7

@sylr There's indeed a cache, but it should expire after a while (in the order of the hour), so your problem should resolve by itself after that expiration.

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


Updating: gan_sample/chapter7/requirements.txt

It might make more sense to update from ipython-sql to Jupysql.
Adding more context.
This transition should help you avoid compatibility issues and get access to newer features.
Just switching the name and version as backward compatibility is on.

thank you for your advice
I would like to take the opportunity to update


Recommendations for filtering/grouping correlated features

Hi again.
I'm dealing with a high dimensional dataset (~400k) of high correlated features, and am working on explaining them (using gradient explainer) and making sure that I retain enough of the top features for more nuanced explanations.
What's your recommended approach for the number of features to take, and getting rid of these correlated features?
Also, would you recommend interpretations for regression that are based on both positive and negative attributions, or split the analyses into three explanation analyses, one based on pos, one neg and one based on absolute value? I'm also trying to think of the best way to extend these analyses to multi-output regression explanations.
Thanks!

It seems like if you have 400k correlated features they are likely not all individually meaningful, rather groups of them are. If you can somehow create meaningful groups, then you can just sum the SHAP values within each group to get an estimate of the group's importance. Just keep in mind that large groups will likely be more important than small groups just because the model has a better chance of randomly using them (in addition to other more interesting reasons large groups might matter more). As for selecting a specific number you could always do a bootstrap and see how many groups get weights consistently above or below zero.
For your second question, I think seeing positive and negative together is helpful, but depending on the situation I could imagine breaking it apart might make sense. It really depends on who you are communicating with and what you are trying to communicate.

Is there also a p-value type approach I can use for selecting significant features?
Because I have 400k features its hard to know how many top features to inspect. What would you recommend?

Thanks for the answers!

You could get P-values by putting permuted versions of the features into the model and then comparing statistics between the permuted columns and the real ones. There is also a paper that explores another approach (not written by me) at: https://arxiv.org/abs/1903.04209

Thanks! I’ll check it out.


Is there a dicom conformance statement or list of supported Syntax transfers?

 Your question is much more likely to
be answered if it is
a good question
Description
I wanted to check what transfer syntaxes are accepted by OHIF, but I couldn't find any Dicom conformance statement. Thanks to the monorepo branch, I was able to find that transfer syntax is handled by the Cornerstone Wado Image Loader dependency . I couldn't find a Conformance statement in there either.

This is the closest thing we have:
https://github.com/cornerstonejs/cornerstoneWADOImageLoader/blob/master/docs/TransferSyntaxes.md
Is there specific information you are looking for or think would be valuable to document?

Thank you! My search parameters must have grazed this file in the cornerstone repo.
I opened this because someone in a dcm4che group was trying to use compression. https://groups.google.com/forum/#!forum/dcm4che
 I remember trying this in the meteor version a while back but decided against it because it required a level of skill I did not have.
I think configuration options would be a good place to focus regarding documentation. If I found a list of  all configuration options, I could quickly check whether alternate TransferSyntaxes are easily configurable, and move on if not.

You should be able to configure the WADO Image Loader (as here: https://github.com/crowds-cure/cancer/pull/24/files#diff-30a5f46d2481f3745ed7cc8070f71a04R40) to request a specific transfer syntax but we have not added any configuration for that at the OHIF level. That would be a good idea.
I agree we should write a DICOM Conformance statement for OHIF, and probably also for the WADO Image Loader itself.


Update use-dkim-to-validate-outbound-email.md

Temporarily disabling autorotation.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@andypunt - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@MSFTTracyP - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith


[WIP]Added new C_Apis to suport Large vectors and added tests for initial set of ops

Description
New C_apis and verification of Large tensor support in a couple of operators
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot add [pr-work-in-progress]

@mxnet-label-bot add [pr-awaiting-review]

@apeforest @ChaiBapchya this is now ready for review

@apeforest @ChaiBapchya pr is ready for review

Made a note of the skipped tests in this issue. For easy tracking.

Please paste your output here after you run through the test locally. Thanks!


null safe version

hello farzin, is any update for null safety?

Hi Hasan.
Not yet. Maybe after nowruz holidays

@hassanbasanjide
Done 🤔😆


Reorg-capable light client

Ideally a light client is able to sync to the head of the beacon chain, rather than sync only to the finalized block.
Investigate current light client reorg mechanisms.
Help build consensus, write specifications, implement pocs, etc to push this feature towards standardization and production.

Does the latest light client demo solve this issue? Otherwise, the other tasks seem like they can be broken down into some of the other ones we may already have in the Light Client Tracker (#3469). cc: @wemeetagain

Fixed by https://github.com/ChainSafe/lodestar/pull/3461


[config] Add basic config validators for path rewrite, host rewrite and redirect actions

Description: Reject path rewrite, host rewrite and redirect config fields that contain \0, \r or \n characters.  This provides some basic protection against config errors that could result in problems due to the proxy, upstream and downstream disagreeing about the contents of headers.
Risk Level: medium
Testing: Added config tests that trigger on the new validations
Docs Changes: n/a
Release Notes: TBD
Fixes #10332

/azp run envoy-windows

cc @htuch @lizan for API policy review.

First CI attempt failed due to gitdb package being too old.  Now the mac CI failed while installing dependencies.
I'll kick it again sometime later.


[Snyk] Upgrade org.webjars.bower:angular from 1.8.2 to 1.8.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.webjars.bower:angular from 1.8.2 to 1.8.3.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2023-01-03.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

not all dependencies are available for 1.8.3


freecell-solver: 6.10.0 -> 6.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/freecell-solver/versions.
meta.description for freecell-solver is: FreeCell automatic solver
meta.homepage for freecell-solver is: https://fc-solve.shlomifish.org/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.12.0 with grep in /nix/store/slhh0dck2wbmd8dqi8x8ka0gnz5phq3r-freecell-solver-6.12.0
found 6.12.0 in filename of file in /nix/store/slhh0dck2wbmd8dqi8x8ka0gnz5phq3r-freecell-solver-6.12.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath

freecell-solver
kdePackages.kpat
libsForQt5.kpat
plasma5Packages.kpat
pysolfc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/slhh0dck2wbmd8dqi8x8ka0gnz5phq3r-freecell-solver-6.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A freecell-solver https://github.com/r-ryantm/nixpkgs/archive/e5a2f1e622fefd4bd777d3df68bf1114e4cd6fc6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e5a2f1e622fefd4bd777d3df68bf1114e4cd6fc6#freecell-solver

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/slhh0dck2wbmd8dqi8x8ka0gnz5phq3r-freecell-solver-6.12.0
ls -la /nix/store/slhh0dck2wbmd8dqi8x8ka0gnz5phq3r-freecell-solver-6.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

11 packages built:

freecell-solver
freecell-solver.dev
freecell-solver.doc
freecell-solver.man
kdePackages.kpat
kdePackages.kpat.debug
kdePackages.kpat.dev
kdePackages.kpat.devtools
libsForQt5.kpat
pysolfc
pysolfc.dist

Maintainer pings
cc @AndersonTorres for testing.

@NixOS/nixpkgs-merge-bot merge


Flickering menus

VSCode Version: 1.45.0
OS Version: Linux Mint 19.3 Tricia

Steps to Reproduce:

Open VSCode
Click the menus

This video better shows the issue: https://photos.app.goo.gl/R6cs3EdQqihjfqwR7.

Does this issue occur when all extensions are disabled?: Not sure, but it happens on a fresh install.

The video doesn't play for me, looks like it's about the custom title bar though. You could try launch with --disable-gpu to see if that fixes it.

Might be https://github.com/microsoft/vscode/issues/97270?

@Tyriar from the description, it seems the same as #97270 . There's a comment there about a fix potentially being ready.
Google Photos sometimes takes a bit to load the video, please try again. It worked fine for me now on a incognito window.

@fornellas can you check if the issue is fixed with the exploration build https://az764295.vo.msecnd.net/exploration/7faa10cfc640a15751049cdc6e894c5d146ff7dd/code-exploration-1588920827.tar.gz ? Thanks!

@deepak1556 downloading and running binaries from domains unrelated to this project seems... fishy. Can you please point me to the source? Perhaps I can build it myself.
PS: --disable-gpu does not fix the issue.

@fornellas that's our release server where all automatic and manually downloaded updates are served from.

@deepak1556 confirmed your exploration build fixes the issue. FYI, it can be repro at VirtualBox + fresh Ubuntu as well.
This issue is more noticeable with dark themes, but it is still fairly noticeable with white themes. It seems the root cause is that drawing a simple drop down menu is taking a humongous amount of time, during which, the area is white.
My machine runs Chrome just fine ("same" engine, isn't it?) with no performance issues.

Thanks for testing, VSCode is not responsible for drawing the menus, the issue stems from electron and it is being tracked under https://github.com/electron/electron/issues/18184

confirmed your exploration build fixes the issue. FYI, it can be repro at VirtualBox + fresh Ubuntu as well.

However, I am able to repro the issue with exploration build on my parallels vm. I haven't investigated this issue further.
You can workaround with "window.titleBarStyle": "custom" for now, the runtime in exploration build will be pushed to insiders soon. I am merging this to https://github.com/microsoft/vscode/issues/80798


Without pretraining on first 50 classes

Hi @arthurdouillard ,
Thanks for the great codebase!
I would like to evaluate all algorithms in the setting where pretraining on the first 50 classes is not allowed.
I'd like to know if just setting --initial-increment and --increment to appropriate values (eg. 5 and 5) would do.
Would it need any change in hyperparameters, in any of the algorithms?
Thank you very much!

Thanks for the great codebase!

Thank you! 😊

I'd like to know if just setting --initial-increment and --increment to appropriate values (eg. 5 and 5) would do.

Yes it'll work perfectly, just so you know when initial increment = increment, the community often also disabled the fixed memory (see options file).

Would it need any change in hyperparameters, in any of the algorithms?

I'm sure you could improve PODNet or UCIR bu tuning them yes, but neither them or I did. Note that those algos are a bit particular, and are largely SotA when initial increment is large, but their gains is less important with small increments. I think it's because they are metric-based, with a cosine classifier, and thus need more pretraining data.

Got it, Arthur. Thank you very much for the reply.


PaymentElement missing options

Describe the problem
It is not currently possible to specify options such as layout or defaultValues when creating a PaymentsElement.
Describe the proposed solution
The solution would be similar to the Address element, which offers this possibility.
Alternatives considered
No response
Importance
Would make my life easier
Additional Information
No response

+1

Resolved in #72


chore: move release.ci.jenkins.io from prodpublick8s cluster to privatek8s cluster

Ref: https://github.com/jenkins-infra/helpdesk/issues/2844

Testing this PR in its current state from my machine first:
$ kubectl config use-context privatek8s-emerging-ram
Switched to context "privatek8s-emerging-ram".

$ helmfile apply -f clusters/privatek8s.yaml -l name=jenkins-release


Transaction style disabling model cache

Is your feature request related to a problem? Please describe.
I am always having to disable the model cache on certain queries with lazy loaded relationships. I have created a helper for myself and figured others would find it useful for running an entire block of code with the model cache disabled and then turned on after the function is ran.
Here is my definition:
public function disableModelCache(callable $closure)
{
    //get the current value
    $pre_config = config('laravel-model-caching.disabled');

    //disable model cache
    config(['laravel-model-caching.disabled' => true]);

    //run the function
    $closure();

    //reset the config
    config(['laravel-model-caching.disabled' => $pre_config]);
}

In my project I have a Helpers facade that the function lives in and can be used like this.
Helpers::disableModelCache(function(){
    // do things here with model cache disabled
});

//model cache is re-enabled here

Hi @mycarrysun, thanks for suggesting this. Does the ->disableCache() in the eloquent chain not work in your use-cases? If you could explain why that doesn't work, that will help me understand the specific use-case for this way better. Thanks! :)

It does work now yes. Thanks :)
This is more of a convenience thing. I am using it in 2 places where I have multiple lazy load calls that I do not want loaded from the model cache and it is being called by a relation magic getter, which is not an eloquent query (eg $this->cartable->load(['relation1', 'relation2']); - where cartable is a relation of $this and I don't want relation1 or relation2 loaded from model cache). Now, in this situation I believe I can just call $this->cartable()->disableCaching()->get()->load(['relation1', 'relation2']); but that is a much big refactor than wrapping a block of code in a callable.
It is also convenient if you are calling functions that are also calling eloquent queries inside other classes/methods that you don't want to add another param just to flag if you want model cache enabled/disabled.
Hope this makes sense.

Hi @mycarrysun, this is now in release 0.4.13. :) Thanks for the suggestion. Please see the readme for implementation details.

Nice man! Thanks for adding so quickly!

Looks good - just peeped the readme


sftpgo: 2.4.5 -> 2.5.0

Description of changes
https://github.com/drakkan/sftpgo/releases/tag/v2.5.0

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.05 Release Notes (or backporting 22.11 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.

What was the security flag for here?

Thanks to Polina Zvorykina, VK for reporting an XSS vulnerability in the new IP lists page before the official release, although we are not pleased that they don't support the project and they use a private SFTPGo fork.

https://github.com/drakkan/sftpgo/commit/084d4109b88b9209d0720b26acdfc415d71611b7


Editor RubyMine support

I really liked the Brighton Ruby talk on this and want to get started but I looked around and couldn't find anything for running rubyfmt on RubyMine. I can periodically run it from command line on the entire directory and RubyMine will refresh it but that feels quite hacky.
I don't know the right place to put this so I'm sorry if I'm not following the right format for the issues.

https://github.com/penelopezone/rubyfmt/pull/245 - sorry I forgot about this. Just put the image and two links and that should be helpful enough for anyone right now. Maybe the future can have an official plugin on the jetbrains store once rubyfmt is looking kinda done.


MAINT: Add PyOpenGL on macOS

Checklist

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

@marsipu I think since we by default try PyOpenGL on macOS and raise an error if it's not there, it should be in the recipe for that platform. WDYT?
It would have fixed https://github.com/mne-tools/mne-python/runs/5364484062?check_suite_focus=true

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.
Non noarch packages should have python requirement without any version constraints.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch packages can't have selectors. If the selectors are necessary, please remove noarch: python.
noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

It looks like it only built 3.7+ anyway, presumably because the mne dep is 3.7+. Do you think we should have it anyway?

It looks like it only built 3.7+ anyway, presumably because the mne dep is 3.7+. Do you think we should have it anyway?

Yes please add it; maybe rules have changed but I remember that not having such a constraint would regularly lead to a rejection of my PRs from conda-forge/staged-recipes; not sure why the linter doesn't pick up on it though! I'd add it just to be sure…

presumably because the mne dep is 3.7+.

btw conda-forge (currently) doesn't build with anything older than 3.7. Still, I think it's good practice to explicitly add the constraint!

@conda-forge-admin please rerender

Feel free to merge if you're happy @hoechenberger

Thank you, @larsoner lat


Firebase project [myproject] not configured.

Hello,
I am getting this error "Firebase project [myproject] not configured." while sending a notification in laravel with FirebaseChannel.
public function via($notifiable)
{
return [FirebaseChannel::class];
}
it's probably generated from this file but don't know what i did wrong.
vendor/kreait/laravel-firebase/src/FirebaseProjectManager.php:41
protected function configuration(string $name): array
{
$config = $this->app->config->get('firebase.projects.'.$name) ?? null;
if (!$config) {
throw new InvalidArgumentException("Firebase project [{$name}] not configured.");
}
return $config;
}

Hey @virenderscideas, FYI I moved this issue from the firebase-php repo here. How have you configured the package? Which versions of the kreait packages are you using (composer show | grep kreait)? On which PHP version? Is this something that worked before but stopped working?

i'm facing the same issue
Below is the composer show

what is the right way to configure firebase in laravel? all the tutorials and articles are outdated and there's no recent specific laravel based articles.
Thanks in Advance

Have you put a FIREBASE_CREDENTIALS=/path/to/your/service_account.json line in your .env file?

Its in my project root directory

Sorry for the late reply - have you resolved the issue in the meantime? If not, could you please share the full contents of config/firebase.php?

Sorry for the late reply - have you resolved the issue in the meantime? If not, could you please share the full contents of config/firebase.php?

I'm having the same issue, it's my first time trying firebase and this package. I have placed the service account json in the .env file as well. I haven't touched the firebase.php configuration.

I'm having the same issue, it's my first time trying firebase and this package. I have placed the service account json in the .env file as well. I haven't touched the firebase.php configuration.

I just realized that FirebaseChannel seems to be a class from https://github.com/laravel-notification-channels/ - could this perhaps be an error that's triggered from there?
Either way, it would be nice if you could show me some reproducible code that I can use to test this - in my local tests, everything seems to work just fine, and I would be happy if it's a bug in the package, because then I can fix it 🤞

I just realized that FirebaseChannel seems to be a class from https://github.com/laravel-notification-channels/ - could this perhaps be an error that's triggered from there?
Either way, it would be nice if you could show me some reproducible code that I can use to test this - in my local tests, everything seems to work just fine, and I would be happy if it's a bug in the package, because then I can fix it 🤞

In my case i didn't use FirebaseChannel, I'm still new to fire base so i just followed the documentation of the Firebase PHP Admin SDK
`
use Kreait\Firebase\Messaging\CloudMessage;
use Kreait\Firebase\Messaging\Notification;
$topic = 'topic';
$title = 'Title';
$body = 'Body';
    $messaging = app('firebase.messaging');

    $notification = Notification::create($title, $body);

    $message = CloudMessage::withTarget('topic', $topic)
        ->withNotification($notification) // optional
        ->withData($data) // optional
    ;

    $messaging->send($message);`

In my case i didn't use FirebaseChannel, I'm still new to fire base so i just followed the documentation of the Firebase PHP Admin SDK
`
use Kreait\Firebase\Messaging\CloudMessage;
use Kreait\Firebase\Messaging\Notification;
$topic = 'topic';
$title = 'Title';
$body = 'Body';
    $messaging = app('firebase.messaging');

    $notification = Notification::create($title, $body);

    $message = CloudMessage::withTarget('topic', $topic)
        ->withNotification($notification) // optional
        ->withData($data) // optional
    ;

    $messaging->send($message);`

Also, I tried not putting the FIREBASE_CREDENTIALS into the .env file to find out what error it'll give me. And it's the same error.

Also, I tried not putting the FIREBASE_CREDENTIALS into the .env file to find out what error it'll give me. And it's the same error.

I just tried in my test-laravel project and I'm sorry I can't confirm the problem. What wonders me is that you get the error names myproject as a project - if no other configuration is present, the default project is referenced as app. 🤔
Which Laravel and PHP version are you using? What happens when, instead of app('firebase.messaging') you try
use Kreait\Laravel\Firebase\Facades\Firebase;

// ...

$messaging = Firebase::messaging();

?
Just to be sure, please share the output of these commands in your terminal:
$ php -v
$ composer show

I just tried in my test-laravel project and I'm sorry I can't confirm the problem. What wonders me is that you get the error names myproject as a project - if no other configuration is present, the default project is referenced as app. 🤔
Which Laravel and PHP version are you using? What happens when, instead of app('firebase.messaging') you try
use Kreait\Laravel\Firebase\Facades\Firebase;

// ...

$messaging = Firebase::messaging();

?
Just to be sure, please share the output of these commands in your terminal:
$ php -v
$ composer show

I think I found my mistake. I actually specified the project name in the env file FIREBASE_PROJECT thinking that this will only let me specify the "Name" of the firebase project. Looking at the firebase.php config file I think I realize how it works now.
Thank you so much @jeromegamez for the very quick response!!

I think I found my mistake. I actually specified the project name in the env file FIREBASE_PROJECT thinking that this will only let me specify the "Name" of the firebase project. Looking at the firebase.php config file I think I realize how it works now.
Thank you so much @jeromegamez for the very quick response!!

Glad I could help, I hope the package can serve you well from here on! 🌺

Glad I could help, I hope the package can serve you well from here on! 🌺

I had the same issue but running php artisan config:cache fixed the issue.

Hello Everyone, I was just implementing the Laravel Firebase,
I am having confusion issue that what will be the firebase project, is it the title of the project ? or the project id from the credentials.json?
because I am having the same issue that
The Firebase project [Rehbr-App] is not configured.

Yes, it's the project ID from credentials file

hii, I am having the same issue, i run the above mentioned commands also, but not worked..

adding FIREBASE_PROJECT in .env still did not work for me

@liza-nt This issue is three years old 😅


Concrete composition

I really like to use (...) = (.) . (.) in anger, it seemed general enough to live in P.
I  don't know if this is useful to others or if it's ok to squat this namespace, just a proposal!
! @jystic @nhibberd @markhibberd @charleso

I'm obtaining from this. I don't have a problem with this, but at the same time I don't think I would use it.

Might want to consider inline pragmas as well.

I only really want (...), operators are spooky.

@thumphries, on your (...) operator, you do want a {-# INLINE (...) #-} pragma. Thats what @HuwCampbell was getting at.

I really like to use (...) = (.) . (.) in anger

Have you been using it? I'm weary of adding stuff to P before they've been proven useful is all - once something is in P it's unlikely that it'll get removed.

Have you been using it?

I usually spend 20 seconds adding a lambda when it happens (when I've changed the arity of something and ruined a pointfree expression)
Y'all sound suspicious though, happy to close

Y'all sound suspicious though, happy to close

I'm just allergic to adding functionality directly to shared libraries before they've shown value in a downstream project, I've seen too many "common" libraries turn in to sewers this way.
I think there's nothing wrong with having a util module or something in a specific project where you can try something out before it gets promoted.

Happy to be convinced otherwise though :)

x-composr, too large for github to display


gadgets: Update vmlinux.h

Update vmlinux and use core_fixes from BCC to fix some compiling errors.

I don't understand how core_fixes works, but the changes on tcpdrop look good to me.

Please add in the commit message what were the compilation errors.

I'm sorry I didn't record this. Doing so would require some manual work so I prefer to omit it this time.


Patch 2 - add onTextChanged callback

Adds onTextChanged callback and added a description of the function to the readme also

Hey @reggie3 ! thanks a lot for your contributions.


Nordic nRF52832 support

https://shop.pimoroni.com/collections/adafruit-uk-distributor/products/adafruit-feather-nrf52-bluefruit-le-nrf52832

Is there any progress on this subject?

Hi @mronus There has been no progress on this issue yet


phytochelatin metabolic process/ siderophore metabolic process/regulation of pentose-phoshate shunt

in GO
phytochelatin metabolic process (GO:0046937)
and
siderophore metabolic process (GO:0009237) (including ferrichrome)
are is_a is a secondary metabolic process
Is that correct?
If not I can open a CHEBI ticket
also regulation of pentose-phoshate shunt (GO:0043456)
is_ secondary metabolic process  (although pentose-phoshate shunt  itself, is not)

Why not ? Those are not primary metabolites, are they ?

I'm not sure. It seems odd.
scondary metabolism  is defined
GO:0019748    secondary metabolic process
Definition
The chemical reactions and pathways resulting in many of the chemical changes of compounds that are not necessarily required for growth and maintenance of cells, and are often unique to a taxon. In multicellular organisms secondary metabolism is generally carried out in specific cell types, and may be useful for the organism as a whole. In unicellular organisms, secondary metabolism is often used for the production of antibiotics or for the utilization and acquisition of unusual nutrients.
regulation of pentose-phoshate shunt (GO:0043456), for sure does not seem to fit under here.
and phytochelatin metabolism is conserved from yeast to metazoa, so that does not really seem to fit either?
Ferrichrome seems to fit OK:
Ferrichromes are any of a group of growth-promoting Fe(III) chelates formed by various genera of microfungi.
But I guess the definition is a bit hand-wavy...

Hello,
The definition of secondary metabolic process is correct and I do not see how we could improve it. However, the distinction between primary and secondary metabolism is not always obvious. Siderophores are generally (not to say always) considered as secondary metabolites (even if necessary for growth for many organisms/cells).
For regulation of pentose-phoshate shunt (GO:0043456), I agree with you Val, I would not consider it as a  secondary metabolic process. I think it is part of the pentose phosphate pathway which is essential and clearly a primary metabolism process.
Regards,
Marc.

So @ValWood is this a ChEBI issue ? Secondary metabolism is asserted in GO (and not coming from logical definitions).

So it seems that only the " pentose phosphate pathway " needs to be fixed. The others are OK.

also regulation of pentose-phoshate shunt (GO:0043456)
is_ secondary metabolic process (although pentose-phoshate shunt  <<<<<<<<, removed


Cannot read properties of undefined (reading '_emitter') when using HTTP WebHooks

Description
When using the Crisp library with the RTM_MODES.WebHooks mode, the following error is thrown:
TypeError: Cannot read properties of undefined (reading '_emitter') at \node_modules\crisp-api\lib\crisp.js:834:31
This error occurs in the _connectLoopback method of the crisp-api library, which is called by the _prepareBroker method. The problem appears to be that the this reference is not properly bound to the Crisp instance, which causes the _emitter property to be undefined.
Steps to Reproduce:

Initialize a Crisp instance with the RTM_MODES.WebHooks mode.
Call the on method to bind an event listener.
Wait for the error to occur.

Expected Result:
No errors should occur, and the event listener should be properly bound to the Crisp instance.
Actual Result:
The error cannot read properties of undefined (reading '_emitter') is thrown, and the event listener is not properly bound to the Crisp instance.
Potential Solution:
It appears that adding the following line of code var self = this; to the _connectLoopback method in the crisp-api library could fix the problem:
_connectLoopback : function() {
    var self = this;

    return Promise.resolve()
      .then(function() {
        // Assign emitter to loopback
        self._loopback = self._emitter;

        // Unstack broker bind hooks immediately
        self._unstackBrokerBindHooks(self._loopback);

        return Promise.resolve();
      });
  },

This would create a local variable self that references the current Crisp instance and can be used to access its properties and methods.
Version Information:
crisp-api version: 7.4.1
Node.js version: v16.19.0
Operating System: Windows 10
Additional Information:
**I'm not entirely certain that this is a proper solution, and there may be other underlying issues causing the error. Maybe it is the way i implemented the crisp-api into my service. It's also possible that adding the var self = this; line may have unintended side effects. But other functions are using the same line. **
I tried to followed these instructions. I would loved to just use this example, but i did not want to mix the express code with raw http server code.

Hello! Could you provide the full code leading to the error?

Fixed in v8.1.0, related to #58


finished.yaml

Hello to the arara team!
Thanks for creating & maintaining such a great tool, it's a vital part of my workflow both at work and at home :)
I'm currently working on a project that has a lot of images, and as a result takes quite a long time to produce a pdf (approximately 10 minutes); as such, I like to leave it running in the background. Rather than checking it regularly, I thought that I would create a little 'pop up' rule that tells me when it has finished. As such, I have the following (the following demonstrates a Windows implementation):
% arara: latex
% arara: latex
% arara: dvips
% arara: ps2pdf
% arara: finished

where finished.yaml looks like this:
!config
# long tasks can run in the background;
# this rule launches the finished.bat file
# which should bring up a DOS prompt
# author: Chris Hughes
# requires arara 3.0+
#
# Sample usage
#
# % arara: finished
#
identifier: finished
name: finished
commands:
- <arara> cmd /c start cmd /C finished.bat @{file}
arguments: []

and finished.bat contains
echo off
REM This is a small file to help me when compiling large
REM LaTeX documents, e.g the MST125 units; it is called
REM arara using the finished.yaml rule. It simply brings
REM a DOS prompt to the front of my screen telling me it is
REM finished.
REM This saves me from having to watch it
title finished! %1
For /f "tokens=1-3 delims=/ " %%a in ('date /t') do (set mydate=%%b-%%a-%%c)
For /f "tokens=1-2 delims=/:" %%a in ("%TIME%") do (set mytime=%%a.%%b)
echo finished working on %1
echo
for /l %%i in (1,1,3) do echo time stamp: %mytime%, %mydate%
pause

I don't think my implementation is ideal/optimal, but I wondered if it might inspire a better/more robust idea from the arara development team?
Chris :)
PS: this isn't really an issue, but I wasn't sure where it would best be placed...

Hello, Chris! :smiley:
I have good and bad news.
Good news: it is, in fact, quite straightforward to make arara trigger a message box using Java's JOptionPane. Something along these lines would do the trick:
!config
identifier: finished
name: finished
commands:
- <arara> @{ javax.swing.JOptionPane.showMessageDialog(null, "Yay, arara has finished the job!"); "" }
arguments: []

As showMessageDialog does not return any values, I have to force the evaluation to bring an empty string in the end as result, but it is just a technical detail, do not worry with it. :smiley:
When running this rule, you will get a lovely message box:

I haven't included the code calling the Swing UI manager to use the system look and feel, that's why this message box does not look so nice, but it does the job.
Bad news: The message box will appear before arara effectively runs any system command. This is a nuisance changed in the upcoming 4.0 branch; older versions evaluate expressions beforehand, then runs the resulting commands as a batch. From 4.0 on, each rule is evaluated and executed on the fly, which is, to some extent, along the lines of a REPL concept (read, eval, print, loop).
Sadly, there's no way of changing this behaviour in the current version of arara, but our upcoming version already solves this problem. For comparison, here's the very same rule ported to the new format (amongst other options of the new format):
!config
identifier: notify
name: Notify
authors:
- Chris Hughes
- Paulo Cereda
commands:
- name: User notification
  command: >
    @{
        javax.swing.JOptionPane.showMessageDialog(null, "Yay, arara has finished the job!");
        return true;
    }
arguments: []

I took the liberty of changing the rule name.
My test file is as follows (it calls the TeX engine and the notification):
% arara: tex
% arara: notify
Hello world!
\bye

When running 4.0, I get the following output:

As expected. :smiley: When clicking the OK button, we have the final output:

There we go.
Sadly, there's nothing much I could do with the current version. :cry: Thankfully, I am working pretty hard on the user manual (expect a huge list of improvements, corrections and features), so the new version will finally shine and you will be able to do wonderful things once again. :smiley:
Message to the team: (Chris, you are also part of the team, by the way) How do you like the idea of including a couple of UI methods to the rule context? Like the one Chris wants to use in this example. Maybe just one generic message box, where you can specify title, message body, width and type of message (information, error, warning, etc). To the Gitter chatroom, boys and girls! :smile:
All the best!
Paulo

Hi Paulo,
Thanks so much for the very speedy response! I knew that you would have
ideas, and they all sound great. There's no worries about implementing it
in the current version, and indeed no need to rush it into v4.0, I'll keep
an eye out to see what you all think about it :)
Feel free to close this issue if you like, now that the seed has been
planted.
Cheers
Chris
On Tuesday, June 16, 2015, Paulo Cereda<EMAIL_ADDRESS>wrote:

Hello, Chris! [image: :smiley:]
I have good and bad news.
Good news: it is, in fact, quite straightforward to make arara trigger
a message box using Java's JOptionPane. Something along these lines would
do the trick:
!configidentifier: finishedname: finishedcommands: -  @{ javax.swing.JOptionPane.showMessageDialog(null, "Yay, arara has finished the job!"); "" }arguments: []
As showMessageDialog does not return any values, I have to force the
evaluation to bring an empty string in the end as result, but it is just a
technical detail, do not worry with it. [image: :smiley:]
When running this rule, you will get a lovely message box:
[image: message]
https://cloud.githubusercontent.com/assets/302062/8186636/c3257fda-1421-11e5-8b4a-8948c0fcd22a.png
I haven't included the code calling the Swing UI manager to use the
system look and feel, that's why this message box does not look so nice,
but it does the job.
Bad news: The message box will appear before arara effectively runs any
system command. This is a nuisance changed in the upcoming 4.0 branch;
older versions evaluate expressions beforehand, then runs the resulting
commands as a batch. From 4.0 on, each rule is evaluated and executed on
the fly, which is, to some extent, along the lines of a REPL concept (read,
eval, print, loop).
Sadly, there's no way of changing this behaviour in the current version of
arara, but our upcoming version already solves this problem. For
comparison, here's the very same rule ported to the new format (amongst
other options of the new format):
!configidentifier: notifyname: Notifyauthors:- Chris Hughes- Paulo Ceredacommands:- name: User notification  command: >    @{        javax.swing.JOptionPane.showMessageDialog(null, "Yay, arara has finished the job!");        return true;    }arguments: []
I took the liberty of changing the rule name.
My test file is as follows (it calls the TeX engine and the notification):
% arara: tex% arara: notify
Hello world!\bye
When running 4.0, I get the following output:
[image: message]
https://cloud.githubusercontent.com/assets/302062/8187097/754d93b2-1424-11e5-9a2b-868b5886d526.png
As expected. [image: :smiley:] When clicking the OK button, we have the
final output:
[image: message]
https://cloud.githubusercontent.com/assets/302062/8187122/95480fe4-1424-11e5-9602-c4557237e83f.png
There we go.
Sadly, there's nothing much I could do with the current version. [image:
:cry:] Thankfully, I am working pretty hard on the user manual (expect a
huge list of improvements, corrections and features), so the new version
will finally shine and you will be able to do wonderful things once again. [image:
:smiley:]
Message to the team: (Chris, you are also part of the team, by the
way) How do you like the idea of including a couple of UI methods to the
rule context? Like the one Chris wants to use in this example. Maybe just
one generic message box, whDere you can specify title, message body, width
and type of message (information, error, warning, etc). To the Gitter
chatroom https://gitter.im/cereda/arara, boys and girls! [image:
:smile:]
All the best!
Paulo
—
Reply to this email directly or view it on GitHub
https://github.com/cereda/arara/issues/69#issuecomment-112475574.

Implemented. :smile:

Awesome :) can't wait to see it in action :) thanks for your time!
On Friday, June 19, 2015, Paulo Cereda<EMAIL_ADDRESS>wrote:

Closed #69 https://github.com/cereda/arara/issues/69.
—
Reply to this email directly or view it on GitHub
https://github.com/cereda/arara/issues/69#event-334755020.

A taste of things to come, just for you Chris. :smile:
We have showMessage now available only in the rule context, as it does not return any value (it simply displays a message). A possible implementation would be writing a notification rule, as we did in the previous comments; an alternative way of doing this would be exploiting conditionals and using another messaging feature available in the rule context, which is showOptions (in this case, I ignore the returned value from the message and simply inject the explict boolean value in order to end the conditional). My sample file would be:
% arara: pdftex until showOptions(2, "A message from our sponsors",
% arara: --> "Yay, arara has finished the compilation! Let's have
% arara: --> a nice and warm cup of coffee!", "Sure thing!"); true
Hello world.
\bye

When we run it:

After clicking the button, arara ends gracefully:

Yay! :smile:

Looks great, Paulo, thanks so much for putting it together :) can't wait!
On Friday, June 19, 2015, Paulo Cereda<EMAIL_ADDRESS>wrote:

A taste of things to come, just for you Chris. [image: :smile:]
We have showMessage now available only in the rule context, as it does
not return any value (it simply displays a message). A possible
implementation would be writing a notification rule, as we did in the
previous comments; an alternative way of doing this would be exploiting
conditionals and using another messaging feature available in the rule
context, which is showOptions (in this case, I ignore the returned value
from the message and simply inject the explict boolean value in order to
end the conditional). My sample file would be:
% arara: pdftex until showOptions(2, "A message from our sponsors",% arara: --> "Yay, arara has finished the compilation! Let's have% arara: --> a nice and warm cup of coffee!", "Sure thing!"); true
Hello world.\bye
When we run it:
[image: run1]
https://cloud.githubusercontent.com/assets/302062/8253506/23f76548-1667-11e5-9aa5-5595079f52ed.png
After clicking the button, arara ends gracefully:
[image: run]
https://cloud.githubusercontent.com/assets/302062/8253519/397f9d5e-1667-11e5-89c3-f141dbea6115.png
Yay! [image: :smile:]
—
Reply to this email directly or view it on GitHub
https://github.com/cereda/arara/issues/69#issuecomment-113503765.


Page not found

Hello,
i was just trying to download twitter extension and i received page not found error. Could you please take a look on it? Thank you

Hi,
where did you get the page not found error? I just tried to download the zip folder and it worked as expected.


[Feature Request] Create a PSBT-like flow for signing messages

Not sure if this is possible, but the idea is to create a user-friendly UX within Sparrow to let users create signed messages for their cold wallets. For example, with ColdCard you really have dig through their docs to figure out how to create the text file and how to format it so the device will recognize it and generate the signature. If Sparrow could abstract that and make a clean UI for signing messages that mimics the flow we're already used to for PSBTs, that would be a pretty cool feature-add -- especially if it could be abstracted such that it would work for any of the supported signing hardware devices.

I wouldn't mind doing this if there was a standard, but as far as I'm aware the Coldcard approach is proprietary. PSBTs otoh are a well documented standard (BIP174). Hopefully there will be a QR standard for message signing soon though.

I see, yeah that makes sense to hold of until there's a standard. Is that your next BIP? :)


Add Colegio Cristiano Genesis

Fixed the "domain not found" problem.

@JoshuaColell First stage of verification passed, official domain is genesis.edu.do as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@JoshuaColell Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Add devtoolsecrets.com website ?

Do you thing it's worth adding http://devtoolsecrets.com?
Why this interrogation? Because this is not only about Chrome but all browsers debuggers.
Depending on feedback, I will submit it after discussion where to insert the content.

Personally I wouldn't add it until the content is updated to reflect the
current tool states. The instructions it provides on finding things are old.
On Thu, Mar 17, 2016, 9:27 PM Thomas Gratier<EMAIL_ADDRESS>wrote:

Do you thing it's worth adding http://devtoolsecrets.com?
Why this interrogation? Because not Chrome only but all browsers debugger.
Depending on feedback, I will submit it after discussion where to insert
the content.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ChromeDevTools/awesome-chrome-devtools/issues/33

yeah i think it's a bit old at this point (unfortunately). it's a well done guide though


When the debug debugging, the node cannot be started

VSCode Version: Code 1.9.0 (27240e71ef390bf2d66307e677c2a333cebf75af, 2017-02-02T08:31:00.827Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

vscode-eslint
dbaeumer
1.1.0

Steps to Reproduce:
1.So much about the debug debugging, the node cannot be started
2.I have to restart the vscode to save it.

@katoongzhe please provide reproducible steps.
What do you mean by "debug debugging"?


Send scan output to file

Add a -o or similar option to send scan output to a file instead of STDOUT.

If they are using the console, would you prefer the file as plain text as it was in the terminal? As html but looking like the console? As html in the graphical way it is seen in the webui? As a pdf of any of those?
If they are using the webui would you like it to be in html? As a pdf?
Cheers

I think the output format should be what better matches the chosen execution mode — that is, plain text if using the console, or HTML if using the web UI. Not a big fan of PDF for either of those.

Awesome thanks! For the text output: what would you like to see for the URL? I have two values that I use everywhere: a friendly "display" UID, and also a clickable link that takes you directly to the github page for example. Since it's just plain text, I am going to only show the display one, but if there is something better we should do instead please let me know.
Eg: we could show:
display / link
or something, but I think it will be too wide.

Whatever makes it easier to retrieve the original file for validation will be best IMHO, so the URL would be my choice.

This is now implemented and released in v0.0.7
Please have a try and let me know what you think!


Added the step of subscribing to 'IoT Core' API

You will get a "No permission" error if continued without subscribing to "IoT Core" API

Thanks @prabch , I miss this in the readme.
However wee need to subscribing 3 APIs at least:

Authorization Token Management
Device Status Notification
IoT Core
Industry Project Client Service (for "Custom" project)

https://github.com/0x5e/homebridge-tuya-platform/blob/develop/src/core/TuyaOpenAPI.ts#L39-L57
Anyway, thanks again:)


Feature/Add subtitle [DO NOT MERGE]

I'm making this for discussion on the subtitle added onto the masthead.

@domfarolino What's a solution so that Router.js removes the secondary subtitle if it is not defined? Right now the secondary subtitle sticks if it's not defined. A solution is to define secondary_subtitle as an empty string but that would leave a large empty space between the bottom of the masthead and the text.
@noahbass Font suggestions?

Idk if its just when I pull it down or what, but route navigation does not work and the masthead text being more centered than all the way to the left (a recent change I made this week) was not kept. Do you see this too @noahbass @isiah-lloyd ?

I removed my directory and re-pulled. I ran npm install on master and everything looked good when dev was running. I checked out this branch, ran npm install again just in case, then ran dev and the masthead did not seem to be rebased with master(?) and consequently route navigation failed. I can try and merge master into this branch and fix the issues if you want.

@isiah-lloyd I fixed the routing issue. We just need to re-style the masthead so the h3 titles are smaller (presumably), and h1 and h3 have media queries on them. I'll let you take care of this and we can merge this. /cc @noahbass

@domfarolino Why did you change the styles? Was it required for the router changes? Because it messed up the styles but I can make a workaround if it was needed.

In master, inside the div.masthead (the entire masthead) we have have a div.masthead-title which is a div wrapping the title h1. In your branch, you added an h1, and 2xh3 which was good, but the internal div no longer had the class masthead-title. This meant the style was not affecting (or pushing the title(s) to the left anymore, and the font-size was a little off) so I made sure that the styles were more representative of how they are in master, while keeping the new masthead subtitle and location information that you added. Does that kinda make sense?

What media queries are needed? This is how it looks on mobile right now:
.

Yeah that looks fine. @noahbass how do you feel about serif. I'm starting to wonder if we should just go back to regular Jockey One. I feel like it might not look that bad.
@isiah-lloyd I think we should put some bottom-padding on the last element inside the masthead title.


how do u use spam open it wont work for me

the spam open box wont work when i put the name of the box in

ya i found it out


Apply typed Expression for (compare_by) feature

This PR applies the updated Expression API to (compare_by) feature.

@armiol @alexander-yevsyukov PTAL


2 different version of unplugin in yarn.lock

Describe the bug
Two versions of unplugin appeared in the file yarn.lock after I upgraded to<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>.
This seems to make running yarn build very slow, about (nearly 300s).
I don't know if this is the cause of the slow build. Looking forward to your feedback. Thank you.
$ yarn why unplugin

yarn why v1.22.19
[1/4] Why do we have the module "unplugin"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "unplugin"
info Reasons this module exists
   - Hoisted from "unplugin-auto-import#unplugin"
   - Hoisted from "unplugin-vue-components#unplugin"
info Disk size without dependencies: "164KB"
info Disk size with unique dependencies: "1.08MB"
info Disk size with transitive dependencies: "1.52MB"
info Number of shared dependencies: 8
=> Found<EMAIL_ADDRESS>info This module exists because "unplugin-auto-import#unimport" depends on it.
info Disk size without dependencies: "164KB"
info Disk size with unique dependencies: "1.08MB"
info Disk size with transitive dependencies: "1.52MB"
info Number of shared dependencies: 8
Done in 0.18s.

Reproduction
...
System Info
System:
    OS: Linux 5.18 undefined
    CPU: (12) x64 AMD Ryzen 5 5600G with Radeon Graphics
    Memory: 3.69 GB / 14.93 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.volta/tools/image/node/16.16.0/bin/node
    Yarn: 1.22.19 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 8.16.0 - ~/.volta/tools/image/npm/8.16.0/bin/npm
  Browsers:
    Chromium: 104.0.5112.79
    Firefox: 103.0.2

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

It's how packages works. You can use yarn resolution to force single version before every package get updated


Small bug in nt_xent_loss for SimCLR model

🐛 Bug
Adding eps is done twice, second is unnecessary in nt_xent_loss: first here and then again here.
We should change
 loss = -torch.log(pos / (neg + eps)).mean()

to
 loss = -torch.log(pos / neg).mean()

We are deprecating the self-supervised learning paper implementations in bolts and instead provided a VISSL integration in PyTorch Lightning Flash which can be used to train models using self-supervised learning algorithms. You can refer to the documentation here.


Add initial inbucket chart

What this PR does / why we need it:
Add the Inbucket which is an email testing application
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
N/A
Special notes for your reviewer:

/assign

@unguiculus thanks so much for your time to review. I made the changes you proposed and move from incubator to stable

/ok-to-test

/lgtm


[Question] difference iventory trim vs cable & connector?

what exactly speaks in favour of cables instead of using trims when cables are arguably more expensive? (requires diamonds and ender pearls vs trim wood only)

The inventory connector and trims connect all touching inventories. The inventory cable connector only connects the inventory it is attached to. The inventory trims only connect up to 16 blocks (by default), The inventory cables can go much further.


ui-grid 3.0 three-state sorting

New to version three is a the three-state sorting on the columns where the first click sorts ascending, the second click sorts descending and the third click turns sort off for that column.  Our users have found this confusing as no one knows what is supposed to happen when no sorting is selected.  In the version 2.x grid there was only two-state sorting i.e. it just toggled between ascending and descending with no state of “not sorted”.
We are using external sorting on the grid so the issue is that when turning sorting off the grid basically just stays the same because the external sorting is not going to do any work to randomly sort things just to show the user that their action caused a change.
I would like to have the ability to configure the grid to use the "old" two-state sorting functionality.

This would be better if I could just configure this at the top level in gridOptions. Conceptually I want to not support 3 state sort anywhere, and logically there is just one place I should do that. We are using externalSorting true.

In my opinion this one is not solved. We want that the whole grid acts in a two state sorting mode. If you add "suppressRemoveSort" to every column than once you have activated that sort you can never remove it, meaning you can not change to one other column to sort against that.
To reproduce just add  "suppressRemoverSort: true" to at least two columns and try to sort by only one column and changing between the two.

Agreed, this is not a full solution. My users find the 3-sort confusing and I don't think I can push out an update until the bug pointed out by @fkoehler is fixed or a good workaround is found.. :(

OK, I'm going to look at this to come up with a different set of options that in combination give some more flexibility.  The problem I think I have is that when people say "I want a 2 state sort" they're ignoring the fact that for most columns, upon opening the page, they are unsorted.  If we say once you touch a column it must stay sorted, then you're saying you cannot return the page to the way it was when you opened it.
I think that the function people want that isn't base functionality at present is a sortMinOneCol option, which when set allows the sort to be removed from a column, but only if another column has sort being added.
I think that I need to rejig the options to give that outcome.  I think that the new options would be:

sortAtLeastOneCol at the gridOptions level, which means that at least one column always has to have a sort
suppressRemoveSort at the column level, which means that this column cannot have it's sort removed - it always is sorted asc or desc

PaulL1, yes - but we always come in with one column sorted. The behavior you describe is like a radio choice, it can come in unchecked but once checked, you can't uncheck it - only check another. totally legit.

@httpete: maybe totally legit, except if I want to sort on another column, then I want the sort on this column to go away.  Hence three states - this column is sorted ASC, it's sorted DESC, or it's not sorted (presumably because, in your case, you've sorted on another column).

Hello Everyone,
We are also facing the same problem. As per our requirement, we need [asc/desc] sorting on column.
Please suggest the solution.

I have added the code that is using above suggested options 'sortAtLeastOneCol' and 'suppressRemoveSort' on plunker.
Here is the link http://plnkr.co/edit/dGnaoyhUtiwWCCgna2Xo?p=preview.
Please suggest the solution as we are in very crucial stage of our project.

@MaltiGumber I don't think those options have been added. For now I'd recommend just specifying
suppressRemoveSort: true
for every column that you need to.

Is there any good solution for removing 3 way sort, It is the most confusing feature.

this commit should address this issue.  https://github.com/angular-ui/ui-grid/commit/3eca46e99766eb0cc9f330948f68739dbf7d7bff


chore: change .github/workflows of project, created by cargo near new

checked on https://github.com/dj8yfo/workflows_test/actions/runs/12243985822/job/34154726255 and https://github.com/dj8yfo/workflows_test/actions/runs/12244281047/job/34155683767

diff -r old/.github/workflows/deploy-production.yml new/.github/workflows/deploy-production.yml
21c21
<           cargo near deploy "${{ vars.NEAR_CONTRACT_PRODUCTION_ACCOUNT_ID }}" \
---
>           cargo near deploy build-reproducible-wasm "${{ vars.NEAR_CONTRACT_PRODUCTION_ACCOUNT_ID }}" \
diff -r old/.github/workflows/deploy-staging.yml new/.github/workflows/deploy-staging.yml
44c44
<           cargo near deploy --skip-git-remote-check "${{ env.NEAR_CONTRACT_PR_STAGING_ACCOUNT_ID }}" \
---
>           cargo near deploy build-reproducible-wasm --skip-git-remote-check "${{ env.NEAR_CONTRACT_PR_STAGING_ACCOUNT_ID }}" \

@race-of-sloths include

@dj8yfo Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
Weekly streak is on the road, smart strategy! Secure your streak with another PR!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command. Alternatively, autoscoring [1,2] will be applied for this pull request
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths and receive a reward
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called


About page hero should have a max-height

Current: https://main--esri-eds--esri.aem.page/fr-fr/about/about-esri/overview
Live: https://www.esri.com/fr-fr/about/about-esri/overview

Does't need max-height so much as content | image sections need to be aligned better.
Wonder if it wouldn't be better to switch to grid and set up some template areas?

Does't need max-height so much as content | image sections need to be aligned better. Wonder if it wouldn't be better to switch to grid and set up some template areas?

I think there's two different issues that we're discussing, one is that in regular displays the grid is slightly different:
EDS:

Live:

The issue mentioned here is that on wider displays the height is limited on the live site:
EDS:

Live:

In any case, both issues should be addressed.


Use urllib's quote to encode user ids in urls #307

Fixes #307

Closing in favor of continued https://github.com/plamere/spotipy/pull/350


[React Native for X] Create cocoa application

Is it possible to use react native to target OS X apps? And if not are there plans to make it compatible?

React native currently extends Cocoa Touch.  It would be cool to see a Cocoa desktop bound layer :).
JG
:: sent from my mobile device ::

On Mar 26, 2015, at 16:13, Timur Carpeev<EMAIL_ADDRESS>wrote:
Is it possible to use react native to target OS X apps? And if not are there plans to make it compatible?
—
Reply to this email directly or view it on GitHub.

An engineer here at Facebook actually hacked up a prototype a while back - shouldn't be hugely difficult for someone to make it happen if you want to give it a go :)

On Mar 26, 2015, at 5:34 PM, Jay Garcia<EMAIL_ADDRESS>wrote:
React native currently extends Cocoa Touch. It would be cool to see a Cocoa desktop bound layer :).
JG
:: sent from my mobile device ::

On Mar 26, 2015, at 16:13, Timur Carpeev<EMAIL_ADDRESS>wrote:
Is it possible to use react native to target OS X apps? And if not are there plans to make it compatible?
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

Great! any plans?

I would love to be able to develop both Mobile (iOS/Android) and Desktop (Mac OSX, Windows) apps with React Native! @sahrens would that engineer be able to publish their progress? It would be great to get started on this development. Thanks!

Oh god I would more than love this.

:heart:

This would be a great addition.

+1

:+1:

+1

+1

+1

+1

@sahrens would that Facebook engineer be able to publish their progress? It would be great to get started on this development. Thanks!

+1

:+1:

:+1:

+1

+1

+1

Is this the approach Quip used to build their native apps? (https://medium.com/@btaylor/react-with-c-building-the-quip-mac-and-windows-apps-c63155c1531b) If so, did they home grow it?
It's clear there are lots of us who want to apply React to Mac apps. If there's any code or there that can be shared, please do!

Quip is using a web view, similar to Atom editor, which also uses/used to use React. I agree with what @sahrens said -- I don't think this is fundamentally difficult. There's a clear goal and path to get there if the people who want this feature wanted to collaborate on it.

+1

+1

+1

+1

+1

++++++++++++++++++++10000000000000

+1

+1

+1

+1

:+1:

+1

+1 some rough sample code would be a great staring point

+1

+1

+1

Being that this isn't really an issue with React Native per-say, and it's been agreed upon that such an effort would be a community effort, should this issue be closed? /cc @brentvatne

@jaygarcia - let's just keep it open as someone will probably create another issue for it if we don't :smile:

+1

+1

+1

+1

+1

:+1:

+1

+1

+1

+1

+1

+1

To pull this off requires a fairly intimate understanding of both React and Mac development. I'll hazard to guess that the vast majority of people in this conversation are comfortable with web development but not Mac development and would love a way of transferring their web skills to building native Mac apps. So, stating that this isn't "fundamentally difficult" is probably true for a particular audience, but I don't think this is that audience. Is anyone on the React Native team willing to put together a working starting point to jump start things?

I'm currently on https://github.com/ptmt/react-native-desktop. It's a "hacking weekend" kind of project, in a very early stage, though I hope it could change soon. If anyone have a strong demand in some desktop app, let me know on #react-native-desktop slack channel.

JS is a 1st-class citizen in OSX in terms of automation
http://tylergaw.com/articles/building-osx-apps-with-js
Also, don't forget about JavaScriptCore
https://developer.apple.com/library/mac/navigation/ (search for JavaScript)
This MacGap thing was popular at one point also.
https://macgapproject.github.io/

Oh right. Duh. Electron.

Awesome work @ptmt . I am extremely excited to see your project develop. Thank you!

👍

👍🏻

👍

Another substitute: https://github.com/gabrielbull/react-desktop

@therealmarv : https://github.com/gabrielbull/react-desktop uses Electron and React.js with some HTML & CSS to make the app look like a desktop application. However the discussion here is specifically to use React-Native, which executes native code and builds more performant applications than running a web browser (Electron).
@ptmt : https://github.com/ptmt/react-native-desktop is a great start and the only project I have found so far developing this functionality into React Native.

+1

+1

+1

+1
@ptmt it would be great to see your project mature

:+1:

https://github.com/ptmt/react-native-desktop

+1 , awesome

:+1:

Since there are no plans to add this to React Native core, and we're working now to clean up issues, please checking existing projects like react-native-desktop, or open an issue on Product Pains. Thanks!

+1

+1

+1

+inifinity

+1

+1


Remove bottom margin on clickable images

Here is current rule applied to img:
img {
	/* Margins for most elements */
	margin-bottom: 1rem;
}

A clickable image appeared with an empty space below it:

So I added a rule to prevent this.

Hello @3x, could you please have a look at this PR?

Thank you very much for the update! Much appreciated.
I made a minor grammatical change in https://github.com/xz/new.css/pull/60/commits/b8ec74eb3b931fbbdb84e400f4ac8b42f22d936f.


change

Committer: Kisung<EMAIL_ADDRESS>

@kisungyi92 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


[20.09] chromium: 88.0.4324.96 -> 88.0.4324.146

Motivation for this change
Backport of #111740.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

nix-build -A nixosTests.chromium succeeds.


Refactor Example Application Build Process

Remove generated files
Add missing WalletConnect dependency
Suggest usage of environment variable for Web3 provider
Resolve vulnerabilities in example app

I know you already merged this, but these changes look good to me 👍


Update template.html

In this link
https://cdnjs.com/libraries/jquery/1.11.3
I looked for the previous rendered version and his link seems to have changed.
I changed the

in the template.html file to

thanks

Already fixed.
Anyway, Thanks!

修改成 最新的https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js完美解决问题


Update docker-compose.yaml

Changed instrumentation example filename from server_uninstrumented.py to server_automatic.py as per open-telemetry/opentelemetry-python repository.
Refer to their pull request #3206 in https://github.com/open-telemetry/opentelemetry-python/pull/3206/commits/8ebf9974e3f1bd53759f4930e3a785107f6a94d4

It seems the automatic instrumentation with the example "server_automatic.py" does not generate any trace anymore, while other examples like "server_programmatic.py" work well.
For this cookbook 103, for now we can merge with server_automatic.py and track the issue.
I also noticed some other things need update (apm collector version, replace deprecated otlp_proto_http to use otlp, ...)


Add wasi.Errno type implementing the error interface

Hello,
I'm opening this issue to discuss changing the way error codes in https://github.com/tetratelabs/wazero/blob/main/wasi/errno.go are represented.
Instead of being simple uint32, how about making the a type implementing the error interface. This would be useful to return error codes from custom implementations of the wasi.FS and wasi.File interfaces, which are otherwise converted to the generic EIO code in functions like fd_read or fd_write, for example https://github.com/tetratelabs/wazero/blob/main/wasi/wasi.go#L258
The Errno type would be defined as such:
type Errno uint32

func (e Errno) Error() string { return fmt.Sprintf("wasi.Errno(%d)", uint32(e)) }

The error codes declared in errno.go would be declared as constants of the Errno type:
const (
  ESUCCESS Errno = 0
  ...
)

The signature of functions like fd_read can then be modified to return an Errno value instead of a plain uint32. I believe this should remain compatible with the current implementation since the underlying type remains unchanged, the use of reflection to discover the function signature would keep seeing return values of kind reflect.Uint32.
Let me know if you have any concerns about it or I have overlooked implementation details, I can send a pull request if we agree the change would be useful.

unless there is some implicit overhead added when using type Errno uint32 vs plain uint32, SGTM (especially using const)
@mathetake do you see any other things we should consider here?
aside: this file is also due some backfilling of docs similar to this regardless https://github.com/tetratelabs/wazero/pull/61/files

SGTM as well, thanks you @achille-roussel. Note that WASI code is not written by me but a contributor when this is project was hiatus period, so in anyway the WASI package needs refactoring! 🔥
I would really appreciate it if you could send a PR! Thanks in advance! 👍


Fix handling of scalars in cupy.r_

After https://github.com/cupy/cupy/pull/7651, cupy_r stopped working with floating point scalars, which were being interpreted as integer ones. This was due to the use of the positions of the values (integer values) as opposed to the values themselves.
For example:

See https://github.com/cupy/cupy/pull/7721#issuecomment-1688923731

/test mini

Could you check the CI failures?

/test mini

Could you check the CI failures?

/test mini

/test mini

The CI failure seems unrelated.

LGTM for the changes in _splines.py.

@andfoy LGTM! Thanks!


Remove FuncSimAndMemory and PerfSimAndMemory

Also changed c++ references to std::shared_ptr in memory/t/unit_test.cpp

All test cases successfully pass now.


components are appended after the gtk widgets

I'm learning rust so please be lenient with me...
When appending components to the gtk::Box together with other gtk::widgets, components are added at the end.
#[widget]
impl Widgets<MainWindowModel, ()> for MainWindow {
    view! {
        gtk::ApplicationWindow {
            set_title: Some("main window"),
            set_default_width: 600,
            set_default_height: 300,

            set_child = Some(&gtk::Box) {
                set_margin_all: 0,
                set_orientation: gtk::Orientation::Horizontal,

                // append = &gtk::Box {
                    // set_orientation: gtk::Orientation::Vertical,

                    append: component!(components.profile_view.root_widget()),
                // },
                append = &gtk::Paned {
                    set_orientation: gtk::Orientation::Horizontal,
                    set_position: 250,
                    set_shrink_start_child: false,
                    set_shrink_end_child: false,
                    set_start_child = &gtk::Button{
                        set_label: "sources",
                        set_hexpand: false,

                    },
                    set_end_child = &gtk::Paned {
                        set_orientation: gtk::Orientation::Horizontal,
                        set_position: 250,
                        set_shrink_start_child: false,
                        set_shrink_end_child: false,
                        set_start_child = &gtk::Button {
                            set_label: "items",
                        },
                        set_end_child: component!(components.item_view.root_widget()),

                    }

                },

            }
        }
    }
}

Leads to the main window looking like:

While I would expect

Which can be achieved by uncommenting the box wrapping around the append: component!(components.profile_view.root_widget()),.
My profile view  widget looks like
#[widget(pub)]
impl<ParentModel> Widgets<ProfileViewModel, ParentModel> for ProfileView
    where
        ParentModel: ProfileViewParent,
        ParentModel::Widgets: ProfileViewParentWidgets,
{

    view!{
        gtk::Box{
            set_orientation: gtk::Orientation::Vertical,
            set_margin_all: 5,
            set_spacing: 5,
            factory!(model.profiles),
        }
    }
}

Since root of the ProfileView is a vertical gtk::Box I would expect wrapping it with another vertical box to be idempotent in terms of view (ignoring margins, paddings, borders, etc...).

Factory for profile buttons:
impl FactoryPrototype for ProfileViewItem {
    type Factory = FactoryVecDeque<Self>;
    type Widgets = ProfileViewItemWidgets;
    type Root = gtk::Button;
    type View = gtk::Box;
    type Msg = ProfileViewMsg;

    fn position(&self, _index: &Rc<DynamicIndex>) {}

    fn update(&self, _index: &Rc<DynamicIndex>, _widgets: &ProfileViewItemWidgets) {}

    fn get_root(widgets: &ProfileViewItemWidgets) -> &gtk::Button {
        &widgets.profile_button
    }

    fn generate(
        &self,
        _index: &Rc<DynamicIndex>,
        _sender: Sender<ProfileViewMsg>
    ) -> ProfileViewItemWidgets {
        let mut graphemes = UnicodeSegmentation::graphemes(
            self.profile.name.as_str(),
            true,
        );
        let c = match graphemes.next() {
            Some(v) => v,
            None => "?"
        };

        let profile_button = gtk::Button::with_label(c);

        profile_button.add_css_class("flat");

        ProfileViewItemWidgets {
            profile_button,
        }
    }
}

That's a general problem in Relm4 that can't be really fixed. The thing is that the components are initialized after their parent so adding components to your widgets must happen later (all other things should still be in order).
Fortunately, you can work around this behavior by using the prepend method on the box. Simply replace append with prepend. That tells GTK to add the widget to the start so you don't have any issues with the order anymore :)

Prepend works for me.
Only thing I would like to see in this case is big red warning in a book in component's chapter.

I've thought about this issue a bit and actually found a way to solve this. If everything goes well, I'll release version 0.2 soon with a fixed version of the macro. Until then I'll keep this issue open.

Fixed in Relm4 v0.2


[Fix-14149][master] fix workflow always ready pause

Purpose of the pull request
close #14149
Brief change log
Verify this pull request

Codecov Report

Merging #14161 (b063fb0) into dev (8315279) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

:exclamation: Current head b063fb0 differs from pull request most recent head 366903d. Consider uploading reports for the commit 366903d to get more accurate results

@@             Coverage Diff              @@
##                dev   #14161      +/-   ##
============================================
- Coverage     38.41%   38.37%   -0.05%
+ Complexity     4461     4453       -8
============================================
  Files          1223     1223
  Lines         42549    42472      -77
  Branches       4716     4699      -17
============================================
- Hits          16345    16297      -48
+ Misses        24403    24377      -26
+ Partials       1801     1798       -3

Impacted Files
Coverage Δ

.../server/master/runner/WorkflowExecuteRunnable.java
10.33% <0.00%> (ø)

... and 65 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more