[ENG-1328] Cleans up welcome page

Describe your changes and why you are making these changes
As discussed on Linear, this PR makes a number of small fixes to the welcome page:

Makes all the blocks even width.
Removes the light grey background adds dark blue borders to each block, combined with a light blue hover background.
Adds Aqueduct logo to the top of the page.
Cleans up getting started instructions to match the latest information.
Animates wave emoji on page load and when hovering over the welcome block.

https://user-images.githubusercontent.com/867892/184013864-69cd5881-51b0-4361-ba63-4f191d42b150.mov
Related issue number (if any)
ENG-1328
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[N/A] If this is a new feature, I have added unit tests and integration tests.
[N/A] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

This is very helpful @vsreekanti ! I think the only thing I'm unsure about is if we want to put integration connection as the first step, esp. that majority of step 2 and 3 are actually both using the demo. I'm considering the following change:
1. (current step 2) Create your first workflow using our demo database - see our quick start guide for an example.
2. (current step 3)
3. Try out with your own data by <link> connecting to an integration. </link>

My motivation is this is easier to follow for first-time user. And for non-first-time users it's obvious for them to ignore step 1 and 2 since they know they've already done it.

This is very helpful @vsreekanti ! I think the only thing I'm unsure about is if we want to put integration connection as the first step, esp. that majority of step 2 and 3 are actually both using the demo. I'm considering the following change:
1. (current step 2) Create your first workflow using our demo database - see our quick start guide for an example.
2.  Try out with your own data by <link> connecting to an integration. </link>

My motivation is this is easier to follow for first-time user. We could minimize the risk that one user decide to connect to an integration, and the following steps becomes less helpful. And for non-first-time users it's obvious for them to ignore step 1 and 2 since they know they've already done it.
I'm curious about how other folks @agiron123 feel as well

@likawind these are great ideas, but are a bit out of scope for the task at hand. I've documented these and created a new design task here for us to follow up:
https://linear.app/aqueducthq/issue/ENG-1562/improve-design-of-first-time-user-experience
I definitely agree that there is a lot that we can do to make our getting started page easier to follow. However, I think this warrants a bigger design discussion on how we wish to surface our features to users.

Thanks for creating the new task, @agiron123! That makes sense to me. Anything you'd like me to change before we merge this?


net: dial tests are flaky on BSD

These have been flaking a lot on OpenBSD ...
https://storage.googleapis.com/go-build-log/f99ca413/openbsd-amd64-gce58_83506189.log
--- FAIL: TestDialTimeoutFDLeak (1.89s)
    dial_test.go:164: got 96; want >= 100
--- FAIL: TestDialerDualStackFDLeak (0.80s)
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
    dial_test.go:213: dial tcp <IP_ADDRESS>:24574: i/o timeout
--- FAIL: TestReadUnixgramWithUnnamedSocket (0.19s)
    unixsock_test.go:60: read unixgram /tmp/go-nettest180765192: i/o timeout
--- FAIL: TestDialTimeoutMaxDuration (0.40s)
    timeout_test.go:140: #0: Dial didn't return in an expected time
FAIL
FAIL    net 12.082s

/cc @mikioh

Also on FreeBSD:
https://build.golang.org/log/73446e673c8f780dbfbc11aaab2b4f8e4daefb68
ok  	mime/quotedprintable	0.156s
--- FAIL: TestDialerDualStackFDLeak (0.58s)
	dial_test.go:172: dial tcp: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
	dial_test.go:172: dial tcp <IP_ADDRESS>:59846: i/o timeout
FAIL
FAIL	net	2.256s
2016/05/11 17:45:36 Failed: exit status 1

@mikioh, @mdempsky, can one of you investigate?

Yeah, I'll look into the OpenBSD failures today.

Just saw what looked like a flake on a linux/amd64 race trybot run:
https://storage.googleapis.com/go-build-log/01e274f4/linux-amd64-race_4322dd7e.log

Another possible flake on a linux/amd64 race trybot run:
https://storage.googleapis.com/go-build-log/f6b2f823/linux-amd64-race_be3b785d.log

I a little time looking into the TestDialerDualStackFDLeak flake on OpenBSD last night.
I was able to repro the issue under ktrace, and Go doesn't appear to be doing anything obviously wrong. We make a non-blocking connect call, it returns EINPROGRESS, we register it with kqueue, and then the kernel reports back 6 seconds later that the connect failed.
The failure is always around 6 seconds, so I suspect it's something TCP timeout related.
I was next trying to repro the issue while tcpdump'ing lo0 (hoping it hints what part of the stack might be failing), but no success yet.

@mdempsky, thanks for investigating.
If we can't make progress on this, though, the openbsd builders are doing more harm than good with flaky tests.
I think it might be time to slap on a bunch of testenv.SkipFlaky(t, 15157) to all these tests on OpenBSD.

@bradfitz For net flakes on OpenBSD, I'm inclined to agree.

Doesn't seem to be limited to BSD: https://storage.googleapis.com/go-build-log/fa1eb023/linux-amd64-race_e3f8fc0c.log
--- FAIL: TestDialTimeoutFDLeak (0.59s)
	dial_test.go:136: got 99; want >= 100

On darwin-386-10_14 (https://build.golang.org/log/6e8422bf8109adb9f942363402c03bd942fe0):
--- FAIL: TestDialTimeoutMaxDuration (0.36s)
    timeout_test.go:133: #0: Dial didn't return in an expected time
FAIL
FAIL	net	11.653s

Filed the darwin failures separately as #43069.

I don't see any recent failures for TestDialTimeoutFDLeak or TestReadUnixgramWithUnnamedSocket.

The i/o timeout failure mode of TestDialerDualStackFDLeak now only occurs on Solaris (#43070).

The remaining TestDialerDualStackFDLeak failures on BSD have a different failure mode from the one reported here, filed as #43071.
I'm going to close out this meta-issue, since there are now separate issues for the individual observed failure modes.


added securitygrouprule for accessing Elasticache/Redis

Description of your changes

Added securitygrouprule for accessing Elasticache/Redis, so that this configuration can be used by a forthcoming configuration-aws-elasticache reference.
Fixes #
I have:

[x] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

make e2e

/test-examples

/test-examples

/test-examples

/test-examples

rebase does not look correct, I expect only your commit to be a part of this PR

looks stale - @humoflife if you want this change please open a new PR


Add rust-toolchain file

cc https://github.com/rust-lang/rust/issues/65424.

Will remove the rust-toolchain file once the bug gets fixed.

Closing in favor of #3870.


Building pulsing is buggy on concourse 2.5.1

This screenshot actually makes it look tame in comparison to the frequency this thing is pulsing on my screen. It seems like it only manifests itself at certain zoom levels.
http://whatsmybrowser.org/b/M1ED8RH

This is some sort of Chrome regression; we haven't touched that part of the UI in ages. Plotting to come up with a new indicator anyway.

I'd also like to add that when we have lots of parallel jobs there's quite a bit of overlap, here's a screenshot (oddly, not showing the corruption although it is occurring in the browser) -- thought I'd mention this here as it's related to the indicator:

Has anyone managed to trace down what changed between the chrome versions to introduce this top try fix it? The pulsing looks like it's having a serious epileptic moment!

@vito - you think it would be enough if we just swapped the radiating animation for actually making the whole job box pulse? if it grew by a significant amount it would probably be noticeable.

Moved to concourse/concourse#1127


Update package.json to include the repository

NOTE: This is not a bot. This change was made by and comments will be reviewed by humans. We are using this service account to be able to track the overall progress.
With the rise in supply chain attacks and OSS dependencies being used as a attack vector, Microsoft is working with our ecosystem partners, such as the Linux Foundation's OpenSSF, to enable OSS consumers to track packages back to their public sources.
We've identified that the following packages published to NPM do not report where sources can be found, typically accomplished by including a link to your GitHub repository in your package.json REPOSITORY field. This PR was created to add this value, ensuring future releases will include this provenance information.
If you do not want us to create such PRs against your GitHub repositories, or wish to provide any other feedback, please comment on this PR.
Published NPM packages with repository information:
• canvaskit-local
• canvaskit-wasm
• pathkit-local
• pathkit-asmjs
• pathkit-wasm

@googlebot I signed it!

Individual CLA has been signed. Please let me know if there is anything additional needed from me to land this Pull Request.

Is this the repo? I thought it was https://skia.googlesource.com/skia.git ?


Unsupported module required

This requires a preview version of a powershell module that is soon to be deprecated be used. This functionality should be ported over to the newest powershell Azure module and the guidance updated accordingly.

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

ID: 7b913b35-30e0-0781-c527-059675f76cdd
Version Independent ID: ef1537fc-3410-52da-07c5-5e56e71a803c
Content: Configure group owner consent to apps accessing group data - Microsoft Entra
Content Source: articles/active-directory/manage-apps/configure-user-consent-groups.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @eringreenlee
Microsoft Alias: ergreenl

@werdnotrom11
Thanks for your feedback! We will investigate and update as appropriate.

@werdnotrom11, thank you for your feedback. Currently, we're working on achieving 100% parity for Microsoft Graph PowerShell to Azure AD graph PowerShell and MSOnline. Once we complete this, we'll embark on achieving the same with the preview content and convert the cmdlets to Microsoft Graph PowerShell.
I've created a work item to track this internally and will update this issue once we've effected the changes. I'll go ahead and close the issue for now. Feel free to reach out in case you have any concerns.
#please-close


Would be nice to have Exact Path Matcher Predicate

I want to serve angular frontend under one of the servers classpath i.e. localhost:666/gui, it goes to a static content serving server.
Now using
localhost:666/gui  it does not work as the javascripts/css have a relative path, and so on a url localhost:666/gui the browser thinks that i.e. styles.css is in localhost:666/styles.css
When in localhost:666/gui/  (only a slash difference) it works like it should as browser sees it is a path segment and loogs for styles.css in /gui.css
The HARDCODE solution would be to hardcode absolute paths /gui/** for anything n the Angular GUI, but then changing the path to something else would require a rebuild.
The gateway soultion would be to add a routing that sees that the path is localhost:666/gui and redirects it to localhost:666/gui/
As simple as it sounds:
      - id: guiSlash
        uri: "lb:http://guiserver"
        predicates:
        - Path=/gui
        filters:
        - RedirectTo=302, http://localhost:666/gui/

      - id: gui
        uri: "lb:http://guiserver"
        predicates:
        - Path=/gui/**
        filters:
        - StripPrefix=1

But what actually happens is that - Path=/gui matches /gui/ too and is in a neverending redirect loop.
I was able to create my own:
@Component
public class ExactPathRoutePredicateFactory extends PathRoutePredicateFactory{
	public ExactPathRoutePredicateFactory() {
		super();
		PathPatternParser pathPatternParser = new PathPatternParser();
		pathPatternParser.setMatchOptionalTrailingSeparator(false);
		super.setPathPatternParser(pathPatternParser);
	};

	@Override
	public Predicate<ServerWebExchange> apply(Config config) {
		return super.apply(config);
	}
}

So this works now:
       - id: guiSlash
        uri: "lb:http://guiserver"
        predicates:
        - ExactPath=/gui
        filters:
        - RedirectTo=302, http://localhost:666/gui/

      - id: gui
        uri: "lb:http://guiserver"
        predicates:
        - Path=/gui/**
        filters:
        - StripPrefix=1

But I think the trailing separator option should be available out of the box for such cases?

IMO I think that the UI app needs to have some knowledge that it is being served through the gateway.
I think it would be simpler to change the resources so they are served via a path other than /gui, that way you would avoid the confusion.

Why would the app need to know the knowlege how it is being served? That is why You can use relative paths to any resource and not hardcoded URLs. The only problem is with brower resolving relative paths (it has nothing to do with UI app, its the browser that resolves stuff)
Say we have a resource with relative path "scripts/script.js"
When the app is opened at path localhost:8080/guiserver --> the browser resolves it as "localhost:8080/scripts/script.js"
When the app is opened at path localhost:8080/guiserver/ --> the browser resolves it as "localhost:8080/guiserver/scripts/script.js"
and it has nothing to do with the UI

@ryanjbaxter because this problem is with every browser, and to fix this You need to create a redirection to a one with a backslash. This should be really simple for any gateway soft, but there is no way to do it in gateway.
The problem is that the gateway does not allow to select an exact path, so even when I do a path /guiserver to redirect to  /guiserver/ it matches up all resources in /guiserver/* with /guiserver
Basically there should be an option for EXACT path matching to allow full control on URLs etc. The option MatchOptionalTrailingSeparator in path pattern parser was added there for a reason....

I understand this a little better now that I experimented on my own.  A couple of additional things I found

The problem only comes into play if serving content from a URL through the gateway with a path.  If for example the resources are served from http://gateway, adding a slash makes no difference (at least in Chrome).  If however you serve the resources from http://gateway/frontend than the behavior will change based on whether there is a trailing / or not.

I found a pretty clean solution by placing all my Javascript in a js folder and then creating a route for that in that gateway.

Fixed via ca65417


[bug]: RPC ERROR: WiFi Internal Error end0: error fetching interface information: Device not found

Prerequisites

[X] I have searched for existing issues that already report this problem.

Server Hardware
Pi(2GB) w/ 32GB Microsd & Samsung Evo SSD
StartOS Version
<IP_ADDRESS>
Client OS
MacOS
Client OS Version
13.5.2
Browser
Chrome
Browser Version
117.0.5938.132
Current Behavior
The error am getting occurs when I try to switch from ethernet to WIFI, it pops the following: RPC ERROR: WiFi Internal Error end0: error fetching interface information: Device not found and doesn't display any available WIFI .

Expected Behavior
Should show a list of available WIFI connections and allow a user to select the preferred network they want to join.
Steps to Reproduce

Use the access from Home Address, paste the url in chrome
Start Os login page appears (enter your password)
Go to system > WIFI
It tries to scan the the Error pops

Anything else?
No response

Noted, thanks @kn0wmad .


could jbang-vscode offer to install jbang if it is not available?

its all nice downloading jbang + jbang edit  gives you full dev environment but
it would be nice if jbang-vscode could offer to install jbang to make it easy to start from downloading vscode instead of installing script via terminal.
wdyt?

Yeah I thought about it, also to embed jbang by default.
Where should we install it by default? ~/.jbang?

yeah - I was thinking to just do what curl -Ls https://sh.jbang.dev | bash -s - app setup does.
for windows its a bit more tricky as it might require elevated privileges due to reliance on symbolic linking ;/

/cc @quintesse

I would be -1 on embedding jbang by default; unless its just used as absolute last fallback or we can release vscode-jbang immediately when jbang updates.

yeah - I was thinking to just do what curl -Ls https://sh.jbang.dev | bash -s - app setup does.
for windows its a bit more tricky as it might require elevated privileges due to reliance on symbolic linking ;/

So do you want that we run curl / iex from vscode to trigger the install in a terminal, or do you have something else in mind?

... like detect if sdkman, homebrew, choco is installed and delegate the JBang installation to those


[MLDB-1451] serving index.html in directories if it exists

changed the nginx config to serve all documents under doc/ and resources/
changed the behaviour of the static file handler to look for an index.html if the uri points to a folder
fixed a couple path building to make them more robust when ill-formed user input is provided

@nicolaskruchten I believed I covered all the cases and my tests in the docker reveal no problem.  However, when using the mldb_doc_server it seems that using /doc will brake the frame display in index.html because the browser history is not replaced correctly in the javascript.  I can add better check there but I'd liked to get your input first as whether this a problem.

After further thinking I realized that my test with the container were mostly likely incorrect since some of the pages were likely serve with nginx and not mldb.  The problem affecting the mldb_doc_server will  likely be problematic.

Capturing HipChat feedback: /doc should return a 3xx to /doc/ and the problem will go away I think.

@jraby Can you please review the changes to nginx?

nginx part looks ok to me, modulo the /resource rewrite rule which is possibly not needed.

@nicolaskruchten I've reworked the code.  Redirect is done by mdlb except for uri .../doc and .../resources which is done by nginx (doing it in mldb required more changes than expected).  The mldb_doc_server works fine now including the interactive REST doc (not that it really matter!).

In the docker, yes, but what about the raw mldb_runner or mldb_doc_server ?

It returns a 404 because that route is not registered in mldb.

Ok, that's good. Any objections to getting rid of the doc_server
executable, given that mldb_runner does the same thing?
On Tuesday, 29 March 2016, Guy Dumais<EMAIL_ADDRESS>wrote:

It returns a 404 because that route is not registered in mldb.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/mldbai/mldb/pull/283#issuecomment-203086496

--
Nicolas Kruchten, Eng  |  Staff Software Engineer at Datacratic  |
http://datacratic.com/

I've certainly have no objections to remove the mldb_doc_server.

OK, let's remove the doc_server as part of this PR then please, and +1 from me :)

@jraby once this is merged, you should be clear to work on MLDB-1446

I removed the mldb_doc_server as agreed.


Add support for SQL strings to language_php

Naively detects strings starting with CREATE, SELECT, INSERT, UPDATE, REPLACE, DELETE, DROP, or ALTER (case insensitive), and marks them as a subsyntax for .sql files.
Note that this doesn't create a hard dependency on language_psql or any other specific SQL highlighting plugin; if no such plugin is present, SQL strings will simply appear un-highlighted instead of as strings.

What do you think about using an approach like this:
local sql_words = {
  "create",
  "select",
  "insert",
  ...
}

local sql_combined = "("
for k,v in pairs(sql_words) do
  local multi_case = "(?:"
  for i=1,#v do
    local char = string.sub(v, i, i)
    multi_case = multi_case.."["..string.lower(char)..string.upper(char).."]"
  end
  sql_words[k] = multi_case..")"
end
sql_words = "(?:"..table.concat(sql_words, "|")..")"

...
    {
        regex = { '"(?='..sql_words..')', '"', '\\' },
        syntax  = '.sql',
        type    = "keyword"
    },
    {
        regex = { "'(?="..sql_words..")", "'", "\\" },
        syntax  = '.sql',
        type    = "keyword"
    },
...

This way you automatically generate all the "multi-cased" keywords and only need two regexes.

To be honest I'd forgotten since reading the docs that regex was an option or I absolutely would have. I did try a generative approach, but Lua patterns don't support alternation, and I wasn't having much luck with table.unpack to pregenerate all the entries. I'll make a few tweaks to implement that.

Just to confirm, you're dropping the mixed case support, right?

Technically yes, it was initially a quirk of how pattern syntax required it to be written. I can add it back if that's preferred though.

Is the first letter often capitalized? If not we can leave it as it is. If someone really wants to support mixed case, they can just open a PR.
I'd say just do what you think is best.

Official style guide is all caps. I see a lot of all lowercase, but rarely if ever mixed.


Projects Section Added

Projects Section Added with Hover effects.

Currently we don't need this, thank you @taniya542

Then why was it even assigned to me?


feat: added command to update the issue label

What does this PR do?
It updates the issue label when a member of the repository comments /oss.gg 500

Fixes #40

How should this be tested?

Test A
Test B

Checklist

Required

[ ] Filled out the "How to test" section in this PR
[x ] Read How we Code at oss.gg
[x ] Self-reviewed my own code
[x ] Commented on my code in hard-to-understand bits
[x] Ran pnpm build
[x ] Checked for warnings, there are none
[ x] Removed all console.logs
[ x] Merged the latest changes from main onto my branch with git pull origin main
[ ] My changes don't cause any responsiveness issues

Appreciated

[ ] If a UI change was made: Added a screen recording or screenshots to this PR
[ ] Updated the Formbricks Docs if changes were necessary

hey!
i've got the same comment several times:

any idea why? 🤓


Keyborad

how can move up bottom sheet when keyboard is visible?

Hello @mohodroid,

Hello @mohodroid,
This depends on your activity windowSoftInputMode .
To check what mode feats your issue, please take a look at this documentation page.


Linting without IntelliJ

I've been uncomfortable tying our linting to IntelliJ. It prescribes an editor when I'd prefer developers are able to choose whatever editor they are comfortable working in.
At the Lead Developer conference, someone recommended Prettier. The suggested approach was to have Prettier auto-commit code fixes to a PR.

I have been thinking this over after some discussions with @zarsky-broad. Breaking things down a bit, here are the decisions at play, from what I see:
What mechanism we use to perform and enforce the checks.
Given the requirement of editor independence (which I support), I think the most reasonable choice available is ESLint.
What checks we enforce.
This further breaks down into:
Semantic checks
ESLint has a strong set of rules that we can enable to catch likely errors and problematic patterns. This seems like a straightforward choice.
Stylistic checks
ESLint has a comprehensive and flexible set of rules we could enable, OR we could use Prettier (which also integrates well with ESLint). Both options seem suitable, so we could take a look at the possible outputs and decide what we want.


Strange scroll bar apppears on ion-tabs

Strange scroll bar appears on ion-tabs, you can see this on the photo below:

It happens only from time to time when I navigate in app using default navigation.

Greetings @Klapsa2503!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

Application complexity seems to be the problem.


Usage without TypeScript

Hello!
I gave a try with vitesse template and a standalone vite project, everything seams to work quite well.. except when I'm not using typescript (eg. no "lang='ts'" and/or no tsconfig.json).
Maybe this library is designed to work especially with TS? But the samples in the readme do not include any TS (except vite config example) ; while playground and nuxt example do.
I'm using vite, vue 3 and

I don't see a problem of using without TS as TS is only provided as some hint and the functionality is provided in js indeed.
If you have any issue on that, please provide a minimal reproduction. Thanks.

Hey @antfu,
Made a minimal repro : https://github.com/ttxtosca/unplugin-auto-import-issue-12
From vite/vue start template. auto-imports.d.ts is fully populated but from components/HelloWorld.vue, got the error ReferenceError: ref is not defined while import line is commented (or not present).
Thank you for your time. I think this is an issue ; except if I missed something.

Works like a charm. Thank you for this and your work!


🖼 figure with nozoom

New attribute for figure shortcode:
nozoom disables the zoom functionality of the image displayed in the figure tag.
closes #934

Awesome @fuse314 thanks for this


Wrong badge icon

Component
web-ui
Describe the bug
We have a good state build, but the WEB UI shows a bad build result badge:

We have newer seen this problem before!
Steps to reproduce
...don't know...
Expected behavior
No response
System Info
{
"source": "https://github.com/woodpecker-ci/woodpecker",
"version": "2.7.3"
}

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Checked that the bug isn't fixed in the next version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]

Is the status wrong in your example, or the badge in the upper right?

Is the status wrong in your example, or the badge in the upper right?

Title + description updated.

The badge is intentionally limited to the push event.

According to the screenshot, the last successful build is a commit to master and should be reflected in the badge status.

Ah, because of the clock symbol I see 👍

The badge is intentionally limited to the push event.

Hmm... why?
No matter the trigger of the pipeline, the badge should express the state of the pipeline (like the first word in the badge).
We have an dashboard where we intentionally monitor the state of our pipelines.

Maybe it would be better to allow the choice to the user and add an option in the badge settings for each repo. This way if someone would like to have that updated even on PRs, that would be possible.


[ALLUXIO-2221] Avoid crashing worker UI in case of missing files

https://alluxio.atlassian.net/browse/ALLUXIO-2221

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11304/
Test PASSed.

LGTM

LGTM

LGTM


Add breaking change note for Unhex() nullability change

See https://github.com/dotnet/efcore/issues/33864
/cc @ranma42

Thank you for taking care of that :)


Add support for AZ aware redis followers

Added support for creating followers
Added affinity rules to prioritize sheduling of followers and their leader on different AZs

Closing because of the new branch with code updated.
https://github.com/PayU/Redis-Operator/pull/10


How can Patches be obtained?

According the description, CFPU produces an implicit surface from a point cloud consisting of points and normals.
However,your matlab code of 'cfpurecon' requires patches.
Would you let me know how the patches can be obtained?

The last example in cfpu_ex.m shows how to do this.


Drag n' drop is not enabled in smartphone for legend control

This still has an issue. For now, I disabled drag n' drop feature in mobile by PR #137


fix: Remove LogLevel import from Node.JS Getting Started guide

LogLevel doesn't seem to be exported from @opentelemetry/node (anymore?) and causes the example to crash
/Users/nvenegas/Code/otel-nodejs/tracing.js:8
  logLevel: LogLevel.ERROR
            ^

ReferenceError: LogLevel is not defined
    at Object.<anonymous> (/Users/nvenegas/Code/otel-nodejs/tracing.js:8:13)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1217:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:449:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:76:3)
    at internal/main/run_main_module.js:7:1

What's the relationship of this file vs https://github.com/open-telemetry/opentelemetry-js/blob/main/website_docs/getting_started/nodejs.md?
That file also has a reference to LogLevel

What's the relationship of this file vs https://github.com/open-telemetry/opentelemetry-js/blob/main/website_docs/getting_started/nodejs.md?
That file also has a reference to LogLevel

The authoritative copies of the docs are stored in the SIG repos; Please make this PR against these docs, and then the JS SIG can merge them over. Thanks!


List inside FocusZone is getting OOM errors in wasm.  Fine in server-side

It was a bug in List where the page was redrawing in a never-ending loop.
https://github.com/limefrogyank/BlazorFabric/commit/d9565f7f34b8f74023d8006ef36c442765e9d5a2


Allow to return value from callback function

Describe the feature
Introduction
First of all, this is kind a comment for PR #81, and issue (feature request) + discussion topic.
Problem
So, what we have is the two types that resolves function signature for given hook:

HookCallback type that is used as type hint and being the part of the next one...
https://github.com/unjs/hookable/blob/main/src/types.ts#L1

InferCallback type that ensures hook callback to be appropriate to HookCallback otherwise sets its type to never.
https://github.com/unjs/hookable/blob/main/src/hookable.ts#L14-L16

And in PR #81 we have some kind of extension over type determination for caller side:
https://github.com/unjs/hookable/pull/81/commits...
As for me, this patch cannot be applied without changes in HookCallback type. I consider to replace void by any
to make callbacks with returned value appropriated for InferCallback type.
In case if you (authors, maintainers) think that this feature will be suitable for the future vision of hookable package internal structure, I could try to implement it (but for know I will left the check under unchecked).
As for current implementation is allowed to pass values from handlers but values have type any, and exactly that is what DMReal32 aims to fix, but since hook must extend HookCallback type, user must pass (...) => void or an type error will be occurred on hook set.
Example
// nuxt module (types.d.ts or related to it), we want to extend hooks

declare module 'nitropack' {
  interface NitroRuntimeHooks {
    'calculate:void': () => void
    'calculate:number': () => number
  }
}

// playground, hook setting
import type { NitroApp } from 'nitropack'

export default (nitroApp: NitroApp) => {
  nitroApp.hooks.hook('calculate:void', () => {
    return 0
  })

//  InferCallback consider this hook function as never type
  nitroApp.hooks.hook('calculate:number', () => {
//                                        ~~~~~~~
    return 0
  })
}

Image for more clarify representation

Solution(s)
First solution is not the solution for me, since I want to have this feature (already works, but lack of type hints):
Replace Promise<any> by Promise<void> and deny PR #81
Second solution is to deny PR #81 (temporary), and ask for implementation of mentioned notice
Third solution is to approve PR #81 and ask \ assign me \ somebody else for this issue implementation (I thinks this is less desired since only one line requires for changes).
Thanks for attention
Additional information

[ ] Would you be willing to help implement this feature?

+1 It's really a important feature


Update Unity.gitignore (Added rule for Rider cache directory)

Added rule for Rider
Reasons for making this change:
Rider generates a .idea/ directory which contains cached files that probably should not be committed
Links to documentation supporting these rule changes:
I don't have any specific documentation, but for the same reason, the .vs/ folder is excluded rider's .idea/ folder should be as well.

See: https://github.com/github/gitignore/pull/3529#issuecomment-810453567


purge-docker-cluster: ensure old logs are removed

purge-docker-cluster must remove all osd_disk_prepare logs in
{{ ceph_osd_docker_run_script_path }}, otherwise if you purge your
cluster and try to redeploy it, osds will fail to start since because it
will try to retrieve find a partition uuid which doesn't exist.
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1510470
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container

jenkins test luminous-ansible2.4-purge_filestore_osds_container

jenkins test luminous-ansible2.4-purge_bluestore_osds_container


Label icons for accessibility

The buttons to add or remove items have no accessible text for screen reader users.
aria-label added to add and remove buttons for the afArrayField for accessibility

Hi @emollett
thank you for your contribution. Improving accessibility is always a good idea. However, we may have to consider that this component is used by non-English speakers, too. Thus, it needs to be configurable to let the developer define what word to display.
Please take a look at how the submit button label is defined in a quickForm. By default it is defined as Submit but you can easily override it using `button-content="Whatever submit text". I think this is the right way to go.

@jankapunkt thanks that makes sense. Thanks for the pointer on overriding the button content, my understanding had been this is just for the submit button and not the add/remove ones. I understand I can make my own template for these though. For now as a quick fix I'm adding content to the buttons with css which works for the accessibility needs in this instance.

Hey @emollett no need to close the pr. You just add your changes as new commits to your fork and we squash-merge it all at the end into one commit.
I think you don't need a full template, just a helper and a reactive variable, as the submit button does.


What's the big difference between local test and cluster test?

Hi all,
Recently I have did a research about operator,and I have a question about e2e test:"what's the big difference between local test and cluster test?"
AFAIK, local test creates operator service by deployment and cluster test creates operator service derectly by specifying the operator images. What is the significance of these two ways?

/close


[v4.0.0-beta.15] Documentation UI not helpful

Hi,
I am working on the Ionic 4 app. Looks like the documentation with the UI is broken in https://beta.ionicframework.com/docs/api/searchbar

Yes, it is broken, it seems something missing from distributed file:

Thanks for the issue! We'll have a fix in for this soon, but in the meantime please track it on this issue: https://github.com/ionic-team/ionic-docs/issues/168


Include WNDT 88 video

Target Live Date: 2020-01-15

[x] This has been reviewed and approved by (@chybie )
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 40 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/11/devtools.md#L7 - Unknown tag 'chrome7' found, use an existing tag, or add it to 'src/data/commonTags.json'.
src/content/en/updates/2020/11/devtools.md#L342 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/11/devtools.md#L172 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L176 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L178 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L5 - WF Tag 'wf_updated_on' must be within the last 7 days.
src/content/en/updates/2020/11/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L47 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L60 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L70 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L83 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L97 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L101 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L112 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L114 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L116 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L134 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L150 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L166 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L176 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L178 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L195 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L211 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L225 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L227 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L239 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L248 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L272 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L278 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L299 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L307 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L322 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L326 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L330 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L334 - Line must be at most 100 characters

Whoops!
There were 40 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/11/devtools.md#L7 - Unknown tag 'chrome7' found, use an existing tag, or add it to 'src/data/commonTags.json'.
src/content/en/updates/2020/11/devtools.md#L342 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/11/devtools.md#L172 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L176 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L178 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/11/devtools.md#L5 - WF Tag 'wf_updated_on' must be within the last 7 days.
src/content/en/updates/2020/11/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L47 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L60 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L70 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L83 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L97 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L101 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L112 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L114 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L116 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L134 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L150 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L166 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L176 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L178 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L195 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L211 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L225 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L227 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L239 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L248 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L272 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L278 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L299 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L307 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L322 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L326 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L330 - Line must be at most 100 characters
src/content/en/updates/2020/11/devtools.md#L334 - Line must be at most 100 characters


Support for multiple windows

-New windows can be added by "CMD+N"
-Each window pops from the delegate, including the one that appears on
startup (note that this is a change from the initial storyboard setup)
-Replaced ALL NSNotification center calls made to directly modify each
window - This prevents signals from getting mixed up between two
different windows
-State for Transparency and Opacity menu items are inferred for each
window from the validateMenuItem method - No longer called manually
from each IBAction
-UNTESTED: Starting the app from URL - This method should work given
the changes I made, but I was unable to test it

Is using an array of window controllers really the right way to do this sort of thing? I know document-based OS X applications don't require this to be (at least explicitly) stored. That said, I'm not sure how this is normally done, so this maybe be 100% standard.

Hmm... Honestly I don't know if this is the standard, but I do know that the view controller must remain stored in memory somehow so the user can interact with the view. An array just seemed to be the simplest way. Do you have any other ideas?

:+1: Anything I can do to lend a hand on this? I can clone and build and test this branch?

@scottwarren that would be great! My issue was that I did not understand what sort of URL would start the app, what would happen if you opened a URL linking to the app while the app was already opened, etc. If you could test both of these cases, that would be great. I believe starting the app with a URL will work, but opening a URL linking to the app while the app is open will probably not work. Uncertain whether this will crash or just not open anything, but there definitely needs to be some sort of method for tracking the front-most window for this type of thing to work properly.

Sure - I will have a look at this tonight and tomorrow night

@dannyflax: What's the role of the lazy "nextWindowController" property? From what I can tell, it is never used.

@ryh @dannyflax I'd prefer if we used firstElement instead of subscript notation. firstElement will return an optional and thus is inherently more safe.

Shoot, I left "nextWindowController" in there from a previous implementation. That shouldn't be there. And yeah I agree, firstElement definitely seems like the way to go. I'm a pretty new to swift, so I didn't even know that was an option.

@JadenGeller In follow-up to the original inquiry about an array of windows, I found NSDocumentController which appears to manage simultaneous window controllers. I don't really think this would suit our needs and probably would bring in a lot of unnecessary overhead.

@dannyflax The current implementation doesn't display the open windows in the "Window" menu like a normal OS X application. Perhaps NSDocumentController enables this behavior?

@JadenGeller That's interesting, I didn't notice that. It appears the previous implementation doesn't show the window in that menu either. Just so we're clear, you're referring to this menu, correct?

@dannyflax I'm referring to the menu bar. I removed that menu earlier because the app only supported one window and does not support minimization. It probably has to be re-added.
I'm not sure what you're pointing out in the side note or the screenshot.

@JadenGeller That screenshot is a picture of the Mission Control menu that you can reach by swiping down with three fingers. It's supposed to show all of the windows for the currently opened app. Sorry for any confusion, but I'm still not really sure which menu bar you're referring to. Could you post a screenshot?

@dannyflax Helium is implemented with NSPanel which, by default, does not show up in mission control. There may or may not be able to change that.

I'm referring to the "Window" menu bar menu: https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/MenuBarMenus.html

Got it. Now I see what you're talking about. Yeah, it's definitely odd that the windows don't show up in that menu by default using the current implementation. I'll look into NSDocumentController and see if that changes anything.

Actually, the docs say here that panes shouldn't be shown in this menu. Hmm...

@dannyflax I'm going to choose to disregard that instruction because we are using panels as windows. Normally, a panel is an auxiliary view for a window (look at Pixelmator's use of panels as an example). Since we are treating it as the only windows of this application, we will use the.
I think this is what we want to add them to the menu.
http://stackoverflow.com/questions/5926431/is-there-a-way-to-force-appkit-to-include-my-borderless-nswindow-subclass-in-the

Another idea. We can override this default panel behavior by subclassing NSPanel:
https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/WinPanel/Tasks/UsingWindowsMenu.html
This way the title in the menu will automatically update when the title of the panel changes.

@dannyflax 👍 even better

@dannyflax As I understand it there is some work to do, I will wait until that is complete before I test. Let me know if that's all good :+1:

Hi all! I apologize for the delay. So I've spent a decent amount of time working on a solution, and the best I've been able to come up with is in the latest commit. Unfortunately, subclassing NSPanel was not doing what I wished, and due to a combination of inconsistencies in the documentation as well as a vast number of recommendations not to subclass, I decided to go with NSApp.changeWindowsItem. This method seemed to do the trick nicely. @JadenGeller, please take a look at this build and let me know your thoughts.


Handle paths that cannot be resolved

Sometimes dependency-tree cannot resolve all the required paths (due to bugs or configuration problems). Madge should not let these errors go unnoticed since it can result in an incorrect dependency graph. See dependents/node-dependency-tree#53 for a discussion of this.

This is fixed in v1.4.0 now @pcardune @mrjoelkemp :)


Hide JS CSS in the network tab of devtool

replace vite with esbuild?

just separate content script and other page(popup,options...),and then bundle twice


Site is not updated when when you add or update you sanity data

Hey, Samuel. To see the updates, you'll need to setup Sanity deploy hooks or revalidation in nextjs. The former is less cost intensive and easier to setup so I suggest it. You can visit this guide on how to setup the hooks.
If you prefer the revalidation route, you can check out the nextjs documentation. You might be tempted to add this into every page that uses the fetch function:
export const revalidate = 10 // revalidate every 10 seconds

Although this will work, this is not a good solution as it places a huge load on the server due to data revalidation happening every 10 seconds, especially since Sanity has a monthly threshold that can be maxed out.
Currently, I'm using deploy hooks for this portfolio, but I'll work on the on-demand revalidation solution as it's the best option so anytime soonest, I should push a fix for this. In the meantime, feel free to choose what works well for you.


jagged printing in emacs

Functions that involve multiple calls to print, println, (.Write ^TextWriter w "bla"), etc – basically anything that writes to *out* in multiple steps – are prone to print to the emacs repl in a garbled form, with newlines inserted and removed seemingly at random. This makes data almost unreadable.

Does the same thing happen if you use the standard read function? It seems similar to the issue where the repl gets stuck, which doesn't happen when you use the standard read function (as described in #292).


Wrong Identification Of ACL Paths

Description:
In the domain i am analyzing (BHE) the EXCHANGE RECIPIENT ADMINISTRATORS are shown with a lot of WriteDacl and WriteOwner edges. Even to the Domain Root Object:

The only existing ACL that could produce this edge are ACL on the domain root object where the EXCHANGE RECIPIENT ADMINISTRATORS receive CreateChild, DeleteChild, Self, WriteProperty, DeleteTree, ExtendedRight, Delete, WriteDacl, WriteOwner on the object type ms-Exch-Dynamic-Distribution-List.
Full ACL:
InheritedObjectType   : All
ObjectDN              : DC=CHILDDOMAIN,DC=net
ObjectType            : ms-Exch-Dynamic-Distribution-List
IdentityReference     : PARENTDOMAIN\Exchange Recipient Administrators
IsInherited           : False
ActiveDirectoryRights : CreateChild, DeleteChild, Self, WriteProperty, DeleteTree, ExtendedRight, Delete, WriteDacl, WriteOwner
PropagationFlags      : None
ObjectFlags           : ObjectAceTypePresent
InheritanceFlags      : ContainerInherit
InheritanceType       : All
AccessControlType     : Allow
ObjectSID             : S-1-5-21-[REDACTED]
TargetObjectType      : DomainRoot

In this case the EXCHANGE RECIPIENT ADMINISTRATORS comes from a parent domain and the privileges are present on the child domain root object, this might be relevant.
This is a false positive and creates a LOT of unnecessary edges.
Component(s) Affected:

[ ] UI
[ ] API
[ ] Neo4j
[ ] PostgreSQL
[ ] Data Collector (SharpHound, AzureHound)
[ ] Other (tooling, documentation, etc.)

Steps to Reproduce:

Create environment with parent and child domain
Install Exchange Organization in the parent domain in Active Directory Split Permission mode.
Verify EXCHANGE RECIPIENT ADMINISTRATORS have a permission on the domain root object of the child domain
Collect data and run analysis
Check outbound control of EXCHANGE RECIPIENT ADMINISTRATORS

Expected Behavior:
Edges should not be created as permissions on the object type ms-Exch-Dynamic-Distribution-List are not abusable.
Actual Behavior:
EXCHANGE RECIPIENT ADMINISTRATORS show outbound control over all objects in the domain.
Screenshots/Code Snippets/Sample Files:
If applicable, add screenshots, relevant code snippets, or sample files that help illustrate the issue.
Environment Information:
BloodHound: Bloodhound Enterprise
Collector: Sharphound <IP_ADDRESS>
Contributor Checklist:

[X] I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
[X] I have provided clear steps to reproduce the issue.
[X] I have included relevant environment information details.
[X] I have attached necessary supporting documents.
[X] I have checked that any JSON files I am attempting to upload to BloodHound are valid.

Hey @lbrauns,
Thanks for reporting this.
I have Exchange configured in the AD split model in my lab, but I do not have the EXCHANGE RECIPIENT ADMINISTRATORS group at all. I guess it depends on the Exchange version.
Is it possible for you to send a screenshot of the ACE(s) the group has on the domain? Potentially from ldp.exe. Then I will try to create it manually in my lab.

Oh, you added the ACE. never mind!

I just confirmed in my lab that these edges are being generated when creating the given ACE granted to a user, and the user is not able to modify the DACL or change the owner.
When I remove the object type, then I can do those things. So it seems we should confirm that object type is not set before creating WriteDacl and WriteOwner edges. Do you agree @lbrauns?

I just confirmed in my lab that these edges are being generated when creating the given ACE granted to a user, and the user is not able to modify the DACL or change the owner.
When I remove the object type, then I can do those things. So it seems we should confirm that object type is not set before creating WriteDacl and WriteOwner edges. Do you agree @lbrauns?

I am not sure if it is sufficient to check for the presence of an object type. The GUID map of the directory contains abusable object types as well, for example ms-DS-Key-Credential-Link is in there (but is already covered by SharpHound anyways). There might be more abusable object types contained there.

Yes, you are right. We should only avoid creating WriteDacl and WriteOwner if an object type is set. Maybe also GenericAll - I need to test that. We should still create edges like WriteAccountRestrictions that depends on the object type to be set 👍


Debug terminal seems to break when ENABLE_VIRTUAL_TERMINAL_PROCESSING is enabled

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.71.2
OS Version: Windows 10 21H1

Steps to Reproduce:

Compile any C/C++/Rust program that calls SetConsoleMode(handle, ENABLE_VIRTUAL_TERMINAL_PROCESSING) via the Windows API (to get ANSI escape codes working and colorful log messages).
Debug the program (I use the lldb extension), and no matter which terminal values i choose, the log messages all look like this (without the usage of any escape codes, this is just plain Rust println calls):

hello
hello
hello
hello
hello
(after the SetConsoleMode call)
hello
     hello
          hello
               hello
                    hello

This problem did also occur to me when I was writing C++, so I don't think it's a Rust thing.
Also, if I run the program in the terminal manually, everything works as expected.

It seems that printing \r will make the terminal handle the line break properly.

If ENABLE_VIRTUAL_TERMINAL_PROCESSING is on, then Windows (i.e. conhost.exe) interprets the escape sequence instead of xterm.js, correct @Tyriar ?

@zadjii-msft any idea what's going on here?

Which terminal - the embedded xterm.js on, conhost, the Windows Terminal?

Both the VSCode terminal and using an external terminal like cmd.exe worked as expected. The problem only occurs when I debug the program.

This probably isn't a vscode bug, but just something that should be documented better about the Console API. Do you have a minimal code repro?

I was using the fern library for logging. I think just using their pretty_colored.rs example should be enough to repro the issue.

Yea this looks like the client app is only emitting \n to move the cursor down, and not a \r (to move the cursor to the start of the line). The environment matters a bit here - IIRC, the TTY in WSL will automatically convert a \n to a \r\n, but that won't happen if running a straight-up console app without WSL involved.

I looked at the source of the library that I've been using and it does seem that it was only emitting \r\n, but I was still curious that why there was no issues when the program was not debugged and manually run from the integrated terminals.

Hey @Tyriar @meganrogge, this issue might need further attention.
@ngoduyanh, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


SOPA Act

Can I check how BC can help the construction industry around the Security of Payment Act SOPA
https://www.fairtrading.nsw.gov.au/trades-and-businesses/construction-and-trade-essentials/security-of-payment
[Enter feedback here]

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

ID: c1fd6e96-76f1-6d75-570d-1d1cd571be0d
Version Independent ID: 4647bb84-b1ce-abac-5aa3-41df2134d40e
Content: Australia Local Functionality - Business Central
Content Source: business-central/LocalFunctionality/Australia/australia-local-functionality.md
Service: dynamics365-business-central
GitHub Login: @sorenfriisalexandersen
Microsoft Alias: soalex

Hello,
Thank you for your feedback. Since your question is not about the Help, we suggest that you submit a feature request here: https://aka.ms/businesscentralfeedback


Some code block text is very hard to see

For some languages, certain code elements are a dark maroon color on the dark background that is really hard on the eyes.
For example:

Function definitions in Python: https://deploy-preview-8489--cockroachdb-docs.netlify.app/docs/v20.2/build-a-python-app-with-cockroachdb
Function calls in Ruby: https://deploy-preview-8489--cockroachdb-docs.netlify.app/docs/v20.2/build-a-ruby-app-with-cockroachdb.html

FYI: SQL code uses a "purple keywords and blue strings on dark background" that I am finding pretty hard to read also (example: https://www.cockroachlabs.com/docs/v20.2/import#import-a-cockroachdb-dump-file).
I wonder if code samples on a "light mode" page can have a light background?  Sorry, I do not have good eyesight.

This issue will require design work.
@anagio how were the code-block styles implemented? Wondering if we would need wireframes to update this, or we are pulling from a pre-existing library that engineering can directly work with.


Unable to edit files [ Workspacer 0.4 + Smyphony 2.6.11 ]

I'm unable to edit files (I've tried XSL, CSS and JS) because whenever I try to type in the editor the following two Javascript-errors are thrown:
TypeError: $ is not a function
$(document).ready(function() {

in .../workspacer/editor_js/ (Line 104)
TypeError: parent.window.displayLineNumbers is not a function
return parent.window.displayLineNumbers(num_lines);

in .../workspacer/assets/editorframe.js (Line 440)
I'm using latest Firefox (45) on a Mac.

The latest Firefox is 54. Somehow I do not get the errors that you are getting. I have made a small change to editor.js which I hope will fix the problem.


Integrated Terminal not auto-scrolling

VSCode Version: Insider (1.9.0-insider)
OS Version: Mac OSX

Steps to Reproduce:

Open integrated terminal
Do a command which will output text which should scroll the window
The window is not scrolled all the way to the bottom

This is something which is only happening very recently in the Insider build (last day or 2)

I don't really know much about your code base here, but this might be the culprit:
https://github.com/Microsoft/vscode/commit/5f73daec57aabf74458bd2f67635020870513104

Just fixed it :smile: https://github.com/Microsoft/vscode/issues/18370
Resizing the terminal should fix the problem until the fix is out tomorrow.

I checked on my other PC and this is in fact a distinct issue from #18370

Increasing the vertical size of the panel breaks the prompt line until something is input.

@jmc265 you were right, it was exactly that commit :+1:


Set auto SSL renewal for https://directory.atsign.wtf/

As of now we have to renew manually can we setup letsencrypt SSL auto-renewal for this dev site

@cpswan - Created workflow to renew certs for directory.atsign.wtf. Please review and let me know if any changes are required.
https://github.com/atsign-company/at_find_api/pull/66

Presently open PR is https://github.com/atsign-company/at_find_api/pull/67
Still waiting on @kumarnarendra701 to respond to requests for change. Bumping to PR47 and reducing to 2SP.

@cpswan - Please review the below PR.
https://github.com/atsign-company/at_find_api/pull/67
https://github.com/atsign-company/secondaries-scripts/pull/59

This is nearly ready to merge, bumping to PR48 and reducing to 1SP


Feature: Adding intensity color and toggle between z-axis and intensity.

Hi,
first of all, great tool, to replace all visu scripts hacked together over the years!
I would find it really helpful to visualize the intensity of the points.
Happy to help and create a PR.
What needs to be done? Does the dataloader return intensity?
Thanks!

Hi @bjajoh. I'd actually love to see this as well. Sadly Open3D which is the core of the visualizer does not support this. So even if we manage to load it from the data it won't be easily visible.
The other option would be to colorize the poincloud but, I have done that in the past and never looked as nice as, rviz for example.
On the other hand the Dataloaders are the one from kiss icp. So this would involve modifying that as well.
If you see more light in this regards please let me know, I'm also happy to implement stuff.

@bjajoh sorry for the late reply. I did something exactly like this some years ago, and I had a terrible experience when changing from different LiDAR vendors.
I can see that you are using KITTI as an example, the intensity channel has a proper bound. I do remember back then, Ouster was not spitting intensities, let's say, between 0-255. But some integer numbers where not normalized. I'm not sure if this is still the case.
In any case, I will add this to my ToDo list and come back in a few weeks (I'm now overloaded). I guess that the "only" solution I see is to create a dataloader wrapper within this package to load the intensities. Since adding all this complexity into KISS-ICP would be unnecessary for the Odometry pipeline per see.
Thanks for giving some hints :)

Hello again @bjajoh
So I started an experimental branch that adds intensity to the visualizer. Would you like to check it out?
https://github.com/PRBonn/lidar-visualizer/tree/nacho/intensity


Creating a Gallery returns a Liquid Syntax error

I've placed the gallery front matter per minimal mistakes documentation. I then drop into the body of the post using {% include gallery %}.
When I bundle exec jekyll serve, I get the following error:
Liquid Exception: Liquid syntax error (C:/dir/_includes/gallery line 2): Syntax Error in 'assign' - Valid syntax: assign [var] = [source] included in C:/dir/_real_estate/2018-12-30-V2-lessons-learned.md
jekyll 3.7.4 | Error:  Liquid syntax error (C:/dir/_includes/gallery line 2): Syntax Error in ' assign' - Valid syntax: assign [var] = [source] included
front matter

inserting to body of post

I have a feeling that I'm supposed to include {% include gallery %} elsewhere, but I'm not sure where.

You have a public GitHub repo demonstrating this? From the YAML above everything looks correct. Something else is likely the culprit but I'd need your source code to try and reproduce it.

Hi,
I've pushed the changes from my local repo to master.
https://github.com/NahuatlC137/PracticalTechStudios/blob/master/_real_estate/2018-12-30-V2-lessons-learned.md

I see your problem. For some reason when you forked the theme you also changed the gallery include code, which broke it.
Remove your _includes/gallery and replace with the latest theme's. Then it will work.
Also I'd suggest not forking the theme, and instead use it as a remote_theme. You can then remove all the theme files (_layouts, _includes, _sass, assets/css, assets/js, etc.) since it doesn't look like you're customizing anything. This will make sure you always have the latest version without having to manually pull over files and potentially break something.


Syntax Highlighting Bug

There seems to be an issue with the syntax highlighting, at least inside the constructor. Looks like it's intreperting the /* sequence inside the string literal "**/*.json" as the start of a comment block.

I don't seem to reproduce the problem (latest bit in master):

Can you give it another try? If it still occurs, can you provide a bit more about your code, like what is the outer scope and other things may interfere with the highlighting?

It's still happening for me. Though I figured out a very small change that causes it.
It looks like it's broken when the opening curly brace is on a new line instead of next to the function name and arguments.
Broken:

Working:

Can you give #215 a try? It should be fixed there.

Works for me. Thanks!
On Mon, Jun 8, 2015 at 3:08 PM Zhengbo Li<EMAIL_ADDRESS>wrote:

Can you give #215
https://github.com/Microsoft/TypeScript-Sublime-Plugin/pull/215 a try?
It should be fixed there.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript-Sublime-Plugin/issues/191#issuecomment-110109594
.

Great!


Filter if proxy isnt the selected one

closes #316

I'm self confident on this one, it's small and is requested in prod.


Add test for deleting good and bad parent namespaces under race condition

Tested: make e2e-test

/assign @yiqigao217
/assign @adrianludwin

I wonder if we will add more it blocks in this describe block for other tests that require repairing. If so, maybe move the create ns out of beforeEach and put them in each it block? If not, the k apply -f recover can also be moved from it blocks into beforeEach.
WDYT @GinnyJI @adrianludwin

I looked at the two other tests left and they both requires the same set up. I'm not sure in the future if we would add any other new test under this Describe block. For now it seems cleaner to put the set up under BeforeEach than copying them four times

I looked at the two other tests left and they both require the same set up. I'm not sure in the future if we would add any other new test under this Describe block. For now it seems cleaner to put the set up under BeforeEach than copying them four times

sgtm. Also we can change the describe message in the future if there's any change. For now, do you want to move the k apply -f recover to beforeEach as well? Or you can leave it as if in the other two tests, it is not needed. LMK and I will lgtm it.

I looked at the two other tests left and they both require the same set up. I'm not sure in the future if we would add any other new test under this Describe block. For now it seems cleaner to put the set up under BeforeEach than copying them four times

sgtm. Also we can change the describe message in the future if there's any change. For now, do you want to move the k apply -f recover to beforeEach as well? Or you can leave it as if in the other two tests, it is not needed. LMK and I will lgtm it.

Right, I was thinking of that as well. The other two tests require setting up a sub-child namespace under child. Do you know if we can set it up after we repair the HNC, since we have a bad anchor in this tree? If not, we can just leave the k apply -f recover as it is here.

Right, I was thinking of that as well. The other two tests require setting up a sub-child namespace under child. Do you know if we can set it up after we repair the HNC, since we have a bad anchor in this tree? If not, we can just leave the k apply -f recover as it is here.

Yes, we can create subnamespace in this child (which is a subnamespace of the good anchor) without having to bypass the webhook. So we can recover the webhook before that.

Right, I was thinking of that as well. The other two tests require setting up a sub-child namespace under child. Do you know if we can set it up after we repair the HNC, since we have a bad anchor in this tree? If not, we can just leave the k apply -f recover as it is here.

Yes, we can create subnamespace in this child (which is a subnamespace of the good anchor) without having to bypass the webhook. So we can recover the webhook before that.

Great, updated

/lgtm


rabbitmq-server: 3.11.9 -> 3.11.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/rabbitmq/rabbitmq-server/releases.
meta.description for rabbitmq-server is: An implementation of the AMQP messaging protocol
meta.homepage for rabbitmq-server is: https://www.rabbitmq.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 3.11.10 with grep in /nix/store/b932j09rl9f9bhq7yn28avgcbhdr52h4-rabbitmq-server-3.11.10
found 3.11.10 in filename of file in /nix/store/b932j09rl9f9bhq7yn28avgcbhdr52h4-rabbitmq-server-3.11.10

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
rabbitmq-server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/b932j09rl9f9bhq7yn28avgcbhdr52h4-rabbitmq-server-3.11.10 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rabbitmq-server https://github.com/r-ryantm/nixpkgs/archive/46a66f85af41e364aaf37a27d6bc787beb55c091.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/b932j09rl9f9bhq7yn28avgcbhdr52h4-rabbitmq-server-3.11.10
ls -la /nix/store/b932j09rl9f9bhq7yn28avgcbhdr52h4-rabbitmq-server-3.11.10/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

rabbitmq-server

Maintainer pings
cc @turion for testing.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 219560 run on x86_64-linux 1

3 packages built:

rabbitmq-server
rabbitmq-server.doc
rabbitmq-server.man

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

rabbitmq-server:

warning: EvalError
Cannot evaluate attribute ‘rabbitmq-server’ in ‘/nix/store/b0n1fr8py2rsy02b9xbhnrdm8f9q9qlw-nixpkgs’.


Make conventional changelog preset configurable

Is it something reachable to make the preset used for conventional changelog configurable from outside? As of now it's hard coded to the angular one;
Thanks for your huge work!

Hi @apocaliss92, this is something we can introduce pretty easily by adding a new option. The default preset should still be angular, not that we also need to modify the install generator to ask which commitlint config should be installed. Would you want to contribute?

Hi @edbzn , sorry for the late reply, I will create a pr very soon for it!


Better default filenames

Right now all default file names are just 'geoparquet_download_'. It'd be nicer if it'd make use of knowledge from the user selection (like of overture names) or the file name (like when it's just a parquet file).

This could also make use of the 'theme' in overture (under 'base').

This could also make use of the 'theme' in overture (under 'base').

@mtravis - you mentioned this on email, but definitely makes sense to tackle this one and #28 at the same time. In my original code it just displayed the file name instead of 'downloaded layer' (at some point the llm coding assistant changed it ;) ).
So I think the core thing to do is this issue. I think you could add another attribute in the pre-set list that is the default filename, or could try to reuse the labels in some way. That may bring you into https://github.com/cholmes/qgis_plugin_gpq_downloader/issues/15 - like if you add another attribute to all of them then it may be time to just pull those into a separate file (csv?). Ideally it's an easy PR for someone to add a new layer.
I do think just displaying the file name the user chose could be a step in the right direction. Or could make use of the same attribute that we put in as the default for the file name.


Node doesn't support some samples for smoke test

This PR is related to issue https://github.com/Azure/azure-sdk-for-js/issues/17951 which resolves the Node support issue for running the search-documents sample.
@HarshaNalluru Please review and approve it.

@sarangan12 I ran the experimental generator on these samples and pushed the result. I needed to change a couple of things in the samples due to some syntax that is now disallowed because it doesn't play nice with Node 12, so I changed some optional chains into && chains. Other than that I also added a couple of JSDoc tags to the samples that the generator uses to omit certain things from the output. PTAL and let me know if anything looks like it's out of place.
It looks like the experimental generator did its thing. The contents of setup.ts were automatically added to a module.exports block.


ULTRA Basic Documentation

Provide minimum documentation to get users up to speed on running the ULTRA baselines.

[x] How to get baseline models trained on task1 and task2
[x] How to get the ULTRA docker set up
[x]  Clean up writing on key features
[ ] Link ULTRA paper

@AlexLewandowski does the ULTRA paper currently have an available link?

@AlexLewandowski does the ULTRA paper currently have an available link?

@christianjans yeah here is the link

@christianjans yeah here is the link

@AlexLewandowski awesome thanks! I will add it to the README.

@AlexLewandowski awesome thanks! I will add it to the README.


Docs: put some docs together for configuration for zone aware routing

@lyft/network-team

I added a little bit more glue here.

@RomanDzhabarov I would like to finish this up today. Please sit with @junr03 or @ccaraman for 20 minutes and "pair doc write" until it's done.


[Debug]How to verify compiled cluster results against original tf subgraph?

Hi, there! I am now trying to use BladeDISC to optimize my tensorflow model, I have successfully get my model compiled by DISC, however, when checking the optimized model output against original tf version, I found there is a big difference. So i think there might be something wrong with some of the disc-compiled  clusters which i am trying to figure out. After I spent some time diving into the code, i found a setting FLAG called tao_launch_enable_check. According to the code comments, when this flag is ON, it should check the compiled cluster result against tf original subgraph. But i could not find the implementation for this flag. So i am wandering if this logic has been implemented in the codebase. If not, could you please give some advice on implementing it?  I would be glad to contribute to this feature if it is with my ablility. Thanks a lot! @linearhit

@EddieBurning Hello and welcome. the flag tao_launch_enable_check   does not work for disc right now (it was designed for our previous work TAO compiler, an XLA based static shape compiler). Currently, you could try the environment variable export DISC_DEBUG=true, which will dump all inputs and outputs of each cluster and a tgz file used for replay the cluster (see doc here).

Another useful  env is DISC_FORCE_FALLBACK, which will enforce all cluster to go fallback branch (using TF executor).
At present, a quick (but not very convenient, welcome to contribute) way to debug is shown as following：
step 1， set `DISC_DEBUG=true`, and save all outputs of the cluster

Step 2,   set `DISC_DEBUG=true` and `DISC_FORCE_FALLBACK=true`,  and save all outputs of the cluster (this is used as golden)

Step 3,  compare the outputs in step 1 and step 2

Thanks a lot! I will have a try.

set DISC_DEBUG=true, and save all outputs of the cluster

Another useful env is DISC_FORCE_FALLBACK, which will enforce all clusters to go fallback branch (using TF executor).
At present, a quick (but not very convenient, welcome to contribute) way to debug is shown as following：
step 1， set `DISC_DEBUG=true`, and save all outputs of the cluster

Step 2,   set `DISC_DEBUG=true` and `DISC_FORCE_FALLBACK=true`,  and save all outputs of the cluster (this is used as golden)

Step 3,  compare the outputs in step 1 and step 2

Another useful env is DISC_FORCE_FALLBACK, which will enforce all clusters to go fallback branch (using TF executor).
At present, a quick (but not very convenient, welcome to contribute) way to debug is shown as following：
step 1， set `DISC_DEBUG=true`, and save all outputs of the cluster

Step 2,   set `DISC_DEBUG=true` and `DISC_FORCE_FALLBACK=true`,  and save all outputs of the cluster (this is used as golden)

Step 3,  compare the outputs in step 1 and step 2

Hi, there, After checking the env you mentioned, I find out set DISC_DEBUG=true won't dump the cluster output tensors, So
we still can't get the cluster golden output tensors even if we also set DISC_FORCE_FALLBACK=true. Any ideas on how to fix this? @wyzero

@EddieBurning The output will be dumped to stderr. see the code here:
https://github.com/alibaba/BladeDISC/blob/main/tao/tao_bridge/kernels/launch_base.cc#L321
You could also change the above place to save the outputs to files if needed.
Here are some examples to demo how to save tensors to file.
https://github.com/alibaba/BladeDISC/blob/main/tao/tao_bridge/kernels/tao_compilation_cache.cc#L764

thanks a lot. This works!


Remove category-hacks from the HDK tests.

As discussed here https://github.com/modin-project/modin/pull/5738#pullrequestreview-1348432612, the hacks should not be required anymore, after applying the fix #5738.

@AndreyPavlenko Is it still relevant?

@AndreyPavlenko Is it still relevant?

Yes, it's relevant.

HDK engine is deprecated and will be removed in a future version.


Spinner should support format string replacement

Just like Bar supports using %(propname)s, Spinner should do so as well. This allows each loop to give information on what is happening on each iteration.
spinner = Spinner('message with %(context)s')

while some_cond():
    spinner.context = what
    spinner.next()

Actually, Spinner.iter could provide a value property automatically to make this a lot easier as well (of interest to streaming or infinite iterators as well as generators).

Actually, Spinner.iter does exist. Adding a way to get the iteration value is a different request then.


V-Rising LAN Setting is Incorrect

The LAN setting for V-Rising is incorrect. I have found the fix however.
Example Ticket (Not Mine): https://discourse.cubecoders.com/t/configuration-with-v-rising-lanmode/12752
Problem:
"LanMode": true, changes to "LanMode": false, even when LAN mode is set to true in the configuration.
Fix:
Change:
    "DisplayName": "LAN Mode",
    "Category": "V Rising - Host Settings",
    "Description": "Use this setting for a server without internet connectivity. The LAN Mode check box must also be checked in-game when connecting.",
    "Keywords": "lan,mode",
    "FieldName": "LanMode",
    "InputType": "checkbox",
    "DefaultValue": "",
    "IsFlagArgument": false,
    "ParamFieldName": "LanMode",
    "IncludeInCommandLine": false,
    "EnumValues": {
      "False": "",
      "True": "-lan"
    }

To:
  {
    "DisplayName": "LAN Mode",
    "Category": "V Rising - Host Settings",
    "Description": "Use this setting for a server without internet connectivity. The LAN Mode check box must also be checked in-game when connecting.",
    "Keywords": "lan,mode",
    "FieldName": "LanMode",
    "InputType": "checkbox",
    "DefaultValue": "false",
    "IsFlagArgument": false,
    "ParamFieldName": "LanMode",
    "IncludeInCommandLine": false,
    "EnumValues": {
      "False": "false",
      "True": "true"
    }
  },

For me I changed the file located at \instances\VRising01\configmanifest.json
Once I made these changes the LAN mode worked fine.

What's the actual flag format?
Your change would just put true or false in the command line, which doesn't make sense

try this
https://cdn.discordapp.com/attachments/1277836331501883449/1280291965879193731/fix.zip?ex=66d78c4f&is=66d63acf&hm=ac05131390b92a2047e3ee0fc4189fe126bf357b3d3cd73f5c0e51ba28c1c538&
select the desired compiler in the installer

What's the actual flag format?
Your change would just put true or false in the command line, which doesn't make sense

It changes the ServerHostSettings.json file. It sets the "LanMode" setting to either true or false in that file.

The default json supplied with V Rising from steam doesn't have this setting. I see this now at https://github.com/StunlockStudios/vrising-dedicated-server-instructions/blob/master/1.0.x/INSTRUCTIONS.md for the v1.0 server:
Setting: LanMode
Description: Enable LAN mode.
Type: boolean
Example value: true, false
Overrides: VR_LAN_MODE=<value>, -lanMode <value>, -lan, -enableLanMode, -disableLanMode

Which suggests the existing approach of using -lan in the command line should still work. Perhaps try one of the other command line args to see if they make a difference?
It would be easier to use a command line arg given that the setting is not included in the json config by default.

You might also need to disable List on Steam and List on EOS in case they are overriding the effect of the flag.

You might also need to disable List on Steam and List on EOS in case they are overriding the effect of the flag.

I do have those disabled. Unfortunately the other flags also did not work for me.

Can you try with the env var? Add "VR_LAN_MODE":"true"to App.EnvironmentVariables (comma separated from the other variables) and remove the LanMode setting from the json file to test

Thanks for looking into this with me. I think we can close it out. As it turns out AMP was broken and was not updating my templates when I fetched them, so it was an old template. After I fixed that and updated the instance it seems to be working as intended. Much appreciated!


Release Google.Cloud.BigQuery.DataExchange.V1Beta1 version 2.0.0-beta05

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.BigQuery.DataExchange.V1Beta1-2.0.0-beta05


[Request]: Add support for the Windows Share Dialog

Plugin
share_plus
Use case
I am currently working on a multiplatform app and I wanted to implement a share function for them and I run into a missing feature.
Proposal
Add support for the ability to share files/text via the Windows Share Dialog.

https://docs.microsoft.com/en-us/windows/apps/get-started/make-apps-great-for-windows#share-dialog

hey, i am a biggner and i would love to work on this but could you first tell me if i just need to implement a plugin (that i can do)but if intermediate or higher knowledge is required please guide me.

I made an implementation, uses same UWP API through Com/WRL. See: #1158
https://user-images.githubusercontent.com/28951144/193889028-b15f6c3c-9fc1-442c-b472-39b848fcf0ae.mp4


[Feature] May I know how the current progress of 3.3.0 is still far from the official version?

Pre-check

[X] I am sure that all the content I provide is in English.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component
Java SDK (apache/dubbo)
Descriptions
May I know how the current progress of 3.3.0 is still far from the official version?
Related issues
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

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

It should be quick soon.

Synchronizing the latest news, today's meeting said it would be sent at the end of July

this month will publish it.


Bug with icon

https://www.mapcontrib.xyz/t/adb1ea-Les_objets_OSM_avec_un_tag_Mapillary#position/14/44.7830771/-0.5711666
a little so big :)

i think it's external links only

Fixed and deloyed in the 1.10.1 version 🚀


Enable injection prevention

This change doesn't guarantee users will prevent any injection attack,
but by changing the method signature to accept a variable number
of inputs it allows callers to split their input as needed to call the
safer, shell-less kernel.system calls.

@zquestz LGTY? Seemed to resolve the issue I was having with the github stager.

LGTM

Rebased due to changelog conflict; merging.


Port Rotate Certificates action from Ember UI for a cluster

Check Cluster Manager UI - for some clusters, you can rotate secrets.
You can determine if the action is applicable from the mgmt.actions field of the cluster.provisioning.cattle.io model.

You'll need to call the old Norman API for this.

I created DO-rke1 and custom clusters in emberUI, then switched to Dashboard:
Dashboard -> Cluster Management -> cluster menu (...)

Rotate Certificates button is not visible in the menu
Rotate encryption keys button is visible, even though secrets encryption is not enabled
When I enable secrets encryption I can see Rotate Certificates button

It seems that logic for button visibility is swapped between certificate / encryption keys.
I tested the same few days ago (4d18400) and it was working fine.

Tested on master-head (d44698d)

Tested on rke1 DO infra provider cluster with 1 master 1 etcd 1 worker nodes and run on all nodes:
# Commands to get cert information
for file in $(find . -type f -name "*.pem"); do printf "$(md5sum $file)\n\n"; done | grep -v ^$
for i in `ls *.pem|grep -v key`; do echo $i; openssl x509 -startdate -enddate -noout -in $i; done

expiration date is 10 years from now
expiration date is updated after cert rotation
calls are going to v3 api

Rotate single certificate:

etcd: modified kube-etcd cert on etcd node
kubelet: modified kube-node cert on all nodes
kube-apiserver: modified kube-apiserver on control node
kube-proxy: modified kube-proxy on all nodes
kube-scheduler: modified kube-scheduler on control node
kube-control-manager: modified kube-control-manager on control node

Rotate all certificates: rotated all expecpt kube-ca.pem (requestheads / tokens ignored)


[FLINK-12151][es1] Remove Elasticsearch 1 connector

What is the purpose of the change
Remove ES1 connector.
Brief change log

remove e2e test (remove program jar module and test invocations)
remove entry from travis stage organization
remove connector module
bump ES version of elasticsearch-base to 2
remove all documentaton entries relating to ES1

@flinkbot approve consensus

@flinkbot approve all


Refactor multiplication.c to Reduce Duplication and Free Memory

The multiplication.c file contains several code blocks that could benefit from refactoring to remove duplication. Identify the redundant code and create functions to streamline the logic. Also, make sure to free any dynamically allocated memory at the end of the multiplication operation.
Acceptance Criteria:

Minimize code duplication by using helper functions.
Free all dynamically allocated memory at the end of the operation.
Ensure the correctness of the program after refactoring by running tests.

Hey @arya2004 can you assign me this?

Hey @arya2004 i want to work on this issue. Can you assign me?

sure @VaradJadhav


[Bug]: The SAML login checks the signature configuration and saves it, but when you view it, the signature configuration is empty

ODC version
433
OB version
norelated
What happened?
The SAML login checks the signature configuration and saves it, but when you view it, the signature configuration is empty

What did you expect to happen?
The SAML login has the signature configuration checked and saved, but when viewed, the signature configuration should be the same as the configured value, not empty
How can we reproduce it (as minimally and precisely as possible)?
Select a SAML login, configure a signature, click Save, and then review the configuration to check whether the signature takes effect
Anything else we need to know?
No response

Fixed In Commit 7b28c6ef4228bdf39e2aaa0dca264dc0631db33d
------
艺泽
Mon Dec 23 17:57:07 2024 +0800


Can you provide training time and the GPU spec for running this project?

We train a single GPU (12GB) on CIFAR100, miniImageNet, and a single GPU (48GB) on CUB200.


Ronakbsh https services elb

Issue #, if available:
https://app.asana.com/0/1200678426853792/1201481350340429/f
Description of changes:
Support for service ELB running https with selfsign cert
Description of testing performed to validate your changes (required if pull request includes CloudFormation or source code changes):
Deployed via S3 and tested.
it creates selfsign ACM Cert
It creates ELB 443 listener with cert ARN

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

updated to use cert from S3. deployed it at http://d1jgkcqqzb7qqr.cloudfront.net/


添加新的select best ip的方法为默认选取ip的方法

可以用参数选择是用新的还是旧的方法,也增加了reget字段,方便重新测试最优ip

Hello @Wilson-G! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file QUANTAXIS/QAFetch/QATdx.py:

Line 199:80: E501 line too long (88 > 79 characters)
Line 210:80: E501 line too long (82 > 79 characters)
Line 948:80: E501 line too long (93 > 79 characters)
Line 949:80: E501 line too long (87 > 79 characters)
Line 951:80: E501 line too long (90 > 79 characters)
Line 952:80: E501 line too long (87 > 79 characters)


Endpoint -> Environment saved to a yaml doc

Allows for saving environment data in a yaml file.
This should be easily extendable for setting general environment variables,
not just headers and endpoint

Damn you python3, will fix tomorrow


integrate with polkit / restrict access to D-Bus methods

Access to tcd's D-Bus methods is currently forbidden to non-root users.
Instead of this D-Bus policy, tcd could instead integrate with polkit so that non-root users will be asked a password, in the same way as systemctl.

https://www.collabora.com/about-us/blog/2015/06/08/why-polkit-(or,-how-to-mount-a-disk-on-modern-linux)/


ARTEMIS-2721 Activation keeps retrying even after server.stop()

This won't be an issue on a real server (Production system)
however, on the testsuite or while embedded this could cause issues,
if a same instance is stopped then started.
This is the reason why BackupAuthenticationTest was intermittently failing.
I also adapted the test since I would need to stop the server and reactivate it in order to change the configuration.
The previous test wasn't acting like a real server.

ran the whole testsuite. .and it's passing.


[Bug report]:

Platform
Desktop
Version
1.6.4
Description
My Shimmer token balance is wrong after last update on Firefly platform.
I have gone from having five thousand seven hundred ninety-six million, forty-nine thousand six hundred eighty-two Shimmer tokens 5.796.049.682 To having or as I interpret it: Five thousand seven hundred ninety-six Shimmer Tokens with forty-nine thousand six hundred eighty-two hundred thousandths 5.796,049682
5.796.049.682 = 5.796,049682 ????
I upload the documents that I have in my possession!
Thanks for your help and greetings

.
Expected behaviour
I would like it to be well differentiated between the tokens that are integers and the decimal part so that there are no errors. Ex:
5,796,049,682 = 5,796.049682 ???
Actual behaviour
5,796,049,682 = 5,796.049682 ???
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
1 Analyze my Shimmer backgrounds in the previous version
2 Check my Shimmer backgrounds after the update.
3 Check how many Iotas I had in staking 10,013 GI
4 Check how many Shimmer I received from staking
5 Compare all the data to see if they match
Operating System
Windows
Diagnostics
Versión 1.6.4
Idioma: es-ES
Divisa: EUR
Selección de nodo: Automática
Plataforma: win32
Versión de la plataforma: 10.0.19044
Arquitectura de la plataforma: x64
Número de CPU: 4
Memoria Total: 8127.5 MB
Memoria Libre: 3035.5 MB

Developer Profile
No
Profile Type
Software (Stronghold)
Staking
Previously staked
Crash Status
None of the above
Error Messages
No response
Error Logs
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

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

The unit of Shimmer has been changed. But you have the same amount of tokens like before. See also https://twitter.com/fireflywallet/status/1552319343412842496?t=4Ff-VDehCih8NsJdwtm_jw&s=19


Tech Docs review of image_classification.ipynb

This PR fixes typos and improves the text of the notebook.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[iOS] SVG image support

Automatically generated task. Any updates to the title and body will be overwritten. Do NOT modify the labels.
iOS implementation of #777

So there is no SVG support on iOS at the moment?  Any recommended workarounds?

For future reference if this item is re-evaluated in the future: https://github.com/SVGKit/SVGKit/


Add a missing word

"would existing" → "would prefer existing"

Closing because this seems to mean the opposite to what it should.