Working with bash arrays

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

This closes #7687

Our team has been working diligently to clear the backlog and we should be getting this pull request ready to be published next week 🚀

Plagiarism check is done

Sure, he can take it over @

👍  Thank you @WanjaMIKE
@Youngshark3
Be sure to reach out if you have any questions along the way - be sure to use the comment feature via GitHub to leave notes.

okay thanks @hectorkambow on it

@Anitaachu okay checking

cc @WanjaMIKE @hectorkambow done its okay for the next step

Did you complete the prelim review - or the tech review portion?? @Youngshark3

If both are complete - we can add the "ready for final review" 👍

@hectorkambow  yeah everything is fine. Done both prelim and tech review

🚀
Fantastic !!! We will be sure to give this a final review and assess the PR 👏
Nicely done.

👏
Nicely done @Anitaachu  & @Youngshark3
🚀
Please be sure to go over any edits made to the PR to improve future blog posts and reviews.
@Anitaachu
You'll be able to see your live published article on the site (in about 30 mins or so).
To give your article a boost in page engagement - be sure to share it across your social site (LinkedIn/Twitter) and tag the EngEd program so we can also share it and give it some traction/exposure as well!
If you have not done so already - consider adding a skill section to your author page. This will go a long way for potential future employers.

NOTE: Also, take into consideration that you can add any other past projects of yours: videos, talks, tutorials, articles (on ANY >other site) - you can add them to your EngEd profile.
Think of the EngEd profile as your one-stop shop for everything you do in DEV - making it easier for you to share all your >accomplishments when you go out for an interview or employment opp.
It can be from any blog site (or site in general).

Let me know if you have any questions moving forward.

Thanks @hectorkambow and congratulations 🎉@Anitaachu

@Anitaachu
Hello hello!
We wanted to announce that we're going to take a focus on content centered around Kubernetes (K8s) for the month of August.
We have enjoyed reading all amazing content that has been created the last few months - and with so much to explore with K8s we wanted to invite the community to approach it.
Wit_h that said, the best five (5) K8s related articles that come in this month will be eligible to receive a complimentary virtual pass to KubeCon USA ($75.00 value) in Oct.
We're looking for content that enriches developers' understanding of K8s, best practices, and its many use cases._
Please be sure to go over the already published content the EngEd community has created on Kubernetes to see where we can build upon or further explore.
While we're not restricting content solely to K8s-related articles over the next month, we will prioritize acceptance and review of K8s content over other topics.
Please be sure to complete the topic suggestion form when you're ready to dive in.
Happy coding!


Accept connections over HTTPS.

This feature request is geared towards being able to run an HTTPS proxy server, as opposed to being able to connect through to HTTPS target pages on the other side, as is the goal of #4.
The Problem

Presently, all client connections to hoxy are only possible over plain HTTP.
In reverse mode, target pages that assume or demand HTTPS in their implementation may break completely because an HTTPS reverse proxy endpoint is not available.
In forward mode, target pages that assume or demand HTTPS in their implementation will generally load their resources in a way that avoids proxying completely, because typically the OS routes HTTPS requests through an entirely different proxy configuration (via the $HTTPS_PROXY environment variable, for example, instead of $HTTP_PROXY) and in many cases this is out of the control of the user of hoxy's API. Setting both configurations to the same proxy will work in some scenarios when #4 lands, but will break when the environment assumes (reasonably) that the proxy itself speaks HTTPS.

The Solution

Provide an API to create a hoxy instance that will respond to HTTPS connections. This could be exposed through configuration on the existing options object given to Proxy or via a new class, as is common with other libraries.
Ideally, all combinations of client and target protocols work by the time this is complete.

Client Protocol
Target Protocol
Proxy Direction
Works Today

HTTP
HTTP
Forward
:heavy_check_mark:

HTTP
HTTPS
Forward
:x: (soon)

HTTPS
HTTP
Forward
:x:

HTTPS
HTTPS
Forward
:x:

HTTP
HTTP
Reverse
:heavy_check_mark:

HTTP
HTTPS
Reverse
:heavy_check_mark:

HTTPS
HTTP
Reverse
:x:

HTTPS
HTTPS
Reverse
:x:

Yay! What glorious tables!

I'm going to try to argue that rows #3 and #4 can go away, and that #1 and #2 are good enough to cover all interesting forward proxying use cases.

[forward proxying] will break when the environment assumes (reasonably) that the proxy itself speaks HTTPS.

Maybe if I understood this part I'd come around, but it's the part I'm specifically unclear about. Which environment? And in what sense would it assume https? Neither OS X or Firefox proxy config screens for example have a "this proxy is itself an https server" checkbox. Thanks for bearing with me.

So the issue with ignoring row 4 is Strict Transport Security, where the site demands a secure protocol. Most of the sites I work on use this and it's only going to get more popular. The end result is that the browser will refuse to display anything if the client protocol is plain HTTP.
Row 3 probably isn't so important. I don't have a strong need to upgrade the security of a target site through my proxy, although that would be cool. I included it mainly for completeness.

HSTS guards against attempts to make anything other than "https://" appear in the URL bar. "https://" being in the URL bar depends not on whether the proxy runs as HTTPS, but on the conversation happening in the tunnel, which for our purposes is always going to to be HTTPS. So even though Hoxy always runs as HTTP, "https://" still appears in the URL bar and thus it shouldn't run afoul of HSTS.

So even though Hoxy always runs as HTTP, "https://" still appears in the URL bar ...

I'll have to see this to believe it, I've never heard of a proxy setup where that is the case.
If you are correct, then fair enough, I will concede that we don't need row 4.

@sholladay, Could you be thinking of reverse proxies?

Well, 2.0 is released now, so you can try it out directly against your HSTS servers. It would be good in any case to start getting more eyeballs on it, surfacing bugs, etc.
I think the reason an http server is allowed to mediate the tunnel is that it doesn't participate in the encryption, so there's really no need.

Well how about them apples. I learned something new today. Thanks, guys, you are totally correct.
I am a bit confused about how this works underneath. Presumably the network layer needs to know the protocol of the proxy itself before connecting to it and my (incorrect) understanding was always that the whole point of having separate configurations for HTTP and HTTPS is to allow one to be assumed when an app (like a web browser) decides to route through that configuration (based on the protocol in the address bar, for example).
Now I'm left wondering what the consequences are of doing it like this (row 2) vs row 4.

So to summarize the scope of this issue, given rows 1, 2, 5, 6 all now work and 3 and 4 can go away (with the caveat that Hoxy needs better documentation about how it intercepts http connect tunneling) the focus here is to get 7 and 8 working, agreed?

Agreed. So @snoj, do you expect both row 7 and 8 to work with your version? Or is 8 a whole other level of project? And what is left to make a PR based on that?

e651fcbdccdcef1eb75b45f76936690a5bd92b79 should do the trick for 8.....maybe 7 (hadn't tested that one).

I think the only difference between 7 and 8 would be the value of the reverse option, which would simply trigger Hoxy's existing protocol switch like so:
// row 7
new hoxy.Proxy({
  reverse: 'http://example.com',
  key: ...,
  cert: ...
})

// row 8
new hoxy.Proxy({
  reverse: 'https://example.com',
  key: ...,
  cert: ...
})

@greim I agree, that should be the only difference. Again, my earlier commit was only tested under the 8 but I don't see why it wouldn't work for 7.

Thanks @snoj. In my own tests it works for both 7 and 8. Published as 2.1.0. Let me know how it works.
PS: I shortened the option to just tls:
new hoxy.Proxy({
  reverse: 'https://www.google.com',
  tls: {
    key: fs.readFileSync(__dirname + '/my-server.key.pem'),
    cert: fs.readFileSync(__dirname + '/my-server.crt.pem'),
  }
});

Thanks for all of the hard work on this, everyone. @greim if you create a new temporary ticket or re-open this, I would be happy to post another bounty against it. It really saves the day for me.


foundation agent need inbound network available which break acm pull mode design

Problem:
I follow the guide to make  foundation-hub and foundation-agent get deployed and all related pods state in Runnning ,  I noticed that foundation-agent depends on inbound network agent-address so that hub cluster access to managed cluster directly, this behavior break ocm pull mode, in the most of case,  the managed cluster doesn't have inbound network, such as the managed k8s cluster placed in private IDC.
Due to above problem, the api to get container log from managed cluster doesn't work as well, please take a look this issue and rethink the container log retrieval solution, thanks in advance.
curl -sk -H "Authorization: Bearer $TOKEN" -H "Content-Type:application/json"  https://<IP_ADDRESS>:32768/apis/proxy.open-cluster-management.io/v1beta1/namespaces/cluster1/clusterstatuses/cluster1/log/open-cluster-management/klusterlet-registry-server-6b4f866fcd-wl8sc/klusterlet-registry-server
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "error trying to reach service: dial tcp: lookup foundation-agent.open-cluster-management-agent.svc on <IP_ADDRESS>:53: no such host",
  "code": 500
}

Thanks. This is currently by design...since we do not want to save logs from clusters on the hub. I would certainly like to know if there are other techniques for log collection that we can leverage.

Thanks. This is currently by design...since we do not want to save logs from clusters on the hub. I would certainly like to know if there are other techniques for log collection that we can leverage.


Remove implicit retain of self in eventMonitor block

In MASShortcutView.m, -activateEventMonitoring: was implicitly retaining self in two places by using the _shortcutValidator variable. In certain cases, this caused the control to fail to recognize new keystrokes.
To see the problem in action, run the attached sample project. Click shortcut view, then press command-w to close the window (before a shortcut has been set). Open a new document window and click the shortcut view there - at this point modifier keys will not register in the view.
The reason seems to be that because self is retained buy the block, when the new control calls -activateEventMonitoring:, the old block and therefore the old self is dealloc'ed, which causes activateEventMonitoring: to be called a second time with NO.
TestApp.zip

Perfect, thanks @danmessing!


Schedule an accessibility consult when we have a built out prototype

moved to jira https://jira.cac.washington.edu/browse/DAWGPATH-20


Cropped transparent PNG produce red background

hello,
and thank you for this cropper :)
i crop a PNG image in my Flutter web project.
i take the cropped bytes and set them to an Image widget but instead of transparent background i see a red background.
code:
ui.Image bitmap = await controller.croppedBitmap();
var data = await bitmap.toByteData(format: ui.ImageByteFormat.png);
if (data == null) {
//TODO: handle error
return;
}
Uint8List pngBytes = data.buffer.asUint8List();
setState(() {
  _croppedImage = pngBytes;
});

and then show the bytes with:
Image.memory(_croppedImage!)
i also tried to save the bytes to a file and show the file with the same result.
i attach a PNGs files for debug :)

Ooops, that seems to be the remants of a debug move at: https://github.com/deakjahn/crop_image/blob/1db6ca118894a6e1cd207a94cdbfd20d01be5ebc/lib/src/crop_controller.dart#L246

@deakjahn Sorry about that, I didn't think about transparency!

Nothing to it. :-)


Byron era: Make rules pertaining to the permissive BFT polymorphic

Building upon issue #238 and a corresponding PR #239, the implementation of transition rules for the permissive BFT in the Byron era has to be updated so that the rules are constrained by the Block b type class from Cardano.Spec.Consensus.Block module instead of relying on the monomorphic Block type from the Cardano.Spec.Chain.STS.Block module.
This is all part of https://github.com/input-output-hk/ouroboros-network/issues/168.

@nc6, I'm planning to change the STS framework a bit. In particular, given that at the moment a specific type is expected as a signal for an STS, I'm planning to change that to a class constraint. For example, the CHAIN STS's signal wouldn't be the Cardano.Spec.Chain.STS.Block.Block type, but instead the signal would be constrained by the Cardano.Spec.Consensus.Block.Block class. Does that sound reasonable to you?
I started making changes along these lines, but then there's a whole snowball effect. For example, the first change to be made is in what is a signal of an STS:
class ( Eq (PredicateFailure a)
      , Show (PredicateFailure a)
      )
  => STS a where
  ...
  type family Signal a :: * -> Constraint
  ...

This then made me to change the transition rule context from a newtype wrapping an environment, a state and a signal to this:
-- | Context available to transition rules.
data TRC sts sig where
  TRC :: Signal sts sig => (Environment sts, State sts, sig) -> TRC sts sig

Does it make sense for a TRC to be parameterised by a signal? This change then triggers many more changes further down the line.

So, this could make sense, but I'm a little sceptical of the value. Such a block constraint is likely to be very constrained, since we rely a lot on the internal details. And part of such a constraint would require that e.g. we are able to extract the UTxO in the precise format used in the executable spec. I can't imagine we'd end up with very many instances for such a class, which limits the usefulness of making it one.
As an alternative, if the blocks are suitably equivalent, we could just pre-process them to create the Block type, which is after all meant to represent the most basic block needed for implementation of the spec.

cc @edsko if you think there are good arguments the other way

No no, we certainly shouldn't need to abstract over stuff like the UTxO, delegation, whatever. We just need to make sure that the consensus aspect is separated out. We should be able to run PermBFT with a different type of block and a different type of ledger, since PermBFT is independent from the ledger. I'd not expect to be able to compute the entire ledger on a different type of block; that would likely not be very useful, since you'd end up with constraints for all parts of the blocks and then might as well just require the very block type that the ledger rules require.

@nc6 @mdimjasevic This is the same consensus/ledger split we discussed previously, no?

@nc6 @mdimjasevic This is the same consensus/ledger split we discussed previously, no?

Yes.
Where do I go from here?

We need to make sure that the consensus part of the rules is independent from the ledger part of the rules, and that the consensus part (but not the ledger part) is polymorphic enough.

As we discussed it earlier today, instead of making the rules polymorphic by making their signals a constraint rather than a type, I'm simply providing a function that converts a polymorphic block as given by a type class into the concrete block type used in cs-blockchain.


Add logos to footer

mostly fixes #244 - all logos and links are present, but some are still very small.

the individual commits are a little messed-up - I renamed the creative commons logo earlier in the process than I meant to. Everything works in the final commit, however.


Skywalker X8 VTOL unable to recover from gust

After attempting to climb to 30 m in mission mode a moment is applied due to a gust. This causes the DeltaQuad to bank excessively sending it into a pitch down dive. We attempted to take over manual control but we didn't have enough altitude to recover.
We flashed our flight controller (Dropix V2.1) with the Master branch (Updated 24th September). We then tested our DeltaQuad in manual mode quickly to ensure everything was working correctly and we set up a simple mission (with a few way-points then a land only in QC mode). It began climbing normally until 24 m when a gust caused the drone to enter a roll. The drone wasn't able to recover from this and caused an adverse roll followed by a nose down attitude until contact with the ground.
Link to the log file: https://review.px4.io/plot_app?log=992ecb6b-8410-4bd6-91e2-e82a7fa5e826
Our drone is a Skywalker X8 with VTOL modules.

Hi @DavidMackie
The log you posted is not from a Vertical Technologies DeltaQuad as far as i can tell. Is this your own build?

This was flying with the master branch

My best theory is IMU failure between 1:15 and 1:16. Can anyone confirm this?

@DavidMackie can you please confirm if this was your own built vehicle or an official Vertical Technologies DeltaQuad?
If it was your own vehicle then i should note that the parameters associated with the airframe you selected have been specifically tuned for the proprietary hardware in the official DeltaQuad and should not be used on other vehicles. You would be better of using the Generic Quad Delta airframe as the settings in the Vertical Technologies DeltaQuad will likely not work on your vehicle.
From your log it seems like there was a motor failure (motor 4).


Are there any suggestions about how to get better registration result for brain image?

I use default parameters to register my data, but the result is real poor. Is there anyone who could give me some suggestions about how to get better registration result for brain image?
One of images looks like that:

Which default parameters are you using? What do you mean by "poor"? Is the the images not overlapping? Is your evaluation (Dice Similarity Coefficient, Target Registration Error etc) bad? Can you add (like, pixelwise add using sitk.Add()) the fixed image to the result image and show the result?


"Embed" bower and grunt in plugin

Hi,
Bower and Grunt must be installed before one can run this plugin. Shouldn't this plugin install them (locally if needed) and execute them from node_modules?
What do you think about it? It would help make the build more self-contained (except for the npm requirement, but this seems valid as it is maven-like).
Regards,

+1


Fix file owner and group out of sync in activeSync

activeSync:  Fixes file owner&group out of sync

@fuchaohong Hi Thanks for this contribution! I think your branch is in an incorrect state. It contains other commits other than your own, so it is causing conflicts.

@fuchaohong Hi Thanks for this contribution! I think your branch is in an incorrect state. It contains other commits other than your own, so it is causing conflicts.

@gpang Hi Thanks for your adivce! The base branch is wrong, now changed.

@gpang Hi Would you please help me answer. I find the reasons for unsuccessful check is building, but i used the same command to build successfully. https://github.com/Alluxio/alluxio/pull/13051/checks?check_run_id=2094216645

@fuchaohong thanks for your fix. Our normal process is that  we fix any bugs in the master branch and then maintainers will cherry-pick to the needed release branches. So for this fix, could you please target the master branch instead?
Thanks.

@fuchaohong thanks for your fix. Our normal process is that we fix any bugs in the master branch and then maintainers will cherry-pick to the needed release branches. So for this fix, could you please target the master branch instead?
Thanks.

@yuzhu  Thanks for your advice. I will try again base the master branch.


App crashes when select the second image with FormBuilderImagePicker()

When i click to slecte the second image, the app crashes on iOS leaving no information on debug console.
Debugging with xcode I got this error:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread.'
terminating with uncaught exception of type NSException
CoreSimulator 732.17 - Device: iPhone 11 (88C2B28E-CBE3-4968-BA1F-8A8300282058) - Runtime: iOS 14.0 (18A372) - DeviceType: iPhone 11

See https://github.com/flutter/flutter/issues/65995 for the tracking issue in Flutter


add event bucket index & middleware

Which usecase do we have rot this index based approach?

I'm thinking of how to get projection asynchronous. Or rebuild the projection separately. And so that everything works, in my opinion, you have to know at which event you stopped in order to continue there.

@DanielBadura This is important so that we can run parts of the stream in the future. Such as a cron job that delays the processing of events and always remembers where it has stopped. Or a async runner, who always pulled the last events.


SAMZA-1108: Implementation of Windows and various kinds of Triggers (WIP)

Implemented various triggers and the orchestration logic of the window operator.
Implemented wire-up of window and the flow of messages through various trigger implementations.
Implementations for count, time, timeSinceFirst, timeSinceLast, Any, Repeating triggers.

Pending:

More tests.

@vjagadish1989 Can you please refer the JIRA for this PR?

@vjagadish1989: I'm working through the pull request locally as discussed. One observation: we're losing type information in WindowOperatorImpl and when I add the missing type information (e.g. to spec.getWindow()) the types don't match up (e.g. there is an assumption that K = WK that is not explicitly worked out in the type system). I would suggest taking a look.

Address @prateekm 's feedback.

@nickpan47 :

I do prefer to make the whole queue of callbacks, the context to schedule and cancel callbacks in a single class (maybe TriggerCallbackScheduler??).

Wouldn't this will move complexity (and simply a bunch of code) from WindowOperatorImpl to a differentTriggerCallbackScheduler class? The context to schedule and cancel callbacks must be created per trigger key instance.

The functions that refer to a lot of WindowOperatorImpl internals can stay in the inner classes that mainly implementing callback functions to be invoked by the scheduler.

I extracted out inner classes for greater readability into their separate files.


nuxt.config.js unexpected identifier import webpack  nodemon

Version
v2.4.5
Reproduction link
https://github.com/rossma/nuxt-express
Steps to reproduce
npm install
npm run dev
What is expected ?
Client and server files are compiled and server starts up
What is actually happening?
The following exception is thrown
(function (exports, require, module, __filename, __dirname) { import webpack from 'webpack'
^^^^^^^
SyntaxError: Unexpected identifier
at new Script (vm.js:80:7)
at createScript (vm.js:274:10)
at Object.runInThisContext (vm.js:326:10)
at Module._compile (internal/modules/cjs/loader.js:664:28)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
at Module.load (internal/modules/cjs/loader.js:600:32)
at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
at Function.Module._load (internal/modules/cjs/loader.js:531:3)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
Additional comments?
Create a nuxt app using npx create-nuxt app
Specify express as an option
Following script is generated in the package,json
"dev": "cross-env NODE_ENV=development nodemon server/index.js --watch server",
Modify the nuxt.config.js file so that we import webpack : import webpack from 'webpack'
call npm run dev and exception occurs.
running with nuxt command doesn't cause this exception.
instead of using import I still with using require.

This bug report is available on Nuxt community (#c8825)

You can't use ESM syntax for your nuxt.config.js when calling it programmatically. Nuxt knows what ESM syntax is but express not ofc.)
Solution:
Preload the esm module as in:
node -r esm server/index.js

The docs do show to 'import webpack' here  https://nuxtjs.org/faq/webpack-plugins/


CLOUDSTACK-10137: Only link log4j if not already present

When reinstalling the package, cloudstack-management fails to install properly due to the log4j.xml already present.

@rhtyd to be confirmed in your upstream environment.

@marcaurele thanks, I went ahead and fixed similar issues for centos6 and centos7 as well.  I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1242

Tests LGTM, this is a packaging only change so no need for regression testing. Was able to install and upgrade.


Feature Request:  Request for Data folder in Vaccine Admiral Repo

Feature Idea
Vaccine Mock Data Folder: This folder is for Storing the mock (dummy) SDTM data required for Vaccine ADaM Development, we have generated 6 SDTM (DM,EX,AE,VS,CE,FA) also be including IS required for ADCE, ADFA, ADIS to start with. The data is pulled from Vaccine CDISC TUG or SDTM IG or Scenario based on comments received for Pfizer, GSK, J&J Colleagues. It has 7 programs and individual programs for each domain and one util for generating basic SDTM meta data from the List of variables given in SDTM IG. It will be helpful place the above-mentioned files in a folder to share across pharma and make updates as applicable (As discussed in the admiral vaccine meeting). (Please be informed that this mock data is for vaccine development since the Admiral Test data was not sufficient)
Relevant Input
input to the meta data is a excel sheet containing Variable Name, Variable Label, and Variable time (Charecter / Numeric) . Few data records are taken from Vaccine CDISC TUG (might expand based on client specific requirements)
Relevant Output
SDTM data frames in Rda file
Reproducible Example/Pseudo Code
Kindly provide the folder and access, so the code can be uploaded for review and enhancement

Hi @jsrivj please do a Pull Request for uploading this data.  Spec is also really nice to have!


faucet transactions fail to deliver tokens

Describe the bug
@yelllowsin writes:

I am still having issues with the faucet, can't get tokens to be delivered to this address. I am feeling hopeless already, I have tried many times, but still none worked for me: https://testnet.explorer.agoric.net/account/agoric1qr2s775y7umrm90ykjtfnhyk76zsrapx3z2xm8

Here another example of RUN tokens that should have been delivered but are not at the destination address: https://testnet.explorer.agoric.net/transactions/9EF1AAFC10A92C6B195A6B438894D5372BEB16A5D6CE6F2C53121BDC2B34FD04

To Reproduce
?
Expected behavior
?
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

?
Additional context
originally reported in https://github.com/Agoric/faucet/issues/6#issuecomment-904552904

I changed the faucet to use --gas=600000, based on experience from Osmosis DeFi and IBC relayed by Wanderer and @dtribble .
https://discord.com/channels/585576150827532298/819073555446759444/879623916484689960
This seems to have addressed the issue:
https://testnet.explorer.agoric.net/account/agoric1e7uewvgnr8t47xmfwl5ul9rej2n2ylm9ju5ejp
https://testnet.explorer.agoric.net/account/agoric1qkq7vy0upxdeg5rm367skxrr687la85hgdfcvj
cc @michaelfig @katelynsills @mhofman @warner @rowgraus


[Infra Doc Fixit] Refresh documentation for Goma RBE

Hi!
To close this issue:

Are you still the owner? Update the spreadsheet if not and reassign.
If you don't consider any work is needed, close.
Please double check if the documentation is up to date and prune any stale
information
i. Review markdown docs in related code repos
ii. Review associated sites and wikis
Review the cookbook
i. If one does not exist, create it and link it on the team page
ii. Add and review common tasks
Review related dashboards
i. If this service does not have a dashboard, but should create it!
ii. Ensures it's on the Fuchsia infra teams dashboards

Thank you for keeping our service's documentation up to date!

Hi @CaseyHillers
why you have created same issue more than 1 times?
Thanks

Two days left of the fixit 🥳

Is there documentation for GOMA? I tried to investigate https://github.com/flutter/flutter/issues/99764 but I can't find any docs on it

We usually look at the goma stats json file. If there is something bad there will be a lot of errors or cache misses. In this case as the information was not collected we may need to look at the previous steps.
To bisect, usually we check if there was a toolchain roll when this started happening or if the toolchain cipd package is still available. If there haven't been any recent rolls the package may have been removed.

Closing because the bug has not been updated for more than one year.
Feel free to reopen any bugs that you believe are important but please provide updates on how to resource the fix of the bug and what can be done to prevent the issue from not getting updates for another year.


use covariant tests rather than exact ones

There are so many exact tests in the test suite that we don't need to duplicate them here - just a covariant test will do.

This is blocking https://github.com/dlang/dmd/pull/5881

LGTM


MM-11725: Filter archived channels by membership on search autocomplete

Summary
Filter archived channels by membership on search autocomplete
Ticket Link
MM-11725
Device Information
This PR was tested on: [One Plus 5, Android 8.1]

@enahum PTAL


Troff n Scoff Portal Location

Seagull is coming up with more locations (his computer is down for a bit)


feat: added HttpInterceptor to rewrite url at the client level

following https://github.com/Decathlon/tzatziki/discussions/17
This new HttpInterceptor class can intercept and rewrite the urls before any call from a RestTemplate or WebClient.
That way we don't need to override the production urls in the test config.
If a mock exists, the url will be transparently replaced by the mock url and port.

Codecov Report

Merging #19 (afe5361) into main (aaf66d5) will increase coverage by 0.35%.
The diff coverage is 92.68%.

@@             Coverage Diff              @@
##               main      #19      +/-   ##
============================================
+ Coverage     69.99%   70.34%   +0.35%
- Complexity      662      677      +15
============================================
  Files            34       35       +1
  Lines          2616     2657      +41
  Branches        283      288       +5
============================================
+ Hits           1831     1869      +38
- Misses          636      638       +2
- Partials        149      150       +1

Impacted Files
Coverage Δ

...com/decathlon/tzatziki/spring/HttpInterceptor.java
92.68% <92.68%> (ø)

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 aaf66d5...afe5361. Read the comment docs.


default-skin.png does not found in dist version

We are using Yeoman scaffolding in our project. When we run grunt serve:dist, the default-skin.png file doesn't found in dist folder - photoswipe plugin look for styles/default-skin.png.

I just added an item in 'copy' configuration in Gruntfile.js, like this:
{
  expand: true,
     cwd: 'bower_components/photoswipe/dist/default-skin',
     src: '*.png',
     dest: '<%= yeoman.dist %>/styles'
 }

Not the best approach, but... WFM - works for me


Don't work in Linux Fedora24

>>> random_account()
Attempting to create user UyD5ilsS22gQYK4:QGPflA21NGKiS9s. Opening browser...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "ptcaccount2/accounts.py", line 210, in random_account
    account_created = create_account(try_username, password, try_email, try_birthday)
  File "ptcaccount2/accounts.py", line 116, in create_account
    driver = webdriver.Chrome()
  File "/usr/lib/python2.7/site-packages/selenium/webdriver/chrome/webdriver.py", line 62, in __init__
    self.service.start()
  File "/usr/lib/python2.7/site-packages/selenium/webdriver/common/service.py", line 71, in start
    os.path.basename(self.path), self.start_error_message)
selenium.common.exceptions.WebDriverException: Message: 'chromedriver' executable needs to be in PATH. Please see https://sites.google.com/a/chromium.org/chromedriver/home

>>>

I've never tested it with any other OS other than OSX so far; do you have Chrome installed? The actual browser, not ChromeDriver. I should add to the readme that it requires Chrome to be installed, unless someone wants to do a pull request that adds firefox or other browser support.

See #11


[FLINK-15146][core][ttl] Fix check that incremental cleanup size must be greater than zero

What is the purpose of the change
ahead pr
At the moment, we allow zero value for the TTL incremental cleanup size.
Although technically zero value will not break the cleanup but practically there will be no cleanup.
We change cleanupSize to be strictly greater than zero to avoid confusion.

@flinkbot re-run

Hi @azagrebin , please take a look at the remaining issues before.

Hi @azagrebin ,

Hi @azagrebin ,
please take a look at the remaining issues.

Hi @azagrebin ,
please take a look at the remaining issues.

Hi @azagrebin ,
please take a look at the remaining issues.

Hi @wuchong , can anyone  look at this ?

@hehuiyuan , sorry, I'm not familiar with this component. Maybe @Myasuka can help to review this.

@hehuiyuan , sorry, I'm not familiar with this component. Maybe @Myasuka can help to review this.

@wuchong thanks

Thanks for your contribution, please rename your commit as #10507 (review) suggested.
(You could force push to your branch instead of creating a new PR)

Thanks for your contribution, please rename your commit as #10507 (review) suggested.
(You could force push to your branch instead of creating a new PR)

updated.

@flinkbot re-run.

@flinkbot re-run

Hi @Myasuka ，please review.

@flinkbot re-run

@flinkbot re-run

@flinkbot re-run

Hi @Myasuka , please review.


4-digit (integer) Strings are being converted into Dates when pushing to Consumers

Describe the bug
Whenever we send an event with a 4-digit string (e.g.: "4000"), it is converted to a date (e.g: "4000-01-01T00:00:00.000Z") instead of keeping the data type.
The workaround for this is to send the value as a Number instead of a String.
The issue is most implementations of Decimal serialization to JSON in JavaScript defaults its serialization to String instead of Number. And this actually makes sense to retain the value precision of the sender.
So, this is very likely to happen whenever we got 4-digit Decimals (with no decimal places) being sent on the event payload.
This is such a common thing to happen in monetary values.
We noticed this occurs due to this ISO_8601 conversion here:

(Most recent code here.)
This treats 4-digit numbers as a valid date (which is actually not wrong, as per standard).
We were thinking of skipping this specific case with something like:
const fourDigitInteger = /^\d{4}$/
const ISO_8601 =
  /^(\d{4})-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])(\.\d+)?(Z|[+-][0-2][0-9]:[0-5][0-9])?$/;
export const dateReviver = (key: string, value: string): string | Date => {
  if (typeof value === "string" && !fourDigitInteger.test(value) && ISO_8601.test(value)) {
    try {
      return new Date(value);
    } catch {
      return value;
    }
  }
  return value;
};

@Rotorsoft what do you think?
To Reproduce
Steps to reproduce the behavior:

Create a producer that sends an event with a 4-digit integer:

import * as dotenv from "dotenv";
dotenv.config();
import {
  randomId,
  store,
  Message
} from "@rotorsoft/eventually";
import { PostgresStore } from "@rotorsoft/eventually-pg";
import express from "express";

async function main() {
  store(PostgresStore("sandboxtesting"));

  const app = express();
  app.use(express.json());

  app.post("/produce-event", async function produce(req, res) {
    const event: Message = {
      data: {
        controlString: "5400",
      },
      name: "GenericEvent"
    };

    await store().commit("generic", [event], {
      correlation: randomId(),
      causation: {}
    });

    return res.status(204).send();
  });

  const port = 7330;

  app.listen(port, function () {
    console.log("listening at port", port);
  });
}

main();

Create a consumer to listen to the event:

import * as dotenv from "dotenv";
dotenv.config();
import express from "express";

const app = express();

app.use(express.raw({ type: "*/*" }));

app.post("/handle-event", function (req, res) {
  const data = req.body.toString("utf8");
  console.log("[handle-event] body", data);
  return res.json({ body: data });
});

const port = 7331;

app.listen(port, function () {
  console.log("listening at port", port);
});

Send the event by posting to the producer:

curl --location --request POST 'http://localhost:7330/produce-event'

See the failed conversion on the consumer:

[handle-event] body {"id":46,"name":"GenericEvent","data":{"controlString":"5400-01-01T00:00:00.000Z"},"stream":"generic","version":45,"created":"2024-06-24T17:38:14.879Z","metadata":{"correlation":"qJQU7HpabFKWVQxkSXQ-SOGJ","causation":{}}}

Expected behavior
Conversion not changing anything on the string:
[handle-event] body {"id":46,"name":"GenericEvent","data":{"controlString":"5400"},"stream":"generic","version":45,"created":"2024-06-24T17:38:14.879Z","metadata":{"correlation":"qJQU7HpabFKWVQxkSXQ-SOGJ","causation":{}}}

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: macOS Ventura 14.4 (23E214)
Browser: Postman Version 11.2.13

Additional context
:)

Sorry, I just noticed this was fixed on 2.1.4 and we were on 2.0.9. Closing issue :)


Add topic for diagnostic IDs

[ ] Add links from APIs
[x] Add links from C# coding guidelines

Internal previews

📄 File
🔗 Preview link

docs/csharp/roslyn-sdk/choosing-diagnostic-ids.md
Choose diagnostic IDs

[ ] Add links from APIs

Looks like those would be in a different repo, so I guess we'll have to wait until this PR is merged.


add formatDateLocal to convert dates to local tz

Issue: https://github.com/omnistrate/saasbuilder/issues/107

@coderabbitai review


Visualize Weights

Hi guys would be possible to add this feature for layer visualization or weights visualization, like on https://github.com/bruckner/deepViz
The feature that we have today make it difficult to see what is going on

Thanks, are you saying it is difficult to navigate through layers or is this difficult to inspect the weights and activations of a given layer? In case you haven't noticed, you can zoom in/out within visualizations by scrolling up/down with your mouse.

Hi you're saying like checking the weights of for instance Alex net layer 5? Correct me if I'm wrong, but scrolling up/down with the mouse on this seems practical?

It sounds like you're asking for visualizations of what each neuron has learned, rather than simply the weights of each neuron. It sounds like you're asking for visualizations that require "deconvolution".
I've looked into integrating https://github.com/yosinski/deep-visualization-toolbox, which is similar to DeepViz. Last I checked, there wasn't a deconv layer checked into BVLC/master yet (and thus not into NVIDIA/caffe, making this impossible for now.
Please correct me if I'm wrong.

Yes exactly they rely on a branch of caffe that has deconvolution, but still seems strange to zoom with the mouse just to check the weights right? That's why I was thinking more on a UI improvement even if there is no deconvolution yet

You're right - visualizing conv5 probably isn't going to be very helpful. But conv1 can be interesting to look at. Do you have a UI improvement suggestion other than adding deconv visualizations?
Our current visualizations are based off of this Caffe notebook:
https://github.com/BVLC/caffe/blob/master/examples/00-classification.ipynb

Fully agree I was just thinking in something that you click on the weight and it maximise/open in another window

Oh I see. Yes, I can see how that would be nice. I don't actually embed all of the data on the page now because for some models (i.e. GoogLeNet) the amount of data would be pretty huge. But it would be nice to be able to view the full image and/or download the data in some easy-to-read format (and you're not the first to request it). I'll put it on the v4.0 TODO list. Thanks for the suggestion!

@lukeyeager Is there any way to download the images from activation of each layer? How can I save the output of each of convolutional layers, when testing a single image?
@leonardoaraujosantos Did you find any other way for what you were looking for?


REST GET / endpoint not working

Following the merge of #66, I tried to use the new endpoints and noticed that GET / is not working (this is right after successfully creating both a global and a personal Snippet, using the POST / endpoint).

With global=1 I get HTTP 200 but it's actually a Mantis Access Denied error page
GET http://localhost/mantis/api/rest/plugins/Snippets/?global=1

HTTP/1.1 200 OK
Date: Sun, 10 Sep 2023 10:09:36 GMT
Server: Apache/2.4.57 (Unix) OpenSSL/3.1.2 PHP/8.1.22
X-Powered-By: PHP/8.1.22
Cache-Control: private, max-age=10800
Last-Modified: Sun, 10 Sep 2023 10:02:40 GMT
Content-Encoding: gzip
Vary: Accept-Encoding
Content-Length: 184
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8

Access Denied.

Login

Proceed

With global=0 I get HTTP 200 and an empty list, but there should be one Snippet; notice the X-Mantis-Username: anonymous header, which should actually be the administrator account owning the API Token I used for Authorization.
GET http://localhost/mantis/api/rest/plugins/Snippets/?global=0

HTTP/1.1 200 OK
Date: Sun, 10 Sep 2023 10:07:25 GMT
Server: Apache/2.4.57 (Unix) OpenSSL/3.1.2 PHP/8.1.22
X-Powered-By: PHP/8.1.22
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Last-Modified: Sun, 10 Sep 2023 10:02:40 GMT
X-Mantis-Username: anonymous
X-Mantis-LoginMethod: cookie
X-Mantis-Version: 2.26.0-dev
Content-Length: 15
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: application/json

{
  "snippets": []
}

@dregad

I fixed the access html / 2xx in case of access check error.  I'll open an issue for making sure methods like ensure* and access_denied() are REST API friendly.
I am not able to reproduce the second issue with anonymous. Authentication is handled by core, make sure API key is passed in your call.

See PR #69

I have also seen some local servers redirect http to https and lose authentication headers in the process.

Thanks for the fix. I confirm that with #69 merged,

With global=1 I get HTTP 200 but it's actually a Mantis Access Denied error page

is fixed

With global=0 I get HTTP 200 and an empty list, but there should be one Snippet

is working fine on this computer (Windows 10 with ubuntu running on WSL) but it's not the same one I used when I got the issue last week, so I'll double-check on the other box (MacOS) later to make sure.

With global=0 I get HTTP 200 and an empty list, but there should be one Snippet

is no longer reproducible on my Mac (even with 8d9a4c08) so it must have been an environment-specific fluke.


Support for React 19

Please support React19 !
In my opinion, it seems to be possible to handle this by simply appending ^19.0.0 to the peerDependencies field in package.json.

Thanks for reporting, fixed in 0.5.1


If you touch again while touching, the swipe does not work.

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: Swiper 3.4.0 - Released on October 16, 2016

Platform/Target and Browser Versions:

Android

Chrome and Default Browser
Webview

iPhone

Safari Browser
Webview

What you did
summary html

            ... there are many slides

summary javascript
var sswiper = new Swiper('.swiper-container', {
            loop : true,
            pagination : '.swiper-pagination',
            paginationClickable : true,
            autoplay : 2000,
            autoplayDisableOnInteraction : false,
            autoplayStopOnLast : false
        });

reproduce steps.

Touch and move with one finger.
Touch another finger again.
Release your finger.

When i touch one more by another finger while dragging slide, swipe stopped.
In additional, if i do set autoplay, autoplaying stopped as well.
test video is as below. you can see that.
https://goo.gl/qlbHcI
Expected Behavior
I expect swipe should not be stopped and autoplaying should work.
Actual Behavior
Swipe will stop and autoplay will not work.
Additional
i think, this is critical issue.
so, i have one solution.
solution is as below.
it is that add code in onTouchStart function of core.js.
AS-IS
if (!isTouchEvent && 'which' in e && e.which === 3) return;
TO-BE
if (!isTouchEvent && 'which' in e && e.which === 3) return;
if (isTouched && isMoved) return;
how do you think about it?

Me too. In the sliding process, another finger's touch will stick

same problem


Add skip_invalid_event parameter to in_forward. fixes #774

See #774

@sonots @tagomoris
I will add tests but how about this?

I commented on #774.

Add tests

Can I merge this?
After merge this PR, I will release v0.12.20.

@frsyuki @tagomoris @sonots if no problem, I will merge this today.


Fix wrong space to avoid error during deployment of the sample app with helm

Absolutely! Thank you very much :)


Enterprise Zones Proof of Concept app

Benefit
Proof of concept ExB app aimed at simplifying and at some point replacing current Locate app. Provide GOEO some possible options to keep core Locate functionality on a lighter weight platform.
Acceptance Criteria

[ ] GOEO finds that ExB alternatives meet business needs currently used in Locate.

Notes
No response
Risks
None
Issue Reference
refs #

Q3 Sprint 5 Tasks

[ ] Mock up Enterprise Zones in ExB

In progress. Options to filter Enterprise Zones by year haven't been working out as expected.

Can you share a link

I should have a couple options ready this week.

Experience Builder PoC:
https://experience.arcgis.com/template/eb28d48dda4045b0a18dfc9b99b06e03
Dashboard PoC:
https://utah.maps.arcgis.com/apps/dashboards/886f50a7af744c23884f5301630fb85f

Sprint 3

Investigate ExB more closely as a replacement for Locate

Layer grouping
Multiple EZ layers vs custom dropdown
Report replacement options

We're shifting gears to migrating the whole locate app to AGOL via https://github.com/agrc/planning-queue/issues/411


Use observability platform for modernisation platform cost metrics per application

User Story
As an MP Product manager, service owner and MP user
I want to view platform costs per application
So that I can use the data to drive cost savings
Value / Purpose
Replace a manual process of cost metrics with automated dashboards which are easily accessible to mp PM and service owner to view their cost metrics.
Useful Contacts
No response
Additional Information
When doing this work it would be beneficial to do it at an AWS org level, so that we could also monitor total AWS spend, off platform AWS spend, platforms AWS spend, and application AWS spend in future issues.
Proposal / Unknowns
No response
Definition of Done

[x] Total cost metrics for the modernisation platform on the observability platform split per application
[ ] README has been updated
[x] User docs have been updated
[ ] Another team member has reviewed
[x] Tests are green

See #7169 - we think there's a lot of commonality in how to get the data for both of these issues, although the information to be surfaced will be different in each.

Two thoughts here. Both #7169 and #7170 probably have the same requirement of hooking up the org root to observability platform. Once that's done, the question of how to display the data is the differentiator in these tickets, and they may well be repointed to a 3 once that first hard part has been achieved.

I have updated the Cost and Usage Report Dashboard (athena-cost-and-usage-report) to include an Account_id variable which allows our users to select single or multiple accounts allowing them to drill down and see specific costs.
documentation has also been updated in PR https://github.com/ministryofjustice/modernisation-platform/pull/8467 which can viewed here: https://user-guide.modernisation-platform.service.justice.gov.uk/user-guide/cost-metrics.html#using-the-account-id-filter

I think we can tidy this up, but the basics are here and look good - they have already helped the digital-prison-reporting team understand exactly where their costs have increased

I've reviewed this as well and I agree with Simon's comments above. All the DoD is complete.
Over time perhaps we will tweak it as needed when more users have had the opportunity to use it.
Nice one @ASTRobinson  👍


Changing ISO doesn't appear to change sensitivity

Firstly thanks for a wonderful library!
I'm probably missing something here but don't seem to be able to do much to control the sensitivity of the camera e.g. when I switch exposure_mode=off and then set the ISO to 100 then 400. I was expecting that this would change the analog_gain and digital_gain and therefore the exposure of the preview etc. assuming nothing else is changed. In my testing the preview exposure doesn't seem to change and neither do the values of the gains. I've included the status output from my program (just the values returned by calls to the picamera object)
exposure_mode set to off, iso set to 100
resolution:            2592,1944
framerate:             5
shutter_speed:         59984
exposure_speed:        59984
iso:                   100
exposure_mode:         off
exposure_compensation: 0
analog_gain:           83/16
digital_gain:          141/128
iso then set to 400, no change to analog_gain or digital_gain.
resolution:            2592,1944
framerate:             5
shutter_speed:         59984
exposure_speed:        59984
iso:                   400
exposure_mode:         off
exposure_compensation: 0
analog_gain:           83/16
digital_gain:          141/128
Am I missing something about what iso should be doing and how I should be adjusting the sensitivity.
Finally is there any way I can read/deduce the iso value when using auto-exposure (in the same way I can use exposure_speed to see what the automatically set value of shutter speed is) e.g. is iso=100analog_gaindigital_gain?

Hi,
Thanks for this library, which is well documented, and easy to use for Raspberry Pi newbies as me.
I'd like to bump up this question, since I observe the exact same issue on my RPi 3B+ with camera Board v1.3.
As Dpcryer noted, it seems not possible to read the ISO value while the camera is in auto exposure mode. (the attribute getter returns the previously set ISO value, hence 0 if in auto exposure instead of the actual ISO value)
What I would like to do is set the camera on auto exposure mode, and then read the actual values of every attributes, and observe how the camera behaves under particular condtions.
Many thanks for considering this request

Hi,
First of all, thanks a lot for this well documented Python module, very handy for quick Pi camera setup.
I'd like to bump up Dpcryer's question regarding the access of ISO attribute while in auto exposure mode.
As previously indicated, there is no way of knowing the ISO value while the exposure mode is set to 'auto' (the value is 0 in automatic mode, and the ISO getter yields 0 as well).
Would it be possible to read the camera parameters at any time, and no matter the camera mode ?
Moreover, what are the relation between the analog and digital gains and the ISO value ? In the documentation, it is written that when both gains equal 1, the ISO value is 100, but after some testing, I observe that analog_gain * digital_gain * 100 does not equals to the ISO value, and there are no correlation at all.
Thanks for considering this request,

The ISO value 0 simply means "auto". When you query the iso attribute you're simply querying the current ISO setting of the camera. If that's zero it simply means it's up to the camera to pick an appropriate ISO when it captures.
As to the correlation between ISO and the camera's gains - when camera's ISO is set to 100, the analog gain defaults to 1 (it may float higher though if the AGC algorithm, controlled by the exposure_mode property, determines that it needs to be higher). When camera's ISO is set to 200, the analog gain defaults to 2 (again, it can float around this as AGC adjusts things). What the gain limits are for each ISO, I don't know - you'd have to ask the firmware devs. Also, I don't expect the relationship is as simple as a linear multiplication given that the gains are both limited to a range of 1-8 overall.

Oh, the other point was: why do the gains not change when setting iso while exposure_mode is "off"? The answer is simply that exposure_mode "off" fixes the gains entirely - they won't budge at all (unless the camera is reset, e.g. by changing resolution / framerate). If you're looking for a way to control the gains manually there currently isn't one (not directly).
The best you can manage is to set exposure_mode to "auto" then fiddle with iso until the gains float to what you want (or close enough) and then set exposure_mode to "off" as fast as you can.

Thanks for the explanation and the work around. It at least kind of works for me.
But are there any plan to implement a manual control for iso and the analog/digital gains?
The ability to set custom gains (or at least setting the iso value to control the gains) would be a really nice feature!

Currently, the firmware provides no means to set the gains manually (thus picamera, which is a relatively thin layer on top of MMAL cannot provide a means to do so either). I've not heard any plans for manual control of analog/digital gains - but that doesn't mean much one way or another. You're best off asking about that on the camera forum where you're more likely to get a response from the firmware developers.
You can set the ISO value which influences the gains (as described above), though.


Numeric input

Begin to work on the numeric input
doc: https://blueprintjs.com/docs/#core/components/numeric-input
code: https://github.com/palantir/blueprint/blob/develop/packages/core/src/components/forms/numericInput.tsx

need some improvements and implementation of other component like ControlGroup and InputGroup

With #68 inputGroup and controlGroup is now implemented, let's go

@cecton Maybe already push this ?
The numericInput look like a NumericInput but props not working as expected and it's not numeric at all but i will to take a look to some other component for now

@cecton Maybe already push this ?
The numericInput look like a NumericInput but props not working as expected and it's not numeric at all but i will to take a look to some other component for now

Thanks for the review, i take a look now

Thanks for the review, i take a look now

Numeric Input look like an example for now, i try to give him a less redundant and basic render.
But for now, props works! just need to begin the journey of a more functionnal NumericInput

Numeric Input look like an example for now, i try to give him a less redundant and basic render.
But for now, props works! just need to begin the journey of a more functionnal NumericInput


OneClick - Work item from one click actions by Mohit Bagra is taking longer than expected to load.

OneClick - Work item from one click actions by Mohit Bagra is taking longer than expected to load.
Is it able to be fixed with new version?

I'm seeing this very frequently (90% of the time) now: "Work item form one click actions by WDG ES Work Management is taking longer than expected to load"

Hi,
I will be changing laptops soon.
Why I mention that is our Internal Service Desk is saying I'm having internet connection latency issues because I have an old and unsupported window version on my laptop.  I've been supplied with an update, but I have to transfer data, setup etc yet.
I don't know if my old windows version related to the issues you are seeing.  It might be.
Jessica Molina
Cognizant Healthcare (CHC)
T3 Operations | Phoenix, AZ | United States
M<PHONE_NUMBER> |<EMAIL_ADDRESS>@.***D5C7C4.ADC676C0]
This electronic message transmission is intended only for the person or the entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure, including personal health or other information which may be protected by federal or state law. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact the sender of the e-mail and destroy the original message and all copies.
From: swartanian @.***
Sent: Wednesday, March 24, 2021 11:49 AM
To: mohitbagra/vsts-extensions @.>
Cc: Subscribed @.>
Subject: Re: [mohitbagra/vsts-extensions] OneClick - Work item from one click actions by Mohit Bagra is taking longer than expected to load. (#62)
[External]
I'm seeing this very frequently (90% of the time) now: "Work item form one click actions by WDG ES Work Management is taking longer than expected to load"

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmohitbagra%2Fvsts-extensions%2Fissues%2F62%23issuecomment-806071242&data=04|01|jessica.molina%40cognizant.com|0fe98f7cd1db4c029fed08d8eef57b37|de08c40719b9427d9fe8edf254300ca7|0|0|637522085484371252|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=IgU28Qr7LriY5x8lEDBXcn9IM9xFqPP1JvVqxFUAns4%3D&reserved=0, or unsubscribehttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAODPKC3BJD6HXYFUN44VFPTTFIXZPANCNFSM4HYAYTLA&data=04|01|jessica.molina%40cognizant.com|0fe98f7cd1db4c029fed08d8eef57b37|de08c40719b9427d9fe8edf254300ca7|0|0|637522085484381248|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=3iVtzE9DO6R6nWJQEJ%2Fp9aqLGBQ%2FrZ8Nr2vndeQa%2F3Y%3D&reserved=0.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.


HTTP Error 403: Forbidden on Adult Swim (w/Comcast MSO)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
USA
Provide a description that is worded well enough to be understood
Trying to download some shows\ on Adult Swim. Was able to download five without needing to use Comcast MSO, but the next ones I try needed logins. Logged in with my Comcast account but got the HTT 403 Forbidden error. Shows play on Chrome, Firefox, Brave with no problem.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--ap-mso', 'Comcast_SSO', '--ap-username', 'PRIVATE', '--ap-password', 'PRIVATE', 'https://www.adultswim.com/videos/rick-and-morty/rickfending-your-mort']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [1a176d874] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.22631-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 4.4.1-essentials_build-www.gyan.dev (setts), ffprobe N-91181-gcba167934b
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.35.5, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1838 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[AdultSwim] Extracting URL: https://www.adultswim.com/videos/rick-and-morty/rickfending-your-mort
[AdultSwim] rickfending-your-mort: Downloading JSON metadata
[AdultSwim] 6da5cf250e9fc118d812e023c2b554573ba9211a: Downloading JSON metadata
[AdultSwim] 6da5cf250e9fc118d812e023c2b554573ba9211a: Downloading Provider Redirect Page
ERROR: [AdultSwim] Unable to download webpage: HTTP Error 403: Forbidden (caused by <HTTPError 403: Forbidden>)
  File "yt_dlp\extractor\common.py", line 741, in extract
  File "yt_dlp\extractor\adultswim.py", line 151, in _real_extract
  File "yt_dlp\extractor\turner.py", line 232, in _extract_ngtv_info
  File "yt_dlp\extractor\turner.py", line 37, in _add_akamai_spe_token
  File "yt_dlp\extractor\adobepass.py", line 1448, in _extract_mvpd_auth
  File "yt_dlp\extractor\adobepass.py", line 1366, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 961, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 910, in _request_webpage

  File "yt_dlp\extractor\common.py", line 897, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 4172, in urlopen
  File "yt_dlp\networking\common.py", line 117, in send
  File "yt_dlp\networking\_helper.py", line 208, in wrapper
  File "yt_dlp\networking\common.py", line 340, in send
  File "yt_dlp\networking\_requests.py", line 365, in _send
yt_dlp.networking.exceptions.HTTPError: HTTP Error 403: Forbidden

Duplicate of #10848


Progress Bar - Design Doc

Introduce design documentation for the Progress Bar.
Related issue: #24

Hi @mcarrano,
@srambach and I were reviewing PR https://github.com/patternfly/patternfly-next/pull/648, and had a few questions:

Is the descriptive text above the progress bar meant to be dynamic or static? We assumed we would support both, since our current PF3 examples support both (e.g. the example labeled with "Downloading: Product Repositories" most likely changes to state what's being downloaded, whereas the one labeled "CPU" always says "CPU"). For screen reader support, we can either provide a numeric value in the form of aria-valuenow, or specific text string that describes the current status in the form of aria-valuetext, but not both (unless we incorporate the numeric value with the string).* For now, we decided to have all but the last example show a static text description of the progress bar, and will include an example at the end that illustrates how to provide a text string that describes the current progress state. But let us know if you have any suggestions for these patterns (especially regarding example text strings to use 😄).
Is the expectation that we would always show percentage as a value?
There is one example near the end where the value is not included in the form of text, labeled "Progress Without Measure". Since the other examples provide the progress value in text as well as the bar, we aren't as concerned with the color contrast of the bar itself. But this last example isn't accessible for low vision users (e.g. if progress is perceived by comparing the width of the dark blue to the width of the light blue, but the light blue isn't visible, then they can't assess progress). My question for you here is whether this is a pattern you want to support? If it is, then I'd suggest we revise the visual design to address low vision accessibility, at least for this one case (@mceledonia, @kybaker).

*I was testing in JAWS, which will ignore aria-valuenow if aria-valuetext is present. Other screen readers might have different behaviors.

@rachael-phillips Would you be interested in taking on documentation for this issue (instead of Breadcrumbs) since we already have completed examples here: https://pf-next.netlify.com/components/Progress/examples/ ?
The biggest challenge is that there are a large number of different example configurations for the progress bar, but no guidance on what to use and when. It may be that we don't need all of these options. See comment from @jgiardino above. We can discuss.

Here are the visuals that we will need to support the use cases that are currently addressed in the documentation. Please reach out with any questions on this work!

A state that demonstrates a progress bar that tracks user progress by percentage. This example would demonstrate a user tracking their own progress through a tutorial or similar use case.

A state that demonstrates to the user a system's progress through downloading a file or application.

A state that demonstrates the progress through a series of steps (less than 10). This use case could also be as a user walks through a tutorial.

We will also need a state that represents a time remaining, such as "4 minutes remaining" instead of a percentage. My view is we could just replace this copy in state 1.

Hi! Let me know if this is the wrong place to write this question, and I will take it on over to Slack, but in the process of writing the documentation for progress bars, I've realized that we really do need an animation that demonstrates the difference between indeterminate and determinate progress bars. The documentation I've written covers the differences, but as you can see, only an animation can make this obvious to the user. Can we also provide animated examples for indeterminate and determinate? Here's what that animation looks like:

This is looking good @rachael-phillips I just had a couple of comments that I left in your Google Doc. The examples above look good. Were you thinking that these would be just integrated into the document as static graphics or built as examples in code? We may want to create a demo for this. @LHinson would be interested in your thoughts. Also, @mceledonia and @kybaker please take a look. The step-wise progress indicator is not in the current implementation, so we may need to create a new issue to add this as an enhancement.
As for your question about animations, I think we can include these if they are just animated GIFs like the one attached here. Agree that in some cases these are needed to reflect the design intent.

Hi Matt,
I think our conversation with Kyle this morning will clarify some of this.
I think the progress bar states I've provided need contextual visuals on
the design docs page and examples with code for the examples page. I would
actually narrow the examples we see in the PF-workspace right now and
reorganize the examples to align with the design docs, so that as the user
navigates between examples and design documentation that experience is
consistent. Let's speak more about this, and I'll update here when we are
feeling confident about an idea of what we want to do here.
Thanks!
Rachael
On Wed, Sep 26, 2018 at 3:56 PM mcarrano<EMAIL_ADDRESS>wrote:

This is looking good @rachael-phillips
https://github.com/rachael-phillips I just had a couple of comments
that I left in your Google Doc. The examples above look good. Were you
thinking that these would be just integrated into the document as static
graphics or built as examples in code? We may want to create a demo for
this. @LHinson https://github.com/LHinson would be interested in your
thoughts. Also, @mceledonia https://github.com/mceledonia and @kybaker
https://github.com/kybaker please take a look. The step-wise progress
indicator is not in the current implementation, so we may need to create a
new issue to add this as an enhancement.
As for your question about animations, I think we can include these if
they are just animated GIFs like the one attached here. Agree that in some
cases these are needed to reflect the design intent.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patternfly/patternfly-next/issues/580#issuecomment-424848695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmaPXnbQGbcRG_txh-1bvdAQFpqXT3sDks5ue9vegaJpZM4V3dDv
.

Completed.


klipper: 0.8.0 -> 0.9.1

Motivation for this change
Noticed a new release was made.
cc. @flokli
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

did anything change w.r.t. the funky way this is packaged? Is there an upstream issue about it?

did anything change w.r.t. the funky way this is packaged? Is there an upstream issue about it?

It didn't, it's still funky.
I'll open an issue upstream asking for a normal setup.py to see if we can make this less weird.

Result of nixpkgs-review pr 102143 run on x86_64-linux 1

1 package built:

klipper


[BUG] Brief Description of the Issue

Found a bug? Please fill out the sections below. 👍
Describe the bug
A clear and concise description of what the bug is.
Steps to Reproduce

when starting the project in vscode and running it locally it just open the git local and creash the project
just screens open for the 2 second and wiped out

Expected Behavior
A brief description of what you expected to happen.
I expected to open the file where I can write something and order it to do the task as others are doing.
Actual Behavior:
what actually happened.
mentioned above
Environment

OS: win 10
Model Used (e.g., GPT-4v, Gemini Pro Vision):
Framework Version (optional):

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Error at Thu, Jan 25, 2024  7:37:06 PM: Error running python3 -m venv venv.
Error at Thu, Jan 25, 2024  7:37:42 PM: Error running python3 -m venv venv.
Error at Thu, Jan 25, 2024  7:40:52 PM: Error running python3 -m venv venv.


Mark most functions as unsafe

Because we follow Vulkan closely for the HAL API, we don't have many safety guarantees for most of the API usage. A few users have asked to have the explicit unsafe annotation to make it more obvious that no guarantees are provided here.

Thank you for filing the issue! It did raise up quite a few times, and it's super important to discuss in detail.
The initial approach of not having unsafe was taken for the following reasons:

gfx-rs wanted to be safe, but actually, it just steered too low for that
there is a precedent of gleam wrapping around a graphics API (a thin wrapper) and doesn't mark the functions as unsafe
while the driver can technically collapse the universe, Rust code itself doesn't do any exposed unsafety. In that sense, why is, say, division operator on CPU is not unsafe? There is a line to draw between what we consider safe and what the driver/firmware/hardware considers safe.

FWIW, gleam lying about unsafety has been criticized by ~the rust safety brigade~ some people in the past.
I believe the question is: can you pick parameters that cause safety hazards per specification (as in not relying on a driver bug)? if so, something should be unsafe.

there is a precedent of gleam wrapping around a graphics API (a thin wrapper) and doesn't mark the functions as unsafe

Many of those methods should actually have been marked unsafe, I'm fixing them when I stumble upon such methods.

I believe the question is: can you pick parameters that cause safety hazards per specification (as in not relying on a driver bug)? if so, something should be unsafe.

It's a bit more complicated than that, for example new unpack parameters could be introduced in such a way that tweaking them makes your safe glTexImage2D wrapper unsound, and we can't predict the future.

One approach that may work for gfx-hal is to use the same strategy as the memmap crate and mark one of the early initialization functions unsafe (say the function to create an Instance) and then leave everything else as safe. This way users have to acknowledge that misuse could technically result in unsafety without severely degrading ergonomics across the entire crate.

@fintelia this is an interesting idea, but I'm not sure if it's valid. The point of unsafe in general is that you can build safe abstractions on top. If you use it in a way of saying: "here you opt into unsafety, so don't expect any further work to be safe", then this would be against the spirit of the word.
summoning @Gankro as our unsafety expert :)

There's definitely some precedent for rules-lawyering unsafe boundaries. The key invariant that the stdlib team has generally focused on is: if you don't write unsafe anywhere in your application, then we can guarantee memory safety.
This gives us a fair amount of leeway to only mark key operations as unsafe, and mark many others as safe, with the understanding that you need to use one of those key unsafe operations to trigger unsafety.
For instance casting pointers to different types, or making them from integers is considered safe, because all the other operations like offset and read are marked as unsafe, and clearly document that they assume that the pointer is well-aligned, valid to access, and so on.
With that said, I can't think of an example where we made this kind of "blood pact" design, where you sign away your rights by calling unsafe once upfront, and then never need to state that you understand things are unsafe again -- at least for public APIs, we lie about unsafety internally in the stdlib all the time since it doesn't matter.
I think the reason we don't tend to do that is it makes it easy for someone to "sign the pact for you" -- imagine a version of the *const API where we flip it on its head: creating pointers in unsafe, but every other operation is marked as safe. In this way we could technically still make the "you wrote unsafe so everything in unsafe" argument. However, any API that claims to be safe but hands you a raw pointer is messing up the whole concept of unsafe APIs, because it has signed the pact on your behalf. Not dissimilar to writing fn totally_safe_transmute<T, U>(t: T) -> U { unsafe { transmute(t) }, but much less obvious to notice.

As a rule of thumb I think that any function that can be used to violate Rust safety guarantees must be marked unsafe. E.g. if you can provide a set of valid usage rules for the function - mark function unsafe and specify rules in doc comment.
This rule of thumb won't work with unsafe init and safe everything because you'll fail to write exhaustive valid usage rules for such init function.

This crate provides low level access to an extremely powerful, programmable co-processor with direct DMA access to main memory. It relies on underlying APIs which deliberately leave certain misuses undefined because detecting them would incur too large of a runtime cost. I agree that the ideal option would be to identify a small subset of the gfx-hal functions that are unsafe and mark everything else safe, but I'm not convinced that there is a small subset that would qualify. As I see it there are a couple options:

Just lie about safety and don't mark anything unsafe.
Mark some init function unsafe (satisfying any rules lawyers, but in practice the same as 1)
Mark only some subset of functions (but hard to figure out which, might end up being almost everything)
Mark everything unsafe (bad ergonomics but minimal effort)

In cases 2-4 the "set of valid usage rules" will probably just be a pointer to the vulkan spec and a disclaimer not to do anything that would cause problems, perhaps with a specific warnings about avoiding use after frees, etc.

@kvark I can't see how this can solve the problem.
By wrapping unsafe function into unsafe block in safe function implementation you guarantee that no changes in public API usage will cause UB or something.
If changes in command recording process can lead to invalid usage of backend then this unsafe block does not provide required guarantees. Simple example would be destroying resource after recording.

@kvark I'm not sure how you will assert valid usage of vkCmdDraw.

This one looks similar to glDrawElementsInstanced and friends, and that is safely exposed to the entire Web in WebGL, either by extensive checks or by relying on the KHR_robust_access extension.
One could make the crate panic if the robustBufferAccess feature is missing or if the unsafe omit_robust_buffer_access method is not called.
Disclaimer: I know nothing about Vulkan.

@nox if we are willing to do extensive checks sacrificing performance like OpenGL does - we would use OpenGL 😄

How is that related? Whichever group will expose Vulkan to the Web will have to implement those extensive checks too. It's not about the tech but about where it's exposed. The Web runs third-party code so the API to access OpenGL needed safety checks, that's all.
My solution didn't say anything about implementing extensive checks in this crate.

@nox so does CommandBuffer::draw method should be safe or unsafe?

Whichever group will expose Vulkan to the Web

This is not the only use case for the crate.

If there is something that leads to out-of-bounds buffer access, yes, that thing should definitely be unsafe. My point was that the robustBufferAccess feature seems to make those go away, so the crate could panic if it's missing, and provide an unsafe method to say "yeah even if that feature is missing, I swear with my blood that I know what I'm doing". Everything else about the Web was to explain where I'm coming from.

Take note that robust buffer access doesn't guard you against other usage violation.

Don't edit your comments, I almost missed that. I am aware this doesn't guard against other usage violations, this kind of safety study is on a per-basis thing.

Also robustBufferAccess takes buffer range from descriptor or buffer view which can be set to wrong value.

Don't edit your comments

My worst habit.

My point is that command buffer recording methods has complex rules for valid usage. The idea to mark them all safe seems weird to me.

I think of it as Draw() being an analogy of taking a pointer from a reference (no real unsafe work done yet), and Submit() being the pointer dereference.

On Nov 2, 2018, at 07:18, Zakarum<EMAIL_ADDRESS>wrote:
My point is that command buffer recording methods has complex rules for valid usage. The idea to mark them all safe seems weird to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@kvark can you be sure aabout that?

I expect vkCmdDraw to prepare draw command data for gpu, read from pipeline, descriptors, framebuffer and renderpass objects. And I would expect no checks during those reads.

I expect vkCmdDraw to prepare draw command data for gpu, read from pipeline, descriptors, framebuffer and renderpass objects. And I would expect no checks during those reads.

I don't expect so, or the specification would have to mention that these resources (at least the mutable ones) be externally synchronized in the list at section 2.6 of this page: https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html.

@nical Those resources are immutable. You don't need to externally synchronize them if there is no way to mutate them.

It may be don't read them until submission. But it would make sense to do CPU side job since recording can be done in parallel. Deferring computations until submission will reduce CPU utilization.

@omni-viral I checked the AMD's Vulkan implementation, and this indeed appears to be the case: https://github.com/mesa3d/mesa/blob/677b496b6bd07cbe05dd429344ba525619cdd08c/src/amd/vulkan/radv_cmd_buffer.c#L1843
The driver checks the pipeline, active descriptor sets, vertex buffers, and more - all on the draw().

Perhaps we should make all the draws, dispatches, and copies unsafe then. It's still a big win if all the state setting is "safe" prior to the draws.

@kvark I'd stick with Vulkan valid usage rules. Without making assumptions about how spec is implemented. If there is enough data to assert valid usage (without compromising speed) then do that and mark function safe.

Unfortunately there aren't many you can check that easily.


log2timeline-sift command missing

When issuing "log2timeline-sift" command, it returns a "command not found" error.
This is on the default install (unzip SIFT 3.0 to Virtual Machine directory, open Virtual machine, start it up, issue command in terminal).

Thanks for this guys! I've been meaning to write my feedback for a while now, but yes I concur with "fligi7" in using log2timeline.py for the processing of dd'ed images.

@fligi7 I'll make note to update the documentation.

Resolved https://github.com/sans-dfir/sift-docs/commit/f6581ecf98dba1e61014e9e054a8520823b0c030


minutes-grid-increment issue with version 4.0.1

When select the minutes, will show "Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'value')"
if delete minutes-grid-increment="30", it's work.
                  <datepicker
                    v-model="open_time"
                    :clearable="false"
                    timePicker
                    minutes-grid-increment="30"
                    auto-apply
                    @update:modelValue="update_time()"
                    textInput
                  />

it's still not work after i follow your solution, will be fine in next version? @Jasenkoo

Hello when is the next merge planned?

Sometime during the next week


Review use of etcd as a message queue

User requirement
As a Dotmesh user, I don't want etcd being used as a message queue inside Dotmesh, so that I can have fewer problems with it getting overloaded.
Key acceptance criteria

[ ] Everything that works now should continue to work, just as well.
[ ] Dotmesh should still still work when a node is down and comes back - queued activities that were waiting for the node to return should seamlessly resume when the node comes back, within a reasonable timeframe.
[ ] It should continue to work when there is a lot of activity in the system (defined as lots of operations that cause requests to be sent to state machines); throughput should reach a reasonable peak as the applied load increases and not drop much as applied load continues to rise beyond that point.
[ ] It should not require any additional steps for the user during installation (eg, any third-party message queue tools we decide to use should be installed seamlessly by dm cluster init or the Dotmesh Operator)

See Also

#579: File uploads using statemachine requests particularly exacerbate the weaknesses of the current etcd message queue; whether this issue provides a good enough message queue that we can send bulk file uploads through it or if a different mechanism is still needed is an open question (but note that file uploads may be much larger than RAM in future).

I think this is duplicated/superceded by #602


remove links from navigation but api reference

I don't think the changes done here are consistent with our navigation in other modules' documentation
https://github.com/micronaut-projects/micronaut-gradle-plugin/pull/295

Example of other modules:

I don't have a strong opinion on this. We can remove the links, or we can switch to the template used by the other projects for documentation.

At least remove the links. What we currently have does not work at all.


Fix #396: Add script to apply style

Describe the contribution
Fixes #396, adds script to apply style
Testing performed

Ran against ci_lab repo, confirmed acceptable style

Expected behavior changes
No functional changes
System(s) tested on:

Hardware: cFS Dev Server
OS: Ubuntu 16.04
Versions: master bundle

Additional context
None
Contributor Info
Jacob Hageman - NASA/GSFC

CCB 20191106 - Discussed other more IDE friendly options, clang-format will be evaluated.

Not using indent, plan to use clang-format (apply and enforce will be new issues/pull requests).


Add new MISRA query suites and deprecate ambiguously named suites

Description
This PR makes some changes to the query suites available for MISRA C and MISRA C++:

Renamed the default suites to misra-cpp-default.qls and misra-c-default.qls to avoid confusion between them, and deprecated the old suites.
Added new query suites to enable running only the mandatory, required or advisory level queries.
Added a new query suite for MISRA C which enables users to run the current set of queries for MISRA C (equating to MISRA C 2012, 3rd Edition, First Revision + Amendment 2). This gives users the option to retain the current set of queries as we added new queries to the default suite for MISRA C 2023.

To be able to write a query suite for the latter, I have added a set of new tags to the MISRA C queries to determine when those rules were added to the standard.
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[ ] Query files (.ql, .qll, .qls or unit tests)
[x] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[x] No rules added
[ ] Queries have been added for the following rules:

rule number here

[ ] Queries have been modified for the following rules:

rule number here

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[x] Yes
[ ] No

🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.

[ ] Confirmed

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Would it be a valuable follow-up to check tags against a dictionary in some of our CI package json verification scripts?

We validate the tags against the rule schema - that avoids the typo/mis-spelling issues, because the tags can only be from a specified list.

We could also add a check that misra c contains a relevant revision tag, and that the misra revision tags don't appear in c cert rules.

Great idea, I've updated the validation script to do this.


PAGE NUMBER FORMAT

Is there any way we can show page number like : 1/2 2/2 3/3 where current page / Total page number
Please help.

Any update ??

?? @jdugan


Chrome extension's "Get CSS" always returns text 'undefined' below (on any html element)

OS X 10.10.5, Chrome 45.0.2454.101 (64-bit), CSSSteal 1.0.1

Thanks for reporting @rubyconvict I'll try reproducing it probably tonight.

Hello @rubyconvict,
can you please open chrom://extensions and click on the Update extensions button. You should get 1.0.2 version and the problem should be solved. Let me know.

Fixed.


core: use external modules

I think it's about time we incorporate the spirit of npm in our library; that is, small modules, preferring re-use over re-creation.
Todos

[ ] Merge #721 (so @mziccard doesn't hate us)

New modules used:

arrify - replaces util.arrayize
is - replaces util.is
methmeth - replaces util.exec
prop-assign - replaces util.propAssign
propprop - replaces util.prop
string-format-obj - replaces util.format

Sorry for the enormous PR, @callmehiphop.

Looks good :dancer:


feature request : color line according to status and severity combination

in web UI, will be a great setting to color a line according to (status + severity) combination

Interesting suggestion. There would potentially be 54 different colour combinations though as there a 9 severity levels and 6 different statuses.

Yes, alarm management in scada software are often colored according this combination ! or a color and blink combination

Added to the backlog. Probably for the next major version of the web UI (which might be some time away yet).


OVH S3 HighPerformanceBucket

How to create a standard s3 bucket is shown in /tf-at-ovhcloud)/s3_bucket_only/
But how do i create a HighPerformanceBucket? What Parameter must be set to change the storage type?

Hello @markbonfert
You will need to update the s3_endpoint to the one for the high performance offer.
This documentation page  provides the complete and up to date endpoint list.
I will add this to the Readme.


[ios_platform_images] Platform tests fail in CI with Xcode 15 and iOS 17

xcode analyze step fails with the following error:
While building module 'ios_platform_images' imported from /Volumes/Work/s/w/ir/x/w/packages/packages/ios_platform_images/example/ios/Runner/GeneratedPluginRegistrant.m:16:
In file included from <module-includes>:1:
/Users/chrome-bot/Library/Developer/Xcode/DerivedData/Runner-ebfdwekzmldmdefbogamgoyvamxm/Build/Products/Debug-iphonesimulator/ios_platform_images/ios_platform_images.framework/Headers/ios_platform_images-umbrella.h:20:1: error: umbrella header for module 'ios_platform_images' does not include header 'ios_platform_images-Swift.h' [-Werror,-Wincomplete-umbrella]
1 error generated.
/Volumes/Work/s/w/ir/x/w/packages/packages/ios_platform_images/example/ios/Runner/GeneratedPluginRegistrant.m:16:9: fatal error: could not build module 'ios_platform_images'
#import <ios_platform_images/IosPlatformImagesPlugin.h>
 ~~~~~~~^
2 errors generated.

https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64 ios_platform_tests_shard_3 master/7590/overview
https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64 ios_platform_tests_shard_3 master/7567/overview
I also tried temporarily skipping the xcode analyze step, but the native test step also fails
While building module 'ios_platform_images' imported from /Volumes/Work/s/w/ir/x/w/packages/packages/ios_platform_images/example/ios/Runner/GeneratedPluginRegistrant.m:16:
In file included from <module-includes>:1:
/Users/chrome-bot/Library/Developer/Xcode/DerivedData/Runner-ebfdwekzmldmdefbogamgoyvamxm/Build/Products/Debug-iphonesimulator/ios_platform_images/ios_platform_images.framework/Headers/ios_platform_images-umbrella.h:20:1: error: umbrella header for module 'ios_platform_images' does not include header 'ios_platform_images-Swift.h' [-Werror,-Wincomplete-umbrella]
1 error generated.
/Volumes/Work/s/w/ir/x/w/packages/packages/ios_platform_images/example/ios/Runner/GeneratedPluginRegistrant.m:16:9: fatal error: could not build module 'ios_platform_images'
#import <ios_platform_images/IosPlatformImagesPlugin.h>
 ~~~~~~~^
2 errors generated.

...

Umbrella header for module 'ios_platform_images' does not include header 'ios_platform_images-Swift.h'
	Could not build module 'ios_platform_images'
	Testing cancelled because the build failed.

https://ci.chromium.org/ui/p/flutter/builders/try/Mac_arm64 ios_platform_tests_shard_3 master/7593/overview
Strangely the build examples step passes fine.
Also, I was unable to recreate this locally. Both the analyze and test work for me locally.
Also, doesn't seem to happen every time: https://luci-milo.appspot.com/ui/p/flutter/builders/try/Mac_arm64 ios_platform_tests_shard_3 master/7545/overview
Not sure if this is a flake or legit issue

I can't repro locally either. I was wondering if it was due to cached build output from the PR that did the Swift migration, where some earlier run might have left bridging header that shouldn't be there, but I've verified that the generated header is present locally when I build. There's just no error about it not being included in the umbrella.
It looks like the umbrella is generated by Cocoapods in this scenario, so it could be a bug there, but I don't think the generated -Swift.h bridging header is supposed to be in the umbrella based on what I can find (which isn't anything official so far).

Downgrading to P2 for now since we aren't able to repro. If it happens again in CI tests we can revisit.

I haven't been able to recreate this since. Closing.