Publish to the PowerShell Gallery

I use this module every day and when I setup a new machine I have to register the AppVeyor nuget feed to get the latest bits.

Will do

This can be closed.  PowerShell guard is in the gallery.
https://www.powershellgallery.com/packages/PowerShellGuard/

But the latest on the Gallery is 0.6.1 while the repo has 0.8.0.

Good point.  The latest is greatest.

@ngetchell and @jpvantuyl  I pulshed 0.8.0 to the Gallery last week.  Better CI/CD coming soon.


Use googleapis/rpc status protos

Migrates internal status message for gRPC to googleapis/rpc. The googleapis have been refactored into a smaller module making this a much lighter dep!

Oh, I missed that. I'll close, makes sense to wait for LTS.


fix: cmp colors

Currently, the cmp colors are not as they should be. In dracula/vim  you can see the colors are completely different.
For example, the text in the cmp is pink which should be white. Also, the colors are not the same as in the vscode too,
Here I wrote a basic color change that should be similar to other editors.
 CmpItemKindSnippet ='fg'
 CmpItemKindText = 'fg'
 CmpItemAbbrDeprecated = 'error'
 CmpItemKindVariable = 'purple - i'
 CmpItemKindFunction = 'link:@function'
 CmpItemKindMethod = 'link:@method'
 CmpItemKindConstructor = 'cyan'
 CmpItemKindClass = 'cyan'
 CmpItemKindEnum = 'pink'
 CmpItemKindEnumMember = 'purple'
 CmpItemKindInterface = 'link:@type'
 CmpItemKindStruct = 'link:@storageclass'

I did not write everything, needs rechecking with vscode and dracula/vim. If you want and are the same opinion I can create a PR, or you can check it.
The most important one,
Text -> fg
deprecated -> error
snippet -> fg.
The text is pink which makes it important but is not, and should not attract our eyes to read it first.
Thanks in advance

Thank you for raising this issue. I believe that the colors used for the kind icons should match the code. While Dracula/Vim and VS Code use different colors, my implementation of Dracula.nvim may not use the same colors as either of them.
here an example:

I do not know what this example has to do with CMP

Thank you for raising this issue. I believe that the colors used for the kind icons should match the code. While Dracula/Vim and VS Code use different colors, my implementation of Dracula.nvim may not use the same colors as either of them.
here an example:

I do not understand what does the example you gave has to do with what I am saying.
You are showing the colors inside enum and lsp-saga, coding colors.
I am talking about CMP (completion engine) :

As you can see in the image above.

The example I showed earlier was from Lspsaga. What both Lspsaga and cmp have in common is that they both use lspkind icons. If you look closely at the example, you'll see that the Direction enum has the same color as the icons used in lspsaga. This is the same color that cmp uses.
Here are the code snippets for cmp and lspsaga, respectively:
cmp
hl(0, "CmpItemKindEnum", { link = '@type' })
hl(0, "CmpItemKindEnumMember", { link = '@constant' })

lspsaga
hl(0, "SagaWinbarEnum", { link = '@type' })
hl(0, "SagaWinbarEnumMember", { link = '@constant' })

By the way, I forgot to mention earlier that I actually updated the Dracula.nvim colorscheme based on the issue you reported. I double-checked and revised the colors for lspsaga, navic, and cmpkind to make sure everything is in order.
commit


New dashboard in Singularity + other UI improvements

@kwm4385 , this is the WIP PR we can build upon for creating user and group based views within Singularity. I have created a separate dropwizard resource with new pojos that will aggregate all data the UI needs for certain pages in a single call. We may need to do some extra bits around things like history paging and such, but we can at least get the basic details of active elements all in a single call, with some extra details like instance health included.
My goal with this would be to replace the current dashboard page with something smarter, generally eliminating the need for the requests page, as well as adding some needed details like instance health in the task detail page.
We should also try to eliminate some extraneous calls we tend to make on a number of pages like:

fetching /requests on every page
fetching all request groups on every page
fetching the user occasionally multiple times per page

Feel free to comment on anything you might specifically want the backend to serve up all together. I'll add more detail here as I flush things out

On a good suggestion from @baconmania , going to not use the specific endpoints, but instead refactor the current requests/etc ones a bit to better fit the needs of the ui (behind filters/params/etc)

@kwm4385 I put together a quick 15-minute version of a new dashboard, mostly so that the logic is all written out for you to see the new data the backend is providing for you (and because I got angry at auth and wanted to take a break from it...).
Ordering by default is based on requests that have most recently had something interesting happen, and the list of requests is filtered (by the backend) to ones that are relevant to the user.

Tasks expands/collapses when clicked so we can show more/less data without cluttering things

Some updates to the new UI stuff:
Dashboard has slimmed down a bit, and non-long-running tasks will now include a recently started/finished task as recent activity:

With tasks expanded...

Icons replace text for request types and statuses to save space:

Don't show full task ID on the request detail page to save space:

Some thoughts on the current iteration:

Do people really need to see the task table on this page? If not, linking Tasks - 1 Healthy etc. to the request page might be enough.
Can we use the same icons as Orion for request types for more consistency? They can be found in OrionUI/app/images/icons/.
We probably want some type of title and subheader on the page so people know what they're looking at.
Consider moving the Recent activity column first (after the star) if that's the most important, unique information in this view.
Shortened task ids everywhere is 💯
What's the reasoning behind the external link icon next to the instance id? Typically this is used to signify the link will open in a new tab and/or leave the current app.

Just one final thought here

Should we have icons for Pending and Cleaning as well?
cc @ssalinas

Yeah, I can add two more. They are actually separate concepts, not separate states on the backend which is why i didn't at first (i.e. you'll never see a pending/cleaning in the same list as active/paused/cooldown)

Extra icons added now @kwm4385

I think this is in a good state to move forward to stable. We'll keep an ear to the ground for user feedback and make further tweaks based on that. 🚢


Add support for missing references (w/ warnings)

Description
Coming from LaTeX, you could compile a document even if a reference is not defined. This would trigger a warning and a "??" would be printed on the resulting file.
Currently, Typst just errs and exits the whole compiler process (e.g. if using typst watch).
Use Case
A similar functionality where the error is ignored and a warning is emitted instead would help creative flow while writing so that one does not have to immediately go back to a missing reference and try to address it.

See https://github.com/typst/typst/issues/1322

I would love for the functionality of #1276 to be included in the base compiler, as this should not be considered as a critical compiler failure.

If we can come up with a good design, I'm open to it.

Maybe we can add a cli argument (like --allow-missing-ref, or something else) to toggle the compile/watch behavior:

normal (current) behavior: deny missing ref
--allow-missing-ref behavior: warn on missing ref, and print ? (or something else, or something configurable by cli args) in the result

I think instead of having a specific flags just for refs we should instead think about how to implement a more generalized system for enabling/disabling warnings, then this could be extended to this specific use case as well.

Yes! You want to be able to just put the references in as you're writing and add the actual reference targets at the end. An --ignore-refs flag or something would be ideal.

Thank you for your solution. As I tend to overlook such messages, I added some additional code
#let MissingRef(body, small_text: 5pt) = {
      let body = if body == [] {
        [Missing Ref: XXX]
      } else {
        body
      }
      set text(fill: white, size: small_text, weight: "bold")
      text()[~~]
      box(
        fill: rgb("#e046d3"),
        outset: 4pt,
        radius: 3pt,
        stroke: luma(1),
        [#body #place()[
          #set text(size: 0pt)
          #figure(kind: "MissingRef", supplement: "", caption: body, []),
        ]])
      text()[~~]
}

With the #show rule
#show ref: it => {
  if query(it.target).len() > 0 {
    it
  } else {
    MissingRef[Ref Missing #str(it.target)]

  }
}

With this set, I can create a new outline only displayed when there are some missing refs
#context {
  let elems = query(
    selector(figure.where(kind: "MissingRef")),
   )
   if elems.len() > 0 [
      #pagebreak()
      //#set text(fill: rgb("#D70F37"), size: 30pt, weight: "bold")
      #text(fill: rgb("#D70F37"), size: 30pt, weight: "bold")[Missing Refs]
      #linebreak()
      //#set text(fill: rgb("#D70F37"), size: 12pt)
      #text(fill: rgb("#D70F37"), size: 12pt)[
        #outline(
          title: [],
          target: figure.where(kind: "MissingRef")
          )
      ]
      #pagebreak()
 ]
}

This is even cooler as compiler warnings, as I tend to ignore them and with this outline, I get informed within the document directly

To be honest, I'm wondering if a compiler flag would be the best solution. I think a standard (built in) package you could import that would do this for you might be better.

I think the best solution is to just downgrade it to a warning.

I would also be in favor of warnings for missing refs. Developing and debugging is easier when you can remove large parts of the document, and now everything is very strongly connected.

#show ref: it => {
  if query(it.target).len() > 0 {
    it
  } else {
    it.target
  }
}

This is a great help, but unfortunately does not seem to work for citations which return () when queried. I've opened a separate issue. If someone has a workaround there, let me know.

At this point, I think the best solution is to just downgrade it to a warning.

Is this the line?
https://github.com/typst/typst/blob/c4dd6fa06227b8c4a04cf488f371f52d5379ef9b/crates/typst/src/introspection/introspector.rs#L246
echo '@a' | typst c -f pdf - /dev/null

At this point, I think the best solution is to just downgrade it to a warning.

I think this is a good use case for deny-by-default warnings - a simple allow or warn annotation would solve the problem. I believe erroring is a preferred behavior over replacing the reference with some ad-hoc thing (or nothing) together with a warning, which feels off (one should at least be able to pick what appears for missing references; also, the compiler should indeed be loud about this problem by default). But having a warning that one can manually downgrade seems right to me.

I think deny-by-default would make things inconvenient again. The whole thing is that people want to just keep writing before filling in their references. Having to manually allow it would probably be a hassle.

I don't think I would mind as long as the compiler tells me how to switch it to a warning in the error message

The whole thing is that people want to just keep writing before filling in their references.

I'd argue that the compiler is right to be loud about this by default: the main use case is when the references do, in fact, exist, to the point that we have autocomplete for existing references, and I'd certainly not want to accidentally share a document with missing references at some spots (can be easy to miss when the document is large) - warnings are good, but an error is even better and ensures you won't miss it. I feel like blocking compilation unless you're certain this is what you want is a good default, and you only have to change it once per module. Warning by default feels like a step backwards on reliability, imo.

I don't think I would mind as long as the compiler tells me how to switch it to a warning in the error message

Sounds like a good idea to me!

I'd argue that warning by default is better for usability. Otherwise you'll have to add preamble to every single subfile (chapters e.g.) to compile them stand-alone.

Otherwise you'll have to add preamble to every single subfile (chapters e.g.) to compile them stand-alone.

I'm fine with that tradeoff. Using subfiles standalone is already problematic for any kind of introspection, not just references, so I'm not sure this would bring enough of a gain compared to having a more general solution to provide more context to subfiles.
Besides, we could add compiler flags that permit controlling warning levels externally regardless of the file being compiled, or even settings in a future typst.toml.

Re: #4974
Cc @Enivex

I have the exact opposite impression. The majority would rather have references be a warning, without blocking compilation.

I think arguing in terms of amount of users isn't productive in this discussion (and was a mistake in my part) because there is actually overlap between the groups "users who would like missing references to not block compilation" and "users who would like missing references to block compilation". Rather, the same user may want both at different moments.
Let's consider the two "purposes" for triggering a Typst compilation below (which would influence what would block it or not), in a usual workflow for writing a document:

Preview: when you just want to preview your document, missing references are usually OK, since you're just looking to have an idea of how it looks.

Although a missing reference might still change how the document looks due to show rules on #ref, so not all documents would produce accurate preview compilations if missing references are allowed, so it should still be toggleable somehow (see one potential proposal below).

Export: when you want to share your document to others (e.g. turn in your thesis, present your slides and so on), you certainly do not want to allow missing references for obvious reasons. For example, you wouldn't want a reviewer to ask what is this red @typstlaur text. A warning would help in this case, but it is often the case that people export with warnings anyway because they're satisfied with how everything looks and don't want to spend more precious time satisfying the Typst compiler (and thus may miss this warning which is clearly different from something like redundant **, which can be safely ignored).

Therefore, I'd argue that

Being stricter by default is better, as I'd rather have the compiler, by default, reject otherwise valid preview compilations than accept one invalid export compilation. Typst is here to ensure quality in your documents, and detecting this kind of problem (at the right time) is part of what makes the Typst compiler so useful and helpful.
But it should still be possible to make the compiler more flexible. One potential proposal here is to differentiate preview and export compilations somehow. This could be implemented by marking some errors as dismissible for preview compilations (/ "deny-by-default warnings"), and:

The web app and LSPs would compile in "preview mode" / downgrade those warnings by default when displaying the document preview, allowing the user to still preview their documents, whereas clicking the export button would either fail or at least prompt the user for confirmation, listing problems which should be given attention;
The Typst CLI is more often than not used for final exports, so it should fail compilation by default, but could simulate the same behavior through a --preview flag which downgrades dismissible errors.

Hopefully this clarifies my position better; I think this isn't a matter of catering to a certain group users or another, but rather (since those groups do have an intersection) appealing to different needs they may have in their workflow with Typst.

Martin and I had thoughts in a similar direction. I don't like --allow-missing-refs at all, but a generic preview/draft compile that demotes certain errors to warnings and is enabled by default for previews sounds like a good idea.

Yes! You want to be able to just put the references in as you're writing and add the actual reference targets at the end. An --ignore-refs flag or something would be ideal. The current behavior encourages putting in a bunch of dummy referands just to get the compiler off your back, which is worse since you might forget them.
This at the beginning of the document makes a good workaround:
#show ref: it => {
  it.target
}

However, this doesn't solve the problem because now all refs will be replaced by a placeholder, even ones that work, so you can't gradually fix broken refs and have them fill in. This will do both:
#show ref: it => {
  if query(it.target).len() > 0 {
    it
  } else {
    it.target
  }
}

This did not work for me. Still hitting compiler errors


Chrome 128 pattern failure

[*] Targeting Chrome
[*] Targeting process: chrome.exe on PID: 14226
[-] Failed to find the first pattern!

Version from chrome://version:
128.0.6613.85 (Official Build) (64-bit) (cohort: Stable)

Hi, I have released a new version that should fix the issue.


Use a function helper for checking if something is an instance of a class, when the class has a Symbol.hasInstance static method.

fixes #130

@corruptedzulu It may be a while before we drop IE11, but yep, at some point we'd put instanceof back in. The project is currently using Buble which doesn't transpile instanceof, which is why I did it by hand only for classes that have Symbol.hasInstance static methods. However, if we add an additional Babel step (so we would be using both Buble and Babel) then we can remove this manual work, leave instanceof as is, and Buble would transpile instanceof into something similar to what I've written by hand (because Babel does support that feature via transpilation).

@corruptedzulu One thing we could do is use the babel-preset-env which is useful for specifying build targets (f.e. build for IE11, build for Chrome, etc) and each build only has features transpiled if the target needs those features transpiled.
Then what we could do is something similar to polyfill.io, which exposes a single endpoint for retriving a JavaScript file, and based on the detected browser it will send back a file with specific features in it (in this case, specific polyfills that the browser needs).


Failed to login to Daikin Cloud error

I tried installing the plugin and configuring with my userid and pw that I use to log in to the Daikin Cloud NA iPhone app but am getting the follow error in the Homebridge log when the Bridge tries to start up:
[3/2/2023, 1:56:04 PM] [homebridge-daikin-cloud] Failed to get cloud devices from Daikin Cloud: Failed to login to Daikin Cloud with<EMAIL_ADDRESS>Login failed: invalid loginID or password
[3/2/2023, 1:56:04 PM] [homebridge-daikin-cloud] ---------- End Daikin info for debugging reasons ---------------

Check your credentials. Maybe there's a typo.

I'm going to close this one. It seems to be a problem with the credentials rather then with the plugin. If you would have new information let me know and then we can reopen this.


The PaddleOCR Invoice Recognition Docker Image

Hi,
Do you provide the url for the docker image invoice recognition, since in your code, you just hit to the https://paddleocr.i247365.net/predict/ocr_system ?
Thanks
Yusak
Indonesia

hello,
I build a docker image for paddleocr api
https://github.com/neozhu/PaddleOCRFastAPI


added support to extend curl options

This PR add a curlOptions option to merge custom parameters to curl, and add the ability to set a proxy and/or a timeout.
Should be merged after:
https://github.com/sendgrid/php-http-client/pull/11

This is awesome @ninsuo, thanks!
Can you please sign our CLA so we can get this merged? https://github.com/sendgrid/sendgrid-php/blob/master/CONTRIBUTING.md#cla
With Best Regards,
Elmer

Hi,
How to sign it? I don't see a CONTRIBUTORS file?
Thanks

Hi @ninsuo,
You can find the form here: https://drive.google.com/a/sendgrid.com/file/d/0B0PlcM9qA91LN2VEUTJWU2RIVXc/view
Please email the signed version to<EMAIL_ADDRESS>Thanks!

Ok, I'm abroad right now but will see that next week.
A

Thank you @ninsuo!

Any update on this one?
Thanks

Hi @ninsuo,
I am just awaiting the requested changes:

Please change the version back to version 5.1.0
Please update the dependency to php-http-client to 3.5

Thanks!

Hi mate,
I done those changes more than 20 days ago in 26880af
Please let me know if you need something else
A

Hello @thinkingserious
Requested changes are made since 4 weeks now, it becomes urgent to use this feature in our side.
Can you please have a look?
Thanks,
Alain

Hi @ninsuo,
As of right now, this PR is at #7 in our backlog. Apologies for the delay and thanks for the follow up.

Hello,
Is it possible to get this merged?
Travis fails because this should be merged after sendgrid/php-http-client#11
But everything is perfectly fine and I should release my project tomorrow.
I'll need to use my fork otherwise, not a good practice.

Hi @ninsuo,
Unfortunately, this one has not bubbled to the top of our backlog just yet, but it is scheduled for a review and merge.
Looking briefly now, I see there are a couple tests passing. I think you might need to update to v5.1.2.
Thanks for checking in and I'm hoping to get this merged soon.

Yes you're right, it needed a rebase, that's now ok.

Awesome, thanks for the quick update!

No feedback after almost 3 months, we'll be using our branch as the main one in production.
Thanks anyway

@ninsuo,
My apologies :(
I'm glad you got it working in production though.
This is still in our backlog to merge and deploy. Also, for your contribution, we would like to send some swag your way. Could you please fill out this form for us?
Thanks!

Please do not merge this one before fixing #17 on php-http-client (i'll need to revert a commit in composer.json).

Thanks for the heads up @ninsuo!

Note: need to merge this one first https://github.com/sendgrid/php-http-client/pull/16

Hi @ninsuo,
We have merged #17 on php-http-client and now this one has come up for merge.
Could you please resolve the conflicts?
Thanks!
With Best Regards,
Elmer

Thanks again for the PR @ninsuo! Please take a moment to fill out this form so we can send you some swag :)


Parametric FreeCAD model of tibia

R_1 - main radius, R_2 - main hole radius, R_hole - screw hole radius, L_c - length of center part, L_low - length of lower hexa section, L_h - len of higher hexa section

This looks fantastic :star_struck: Thank you for this contribution!


Fix buildbot reporters warnings

Fix 3 warnings from buildbot/reporters/message.py,
"DeprecatedApiWarning: [3.4.0 and later] CustomMessageFormatter":

wantLogs has been deprecated, use want_logs and want_logs_content
wantProperties has been deprecated, use want_properties
wantSteps has been deprecated, use want_steps

Oops, I forgot about this PR, thanks for merging it!


feat(zipObj): stricter types, add test

Narrow values types per key when possible, otherwise fallback on wider mapped type.
Tests included

While I understand what you're changes do, I'm struggling to find the use case for it.
What you're additions are handling for tuples, but not only tuples, strict subtypes within (eg 'foo' over string, overnumber`).
Was hoping you could provide some

To dive into specifically when I mean here... all your unit tests utilize tuples in that each index of the array is strongly typed to be separate:
zipObj(['bool', 'number', 'null', 'undefined'], [true, 1, null, undefined])

This use case is extremely rare. Even you did receive back from an API this way, as a list of key/value tuples [['name', string], ['age', number], ['gender', 'M' | 'F' | 'X']], you would almost always know the key/value type pairing in advanced and would have defined a type for them
type Types = {
  'bool': boolean;
  'number': number;
  'null': null;
  'undefined': undefined;
};

type Person = {
  'name': string;
  'age: number;
  'gender': 'M' | 'F' | 'X';
};

My concern over this additional typing is the complexity of it. And while yes we could do it this way, doesn't mean we actually should. And in this case, I think the complexity of extracting an exact type over exactly defined tuples is not worth  it. Type casting does the trick just the same since you can define the exact type of the object ahead of time as well
const person = zipObj(['bool', 'number', 'null', 'undefined'], [true, 1, null, undefined]) as Person; // gives you what you'd need 99% of the time

I'm making some assumptions here of course, as I don't know your actually use course, and I'm more than happen to entertain it and discuss. But right now my gut is telling me that adding the additional complexity is not worth support a <1% edge case of usage

While I agree with your concern, my use case was based on pipe. I used zipObj as a part of a pipe with multiple processings, where typing each functions/params would be very verbose and unpractical. And in that situation, the current implementation would return something like this:
const splitBools = pipe(
  partition((v):v is boolean => typeof v === 'boolean'),
  zipObj(['bools', 'others'])
)

const splitted = splitBools(['a', 1, true]) // Should be auto infered as {bools: boolean[], other: Array<number | string>}

Also, narrowing 2nd parameter as tuple when possible won't actually narrow to literals most of the times, since the 2nd param will be wider at usage.

Hello, do you need anything for this PR ? Or should I close it ?

Please keep it open. I've been meaning to come back to it to review. I wanted to get your other MR as well as mine for isNil merged and released first.

I also have a much better idea why you wanted this changes and how the complexity helps from those other MRs. So I'm not still apposed to these changes as I initially called out as a concern. Now it's just a point to review the changes themselves. I'll try to block out some time before the end of this week to do that

I made a key assumption about the complexity of the typings in that it would return something like this:
const r = zipObj(['foo', 'bar'], [1, 2]);
//    ^? _.L.ZipObj<['foo', bar'], [1, 2]>

Those types coming out of a library that can take plan array/object types in and not return them back out is not a goot user experience and is something I'm trying to avoid where I can.
To my present surprise, it actually returns plan types!
const r = zipObj(['foo', 'bar'], [1, 2]);
//    ^? { foo: 1, bar: 2 }

I tested your changes against the existing tests defined in DefinitelyTyped and all passed

Just as a note, if you need a hand for some type definitions, and since I love TS types, don't hesitate to ping me somehow, maybe by creating an issue.

Hey there, hope you're doing well ! Would it be possible to have this merged someday ?


Add STM32 GDB Server to west debug

Is your enhancement proposal related to a problem? Please describe.
Currently ST products use OpenOCD or J-Link as runners for west debug. https://github.com/zephyrproject-rtos/zephyr/pull/75284 proposes setting the default west flash runner for STM32 parts to the STM32CubeProg utility. west debug does not allow use of the corresponding ST GDB server available in the STM32CubeCLT command line tools package.
I feel it would be an advantage for users to only have to download a single set of tools than have to have ST for flashing and OpenOCD/J-Link for debugging.
Describe the solution you'd like
west debug to support the STM32CubeCLT GDB server
Describe alternatives you've considered
Keeping with OpenOCD for debug - does not support latest STM32 parts
Additional context
STM32 GDB server is available in the STM32CubeCLT package downloadable here:
https://www.st.com/en/development-tools/stm32cubeclt.html
I'm not keen on requiring an ST account or valid email address to download it, but if we approve https://github.com/zephyrproject-rtos/zephyr/pull/75284 then you'll need one for the default flash runner.

but does not allow use of the STM32 GDB server

@glenn-andrews I don't think this is accurate, the changes in #75284 won't affect west debug behavior which always defaults to OpenOCD when it's available (meaning support/openocd.cfg exists).

@glenn-andrews The title should be "Add ST-LINK GDB Server to west debug" since STM32CubeCLT is just a software bundle that contains many things.

For more info about ST-LINK GDB server: https://www.st.com/resource/en/user_manual/um2576-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf

but does not allow use of the STM32 GDB server

@glenn-andrews I don't think this is accurate, the changes in #75284 won't affect west debug behavior which defaults to OpenOCD or JLink depending on which is included first in board.cmake.

You're correct, I meant to say that we can't use the corresponding STM32 GDB because it is not supported. I'll fix it when I'm home and not trying to edit it on the phone.

#75284 proposes changing the default STM32 west flash runner from OpenOCD to the STM32CubeProg utility

@glenn-andrews Actually OpenOCD wasn't default, the selection of the runner to be used with west flash was really arbitrary & depended on which runner is mentioned first in board.cmake of each board, as explained in the PR, it could be pyOCD, STM32CubeProg, OpenOCD or JLink....

#75284 proposes changing the default STM32 west flash runner from OpenOCD to the STM32CubeProg utility

@glenn-andrews Actually OpenOCD wasn't default, the selection of the runner to be used with west flash was really arbitrary & depended on which runner is mentioned first in board.cmake of each board, as explained in the PR, it could be pyOCD, STM32CubeProg, OpenOCD or JLink....

Better?


Untyped TH to appease hs-src-exts

Use untyped TH splices to allow hlint and stylish-haskell to work
see https://github.com/haskell-suite/haskell-src-exts/issues/383
Unfortunately this reverses some of the formatting changes from c907023

My manual formatting changes were very sketchy, this is much better!

@j-mueller I would think that we'd prefer to use typed TH, though.

Yes, but it makes very little odds in this case, since the result type is always just PlcCode. I think we should in general encourage people to use the typed version, although it's annoying that it breaks most development tools that use haskell-src-exts.


Reset current setpoint when entering RTL

Fixes #3844
SITL tested

Sounds like we should merge this once Travis passes.

Rebased, I was a bit out of date..

Rebased and applied.


running flutter doctor on ARM64

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel stable, v1.17.4, on Linux, locale en_US.UTF-8)
✗ Downloaded executables cannot execute on host.
See https://github.com/flutter/flutter/issues/6207 for more information
On Debian/Ubuntu/Mint: sudo apt-get install lib32stdc++6
On Fedora: dnf install libstdc++.i686
On Arch: pacman -S lib32-gcc-libs

@fiurthorn
does it help if you execute needed command
On Debian/Ubuntu/Mint: sudo apt-get install lib32stdc++6
On Fedora: dnf install libstdc++.i686
On Arch: pacman -S lib32-gcc-libs

?

Unfortunately not, since the package does not exist under ARM64.
sudo apt-get install lib32stdc ++ 6
Reading package lists ... Done
Building dependency tree
Reading state information ... Done
E: Unable to locate package lib32stdc ++ 6
E: Couldn't find any package by regex 'lib32stdc ++ 6'

I've been working on supporting ARM64 Host. https://github.com/flutter/engine/pull/20254

@TahaTesser
possible duplicate of https://github.com/flutter/flutter/issues/56992

Hi @fiurthorn
Looks like this is currently not supported yet, closing as a duplicate of https://github.com/flutter/flutter/issues/56992


Mention PTDS in ROCm Limitation

Close #5142.
This PR changes ROCm limitations to mention the Per-thread default stream as well as removing several links to GitHub issues that should be covered in the earlier paragraphs.

pfnCI, test this please.

Jenkins CI test (for commit 89bce827c15842c11ef2fe9ced972d3c7779d82d, target branch master) succeeded!


Added draggable GUI for script

Added a draggable GUI window for the script.
So far only has stop, restart bot buttons along with Github link.
I think it would be nice to have a GUI to change the word frequency and other options without having to type app.stop() in console and modifying the script.

This is fantastic!  I think having the word frequency, attacker index, mine frequency, etc. exposed in the GUI would be great.  Great work, and I hope to see more later :shipit:

Thanks I appreciate it,
gonna be honest though, that draggable function was a snippet from stack
overflow, i tried rewriting it in jquery to keep the consistency but
haven't got anywhere lol.
On 26 June 2017 at 23:47, Matt Horning<EMAIL_ADDRESS>wrote:

Merged #4 https://github.com/snollygolly/sourceio-automation/pull/4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snollygolly/sourceio-automation/pull/4#event-1139557741,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYghV60wqsyNngJ_AxLZFyYF5uvycZbvks5sIDUWgaJpZM4OF8RL
.

I rewrote it to show you what that might look like.  Let me know if you have any questions: https://github.com/snollygolly/sourceio-automation/pull/5

Yeah that function looks much better now,
looks more like it is part of the script instead of a random snippet.
On 27 June 2017 at 01:41, Matt Horning<EMAIL_ADDRESS>wrote:

I rewrote it to show you what that might look like. Let me know if you
have any questions: #5
https://github.com/snollygolly/sourceio-automation/pull/5
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snollygolly/sourceio-automation/pull/4#issuecomment-311220262,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYghV9SWllHy6ToJpaUWQk7lscyQ1qEvks5sIE-tgaJpZM4OF8RL
.


Webpack issue - ver 2.2.4

Hi,
When running webpack to build a dev version - receiving the following issue -
material-ui-pickers/_shared/DateTextField.d.ts(101,74):
TS2344: Type '"hidden" | "color" | "style" | "disabled" | "label" | "select" | "title" | "mask" | "children" | "error" | "dir" | "slot" | "type" | "component" | "margin" | "name" | "defaultChecked" | ... 283 more ... | "onInputChange"' does not satisfy the constraint '"hidden" | "color" | "style" | "disabled" | "label" | "select" | "title" | "mask" | "key" | "ref" | "children" | "error" | "dir" | "slot" | "type" | "margin" | "name" | "defaultChecked" | ... 286 more ... | "onInputChange"'.
Type '"component"' is not assignable to type '"hidden" | "color" | "style" | "disabled" | "label" | "select" | "title" | "mask" | "key" | "ref" | "children" | "error" | "dir" | "slot" | "type" | "margin" | "name" | "defaultChecked" | ... 286 more ... | "onInputChange"'.
What is the cause of the same?

We are not supporting the v2 version. But looks like mismatch of material ui and pickers version


Remove build warnings

This gets rid of the build warnings, mostly unused imports and dead code, some of which are caused by building for different OSs.

@bors-servo r+

:pushpin: Commit 5a96854 has been approved by jdm

:hourglass: Testing commit 5a96854ad0cd511e4670d5af8c9a3e2d684e7f5e with merge c362f2aa75648199cab46c0103692acddb9a67d4...

:sunny: Test successful - checks-travis
Approved by: jdm
Pushing c362f2aa75648199cab46c0103692acddb9a67d4 to master...


Script Broken After Newest Blueprint Installation Release

The script calls to the Blueprint API and seems to never be able to reach it and load indefinitely. The script will then continue to run and never complete the install.

Alright im going to look into it thanks for pointing it out sorry for taking so long to see your issue

I asked Ivy (purple) about if he changed anything and he said that he didnt and it could be the fact that he had some upstream downtime which would explain the issue anyway i'll close the issue for now.


[TOMEE-2671] Adding mp-custom-healthcheck Spanish Translation

https://issues.apache.org/jira/browse/TOMEE-2671

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Seems like this one is good now.  Gracias @emecas y @sercheo87 !


Azure Dev Provision  failed to run  in action logs

Describe the issue:
After providing  required value as repository secrets to be used by the GitHub Actions workflow, execute the azure-dev.yml action workflow.
The following error was encountered.

Repro Steps:

Fork the repository https://github.com/Azure-Samples/apptemplate-wordpress-on-aca.
Create an Azure Service Principal.
Store the required value as GitHub Actions secrets.
Execute the azure-dev.yml action workflow.

Expected behavior:
Workflow can deploy resources normally.
@kpantos for notification.

looking forward to the update


Differences in shape using from_geopolygon with odc.geo.GeoBox and datacube.utils.geometry.GeoBox

With the datacube 1.9 release coming soon, I wanted to make sure that some minor differences are expected between the behavior of the GeoBox classes. This issue will also serve as a reference for others who encounter this.
Library versions:
datacube 1.9.0rc1 & 1.8.17
odc-geo 0.4.2

Base setup:
from odc.geo.geom import Geometry
from odc.geo.geobox import GeoBox as OdcGeoBox
from odc.geo import res_
from datacube.utils.geometry import GeoBox as DcGeoBox

geom = Geometry(
    geom={
        "type": "Polygon",
        "coordinates": (
            (
                (-93.3043568, 41.8665694),
                (-93.3043349, 41.8701339),
                (-93.3008453, 41.8701405),
                (-93.2985946, 41.8690252),
                (-93.2979561, 41.8685513),
                (-93.2985067, 41.8665745),
                (-93.3043568, 41.8665694),
            ),
        ),
    },
    crs="EPSG:4326",
)
dst_crs="EPSG:6933"

odc.geo:
odc_geo_box = OdcGeoBox.from_geopolygon(
    geopolygon=geom,
    resolution=res_(3),
    crs=dst_crs,
)
odc_geo_box.shape.yx

(115, 207)

odc_geo_box = OdcGeoBox.from_geopolygon(
    geopolygon=geom,
    resolution=res_(3),
    crs=dst_crs,
    tight=True
)
odc_geo_box.shape.yx

(114, 206)

datacube.utils.geometry:
dc_geo_box = DcGeoBox.from_geopolygon(
    geopolygon=geom,
    resolution=[-3, 3],
    crs=dst_crs,
)
dc_geo_box.shape

(114, 207)

I am going to dig into the history

Difference from #38. Specifically this commit according to git bisect:
commit 16714c29aa88402eea93aae0565929688fe27338
Author: Kirill Kouzoubov<EMAIL_ADDRESS>Date:   Fri Apr 22 20:59:55 2022 +1000

    Replace alignment with anchor

    `align=` was too confusing and hard to document, concept of anchor I
    feel is more reasonable. You can anchor pixel edges to 0,0 or pixel
    center to 0,0, or you can leave it floating. Or you can pick any
    location within a pixel and say that 0,0 should coincide with that.

    center == (0.5, 0.5)
    edge == (0, 0)

    Also replacing _align_pix methods, that were hard to decipher, with
    snap_grid method in odc.geo.math

 tol=0.1 seems to make them behave the same:
odc_geo_box = OdcGeoBox.from_geopolygon(
    geopolygon=geom,
    resolution=res_(3),
    crs=dst_crs,
    tol=0.1
)
odc_geo_box.shape.yx

(114, 207)

The default for tol is currently 0.01 ref. However, datacube is hardcoded to 0.1 ref.

from odc.geo.math import snap_grid

bbox = geom.to_crs(dst_crs).boundingbox
tol = 0.01
offx, nx = snap_grid(bbox.left, bbox.right, rx, None, tol=tol)
offy, ny = snap_grid(bbox.bottom, bbox.top, ry, None, tol=tol)
(ny, nx), (offx, offy)

((114, 206), (-9002590.31883444, 4888352.245956851))

tol = 0.01
offx, nx = snap_grid(bbox.left, bbox.right, rx, 0, tol=tol)
offy, ny = snap_grid(bbox.bottom, bbox.top, ry, 0, tol=tol)
(ny, nx), (offx, offy)

((115, 207), (-9002592.0, 4888353.0))

from datacube.utils.geometry._base import _align_pix

offx, nx = _align_pix(bbox.left, bbox.right, rx, 0)
offy, ny = _align_pix(bbox.bottom, bbox.top, ry, 0)
(ny, nx), (offx, offy)

((114, 207), (-9002592.0, 4888353.0))

There are some minor differences between odc-geo GeoBox and datacube.utils GeoBox, yes.
1.9 will use the odc-geo GeoBox internally, but still provide the old datacube.utils class with a deprecation warning.

I'm not surprised that difference exists. I guess a more important question is which one is "more correct", it's good to have such definition, ideally backed by rigorous tests.

IMO the way odc-geo provides clear, consistent for its behaviour in potentially ambiguous areas - AND provides convenient tools for interoperating with systems that made different choices those areas - is the strongest argument for migrating to odc-geo.
Core's current behaviour is unclear, inconsistent and poorly documented.


Add additional kinds

To resolve these debug warnings
11:50:18.726 [debug] Could not determine kind of error: {:type_error, :unreachable_clauses, 26}

11:50:20.408 [debug] Could not determine kind of error: {:type_error, :call_intersect, 390, {:remote, 390, {:atom, 390, List}, {:atom, 390, :first}}, [{:type, 0, :bounded_fun, [{:type, 0, :fun, [{:type, 0, :product, [{:type, 0, nil, []}, {:type, 0, :any, []}]}, {:type, 0, :any, []}]}, []]}, {:type, 0, :bounded_fun, [{:type, 0, :fun, [{:type, 0, :product, [{:type, 0, :nonempty_list, [{:var, 0, :elem}]}, {:type, 0, :any, []}]}, {:var, 0, :elem}]}, []]}], [{:type, 0, :list, []}, {:type, 0, :tuple, [{:atom, 0, nil}, {:atom, 0, nil}]}]}

I'm working on a huge codebase that (mostly) passes Dialyzer but gets lots of exciting warnings from Gradient

Giving this a bump @erszcz in case it slipped through the notifications


Silence app version warning

When running the elctron app, a runtime error occurs due to no version
number being present in package.json.  This change temporarily injects a
version number into package.json and cleans up when we're done.
The process creates a ending newline in package.json, so we check it in
in order to keep that from polluting the git changes.
Also adds a note about running the electron app from the commandline in
README.md

It's an error that the default version "0.0" isn't a valid semver version.  It doesn't cause the app to exit but it does pollute the console output.


CreateNewAccount documentation

Tried making a CreateNewAccount call but after reading the code a little bit it seems the call only works with btcd's custom wallet server running.
I don't understand too much about btcd yet, but maybe it should be documented in the code that some RPC calls don't work with the default Bitcoin protocol / bitcoind daemon?

This issue was moved to btcsuite/btcd#997


Clone from master create branch 51_new_root_element_new, apply the ch…

Fixes #51
Changes
Clone from recent master
Create branch 51_new_root_element_new
Apply the changes for root element
Generate new output

Not quite right.
Regions tile should be on welcome page. Clicking on it goes to the world map.
We currently have an intermediate step we don't need.  We don't need this page:

Hello, @brahnavank - have pushed a commit that removes the top level tier.  Could you review the commit please?
If it's ok, then please pull the branch to your repo, then re-generate the output and commit the new versions.

Hello, @brahnavank - have pushed a commit that removes the top level tier. Could you review the commit please?
If it's ok, then please pull the branch to your repo, then re-generate the output and commit the new versions.

Yes also we can remove index.dita

Ok. Unncecessary files removed. Would appreciate you pulling this branch, re-generating output, then pushing, please.


FILE SIZE

@snikeguo There is a high chance this is an issue in your implementation between the information returned by findfiles and getfileinformation.

04/09/2023 13:01:02 - [Dokan] [David]FindFiles:add item:\E\Test\B_false_app_test_flashdriver_erase.s19,size:3604476
04/09/2023 13:01:02 - [Dokan] [David]FindFiles:add item:\E\Test\LaoMaoTao.7z,size:1213467906
04/09/2023 13:01:02 - [Dokan] [David]FindFiles:add item:\E\Test\test.txt,size:291
 public NtStatus FindFiles(string fileName, out IList<FileInformation> files, IDokanFileInfo info)
        {
            MyDebug($"[David]FindFiles:{fileName}");
            files = new List<FileInformation>();
            try
            {
                var dirInfo = ExplorerService.GetItemInfo(fileName).Result;
                List<ItemInfo> items = null;
                if (dirInfo.ItemType == ItemType.File)
                {
                    info.IsDirectory = false;
                    items=new List<ItemInfo>();
                    items.Add(dirInfo);
                    MyDebug($"[David]FindFiles:this is a file:{dirInfo.FullName},size:{dirInfo.Size}");
                }
                else
                {
                    info.IsDirectory = true;
                    items = ExplorerService.GetSubItemInfos(fileName).Result as List<ItemInfo>;
                }

                foreach (var item in items)
                {
                    var dfi = new FileInformation();
                    dfi.FileName = PathManager.GetItemName(item.FullName);
                    dfi.LastAccessTime = DateTime.Now;
                    dfi.CreationTime = null;
                    dfi.LastWriteTime = null;
                    MyDebug($"[David]FindFiles:add item:{item.FullName},size:{item.Size}");
                    if (item.ItemType == ItemType.Directory)
                    {
                        dfi.Attributes = FileAttributes.Directory;
                        dfi.Length = 0;
                    }
                    else
                    {
                        dfi.Attributes = FileAttributes.Normal;
                        dfi.Length = item.Size;//trace output :the item 's size is 291
                    }
                    files.Add(dfi);
                }
            }
            catch (Exception)
            {

                return NtStatus.Error;
            }

            return NtStatus.Success;
        }

test.txt 's size is 291 bytes

@Liryna But when I created an folder, everything worked fine

@Liryna  this is my test code:
https://github.com/snikeguo/DoKanyTest
Merci beaucoup!

@snikeguo This is working as expected. Explorer round the size to 1KB for small size. You can try to reproduce on your local disk and you should see the same.

@LirynaI mean, this file is only 291 bytes, but the property panel of this file shows 3.43MB.

@Liryna Test.txt is a text file, but the property panel shows that it is a folder. I clearly set the attribute as fileattributes.normal.

I unfortunately don't have time to look into the code. Please compare with the dokany sample the difference of behavior with your implementation. If you are capable to reproduce the issue with the sample I will be happy to look into it.

@Liryna Test.txt is a text file, but the property panel shows that it is a folder. I clearly set the attribute as fileattributes.normal.


Add an OpenShift Deployment for an EMDT Traceability Traction Tenant Controller for use with the VC Traceability Test Suite

Tagging folks: @WadeBarnes @esune @PatStLouis @krobinsonca
Patrick has developed a Traceability Traction Tenant Controller (TTTC - github reference to be added) that interacts with the Traceability Test Suite (TTS - link to be added). The intention of the TTS is that each participant standup an active Web component that can be used to test conformance with any other participant of the TTS.  The purpose of this issue is to request cooperation in standing up an OpenShift workspace to hosts the TTTC such that it can be used by other TTS participants.
My thoughts on what needs to be done. I expect that others — especially Wade, Emiliano and Patrick will extend/update/correct this list to make it accurate and to enable the work be done over the next short while. As I understand it, there is not a lot to do this, and so the hope is that this can be done with a meeting or two, Discord discussions as needed, and everyone doing a little bit off the side of their desks.  If this is a bigger thing — we’ll determine that quickly.
Tasks:

[ ] Patrick creates a Helm chart for the TTTC
[ ] Patrick will transfer his github repo for the TTTC to the BCGov github organization.
[ ] Wade will create an “EMDT-TTTC-DevOps” github repo to be used for managing the application in GitHub.
[ ] Wade will requestion an OpenShift Workspace for this.
[ ] For now, only the “dev” instance of the OpenShift workspace will be used.

Given this is a “no guarantees” service we are deploying is there any reason to also have a test or test+production environments?  If this does turn into something, we can add such things later, but it is not likely to happen.

[ ] Patrick (or @krobinsonca ?) will request a Traction Dev instance Tenant, and giving Patrick access.

Given this is just for intermittent testing, is Dev Traction the right place?

[ ] Wade will point Patrick to what is needed in the “EMDT-TTTC-DevOps” github repo (Helm Chart, secrets, config files, etc.)
[ ] Wade will point Patrick to minimum viable deployment requirements — e.g. adding a monitor on the service, etc.

The intention is that Patrick will do most of the work.

[ ] Patrick will oversee the deployment.
Collaborate on any issues that come up.
[ ] Patrick will arrange for the deployed app to be added as a participant in the TTS.

Thoughts on other things to be done?
An interesting question is if Patrick needs access to the OpenShift instance.  Ideally not, but will that just create an undue burden on others?

In order to determine the most appropriate home and access controls for the new controller, I'll need some more information about the TTTC itself, along with how it interacts with an agent and the TTS.  Things like;

How does the TTTC connect with and interact with an agent?
What operations can a TTTC have an agent perform?
How do you register an agent with the TTTC?
Is there a TTTC instance per tenant, or is it itself a multi-tenant service?
How does the TTS interact with the TTTC?
How do you register a TTTC instance with the TTS?

For monitoring.  Are there any health endpoints on the TTTC we could utilize for health/uptime monitoring?  What conditions need to be met in order to consider the service as operational?
EMDT has their own set of namespaces in OCP.  Will their agent be hosted there, or is the plan to have them use a Tranction tenant hosted in the main Traction environemnt?

Answers:

How does the TTTC connect with and interact with an agent?

TTTC is a Traction Controller Tenant. It receives HTTP requests from other TTS participants and uses Traction to process those requests and respond. It uses OAuth tokes from other participants.
What operations can a TTTC have an agent perform?
It can interact with Traction and process the HTTP requests from other TTS participants.
How do you register an agent with the TTTC?
Other agents registered via the TTS use TTTC.
Is there a TTTC instance per tenant, or is it itself a multi-tenant service?
There is only one TTTC instance.
How does the TTS interact with the TTTC?
Other TTS participants call TTTC as per the Test Suite.
How do you register a TTTC instance with the TTS?
That is done by Patrick — I think it is a PR to a GitHub instance.

Let’s have a call about this.

Thanks @swcurran  for setting up this issue.
TTTC is an implementation of the w3c-ccg traceability specification which leverages traction/aca-py as the backend service.
Here's some answers for @WadeBarnes questions:

How does the TTTC connect with and interact with an agent?

The TTTC will interact with the agent by requesting a traction multi-tenant token and sending authenticated requests to the API

What operations can a TTTC have an agent perform?

The TTTC will use the following endpoints from the traction api:

Request a multi-tenant token
Create dids (the TTTC will create a web did and host the did document)
issue/verify json-ld credentials (plan is to move to the new vc-api endpoints once 0.12.0 is deployed in the traction environment)
resolve dids

How do you register an agent with the TTTC?

When deploying TTTC, you pass in a client_id/api_key as environment variables
The application will be able to request tokens as long as the api key still exist in the tenant's api keys

Is there a TTTC instance per tenant, or is it itself a multi-tenant service?

Per tenant

How does the TTS interact with the TTTC?

The TTS is ran every 24 hours through github actions
There is a test client for conformity testing and interoperability testing. (See Interoperability Report and Conformance Testing actions)
The results will be published. This is similar in design to how aath operates, with the exception that it tests live services.
https://w3c-ccg.github.io/traceability-interop/reports/conformance/
https://w3c-ccg.github.io/traceability-interop/reports/interoperability/
https://w3c-ccg.github.io/traceability-interop/reports/archive/

How do you register a TTTC instance with the TTS?

Here's the official procedure.

For monitoring. Are there any health endpoints on the TTTC we could utilize for health/uptime monitoring? What conditions need to be met in order to consider the service as operational?

I've added a /healthz endpoint, we can have endpoints to setup readiness/liveliness and healthiness k8s probes.

EMDT has their own set of namespaces in OCP. Will their agent be hosted there, or is the plan to have them use a Tranction tenant hosted in the main Traction environemnt?

As long as the traction instance doesn't reset periodically as we do not want to have to resubmit the information to the TTS maintainers.

+1 to have a call as I also would like to understand the deployment models we will aim for. I can also do a quick demonstration of how the app will interact with Traction.
Here's the project, I have a branch for this specific deployment. From my understanding the charts will live in a different repo and the deployment will be done mostly through GA?
A few questions that come to mind:

What is the build pipeline going to look like?
What domain will we use and how will we configure the ingress/service so the application is reachable?

The deployment itself is a simple fastapi server with a connection to a postgres database. Until v0.12.0 is available in a traction instance, I also deploy an agent for verification (this agent does not need to be exposed.)

EMDT has their own set of namespaces in OCP. Will their agent be hosted there, or is the plan to have them use a Tranction tenant hosted in the main Traction environemnt?

Reading back on this question, I think it would make most sense if the TTTC instance is deployed in a EMDT namespace.

EMDT has their own set of namespaces in OCP. Will their agent be hosted there, or is the plan to have them use a Tranction tenant hosted in the main Traction environemnt?

I don’t think this is an either/or.  The plan is for them to use a Traction Tenant in Traction Dev (or Test or Prod as you see fit). The TTTC itself will need an OCP namespace and it should go wherever is easiest. Who manages the EMDT namespaces? What I don’t think we want is to use an OCP namespace managed by EMLI folks that know nothing about Digital Trust.

From my understanding the charts will live in a different repo and the deployment will be done mostly through GA?

Typically the charts live with the application, provided they are somewhat generic (deploys to a K8S environment), and the values file (the environment specific settings) would be contained in a separate repo.  What we try to avoid is imposing our specific infrastructure (BC Gov OCP platform specifics) on others.  Traditionally our OCP templates have been contained in a separate repo because they are tailored to the BC Gov OCP environments.  As we move to Helm charts we're consciously making them more generic.

From my understanding the charts will live in a different repo and the deployment will be done mostly through GA?

What we have done for our projects is have a charts folder that contains the generic charts - a separate repo is used to store the values.yaml files that have deployment-specific settings (URLs, database provider settings, etc.).

Reading back on this question, I think it would make most sense if the TTTC instance is deployed in a EMDT namespace and use a traction tenant from the main traction environment.

What is the expected lifespan for this project? If it is a prototype/demo and it is expected to stay as such, we may want to possibly use our demo namespaces in OCP rather than requesting a new set that will add to the list and be only partially used? Unsure about using the EMDT namespaces as I don't know how much they're involved technically, especially if this is a prototype that may/may not evolve and be there long term.
@PatStLouis is the service stateless, or do we need to provision storage in form of a database? If this is the case, we will want to conenct it to a backup instance so we have the data if we ever need to move and restore it elsewhere.

Thanks for the information @WadeBarnes @esune
What you described is what I currently have. I usually template my values.yml file to be overwritten with a GA. So if I understand you would have a sperate repo with a GA to clone, build, push and deploy the application? Makes sense, do you have an example for me to have a look at? I've deployed github ARC in our infra and this is how we manage our deployments. Where do you push the docker images and how do you connect to your cluster?
The lifespan of it will be however long BCGov wants to be published as a w3c-ccg traceability spec implementor. This instance will only be used for conformity/interoperability testing and demonstration. The demo namespace might be the way to go for the time being.
I have a postgresDB service in my architecture. This can be deployed along the application or we can just provide a connection url to the application if you use an external DB service. We will need permanent storage for did documents, oauth client information and status list credentials.

@PatStLouis check out the traction and/or vc-authn repos. For those we publish charts to their gh-pages site so that they can be installed without having to clone the repo - see https://github.com/bcgov/vc-authn-oidc/tree/main/.github/actions/chart_releaser as an example

The values files for those can be found in a separate repo, here; https://github.com/bcgov/trust-over-ip-configurations/tree/main/helm-values

@esune @WadeBarnes Here's the current state of the charts. I based them on the traction deployment and simplified some components. I also copied the chart release files.
I will need some clarification on how we will manage tls certificates to complete the ingress configuration. Only the controller service will need an ingress and be exposed publicly. The controller will communicate with the agent/db through their respective internal service endpoints. The agent does not need a connection to a ledger or a db, it's only used to verify proofs on json-ld credentials. Issuance will be made through the traction instance.
Let me know if network policies/service accounts are needed.
The controller has a secret ressource with all required environment variables which is injected into the deployment. They just need to be populated when we are ready to deploy.
For the domain, I think a *.interop.vonx.io would be suitable. Here's some suggestions...
traceability.interop.vonx.io
trace.interop.vonx.io
vc.interop.vonx.io
What are the suggested next step? I'm available friday for a session where we could proceed with the repo transfer/deployment.

With the certs, we typically use the BCDevOps/certbot to manage Let's Encrypt certificates on our Routes in OpenShift.  Any Route labeled with certbot-managed=true gets a certificate assigned and managed.  We need to determine how best to get that to work with this service.  I may be wrong but I don't think our OCP environment supports any certificate issuers for use with ingress resources, will check.  With Traction both routes and ingress are provisioned.

For network policies, one will need to be defined to allow ingress to the pod exposing the public endpoint, and one each for the inter-pod communications.

I believe if you leave the ingressClassName as a blank string, OpenShift will automatically create the associated Routes.  That's how the vc-authm-oidc charts behave.  From there you just need to ensure they are labeled correctly. The certbot-managed label should remain set to false until we've finalized the URL.
Refer to the charts

For the domain, I think a *.interop.vonx.io would be suitable. Here's some suggestions...
traceability.interop.vonx.io
trace.interop.vonx.io
vc.interop.vonx.io

My vote is for traceability.interop.vonx.io

@WadeBarnes @esune @i5okie
Let's have a session to deploy this project. Is there availability today or tomorrow around 17hPM EDT (14h PDT)?

@swcurran the controller is available at https://traceability.interop.vonx.io. It's currently pointing to a sandbox tenant and I will run the test-suites again tonight to make sure all is still running smooth. In the meantime I'll submit a ticket for a dev/test tenant to use when we are ready to submit the implementation to the w3c-ccg.

Awesome — nice work!

@esune I managed to pass most of the conformance tests, I'm getting gateway timeouts when verifying credentials and resolving did's. These are the 2 operations which rely on the deployed agent so I'm suspecting that the controller is unable to talk with the agent admin endpoint. It might have to do with the network policy. Can we have a look?

@PatStLouis, It's an issue with the Network Policy.  The controller pod is missing the expected app label.  You'll need to update the charts.  I'll manually update the pod spec for now to add the label.

The controller can talk to the aca-py instance now:

@WadeBarnes I confirm that it's working, thanks!

Thanks @WadeBarnes - you got to it before I did.


Throw error on null/empty Id created

Closes https://github.com/eclipse-basyx/basyx-java-server-sdk/issues/68


Ori Changes ItemNames

Might need to revert the ItemAPI updates. I think it'll mean too many plugins will need to be recompiled and staged seeming that the signatures were changed so that less exceptions are thrown, that instead booleans are returned.

Just going through

RecipeAPI :: Added exit early null check - Safe to merge

TextUtil :: Removed redundant replace code - Safe to merge

Iteration :: Added new collect API - Safe to merge

NullCoalescing :: Added new cast API - Safe to merge

ResourceUtils - Safe to merge

itemNames :: Refactor - UNSAFE TO MERGE

ItemAPI :: Update all APIs to be less throwy - UNSAFE TO MERGE

ItemAPI :: Add normalise item API - Safe to merge

CustomItems :: New concept for custom items - Safe to merge

BlockAPI :: add attached face api - Safe to merge

BlockAPI :: rotate change - Safe to merge

ItemAPI :: added getDamageable() api - Safe to merge

"ItemAPI :: Update all APIs to be less throwy" is unsafe by nature of it changing the signature of a few methods. The removal of annotations doesn't seem to matter to the compiler, but the change of ItemAPI.addLore() for example from a void return to a boolean return has non-recompiled plugins throwing fits. So whether or not to merge this is dependent on your patience to recompile and stage a lot of plugins :P I'll leave that up to you to decide.. that is what this PR is for after all ;)
"itemNames :: Refactor" is unsafe by nature of it being a pretty substantial refactor of the item name storage and registration system. Any plugins that was previously using LoadCustomItemNamesEvent, which is unlikely but nonetheless possible, will break.


Multiple debugging session with voltron

Can we have a feature that support for multiple debugging session with voltron?

I suggest that we can choose a port randomly for Flask, and tell to voltron view client which one it needs to connect to

I think that with a few modifications it can be done (please, correct me if I'm missing something):
First, the server (in the debugger) must choose a random port (tcp) or random domain (unix):
https://github.com/snare/voltron/blob/0b7a2fba88077406a5223984139475b0c1b98da6/voltron/core.py#L162-L171
We could say "if you choose a port == 0 in the configuration, voltron will pick a random one for you". Something similar for the domain like "if the domain ends in a -,  voltron will add a random postfix to it".
Then we should let the user know which port/domain was chosen:
https://github.com/snare/voltron/blob/0b7a2fba88077406a5223984139475b0c1b98da6/voltron/entry.py#L108
The client side is a little more complex.
First, we should add a parameter to the views to change the port/domain.
https://github.com/snare/voltron/blob/0b7a2fba88077406a5223984139475b0c1b98da6/voltron/view.py#L148-L153
Now, the problem is that the client expects the final URL, not an IP+port or a domain:
https://github.com/snare/voltron/blob/0b7a2fba88077406a5223984139475b0c1b98da6/voltron/view.py#L166
The simplest solution (but not human friendly) would create a parameter to change not the port/domain but the api_url and configure the client to use it.
Any thoughts? If there is interest on this I could write a PR.


Minor feedback/suggestions.

Preface
"Such cloud environments may or may not conform to hybrid, public, or private cloud topologies and the associated Cloud Service Providers." Not quite sure the purpose of this sentence , and the link between the topologies list and 'associated Cloud Service Providers' is unclear - propose review and revise.
On-Premises (On-Prem)
Proposed definition: On-premises refers to IT infrastructure hardware and software applications that are hosted on-site at the customer. The customer has direct control of on-premises IT assets including security and upkeep, and the physical location. Traditionally, Common Criteria has assumed on-premises environments.
Architecture - Life-cycle presentation.
I am not sure if this section really contributes much (maybe someone else will expand). The Agile vs waterfall issue in CC has been around for a long time and not sure if it is a problem we should try to tackle here. Maybe move these to glossary? The only other reference to dev ops is under "Development Environment Sub-Process"
Cloud Sub-Processes
Development Environment Sub-process.
The 'Trusted Provider' material around Assumptions and Objectives for the Operating Environment could be merged into this section.
Security Target (TSS) Sub-Process
The 'Trusted Provider' material around SFRs etc could be merged here. It probably would be good to review each section of an ST/PP. Again, Trusted Provided document does this at a very high level so can be merged in.

Preface already revised.
On-Prem needs more work will make a sep issue. @jgb1128 do this later
Move architecture to parking lot to discuss down the line
Cloud Sub-Process: agree will add placeholder.
ST Sub Process Agree.

All resolved, closing.


Enhance behavior tests

I experienced a weird thing, where properties within behaviors were not being used.  Make sure we understand if this is misbehave's problem or not.

Was a bug, resolved by 7946c5e3b034027c1def2a6649aba8fdab14d225.


WIP: Match Docker/Podman default container stop timeout

Codecov Report
Attention: Patch coverage is 46.15385% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 70.49%. Comparing base (bb64c84) to head (bb64174).

Files
Patch %
Lines

compose.go
50.00%
4 Missing and 2 partials :warning:

main.go
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   70.39%   70.49%   +0.10%
==========================================
  Files           6        6
  Lines         743      749       +6
==========================================
+ Hits          523      528       +5
- Misses        189      190       +1
  Partials       31       31

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add latest and running

output:
RancherOS rancher-dev ttyS0
eth0: <IP_ADDRESS> lo: <IP_ADDRESS>
rancher-dev login: rancher (automatic login)

[rancher@rancher-dev ~]$ sudo ros os list
rancher/os:v0.4.0 remote available
rancher/os:v0.4.1 remote available
rancher/os:v0.4.2 remote available
rancher/os:v0.4.3 remote available
rancher/os:v0.4.4 remote available
rancher/os:v0.4.5 remote available
rancher/os:v0.5.0 remote available
rancher/os:v0.6.0 remote available
rancher/os:v0.6.1 remote latest
e97ad03-dirty installed
[rancher@rancher-dev ~]$ qemu: terminating on signal 2

(I'm not sure if "installed" or "running" is the right thing to say)
the first commit comes from #1271 - I'm presuming that can be merged first.
This PR relates to #147 and #148

It's not really necessary for this PR, but reversing the order of the releases might be a nice addition. Putting the current version at the top might be nice too.
On a somewhat related topic, I don't really like the ros os subcommand in general. It seems like both words basically mean the same thing and it's only used for ros os upgrade and ros os list. I think this made more sense when it was rancherctl os ... and then when we moved to ros it was never updated.
Instead, maybe we could just move ros os upgrade to ros upgrade and include ros os list functionality in ros version. It's not a perfect fit for ros version, but I think it might be preferable to what we currently have.

OI, you! @joshwget that's a separate issue :p.
I've created you #1274
wrt reverse ordering, yup, we can do that, but the currently running version will be at the end if its not in the list that we request :)

updated with reverse order, and using running instead of installed

LGTM


How to support for still / animated WebP image format

I would like to use Nuke to deal with web image loading and image cache.
And I also have need for loading animated WebP image so I import NukeWebPPlugin.
I wrote some code with Nuke for testing:
WebPImageDecoder.enable()
let urlStr = "https://isparta.github.io/compare-webp/image/gif_webp/webp/2.webp"
if let onlineFileUrl = URL(string: urlStr) {
let task = ImagePipeline.shared.loadImage(with: onlineFileUrl, queue: nil, progress: nil) { (result: Result<ImageResponse, ImagePipeline.Error>) in
switch result {
case .success(let imageRespoonse):
//...deal with image
break
case .failure(let error):
debugPrint("error: (error.localizedDescription)")
//...error handling
break
}
}
And I got an error:
"decoding failed : Failed to create an image from the image data"
I would ask How to support for still / animated WebP image format?
Thank you.

is there any progress on this issue? @ryokosuge


automation: build for c9s on x86_64

Build for CentOS Stream 9 on x86_64
Signed-off-by: Sandro Bonazzola<EMAIL_ADDRESS>

Job failure is due to some bug in CI, opened https://issues.redhat.com/browse/CPDEVOPS-242


Dash.vim and neocomplete.vim

I'm wondering if there are any ideas about integrating Dash database with neocomplete.vim. It seems like Dash.app could be a really good source of keywords for autocompletion, but I didn't find anything about it.

Hi @slabko.
The way dash.vim works right now is quite simple, figuring out the possible types of documentation one might be looking for depending on the filetype one is using, and allowing some configuration around this.
But after that, it completely delegates the search to Dash.app.
The thing is, the plugin API from Dash.app does not grant access to it's internal data. It's a one way street.

He @rizzatti
Thank you very much for the response. One more question about it - I saw that was actually possible to get more information from Dash. A simple example could be Alfred, where, if you type dash and part of the searching text, it shows dropdown with matching names. I thought, if I want to implement such a thing for VIM, there should be an API of such kind, which gives the matching result for my search outside the app.

@slabko Thanks for letting me know. I'll look into how that integration works.


ColorOp in shaders only operate in limited range which cause clipping in bright areas

Tested versions
Godot 4.3 Stable
System information
Windows 10, Godot 4.3 Stable
Issue description
If you apply Color Operations to images, the operations are performed in the 8-bit space only. Which means, if the brightness exceeds 1, it will not be extended (like it have to) but will be clipping to 1 and will be grayed out on the final image.
Here is the overlay with central area as gray:
(which will not change the luminosity)

Here is the overlay with white center:
(the sky is now clamped into 1, it is in fact Darker, than it used to be, and auto exposure lit up the landscape):

When someone applies effects that supposed to make the image brighter, the last thing they expect is to get a darker image with the loss of details. And since the majority of games have bright areas, these effects are barely usable.
The desired result
Instead, it would be nice to make it the same as in other apps, where it can operate in the same range as the original vector and can in fact be much brighter than 0-1 range. Otherwise, half of these operations are barely usable, since they can only be safely used to make the image darker.
Steps to reproduce
Use ColorOp node with any mode that makes the original image brighter.
It will in areas of 0-1, but will cause clipping in 1+
Minimal reproduction project (MRP)
N/A

I was wrong: you can use a full range by applying USE HDR toggle in texture settings, which means, case closed.


Dashboard Token Listing: ARMY

Discord Handle of Submitter: Fran | Superfluid#3671
Token Symbol: ARMY
Network: Mumbai (testnet)
Token Address: 0x6C357412329f9a3EE07017Be93ed0aC551faa77b
Network Explorer Link: https://mumbai.polygonscan.com/address/0x6C357412329f9a3EE07017Be93ed0aC551faa77b
Is a Super Token? true
Address of Underlying Token:  None
SVG Logo Link: https://keyboard.cool/assets/Twemoji/2694.svg
Coingecko or Hardcoded Price?: Hardcoded
Coingecko ID:
Harcoded Price (if Coingecko ID is unavailable): 0
Token HEX Color: #ccd6dd
Info on Listing: https://github.com/kobuta23/king-of-the-hill
Please close only after token has been added to resolver!

listing done: https://console.superfluid.finance/mumbai/supertokens/0x6C357412329f9a3EE07017Be93ed0aC551faa77b?tab=streams


fix MD5 calculation of empty message

This allows using messages that refer to move_base_msgs/MoveBaseResult
for example.

thank you very much


Update scalafmt-core to 3.7.6

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.5 to 3.7.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #144 (d8054d6) into master (503251b) will not change coverage.
The diff coverage is n/a.

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

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.


Failing tests on Mono 5.0.0.x

Please provide a succinct description of the issue.
FSharp.Compiler.Service.Tests.FscTests are failing on Mono 5.0.0
Repro steps
Provide the steps required to reproduce the problem

run ./build.sh

Expected behavior
Tests pass :)
Actual behavior
5) Test Error : FSharp.Compiler.Service.Tests.FscTests.4. Compile from simple AST
   FSharp.Compiler.Service.Tests.FscTests+VerificationException : Verification of '/var/folders/xq/6w_9rpz96rxdl1k47q5plk5c0000gn/T/test-1953860418/foo.dll' failed with code 134, message <<<mono_os_mutex_lock: pthread_mutex_lock failed with "Invalid argument" (22)

Known workarounds
None

https://bugzilla.xamarin.com/show_bug.cgi?id=55801

This was the pverify issue which has subsequently been fixed in Mono


Fixes code analysis dependency upgrade

Breaking change

Proposed change

Type of change

[x] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the [development checklist][dev-checklist]
[ ] The code compiles without warnings (code quality chek)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

Codecov Report

Merging #712 (ebed21c) into dev (a398c41) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #712      +/-   ##
==========================================
- Coverage   79.67%   79.59%   -0.09%
==========================================
  Files         135      135
  Lines        3464     3464
  Branches      354      354
==========================================
- Hits         2760     2757       -3
- Misses        560      563       +3
  Partials      144      144

Flag
Coverage Δ

unittests
79.59% <ø> (-0.09%)
:arrow_down:

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

Impacted Files
Coverage Δ

...mon.HassClient/Internal/Net/WebSocketClientImpl.cs
61.11% <0.00%> (-8.34%)
:arrow_down:

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 a398c41...ebed21c. Read the comment docs.


:wrench: add timeout also for batch jobs in load_table_from_uri

Description
This MR aims to fix the issue mentioned in here, where there seems to be some confusion between the docs and the implementation.
Summoning @z3z1ma

LGTM, sorry for long delay. Not sure why I didnt see the GH notification.


About AutoencoderKL

Did you train yourself to use AutoencoderKL in the latest version? Or still using the official SD AutoencoderKL weight? Have you ever tried training an AutoencoderKL from scratch?

Hi.
No, we didn't train or tune AutoencoderKL and we still use the official one. We haven't tried to train that from scratch. Thanks for your question, and we may try it by tuning AutoencoderKL in the future.


Running Sum of 1d Array.cpp

Running Sum of 1d Array
Related Issue
Closes: #847
Describe the changes you've made
Added Folder for Running Sum of 1d Array in cpp
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

Solved Issue No. #1039 Within the same PR . @Nivedita967 Mam Please Review.


No Crashes but Nothing Loads

So I've used Schematica in the past and never had an issue. However I've recently moved into a new modpack and wanted to transfer some things. (I'm in Single player, creative, and made sure the mod is enabled, and don't have optifine.)
The Issue: I've got schematics in the folder, but regardless of what I click, nothing happens, no crash, no outline, no problem except that nothing happens.
I've tried new schematics, mine, but nothing happens.

Ditto. However, I think it might be a block from a mod you're missing in the target mod pack?
It would be nice if there was a way to get a list of needed mods for a given schematic.

I don't know if its that or not. The schematics I'm trying to load are full vanilla minecraft

Can't help but having the same problem.  New world and no ghost image.  Just took a quick schematic of a tree in this new world and that bit worked fine but will not load it. Gonna carry on poking at it. If i figure anything out I'll let ya know.

im having the issue and still need help, any updates?

For me i think it's a conflict between the biome mod and scematica.  It's the only thing that's different between a world where schematica works and once where it doesn't.  I think.  I may be mistaken as i haven't logged into MC for a month or 3. Will check later.


MMM-Powerwall/auth gives scraping oauth form failed warning

Within the last few days attempting to enter Tesla login credentials via MMM-Powerwall/auth gives an error
"scraping oauth form failed"
this is for the Tesla API.  Logging into the local Powerwall API still works OK.
Any ideas?

I'm seeing the same thing. Only part of the data is showing up now.

Yes, this cropped up a while ago -- the request to Tesla's auth server times out.  It only seems to happen in Node and on Raspberry Pi; the same code works running on my desktop.  I haven't found a solution yet.

I'm very sorry for the delay -- I eventually gave up trying to solve the problem and worked around it instead.  Can you try the python branch (PR #49) and see if that fixes things for you?

Thanks for the workaround - I ran the python script with the required credentials and it seemed to update the tokens.json file  I then restarted the MagicMirror but the go to "MMM-Powerwall/auth to login message still shows"

The script is used by the helper; you still sign in via the /auth page.


Armada Server CRD

Codecov Report
Base: 78.07% // Head: 74.77% // Decreases project coverage by -3.29% :warning:

Coverage data is based on head (29a2d25) compared to base (8b53554).
Patch coverage: 60.63% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #28      +/-   ##
==========================================
- Coverage   78.07%   74.77%   -3.30%
==========================================
  Files          11       11
  Lines         903     1114     +211
==========================================
+ Hits          705      833     +128
- Misses        145      206      +61
- Partials       53       75      +22

Impacted Files
Coverage Δ

controllers/install/armadaserver_controller.go
60.63% <60.63%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


merge tide-compress's mime db stuff into the Content-Type typed header

basically, this but with the other fields that the json database provides: https://github.com/Fishrock123/tide-compress/blob/main/build.rs
see https://github.com/jshttp/mime-db/blob/master/db.json

@yoshuawuyts I think static file serving should probably also use this to attempt to determine mime type before sniffing

Oh yeah, this would be great! @Fishrock123 is this something you'd be able to contribute?
I'm thinking ideally we could move this from a build.rs script into a standalone command [^xtask] which we can run periodically instead of every time someone builds. Some systems intentionally lock down external network connection during building; but in general pre-building it / checking it into the repo should be faster for most builds. But no worries if we start with a build.rs script and then refactor it later.
[^xtask]: I'm a big fan of the matklad/cargo-xtask pattern for this. That would allow us to do something like cargo xtask codegen in the repo to generate all the code we need.

That's now been done in tide-compress: https://github.com/Fishrock123/tide-compress/commit/cc1551b6a8267cccb70fa3e84ee787e6aaad2fa0
I did not use xtask as that seemed like it added more unnecessary stuff, I just made a run-able subcrate which isn't publishable.


done email problem #1427

Related Issue
None
Fixes:  #1427
Description
email was taking only upper case letters and invalid inputs

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes. Make sure to attach before & after screenshots in your PR.]
before:

after:

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@dnyandeepchute Why does the "Subscribe" button lead to the "Contact" section? Please correct it

Conflicting files
index.html
Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Fixed typo in xref

@hdrabkin - any idea how this slipped in?

It should have been picked up by travis shouldn't it?

AH, I know; it's because of passing back and forth between me and Peifen. I missed it apparently.


GIT-48 Added optional fields to the book model

Works well! I wonder if there's a way that we can also show the price beside the books (maybe beside the author?)


Error while executing Dumpinfo code on raspbian

I am trying to run this code in arduino IDE that I have installed on rasberry pi. I have included MFRC522 library in arduino IDE that I generated using make command after extracting the zip folder downloaded from here. When I try to compile the code, it shows following errors. Please help..
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp: In member function â€˜void MFRC522::PCD_WriteRegister(byte, byte)â€™:
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:41:6: error: â€˜class SPIClassâ€™ has no member named â€˜beginTransactionâ€™
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:41:70: error: â€˜SPISettingsâ€™ was not declared in this scope
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:46:6: error: â€˜class SPIClassâ€™ has no member named â€˜endTransactionâ€™
SPI.endTransaction(); // Stop using the SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp: In member function â€˜void MFRC522::PCD_WriteRegister(byte, byte, byte*)â€™:
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:57:6: error: â€˜class SPIClassâ€™ has no member named â€˜beginTransactionâ€™
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:57:70: error: â€˜SPISettingsâ€™ was not declared in this scope
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:64:6: error: â€˜class SPIClassâ€™ has no member named â€˜endTransactionâ€™
SPI.endTransaction(); // Stop using the SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp: In member function â€˜byte MFRC522::PCD_ReadRegister(byte)â€™:
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:74:6: error: â€˜class SPIClassâ€™ has no member named â€˜beginTransactionâ€™
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:74:70: error: â€˜SPISettingsâ€™ was not declared in this scope
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:79:6: error: â€˜class SPIClassâ€™ has no member named â€˜endTransactionâ€™
SPI.endTransaction(); // Stop using the SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp: In member function â€˜void MFRC522::PCD_ReadRegister(byte, byte, byte*, byte)â€™:
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:98:6: error: â€˜class SPIClassâ€™ has no member named â€˜beginTransactionâ€™
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:98:70: error: â€˜SPISettingsâ€™ was not declared in this scope
SPI.beginTransaction(SPISettings(SPI_CLOCK_DIV4, MSBFIRST, SPI_MODE0)); // Set the settings to work with SPI bus
^
/home/pi/sketchbook/libraries/MFRC522/MFRC522.cpp:121:6: error: â€˜class SPIClassâ€™ has no member named â€˜endTransactionâ€™
SPI.endTransaction(); // Stop using the SPI bus
^

Something is wrong with your SPI lib.
Which ide version and board did you tried?

arduino 2:1.0.5+dfsg2-4 IDE. I installed it using 'sudo apt-get install arduino' command
and I am using arduino uno board
can I install new version of IDE or can I upgrade SPI library?

Ok, 1.0 is too old, this library targets the latest 1.6.
Maybe upgrading SPI lib works but I don't know.

Yes, 1.6 uses new version !
But 1.0 version was installed by default from command line.
Can you please suggest how can I install a newer version?

Or how can I upgrade SPI lib?

The repo do not provide a newer version and website do not offer a arm compiled version. So you have two options: 1. get source code and compile it by your own or 2. search a arm compiled version on the internet.
To upgrade SPI lib: search spi.h and spi.cpp and replace them by the latest source.

Okay!
Thank you for helping :-)

Issue can be closed.