Cannot set cell value in Excel 2016

Hello,
I am trying to use your example for Excel 2016 and I am not able to set cell value, though I can read it.
Code sample:
AutomationDataGridCell cell = ...
cell.select(); // Works
cell.setValue("5555"); // Doesn't work

I have had a play with this, but I have Excel 2016 only, and the examples no longer work as I would expect - I think the underlying hierarchy of the elements has changed, so I will update the documentation and let you know whether it still works

@mmarquee I wonder if there are any updates on this?

Hi, I am still looking at this, I now have access to Excel 2016, and it looks like the structure the elements on the screen has changed, and so we have to navigate down to the grid different;y. I might be able to look at it this week, depending on my 'real work' schedule.

I have returned to this issue, and it seems to 'set' the value, without actually changing the value in the cell. I will continue to investigate

I've done a bit more experimenting, and it looks like a bug somewhere in Excel or the automation library - I can get the value via the inspect tool (i,e. using automation, but not the library), and it behaves in the same way - it sets the value (you can see in the inspector, but the actual value in the cell doesn't change.
I will keep this issue open and periodically restest - especially when a new release of Excel happens.


Picovoice Issue: cant put cheetah on pi zero w

Make sure you have read the documentation, and have put forth a reasonable effort to find an existing answer.
Expected behaviour
Cheetah working fine
Actual behaviour
Not working
Steps to reproduce the behaviour
I followed the docs, downloaded the demo package but, when i tried to run the demo it says unsupported cpu architecture ‘armv61’
(Include enough details so that the issue can be reproduced independently.)

You've posted the issue in the wrong repository. Please submit it in the appropriate repository, Cheetah, in the future.
Regarding the error you're encountering, Cheetah is designed to work only on Raspberry Pi 3 and 4, as clearly stated in the official doc and an error is expected if you're attempting to run it on a different board.


Application Windows icon is wrong

The svg export of this stencil from Visio seems to fail. Using an emf export and then convert this to svg seems to work better in that case.
Attached is the new svg.
Drawing1.zip

Fixed in #46d4844


Use Select for bool fields

What it solves
Resolves #184
How this PR fixes it
Using the <Select /> component from the safe-react-components instead a regular input
How to test it

Choose True and False values from the dropdown and add several transactions using them
Send transactions to safe-web and check that the values are correctly propagated

All good from my end, top job yago ;)


Create Chapter 3.jl

Initial attempt to translate the code of chapter 3 for julia, please inform me if you need any change.

It looks very nice, thanks. Only two comments: a few of the plots display legends, when the images in the book's web page have none. It might be good to set legend=false in those cases. Second, the Erdos Renyi graph looks a bit different than the one on the web page. On the web page, there are a few points with only one or two connections, while the Julia code generates points with more connections. Your code looks correct to me, but when I run it, I never get a figure that looks like the one on the web site. I suspect that the web page may have created the graph with the probability of a connection lower than 0.3, so the problem may not be with your code. What do you think?


Refactor ServerTypeDefine and ComponentsDefine to be more extendable

ServerTypeDefine and ComponentsDefine are now defined in SkyWalking project as Java file. In before, this is good, but now, our community grows. From @liuhaoyang 's .NET SDK experiences,  he need to extend these two to support .NET ecosystem.
So, I proposal to change the defines to be in file, and provide a document to describe it, which is easier to understand find and extend.
Hope anyone has time to contribute this feature. And provide this in 5.0.0-beta and binding with .NET agent 0.1

FYI @ascrutae @peng-yongsheng

My schedule is full during the improve feature of 5.0.0-beta.

Working on this. Provide extention to any language implementor.

Supported. @liuhaoyang and @ascrutae you can send your .NET and nodejs components now.
I proposal to reserve 1000-2000 to .NET, and 2000-3000 to nodejs, but if you are using the same components as Java, e.g. mysql, please consider to add languages under MySQL, rather than add a new one.

got it, Thanks


Initial package

This pull request introduces the initial version of Drafter NPM (version 1.0.0) which provides an NPM package for API Blueprint parsing. This package will optionally depend on Protagonist and fallback to Drafter.js when Protagonist isn't installable.
To be able to test this during CI, I've added a step to Travis CI to uninstall the ubuntu build-essentials package which removes the compiler to make the optional dependency of Protagonist fail. There is an additional assertion that the node_modules directory doesn't contain protagonist just incase something in Travis CI changes in the future and the Protagonist package is installed successfully.

Smart! 👍

Only... It's a pity that now we have Drafter (containing Snowcrash), Drafter NPM, Drafter.js (which was replacing Protagonist in the past and then got deprecated in favor of Protagonist again), and Protagonist. Unless we start to give away posters with infographics about our parser chain, nobody will be able to use it, including our own employees (many of them are confused already).

This should simplify it, if you don't know do npm i drafterand if you need it fast install the optional dependencies too ... the rest is unimportant.

Unless we start to give away posters with infographics about our parser chain, nobody will be able to use it, including our own employees (many of them are confused already).

I've added notices to the READMEs of respective projects to hopefully make this clear.
Check:

https://github.com/apiaryio/drafter.js/pull/57
https://github.com/apiaryio/protagonist/pull/159


[BUG] Can`t make more then 1 script (breaks the tabulation of the python)

When I create the second script, I break the first, make first (python) like a second (Jint)
With this have error, unreal to use diff languages scripts (+ breaks the tabulation of the python )

For the tabulation see this issue https://github.com/openbullet/OpenBullet2/issues/113

@openbullet It`s a Joke? said about tabulations.... Minified not helping 200%
Can u add import script file? (u doing it in C# CodeBlock )
ExecuteIronPyScript(data, tmp_rvwpkf, "Scripts/66c8ac26ebe6e672f991ce8ffac3c373.py");
its a python, tabulations cant be Minified

What's a joke?
#113 is still open as you can clearly see, which means it hasn't been fixed yet. What are you being salty about?

@RiseFox missed to add:
It`s a Stacker make a problem - deleting tabs when reopened as Stacker

@RiseFox missed to add:
It`s a Stacker make a problem - deleting tabs when reopened as Stacker

I already fixed that, as you can see

if you go to that commit you will see the change
please learn how github works


Fix def 'regulation of transcription, epigenetic'

transcription call @colinlog @hattrill @ValWood
New def
A process that modulates the frequency, rate or extent of gene expression by remodelling of chromatin by either modifying the chromatin fiber, the nucleosomal histones, or the DNA. Once established, this regulation may be maintained over many cell divisions. It can also be heritable in the absence of the instigating signal.

negative regulation gene expression, epigenetic, newdef:
An epigenetic process that stops, prevents or reduces the rate of gene expression by remodelling of chromatin by either modifying the chromatin fiber, the nucleosomal histones, or the DNA.

Add ref: PMID:22243696

Add parent: 'part of' some 'chromatin organization'


Script issues and vulnerabilities

We use SonarCloud to help us identify issues and vulnerabilities. After implementing BlazorApplicationInsights 3.0.4, SonarCloud raised multiple issues and brought to our attention two possible vulnerabilities.
Security hotspots (Vulnerabilities)

Issues (I can't open them all there are just too many 😅. 40 to be exact)

Note : We marked them as fixed without applying any fix out of trust but we would like to get back to them.
BlazorApplicationInsights works and doesn't show any console or network error. That being said, these issues and vulnerability SonarCloud is showing us is raising concerns among us.
I was wondering if these issues were known or if there are any plans on handling them ?

Thanks for the information. I think we can close this ticket. I will try to get more information from Microsoft's Application Insights


Any way to get around absolute path?

Hi @tcmetzger, thank you very much for the package. It is very useful.
I was wondering, is there anyway to get around the absolute path requirement?
Considering that Sphinx currently copies everything inside the directories listed in html_static_path to _static, couldn't we just use /_static/<file name> in the href?

@abravalheri I'm glad to hear you find this package useful! You could probably use /_static/<file name>, but as far as I can see, this would only work with pages that are in the same directory. Once you start having RST files in subdirectories as well, the reference won't work anymore.
I'm sure there is a way to fix this - I just haven't had the time to research and implement that. Please feel free to make a PR if you can. Thanks!


vulkaninfo: Check support for surface extensions before using them

Not all ICDs support all the surface extensions that vulkaninfo
enumerates.
For example, on Linux with an ICD that only support VK_KHR_xcb_surface,
vulkaninfo crashes:
Presentable Surfaces:
=====================
ERROR: VK_KHR_xlib_surface extension not enabled.  vkCreateXlibSurfaceKHR not executed!

vulkaninfo/vulkaninfo.c:1427: failed with VK_ERROR_EXTENSION_NOT_PRESENT

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

Global CI should be fixed.  Please rebase and resubmit your change so that it can run through CI.


Add Nano and Vim into Docker Image

Hey !
I found this issue and I had time to answer it. So here is the PR.
Today, this update install :

Nano v7.2
Vim v9.0

Feel free to comment if I missed something

Thanks!


ILRepack fails to install as a dotnet tool

I recently saw that as part of the 2.0.35 release, it's supposed to be possible to install ILRepack as a dotnet global tool.
So I issued the command dotnet tool install -g ilrepack but was met with the following error:
Tool 'ilrepack' failed to update due to the following:
The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package.
Tool 'ilrepack' failed to install. Contact the tool author for assistance.

OK, so because dotnet tools share Nuget.org as their repository, of course ilrepack didn't install as a dotnet tool, because it's not a dotnet tool but a regular old Nuget package.
The dotnet tool needs to be installed with dotnet tool install -g dotnet-ilrepack. It would be nice if the README mentioned this 😄


Seo improvement ans accessibility fixes

SEO and Accessibility Enhancements
I've made key improvements to enhance both SEO and accessibility on the website:

SEO: Optimized alt attributes, and internal links for better search engine visibility.
Accessibility: Added aria-label to buttons, input, and navigation for improved screen reader compatibility and enhanced keyboard navigation.

These updates will boost both user experience and search performance, making the site more inclusive and discoverable.
Looking forward to your feedback!

issue number ?

#1129

@SumaLatha2023 wrong issue number
Kindly mention correct issue number
Haven't you raised issue

@SumaLatha2023 You have to Raise issue first


Add more complete test cases / testing

No further test content will be added at this time because of copyright concerns.


Implement browser User-Agent string + pull from forks

on iPhone, it is:
Mozilla/5.0 (iPhone; CPU iPhone OS 13_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148
Make it:
Mozilla/5.0 (iPhone; CPU iPhone OS 13_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148 AlphaWallet/2.30
And pull the changes to the forks.
Whether or not the forks have their own variation of User-Agent is a seperate topic not covered in this issue. Currently I'm not seeing the need of it and cautious of over-design.

Done in 9c21a214f65c5dfbd19e482dcd427f92f1a7afde 😈


Where should packages store their data

I needed to store some state in my elvish-gitstatus package and I used the following place:
~/.elvish/package-data/gitstatus

This is super low-priority, but I was wondering: Does anyone have a better idea? Is there already a common place where others store their state?

XDG_DATA_HOME or .local/share

I don't think there's an accepted convention, but storing it under ~/.elvish/ sounds reasonable. @SolitudeSF's suggestions make sense too. My aliases module stores the alias definitions under ~/.elvish/aliases/.

One reason I didn't store it outside of .elvish is the thought that this keeps everything related to Elvish in one place, so cleanup is more straight-forward.

I agree with that, I like having the whole config coalesced under a single directory. I am not much of a fan of XDG :)

I just noticed you are another Swiss user of Elvish 🇨🇭👍

The Swiss do like high quality tools 😉

As others said, there isn't any guidance at the moment yet.

This should take into account the proposal to switch to using the XDG specification, issue #383. Since the data discussed in this issue is inherently per-system it should be stored someplace under ~/.local/share/elvish if the project adopts the XDG spec.

FWIW, I just started seeing this warning after upgrading elvish to the HEAD version a few minutes ago:
Warning: ~/.elvish will be ignored from Elvish 0.20.0.

The warning is due to the hardcoded path in package github.com/href/elvish-gitstatus:
# the folder where the gitstatusd related data is stored
var appdir = ~/.elvish/package-data/gitstatus

I would argue this should use $XDG_STATE_HOME (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) or equivalent. The problem is that determining that directory is complicated since Elvish does not require the XDG env vars to be set and has fallbacks which differ between UNIX and Windows. It shouldn't be necessary for a module to implement this logic. See #1385 where I proposed exposing this information via the platform: module to make it trivial for modules to use whatever directory the current Elvish instance deems is appropriate for each type of file Elvish searches for (see https://elv.sh/ref/command.html).
For the moment I'm just going to locally edit github.com/href/elvish-gitstatus/gitstatus.elv but this needs to be resolved ASAP since ~/.elvish is now officially deprecated.


Extra line in raw(read(file))

My codly is 1.0.0 .
When using #raw(read(file), block: true) extra line with a line number appears at the end of the code block.
Probably an issue of Typst 0.11.1 (installed via nix on SteamOS), because the same thing happens when I use this simple rule instead.
#show raw.where(block: true): code => {
  show raw.line: line => {
    text(fill: gray)[#line.number]
    h(1em)
    line.body
  }
  code
}

Can't reproduce this behavior in the web app.
My fix was downloading codly and adding or line.number == line.count to
      if not in_range(line.number) {
        continue
      }

Is there a better way?
Seems like work is being done on line numbers in typst itself.

Just to mention, the PR you listed is lines but not specifically for code, the original work to make line numbers for raw blocks was in https://github.com/typst/typst/pull/2341
As for the extra line, does your file contain it? Bit of a dumb question but I would rather check that first. Also, if it's an issue with typst v0.11 and fixed in v0.11.1, see what I mean here: https://typst.app/project/rq9BcVmddB0jX80iQ3679R If I put a newline at the end of the read file, it will show up but that's just how it is. Your solution just removes the last line and therefore could break other code blocks.

As for the extra line, does your file contain it? Bit of a dumb question but I would rather check that first.

A very well placed question and the first one I asked myself too.
Unfortunately, no, there is only one line feed character at the end of the files.
Is that how it should be? Maybe it's a Posix thing?

Your solution just removes the last line and therefore could break other code blocks.
If only I could use "range" and "skips" based on their number counting from the end of file.

It turns out read returns string and I can just slice it with the Typst built-in function to cut off the last lines.
#let solution = read(sql_path + "spool.txt").slice(0, -1)
#raw(solution, block: true)

If only I could use "range" and "skips" based on their number counting from the end of file.
That's actually a pretty neat idea


Navigator.vibrate is not recognized by Lib.d.ts

It is supported by many browsers (mobile) so should be included.
Specification can be found at: http://www.w3.org/TR/vibration/

May need a new sub-part for lib.d.ts for stuff like this

I agree, did you mean something like... ?
interface Navigator extends ... (lots of others) ... NavigatorVibrate {
}
interface NavigatorVibrate {
vibrate(pattern: number | number[]): boolean;
}


why cant it download???

i tried all the ways to download it on linux mint and the furthest i got was E: No se ha podido localizar el paquete scratchattach or in English that it couldn't find scratchattach

I probably can't help you but I do advise that you provide some more detail about what happened (screenshot? maybe censor parts if necessary)

I probably can't help you but I do advise that you provide some more detail about what happened (screenshot? maybe censor parts if necessary)

im doing sudo apt install python3-pip to see if not installing it could be the problem

i think its stuck on 12%

do sudo apt install python3-scratchattach

couldn't find the packet named python 3 scratch attach

do pip install -U scratchattach or pythom -m pip install -U scratchattach
tiziano220812 @.***> schrieb am So., 29. Dez. 2024,
21:56:

couldn't find the packet named python 3 scratch attach
—
Reply to this email directly, view it on GitHub
https://github.com/TimMcCool/scratchattach/issues/303#issuecomment-2564836382,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCKMZUJJVESFDCOOEUYL2L2IBOYHAVCNFSM6AAAAABUCNR4MKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRUHAZTMMZYGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, try with venv, and don't use sudo:
python -m venv venv
source venv/bin/activate
pip install scratchattach


Repo config files

Added repo config files, such as:

pre-commit configurations: .pre-commit-config.yaml.
workflow files: .github/workflows/
Readme file adjustments: README.md.
Added issue templates: .github/ISSUE_TEMPLATE/.

closes #23


Feat/devex 1560 generate project

@jdidion I think the code is fine. I noticed two things, and may have missed others:

There are now separate modules for parsing stand-alone types and expressions. Could we use the ParseDocument module to do this one place?
The coverage plugin is now enabled. This is good, it is just that I had some experience with it in dxWDL land.

I didn't understand what the Interactive stuff was about. I suggest having a zoom meeting, so we can discuss face to face.

Since the tests are failing because of the ANTLR compilation, how about using the top-level makefile instead of the instructions in the master.yml?

Fix the makefile, according to the new locations of the grammar files
Call the makefile from the master.yml file, instead of building the java files directly.


feat: add srcset generation

This PR creates a new class method in ImgixClient that will generate a srcset string, which can be used in the srcset attribute on an <img> HTML element. buildSrcSet() takes a path and params argument similar to createURL(), and will return a String in one of two srcset formats.
Srcset Width-Pairs
The first format creates srcset width-pairs, a comma-delimited list of URLs and width descriptors corresponding to each one. This allows for responsive size switching based on the current width of the browser viewport. buildSrcSet() will append any params passed to the method to each URL constructed within the list. The following is an example of how to generate a width-pair srcset:
var client = new ImgixClient({domain:'my-social-network.imgix.net', includeLibraryParam:false});
var srcset = client.buildSrcSet('image.jpg');
console.log(srcset);

will return the following String (collapsed for brevity):
https://my-social-network.imgix.net/image.jpg?w=100 100w,
https://my-social-network.imgix.net/image.jpg?w=116 116w,
https://my-social-network.imgix.net/image.jpg?w=134 134w,
                                            ...
https://my-social-network.imgix.net/image.jpg?w=7400 7400w,
https://my-social-network.imgix.net/image.jpg?w=8192 8192w

Notice that a w= parameter is automatically inserted for each entry in the srcset list. This is required in order for the element to properly display the correctly-sized image corresponding to the viewport's width.
Device Pixel Ratio (DPR) Srcset
The second format this method can return is a srcset list of same-size images in varying resolutions. In this case, images are scaled using the dpr= parameter to adjust for the device pixel ratio of the browser. A DPR srcset will be automatically generated instead of a width-pair srcset if exact dimensions for the output image are specified, by providing either a w (width) or a h (height) and ar (aspect ratio) in the params argument. The following is an example of how to generate a DPR srcset:
var client = new ImgixClient({domain:'my-social-network.imgix.net', includeLibraryParam:false});
var srcset = client.buildSrcSet('image.jpg', {h:800, ar:'3:2'});
console.log(srcset);

which will return the following String:
https://my-social-network.imgix.net/image.jpg?h=800&ar=3%3A2 1x,
https://my-social-network.imgix.net/image.jpg?h=800&ar=3%3A2 2x,
https://my-social-network.imgix.net/image.jpg?h=800&ar=3%3A2 3x,
https://my-social-network.imgix.net/image.jpg?h=800&ar=3%3A2 4x,
https://my-social-network.imgix.net/image.jpg?h=800&ar=3%3A2 5x

Signing URLs
buildSrcSet() also supports signing URLs, which can be very useful for generating server-side and then passing it to the client. This will avoid having to expose your imgix source's secure token to the client.
var client = new ImgixClient({domain:'my-social-network.imgix.net', secureURLToken:'my-token', includeLibraryParam:false});
var srcset = client.buildSrcSet('image.jpg', {w:100});
console.log(srcset);

generates a srcset with unique signatures for each URL:
https://test.imgix.net/bridge.png?dpr=1&w=100&s=f461367db3c5fad8ae9d18864b38533a 1x,
https://test.imgix.net/bridge.png?dpr=2&w=100&s=9cac4c9fa5a263cef1ca443340a64a2c 2x,
https://test.imgix.net/bridge.png?dpr=3&w=100&s=29a0aa19b074a000de96eb4f1a24803b 3x,
https://test.imgix.net/bridge.png?dpr=4&w=100&s=f16ac140640d46ed8499102730e1f62d 4x,
https://test.imgix.net/bridge.png?dpr=5&w=100&s=3ef7c404f749ed5296fe0b6de47d8d2f 5x

For more information on srcset, building responsive images, and resolution switching:

Responsive images - MDN
Srcset and Sizes - Eric Portis

@jayeb Also wanted to ask, do you have any ideas for other test cases that could helpful here?

:tada: This PR is included in version 0.3.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add "nearest" kwarg to ghost boundary

This adds a "nearest" as a boundary mode for ghosting. This is needed for compatibility with skimage.

Seems like a good addition to me.  +1

Also @cowlicks you should now have push access.  Want to test it out?

@mrocklin sure, merging


Can not to render a few pages correctly

@jlhotar any changes?

@jlhotar any changes?

No, new version of Google Chrome and still the same problem

@jlhotar any updates on this error?


Possible fix for a memory leak [SR-4036]

This is related to https://bugs.swift.org/browse/SR-4036
I've documented all my findings in the JIRA report.
This may not be the best way to fix this problem. I'm keen to know what others think

What does _persistCString do exactly?
On the face of it this seems like it will just result in a use-after-free. Getting the cString without having the ObjC autoreleasepool in place is probably not going to work well.

Hi @parkera :
_persistCString creates a new [CChar], copies contents of the memory (which we malloc'd) pointed by the UnsafePointer passed to it into this array and then returns the array. So, I guess after we return from here, there's no need to hold on to the malloc'd memory. The free could also be called here but other callers of _persistCString may not expect this behaviour.

Hm, I'm not really a fan of this approach for a couple of reasons:

It makes this file different across darwin and Linux, because on darwin that C string is backed by an autoreleased NSData and it would be a serious error to free it.
It leaves the leak in place at the source of the problem, which is NSString's cString (and utf8string, which we do nothing about here).

It seems like we should elide cString and utf8String from NSString on Linux, because there is no choice but for them to leak, and implement this method in a way which is more canonical (perhaps data:usingEncoding: followed by a copy).

I agree @parkera . Closing this PR. Let's continue this discussion on https://bugs.swift.org/browse/SR-4036
Thanks!


Android+iOS usage of User Certificate Authorities with dart.io

Hi,
Our application which is a mobile application written in flutter targets both Android and iOS, and is deployed On-Premise (The Backend API is installed on premise, and isn't public to the internet)
As part of our solution, the customer often has their own Certificate Authority for their internal network, and does not have access to public certificates.
We planned to deploy that private CA certificates to the mobile devices, as a trusted root certificate (also known as a user-ca), and planned for flutter to trust the API server certificate issued from that CA.
However, it seems that flutter isn't using the User CA in any of its internal operations, and always returns this error:
Unhandled Exception: HandshakeException: Handshake error in client (OS Error: E/flutter ( 7370): CERTIFICATE_VERIFY_FAILED: self signed certificate(handshake.cc:354))
At first we thought it is because we are missing some manifest as described here (in case of android), however it seems that flutter completely ignores it (dart.io), and and uses only its internal logic (non-platform) to approve/reject the certificate.
The only thing that worked is specifying the certificate as a Trusted Certificate as part of the SecurityContext of dart.
This however does not allow us to specify a trusted root certificate, but rather a 'self-signed' certificate type of approach.
Further more, even if it did, we would still need to find a secure way to load the trusted user certificate from android/iOS and give it to flutter as input, as it is different per-customer/deployment.
Can you advise on a possible solution, or better yet, add support within flutter for this scenario?

Hi @ImdShatz, please provide a minimal, reproducible example and the output of flutter doctor -v as well as flutter run -v so that we can investigate the issue. Would be ideal if you could also include the steps you are taking to produce the self-signed user ca and how you're installing it on the app/device.


Access to accum function

Was trying to build a custom accumulator, and am having troble getting access to the accum function.
When i put (:require [clara.rules.accumulators :as acc]) in my project i get access to the predefined accumulators but not the accum function to define my own. Is there something else i need to be doing?

Just noticed that accum was committed 15 days ago, whereas 0.8.9 was published in late September, which explains it. Do you plan on pushing a new version soon or Is there a RC version i can use? it would be really helpful.

Yes, I published the 0.9 API doc prematurely with a 0.8.9 label. My mistake! I am planning on doing a release of 0.9 this week, but I just published a snapshot build to the Sonatype repository, so you can change your Clara dependency to this:
[org.toomuchcode/clara-rules "0.9.0-SNAPSHOT"]

And add the following to your project.clj.
  :repositories [["snapshots" {:url "https://oss.sonatype.org/content/repositories/snapshots/"}]]

Of course, the the Maven equivalents will work as well. Sorry for the confusion!

Great thanks so much for yr quick response and this great tool.
On Oct 27, 2015 5:32 PM, "Ryan Brush"<EMAIL_ADDRESS>wrote:

Yes, I published the 0.9 API doc prematurely with a 0.8.9 label. My
mistake! I am planning on doing a release of 0.9 this week, but I just
published a snapshot build to the Sonatype repository, so you can change
your Clara dependency to this:
[org.toomuchcode/clara-rules "0.9.0-SNAPSHOT"]
And add the following to your project.clj.
:repositories [["snapshots" {:url "https://oss.sonatype.org/content/repositories/snapshots/"}]]
Of course, the the Maven equivalents will work as well. Sorry for the
confusion!
—
Reply to this email directly or view it on GitHub
https://github.com/rbrush/clara-rules/issues/137#issuecomment-151651517.

clara-rules 0.9 is out and available on Clojars, so you can move away from that snapshot build. Details in the release announcement here: https://groups.google.com/forum/#!topic/clara-rules/6Y2zHx9OQwA.
I'm closing this since there isn't anything more to do here. If you have any further topics, I keep an eye on the Clara google group (https://groups.google.com/forum/#!forum/clara-rules) and am happy to follow up there.

Apparently I forgot to close this. Doing so now. ;)


Example in DataFidelity

data_fidelity is not defined in the example proposed in DataFidelity. It's working correctly with the additional line: data_fidelity = L2()

Thank you very much for noticing! This example will be fixed in this PR.

Closing as #19 is now merged


Fix autotick-bot

See https://github.com/conda-forge/libignition-msgs1-feedstock/issues/50 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Implement appid extension in WebAuthn?

Are we able to support the appid extension which is defined in WebAuthn?
To transfer from old U2F api to WebAuthn, we face the issue that both old appid and rpid exist. Is it possible to support this extension?

This extension is already supported, see the U2FFido2Server class for reference: https://github.com/Yubico/python-fido2/blob/main/fido2/server.py#L387

Thank you for your reply.
AFAICT, that is the implementation on the server side, to help verify both U2F and FIDO2 signatures.
I am asking whether it is possible to support it on the client side?
In browsers, we normally make a single assertion call like this with WebAuthn to assert both rpid and originally registered appid.
await navigator.credentials.get({
  publicKey: {
    challenge: randomUint8ArrayFromServer,
    rpid: "example.com"
    allowCredentials: [{
      id: Uint8Array(credentialId),
      type: 'public-key',
      transports: ['usb'],
    }],
    timeout: 60000,
    extensions: {
      appid: "https://login.example.com/appid.json",
    }
  }
});

To achieve the same result using python-fido2, we need to call the get_assertion API twice, to ensure that both rpid and appid are asserted.
Is this your suggested approach to achieve this behavior described by WebAuthn?
Or do you think it will be better that python-fido2 can support this extension natively? If so, I am very happy to help implement that.

Ah, sorry I misunderstood. You're correct, this extension is only implemented for the server-side. It's a little trickier to implement cleanly on the client as it is quite different from the other extensions in that it changes the logic of the command quite a bit. One reason we didn't implement this was also that we didn't see an immediate use case for it: Our assumption being that if you have existing U2F-credentials these are very likely to come from a browser-based client, and would likely only be used in a browser setting. Maybe this assumption doesn't hold up. Can you share a bit more about your use case and why you need the appId extension support on the client?

We want to log existing users in through command line applications, and at the same time we want to keep their registered security keys working as well.
So we have users with mixed registered key handles with both appid and rpid.


Get setTimeout lazily

This prevents from using old versions of setTimeout/Date.now.
Previously, if jest's timers were set as fake by default and then you wanted to use real timers in a test suite with jest.useRealTimers(), the waitForExpect function would still use the default functions.
Solution: The functions just need to be gotten every time the function is called.

The tests are failing but I don't think they are really covering the uses cases.
E.g. "it works even if the timers are overwritten by jest" it's assuming that the jest environment has set the timers to real by default and that they are being changed to fake, but it could be the other way around: default: fake -> changed to real.
You can easily test it with a jest.config.json file.

Hmmm.... I took the #21 code to simplify things, and moved got the setTimeout lazily as you did in this PR. Now we have one test breaking. (the other two were about Date() being mocked which we don't use now, so they should be removed)
I understand the remaining test is not covering all use cases. (we should add them, if possible)
But more importantly, for backward compatibility, I'm not exactly sure why this test should fail after this change. What I'm afraid of - will people that have exactly this scenario:

having the jest environment timers set to real by default, that are then changed to fake
will have their tests failing now?

Sorry, I'm not particularly knowledgeable around jest fake timers, that was someone elses code that we've merged in, and the tests seemed reasonable at the time.. :) Was this test incorrect to start with?

having the jest environment timers set to real by default, that are then changed to fake
will have their tests failing now?

Yes. Previously, it didn't matter that the timers were changed to fake as the module was always using the default (timers are set by default to real in this tests).
However, now that the function is getting the setTimeout fn lazily, it's going to use the mocked version of setTimeout because of the change to fake timers. Therefore, this is what is happening with the test:
 jest.useFakeTimers();
 ...
 setTimeout(() => {
    numberToChange = 100; // Timeout is enqueued in fake setTimeout
 }, randomTimeout);

 jest.runAllTimers(); // fake setTimeout is run (i.e. numberToChange is set to 100)

 await waitForExpect(() => { // Timeout is enqueued in fake setTimeout
    expect(numberToChange).toEqual(100);
 });

 // There is no jest.runAllTimers() call that runs the previous enqueued timeout!

@slightlytyler would you like to chip in here? Maybe see if your tests still work if you move things the way @brapifra suggests in this PR?
btw, I just noticed that that test was mine, so maybe I indeed messed it up to begin with. I am a bit worried about people that relied on the existing behavior, but we could do a major bump if needed.
@brapifra Do you not see any reason to use waitForExpect while using fake timers (in the same test)? I think that this change ultimately will prevent that use case. But maybe that use case doesn't exist?
sorry for taking so long here :) It seems like a very simple change, but the consequences are not fully clear to me yet.

That's the thing, I don't think that using fake timers is even a use case. It doesn't make sense to wait for something that won't be run until you explicitly call jest.runAllTimers. In that case you would basically do the call first and then the expect:
setTimeout(() => {
    numberToChange = 100; // Timeout is enqueued in mocked setTimeout
 }, randomTimeout);

jest.runAllTimers();
expect(numberToChange).toBe(100);

No worries, I understand your concerns. Let's see @slightlytyler's opinion about this.

Agreed with @brapifra here. I've never used them together...

@brapifra if you wanted to work on tests that covering the correct scenarios that would be great. Unless @slightlytyler comes in and protests I will merge this in by the weekend.

I can correct the tests this Saturday morning if that suits you @lgandecki

@brapifra  That would be great, thanks!

@lgandecki As discussed, I've modified the unit test to cover the correct scenario. Let me know what you think.

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix potential bug in where we copy a lock value

My linter just picked up the issue that we're passing around a proto by value vs pointer. This has the issue that protos have locks embedded in them which we shouldn't copy.
https://github.com/golang/tools/blob/master/go/analysis/passes/copylock/copylock.go

Codecov Report

Merging #4650 (2579680) into main (30e5362) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #4650      +/-   ##
==========================================
- Coverage   68.97%   68.91%   -0.06%
==========================================
  Files         213      219       +6
  Lines       14861    15077     +216
==========================================
+ Hits        10250    10390     +140
- Misses       4558     4632      +74
- Partials       53       55       +2

Flag
Coverage Δ

unittests
68.91% <0.00%> (-0.06%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/envoy/ads/grpc.go
0.00% <0.00%> (ø)

pkg/envoy/ads/stream.go
8.12% <0.00%> (ø)

cmd/cli/verify.go
100.00% <0.00%> (ø)

pkg/cli/verifier/verifier.go
92.68% <0.00%> (ø)

pkg/cli/verifier/connectivity_pod_to_pod.go
56.52% <0.00%> (ø)

pkg/cli/verifier/namespace.go
73.52% <0.00%> (ø)

cmd/cli/verify_connectivity.go
42.10% <0.00%> (ø)

pkg/cli/verifier/envoy_config_parser.go
50.98% <0.00%> (ø)

pkg/smi/client.go
73.45% <0.00%> (+0.26%)
:arrow_up:

cmd/cli/osm.go
80.70% <0.00%> (+0.34%)
:arrow_up:

... and 1 more

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 30e5362...2579680. Read the comment docs.


chore: import repository https://github.com/rocannon77/jx2-python-http-01-6.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[T2A4][T09-A4]Zhang Yunxuan

@yunxz is this PR ready for review?

Yep ready for review

alright! Looks like you really decreased SLAP a lot, and by using a combination of tabs and spaces in your code, the code is now really really smelly. Good job!


[HiTL] CA Interaction HIT Performance Incentives

Description
This PR is a continuation of #848, with the addition of performance incentives for high quality interactions.  "High quality" is determined by stoplight score, with $0.30 bonuses for each stoplight point (a theoretical maximum of $3.00 bonus per HIT).
Note that bonuses are not issued automatically, they need to be parsed from the local Mephisto DB and issued via the issue_bonuses.py script.
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[X] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[X] I want a thorough review of the implementation.
[ ] I want a high level review.
[ ] I want a deep design review.

Before and After
A before and after view of the stoplight can be seen here
Testing
I've tested this version of the dashboard locally and ran several batches of HITs.
Checklist:

[X] I have performed manual end-to-end testing of the feature in my environment.
[X] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[X] New and existing unit tests pass locally with my changes.
[X] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I have verified that all scripts in tests/scripts runs on hardware.

This PR has ~180 files, can you point out which files need a review ?

Yes most files are the updated dashboard build.  The only file with substantive changes is issue_bonuses.py

Thanks for creating this PR! The performance incentive work is great! Here're some feedback:

Could you also integrate issue_bonus logic to Interaction Job? Like run this script as soon as interaction job is terminated and resources are cleaned.
We should have a mechanism to mark whether the bonus has been issued, and decline to issue the same bonus twice.

Thanks for creating this PR! The performance incentive work is great! Here're some feedback:

Could you also integrate issue_bonus logic to Interaction Job? Like run this script as soon as interaction job is terminated and resources are cleaned.
We should have a mechanism to mark whether the bonus has been issued, and decline to issue the same bonus twice.

Thanks for the feedback @snyxan!  I've resolved these comments by introducing a shared bonus records file in a private S3 bucket, and now issue_bonus.py is imported into the interaction job data generator.  Please let me know if you think the implementation is OK.

I missed the bug fix commit. Now LGTM. Ship it!


Vocabulary in entry point

It would be very nice to be able to retrieve the vocabulary from the entry point, so that dereferencing vocabulary is no longer reliant on RDF or any external specs.
Strawman:
{
  "@context": {
    "µ": "https://micro-api.org/"
  },
  "µ:vocab": [
    {
      "@id": "fieldName",
      "@type": "µ:String",
      "µ:belongsTo": [ "TypeName" ],
      "µ:description": "Field name description."
    },
    {
      "@id": "TypeName",
      "@type": "µ:Type",
      "µ:description": "Type name description."
    }
  ]
}

Dereferencing vocab: http://example.com/#fieldName would map to vocab @id with value fieldName. Fragment identifiers correspond to @ids which is consistent with JSON-LD.
This has the following considerations:

Adds vocabulary for basic types: String, Number, Boolean, Object, Date, Buffer.
Adds vocabulary for a type itself, µ:Type, and µ:description.
Adds vocabulary for the µ:vocab container.

That would be 9 new vocabulary definitions, but they're all necessary to sidestep existing RDF vocabularies. This is actually completely normal, even schema.org does this.
http://schema.org/Text
http://meta.schema.org/Class

Done https://github.com/micro-api/micro-api/commit/ba63c7d33cc0e018ab68f1d5ee3480a097d5ca0b.


License is missing

Good point, what license would be most appropriate for it? WebSharper itself is Apache 2. I would like to release SiteFi on a worry-free license, it's just code that helps people do more.

Dunno. Maybe MIT. It is very common.

Added MIT, the sample blog already stated it's under MIT.


add serde feature

Needed to add the sandbox in SiR
Description
Description of the pull request changes and motivation.
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (7c70e71) 75.66% compared to head (f40b41c) 75.64%.

Files
Patch %
Lines

src/starknet.rs
0.00%
7 Missing :warning:

src/values.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #422      +/-   ##
==========================================
- Coverage   75.66%   75.64%   -0.03%
==========================================
  Files         108      108
  Lines       29001    29008       +7
==========================================
- Hits        21945    21944       -1
- Misses       7056     7064       +8

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


Unable to recover my account

I am trying to recover from my account backup, but it tells me Authenticator is "Unable to Recover"!
Why. I checked on my iPhone that iCloud backup is enabled. Please help me here.

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

ID: 8b52a210-1be6-4e5f-d95c-8ea7b87919ca
Version Independent ID: 02a43ebb-7471-d7ff-4f7e-84c9f7a66326
Content: Back up and recover accounts with the Microsoft Authenticator app - Azure AD
Content Source: articles/active-directory/user-help/user-help-auth-app-backup-recovery.md
Service: active-directory
Sub-service: user-help
GitHub Login: @curtand
Microsoft Alias: curtand

@mrlerch Thank you for your query. We use the github azure-docs repository for issues with the documentation however will try to help you on this . In case it requires deeper troubleshooting we would request you to engage with support team directly . As of now we have assigned this to one of our engineers to review and provide guidance around this issue . They will investigate and update the thread further.

@mrlerch ,
Could you please provide us more information, are you trying to restore across platforms (Example: Restore an android based backup when switching to an iPhone.)? If so then its know limitations.
If you trying to backup on same mobile iOS then you need to make sure that you do not add that account first, instead use the Begin recovery process to fetch that account from your saved up cloud.
For any work or school account, you will need to follow these steps in full view mode in order to recover.
Let me know if your have any different scenario.
Regards,
Siva

Closing this out as I have not heard back. Feel free to tag me in the comments or open a new issue if you'd like to continue the discussion.

You really should consider cross platform cloud backup. Thanks!
Martin Lerch
702.321.0908 (mobile)
Sent from my iPhone (mobile)

The information contained in this communication is potentially confidential, and intended only for the use of the addressee. If you received this communication in error, please notify us by return e-mail and delete this communication and all copies, including all attachments.

On Apr 19, 2021, at 7:09 AM, SivaKumarSelvaraj-MSFT @.***> wrote:

Closing this out as I have not heard back. Feel free to tag me in the comments or open a new issue if you'd like to continue the discussion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

These are critical:

manual backup option, allow to export accounts manually, avoid the "walled garden" approach
cross platform backup support
backup to text file stored in OneDrive vault


Add id column in /POST cachegroups response structure and xmlid query parameter for /GET cachegroup

I'm submitting a ...

[ ] bug report
[ ] new feature / enhancement request
[x] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[x] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:

So after user create a cache group, it doesn't display any id in the response but then the rest of the cache group method are using id to navigate like cachegroups/{{ID}}/deliveryservices , cachegroups/{{ID}}/parameters.
Right now, the only way to get the id is go to Traffic Portal and look at the URL of that cache group because you cannot /GET cachegroup with topologies or type; there will be a lot of cache group display in the result.
Expected / new behavior:

I suggest we add id in the response of the POST cachegroups API and add xmlid query parameter in  /GET cachegroups so that if TP failed user can able to use the TO API.
Minimal reproduction of the problem with instructions:

Anything else:

@dpham692 - i'm confused by the term xmlid in the title. xmlid is a delivery service property.

When I create a new cache group with, it returns the id for me:
{"alerts":[{"text":"cachegroup was created.","level":"success"}],
"response":{"id":112,
...}}

@shamrickus Confirm it's display the id.


on_client_wakeup happens before on_register

Environment

VerneMQ Version: 1.5.0
OS: Docker/Kubernetes
Erlang/OTP version (if building from source):

Expected behavior
According to https://vernemq.com/docs/plugindevelopment/sessionlifecycle.html, the on_client_wakeup webhook should be called after the on_register webhook.
Actual behaviour
In my Node.js service where I implemented the webhook endpoints, I can see that on_client_wakeup is called about 10ms before on_register when I connect a client to the broker.

Hello @doubliez , thank you for reporting.
You're absolutely correct, the on_client_wakeup is called before on_register. We'll change the flow chart accordingly.

I've just updated the diagrams on the website.
Again thanks for reporting.


Building rust-parcel-template fails with  🚨  Error writing to cache: ENOENT: no such file or directory, stat 'build.rs'

Hello, I'm getting

🚨  Error writing to cache: ENOENT: no such file or directory, stat 'build.rs'

When trying to build rust-parcel-template.
Steps to reproduce:
npm init rust-parcel my-app
cd my-app
npm start

My versions:
npm 6.14.7
parcel 1.12.4
parcel-plugin-wasm.rs 1.2.16
Arch Linux

Exactly same issue here, just mkdir build.rs in the root folder of your project

isn't build.rs supposed to be a file that defines your project is built?