ERROR: Unable to map scan scope variable to a value.

im running this via ps but when I run it I get the below error without asking what option I want to run:
PS D:\log4j> .\scanner-8b.ps1
Log4j/Log4Shell CVE-2021-44228 Scanning/Mitigation Tool (seagull/Datto)
=======================================================================
! ERROR: Unable to map scan scope variable to a value. (This should never happen!)
  The acceptable values for env:usrScanScope are:
    1: Scan files on Home Drive
    2: Scan files on fixed and removable drives
    3: Scan files on all detected drives, even network drives
PS D:\log4j>

Before running the script you need to set three variables:
$env:usrScanscope = # 1, 2, or 3 - 1 = Scan home drive, 2 = scan fixed and removable, 3 = scan all local and network drives
$env:usrUpdateDefs = # 'true' or 'false' - Update YARA definitions, true or false
$env:usrMitigate = # 'Y', 'N', or 'X' - Y = Set LOG4J_FORMAT_MSG_NO_LOOKUPS to true, N = Set LOG4J_FORMAT_MSG_NO_LOOKUPS to false, X = Don't set LOG4J_FORMAT_MSG_NO_LOOKUPS

Well-put.


[$1000] Dev: IOS -The main composer disappears when the thread message edit composer is open

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a chat
Send a message
Click on "Reply in thread"
Send a thread message
Click on "Edit comment" of sent thread message
Press the back button
Notice the main composer is not visible when the thread message edit composer is open

Expected Result:
The main composer should remain visible even when the thread message edit composer is open
Actual Result:
The main composer disappears when the thread message edit composer is open
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev <IP_ADDRESS>
Reproducible in staging?: no
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/aff0a6ec-2fdc-4731-9c08-b768cb8e8d50
Expensify/Expensify Issue URL:
Issue reported by: ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693252930657099
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01a57e2ba43c540555
Upwork Job ID:<PHONE_NUMBER>486952960
Last Price Increase: 2023-09-21

This is different but I believe same rca as https://github.com/Expensify/App/issues/24555 that is goimg to be merged soon

I'm getting a different error on all iOS devices due to this
https://github.com/Expensify/App/assets/59587260/718b4a8d-ee78-4dbd-abf0-900898c889dd

Have posted here to get help reproducing this so I don't continue to be a blocker.

Unable to reproduce on iOS v1.3.68-15
https://github.com/Expensify/App/assets/22508304/93107c83-57af-4927-9fa4-1bd87581e2e7

Not overdue!

Not overdue!

Proposal
Please re-state the problem that we are trying to solve in this issue.
Dev: IOS -The main composer disappears when the thread message edit composer is open
What is the root cause of that problem?
Bug 1: Why composer didn't shown at all? As per the recording we can see that there is no keyboard at all, but we hide/show main composer based on the keyboard visibility. As the simulator doesn't contain any keyboard there's a high chance that keyBoardWillHide is not called at all.
https://github.com/Expensify/App/blob/f65c58e2ccaf9204fec93852c5fb4e6b0667926f/src/libs/setShouldShowComposeInputKeyboardAware/index.native.js#L22

I'm also not able to re-produce this.

Bug 2: Composer getting pained a bit late as per this comment - https://github.com/Expensify/App/issues/26577#issuecomment-1717383557
https://github.com/Expensify/App/blob/f65c58e2ccaf9204fec93852c5fb4e6b0667926f/src/libs/setShouldShowComposeInputKeyboardAware/index.native.js We handle the main composer visibility in this based on the parameter shouldShow
The values can be true or false but we are never conditioned to the value true whereas we call the function with value true here https://github.com/Expensify/App/blob/f65c58e2ccaf9204fec93852c5fb4e6b0667926f/src/pages/home/report/ReportActionItemMessageEdit.js#L402 which is calling the function correctly but function does nothing :/
Final RC is, composer visibility depends on keyboard visibility which takes a bit of time because of the listener's callback needs to be called and then again composer visibility changes required.
What changes do you think we should make in order to solve the problem?
We can have a condition if shouldShow is true we reset the composer visibility in this file
https://github.com/Expensify/App/blob/f65c58e2ccaf9204fec93852c5fb4e6b0667926f/src/libs/setShouldShowComposeInputKeyboardAware/index.native.js
if(shouldShow){
    Composer.setShouldShowComposeInput(true);
}

Which show the composer whenever the ReportActionItemMessageEdit component looses focus on the composer.

There might be a little jerk because of component rendering while keyboard is closing, which I feel ok and oddly noticeable on mobile screen. Better than showing
late right?

What alternative solutions did you explore? (Optional)
NA
https://github.com/Expensify/App/assets/59088937/ac8f3871-a5bd-47a0-9984-66fb7b4853c2

Is this issue still reproducible on main? I wasn't able to reproduce on the latest main

I think this issue was fixed already. We can close this

We show composer after hiding keyboard if keyboard is visible. If keyboard isn't visible, we show the composer instantly. This is an intentional behavior.

@s-alves10 the point is composer should show instantly when we close the keyboard... if you see the video it's taking a few seconds delay to show. That's a bug.

Closing as no longer a bug.


Incorrect Windows service name

The Windows service name is "On-premises data gateway service", not "Power BI Enterprise Gateway Service"

@ghRSampei Can you please provide the URL of the documentation that you are following where the service name is incorrect?

I’m sorry Peter, but it’s been more than 3 months and I can’t find the page anymore. I tried the History on my browser but it’s only going back to 4/30; I did this on 4/15.
From: Peter Hecke<EMAIL_ADDRESS>Sent: Thursday, July 25, 2019 7:52 PM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: ghRSampei<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Incorrect Windows service name (#327)
@ghRSampei https://github.com/ghRSampei  Can you please provide the URL of the documentation that you are following where the service name is incorrect?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/powerapps-docs/issues/327?email_source=notifications&email_token=AL2ZSJHKUQ4AOXCSLCRJMCTQBI4C3A5CNFSM4HGAY3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD23C22A#issuecomment-515255656 , or mute the thread https://github.com/notifications/unsubscribe-auth/AL2ZSJFWNXTBBUDDQAC2ESDQBI4C3ANCNFSM4HGAY3IQ .  https://github.com/notifications/beacon/AL2ZSJB3TDYMH4Q4IIXJYI3QBI4C3A5CNFSM4HGAY3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD23C22A.gif

@phecke @ghRSampei - it looks like it's https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/gateway-reference.

Yes, thank you. It’s the 3rd question in the FAQ section.
From: Michael Blythe<EMAIL_ADDRESS>Sent: Friday, July 26, 2019 4:51 PM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: ghRSampei<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Incorrect Windows service name (#327)
@phecke https://github.com/phecke  @ghRSampei https://github.com/ghRSampei  - it looks like it's https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/gateway-reference.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/powerapps-docs/issues/327?email_source=notifications&email_token=AL2ZSJGF2VIHY3LQKFZ7URDQBNPTTA5CNFSM4HGAY3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD25V2HY#issuecomment-515595551 , or mute the thread https://github.com/notifications/unsubscribe-auth/AL2ZSJDZIXQEPG37SALLA63QBNPTTANCNFSM4HGAY3IQ .  https://github.com/notifications/beacon/AL2ZSJABH4WYD7UNKXMGNDTQBNPTTA5CNFSM4HGAY3I2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD25V2HY.gif

Thanks for reaching out. The content probably relates to this article and it's updated. Please reach out to updated appropriate topic feedback if any further feedback.


Skip over non-envvar lines

.env files may contain lines that don't set environment variables. For example, I use autoenv in order to automatically activate the current project's Python virtual environment. I also set per-project aliases in .env.
dotenv raises an error when it encounters lines that don't set envvars:
/usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/parser.rb:63:in `parse_line': Line "source activate osf" doesn't match format (Dotenv::FormatError)
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/parser.rb:47:in `block in call'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/parser.rb:46:in `each'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/parser.rb:46:in `call'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/parser.rb:36:in `call'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/environment.rb:13:in `load'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv/environment.rb:9:in `initialize'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:15:in `new'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:15:in `block (2 levels) in load'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:59:in `ignoring_nonexistent_files'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:14:in `block in load'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:46:in `block in with'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:45:in `each'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:45:in `reduce'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:45:in `with'
        from /usr/local/lib/ruby/gems/2.4.0/gems/dotenv-2.2.0/lib/dotenv.rb:13:in `load'
        from /usr/local/lib/ruby/gems/2.4.0/gems/docker-sync-0.2.0/lib/docker-sync/sync_manager.rb:19:in `initialize'
        from /usr/local/lib/ruby/gems/2.4.0/gems/docker-sync-0.2.0/tasks/sync/sync.thor:30:in `new'
        from /usr/local/lib/ruby/gems/2.4.0/gems/docker-sync-0.2.0/tasks/sync/sync.thor:30:in `start'
        from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.19.4/lib/thor/command.rb:27:in `run'
        from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.19.4/lib/thor/invocation.rb:126:in `invoke_command'
        from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.19.4/lib/thor.rb:369:in `dispatch'
        from /usr/local/lib/ruby/gems/2.4.0/gems/thor-0.19.4/lib/thor/base.rb:444:in `start'
        from /usr/local/lib/ruby/gems/2.4.0/gems/docker-sync-0.2.0/bin/docker-sync:14:in `<top (required)>'
        from /usr/local/bin/docker-sync:22:in `load'
        from /usr/local/bin/docker-sync:22:in `<main>'

Would the maintainer(s) be open to skipping these lines rather than raising an error?

For what it's worth, both Foreman (https://github.com/ddollar/foreman/blob/5f5502efed74c68f5cf381d38b2ad497676837ec/lib/foreman/env.rb#L8-L18) and honcho (https://github.com/nickstenning/honcho/blob/6bad0da2806231ac8f3a07d76847a566b96745e6/honcho/environ.py#L73-L99) implement the suggested behavior (skipping lines that don't set envvars).

Is this something the maintainers would be willing to change? If so, I could work on a PR.

Hey @sloria, thanks for the suggestion. I'm not opposed. My only concern is that it might lead to unexpected behavior for people that don't realize they have the format wrong, but I think I'm ok with that.
Feel free to open a PR!


Text messages possible?

First of all: Thanks for all your work!!!
I use my raspi 3 with original 7"-touchscreen to experiment with your project. I'm not very experienced with linux or raspi, but a faithful reader of 'make' and c't ;-)
I want to send not only images but also text messages to the raspi. I understand, that i can send them as a caption of an image, but independant of the config-entry "senderAndCaptionDuration" the caption disappears after some seconds. Ok, i could write it an a sheet and take a picture ;-) but is there an easyer way to let the TeleFrame show text messages?
Best regard
Hansruedi

I also thought of something like this already. Just a grey/whatever background and a nice font with auto-size to fit the text to the available space.

I also thought of something like this already. Just a grey/whatever background and a nice font with auto-size to fit the text to the available space.


fixes mismatching original redirect uri

fixes #121
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Other, please describe:

[x] You consent that the copyright of your pull request source code belongs to Authlib's author.

close it. I've fixed it in https://github.com/lepture/authlib/commit/177345d2447b8c18702ee675f4d7ee6e2a493feb
Thanks.


Hardware testing framework

Right now we can check whether electronic components (and our firmware drivers for them) are working by using the STM32Cube IDE's debugger. Once we get them to work, we will want an easier way to repeat basic unit tests of sensor & driver functionality, both for regression testing, unit testing for V&V, and troubleshooting of hardware boards.
The following overall approach is proposed as a strawman for critique and discussion:

We will create one or more main.cpp programs to exercise our various electronic components.
We will use send some data about the component over a serial connection to a computer. For example, for sensors we will just send sensor readings. (Or will we need to send slightly richer data, e.g. structs?)
We will print that data on the computer.

For 1), I can think of two possible approaches: a) We create one main.cpp program (and a corresponding build target) for every single component we want to make a test for. This would be an incredible headache to manage as far as STM32Cube MX configurations ans STM32Cube IDE configurations; and it would require re-uploading a new firmware for every test we want to run. b) We create one main.cpp program which contains test code for all components, we upload it once, and it runs one test at a time which will be selected by some data we send it over the serial connection from the computer.
For 2), I can think of two possible approaches: a) We keep things as simple as possible for the serial connection and use printf or sprintf or their equivalents and write ASCII representations of our data directly over the serial connection. b) We allow more flexibility for the data sent to the computer from tests by reusing some of my communication protocol code (for data framing and message serialization) so that we can send arbitrary data as raw bytes; the arbitrary data would have to be serialized and deserialized, e.g. as protocol buffer messages defined for test code.
For 3), I would suggest that we just write a script which uses some of our backend code and just prints received data to stdout. We could use command-line args to specify any special behavior (e.g. if it needs to send the firmware a command code of which test to run for option 1b).

Due to the complexity of this issue and the ability to run manual tests for now, we are not prioritizing it in the near term. @renjipanicker Whether/how to prioritize this in the longer term is probably a decision for you/your team.


Panzoom breaks on Jquery 3.4.1

Hi Timmy
When i use panzoom with jquery 3.1.0 its works perfectly fine but when i tried with jquery 3.4.1 then I am getting below issue
"Cannot read property 'replace' of undefined"
I think its something related with $_.cssProps

Thanks for opening an issue. Panzoom has recently been rewritten to remove its jQuery dependency. The old version that is a jQuery plugin is no longer being maintained. I plan on making a jQuery wrapper so the new Panzoom is still easy to use as a jQuery plugin, but I think it's safe to say it won't have this particular issue as it won't be using $.cssProps.


Log File output + 5 auto saved log files

Add user input in settings page to alter number of auto saved log files

each autosave is a session of the controler


Switch to nbviewer and fix broken link

I think it might be preferable to link to nbviewer.jupyter.org instead of Github (e.g. on my mobile browser Github displays only raw text files of notebooks). Moreover, I discovered a broken link in the documentation.

Looks good to me, thanks for catching the link!


Bugfix for verbosity flags

This started out as "hey, why doesn't -v work?"
and grew into an overhaul of how the CLI interacts with DI.
Comments inline

One of the overall outcomes here is that flag parsing happens before DI runs, which means the user can actually manipulate the parameters of object construction.

Looks great, just that missing vendored package and I'll merge...

Current coverage is 40.70% (diff: 53.42%)

Merging #99 into master will increase coverage by 3.02%

@@             master        #99   diff @@
==========================================
  Files            97         98     +1
  Lines          4859       4835    -24
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1831       1968   +137
+ Misses         2840       2671   -169
- Partials        188        196     +8

Powered by Codecov. Last update 8ad10c2...bbc0fa8


Allow users to ignore config files in the package.

Adds the CROSS_IGNORE_CARGO_CONFIG environment variable, which if set will mount an anoymous data volume for each .cargo subdirectory for the current directory and any parent directories up to the workspace root. If the build is called outside the workspace root or at the workspace root, only mount at the $PWD/.cargo.
Partially addresses #621.

I've moved the configuration to Cross.toml, but this still needs to create the .cargo directories (or better yet, check if they exist and only mount them if they do).

I'm likely going to merge this into a PR with #931, since the two are complimentary and I also need that to support allowing full passing of Cargo configuration files to cross. So, we can therefore have the default behavior (CARGO_HOME and the project config files are passed), the behavior where everything except CARGO_HOME is skipped, and allowing everything to be included.

Superseded by #931, which now includes this functionality.


image_picker - Images from Drive are returned null

When selecting images from any location on Drive the return value is always null.
Tested with image_picker v0.4.5 on Android 8.1.

Just saw v0.4.6 is in the pipeline which fixed this problem but hasn't been released yet.


AudioKit stops when setting up a custom AURenderCallbackStruct

I am using AudioKit but i also want to use a custom AURenderCallbackStruct.inputProc in order to process incoming data. I have just realized that this seems not to work. So whenever i activate one (AudioKit.start() or AudioUnitInitialize) the other stops to work.
Is there any best practice to achieve this? Or is the only way to use the AKMicrophone?

I don't know the answer to this question.

What a pitty. Never used AudioKit besided regular AudioUnit?

@mlostekk I just posted this on SO. I could get a render callback (on the output node). I hope it helps.


isCurrentUserSick is not used properly.

isCurrentUserSick is never set to true.
Probably need to isCurrentUserSick:=true when user self reports.

Also I have a few questions about the code.

Why CurrentUserExposureNotifier needed if it's possible to notify right when report is received from the backend?
Why do you need to save self-reports locally and later upload if it's possible to upload them right when they are generated?

Why do you need to save self-reports locally and later upload if it's possible to upload them right when they are generated?

I imagine it would have something to do with HIPPA Emergency Access Procedures or Data security restrictions. Anything with ePHI or PHI would need to be accessible in the instance of a power outage or data loss.


[feature request] Dynamically add requests to Pool

I have a case where I need to dynamically add requests to the Pool, but from what I see current Pool implementation doesn't allow that.
Use case would be like:
$pool = new Pool(
  $client,
  [$client->createRequest('GET', 'http://www.example.com')],
  ['complete' => 'parser']
);
$pool->wait();

function parser(CompleteEvent $e) {
   global $pool; // sorry for global, just for sake of conciseness
   /// handling
   /// ...
   /// some elements were discovered and need to be added to the Pool:
   $pool->add($client->createRequest('....'));
   $pool->add($client->createRequest('....'));
   $pool->add($client->createRequest('....'));
}

It's not really necessary to use an AppendIterator. The normal ArrayIterator is capable of adding requests itself. See my comment at https://github.com/guzzle/guzzle/issues/946#issuecomment-92018988 for a full example or this gist for a more in-depth example of a comparison between generator, retry and sequential send with guzzle.


DISTX-397 DE HA template co-locate JN and ZK nodes to masters and manager

CB-5660 added the ability to have JN across node groups.
Tested the template and the fix for CB-5660 works for the DE HA template in a private stack.

Thanks @keyki


Private transaction executed at most once when sent to multiple builders

Hello, does this library support sending a transaction privately to multiple builders and ensuring it will only be executed once at most?
If I understand correctly, not all builders support the max block number parameter, but would it be possible to send a tx to many builders and send cancellation requests once it's been executed once?

Hi, lil0uuu
A couple things:

To my understanding block builders which do not support the max block parameter mostly support only single execution, but I understand it is a concern that you want to be sure that your transactions execute at most one time, ideally without consulting with often unreliable documentation.
In order to add support in the way you want, a somewhat complex lifecycle of events must occur.

The transactions must be sent out to each block builder and each transaction stored to tell builders what to cancel later.
We must either wait for the next block to occur to see whether it has been included or directly query each builder if possible.
We must then broadcast out cancellation requests to all builders upon finding the receipt of our transaction in the next block.

While possible to implement this, it is a little finnicky and unreliable (if you have a slow internet connection you might not even be able to cancel your orders in time). I would prefer a more reliable solution to problems like this. As such I will have to dedicate a bit more thought and work to it.
I do not have a huge amount of time at the moment to dedicate to the library, as such while I understand the concern and would like to help, it may be a little while. (However, if you have any suggestions or implementation ideas for things such as this, I am more than happy to review ideas / pull requests)
I do intend to improve the transparency of the whole block builder RPC lifecycle, including doing things such as adding support for getting the status of blocks you submit for builders who allow this such as TitanBuilder

I apologise if this isn't the "yes, it always works that way!" you were looking for, however do know that now that you have brought the issue to light, it will be top priority for any time I spend developing the lib.

Thank you for the quick and detailed response!
I was thinking of the same implementation and I agree it's not perfect... It would be simpler if all builders supported the max block parameter. It's also unclear to me whether all builders support cancelling private transactions? For instance, rsync doesn't seem to support it https://rsync-builder.xyz/docs. How does that work in practice then? Is it not possible to cancel transactions with this library either?
It would be great if you can prioritize this! None of the existing python libraries seem to support private and fast transactions executed at most once, and it feels like a feature that many people could be interested in.

That is all ok!
It is true that there are some builders which do not support cancel methods in their native RPCs and as such nothing can cancel them.
However there is a solution in the form of MEV-Bundles, every builder supported by MEV-Share is able to have it's block number specified, as such you can specify that it only will be executed in one block. Due to advancements in the MEV protocol, I have to adjust how the library interacts with it (you can no longer submit MEV bundles directly to builders, but rather through the Flashbots protocol with builders specified in the privacy section), but you should have a solution to your problem once it is fixed.

An addendum,
It seems many of the "supported" endpoints for MEV-Share are only "supported" in that they support receiving transaction refunds. It is the unfortunate reality of the world that if a bundle builder does not support v0.1 of the MEV protocol, or natively support cancellation or block specification, you cannot have a guarantee your transactions will only be included in one block.
This is something that has to be dealt with on the side of the block builders who create their APIs, since if the support isn't there via any channel there is no way for any library to circumvent it.


Downstream release of the odo cli

@girishramnani @mohammedzee1000 Can you please provide the detailed description.

As this is downstream, i cannot give out too much
But basically, we are almost done with this
There is a  ticket up in the release pipeline which is waiting on QE approval (docs is already done). Once this is done, we can push it to redhat cdn.
Documentation is being updated accordingly in internal release repo.

The ticket is now ready for push to redhat cdns, pinged and waiting internal  team member to ship it

the ticket is now shipped live on redhat cdn
/close


Packaging broken

Running Ubuntu 22.04 with Nvidia proprietary driver 515. It appears that the APT packages break between 510 and 515 regarding NSCQ. While I did not install the package myself (probably came along with CUDA, cuDNN or some other ML/GPU computing related library/toolkit), my system is currently broken due to libnvidia-nscq-xxx. I am unable to update, upgrade, fix or install anything due to this package.
Attempting to install the package results in the following error:
(Reading database ... 228886 files and directories currently installed.)
Preparing to unpack .../libnvidia-nscq-515_515.86.01-0ubuntu<IP_ADDRESS>_amd64.deb
...
Unpacking libnvidia-nscq-515 (515.86.01-0ubuntu<IP_ADDRESS>) ...
dpkg: error processing archive /var/cache/apt/archives/libnvidia-nscq-515_515.86
.01-0ubuntu<IP_ADDRESS>_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-nscq.so.515.86.01', wh
ich is also in package libnvidia-nscq-510 515.86.01-0ubuntu<IP_ADDRESS>
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-nscq-515_515.86.01-0ubuntu<IP_ADDRESS>_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I was told that the problem lies in moving from multiverse to restricted. I have restricted enabled yet it does not solve the issue.

Based on the apt policy output on stackexchange, this .deb package appears to be coming from Canonical's repository rather than NVIDIA's CUDA repository. I will reach out to the Ubuntu maintainer to see if this is expected.
Out of curiosity, can you please elaborate on your hardware setup? NSCQ is an optional dependency for DCGM and intended for DGX (and similar) multi-GPU machines, see: https://docs.nvidia.com/datacenter/tesla/hgx-software-guide/#nscq


[performance] Prevent string conversion in Custom Element setAttribute methods, accept numerical values.

Historically, DOM elements have a problem: their attributes must be coerced into strings. When you set them (for example you set a style attribute on an element) the values are converted from their previous form into strings (for example, you set 'style="width: "+someVariable+"px"' in some innerHTML string, or you call setAttribute('style', 'width: '+someVariable+'px') on an element. someVariable might be a number, and you've converted it into a string in order to set an attribute on an HTML element.
Well, with Custom Elements, there's a way to avoid this. When you design a Custom Element, it is possible to override setAttribute and getAttribute to make them do what you want.
For example, we have a custom element that when used in HTML can be written like <motor-node position="20 30 40"></motor-node>.
But, if we get a reference to the element (f.e. with jQuery const node = $('motor-node')[0]), then we can call setAttribute on it to set an attribute, but because we made the definition of setAttribute, we can override the super method, and we can accept anything we want into the method.
For example, we want to pass numbers in:
const position = [20, 40, 50]
const node = $('motor-node')[0]
node.setAttribute('position', position)

What we can do internally is take those number values, apply them directly to the node's transforms, send them directly to the WebGL renderer without ever converting them to strings, and we can prevent the super.setAttribute call and therefore prevent the HTML engine from doing convert-to-string routines.
With some careful bookkeeping, we can have super.setAttribute calls happen only on getAttribute calls, so that string conversion only happen if and only if introspection happens on the elements (for example devtools needs to show what the values are in the element inspector, or someone else calls getAttribute to get some values).
The benefit of this would obviously be saved CPU time for WebGL. Unfortunately, for DOM rendering, the string conversions are currently required because that is how CSS transforms currently get their values (although that will soon change with TypedOM whenever that eventually comes out sometime in the possibly not soon enough future).
But, for WebGL apps, we can make HTML element that perform even better than DOM.
This will be super great when/if React stops manually coercing values to strings or at least gives us an option to disable it because then raw JavaScript values can be passed to Custom Element APIs and we can benefit from the performance benefit of avoiding string conversions.

[ ] Be sure to consider how doing something like el.attributes.foo.value = "foo". That should also then accept non-strings for consistency.


Add download queue data button

This PR:

Adds a button and endpoint to download course queue data as a csv on the course page

This is only viewable to course staff, which I have tested

Changed a comment that was probably not changed after copy/paste to say "remove" instead of "add"

Here is an example of what the download would look like given fake data.  Unfortunately, I couldn't upload to GitHub as a csv.
Here is the SQL query that this was based off of:
SELECT
  questions.id AS id,
  courses.name AS CourseName,
  queues.name AS QueueName,
  u_asked.netid AS AskedBy_netid, u_asked.universityName AS AskedBy_RealName,
  u_answered.netid AS AnsweredBy_netid, u_answered.universityName AS AnsweredBy_RealName,
  topic,
  CONVERT_TZ(enqueueTime, '+0:00', 'US/Central') AS enqueueTime,
  CONVERT_TZ(dequeueTime, '+0:00', 'US/Central') AS dequeueTime,
  CONVERT_TZ(answerStartTime, '+0:00', 'US/Central') AS answerStartTime,
  CONVERT_TZ(answerFinishTime, '+0:00', 'US/Central') AS answerFinishTime,
  comments, preparedness,
  questions.location AS UserLocation,
  queues.location AS QueueLocation,
  CONVERT_TZ(queues.createdAt, '+0:00', 'US/Central') AS Queue_CreatedAt,
  queueId, courseId
FROM questions
  INNER JOIN queues ON questions.queueId = queues.id
  INNER JOIN courses ON queues.courseId = courses.id
  INNER JOIN users u_asked ON questions.askedById = u_asked.id
  LEFT JOIN users u_answered ON questions.answeredById = u_answered.id
WHERE courseId=6
ORDER BY enqueueTime DESC

Adding onto Nathan's comments, we should also add some tests for this new endpoint

@nwalters512 as for your point about downloads being in another section, I think at this point @wadefagen just wants downloads to be pushed out as quick as possible - so I guess think of this as a temporary solution, and later I can make it nicer to be able to download per queue as well.

Now ready for review again.

Sequelize is weird in that if you specifically include an attribute in a related model, it doesn't exclude other attributes.  So in the getColumns function, I whitelist the fields we want to display.
Added tests for the endpoint.
RealName is changed to UniversityName
Moved all logic to api except for the download

Here is an updated version of an example csv.

Tested on staging.  Everything appears to be working properly and correctly (times are verified to be in CST as well).

Going to give this a final look over!


upgraded to flutter 3.7 and had this issue ?

Could not build the precompiled application for the device.
Uncategorized (Xcode): Command CompileSwift failed with a nonzero exit code
Swift Compiler Error (Xcode): Type 'WKDataDetectorTypes' has no member 'WKDataDetectorTypes'
/Users/kp/.pub-cache/hosted/pub.dev/flutter_inappwebview-5.7.2+3/ios/Classes/Util.swift:85:20
flutter doctor output:
[✓] Flutter (Channel stable, 3.7.3, on macOS 12.3.1 21E258 darwin-x64, locale en-IN)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.75.1)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

Seems the error is caused by flutter_inappwebview, which is not maintained by the Flutter team, maybe it's a good idea to open this issue at their repository: https://github.com/pichillilorenzo/flutter_inappwebview

but  i am not using this dependency but i have noticed that i used a packages that uses this dependecy internally .

Hi @harryandroiddev
The issue is related to a 3rd party plugin rather than to Flutter itself. Please find the existing issues or open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.  If you disagree, please write in the comments, providing your flutter doctor -v, your flutter run -v,  your pubspec.yaml, a completed and minimal reproducible code sample that does not use 3rd party plugins and I will reopen it.
Thank you!


optimize bulk pub response to contain only failed entries

Signed-off-by: Mukundan Sundararajan<EMAIL_ADDRESS>Description
The BulkPublishResponse struct will only contain entries that have failed to publish with the corresponding error.
Internally on any error, the error field in the response is sent to be processed by Dapr runtime as needed.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #2260
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

stable cert tests are failing because of the struct field name change. Will add a PR to dapr/dapr and then try to use that in the stable cert tests ...

You left merge conflict markers in several go.mods
Please fix.
Also some certification tests are now broken due to this.

missed it in the number of go.mod files that had to be replaced. Have added a fix in the make command that helps identify which mod files have error during do mod tidy. Please see that PR #2373
Please review PR again.

@berndverst @ItalyPaleAle

Resolve conflicts
Create a dapr/dapr fork and include your changes, then replace dapr/dapr in certification tests

I have a separate fork ... but the changes from https://github.com/dapr/dapr/pull/5640 needs to go into dapr also so that the cert tests do not fail on not having context potentially for lock and pubsub APIs

@mukundansundar yes you must integrate the changes from dapr/dapr#5640 which is already merged.

just saw ... have done that ... now waiting for all tests to pass


Default btn and form field sizing inconsistent

Upon close inspection it seems that the default form input fields vary between 38-39px height. The default button height is is 39px. Can we make these consistent?

Can you give more examples of which are too big?

Also, the difference between the small and default buttons is not enough. We are using 36px and 39px. Bootstrap has a nice difference with 30px and 38px.

agree re:small buttons we can shrink those more.
The inputs have the exact same padding. Their not different, it's probably just a rounding issue. WE can move to use even pixels for padding on these

The goal would be that a default button and default inputs could be placed side by side and the heights match exactly.

@TheBlueDog can you send a screenshot where that's not the case?

I built Sketch symbols for prototyping based on the day pages. This is where I noticed the difference. I don't have it in code yet.

I think it won't happen in code. The rounding error comes when they fall in the middle of a pixel, chrome rounds down, or up depending on which is closest. But if they are inline with each other they will be rounded the same way, so shouldn't be an issue.
When you code it, let me know if you see the problem and we can patch the button padding to be more explicit.


Vulnerability roundup 96: gitlab-13.0.12: 2 advisories [9.1]

search, files

[ ] CVE-2020-13347 CVSSv3=9.1 (nixos-20.03)
[ ] CVE-2020-13335 CVSSv3=4.3 (nixos-20.03)

Scanned versions: nixos-20.03: fbd345dd005.
Cc @fpletz
Cc @globin
Cc @krav
Cc @talyz

See also: #101157, #100298, #99768, #96779

20.03 is frozen and EOL.
Closing.


Add backup_url to load and remove legacy loading functions

Fixes #1484

Closing in favor of https://github.com/scverse/scvi-tools/pull/1505


Decoded token access from strategy+

Is what ever is returned from the strategy available on the request? I was hoping to access the decoded token in the guard. is this possible?

I am closing this now. Feel free to reopen or submit a new issue if it still needs to be resolved. @teaglebuilt


Narrowing conversion in v0.9.1 - Found using clang

Using v0.9.1 I cannot build using clang. I get the following output. It would be great if narrowing conversions where handled more explicitly. It looks like there is no bug in the code at hand, but in general I think it's good to avoid doing to crazy things to keep things working nicely.
/usr/include/libusb-1.0/libusb.h:732:3: warning: zero size arrays are an extension [-Wzero-length-array]
[0] /* non-standard, but usually working code /
^
/usr/include/libusb-1.0/libusb.h:763:3: warning: zero size arrays are an extension [-Wzero-length-array]
[0] / non-standard, but usually working code /
^
/usr/include/libusb-1.0/libusb.h:1257:3: warning: zero size arrays are an extension [-Wzero-length-array]
[0] / non-standard, but usually working code */
^
src/uvc-v4l2.cpp:164:43: error: non-constant-expression cannot be narrowed from type 'int' to '__u8'
(aka 'unsigned char') in initializer list [-Wc++11-narrowing]
uvc_xu_control_query q = {xu.unit, control, UVC_GET_CUR, static_cast<uint16_t>(size), re...
^~~~~~~
src/uvc-v4l2.cpp:164:43: note: insert an explicit cast to silence this issue
uvc_xu_control_query q = {xu.unit, control, UVC_GET_CUR, static_cast<uint16_t>(size), re...
^~~~~~~
static_cast<__u8>( )
src/uvc-v4l2.cpp:170:43: error: non-constant-expression cannot be narrowed from type 'int' to '__u8'
(aka 'unsigned char') in initializer list [-Wc++11-narrowing]
uvc_xu_control_query q = {xu.unit, control, UVC_SET_CUR, static_cast<uint16_t>(size), re...
^~~~~~~
src/uvc-v4l2.cpp:170:43: note: insert an explicit cast to silence this issue
uvc_xu_control_query q = {xu.unit, control, UVC_SET_CUR, static_cast<uint16_t>(size), re...
^~~~~~~
static_cast<__u8>( )
3 warnings and 2 errors generated.
make: *** [obj/uvc-v4l2.o] Error 1

Can you be specific about what version of clang you are on? We see narrowing conversion errors from time to time, but our continuous integration infrastructure usually lets us know. Between Travis and Appveyor, every commit gets built on clang, GCC, and the vs2013 compiler.

Cool, yeah I saw you also build on Mac. Very nice indeed. Anyway this was
on clang 3.6
Den 4 apr 2016 17:32 skrev "Dimitri Diakopoulos"<EMAIL_ADDRESS>
Can you be specific about what version of clang you are on? We see
narrowing conversion errors from time to time, but our continuous
integration infrastructure usually lets us know. Between Travis and
Appveyor, every commit gets built on clang, GCC, and the vs2013 compiler.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/94#issuecomment-205352399

Ah, you've exposed a gap in our testing. We currently only test the V4L2 backend on gcc, the LibUVC backend on clang, and the WMF backend on Visual Studio, which lets stuff like this sneak in sometimes.

Should now be fixed in 2b19cde89b42ff325d407e4822d4b8ee8e149ee4

Great! Thanks a lot for the quick fix guys. :-)
Short git hint of the day: You can easily rebase your branch to make the history cleaner and get rid of the "merged in master into my branch"-commits.


Implement Simple UI for TJED

We should have a simple UI for TJED, allowing users to query TJED via their web browser.

We should have something on the UI that allows for "sentence parsing" - the ability to check for multiple words in a Japanese sentence provided, and attempt to break them down into smaller, more digestible parts.

Sentence parsing will become a microservice.


Allow sapi retry delay method override

requires: https://github.com/keboola/storage-api-php-client/pull/180
ref: https://github.com/keboola/syrup/issues/118

I would probably do this in Docker Runner, so it's easier to modify if needed.

ok, we can remove the feature check from here.

resolved by https://github.com/keboola/docker-bundle/issues/247


fixed bug with wrong function name being included

Fixed a bug with the most recent merge where the called function name was wrong.

Looks good. Thank for fixing bug


Not showing notification banner when app closed Android

I don't receive notif when app is closed and not pass by initial notif (undefined)
exemple of send
{
"data":{"test":"data de test"},
"priority":"high",
"notification":{"title":"NOTIFY","body":"content notif","click_action":"huhschool.story"},
"to":"deviceToken"
}
and it works when app background
RN : 0.33
RN-fcm 2.3.2
Android 6 device
App not running

investivating

@justineraze are you seeing notif in tray?

We are having the same problem. We see the notification in the tray but it does not popup/show banner.
example of send:
{
"to" : "/topics/test",
"priority": "high",
"notification" : {
"body": "HELLO",
"title" : "HELLO"
}
}
This works when the app is in foreground or background because we create a local notification with priority: "high".
Even though we send "priority": "high" with the remote notification it dos not show the banner.

that's the limitation of FCM. They don't show banner at all.
One work around would be creating a message receiver in native code

@evollu: Do you know if this problem also happens with GCM?

GCM doesn't build notification for you at all. So you need to build it yourself anyway

I guess Firebase doesn't want to do it is because android notification is so rich that building a default one will cause more feature request?

Hi, I have tried to get remote notifications to work when the app is closed both with GCM and FCM, but neither of them showed any notification. It worked when the app was active or in background.
Could it be an error in the Android Manifest?
One interesting thing that I have noticed, that remote notifications arrive even when the app is closed on Android version 4. However on version 6 - no sign, no sound, nothing.
@evollu: Can you elaborate on the limitation of FCM? What would a message receiver in native code have to cover that this module does not?
My AndroidManifest.xml looks as follows:
A<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="---my.package---">

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/>
    <uses-permission android:name="android.permission.VIBRATE"/>

    <application
      android:name=".MainApplication"
      android:allowBackup="true"
      android:label="@string/app_name"
      android:icon="@mipmap/ic_launcher"
      android:theme="@style/AppTheme">

      <receiver android:name="com.evollu.react.fcm.FIRLocalMessagingPublisher"/>
      <receiver android:enabled="true" android:exported="true"  android:name="com.evollu.react.fcm.FIRSystemBootEventReceiver">
        <intent-filter>
          <action android:name="android.intent.action.BOOT_COMPLETED"/>
          <action android:name="android.intent.action.QUICKBOOT_POWERON"/>
          <action android:name="com.htc.intent.action.QUICKBOOT_POWERON"/>
          <category android:name="android.intent.category.DEFAULT" />
        </intent-filter>
      </receiver>

      <service android:name="com.evollu.react.fcm.MessagingService">
        <intent-filter>
          <action android:name="com.google.firebase.MESSAGING_EVENT"/>
        </intent-filter>
      </service>

      <service android:name="com.evollu.react.fcm.InstanceIdService" android:exported="false">
        <intent-filter>
          <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/>
        </intent-filter>
      </service>

      <activity
        android:name=".MainActivity"
        android:label="@string/app_name"
        android:launchMode="singleTop"
        android:configChanges="keyboard|keyboardHidden|orientation|screenSize">
        <intent-filter>
            <action android:name="android.intent.action.MAIN" />
            <category android:name="android.intent.category.LAUNCHER" />
        </intent-filter>

        <intent-filter>
            <action android:name="fcm.ACTION.HELLO" />
            <category android:name="android.intent.category.DEFAULT" />
        </intent-filter>

      </activity>
      <activity android:name="com.facebook.react.devsupport.DevSettingsActivity" />
    </application>
</manifest>

any update? I'm still getting the same error.

try adding android:exported="true" for both service?

I solved the problem sending from the server (I'm using python and pyfcm) to fcm with the following object:
data_message = {
    "custom_notification": {
        "title" : "Test title",
        "body" : "Test body",
        "color": "#00ACD4",
        "priority": "high",
        "show_in_foreground": True
    }
}

ah. i guess your issue is that the banner doesn't show up? FCM only creates system tray icon, no banner. so "custom_notification" is the solution here

Yeah that is the solution since all notification foreground/background/closed will be received on FirebaseMessagingService.

@JohnProg right because that is just JS code. If you want to show local notification when app is closed, use schedulelocalnotification

Not receiving notification in tray when app is closed even after using custom notifications on the server end. I am using pyfcm on server and used data message as suggested.

@JohnProg can you please help as you used the same code on server

Got it working, it was just issue with the android phone. Thanx ")

@arun542 would you mind sharing you code on how you setup the pyfcm. I'm totally lost

@JohnProg
I'm using Python also
I tried:
    payload.update({
        "custom_notification": {
            "title" : "Test title",
            "body" : "Test body",
            "color": "#00ACD4",
            "priority": "high",
            "show_in_foreground": True
        }
    })

    print payload

    result = push_service.notify_single_device(registration_id=test_id,
                                               message_body=payload['short_message'],
                                               message_title=payload['title'],
                                               data_message=payload, sound='default',
                                              )

Result:
{u'name': u'3f14282126', u'title': u'Test Lab/2017-09-19/Assignment test Lab', u'image': u'', u'custom_notification': {u'body': u'Test body', u'color': u'#00ACD4', u'priority': u'high', u'show_in_foreground': True, u'title': u'Test title'}, u'messsage_type': u'HOMEWORKS', u'message': u'Science and computer homework, pass it tomorrow 9am in the Senior high building', u'short_message': u'Assignment test Lab'}
and it succeeded, but still I didnt get any banner just a notification in tray.  Any idea?

@JohnProg Working now thanks!

@JohnProg tried this when app is on background but it won't work. custom_notification doesnt work on background?

@JohnProg Its working now I found out that "custom_notification" won't work if "notification" exist

@jvfiel can you explain pls, i use custom_notifi in example code, notifi only show on tray, not show banner? Any help? Thanks.

@ducpt2 can you share your code here

@jvfiel i change server code become custom_notification, and it work. Thanks. But it seem like not a elegance way to push notifi (change server code, server code need to know device is ios or android). Or do you know another way? Thanks?

@ducpt2 if you want to know what device refer to http://www.reactnative.com/ios-and-android-device-information-for-react-native/


Invalid stat provided

🐞 bug report
Describe the bug
When i try to estimate a flask with 2 mods it gives me the Error: Invalid Stat provided: Explicit.Stat_3139816101

Exactly the same thing happens to me


The Tone.Player audio gets out of sync with the Tone.Transport timers.

I don't think this is a duplicate of https://github.com/Tonejs/Tone.js/issues/839. The two issues are similar.
As the title says, the Tone.Player audio sometimes gets out of sync with the Tone.Transport timers. This could happen when:

changing player.playbackRate
there is lag in the program
the duration of Tone.Transport.loopEnd is not equal to the duration of the player's audio buffer.

There ought to be a way to perfectly synchonize the looping in Tone.Transport with the audio player source. I thought about forking Tone.js and seeing if I can add an onended event listener to the original audio source, but I thought I might make this issue first.
Note, calling player.seek(0) or player.start(0) in Tone.Transform.on('loop', ...) does not work because it causes audio pops and lags/delays (see https://github.com/Tonejs/Tone.js/issues/1262)

As it turns out, the players need to have a sync() method called manually before their times are correct.
I'm reading through the docs -- this isn't meantioned anywhere. To know about this, one would have had to read through all the methods in the docs for player until they come across the sync() method and read what it does.
I think there are such things as usability "bugs", and this would be one of them.
Please consider:

having the players sync by default, as is the expected behavior to probably most devs using this library
the documentation needs to explain up front these sorts of "gotchas". When people go to the docs for things like the Player class, they need to be told hold to use the class, including all the gotchas and assumptions.


M1 Mac runtimecheck Errors

With the following code:
import nimsimd/runtimecheck

let
  cpuHasAvx* = checkInstructionSets({AVX})
  cpuHasAvx2* = checkInstructionSets({AVX, AVX2})

This fails to compile:
/Users/miguelmartin/.cache/nim/nimsimd_test_d/@m..@s..@s..@s..@s.nimble@spkgs2@snimsimd-1.2.5-9f919415ad69edb599c3362b0cc0fe0b044097c9@snimsimd@sruntimecheck.nim.c:130:10: error: invalid output constraint '=a' in asm
        :"=a"(eaxr), "=b"(ebxr), "=c"(ecxr), "=d"(edxr)
         ^
1 error generated.
Error: execution of an external compiler program 'clang -c  -w -ferror-limit=3 -pthread   -I/Users/miguelmartin/.choosenim/toolchains/nim-2.0.0/lib -I/Users/miguelmartin/repos/nim_playground/nimsimd_test/src -o /Users/miguelmartin/.cache/nim/nimsimd_test_d/@m..@s..@s..@s..@s.nimble@spkgs2@snimsimd-1.2.5-9f919415ad69edb599c3362b0cc0fe0b044097c9<EMAIL_ADDRESS>/Users/miguelmartin/.cache/nim/nimsimd_test_d/@m..@s..@s..@s..@s.nimble@spkgs2@snimsimd-1.2.5-9f919415ad69edb599c3362b0cc0fe0b044097c9<EMAIL_ADDRESS>failed with exit code: 1

System Details:

OS: MacOS 13.5
CPU: M1 Max
RAM: 64GB

Compiler version: 2.0

I have confirmed this works as expected on my M1 using nim c -r examples/runtimecheck.nim added https://github.com/guzba/nimsimd/pull/13
What is your compile command?

Ah, I'm guessing you are compiling as arm64. It is only possible to runtime check amd64 instruction sets. You'll need a when defined(amd64): block.

It seems related to choosenim not providing an arm64 build (https://github.com/dom96/choosenim/issues/318). I'll install the compiler myself.

Ah, interesting. Lets see if anything changes with a fresh compiler build. Fortunately Nim makes that relatively straightforward imo.

Compiling & installing the nim compiler worked to resolve this (I can now use pixie!). Apologies for the noise.

All good, glad that fixed things and hopefully choosenim stuff will be sorted out soon too.


🍎 config: expose FastlyConfig::from_str

in order to facilitate using viceroy_lib in tests, without needing to
write many fastly.toml files to the filesystem, we expose the
from_str constructor for FastlyConfig.
this patch is made with use cases like those described in #146 in
mind. cc: @GeeWee

error: method `from_str` can be confused for the standard trait method `std::str::FromStr::from_str`
  --> lib/src/config.rs:83:5
   |
83 | /     pub fn from_str(toml: impl AsRef<str>) -> Result<Self, FastlyConfigError> {
84 | |         toml::from_str::<'_, TomlFastlyConfig>(toml.as_ref())
85 | |             .map_err(Into::into)
86 | |             .and_then(TryInto::try_into)
87 | |     }
   | |_____^
   |
   = note: `-D clippy::should-implement-trait` implied by `-D warnings`
   = help: consider implementing the trait `std::str::FromStr` or choosing a less ambiguous method name
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#should_implement_trait

ah! we can already std::str::FromStr. :sweat_smile:
i see two options:

allow the lint, said trait implementation delegates to this. having an inherent method just makes this a bit more discoverable.
close this

I think we can either just close (the docs.rs page makes FromStr fairly prominent), or else add a doc comment on the struct itself mentioning the from_str constructor.

going to close this, 'twas a bit of a misstep on my part. sorry for the noise!


support for decimals dtype in adbc (duckdb tested)

Hi there!, I'm having an issue because duckdb defaults to decimal instead float:
:ok = Adbc.download_driver!(:duckdb)
{:ok, db} = Kino.start_child({Adbc.Database, driver: :duckdb})
{:ok, conn} = Kino.start_child({Adbc.Connection, database: db})
Adbc.Connection.query(conn, "SELECT 11.1111;")

>  {:error, %ArgumentError{message: "not yet implemented for format: `d:6,4`"}}

Sadly I couldn't replicate in sqlite, it seems it always uses float (even casting to decimal or numeric).
Thanks!

Hi @matreyes, thanks for reporting this issue. I’ll try to implement this today. :)

Perhaps it is worth bringing the Decimal library as a dependency for this one?

Perhaps it is worth bringing the Decimal library as a dependency for this one?

I agree. It'd be much easier to start from scratch or casting it to other types

Explorer does not support a decimal yet but we want to. There is an open issue.

Looks like this was recently^1 fixed^2 in adbc

Hopefully we can get an adbc 0.3.2 soon! :clap: :clap:

Hi @jc00ke, my plan is to implement all list types plus the struct one in Adbc.Column in this week (and more types if I have enough time), and then perhaps we can release a new version.
But I'm not sure if @josevalim has any plan for the next release, like if we're only going to release one once all types are supported in Adbc.Column. Below is the list of types that haven't implemented yet:

NANOARROW_TYPE_LIST
NANOARROW_TYPE_FIXED_SIZE_LIST
NANOARROW_TYPE_LARGE_LIST
NANOARROW_TYPE_STRUCT
NANOARROW_TYPE_SPARSE_UNION
NANOARROW_TYPE_DENSE_UNION
NANOARROW_TYPE_DICTIONARY
NANOARROW_TYPE_MAP
NANOARROW_TYPE_EXTENSION


Ab.type.migration

Types for core package.
the types are a bit wild in order to cover some edge cases so we can go over them and how they work a few days before the release
React package types are coming later today

@jonathantneal just checked the build and it's failing because in some areas we're using unknown scales for the theme scale color instead of colors
and the other instances are things that need casting to any because the react types aren't in yet


User-reported unhelpful error message

Program: https://code.world/blocks#P0ecZEhTn_SsBVq3sE58FhA
Comment:
What types are expected and what is there instead?
Message:
This program contains type errors

Type errors are supposed to be impossible in blocks.  In this case, a user-defined block with the type Picture fits into a slot designed for Number -> Picture.  The block should not connect.


Windows Firewall Rule not working properly

I enabled the windows firewall after installing the wmi_exporter and it wasn't working properly with the default rule. I had to change the firewall rule to not be specific to the wmi_exporter.exe program but rather to "All programs that meet the specified conditions"

We seem to have dropped this, but since it has been over two years, I'm not sure this is a problem any more. Feel free to re-open if it is still causing issues.


Matplotlib constraint

@oesteban Just want to check in before updating all the projects...
Niworkflows is constrained here to ~=3.3.1, but in downstream projects as >=2.2.0 (or similar). Is there a reason that we're stuck in the 3.3.x series? Should we do ~=3.3 everywhere so that we only avoid an API-breaking 4.0 bump?

The problem I was seeing was actually a problem with using python setup.py directly (nipreps/smriprep#270), but it seems like a good idea to do this consistently.

@mgxd was stuck with this too. It's probably safe to pin ~= 3.3 and make everyone's life easier


feat: convert iOS translations to Android format

Summary
Ticket: 🤖 | Determine localization approach
I couldn't find any obviously useful automated tools for converting between iOS Localizable.xcstrings and Android string resources, but it turns out it's fairly straightforward to staple something basic together myself.
Tradeoffs:

I'm using the iOS format as the source of truth here, because there's nothing in Android that can explicitly represent the "Needs Review" state that our workflow relies on.
Instead of generating Android IDs for new iOS strings eagerly, this will only copy translations for strings which are already defined on Android in English. This is both easier and more useful, since it lets us pick manually what ID makes the most sense.
The iOS string templating system and the Android string templating system aren't all that far apart, so it's not difficult to translate the easy cases over automatically.

I suspect but am not confident that multi-argument templates will also Just Work™.

There are several options for inline text formatting on Android, some of which might even be easy to handle here, but we are currently not doing any of them and doing string manipulation after the fact instead, so this needs to be a separate ticket.
Android plurals are a separate kind of resource entirely from Android strings; conveniently, we aren't using that subsystem at all yet, so I'm keeping things simple and ignoring that entirely for now.

Notes:

I've set things up so we can manually define localized strings separate from the automatically converted translations; if we define a key in the strings.xml it will be removed from strings_ios_converted.xml to avoid confusion.
I've flipped the switch to allow Android app-specific language preferences at the OS level, but if we want that functionality to be usable on Android 9-12 and not just 13+ we need our own UI for it, and I'm not going to preemptively do anything for that.
In the distant future we may benefit from linting on strings that are present in iOS but absent in Android, but right now we still have a ton of functionality that is simply not present in Android, so that would be incorrect to build now.

I've re-enabled the default lint for strings which have not been translated into all supported languages, though, which winds up being a lint on strings that are present in Android but absent in iOS.

Testing
Manually validated that the imported translations work for the languages I can check. (Neither my emulator nor my physical Android phone support Haitian Creole at all.)

There are definitely some strings for which light post-processing of the English text would make a decent ID, but I don't think R.strings.in_1d_hr_2d_min or R.strings.mbta_go_is_in_the_early_stages_we_want_your_feedback_as_we_continue_making_improvements_and_adding_new_features or R.strings.made_with_by_the_t would be all that great, and I'd rather let people come up with good IDs as they add new functionality than have them put up with merely tolerable IDs generated in a one-off eager migration.


Add configurable access for generated clients (#6374)

Add an option in graphqlrc.json to specify the access modifier of generated clients, the default access modifier is internal.
Closes #6374

 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.

I added a new property to AssertSettings so you can specify the access modifier. Also made changes to the GetAccessModifier method, so now only public and internal are supported (as private and protected classes are doesn't make any sense)

When looking at the snapshot ... only the client seems to be internal ... models and all other types are still public.

Fixed, now interfaces, enums, and other models (inputs, results, etc) can be made internal. However the method and properties generation we're not changed, since if you set the class to internal the methods and properties wouldn't be accessible outside the assembly.

When looking at the snapshot ... only the client seems to be internal ... models and all other types are still public.

Done, however the generated methods and properties are still public, I'll mark this PR as draft till a fix that. Let me know if the current changes are enough.

Thank you for contributing ... your PR is merged and we have integrated the changes into this release:
https://github.com/ChilliCream/graphql-platform/releases/tag/13.5.0-preview.24


Removed minSize dimension from data matrix writer.

Calling [writer encode:string format:kBarcodeFormatDataMatrix width:size.width height:size.height error:&error] would raise an NSInvalidArgumentException - "Can't find a symbol arrangement that matches the message. Data codewords: 5".
This is the same bug as identified here so same fix was applied.

Ported ea00f5a from ZXing


Revisit GitHub workflows

This PR updates current GH workflows.
Overall changes:

Refactor ruby-matrix
Add Ruby 3.2
Rename some gemfiles
Use ubuntu-latest
Should fix #2300

Specific changes

rack_2_2 has been deleted in favor to rack_2_0 to fit like rack_1_0
multi_json and multi_xml are tested once with ruby 2.7 (no major updates for these gems for a while now)
rack_1_0 is tested only under 2.7 (2 major version since, I think people move at least to 2.0 since)
rails_5_2 is tested only under 2.6
rails_7_0 has been updated to fit 7.0.0 versions
rack_3_0 has been updated to fit 3.0.0 versions

It's a step in the right direction thanks!


🚧 Dev ➾ review the e2e test implementation for taqueria-plugin-taquito.spec.ts to remove flaky tests

🔗 Epic|Feature Link
#1555
🚥 Definition of Done

[ ] 🎯 Planning and Design
[ ] 🏎 Dev Implementation Complete
[ ] ♾ PR Merged
[ ] 🏆 Product Acceptance

🧰 Work Description
Two tests repeatedly fail in the cicd. These should be examined and made more robust. Will try to rewrite with the CLI-testing library to remove memory leaks and other implementation problems.
E2E Testing for taqueria taquito plugin › Verify that taqueria taquito plugin will fund instantiated accounts on a network
E2E Testing for taqueria taquito plugin › Verify that taqueria taquito plugin will can send from one instantiated account to another
✅ To Do
No response
⚖ Acceptance Criteria
✨ Functional:

[ ]
[ ]

🔭 Scope
🙅♂ Out of Scope:

...

Code of Conduct

[X] I agree to follow this project's Code of Conduct

duplicate of 1666


Conversion error: Jekyll::Converters::Scss encountered an error while converting '/assets/css/main.scss'

After the bump to Jekyll 3, I'm getting this build error: Conversion error: Jekyll::Converters::Scss encountered an error while converting '/assets/css/main.scss': Invalid CSS after "...r : #3b5998": expected "{", was ";" on line 44.
That seems to be the $facebook-color: line imported from variables.scss but I have no idea what's tripping up the converter.
Any ideas? Again, thanks for the help!

Did you make any changes to the SCSS files? The un-altered ones work just fine with Jekyll 3 as I haven't received any errors and it make the trip fine through GitHub Pages where I host the demo.
My guess is you're missing a ; or { after a declaration as the error suggests. It can be tricky finding which line that's on though since it's likely in a SCSS partial.

Looks like you're using Bigfoot.js. I'd start by disabling those @imports in main.scss and see if it builds. Probably something in there it doesn't like. If that doesn't work then disable each import and enable 1 by 1 to find the problem partial. Then check the lines for missing ;, {, }, or duplicates.

Had a free second and looked at you _sass partials. Wonder if line 42 in variables.scss is your problem. ======= underneath // Links is not valid and probably breaking the compiler. If this existed before updating to Jekyll 3 then perhaps you just got lucky that it didn't fail... or silently failed. When in doubt diff against the files in my repo to see where the errors might have creeped in.

That's exactly the culprit. I guess I wasn't careful enough comparing the HEAD and new versions when I pulled everything in from your update.
Thanks so much!

FWIW I think I saw this issue caused by two lines each containing --- at the top of an .scss file; I don't remember why I'd added them (likely a hack to get something about Jekyll-plumbing/processing to work, maybe no longer necessary?), but removing them seemed to resolve this error.

I got  this build error : Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/main.scss':                     Invalid GBK character "\xE2" on line 54
here is main.scss file:
---
# Only the main Sass file needs front matter (the dashes are enough)
---

@charset "utf-8";

@import "minimal-mistakes/skins/{{ site.minimal_mistakes_skin | default: 'default' }}"; // skin
@import "minimal-mistakes"; // main partials

if I remove ‘---’ then build with no error ，but can't get main.css file

@ssy341
Any links to the place that told you to do that?
I'm having the same issue where the new jekyll updates are not compiling the scss to a main.scss file.

@rchatham If you're on Windows try Jekyll's guide for installing. Encoding issues can be a common problem depending on how your Ruby environment is setup. It happens a lot with CI setups, Docker, and the like.
https://jekyllrb.com/docs/installation/windows/#encoding

Hi!
I got the same problem, but I can't seem to work it out.
 Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':
                    Internal Error: Invalid UTF-8
                    ------------------------------------------------
      Jekyll 4.0.1   Please append `--trace` to the `serve` command
                     for any additional information or backtrace.
                    ------------------------------------------------

I have been searching solution for this for like a week now. Could anybody please explain what's going on?
Thank you in advance!

@DOEHOONLEE Not until you provide more information, such as the content of your assets/css/style.scss as well as other relevant files.

@iBug  Thank you for the fast reply and I'm so sorry about not providing more information.
This is what I have on style.scss
---
---

@import "jekyll-theme-minimal";

#main-title {
    text-align: center;
    opacity: 0.9;
    box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19);
}

Is the "Please append '--trace' to the 'serve' command for any additional information or backtrace" part also an error? I only saw the style.scss error last week. I have no idea what is going on :(

@DOEHOONLEE What is jekyll-theme-minimal? That's not something coming from this theme.

@DOEHOONLEE Two things surfacing at first:

jekyll-theme-minimal doesn't appear to be related to this theme (Minimal Mistakes by Michael Rose), but rather this one.
If you're building on Windows then there's (probably) a hidden UTF-8 BOM at the beginning of the file which you'll need to find a way to get rid of. This is a blind guess (you haven't yet provided the error trace) but my experiences point in this way.

I added
gemspec

gem "jekyll-theme-minimal"

to Gemfile and now I'm getting

Oh, I am sorry I got the wrong repository :O

Hi
I am getting below error
  Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':                     No such file or directory @ dir_chdir - /github/workspace/docs

What Should i do i have same error
Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':

Please help me in that.....

What Should i do i have same error Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':

Please help me in that.....

I have the same problem and i don't know what it means... it was all good before so i don't know what's wrong with my css...

If you look through the stacktrace above there's a conversion error with assets/css/style.scss. This theme doesn't use that file.
If you look a few lines above that it indicates Theme: jekyll-theme-primer... again not this theme.

@asolene My Bugs Error Fixes and i know what should the mistake i do

.
After so many errors in it but at last i deployed my Website Successfully.

How did you solved it? I have the same error...

I had an error Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':
No such file or directory @ dir_chdir - /github/workspace/docs

How did you solve it?

I have the same error.

I think I am in the same basket.. some issue here.

FWIW I think I saw this issue caused by two lines each containing --- at the top of an .scss file; I don't remember why I'd added them (likely a hack to get something about Jekyll-plumbing/processing to work, maybe no longer necessary?), but removing them seemed to resolve this error.

I had the same problem, and solved it this way. Many thanks!
problem:

solved:

I managed to solve
One "." before the css file and images link is what was missing.
before:

after:


Unable to save resolv.conf

Version
Microsoft Windows [Version 10.0.19045.2130]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Debian 11
Other Software
No response
Repro Steps

Create /etc/wsl.conf
Add: [network] generateResolvConf = false
Close terminal
Open windows command prompt
Run wsl --shutdown
Open Debian terminal
sudo vi /etc/resolv.conf
Add nameserver <IP_ADDRESS>
Write & Quit (:wq)

Expected Behavior
After following instructions (that I've gleaned from delving through several other bugs related to name resolution issue in WSL2) to make resolve.conf changes permanent, I should be able to save the resolv.conf with the custom nameserver, and this should persist between restarts and reboots. As a bonus, name resolution will work from within WSL2.
Actual Behavior
Get error: "/etc/resolv.conf" E166: Can't open linked file for writing
Diagnostic Logs
No response

@glasko-dp after you created /etc/wsl.conf and restart, /etc/resolv.conf no longer points to /run/systemd/resolve/stub-resolv.conf:
root@RIPPER:~# file /etc/resolv.conf
/etc/resolv.conf: broken symbolic link to ../run/systemd/resolve/stub-resolv.conf

Just remove the broken link and create a new /etc/resolv.conf with your settings.

Thanks for reporting this @glasko-dp.
If generateResolvConf is set to false then the /etc/resolv.conf will point to a file that doesn't exist. @elsaco's solution of simply deleting the file should solve the issue.


virtualbox: fails to start, Qt error

Describe the bug
Cannot start Virtualbox:
août 06 13:41:06 nixpsla virtualbox.desktop[2469]: Qt WARNING: Could not find the Qt platform plugin "xcb" in ""
août 06 13:41:06 nixpsla virtualbox.desktop[2469]: Qt FATAL: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

To Reproduce
Steps to reproduce the behavior:

Open virtualbox

Expected behavior
Virtualbox should start
Additional context
I saw this mentioned here: https://github.com/NixOS/nixpkgs/issues/65448#issuecomment-515971498
But the related fixes have been pushed to master a week ago, I think?
Metadata

system: "x86_64-linux"
host os: Linux 5.1.21, NixOS, 19.09pre187507.525eaf407d4 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-19.09pre187507.525eaf407d4, home-manager, nixos-hardware"
channels(stanislas): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

The issues are https://github.com/NixOS/nixpkgs/issues/65399.
That issue should have many linked examples and documentation on how this can be fixed.

Thanks! Shall we close this one then?

Thanks! Shall we close this one then?

No, we should keep it open so someone can act on it specifically.

OK :) I don't really understand what all these issues are about so I will let someone else fix this

Thanks @worldofpeace!

@worldofpeace @angristan This issue is open for me again at least since b839d4a8557adc80e522f674529e586ab2a88d23.


Re-evaluate usefulness and correctness of the Verifier/Loader interfaces

The Loader seems to have more responsibilities than its name suggests - it also is used to append blocks and fetch state from the DB.
Additionally, the Verifier interface seems a bit unnecessary. The verifiers package exposes all the checks that the Chain can make, but the Verifier doesn't actually use all of them, which seems like a strange choice - which subsequently affects testing, since we can not mock certificate checks for instance.

A thorough assessment of the Chain should be done during the imminent migration to rust


Uncaught Error: ENOENT, no such file or directory  C: Users Roland AppData Local atom app-0.187.0 rustc

Enter steps to reproduce below:  1. ... 2. ... Atom Version: 0.187.0 System: ROLAND-WIN7-PC Thrown From:  linter  https://github.com/AtomLinter/Linter  package, v0.12.0 ### Stack Trace Uncaught Error: ENOENT, no such file or directory  C: Users Roland AppData Local atom app-0.187.0 rustc      At fs.js:807 Error: ENOENT, no such file or directory  C: Users Roland AppData Local atom app-0.187.0 rustc  at Error  native  at fs.statSync  fs.js:807:18  at Object.fs.statSync  ATOM_SHELL_ASAR.js:206:16  at LinterRust.Linter._cachedStatSync  C: Users Roland .atom packages linter lib linter.coffee:69:17  at LinterRust.Linter.getCmdAndArgs  C: Users Roland .atom packages linter lib linter.coffee:86:16  at LinterRust.Linter.lintFile  C: Users Roland .atom packages linter lib linter.coffee:127:24  at LinterRust.lintFile  C: Users Roland .atom packages linter-rust lib linter-rust.coffee:42:7  at LinterRust.lintFile  C: Users Roland .atom packages linter-rust lib linter-rust.coffee:1:1  at C: Users Roland .atom packages linter lib linter-view.coffee:158:18 at Array.forEach  native  at C: Users Roland .atom packages linter lib linter-view.coffee:157:18 at FSReqWrap.ONCOMPLETE  fs.js:100:15      ### Commands     -0:16.4 application:OPEN-folder  atom-text-editor.editor  3x -0:08.8 core:backspace  atom-text-editor.editor.is-focused  3x -0:08.1 core:save  atom-text-editor.editor.is-focused      ### Config    json { core : {}, linter : {} }     ### Installed Packages    coffee # User keyboard-localization, v1.1.6 language-rust, v0.4.2 linter, v0.12.0 linter-rust, v0.0.5 minimap, v4.6.0 # Dev No dev packages

Is this still relevant with latest linter-rust?

No it is not, but I have another issue now. The linter silently fails, and does not do anything at all.

Which version of the Rust are you using?
rustc --version

I use always the latest nightly. I use the multirust tool to update my toolchain.

Are there any messages in the Developer Tools (View -> Developer -> Toggle Developer Tools)?


Add a task for optional labels check

Add a task for optional labels check using this policy: https://github.com/redhat-appstudio/hacbs-test/pull/3
Based on https://github.com/redhat-appstudio/build-definitions/blob/main/tasks/sanity-label-check.yaml

@dirgim @hongweiliu17 @jsztuka @Dannyb48 PTAL

Please rebase and include tasks/sanity-optional-label-check.yaml in tasks/kustomization.yaml. Also add it into pipelines/hacbs/hacbs-test.yaml and test using ./hack/test-builds.sh hacbs

Please rebase and include tasks/sanity-optional-label-check.yaml in tasks/kustomization.yaml. Also add it into pipelines/hacbs/hacbs-test.yaml and test using ./hack/test-builds.sh hacbs

Rebased and added, however ./hack/test-builds.sh hacbs skips all the jobs for some reason, why is that?

@staticf0x probably because the image is already built, you can remove the by running oc delete is --all

Thanks, that was it. The tests pass now.

@Michkov As @dirgim mentioned, we can actually reuse sanity-label-check and just pass the correct namespace. PTAL now, if the test is enough for HACBS-201 requirements.

LGTM in the new form


whitespace tokenizer is not documented

The whitespace tokenizer is not listed in the docs but is implemented here.

Addressed in #4975


Split interface and class tag generators

Motivation
There is not currently a means for extensions to determine the name of
the API implementation class, only the API interface.
Modifications

Split the generation of the implementation out to a new category of
generator and new implementation.
Move some common logic into a shared abstract class.
Move the TagComparer out to a shared public instance.

Results
Extensions may use the TypeGeneratorRegistry for OpenApiTag with the
TagImplementationCategory to get the TypeInfo, etc, for the
implementation class.
They may also use the TagComparer instance to get a distinct list of
tags.

/merge


DRILL-7143: Support default value for empty columns

Modifies the prior work to add default values for columns. The prior work added defaults
when the entire column is missing from a reader (the old Nullable Int column). The Row
Set mechanism now will also "fill empty" slots with the default value.
Added default support for the column writers. The writers automatically obtain the
default value from the column schema. The default can also be set explicitly on
the column writer.
Updated the null column mechanism to use this feature rather than the ad-hoc
implemention in the prior commit.
Semantics changed a bit. Only Required columns take a default. The default value
is ignored or nullable columns since nullable columns already have a file default: NULL.
Updated the CSV-with-schema tests to illustrate the new behavior.

@arina-ielchiieva, here is a first-cut at the improved default values. Have tested selected mechanisms and CSV with schema. Have not yet run the full set of unit tests. Consider this a "preview" to begin the code review in parallel with the remaining busy-work needed to complete the PR.

Additional fixes: for Boolean and Decimal issues. Turns out the column writers for these types had some issues, now fixed.

Fixed a number of issues relating to Boolean and Decimal types. Provided support for blank columns in CSV. Added a bunch more unit tests.
At this point, we should have everything we wanted for the alpha version of the schema feature. There is much more we can do. But, the most important next step is to allow others to try the feature and provide feedback.
This PR passes the full set of Drill unit tests. After a final code review, it should be ready to go.

@paul-rogers let me summarize new blank handling strategy.
We introduce new column property drill.blank-as. It can have four values: blank-as, null, 0, simple.  User can indicate which strategy to use in column schema. For example:
create or replace schema (id int, amount int properties { 'drill.blank-as' = 'simple' }) for table dfs.tmp.text_table
If no blank strategy is indicated, behavior is the following:

for columns which are not indicated in schema, blank-as strategy will be used. I suggest, we rename blank-as value to blank. For example: `property { 'drill.blank-as' = 'blank' }. Why do you think?
for nullable columns indicated in schema, null strategy will be used.
for non-nullable columns indicated in schema with or without default value, which strategy will be used? 0 or simple? So far I don't see much difference between both, maybe we don't need one of them?

I have left some other comments in the PR, once we clarify this issue and address code review comments, PR will be good to go.

@arina-ielchiieva, your summary is mostly correct. Just to refine a bit.
By default, if code using the row set framework asks to convert strings to other types, blanks have no special meaning. A blank will be parsed as any other string, which typically produces an error.
Any client of the row set framework can specify a blank-handling policy. Using an internal property set. The name of this internal property is blank-as. There are four choices:

Unset: use the default policy described above.
null: If the column is nullable, treat the blank as null. If non-nullable, leave the blank unchanged.
0: Replace blanks with the value "0" for numeric types.
skip: Skip blank values. This will set the column to its default value: NULL for nullable columns, the default value for non-nullable columns. If no default is set, then the "default default" of all-zero bytes is used.

(Note that I renamed "simple" to "skip".)
Normally, the blank policy is set by the reader. For example for CSV, it seemed to make sense to use the skip policy.
But, to provide maximum flexibility (and because there are many different requirements), the user can also optionally set the drill.blank-as property on a column. If set, that property overrides anything the reader may have set. For example, suppose I want to use -1 for missing columns, but 0 for blank columns. I could set the column default value to -1, then set the drill.blank-as property to 0.
The bottom line for users of the CSV file format, with a schema, is that, by default, blanks are skipped and either become NULL or the default value.
Note also that this change strips leading and trailing white space from columns prior to type conversion. So a value of "  " is trimmed to "" and treated as a blank string. Trimming is not done for values stored as VARCHAR. In this case, if the value is "  ", that is what will be stored in the vector.
This is all a first draft. Let's get this into the hands of users as an "alpha", get some feedback, and adjust the code based on what we learn.

Squashed commits. Should be ready to go.


Add Medical University of Lodz

@LaVestima Pull request merged. Thank you!

@LaVestima Pull request merged. Thank you!


Fix typos in ViewModels

Fix typos in the files:

ReportErrorDialogViewModel.cs
WelcomeDialogViewModel.cs

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
[ ] Performance improvement
[ ] Refactoring (so no functional change)
[x] Other (docs, build config, etc)

Checklist:

[ ] I've added tests for my code. (most of the time mandatory)
[ ] I have added an entry to the changelog. (mandatory)
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Thanks a lo!


More CLI options

The CLI allows tagging, deleting tags, and deleting annotations. These three allow filtering based on tag, uri, text, quote, and date.  What else would a knowledge-base maintainer need?

--before to complement --from in Filters
--exact to complement the default fuzzy search (or the other way round with --fuzzy)
edit for editing annotations - this could open the search window to select an annotation and then an editor window to edit the text/comment.
view to print out a single annotation - again, search window + print prettily including created/updated dates and a link to the annotation on Hypothesis.
sync --group id - to sync annotations from a different group just once? this could also post these annotations to gooseberry's group to collect annotations from here and there into the KB. Make sure to set the user though, o/w if the group is public then you'll be syncing millions of annotations. This should have Filters - maybe a different command makes more sense for this: move?.

oops, wrong project, this needs to be in gooseberry


The Increase Quota Edit for tools request stopped displaying the changes on Test both for User and Approval Admin for Tools and Dev namespaces

Description:
The Increase Quota Edit for tools  request stopped displaying the changes on Test both for User and Approval Admin for Tools and Dev namespaces:
User email:

Admin email:

Fixed:


[livedoc] Fix several minor typos detected by github.com/client9/misspell

See https://github.com/apache/predictionio/pull/456 for details.

LGTM!


Styled-Components -> vanilla-extract

"React v18 Workgroup" and Twitter, especially Sebastian Markbåge's statements,
have led me to conclude that the CSS-in-JS approach has only disadvantages and no merit to be adopted.
On the other hand, I thought that CSS-Modules,
Tailwind CSS, and Plain CSS as a global style were the most likely candidates for incorporating old-fashioned statically generated CSS into modern development,
so I went with CSS-Modules, which is the most versatile and can be used with Tailwind.
I decided to migrate from the current Styled-Components to CSS-Modules.

I edited CSS Module to vanilla-extract


Test for connection leaks in more tests

This will help prevent regressions and point to the leaking test, rather than to a later test that happens to checks for leaks. The change is applied to all tests that have an OkHttpClient member variable.

Looks good, provided it doesn't obscure the root cause.  IT does make me wonder whether the client creation and this check should be part of a @Rule instead?

Agreed. If you wanna do a follow-up to make a rule for the default OkHttpClient, that’d be rad.

Are you suggesting to add a new OkHttpClientRule class that extends OkHttpClient and implements TestRule.

Or maybe OkHttpClientTestingRule that has an OkHttpClient instance that you can use.

@Rule public OkHttpClientTestingRule clientTestingRule = ...
private OkHttpClient client = clientTestingRule.client;


WIP: Distributions change. Use 32-bit bins, buffer counts, increase buffer size.

Uses: https://github.com/DataDog/opentelemetry-mapping-go/pull/189
Sibling to: https://github.com/DataDog/datadog-agent/pull/20524 https://github.com/DataDog/datadog-agent/pull/20525 https://github.com/DataDog/datadog-agent/pull/20526
Ref: https://datadoghq.atlassian.net/browse/SMPTNG-72

What does this PR do?

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

PR commenter failed, here's analysis copied from CI output:
Changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%:

experiment
goal
Δ mean %
confidence

uds_dogstatsd_to_api_150MiB
ingress throughput
1633.35
100.00%

uds_dogstatsd_to_api_100MiB
ingress throughput
1035.79
100.00%

uds_dogstatsd_to_api_10MiB
ingress throughput
14.78
100.00%

udp_dogstatsd_to_api_10MiB
egress throughput
-91.34
100.00%

udp_dogstatsd_to_api_100MiB
egress throughput
-97.12
100.00%

Fine details of change detection per experiment.

experiment
goal
Δ mean %
Δ mean % CI
confidence

uds_dogstatsd_to_api_150MiB
ingress throughput
1633.35
[+1631.94, +1634.76]
100.00%

uds_dogstatsd_to_api_100MiB
ingress throughput
1035.79
[+1034.57, +1037.00]
100.00%

uds_dogstatsd_to_api_10MiB
ingress throughput
14.78
[+14.11, +15.46]
100.00%

idle
egress throughput
-0
[-2.46, +2.45]
0.13%

uds_dogstatsd_to_api
ingress throughput
-0.02
[-0.17, +0.13]
17.45%

udp_dogstatsd_to_api_10MiB
egress throughput
-91.34
[-96.29, -86.38]
100.00%

udp_dogstatsd_to_api_100MiB
egress throughput
-97.12
[-102.25, -91.99]
100.00%


Feature/job specs pt3

targeting #173 til merged
tests/modifications to RapidproDeleteJob
details in commit msgs

Coverage increased (+0.5%) to 58.019% when pulling cb918ea4276ca009fd3935d7458675d8c08526ff on feature/job-specs-pt3 into 4f616090e5d783a637675e0a8dd65127fcfc3297 on feature/job-specs-pt2.


Whats the baud rate and pinout on the Wio terminal?

Hi!
I'm implementing support for Wio Terminal + WiFi (using eRPC ameba firmware) in Rust.
Can you help me work out what the parameters are for talking to the ameba? In particular, I'm not sure what the baud rate is.
Is this correct?

Reset the RTL8720 by bringing PA18 low for 100ms, then high, and waiting 100ms
Communicate using NXP eRPC over  SERCOM0 in UART mode, with RX on PC24 (Pad2) and TX on PB24 (Pad 0). No CTS/RTS.
? Baud rate 1843200 ?
eRPC uses the default codec, default framed transport, default crc16 (starting value 0xEF4A, polynomial 0x1021)

Hi,Twitch
1.yes,use PA18 at WIO Terminal to reset RTL8720,100ms low and 100ms high
2.yes,use  SERCOM0,PC24(PAD2)/PB24(PAD0),no CTS/RTS at WIO Terminal
3.yes,use badu rate at 1843200
4.yes,default codec, default framed transport, default crc16(crcStart is 0xEF4A,polynomial is 0x1021)

Got my eRPC implementation working! :DD
One thing to note: I'm observing the Ameba is taking at least 120ms to be ready after I bring PA18 high, so any bits sent earlier are corrupted.
Maybe increase the delay before any bits are written to it? I'm having no issues if I give it 200ms.

@twitchyliquid64  We are very glad that our software can help you. Can you share your rust repository? I'm very interested.

@Pillar1989 I'm implementing this upstream in https://github.com/atsamd-rs/atsamd, specifically in the Wio Terminal board support crate (here).
My eRPC / Wifi implementation is a work in progress on my local machine, however I hope to get it merged upstream into atsamd-rs in the next week or so.

@twitchyliquid64  Great. I'm really looking forward to see eRPC run successfully on the rust.

Still a work in progress but ive gotten the GetSystemVersion & GetMacAddress RPCs working.
Main controller: https://github.com/twitchyliquid64/atsamd/blob/wio_terminal/boards/wio_terminal/src/wifi.rs#L54
RPC trait: https://github.com/twitchyliquid64/atsamd/blob/wio_terminal/boards/wio_terminal/src/wifi/erpc.rs#L165
RPC implementation for GetMacAddress: https://github.com/twitchyliquid64/atsamd/blob/wio_terminal/boards/wio_terminal/src/wifi/wifi_rpcs.rs#L5
Aside from implementing the bulk of the RPCs, im not 100% happy with the RPC trait or the streaming parser yet, so it will probably be a week or two before its upstream and ready for public use.

@twitchyliquid64    Is it possible to write a rust erpcgen(https://github.com/EmbeddedRPC/erpc/tree/develop/erpcgen)? This will automatically generate the corresponding code from an idl file.
https://github.com/Seeed-Studio/seeed-ambd-firmware/tree/master/erpc_idl
Most of our code here is generated automatically by erpcgen.
https://github.com/Seeed-Studio/Seeed_Arduino_rpcUnified/tree/master/src

Yes, there are some corner cases (because I am trying to do everything without memory allocations) however.

I've published a crate for this: for now it only supports scanning RPCs + getting the MAC + getting the version: https://github.com/twitchyliquid64/seeed-erpc-rs
This crate only handles parsing/serializing the different RPCs, so it should be usable from any Rust embedded codebase. It also does everything entirely on the stack, so no memory allocator is needed.
Next up I'll implement connecting to APs, and some of the LWIP RPCs. Should be straightforward now I have all the boilerplate working.
I'm also merging an example that shows all the wifi networks on the screen, into the atsamd HAL.

@twitchyliquid64  rust eRPC have any new progress?

@Pillar1989 at the moment just AP scanning and connecting to a network is implemented, but next I want to get UDP sockets working. I'll hopefully have that in sometime this week.


delete user groups

hi, im not sure but is there no way to delete user groups ?

Open a user group, then click the little trash can icon in the bottom right hand corner.

Oh man im sorry to Make an issue for this thank you