Unable to get Tracking Information about a specific order

When I use the "GetOrderRequestType" function to get the specific order I bought, I do not get the Tracking information for the order (carrier / Tracking Number, etc), but when I check online the seller already listed the tracking number on the package.
I dont know what to do at this point.
The code I use (simplified) is this to make the call:
`
$request = new Types\GetOrdersRequestType();
$request->DetailLevel[] = "ReturnAll";
$request->NumberOfDays = 10;
$ordersArray = new Types\OrderIDArrayType();
$order = (example) 111-111;
$ordersArray->OrderID[] = $order;
$request->OrderIDArray = $ordersArray;
$request->OrderRole = "Seller";
    $response = $service->getOrders($request);

`

before posting here, you should be sure that this is related to the SDK. to check this, use the ebay api test tool to find out, if the response contains the info you are looking for, if it´s not there, the SDK cannot provide it - of course 😏


[BUG] saveVideo method doesn't save video in Android

Describe the bug
await PhotoManager.editor.saveVideo(File(file.path)) is not working in Android
here my file.path comes from video that is captured by camera plugin
Working in iOS
Description
Above method returns object of AssetEntity? but in Android it returns null
Expected behavior
Above method should work on also Android
Flutter version
2.2.3
Smartphone

Device: Asus Zenfone Max Pro M1
OS: Android 11

title is a required argument in the code at present. Closing as it'll be solved in the next major release.

You probably un-required title at some point since I just encountered the same exact issue as this user. Adding a title fixed my problem. Please either require title or add "title is required on Android" in the docstring of editor.saveVideo()

You probably un-required title at some point since I just encountered the same exact issue as this user. Adding a title fixed my problem. Please either require title or add "title is required on Android" in the docstring of editor.saveVideo()

The file path is required when saving the video and the file extension will be using for the type recognition. Do you still running into the issue using v3.3.0?


Issue reporting in Wikibase edit schema, focused on the Wikimedia Commons use case

When using OpenRefine's schema editor to prepare edits and uploads to Wikimedia Commons, users should get clear feedback (in the 'issues' tab) about what may go wrong in their edit/upload batches.
This feedback will in some cases be different from the generic feedback for any Wikibase (i.e. not just constraint related) and specific to Wikimedia Commons: think about feedback that concerns duplicate file names, file names with invalid characters...

[ ] @trnstlntk to write specifications for this (what potential problems do we need to cover here; draft copy for clear error messages?..) - deadline May 31, 2022
[ ] @wetneb to build this - deadline June 30, 2022

I hope I got / remembered this one right from our team roadtripping exercise last week. Feel free to tweak.

This one fell between the cracks somehow. Error reporting is important, and we talked about it quite a bit in various contexts.
I feel inclined to close this task (merely for cleanup purposes) because we are tackling this partly in different areas, example: https://github.com/OpenRefine/OpenRefine/issues/5032

#5032 is about reporting errors after we attempted the upload
This GitHub issue seems to be about the "Issues" tab, which is about reporting problems before the upload (which is something we already have the infrastructure for). It is worth opening issues for issues related to file upload that should be flagged in this Issues tab, for instance like this one: https://github.com/OpenRefine/OpenRefine/issues/5181

There's also this issue: https://github.com/OpenRefine/OpenRefine/issues/5192
I agree that separate issues are better as they emerge (I'm not sure if I'll ever be able to comprehensively list everything that may go wrong).


D3 v7 support

closes #365, This PR adds support for d3 v6!
Resources

selection.datum function.
drag.on function
d3 v6 changes.

@danielcaldas Is the README.md treated like DOCUMENTATION.md? Should I discard my changes to README.md?

Whats the ETA for this release @danielcaldas ?

@danielcaldas @antoninklopp guys a whole new major version of d3 was released and this PR wasn't merged 😆.
Resources for this PR
--env=jsdom
rename to babel.config.js, jest doesn't recognize .babelrc for some reason.


Allow notifications to be hoverable / closeable on modals

Also moves them to the bottom
Related discussion with context and screenshots

Assuming this doesnt break autoscroll 😆
Lol same joke at the same time :)

Looks good, does it work properly if the page is server side rendered?

Yes afaict when the page is SSRd react still makes a pass (setup JS events, hooks, and run all js code)
However this raises a good point => isolating the portal in NotificationList to be sure react does not re-render what isn't needed

Actually AFAICT react will only rerender the notificationlist in this case so no real need to change


(node:8808) fs: re-evaluating native module sources is not supported

lovefield quickstart, updated version dependency to latest 2.1.8

This is a bug on glob's npm package, which refers to an old version of graceful-fs. There's nothing Lovefield can do with it since we don't own glob.


fix(babysit): do not error out for missing config

Follow-up on packit/packit#1566
Signed-off-by: Matej Focko<EMAIL_ADDRESS>TODO:

[ ] Write new tests or update the old ones to cover new functionality.
[x] Update doc-strings where appropriate.
[x] Update or write new documentation in packit/packit.dev.

yay, less sentry issues!


github-pages minimal-mistakes-jekyll jekyll-sitemap version conflict

When installing the latest 4.2.1, bundler throws:
   Bundler could not find compatible versions for gem "jekyll-sitemap":
     In snapshot (Gemfile.lock):
       jekyll-sitemap (= 0.12.0)

     In Gemfile:
       github-pages (= 112) was resolved to 112, which depends on
         jekyll-sitemap (= 0.12.0)

       minimal-mistakes-jekyll (= 4.2.1) was resolved to 4.2.1, which depends on
         jekyll-sitemap (~> 1.0)

It appears the github-pages gem that I use for bootstrapping jekyll (but is also used for any github page), wants jekyll-sitemap (= 0.12.0) but minimal-mistakes-jekyll wants jekyll-sitemap (~> 1.0).
The latest version of github-pages (120) still requires the old jekyll-sitemap version: https://rubygems.org/gems/github-pages/versions/120.
Any chance to losen the dependency on jekyll-sitemap, or should I rather file a bug report with GitHub instead?
Thanks for minimal mistakes - I love it

It seems like this problem will go away with https://github.com/github/pages-gem/pull/409
Sorry for the noise!

The other option is to use the Jekyll gem in your Gemfile instead of github-pages. Minimal Mistakes doesn't work on GitHub Pages as a theme gem anyways since there are only a few themes whitelisted currently (all GH owned owns).


implement simplified precedence handling

References #2 .

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@100f851). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   97.80%
=========================================
  Files             ?        6
  Lines             ?      319
  Branches          ?        0
=========================================
  Hits              ?      312
  Misses            ?        7
  Partials          ?        0

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 100f851...ac0137d. Read the comment docs.


Exclude sensor from arming prevention mechanism

Hi Niels,
Is there any possibility to exclude a sensor from preventing an arming action?
For example if my waterleak sensor somehow lost the connection to HA and still want the alarm to arm, exclude that sensor from blocking the arming action.
I know I can get the notification with the force arm action, but I would rather not get this notification for configured sensors.

Hi Bob,
If you keep this setting OFF, the sensor should not trigger or block arming when it has state unavailable or unknown

Otherwise there is no functionality to "automatically bypass" sensors.
With this the security of your house becomes a bit questionable, I rather have the user confirm (every time) that they are OK with bypassing sensors.

Hi Bob,
If you keep this setting OFF, the sensor should not trigger or block arming when it has state unavailable or unknown

Otherwise there is no functionality to "automatically bypass" sensors.
With this the security of your house becomes a bit questionable, I rather have the user confirm (every time) that they are OK with bypassing sensors.

Thanks that'll help!

Thanks that'll help!


Fixed commit link in changelog_html.mustache

Generated commit link was not working due to incorrect basepath
Generated commit link was not working due to usage of shortened commitID instead of full commitID

Thanks!

Wow - that was fast! Thanks


Skip generating rollup task with all merged segments when "skipAllMerged" mode is enabled

This PR adds a filtering step during the minion task generation process to skip generating rollup task with all merged segments.

For non rollup task, the task generation process stays the same.
For rollup task, if some of the input segments are not merged, the process stays the same.
For rollup task, if all input segments are all merged but the target merge level is higher, the process stays the same. E.g. input segments are merged at 5mins but the target merge level is 1 day then we still generate the rollup tasks.
For rollup task, if all input segments are all merged at the target merge level, skip generating the task.

Since these segments cannot be further rolled up, this change can help improve the task execution performance by skipping rerunning these tasks.

Hi @jtao15 could you help review this change? Thank you!

Codecov Report

Merging #10979 (fa32382) into master (8170d43) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #10979      +/-   ##
==========================================
- Coverage    0.11%    0.11%   -0.01%
==========================================
  Files        2189     2189
  Lines      118056   118064       +8
  Branches    17872    17874       +2
==========================================
  Hits          137      137
- Misses     117899   117907       +8
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
?

integration1temurin17
?

integration1temurin20
0.00% <0.00%> (?)

integration2temurin11
?

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
?

unittests2temurin11
0.11% <0.00%> (-0.01%)
:arrow_down:

unittests2temurin17
0.11% <0.00%> (?)

unittests2temurin20
0.11% <0.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...on/tasks/mergerollup/MergeRollupTaskGenerator.java
0.00% <0.00%> (ø)

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

@Jackie-Jiang
I believe the intention is to introduce a feature that allows skipping merged segments in cases of minion instability. When there is a failed task for a specific bucket and all other tasks succeed, the current code will reschedule all segments for that bucket, including the merged segments. The proposed change aims to use less minion resources by skipping the rescheduling of merged segments in such scenarios, particularly for large tables.

In certain cases, such as when input segments consist entirely of spilled-over data and have small sizes, there is a possibility of having fractions due to the proposed change. Do we want to have this skipping feature as an option?

@Jackie-Jiang @jtao15 Your concern make sense. I'm thinking we can make this an optional mode like the 'processAll' mode so that people can opt in to skip.

@jtao15 I've added a new mode "skipAllMerged" so we will only skip generating the task with all merged segments when this mode is enabled. Could you help take a look? Thank you!

@jtao15 @zhouxiz9 I synced up with @jtao15 yesterday. It looks that the issue that we need to address 2 things:

detect the failure issue earlier than 24 hours.
optimize the runtime by only running the failed portion.

It looks that this PR potentially improve 2; however, this may not address the issue that @zhouxiz9 and @jtao15 is currently facing. We will revisit the PR once the root cause of the ongoing is identified.

Hi @snleee, I synced with @jtao15 today and understand that a more comprehensive design is needed to cover the cases such as late events and spill-over. The current fix is only solving part of the problem. I'll close this PR and create a new one once that design is ready.
Since we are facing the minion delay issue (due to repetitively merging already merged segments) in production, a short term fix is needed. I've created another PR to make MaxAttemptsPerTask configurable so that we can try to increase this value and to better handle the transient errors. Please let me know if that works.


New lines rendering as spaces in mustache templates

For whatever reason, text files that are parsed by mustache are rendering new lines as spaces on output. When I parse files using some other mustache implementation (Hogan.js, e.g.), this does not occur.

+1

+1

+1

You can circumvent this by using  to mark newlines.

+1

there is another issue on this matter: https://github.com/Marak/node_mailer/issues/32 which explains this behavior.

Ahh, that makes it make sense ... thanks @topliceanu

+1

@topliceanu Do we know if there is a workaround for this?


Add examples for styling Primitives with Styled Components

I'm using Styled Components for my personal project and I intend to enforce it as my main tool for styling, even though Stitches does have its merits. However, since the few examples available in the docs only use Stitches, I end up having to maintain both. This addition would offer better versatility for a wider range of development stacks.

We're actually leaning towards vanilla CSS examples rather in the long term.
At the moment though, I'm curious why you feel the need for styled-components examples seeing that the stitches API is pretty much the same. Is it not clear how you would go about styling things with styled-components?

I'm using Styled Components for my personal project and I intend to enforce it as my main tool for styling, even though Stitches does have its merits. However, since the few examples available in the docs only use Stitches, I end up having to maintain both. This addition would offer better versatility for a wider range of development stacks.

@sidneifjr I'm using styled-components too and their syntax is similar to stitches
An example

Then use as


Support Cloudflare with Nginx for Digital Ocean Droplet

In order to prevent DDOS and protect the service better, it'd nice to introduce Cloudflare.
On the other hand, Nginx is responsible for proxying and hiding the port :7300.
Acceptance Criteria

Support Cloudflare
Setup Nginx and expose default port :80

Nginx + Go server : https://www.digitalocean.com/community/tutorials/how-to-use-martini-to-serve-go-applications-behind-an-nginx-server-on-ubuntu

Cloudflare SSL and Authenticated Pull Origin : https://www.digitalocean.com/community/tutorials/how-to-host-a-website-using-cloudflare-and-nginx-on-ubuntu-16-04

Done: From now we could access by https://megaton.xyz 👨💻


Update the PreferNominatedNode from ALPHA to BETA

xref #https://github.com/kubernetes/enhancements/issues/1923

/cc @Huang-Wei

/lgtm
And I suppose the other cascading changes will be applied by an automation script.

And I suppose the other cascading changes will be applied by an automation script.

Yes, I did that initially, pls see: https://github.com/kubernetes/website/commit/1c73213cfa1be0d0b3344497f1383f6a5a70bf19,
but that needs involvement from lots of OWNERS, so let's just leave that for a auto-generated PR instead.

/assign @tengqm
Hi Qiming, could you pls help to approve this, we still need get this doc in 1.22 for beta, pls see: https://github.com/kubernetes/enhancements/issues/1923

/hold
this is already covered by https://github.com/kubernetes/website/pull/28644, will close this one when that is got merged.

also, this shouldn't be open against main the way that it is right now, it should be open against dev-1.22. or split and add 1.21 changes to main and 1.22 changes to dev-1.22

also, this shouldn't be open against main the way that it is right now, it should be open against dev-1.22. or split and add 1.21 changes to main and 1.22 changes to dev-1.22

thanks @PI-Victor , I am going to close this one,  https://github.com/kubernetes/website/pull/28644 is opened on the right code branch.


CI: Fixing Cloudflare deploy

What is it?

[ ] Feature / enhancement
[x] Bug
[ ] Docs / tests

Description
Fixing cloudflare deploy scripts
Please don't merge it yet, I'm still trying to fix stuff (I'll merge it when done)

FYI @tleperou I needed to fix a lot of linting issues for using "use" methods in conditionals etc
Please review the changes
Thanks 🙏


Generic extended jacobian with interface types

Code review PR
FollowUp of #5

ToDo:

InterfaceJointStates: publish joint_states instead of *controller/command
KinematicExtensionLookAt: append columns to reflect LookAt chain (lin + rotX, rotY, rotZ)

Several remarks have been addressed according to this CodeReview PR

Why is this package called "cartesian_controller" although it doesn't have anything in common with a controller.
The real PID "cartesian_controller" functionality is located in the FrameTracker package.
Also thinking about ICRA and other future presentations it is quite confusing to hear "cartesian controller" and all the package does is calculation and publication of trajectories or PTPs and so on.
The package should be renamed to clarify what it is responsible for!
Like before PathBroadcaster, TrajectoryBroadcaster, TrajectoryGenerator, PathGenerator ...

Prepared the cob_twist_controller package for doxygen automatic doc generation.
To get a good documenation it is necessary to provide comments on the code.
Please add comments to the kinematic extension module: E.g. to clarify why it is necessary to have KinematicExtension6D base, what method processResultExtension stands for, and so on.

doxygen comments added in cob_twist_controller!
All comments considered, thus closing this Code Review PR!


Surprising and unclear behavior of package --standalone and package --assembly

scala-cli 0.19.0
When comparing the following invocations:

scala-cli package --standalone test.scala --output standalone.jar
scala-cli package --assembly   test.scala --output assembly.jar
scala-cli package --standalone test.scala --output standalone-no-preamble.jar --preamble=false
scala-cli package --assembly   test.scala --output assembly-no-preamble.jar --preamble=false

The result are 4 files:
1) -rwxrwxr-x 7,1M standalone.jar
2) -rwxrwxr-x 6,9M assembly.jar
3) -rwxrwxr-x 7,1M standalone-no-preamble.jar
4) -rwxrwxr-x 6,9M assembly-no-preamble.jar

I observe the following inconsistencies:
• 1 and 3 (standalone) are larger than 2 and 4 (assemblies) even though they seem functionally equivalent.
• 1 and 3 (standalone) require about 120ms (depends on the system in question, but it is a lot) of additional startup time compared to  2 and 4 (assemblies). Both when running directly or via java -jar. I assume there is some launch logic included … ?
• a plain runner script (that downloads dependencies) has an execution time somewhere in between standalone and assembly.
• 4 is marked executable, even though it is not executable (no preamble included)
• 3 is executable (has a preamble included) – preamble is documented to only work for assembly, so this is somewhat expected.
As far as I can tell, --standalone is just a worse version of --assembly, so maybe --standalone should be removed or just become an alias … ?

I think the problem here lies in the lack of proper documentation on how --standalone works, actually. And we should definitely fix that part, so thanks for raising this!
As for the difference between --assembly and --standalone, let me try to explain.
The --assembly flag allows to create an assembly JAR (or a fat JAR, as they're also known), blending all of the dependencies byte code together into a single Jar file. More on assemblies can be found in the assemblies section of the package doc
The --standalone flag in turn allows to modify how a bootstrap JAR is packaged.
bootstrap JARs are the default package format of Scala CLI, they're a sort of lightweight launcher JAR. More on what that means can be found in the default package format section of our package doc.
When packaging with --standalone set to on, all of the dependencies will be packed into the JAR (similarly to an assembly, yes), but it will retain the bootstrap format.
To illustrate this further, here's what a fat JAR created with --assembly contains:
assembly.jar
├── LICENSE
├── META-INF
├── Main$.class
├── Main.class
├── Main.tasty
├── NOTICE
├── library.properties
├── rootdoc.txt
└── scala

and here's what a bootstrap looks like:
bootstrap.jar
├── META-INF
└── coursier

I do agree they are functionally very similar (2 kinds of JARs with all the dependencies packed in, yes), but they do produce slightly different outputs.

Now, there's a separate-but-tied issue I spotted while investigating this: --assembly and --standalone can currently be passed together, which I believe shouldn't be the case. We should probably at the very least warn the user about the --standalone being overridden by --assembly, as passing both produces a fat JAR.


Mat/Pat - Send email "Reminder to return to work

As a user I want to setup workflow that send and email to applicant about leave end. This content was copied from ticket #874.
We have leave start date logic in place. Now need to add leave end date logic (last date of maternity and/or parental leave). Based on end date needs to calculate date and time to send this email.
Please find email detail as per below.

4. Reminder to return to work.
Sent to applicant's alternate email. To be sent 6 weeks before end of leave (last date of maternity and/or parental leave).
**Sub: Reminder to notify return to work 4 weeks before Maternity/Parental Leave **
This is to inform you that you must inform your supervisor about your intent to return to work at least 4 weeks before your intended date of return. Please include the following information i your communication to your supervisor

Type of leave you took
First day of work
Phone number for supervisor to connect with you if needed
You must ask your supervisor to submit an AskMyHR service request for "My Team or Organization" under the following category "Leave & Time Off > Maternity, Parental, Adoption" with the letter attached.

You can also inform your supervisor about your intent to extend your leave if you do not intend to return to work on your originally chosen return date. To extend your leave, your should ask your supervisor to update your Maternity and Parental leave form with the new length of maternity or parental leave and resubmit the form.
[only if deferred allowance] (Copy To be confirmed)
To claim your allowance after you return to work, you should have applied for Employment Insurance after you started your leave. You will need a copy of your proof of approval. To get your proof of approval -
Log into the Service Canada website. Click on “My Latest Claim".
Take a picture or screenshot of the contents on "My Latest Claim" page. This information confirms that the you have been approved by Service Canada to receive the Maternity/Parental benefits.
[only if taking extended parental leave allowance] Since you opted for extended parental leave allowance, you must provide another proof of approval for your parental leave allowance.

Task:

[x] Setup logic on form and workflow to determine time to send email(six week before enddate)
[x] Setup send mail task in workflow

Bhumin to check with Iman and implement a solution.

Bhumin to add testing details once Iman posts changes

To test out this ticket,
we need to set date of tomorrow or near future for "reminderEmailDate".
That can be done in 2 ways.

Select enddate 4 week after tomorrow. To do that please select appropriate start date.
verify it in console. Open console by right click on form page - > select "inspect" -> select "network" tab
Select latest draft request and go to payload tab, in this click on "data" and expand it. checkout below image for more details.
make sure "reminderEmailDate" set to tomorrow ("YYYY-MM-DD" format)

In this approach we are setting "reminderEmailDate" manually in form.
go to form -> edit -> find "reminderEmailDate" hidden field -> select "data" tab -> go to "calculated value" section.
here please comment out all code. and write line
value = "2023-08-10";
here date is in "YYYY-MM-DD" format. please add any date in future.
Note: Make sure you enable comment code again and delete additional line once you submit form.

@Bhumin - thanks for the details. Was your test successful? For next steps, should the PSA dev team test this one?

Yes Meghan. It is available for PSA team to test it on DEV and TEST environment.

In the Dev env, I sent 3 Mat/pat forms for Bhumin to review. I will check with him on Monday if the testing was OK.

@chriscaldwell-psa I have fix issue in TEST environment. Now you should receive email for the same.
Let me know if you still haven't received any email. We can connect tomorrow after standup for 5 minute and submit new form. I'll review the same in system and confirm and we will for email.

Submitted a form on Friday but did not receive a reminder email. Bhumin is looking into this.

@ayushdamani
It is ready to test on DEV and TEST. Please submit new form and do let me know (in which env you have submitted form), so I can update date in workflow and you will receive an email by tomorrow.

Received the email - a reminder to return to work ✅
Private Zenhub Image


Fix channel frame handling upon framing error

Drop non-close/close_ok methods per AMQP stability rule when closing due to input framing error.
Fixed up/improved a number of tests, inluding two with duplicate names.
Don't override system-level exceptions (e.g., SystemExit, KeyboardException) in Channel.process_frames()

@awestendorf: this PR, together with PR #73 should fully address issue #72

Per http://www.rabbitmq.com/resources/specs/amqp0-9-1.extended.xml, re. channel.close:

After sending this method, any received methods except Close and Close-OK MUST be discarded. ...

I see what you're doing here and I like it, but I want to be sure that this doesn't break anything, so it will take some testing and review before I'm comfortable merging.

@awestendorf, thanks for reviewing. This one is far less urgent for me than #73.
This basically fixes the secondary issues that I discovered and described when investigating issue #72:

The channel was getting confused by incoming framing error and was unable to recover (internal exceptions resulting in recursive Channel.close calls,  and finally hang)
It was overriding system-exiting exceptions, preventing things such as SystemExit and KeyboardException from working properly.

In this PR, I took the cautious approach of only implementing the stability rule when closing the channel under the above-described framing error duress conditions.
I limited the scope to this change to the framing error scenario out of concern for creating an unintended side-effect under normal Channel.close conditions.
For example, in the basic.return failure scenario, the basic.return frames were getting chewed up and causing internal exceptions and Channel.close recursion, and if we didn't start dropping non-close-related frames, then the user code listening for Basic.Ack, would have its "ack listener" callback called, and would have mistakenly concluded that the message was delivered successfully and marked the operation as successfully-completed, which would be a mistake.

Hi Aaron, we've been running with this change in production error-free 24/7 for several months now. Prior to this PR, Haigha would hang when encountering an unexpected frame as discovered with missing Basic.Return support and documented in issue #72. It was also overriding system-level exceptions (e.g., SystemExit, KeyboardException) in Channel.process_frames().

rebased against current master

@awestendorf: Hi Aaron, I addressed your outstanding concern about the use of the "naked" constants for class and method identifiers via 9ec77191667b65b7e65483ce18950022c4e53469 in this PR and rebased against the current master.

@vitaly-krugl I forgot about this PR. I'd like to find a way to abstract this, so that the ChannelClass ids don't bleed into the Channel abstraction. I may just have to get over it and consider an alternative relationship, like I did with Connection and ConnectionChannel.
Since I've sat on this so long and my only hangups are with the abstraction, I'm going to merge it any way. It's more important for it to be technically correct than to wait for a potential improvement to the code structure. I can always revisit that at a later date.


net/dtlslistener: use parallel handshakes for connections

Codecov Report

Merging #379 (8c8c63f) into v3 (d1c0c08) will decrease coverage by 0.21%.
The diff coverage is 69.62%.

@@            Coverage Diff             @@
##               v3     #379      +/-   ##
==========================================
- Coverage   70.77%   70.56%   -0.22%
==========================================
  Files          68       68
  Lines        5098     5160      +62
==========================================
+ Hits         3608     3641      +33
- Misses       1116     1137      +21
- Partials      374      382       +8

Impacted Files
Coverage Δ

net/options.go
42.10% <33.33%> (-4.96%)
:arrow_down:

net/dtlslistener.go
69.38% <72.46%> (-0.62%)
:arrow_down:

net/connUDP.go
62.00% <75.00%> (ø)

dtls/server/server.go
76.25% <0.00%> (-5.04%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update to Micronaut 4

We will probably need to Update Micronaut 4 and Camunda 7.20 together because both switched from javax to jakarta namespace.  We will also need to update to Java 17.

A fork working on this issue from the branch of @tobiasschaefer is here

See also https://micronaut-projects.github.io/micronaut-servlet/latest/guide/#versioning

@tobiasschaefer Thanks for this awesome project. Is this possible to consider 4.x.x now as there is no patches released for version 3 since Mar 23, 2024.

HI @amardeep2006 :
thanks for your comment.
There is the PR #487 but updating is harder than expected.
Feel free to contribute by using the PR as a basis and creating your own. If all tests are green and it looks good, I'd be happy to approve it.
How are you using this integration project? Is it running on production for you?

I will have a look on PR. Micronaut is new for me as I have worked in Springboot mostly in past.
We are using Springboot based solution in production and looking for alternative that offers Native compilation.

@amardeep2006 : please note:

I actually didn't manage to get a project using this integration project natively compiled with GraalVM. The problem is that it embeds the Camunda Process Engine and this together with MyBatis (used for data persistence) makes use of reflection. This is a challenge but probably solvable
Spring Boot also supports native complilation now. However, you will probably run into similar challenges as mentioned in the previous bullet point
The Camunda External Task Client for Micronaut actually works with native images, see https://github.com/camunda-community-hub/micronaut-camunda-external-client?tab=readme-ov-file#graalvm.

Hope that helps


xban seems to have no effect

Hi there, my server is on 9bff154cba14686f5a3b56f4cba405824b88c402 (Fix horizontal/vertical merging bug of hardware-colored framed glass (#10417)), Thu Sep 24 00:10:50 2020 +0100, banning or temp banning a user seems to have no effect. The user is able to rejoin with and without alt-accounts.

sorry, this is a general ban issue on our server

sorry, this is a general ban issue on our server


Pressing ESC should not close all Portal components

Pressing ESC should not close all Portal components

This update adds a new "Manager" to the PortalWrapper component,
created with the new globalManager utility. This manager ensures
that pressing Escape ONLY closes the most recently Portal'ed component.
This is done by the manager tracking the IDs (which are unique) of
all the PortalWrapper created components.
This has been tested with Modals as well as Dropdowns.
Resolves: https://github.com/helpscout/blue/issues/97

Changes Unknown when pulling 6a575662f241eb5d13bca59c51ee134a2d1b5e48 on portal-manager into ** on master**.


make build fails to compile pkg/driver/kubernetes.go

Building (using docker) on macOS 10.14.5 fails, thus:
$ make build
docker run -it --rm -e SKIP_DOCKER=true -v /Users/gnormington/go/src/github.com/deislabs/duffle/:/go/src/github.com/deislabs/duffle -w /go/src/github.com/deislabs/duffle quay.io/deis/lightweight-docker-go:v0.7.0 bash -c "LDFLAGS=\"-w -s -X github.com/deislabs/duffle/pkg/version.Version=4dccb95\" scripts/build.sh"
building linux-amd64
# github.com/deislabs/duffle/pkg/driver
pkg/driver/kubernetes.go:350:10: undefined: strings.ReplaceAll
make: *** [build-all-bins] Error 2

Building locally works fine:
$ go version
go version go1.12.6 darwin/amd64
$ SKIP_DOCKER=true make build-darwin
bash -c "GOOS=darwin LDFLAGS=\"-w -s -X github.com/deislabs/duffle/pkg/version.Version=4dccb95\" scripts/build.sh"
building darwin-amd64

Note: strings.ReplaceAll was added last year here.

Fixed by 0ce61af583a85886d1607d0e0677f2bf9d3b5848


Investigate regression on CI upgrade job

Is your feature request related to a problem? Please describe.
Since around a week, the upgrade job seems to be failing:
https://concourse.suse.dev/teams/main/pipelines/kubecf/jobs/upgrade-test-master/builds/58
https://concourse.suse.dev/teams/main/pipelines/kubecf/jobs/upgrade-test-pr/builds/98
Describe the solution you'd like
Make the upgrade job green again, and mark its status as required.
Describe alternatives you've considered
None
Additional context

The bosh-pre-start-cloud-controller-ng pod fails with  VCAP::CloudController::ValidateDatabaseKeys::EncryptionKeySentinelDecryptionMismatchError
(see: https://github.com/cloudfoundry/cloud_controller_ng/blob/master/spec/unit/lib/cloud_controller/validate_database_keys_spec.rb#L321-L343)
It may be a legit regression in kubecf. AFAIU the database key gers created on first run, from https://github.com/cloudfoundry-incubator/kubecf/blob/13ffb01dff8ab5eba16da54539b36e3b3b5f758e/deploy/helm/kubecf/values.yaml#L490-L498, which we aren't touching on the CI deployment.
the failure always happens after a helm upgrade. Could it be that when upgrading, there's a recreation of the keys, but a mismatch in passing them?

FWIW, the raw data backup and restore for CCDB (kubecf cluster 1 -> kubecf cluster 2) also fails with the exact same error.

The regression seems gone after the recent bumps.
But now, diego-cell pod fails with not enough space on the ephemeral storage space of /var/vcap/data/ grootfs. This only happens with upgrades from one version to another, not within the same version (maybe the node fills after fetching the container images of both versions?).
I think we need to either set taints for the GKE deployment, or change the size of the ephemeral_disk for GKE.

I think we need to either set taints for the GKE deployment, or change the size of the ephemeral_disk for GKE.

Yes, don't you just need a variant of #1285 for this?

For the current regression, we were only missing changing the ephemeral_disk on the upgrade job also. Opened:  https://github.com/cloudfoundry-incubator/kubecf/pull/1308

From concourse CI (but not manual testing when setting epehemeral_disk), I get cannot delete '/var/vcap/data/grootfs/store': Device or resource busy. Full output:
e489f178-bfd4-4839-7fb5-90e6b66055d5:/tmp/build/7c5e83d7/catapult/buildgke # cat /tmp/k9s-screens-root/gke_suse-225215_europe-west3-c_kubecf-pr-upgrade-0-0-152/scf-diego-cell-0-1599648239023777426.log
+ /var/vcap/jobs/garden/bin/bpm-pre-start
find: cannot delete '/var/vcap/data/grootfs/store': Device or resource busy
find: cannot delete '/var/vcap/data/grootfs/': Directory not empty
2020-09-09T10:42:43.100166194Z - running thresholder
The node running this cell doesn't have enough disk space. You requested 60000M but the disk is 59212M in size.

real    0m0.081s
user    0m0.027s
sys    0m0.023s

After upgrading cf-operator from 2.4.0 to master, the cc-deployment-updater of the scheduler pod gets stuck not ready. On the deployment-updater I get DatabaseDisconnectError (…) Mysql2::Error: WSREP has not yet prepared node for application use. Only happens sometimes; a race condition with the state of the database pod after cf-operator prompts changes to the deployment.
It seems to be gone after merging https://github.com/cloudfoundry-incubator/kubecf/commit/3f2dd6780359147ca438e3bf13cbda4387b8917b.

Opened https://github.com/cloudfoundry-incubator/kubecf/pull/1335 and https://github.com/cloudfoundry-incubator/kubecf/pull/1332, with those I'm getting green upgrades locally.

The upgrade job is green, and is being successfully used to gate master.
I consider this card done, so I'm closing it (Nevertheless, this does not mean that regressions on upgrades don't need to be fixed. It seems that the only one around is https://github.com/cloudfoundry-incubator/kubecf/issues/1302).


Praxis::Docs::Generator fails to find MediaTypes that aren't reachable from the "canonical" MediaType of any resource

If a resource omits a media_type declaration and instead specifies media types for the response declarations of each of it action, then Generator#collect_types will fail to recurse into the response-specific media types to find embedded types. The result is that some of the types in the documentation will appear as unadorned Attributor hashes.
Reproduction of the issue is available here: https://github.com/xeger/praxis-issue-generator-collect-types

I don't seem to get what you are describing from your repo. The Hello resource, despite not having the default media_type defined, properly reports the collection of Hello mediatypes in the response definition.
Is there something else that should be done?
I'm using Praxis version 0.20.1

I'm also seeing this behaviour. The media type is not showing in the Schema tab.

@gstamp you're getting that behavior from a clean @xeger repo?
I just did it again and I can see the Hello type in the Schemas tab without issue. I did:
git clone, bundle and bundle exec rake praxis:docs:preview ...
and the browser shows the tab without issues.
Do you have an old version of Praxis somehow installed in the system or something? not sure what's going on here...

@blanquer No, it was an observation from my project. I'll check out that repo and try it.

I've checked out that repository. I see the Hello type in the generated docs. I don't see the Foo type which is perhaps what @xeger was referring to?

ok, I've taken another look based on @gstamp comments. And I've verified that the problem is indeed an outdated version of Praxis.
@xeger :  the repo comes with a .lock file that pins Praxis to 0.20.1.
The version that has that fix in is 0.21.
In particular it was #299 (back in May 2016) which provided the fix in master, and the gem was published back in August, so it's been a while.
So, the solution is to update to version 0.21 or master.
Thanks again guys for the repo and for bringing up a potential problem. We appreciate it.


⚠ Bofrost.at has degraded performance

In bea0d8a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1193 ms

Resolved: Bofrost.at performance has improved in d3d3f53.


well

ERROR: Manifest merger failed : uses-sdk:minSdkVersion 17 cannot be smaller than version 21 declared in library [com.alespero:expandable-cardview:0.8] C:\Users\vn149.gradle\caches\transforms-2\files-2.1\77a8e153d09f09dd93369c863f2522a3\AndroidManifest.xml as the library might be using APIs not available in 17
Suggestion: use a compatible library with a minSdk of at most 17,
or increase this project's minSdk version to at least 21,
or use tools:overrideLibrary="com.alespero.expandablecardview" to force usage (may lead to runtime failures)

Hello,
The minimum supported version for this library is API 21, so by setting a minSdkVersion 17 in your app, the compilation failed.
Currently, there are no plans of lowering the minSdk, but i will definitely get back to you if this happens.
Regards,
Alessandro


Radio Thermostat CT80 Rev B1 V1.00 error updating in home assistant

(I believe this is not exactly the same as #26 -- although the result is similar -- since the error message isn't quite the same.
Apologies if it's a dup.)
When I add the radio thermostat component to my home assistant configuration, HA tries to add my device but fails and puts this error in the log:
2018-04-21 10:41:14 ERROR (MainThread) [homeassistant.components.climate] radiotherm: Error on device update!                                       Traceback (most recent call last):                                                                                File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 188, in _async_add_entity                                      await entity.async_device_update(warning=False)                                                                                File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity.py", line 327, in async_device_update                                             yield from self.hass.async_add_job(self.update)                                                                                File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run                                                                               result = self.fn(*self.args, **self.kwargs)                                                                                File "/usr/lib/python3.6/site-packages/homeassistant/components/climate/radiotherm.py", line 237, in update                                           self._name = self.device.name['raw']                                                                                AttributeError: 'NoneType' object has no attribute 'name'                                                                                2018-04-21 10:41:44 WARNING (SyncWorker_2) [netdisco.ssdp] Error fetching description at http://[fe80::d4e2:6588:1d90:ba8a]:6544/getDeviceDesc
Like in #26, I believe this may be related to the Rev no. of the device.

It seems like radiotherm is not able to connect to your device. This is curious because the CT80 B1 v1.00 is supported by radiotherm.
Are you able to run radiotherm from a python console? (i.e. reproduce this error by cloning this project, and running it with python following the readme) If so, there's an experiment that might be helpful in determining what might be wrong.

Here's what I get when I try radiotherm from python console on my desktop (which is on the same network as the thermostat and can ping it successfully) following the readme.rst instructions:

import radiotherm
tstat = radiotherm.get_thermostat()
tstat.temp
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'NoneType' object has no attribute 'temp'
tstat.mode
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'NoneType' object has no attribute 'mode'

BTW, the run-tests script passed all tests.

Try running this (use the actual IP address of your thermostat)
import radiotherm
tstat = radiotherm.CommonThermostat( "<IP_ADDRESS>" )
print( tstat.model )

Ok, I gave it a try . . .
import radiotherm
tstat=radiotherm.CommonThermostat( "<IP_ADDRESS>")
print(tstat.model)
{'raw': u'CT80 Rev B1 V1.08'}

Additionally, the temp and mode methods now return data.
tstat.temp
{'raw': 68.0}
tstat.mode
{'raw': 1, 'human': 'Normal'}

The version specific subclassing has been a real limitation for compatibility and is also largely unnecessary; I've been meaning to implement a proper class heirarchy with unknown models falling back to CommonThermostat.

Another think to consider in a fix for this is that the thermostats aren't very reliable.  At least for home assistant, it would be better to just use the common thermostat and not require a connection to be valid at start up.  Right now, if a the library can't connect to the thermostat, it fails and will never be available in home assistant which is annoying.  I think this is mostly a code change on the home assistant end but being able to create the thermostat class (probably common thermostat) w/o a valid connection is important.  Most of the time, the connection will be available later so it's not normally a big deal if it's not there at construction time.

I created a pull request on Nov 5, 2016 that fixes this problem. It was
ignored.
As I recall I also added caching which was sorely needed.
https://github.com/JerryWorkman/radiotherm
On Fri, Jun 22, 2018 at 11:55 AM Ted Drain<EMAIL_ADDRESS>wrote:

Another think to consider in a fix for this is that the thermostats aren't
very reliable. At least for home assistant, it would be better to just use
the common thermostat and not require a connection to be valid at start up.
Right now, if a the library can't connect to the thermostat, it fails and
will never be available in home assistant which is annoying. I think this
is mostly a code change on the home assistant end but being able to create
the thermostat class (probably common thermostat) w/o a valid connection is
important. Most of the time, the connection will be available later so it's
not normally a big deal if it's not there at construction time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mhrivnak/radiotherm/issues/34#issuecomment-399490198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsbQBz_5pr-9f0KcCSa8XGTshBOslQMks5t_RNXgaJpZM4TesD0
.

I created a pull request on Nov 5, 2016 that fixes this problem. It was
ignored.

You did? I don't see any opened or closed PRs in this project from you:
https://github.com/mhrivnak/radiotherm/pulls?q=is%3Apr+is%3Aclosed
Feel free to re-submit it and I'll take a look.

See my issue post here: https://github.com/mhrivnak/radiotherm/issues/14
It's been so long I'll need to diff/clone/pull all over.
On Sat, Jun 23, 2018 at 1:04 PM clayton craft<EMAIL_ADDRESS>wrote:

I created a pull request on Nov 5, 2016 that fixes this problem. It was
ignored.
You did? I don't see any opened or closed PRs in this project from you:
https://github.com/mhrivnak/radiotherm/pulls?q=is%3Apr+is%3Aclosed
Feel free to re-submit it and I'll take a look.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mhrivnak/radiotherm/issues/34#issuecomment-399693496,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsbQLX0YWXs7hpeIAejHdV08XrFyZ0iks5t_nUcgaJpZM4TesD0
.

Ah, an issue, not a pull request. Yea if you have something to submit in a pull request, I'd be happy to review/merge it :)
If not, I can take a look at your branch later on when I have time and come up with a patch that will apply to the current codebase.

Can you try with #38 ? This adds support for thermostats that are not explicitly defined in this project, with basic functionality. In your case it should enable functionality that all CT80 devices, regardless of rev and version, support. But since I don't have your device, it would be awesome to get a confirmation that this branch works before I merge it!
Special thanks to @JerryWorkman for his PR :+1:

I have since replaced my Radiotherm.
On Wed, Jun 27, 2018 at 10:28 PM clayton craft<EMAIL_ADDRESS>wrote:

Can you try with #38 https://github.com/mhrivnak/radiotherm/pull/38 ?
This adds support for thermostats that are not explicitly defined in this
project, with basic functionality. In your case it should enable
functionality that all CT80 devices, regardless of rev and version,
support. But since I don't have your device, it would be awesome to get a
confirmation that this branch works before I merge it!
Special thanks to @JerryWorkman https://github.com/JerryWorkman for his
PR 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mhrivnak/radiotherm/issues/34#issuecomment-400890935,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABsbQHpKvp-eiVTQh8hDBDck1A5GBtC8ks5uBD9kgaJpZM4TesD0
.

This should be resolved now. Closing issue, but please re-open if someone continues to experience this after testing the latest in master branch.


Information Disclosure in error messages

We are using Backstage and we need to avoid Information Disclosure in error messages
For example there are verbose error messages which contain SQL statements which triggered the error, also from some other error messages can be verified which files exist on the application server and which do not!
We want to have generic error pages or messages when getting errors.

Where are you seeing SQL errors being forwarded to the frontend? Would like to fix those 😁
Apart from that the best way forward here is for you to register a custom error handling middleware. The backend service builder has a setErrorHandler which you can use to that end.


No way to tell if at EOF when using Decoder.Decode() with struct

Looking at:
https://github.com/ianlopshire/go-fixedwidth/blob/master/decode.go#L81-L93
and
https://github.com/ianlopshire/go-fixedwidth/blob/master/decode.go#L113-L128
As far as I can tell, readLine eats the EOF error -- it returns an ok bool, but Decode throws that away. This could be fixed by having Decode transform the ok bool back into an err == io.EOF, or the done bool could be exposed via a public API.
I'm happy to implement a PR for either one of these strategies that you prefer.
Thanks for this package!

@alex, thanks for submitting this issue.
I think the best solution here, is for Decode to return an io.EOF error when there are no remaining lines to read and the target is not a slice. I'd prefer not to expose done and expand the public API. Decoding an empty file into a slice should result in an empty slice.
I am open to discussion if you have other thoughts.
I'd happily merge a PR for this provided it includes tests and documentation.

Expect a PR later today! Thanks much!


fix: switch initial version of milli to v0.38.0

The last change that is needed before mimir's first stable release! 🎉🎉
Just waiting on milli v0.38.0 with my PRs.

Note to self: delete my milli fork once I have merged this.


The number of epoch

Hello, I would like to ask why the epoch is 1 by default? Will adding epoch improve detection performance?

Hi, the default number of epochs depends on the type of algorithm. Feature extraction based methods such as Padim and PatchCore require only a single epoch, because the weights of the convolutional backbone are fixed. These methods rely on pre-trained feature extractors to obtain a feature representation for each image, and then use statistical methods to create a normality model on top of the extracted features. No fine-tuning of the neural network weights is involved when these models are trained, so increasing the number of epochs will be ineffective.
Other algorithms, such as STFPM, do require fine-tuning of the neural network weights, so you will see that for those models the default number of epochs is higher.
More information about each of the individual algorithms can be found in the readme files in the root directory of each of the model implementations, e.g.
Padim: https://github.com/openvinotoolkit/anomalib/tree/development/anomalib/models/padim
STFPM: https://github.com/openvinotoolkit/anomalib/tree/development/anomalib/models/stfpm

Thank you very much for your answer

No problem! I will be closing this issue now. Feel free to re-open if anything is still unclear

Hi, the default number of epochs depends on the type of algorithm. Feature extraction based methods such as Padim and PatchCore require only a single epoch, because the weights of the convolutional backbone are fixed. These methods rely on pre-trained feature extractors to obtain a feature representation for each image, and then use statistical methods to create a normality model on top of the extracted features. No fine-tuning of the neural network weights is involved when these models are trained, so increasing the number of epochs will be ineffective.
Other algorithms, such as STFPM, do require fine-tuning of the neural network weights, so you will see that for those models the default number of epochs is higher.
More information about each of the individual algorithms can be found in the readme files in the root directory of each of the model implementations, e.g.
Padim: https://github.com/openvinotoolkit/anomalib/tree/development/anomalib/models/padim STFPM: https://github.com/openvinotoolkit/anomalib/tree/development/anomalib/models/stfpm

If I use RandomHorizontalFlip, RandomVerticalFlip, RandomAffine to augment Images, then Padim need more epochs.


Low Power Mode backup timer

Introduction
Add an additional IDLE timer actions, for system timers that are not clocked in a low power mode.
Problem description
Some system timers are not clocked in a low power mode (LPM). The core example is SysTick in STM32 chips (not sure how other chips works).  Some chips use low power timer that runs in the LPM e.g. STM32Lx use LPTIM, but some chips families don't have such feature, e.g. STM32Fx. That means chips that use the SysTick as the system timer can't enter the low power mode. See #60558
Proposed change
Add a "backup/lpm" timer that is used while entering the low power mode. The additional timer would be used to wake up a chip and measure time missed by the main timer.
Detailed RFC
Add a chosen node e.g. zephyr,idle-timer. If defined, the timer would be used in the sys_clock_set_timeout function to set an alarm to wake up the chip and save current time. The function takes idle as an argument, which indicates that we are going to enter low power mode.
Then, in the sys_clock_idle_exit function, we should be able to calculate time missed by the main timer, update the cycle counter and announce it to the kernel.
My assumption in that the zephyr,idle-timer node should support the counter API.
For the mentioned STM32Fx chips, the only timer/counter that runs in LPM is RTC, so it would be the idle timer. The maximum frequency that can be used for such case is 16kHz (LSI/2), so really not accurate comparing to the main clock.
Concerns and Unresolved Questions

How to announce the time to the kernel - call the sys_clock_announce in sys_clock_idle_exit or update the cycle counter and call sys_clock_set_timeout(0, false)
It increases the exit latency/min residency, because of additional operation, but the alternative is no low power mode at all so it still sounds like a good deal
Some inaccuracies in time measurement are unavoidable, due to difference in the clock frequencies

Alternatives
Use the idle timer as the main system timer. The RTC with 16kHz means 62,5us clock cycle, which is really low.

Hi Dawid,
It looks like our tickets are related (my is #61618).
IMHO It will be better to use counter RTC as a system tick source (default system tick is 10KHz or 100Hz) and SYSTICK timer  as a cycle reference for sys_counter_cycle_get_XX (in this case it can be stopped in the idle).
I suspect that your suggestion to recalibrate the system timer after every idle would be a nightmare.

Hello Andrey,
thanks for the response.
I've been considering both options here #60558. I've decided to start with the presented solution because of the low frequency of a RTC clock. For STM32 it would be 16kHz. The frequency should be high enough for the 100Hz system tick, but for system with higher requirement it may not be enough.
Regarding #61618, separation system timer driver and cycle counter sounds like a nice option, but I'm not familiar enough how the cycle counter is used to give you more feedback. Just please keep in mind, that some clocks might be disabled in low power mode and some can still run. If system timer and cycle counter use different clock the measurements may be shifted because of that e.g. system timer RTC uses LSE (running in LPM) and clock counter uses PLL that is disabled while entering LPM.

I suspect that your suggestion to recalibrate the system timer after every idle would be a nightmare.
I'm not sure what you mean by recalibrate. The main system timer would run without any changes and the idle timer would measure the "missed" time and set alarm to wake up the device.

Hello Andrey, thanks for the response.
I've been considering both options here #60558. I've decided to start with the presented solution because of the low frequency of a RTC clock. For STM32 it would be 16kHz. The frequency should be high enough for the 100Hz system tick, but for system with higher requirement it may not be enough.

But tick frequency could also be power of 2. 100 HZ/10 KHz is just anthropocentric numbers. Why not use a 16384/8192 Hz system timer instead, if it's acceptable for your application?

Regarding #61618, separation system timer driver and cycle counter sounds like a nice option, but I'm not familiar enough how the cycle counter is used to give you more feedback. Just please keep in mind, that some clocks might be disabled in low power mode and some can still run.

Yes, I know, this STM's (and Renesas) decision has already made be headache.

If system timer and cycle counter use different clock the measurements may be shifted because of that e.g. system timer RTC uses LSE (running in LPM) and clock counter uses PLL that is disabled while entering LPM.

I suspect that your suggestion to recalibrate the system timer after every idle would be a nightmare.

I'm not sure what you mean by recalibrate. The main system timer would run without any changes and the idle timer would measure the "missed" time and set alarm to wake up the device.

You will need to keep 2 timers (backup and system) in sync, and it will not be so easy since LPM timer is 32,768 KHz based, but high precision system one is 64 MHz (or more) based. So after a couple of days of running the chip, you will have a leap error, if you do not take some action. The "missing" time is a fractional value in therms of system/or backup timer.

But tick frequency could also be power of 2. 100 HZ/10 KHz is just anthropocentric numbers. Why not use a 16384/8192 Hz system timer instead, if it's acceptable for your application?

Yes yes, I know. The max freq for STM32 RTC is 16kHz. However, we are migrating our system with much higher frequency to Zephyr. I want to keep all parameters as much as possible. It the proposed solution doesn't work, I will try with the RTC as system timer.

You will need to keep 2 timers (backup and system) in sync,

That is not actually true. Every time before entering the LPM and after exiting, I would read the time from both timers. I allows calculating the passed time. The difference between measurements is the time missed by the main timer, and cycle counter should be increased with this value.
The process would be repeated for every idle entrance, the backup timer doesn't keep its version of the cycle counter.

Added with #63187


Do we statically link to the CUDA runtime and how do we know it?

This say that static linking is default. So do we do it?
http://docs.nvidia.com/cuda/cuda-c-best-practices-guide/index.html#distributing-cuda-runtime-and-libraries

Yes, we do. In Visual Studio go to Properties of GpuFit, then Linker, Input, Additional Dependencies and there will be something like:
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\lib\x64\cudart_static.lib


Set the parsec sock directory permission to 0755

This is required so that users which are part of the group=parsec
are able to access the sock. Also its the recommended permission level - https://parallaxsecond.github.io/parsec-book/parsec_service/install_parsec_linux.html#from-an-admin-user-with-privileges

Others can READ and EXECUTE. They can't write to it though - so they can't really make any Parsec requests, so I'm not quite sure what's the benefit of it.

Others can READ and EXECUTE. They can't write to it though - so they can't really make any Parsec requests, so I'm not quite sure what's the benefit of it.

Not so. With this change you can use parsec-tool to create new keys, because the socket has rw permissions:
ls -l /run/parsec/parsec.sock
srw-rw-rw- 1 parsec parsec 0 Apr 13 07:02 /run/parsec/parsec.sock

@petedyerarm  Ahh make sense. Should we then change the permission to 750 ?


Make upgrading a python app more predictable

Check with Team Water the prospect of migrating to turbine-core.

Confirmed with Team Water that the Turbine-core/Turbine-IR work kickoff is this upcoming week. Meroxa-py will become irrelevant in that work and therefore this task is unnecessary.

Confirmed with Team Water that the Turbine-core/Turbine-IR work kickoff is this upcoming week. Meroxa-py will become irrelevant in that work and therefore this task is unnecessary.

@ericcheatham does that confirm that there is no upgrade path for older apps, just need to delete and recreate?


Rewrite configurable parameters as new class instead of a tuple

Configurables are now a tuple with increasing amount of parameters. The code would be more readable and understandable if configurables will be a separate class with private and public params, type and description. Documentation also needs to be updated. This change is backwards incompatible because external rules will not be properly loaded. We also agreed that probably there are not many people using external rules and if there are any, they will be able to update their code to follow new standard. Also we are going to provide simple examples that will explain the difference.

We could support backward compatibility by allowing to have either tuple or Configurable class in rule definition:
        "0301": (
            "invalid-char-in-name",
            "Invalid character %s in %s name",
            RuleSeverity.WARNING,
            (
                'invalid_chars',
                'invalid_chars',
                set,
                'set of characters not allowed in a name'
            )

or
        "0301": (
            "invalid-char-in-name",
            "Invalid character %s in %s name",
            RuleSeverity.WARNING,
            Configurable('invalid_chars', set, 'set of characters not allowed in a name') # since its class we can be more flexible, ie reuse public name as private name if not set

Then when parsing rule when our value is of tuple type, use something like Configurable.from_tuple().
Of course it depends it's good to increase complexity of code for this.

Good idea but I think I would opt to use just a class.

We have a very similar issue related to configurables in #162.
@bhirsz Which solution we want to implement? Better not to separate the discussion into 2 different issues, so we need to decide which one we want to close.


Add the DockPanelSuite as .NET framework component in visual studio 2013

Hi,
I'm just new on this and wanted to test it. However when i try to add the .NET framework component through the dll file, i got the error.
"There are no components in ...\WeifenLuo.WinFormsUI.Docking.dll that can be placed on the toolbox"
There is a way to add this as a component?
Thanks in advance.

Please see #184


google-cloud-sdk: 467.0.0 -> 472.0.0

Description of changes
Update to the latest Google Cloud SDK
See: https://cloud.google.com/sdk/docs/release-notes#47200_2024-04-16
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3888

Hey, 475.0.0 is the latest by now, can you please update this pr? :)

Closing this in favor of #311598


MRG: Fix source

Testing PR to master to fix source links.

CSS and links fixed here, too:
https://5385-1301584-gh.circle-artifacts.com/0/tmp/circle-artifacts.LiNfezn/html/generated/mne.io.Raw.html
Merging


One line of padding on both top and bottom of pretty hover

Hey! I find this plugin to make things more pretty! But I am running into a specific difficulty regarding that padding, as shown below. For very small definitions it can literally triple the size of the popup. If this is a stylistic choice, could an option be added to turn it off?

It's because under the hood it's just hidden markdown

( i forgot to say that vanilla neovim works like that, and it's noice.nvim which removes the padding by removing the markdown text )

I suspected this but didn't understand the need -- in the term it's all just plaintext, modified by colors and font-options, so wouldn't it be easy enough to just convert the source markdown into text with the equivalent formatting?  I could help!

there's alot of return "" inside this plugin this might the culprit

i'm not a lua dev but the issue seems to be in either util.lua or references.lua

Hi, to clarify. Would you like to remove it just from the one-line statements? If yes and you do not care about the highlighting it would be easier (i.e. the number color)

Hi, i just want to remove the "padding" above and below "22 bytes"
I don't really care about the highlighting

Hi, can you confirm that it works also for your usecase?

works perfectly


Fix references

We still haven't cleaned up completely since the repository move :wink:

Looks good, but should probably be rebased against master as soon as #78 is merged.

Looks good, but should probably be rebased against master as soon as #78 is merged.

Done.


Fix/215 toleration on hook

Please ensure your pull request adheres to the following guidelines:

[x] explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
[x] Document your Changes in the CHANGELOG.md file of the respected chart as well as the Chart.yaml
[x] Bump the Version number of the respected chart

Fix for issue 215,
adding tolerations and affinity to Hooks

Hi @leo-geoffroy-sonarsource  can you take a look at this one?

@Jufik
Thank you for your contribution.
This change does not qualify for the LTS, could you please remove the changes from the sonarqube-lts folder?

@leo-geoffroy-sonarsource : removed LTS modifications

LGTM, I just fixed a typo and squashed the commit
Thanks again for the contribution


updated ruby install for Mac

As of Catalina default shell switched to zsh.  Steps reflect how to setup rbenv with zsh. I drew heavily from:  https://programmingzen.com/installing-rbenv-on-zsh-on-macos/

@elibtronic thank you for the PR, we really appreciate it!
I will defer to Mac users @owikle or @dcnb to review this.


_rng functions in transformed data block

Submisison Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
Allow functions ending in _rng to be called in the transformed data block.
Intended Effect
Allow simple data simulations.
How to Verify
Unit tests for legal and illegal contexts.
Side Effects
No.
Documentation
Updated manual to reflect change; added new section to BNF on _rng placement.
Reviewer Suggestions
Anyone.
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Columbia University
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Looks like a test failed with new compiler warnings: http://d1m1s1b1.stat.columbia.edu:8080/job/Stan Pull Request - Tests - Integration/892/
I'm going to try to recreate locally.

@bob-carpenter, I'm seeing a test failure. From the Stan branch, if you run this, you'll see that the generated code is producing code that's not compilable:
> make src/test/test-models/good/rng_loc.hpp-test
...
src/test/test-models/good/rng_loc.hpp:81:51: error: use of undeclared identifier 'base_rng__'
            stan::math::assign(y, normal_rng(0,1, base_rng__));

Thanks --- fixed it and have just been running more tests
to make sure it works now.
It's going to require all the interfaces to start passing
an RNG to the constructor.  For now, I made it work by adding
a second constructor that creates its own RNG for the constructor,
and it'll lead to reproducible results, but it'll be the same
results every time.

Bob

On Jul 19, 2016, at 9:44 AM, Daniel Lee<EMAIL_ADDRESS>wrote:
@bob-carpenter, I'm seeing a test failure. From the Stan branch, if you run this, you'll see that the generated code is producing code that's not compilable:

make src/test/test-models/good/rng_loc.hpp-test
...
src/test/test-models/good/rng_loc.hpp:81:51: error: use of undeclared identifier 'base_rng__'
stan::math::assign(y, normal_rng(0,1, base_rng__));

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I can't see what went wrong with the travis-ci/pr.  There aren't any errors when I click through and the badge seems to say passing even though it's highlighted in red.

Travis isn't 100% reliable.
I restarted the job. Just in case you're wondering how -- if you're
authenticated through GitHub, you can click through the broken travis
project all the way to the job that failed. In this case, it's this one:
https://travis-ci.org/stan-dev/stan/jobs/145956598
When it's not running, there's a circular arrow in the top right with a
hover-over tool tip, "restart job." When it is running, there's an X icon
in its place.
Once you click that, it'll restart the job.
On Wed, Jul 20, 2016 at 8:40 AM, Bob Carpenter<EMAIL_ADDRESS>wrote:

I can't see what went wrong with the travis-ci/pr. There aren't any errors
when I click through and the badge seems to say passing even though it's
highlighted in red.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/pull/1959#issuecomment-233936968, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F_SuU_IHcvGVYW8-IX3oaYoGNQnZks5qXhcigaJpZM4JPZ7M
.

Thanks.  Looks like the restart thing goes away if it passes.

On Jul 20, 2016, at 8:48 AM, Daniel Lee<EMAIL_ADDRESS>wrote:
Travis isn't 100% reliable.
I restarted the job. Just in case you're wondering how -- if you're
authenticated through GitHub, you can click through the broken travis
project all the way to the job that failed. In this case, it's this one:
https://travis-ci.org/stan-dev/stan/jobs/145956598
When it's not running, there's a circular arrow in the top right with a
hover-over tool tip, "restart job." When it is running, there's an X icon
in its place.
Once you click that, it'll restart the job.
On Wed, Jul 20, 2016 at 8:40 AM, Bob Carpenter<EMAIL_ADDRESS>wrote:

I can't see what went wrong with the travis-ci/pr. There aren't any errors
when I click through and the badge seems to say passing even though it's
highlighted in red.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/pull/1959#issuecomment-233936968, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F_SuU_IHcvGVYW8-IX3oaYoGNQnZks5qXhcigaJpZM4JPZ7M
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Great. I think we can address the overall design goals of the model class at some point, but this works.


Tab format issue

Operating System (+Version):
VS Code Version: 1.21.0
beautify Version: 1.3.0

NOTE: Please provide code snippets instead of screen shots. Your issue needs to be replicated, and we need the failing code (text) to do this.
Provide the settings you use:
User Settings:
"editor.tabSize": 4,
VS Code:
{
	"beautify.editorconfig": false,
	"editor.formatOnSave": true
}

.jsbeautifyrc
{
	"max_preserve_newlines": 2,
	"preserve_newlines": true,
	"end_with_newline": true,
	"brace_style": "collapse-preserve-inline",
}

Action performed
Format javascript file with HookyQR.beautifyFile command
Expected results
Expected ... to ...
provide example (expected) output
Expecting 4 spaces for tabs on formatting.

Actual results
Details of what happened ...
provide example (actual) output
Returning only 2 spaces.

Disregard I just fixed it.


can't  resolve fs

I'm using Webpack and somehow it can't resolve 'fs'. Do I  need a polyfill?
Note: I'm trying to use it in background js in Chrome Extension
ERROR in<EMAIL_ADDRESS>93:81-94
Module not found: Error: Can't resolve 'fs' in<EMAIL_ADDRESS>resolve 'fs' in<EMAIL_ADDRESS>  Parsed request is a module
  using description file<EMAIL_ADDRESS>(relative path: ./dist)
    Field 'browser' doesn't contain a valid alias configuration
    resolve as module
<EMAIL_ADDRESS>doesn't exist or is not a directory
<EMAIL_ADDRESS>doesn't exist or is not a directory
      ./node_modules/@jlongster/node_modules doesn't exist or is not a directory
      ./node_modules/node_modules doesn't exist or is not a directory
      looking for modules in ./node_modules
        single file module
          using description file: ./package.json (relative path: ./node_modules/fs)
            no extension
 @ ./src/worker/index.ts 43:31-59

Solved with using 👇in  Webpack config.resolve
fallback: {
      crypto: false,
      path: false,
      fs: false
}


Adding RADseq.yaml tour file

This tour will walk you through the process of RAD Sequencing to
identify SNP and analyse data to produce population genomics statistics
or genetic maps

Wonderful!

A first try, I have to take more time to make something better.... But I find this functionality quite cool ;)


Code with Us page - link terms and p4p process

Add a link to the terms and p4p process on the code with us page to give developers this information before exploring opportunities in GitHub.

will work with @mark-a-wilson to determine how and then work with technical team to implement.


Compiler error with -std=c++17 on gcc

../../third-party/libsimdpp/simdpp/types/empty_expr.h: In instantiation of ‘simdpp::arch_sse3::mask_int32<N, simdpp::arch_sse3::expr_empty>::operator simdpp::arch_sse3::uint32<N>() const [with unsigned int N = 4]’:
../../third-party/libsimdpp/simdpp/detail/insn/cmp_neq.h:195:52:   required from here
../../third-party/libsimdpp/simdpp/types/empty_expr.h:220:52: error: could not convert ‘((const simdpp::arch_sse3::mask_int32<4, simdpp::arch_sse3::expr_empty>*)this)->simdpp::arch_sse3::mask_int32<4, simdpp::arch_sse3::expr_empty>::e’ from ‘const simdpp::arch_sse3::mask_int32<4>’ to ‘simdpp::arch_sse3::uint32<4>’
  220 |     SIMDPP_INL operator uint32<N>() const { return e; }
      |                                                    ^
      |                                                    |
      |                                                    const simdpp::arch_sse3::mask_int32<4>

is this related to #137?

This is fixed with https://github.com/p12tic/libsimdpp/pull/118


vpc_peerings implemented as nodes

This would be the first step to implement Ec2RouteTables (#410).

Hi, last time I was trying to delete vpc_peering.py it broke testing.

Appearantly this time it worked, what should be the next step?


Add 'meetings' command

Any upcoming meeting will popup at the top of the Ui, to show the meeting to remind the insurance Agent.

As discussed, we will move reminders command to a later iteration.
I will make a 'meetings' command to view all meetings instead.

Meetings command successfully implemented.
No tests written for it yet, will do that soon.


Parsing seems to skip arrays

Your plugin is a life saver for me. Thank you. I noticed that it doesn't seem to parse imports that are embedded in arrays, such as:
/**
 * @method
 * @param {Object} someObject
 * @returns {Array<import("../path/file.js").Declaration>}
 */

Am I doing something wrong?

Glad to hear it!
Sorry for the slow response, I'll fix this now.

Glad to hear it!
Sorry for the slow response, I'll fix this now.

Fixed in v1.0.2
Thanks for trying it out

Fixed in v1.0.2
Thanks for trying it out


scaffolded OperatorConfig API

opening PR now for easier reviewing since a lot of files are generated when a new API is added.
How to test:
Should be no change to functionality, just able to install it and see OperatorConfig CRD

/retest


experimental windows setup

Added a windows installer and uninstaller. It copies bicep.exe and bicep.pdb to the user's chosen installation directory and adds that directory to the PATH. Uninstall reverts all changes.
The installer is built using an open-source tool called Inno Setup. VS code uses it for its own Windows setup.

Codecov Report

Merging #421 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #421      +/-   ##
==========================================
- Coverage   91.93%   91.91%   -0.03%
==========================================
  Files         199      199
  Lines        6708     6688      -20
==========================================
- Hits         6167     6147      -20
  Misses        541      541

Flag
Coverage Δ

#dotnet
91.91% <ø> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/Bicep.Cli.UnitTests/PathHelperTests.cs
100.00% <0.00%> (ø)


Moving logic to constructor + prototype functions

I did some minor changes while looking through the code.
The diff is substantial but it's simply moving logic out of the scoped function block of exports.extend and into a constructor with prototype functions.
/cc @caridy

LGTM

I'll merge this once I finish my testing with the membership app :+1:


Create User Model including authentication

Create a User model with the following characteristics:

A user should have the following properties: firstName, lastName, password, role (viewer, owner, admin), email.
When creating a new user the user should get an email with a link to confirm its identity.
Implement a mongoose pre hook so that before saving every user check if their password has been modified. If it did generate a new password encrypted/hashed with a salt.
Use bycript library to encrypt the passwords:

Generate a salt (10) to encrypt the use password
Create a password hash using the previous salt

Use jwtoken library to generate the tokens

Authentication Guide
Additional resource


GENIE: decoder_nll loss is always equal to 0 for training from scratch

Hi @qiweizhen,
I try to reproduce your reported result of the training from scratch for XSum. However, the decoder_nll loss is always equal to 0, which is quite weird since it's cross-entropy loss.
If I load your pre-trained model, it is not equal to 0.  Do you know the reason?

Hi, I'm trying to reproduce the result of XSUM from scratch too, using recommended parameters in README. But I cannot reproduce the ROUGE score, which is much lower than the score reported in the paper. Any suggestions? @qiweizhen , thank you!


Make diagnostic messages optional?

It's good to make logging optional.
If anyone will want to try this library for more than demonstration cases they certainly will want to remove logging to increase the speed.
I suggest to make logging optional by adding template parameter or your own wrapper class for logging to separate memory manager class and logging logic.

Also maybe a good thing to change all int pointer to template parameter

I'll have these out by 10PM UTC-7.


tctl: Format timestamp fields using a flag [p1]

Origin issue:

Summary
Adds control over how timestamp fields are printed
Basic example
$ tctl workflow list --format-time relative # default in tty
$ tctl workflow list --format-time iso # default in non-tty
$ tctl workflow list --format-time raw
$ tctl workflow list --format-time "Jan 2 15:04:05 2006 MST" # ie. custom format

Motivation
Helps reading timestamp values in Tables and Cards.
Reduces noise in tty Tables by default, since relative format (6 hrs ago) is shorter and less-noisy than others
Detailed design
in doc
Drawbacks
Why should we not do this? Please consider:

changes the default format

Alternatives
What other designs have been considered? What is the impact of not doing this?
Adoption strategy
Not a breaking change, though changes the default timestamp format
How we teach this
--help for this flag should be clear and show possible values
Unresolved questions

golang has https://golang.org/pkg/time/#Time.Format which takes a formatted date string for Jan 2 15:04:05 2006 MST and copies the same format for the supplied datetime value. Might be nice to present this to the user so they can choose exactly how the timestamp should appear. I'm wary of things like datetime having meaning because would that be with seconds? What about timezone? Most date related terms are ambiguous. So perhaps relative, raw and custom or something along those lines? Even date could be any of 2006-01-02, 01/02/2006 or 02/01/2006

golang has https://golang.org/pkg/time/#Time.Format which takes a formatted date string for Jan 2 15:04:05 2006 MST and copies the same format for the supplied datetime value. Might be nice to present this to the user so they can choose exactly how the timestamp should appear. I'm wary of things like datetime having meaning because would that be with seconds? What about timezone? Most date related terms are ambiguous. So perhaps relative, raw and custom or something along those lines? Even date could be any of 2006-01-02, 01/02/2006 or 02/01/2006

how about the following possible values for the flag then? :

relative
iso
raw
"Jan 2 15:04:05 2006 MST" - anything that is not relative, iso or raw is treated as "custom" and passed to Time.Format

Opened PR https://github.com/temporalio/tctl/pull/24/files

@robholland @bergundy @alexshtin adding support for specific timezones due to user request here https://github.com/temporalio/temporal/issues/1607
feedback is welcomed:
https://github.com/temporalio/proposals/pull/35/files#diff-fd43e76660a0644c8d5027ed26ef9dbb8086737f8145733070445413a18f4133R13

Only thing I would maybe change is to rename the flag --time-format instead of --format-time but other than that LGTM.

sg


[cert] add cert lib with util functions / structs

This adds a cert library in the silicon_creator dir that contains helper functions and structs for managing OpenTitan certificates. Specifically a function is added to check if a cert's serial number matches what is expected. This function will be used to determine whether CDI0/1 certs need to be updated in the ROM_EXT (if the ROM_EXT or OWNER firmware is ever updated).

Good point @pamaury. I will capture your comment in a separate issue and track in the manufacturing board.


Training and testing instruction

Will you be able to provide the instruction for training and testing without using ocr (only table / cell detection). It's been really hard to get the code to work using setup.sh.
Thanks.

You can simply command the code such as "from .davar_det import *" in "/DAVAR-Lab-OCR/davarocr/davarocr/init.py" to select whether to use such package.


Suggestion for coursework spec

It may be wise to add some simple instructions on installing Spacy and the Spacy language models like "en_core_web_sm" etc.

I think that is reasonably easy to find online and taking the initiative on issues is part of courseworks. So I won't add that this time


Yes
If yes, what did you edit exactly?
Disabled "Flip" and "Redeploy" interaction menu
Short Issue Description
I've disabled instant death in ACE module settings, but i'm still instant dying if we take heavy shots (loosing conscience, then taking one or 2 more shots and dying)
Expected Behaviour
I've set 600sec before dying in ACE settings, so i expect not dying until this time limit :)
Steps to Reproduce the Issue
Server name: [EU]HoJ[www.hammerofjustice.org  -=TS:<IP_ADDRESS>=-]
Address: <IP_ADDRESS>:2302
Screenshots, Serverlog or any other helpful Information
"[KP LIBERATION] ACE detected. Deactivating resupply and weather scripts from Liberation."
"[KP LIBERATION] ACE Medical detected. Deactivating BI Revive System."
"[KP LIBERATION] [PARAM] Server finished parameters initialization."
Here is an action video recorded this evening
http://plays.tv/video/5b0200c5781c7d31a7/instantdeath
Same as : https://github.com/KillahPotatoes/KP-Liberation/issues/335

Hi Wyqer,
ok sorry for the annoyance, please close the ticket
rgds


Patch 1

Closes #1197
Hopefully this isn't a breaking change. Keeping the default that using --diff disables the stash, but allows someone to turn that back on if they want to.

So this will enable it with --diff --stash, looks good! Maybe the README can be updated as well.

Ping?


yolov8 notebook

Wow YoloV8.
I wonder if we can make this a webcam demo?

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

I think it is not good idea at least for now, when they have a pick of popularity. People search such tutorials and want to have only related stuff. Downloading and converting approaches are different, it will lead to mess (however it is usual state for yolo) and do not provide more clarity...
Beside that this tutorial not fibnished in quantization part, I got some issues with model accuracy, so this part I believe requires more efforts then for other models. I have nothing against to combain it with yolov5, because now ultralytics provides unified api for both yolov8 and yolov5.

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

I think it is not good idea at least for now, when they have a lot of popularity. People search such tutorials and want to have only related stuff. Downloading and converting approaches are different, it will lead to mess (however it is usual state for yolo) and do not provide more clarity... Beside that this tutorial not finished in quantization part, I got some issues with model accuracy, so this part I believe requires more efforts then for other models. I have nothing against to combain it with yolov5, because now ultralytics provides unified api for both yolov8 and yolov5.

One option could be to have a common notebook which introduces to YOLO and compares it's different versions which are generated in separate sub-notebooks for each version. That notebook could be useful if the user wants to compare accuracy and performance of different version on the same HW and even same video sample.

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

I think it is not good idea at least for now, when they have a lot of popularity. People search such tutorials and want to have only related stuff. Downloading and converting approaches are different, it will lead to mess (however it is usual state for yolo) and do not provide more clarity... Beside that this tutorial not finished in quantization part, I got some issues with model accuracy, so this part I believe requires more efforts then for other models. I have nothing against to combain it with yolov5, because now ultralytics provides unified api for both yolov8 and yolov5.

One option could be to have a common notebook which introduces to YOLO and compares it's different versions which are generated in separate sub-notebooks for each version. That notebook could be useful if the user wants to compare accuracy and performance of different versions on the same HW and even same video sample.

Maybe we could create a series of notebooks over the same number(folder) and include several approaches. I found it interesting in this notebook, that is covering the complete pipeline conversion, optimization, validation and also using the benchmark app. I will add more comments in my review.

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

We can build a webcam demo that can toggle between all these models maybe? How do we host the pre-trained and optimized model without model zoo?
I think it's great if we can run these demo side by side, and then reference back to the 'how-to-get-there' notebooks here.

Adding this to my previous review:
An error in cell 10.

In my first review I used a 10th Gen Machine - Windows 10 - Python 3.8.0
This error is happening in a 12th Gen Machine - Windows 11 - Python 3.9.13

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

We can build a webcam demo that can toggle between all these models maybe? How do we host the pre-trained and optimized model without model zoo?
I think it's great if we can run these demo side by side, and then reference back to the 'how-to-get-there' notebooks here.

Yes, But we have already got 401 for object detection webcam ?  shall we put them together in it ? or let's re-design our notebooks category. For example, put all objection model example into one separate fold and label it for different use case (entry level, webcam, model optimization or solution level)?

Adding this to my previous review: An error in cell 10.  In my first review I used a 10th Gen Machine - Windows 10 - Python 3.8.0
This error is happening in a 12th Gen Machine - Windows 11 - Python 3.9.13

OMG! They change interface again.  :(
Probably issue connected that you use 8.0.5 version (in 8.0.3 format was different from 8.0.4 too), thanks I take a look

Regarding loggin, it looks like some difference logging setup on windows and linux machine (it is expected at least in emoji usage part, because their printing is problematic. Regarding return none, please see https://github.com/ultralytics/ultralytics/issues/313As I already answered on Paula comment, they change api. I pin yolov8 version for now for avoid unpredictable result

View entire conversation on ReviewNB

misclick, removed

View entire conversation on ReviewNB

added

View entire conversation on ReviewNB

added

View entire conversation on ReviewNB

increased output resolution

View entire conversation on ReviewNB

added explanation how to read this plot

View entire conversation on ReviewNB

now they should be consecutive

View entire conversation on ReviewNB

provided

View entire conversation on ReviewNB

added

View entire conversation on ReviewNB

aligned

View entire conversation on ReviewNB

Hi Since YOLO's input and out layout are almost same, I just wonder can we combine all YOLO-based instance into one notebook?

I think it is not good idea at least for now, when they have a lot of popularity. People search such tutorials and want to have only related stuff. Downloading and converting approaches are different, it will lead to mess (however it is usual state for yolo) and do not provide more clarity... Beside that this tutorial not finished in quantization part, I got some issues with model accuracy, so this part I believe requires more efforts then for other models. I have nothing against to combain it with yolov5, because now ultralytics provides unified api for both yolov8 and yolov5.

One option could be to have a common notebook which introduces to YOLO and compares it's different versions which are generated in separate sub-notebooks for each version. That notebook could be useful if the user wants to compare accuracy and performance of different versions on the same HW and even same video sample.

I am thinking that this is probably not a good idea. With this, we show the advantages of some models to the user while creating a negative perception of other models. You should hear about the strong competition between YOLOv7 and YOLOv5 Ultralytics which led to YOLOv8 finally. I would suggest not making comparisons of algorithms, models, etc. but letting the user decide on his end based on the public data or whatever.

this resize type in not supported, because it is preserves aspect ratio plus requires padding.also not sure about dims expanding (at least on python side HWC layout can not be fit to NCHW)

View entire conversation on ReviewNB

I can rewrite this op on numpy for now instead of using it on yolo side

View entire conversation on ReviewNB

FP32 - 330FPS with ARC A770

INT8 - 356 FPS with ARC 770

Nice!

Webcam - OV_model FP32 - 12Gen Machine

Webcam - INT8 model - 12Gen Machine

My best pajama version 😂

@eaidova, could you please add the device_name option? so we will have the flexibility to change the device if needed. Thanks

fixed, thanks

View entire conversation on ReviewNB

agree, changed structure

View entire conversation on ReviewNB

I deeply analyze postprocessing, it will be a lot of code if I add it directly to notebook... I think we can have it in future or at least it can be possible to converted using pytorch fe (torchvision.nms layer is already in plans, yolov8 nms based on it)

View entire conversation on ReviewNB

I added next steps section with info how to use async api and integrate preprocessing (but letterbox stayed in user code), I think we can consider it as part of preprocessing api

View entire conversation on ReviewNB

@eaidova Do you know how it is possible to fix this? It is just working on CPU, iGPU and dGPU are not working. :(

 @eaidova Do you know how it is possible to fix this? It is just working on CPU, iGPU and dGPU are not working. :(
run_object_detection(source=0, flip=True, use_popup=False, model=ov_model, device="CPU") is the function to work with the webcam and see the inference in real-time.

@paularamo probably ov_model should be reshaped to have static shape before loading- for working on GPU as it does not support dynamic shapes.
we need to have it dynamic for obtaining accuracy results (inside yolov8 code, it uses preprocessing which lead to dynamic input shapes

detect_without_preprocess and quantize_model_with_preprocess is much faster but I cannot see correct BB over the video.

Thanks @eaidova It is working with GPUs now.

done

View entire conversation on ReviewNB

Since we are sharing the dataset, shouldn't this be part of the data directory @ the root folder?

impressive... A770 and YoloV8 = over 1000fps.

Hi @eaidova ,nice work!
Any plans for the yolov8's segmentation?


[workload] WaitForPodsReady: Requeue at the back of the queue after timeout

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #599
Special notes for your reviewer:

/ok-to-test

/assign

/closed
superseded by #689

/close
superseded by #689


Error installing thpp: Wangle no such file or directory

For me the install script didnt work. So installing each dependency by itself.
Folly is ok (at least it says so, and included in (/usr/local/include/folly)
Fbthrift seems ok.
But then thpp fails: after creating build directory and running cmake when running make I get the following error:
In file included from /usr/local/include/thrift/lib/cpp2/server/Cpp2ConnContext.h:22:0,
                 from /home/downloads/fbcunn/fb/thpp/thpp/build/thpp/if/gen-cpp2/Tensor_types.tcc:15,
                 from /home/downloads/fbcunn/fb/thpp/thpp/build/thpp/if/gen-cpp2/Tensor_types.cpp:9:
/usr/local/include/thrift/lib/cpp/concurrency/ThreadManager.h:28:43: fatal error: folly/wangle/concurrent/Codel.h: No such file or directory
 #include <folly/wangle/concurrent/Codel.h>

any help is appreciated. It seems that by installing folly not all files are copied correctly.

hi, sorry about this. I just fixed the fblualib install script so that this error does not happen now.
You'll have to redo the install process starting from this step:
https://github.com/facebook/fbcunn/blob/master/INSTALL.md#install-folly-fbthrift-thpp-and-fblualib

Thanks!


i use power toys to remapp the escape to shift (right) but save and restart the pc no change

Microsoft PowerToys version
zae
Running as admin

[X] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce

✔ Expected Behavior
shift (right become escpae)
❌ Actual Behavior
No modification shift right the same thing as before and doesnt act like escape
Other Software
No response

My bad ad the second command to correct
Good day


[RFE] Change the color and shape of the icon on the button depending on the status

It would be nice to see at a glance why clearing isn't occurring rather than needing to hover over the button and read the text. As such, I propose that the color and shape of the icon on the button should be different for each reason that clearing is blocked.

@TehFreek I've added the option in v2.0.0 to configurably color the icon based on categories of reasons that drones might not be clearing.  Thank you for the idea.