change poll answering to happen all at once

Fixes #110
Describe your changes
Changed poll answering so that all of the poll's questions are answered in one request. Before the poll's questions needed to be answered one at a time which was inefficient and made it too difficult to track how many times the poll has been answered. No new unit tests added. The integration test poll.test.ts was updated for the new api. Documentation was also updated for poll answering. Also added the missing documentation for poll results.
Note: this update will break the current frontend integration for poll answering.
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added thorough tests

Codecov Report

Merging #121 (0a0bf72) into dev (153abf1) will increase coverage by 7.24%.
The diff coverage is 84.09%.

@@            Coverage Diff             @@
##              dev     #121      +/-   ##
==========================================
+ Coverage   55.42%   62.67%   +7.24%
==========================================
  Files          50       29      -21
  Lines        2035     1661     -374
  Branches      270      147     -123
==========================================
- Hits         1128     1041      -87
+ Misses        888      602     -286
+ Partials       19       18       -1

Flag
Coverage Δ

backend
62.67% <84.09%> (+<0.01%)
:arrow_up:

dev
62.67% <84.09%> (?)

frontend
?

staging
?

unit
62.67% <84.09%> (+7.24%)
:arrow_up:

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

Impacted Files
Coverage Δ

backend/src/controllers/pollController.ts
0.00% <0.00%> (ø)

backend/src/models/Poll.ts
66.21% <86.48%> (+2.33%)
:arrow_up:

backend/src/models/BooleanQuestion.ts
23.33% <100.00%> (-4.80%)
:arrow_down:

backend/src/models/NumberQuestion.ts
67.44% <100.00%> (-4.66%)
:arrow_down:

backend/src/models/Question.ts
81.19% <100.00%> (+0.08%)
:arrow_up:

backend/src/services/VotingService.ts
77.66% <100.00%> (ø)

backend/src/models/Answer.ts
64.45% <0.00%> (-1.81%)
:arrow_down:

backend/src/app.ts
0.00% <0.00%> (ø)

frontend/src/components/NavBar.tsx

... and 20 more

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


the number of iterations of each epoch during training

I run it using the command:
CUDA_VISIBLE_DEVICES=1,2,3,4 ./tools/dist_train.sh configs/ReDet/ReDet_re50_refpn_1x_dota1.py 4
I used 4 gpus, and batchsize is 8.
I found that the number of iterations in each epoch is different from your log file. Mine is 1695, but yours is 1550. Why? I did not make any changes to the DOTA dataset other than run "prepare_dota1.py". Looking forward to your reply.

Thank you for your answer.
I have tested both 1695 and 1550 Settings, but the accuracy of the implementation is very low (63.07% mAP in 1695 setting, 64.48% mAP in 1550 setting). I'm so confused.
I have tested on Quadro RTX 6000 with Pytorch=1.1.0, cuda=10.0.
The only change I made to the code and parameters was https://github.com/csuhan/ReDet/issues/4#issuecomment-806330053
20210330_175152.log
20210331_085525.log

I have changed the data spliting setting to 1550.
For the performance, I suggest to:

Run inference using our pretrained models to validate the performace.
Test RoI Transformer. The mAP would lies in [73.7,75.0].

Hi, @ChujieXu . There is something wrong with our ReResNet pretrained models. We have updated it.
See https://github.com/csuhan/ReDet/commit/f01eb2ac0ea90bac47626feb22d42db26b0d6da4 and https://github.com/csuhan/ReDet/commit/88f8170db12a34ec342ab61571db217c9589888d

Thank you for your reply. @csuhan
I will try it with the updated pretrained model.

Hello   @csuhan.
Is it same for DOTA 1.5 also?
In DOTA_devkit/prepare_dota1_5.py
DOTA2COCOTrain(os.path.join(dstpath, 'trainval1024'), os.path.join(
dstpath, 'trainval1024', 'DOTA_trainval1024.json'), wordname_15, difficult='-1')
Could you kindly let me know if you took difficult = '2' or '-1' ?
Thank you.


Convert result to str before regex

Also more logging if there are no matches.
update and add/remove sections as needed
New Features
please describe new capabilities
Fixes
please list/describe an fixes, including links to related issues
Testing
please describe both unit tests included and any integration tests conducted
Prior to merging for releases:

[ ] update the project's version in the top-level CMakeLists.txt file
[ ] update the appVersion to be the new container image tag version in chart/Chart.yaml

from a consistency perspective, dripline has traditionally sent unicode in packets on the mesh - the bytes encoding from the ethernet socket.recv is a bit of an anomaly
should consider the most uniform implementation

the socket.rcv method in _listen should be retrieving a bytes object, this then gets decoded into a string https://github.com/driplineorg/dripline-python/blob/develop/dripline/implementations/ethernet_scpi_service.py#L186
that data gets packaged in _send_commands into a list with all other responses https://github.com/driplineorg/dripline-python/blob/develop/dripline/implementations/ethernet_scpi_service.py#L165
which is then joined into a string by send_to_device https://github.com/driplineorg/dripline-python/blob/develop/dripline/implementations/ethernet_scpi_service.py#L142
the FormatEntity would expect to get this same string formatted object as its response https://github.com/driplineorg/dripline-python/blob/develop/dripline/implementations/entity_endpoints.py#L133

That this isn't the case indicates that the code is doing something unexpected somewhere in one of the passes.  I would recommend tracking the type of this reply through this chain - particularly right before it leaves the ethernet_scpi_service in send_to_device and right after on_get of FormatEntity gets it.


SMTP Error : could not initiate SMTP session: remote error: tls: handshake failure

Description
I try use Gitea's mailer, but has a error
Settings is:
[mailer]
ENABLED = true
PROTOCOL = smtps
SMTP_ADDR = gz-smtp.qcloudmail.com
SMTP_PORT = 465
USER = ***
PASSWD = ***
FROM = ***

But report this: gomail: could not send email 1: could not initiate SMTP session: remote error: tls: handshake failure
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Ubuntu Systemd
Database
MySQL/MariaDB

I found a post on the forum with a similar issue to yours. tomekk provided a possible solution that you can try. I hope it helps you!

I found a post on the forum with a similar issue to yours. tomekk provided a possible solution that you can try. I hope it helps you!我在论坛上发现一个与您类似问题的帖子。tomekk 提供了一个您可以尝试的可能解决方案。希望对您有所帮助！

No, he still doesn't work, still prompting 'tls: handshake failure'

We close issues that need feedback from the author if there were no new comments for a month. :tea:


Use laxar-infrastructure

To cut down on boilerplate and simplify maintenance, laxar-mocks should use laxar-infrastructure to generate webpack- and karma-configuration.

Implemented on master (v2.0.0).


npx use-yarn fails on node 16

Node version: 16.13.0
Npm version: 8.1.0
use-yarn version: using via npx so latest
npx use-yarn now throws an error, probably because the behavior of npx was changed such that it looks like npm to whatever detection method your package uses.

@bencooper222 Good find. Do you think we should just remove the documentation around npx use-yarn? Have you tried using "use-yarn || ( npm install --save-dev --no-scripts --no-save use-yarn && use-yarn )" from the docs?

@AndersDJohnson For me, the mentioned command "use-yarn || ( npm install --save-dev --no-scripts --no-save use-yarn && use-yarn )" leads to an infinite loop /bin/sh: use-yarn: not found.

@MaSpeng Interesting, is the npm install not working for you there? I thought that was a valid bash command.

@AndersDJohnson at least for me it's not working in the yarn context. When I use it directly in the shell it works as expected.

@bencooper222 @MaSpeng OK so with PR https://github.com/AndersDJohnson/use-yarn/pull/16 and some additional fixups, I think I have this working now in version 2.3.1. You do need to update your usage in preinstall to pass $npm_execpath in as standard input, as follows:
-  "preinstall": "npx use-yarn"
+  "preinstall": "echo $npm_execpath | npx use-yarn"

Please let me know if it works!

@AndersDJohnson Works 👍


feat: add the tree Close api

Context
ref: https://github.com/cosmos/cosmos-sdk/issues/19704

@Mergifyio backport release/v1.1.x


Email messages after private notes doesn't get sent in Email forwarder

Describe the bug
If you send a message after a private note in our shared Inbox feature(Beta) it doesn't get sent to email
To Reproduce
Steps to reproduce the behavior:

Send email to a shared inbox
Reply with a normal message - It'll show up
Add private note
Reply with normal message - it doesn't show up in inbox

Expected behavior
Emails should continued to be delivered
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Doesn't impact gmail integration or any customers. Only impacts Shared inbox feature on Staging at the moment

Some more context:
If the customer replies after the private note is set: The issue is fixed for the conversation.


strtok_s is not defined in Cygwin. Use strok_r instead.

Also do some minor re-styling.

One additional thought: should the Linux side scan list line parsing gracefully consume carriage returns?  It should probably adhere to any rule file accommodations.


Add metavisor-version argument

Add support for determining metavisor version through published
version artifacts in AWS.

Add mv_version module to brkt_cli

Update esx provider to fetch OVF objects from S3 using metavisor
version

TODO gce provider

TODO aws provider

Tests failed because we cannot reach packages.int.brkt.net from outside. Trying to think of a better workaround to make sure internal dev still works.

lgtm. I will let @apoorva-jindal approve this, pending the tests passing.


#Bug; Prices are not fetched correctely on Arbitrum

Describe the bug
LUSD and Compound price feed are incorrect
Reproduction
Where can we see this bug in action?

Link to subgraph on USDs V2 Subgraph
  dailyRewardTokens(first: 100,orderBy:blockTimestamp,orderDirection:desc) {  id name  actualPrice  blockTimestamp }
Expected behavior
The LUSD price should be around 1 and compound price is wrong
I'm using getUsdPricePerToken function to get the asset price

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

@bayou020 the subgraph you mentioned above is not a Messari Subgraph. Is there a Messari subgraph that has the errors you mentioned above and if so, can you link that one?

@bye43 here is the link: https://github.com/messari/subgraphs/tree/master/subgraphs/reference/src/prices


chore: Add focus-trap example

This update adds a basic example for the FocusTrap component as part of this effort: https://github.com/reakit/reakit/issues/939
Screenshots

How to test?
The example showcases 2 sets of buttons, totalling 5, a "Focus trapped" set and a "Untrapped focus" set.

Run yarn dev
Visit http://localhost:3000/examples/focus-trap.
Press Tab.
Once you Tab into the "Focus trapped" set, you cannot Tab out.
Click a button outside the "Focus trapped" set.
You should be able to Tab normally.
If you Tab back into the "Focus trapped" set, either Tab or Shift + Tab, your focus will be trapped again.

Does this PR introduce breaking changes?
Nope! Only adding an example.
Notes

I'm seeing a TS error in this example saying that the ref may possible be null, even though I'm specifying it as HTMLDivElement. I'm not sure how to fix that one 🤔
Thank you all so much! ❤

Great job! I'd suggest we make this example more simple though. And let users disable the focus trap behavior so keyboard users accessing the docs will be able to use the site. Let's also avoid using ariakit-utils in the examples.
Wrote this snippet to illustrate what I'm talking about:
import { FocusEvent, useRef } from "react";
import { useCheckboxState, Checkbox, CheckboxCheck } from "ariakit/checkbox";
import { FocusTrap } from "ariakit/focus-trap";
import "./style.css";

export default function Example() {
  const focusTrapped = useCheckboxState({ defaultValue: true });
  const firstRef = useRef<HTMLButtonElement>(null);
  const lastRef = useRef<HTMLButtonElement>(null);

  const onTrapFocus = (event: FocusEvent) => {
    if (event.relatedTarget === firstRef.current) {
      lastRef.current?.focus();
    } else {
      firstRef.current?.focus();
    }
  };

  return (
    <>
      {focusTrapped.value && <FocusTrap onFocus={onTrapFocus} />}
      <div className="wrapper">
        <button className="button" ref={firstRef}>
          First
        </button>
        <Checkbox
          state={focusTrapped}
          clickOnEnter
          as="button"
          className="button"
        >
          <CheckboxCheck />
          Trap focus
        </Checkbox>
        <button className="button" ref={lastRef}>
          Last
        </button>
      </div>
      {focusTrapped.value && <FocusTrap onFocus={onTrapFocus} />}
    </>
  );
}

@diegohaz Wow! Thank you so much 🙇
I've updated the example based on your snippet. I adjusted the styles a bit to make the example a little clearer.

Let me know if this works! Happy to make any updates necessary


Fix mangadex scraper (paginated chapters)

Mangadex changed it's chapter lists to be paginated. This is a quick fix so that it at least works for page 1 without crashing.
For some reason there is an a tag without any href around the page number and this causes this bug.

I made the lines shorter, but I'm not sure if this is the accepted style for if expressions in python.

test_chapter_information_tomochan
I have no clue why this fails on travis. It passes locally for me and this merge request should have addressed the issue with this test. Any ideas?

I found another bug where '/chapter/1235/comments' would be matched as a chapter url.
I fixed it by appending (?:/[^a-zA-Z0-9]|/?$) to the MangadexChapter regex, that makes the line 92 chars. Is there any way to make this line shorter?

----------------------------------------------------------------------
Ran 9 tests in 111.488s

Finally got this done. Thanks for the PR.


Possibility to use function instead of string in action property for shortcut field.

Is your feature request related to a problem? Please describe.
Hey, I am trying to implement that functionality to the Hyper theme.

But I got this error.

Describe the solution you'd like
Is it possible to implement of function instead of a string in shortcut field for action property ?
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello friend, hey a question, how did you do to put the date in the footer?

Hello friend, hey a question, how did you do to put the date in the footer?

Use this lua function os.date()?

Hello friend, hey a question, how did you do to put the date in the footer?

Hey
In lua you can use os.date("%A %d/%m/%Y %H:%M")

@glepnir  thanks for the possibility to add function in action.
I am sorry to bother you again :/ Now I have an other error.
I can use function as you can see in the next two screenshots

Then I got this error

Any ideas ?
Thanks !

hmm because it's a function type then it can not write into cache by using json.encode ..

maybe need dump it first then encode the binary data into json ...let me try it later.

maybe need dump it first then encode the binary data into json ...let me try it later.

Okey ! I get it. Thanks !
You rocks !

update . should be works .

update . should be works .

It's working great ! thanks
Next step, dashboard.nvim should be able to make my coffee xD
Good job !


the release CI failed at "build binaries" step

https://github.com/containerd/runwasi/actions/runs/5605326723/job/15185844827#step:4:5351

There is a discussion on CNCF Slack #runwasi channel https://cloud-native.slack.com/archives/C04LTPB6Z0V/p1690411959642039

Closing this one as the release pipeline is working again after #211


spike(test): commit that breaks register-level error count

Demo of breaking a build with a bad register-count
What this code looks like:

Demo complete!


support defer statement

We may support the defer statement to do some clean-ups. There're several cases:

We've created too many materialized views, and the dependency becomes too complex to resolve and write the drop statements correctly. With defer, that'll be natural.
We may create tables with the same name in multiple tests. If one fails, others may also fail because of not dropping the table: we may also allow defer to clean-up on failures.
We may not want to make control mode or session variable configurations bring side effects for other parts in this session.

Cool! I think this is a nice-to-have feature.
But the problem 1/2 (clean-up) can be alternatively solved by -j1 😄.
For the .part problem, this solution can partly solve it, but I think it's still not the best way. IMO include subtest1.part should be (able to be) parallized (but maybe another syntax e.g., subtest subtest1.part). If so, the session-level side effects can also be isolated.

But the problem 1/2 (clean-up) can be alternatively solved (or bypassed) by -j1 😄.

You're really clever! 😄

But the problem 1/2 (clean-up) can be alternatively solved (or bypassed) by -j1 😄.

But we may also want to test the drop statement. 🥵

But the problem 1/2 (clean-up) can be alternatively solved (or bypassed) by -j1 😄.

But we may also want to test the drop statement. 🥵

drop is tested in a single slt? Or what case do you mean.

But the problem 1/2 (clean-up) can be alternatively solved (or bypassed) by -j1 😄.

But we may also want to test the drop statement. 🥵

drop is tested in a single slt? Or what case do you mean.

We want to test the correctness of the drop statements, but we may not want to resolve the dependencies manually to write the lines in order. 🤣

Yes, so I said your proposal is a nice-to-have feature 🤤


Option to provide a list of inputs from a file or stdin

While it's likely a niche case, if providing many explicit inputs to lychee, as file paths and URLs can be lengthy, I am a bit concerned about exceeding the character limit (at least I think there is one for some shells with command args).
It may be worthwhile having an option to provide inputs via a line delimited list instead? (--inputs-from or similar?)

My use-case was with a generated list of files to check (output from git diff-tree), which was simple enough to get, but slightly problematic providing as a list of args to lychee via a shell this way (especially with edge cases like file paths with spaces). I ended up using xargs for the first time to handle this, but found it required -d '\n' to work correctly.
I'm not super great with shell commands/scripts, and I struggled a bit with other approaches before finding the simple solution with xargs. Being able to read a list of lines from a file as inputs, via a supported option for lychee would prevent others like myself from stumbling about in bash/shell :sweat_smile:

It's totally fine if you'd rather hold off on such an option until there's enough demand, or someone were to open a PR for it :+1:
For anyone else that lands here, you can use whatever command to get your list of inputs (1 per line), and provide them to lychee with xargs like this: your-command | xargs -d '\n' lychee --, that simple :smile: (quotes around \n is important)

More info
your-command examples:

echo -e 'path/to/file\npath/to/another file.md' (more useful in scripts or testing)
cat path/to/input-list-file (if you stored your input list to a file)
git diff-tree --no-commit-id --name-only --diff-filter 'AM' -r --merge-base master remote/branch-name (generated list output from a binary or script of your own)

These work with xargs, but prior to getting a solution with xargs I had tried approaches with echo/printf and such but I had problems especially when testing with file paths that had spaces:

xargs -d '\n' lychee -- < <(echo -e 'path/to/file\npath/to/another file.md')
xargs -d '\n' lychee -- <<< $(echo -e 'path/to/file\npath/to/another file.md')

Instead of piping output of your-command to stdin, you can use < (redirection) / <<< (here-string), or <(your-command; another-command) which is process substitution to provide a temporary pseudo-file stream, which would be useful when a file is expected I think.
Within a script there's other options like expanding an array of path values lychee -- "${FILE_PATHS[@]}", which should keep it all intact if some paths have spaces, provided the array was constructed correctly (another pain point I've had with bash with other projects).

Relevant discussion over on ripgrep: https://github.com/BurntSushi/ripgrep/issues/273

Relevant discussion over on ripgrep: BurntSushi/ripgrep#273

Worth noting is the common --files-from option used across mentioned programs in that discussion. If lychee adds support, it might make sense to use that, or as other input types are supported: --inputs-from (plural).

While it's likely a niche case, if providing many explicit inputs to lychee, as file paths and URLs can be lengthy

I wouldn't say it's that nichey at all. A rather common case should be to check files in your local Git working tree. As the working tree may contain a lot of generated / build files that cannot be easily excluded by path glob, you probably only want to check those files that are committed to Git, where such an option becomes handy.
Otherwise lychee also checks all of the generate files, which in my case contained a lot of links to GitHub and triggered a rate limit, locking me out of GitHub for a few minutes :unamused:

instead we may invest more in integrating with version control system, such as ignoring files excluded by vcs by default and add an CLI option to only scan files managed by vcs.

instead we may invest more in integrating with version control system

I was thinking about that, too, but that's less generic, and then people will show up to get Mercurial, Subverion, you-name-it supported, too...

by vcs I meant all of them. but we don't have to implement all of them at once.

After re-reading the comments here and over at ripgrep, I think we should go with --files-from as the name for this option as @polarathene suggested, because file, rsync, and ack also use --files-from.
I will mark this as ready to be worked on.

[ ] Add --files-from argument, which takes a list of input files to be checked.


Git provider fails to force update when you are already on the branch

Consider the following invocation of the git provider:
 git '/opt/fenestra' do
  action :sync
  repository 'https://github.com/osuosl/fenestra'
  checkout_branch 'master'
end

By default, git will check out the master branch. The provider will then attempt to force update to the checkout_branch, but will fail because you can't force checkout a branch you are on.
https://github.com/chef/chef/blob/master/lib/chef/provider/git.rb#L160
An example on the command line:
$ git checkout master
$ git branch -f master
fatal: Cannot force update the current branch.

I'm interested in fixing this issue. What would be the best way to go about it?
Would I want to change the provider to look something vaguely like the following?
def checkout
  sha_ref = target_revision
  converge_by("checkout ref #{sha_ref} branch<EMAIL_ADDRESS>do
    # checkout into a local branch rather than a<EMAIL_ADDRESS>HEAD
    current_branch = shell_out!("git rev-parse --abbrev-ref HEAD") # I don't know what this returns, but let's pretend it just returns stdout
    if current_branch != @new_resource.checkout_branch then
        shell_out!("git branch -f<EMAIL_ADDRESS>#{sha_ref}", run_options(:cwd => @new_resource.destination))
    end
    shell_out!("git checkout<EMAIL_ADDRESS>run_options(:cwd => @new_resource.destination))
    Chef::Log.info "#{@new_resource} checked out branch<EMAIL_ADDRESS>onto<EMAIL_ADDRESS>reference: #{sha_ref}"
  end
end

Thanks @jordane for helping me find where the issue was.

Any thoughts on this issue?

There a workaround for this?  I just ran into it as well.  Thanks.

same issue. any ideas?

@ddarbyson You can try passing the hash which master is at to the provider. Good luck.

same issue here

Confirmed this issue also.

Confirmed.

Thanks for mentioning that you're having the issue too, I was beginning to wonder if I was crazy.
Here is a minimal test case cookbook which demonstrates the issue. To see the bug in action just run kitchen test. The README has more information.
@danielsdeleo said this could be a documentation bug, as opposed to an issue with the git provider.

See #3289

https://github.com/chef/chef-docs/issues/552

Ok, I still don't get it.
When I use
git '/opt/fenestra' do
  action :sync
  repository 'https://github.com/osuosl/fenestra'
  revision 'master'
end

chef does still create a deploy branch. I want master to master. How to achieve that?

@aronwoost That is expected behavior. Is there a reason the deployed branch has to be master? If so, there isn't a great way to do this right now.
revision is what you change to change what the repo tracks
checkout_branch is the local branch that is checked out at whatever revision is. As @iankronquist originally mentioned, having checkout_branch set to master causes errors, because the underlying git checkout command fails.

@aronwoost The reason for the branch name being deploy is beyond me. Perhaps @danielsdeleo can shed some light on that. I agree it probably isn't the most intuitive choice for the average bear.

https://github.com/chef/chef-docs/issues/552#issue-90142019 explains why the behavior is the way it is. As for the name "deploy", that comes from Capistrano (as of 5ish years ago). Originally, some folks at engine yard adapted the capistrano code to make a "deploy" resource in Chef (as a gem external to Chef), which was supposed to be able to "take over" an existing capistrano deployment and just work, so you could move EC2 nodes into EY Cloud. I moved that deploy resource into Chef and extracted the git and svn code into separate resource/provider pairs so you could use them outside of the capistrano stuff, but that all was supposed to be compatible with the existing EY stuff so we wouldn't break them in the process of adding the features to core.

I did get this to work using the following snippet:
git "/var/xxx" do
  repository "git@github.com:xxx/xxxx.git"
  user "xxx"
  group "xxx"
  revision "master"
  checkout_branch "master"
  enable_checkout false
  action :sync
end

Is this not the right/one way to do it? Or am I missing something?

Copying from the other issue ( https://github.com/chef/chef/pull/3289#issuecomment-113790597 )
The git provider is designed to work two ways:

You want to always sync a particular commit (which can change over time based on use of attributes, etc.). In this case you identify what commit you want from the upstream repo using the revision property of the git resource. The git provider will locally maintain its own branch and force it to whatever commit you want. This way, if you want to switch from one branch to another, or only deploy certain tags (maybe you set with attributes or a data bag item), you just set the revision and the provider will always ensure you're on the correct commit by checking git ls-remote on the upstream repo.

You want to do a one-time checkout. Usually this happens when you're maintaining developers' laptops with Chef. In this case, you set enable_checkout to false which prevents the git provider from attempting to checkout master to master. This usage was sort of bolted on to the git provider after use case (1), so it's a bit unwieldy, I admit.

@pkyeck that is the correct usage for use case # 2.

@danielsdeleo thanks for the detailed answer.
(2) is exactly what I was trying to achieve - so all good :) cc @aronwoost


Fixed "Contributing section of the Developer Guide" link

Current link shows error and it's moved to a different page.
Added the link of Contribution Process

Thanks for fixing this link!


OU based filtering and Group writeback feature

If we use OU Filtering to only select some parts of the AD, in the documentation it is precised to select the locations where the group writeback is enabled if this feaature is enabled.
I did exactly this setup but all my groups are now with a sync-generic-failure when they are sync from AD to AAD. This error happens during a Delta Synchronization.
The Stack Trace error is:
An error occurred, ..\ObjectNamespace.cpp(666), code 80230218,
 BAIL: MMS(4024): ..\syncrulesimp.cpp(256): 0x80230218 (Provision under phantom parent or without a parent.)
BAIL: MMS(4024): ..\syncrulesimp.cpp(574): 0x80230218 (Provision under phantom parent or without a parent.)

In the connector Space Object Properties, the difference is the Distinguished Name.
The old one is CN=Group_Numbers,OU=WRITEBACK,OU=GROUP,DC=mydomain,DC=com
The new one is CN=Group_Numbers,CN=Deleted Objects,DC=mydomain,DC=com
It changes from my specific OU to "deleted objects"
Thanks for your feedback
[Enter feedback here]

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

ID: faed3c33-d05e-7a05-1327-27a79325f677
Version Independent ID: 151a61e3-ea34-7716-bbc8-66177f768b7b
Content: Azure AD Connect sync: Configure filtering
Content Source: articles/active-directory/hybrid/how-to-connect-sync-configure-filtering.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@Cherif-Git Thank you for your feedback . We will investigate and update the thread further.

Hi @Cherif-Git,
Do you have Parent OU name GROUP and Child OU named WRITEBACK present in your domain?
Without getting a closer look at your environment it will be hard for me to know what could be causing this error. Please open a support case as the error appears to be due to some configuration issue.

Yes I do have a Parent OU named GROUP and Child OU WRITEBACK.
I'll create a support case.
Thank you


Auto cron schedules

Checklist

[ ] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

Explain the details for making this change. What existing problem does the pull request solve?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

discussed in standup:

add tags system production and development to backup, check and prune schedules
rename yaml key to productionBackupSchedule


[Concurrency] Add async versions of some functions on Sequence

Resolves rdar://73627252

@swift-ci smoke test

@swift-ci smoke test linux

@swift-ci smoke test windows

@swift-ci smoke test windows

@Catfish-Man I think all of your questions can be answered with: I just copied the non-async functions and added the aync to them 😅.


vault-operator/*: sync with operator-sdk master

This commit updates the vault-operator to work with the master
version of the operator-sdk. This makes the example a better
representation of the current state of the operator-sdk and also
allows us to add e2e tests using the sdk's test framework.

LGTM


Use the same mbed target Id for different mbed-os target

Description
I would like to have different HW package using the same mbed target Id.
In mbedls, database is configuring each target:

u"1234": u"MY_TARGET",

In targets.json mbed-os file, the detect_code macro can be available and is no more used.
"MY_TARGET": {
    "detect_code": ["1234"],

Proposition is to re-use it, and to be able to create a new target using the same detect code Id.
"MY_NEW_TARGET": {
    "detect_code": ["1234"],

mbed test command could work for both targets:
mbed test -m MY_TARGET
will work as usual
mbed test -m MY_NEW_TARGET
will work, even if MY_NEW_TARGET is not in mbedls database
Maybe it could be easier to use directly the target name to detect:
"MY_NEW_TARGET": {
    "detect_code": ["MY_TARGET"],

@MarceloSalazar
@LMESTM
Issue request type
[ ] Question
[x] Enhancement
[ ] Bug

@jeromecoutant thanks for raising this request. I agree with you and believe it's important to have this place to let us introduce different variances of platforms that may require a slightly different configuration.
FYI @ARMmbed/mbed-os-maintainers

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1285

Any chance to get this update soon,
or it is better to find a workaround ? :-)

Hi @jeromecoutant, I'm sorry but it is unlikely we'll get to this anytime soon.

Just for the record: the target names are currently restricted to a maximum of 20 characters...

Thank you for raising this issue. Please note we have updated our policies and
now only defects should be raised directly in GitHub. Going forward questions and
enhancements will be considered in our forums, https://forums.mbed.com/ . If this
issue is still relevant please re-raise it there.
This GitHub issue will now be closed.


Support for optional file validation

Current Behavior:
When using the nestjs-form-data package, it seems that there is no built-in support for handling optional file validation. The library provides excellent support for handling file uploads, but it lacks a feature to easily specify that a file upload is optional and should not trigger validation errors if absent.

Validations used:

Expected Behavior:
I would expect the nestjs-form-data library to have a mechanism to define certain file fields as optional, meaning that if a file is not provided during the upload, it should not trigger validation errors.
Steps to Reproduce:

Attempt to create an endpoint using nestjs-form-data where a file upload is optional.
Upload a request without the optional file field.
Observe that validation errors are still triggered even though the file is optional.

Environment:

nestjs-form-data version: 1.9.0
NestJS version: 9.0.0
Node.js version: 18.12.0

Additional Context:
I believe that adding support for optional file validation would enhance the usability and flexibility of the nestjs-form-data, especially in scenarios where certain files are not required for every upload.

@mondyfy
Hi! Thanks for your feedback!
For mark field as optional use @IsOptional() decorator then class-validator will know that the field is optional.
Here's an example

Please close your issue if it is solved

Sorry I missed that part, the issue was with the null value passed in the key:
curl --request POST
--url http://localhost:3000/api/v1/candidate-story
--header 'Content-Type: multipart/form-data'
--form file=
closing as completed


Bug: some values are not converted correctly

Added some of the columns to the example.vcf for debugging

The issue is that the header logic appears to not look for info fields in all rows, resulting in the omission of some fields such as "OriginalAlleles" and "SwappedAlleles" in the bug-affected rows.
The solution here should be to extract the INFO from the header columns ("##INFO") rather than the INFO itself, and then use this to compose the columns.

It is possible that the Header does not contain all of the information field values. Thus, the script must still go through all of the entries to find all possible values for the info variables.


Upgrading from version 1.2 to 1.3 makes Pods stuck on Terminating

Hey All,
I want to start by saying that we really like this Kuik solution and think you are doing a great job.
Yesterday we upgraded to version 1.3 and started noticing pods that were being deleted are stuck on terminating.
After a little bit of code digging, we noticed that the finalizer was removed from version 1.3. This of course makes the terminating pods stuck since no one is handling the finalizers anymore.
So we delete all the finalizers from old pods, but I think you need to add a migration part in the documentation and maybe bump the version to 2 since there are breaking changes
Thank you
(Or maybe we are completely wrong and missed something)

Hi @guy-frontegg , Thanks a lot for your feedbacks !
There is a section in the doc explaining the "migration path", BUT if you did not see it, it means that we made a mistake somewhere ...What would be the best way to communicate this kind of info ?

Thank you for your answer, you are absolutely correct and we just saw the upgrade section.
If I could just suggest bumping the Upgrade section to be higher in the readme section.


Translations

From Terry: The translation is not done.  We discussed at least a Google translate option, or a true interpreter. What is progress on that?
Which languages are we doing?

I think we want them to do a real translation, or at least review it. I usually wait until it's done in English.
I recommend Spanish, but we can add as many as are wanted.

Related to #266 which @RamiLorca is working on

Spanish translation is in progress and will be delivered any day.


Disabled packages

Description

Disabled packages should not be counted ((N) Updates message at the bottom-right corner)

Notification should not tell user to restart Atom to apply changes to disabled packages (or, notification shouldn't show up at all) because it makes no sense and just annoying

Both these issues belong in atom/settings-view.


There is no validation when inputting username with "test1"

OS: All
Build Version: 20210512.8
Repro Steps:

F1 --> Click "Create Virtual Machine...(Advanced)" --> Enter a name --> Select Windows/Linux OS --> Select an image --> Input the username with "test1".
Check whether there is a validation or not.

Expect:
There is a validation when inputting the username with "test1", like inputting with username "test".

Actual:
There is no validation when inputting the username with "test1".

More Info:

There is an error when creating this VM with username "test1".

There is a validation when inputting the username with "test1" in portal.

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


⚠ SceneTime has degraded performance

In 8527f02, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1413 ms

Resolved: SceneTime performance has improved in 6307f01.


fix techradar modal width

Hey, I just made a Pull Request!
Fixed the spacing in this table by making the dialog large enough.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ X] Screenshots attached (for UI changes)
[X ] All your commits have a Signed-off-by line in the message. (more info)

I created a new pull request because I made some mistakes in this one: https://github.com/backstage/backstage/pull/19574


fixed CTC regression

While working on #1625 I discovered a regression in our compile-time constant (CTC) visitor introduced when we added instance function calls and loops. This fixes that.

4183606934 the


How do I use the methods inside dynamically added file?

This library is neat. But I have a question - how do I use the services inside a newly loaded angular file? They don't seem to be available for injection. thoughts?

angular-load-module-shim


Add loading indicator (or spinner) while loading resources

When loading resources from the backend, the UI shows an empty list/table. This could be confusing as it is not clear whether Octant is loading the list of resources or if there are indeed no resources in the cluster.
Screen capture:

I think having the default data icon be a spinner until the first response / stream from octant to the UI happens is a good idea. As you mention, this would at least signal that there are no resources of that type.

There are multiple locations that should have spinners:

in navigation
described resources (i.e the lists you see in the dashboard)

I want to investigate solving them both. More details as I have them

This enhancement will be in our next release.

It looks like this may have been removed / broken in the 0.7.0 release.


Failed detection in injection_sql plugin

Describe the bug
injection_sql.py plugin fails to check hardcoded_sql_expressions on certain test cases.
To Reproduce
Steps to reproduce the behavior:

Create test.py file with content:

"SELECT a " + "FROM " + vuln

Run bandit: bandit test.py
There are no detected issues in the console output

Expected behavior
The above test.py file should generate hardcoded_sql_expressions issue.
Bandit version

1.6.2

In order to fix this bug, an additional module needs to be added to the code which checks the string on the left from the add operator to contain a keyword (SELECT) followed by a random string (an attribute name) and the string to the right to contain a keyword (FROM).
And also, the query ("SELECT a " + "FROM " + vuln) needs to be added in their example scripts to be more informative to the users of Bandit.


Start validating message queue payloads with the schema

Currently just log failures, and continue as normal.
This is dependant on https://github.com/alphagov/govuk-content-schemas/pull/333

Hi. Is the plan to do this validation in all environments? The integration environment, even though it represents the master branch, is a shared testing area so it's quite likely that a change from one team could stop another team testing their work.
Maybe that is a good thing of course..

@thehenster I'm still getting up to speed on the use of the schemas, so I'm not too sure.
This change should not break anything, as it just does reporting on the output of the publishing api.
I've gone round the wiki and tagged all the pages relevant to this repository [1], which I have not read in detail yet, but might describe the intent of others regarding the use of the schemas.
1: https://gov-uk.atlassian.net/wiki/dosearchsite.action?cql=siteSearch+~+"labelText%3Agovuk-content-schemas"&queryString=labelText%3Agovuk-content-schemas

Cool.
I'm not sure what the answer to the problem is.. The purpose of the environment integration is in the name isn't it. It's supposed to check that stuff integrates together.
An "integrates in isolation" environment would require the whole stack with just your changes in it. As we don't have QAs here then perhaps this is just our development environments..

Closed in favor of https://github.com/alphagov/publishing-api/pull/387


dbt flow fails to sync back

Hi there,
I think I hit a strange bug :|
Bug summary:
I'm defining a flow that triggers a dbt cloud job, which should wait until it finishes. Fails instead.
Repro:
prefect 2.4.0
prefect-dbt 0.2.2
python 3.8.10
from prefect import flow
from prefect_dbt.cloud import DbtCloudCredentials
from prefect_dbt.cloud.jobs import trigger_dbt_cloud_job_run_and_wait_for_completion
import constants

@flow(name="trigger_dbt_cloud_job")
def trigger_dbt_cloud_job():
    run_result = trigger_dbt_cloud_job_run_and_wait_for_completion(
        dbt_cloud_credentials=DbtCloudCredentials(
            api_key=constants.dbt["auth_token"],
            account_id=int(constants.dbt["account_id"]),
            domain=constants.dbt["domain"]
        ),
        job_id=int(constants.dbt["jobs"]["qa"]["dev_test_job"])
    )

trigger_dbt_cloud_job()

Expected behavior: trigger the flow and wait until it finishes.
Actual behavior: the dbt cloud job gets triggered, but the prefect flow fails while checking for job status.
Complete error message:
16:52:54.757 | INFO    | prefect.engine - Created flow run 'ingenious-chameleon' for flow 'trigger_dbt_cloud_job'
16:52:55.067 | INFO    | Flow run 'ingenious-chameleon' - Created subflow run 'manipulative-newt' for flow 'Trigger dbt Cloud job run and wait for completion'
16:52:55.119 | ERROR   | Flow run 'manipulative-newt' - Encountered exception during execution:
Traceback (most recent call last):
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 588, in orchestrate_flow_run
    result = await flow_call()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect_dbt/cloud/jobs.py", line 287, in trigger_dbt_cloud_job_run_and_wait_for_completion
    run_id_future = get_run_id.submit(triggered_run_data_future)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/tasks.py", line 492, in submit
    return enter_task_run_engine(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 740, in enter_task_run_engine
    return flow_run_context.sync_portal.call(begin_run)
AttributeError: 'NoneType' object has no attribute 'call'
16:52:55.152 | INFO    | Flow run 'manipulative-newt' - Created task run 'Trigger dbt Cloud job run-e4229069-0' for task 'Trigger dbt Cloud job run'
16:52:55.152 | INFO    | Flow run 'manipulative-newt' - Submitted task run 'Trigger dbt Cloud job run-e4229069-0' for execution.
16:52:55.783 | INFO    | Task run 'Trigger dbt Cloud job run-e4229069-0' - Triggering run for job with ID 2
16:52:56.490 | INFO    | Task run 'Trigger dbt Cloud job run-e4229069-0' - Run successfully triggered for job with ID 2. You can view the status of this run at https://<hidden_domain_on_purpose>.getdbt.com/#/accounts/1/projects/1/runs/579/
16:52:57.111 | INFO    | Task run 'Trigger dbt Cloud job run-e4229069-0' - Finished in state Completed()
16:52:57.162 | ERROR   | Flow run 'manipulative-newt' - Finished in state Failed('Flow run encountered an exception.')
16:52:57.163 | ERROR   | Flow run 'ingenious-chameleon' - Encountered exception during execution:
Traceback (most recent call last):
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 595, in orchestrate_flow_run
    result = await run_sync(flow_call)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/utilities/asyncutils.py", line 57, in run_sync_in_worker_thread
    return await anyio.to_thread.run_sync(call, cancellable=True)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/bogdan/_dev/<hidden_domain_on_purpose>_corporate_it/orchestration-tools-poc/prefect/v2/main.py", line 9, in trigger_dbt_cloud_job
    run_result = trigger_dbt_cloud_job_run_and_wait_for_completion(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/flows.py", line 384, in __call__
    return enter_flow_run_engine_from_flow_call(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 162, in enter_flow_run_engine_from_flow_call
    return run_async_from_worker_thread(begin_run)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/utilities/asyncutils.py", line 137, in run_async_from_worker_thread
    return anyio.from_thread.run(call)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/from_thread.py", line 49, in run
    return asynclib.run_async_from_thread(func, *args)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 970, in run_async_from_thread
    return f.result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 444, in result
    return self.__get_result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/client.py", line 103, in with_injected_client
    return await fn(*args, **kwargs)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 521, in create_and_begin_subflow_run
    return terminal_state.result()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/orion/schemas/states.py", line 143, in result
    raise data
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 588, in orchestrate_flow_run
    result = await flow_call()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect_dbt/cloud/jobs.py", line 287, in trigger_dbt_cloud_job_run_and_wait_for_completion
    run_id_future = get_run_id.submit(triggered_run_data_future)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/tasks.py", line 492, in submit
    return enter_task_run_engine(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 740, in enter_task_run_engine
    return flow_run_context.sync_portal.call(begin_run)
AttributeError: 'NoneType' object has no attribute 'call'
16:52:57.194 | ERROR   | Flow run 'ingenious-chameleon' - Finished in state Failed('Flow run encountered an exception.')
Traceback (most recent call last):
  File "/home/bogdan/_dev/<hidden_domain_on_purpose>_corporate_it/orchestration-tools-poc/prefect/v2/main.py", line 19, in <module>
    trigger_dbt_cloud_job()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/flows.py", line 384, in __call__
    return enter_flow_run_engine_from_flow_call(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 158, in enter_flow_run_engine_from_flow_call
    return anyio.run(begin_run)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_core/_eventloop.py", line 70, in run
    return asynclib.run(func, *args, **backend_options)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 292, in run
    return native_run(wrapper(), debug=debug)
  File "/usr/lib/python3.8/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 287, in wrapper
    return await func(*args)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/client.py", line 103, in with_injected_client
    return await fn(*args, **kwargs)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 238, in create_then_begin_flow_run
    return state.result()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/orion/schemas/states.py", line 143, in result
    raise data
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 595, in orchestrate_flow_run
    result = await run_sync(flow_call)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/utilities/asyncutils.py", line 57, in run_sync_in_worker_thread
    return await anyio.to_thread.run_sync(call, cancellable=True)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/home/bogdan/_dev/<hidden_domain_on_purpose>_corporate_it/orchestration-tools-poc/prefect/v2/main.py", line 9, in trigger_dbt_cloud_job
    run_result = trigger_dbt_cloud_job_run_and_wait_for_completion(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/flows.py", line 384, in __call__
    return enter_flow_run_engine_from_flow_call(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 162, in enter_flow_run_engine_from_flow_call
    return run_async_from_worker_thread(begin_run)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/utilities/asyncutils.py", line 137, in run_async_from_worker_thread
    return anyio.from_thread.run(call)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/from_thread.py", line 49, in run
    return asynclib.run_async_from_thread(func, *args)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 970, in run_async_from_thread
    return f.result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 444, in result
    return self.__get_result()
  File "/usr/lib/python3.8/concurrent/futures/_base.py", line 389, in __get_result
    raise self._exception
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/client.py", line 103, in with_injected_client
    return await fn(*args, **kwargs)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 521, in create_and_begin_subflow_run
    return terminal_state.result()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/orion/schemas/states.py", line 143, in result
    raise data
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 588, in orchestrate_flow_run
    result = await flow_call()
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect_dbt/cloud/jobs.py", line 287, in trigger_dbt_cloud_job_run_and_wait_for_completion
    run_id_future = get_run_id.submit(triggered_run_data_future)
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/tasks.py", line 492, in submit
    return enter_task_run_engine(
  File "/home/bogdan/.virtualenvs/orchestration-tools-poc-prefect-v2/lib/python3.8/site-packages/prefect/engine.py", line 740, in enter_task_run_engine
    return flow_run_context.sync_portal.call(begin_run)
AttributeError: 'NoneType' object has no attribute 'call'

I think this is related to calling an async flow using sync flow
https://github.com/PrefectHQ/prefect/pull/6514/files#diff-ae6f1b6d423c9f28188aedf4ab0f0afbce428d61b84feed78ca9c716ce3e26caL158
Not sure why the sync_portal is None though.

It looks like the same issue here: https://discourse.prefect.io/t/attributeerror-nonetype-object-has-no-attribute-call-on-sync-portal/1638

Okay we found the issue; this reproduces it.
from prefect import flow, task

@task
def test_subtask(obj):
    return obj.get("id")

@flow
async def test_async_flow():
    obj = {"id": 123}
    return test_subtask(obj)

@flow
def test_sync_flow():
    test_async_flow()

test_sync_flow()

Essentially, Prefect gets confused when sync flow calls async flow calls sync task; sync_portal does not get started.
Will try to get a PR in core Prefect to fix this.


The issue of upgrading to a larger version

Is there an existing issue for this?

[X] I have searched the existing issues

Use case
flutter_quill: ^8.6.4   ----->         flutter_quill: ^9.0.3
Proposal

I will encounter this error when upgrading from 8.6.4 to 9.0.3

Clean the project, rerun flutter pub get and the issue should be solved, even though I didn't have to in the example so I don't know why
can you share more info?

I have tried the first method, but it's not possible

can you share more info?
The example is possible, but when combined with other packages, it may conflict

yes package issue with me the same in v 9.x.x and it work in mac os but windows not work

Please make sure to follow the instructions on super clipboard plugin

This will be closed since we have no responses from the OP. Please, reopen if is needed (i think that wont be the case since we remove quill_html_converter and super_clipboard is being removed from the fluter_quill_extensions).


enableDirtyFormCheck function doesn't take into account keyboard shortcuts

The function in wagtailadmin/core.js that raises a warning if the user attempts to navigate away from the page without saving does not understand that if the keyboard shortcut is used to (e.g.) save draft, the $trigger for the event is the currently focused element, and not the actual submit button. This means that if a user edits the page and then uses ctrl+s to save, a warning pops up saying "Are you sure you want to leave the page?" Which is confusing and defeats the purpose of a shortcut .

Thanks for the report, @ptink. Is this something you could help with?

Fixed in #2526


Fixed small error in BMI calculator basic example

In the final listing of the BMI calculator basic example there is a small error with the input declaration. It's missing the attr key in the config object.
Fixes #783

[x] There exists an issue discussing the need for this PR
[x] I added new tests for the issue I fixed or built
[x] I ran make test FOO for the package FOO I'm modifying
[x] I used make commit instead of git commit

Hi @alexdennis  :)
Thanks for submitting this PR, we appreciate any kind of desire to help. Note that the html files are not meant to be edited directly because they are generated from the markdown files in docs/content. I'll do these markdown changes and generate the html, no worries


Support for Windows Display Names

In a database I have timezones with Windows Display Names such as "(UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna". Seems like those are not currently supported
in general: thanks for this library, it solves a real problem for me, timezones are a mess and everything that helps is more than welcome :)

@aersam Glad I could help!
IIRC, the original reason I wrote this was to map those sorts of names to proper IANA timezones.
So they're supported in that sense. What were you trying to do but couldn't?


Create Data Model and Lock Object in SAP Cloud Platform ABAP Environment

Tutorial URL: https://developers.sap.com/tutorials/abap-environment-lock-object.html
Please specify the step you are referring to: 5
The used standard association view 'I_BusinessUser' is not whitelisted in ABAP cloud so it is not permitted to be used:
The following error is shown:
Use of Entity I_BusinessUser is not permitted.
ABAP Syntax Check Problem
define root view Z_I_ROOM_XXX as select from zroom_xxx as room
  association [0..1] to I_BusinessUser as _SAPSysAdminDataChangeUser on _SAPSysAdminDataChangeUser.UserID = room.lastchangedbyuser

Hi @sedacrivity ,
you need a licensed user to do this tutorial. This won't work with a trial user.
Best regards,
Merve

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Blockhash not found

error Error: failed to send transaction: Transaction simulation failed: Blockhash not found

https://stackoverflow.com/questions/70717996/blockhash-not-found-when-sending-transaction
Stack Overflow
Blockhash not found when sending transaction
When sending a transaction using Solana web3, it sometimes shows this error:
Error: failed to send transaction: Transaction simulation failed: Blockhash not found
What is the proper way of dealing ...
Image
maybe can add maxRetries: 5
Most likely, the user is taking too long to sign the transaction, so by the time you send the transaction, the blockhash has expired.
https://solana.stackexchange.com/questions/6093/blockhash-not-found-when-sending-transaction


Correcting source of candidate SA data for panel packs

Background
On a recent exercise, it emerged that the panel packs were pulling the candidate SA data not from the extracted content on Application view, but from the uploaded original SA document, which is only there as a back-up. This needs to be remedied.
User Story
As an Admin, I would like the SA data appearing in the panel packs to be based on the content extracted from candidate uploads after they have made edits and submitted so that I can be sure the final candidate version is shared with panels.
Feature(s) Description

[ ] Pull the SA content for the panel packs from the extracted and edited content in Application view NOT from the uploaded Word document

Acceptance Criteria
It's done when the panel packs display the final, edited candidate SA data output onto Application view from the extraction process.
Definition of Done

[ ] User stories/acceptance criteria met
[ ] Internal reviews passed (feedback actioned)
[ ] User testing passed
[ ] Relevant technical documentation updated
[ ] User guidance updated
[ ] Deployed and merged without errors

User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Akua/Abbey

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @warrensearle


tfsec does not see variables in the modules

We use our repo with custom google modules for terraform. We set default variables in modules. But when we run tfsec, tfsec doesn't see the variables and we have warning. But if we set variables in the main project all is fine and we don't see warning. For us, it is not convenient and is a problem. How can we force tfsec to read variables from the modules?

I have the same issue. For example using the following module: https://github.com/terraform-aws-modules/terraform-aws-s3-bucket with the most basic setup like the following snippet gives S3 bucket level warnings which are are all blocked by the module variables.:
module "s3_bucket" {
  source  = "terraform-aws-modules/s3-bucket/aws"
  version = "3.6.0"

  bucket = var.bucket_name

  # S3 bucket-level Public Access Block configuration
  block_public_acls       = true
  block_public_policy     = true
  ignore_public_acls      = true
  restrict_public_buckets = true

  acl = "private"
}

I am currently forced to add the following on top of the module because its not interpolating correctly:
  # tfsec:ignore:aws-s3-block-public-policy
  # tfsec:ignore:aws-s3-ignore-public-acls
  # tfsec:ignore:aws-s3-no-public-buckets
  # tfsec:ignore:aws-s3-specify-public-access-block

we are observing the same issue with module code.
Our postgres module has some default configuration parameter defined, which are not recognized by tfsec
locals {
  pgconfig_default = {
    "log_connections" = "on"
    "log_checkpoints" = "on"
    "connection_throttling" = "on"
  }
  pgconfig = merge( local.pgconfig_default, var.config_settings )
}

resource "azurerm_postgresql_configuration" "postgresql_configuration" {
  for_each = local.pgconfig
  name                = each.key
  resource_group_name = var.resource_group_name
  server_name         = azurerm_postgresql_server.postgresql_server.name
  value               = each.value
}

Wrong failed tests are

Ensure server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database Server
Ensure server parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server
Ensure server parameter 'log_connections' is set to 'ON' for PostgreSQL Database Server

So, how can this be fixed?

This issue is still ongoing and prevents additional problems when trying to use a wrapper around the community modules as tfsec doesn't see the exceptions.

Hi @igimot !
Our efforts have moved to Trivy.
It seems I can't reproduce the problem using Trivy.
Config:
variable "versioning" {
  type = bool
  default = true
}

resource "aws_s3_bucket" "this" {
  versioning {
    enabled = var.versioning
  }
}

Trivy output:
trivy config . | grep "versioning enabled"
2023-09-02T16:44:43.311+0700    INFO    Misconfiguration scanning is enabled
2023-09-02T16:44:43.664+0700    INFO    Detected config files: 2

/cc @simar7


Sending colored content to .splash

I have colored content I'd like to send to splash, but it is rendering incorrectly.
What would I need to do. There is only color codes in the string I am sending in.
Thanks

What if there was a way to pass in the width of the actual text to center?
Would splash still be the best way to do it or would I need another method to add in the raw content?

Hmm, passing the width could remove that requirement I suppose -- but it could take some work -- splash just uses put which looks for either text or format => text pairs, so this method would probably need a way to take text that also had escape sequences...things would get unfortunate when callbacks are triggered and the text conatins formatting codes though, so if there's a way to separate them I think that's ideal.


[material-ui-icons] Icons have no TS typings

The icons from material-ui-icon have no TS typings, so there's no way to import them without getting a (Could not find a declaration module for module FOOBAR) warning.
The only workaround is to use an old const AddIcon = require('material-ui-icons/Add').default;

[X] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Icons from the package should have a typing so TS doesn't generate a warning when importing them.
Current Behavior

Importing them generates a TS warning, having to resort to require
Steps to Reproduce (for bugs)

import AddIcon from 'material-ui-icons/Add';
Your Environment

Tech
Version

Material-UI
1.0-beta9

React
15

browser
Chrome 61

TS
2.5.2 on strict mode

In the currently released version there is only an index.d.ts. IMHO a new release should resolve this.
@oliviertassinari I noticed this to, but just imported from index for now. Do you have time to cut a new release?

@sebald I will cut a release this evening.

Published 🎉


Build automation to verify/manage drift across repositories

Is your feature request related to a problem? Please describe.
We currently rely on opening GitHub issues and manual intervention to align repositories across this organization for such things as copyright notices. When these change, such as in https://github.com/opensearch-project/.github/pull/24, there are no guarantees that everybody applies the changes in a timely manner.
Describe the solution you'd like
A mechanism that evaluates drift across repositories for such things as common files and opens GitHub issues automatically. This mechanism would support common types of things: files must match 100% (e.g. code of conduct), files must contain text (e.g. copyright notice as is), files must be present (e.g. developer_guide), TOC must be present in README, etc.

Hi @dblock, I had some solution in mind but I forgot to post over here last month.
I will try to explain it in different steps.
The implementation of the below explanation should go in the opensearch-project/.github repository.

Make sure all the repos have the same content of the common files (code-of-conduct, license, opensearch.svg, etc.)
Make a github action which gets triggered when there is a push event to such common files.
Whenever it is triggered, it should open an issue in all the repositories with the maintainers assigned or commented atleast. Still need to evaluate if create-an-issue-in-all-repos can be used.
We can use JasonEtco/create-an-issue but can't think of how to assign different maintainers. (We can have some yml file which has the repository name and maintainers name and some script which does the job.).

- opensearch:
  - name: "OpenSearch"
  - maintainers:
    - name: "dblock"
    - name: "CEHENKLE"
- opensearch-py:
  - name: "opensearch-py"
  - maintainers:
    - name: "rushiagr"

A mechanism that evaluates drift across repositories for such things as common files and opens GitHub issues automatically.

This would target this problem.
We can extend this a bit to target the second problem. (optional)

This mechanism would support common types of things: files must match 100% (e.g. code of conduct), files must contain text (e.g. copyright notice as is), files must be present (e.g. developer_guide), TOC must be present in README, etc.

The implementation of the below explanation should go in the all the individual repositories (example opensearch-project/opensearch-py).

In step-2 of the previous solution, we need to configure so that it adds a label (some unique label maybe mismatch) too while opening the issue.
The individual repositories  (opensearch-project/opensearch-py) should have a github action which gets triggered when an issue is opened with a particular label (here mismatch).
The action should clone both the repositories opensearch-project/.github and opensearch-project/opensearch-py, and check the difference between files using diff command.
I think there is a way to add the required changes using diff command itself. https://www.computerhope.com/unix/udiff.htm
Once the file is updated, we can open a PR using peter-evans/create-pull-request to the same repository.
If possible, assign the maintainers or comment their names.

Sorry, but I haven't worked on the whole solution. These are mere hacks when I was thinking about the issue. There might be some barriers which I might have missed.
Please let me know what do you all think. I'm willing to work if someone is willing to help/guide and reviewing the PRs along the way.
Thanks.
Best,
Venu

Are you planning to take a stab at this? I would be more than happy to review PRs and help out!

I didn't have enough time to put in during that time, but I would like to take a shot now!
I will be working on this if this is open.

Moving this to metrics repo categorizing it under project health.


Change the "Change was Successfull-bar" to a Tooltip/Overlay

If you change a version inside a build, you get notified that the "change was successful" (with this little bar at the top of your build) this shifts the whole list down and if you are editing the 100th mod you can't even see this message/bar , so it would be nice if it would be changed to a tooltip next to your mouse so that the whole list doesnt get shifted :) or maybe just make the thing that pops up at the top be a Overlay or something so the whole lsit stays where it is. I is irritating when the whole list is moving down and then up again.

Good suggestion! Similar to #144

ohh ok yes that would be pretty similar, didnt saw this one

Yeah.

I also think this would be a very helpful change, as I have messed up version changes countless times due to all the shifting.

I like this, can we please have it?


dailyUsageSummary output CSV one line per date

closes #72

should this fix #74 first too before merging?


Clarifies usage of jit(init) in WMT example

Closes #879

Codecov Report

Merging #910 (c872f5f) into master (e14840e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #910   +/-   ##
=======================================
  Coverage   81.06%   81.06%
=======================================
  Files          55       55
  Lines        4374     4374
=======================================
  Hits         3546     3546
  Misses        828      828

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e14840e...c872f5f. Read the comment docs.

Codecov Report

Merging #910 (c872f5f) into master (e14840e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #910   +/-   ##
=======================================
  Coverage   81.06%   81.06%
=======================================
  Files          55       55
  Lines        4374     4374
=======================================
  Hits         3546     3546
  Misses        828      828

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e14840e...c872f5f. Read the comment docs.


Add 2.6 release notes

Description
Add 2.6 release note
Issues Resolved
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@VijayanB I dont think this PR needs to be tagged as Maintenance and Docs. Maybe just docs? Also, can backport tags be added?

@jmazanec15 Am i missing any change?


Issue26

This change modifies the way we handle requests for GET/POST /db/_all_docs.

if a request for /db/_all_docs is received without a keys parameter, then we access a MapReduce view which is already indexed by com_cloudant_meta.ownerid, so can return a users documents quickly.
if a request for /db/_all_docs?keys=["a","b","c"] then we simply hit Cloudant's _all_docs endpoint
both methods go through a filtration process to ensure that only that user's documents are returned.

The idea is to ensure that calls to /db/_all_docs (without parameters) can be serviced in performant and scalable way, even when a user's documents represent a small subset of a much larger collection.
It's important to note here that Envoy's /db/_all_docs endpoint doesn't provide all of the functions of a Cloudant _all_docs endpoint: we only support _all_docs with no parameters and _all_docs with a keys parameter.

+1


Adding mikkt tangent support to CSG objects

CSG objects now calculate tangents so normal mapping will work. Most CSG objects don't calculate very nice UVs so not sure how useful this is but it does work very well with CSGMesh and CSGPolygon.
Here is an example of using two CSGMesh objects in combination with a cube and sphere mesh primitive:

Request from @reduz was to make it possible to turn off the tangent calculation if its unwanted as it can eat up performance. It will be enabled by default and only applied on the final mesh. Commit to follow

Hey, I'm not sure if it has to do with this but, if I use an ArrayMesh I generate from code, i get the normals as in the picture, quite strange as in a regular Mesh does not do that.

terrain.zip
It can be because the mesh is composed of 16 surfaces? Or the way I built it, not sure.
Should I open a separate issue?

@Toshiwoz , this looks like a difference between smooth and non-smooth shading.

Owh and yes, raise a new issue I'd say or it'll get lost ;)


Fix an UnboundLocalError if a compiler fails.

Depending on where an exception is raised inside a compiler's
execute_command, the stdout variable may not be assigned. In this case, the
finally handler would fail with an UnboundLocalError, hiding the true cause
of the exception. This change adds a new variable, stdout_name, which is
populated once we've actually created the file. After this, the CompilerError
is successfully raised with the contents of the true error.

A quick note to the maintainer that I included the fix for this in my compiler/compressor unit tests pull request (#531) in commit https://github.com/theatlantic/django-pipeline/commit/9d7c6c0ddca7f3781b46a7809d0bf30c40fbc894 . If this gets merged it will create a merge conflict, so I'll keep an eye out (as that would be relatively easy to resolve).

Oops. Thanks for the fix.
:runner: :evergreen_tree:


Error after starting a route

Hello,
I am having a problem after setting a route and trying to get the vehicle to move forward through Apollo. I am using this implementation of Apollo with the Carla simulator. I wonder if anyone has had this error message and has any suggestions on how I can resolve it?
System information

Ubuntu Server 20.04.6
Apollo version 8.0

Steps to reproduce the issue:

Open apollo client: http://localhost:8888/
Select "Task" in the sidebar and turn on "Camera Sensor" in "Others".
Select "Layer Menu" in the sidebar and turn on "Point Cloud" in "Perception".
Select "Module Controller" in the sidebar and turn on "Routing" module.
Select "Route Editing" in the sidebar.
Click "Add Point of Interest" and left click at any point on the road to set the destination.
Click "Send Routing Request".
Select "Tasks" and click "Setup" to start co-simulation.

Supporting materials (screenshots, command lines, code/script snippets):
Error
E0403 22:18:33.270490 6624 channel_manager.cc:326] [spawn_objects] newly added writer(belongs to node[conti_radar_front])'s message type[apollo.drivers.ContiRadar] does not match the exsited writer(belongs to node[cyber_bridge_node])'s message type[apollo.drivers.PointCloud].
Image

I also received the same error message. May I know the reason and how to resolve it? Thank you very much

Will check and feedback then!


Reduce to max of 2 retries

In main codebase, drop from 5 to 2 max_tries within the retry() code chunk. This makes it consistent with how we've been running model runs on Tallgrass -- those have been run within the denali_glm_tests branch on Tallgrass, which makes this reduction and also times different parts of the run_glm3_model() Function. For the next full re-runs I'd like to run on the main branch and keep that drop in max_tries but not the timing variables, as they increase the size of the tibble returned by run_glm3_model()

Merging b/c already tested and very minor


api field as password field

I think it is better to take the API fields as the keyword field.

the API can not be seen when you enter it
password databases recognize the field automatically

Thanks!


FontAwesome doesn't work without adding ionicons.ttf?

I followed the instructions, added foundation-icons.ttf and ran the project from Xcode but it crashed on launch with the following error:
2015-11-29 16:55:01.645 ReactNativeIconsTest[94365:5697032] *** Assertion failure in +[FAKIonIcons registerIconFontWithURL:], /Users/simonwade/Temp/ReactNativeIconsTest/node_modules/react-native-icons/ios/ReactNativeIcons/Libraries/FontAwesomeKit/FAKIcon.m:14
2015-11-29 16:55:01.653 ReactNativeIconsTest[94365:5697032] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Font file doesn't exist'

I fixed this by adding ionicons.ttf to the Bundle Resources.

This is my bad. I was actually asking for ion|beer.


Container logs choke angular sanitization parser

Cannot view logs due to javascript error:
http://cl.ly/image/3r31341M243t
This happened after upgrading to Docker 1.9
Here is log content returned from the shipyard api:
cfda-program-container-log.txt

Same issue here -- Log page loads but does not render any content.
Interestingly #677 and #676 both are having issues related to Spring - I am also trying to output Spring logs and Angular's parser is erroring out. I wonder there is some magical escape character present in Springs build/startup that is causing the problem here.
My Shipyard log API response

@dddanmar Would you be able to test out PR #749 to see if it fixes your issue?


Make sqlite bundling optional

Codecov Report

Merging #110 (a036a74) into master (454d73c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #110   +/-   ##
=======================================
  Coverage   71.94%   71.94%
=======================================
  Files          28       28
  Lines        1554     1554
=======================================
  Hits         1118     1118
  Misses        436      436

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 454d73c...32cd4b1. Read the comment docs.

That's an interesting (but reasonable) way to do it :-). I think I used:
[features]
default = ["bundled-windows"]

bundled-sqlite = ["rusqlite/bundled"]
bundled-windows = ["rusqlite/bundled-windows"]

I think I find mine a bit easier to read. Thanks for showing this variant, I did not know about the syntax to re-export features. It also clarifies what I was reading earlier today in the Cargo.toml from the image crate.


⚠ Bofrost.fr has degraded performance

In 610e6d8, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1552 ms

Resolved: Bofrost.fr performance has improved in 19143ee after 2 hours, 13 minutes.


Comments being published on blog's Mastodon profile

Quick summary
After updating to 2.0.1 (I skipped 2.0), new comments in WordPress, from registered users without publish_posts permission), are being cross-posted to blog's profile on fediverse. See: https://mastodon.social/<EMAIL_ADDRESS>Steps to reproduce

Register a new user as subscriber;
Activate blog profile in ActivityPub plugin settings (authors profiles are deactivated);
Registered user posts a comment;
Comment appear as a comment made by the blog's profile on Mastodon.

What you expected to happen
WordPress comments from nobody shouldn't appear on blog's profile on Mastodon.
What actually happened
WordPress comments by registered users appear on Mastodon as replies by blog's profile.
Impact
Some (< 50%)
Available workarounds?
No but the platform is still usable
Logs or notes
No response

Thanks, this is indeed a bug!
I was able to find the comment:
https://manualdousuario.net/mesa-de-trabalho-felipe-souza/comment-page-1/#comment-237679

Ah! this only works if you only have enabled the blog-user. Thanks for the report!

@pfefferle I'm sorry if I misunderstood you, but in my case it's not working as intended, right?

Yes, I just needed an excuse why I hadn't thought of it myself yet 🫣

Sorry to bring this up again, but wouldn't it make sense this somehow fit into a "better" post/comment "validation" strategy? See also #631 where I was able to federate a private post, simply because federation was delayed (in this case, due to me having WP Cron disabled, but there are more scenarios where federation happens either "too late," or even "too soon"). 😬

sure, and I am currently working on it, but in case of the comments it is not trivial :(

Something like an is_post_valid() helper function or so, that checks whether the post or comment author still exists, is allowed to publish posts, the post (if it's a post) is really still public at the time of federation, or the comment (if it's a comment) still approved?
And then it should probably be run/checked against not only when scheduling but also right before actual federation.

In my crossposting plugin, I basically do this: https://github.com/janboddez/share-on-mastodon/blob/3d26953f286e068edfb4d396c2a74f8c8aa27cd4/includes/class-post-handler.php#L476-L490
In my Webmention plugin, I'm a bit more pragmatic and only check if a comment was (and still is!) approved: https://github.com/janboddez/indieblocks/blob/4708d4a53e8c43277c61a3bd1139e46f43355d96/includes/class-webmention-sender.php#L152-L167
Not saying this is how it should be done, but it's something.
For webmentions, I'm not worried if me approving someone else's comment triggers a webmention. Most receiving servers will probably not even know how to parse comments and simply ignore the mention.
In the case of ActivityPub, I'd probably also not want someone else to be able to "use" my site to interact with the Fediverse.

Well, I was saying, I liked the idea of having the Transformer classes return an error whenever they "encounter" anything that should not be published.

I am doing nearly the same validation, but maybe at the wrong end (before the scheduling).
I would like to lock myself in for a week and build a real outbox. that would help with scheduling, chunk-processing and at the same time I could also rebuild the validation.

@pfefferle, I have a doubt related to this bug. If I enable blog-users in my blog, is there a way for them to associate their own fediverse accounts so that when they comment in my blog, the comment is published on their fediverse account, instead of<EMAIL_ADDRESS>An example: I have myblog.com and enable ActivityPub plugin and blog-users on it.  When they publishes a comment in my blog logged in as reader1, this comment appears on fediverse as published by<EMAIL_ADDRESS>instead of<EMAIL_ADDRESS>Is that available, or could be a future feature?

This can not be done using ActivityPub! You can not post in the name of a different account, this would be a security problem! To do that you have to use the Mastodon API!

Yeap, I was wondering if ActivityPub plugin could offer an option to link blog accounts to profiles in a different server/instance. It seems (at first thought) as a safe, orderly way to achieve this.

Hmmm, I'm having trouble to picture this. This way, they wouldn't comment in my blog (using the WordPress form)? I see WordPress as a main actor in this scenario, and fediverse as an accessory (something like POSSE, with WordPress as the place to "publish once").

But this way (POSSE) it would not be possible to comment on the blog as user<EMAIL_ADDRESS>and to federate it as user<EMAIL_ADDRESS>

Yeah, it would skip entirely the<EMAIL_ADDRESS>and establish a direct connection of reader1's WordPress account to their fediverse account. Is this scenario out of the plugin's scope? Because it sounds amazing. Add a new field to WordPress profile ("fediverse handle"), plus a checkbox to repost comments there, and we're good to go.
I say this with utmost respect for your awesome work, but current implementation for blog-users creates a limbo, with new accounts created for each user that they can't manage directly — for instance, if someone replies a post or comment by<EMAIL_ADDRESS>on Mastodon, this reader/author isn't notified anywhere (for comments at least, I guess) and can't interact with the person that replied to them.

The problem is, (as I already said) that this is not possible using ActivityPub. This feature would require to implement Mastodons proprietary API and it would require that blog visitors would have to authenticate themselves to your blog with their Mastodon Accounts.
There are two tricky things about this:

It would be a lot of work for simply POSSEing comments to Mastodon and only Mastodon, any other platform has to be implemented separately.
If you Authenticate yourself on "blog.example.com", this blog and its admins would have an Access token, that could be used to post ANYTHING to Mastodon in your name!

I say this with utmost respect for your awesome work, but current implementation for blog-users creates a limbo, with new accounts created for each user that they can't manage directly — for instance, if someone replies a post or comment by<EMAIL_ADDRESS>on Mastodon, this reader/author isn't notified anywhere (for comments at least, I guess) and can't interact with the person that replied to them.

I am currently working on a fix, to only be able to comment to federated comment as Author on the blog or from the Fediverse, to not have this issue any more.
Yes it would separate conversations, but at least there wouldn't be any local answers to federated comments any more.

I understand your point, but in this specific case, POSSE is not the fediverse way to do it.
If someone should answer to a comment thread on your blog using a mastodon account, he has to do it on mastodon and his/her comment will be then federated to your blog!

I see, now I understand your point. It really is a tricky balance to integrate both platforms, and knowing what I've just learned, ActivityPub plugin decisions seems sensible indeed.

Yes, the comment implementation was the hardest one so far! Mixing up a former local comment system with federated and decentralised comments is tricky. I learned a lot from the feedback after the launch of 2.0.0, so comments will be a major topic for quite some more releases.
I totally agree that the current version has not a really good UI/UX, but we will improve it over time!
Thanks for all your feedback, I really appreciate it, even if not everything is possible :)

I had the same problem and would argue we need a way to opt out from posting comments WordPress -> AP, especially in blog user mode.
Specific example: a regular commenter responded on the blog (this did not federate, and I don't think it should). I responded to that comment, logged in as myself.
That response is now federated, leading to an out of context reply showing up in the Fediverse feed. I didn't expect a response to a non-fedi comment to federate. And moreover there is no way for me now to delete that from my feed. (Short of removing the comment on my blog, and even that may not work.)
For me this is a breaking feature: I cannot use my own blogs commenting system in the way I want currently.
Another reason we should be able to opt out: Think of a well read blog where feeding subscribers set their notifications for new posts. Now they would be pinged for every new comment.

Specific example: a regular commenter responded on the blog (this did not federate, and I don't think it should). I responded to that comment, logged in as myself.

This is a bug I am currently working on and I am also adding methods to disable comment federation.

Sorry for commenting on a closed issue @pfefferle but I wasn't sure what exactly has been implemented in the last update. Do comments not federate anymore? Is there a way to opt out? I hesitate to try it on my blog currently for fear of blasting another series of unwanted comments into the fediverse.

@mdingemanse Only comments that are published by an blog user and only in reply to the post or a comment from the fediverse will be federated.
To deactivate comments completely, you can use constants: https://wordpress.org/plugins/activitypub/#constants

ACTIVITYPUB_DISABLE_INCOMING_INTERACTIONS – Block incoming replies/comments/likes. Default: false.
ACTIVITYPUB_DISABLE_OUTGOING_INTERACTIONS – Disable outgoing replies/comments/likes. Default: false.


xSQLServer issue on Azure VM

Hello,
Im using xSQLServer DSC resource through Azure Automation DSC and it returns this issue. It successfully installs SQL Server but something fails.
Best,
Kaido
"Exception":  {

                  "Message":  "PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message: Test-TargetResource returned false after calling set. ",
                  "Data":  {

                           },
                  "InnerException":  {
                                         "ErrorRecord":  "Test-TargetResource returned false after calling set.",
                                         "StackTrace":  "   at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)\r\n   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)",
                                         "WasThrownFromThrowStatement":  true,
                                         "Message":  "Test-TargetResource returned false after calling set.",
                                         "Data":  "System.Collections.ListDictionaryInternal",
                                         "InnerException":  "System.Exception: Test-TargetResource returned false after calling set.",
                                         "TargetSite":  "System.Collections.ObjectModel.Collection`1[System.Management.Automation.PSObject] Invoke(System.Collections.IEnumerable)",
                                         "HelpLink":  null,
                                         "Source":  "System.Management.Automation",
                                         "HResult":  -2146233087
                                     },
                  "TargetSite":  null,
                  "StackTrace":  null,
                  "HelpLink":  null,
                  "Source":  null,
                  "HResult":  -2146233079
              },
"TargetObject":  null,
"CategoryInfo":  {
                     "Category":  7,
                     "Activity":  "",
                     "Reason":  "InvalidOperationException",
                     "TargetName":  "",
                     "TargetType":  ""
                 },
"FullyQualifiedErrorId":  "ProviderOperationExecutionFailure",
"ErrorDetails":  null,
"InvocationInfo":  null,
"ScriptStackTrace":  null,
"PipelineIterationInfo":  [

                          ]

}

Hi
Were there any errors in the SQL setup log file (%programfiles%\Microsoft SQL Server###\Setup Bootstrap\Log)?
Have you checked the DSC logs as well? You can either manually check this in Event Viewer or you could use the xDscDiagnostics  module.
The exception you posted indicates is that the Test-TargetResource function has returned false, so it would appear that something wasn't quite setup correctly but you will need to look at those additional logs to see what.
Hope that helps. Let us know what you find so we can determine if there are any issues to fix in the resource.
Matt

Closing this since there has been no activity on this one. If this problem still exist with recently release module SqlServerDsc v<IP_ADDRESS> then please reopen or submit a new issue.


eth_chainId API

Description
A new endpoint eth_chainId needs to be created, which returns the chain id as uint.
https://github.com/ethereum/execution-apis/blob/188589473adb07a48f11fcb0d687d159e790b8a4/src/eth/client.json#L15
needed for Kiln v2.1

In the v2.1 spec it seems like it is a new endpoint, but in reality it isn't. There was an EIP a long time ago, which specified the endpoint: https://eips.ethereum.org/EIPS/eip-695
We have this already implemented.
In the current implementation we return a hex value, which is correct because uint is indeed a hex value per spec: https://github.com/ethereum/execution-apis/blob/188589473adb07a48f11fcb0d687d159e790b8a4/src/schemas/base-types.json#L42


Add support for GCP cloud provider

Issues AN-307, AN-309
I was able to include AN-309 as it wasn't that hard to do and testing was much easier that way.
Main changes:

Added full support for GCP cloud (except HTTP gateway) - you can now deploy Airnode to GCP via deployer (just CLI, there may be some changes needed to support credential passing for containers)
Extracted common handler to be available in the root of cloud function (needed by GCP)
Added possible import step to the Terraform flow (needed because of the GCP's AppEngine)
Increase AWS lambdas memory size - both AWS and GCP functions were failing for me on 128 MB memory limit so I set both to 256 MB. This will probably change soon anyway based on the stress test results.

I'm still going through the terraform files, but the typescript part looks good. Quick question, are the deployed functions public or private? I remember when I deployed the functions by default they would be private and had to manually change it to public(although I don't think it matters)

I'm still going through the terraform files, but the typescript part looks good. Quick question, are the deployed functions public or private? I remember when I deployed the functions by default they would be private and had to manually change it to public(although I don't think it matters)

They are private but we don't need them to be public. They are not invoked by anything external. The startCoordinator is run periodically by the scheduler and the rest is invoked from within.


Inconsistency in typedb interface: get_type, get_types

The functions
typedb:get_type
typedb:get_types
are inconsistent with the rest of the interface, where the other typedb:get_* functions always find something in the current or an enclosing scope. get_type and get_types return a type of a type list in the current scope only.
They should be called this_type and this_types instead. get_type and get_types on the other hand should return a type of a list of types in the current or an enclosing scope to make the interface consistent.

Renamed the functions
get_type -> this_type
get_types -> this_types
and deprecated
get_type and get_types
Currently, the use of get_type and get_types is redirected to this_type and this_types with a warning issued on stderr.
Later, the use of get_type or get_types will raise an error.