Foundation.Process on Linux doesn't correctly detect when child process dies (creating zombie processes)

Description
Foundation.Process on Linux uses a trick (that doesn't actually work...) to detect if the child process has exited: It inherits a socketpair descriptor into the child and it expects this socket to be closed when the child exits. In simple scenarios that is true but UNIX by default inherits all file descriptors into child processes. That means if the sub process itself spawns another process, the special socket will be inherited into the child.
That's a huge issue however because now the parent process will no longer detect if the child is dying because the child's child also has that file descriptor...
Attached, please find a reproduction which does the following:
The parent process spawns a /bin/sh as its child process. That child process spawns another process (childs child) which does sleep 12345678 which is a very very long sleep. After one second, parent kills child with SIGKILL which means that child now immediately exits. Then, the parent calls process.waitUntilExit() which should immediately return (because the child is dead). Alas, Foundation.Process does not realise that child is dead because that special socketpair is also inherited into childs child (and further sub processes)...
  Running ps uw -p 13 -p 35 -p 36
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root        13  8.3  4.3<PHONE_NUMBER>84 pts/0   Sl+  14:23   0:00 /usr/bin/swift-frontend -frontend -interpret process_bug_repro.swift -Xllvm -aarch64-use-tbi -disable-objc-interop
root        35  0.0  0.0      0     0 pts/0    Z    14:23   0:00 [sh] <defunct>
root        36  0.0  0.0   2308   832 pts/0    S    14:23   0:00 /bin/sh -c echo "[in childs child: $$] start"; sleep 12345678; echo "[in childs child: $$] done"
[...] output continues "forever"

Fix
Instead of using this special socketpair which has two issues:

As demonstrated above, this can lead to false negatives (because fd gets inherited further)
This can also lead to false positives (because the child process could close all its file descriptors making Foundation.Process think that the child has exited when it hasn't)

To fix both of these, Foundation.Process should either use pidfd_open or signalfd on SIGCHLD to get an epollable signal when the child process dies.

https://man7.org/linux/man-pages/man2/pidfd_open.2.html
https://man7.org/linux/man-pages/man2/signalfd.2.html

single file repro: process_bug_repro.swift ( in zip for GitHub)
process_bug_repro.zip

Still happens in 6.0 with swift-foundation.


Syntax highlighting broken when using ES6 arrow function's implicit return to return JSX

From https://github.com/Microsoft/TypeScript-TmLanguage/issues/401

VSCode Version: 1.8.1
OS Version: OSX 10.11.6

Steps to Reproduce:

Create a .js file, and write some JSX in it like so:

Use an arrow function to implicitly return JSX.

Watch as the syntax highlighting below breaks.

This only breaks when the JSX is implicitly returned with the ES6 arrow function. If you wrap the JSX in parens, the syntax highlighting is not broken:

Using the arrow function and using an explicit return fixes the syntax highlighting as well:

@matthamil Thanks for the report. Which color theme are you using?

@joshpeng https://marketplace.visualstudio.com/items?itemName=joshpeng.theme-charcoal-oceanicnext

@matthamil This was pretty nasty. I committed a potential fix to the arrow-implicit-return branch. Can you please try it out locally on your end and provide feedback? To test, you can grab the sublime-babel.json file and replace the current version in your VS Code extensions folder.
Windows: %USERPROFILE%\.vscode\extensions\joshpeng.sublime-babel-vscode-0.2.3\syntaxes
Mac/Linux: ~/.vscode/extensions/joshpeng.sublime-babel-vscode-0.2.3/syntaxes

:tada: I think that fixed it

Aw crap. Just noticed it doesn't fully work when two or more tags are used.

@matthamil Did another commit. Can you please try again? Something like this should have all the tags highlighted the same color now. If you run across any other scenarios where this might be broken please let me know. Thanks.
org => <UserOrganizationItemContainer><Blah><zxclk>fdsa</zxclk></Blah></UserOrganizationItemContainer>

It works unless you nest the same type of element like so:
The first example is nesting 3 <div> tags. The second example nests varied tags.

@matthamil Pushed another commit. Please try again. Thanks for all the testing help.
sublime-babel.json

Sure thing, thanks for maintaining this project :tada:. All seems to be working now. If another bug comes up, I'll open another issue.

@matthamil One last time haha. I reverted the previous commit and put in another approach. Fingers crossed. The earlier issue was leaking tokens and messing up closing ) and } brackets.


feat : Support uniform bucket level access.

This closes #2869

This change is

/cc: @JesseLovelace in case you want to take a look.

@JesseLovelace ,
Please let me know your comments on this PR.

@JesseLovelace any thoughts?


ARTEMIS-2541 Improve message browser of Admin UI

any chance you could attach before and after images to the PR discussion?

@clebertsuconic I added another screenshot before the modifications.

I checked AMQP, and this property is only filled with Core Protocol. I checked and it worked fine.
Perhaps we could add with extra properties.

but that will be an improvement. I'm merging this.


Update scala-library to 2.13.5

Updates org.scala-lang:scala-library from 2.11.12 to 2.13.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, semver-minor

Codecov Report

Merging #125 (6e459c6) into master (bc467fe) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #125   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           41        41
=========================================
  Hits            41        41

Continue to review full report at Codecov.

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


Not generating thumbnail from URI (from link)

I am not able to  generate thumbnail from URI (from link)
example (http://www.africau.edu/images/default/sample.pdf)
code
const { uri, width, height } = await PdfThumbnail.generate("http://www.africau.edu/images/default/sample.pdf", 0);

On Android it doesn't support http uri scheme.
On iOS I haven't tested whether it is supported.
I think you can download the file first, then use the local file path to get thumbnail.

Closing as we don't want to add dependency to download files. Your app can download the file first and use the local file path to get thumbnail.


Since the StoragePoolSpec has changed, modify the selector

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
design spec #6
design spec #7
Special notes for your reviewer:
Release note:

Coverage increased (+3.3%) to 58.169% when pulling e7a3fed5316b5eb8c62ab24dad8b2de123477d45 on PengYiOfOpenSDS:ModSelectorTest into c818d79c934a365e6e5f5a3cd099a6a53914139d on opensds:development.

Coverage increased (+3.3%) to 58.169% when pulling e7a3fed5316b5eb8c62ab24dad8b2de123477d45 on PengYiOfOpenSDS:ModSelectorTest into c818d79c934a365e6e5f5a3cd099a6a53914139d on opensds:development.

Coverage increased (+3.3%) to 58.169% when pulling e7a3fed5316b5eb8c62ab24dad8b2de123477d45 on PengYiOfOpenSDS:ModSelectorTest into c818d79c934a365e6e5f5a3cd099a6a53914139d on opensds:development.

Coverage increased (+3.3%) to 58.169% when pulling e7a3fed5316b5eb8c62ab24dad8b2de123477d45 on PengYiOfOpenSDS:ModSelectorTest into c818d79c934a365e6e5f5a3cd099a6a53914139d on opensds:development.

@xxwjj @wisererik @lasshpanzer Please have a review at this patch


Terminology update: High-availability control plane

Towards https://github.com/giantswarm/giantswarm/issues/14964
This PR aligns the naming of the feature high-availability control plane (formerly called high-availability master nodes). Also in the feature page the term master node is replaced with control plane node. Links and shortcodes are adapted accordingly.

FYI @alex-dabija as the page and feature is owned by Firecracker.

I am a little confused. Isn't what we called control plane now management cluster ?

@stone-z This wasn't supposed to be the only PR for the terminology change. I wanted to keep it digestible and easier to review by making several PRs.


Reproduce Bodesheim et al 2013

http://www.inf-cv.uni-jena.de/Forschung/paperProjects/Kernel+Null+Space+Met
hods+for+Novelty+Detection.html

Reproduce results on Caltech256 only.

Once you have convinced yourself that your code is correct, please refer to this issue in the commit message.


Add Italian website translation

Bot was translated to Italian here: https://github.com/ro31337/libretaxi/issues/526 and we need to translate the website (http://libretaxi.org/) into Italian the same way it was done for other languages: by translating index.html in this repository.
For translator: feel free to create PR right to master, feel free to skip updating links on other pages if you don't have time (I will update them). You just need to translate and commit 1 page only.

Translations have been added to master. Closing.


How can I test abap2UI5 locally?

I ran npm install successfully and installed all available VSCode extensions for UI5/Fiori.
Though none of the npm scripts work for me.
npm run start

npm run start-local

npm run start-noflp

What am I missing?
P.S. I'm on Windows 10 if that's important

i think you have to run without flp, try:
npm run start-noflp

you can also check here (will update and bring it to the documentation):
https://github.com/abap2UI5/abap2UI5/blob/main/app/README.md

and do one time a global renaming, that your abap backend system can be found:
replace in all files: <<system>> with your abap url.
for example here:
https://github.com/abap2UI5/abap2UI5/blob/main/app/ui5-mock.yaml#L20C18-L20C28

Thx. I'm one step further with npm run start-noflp.
Now I'm getting CORS issues. What's the best way to deal with them?

Mhh normally this should not happen because all requests go to the local server and then via proxy to the abap system.
Did you renamed the server url correctly in all three files? I did the following:

I also tested it on my machine and updated the readme with all steps i did, check it here:
https://github.com/abap2UI5/abap2UI5/blob/main/app/README.md
It works on my side, here is my terminal:

Thx. I'll try again. Maybe it was too late yesterday ;-)

@oblomov-dev
link https://github.com/abap2UI5/abap2UI5/blob/main/app/README.md is dead. Did you move it?

yes its here now: https://abap2ui5.github.io/docs/advanced/extensibility/frontend.html

Great. It's working for me now. Don't know what I did differently than last week. Thx a lot.


[Base] Theme Screen

[X] Issue does not already exist
Identify exactly what aspect your issue is about

[X] ignite base application
[ ] ignite the cli
[ ] ignite generated code

I think what I came up with for one of our projects would be a reasonable starting point:

Nice, but how would you find "headings" programmatically?  You can only find font sizes.


Unable to run extension development host on Ubuntu

VSCode Version: 1.2.1
OS Version: Ubuntu 16.04 LTS

Steps to Reproduce:

Create a new Ubuntu VM using 16.04 LTS
sudo apt-get install nodejs nodejs-legacy npm
Install Code from the website
Clone an extension (eg. https://github.com/DanTup/Dart-Code/)

Extension fails to activate and the console in the main Code instance reports:
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell

From the error in the console it appears that extension.js did not get created by TS compiled/
Can you please complete the steps. You clone the dart repo, then what?
I tried:

cd to the cloned repo
npm install
npm run compile
open vscode on the folder
press F5 (launch extension).
The dart extension seems to come up properly.

Ok, so it worked after that. It still spewed the same error, but it did launch :)
So, is it something I did wrong? If I clone a repo with an extension should I be running npm install manually, or is there something that should've done this for me when I hit F5 in Code?

npm install normally needs to be called manually right after cloning.
What happens on launch depends on what's listed as 'preLaunch' task in launch.json.
In your case it calls the npm default task (defined in tasks.json) which runs npm run compile.
Now, in my steps I ran npm run compile manually and that's why it worked. If not doing that, it seems that F5 does call the npm task, and the npm tasks calls npm run compile. I even get the message 10:52:32 PM - Compilation complete. Watching for file changes. in the output window,
but no files get generated (out/src stays empty)

@aeschli Just to confirm (it's not clear to me from your message), this sounds like a bug and not something I did wrong?

There seems to be bug on our side that the launch preTask does not really compile the TS files. It says it does, but no files are created in out/src. We will investigate...

Was not able to reproduce this.
@aeschli are you sure that the out folder didn't get created. It is filtered in the .settings :-)

Yes I unfiltered it.
Trying it again:

start vscode fresh, unfilter the out folder.
delete the out/src folder, create a empty src folder again
press F5.
Extension Development Host starts, open a dart file, all works fine, files are compiled
shutdown the Extension Development Host
delete the out/src folder, create a empty src folder again
press F5.
Extension Development Host starts, open a dart file, error, out/src stays empty.
Run 'terminate running task'
press F5.
Extension Development Host starts, open a dart file, all works fine, files are compiled

Is that the expected behaviour that the compile task stays running and prevents recompiles?

Yes, that is the current 'expected' behavior. The way how @bpasero sets this up in the vscode npm module is as a watching compile, which doesn't recompile if the output folder gets deleted (tsc behaves the same). A watching compile only runs if the input changes, not if the output gets deleted.
I opt to close this issue. Any objections.

Wouldn't it be better to kill the task when the Extension Development Host is closed? It is not obvious to the user that there's still a task running and how to terminate it. Also I don't need to have my files compiled until I start the the Extension Development Host again.
But I guess I'd rather create a separate issue for that... I created #10118.
Closing this issue. It looks the main problem was that npm install was not called after cloning.

Just to confirm - when I clone the repo to a clean machine, I should run npm install before opening it to avoid this, it's not expected for Code to do this?
(I'm not complaining, I just want to be sure I understand!)

Yes, correct, it's up to you to run npm install.

Thanks!


Variable DAG targets do not work in WorkflowTemplates

Summary
Given this YAML:
apiVersion: argoproj.io/v1alpha1
kind: ClusterWorkflowTemplate

metadata:
  generateName: dag-target-

spec:
  entrypoint: main
  templates:
    - name: main
      inputs:
        parameters:
          - name: target
            value: heads
      dag:
        target: "{{inputs.parameters.target}}"
        tasks:
          - name: heads
            template: heads

    - name: heads
      container:
        image: alpine:3.6
        command: [sh, -c]
        args: ["echo \"it was heads\""]

$ argo cluster-template create dag-target.yaml
2021/07/02 17:28:30 Failed to create cluster workflow template: ,  templates.main.targets: target 'placeholder-4' is not defined

This happens for both CWFT and WFT. However, changing it to a simple Workflow and doing argo submit seems to work completely fine.

K8s v1.20
Argo Workflows v3.0.7; I have not yet been able to test v3.1.x :(
Docker executor

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I also hit by this issue in v3.4.11. I have some strange finding. If the template name is main it works and it won't if it changed to something else.
@alexec, @terrytangyuan I think we should re-open this issue and address the bug.

up

This issue is still relevant.


Roll Engine from 819ca4ec8cd5 to 8ab4124eeff5 (2 revisions)

https://github.com/flutter/engine/compare/819ca4ec8cd5...8ab4124eeff5
2022-04-22<EMAIL_ADDRESS>Reland: simplify the logic around computing subtree opacity inheritance (flutter/engine#32853)
2022-04-22<EMAIL_ADDRESS>add DlPaint object for optional use with DisplayListBuilder (flutter/engine#32860)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Missing link

Link missing at the end of Line 39, it says "To get started, see ."
https://github.com/MicrosoftDocs/azure-docs/blame/master/articles/azure-functions/dedicated-plan.md#L39

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

ID: 57106982-21bb-f60a-fde3-7f9d4e83afb1
Version Independent ID: 5922b4e9-ea56-be60-760e-5e01f4dc422b
Content: Azure Functions Dedicated hosting
Content Source: articles/azure-functions/dedicated-plan.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hello @tyeth,
Thank you for your feedback! We will review and update as appropriate.

Thanks @tyeth for reporting this and @ChaitanyaNaykodi-MSFT for fixing it!


Consume published angular component

Which scope/s are relevant/related to the feature request?
Don't know / other
Information
I have a private package on my registry, that exports an angular directive which looks like this
Directive()
export abstract class StatefulComponent<S, VE> implements OnInit, OnDestroy {
// ...
}

This library was created in an NX monorepo. It is using angular v17.
tsconfig.json
{
	"compilerOptions": {
		"target": "es2022",
		"useDefineForClassFields": false,
		"forceConsistentCasingInFileNames": true,
		"strict": true,
		"noImplicitOverride": true,
		"noPropertyAccessFromIndexSignature": true,
		"noImplicitReturns": true,
		"noFallthroughCasesInSwitch": true
	},
	"files": [],
	"include": [],
	"references": [
		{
			"path": "./tsconfig.lib.json"
		},
		{
			"path": "./tsconfig.spec.json"
		}
	],
	"extends": "../../../tsconfig.base.json",
	"angularCompilerOptions": {
		"enableI18nLegacyMessageIdFormat": false,
		"strictInjectionParameters": true,
		"strictInputAccessModifiers": true,
		"strictTemplates": true
	}
}

tsconfig.lib.json
{
	"extends": "./tsconfig.json",
	"compilerOptions": {
		"outDir": "../../../dist/out-tsc",
		"declaration": true,
		"declarationMap": true,
		"inlineSources": true,
		"types": []
	},
	"exclude": [
		"src/**/*.spec.ts",
		"src/test-setup.ts",
		"jest.config.ts",
		"src/**/*.test.ts"
	],
	"include": ["src/**/*.ts"]
}

tsconfig.lib.prod.json
{
	"extends": "./tsconfig.lib.json",
	"compilerOptions": {
		"declarationMap": false
	},
	"angularCompilerOptions": {
		"compilationMode": "partial"
	}
}

This component is built and published through ci/cd to my private registry. I then consume this component from other angular applications(outside of the NX monorepo) by extending it.
export class ExampleComponent extends StatefulComponent<
  ExampleState,
  ExampleEvent
>

This has been working for my normal angular applications.

When I started my migration to astro-angular, I started getting errors like the one below
[ERROR] No value provided for @angular/core symbol 'ɵɵInputFlags'.

when i'm serving the application (astro dev) and accessing the component in question.
I've tried adapting the tsonfig.lib.json with the values that are in the documentation (https://analogjs.org/docs/packages/astro-angular/overview), but I keep getting the same error.
Is this something that should work generally?
Describe any alternatives/workarounds you're currently using
Copied the library to component in my project as is, and it worked.
I would be willing to submit a PR to fix this issue

[X] Yes
[ ] No

A minimal reproduction might be helpful here; as this seems very project-specific. I'd like to volunteer to investigate this if you're able to provide that

Some updates:
I started trying to create a repro and figured out that I had different minor versions of angular in the library and the application(17.3.2 vs 17.0.0). Updating the versions to match made the reported issue go away. I am now getting a different issue, which i'm not sure if it is an analog or an angular problem.
ERROR RuntimeError: NG0203: inject() must be called from an injection context such as a constructor, a factory function, a field initializer, or a function used with `runInInjectionContext`. Find more at https://angular.io/errors/NG0203

Repro in stackblitz

Started with astro - minimal repo
Installed analog(Followed the documentation)
Installed @astrojs/node
Installed the angular cli
Created an angular project ( named another-lib)
Created an angular library inside of it (named lib1)
Added a very basic component and exported it( lib1/Lib1Component )
'Linked' it to the main astro/analog application(Follow the steps in the readme)
Extend the Lib1Component(hello.component.ts)
Build the astro application(astro build)
Serve the astro application(astro preview)

It's likely that this only happens during SSR? If so, try doing this first as Angular packages need an extra compilation step
https://analogjs.org/docs/features/server/server-side-rendering#transforming-packages-for-ssr-compatibility

Yep, this fixed it on the stackblitz repro. I still have issues on my main project which is only different from the repro, on that the library is generated in an nx monorepo. Will close this issue for now as my problem is probably due to different/faulty tsconfig.

For reference: I fixed it, and it was dumb. So i use bun, and i was linking the library with bun link for local testing. Apparently if said library is a symlink, the above errors were thrown. Once i copied(instead of symlinked) the library in the node_modules, it worked.

@alator21 cool, glad you got it figured out


v3 Toast and Snackbar prevent touch when present

I have gone through these following points

[x] Check latest documentation: https://docs.nativebase.io/
[x] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[x] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[x] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description

node, npm, react-native, react and native-base version, expo version if used, xcode version
RN 64 (Hermes enabled)
NativeBase: ^3.0.0-next.36
Expected behaviour
Displaying Toast or Snackbar should not prevent user to manipulate with the rest of the UI.
Actual behaviour
When Toast or Snackbar are present they prevent from using rest of the UI.
Steps to reproduce

<Button  onPress={() =>  toast({position: 'bottom', title: 'TEST TOAST MESSAGE', duration: 5000})}>
   TEST
</Button>

Is the bug present in both iOS and Android or in any one of them?
Both for me
Any other additional info which would help us debug the issue quicker.
From the source code it looks like they are using Overlay internally and a Wrapper.tsx component that has always a fullscreen transparent view applied to it.

same problem

@DavideCrapa @LadislavBohm Thanks for reporting. This has been resolved in new version. Let me know If you're still facing any issue.


Exercise diamond \n at end of diamond

Hey, as discussed in #2255 we could remove the required \n at the end of the diamond, as also the instructions do not have one as you can see here:
Diamond for letter 'C':
··A··
·B·B·
C···C
·B·B·
··A··

Alternatively, we can make the tests accept both forms, by comparing the newline trimmed versions of expected vs. actual. This might make the tests harder to debug though.
I don't think there's a right answer here because what's more convenient depends on the algorithm the student is using. I'll post here the two kinds of solutions I see the most when mentoring, one would benefit from having a \n at the end, and the other would prefer for the \n to not be there.
strings.Join based solutions - prefers no \n at the end
If the student computes all the rows and puts them in a slice, then the more natural approach to generate the final string is using strings.Join:
var rows []string

for keepGeneratingLines {
    row := ComputeRow(...)
    rows = append(rows, row)
}

return strings.Join(rows, "\n")

In this case not having a final \n is desirable, just so the student doesn't have to write strings.Join(slice, "\n") + "\n".
strings.Builder based solutions - prefers \n at the end
However, some students also build the string using strings.Builder:
var b strings.Builder

for keepGeneratingLines {
    row := ComputeRow(...)
    b.WriteString(row)
    b.WriteString("\n")
}

return b.String()

In this scenario, it is more convenient for the final \n to be there, just so the loop doesn't have any "last row" special condition.

Thanks @andrerfcsantos for the insights! I forgot to consider the different approaches here.

Thanks @andrerfcsantos for the examples. There is of course no right answer for this issue, but we should at least adjust the instructions to make clear what is expected (\n or not). Which version do you prefer?

I pondered this a bit more and my tendency is now towards actually requiring no line break at the end as @eklatzer originally suggested. Contrary to what I wrote before, I think that it actually adds value to the exercise because the scenario that you build something up line by line but then need to do something different at the end also happens in the real world.
Let's say we stated clearly in the instructions that there should not be a line break at the end. Then there are two options for students.

They already used a way of solving the exercise that incorporates the requirement of no new line at the end (e.g. via strings.Join). In this case there is no additional difficulty which is fine.
Their approach leads to a line break at the end (e.g. when using builder or string concatenation) then they need to deal with removing it before returning the result. In this case the exercise is a bit harder but I think in a good way because besides being quite a realistic scenario, it is one of these "the devil is in the detail" cases which was a tag line of Exercism in V1 I think. There are quite some exercises which have similar vibes.

A mentor could then potentially even mention that the issue with the new line does not arise with the strings.Join approach. Or if someone used a loop but excluded the last iteration to handle it separately you can discuss this approach vs. running the entire loop and fixing the line break afterwards.
If people disagree with my favorite solution described above, my second favorite would be the one with making the tests agnostic to the last line break. Shouldn't be too hard as we only need to do "if it is there, remove it before checking against the expected result" or the other way around. If we go with this, there should be a comment in the test file about why we do that part though.

I pondered this a bit more and my tendency is now towards actually requiring no line break at the end as @eklatzer originally suggested. Contrary to what I wrote before, I think that it actually adds value to the exercise because the scenario that you build something up line by line but then need to do something different at the end also happens in the real world. Let's say we stated clearly in the instructions that there should not be a line break at the end.

I also agree with this. I think my position of allowing both comes from my brief experience in competitive programming, where my team got screwed a lot by these kinds of things. Failing a submission because of missing or extra whitespace at the end always gave me this "unfair" feeling.
I agree with imposing no extra line at the end, but we must state that clearly in the exercise description and we must ensure the test output shows clearly that is the case. A failing test because extra or missing whitespace should scream that is the case. Using %q might not be enough, especially for exercises like the diamond exercise where the strings are quite big.

Their approach leads to a line break at the end (e.g. when using builder or string concatenation) then they need to deal with removing it before returning the result.

One more argument in favor of requiring no extra line at the end is that you don't actually need to remove the extra line at the end, or add a special condition inside the loop. Instead of:
var b strings.Builder

for keepGeneratingLines {
    row := ComputeRow(...)
    b.WriteString(row)
    b.WriteString("\n")
}

return b.String()

You can handle the first case especially instead:
var b strings.Builder

row := ComputeRow(0)
b.WriteString(row)

for generateLinesExcludingFirstOne {
    row := ComputeRow(...)
    b.WriteString("\n")
    b.WriteString(row)
}

return b.String()

This is actually the way strings.Join works internally.
The issue here is that such solution might not be obvious for students, and they might have all the logic to create a line in the loop itself and not in a function like ComputeRow. But I'm ok with this not being obvious and leave this to mentor discussions.

So summarized: no \n at the end but a specific test (or maybe included in the other tests) that checks if the only error is a additional \n at the end?

Yes :) I don't think it needs to be a new test, can be included in the existing ones.

I will work on this one when #2279 is finished, so I can directly update the generator


Semaphore improvement and addition to upload flows

Explain the changes

Accounted PUT Object / Upload Part in the global semaphore
Changes to semaphore cleanup logic on non settled working items

Issues: Fixed #xxx / Gap #xxx

https://github.com/noobaa/noobaa-core/issues/6707

Testing Instructions:

@liranmauda
Yes, we still need the same logic for surround as well since it just takes up 1 instead of a count that you gave it.
Even in that case we can have a Semaphore of 1 and take it all up and not release on non-settled promises.


Remove debug println

It's filling up our test logs :p

@Krastanov looks like the breakage on QuantumSymbolics is transient? At least not related to this change :)

indeed, the QuantumSymbolics failure is unrelated. LGTM

Are you able to merge it? Looks like I don't have permission :)

I will merge and release.
@david-pl , could you check the permissions?


Parallel elm make calls corrupt elm-stuff/0.19.1/i.dat

Quick Summary: Elm make running in parallel corrupts elm-stuff/0.19.1/i.dat

Elm: 0.19.1
Browser: N/A
Operating System: Ubuntu 16.04

Running elm-make in parallel to compile different entry points every now and then errors out with the message below:
Compiling ...+-------------------------------------------------------------------------------
|  Corrupt File: /build/source/myproject/elm-stuff/0.19.1/i.dat
|   Byte Offset: 102336
|       Message: not enough bytes
|
| Please report this to https://github.com/elm/compiler/issues
| Trying to continue anyway.
+-------------------------------------------------------------------------------

-- CORRUPT CACHE ---------------------------------------------------------------

It looks like some of the information cached in elm-stuff/ has been corrupted.

Try deleting your elm-stuff/ directory to get unstuck.

Note: This almost certainly means that a 3rd party tool (or editor plugin) is
causing problems your the elm-stuff/ directory. Try disabling 3rd party tools
one by one until you figure out which it is!

Additional Details
This has been mentioned in https://github.com/elm/compiler/issues/1830#issuecomment-727259777, we found it by searching for the error message.
We were facing the same problem when using esbuild's elm plugin. I opened an issue on the plugin's side here: https://github.com/phenax/esbuild-plugin-elm/issues/2
There might be other spots https://github.com/elm/compiler/commit/054fa04074fd819958affd04a526e10f69aa5197 didn't cover that might be worth locking on.
Work-around
Don't let elm run in parallel.
It might be hard to track who's launching elm in parallel. It was for us. To track down all places we wrapped the elm executable in a shell script that blew every elm up when launching more than one instance of elm in parallel. This way we also caught a failures in the already-running elm callsite once a parallel launch was attempted.

Not sure if it's relevant, but we were also observing o.dat get corrupted.

@evancz Any plans to make the compiler able to run in parallel?

Any updates on this?

I have one potential update. In my experience, Elm has a file based lock so that parallel elm make actually run in sequence. However, there is no lock for the “dependencies” part of the compilation – that’s where I’ve seen failures. So what I did in my case was to first run elm make --output /dev/null Dummy.elm to force the dependencies stuff to be done, then I started my parallel elm make processes.

We tried serial dependency fetching -> parallel compilation, and can report it didn't work for us. We still ran into the same issue described in the OP and had to quickly revert.
I'm not contesting @lydell's report tho. The trick might indeed reduce the likelihood of corruption, but that reduction wasn't enough to prevent corruption from happening frequently in a codebase with so many Elm apps to be compiled in parallel as NoRedInk's codebase.


Make it possible to show numeric keypad on Android

Right now we always show the default keypad.

It appears EditorInfo is part of this story.  We may need to create our own input connection like Chromium does:
https://code.google.com/p/chromium/codesearch#chromium/src/ui/platform_window/android/java/src/org/chromium/ui/PlatformImeControllerAndroid.java&q=editorinfo&sq=package:chromium&type=cs&l=9

Looks like we already do. This is the line needing changing:
https://github.com/domokit/sky_engine/blob/master/services/keyboard/src/org/chromium/mojo/keyboard/InputConnectionAdaptor.java#L28

I believe we need to fork the keyboard service into sky first.

Ended up deciding to do this in mojo.  I am sad panda. Step 1: https://codereview.chromium.org/1279863003


Stop ignoring panics in the peer receiver and heartbeat tasks

Motivation
Zebra currently ignores panics in the peer message receiver task, and in the peer heartbeat task.
This can cause security or usability issues, because it can hide bugs, and cause hangs.
Designs
Add the join handles for these tasks to the Client, and poll them for panics during Client::poll_ready
https://github.com/ZcashFoundation/zebra/blob/3ddb9f9e59e3c9d477c011c1feb424390eb0ac14/zebra-network/src/peer/handshake.rs#L929-L931
https://github.com/ZcashFoundation/zebra/blob/3ddb9f9e59e3c9d477c011c1feb424390eb0ac14/zebra-network/src/peer/handshake.rs#L947-L948
Related Work
This might be the cause of peer set or Zebra hangs.

Hey team! Please add your planning poker estimate with ZenHub @conradoplg @dconnolly @jvff @oxarbitrage @teor2345 @upbqdn


[Spotify Player] Menu command no longer works

Extension
https://www.raycast.com/mattisssa/spotify-player
Raycast Version
1.82.0
macOS Version
14.6.1
Description
Error:
Error: The operation couldn’t be completed. (Foundation.JSONError error 0.)

Steps To Reproduce
Error occurs even after logout/login.
Current Behaviour
No response
Expected Behaviour
No response

Hey, just found out the same behaviour on my machine, investigating what can it be. A tricky one since once I built it locally everything started to work normally...

It may have been caused by a regression in the API. Are you still experiencing the issue?

@thomaslombart Now it only shows the menu bar item when there's an error. It no longer shows what's playing. I've tried deactivating and reactivating it. Any ideas?

Could you share a recording? It'll make it easier to see what's happening.

This'll be pretty easy, as it just doesn't show anything. :) Thanks for looking into this.
https://github.com/user-attachments/assets/e71f9607-e28d-4202-9044-31e80d6aed54

The Foundation.JSONError has been fixed in 1.82.3, so I'd first check if you're up-to-date. I also know that the Hide icon when idle option, as shown below, has caused the menu bar player to be a bit buggy. If it's enabled, I'd recommend disabling it. Otherwise, you can uninstall and then reinstall the extension.

@thomaslombart It was the "Hide icon" setting. I subscribed to the other issue. Thanks!

Thanks for letting me know! I'll close this one out then.


New PR

Description

Motivation and Context

Testing

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist

[ ] I have read the CONTRIBUTING document
[ ] Local run of mvn install succeeds
[ ] My code follows the code style of this project
[ ] My change requires a change to the Javadoc documentation
[ ] I have updated the Javadoc documentation accordingly
[ ] I have read the README document
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed
[ ] A short description of the change has been added to the CHANGELOG
[ ] My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

[x] I confirm that this pull request can be released under the Apache 2 license

/tests-integration

/override-changelog-check

/reassign


Refactor String.prototype.replace

This change brings the replace operation up to date with ES6 by
implementing support for the @@replace well-known symbol, while
also improving performance and memory usage.

Benchmark
Heap (bytes)
Perf (sec)

regexp-dna.js
1311936 -> 1011720 : +22.88%
2.343 -> 1.302 : +44.452%

string-tagcloud.js
1308912 ->  995680 : +23.93%
3.037 -> 2.270 : +25.247%

string-unpack-code.js
751824 ->  645456 : +14.14%
9.688 -> 0.977 : +89.919%

Binary (ES5.1)
master
patch
diff

.text
119460
119404
-56 bytes

Binary (ES2015)
master
patch
diff

.text
157300
158396
+1096 bytes


Add WorkflowStubCallsInterceptor which provides an access to Headers

Partially addresses #373.
Added new WorkflowStubOutboundCallsInterceptor with the same idea and implemented in the same way as WorkflowOutboundCallsInterceptor, WorkflowInboundCallsInterceptor, ActivityInboundCallsInterceptor that provides Header access.
Part of WorkflowStubImpl is refactored to be implemented in a similar manner with SyncWorkflowContext implements WorkflowOutboundCallsInterceptor
The reason to add a new interceptor interface is an inability to wire Headers in the existing WorkflowClientInterceptor/WorkflowStub, because it would expose Headers to WorkflowStub client code and break compatibility. Also, this solution is adding a layer of Stub interceptors that is organized the same way as interceptors in Worker.

@vitarb Yeah, probably you are missing a context.
I need to implement opentracing support and for that, I need abilities that interceptors give us. Also, I need to propagate context on all stages. Client code -> workflow execution -> activity execution.
I can theoretically implement in using context propagator + interceptors, but after discussion with @mfateev we decided that this should be implementable fully in interceptors. And context propagator itself in the future should be implemented using interceptors.
So, this is the last missing piece. Adding an ability to modify headers in client stub propagators.

we considered adding headers into WorkflowOptions instead?
Nah, as far as I know.
The use case I care about is an ability to modify headers "silently", not by explicitly passing anything in WorkflowOptions.
Also, as far as I see from the code, we do our best to don't expose Headers even for workflow code, we want to keep it an implementation detail and expose them only for interceptors.

An alternative solution that is lighter will actually be bothering of Worflow stub interface and passing Headers there in a start method. But it will 1. break backward compatibility 2. Expose Headers as a part of WorkflowStub interface that is not internal and a part of public API. That's why I chose this way of implementing it, especially because it's the closest way to Worker Interceptors by how it works.

Discussed over zoom call, concluded that there is an alternative path through setting headers in workflow options, which we can access through workflow stub in the WorkflowClientInterceptor.
My main concern with this PR is that it looks like a bit of an overkill for simply setting headers. On the other hand I do see value of having more generic solution.
Dmitry is going to implement this approach as well and then we can discuss both of them with @mfateev and decide which one we want.

Drafted an alternative solution https://github.com/temporalio/sdk-java/pull/384 with an example of how the actual interceptor could look like with that solution. From my point of view, it's as bad as it could get. Let's discuss next week. @vitarb @mfateev

@vitarb @mfateev could you guys please revisit this PR? It's pretty much done.
There is some more work to do around, especially WorkflowExecutionUtilsneeds a revisit and reorganization and because of that, exceptions handling in this PR is not fully systemic, but it has to be done as a separate PR. Also TimeLocking code can't be reworked on the new interceptors because of an issue highlighted in a separate bug report: https://github.com/temporalio/sdk-java/issues/392
Please feel free to leave any naming suggestions for anything created in this PR, I will revisit your comments and amend the names that I used.


How to get the instance and invoke execCommand() method?

I want to insert some extra content to the tinymce, and if I use pure tinymce I can achieve that by
tinymce.activeEditor.execCommand('mceInsertContent', false, 'your content');

How do I achieve it with ui-tinymce?

You can add a setup function to the options object. The function gets passed the editor as the first argument.
$scope.tinymceOptions = {
    setup: function(editor) {
        //Save editor to var or execCommand here.
    }
}

Please note that there are a few issues (#143, #166) where adding a setup function may break some other things. I plan to have this fixed on the next release coming out soon.


Need help urgent can some combine the fallowing code with this AUTORCcar code or provide any ideas or suggestions

Link to github
https://github.com/nikgens/TankRobotProject/tree/master/signRecognition

Have you connected that one
Please tell me it's urgent


List of ideas for what looks possible/interesting

A task list of points of exploration, as issues. The issues should include

what's possible with existing data
what data enhancement would we like (and why)

[ ]

Multiple points have been mentioned in the summary after discussion and deliberation, and as data breadth and depth increases, more things will be possible.
Also, one possible limiting factor that slowed progress a bit was being from a Computer Science and Technology background and realizing which features of data can be valuable for this domain. This can definitely be improved by some background study.


Suggested changes to PR 109

Move processing of --grpc_addr to ovs_set_grpc_addr() and rewrite it to remove vulnerabilities.
Note that this has not yet been tested.

Tested these changes and they work properly. LGTM. Merging to the branch grpc_option_support


At some point, I request a code.

Enter code (6 digits) for INSTA_ACCOUNT (ChallengeChoice.EMAIL):
Other accounts work fine. How do I solve it?

You need to verify your account

met the question too, how to fix it

You need to verify your account

where to verify?ins or gmail?

@j-teng96 on the mail service, if you have gmail, then there

You need to verify your account

It doesn't pop up when I run it on my other computer, can't I set it up?


Log: MR Python client REST rebase

This is just a convenience GitHub issue to log data from multiple sources, and provide a summary of the Model Registry Python client rebase on REST work, so far.
The challenge
Historically, the Model Registry Python client connected directly to the gRPC MLMD container/service.
Besides this requiring to replicate logic on GoLang REST server and the MR Python client itself (i.e.: implement the Logical Model mapping to/from MLMD both in GoLang and Python) so in pragmatic terms implementing the same logic in 2 places, it posed some additional challenges due to the only distributions available of the MLMD python library/wheel.
For example, but not limiting to:

the MLMD python wheel only distributed for x86 (example at this link, only amd64/x86 available)
the MLMD python wheel only distributed for CPython 3.9 and 3.10, not available for 3.11 (see, for example, https://github.com/google/ml-metadata/issues/198)

Introducing a workaround
Some of these concerns where partially addressed with:

providing a remote-only, grpc-only version of the MLMD whl (see related document)

However, this posed some challenges to end-users, for example but not limiting to:

https://github.com/kubeflow/model-registry/issues/90#issuecomment-2141340442
https://cloud-native.slack.com/archives/C073N7B6K3R/p1719234732313409
https://groups.google.com/g/kubeflow-discuss/c/yMZ7q1gTSak/m/4MSuTkFJAQAJ

as can be seen, it was difficult to explain to end-user the constraint mainly came as the requirement from the MLMD whl, not necessarily a choice originating in the MR client itself.
The solution
This was overcome with:

https://github.com/kubeflow/model-registry/pull/152
work by @isinyaaa which rebased the MR Python client to interact with the Model Registry server directly instead (and no longer the wrapped MLMD) via its exposed REST API.

Please notice the code-generated part is not exposed (and is not intended to be exposed in the future) to the end-user of the MR Python client; this is so that, if in the future we will need to change the underlying implementation, that would require a little less effort eventually.
What else was considered
Different REST code generators were evaluated, including Kiota, openapi-codegen, etc.
Each code generators had some limitations; for posterity in the case of Kiota a bunch were actually addressed upstream, for example:

https://github.com/microsoft/kiota/issues/4428
https://github.com/microsoft/kiota/issues/4325

While other remain (at the time of writing):

https://github.com/microsoft/kiota/issues/4178
https://github.com/microsoft/kiota/issues/4433
https://github.com/microsoft/kiota/issues/4750#issuecomment-2160551178

In the case of openapi-codegen, limitations affected discriminator fields too, for example requiring to "manually" change the generated code anyway:
https://github.com/kubeflow/model-registry/blob/aeb4bdaf2d1eddb5c6540043a3a2b343a038808e/clients/python/patches/fix-validators.patch#L1-L24
Since the openapi-codegen is already used on the Go side to generate the server models, this was picked as the selected code-generator to go forward with at this time.
Additional considerations
This workaround is no longer needed:
https://github.com/kubeflow/model-registry/pull/116/files#diff-6b074bce6a463d7cd6b69e5b1901d4d48c6ff2cd150a40ce849f7a99cb68bce4R123-R124
thanks to the REST rebase.
With KF 1.9, this workaround is no longer needed:
https://github.com/kubeflow/model-registry/issues/165#issuecomment-2202204285
thanks to the REST rebase.

I would like to express my gratitude to everyone who contributed directly or indirectly to this work, it benefits a lot the MR python client itself and its end-users 🙏

Considered Done.


[SR-435] Less specific method recorded in the protocol witness table

Previous ID
SR-435

Radar
rdar://problem/24031731

Original Reporter
@an0

Type
Bug

Additional Detail from JIRA

Votes
1

Component/s
Compiler

Labels
Bug

Assignee
None

Priority
Medium

md5: ebc1bb2c8590dd5c9b38b1264038435b

Issue Description:
When there are default protocol implementation, constrained protocol extension implementation, type implementation, constrained type extension implementation, of an API, which one is actually called is very confusing and some current behaviors are quite odd.
I think:

The definite dispatching rules should specified and documented.
Some of current behaviors are bugs — though I'm not sure which because I'm not sure about the dispatching rules — and should fixed.

Commented code with execution results should explain the issues more clearly:
protocol P {
    typealias T

    func f()
    func g()
}

extension P {
    func f() {
        print("P.f")
    }

    func g() {
        print("P.g")
        f() // Should call P.Equatable.f if T is Equatable, shouldn't it?
    }
}

extension P where T: Equatable {
    func f() {
        print("P.Equatable.f") // Inaccessible to P.g? Not even to P.Equatable.g but accessible to to Foo.Equatable.g — odd.
    }

//    func g() {
//        print("P.Equatable.g")
//        f() // Should call P.Equatable.f if T is Equatable, shouldn't it?
//    }
}

struct Foo<U>: P {
    typealias T = U

//    func g() {
//        print("Foo.g")
//        f()
//    }
}

extension Foo where U: Equatable {
//    func f() {
//        print("Foo.Equatable.f") // Inaccessible to P.g or Foo.g? At least accessible to Foo.Equatable.g.
//    }

//    func g() {
//        print("Foo.Equatable.g")
//        f()
//    }
}

let foo = Foo<Int>()
foo.f()
print("")
foo.g()

// Uncomment P.Equatable.g, Foo.g, Foo.Equatable.g, Foo.Equatable.f to see other behaviors.

The actual output:
P.Equatable.f

P.g
P.f

The expected output:
P.Equatable.f

P.g
P.Equatable.f

We need a one-to-many mapping for generic conformances to support this. Currently conformances are always a one-to-one mapping.


Support for IntelliJ 2022.3 EAP

IntelliJ just launched another new EAP.

Interestingly IntelliJ complains about incompatible plugin, but if you click "Enable Plugin", it still seems to work.
It even looks ok in their completely new UI:

A 223 specific plugin has been released pending jetbrains approval.


Add regression tests

Move branch to azure-tros instead of fork.

Reopen for tests.

Closing, tests already added in another PR.


Mustache Package Extension: mustache not found.

I have a package called Foo which consists of the following
module Foo
using Mustache
using Oxygen
mustache
end

When I call include("src/Foo.jl"), everything is fine and mustache exists. However, when I call using Foo, it tells me that mustache is not found.
Failed to precompile Foo [824a3e6e-b590-4e34-af71-7e7af32a149a] to "/Users/ian/.julia/compiled/v1.10/Foo/jl_NHg9jE".
ERROR: LoadError: UndefVarError: `mustache` not defined
Stacktrace:
 [1] top-level scope
   @ ~/Documents/Foo/src/query.jl:7
 [2] include(mod::Module, _path::String)
   @ Base ./Base.jl:495
 [3] include(x::String)
   @ X ~/Documents/Foo/src/Foo.jl:1
 [4] top-level scope
   @ ~/Documents/Foo/src/Foo.jl:15
 [5] include
   @ ./Base.jl:495 [inlined]
 [6] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::Nothing)
   @ Base ./loading.jl:2222
 [7] top-level scope
   @ stdin:3
in expression starting at /Users/ian/Documents/Foo/src/query.jl:7
in expression starting at /Users/ian/Documents/Foo/src/Foo.jl:1
in expression starting at stdin:
Stacktrace:
 [1] pkgerror(msg::String)
   @ Pkg.Types ~/.julia/juliaup/julia-1.10.4+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Pkg/src/Types.jl:70
 [2] precompile(ctx::Pkg.Types.Context, pkgs::Vector{Pkg.Types.PackageSpec}; internal_call::Bool, strict::Bool, warn_loaded::Bool, already_instantiated::Bool, timing::Bool, _from_loading::Bool, kwargs::@Kwargs{io::Base.TTY})
   @ Pkg.API ~/.julia/juliaup/julia-1.10.4+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Pkg/src/API.jl:1659
 [3] precompile(pkgs::Vector{Pkg.Types.PackageSpec}; io::Base.TTY, kwargs::@Kwargs{warn_loaded::Bool})
   @ Pkg.API ~/.julia/juliaup/julia-1.10.4+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Pkg/src/API.jl:159
 [4] precompile(; name::Nothing, uuid::Nothing, version::Nothing, url::Nothing, rev::Nothing, path::Nothing, mode::Pkg.Types.PackageMode, subdir::Nothing, kwargs::@Kwargs{warn_loaded::Bool})
   @ Pkg.API ~/.julia/juliaup/julia-1.10.4+0.aarch64.apple.darwin14/share/julia/stdlib/v1.10/Pkg/src/API.jl:174

Hi @limarta,
Sorry about the slow turnaround - but I have a solution to your problem!
you just need place any code that uses the mustache function inside the __init__ function in your package - to ensure it's ran once at the correct time.
The mustache function is loaded dynamically when the module is loaded. The root issue is that your code is trying to access a symbol that doesn't exist until the __init__ function within Oxygen in ran.
I created a test package to reproduce this error - below is a runnable example that uses mustache templating.
Important takeaways

not all code has to defined inside the __init__, but anything that uses extensions does
I heavily recommend running the @oxidise macro at the top of your module when building a package on top of Oxygen. This macro will ensure we use a unique internal state object each time it's loaded. If you don't do this, then it will default to Oxygen's internal global state which will cause issues if someone tries to use Oxygen alongside your package.

module TestPackage

using Mustache
using Oxygen; @oxidise

export serve, terminate

function __init__()

    # Define a Mustache template (both plain strings and mustache templates are supported)
    template_str = "Hello, {{name}}!"

    # Create a render function, specifying the MIME type as text/plain
    render = mustache(template_str, mime_type="text/plain") # mime_type keyword arg is optional

    @get "/plain/text/{name}" function(req, name::String)
        data = Dict("name" => name)
        return render(data)  # This will return a plain text response with the rendered template
    end

    @get "/" function()
        return "home"
    end
end

end # module TestPackage

And here's my runtests.jl file
using Test
using HTTP
using TestPackage

serve(async=true, port=6001)

@test HTTP.get("http://localhost:6001/").body |> String == "home"
@test HTTP.get("http://localhost:6001/plain/text/joe").body |> String == "Hello, joe!"
@test HTTP.get("http://localhost:6001/plain/text/Danny").body |> String == "Hello, Danny!"

terminate()


libcore.io does not exist

Custom Android template build fail:
OS/device including version:

Linux Mint 19.1
Oracle JDK 8
NDK ver.:  android-ndk-r17c
SCons ver: 3.0.1
Issue description:

Steps to reproduce:
scons platform=android target=release android_arch=armv7
scons platform=android target=release android_arch=arm64v8
scons platform=android target=release android_arch=x86
cd platform/android/java
./gradlew build
result:
/home/ghost/Develop/Games/Godot/source/godot-master/platform/android/java/src/android/system/ErrnoException.java:21: error: package libcore.io does not exist
import libcore.io.Libcore;
^
/home/ghost/Develop/Games/Godot/source/godot-master/platform/android/java/src/android/os/Handler.java:708: error: cannot find symbol
final IMessenger getIMessenger() {
^
symbol:   class IMessenger
location: class Handler
/home/ghost/Develop/Games/Godot/source/godot-master/platform/android/java/src/android/os/Handler.java:746: error: cannot find symbol
IMessenger mMessenger;
^
symbol:   class IMessenger
location: class Handler
/home/ghost/Develop/Games/Godot/source/godot-master/platform/android/java/src/java/net/InetAddress.java:23: error: cannot find symbol
import dalvik.system.BlockGuard;
^
symbol:   class BlockGuard
location: package dalvik.system
/home/ghost/Develop/Games/Godot/source/godot-master/platform/android/java/src/java/net/InetAddress.java:37: error: package libcore.io does not exist
import libcore.io.IoBridge;
^
...etc...
...etc...
...etc...
Minimal reproduction project:

Please, ignore this. I've put some symbolic links in my platform/android/java/src folder by mistake. :/


Component filling

PR to fill the missing component as life takes me.

All the remaining components have been implemented.
Two things to clean before we merge:

make all components to inherit from a base trait that people can use for some magic
make all attributes lazy to reduce footprint as low as possible.


Colors and pictures

Add image optimization action and convert from hex to hsl notation for colors

Images automagically compressed by Calibre's image-actions ✨
Compression reduced images by 19.8%, saving 14.70 KB.


Pop Quiz

0.89/1

0.95/1

0.9/1

This allows users to have authentication requests based on a certain requirements through .permit all and have restrictions with.authentication

0.9/1

0.89/1
0.95/1
0.9/1
0.7/1(lowest score left out)
0.9/1

0.89 + 0.95+0.9+0.9 = 3.64/4 (0.91/1)


feat!: add x/upgrade params

ref: https://github.com/osmosis-labs/osmosis/issues/1612
Add Params to x/upgrade which includes a single field: IsMainnet of type bool.

@ValarDragon what should this be backported to, v11?


client-side library to build generic queries

Consider I have Settings model in my app which often being searched by different fields. Usually I have to make a wrapper like following, and I would like to have a library already implemented generic wrappers like below for any model.
import type { Settings } from './types.ts'
export const getSettings = async (args: Settings) => {
    try {
        const queryUrl = `${dbUrl}/dev/settings`
        const params = Object.entries(args)
        const [key, value] = params.pop()
        queryUrl += `?${key}=${value}`
        for (const [key, value] of params) {
            queryUrl += `.${key}=${value}`
        }
        const resp = await fetch(queryUrl)
            .then(resp => resp.json())
        if (resp.results[0]) {
            return [null, resp.results[0]]
        } else {
            throw `settings not found`
        }
    } catch (err) {
        return [err.toString(), null]
    }
}

@7flash, @BearLemma is working on such a thing, I'll let him explain :)

Hey @7flash ! We are on the verge of releasing version 0.15 which contains support for automatically generated clients for CRUD endpoints. @CodingDoug already wrote a blog post about it - https://blog.chiselstrike.com/new-in-0-15-the-chiselstrike-typescript-client-api-a4f6760cee9e Check it out and let me know if it helps :]
I'll be trying to add support for general endpoints as well, but that's unfortunately significantly harder so I don't have an ETA yet.

Well done!


Remove lower cutoff for fock bases.

Coverage decreased (-0.006%) to 98.109% when pulling 3ea26de724efc4fc4d60a6c67361cde2a659168d on fock into f0f4a20f308287241dcc1a5c3c8c6ec236699644 on master.


add Persian (farsi) language

First of all, thank you for the PR, I was going to make this arrangement.
But when I examined the codes, I saw that you wrote "ltr" instead of "rtl", didn't you have a chance to test it?
Can you review, edit and test the code again?


DA-847 updated the sdk to allow empty profile sharing.

update to allow empty profiles, also updated package.json to add dependencies  to package.json

Looks good, there's a lot of let statements that should be const, especially for test mocks. But it seems the whole SDK was written like this.
Don't forget to bump the package version number.

made updates to version number and pinned dependencies thanks guys


Install CoreDNS as HelmRelease

Towards https://github.com/giantswarm/giantswarm/issues/23449

It's tested in both WC and MC


Improve test coverage

Coverage increased (+2.4%) to 69.212% when pulling 3e947ff57d1b1423010a9e909a3daecaa18aa7e7 on unittest into df10ee6e8ac6980f407782548f8b6da8290fbc9e on master.

Coverage increased (+3.7%) to 70.476% when pulling 2013023e001106d2b81de2979de60046a0abad83 on unittest into df10ee6e8ac6980f407782548f8b6da8290fbc9e on master.


Why are you so evil?

I posted a thread like this with my @6bmwrkjc account:
Where to download VSCode for Windows 7? #16

The vscode-win7 repo doesn't have any releases!
https://github.com/Alex313031/vscode-win7

The thread received no replies. I found that I can't see the issues I have submitted in https://github.com/issues anymore but at that time I have not yet realized what happened to that account. I simply thought that it's Github that is buggy so I created a new account. Today I posted a new issue in the supermium repository and logged out. I found my issue is hidden from the public. After some research I know I'm being flagged. Man, if you think I'm not worth for you to care about please just close or delete the issue I have submitted to your repository. Why did you report my account? My question is sincere. I really don't know. If you think I'm a troll please just ignore me. Why did you do that? You are so evil!

You are one of the motivations for me to switch to Linux. Thank you :-1:


Forbid performing Clean command against all system schemas in Oracle

This PR is to forbid cleaning system schemas in Oracle. Currently Flyway forbids Clean only against SYSTEM schema, but not others. (See issue #1550)
This PR includes PR #1558. Only commits starting from https://github.com/vosolovskiy/flyway/commit/f900b760f1603ebb705a915f0a543f471c760081 are related to the mentioned change.
The list of system schemas is determined based on Oracle Documentation and the data dictionary of the target database.
One test class for EnterpriseDB was removed, because it was mistakenly created and didn't contain any proper tests.

Merged. Thanks!

@configman I don't get why you need to use clean in your production environment. However, @vosolovskiy what are your thoughts on the root container after upgrade issue?

@axelfontaine You are right, I got my logic a little confused, the point is that the change prevents use on 12c root container schemas, which we have, and therefore prevents upgrade from V4.1.2.  My point about production is really that we would like to use the latest but that the inability to use the same version in lower environments would prevent that.
As things stand we would be required to migrate all schemas into a PDB, which is doable, but will require planning and effort.  We would also be unable to upgrade until the last schema has been migrated.  This is why I think that we need to be able to manage this process and allow the clean on these schemas in some way until all the migrations are complete.

Will be able to check it not earlier than next week.
@configman how do these schemas look in ALL_USERS after migration? is ORACLE_MAINTAINED set to Y for them?

@configman I am curious on how you ended up with your application schemas in the root container of the CDB?
After an upgrade of an 11g database the resulting 12c database will be a Non-CDB database. Then, to switch to the multitenant architecture, the Non-CDB database can be migrated to a PDB as described here: https://docs.oracle.com/database/121/ADMIN/cdb_plug.htm#ADMIN13598 or here: https://oracle-base.com/articles/12c/multitenant-migrate-non-cdb-to-pdb-12cr1
@vosolovskiy I think the logic implemented in this PR is correct. Clean should not touch any of the system schemas. ALL schemas in the root container is to be considered as system schemas. See https://docs.oracle.com/database/121/CNCPT/cdblogic.htm for reference.

@larsulv I am completely in agreement with the principle that the clean should not touch system schemas in the root container.  My point is simply that in introducing a breaking change such as this it would be sensible to allow an option to maintain the previous behaviour.

@configman That can be a point.
But the answer to @vosolovskiy question is interesting.: "how do these schemas look in ALL_USERS after migration? is ORACLE_MAINTAINED set to Y for them?"

I am not involved in migration, but I can see some schemas for which the ORACLE_MAINTAINED flag is set to Y.


C#: Add more examples and improve existing ones

LGTM

Formatting check is failing on master as well (and it is being fixed).


gdax pagination implemented?

According to https://docs.pro.coinbase.com/#get-trades the request is paginated but I'm not seeing how to use this in xchange.
Is this actually implemented?

Yes, it is implemented.
If you look in GDAX.java it is here:
@GET
@Path("products/{baseCurrency}-{targetCurrency}/trades")
GDAXTrade[] getTrades(
@PathParam("baseCurrency") String baseCurrency,
@PathParam("targetCurrency") String targetCurrency)
throws GDAXException, IOException;

OK, I'm pretty sure, though totally surprised, that this has never been implemented.  I'll take a look at it.


tools/extra/opae.io requires libedit header files

@tswhison and @r-rojo Note that this does not fix the missing CMake ordering dependence that is broken. In parallel builds, CMake is building opae.io before pybind11 is ready. I don't know CMake well enough to fix that. I'm having to disable parallel builds to compile successfully.

Coverage decreased (-0.01%) to 65.936% when pulling ec3ed88dc9afecbec1e446a223da92a7e51b6da6 on mcadler/opae.io_libedit into 1d68a32a7334ae04743762ecefed84e0cd06387d on master.

@r-rojo will you work on pybind11 dependence to fix the parallel build?


Per-User MFA to Conditional Access MFA

The script provided to assist with moving away from per-user MFA is not clear on the following point. Why would you set Strong Auth Requirement State to 'Enforced'? Shouldn't this be left at disabled? If disabled, then Conditional Access is the control for MFA. If it's set to 'Enforced' then MFA is configured at the user-level and is required outside of Conditional Access. What am I missing?

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

ID: f132318f-8670-fd0d-2524-01305ccff2a1
Version Independent ID: 0849b4a9-ff14-1d61-47f2-a2daecf3cde9
Content: Plan and execute an Azure Multi-Factor Authentication deployment - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-getstarted.md
Service: active-directory
Sub-service: authentication
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@toddjohnson39 Thanks for reporting this. You are correct. Users should be in a disabled state. I am updating the script accordingly.


Compile our own JRE

Hi @MartelliEnrico, please open an issue to track this change.
I'd suggest naming it "Improve Dockerfile to generate a lighter image"

Will try a different route, using the maven-jlink-plugin.


[Feature] 目前元数据中心推送的元数据都没有过期时间 使用nacos当元数据中心还有数量限制 改用redis当元数据中心之后 发现也没有过期ttl设置

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
目前元数据中心推送的元数据都没有过期时间 使用nacos当元数据中心还有数量限制 改用redis当元数据中心之后 发现也没有过期ttl设置
Related issues
No response
Are you willing to submit a pull request to fix on your own?

[X] 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

Please re-submit the issue in English. We want all the content in GitHub are in English.


on demand animation

How can I have animation to run once on demand? I need to show shot splash animation each time player does a shot. I see 2 options here:

on each shot to add a new entity with SpriteSheetBundle and animation and then track Play component removal and remove whole this entity. But this way I will remove all entities that jsut lost Play component, not only shot animation entity.
create entity beforehand with SpriteSheetBundle and animation but without Play component and with visibility: Visibility{is_visible: false},. And then on each shoot to add Play component in it and set up visibility to true. The problem here is how do I differ shot animation entity from other animation entities?

on each shot to add a new entity with SpriteSheetBundle and animation and then track Play component removal and remove whole this entity. But this way I will remove all entities that jsut lost Play component, not only shot animation entity.

You may ensure that a special Splash component is present before removing the entity.

create entity beforehand with SpriteSheetBundle and animation but without Play component and with visibility: Visibility{is_visible: false},. And then on each shoot to add Play component in it and set up visibility to true. The problem here is how do I differ shot animation entity from other animation entities?

I don't think I understand well. Why beforehand? You could spawn the splash animation when you need it. When it comes to differentiating shot animation from other entities, it's the same as how to differentiate any entity. You may use a "tag" component to recognize the purpose of the entity.
Lastly, be aware that you can also reset the animation by calling reset on the SpriteSheetAnimationState. So you may re-use the same entity, add/remove the play component and reset the animation each time.
Personally, I think I would go the route of spawning a new "splash" animation entity, and despawn it when it is done by detecting when the Play component is removed. I would use a Splash unit struct to tag the splash entities in order to make sure that I despawn only the splash. Example:
fn despawn_splashes(mut cmds: Commands, splashes: Query<(), With<Splash>>, ended: RemovedComponent<Play>) {
  for entity in ended.iter().filter(|e| splashes.get(e).is_ok()) {
    cmds.entity(entity).despawn();
  }
}


fix: Errors in graphql schema autogen

/claim #1331
/fixes #1331
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

New Features

Enhanced API capabilities with new input types and scalar types in the GraphQL schema.

Refactor

Improved efficiency and type handling in the GraphQL schema generation logic.

Documentation

Introduced logic to extract and write descriptions for custom scalar properties.

Please review @tusharmath / @ssddOnTop

Closing in favour of https://github.com/tailcallhq/tailcall/pull/1371


Output VEX documents?

Could daggerboard generate VEX documents like the CSAF or CycloneDX documents?

As of now, Daggerboard is on the ingestion side of the SBOM pipeline - meaning that it was only intended to ingest and analyze SBOMs and, in the future, VEX documents. Daggerboard does not currently support VEX ingestion, but this is on the list of features to add in the next phase of the project.
There is a list of tools for generating VEX documents here: https://cyclonedx.org/tool-center/


[sigstore-conformance]enable delete branch on merge for all current repos in sigstore-conformance

Summary

enable delete branch on merge for all current repos in sigstore-conformance

also to test the changes added in #293

need https://github.com/sigstore/community/pull/297


Drop fails when supplied with an object that implements getitem

When you supply drop with an item that implements __getitem__, drop doesn't drop it. It does when supplied with the item within a list.
That's because instead of checking is_list_like (here), drop calls _index_labels_to_array which does this. That returns an empty list when supplied with an object that implements __getitem__. (if you want the technicals, that's because list(obj) == [], as __getitem__ used to be the way of implementing iteration. is_list_like ignores that case, I think correctly).
Should _index_labels_to_array instead call is_list_like?
In [182]:

class GetItemObj(object):

    def __init__(self, n):
        self.n = n

    def __getitem__(self, item):
        if item == 'a':
            return self.n
        else:
            raise IndexError

    def __hash__(self):
        return self.n

    def __repr__(self):
        return 'Item: {}'.format(self.n)
In [183]:

index=pd.Index([GetItemObj(i) for i in range(2)])
index
Out[183]:
Index([Item: 0, Item: 1], dtype='object')
In [186]:

index.drop(index[0])
Out[186]:
Index([Item: 0, Item: 1], dtype='object')
In [187]:

index.drop([index[0]])
Out[187]:
Index([Item: 1], dtype='object')

I'm not sure about putting iterables in an index.  Does your proposed method solve the case when your object defines __iter__?

@kawochen have a look at is_list_like - it does almost exactly that: https://github.com/pydata/pandas/blob/master/pandas/core/common.py#L2329
Definitely agree putting iterables / list like objects in an index is not a good idea.

I think I did follow.  But I think the support would still be partial.  I was thinking
class DictLikeObj(dict):
    def __hash__(self):
        return hash(tuple(sorted(self.items())))

(I am against making it easy to put iterables in Index)

Apologies @kawochen, I'm not sure I understand. What's that class for?
My class above was a demonstration, I'm not suggesting that goes in the code.
I can do a quick PR - that may makes my point clearer

@MaximilianR that is a class whose instances that I think would still fail to be dropped after your proposed change, so some iterables would work, some wouldn't.

yeh .drop is slightly different, not really sure why. always for cleaning / consolidating. You can try changing and see what breaks (if anything).
And there are slight differences in the iterables & checking and its very very subtle (e.g. the __hash__ DOES matter)


A message on the desktop_drop channel was discarded before it could be handled.

I wrap it on a listview on web, it produces msg:
A message on the desktop_drop channel was discarded before it could be handled.
This happens when a plugin sends messages to the framework side before the framework has had an opportunity to register a listener. See the ChannelBuffers API documentation for details on how to configure the channel to expect more messages, or to expect messages to get discarded:
https://api.flutter.dev/flutter/dart-ui/ChannelBuffers-class.html
It seems ok on a simple zone, like a text container.

My bad, I put it on a empty widget, so it tells no listerner registered.


refactor(openapi): swap EmptyNull with nullable

Replaces user-defined type EmptyNull with the
nullable defined by the OpenAPI specification.

This change is

Hmm, honestly I am not such a fan of this approach. This does not explain at all when the property is null at the behavior (empty array = null) is not obvious (at least for non-Golang dev). If you want to go this path I would suggest adding into all descriptions of these properties info about when it is null.

Hmm, honestly I am not such a fan of this approach. This does not explain at all when the property is null and the behavior (empty array = null) is not obvious (at least for non-Golang dev). If you want to go this path I would suggest adding into all descriptions of these properties info about when it is null.

I'd disagree here since the specification is clear on that what the nullable express and the consumer should be aware of this specification. On top of that, the current description using the EmptyNull is not valid according to the https://editor.swagger.io/ it returns the following error:
Structural error at components.schemas.EmptyNull.type
should be equal to one of the allowed values
allowedValues: array, boolean, integer, number, object, string
Jump to line 143

I'd disagree here since the specification is clear on that what the nullable express and the consumer should be aware of this specification.

I am not saying that the user should not understand what nullable means. Sure, for some generic objects that have an attribute with a potential null value that in its context makes sense, why not. But coming from JS (and few other langs) backgrounds, I would 100% expect you to return an empty array instead of null for the case when there are no entries. Few others team members from Bee Geezs (JS) were also quite surprised by this.

On top of that, the current description using the EmptyNull is not valid according to the editor.swagger.io it returns the following error:

Heh, my IDE then confused me about allowed values 😅 Then I agree with dropping my approach but, as mentioned before, I would add a textual description that "Returns null if there are no entries instead of empty array".

I'd disagree here since the specification is clear on that what the nullable express and the consumer should be aware of this specification.

I am not saying that the user should not understand what nullable means. Sure, for some generic objects that have an attribute with a potential null value that in its context makes sense, why not. But coming from JS (and few other langs) backgrounds, I would 100% expect you to return an empty array instead of null for the case when there are no entries. Few others team members from Bee Geezs (JS) were also quite surprised by this.

On top of that, the current description using the EmptyNull is not valid according to the editor.swagger.io it returns the following error:

Heh, my IDE then confused me about allowed values 😅 Then I agree with dropping my approach but, as mentioned before, I would add a textual description that "Returns null if there are no entries instead of empty array".

I agree with returning an empty array instead of a null. That's best practice when designing an API. This PR doesn't address that, it just fixes the errors pointed out by the validator. Hopefully, the fix replacing the null values with the empty array will come soon, but some things need to be discussed before we make that change.

Yeah agree, I am only trying to be more "dummy developer-friendly" and propose to explain when there can be null value as I don't think it is obvious...


check statusCode from sockRequest and sockRequestRaw

There are still a lot of unchecked statuses.

#dibs

@LK4D4 hmm when I took a stab at it, I pretty much fixed cases where we did err.Error().Contains("201 Accepted") etc.
In other cases, tests already return a nice error message containing the statusCode. Can you show some examples?

@ahmetalpbalkan There are multiple tests where nothing is done with the status code, such as in
integration-cli/docker_api_resize_test.go for TestResizeApiResponse:
_, _, err = sockRequest("POST", endpoint, nil)
if err != nil {
t.Fatalf("resize Request failed %v", err)
}
Where we only check if the error is not nil, but not that the status returned is what we expect. At least that's the changes I have been making.

@LK4D4 @kostickm yes that err definitely contains status code (check sockRequest method). You don't need to use statusCode if it's already printed to screen with t.Fatalf :smile:

@kostickm in most tests we expect HTTP 200 and that's already being checked in sockRequest as well. If you try to check all calls for HTTP 200, you will just increase redundancy/repetition in the code.

@ahmetalpbalkan Ah thank you! Didn't realize that. @LK4D4 I guess I'm not sure which status need checked then?

we should remove check from socketRaw. It is wrong to expect always 200.

@LK4D4 @ahmetalpbalkan I'm starting not to like the method itself. I mean err should be returned if something went wrong with the request not if the request went ok and status was not 200. What I think would be ok for this  method is to return an error if something went wrong with the request itself and then return the status code to later inspect it because it's not a request (socket) error having a 500+ or 400+. I think because most expect 200 is not a valid point to include "valid" status code in a general "request" error

@LK4D4 Hmm then let's pass sockRequest (or whoever check == 200) the status(es) we expect as a function parameter.
@runcom anything status >= 400 means an error unless we are intentionally inducing the error (by doing some faulty operation and expecting it to fail with some status code). my suggestion above solves that problem.

@ahmetalpbalkan 400 is not a socket error (I think) 400 is a successfull request and server replied 400

if the method is sockRequest I expect to get an error only on connection timeout for instance, not on 400+.. 400+ errors for example can even carry a body to be later inspected

Yeah, I don't like that func too. Doing too much.

@runcom aware. what I'm saying is, for convenience those methods are programmed to evaluate semantics of status code because most docker calls return 200 OK. but for sanity, we must change and specify expected set of status codes in each call to sockRequest IMO.

@ahmetalpbalkan could be but isn't simpler to just return it and the caller will check it? I mean, as @LK4D4 this function is doing to many things, let's put the check outside that function. Otherwise it will be called sockRequestAndCheckStatusCode lol

I don't get the relation with doing a "sockRequest" and checking its status code (from the request). I still assume the caller should do the check for more control

@ahmetalpbalkan @runcom @LK4D4 Are we in agreement to remove the 200 check from sockRequestRaw and do the status check from the test then?

I think doing the check in the test will reduce duplication. Why don't we pass valid status codes to sockRequest and let it do the check and raise the error.
Otherwise you will say t.Fatalf("unexpected status: %d") probably 362526482 times in the tests :-)
Instead if we call sockRequest(url, 200) it will return us an error if it doesnt match. Remember sockRequest is a convenience method in test package. Let it bring some convenicence :-)

@ahmetalpbalkan let's change its name then :smile_cat:

I don't see any convenience in concealing test logic somewhere apart from test. For write new test you'll need to read code of that function to understand what's going on with status argument and why we passing it. With checks in tests you can just copy-paste another test and see how we check codes.
I'm not a fan of DRY and event less fan of DRY in tests.

I am coming from a culture where DRY is not appreciated an in fact I'm told I should never go to sleep if I wrote duplicate code today :-) so I guess I'll leave it up to you folks but I can't guarantee I wont send a PR if I don't like it :P

Or with you could pass in the expected status code into sockRequest and it can check it properly.
I always always always have to do something special with this error.
Doing as above helps to remove some boiler plate from the actual tests.

still don't like a method named sockRequest that does the check for status code (even in test) but alright


Add_vector is not working always, segment geopackage is not loading onto the map

Environment Information
leafmap version: 0.29.4
Python version:
Operating System: Colab
Description
I created the segment.tif file and used this code to add the layer to basemap :
style = {
"color": "#3388ff",
"weight": 2,
"fillColor": "#7c4185",
"fillOpacity": 0.5,
}
m.add_basemap("SATELLITE")
m.add_vector(vector, layer_name="Vector", style=style)
m
But the output is not as expected

The segmentation is fine since I tried plotting the segmented image as jpeg. The issue is with the add_vector function it seems.

Please share the vector dataset that can reproduce the issue.


new release is long overdue

Is there anything I can do to nudge that along?

I think, you should release it under some short unique memorable name, something like stronglog.
It'll be a good idea to rename github repo, too. In this case all links from deprecated npm packages will lead ti the new repo with new name.

https://github.com/sam-github/modern-syslog/pull/1

@sam-github I was talking about renaming existing repo, not creating a new one. The main reason to rename current repo is because GitHub will add automatic redirects for all old links with the old repo name to the new one. It'll also keep the history of all previous commits, which could be useful.
Though, if you're going to re-implement node-syslog from the scratch, then you won't need commits history. And since you have access to this repo, you could always place a big deprecation warning with the link to the new one.

@schamane if you're still around, is there any chance you could publish a new version on npm? This is a really useful package, but it currently fails to build beyond node-v0.10.

Hi, i will try to find some solution to this. Sorry...

@schamane Awesome! Thanks so much!

I just published updated package version to npm. Can someone test if it work and give me feedback here?
Thanks.

Works with node v0.10 and v0.12, AFAICT.

@schamane I suppose you can close this issue :)


User Requirements

User requirements document detailing the user stories, requirements and use cases of the project.

Document found here;
https://docs.google.com/document/d/11U3w3X5sKWh6GSgvoXtoYfABS3U25xZgVC8wKHLIivE/edit#


Document libraries that adopted cuda_array_interface

As discussed on Gitter (starting here) and encouraged by @seibert, it'd be nice to document libraries that adopt __cuda_array_interface__ on Numba's __cuda_array_interface__ webpage: http://numba.pydata.org/numba-doc/latest/cuda/cuda_array_interface.html. This serves not only as a showcase of a great community effort toward the interoperability of GPU libraries, but also as a successful model for how different groups of library developers and maintainers can work together.
Currently, the list I have at hand is

Numba
CuPy
PyTorch
PyArrow
cuDF
cuML
mpi4py
ArrayViews

Known planned/proposed efforts:

tensorflow (tensorflow/tensorflow#29039)

I'll make a PR later this week. One question for the PR: should I hyperlink to the 3rd party library's GitHub repo, to the actual documentation that introduces this support, or to the landing page of the official website?
In the meanwhile please feel free to add items to the list. I am sure I must have left out some.
cc: @mrocklin

I think that this would be a great doc to have.  Thank you for proposing it @leofang

My preference for the linkage would be first to the project doc page describing the extent of __cuda_array_interface__ support, if it exists, otherwise link to the project home page.


Set explicit HTTP Accept header to avoid text/html

By default, java.net.HttpURLConnection HTTP Accept header is set to text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
This leads to Microsoft servers responding with a 203 status code and an HTML pages when uploading or downloading artifacts to Azure Artifacts.
Given that Maven also have a similar issue (text/html as the preferred response content-type), Microsoft has implemented a workaround that ignores the Accept header values when User-Agent is Apache Maven/*. However, this workaround is not implemented on their side for SBT.
This pull request sets HTTP Accept header to application/octet-stream, application/json, application/xml, */* to fix this behavior, as evidenced here:
https://dev.azure.com/aironek/sbt-test/_build/results?buildId=43&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=b60649db-91ed-45ce-b0dd-c9633ee87772
Given that the last component is */*, this shoud be backward-compatible with other serivces (Nexus, Artifactory, etc) that reply with different content-types.

see sbt/sbt#5483

This leads to Microsoft servers responding with a 203 status code and an HTML pages when uploading or downloading artifacts to Azure Artifacts.

Does that mean it fixes https://github.com/sbt/sbt/issues/5492 too, @3rwww1?

@dwijnand Ever got a response to your question? :)

No.  But I'm leaning towards yes, because more often than not you hear back when it's still broken... 🙂

Re: sbt/sbt#5492, the issue is mostly about being able to resolve artifacts out of Azure DevOps Maven, so maybe tweaking Ivy might help for ThisBuild / useCoursier := false case, but as a general issue it would likely need https://github.com/coursier/coursier/issues/1649.

@dwijnand unfortunately I'm still not sure, I'm still jury-rigging around the issue with ThisBuild / useCoursier := false
I'll try and test with coursier when I have some free time, I guess that all coursier need is to "set header explicitely to something other than text/html", as per MS dev team instructions. Don't know if coursier does set those headers properly though, last time I checked it seemed it didn't.


Simulator always runs in portrait mode

As per now Simulator runs in portrait mode only and is independent of device orientation but IMO for testing it should support landscape mode too.
@croozeus @opticod Am I missing something here or It's supposed to be Simulator's default behaviour?

@opticod Please share your view on this?

Definitely, you can add the landscape mode too. @yadav-rahul You can proceed


{q} truncated

Category

[x] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[ ] Completion
[ ] Vim
[ ] Neovim
[ ] Etc.

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

echo 'aaa
bbb' | fzf --bind 'change:execute(echo {q} > /tmp/l)'

and type in:
dsfdsf
/tmp/l  will not contain same string. It somehow truncates {q}. Results may vary depending if typed text matches or not item in list
Anyway, very, very nice SW. Such a joy using it! Thanks for sharing.

Hi @henkye, I can't reproduce the issue, I'm guessing by now it has been fixed, do you still have this problem? If not could you close this issue?

Hi, yes, it's OK now. My fzf version: 0.20.0
Thanks.


fix: fix possible invalid retry variables

fix: #511

I have no idea how this code works, let's talk tomorrow :)

Okay now I see how it works, thank you!


[Design] Navbar errors

The icon set is not precise. (Seems like they are emoji)
Proper padding and margin needed
Again maintain the font-family & font-weight of the the buttons etc

Thanks for raising this issue too - Didn't have a thought of this that emojis are relative to the device, They'll not be consistent in all the devices.


Added comptability method to replace old set_id_namespace

Signed-off-by: Luigi Mori<EMAIL_ADDRESS>

Fixes #281


Allow safe sql values to avoid dangerous query method error

json columns require Arel.sql safe specified strings for querying. The mapping of provided columns to strings via to_s was overwriting this specification and so it will always raise an ActiveRecord::UnknownAttributeReference: Dangerous query method error
This honors given column strings/arel safe strings

Thanks for contributing! ❤ I am going to make a small change to the gem and will release a new version.


Issue 137 related docs

updated related cards descriptions to only include first 160 characters
Fix #137
Test URLs:

Before: https://main--merative2--hlxsites.hlx.page/documents/brief/7-strategies-to-optimize-health-plan-performance
After: https://issue-137-related-docs--merative2--hlxsites.hlx.page/documents/brief/7-strategies-to-optimize-health-plan-performance

wrong repo


BaseReporter.js error thrown when test is not successful

/Users/xxxxx/dev/xxxxx/node_modules/webdriverio/build/lib/utils/BaseReporter.js:336
                        throw _iteratorError;
                        ^

TypeError: Cannot read property 'trim' of undefined
    at getTestStatus (/Users/xxxxx/dev/xxxxx/node_modules/wdio-allure-reporter/build/utils.js:31:41)
    at AllureReporter.testFail (/Users/xxxxx/dev/xxxxx/node_modules/wdio-allure-reporter/build/reporter.js:175:51)
    at emitOne (events.js:116:13)
    at AllureReporter.emit (events.js:211:7)
    at BaseReporter.handleEvent (/Users/xxxxx/dev/xxxxx/node_modules/webdriverio/build/lib/utils/BaseReporter.js:324:35)
    at Launcher.messageHandler (/Users/xxxxx/dev/xxxxx/node_modules/webdriverio/build/lib/launcher.js:688:28)
    at emitTwo (events.js:126:13)
    at ChildProcess.emit (events.js:214:7)
    at emit (internal/child_process.js:762:12)
    at _combinedTickCallback (internal/process/next_tick.js:142:11)
    at process._tickDomainCallback (internal/process/next_tick.js:219:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>devsk: `npm run removeReports && wdio test/config/env/dev/opCo/sk/devSK.conf.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>devsk script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/xxxxx/.npm/_logs/2018-10-09T09_13_50_399Z-debug.log
➜  xxxxx git:(develop) ✗ events.js:183
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: channel closed
    at process.target.send (internal/child_process.js:578:16)
    at CucumberReporter.send (/Users/xxxxx/dev/xxxxx/node_modules/wdio-cucumber-framework/build/reporter.js:284:28)
    at CucumberReporter.emit (/Users/xxxxx/dev/xxxxx/node_modules/wdio-cucumber-framework/build/reporter.js:279:18)
    at CucumberReporter.handleStepResultEvent (/Users/xxxxx/dev/xxxxx/node_modules/wdio-cucumber-framework/build/reporter.js:221:18)
    at Object.hear (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/listener.js:6:9)
    at iterator (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/runtime/ast_tree_walker.js:176:20)
    at iterate (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/util/async_for_each.js:7:7)
    at Object.asyncForEach (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/util/async_for_each.js:15:3)
    at broadcastToListeners (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/runtime/ast_tree_walker.js:178:23)
    at Object.broadcastEvent (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/runtime/ast_tree_walker.js:186:7)
    at Object.visitStepResult (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/runtime/ast_tree_walker.js:144:12)
    at /Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/runtime/ast_tree_walker.js:264:14
    at finish (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/support_code/step_definition.js:92:9)
    at process.finish (/Users/xxxxx/dev/xxxxx/node_modules/cucumber/lib/cucumber/util/run.js:13:5)
    at emitOne (events.js:116:13)
    at process.emit (events.js:211:7)
    at process._fatalException (bootstrap_node.js:391:26)

Time to time I am keep getting above written error. It seems to be related to the wdio-allure-reporter and I am using below written versions:
  "dependencies": {
    "babel-preset-es2015": "6.3.13",
    "babel-preset-stage-0": "^6.3.13",
    "babel-register": "^6.3.13",
    "browserstack-local": "^1.3.4",
    "chai": "3.5.0",
    "chai-as-promised": "5.3.0",
    "commander": "^2.15.1",
    "cucumber": "^0.10.4",
    "deepmerge": "^2.1.1",
    "fibers": "^2.0.2",
    "googleapis": "^30.0.0",
    "interval-promise": "^1.2.0",
    "jsonpath": "^1.0.0",
    "moment": "^2.22.2",
    "node-html-parser": "^1.1.10",
    "node-uuid": "^1.4.7",
    "request": "^2.87.0",
    "request-promise": "^4.2.2",
    "wait-until": "0.0.2",
    "wdio-cucumber-framework": "0.1.0",
    "wdio-dot-reporter": "0.0.5",
    "wdio-sauce-service": "^0.4.10",
    "wdio-screenshots-cleanup-service": "0.0.7",
    "webdriverio": "4.12.0"
  },
  "devDependencies": {
    "allure-commandline": "^1.5.0",
    "base64url": "^3.0.0",
    "eslint": "^5.6.0",
    "eslint-plugin-react": "^3.16.1",
    "selenium-standalone": "^6.14.0",
    "wdio-allure-reporter": "^0.6.3",
    "wdio-browserstack-service": "^0.1.16",
    "wdio-json-reporter": "^0.3.1",
    "wdio-junit-reporter": "0.0.2",
    "wdio-phantomjs-service": "^0.2.2",
    "wdio-selenium-standalone-service": "0.0.10",
    "wdio-spec-reporter": "^0.1.4",
    "winston": "^2.4.2"
  }

@ckurban is it stable?
Also
"wdio-cucumber-framework": "0.1.0" can you update to at least 1.1.1 ?

@BorisOsipov it is not stable. Upgrading might be tricky as it might/will change the structure of the Step Definitions which means I would need to apply major refactoring on all my scenarios but i will have it a go and see whats the outcome.

@ckurban Any updates on this? have you fixed problem?

Hey @BorisOsipov I see this now all the time so yes it is stable now :) Can we re-open the ticket ?

I don't think it makes sense. It won't be fixed anyway. Solution for you is update to at least 1.x wdio-cucumber-framework version