Speech Recognition - Audio Training Issue

Hi, I am trying to replicate the AudioTraining.ipynb example on my end, with windows as my client side OS and linux as my server side OS.
Extracting my audio features ran successfully, as shown below. The path to my first audio file was recorded as "/home/sasdemo/STT1/84-121123-0000.wav"

However, I ran into issues when loading the Audio metadata. As the groundtruth file is stored on the client side (windows) and the audio files are stored on the server side (linux), the paths i specified for creating the audio metadata resembles the following:
me = AudioTable.load_audio_metadata(conn, "C:/Users/cwh/Desktop/Speech Recognition Dataset 1/groundtruth.txt", "/home/sasdemo/STT1")
The table containing the audio metadata is created as follows:

The path variable was generated, appending a "" and the filename to the directory specified in the load_audio_metadata function. The path to my first audio file here was recorded as "/home/sasdemo/STT1\84-121123-0000.wav". Note the last backward slash in this path.
Due to the incorrect backward slash appended to the path, I am unable to use the path variable as a common ID to join the tables together.
Any help would be greatly appreciated!

When we have this case, we try to get file two separators: 1) for os of the client and 2) for os of the server. It seems like in this case, we used the client fs in the server side. I will look into this issue. Maybe joining with filenames would be a better idea than the full path. Thanks for pointing out. I will keep this issue updated.

I did some changes with a recent push and updated the example. If you do a git-clone and use the most recent version, you should be able to have a fixed dlpy for your issue. thanks

@9to5routine I am wondering if you had any time to check the fix? thanks

Yes, the file separator issue has been resolved; thanks so much for the help!


19795: Create Test DB for Glue Development

Field
Value

Redmine Ticket Number
19795

App-Dev Road Map #
n/a

Start Date
n/a

Due Date
n/a

App-Dev Priority
UP-Disqueued

Development Story Points
3

Peer Review Story Points
n/a

Ticket Author
@blackeaglejs

🔢


Issue #1

xxxxxx

Hi, I'm not sure how these issues are ending up on our repository but I am guessing it's being done in error. If it's not, please reach out on Slack or Teams 😄


WIP: Dynamic Menubar

It worked a minute ago and then I changed something and now it doesn't. But it's like a single change off of working.
Then we need to take care of updating it after certain actions.
#191

Git started spazzing on me and I couldn't properly resolve conflicts on this branch, so I just copy-pasted your function, fixed it, and pushed to master.
Menubar is now dynamic on startup, but not when you interact with it (i.e. toggling autotrading should change the ON/OFF status on the menubar instantly).


Static plugin loading policy

We already have PluginLoaderPredefImpl, so we just need to refactor OpinionatedDiApp and role logic to hide things specific for PluginLoaderDefaultImpl and make usage obvious/idiomatic.
Also this ticket opens an easy way to compile-time context checks.
Should be done as part of #294

Merged with #294


Add loopback-connector-firestore to connectors

https://github.com/dyaa/loopback-connector-firestore

This change is

Any updates !

I have commented on the code

@pasindud where?

@dyaa oh sorry my bad it seems it was not submitted

Done

👍


Note that changes alpha of an image

Describe your problem here.
So, i wanna make a custom mechanic that, first, if the alpha of a picture is > 0.60, it slowly comes back to 0.60.
Then, if boyfriend presses a note, it adds 0.02 to the alpha.
I've tried everything i know but for some reasons i cannot find out how to make it, here's the code if you think you can find what i did wrong.
function onUpdate(elasped)
    while getProperty('filter.alpha') > 0.60 do
        setProperty('filter.alpha', getProperty('filter.alpha') - 0.001)
    end
end

function goodNoteHit(id, direction, noteType, isSustainNote)
    if getProperty('filter.alpha') >= 0.6 then
        if not isSustainNote then
             setProperty('filter.alpha', getProperty('filter.alpha') + 0.04)
        else
             setProperty('filter.alpha', getProperty('filter.alpha') + 0.02)
        end
    end
end

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

NOT a .Lua person. Sorry

then why did you comment?

There's two reasons why it's not working. The first is while-do loop, this loop will be repeated on onUpdate() over and over again making it, not adding opacity. The second is that I don't really know why it's not working on the getProperty('filter.alpha') > 0.60 on the goodNoteHit() probably a bug or something.
Anyways here the fixed:
function onUpdate(elasped)
     if getProperty('filter.alpha') > 0.60 then
          setProperty('filter.alpha', getProperty('filter.alpha') - 0.001)
     end
end

function goodNoteHit(id, direction, noteType, isSustainNote)
     if getProperty('filter.alpha') > 0.50 then
          if not isSustainNote then
               setProperty('filter.alpha', getProperty('filter.alpha') + 0.04)
          else
               setProperty('filter.alpha', getProperty('filter.alpha') + 0.02)
          end
     end
end

Alright, thank you so much ! I understand my mistake now


Pin libcloud to <2.0.0

Version 2.0.0rc2 currently is causing setup-maas.yml to fail due to
https://issues.apache.org/jira/browse/LIBCLOUD-904https://issues.apache.org/jira/browse/LIBCLOUD-904
Pinning to a version <2.0.0 ensures that the rackspace monitoring
libaries have a libcloud version that works.
Connects https://github.com/rcbops/rpc-openstack/issues/2156
(cherry picked from commit 58dedc7a6cc1ef7eefcab9d7da87c1210cca0196)

As a precaution, let's hold off until the next master+xenial job passes with maas before merging the backport. Even though I tested this on my AIO master+xenial instance, it'll still be good to verify that this pin fixes the master+xenial gate jobs.
https://rpc.jenkins.cit.rackspace.net/job/RPC-AIO_master-xenial-periodic/


WIP: track when we had good data for monitors

Some monitors weren’t really stably reporting data until after a certain date, so record when we started having good data for each monitor and only record/report from after that date.
At the moment, this works by recording a good_after date in our monitor metadata JSON file. We avoid recording data before that date. We’ll also need to throw out existing data we have before that date.

[x] Record good_after date for relevant monitors
[x] Don’t record data in the event hook if the good_after condition is not met
[ ] Don’t record data in tasks if the good_after condition is not met
[ ] Remove old data that doesn’t match the good_after condition

Grr, as @alanjosephwilliams noted in Slack, it looks like what we actually have is periods of bad data. So this probably needs to be flipped entirely so that we record an array of data ranges for bad data.
Probably something like:
"bad_dates": [
  ["2015-02-02T09:32:00", "2015-02-04T09:30:00"],
  ["2015-02-21T13:03:00", "2015-02-26T15:30:00"],
  …
]

Seem reasonable, @alanjosephwilliams @daguar @bensheldon ?

Should those ranges be able to have a placeholder signifying “the beginning of all time” and “heat-death of the universe” for monitors that started bad/are not-yet-fixed? Or just use really ancient/far future dates?

In addition to blanket good/bad times, we should probably base our historical uptimes on ETLed Pingometer Events. We should rely on ETLed Events over webhook events because the webhook is inherently unreliable: in addition to going over the internet, it's easy to crash-out, as happened yesterday  when a slow Pingdom API caused the requests to Time out (this happened on both the Sinatra and Rails apps).
So webhook for reporting contemprary current up/down-ness, but ETLed Event data for determining historical uptime.
Also, in addition to having blanket times, we should probably have an annotation field for incidents, as well as an "accepted/rejected" flag so that we can (more) easily document and filter out incidents if we know that they are not realsy.

So webhook for reporting contemprary current up/down-ness, but ETLed Event data for determining historical uptime.

I’m not sure there’s really a meaningful difference, though. Maybe what that really means is that we should be running the ETL tasks every so often via cron/scheduler.

probably have an annotation field for incidents

:100:

an "accepted/rejected" flag so that we can (more) easily document and filter out incidents if we know that they are not realsy

Hmmm, not sure I’m getting this one (maybe just need more detail)

But also, on uptimes: you’re right that we should be running them off our data, whether that’s coming in via webhook or ETL. Current process is left-behind from before we were tracking stuff appropriately ourselves. Also it’s a bit more work to synthesize those stats. <— new issue?
(Relatedly, maybe we should start ETL-ing checks, too, so we can get latency.)

an "accepted/rejected" flag so that we can (more) easily document and filter out incidents if we know that they are not realsy

Hmmm, not sure I’m getting this one (maybe just need more detail)

We just may need to tag certain events as "our fuckup; doesn't count" (because if we just delete them, they'll get re-created during the ETL process). So just something like an "accepted" flag (defaulted to true, but we can manually set to false if we discover the incident was caused by an issue on our end, rather than the WebPortal itself).

But also, on uptimes: you’re right that we should be running them off our data, whether that’s coming in via webhook or ETL.

Yes. It would be really awesome if @pingometer included the event_id in their webhook so that we could super easily reconcile webhook events with events stored in their API. This would also be way more reliable than our current method of get webook -> get webhook's monitor -> record monitor's last event which has some slackness in the relation between "webhook" and "event" because it's basically time-bound ("last event") rathe than related on a strong event id.

because if we just delete them, they'll get re-created during the ETL process

That’s what the bad_dates field is there to address, though.
That said, it occurs to me that it might make sense to have incidents of “unknown” status (as opposed to down), since we can’t reliably say whether the site was up or down during that time. I guess that’s pretty similar to what you’re saying, though the semantics feel slightly better to me (at first glance at least). We may or may not surface those in charts.

It would be really awesome if @pingometer included the event_id in their webhook so that we could super easily reconcile webhook events with events stored in their API. This would also be way more reliable than our current method

We could switch to the method used in the snapshots ETL task: https://github.com/codeforamerica/snap-it-up/blob/master/tasks/s3.rake#L27 Not perfect, but more accurate than just taking the last event.

We'll include the "last_event" in the webhook - it'll get deployed today.
It makes total sense to do it this way - we're onboard.
On Tue, Mar 24, 2015 at 9:26 AM, Rob Brackett<EMAIL_ADDRESS>wrote:

because if we just delete them, they'll get re-created during the ETL
process
That’s what the bad_dates field is there to address, though.
That said, it occurs to me that it might make sense to have incidents of
“unknown” status (as opposed to down), since we can’t reliably say whether
the site was up or down during that time. I guess that’s pretty similar to
what you’re saying, though the semantics feel slightly better to me (at
first glance at least). We may or may not surface those in charts.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforamerica/snap-it-up/pull/48#issuecomment-85588793
.

@pingometer: Awesome! That makes a lot more sense than the current set-up. What will this look like in terms of how it’s encoded?

That’s what the bad_dates field is there to address, though.

I guess I don't like the idea of bad_dates because it's not really tied to the actual incidents and seems like it will be susceptible to typos or just lack of context (an array of dates, rather an a set of bad_periods objects that can be annotated/explained ) . Though this is probably just the difference between me doing my work on a relational database and you doing work on a non-relational database :smile:

@pingometer Yay! Thank you! :icecream:

I guess I don't like the idea of bad_dates because it's not really tied to the actual incidents and seems like it will be susceptible to typos or just lack of context

Well… it can certainly be annotated if you think that’d be useful. It’s a lot more human-editable by someone other than you and me than having them log into the DB and edit the event :P
Further, I think we still need something like bad_dates or at least good_after because those time periods may have multiple events. There’s no 1:1 correspondence here. We could, alternatively, synthesize “unknown status” or “rejected” incidents from the bad dates (rather than using them to remove/ignore pingometer events).

I guess I also don’t feel like we have anything approaching a stable and canonical DB/storage for metadata like this yet, excepting that JSON file.

We could, alternatively, synthesize “unknown status” or “rejected” incidents from the bad dates (rather than using them to remove/ignore pingometer events).

Or in addition to removing/ignoring pingometer events. I guess I’m warming up to your rejected incidents, even though I still like my naming better :)
(Side note: another reason I like status is that it gives us a way in the future to have incidents for things like “unstable” or “reduced performance” or something, where there is super high latency or intermittent request successes/failures. I might be trying to conflate too many things there, though.)

@Mr0grog It's available in the webhooks now. Here's how it looks in the request body:
monitor_last_event_id: 5511e97819jg74db32400fc5

Suuuuuuuuper janky, but it works, which we need for now.


Latest change to sync breaks smart-enter

What system are you running Yazi on?
Linux X11
What terminal are you running Yazi in?
kitty 0.36.4
yazi --debug output
Yazi
    Version: 0.3.3 (baf062f 2024-11-07)
    Debug  : false
    OS     : linux-x86_64 (unix)

Ya
    Version: 0.3.3 (baf062f 2024-11-07)

Emulator
    Emulator.via_env: ("xterm-kitty", "")
    Emulator.via_csi: Ok(Kitty)
    Emulator.detect : Kitty

Adapter
    Adapter.matches: Kgp

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

SSH
    shared.in_ssh_connection: false

WSL
    WSL: false

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

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

Multiplexers
    TMUX               : false
    tmux version       : No such file or directory (os error 2)
    tmux build flags   : enable-sixel=Unknown
    ZELLIJ_SESSION_NAME: None
    Zellij version     : No such file or directory (os error 2)

Dependencies
    file             : 5.44
    ueberzugpp       : 2.9.6
    ffmpegthumbnailer: No such file or directory (os error 2)
    magick           : No such file or directory (os error 2)
    fzf              : 0.55.0
    fd               : No such file or directory (os error 2)
    fdfind           : 8.6.0
    rg               : 13.0.0
    chafa            : 1.12.4
    zoxide           : 0.9.4
    7z               : 16.02
    7zz              : No such file or directory (os error 2)
    jq               : 1.6

Describe the bug
As per instructions, added to smart-enter init.lua --- @sync entry.
I have smart-enter mapped to Enter. When hitting enter the process just hangs. This happens whether or not I have --sync in my keymap.toml.
Minimal reproducer
I was able to change other plugins with --- @sync entry successfully.
Anything else?
No response
Validations

[X] I tried the latest nightly build, and the issue is still reproducible
[X] I updated the debug information (yazi --debug) input box to the nightly that I tried
[ ] I can reproduce it after disabling all custom configs/plugins (mv ~/.config/yazi ~/.config/yazi-backup)

yazi.log
My yazi.log file.
Also here is my smart-enter init.lua:
-- init.lua
-- Created: 05/20/24
--- @sync entry
return {
entry = function()
local h = cx.active.current.hovered
ya.manager_emit(h and h.cha.is_dir and "enter" or "open", { hovered = true })
end,
}

-- Created: 05/20/24

No, you need to place the --- @sync entry at the head of the file without any other content before, see https://yazi-rs.github.io/docs/tips#smart-enter
Closing as expected behavior

Sorry to bother. Great work

Thanks. Works now.
Yazi is the BEST!!!
On Thu, Nov 7, 2024, at 15:07, 三咲雅 · Misaki Masa wrote:

-- Created: 05/20/24

No, you need to place the --- @sync entry at the head of the file without any other content before, see https://yazi-rs.github.io/docs/tips#smart-enter
Closing as expected behavior
—
Reply to this email directly, view it on GitHub https://github.com/sxyazi/yazi/issues/1892#issuecomment-2463400306, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALLYYRJYZ3XA3MOCSZB3ZULZ7PXBZAVCNFSM6AAAAABRMHNJB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRTGQYDAMZQGY.
You are receiving this because you authored the thread.Message ID: @.***>


name 'Image' is not defined, in "Tutorial #1: Train an image classification model with Azure Machine Learning service"

Hi,
I am Abhijit. I am using "Tutorial #1: Train an image classification model with Azure Machine Learning service", but i am finding issues in "Display some sample images" under Explore data.
It is showing the error:
NameError                                 Traceback (most recent call last)
<ipython-input-8-4b5a98a6ecba> in <module>
3
4 # note we also shrink the intensity values (X) from 0-255 to 0-1. This helps the model converge faster.
----> 5 X_train = load_data('C:/Users/Baryons/data_Azure/train-images.gz', False) / 255.0
6 y_train = load_data('C:/Users/Baryons/data_Azure/train-labels.gz', True).reshape(-1)
7
~\utils.py in load_data(add, status)
151     num = len(imgs)
152     for i in range(num):
--> 153         img = Image.open("C:/Users/Baryons/data_Azure"+imgs[i])   #???????Image????
154         arr = np.asarray(img,dtype="float32")  #?img?????????
155         data[i,:,:,:] = arr   #?????????data
NameError: name 'Image' is not defined.
Could please help me how to resolution these issue.

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

ID: 4bee4b9a-ce0f-f98b-3160-d6c4a40ef3ac
Version Independent ID: a0475a9e-47f6-2803-8707-fac54ba898dd
Content: Tutorial: Train an image classification model with Azure Machine Learning service
Content Source: articles/machine-learning/service/tutorial-train-models-with-aml.md
Service: machine-learning
GitHub Login: @hning86
Microsoft Alias: haining

@dazzler11
Thanks for the feedback! We are currently investigating and will update you shortly.

@dazzler11 We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Aplicacion Files no arranca, da error continuamente...

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS Version: [e.g. Windows 10 1903 18362.175]
App version: [v0.11.0]

Additional context
Add any other context about the problem here. Does this problem occur again after restarting the app?
Log file
Please upload the log file here so that we can understand your issue better. You can access it from Settings->About->Open log location. You can also find this file by going to %localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState, you should see a file in this directory called debug.txt or/and debug_fulltrust.txt.

@aleonmor thanks for this report. Could you add the app version and log files to the issue description?


Events that repeat forever

Hi,
this is a follow-up on 2fd2db6e59229bde7bed2b2745677bc995b6611b and 197975ba35f9767ed4cd2333f7ce816a9e4670e0.
The current behavior is inconsistent if I understand the code correctly. Repetitions from an events are returned but only if the event does not repeat forever. In that case, only the first instance of the event is returned.
I think the cleanest solution for the user of the API is that eventsFromRange() just returns all events in the correct range, with all repetitions. It's just not clear what should happen if the end date of the range is not given. This parameter might even be mandatory: if no recurring events are expected, then one can still set it explicitly far into the future (even the maximal timestamp), or just use getEvents().
This could be implemented by generating some of the events (next four years) and generating more only once eventsFromRange() needs them.

There is also this hack for YEARLY which is still in place which forces only 2 years worth of events: class.iCalReader.php#L385-386.
Would be cleaner to be consistent throughout

Hm I see. Can you provide some background on the behavior of Exchange? Is there a sample file?

I'm currently parsing iCal files which have been produced by the export method of Outlook 2013 but I am not the author of this particular hack so I have no sample file of this scenario. I'm currently preparing a PR which will simply define a default $until value should neither UNTIL nor COUNT be defined which should cover most circumstances.

@real-or-random does this commit (5aae755) help?

Thanks, it's not hackish anymore now. I think it is not optimal yet but fine for my needs. I will create a pull request if I need more. :)

Yes agreed - not optimal so PR welcome :)
Especially regarding #19 whereby you might not want to include in the past events of an indefinite recurring booking


Remove Back swipe from last Controller.

Hi,
First of all any thanks for the Library, I had a requirement to disable back swipe from the last controller, is there any way to achieve it.

You could always modify the liquid-swipe framework yourself in your project. There is a particular line of code that looks like the following:
private func configureNextPage() {
        guard let datasource = datasource else {
            return
        }
        let pagesCount = datasource.numberOfControllersInLiquidSwipeContainer(self)
        guard pagesCount > currentPageIndex + 1 else {
            nextViewController = nil
            rightEdgeGesture.isEnabled = false
            return
        }
      ...
    }

Right under the rightEdgeGesture.isEnabled = false you can include a leftEdgeGesture.isEnabled = false command. Then delete the framework and rebuild the project.
Keep in mind that if you ever pod update you will overwrite the framework and the code will be overwritten.


Fill out models and recipies section in docs

We should add a bit more information: dataset, language model (for speech), maybe how metrics were calculated, etc.

Mostly done. closing for now


Fix comment for cliff in struct

Fix comment.
While the _cliff param of createVestingSchedule() is a duration, inside the VestingSchedule struct it represents time since epoch.
The original comment is a bit confusing.

Also removed the initialized flag as it seems to be unused


sap.m.wizard - several bugs related with delayedCalls

Steps to reproduce:

Go to https://sapui5.netweaver.ondemand.com/explored.html#/sample/sap.m.sample.Wizard/preview
Open developer console
w = ${".sapMWizard"}.control(0)

Three issues:

w.discardProgress() does not return Wizard instance
w.discardProgress();w.nextStep();w.nextStep() produce wrong navigation in wizard (expected step 3, but it is step 2)
use this instead of step 2: w.nextStep();w.nextStep();w.previousStep();w.previousStep(); results with disappearing labels in navigation area

Issues occurs because of delayedCalls in Wizard.js. If the delayed calls wrapper is removed, it seems to work correctly, but it has to be verified. Other option can be to clear delayedCalls before calling nextStep function or generally on change of wizard.
DelayedCalls also destroy the possibility of testing this component, because in time when the delayedCall is triggered it does not exist any more and container is destroy (for example cannot call ._updateStep on 'undefined').

Hi @chicko01 ,

w.discardProgress() does not return the wizard instance. (confirmed).
w.discardProgress();w.nextStep();w.nextStep() reaches step 3 and the next step button has text (step 4)
(can`t reproduce)
w.nextStep();w.nextStep();w.previousStep();w.previousStep(); nav labels do not disappear.
(can`t reproduce)

I was able to reproduce the first issue only.
The first issue will be fixed.
Best,
ilhan

Hello @ilhan007,
I tried it again exactly according to written steps (I omit step 1.w.discardProgress() does not return Wizard instance).
If you try step 2 problem occurs - step 2 is active instead of step 3.
If you then refresh and try step 3 label in upper navigation bar disappear.
If it is necessary I can record video with the problem.
Base of the problem is as I wrote wrongly used delayedCalls. I think it is obviously bad pattern to use them. And if you use them you should keep reference of them and clear them.

Issue 2+3 still persist, followed up with the colleagues

Discussed the issue with the developer experts. The delayed calls need to be cleared again after calling them, a corresponding fix will be made.
As a workaround, you can try the "goToStep" method but it is implemented that it only works for backward navigation, not for forward navigation in the wizard.
Additional issues spotted:

When you are on the first step the following call throws an error and messes up the state if the control similar to the point 3) describd above:
'goToStep(w.getSteps()[1])'
The invalidateStep method does not return "this" for chaining in the standard case
The validateStep method does not return "this" for chaining in the standard case

Kind Regards,
Michael

The "goToStep" workaround does not help us. We need to clear all the progress, status etc. from Wizard and we don't want to do it manually. So there still problem with delayedCalls itself, because there no event or callback to let know that discardProgress was completely done and you can securly work with Wizard without interference from framework.


fix utest, unfork twitter-util

test run in progress at
https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/243/consoleFull

whoops, my twitter fix wasn't merged yet, and Haoyi already merged the needed utest fix, so never mind


Doc - Add RocksDB IOPS program options

Introduced in #8492, but missing in option dump

@matthewvon Should we also mention these options elsewhere, e.g. Troubleshooting?

Troubleshooting:  Yes.  I am not familiar with that portion of the documentation.  Want to point there?

Same low IOPS impacts import via api commands.  Our arangoimport command line has been fixed for the problem.  Thinking there might need to be a "warnings for cheap VMs" section.

Could use some love:
https://docs.arangodb.com/3.4/Manual/Troubleshooting/
Would be great to turn this chapter into a proper guide for users. Related planning issue which I also updated: https://github.com/arangodb/planning/issues/3599

Merging for now so that we can publish v3.4.5 docs with these options included


Week 2 Review Ticket

Scrum Team GitHub pages (2 points) - Link

[x] Project Owner / Sponsor presentation(visuals like wireframes or HTML pages), results of review, PII concerns, hosting plan, and software license
[x] 1st Code in GitHub with software license per 5.5 - Link to license

Issues this week:

#3
#4
#6
#7

As a Teacher, I need to learn to reward failure and effort in projects. The idea of each build is to see students take risks. Not necessarily produce something immediately useful or final, but leading to utility.
This project has great utility and CTE wants you to be successful.  This is a great opportunity for team and this project could be a great advantage to all of you if you continue to CSA.
In this project you have confirmation from others that the bootstrap modal makes thing seem much more fluid or connected.  IMO, there may be a point where after getting summary from Modal you may be leaving to a more complete and robust area in that point of interest.  As an Information Communication and Technology (ICT) Teacher I would like to see Modal to increase interest and then perhaps a more complete site just on ICT.
This would have information on ...
Computer Science Discovery
Computer Science Principles
Computer Science A
as well as other classes in the sector.
Now for you as students and owners of the project.  This could be a lot of information.   So, from your feature perspective you need to consider how do you provide layouts and designs that can be expanded by CTE staff or perhaps the Teacher community to keep things alive.

CTE staff should be able to add and create a new Modal and populate some initial messaging.
Resulting detail page should probably have ability to update an area from initial messaging and modal information.  Have ability to add classes, and perhaps ability to blog or message based off of permissions.

Also, as next level of information.  This is a pretty dead page and it is related to me.
https://www.powayusd.com/en-US/Departments/CareerTechnicalAdultEd/College-Career-Technical-Education/Industry-Sectors/Information-Communication-Technology


Minor fixes

Status :
Ready

Description :
1). Update playground live editor with proper spacing.
2). Fix text alignment on the homepage (small screens)
3). Fix styles and typos on usage page.

Codecov Report

Merging #261 into development will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           development     #261   +/-   ##
============================================
  Coverage        93.18%   93.18%
============================================
  Files               26       26
  Lines              851      851
============================================
  Hits               793      793
  Misses              58       58

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 680358e...7d46d9f. Read the comment docs.


feat(awsconfig): support AWS_SESSION_TOKEN

This PR adds support for the AWS_SESSION_TOKEN parameter used in short-lived session authentication in AWS.
Its usage is explained here in detail:
https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html
In my case, we use AWS SSO that creates temporary sessions with AWS_SESSION_TOKEN.
In order to run the s3 docker compose example as my user I must send this token along with the regular AWS key and id.

Changes available at the master branch Docker build:
https://github.com/cshum/imagor/pkgs/container/imagor/129361933?tag=master
You may pull the image via
ghcr.io/cshum/imagor@sha256:a435c728ab38e06b08ac593a047e577b7598b9e9dbbe4afe6ba02619104722c6


📃: Segment anything on images.

:red_circle: Title: Segment anything in real time
:red_circle: Aim: to develop a model, where we can segment anything in real time.
:red_circle: Brief Explanation:
We will use Fastsam for segmentation, because of its faster responses, in this we would be able to segment anything on an image.
The user will get 4 options: -segment everything, segment by box-prompt, point-prompt and text-prompt.
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name : Jai Dhingra
What is your participant role? GSSOC, Hacktoberfest

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Don't raise more than 1 issue

@Avdhesh-Varshney, I have raised a PR for my previous issue. So, I request you to please assign this issue to me.

Can you explain the keyword segment according to your context? Properly elaborate your project

Although, now I figured out a way to implement it in real time as well.

Based on your use case, I'm assigned it to you


Iteration count is not reset between executions

Create an iterative filter and set a VerboseIterationCommand callback, i.e.

using VerboseIterationCommandType = rtk::VerboseIterationCommand<FilterType>;
typename VerboseIterationCommandType::Pointer verboseIterationCommand = VerboseIterationCommandType::New();
filter->AddObserver(itk::IterationEvent(), verboseIterationCommand);

Call filter->Update() several times.
Iteration count is not reset between executions.

Expected behavior: iteration count should be reset at the beginning of each execution.
Looking at how this feature is written, I don't see an obvious fix.

It's not even obvious that it should always be reset automatically. There are scenarios where you want to do 10 iterations with a parameter (e.g. regularization), then modify it and continue the iterations.

I hadn't thought of that. Should we therefore leave it as is, or do you see something to be improved here?

I'm closing it. If someone is bothered by this, he should keep track of the value returned by AddObserver, and remove it with RemoveObserver + creating a new one. It is however safer to create a new filter for a new reconstruction in case the iterations store intermediate variables (like the conjugate gradient or the nesterov momentum). Thanks @acoussat!


Display QR code without generating a new secret key

Presently, I have not found any way to persuade google-authenticator to display the QR code for my user account without having to generate a new secret key.
I've just recently gotten a new phone and while trying to set up google authenticator on the new phone, I was looking for a way to simplify adding this account to the mobile app without changing the secret key (which would have caused my other devices to stop working properly).
I am well aware that I can obtain the secret key from the ~/.google-authenticator file.  However, given that there is already an interface with libqrencode and it works properly with a newly-generated key, I would like to see the same functionality made available to display an existing secret key as well.

For now you can add this early in main and recompile:
displayQRCode("aaaaaaaaa", "label", 1, "issuer");

Marking this issue an enhancement to parse the config file and reprint. But this will only work for TOTP since I don't think the counter is part of the QR code that apps will read.

For now, I've just typed in the secret code manually....
Having said that, having come across this situation, it occurred to me that this would be a rather useful feature.

This issue was moved to google/google-authenticator-libpam#1


backwards compatibility is maintained via only using new capabilities if they exist

Discussion https://github.com/defenseunicorns/zarf/discussions/1298
Epic https://github.com/defenseunicorns/zarf/issues/1319
Dependant on:
issue #1322
issue #1323
issue #1324
Issue #1321
Tasks

[ ] if the ./images/ dir exists, it will be used instead of ./images.tar
[ ]  if ./components/.tar.? exists, it will be used instead of the ./components// dir
[ ]  if ./checksums.txt exists it will be processed
[ ]  if metadata.checksumSignature is also not an empty string, it will used to verify the signature of the checksums file
[ ] if ./sboms/.tar.zst exists it will be used instead of the ./sboms/  dir
[ ] if ./zarf.yaml.sig exists it will be used to verify the signature of ./zarf.yaml

@YrrepNoj is this more of an *ility on the issue you are already working?

We could also in a future ticket compare the zarf.schema.json if we include it in the zarf package.


How to make cluster arch architect

Just confused,
easegress has a Leader node？Is traffic all through the leader and forward to other node? I mean ,how to load balance the traffic? Is nginx/vip or something at front of easegress?
thank you.

Easegress's leader and follower is the role of the Easegress control plane, which manages metadata of the Easegress controllers, and pipeline/filters configuration. It has no relationship with the Easegress data plane, but a node with a leader or follower role can still accept HTTP traffic.
I hope that my explains can eliminate the confusion of yours

thank you for your answer,now I know the control plane/data plane definition in Easegress.
but just also don't get it about how to build a cluster of data plane,need nginx/lvs ？
traffic -->nginx/lvs --->load balance to every Easegress data plane?

@Liubey

Management traffic is all through the leader.
Real business traffic can run through all Easegress instances.
For example, if u create an HTTPServer in the Easegress cluster which listens 10080 port, then all instances inside the Easegress cluster will create an HTTPServer for receiving 10080 port traffic. So I think the path should be

user-> Traffic gateway(F5) -> API gateway (Easegress )

I think a Layer three Loadbalance(LVS, F5) is the better choice for the data plane.

but just also don't get it about how to build a cluster of data plane,need nginx/lvs ？
traffic -->nginx/lvs --->load balance to every Easegress data plane?

As same as how you've done for multiple nginx servers.
And the major purpose of Easegress cluster is for metadata consistency.
Hope this make senses to you.
-- Hao

@Liubey

Management traffic is all through the leader.
Real business traffic can run through all Easegress instances.
For example, if u create an HTTPServer in the Easegress cluster which listens 10080 port, then all instances inside the Easegress cluster will create an HTTPServer for receiving 10080 port traffic. So I think the path should be

user-> Traffic gateway(F5) -> API gateway (Easegress )

wow,now I'm clear about. leader, it's for "management traffic" to make metadata consistency.

@haoel @zhao-kun @benja-wu
Thank you for your detailed answers.I'm very honored and clear about that.


bug: ionosctl errors with exit code 1 if no images where found

Description

If you search/filter for a name that does not exists - the tool errors:
ionosctl image list --filters name=debian-12-amd64-latest-none-exist,location=txl,location=fra
echo $? # Outputs 1

This is and leads to unexpected behavior. A command should only error if there is anything wrong with the command/network/filesystem - not if the command return its expected outcome. For example in the CI. If there is no image the tool should output nothing and exit with 0. Or at leas there should be a flag for that.
Please apply to standard behavior
Expected behavior

Command returns nothing (or empty array if json output) and exits with code 0
Environment
Go Version:
?

Ionosctl version:
ionosctl version v6.7.1

OS:
Windows 11 Pro 23H2

Shell:
Git Bash

Configuration Files

None
How to Reproduce

If you search/filer for a name that does not exists - the tool errors:
ionosctl image list --filters name=debian-12-amd64-latest-none-exist,location=txl,location=fra
echo $? # Outputs 1

This is and leads to unexpected behavior. A command should only error if there is anything wrong with the command/network/or - not if the command return its expected outcome. For example in the CI. If there is no image the tool should output nothing and exit with 0. Or at leas thee should be a flag for that.
Please apply to standard behavior
Error and Debug Output

ionosctl image list --filters name=debian-12-amd64-latest,location=txl,location=fra
Error: error getting images based on given criteria

Additional Notes

It is Industry standard to use non 0 exit codes if there is anything wrong - hears it behaves as expected. Most other tools also just exit with 0 when used with filter. See docker ps --filter name=none-exist or kubectl
Also if you specify --output json it should also output an empty array/object. In case of an actual error - the output should also be json not text
References

Workaround until this is fixed:
# Good old bash to the rescue...
if ionosctl image list --filters name=${IMG_NAME}-latest,location=txl,location=fra ; then
    export CURRENT_IMG_RUN_IDS=$(ionosctl image list --filters name=${IMG_NAME}-latest,location=txl,location=fra --output json | jq -r ".items[].id")
    echo $CURRENT_IMG_RUN_IDS
    # Do stuff
fi

This does need a second request but that better then a failing CI


Assuming wrong shell in .profile

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Add Homebrew to my PATH as suggested by the docs
What happened (include command output)
set: -g: invalid option (more extensive but not relevant in my opinion as the issue is known)
What you expected to happen
It adds it to my PATH
Step-by-step reproduction instructions (by running brew commands)

Use GNOME
Set fish as your default shell, possibly making sure $SHELL is fish.
Run echo "eval \$($(brew --prefix)/bin/brew shellenv)" >> ~/.profile (in Bash)
Log out and back in
Notice .profile error

Output of brew config and brew doctor commands

$ brew config
HOMEBREW_VERSION: 2.4.5
ORIGIN: https://github.com/Homebrew/brew
HEAD: 6d2c39579e22d0ee9baccdccdd8a12efb8b00304
Last commit: 4 hours ago
Core tap ORIGIN: https://github.com/Homebrew/linuxbrew-core
Core tap HEAD: 5c3e01d57e4bb18d4b338b6893800cfaa65bc197
Core tap last commit: 50 minutes ago
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_DISPLAY: :0
HOMEBREW_MAKE_JOBS: 8
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
Clang: N/A
Git: 2.27.0 => /bin/git
Curl: 7.68.0 => /usr/bin/curl
Kernel: Linux 5.4.0-40-generic x86_64 GNU/Linux
OS: Ubuntu 20.04 LTS (focal)
Host glibc: 2.31
/usr/bin/gcc: 9.3.0
glibc: N/A
gcc: N/A
xorg: N/A

$ brew doctor
Your system is ready to brew.

Additional Context
GNOME sources ~/.profile on login. I believe this is always with Bash and is not affected by the login shell.
Output of ps --forest:
    PID TTY          TIME CMD
  23877 tty2     00:00:00 gdm-x-session
  23879 tty2     00:00:00  \_ Xorg
  23903 tty2     00:00:00  \_ Xsession
  23908 tty2     00:00:00      \_ ps

It seems brew shellenv is impacted by $SHELL, and returns Fish env vars setup code.
Output:
$ brew shellenv
set -gx HOMEBREW_PREFIX "/home/linuxbrew/.linuxbrew";
set -gx HOMEBREW_CELLAR "/home/linuxbrew/.linuxbrew/Cellar";
set -gx HOMEBREW_REPOSITORY "/home/linuxbrew/.linuxbrew/Homebrew";
set -q PATH; or set PATH ''; set -gx PATH "/home/linuxbrew/.linuxbrew/bin" "/home/linuxbrew/.linuxbrew/sbin" $PATH;
set -q MANPATH; or set MANPATH ''; set -gx MANPATH "/home/linuxbrew/.linuxbrew/share/man" $MANPATH;
set -q INFOPATH; or set INFOPATH ''; set -gx INFOPATH "/home/linuxbrew/.linuxbrew/share/info" $INFOPATH;

This also happens in .profile as SHELL is set to Fish, however, as .profile is sourced with Bash, eval $(brew shellenv) errors as the returned commands are for Fish. A workaround:
$ SHELL=bash brew shellenv
export HOMEBREW_PREFIX="/home/linuxbrew/.linuxbrew";
export HOMEBREW_CELLAR="/home/linuxbrew/.linuxbrew/Cellar";
export HOMEBREW_REPOSITORY="/home/linuxbrew/.linuxbrew/Homebrew";
export PATH="/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin${PATH+:$PATH}";
export MANPATH="/home/linuxbrew/.linuxbrew/share/man${MANPATH+:$MANPATH}:";
export INFOPATH="/home/linuxbrew/.linuxbrew/share/info:${INFOPATH}";

As this is not included in the docs, maybe shellenv should detect if it is running part of this GNOME source or use a different way of detecting the shell as using SHELL is not accurate in this context. If this wasn't added then maybe a warning in the docs should be included explaining this.
Full workaround:
Run echo "eval \$(SHELL=/bin/bash $(brew --prefix)/bin/brew shellenv)" >> ~/.profile instead (in Bash)
Workaround part of first installation (replacement for docs):
> bash
$ test -d ~/.linuxbrew && eval $(SHELL=/bin/bash ~/.linuxbrew/bin/brew shellenv)
$ test -d /home/linuxbrew/.linuxbrew && eval $(SHELL=/bin/bash /home/linuxbrew/.linuxbrew/bin/brew shellenv)
$ test -r ~/.bash_profile && echo "eval \$(SHELL=/bin/bash $(brew --prefix)/bin/brew shellenv)" >>~/.bash_profile
$ echo "eval \$(SHELL=/bin/bash $(brew --prefix)/bin/brew shellenv)" >>~/.profile

Currently, https://docs.brew.sh/Homebrew-on-Linux assumes the user uses a Bourne-type login shell. That needs to be fixed.
@nihaals, please try removing the shellenv invocation from your ~/.profile, and add the following to your ~/.config/fish/config.fish instead:
if status --is-login
    if test -f /home/linuxbrew/.linuxbrew/bin/brew
        /home/linuxbrew/.linuxbrew/bin/brew shellenv | source
    end
end

Then logout and login again, and let us know if you're still seeing issues.

Didn't work. I'm not sure why, status --is-login is exactly what is used in the fish docs and running just the test and actual source worked fine in a normal shell.

After testing, it seems that status --is-login is always failing.
> getent passwd $LOGNAME | cut -d: -f7
/usr/bin/fish

I added the following to my ~/.config/fish/config.fish (which is definitely executed when creating a new interactive shell)
if status --is-login
  date >> ~/login-times.log
   ...
end

and had no file created when logging out and back in, but fish -l did work.
According to https://askubuntu.com/a/598072, GNOME does not execute the login shell by default (this was also unticked for me, 20.04). This means that adding this to the documentation wouldn't be a good idea. I'm not sure what the best path for this is as having documentation that a user can use without simply adjusting the commands for their standard setup purely based on their DE is fairly important, but this seems to be fairly exclusive to GNOME. Improving shell detection and continuing to recommend using .profile would probably be best, but I believe if the user is not using GNOME nor a Bourne shell as their login shell, this will either error or not be executed:

Using GNOME

Using Bourne login shell
Currently works fine
Using non Bourne login shell
As explained in Additional Context in the original issue, this errors ($SHELL mismatches the shell currently executing .profile

Not using GNOME (or another DE with the same behaviour if there are any?)

Using Bourne login shell
Currently works fine
Not using Bourne login shell
.profile is probably not executed, depends on the setup of the user. They may do something like bass ~/.profile [bass], in which case see GNOME > non Bourne. They may rewrite ~/.profile in their shell and simply source it in their "on shell" script or not have a ~/.profile and have all the equivalent commands only in their "on shell" script, in which case this is currently fine as the user will know how to make it specific to their setup.

So the current problems are using GNOME with a non Bourne shell set as their login shell or not using GNOME, using a non Bourne shell as their login shell and execute their .profile with a Bourne shell. I'm assuming latter can be ignored as this is pretty user specific so they will know to make a change when setting it up, however, I didn't know basically anything I mentioned in any of these comments a day ago and I was impacted with a "standard" setup, so having the former be supported or for there to be clear documentation may be important for new users.

Actually, I'm starting to think that shellenv should be returning exports based on the calling shell ($PPID) rather than the login shell ($SHELL), especially since the current set of instructions embed a runtime call to brew shellenv, rather than the exports determined at install time.
@Homebrew/brew , if you agree, I'd be happy to issue a PR to fix this.

Actually, I'm starting to think that shellenv should be returning exports based on the calling shell ($PPID) rather than the login shell ($SHELL), especially since the current set of instructions embed a runtime call to brew shellenv, rather than the exports determined at install time.

Another way would be a few lines of feature detection code (along with the returned exports, not at the time shellenv is called.)
I can’t tell though whether that would or wouldn’t be as robust as detecting the shell via $PPID.

feature detection code

As in it would check for the existence of features/commands in the current shell then execute whichever ones exist?

$PPID

Didn't realise this existed, that would cover the better shell detection I was explaining. However, I'm assuming it would return the same as ps, and as my output shows, it's not necessarily the shell, but could be something part of the DE. This might get messy as a variety of DEs would need to be checked to see if they do the same as GNOME and what process calls it

As in it would check for the existence of features/commands in the current shell then execute whichever ones exist?

Yes, that’s exactly what I had in mind. I don’t have a strong opinion about it though.

I think if it was reliable it would definitely be the best as it avoids the identification I just explained. Not sure how easy it is to make shell code that works on any shell and identifies it though, other than just calling /bin/sh (I think every sane setup has it?)

As in it would check for the existence of features/commands in the current shell then execute whichever ones exist?

That would be nice if doable, though I can't imagine a code fragment that can be correctly parsed by both Bourne and C shells, yet do the necessary tests and run the necessary commands.

I'm assuming it would return the same as ps, and as my output shows, it's not necessarily the shell, but could be something part of the DE.

The parent of brew shellenv is either a shell (interactive, or running a script), or not. If it's a shell, ps -p $PPID -o comm= should print its name to be matched. If it's not (e.g. a binary, or Python script), odds are good that /bin/sh was invoked anyway to run brew shellenv, so the current default Bourne-style output would still be the most appropriate.

That would be nice if doable, though I can't imagine a code fragment that can be correctly parsed by both Bourne and C shells, yet do the necessary tests and run the necessary commands.

I was thinking about something along the following (untested) lines:
if (set -gx __probe 1 >/dev/null 2>&1); then
  set -gx HOMEBREW_PREFIX […]
else
  export HOMEBREW_PREFIX=[…]
fi

But as I said, I don’t feel I prefer one approach over the other.

@gromgit just an FYI, on my machine:
-bash-5.0.18- /Users/miccal (29) [> echo $SHELL
/usr/local/bin/bash
-bash-5.0.18- /Users/miccal (29) [> ps -p $PPID -o comm=
login

while:
-bash-5.0.18- /Users/miccal (29) [> ps -o comm=
-bash

That shouldn't be an issue, since $PPID in brew shellenv would point to the process that spawned it, i.e. your interactive session (bash) or whatever script ran it (the shell that said script was written in).

I think if you wrap it in a script it works properly, and that should be the case for brew shellenv:
% bash script.sh
-zsh

% /bin/bash

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
$ bash script.sh
/bin/bash

Ah, I see -- thanks for the explanation @gromgit

@nihaals Please brew update and see if the shellenv fix solves your issue,

It didn't, about to debug

> /home/linuxbrew/.linuxbrew/bin/brew update
Already up-to-date.
> /home/linuxbrew/.linuxbrew/bin/brew --version
Homebrew 2.4.6
Homebrew/linuxbrew-core (git revision 28e0f3; last commit 2020-07-13)
> /home/linuxbrew/.linuxbrew/bin/brew shellenv
set -gx ...
...
> SHELL=bash /home/linuxbrew/.linuxbrew/bin/brew shellenv
export ...
...

Looking at https://github.com/Homebrew/brew/commit/0f6bc6274f8fc0cfc19636688fc8aa6752d0c296, it doesn't seem to be part of the 2.4.6 tag and isn't listed in the changelog

@nihaals unless you have HOMEBREW_DEVELOPER set you will not see this change until a new tag is released.

Oh, didn't realise that was a feature. Yep, works great!


Dependency error during 'idf.py set-target' (IDFGH-13026) (PACMAN-918)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
ESP-IDF v5.2.2 + ESP32C6
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
I expected to be able to set the project target to esp32c6 and then edit configuration via menuconfig or IDE config editor
What is the actual behavior?
I performed a fresh install of IDE 3.0.0 + IDF 5.2.2 via the offline installer on a new Windows 11 laptop, then tried the following inside the standard 'led_light' example project folder with PS:
install.ps1
export.ps1
idf.py set-target esp32c6
The result is a dependency error that is probably simple, but I don't understand it. Please see my pasted log below.
Steps to reproduce.
In project folder:

install.ps1
export.ps1
idf.py set-target esp32c6

Build or installation Logs.
PS C:\Espressif\workspace\esp-rainmaker\examples\led_light> idf.py set-target esp32c6
Adding "set-target"'s dependency "fullclean" to list of commands with default set of options.
Executing action: fullclean
Build directory 'C:\Espressif\workspace\esp-rainmaker\examples\led_light\build' not found. Nothing to clean.
Executing action: set-target
Set Target to: esp32c6, new sdkconfig will be created.
Running cmake in directory C:\Espressif\workspace\esp-rainmaker\examples\led_light\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DPYTHON=C:\Espressif\python_env\idf5.2_py3.11_env\Scripts\python.exe -DESP_PLATFORM=1 -DIDF_TARGET=esp32c6 -DCCACHE_ENABLE=1 C:\Espressif\workspace\esp-rainmaker\examples\led_light"...
-- Found Git: C:/Espressif/tools/idf-git/2.44.0/cmd/git.exe (found version "2.44.0.windows.1")
-- Component directory C:/Espressif/workspace/esp-rainmaker/components/esp-insights does not contain a CMakeLists.txt file. No component will be added
-- ccache will be used for faster recompilation
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/Espressif/tools/riscv32-esp-elf/esp-13.2.0_20230928/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Espressif/tools/riscv32-esp-elf/esp-13.2.0_20230928/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Espressif/tools/riscv32-esp-elf/esp-13.2.0_20230928/riscv32-esp-elf/bin/riscv32-esp-elf-g++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32c6
Dependencies lock doesn't exist, solving dependencies.
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0)(introduced by component esp_diagnostics)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diag_data_store for dependency espressif/esp_diag_data_store(~1.0)(introduced by component esp_insights)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diagnostics for dependency espressif/esp_diagnostics(~1.0)(introduced by component esp_insights)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0)(introduced by component esp_insights)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp_schedule for dependency espressif/esp_schedule(~1.2.0)(introduced by component esp_rainmaker)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_generator for dependency espressif/json_generator(~1.1.1)(introduced by component esp_rainmaker)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_parser for dependency espressif/json_parser(~1.0.3)(introduced by component esp_rainmaker)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2)(introduced by component esp_rainmaker)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2)(introduced by component esp_schedule)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\jsmn for dependency espressif/jsmn(~1.1)(introduced by component json_parser)
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_insights for dependency espressif/esp_insights(==1.1.0), specified in C:/Espressif/workspace/esp-rainmaker/examples/led_light/main\idf_component.yml
..Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diag_data_store for dependency espressif/esp_diag_data_store(~1.0)(introduced by component espressif/esp_insights), specified in C:/Espressif/workspace/esp-rainmaker/examples/led_light/main\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diagnostics for dependency espressif/esp_diagnostics(~1.0)(introduced by component espressif/esp_insights), specified in C:/Espressif/workspace/esp-rainmaker/examples/led_light/main\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0)(introduced by component espressif/esp_insights), specified in C:/Espressif/workspace/esp-rainmaker/examples/led_light/main\idf_component.yml
...Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0)(introduced by component espressif/esp_diagnostics)
....Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0), specified in C:/Espressif/workspace/esp-rainmaker/components/esp-insights/components/esp_diagnostics\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diag_data_store for dependency espressif/esp_diag_data_store(~1.0), specified in C:/Espressif/workspace/esp-rainmaker/components/esp-insights/components/esp_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_diagnostics for dependency espressif/esp_diagnostics(~1.0), specified in C:/Espressif/workspace/esp-rainmaker/components/esp-insights/components/esp_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.0), specified in C:/Espressif/workspace/esp-rainmaker/components/esp-insights/components/esp_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp_schedule for dependency espressif/esp_schedule(~1.2.0), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_generator for dependency espressif/json_generator(~1.1.1), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_parser for dependency espressif/json_parser(~1.0.3), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2)(introduced by component espressif/esp_schedule), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
....Using component placed at C:\Espressif\workspace\esp-rainmaker\components\jsmn for dependency espressif/jsmn(~1.1)(introduced by component espressif/json_parser), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_rainmaker\idf_component.yml
....Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2), specified in C:/Espressif/workspace/esp-rainmaker/components/esp_schedule\idf_component.yml
.Using component placed at C:\Espressif\workspace\esp-rainmaker\components\jsmn for dependency espressif/jsmn(~1.1), specified in C:/Espressif/workspace/esp-rainmaker/components/json_parser\idf_component.yml
.Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\esp_insights for dependency espressif/esp_insights(~1.0.1), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp_rainmaker for dependency espressif/esp_rainmaker(~=1.0), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp_schedule for dependency espressif/esp_schedule(~1.2.0)(introduced by component espressif/esp_rainmaker), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_generator for dependency espressif/json_generator(~1.1.1)(introduced by component espressif/esp_rainmaker), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\json_parser for dependency espressif/json_parser(~1.0.3)(introduced by component espressif/esp_rainmaker), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
Using component placed at C:\Espressif\workspace\esp-rainmaker\components\esp-insights\components\rmaker_common for dependency espressif/rmaker_common(~1.4.2)(introduced by component espressif/esp_rainmaker), specified in C:/Espressif/workspace/esp-rainmaker/examples/common/app_insights\idf_component.yml
CMake Error at C:/Espressif/frameworks/esp-idf-v5.2.2/tools/cmake/build.cmake:544 (message):
  ERROR: Because no versions of espressif/esp_insights match >1.0.1,<1.1.0

   and espressif/esp_insights (1.0.1) depends on espressif/cbor (~0.6), espressif/esp_insights (>=1.0.1,<1.1.0) requires espressif/cbor (~0.6).

  So, because no versions of espressif/cbor match ~0.6

   and project depends on espressif/esp_insights (~1.0.1), version solving failed.

Call Stack (most recent call first):
  C:/Espressif/frameworks/esp-idf-v5.2.2/tools/cmake/project.cmake:605 (idf_build_process)
  CMakeLists.txt:16 (project)

.-- Configuring incomplete, errors occurred!
See also "C:/Espressif/workspace/esp-rainmaker/examples/led_light/build/CMakeFiles/CMakeOutput.log".
cmake failed with exit code 1, output of the command is in the C:\Espressif\workspace\esp-rainmaker\examples\led_light\build\log\idf_py_stderr_output_13704 and C:\Espressif\workspace\esp-rainmaker\examples\led_light\build\log\idf_py_stdout_output_13704
PS C:\Espressif\workspace\esp-rainmaker\examples\led_light>

More Information.
No response

@mjdswan Yes, you are right. The workaround I've posted is just for the master branch and not for v5.2.2 you are using. I'm sorry but I won't be much of a help regarding this.
We've moved the issue into the component manager repository. Please wait until the team gets back to you.

@dobairoland thank you for the update.

@mjdswan
It looks like this issue didn't present in the existing 1.5 releases of the component manager.
Could you please try one of this 2 workarounds.

Use an older version of the component manager: In your ESP-IDF shell run pip install idf-component-manager==1.4.2
Another approach is to force ESP-IDF 5.2 to accept component manager v2. For this you need to remove the line starting with idf-component-manager from [HOME]\.espressif\espidf.constraints.v5.2.txt to allow 2.0 of the idf-component-manager and install the development version from git:

# remove old version of the component manager
python -m pip uninstall -y idf-component-manager
# install the development version (from the main branch)
python -m pip install git+https://github.com/espressif/idf-component-manager.git@main

@kumekay Thanks, your second approach worked well.  The first approach produced errors regarding extra components it was unable to find, even though they were definitely there in the tree.  After installing idf-component-manager 2.0, those components were found and I'm able to proceed and set the target successfully.

@mjdswan  espidf.constraints.v5.2.txt may be overwritten by install.ps1, but it won't be a problem once we release component manager 2.0


Get feedback on amount of unflushed data in buffers

If you have a strict limit on archive size you need a way to decide whether you can add another file without exceeding your limit. Since the LZMA buffers can be very large this is very hard to predict without assistance of the library because you have to assume the worst case scenario, which is uncompressible files. If the files did actually compress then the worst case estimate means closing the archive way before reaching your strict limit.
It would be nice if the library could expose a way to inspect the amount of data in the buffers and give lower and upper bounds on the output length under the assumption that no further input follows.

After researching this in more depth I've decided to not implement this because it is too complicated. I'm leaving the results of what I found here in case I may come back to it later, or if someone else wants to look into it.
For LZMA you can inspect the following variables to determine (a) how buffered input has been read from the input source but not been processed and (b) how much buffered output has not been written to the output sink:
// mEncoder is `Master.LZMA.CLzmaEnc` - for example the member variable in `AsyncEncoder`

// the number of (unprocessed) input bytes in the LZMA encoder
var pMatchFinder = mEncoder.mMatchFinderBase;
var pMatchFinderCachedBytes = pMatchFinder.mStreamPos - pMatchFinder.mPos + fetched;

// the number of (unflushed) output bytes in the LZMA encoder
var pRangeCoder = mEncoder.mRC;
var pRangeCoderCachedBytes = pRangeCoder.mBuf - pRangeCoder.mBufBase;

At this level the problem is primarily that the variables are not synchronized. It may be possible to turn all writes against them to volatile writes, but it should be measured if volatile writes have negative performance impact when the feature is not used (i.e. when there are no volatile reads). If so, then it shouldn't be done. Reading the variables without synchronization is of course always a last resort option.
Above research only is for the LZMA encoder. It can probably be extended to LZMA2 easily but I have not tried. The real problem is extending it 7z encoders, which is what the actual use case of this feature required. 7z encoders can be configured in arbitrary graphs and there is no obvious way to how report and interpret buffers between nodes.


Specify default value via assignment instead of annotation?

It would be more natural for a default value to be set via a regular java assignment at declaration time. Can this be done?

Did you try it?  Seems like assigning a default value at declaration and omitting the defaultValue annotation part should work (but likely won't find it's way into the usage message block).

Actually I didn't. When I saw the other issues I was hesitant to invest time in giving this library a try. But I believe you and it's good to know. Ideally the documentation should say this somewhere but I value minimalism in getting started so probably there's no remaining action item. Feel free to close this.


Convert "git gud instructions" to "git gud explain"

Most of the time git gud instructions exists to explain what's going on, so it's worth renaming

This is completed now, no?
https://github.com/benthayer/git-gud/projects/1#column-7009882 -> https://github.com/benthayer/git-gud/projects/1#column-7009885


Fix random crash with Plex mdns queries on my network

While i was watching movies all my esp32 based projects crash at the same time every 30minutes. For now I only have the uploaded coredump stack traces the esp's.
This "fix" seems to avoid the crash, but I do not understand why it fixes it.
According sentry entry

I managed to dump the packet that very likely crashed the ESP32

@espressif I can privately share the pcap file if you are interested

Thanks for your contribution.

@0xFEEDC0DE64 Thanks for posting the report with the potential fix!
@peterpoetzi would be much appreciated if you can send me the captured packet to my git-email:
git show 9fc9521 | grep Author

Thank you!

Thanks for sharing the packet logs, I was able to reproduce the issue.
The problem is that mDNS service is registered without an instance (which is supported and the general instance name or hostname is used instead):
    ESP_ERROR_CHECK( mdns_instance_name_set("general-instance") );
    ESP_ERROR_CHECK( mdns_service_add(NULL, "_http", "_tcp", 80, NULL, 0) );

Then, when posting a query for that specific host/instance name, the mdns library incorrectly tries to locate service's instance rather then the global instance. In that sense the proposed fix would be:
diff --git a/components/mdns/mdns.c b/components/mdns/mdns.c
index 0faa0b509d6..909250e7c72 100644
--- a/components/mdns/mdns.c
+++ b/components/mdns/mdns.c
@@ -1553,7 +1553,7 @@ static bool _mdns_service_match_ptr_question(const mdns_service_t *service, cons
         return false;
     }
     if (question->host) {
-        if (strcasecmp(service->instance, question->host) != 0) {
+        if (strcasecmp(_mdns_get_service_instance_name(service), question->host) != 0) {
             return false;
         }
     }

The fix proposed in this PR solve the crash, but wouldn't correctly respond (would never reply).
Is this the way you register the services, using default instance names?

Thanks for your contribution, changes merged with https://github.com/espressif/esp-idf/commit/f46dffca627e9578e49a510580f9754ec1e27e2e.


Add details to readme

Given how this project seems to be heavily inspired by the more popular, baicunko/scanyourpdf, it would probably be a good idea to explain exactly how your application differs in the README file.

Thank you!


About the loss formula

In rvae.py "loss = 79 * cross_entropy + kld_coef(i) * kld".
Could you please explain why it is multiplied by 79 and what's the meaning of kld_coef(i)?

Here you can find meaning of 79

@kefirski Thanks!


Add SBOM support

Adds build-time SBOM support using the syft scanner. Support is added for both Syft JSON & CycloneDX JSON.
This PR runs the syft cli scanner during build against the contents of the application directory. The results of running syft are stored stored as the build SBOM information.
Resolves #106.
Signed-off-by: Daniel Mikusa<EMAIL_ADDRESS>

Pausing as this seems to introduce a build problem. It's breaking the layer reuse/caching. Need to investigate more.


Error when closing socket

Using basic hello-world express application, when closing the socket via CTRL+C (twice) I get the following error output:
Click to view application: https://8ff2-107-132-213-237.ngrok.io
^Cngrok closed socket
ngrok closed socket
ngrok closed tunnel: d1fbfc10e879a390f9fe0a716615b608
node:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: error closing tunnel: Response("No tunnel found with the ID 'd1fbfc10e879a390f9fe0a716615b608'\r\n\r\nERR_NGROK_333\r\n")] {
  code: 'GenericFailure'
}

You should only have to ctrl-c once for an orderly shutdown, so would guess something is blocking, and then the second ctrl-c does a hard kill which doesn't shutdown cleanly. Can you give the example code?

Absolutely, here is my example code:
const express = require('express')
const ngrok = require('@ngrok/ngrok')
const app = express()

app.get('/', (req, res) => {
  res.send('Hello World!')
})

ngrok.listen(app).then(() => {
    const url = app.tunnel.url()
    console.log("Click to view application: " + url);
})

Adding, I've tried using one CTRL+C and it still occurs, seems like it doesn't matter whether it's one or two.

Shuts down cleanly for me after a single ctrl-c on mac-aarch, if you've made a request there's a few seconds of delay as things are torn down. What os and architecture are you on?

What architecture

MacOS M2, 13.0 (22A380)
Running VSCode
Running through npm via npm run start
After retrying without npm looks like it's isolated to npm run usage.

Turns out npm double-taps SIGINT to the underlying process, so the handler code is executed twice in very quick succession, will add protections around this.

Updated in https://github.com/ngrok/ngrok-js/pull/51, released in 0.4.1


HBASE-28632 Make -h arg respected by hbck2 and exit if unrecognized a…

https://issues.apache.org/jira/browse/HBASE-28632
The commands in hbck2 do not accept -h in order to display the usage guide. Adding that functionality with this PR. Before the command is performed, the -h option is checked and if it exists, then the command specific usage guide is printed.
Example command
addFsRegionsMissingInMeta -h
Example output
usage: HBCK2 [OPTIONS] COMMAND <ARGS>
Options:
 -d,--debug                                       run with debug output
 -h,--help                                        output this help message
 -p,--hbase.zookeeper.property.clientPort <arg>   port of hbase ensemble
 -q,--hbase.zookeeper.quorum <arg>                hbase ensemble
 -s,--skip                                        skip hbase version check
                                                  (PleaseHoldException)
 -v,--version                                     this hbck2 version
 -z,--zookeeper.znode.parent <arg>                parent znode of hbase
                                                  ensemble
Command:
 addFsRegionsMissingInMeta [OPTIONS]
      [<NAMESPACE|NAMESPACE:TABLENAME>...|-i <INPUTFILES>...]
   Options:
    -i,--inputFiles  take one or more files of namespace or table names
    -o,--outputFile  name/prefix of the file(s) to dump region names
    -n,--numLines  number of lines to be written to each output file
   To be used when regions missing from hbase:meta but directories
   are present still in HDFS. Can happen if user has run _hbck1_
   'OfflineMetaRepair' against an hbase-2.x cluster. Needs hbase:meta
   to be online. For each table name passed as parameter, performs diff
   between regions available in hbase:meta and region dirs on HDFS.
   Then for dirs with no hbase:meta matches, it reads the 'regioninfo'
   metadata file and re-creates given region in hbase:meta. Regions are
   re-created in 'CLOSED' state in the hbase:meta table, but not in the
   Masters' cache, and they are not assigned either. To get these
   regions online, run the HBCK2 'assigns'command printed when this
   command-run completes.
   NOTE: If using hbase releases older than 2.3.0, a rolling restart of
   HMasters is needed prior to executing the set of 'assigns' output.
   An example adding missing regions for tables 'tbl_1' in the default
   namespace, 'tbl_2' in namespace 'n1' and for all tables from
   namespace 'n2':
     $ HBCK2 addFsRegionsMissingInMeta default:tbl_1 n1:tbl_2 n2
   Returns HBCK2  an 'assigns' command with all re-inserted regions.
   SEE ALSO: reportMissingRegionsInMeta
   SEE ALSO: fixMeta
   If -i or --inputFiles is specified, pass one or more input file names.
   Each file contains <NAMESPACE|NAMESPACE:TABLENAME>, one per line.
   For example:
     $ HBCK2 addFsRegionsMissingInMeta -i fileName1 fileName2
   If -o or --outputFile is specified, the output file(s) can be passed as
    input to assigns command via -i or -inputFiles option.
   If -n or --numLines is specified, and say it is  set to 100, this will
   create files with prefix as value passed by -o or --outputFile option.
   Each file will have 100 region names (max.), one per line.
   For example:
     $ HBCK2 addFsRegionsMissingInMeta -o outputFilePrefix -n 100
     -i fileName1 fileName2
   But if -n is not specified, but -o is specified, it will dump all
   region names in a single file, one per line.
   NOTE: -n option is applicable only if -o option is specified.

Is a backport necessary? Can we use the upstream version that has this already?

Is a backport necessary? Can we use the upstream version that has this already?

I thought that a backport is necessary in order to use this change. How can we use the upstream change directly?


arrow 1.2.2

Update arrow to 1.2.2
Changelog: https://github.com/arrow-py/arrow/blob/1.2.2/CHANGELOG.rst
License: https://github.com/arrow-py/arrow/blob/1.2.2/LICENSE
Requierements:

https://github.com/arrow-py/arrow/blob/1.2.2/setup.py
https://github.com/arrow-py/arrow/blob/1.2.2/requirements/requirements.txt
https://github.com/arrow-py/arrow/blob/1.2.2/requirements/requirements-tests.txt

Actions:

Make noarch: python
Fix the test issue with  bad escape \d at position 7 started to happen after version regex 2022.3.15
Update test/commands

There is a missing simplejson on s390x and we should rebuild it https://github.com/AnacondaRecipes/simplejson-feedstock/pull/6

Tests on s390x fail because dateparser requires tzlocal but it's currently not available on s390x


Error: DLL load failed

Describe the bug
Program not work.
C:\Users\guyan\AppData\Local\Programs\Python\Python36\lib\site-packages\onnxruntime\capi\_pybind_state.py:12: UserWarning: Cannot load onnxruntime.capi. Error: 'DLL load failed: The specified module could not be found.'
  warnings.warn("Cannot load onnxruntime.capi. Error: '{0}'".format(str(e)))
Traceback (most recent call last):
  File ".\inference.py", line 1, in <module>
    import onnxruntime
  File "C:\Users\guyan\AppData\Local\Programs\Python\Python36\lib\site-packages\onnxruntime\__init__.py", line 21, in <module>
    from onnxruntime.capi._pybind_state import RunOptions, SessionOptions, get_device, NodeArg, ModelMetadata
ImportError: cannot import name 'RunOptions'

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Windows 10 Enterprise

ONNX Runtime installed from (source or binary):
pip install onnxruntime

ONNX Runtime version:
0.1.4

Python version:
3.6.6

GCC/Compiler version (if compiling from source):

CUDA/cuDNN version:

GPU model and memory:

To Reproduce
run the following code:
import onnxruntime

session = onnxruntime.InferenceSession("alexnet.onnx")

Expected behavior
No error messages.

I got the same question.

You may drag the DLL into Dependency Walker, to get known which DLL was missed.

Your CUDA DLLs are not in the path. Hence they can't be found. Just add them to your environment path.

Please re-open if the suggested solution doesn't work for you. Thanks for your time in trying out onnxruntime.


Workload argument splitting does not respect quotes

Brief summary
When the operator takes the workload arguments, it splits by spaces and does not respect quotes.
k6-operator version or image
0.0.8
K6 YAML
apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  creationTimestamp: "2023-03-30T09:48:06Z"
  generation: 1
  labels:
    k6-workload-id: benchmark-pre-test-328cxme35q2gw
    test-id: pre-test
  name: benchmark-pre-test-328cxme35q2gw
  namespace: k6-tests
  resourceVersion: "104356441"
  uid: f46e0896-b34c-48df-9297-1d8ba9fc8885
spec:
  arguments: --tag=test_id=pre-test -e 'QUERY=*[_type == "collection"][0..10]'
  parallelism: 10
  runner:
    image: eu.gcr.io/sanity-cloud/xk6-sanity
    resources:
      limits:
        cpu: "3"
        memory: 8Gi
      requests:
        cpu: "3"
        memory: 8Gi
    securityContext: {}
    serviceAccountName: k6-test-runner
  script:
    configMap:
      file: test.js
      name: benchmark-pre-test-328cxme35q2gw-script
    volumeClaim:
      name: ""
  scuttle: {}
  starter:
    metadata: {}
    resources: {}
    securityContext: {}
status:
  stage: created

Other environment details (if applicable)
No response
Steps to reproduce the problem
From my spec:
spec:
  arguments: --tag=test_id=pre-test -e 'QUERY=*[_type == "collection"][0..10]'

Expected behaviour
This is the command argument list I expected:
    - -e
    - "QUERY=*[_type == "collection"][0..10]"

Actual behaviour
This is transformed by the operator into the following pod:
spec:
  automountServiceAccountToken: true
  containers:
  - command:
    - k6
    - run
    - --quiet
    - --execution-segment=7/10:8/10
    - --execution-segment-sequence=0,1/10,2/10,3/10,4/10,5/10,6/10,7/10,8/10,9/10,1
    - -e
    - '''QUERY=*[_type'
    - ==
    - '"collection"][0..10]'''
    - /test/test.js
    - --address=<IP_ADDRESS>:6565
    - --paused
    - --tag
    - instance_id=8
    - --tag
    - job_name=benchmark-pre-test-328cxme35q2gw-8

Notice how it has broken the -e value into three pieces and ignored the quotes.

Thanks for opening this @atombender!
I think the workaround in case of env vars could be with using --include-system-env-vars option?
But either way, the parsing of arguments in the k6-operator is rather simple and doesn't cover quotes just as you noted. In addition to env vars, there are other options in k6 that can rely on quotes as well even if they're probably not encountered as much in k6-operator usage, like --block-hostnames or --log-output.

Yes, we use the --include-system-env-vars workaround, but I'd prefer to avoid this to avoid leaking sensitive environment variables.

It seems I forgot to link it, but there's an issue for this actually:
https://github.com/grafana/k6-operator/issues/162


remove online demo table in the navigation bar

Please review #249

@aybcoo Please check:

docs.js#L98
site.js#L66

@aybcoo Please check:

docs.js#L98
site.js#L66

@chengshiwen I will fix it ，Thank you！

@chengshiwen I will fix it ，Thank you！

@aybcoo Please check again:

docs.js#L93
site.js#L63

@chengshiwen  https://github.com/apache/incubator-dolphinscheduler-website/pull/251

@aybcoo Please check again:

docs.js#L93
site.js#L63

@chengshiwen  https://github.com/apache/incubator-dolphinscheduler-website/pull/251


Question about multipage search

Hi, I know this is kind of old, but am trying to tackle a similar issue in my current role. We don't have much engineering support, so I'm shooting in the dark a bit. Could you explain how you got multipage search to work? I've already implemented multipage, albeit differently than you did.
Essentially, my .erb file checks an attribute in index.html.md file and, if set to True, loads that index.html.md file. So, I have a few pages like index.html.md, guides.html.md, etc.
Search, however, only searches the current page.

I think that search was one thing I didn't get around to fixing, but I believe that it can be made to work in much the same way as the toc changes (preserve original search, but also use data.yml for new search), the problem I ran into is having the js search know what was in data.yml. This is where I left off since this was a side project at my old job and I was pulled off it as it were.
The problem though is that the search uses the entire body of an entry, and the data.yml doesn't have that. It might could be modified to have keywords for each data.yml entry, tho... At which point you would only need pass in the data.yml conditionally to the js and make some modifications in the search index population: https://github.com/E1337Kat/slate_server/blob/e1aa4bff702960689e8924ed713a51176f56efbf/app/assets/javascripts/app/_search.js#L22-L34
I might try and work that out actually. It'd be  nice to have a full product.

Thanks for the note! I ended up solving it by editing the populate function to index the other pages, then another function that page data. This works now because we don't have too many pages, and they're not too long. Multi-page was mostly about content organization for us.

Smart idea.

Multi-page was mostly about content organization for us.

That is how I felt about multi-page as well.


https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/429

Request type

[ ] New documentation
[ ] Correction or update

Page to change
If this request relates to an existing article, please give its URL:
Details
Please describe the change you are requesting. If you know of technical experts who can review the change, please mention them.
Related issues
If this request relates to other issues in Bugzilla or GitHub, please provide links:

Hi @JassimAbood! Is there a problem with this page that you want to report?


wgsl shaders without @vertex/@fragment entry point cause panic

Bevy version
v0.9.1
What you did
Hot-Reloading of wgsl shaders, triggering the reload by saving with vscode (on Windows 10).
What went wrong
When vscode saves to disk, bevy seems to randomly pick up an empty file first, which is technically valid wgsl file, but misses an entry point. This missing entry point causes a panic (see error and backtrace below).
I also tried saving the shader in Notepad++ instead, which causes the same issue but seemingly more often (after very limited testing).
Finally I also tried Windows Notepad (the old Window 10 version) for the fun of it, but to my surprise, this one seems to work fine no matter how much I save (yes, I modified the content inbetween each save). Now if only Windows Notepad was a decent editor 😛

Is a panic considered as works-as-intended for this case in particular? I don't think so, but if it were, that would be a very unfortunate coincidence, considering that regular shader compilation errors do not panic and simply log the error and continue without the shader, making hot-reloading of shaders an absolute joy (as long as the empty-file issue doesn't occur).

Error and Backtrace

2022-12-24T13:06:08.385322Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (2)' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_render_pipeline
      note: label = `position_based_pbr_opaque_mesh_pipeline`
    error matching VERTEX shader requirements against the pipeline
    unable to find entry point 'vertex'

', D:\dev\Rust\.cargo\registry\src\github.com-1ecc6299db9ec823\wgpu-0.14.2\src\backend\direct.rs:2403:5
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library\std\src\panicking.rs:575
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library\core\src\panicking.rs:65
   2: <&T as core::fmt::Debug>::fmt
   3: <wgpu::backend::direct::Context as wgpu::Context>::device_create_render_pipeline
   4: wgpu::Device::create_render_pipeline
   5: bevy_render::render_resource::pipeline_cache::PipelineCache::process_queue
   6: <bevy_ecs::system::function_system::FunctionSystem<In,Out,Param,Marker,F> as bevy_ecs::system::system::System>::run_unsafe
   7: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
   8: async_task::raw::RawTask<F,T,S>::run
   9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
  11: std::thread::local::LocalKey<T>::with
  12: std::thread::local::LocalKey<T>::with
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', D:\dev\Rust\.cargo\registry\src\github.com-1ecc6299db9ec823\bevy_tasks-0.9.1\src\task_pool.rs:273:45
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library\std\src\panicking.rs:575
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library\core\src\panicking.rs:65
   2: core::panicking::panic
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library\core\src\panicking.rs:115
   3: <&mut F as core::future::future::Future>::poll
   4: std::thread::local::LocalKey<T>::with
   5: bevy_tasks::task_pool::TaskPool::scope
   6: <bevy_ecs::schedule::executor_parallel::ParallelExecutor as bevy_ecs::schedule::executor::ParallelSystemExecutor>::run_systems
   7: <bevy_ecs::schedule::stage::SystemStage as bevy_ecs::schedule::stage::Stage>::run
   8: <bevy_render::texture::fallback_image::FallbackImage as bevy_ecs::world::FromWorld>::from_world
   9: bevy_app::app::App::update
  10: winit::platform_impl::platform::event_loop::EventLoop<T>::run_return::{{closure}}
  11: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
  12: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::register_window
  13: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::move_state_to
  14: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
  15: winit::platform_impl::platform::event_loop::runner::EventLoopRunner<T>::catch_unwind
  16: winit::platform_impl::platform::event_loop::EventLoopThreadExecutor::execute_in_thread
  17: CallWindowProcW
  18: DispatchMessageW
  19: SendMessageTimeoutW
  20: KiUserCallbackDispatcher
  21: NtUserDispatchMessage
  22: DispatchMessageW
  23: winit::platform_impl::platform::event_loop::EventLoop<T>::run_return
  24: winit::platform_impl::platform::event_loop::EventLoop<T>::run
  25: core::ptr::drop_in_place<hashbrown::map::HashMap<winit::window::WindowId,winit::window::Window>>
  26: <bevy_winit::WinitPlugin as bevy_app::plugin::Plugin>::build
  27: bevy_winit::winit_runner_with
  28: core::ops::function::Fn::call
  29: bevy_app::app::App::run
  30: wgpu_core::device::queue::PendingWrites<A>::dispose

I did some testing and notify does send two Modify(Any) events. The only discernible difference seems to be that the file has a size of 0 at the moment of the first event and a valid size at the moment of the second event.
This is probably because of multiple Windows File API operations being done in succession like writing, setting attributes etc.
Since we don't get the type of Modify event being triggered there is no real way to know when the file is ready for ingestion except from reading the file size and checking that it's not 0.
This could be a quick fix for this problem.
If this is the rout we want to take I could try and implement this.

A file size of 0 may be a valid case for some asset types, it can't just be ignored.
A proper fix would be to keep a queue of file events from notify, and only send one to Bevy events when there hasn't been a new one in a few milliseconds

The only problem with that approach could be how to define a few milliseconds. Did some testing with Notepad++ and the time between events could be anywhere from 1.2ms for a few KB of data to 122ms for a 40+MB file. And that's on an SSD, HDDs are still in use and their write time could be significantly higher.
Maybe we could make the timeout configurable? That would allow the user to adapt it to their use case.

Acceptable time to wait is very dependent on feeling, but around 500ms should be ok I think and cover most cases...

If we're just looking for workarounds rather than preventing the panic in wgpu:
What about simply treating empty wgsl files as an error up front, right before they get sent over to wgpu? Still log some kindof error (and maybe mention the whole file size 0 thing, to avoid others from reporting it because they think it's an actual error), but as long as it's not being sent over to wgpu we can avoid the panic.

A proper fix would also be nice though, as it might happen that you accidentally delete or comment out your entry point, which will still lead to a panic. While admittedly rare, it would be nicer to avoid the panic and handle it more like other errors (as in, just log the error and keep running).

I think instantly reloading the shader asset if changed on disk is a bad idea in general. Many more possible states, that can mess with your program. E.g. even a simple logic problem in your shader might force you to restart, since the program is e.g. reusing a baked texture from the shader.
A much better alternative would be to only notify the program of changes on disk, and then let the game developer choose when to reload in game with a hotkey.
From API side I think we should provide events / status of changed asset state on disk, and a way to reload easily with one function call.
This behavior could be added without breaking backwards compatibility by adding a property auto_apply_changes: bool to AssetPlugin, which defaults to true.


chore: update gradle wrapper to 6.3 in rules_gapic/java

ran gradle wrapper --gradle-version 6.3
I am not sure what the implications of this are downstream. I need this for a newer version of signing.

@vam-google ptal


How to create multilocale form for localized fields

I'm working on multilanguage website, that's going to show visitors some localized information.
To fill in this information I'm going to create multilocale form in back office application that has few fields for each localized attribute (field/locale). Attributes use localize: true approach. But currently I don't see any way how to build such form. Is it possible to create some mechanism in mongoind serialization to do this? maybe.. does it exist already?

Instead of the normal field name, use the field translations name. Ie:
class Product
  include Mongoid::Document
  field :name, localize: true
end

# The getter for all translations:
user.name_translations

# The setter for all translations:
user.name_translations=

You just create an input that will submit to name_translations= in this case with a hash of locale/value pairs.

Thanks, already got it.
Maybe this can be helpful for somebody:
class Category
  include Mongoid::Document

  field :name, type: String, localize: true
end

      <%= f.fields_for :name_translations do |fo| %>
        <%= fo.label :ru %>
        <%= fo.text_field :ru %>
        <%= fo.label :en %>
        <%= fo.text_field :en %>
      <% end  %>

Yeah I'll be sure to put it in the documentation for the next release.

The code above doesn't work for editing - text fields values aren't populated back to the form. Is this known issue (seems I read somewhere about such problem)


fix(swagger): Build swagger docs w/ env vars.

The problem which this pr solves it to allow the example values for swagger to be environment specific. If a user goes to TREST they should see testnet default values. If they go to REST they should see mainnet default values.
The fixtures for each env are in swaggerJSONFiles/fixtures. Each object has a key property which is the path of the endpoint. The name is the parameter and the value is the example value.
If we add new endpoints we need to remember to add them for mainnet and testnet here as well.

Pull Request Test Coverage Report for Build 860

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

Totals

Change from base Build 854:
0.0%

Covered Lines:
2493

Relevant Lines:
2916

💛  - Coveralls


Coding conventions (SwiftLint)

Suggesting a New Feature
Hi folks, I just came here and I see something. Lona is in the first stage of development and still missing coding conventions. There are also have some invalid configs. It would be great if we have rules for coding. It makes Lona code readable and clean.
Proposed Implementation

What do you guys think about to add SwiftLint to Lona?
Remove invalid configs (invalid target) and update .gitignore.
After adding SwiftLint, we will have a lot of convention warnings => refactor it.

Submitting a Bug Report

If you guys interesting in my suggestion, I can give a PR 😄

SwiftLint is 💯 . Thanks for adding it!


SQL Client with JDBC URL provided as options results in a compilation error

Description:
endpoint sql:Client testDB {
username: "SA",
password: "",
options: {url:"jdbc:hsqldb:hsql://localhost:9001/TEST_SQL_CONNECTOR"}
};

With new ballerina data clients above can be achieved as follows.
import ballerina/jdbc;

endpoint jdbc:Client testDB {
        url: "jdbc:hsqldb:file:./target/tempdb/TEST_SQL_CONNECTOR",
        username: "SA",
        poolOptions: { maximumPoolSize: 1 }
    };