Multithreaded mode

--each-feature and --feature-powerset are great!  My only complaint is that they are slow.  bpytop shows that I'm never using more than one core when running cargo-hack.  It would be awesome if cargo hack could run multiple cargo processes in parallel, one for each feature combination.  Normally Cargo doesn't allow two processes to share the same build directory at the same time, so you could set CARGO_TARGET_DIR to a separate value for each.
There is a little contention for the crate cache, but my crude benchmark shows that I can build targets in parallel in about a quarter of the time it takes to build them sequentially.

I think this is a great idea. I would accept a PR to implement this.

I thought about it, but decided that I don't have the time to do it myself.

Hey, I was looking around and it seems that this issue hasn't been addressed in quite a long time. Wanting to know, if you are still accepting PR, for this issue.

@NishantJoshi00 you might want to try #175 that adds a way to get a list of commands out, and then you can run those commands separately for different processes. I'm using that command to run the processes on different machines even.

Interesting! I was able to come up with a similar solution for improving performance. I achieved parallelization with rayon and have a CARGO_TARGET_DIR pool to also leverage caching.
I was planning to raise a PR for this issue too.

This feature request is no longer as important as it was when I filed it, because rust 1.64.0 supports multitarget builds.  So you can now do something like cargo hack check --target i686-linux-android --target x86_64-apple-darwin --target x86_64-apple-ios ....  And cargo-hack happily passes all of those targets through to the cargo check command.  That provides plenty of parallelism if you have multiple targets to care about.  But it still doesn't address the case where the only parallelism comes from different feature sets.

Yeah, this is still useful and PR is welcome.

I think this is already mostly solved by https://github.com/taiki-e/cargo-hack/pull/253, right? If anything, this needs more extensive documentation so that people don't miss it.

Should this issue be closed then?

Closing in favor of improving --partition's documentation (https://github.com/taiki-e/cargo-hack/issues/260).


Fix old CLI documentation.

Update the documentation to use the new CLI commands.

:+1:

thanks @eddanger !


ValueError: Unsupported nproc_per_node value

May I ask if anyone encountered this error while running the file 'dist_train. sh'? I haven't resolved it yet. I don't understand why I made an error before assigning values to the variables in the file. If I receive an answer, I would greatly appreciate it

Hi, the config path and the number of GPU should be specified as arguments when calling dist_train.sh. You can refer to  https://github.com/chenhang98/BPR#train-the-network for details.

ok,thank you!


this message is preventing me from minting(no nfts were ever minted on collection), and when i try it stops me from minting

@vikiival
is it correct to use doWafiu here?
https://github.com/kodadot/nft-gallery/blob/12372c1c3aebf3c5015f2c89c0788a798365f52f/components/collection/drop/Generative.vue#L242
or should we use fxart worker?
if fxart worker
is it
a. /drops/allocate/${id}
b. /drops/do/${id}
endpoint?

@preschian
yep, so i though
ill do this one quick and dirty and create follow up to refactor as part of #9562
there is too much repetition in minting logic between variations
minting logic should be in 1 place

there is too much repetition in minting logic between variations
minting logic should be in 1 place

agree 👍🏻

since /do/:id need to find from table_ref https://github.com/kodadot/private-workers/blob/0cea59de48fad3d11cdf6b2a0920da30d72a7372/fxart/src/routes/drops.ts#L438-L441
It needs both of them. Is it possible?

@preschian  i DM'd you in telegram


add setproperties for Param

@lazarusA this should fix the problem you had setting Param fields with Setfield.jl in #34
julia> p = Param(2.0, units = "k", bounds = (1, 2))
Param{Float64, NamedTuple{(:val, :units, :bounds), Tuple{Float64, String, Tuple{Int64, Int64}}}}((val = 2.0, units = "k", bounds = (1, 2)))

julia> @set p.val = 1
Param{Int64, NamedTuple{(:val, :units, :bounds), Tuple{Int64, String, Tuple{Int64, Int64}}}}((val = 1, units = "k", bounds = (1, 2)))

Codecov Report

Merging #36 (0bb91ae) into master (8ad90e0) will increase coverage by 0.31%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
+ Coverage   72.25%   72.57%   +0.31%
==========================================
  Files           4        3       -1
  Lines         173      175       +2
==========================================
+ Hits          125      127       +2
  Misses         48       48

Impacted Files
Coverage Δ

src/param.jl
86.84% <100.00%> (+1.12%)
:arrow_up:

src/ModelParameters.jl

Continue to review full report at Codecov.

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

nice, thanks. This will also be helpful when doing dimension analysis for units.


How to copy the text in viewZone of inline-diff-editor?

version: 0.20.0
browser: Google Chrome 85.0.4183.121

version: 0.20.0
browser: Google Chrome 85.0.4183.121

Let's track in #1035

Let's track in #1035

get, thank you!


Allow seeing more columns than fit in the window

I'm querying tables that can have 100s of columns, I'd like to be able to see them.

@enricoberti, what do you think?

@romainr we don't really need this, it works for me: https://dl.dropbox.com/s/7xbzskee1mb60vs/Screenshot 2017-04-03 17.56.01.png?dl=0
@ubershmekel where exactly do you have this problem?

clicking on the 3rd icon will show the columns and allow to quick scroll
https://issues.cloudera.org/browse/HUE-5817 will improve the bottom horizontal bar UX

@enricoberti That is exactly the same location in which I can't see a scroll bar. Oh wait now I can.
@romainr which 3rd icon? Are you talking about expand results? That only expands the view for me and does not make it horizontally scrollable.
I've just now noticed hue-scrollbar-x-rail thanks to the @romainr screenshot. The custom dynamic scrollbars do not look like scroll bars to me. For comparison, this is what native scroll bars look like on Windows with Chrome: http://i.imgur.com/wa0pten.png
I'm guessing you guys modeled this scrollbar after mac scroll bars. Here are my complaints now that I can see them:

The scrollbars only appear when I'm hovering over the data, this makes it seem like there is no scrollbar when my mouse isn't hovering over the data.
The middle mouse button and drag does nothing which is the common trick to scroll horizontally when the UI is trying to prevent you from doing it.
The width, shape, and color of the scroll bar isn't what I'd expect on my platform.
The bar vanishes when I'm hovering on the white space between the data and the bar. This is very frustrating UX because when my mouse is over the data I see the bar, I move the mouse down to reach for the bar but then it vanishes only to show up again when I carefully position myself where the bar should be.
When the bar is all the way to the left, it's actually not touching any visible window boundary. So it makes me try to drag it further to the left and fail.

I realize you guys tried to make this bar capable of handling large data sets, but native scrolling is very hard to emulate. If possible, consider just using the native scroll bars when you can. At the very least don't hide the bars ever.

Thanks for the great feedback, we are currently looking at a getting a much easier/stable query result horizontal scrolling in the next release

It has been a while but it feels like these issues has been fixed now?


Link to Cicero documentation is broken in the Accord Project Technical Integration note below each template

Bug Report 🐛
Broken Redirect link to Cicero documentation from Templates under the Template Library.
Expected Behavior
Redirect the user to Cicero documentation
Current Behavior
The user is redirected to https://docs.accordproject.org/docs/cicero.html
The following screen is shown.

Possible Solution
As I understand, the link should redirect the user to https://docs.accordproject.org/docs/started-installation.html
Steps to Reproduce

Open<EMAIL_ADDRESS>Scroll to the bottom of the page, to the Techincal Integration section
Click on  Cicero documentation

Context (Environment)
I was reading through the project website and documentation in order to understand the project and came across this issue. Thought that someone else might run into the same issue as well.
Desktop

OS: Kubuntu 20.04
Browser: Chrome
Version: 89.0.4389.82 (Official Build) (64-bit)

If the proposed solution is correct, I would like to get assigned to this issue and fix it.

Thanks @dinuka-rp, you have the correct URL but this change isn't straightforward.
The site https://templates.accordproject.org is actually statically built by in the cicero-template-library (e.g. https://github.com/accordproject/cicero-template-library/blob/master/build/full-payment-upon-signature%400.10.0.html)
So we have two options:

Update all of the pages in the build folder in the cicero-template-library folder.
Add a redirect proxy in the documentation site so that the link will work again. This may not be possible with Docusaurus.

@mttrbrts, I wondered around the code-base and found out that there's a much easier way of changing this.
This can be fixed by changing this line of code and running the build command.
All pages in the build file will be updated then 😄
Shall I open this issue in the cicero-template-library project and send a PR to that repo?
Thanks for pointing out that that documentation was in a separate repository.

Unfortunately, I worry that it's not quite that easy. The files were all built by historical versions of the Cicero engine and rebuilding is likely to break other parts of the page if we rebuild with a more recent Cicero version. I'd love to be proven wrong!
Alternatively, you could just do a find/replace to be sure that we're only changing that line?
You're right about moving this issue though. Please close this issue and open a new one in cicero-template-library.

Oh, I see...
I'll try doing a find/ replace for now since you're not sure if it'll break and I'm also kinda new here. Don't want to be breaking the docs or the templates 😅.
I'm guessing that when the PR is merged, the built files will get deployed without trying to rebuild the entire project?
Is it ok to update this line as well?
Will close the issue here and reopen it in the cicero-template-library repo for now.


[FEATURE] Support cloudwatch cross account-cross regions

Required Basic Info

Accelerator Version:  1.30.2

Is your feature request related to a problem? Please describe.
While the operations account suppose to be center for operations, the lack of central monitoring is a big hurdle in the architecture. Aws support out of box this feature.
https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html#cross-account-and-AWS-organizations
Describe the solution you'd like
Implement cloudwatch permissions by default

We already do this :-).  This is set by global-options\central-operations-services\cwl: true, followed by the value cwl-access-level: "full", for example.  You can also allow for the security account by setting cwl: true for access from that account as well (you can only specify cwl-access-level in one of the two locations).  Then, in the post install instructions follow step 1v, as their is no API to turn on the multi-account selector drop-down.  Hope this helps!


Typo in documentation (template whitespace)

There is a small (but confusing) typo in this section of the template documentation:
With both trim_blocks and lstrip_blocks enabled...
...
But with both trim_blocks and lstrip_blocks enabled...

It seems likely that the first line (before the example) should read "With both trim_blocks and lstrip_blocks disabled."

Please just fix typos, no need to open an issue first.

It appears to be correct as written. It's talking about enabling those, shows what happens by default, then shows what happens when they're enabled.


Slow startup time

My config:
    use {
        'samodostal/is-prime-online.nvim',
        requires = { 'nvim-lua/plenary.nvim' },
        config = function()
            require('is-prime-online').setup {
                source = 'twitch',
                streamer_name = 'ThePrimeagen',
                refresh_interval_in_seconds = 60,
            }

            local timer = vim.loop.new_timer()
            timer:start(
                1000,
                20000,
                vim.schedule_wrap(function()
                    local status = require('is-prime-online').status()
                    if status == true and vim.g.PRIME_STATUS ~= 1 then
                        vim.notify '🟢 Prime is online!'
                        vim.g.PRIME_STATUS = 1
                    elseif status == false and vim.g.PRIME_STATUS == 1 then
                        vim.notify '🔴 Prime is offline.'
                        vim.g.PRIME_STATUS = 0
                    end
                end)
            )
        end,
    }

Packer returns:   Config for is-prime-online.nvim took 330.372094ms
Sometimes even neovim will hang for a couple of seconds.

Hey, sorry for replying late.
Where do you get the config startup time from? I am not that familiar with packer, and I couldn't find an easy way to get it. On my machine I didn't see a slow down when using this plugin, but if it the startup time is around 300ms I don't think I would notice it.
By the way, instead of creating a new timer that checks every 20 seconds, you can use the callback function like this:
require("is-prime-online").setup({
  source = "twitch",
  streamer_name = "thePrimeagen",
  refresh_interval_in_seconds = 20
  callback_on_live = function()
    vim.notify '🟢 Prime is online!'
  end,
})

To answer your first question: I used these 2 commands to "profile" the loading of plugins.
:PackerCompile profile=true
:q
$ nvim
:PackerProfile

To reply to your second point: in the callback_on_live, can you do the same "Prime went offline" message?
Currently, my config also tells me if Prime was online, but went offline.

Also, the second-slowest plugin in my config loads in 7ms, which is my status line. This does not include any of the other things that are done in my init.lua.

For now I've disabled a call of a function that checks if the twitch command has set-up authentication. It is now much faster (For me 0.4ms). I'll try to make the verification asynchronous in the future.


[release-4.12] OCPBUGS-21031: Bump golang.org/x/net to v0.17.0

Since CI is complaining
Go compliance shim [508] [][]: invoking real go binary
# golang.org/x/sys/unix
vendor/golang.org/x/sys/unix/mremap.go:42:10: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall.go:83:16: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_linux.go:1009:20: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_linux.go:2289:9: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/syscall_unix.go:118:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
vendor/golang.org/x/sys/unix/sysvshm_unix.go:33:7: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
G

Bumped go version to 1.17 from 1.16
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_prometheus-alertmanager/82/pull-ci-openshift-prometheus-alertmanager-release-4.12-test/1714231588763471872

/label backport-risk-assessed
/lgtm

/jira refresh

/jira refresh

/label cherry-pick-approved
/label qe-approved


Implemented integration for ai-verify-plugin and cookiecutter

See https://github.com/IMDA-BTG/aiverify-developer-tools/issues/12.
To test:
Install tool as usual.

Use 'ai-verify-plugin gp' command to generate new plugin
Use 'ai-verify-plugin ga' command to generate new algo component under the new plugin.
Update algo codes and use 'ai-verify-plugin testa' command to test the new algo'
Use 'ai-verify-plugin zip' command to create the plugin zip.
Make sure the zip includes the algorithm.

Feature is working as expected


Clarification needed for mkbootimg.mk instructions

copy the whole (matching to your device..) $(INSTALLED_BOOTIMAGE_TARGET): block from build/core/Makefile
my Makefile has multiple $(INSTALLED_BOOTIMAGE_TARGET):  blocks in it. How do I know which one to copy?
add: @/bin/bash $(ROOT_BOOT_BIN) $$PWD/$@ in the block of $(INSTALLED_BOOTIMAGE_TARGET): , AFTER the MKBOOTIMG line and BEFORE any AVB line
none of the $(INSTALLED_BOOTIMAGE_TARGET):  blocks in the file contain a MKBOOTIMG line.
there is a block called $(INSTALLED_VENDOR_BOOTIMAGE_TARGET): which contains a MKBOOTIMG line.

well that depends usually on e.g. the Android version and device vendor

It's lineageos 19.1, oneplus nord n200

check out https://github.com/sfX-android/android_vendor_extendrom/wiki/EXTENDROM_PREROOT_BOOT-NG


Change of text color in the navigation of expert mode

Context
Right now the text color in the expert mode nav is incorrect. Links should always be white, like everywhere else on expert mode, but in the nav the links are grey.
Design issue: https://github.com/CartoDB/design/issues/489#issuecomment-272486407
Current Result

Expected result

Closed by CartoDB/cartodb#14140
In production! :rocket:


Feature request : Scroll into view ?

When notes are collapsed in the Dendron panel, when you switch note, it does not necessarily open all of the tree in order to see the file AND it does not scroll the panel so that we could see the file we are in
Could it be possible to implement this ?

I just realized that IT IS implemented. I had a few issues … and I'm not able to reproduce this "bug", so … I don't know, I may have messed up somehow somewhere ?


[$250] [CRITICAL] [UX Reliability] Long pressing the comment reaction does not open the reactions modal the first time you do it

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.80-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @mountiny
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1717678892330039?thread_ts=1717676956.216859&cid=C049HHMV9SM
Action Performed:
Break down in numbered steps

Using iOS native
Open a chat with comments that have reactions on it
Long press the emoji reaction
The haptic feadback signals the click
Nothing happens
Long press once more
The modal with who posted those reactions opened

Expected Result:
Describe what you think should've happened
When you long press on the reaction, the modal with who posted those reactions should open
Actual Result:
Describe what actually happened
The first time it does not work and you only feel the haptic feedback but the click does not happen
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
You have to do it twice
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f70177dd3a98fd24
Upwork Job ID:<PHONE_NUMBER>875246255
Last Price Increase: 2024-06-06

Issue OwnerCurrent Issue Owner: @getusha

https://github.com/Expensify/App/assets/36083550/e5d46268-ea7b-44f1-a08b-637693ddb91e
its not really that visible in the video, but I do long press on the heart once and nothing happens

Proposal
Please re-state the problem that we are trying to solve in this issue.
We need to long press the emoji reaction twice to open it.
What is the root cause of that problem?
When we long press, it will call this function.
https://github.com/Expensify/App/blob/bb14c990ca1bbb654d68ebeb2ea95dd8afcb9b5c/src/pages/home/report/ReactionList/PopoverReactionList/index.tsx#L12-L16
The issue here is that the innerReactionListRef is null the first time we do a long press. That's because we render nothing when reactionListReportActionID or reactionListEmojiName is empty.
https://github.com/Expensify/App/blob/bb14c990ca1bbb654d68ebeb2ea95dd8afcb9b5c/src/pages/home/report/ReactionList/PopoverReactionList/index.tsx#L26-L36
Both of those states will be set when we do the long press. That's why the reaction list shows when we long press it the 2nd time because both of those states is already set on the first long press.
What changes do you think we should make in order to solve the problem?

Don't render null and let the popover component be rendered. So, let's remove this code.
https://github.com/Expensify/App/blob/bb14c990ca1bbb654d68ebeb2ea95dd8afcb9b5c/src/pages/home/report/ReactionList/PopoverReactionList/index.tsx#L26-L28
That code was added in this TS PR migration.

Hi! I'm going to work on that :)

@WojtekBoman can you please review the proposal from @bernhardoj and if the RCA/ solution makes sense, they can implement the PR

@bernhardoj Your proposal makes sense to me :)
This if statement was actually added here and wasn't present in the .js file.

if (reactionListReportActionID === '' || reactionListEmojiName === '') {
    return null;
}

This existing check ensures that the popover doesn't open if reactionListReportActionID or reactionListEmojiName is passed as empty. If we remove this check, then the popover will open with a kind of empty state if one of the above values is not available.

@ShridharGoel Is it possible to trigger opening the popover without these values? If so, I believe that it should be secured at a different level that doesn't affect innerReactionListRef value.

That can happen if the emoji name is not available for an emoji.

I'm not sure if the emoji name might be unavailable but if so we should move this checking logic elsewhere to fix innerReactionListRef.

@getusha can you please review the proposals also given @WojtekBoman feedback? thanks

@mountiny I won't be able to review this today, feel free to assign.

I don't know if it's possible for an emoji to not have a name, but I have updated my proposal to not show the list when the name is empty.

I don't think the root cause is correct @bernhardoj, the TS migration PR was merged 5 months ago and i am pretty sure this issue wasn't present while testing.

No proposals yet, bumping the bounty

I'm from Software Mansion and I'll work on this issue

@mountiny both @bernhardoj and @ShridharGoel were right in finding the root cause. Root cause is that on first render null is returned instead of BasePopoverReactionList. I agree with @bernhardoj that we should use isVisible prop on PopoverWithMeasuredContent to show the popover when it's ready instead of rendering null in parent component. I think that adding new state and using effect would introduce unnecessary complexity.

@mountiny PR is ready
cc: @getusha

merged

@kevinksullivan this is ready for payment
$500 to @getusha and to @bernhardoj

@mountiny @kevinksullivan I recently set up a payment to get paid in ND, what should be the process? Should I submit the request in ND and comment here when I did?

Yeah I believe that is the process, in the request you should link to the correct issue

Thanks! Requested in ND.

$500 approved for @bernhardoj

@getusha Have you been paid for this task?

Not yet @mountiny, working on the checklist.

Here's the summary:

@bernhardoj $500 (already paid in newdot)
@getusha $500 (newdot)

Both to be paid in NewDot so I think we can close this. no regression steps required as its quite specific issue

$500 approved for @getusha


After deployed, I got 403 forbidden

The deployment is successful, however when I tried to access the url, I got {"message":"Forbidden"}. Don't know what happened...

Can you post the results from zappa tail <stage>?

I had the same message when I undeploy and deploy back a project which I did certify using "zappa certify". The "Custom Domain Name" in the API Gateway did not have "Base Path Mappings".
I solve it by manually set "Base Path Mappings" to my "Custom Domain Name" manually in the AWS API Gateway console.
I hope this helps.

Thanks for the update, but this project is deprecated and discussion should be moved to Zappa core. Thanks!


Track whether transpiler has ran with a flag on the Loader

This fixes a bug where setting Traceur and/or Babel wasn't happening in
multiple-loader scenarios. Instead of using a closure variable set one
on the loader itself.
Picked a long name to avoid collision. Fixes #347

Sure that works great for me.

Ok, updated.

Would you like a release now as well?

It's not needed, thanks though.


Describe Pros/Cons of Kanidm

https://github.com/kanidm/kanidm

No apparent SAML support (needed for fk.adg ) 👎

Pros:

Complete ID-provider
Dockerized
Oauth2 support
RustC deliveres strong modern and safe code.

Cons:

No SAML support, would need to develop (rust ecosystem is lacking in this department, it seems)
Rust is time consuming to develop in.
Younger project (very modern, but lacks support of larger players in this field)

No SAML support pretty much killed this option for the PoC


Make GEH integration toggleable

Note: grabbable currently uses mouseout to track when queued hands are lost. Would need to rework handling in core to get this message across without GEH


[WIP] Adjust template creation for exit DAGs

#361 brings up a scenario in which Hera does not create a template that is required. This template is supposed to reference an onExit task. Hera is currently missing the logic that would allow it to create the template with a DAG reference that is required in order to run a DAG as an exitTask on any Hera created task. This PR is work in progress - it might not be the ideal solution to the problem. See #361 for a discussion on the issue, example generated YAML with missing and added template

Thanks for looking into this @flaviuvadan . I am on vacation this week. When I get back next week I can test this change out in my environment.

Thanks for looking into this @flaviuvadan . I am on vacation this week. When I get back next week I can test this change out in my environment.

Sounds great! Enjoy the time off 🌴

@ipl31, @Trollgeir and I paired on the solution for this and will open a different PR!


[ENH] Simple feature based clusterers

Implements simple feature clusterers. Includes:

Catch22Clusterer
SummaryClusterer
TSFreshClusterer

@hadifawaz1999 could you re-review this. Thanks.


handle realpath in makerootfs.sh sanely

We use realpath in makerootfs.sh to find the absolute path to various elements. Unfortunately, that has two shortcomings:

realpath is not available on all systems, mainly some Mac
even where realpath is available, we run it against a filename that may not yet exist. Some systems will resolve it, but others will error out.

This updates makerootfs.sh to handle those cases sanely. Instead of realpath the target file, we realpath the parent directory.
If realpath does not exist, we fall back to cd $parent && pwd -P, which gives the same result.

If realpath does not exist, we fall back to cd $parent && pwd -P, which gives the same result.

Why can't we always do this if it gives the same result?

Why can't we always do this if it gives the same result?

No idea. I guess we could. I will try it and update.

Latest changes are still a working build on my machine.

If realpath is removed then we do not need the commit. You might as well revert that commit.
commit bbce62550ec90a366c9828e6a5cc74ba71b1d7a9
Author: Pramodh Pallapothu<EMAIL_ADDRESS>Date:   Tue Jun 6 12:40:58 2023 -0700
Add coreutils package as prereq for MAC

Signed-off-by: Pramodh Pallapothu<EMAIL_ADDRESS>

That commit isn't in here.

I know I did that. But since you are removing realpath you might as remove the prerequisites of coreutils for the MAC.

No problem @zedi-pramodh ; done.


Build on Windows fail without including ctime library

Hello,
I am building the library with VC++2019 build tools and it crashes on a undefined identifier 'time' when compiling shellinford_fm_index.cc
Including  to the source solved the problem

Sorry for late.
I am busy now 💦
Please, wait a moment 🙇

@LucaCerina
This error occurred in an environment where multiple versions of Visual Studio were installed.
I resolved this error to use TotalUninstaller.
https://github.com/Microsoft/VisualStudioUninstaller/releases


Applied copy change suggestions

Reference doc with proposed changes: https://docs.google.com/document/d/1dn_tsG2eZ-wBPBdRay1lHeiCU6fjlDKehzIpTViiLxg/edit


Unable to start REPL

Just installed Visual Studio Code version 1.5.3  on Windows 10 then installed the elm language support extension version 0.8.1
When I try to run the ELM - REPL start command from the command pallete I get the following error:
Cannot read property 'stdin' of undefined so the REPL doesn't start.

The same problem. But the command "Send Selection" works as it should despite the error window.

I am also experiencing the issue.  VSCODE v1.7.2, Node6.5.0 and elm extension 0.8.3

You have to open a folder before trying to launch the REPL. I think a context is needed

I just ran into this on Windows 7, I don't understand what opening a folder does, or what that really means given this context. I bound a keyboard shortcut to open a new repl instance, and hit it while editing a file.
When I do that, I get the same error message the other users are getting. Would you mind expanding on your answer @OzTK ? Is this some kind of work-around for a known bug?
Thanks for your time!

I think that general assumption of the plugin is that work is done with folder opened in VSCode, and we don't really support single in-memory file.


Google home connection failure (MEGH-5132)

Answers checklist.

[X] I have read the Rainmaker documentation and the issue is not addressed there.
[X] I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
[X] I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

General issue report
I saw this problem in this forum but with no resolution.
I configure a dimmer ( with the example provided)  with esp rainmaker  and can see the device in the app , but when connecting to google home I got the error:
" no compatible device were found in your ESP rainmaker account"....
I check my only account with esp rainmaker, and try at different time with no success.
Any help ?
thks

Dimmer is not a standard device type supported in ESP RainMaker. You can see the complete list here. Also, Dimmer is not part of Google's list of supported devices either.


Yazi crashes on rename of long file after long press of del

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
yakuake 24.08.3
yazi --debug output
Yazi
    Version: 0.3.3 (VERGEN_IDEMPOTENT_OUTPUT 2024-10-09)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.3 (VERGEN_IDEMPOTENT_OUTPUT 2024-10-09)

Emulator
    Emulator.via_env: ("xterm-256color", "")
    Emulator.via_csi: Ok(Konsole)
    Emulator.detect : Konsole

Adapter
    Adapter.matches: KittyOld

Desktop
    XDG_SESSION_TYPE           : Some("wayland")
    WAYLAND_DISPLAY            : Some("wayland-0")
    DISPLAY                    : Some(":1")
    SWAYSOCK                   : None
    HYPRLAND_INSTANCE_SIGNATURE: None
    WAYFIRE_SOCKET             : None

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

Variables
    SHELL              : Some("/bin/zsh")
    EDITOR             : Some("nano")
    VISUAL             : None
    YAZI_FILE_ONE      : None
    YAZI_CONFIG_HOME   : None

Text Opener
    default: Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })
    block  : Some(Opener { run: "${EDITOR:-vi} \"$@\"", block: true, orphan: false, desc: "$EDITOR", for_: None, spread: true })

Multiplexers
    TMUX               : false
    tmux version       : No such file or directory (os error 2)
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file             : 5.46
    ueberzugpp       : No such file or directory (os error 2)
    ffmpegthumbnailer: 2.2.2
    magick           : 7.1.1-38
    fzf              : 0.56.3
    fd               : 10.2.0
    rg               : 14.1.1
    chafa            : No such file or directory (os error 2)
    zoxide           : No such file or directory (os error 2)
    7z               : 17.05
    7zz              : 24.09
    jq               : No such file or directory (os error 2)

--------------------------------------------------
When reporting a bug, please also upload the `yazi.log` log file - only upload the most recent content by time.
You can find it in the "/home/nho/.local/state/yazi" directory

Describe the bug
decided to rename a file with name 168 characters long, by putting cursor in the middle and pressing 'del' button. Yazi crashed when cursor reached end of the name.
  cannot remove a char from the end of a string
in rust:library/alloc/src/string.rs, line 1466
thread: main```

### Minimal reproducer

name on which yazi crashed:
`[2024-12-06]_[スタマス]　[_SESSION!_]　水瀬伊織　日焼け(ビキニ).mp4?download_token=28e2ca87cfd1c36e0508afb3eaa5ebfc1d972240430e60e005aeac74e52e6121`
Touch file with this name.
yazi - `r` - `end` - `del` - crash

### Anything else?

_No response_

### Checklist

- [X] I tried the [latest nightly build](https://yazi-rs.github.io/docs/installation#official-binaries), and the issue is still reproducible
- [X] I updated the debug information (`yazi --debug`) input box to the nightly that I tried
- [X] I can reproduce it after disabling all custom configs/plugins (`mv ~/.config/yazi ~/.config/yazi-backup`)

yes, it happens with Yazi 0.3.3 (adb14265 2024-12-07)

Please try https://github.com/sxyazi/yazi/pull/2010

Fixed. Thank you.


hostname_required? and validation of hostname is no longer needed.

Replaces #2216
Fixes #2137 (via deletion) :fire:
Followup to #2136
The initial 4dd2d13fc0a3 SVN History merged commit had:
validates_presence_of :name, :hostname, :ipaddress, :vmm_vendor
ipaddress_hostname_required? for vmm_vendor (vmware) was added in 79b0e8df33f6 for initial support for amazon EC2 hosts. We don't use EC2 hosts anymore so this can be removed.

@gmcculloug Please do the honors :bow: since you said I can delete it :heart:

:tada: Thank you!


smartSelect fix

This PR fixes #90589
The fix was trivial enough. Included some new unit tests.
Had to change the assertRanges function because of the pipe char. With the pipe, the new tests, which try to reproduce the exact scenario in the issue, were passing.
PS - this is my first PR for a OSS, ever... please forgive me for any mistake or misconduct.

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

Thanks


PB10 complains about using class name in static method

In a class like:
class K8sIPAM:
  _TIMEOUT_SECONDS = 1

  @staticmethod
  def example():
    print(K8sIPAM._TIMEOUT_SECONDS)

PB10, described as "Using class attribute that breaks inheritance", is raised, like:
PB10 Instead of K8sIPAM._TIMEOUT_SECONDS use self._TIMEOUT_SECONDS or cls._TIMEOUT_SECONDS with instance methods and classmethods, respectively, so that inheritance works correctly.

This is incorrect because "A static method does not receive an implicit first argument.": https://docs.python.org/3/library/functions.html#staticmethod

Hi, thanks for the report! Any interest in contributing a patch? I'd be happy to review it.
This is the code:
https://github.com/pantsbuild/flake8-pantsbuild/blob/58a1d448ad0ec5266ed4d872edd1f859aa298cbe/flake8_pantsbuild.py#L67-L79


Allow for canary deployments

Since we are using Linkerd, we can do traffic splits between versions of an application. It'd be nice to allow epinio users to leverage that.
https://linkerd.io/2.10/tasks/canary-release/

We are not using Linkerd anymore.


Use LOGIN_REDIRECT_URL setting in login view.

Proposed fix for issue #3, take 2.
The code uses the value of success_redirect if provided in the URL patterns.  If unset, the code falls back to the LOGIN_REDIRECT_URL setting.  If that it still not enough, it uses the default setting for LOGIN_REDIRECT_URL as per Django documentation.  Note that this breaks clients because the old default was /accounts/.

Thanks and sorry that it took so long.


Render Images from Data Sources Test Fix

Updates the test for completion on Render Images from Data Sources to be somewhat more strict.
And this has been tested on a local version of FCC.

closes #7110

Thanks for the PR! This test is moving in the right direction but it's a bit too specific and some of it is unnecessarily complicated. Some suggestions:

All your explicit quantifiers can either be removed ({1} is implied unless otherwise specified) or replaced with the ? shorthand.
Anywhere that your regex checks for a single or double quote needs to be able to accept either.
Anywhere you check for spaces needs to accept any whitespace and you need to make sure you allow whitespace in every place where it would be valid.
You can't assume the user will use += instead of __ = __ + __.
All your capture groups can be removed and simply be character literals.
You don't need to do things like (i|I) if you use the i flag at the end of your regex.

@ltegman
Updated RegEx
/html *(\+=) *\" *<(i|I)(m|M)(g|G) *(s|S)(r|R)(c|C) *= *'? *" *\+ *val.imageLink *\+ *" *'? *> *" *;/g

All your explicit quantifiers can either be removed ({1} is implied unless otherwise specified) or replaced with the ? shorthand.
Can you give specific place where this issues arises in the aforementioned(I think that's the right use of this word...) RegEx
I think I've fixed this is the RegEx at the top of this comment.

Anywhere that your regex checks for a single or double quote needs to be able to accept either.
The main issue I found trying to do this was that it would require checking if the begining quotes where double or single cause mixing them incorrectly won't work.

Anywhere you check for spaces needs to accept any white space and you need to make sure you allow white space in every place where it would be valid.
I've updated the RegEx to work with something like the following(In concern to white space.)

html      +=    "   <img   src =   '    "   +       val.imageLink   +   "   '   >       "    ;

You can't assume the user will use += instead of __ = __ + __
Uhm..... Ok, will have to look more into this piece.

You don't need to do things like (i|I) if you use the i flag at the end of your regex.
The issue I ran into with the 'i' flag was that, "val.imageLink" needs to be case-sensitive or else it won't actually render the images.

@M1kep Any updates on this?

@raisedadead @ltegman never responded to my inquiries/issues in my quoted response.

@M1kep maybe something like this would work:
 assert(code.match(/val.imageLink/g) && assert(code.match(html\s*(?:\+=|=\s*html\s*\+\s*)\s*(?:"|')\s*<\s*img\s+src\s*=\s*(?:"\s*'|'\s*")\s*\+\s*val\.imageLink\s*\+\s*(?:"\s*'|'\s*")\s*>\s*(?:"|')\s*;\s*/giwhere there is one case sensitive check for the variable val.imageLink and another case intensive regex to validate the HTML?

Can we get one of the @FreeCodeCamp/issue-moderators to QA

I would not accept this PR without a significant overhaul to the regex.  It may not be salvageable.

@M1kep Would you consider the comments and update this?

This PR not going to be accepted without changes as pointed in comments above.
Closing as stale as well, with no updates.
Feel free to open a fresh PR after addressing the comments.
Thanks!


Deprecated key & dynamic port warnings when starting minio service

Severity
Low (select if the issue doesn't significantly affect the user experience, like minor visual bugs)
Describe the bug
Got the following warnings when start the minio service. Version 0.2.4
minio_1          | WARNING: MINIO_ACCESS_KEY and MINIO_SECRET_KEY are deprecated.
minio_1          |          Please use MINIO_ROOT_USER and MINIO_ROOT_PASSWORD
minio_1          | API: http://<IP_ADDRESS>:9000 http://<IP_ADDRESS>:9000
minio_1          |
minio_1          | Console: http://<IP_ADDRESS>:46547 http://<IP_ADDRESS>:46547
minio_1          |
minio_1          | Documentation: https://docs.min.io
minio_1          |
minio_1          | WARNING: Console endpoint is listening on a dynamic port (46547), please use --console-address ":PORT" to choose a static port.

@morganekmefjord tagged you here since you already have a fix pending in #240

Merged into develop.

Scheduled for inclusion in the next release.

Now in master. Thanks @tian-cthit for bring this to our attention.


Porting the code to MS MARCO dataset

So I have ported this implementation of RNET on the MS-MARCO dataset, and the rouge-l scores after training are quite low compared to the reported scores on MS-MARCO in the RNET paper.
ROUGE-L dev scores
ROUGE-L train scores
What might have gone wrong?
Here is a link for my implementation reference: rnet-msmarco

Thank you very much. I would also like to know whether bucketing would improve the scores or just the training efficiency?
Also, does heavy padding [for example, if one query has only one para as its context, but another query has 10 para as its context, so I would have to pad the data of the first query to the length of extra 9*para-lengths] affect the scores much? I'm talking in terms of the MS-MARCO dataset which is why I'm explaining the situations.
Another thing I have observed in the code model.py Line#25 is that you trim the [context and question] indexs which are having zeros from the back using the cast->tf.bool->sum->maxlen procedure. So the embedding/word vector gradients that pass through the network have the dimensions equivalent to the actual para/ques length, and not the padded length, right? Please clarify.

# In the README.md, Detailed Implementaion, the last sentence.
The bucketing method can speedup the training, but will lower the F1 score by 0.3%.

I think in the beginning the speed is important, So the bucketing method is a good choice. Finally close it for more score.
The second. I am not so clear about your problem. I try to describe it.
the code from 24~34 is only for the performance. after it the batch will have max length in the batch rather than in the config.py.
Here is a another important thing about the gradients.
 _, (state_fw, state_bw) = tf.nn.bidirectional_dynamic_rnn( cell_fw, cell_bw, ch_emb, self.ch_len, dtype=tf.float32)

When you use bidirectional_dynamic_rnn, There is a parameter sequence_length.
# the comment about it from dynamic_rnn function.
sequence_length: (optional) An int32/int64 vector sized `[batch_size]`.
  Used to copy-through state and zero-out outputs when past a batch
  element's sequence length.  So it's more for correctness than performance.

correctness  is a key word. The meaning is the final state is the last nonzero position depending on the sequence_length parameter. So the padding will not affect the gradients.


Changed r.now() to self.r.now() because r is undefined otherwise

This was causing a crash the first time the sessions we being cleared.

👍🏻


Create 'CMD + Shift + 4 + Space Bar key' screenshots of Gravity

The ultimate aim will be to create a m x n size grid of screenshots in README.md to showcase of different pages in Gravity and put them inside a folder called Screenshots.
Different pages which you can choose are,

Any post on Gravity
Main page of Gravity
About Page
Category Page

Can i solve this?

Aur bhai kyal haal chaal

Gravity is awesome!

As awesome as Pixel!!


Connected devices always show as not connected

Mobile Device Environment
Provide a list of operating systems on which this issue is relevant.

Device:Android
OS: 13

Application Environment
Provide information about your development environment:

React Native version: 0.66.1
RN Bluetooth Classic version: 1.60.0-rc.29

Describe the bug
If I do
RNBluetoothClassic.getBondedDevices()
I get back all the bonded devices.
 Even though Android shows I have a couple devices connected
Could I have something wrong in my manifest that it cannot see connected devices?
<uses-permission android:name="android.permission.BLUETOOTH"/>
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN"/>
<uses-permission-sdk-23 android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.BLUETOOTH_SCAN"/>

Suggest reading the docs:
Bonded = Bonded
Connected = open Serial connection
Connected does not mean what you think it means.

Thank you. Is there anyway to determine if the phone is already connected to a device?

That all depends what you mean by connected?  But the short answer is no.
Only one RFCOMM/serial connection can be opened to a device at one time, so if you have a serial connection open with a device from another application or other library, then there is no way to pass that off to this library.
If you're talking about connected in terms of being connected through one of the other profiles, then no, this library was specifically designed for RFCOMM communication, not any of the other profiles to which the android system would connect behind the scenes.


python310Packages.advantage-air: 0.4.1 -> 0.4.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.advantage-air is: "API helper for Advantage Air's MyAir and e-zone API"
meta.homepage for python310Packages.advantage-air is: "https://github.com/Bre77/advantage_air"
meta.changelog for python310Packages.advantage-air is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.2 with grep in /nix/store/8mjnzm6kfyxx0x7086d68y39mkcspawi-python3.10-advantage-air-0.4.2
found 0.4.2 in filename of file in /nix/store/8mjnzm6kfyxx0x7086d68y39mkcspawi-python3.10-advantage-air-0.4.2

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
home-assistant-component-tests.advantage_air
python310Packages.advantage-air
python39Packages.advantage-air

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8mjnzm6kfyxx0x7086d68y39mkcspawi-python3.10-advantage-air-0.4.2 \
  --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 python310Packages.advantage-air https://github.com/r-ryantm/nixpkgs/archive/bb6c3ed3fc4eeae3d94753e881c1bbcdd641e7ad.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8mjnzm6kfyxx0x7086d68y39mkcspawi-python3.10-advantage-air-0.4.2
ls -la /nix/store/8mjnzm6kfyxx0x7086d68y39mkcspawi-python3.10-advantage-air-0.4.2/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

1 package failed to build:

home-assistant-component-tests.advantage_air

2 packages built:

python310Packages.advantage-air
python39Packages.advantage-air

Maintainer pings
cc @JamieMagee for testing.

Superseded by #206612

Superseded by #206612


Plain text log

Avoid ansi color escape in log file.

Hi, this is expected behavior as I have plans to implement a simple log viewer within Yazi, which requires these color codes

Oh, is that so. Yeah, that makes sense.


Support --argumentfile case-insensitively and document that shortening it does not work

While implementing #2420, I noticed that --argumentfile option doesn't work case-insensitively like --ArgumentFile similarly as other long options do. Additionally using shorter but unique variants like --argumentf don't work either. Both of these limitations are due to --argumentfile being handled using its own logic before using Python's getopt that actually handles argument parsing. Case-insensitivity support is pretty easy to add to our own code, but handling shortened variants is not. My plan is to enhance this situation as follows:

Support --ArgumentFile style.
Document in the User Guide that --argumentf style doesn't work.
If possible/easy, explicitly check that --argumentfstyle wasn't used.

Tasks listed in the original description done by the commits above. This issue is done.


Bugfix/402 e2e nightly failures

Summary
Fixes for nightly e2e tests against public site
Description for the changelog
closes #402
Other info
There is a new "parent" command that should be used in the before function for each e2e test suite, cy.setupTest().
This command will browse to the home page and clear the session storage (thus resetting state and "logging out").
Additionally, handling the v2 warning toast notification is done here so that when it's removed, we only have to update it in one place.

Could we also revert one of my inexpert changes that is not needed?
In td.vue/browserstack.nightly.json
change line
-        "parallels": "1",
to
+        "parallels": "5",
Many thanks, really good to see all this going into the tests

Could we also revert one of my inexpert changes that is not needed? In td.vue/browserstack.nightly.json change line - "parallels": "1", to + "parallels": "5",
Many thanks, really good to see all this going into the tests

Done! That's a logical debugging step.  Glad you brought it up, the tests should run a bit quicker now too! :)


Restructure search from model - Backend.

@sumathi-thirumani-aot - Noticed this is over a year old - is this good to be closed due to inactivity? Or has this already been resolved?

No please. This is one area where we can optimize.


using md5 is not FIPS 140 compliant (for cache paths)

Environment
NodeJs version: v22.11.0
jiti@latest
Reproduction
(please see bug details referring to the FIPS compliant image described)
Describe the bug
I have a requirement to build my application in a FIPS compliant container, and currently that is not possible due to the use of the deprecated md5 crypto algorithm. Since, from what I can tell, this is used only for creating version hashes, I believe it'd be benign to switch to a more modern algorithm.
Container base image: Chainguard's node-fips image built with Node v22 (see here) which ships with the OpenSSL FIPS provider.
Step: 1:
Create a Dockerfile that pulls the Chainguard node-fips image, copies this project's source files into the image, and runs the test command
Step 2: Run the docker build . command
That results in an error that looks like this:

Error output
74.45 Error: error:0308010C:digital envelope routines::unsupported
74.45     at new Hash (node:internal/crypto/hash:79:19)
74.45     at createHash (node:crypto:139:10)
74.45     at md5 (/app/node_modules/jiti/dist/jiti.js:1:247005)
74.45     at opts.transform.Object.assign.Object.assign.Object.assign.legacy (/app/node_modules/jiti/dist/jiti.js:1:251648)
74.45     at transform (/app/node_modules/jiti/dist/jiti.js:1:252178)
74.45     at evalModule (/app/node_modules/jiti/dist/jiti.js:1:255358)
74.45     at jiti (/app/node_modules/jiti/dist/jiti.js:1:254371)
74.45     at /app/node_modules/tailwindcss/lib/lib/load-config.js:52:30
74.45     at loadConfig (/app/node_modules/tailwindcss/lib/lib/load-config.js:54:6)
74.45     at getTailwindConfig (/app/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:71:116)
74.45     at tryRunOrWebpackError (/app/node_modules/next/dist/compiled/webpack/bundle5.js:28:312989)
74.45     at __webpack_require_module__ (/app/node_modules/next/dist/compiled/webpack/bundle5.js:28:131165)
74.45     at __nested_webpack_require_153728__ (/app/node_modules/next/dist/compiled/webpack/bundle5.js:28:130607)
74.45     at /app/node_modules/next/dist/compiled/webpack/bundle5.js:28:131454
74.45     at symbolIterator (/app/node_modules/next/dist/compiled/neo-async/async.js:1:14444)
74.45     at done (/app/node_modules/next/dist/compiled/neo-async/async.js:1:14824)
74.45     at Hook.eval [as callAsync] (eval at create (/app/node_modules/next/dist/compiled/webpack/bundle5.js:13:28858), <anonymous>:15:1)
74.45     at /app/node_modules/next/dist/compiled/webpack/bundle5.js:28:130328
74.45     at symbolIterator (/app/node_modules/next/dist/compiled/neo-async/async.js:1:14402)
74.45     at timesSync (/app/node_modules/next/dist/compiled/neo-async/async.js:1:5027)

Additional context
I attempted to open a PR to change the utility to use the sha256 algorithm, but I do not appear to have permissions to create a branch. I think this would be pretty simple to change the md5 function to sha256 and use that argument in the Node createHash function.
Logs
No response

It is not a security matter for jiti's usage of md5 in cache entry paths and a false-positive in that tooling..
I would love to change it but we have to wait until there is another change in jiti that would require invalidating cache version (otherwise we add extra cache files to (78M users) x (number of jiti cached files in their system!)

Mainly legacy decisions in jiti and if we change it will cause stall caches for lots of files for lots of users which makes chage tricky.
If we can auto detect that env, we can smartly switch though.


Accept PR 16 and work out merge conflicts for latest alpaca

From PR https://github.com/Islandora-Devops/isle-dc/pull/16
Add this to the README.md
Depends on https://github.com/Islandora-Devops/isle-alpaca/pull/3

Comment in the build sections for and point to ^^ once it's merged (or pull it in and point to a local copy on disk).

## How to Test

From your isle-dc folder:
- `docker-compose down -v`
- `rm -rf codebase && mkdir codebase` to clean the codebase
- If you haven't already done so, `(cd scripts; ./generate_keys.sh)` to generate keys
- `docker-compose up --build -d`
-  `docker exec -it isle_dc_proto_solr bash -c "solr create_core -c islandora"`
- `docker exec -it isle_dc_proto_php bash -c "sh /scripts/islandora/install-islandora.sh"`

You can test by ingesting a repository item, giving it a media and tagging that media as an original file.  This should trigger derivatives.

Admittedly, there's still something super wonky with karaf/camel uploading derivatives, and sometimes you get uploaded files of 0.  I'm still working through that, but you can at least see that the whole system is functioning, albeit a bit impaired.

PR merged and accepted. Closing Ticket.


Validation set for the early stopping

Hi,
Thanks for your great work! I have a question about the early stopping. According to your paper, 200 tumor patches (abnormal samples) were used as the validation set. In your code, I noticed that the sum of the adversarial loss and reconstruction loss of the validation set was used as the sign for early stopping. I am a little confused why the loss score of abnormal samples in the validation set instead of the AUC score of validation sets with both abnormal and normal images available is used for early stopping.
I am looking forward to your reply. Thank you!

Hi!
Thanks for the question. We used loss on the validation set for earlier stopping to avoid overfitting on the train data (with the given set hyperparams). And then, we use ROC AUC to choose the best hyperparameters. However, you are right,  ROC AUC  may also be used for earlier stopping.


jail: Add -D option to keep git history

While it's useful to clone without history by default, sometime you
need the full one. For example if you rely on git tags to generate an image.
Signed-off-by: Emmanuel Vadot<EMAIL_ADDRESS>

Do not forget the manpage :)


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade" workflow

Currently failing due to the bad installation during python template test. It first tries installing cdk8s==1.0.0b51, cdk8s-plus-22==1.0.0b4, and constructs==3.3.152 - these are correct / match the current package.json. But cdk8s-plus-22==1.0.0b4 "requires cdk8s==1.0.0.b50, constructs<4.0.0,>=3.3.152, jsii<2.0.0,>=1.34.0, publication>=0.0.3" - so the cdk8s version is conflicting. I think this should be fixed by https://github.com/cdk8s-team/cdk8s-plus/pull/20


Ignore min_keyword_length  on trigger character and manual show

Make sure you have done the following

[X] I have updated to the latest version of blink.cmp
[X] I have read the README

Bug Description
When settingmin_keyword_length to any value that isn't 0 (In my case i set it to 3). show_on_trigger_character stops working. There is no error it just start waits for me to type 3 characters before showing me the completions. Imo, it should ignore min_keyword_length.
Relevant configuration
completion = {
    trigger = {
        show_on_trigger_character = true,
    },
},

sources = {
    min_keyword_length = 3,
},

neovim version
NVIM v0.10.2
blink.cmp version: branch, tag, or commit
main

Update: It also ignores show keymap.
keymap = {
    ["<C-space>"] = { "show", "show_documentation", "hide_documentation" },
},

While trying to replicate the completion behavior I'm used to in cmp, I ran into this issue as well. Since the 'bug' label was removed, I'm assuming blink's min_keyword_length just means something different than it does in cmp -- it's the minimum keyword length to even look at a source rather than the minimum keyword length for auto-completion.
In order to get the behavior I need, I made a PR with two changes that should make things a little more flexible in general:

completion.menu.auto_show can now be either a function or a constant boolean. This gives users the ability to make more complex decisions about whether to automatically show completions.
blink.cmp.Context contains a new field -- update_type. This field provides additional information on what triggered the update. This allows users to vary behavior when completion is manually triggered (as opposed to being automatically triggered by keywords or trigger characters).

So, for example, to automatically show completion only for trigger keys (and not when typing anything else), you could do:
completion = {
    menu = {
        auto_show = function(ctx, list_items)
            return ctx.update_type == "auto_show_trigger_char"
        end,
    },
},

To enforce minimum keyword lengths for all automatic triggers but still allow manual triggering, you could do:
sources = {
    min_keyword_length = function(ctx)
        return ctx.update_type == "manual" and 0 or 3
    end,
},

@mkblast Does this solve your use-case as well? If not, could you expand on exactly what you're trying to do?

Hi,
I face the same issue.
@guill, I can't test your snippet cause if I checkout to main I got some non-related blink.cmp.fuzzy.download.git not found errors.
But in any case, I don't think that defining a custom behaviour is the correct approach here since is too much low detail for an option that already exists and isn't working as expected.
If show_on_trigger_character is set to true, then it should show the menu when the trigger character is inserted regardless the min_keyword_length value.
Is there a use case for enabling show_on_trigger_character and respecting a min_keyword_length non-zero value? I've been thinking about it, and I don't think it makes much sense.

You can now do this via
function(ctx)
	return ctx.trigger.kind == 'manual' and 0 or 3
end

Eventually this will become the default behavior

Thanks for implementing this feature.
I think it's better if I leave this issue open until it is made the default in a new release.


Pages (Sometimes) Not Loading on Netlify

Description
Creating a site for a client using Gridsome, really liking it so far.
But I'm hitting a problem with navigation.

Entering the site from any root page works fine and all navigation works fine.

https://covid-protocols.netlify.com/
https://covid-protocols.netlify.com/about
https://covid-protocols.netlify.com/quick-links

Entering via a subpage locks you to that "subdirectory"

https://covid-protocols.netlify.com/protocols/01-clinical-course-prognosis-and-epidemiology - Cannot navigate to About/QuickLinks or Home
https://covid-protocols.netlify.com/addendum/01-pal-care - As above but also cannot navigate to the Protocols pages.

The URL in the address bar still updates properly, and this issue does not occur locally.
I did also turn on config.mode('development'); in my gridsome.config.js to see if Vue was giving me hydration warnings, but I don't see any. I was particularly concerned about this idea since my content is generated via Google Docs, so I also ran a test with removing all of the queries and data and just having it as a few static pages, with the same results: https://5e860a5999b34f000640d4eb--covid-protocols.netlify.com/
A couple of file snippets:
gridsome.server.js
  api.createPages(({ createPage }) => {
    createPage({
      path: '/protocols/:id',
      component: './src/pages/protocols/Protocol.vue'
    })
    createPage({
      path: '/addendum/:id',
      component: './src/pages/addendum/Addendum.vue'
    })
  })

netlify.toml
[[redirects]]
  from = "/*"
  to = "/index.html"
  status = 200

Steps to reproduce
I'll work on making a demo project now, but in the hopes of this being a quick fix, I'm hoping to get some thoughts / eyes on this in the interim.

Looks like the problem, hilariously, did seem to be non-semantic HTML!

Looks like the problem, hilariously, did seem to be non-semantic HTML!

What was the non-semantic HTML?


MINOR: gradle wrapper should handle directories with spaces

If attempting to build the project from a directory with spaces in its name and gradle-wrapper.jar is missing, the script will fail to download a new one because the "if" condition will break because $APP_HOME will resolve to multiple strings. Protecting $APP_HOME with quotes fixes the issue. Tested by deleting gradle.wrapper and trying to build.

Hmm, we updated an auto-generated file instead of the code that generates the file. I attempted to fix the latter here https://github.com/apache/kafka/pull/9849. @gwenshap please take a look and see if that fixes your issue too.

Hmm, we updated an auto-generated file instead of the code that generates the file. I attempted to fix the latter here https://github.com/apache/kafka/pull/9849. @gwenshap please take a look and see if that fixes your issue too.


Rename field portalIP -> clusterIP

portalIP was deprecated in favor of clusterIP.
@mnagy @bparees PTAL

lgtm

green tests


Kp nomspace integrate

Description
I've integrated the ens with nomspace so users can see their nom domain on this site.
Type of change

[ ] New feature (non-breaking change which adds functionality)

Checklist:

[ ] I have performed a self-review of my own code

@prestonkevin fix merge conflicts.
And make sure that we are working on symmetric-v2 branch only for v2 interface. So when you make a new branch, please branch off of symmetric-v2

@prestonkevin fix merge conflicts.
And make sure that we are working on symmetric-v2 branch only for v2 interface. So when you make a new branch, please branch off of symmetric-v2

Got it

fixed the merge confict


Usage with React

Hi,
I was trying to have my React application connect to Action Hero server. I tried using both the javascript file generated (in https://github.com/evantahler/actionhero-tutorial/tree/master/public folder) and the action hero client (https://github.com/evantahler/actionhero-client). Can you provide a simple example of how a react component can talk to the action hero server?
Thank you!

Sorry, not an issue, have got it working now.

Cool.
Note that this project is for node.js - node.js serers, not for the browser.


Reimplement create queues page to use DaisyUI

When a user create a queue, that user need to be added to "authorized user" in queue(model).


Fix 'safe' write concern option deprecation

The following warning is appearing in the build output:
[DEPRECATED] The 'safe' write concern option has been deprecated in favor of 'w'

It would be good to fix this to improve the signal-to-noise ratio in the test output.

It looks as if we need mongoid >= v4.0.0 to fix this: https://github.com/mongodb/mongoid/blob/master/CHANGELOG.md#400.

I don't see this warning in the branch that upgrades us to using Mongoid 3 - PR #929.

PR #929 has been merged and I'm no longer seeing this warning in master so I'm closing this issue.


[SPARK-9419] ShuffleMemoryManager and MemoryStore should track memory on a per-task, not per-thread, basis

Spark's ShuffleMemoryManager and MemoryStore track memory on a per-thread basis, which causes problems in the handful of cases where we have tasks that use multiple threads. In PythonRDD, RRDD, ScriptTransformation, and PipedRDD we consume the input iterator in a separate thread in order to write it to an external process.  As a result, these RDD's input iterators are consumed in a different thread than the thread that created them, which can cause problems in our memory allocation tracking. For example, if allocations are performed in one thread but deallocations are performed in a separate thread then memory may be leaked or we may get errors complaining that more memory was allocated than was freed.
I think that the right way to fix this is to change our accounting to be performed on a per-task instead of per-thread basis.  Note that the current per-thread tracking has caused problems in the past; SPARK-3731 (#2668) fixes a memory leak in PythonRDD that was caused by this issue (that fix is no longer necessary as of this patch).

Note that this still needs test cases.  I also need to audit PythonRDD, RRDD, ScriptTransformation, and PipedRDD to make sure that they propagate their parent threads' TaskContext thread locals.

/cc @andrewor14 for first-impressions on the approach here; just looking for high-level feedback on whether this is the right route to fix some of these problems of memory being freed in different threads than it was allocated in.

Merged build triggered.

Merged build started.

Test build #38762 has started for   PR 7734 at commit 7b0f04b.

Test build #38762 has finished for   PR 7734 at commit 7b0f04b.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38766 has started for   PR 7734 at commit 44f6497.

Test build #38766 has finished for   PR 7734 at commit 44f6497.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

@lianhuiwang, you might be interested in this change given the related work that you're doing at #7130.

LGTM

As discussed offline, one thing that's missing is to propagate the task context to other threads.

Merged build triggered.

Merged build started.

Test build #38792 has started for   PR 7734 at commit b4b1702.

Test build #38792 has finished for   PR 7734 at commit b4b1702.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

I've merged this. Thanks!

Just for future readers of this PR: note that the ScriptTransformation case was already handled in a previous PR, which is why there's not a change for that here.


Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary

when i  change 'max_step' from 1000 to 10000 in mnist_with_summaries.py ,after 8550 iters occur these error:
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
W tensorflow/core/framework/op_kernel.cc:968] Invalid argument: Nan in summary histogram for: layer1/biases/summaries/HistogramSummary
[[Node: layer1/biases/summaries/HistogramSummary = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](layer1/biases/summaries/HistogramSummary/tag, layer1/biases/Variable/read/_21)]]
Traceback (most recent call last):

I did not confirm this myself, but could it be that this model is basically fully trained within 1000 steps?  If this is the case, continue training may or may not lead to NaNs.  Please confirm.

I think mnist_with_summaries prior to r0.11 had bugs.  If you are using mnist_with_summaries.py at HEAD, they might be fixed.  I wouldn't use mnist_with_summaries.py for anything real -- the point was to demonstrate how to attach summaries to a model.

Automatically closing due to lack of recent activity. Please reopen when additional information becomes available. Thanks!

but my tensorflow version is 1.0.1, so I don't know why have a error? the error is "Invalid argument: Nan in summary histogram for: train/boxes_delta_y
[[Node: train/boxes_delta_y = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](train/boxes_delta_y/tag, strided_slice_45/_99)]]"
I need help, help, help!!! Please!!!

InvalidArgumentError: Nan in summary histogram for: dnn/dnn/logits_activation
[[Node: dnn/dnn/logits_activation = HistogramSummary[T=DT_FLOAT, _device="/job:localhost/replica:0/task:0/cpu:0"](dnn/dnn/logits_activation/tag, dnn/logits/BiasAdd)]]
I am having the same error too.....have been trying to figure out what's wrong but not being able to do it....someone please help me on this

@issxjl2015, @sswarnakar, you may have the same error but for different reasons. Please post detailed issues with reproducible test cases as new issues if you would like help. Assuming the causes of the error being the same is easy to do, but often not true. Thank you.


Cannot authorise github account

The version on the AppStore doesn't work for me. I cannot authorise the app to access my github account.
When I click on the menubar icon, I choose Continue

It opens a github oauth request (blank page?), then ask to launch an external program (PopHub)

After that, nothing happens.
As you can see on the second picture (pay attention to the pophub:// URI), there is an error on the redirect URI.

Same here. I believe the author does not care to resolve this.


feature: seperate plugin options for concurrency limits, better errors

this trades out the env variable for requestConcurrency for two different plugin options
TODO:

[x] plugin options validation
[x] docs
[ ] override using/fallback to env variable?
[x] seperate requestConcurrency for MediaItem
[x] seperate requestConcurrency for schema
[x] better errors for 5xx requests that are usually caused by request overloads

I think we need to rebase from master to get the tests to run 👍

For the question of  override using/fallback to env variable?, I think let's make this a breaking change v4.0.0 and include a note about GATSBY_CONCURRENT_REQUEST not being used anymore in the docs as well as in the error messages.

@TylerBarnes do we want to create a troubleshooting link header for this, rather than adding more content to the errors?

I think it's nicer for the user to not have to leave the terminal to fix it but we could also include a link to docs. Ideally we wouldn't link to docs though, especially since we'll be moving everything around soon

@TylerBarnes ok, i think it's all ready now!

wait... how does changing a markdown file cause the schema test suite to fail? but other test suites to pass?

ok, weird to get a snapshot failure for what appears to be an upstream change??
was there a version released on top of another existing version? afaik, this should only happen if we change something with the schema, or a wp-graphql* plugin is bumped?

Looks like the WPGraphQL schema changed somehow. Maybe it updated to a newer version? 🤔

Ahhh, it's because of a recent WPGatsby change. I added a field WPGatsby.isPreviewFrontendOnline

just confused as to why this would happen without changing plugin versions in the PR? 👀

If you merged or rebased master I likely updated the version elsewhere and that made it's way in here.

@TylerBarnes then the snapshots should have updated as well when I rebased??

i'll try rebasing again

Yeah that's a good point! I'm not sure how to explain this haha. The weird thing is the docker-compose.yml is still on v0.6.0 but the change here wasn't introduced until v0.6.7.
Maybe this is a bug with our docker setup script?
https://github.com/gatsbyjs/gatsby-source-wordpress-experimental/blob/master/docker-compose.yml#L25

@TylerBarnes it appears to be that a wordpress plugin version was bumped without updating the snapshots. Thats why every merge to master fails CI on the test schema job

I'm confused though because on master the version is still v0.6.0 which shouldn't have this change in it

Looks like we should use the install-plugin script instead of using git clone https://github.com/gatsbyjs/gatsby-source-wordpress-experimental/blob/master/docker/wordpress/Dockerfile#L35


update user-agent value to be specific to sigstore-rs

Signed-off-by: Bob Callaway<EMAIL_ADDRESS>
Summary

Release Note

Documentation

Could I get a little more context on the change? Trying to understand how the cargo version maps to the user agent

It would be good to be able to know for debugging purposes which clients
are sending requests to Rekor services (java v 1.2.3 sends input looking
like X vs rust v0.14.6 looks like Y).
On Fri, Sep 2, 2022 at 1:34 PM Luke Hinds @.***> wrote:

Could I get a little more context on the change? Trying to understand how
the cargo version maps to the user agent
—
Reply to this email directly, view it on GitHub
https://github.com/sigstore/sigstore-rs/pull/122#issuecomment-1235752661,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVWTJLDK4QRMS3NWIY5XVTV4I3EFANCNFSM6AAAAAAQDKLBNQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


fix(api): Prioritize mc alarms over errors

The error message returned by the motor controller after a hard halt is
"error:Alarm lock". This is meant to be sensed by logic that raises a
different kind of exception (SmoothieAlarm) from the kind raised by for
instance an unexpected limit switch actuation or malformed
response (SmoothieError). Unfortunately, the way this is sensed is
that SmoothieAlarm looks for the keyword "alarm" and SmoothieError looks
for the keyword "error", and that message contains both, and the error
case is checked first.
The fix is to swap the order of the two. The fix could also be to
special case the message checking, but let's see if keeping it simple
works first.
Testing
This is unit tested and will do what it says on the tin, but it's not clear to me if this is a safe thing to do in all circumstances on hardware. We should test this by running it on a robot and

Cancel a running protocol (or do something else that causes a hard halt) and make sure the error recovery in case of a SmoothieAlarm actually, like, works, since it's probably never occurred before
Run a protocol and tap a limit switch to cause a HardLimitError and make sure it's still a SmoothieError
Hold down the switch during a jog or non-protocol-execution motion and check the same

Run a protocol and tap a limit switch to cause a HardLimitError and make sure it's still a SmoothieError

I'm not sure if I'm testing this right, but this might not be the case?
I ran a protocol and reached in and held down the +X limit switch. The robot stopped and then homed. I see these errors in the GET /run response:
        {
            "id": "a3297d01-2b14-4a7b-a234-11b42aec3c12",
            "createdAt": "2022-01-11T15:41:07.272963+00:00",
            "status": "failed",
            "current": true,
            "actions": [
                {
                    "id": "7f97d037-cd50-466d-81b5-faa208c94c63",
                    "createdAt": "2022-01-11T15:41:14.393300+00:00",
                    "actionType": "play"
                }
            ],
            "commands": [
                [...]
                {
                    "id": "command.DISPENSE-2",
                    "commandType": "custom",
                    "status": "succeeded"
                },
                {
                    "id": "command.RETURN_TIP-2",
                    "commandType": "custom",
                    "status": "failed",
                    "errorId": "13d98c6e-2ff2-44b8-8d45-a68926b12513"
                },
                {
                    "id": "command.DROP_TIP-2",
                    "commandType": "dropTip",
                    "status": "failed",
                    "errorId": "20010b69-781a-46f5-99b7-70e19a00aa32"
                }
            ],
            "errors": [
                {
                    "id": "20010b69-781a-46f5-99b7-70e19a00aa32",
                    "errorType": "LegacyContextCommandError",
                    "createdAt": "2022-01-11T15:42:21.809594+00:00",
                    "detail": "SmoothieAlarm: None returned ALARM: Hard limit -X"
                },
                {
                    "id": "13d98c6e-2ff2-44b8-8d45-a68926b12513",
                    "errorType": "LegacyContextCommandError",
                    "createdAt": "2022-01-11T15:42:21.812395+00:00",
                    "detail": "SmoothieAlarm: None returned ALARM: Hard limit -X"
                },
                {
                    "id": "564028e9-88a7-48e2-8e27-89447e1a97c6",
                    "errorType": "SmoothieAlarm",
                    "createdAt": "2022-01-11T15:42:21.819024+00:00",
                    "detail": "SmoothieAlarm: None returned ALARM: Hard limit -X"
                }
            ],
            "pipettes": [...]
            "labware": [...]
            "labwareOffsets": [],
            "protocolId": "8dfbc3b3-92ff-4a41-83b1-f9317cc0283f"
        }

With the latest commit, GET /runs now shows SmoothieError as specified in the review requests.
However, I noticed this behavior while jogging in deck calibration:

Start deck calibration and click through the dialogs until you have the opportunity to jog.
Hold the +X limit switch down.
While holding down, the limit switch, jog to the right. Release the limit switch.
The robot will home in the Z, A, and X, but not Y. This is weird to me?
Try jogging to the left. The robot will instead home all axes, including pipette plungers. This is also weird to me?
Jog to the left again. This time, the robot doesn't home, and the jog proceeds as normal. No errors are propagated to the Opentrons App.

It looks like this behavior is also present on edge b39d2f9a427baba887e751eb198577ed0ca93205.

The tests themselves look good. I think it would be helpful to have some more context about the expected physical robot behavior change in the test doc strings.
If I understand correctly from the thread/this PR, we effectively don't want to trigger a home when we hit a limit switch?

We do want to - we want to keep behavior unchanged. The behavior @SyntaxColoring noted above is as intended, even if what's intended is a little weird, and is present in edge. The strange homing behavior is because of required homing sequences and trying to home just the erroring axis to avoid e.g. overaspiration - just homing X requires ZA, then Y's homing flag is reset so it homes Y but that requires homing X and thus ZA.