Build package error on Windows: ENOENT: no such file or directory

Issue
Cannot build plugins on Windows (10), as the build script fails with the following error message:
PS C:\Dev\_playground\plugin-workspace-test> npm start

><EMAIL_ADDRESS>start C:\Dev\_playground\plugin-workspace-test
> nps

nps is executing `default` : nps-i
? NativeScript Plugins ~ made with ❤  Choose a command to start... @testing.some-plugin.build      @testing/some-plugin: Build
nps is executing<EMAIL_ADDRESS>: nx run some-plugin:build.all

> nx run some-plugin:build.all

> nx run some-plugin:build
ENOENT: no such file or directory, open 'C:\Dev\_playground\plugin-workspace-test\packages\package.json'
The script called<EMAIL_ADDRESS>which runs "nx run some-plugin:build.all" failed with exit code 1 https://github.com/sezna/nps/blob/master/other/ERRORS_AND_WARNINGS.md#failed-with-exit-code
(node:4684) UnhandledPromiseRejectionWarning: Error: spawn nps @testing.some-plugin.build ENOENT
    at notFoundError (C:\Dev\_playground\plugin-workspace-test\node_modules\@nstudio\nps-i\node_modules\cross-spawn\lib\enoent.js:6:26)
    at verifyENOENT (C:\Dev\_playground\plugin-workspace-test\node_modules\@nstudio\nps-i\node_modules\cross-spawn\lib\enoent.js:40:16)
    at ChildProcess.cp.emit (C:\Dev\_playground\plugin-workspace-test\node_modules\@nstudio\nps-i\node_modules\cross-spawn\lib\enoent.js:27:25)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
(node:4684) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:4684) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I also tried that on macOS, where it works like a charm.
Reproduction

Download a zip of this repo
Unzip and name the folder appropriately (perhaps the name of the npm scope you intend to manage here)
Setup workspace: npm run setup
Configure your npm scope: npm run config
Add a plugin package: npm run add
Execute build command: npm start -> select<EMAIL_ADDRESS>

@cvietor I have the same problem. Did you consider using WSL2 with a Ubuntu Distro? That works for me.

@hrueger I tried that but also with no success. i did some more tests and realized now that if i started with powershell and then try to build a package with ubuntu@wsl2, it does not work. But when i download a fresh copy and repeat all steps in ubuntu, it works, so i suspect a path seperator problem in a schematic or shell script, but could not spot any in a quick glance.
Too bad that ubuntu@wsl2 is unbearingly slow (aka not usable) on my machine.

@cvietor weird. Are you using the VSCode remote thing for WSL2? This is slow for me. But if I just navigate to /mnt/c/source/... in an ubuntu terminal and run the command there, it works and is quite fast.

nope, just using it in windows terminal. i suspect my companies anti-virus software or something like that. but nevermind, that's my workstations's problem :-)

@cvietor I posted a PR to @hrueger 's plugin workspace with what I believe fixes the build.all issue on windows. This is the changeset:
https://github.com/SchoolSquirrel/nativescript-plugins/pull/47/files
Could you try @cvietor when get a chance just modifying your tools/scripts/build-finish.ts file in your workspace as seen in that PR? If that works for you as well I'll add a migration to 1.0.7 of plugin-tools which will auto update that file for others.

thanks @NathanWalker, that does not work unfortunatly. should have mentioned that i already tried that.
the bug seems to be before the build-finish script (a simple console.log at line 18 in build-finish.ts is also not printed)
I'm willing to help, could you provide a little hint on where to look for the build scripts? i.e.
nx run some-plugin:build.all <- i'm struggling to find that build.all script

workspace.json is heart of every workspace. the build.all, using that repo as example, is located here:
https://github.com/SchoolSquirrel/nativescript-plugins/blob/main/workspace.json#L115
There's a build.all target for every plugin in workspace. The purpose is to ensure that the standard build is executed in addition to any other custom (for example angular) build tooling is executed afterwards.

I'm not familiar with Windows nowadays, honestly haven't used Windows in 15+ years at least (and don't have one anywhere around me), but would love your assistance in getting Windows working - My best guess is a path handler somewhere?

Yes, i was wondering what exactly is being executed in that nx run :build.all
I'm not that familiar with nx, so i will do some reading there.
I just found the part which is causing the problem, but i don't have a solution yet.
If i change to "root" property in the workspace from:
"some-plugin": { 			"root": "packages/some-plugin", 			"sourceRoot": "packages/some-plugin",
to
"some-plugin": { 			"root": "packages\\some-plugin", 			"sourceRoot": "packages/some-plugin",
it works

Interesting - there was a pr back in May to Nx for something similar to that:
https://github.com/nrwl/nx/pull/2941

Reverting to plugin-tools 1.0.5 allows the build to run for me.

@NathanWalker it actually is exactly that mentioned problem.
in this scenario, the "all" project's root value in the workspace.json is causing this behaviour to fail on windows.
{
	"version": 1,
	"projects": {
		"demo": { ... },
		"demo-angular": { ... },
		"all": {
			"root": "packages", <----------- this here
			"projectType": "library",
			"architect": { ...

now when nx is building up the project graph and is trying to sort out the dependencies with that (in nrwl/nx#2941 mentioned) method:
  private findProjectOfResolvedModule(resolvedModule: string) {
    const importedProject = this.sortedWorkspaceProjects.find((p) => {
      return resolvedModule.startsWith(p.data.root);
    });

    return importedProject?.name;
  }

my index.android.ts is importing './common.ts', so "resolvedModule" is
packages\some-plugin\common
but that p.data.root is actually
packages/some-plugin
BUT "all" has a p.data.root of
packages
so "all" is returned as an imported project and for that reason ends up in the dependency graph of "some-plugin".
as a result of that, treated as a dependency, if will look for "/packages/packages.json".
changing
{
		"all": {
			"root": "packages", <----------- this here

to
{
		"all": {
			"root": "packages/"

prevents that, but does feel like a hack with unforseen side effects.
still not quite sure what a good solution this should look like

@cvietor interesting find - Have you found that adding a slack to end of packages 100% fixes it on Windows though?
If so I'll make sure no side effect on Mac (don't believe there would be) and we'll update tooling to ensure a slack is always ending there.

yes, that fixes it, as that resolvedModule.startsWith(p.data.root) evaluates to false then on the "all" project (which is good as "all" does not end up in the dependency graph).
the greater question is: "all" is only falsely picked as a dependency from the workspace projects because the actual projects data.root has forward instead of backward slashes, so the filter expression of the find method will never pick the right dependency. now the real question: could that cause issues? if the found project is the same as the resolvedModule, it gets filtered out anyway later on. and a nativescript plugin "package" should not reference another "package" directly.
i did a projectGraph comparison with and without the mentioned /:
windows:

without / -> "all" ends up in dependencies
with / -> no "all" in dependencies

ubuntu@wsl2:

without / -> no "all" in dependencies
with / -> no "all" in dependencies

so at least on linux side, that change does not cause any side effects. it's all quite complicated for a missing slash :-)

Ha for sure. Thank you for help on this, I'll update tooling to ensure an ending slash is there and confirmed Mac is good with that as well so this should be good on Windows, Linux and Mac 👍  Will post back once update is out to resolve this.

Works for me, too. Thank's @NathanWalker and @cvietor!


Adding WeMo/fauxmoesp - Alexa support?

Would it be possible to add support for WeMo via for example fauxmoesp to the demo? This to have it interact with the HomeKit portion as well. If so this code base/example would make the perfect universal device/switch since it would have both HomeKit and Alexa support all rolled into one simple solution.
Fauxmoesp
https://bitbucket.org/xoseperez/fauxmoesp

I very much suspect that this will not merge. The fauxmoesp is Arduino based.
However, if you have a C based source (based on freeRTOS if it has scheduling dependencies), then merging should not be too difficult.
If you found such a source, please indicate where it would be interacted with so we can see how it interacts with the Homekit API


add makefile

Fix xplorfin/go-template#3

Coverage remained the same at 92.683% when pulling d0872a85420c9cab184e1ec9c9a712f5f3c1d5a0 on makefile into a189d2103a04c7b828f2966d903d866fea377891 on master.


Add support for latest Python releases

Add support in CI for latest supported Python versions 3.6, 3.7, and 3.8.

Coverage remained the same at 81.067% when pulling 2cfe65700066030578f7fbc4f90176a0fb26a688 on johnthagen:patch-1 into 2601ae8eab8d7be807bdbed264cd943e441a8da0 on curtacircuitos:master.

Python 3.7+ failure:
ERROR: Test file type detection
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon_statements.py", line 978, in pairwise
    yield tuple([next(itr) for i in range(2)])
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon_statements.py", line 978, in <listcomp>
    yield tuple([next(itr) for i in range(2)])
StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/nose/case.py", line 198, in runTest
    self.test(*self.arg)
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/tests/test_excellon.py", line 23, in test_format_detection
    settings = detect_excellon_format(data)
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon.py", line 826, in detect_excellon_format
    p.parse_raw(data)
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon.py", line 435, in parse_raw
    self._parse_line(line.strip())
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon.py", line 639, in _parse_line
    tool = ExcellonTool.from_excellon(line, self._settings(), None, self.plated)
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon_statements.py", line 155, in from_excellon
    commands = [(command, value) for command, value in pairwise(commands)]
  File "/home/travis/build/curtacircuitos/pcb-tools/gerber/excellon_statements.py", line 155, in <listcomp>
    commands = [(command, value) for command, value in pairwise(commands)]
RuntimeError: generator raised StopIteration

Perhaps fixed by #104?

Hello,

Perhaps fixed by #104?
Yes.

However, I am not sure if this package is still maintained.

Hi @MarinMikael, I left pcb-tools for a while but I am back maintaining it. Will take a look at it now.

Merged #104 but tests still fail for 3.8, looks related to coverage package version. Think we should split this in two, first get 3.7 in and later update packages and tests for 3.8, what do you think?

Hello,
Welcome back. :D
pcb-tools uses coverage 3.7.1, which was released in 2013. This specific line was removed, upgrading the package's version in test-requirements.txt should be enough, if it doesn't break anything else.

I confirm that #104 merged with #105 and modifying coverage to 4.5.4 passes the Travis CI test in my master branch.

I've upgrade the dependencies, CI passing now. Will merge. Thanks @MarinMikael and @johnthagen .


Added description to the commit error

The Error object created by node-rdkafka is not being rendered correctly by logger, so call toString to add description explicitly.
Bug: https://phabricator.wikimedia.org/T148820

I don't think that adding a stack property would be useful here, because the errors are generated in native code in kafka bindings, so wouldn't have much value for us.

Coverage remained the same at 93.196% when pulling cd8c923f25f7d11aff4eee6ac4371cfc6ee6b5af on Pchelolo:error_description into 1ff4e2ae9cb0be331b2f8b2adc83eb58e3c5d0e4 on wikimedia:master.


[Checklist] Clarify Mnnnn or Snnnn are unique

Per discussion with @fearthecowboy and others, "nnnn" alone will not be unique but "Mnnnn" or "Snnnn" will be unique.
Also formats that paragraph with one sentence per line for readability.
Signed-off-by: Rob Dolin<EMAIL_ADDRESS>This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[ ] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

@RobDolinMS,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Thanks for submitting this. I will review this and get back to you shortly

No modification for Python

No modification for Ruby

No modification for NodeJS


DANG-155: Add Storybook (+ global CSS + Card story)

JIRA

https://lobsters.atlassian.net/browse/DANG-155

Description

Adding Storybook. Also, added global CSS (font, typography & color variables) and a story for the Card component.

Screenshots
Component view:

Documentation view:

Areas of Concern

There's some fun behavior where navigating to the docs tab of any component auto-scrolls you to the bottom of the page. There's a workaround out there, but it doesn't work for Vue.

Reviewer Checklist
Testing
How to test:

pull down branch, npm install, npm run storybook
Click into Components/Card, put some words in the box, marvel at it

[ ] This code was tested by somebody other than the developer. Do not merge until this has been done.

Going to merge this for now, if the package-lock.json thing becomes an issue, will revise from there.


cannot install opensim-core

Hi, I encounter the following problem when installing opensim-core. Can you please advise?
85% tests passed, 13 tests failed out of 85
Total Test time (real) = 941.27 sec
The following tests FAILED:
6 - testComponentInterface (Failed)
9 - testSTOFileAdapter (OTHER_FAULT)
13 - testMarkerData (OTHER_FAULT)
44 - exampleHopperDevice (Failed)
45 - exampleHopperDeviceAnswers (Failed)
49 - testControllerExample (Failed)
51 - testExampleMain (OTHER_FAULT)
53 - testOptimizationExample (OTHER_FAULT)
55 - testCustomActuatorExample (OTHER_FAULT)
57 - testMuscleExample (OTHER_FAULT)
83 - testCommandLineInterface (Not Run)
84 - python_tests (Failed)
85 - python_examples (Failed)
Errors while running CTest
During the installation there are 2 errors:
Copying _simulation library to python package in build directory.
[ 94%] Built target _simulation
make: *** [all] Error 2
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [opensim-cmd] Error 1
make[1]: *** [Applications/opensim-cmd/CMakeFiles/opensim-cmd.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
Thanks

I managed to make it work by upgrade to gcc 4.9. Cheers


bullets missing from html

https://pub.beakernotebook.com/#/publications/560ad479-2640-44a4-9d42-be8a7ca6a383

should be fixed by: https://github.com/twosigma/bunsen/pull/1200
(couldn't test it with that specific notebook because it's no longer available)

not working

@ildipo  can you give an example where it's not working? Thanks.

https://pub.beakernotebook.com/#/publications/560b4726-ce94-4e2a-820a-8c828094e309?fullscreen=false
The list of demos and examples should have bullet points

In that particular example the issue is that those lists have incorrect syntax in the notebook source file, they both are missing parent <ul> or  <ol> elements. In my recent fix I changed list bullet styling in Publications to the default value, same as it is in Beaker: https://github.com/twosigma/bunsen/commit/7a1142309a96bf8aca12c5321e8077b95cfa1c37
but I won't be able to use the same fix here because you can't style bullet points just for <li> elements.
Would fixing  html in the notebook source file be an option?

yea give me a sec

actually if i do that then the indentation in the HTML cell goes wrong.
so I think we should take this fix, and fix  in Beaker.

This has been deployed


Users can view workshops through lecture-hall

I haven't been keeping track of how my commits have been aligning with the issues for Lecture Hall, but this is closed as of 82767a88fb374fee59b1b685fe9fa19afc60b9d3.


Adding Rails app to test folder / docker-compose to use activestorage gem as implementation to verify against

Also some other changes to start getting the tests working
I made this PR from my fork because that's where I started the work.  In the future I'll work in your repo.
Wanted to stop here briefly and verify the state of things before moving on.  I see that there isn't a schema for the attachments, but I can add that.  👍 ?  Also I would say we change the table names for the schemas:
storage_blob => active_storage_blobs
storage_variant_records => active_storage_variant_records
That way the tests can run against the same tables as what's being created in the Rails app.
Seem OK?  Any other thoughts / questions?

looks good to me 👍

indeed, there is no schema for attachment

I will merge this now and I will commit the latest changes on another PR

👍  I'll pick this up again tomorrow night, thanks!


Make properties in BaseRequestBuilder public

These properties are now marked as protected by making them public you could easily extend the requestbuilder using extension methods.
https://github.com/microsoft/kiota-abstractions-dotnet/blob/d6d836a90fb81fa894eee5d89660d8145a2e5029/src/BaseRequestBuilder.cs#L16-L20
Background
The new Graph SDK for .NET (even the beta version), does not contain all the endpoints available. By extending the request builder we could easily implement those additional endpoints and have the same experience. No we cannot use the PathParameters or the RequestAdapter even though these are available from other classes.

Thanks for reaching out.
Solving any gap using extension methods is something we refrain from as it will only work in dotnet.
We'd rather fix the metadata or conversion process so it benefits every language.
Can you open issues against the SDK repository to pinpoint what's missing please?

I fully understand, the SDKs should be better. Will do that as well, but it was just background.
I don’t see why those Properties have to be protected. It would also help if you just want to try something out. Is there some architectural decision behind that? Seems like a small change that allows extensibility.
we are planning to also use kiota for our own projects, and we would like extensibility.

Can you provide specific scenarios that having access to these properties would allow you to build? Without using extension methods.

I'm thinking of extensions. So you have this basic api, and build some additional features. Then you can ship those additional features to some beta testers as a nuget with extension methods.
The Graph API currently has two packages, one for v1.0and one forbeta, if you where to allows extensions, you could have 1 package for the v1.0` and a package with the extensions that are currently in beta. If the developer then wants to migrate to the production version of the api he would not have to change the namespace of all elements.
Installing a newer version for the v1.0 api would then be a breeze, just a package upgrade, where you remove extensions from the beta package and add them to the regular package.

Thanks for sharing. The other aspect to making those properties public is they will start showing up with the auto-completion on the fluent API surface e.g.:
client.Me.Messages.UrlTemplate

which will be distracting to most users.
For that reason (and the extensibility pattern only being available in CSharp), we're not planning to change the access to those properties.

I did not think of this, you're right. How about making all the request builders partial. That would enable extensibility without showing all those "not to be used by regular users" properties to users.

This solution would be limited to CSharp and TypeScript as far as I can tell. We've already had a long conversation about extensibility here during the early days of Kiota and couldn't come to a conclusion that'd be satisfactory to most languages.

Hi @baywet I was not talking about all languages. I was talking about C#. You could allow a situation where some languages would support extending the api and some languages won't (like Java so it seems).
In javascript/TypeScript you are able to access private properties if you ignore the boundries (like described here.
Let me revert the question, what is against making all the requestbuilders generated by Kiota partial for C#? This would allow the needed extensibility for C# since the language supports it. And maybe other developers like it so much that you guys decide to enable similar functionality in other languages (that support either partials or extension methods) as well.

@MartinM85 This was not only created for the missing metadata. It was created to allow extending the request builders for all apps generated by Kiota.

Let's leave the gap in the metadata outside of this conversion so we can focus on the extensibility aspect if you don't mind. I've provided a quick reply on the original metadata issue, and it'll be addressed in due time, without needing extensibility itself.
As per the last comment on the partial aspect. On a technical standpoint, I don't have a strong opposition to make things partial in C#. On a product management aspect, I'm more concerned however. This is because we might back ourselves into a corner:

We make things partial in dotnet,
People build all kind of extensibility over that.
Now people want to port those extensions to Java, and it's not possible.
We'd need to either tell them "go complain to the core language team" or "not possible" both stances make for a really poor experience.

This is why I was suggesting you engage on the thread I linked originally.

We'd need to either tell them "go complain to the core language team" or "not possible" both stances make for a really poor experience.

Or give it a positive turn:
Language specific additional features ⭐
Clients generated by Kiota also have some specific features that don't work on all platforms, because either that language does not support it or we did not implemented it in that language, and we are accepting pr's.

Feature
C#
TypeScript
Java
...

Request Builder extensibility
✅ through partials
✅ by extending the class
❌ core language
...

Again, all valid points, please bring those on the issue I linked.
Closing since we're not doing that work for now until a decision on extensibility has been reached.


Issue 105

Hey @tapthaker
We really need to improve here. We're missing a lot of content from #372, and today is publish day.
I think we really need to focus on getting the first half of a draft finished during the first week of the writing cycle. It will help reduce a lot of the stress.

I understand. Give me a few hours to get last few content out. Will ensure that the last minute tension doesn’t happen again.

I'll add some content in the meantime @tapthaker. :)

@BasThomas : I am starting to work on it as well. How do we distribute ?

Ah sorry - I just pushed some changes. Have a look @tapthaker.

@BasThomas : Looks good to me. You are fast !!

Thanks @tapthaker!

No, thank you @BasThomas & @jessesquires for coming in at the last moment and pushing fixes !!

Thanks all! 💯


Birthday Card Using HTML,CSS

Describe the project
A clear and concise description of the project you are going to add to this repository.
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[ ] New Project

Additional context
Add any other context or screenshots about the project here.
Screenshots

If applicable, add screenshots to help explain your problem.

Attach a reference image for your project

Okay di

@TusharKesarwani Can we use Bootstrap ?

@TusharKesarwani Can we use Bootstrap ?

Yes


SAQ Web

Hello,
at the current state the web ui web_enabled=True, is not functioning (or at least the same as saq).
There are two issues.

The http://<IP_ADDRESS>:8000/saq/queues/default does not show the jobs. In order to do so we need to do the following change,

https://github.com/cofin/litestar-saq/blob/main/litestar_saq/controllers.py#L68
-          return {"queue": await queue.info()}
+          return {"queue": await queue.info(jobs=True)}

The respective code in saq is https://github.com/tobymao/saq/blob/f7c5d9d9f4772b9db741a7507a2843e1134dd5a7/saq/web/starlette.py#L67

The job info api does not work.

https://github.com/cofin/litestar-saq/blob/main/litestar_saq/controllers.py#L18
-    job = await queue._get_job_by_id(job_id)  # noqa: SLF001
+    job = await queue.job(job_id)  # noqa: SLF001

The respective code in saq is https://github.com/tobymao/saq/blob/f7c5d9d9f4772b9db741a7507a2843e1134dd5a7/saq/web/starlette.py#L109
Thank you and best wishes
P.S. There is also the issue that http://<IP_ADDRESS>:8000/saq does not work and needs to be http://<IP_ADDRESS>:8000/saq/ or in opposite manner http://<IP_ADDRESS>:8000/saq/queues/default works but http://<IP_ADDRESS>:8000/saq/queues/default/ does not, but that's upstream issue with the way routes regex is constructed.

This fixes the issues mentioned with the job info.  I'll investigate the route issues shortly as well.


Getting weird crashes PFObjectSubclassingController.m

1644 crashes with only 5 users
PFObjectSubclassingController.m line 355
http://crashes.to/s/d1678763779
anyone know how to solve this?

Same here. My app was sent to a beta review a few hours ago:
http://crashes.to/s/dc1ff26327c
I'm rocking iOS SDK v1.14.1.

Same here. Crash when starting the app in the debugger.
PFObjectSubclassingController.m:
char potentialPaths[2][PATH_MAX] = { };

strncpy(potentialPaths[0], bundle.executablePath.UTF8String, PATH_MAX); // crash
realpath(potentialPaths[0], potentialPaths[1]);

bundle.executablePath is nil and thus causing the crash.
The offending bundle is /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/lib.

Why not just use the NSLoadedClasses notification key for a list of all classes instead of examining the executable image? Seems unnecessarily complicated.

I submitted recently an the app to review with 1.14.1, and I got 361 crashes in one device 😨 (apparently they are running the app in some devices before it enters in review):
http://crashes.to/s/e334c371112

We've fixed the issue for us in https://github.com/Widgetlabs/Parse-SDK-iOS-OSX/commit/aaa0632235b0896f5738a234e89a4a377d7eb68c.
You can use it in your Podfile like so:
# https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/980
pod 'Parse', :git => 'https://github.com/Widgetlabs/Parse-SDK-iOS-OSX.git', :branch => 'patch-1'

But I'd recommend to either fork our fix or use Parse SDK 1.13.0 which is not affected by this bug.

Thank you! @fluidsonic

@fluidsonic This worked for me. My code was crashing anytime I initialized an object in the AVFoundation framework, e.g. [[AVSpeechSynthesizer alloc] init]. I traced it back to this code but was wary of changing it. Thanks!

This is getting merged in a few moments and release is coming soon.
Thank you everyone for the input and thank you @fluidsonic for a fast fix!

@nlutsenko thats what I was talking about in https://github.com/ParsePlatform/Parse-SDK-iOS-OSX/issues/975


Added Privacy Policy page

Description
Privacy Policy page has been made and added. @Mr-Sunglasses @akshatcoder-hash Please suggest any changes if required. Also, the issue #122 assigned to @tanishkkkaa can now be completed by linking the 'privacy policy' text on the homepage to the required site.
Fixes # (issue)
Added Privacy Policy page (https://fosscu.org/privacypolicy)

[:heavy_check_mark:] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[:heavy_check_mark:] yarn start

Checklist:

[:heavy_check_mark:] My code follows the style guidelines of this project
[:heavy_check_mark:] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[:heavy_check_mark:] My changes generate no new warnings

The preview can be seen on https://deploy-preview-190--fossc.netlify.app/privacypolicy.

Please add the route to the privacy policy page.

done :+1: ! @Mr-Sunglasses please review it!

Thanks 🙏 @hiCXK

Thank you very much!😁❤


Switch to SVG badges

We made them nice and crispy. http://shields.io/
:-)
Before

After

Thank you ❤


ds1.

VSCode Version:
OS Version:

Steps to Reproduce:

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

/needsMoreInfo


[MM-37054] Refactored trial subscription test scripts for system console

Summary
Refactored Test script for trial subscription functionalities
Ticket Link
https://mattermost.atlassian.net/browse/MM-37054

Release Note
NONE

Hello @vinod-demansol,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has to merged after PR - 8792


Should be able to patch nodes created inside an iframe.

Added a failing test case and the change to fix it. For #64.

Really nice! Thumbs up for adding a test case as well :smile:
I will merge an do a release.


Object Fields missing

Fields Properties Missing from Schema when they are more than one "object" fields.
E.g. Schema model for  data class Between(val from: C, val to: C) is incorrect.
from is ignored due to the way ModelResolver.java works out if it can use the same property as before or not.
This issue is in the use of "cloning" (rather than using standard immutable object pattern)
ModelResolver.java
if (!"object".equals(property.getType()) || (property instanceof MapSchema)) {
   try {
    String cloneName = property.getName();
    property = Json.mapper().readValue(Json.pretty(property), Schema.class);
    property.setName(cloneName);
  } catch (IOException e) {
       LOGGER.error("Could not clone property, e");
   }
 }

Example failing kotlin test:
  @Test
  fun `should model both parameters for Between`() {
    val models = ModelConverters().readAll(Between::class.java)
    val properties = models["Between"]?.properties
    assertThat(properties?.size, equalTo(2))
  }
  data class Between<C>(val from: C, val to: C)

Thanks for reporting this and for the PR! fixed in #3351 (includes and replaced #3349)


[1.18] Adding direction to look at when spawning in config

Describe your idea
As I'm making a skyblock modpack with multiple templates, I faced one problem:
I always look in a direction i don't want to. So i thought, as we can set spawnpoints in config, it could also be worth adding the direction where you should look, when you first spawn. (cause i don't do 360s every time I play a modpack)

Is this what you’re looking for? https://melanx.github.io/SkyblockBuilder/1.18.x/config/spawn/#direction
If not, I don’t fully understand exactly what you suggest.

not really. you have introduced multiple spawnpoints back in 1.16, and now with multiple templates, it's easier to move the direction from the config to the template json as you will have different spawn islands where it would be better to look at a different direction than on another island.

Okay, I'll implement that in 1.18.2 when finished porting.


Key "hashes" does not exist.

[X] I am on the latest Poetry version.
[X] I have searched the issues of this repo and believe that this is not a duplicate.
[X] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: Debian 10
Poetry version: 1.0.0b3
Link of a Gist with the contents of your pyproject.toml file:

Issue
It seems that poetry 1.0.0b3 is removing the [metadata.hashes]. So it makes is incompatible with older version of poetry i.e. 1.0.0b2 or 0.12.x for instance. Is that a bug or it was intentional?
here is the stack trace:
Step 10/12 : RUN poetry -vvv install --no-dev
 ---> Running in f2153be1029f
Creating virtualenv hello-k8s-py3.7 in /root/.cache/pypoetry/virtualenvs
Using virtualenv: /root/.cache/pypoetry/virtualenvs/hello-k8s-py3.7
Installing dependencies from lock file

[NonExistentKey]
'Key "hashes" does not exist.'

Exception trace:
 /usr/local/lib/python3.7/site-packages/cleo/application.py in run() at line 94
   status_code = self.do_run(input_, output_)
 /usr/local/lib/python3.7/site-packages/poetry/console/application.py in do_run() at line 88
   return super(Application, self).do_run(i, o)
 /usr/local/lib/python3.7/site-packages/cleo/application.py in do_run() at line 197
   status_code = command.run(input_, output_)
 /usr/local/lib/python3.7/site-packages/poetry/console/commands/command.py in run() at line 77
   return super(BaseCommand, self).run(i, o)
 /usr/local/lib/python3.7/site-packages/cleo/commands/base_command.py in run() at line 146
   status_code = self.execute(input_, output_)
 /usr/local/lib/python3.7/site-packages/cleo/commands/command.py in execute() at line 107
   return self.handle()
 /usr/local/lib/python3.7/site-packages/poetry/console/commands/install.py in handle() at line 55
   return_code = installer.run()
 /usr/local/lib/python3.7/site-packages/poetry/installation/installer.py in run() at line 73
   self._do_install(local_repo)
 /usr/local/lib/python3.7/site-packages/poetry/installation/installer.py in _do_install() at line 169
   locked_repository = self._locker.locked_repository(True)
 /usr/local/lib/python3.7/site-packages/poetry/packages/locker.py in locked_repository() at line 86
   package.hashes = lock_data["metadata"]["hashes"][info["name"]]
 /usr/local/lib/python3.7/site-packages/tomlkit/items.py in __getitem__() at line 1008
   return self._value[key]
 /usr/local/lib/python3.7/site-packages/tomlkit/container.py in __getitem__() at line 524
   raise NonExistentKey(key)

install [--no-dev] [--dry-run] [-E|--extras EXTRAS] [--develop DEVELOP]

This is a duplicate of #1510

Closing because #1510 exists.


scimPatch mutates the original object

Describe the bug
Currently, the scimPatch function mutates the original object passed in the argument. Can we change it to take a copy of the original before applying the patches?
To Reproduce
// Declare some scimResource & payload
const patchedResource = scimPatch(scimResource, payload.Operations);
console.log(patchedResource === scimResource); // true

Expected behavior
The output for the above script should be false
Additional context
Incase if we want to ensure backward compatibility, how about introducing a flag that is used to decide whether to mutate the original object or take a copy

yup, this is good, gives room for extensibility 👏


Put a "Redeploy may be needed" note on the next upgrade for Azure deployments

Context
I was testing out an upgrade (2024.7.1 -> develop) on Azure and the node groups get deleted and recreated b/c of the Rook Ceph PR, but there is a lag between when terraform thinks the node groups are destroyed and when AKS reports them as being destroyed so terraform tries to create a new "user" node group and terraform throws an error that a "user" node group already exists.  Redeploying after the failure gives enough time for AKS to delete the old "user" node group and things work fine after that.  I'm not sure if this is always an issue or just intermittently.
I'm not sure how to fix this b/c the error is on the terraform Azure provider side.  Maybe we should include a note that this might be possible when users run nebari upgrade.

Try to update Azure provider version

Fixed by https://github.com/nebari-dev/nebari/pull/2726


Anerdw: Watch (?-i:Fu2Bi)(?#shorturl.at)

Anerdw requests the watch of the watch_keyword (?-i:Fu2Bi)(?#shorturl.at). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:Fu2Bi)(?#shorturl.at) has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Fix redefinition of mmap on aarch64.

The error was
src/base/linux_syscall_support.h: In function ‘void* sys_mmap(void*, size_t, int, int, int, int64_t)’:
src/base/linux_syscall_support.h:975:28: error: redefinition of ‘void* sys_mmap(void*, size_t, int, int, int, int64_t)’
     #define LSS_NAME(name) sys_##name
                            ^
src/base/linux_syscall_support.h:2253:12: note: in expansion of macro ‘LSS_NAME’
       type LSS_NAME(name)(type1 arg1, type2 arg2, type3 arg3, type4 arg4,     \
            ^
src/base/linux_syscall_support.h:2783:16: note: in expansion of macro ‘_syscall6’
     LSS_INLINE _syscall6(void*, mmap, void*, addr, size_t, length, int, prot,
                ^
src/base/linux_syscall_support.h:975:28: note: ‘void* sys_mmap(void*, size_t, int, int, int, __off64_t)’ previously defined here
     #define LSS_NAME(name) sys_##name
                            ^
src/base/linux_syscall_support.h:2253:12: note: in expansion of macro ‘LSS_NAME’
       type LSS_NAME(name)(type1 arg1, type2 arg2, type3 arg3, type4 arg4,     \
            ^
src/base/linux_syscall_support.h:2563:16: note: in expansion of macro ‘_syscall6’
     LSS_INLINE _syscall6(void*, mmap,              void*, s,

Applied. Thanks.


Remove data redundancy in questionnaire upload format

If we move away from the CSV format to a different format, the following should be considered as pointed out by @brandelune
there is some redundancy in your data that could be eliminated. If you have a "section name" key, the "question number" can start with the alphabet part and you can remove the first digit, also, you can have a "sub question number" key that starts with 0 and uses only roman numerals. That would make the whole set easier to parse and sort.
(just using key=value here, it would work the same in JSON or anything else)
Section Name=1
Question Number=a
Sub-Question Number=0
...
Section Name=1
Question Number=b
Sub-Question Number=0
...
...
Section Name=1
Question Number=d
Sub-Question Number=0
...
Section Name=1
Question Number=d
Sub-Question Number=i
...
Section Name=1
Question Number=d
Sub-Question Number=ii
...
That would also contribute to clearly separate the 4 "blocs" you have for 1 question:
[Question ID] 3 items
Section Name (Number?)
Question Number
Sub-Question Number
[Question Contents] 2 item
Spec Reference Number
Question Text
[Answer Contents] 2 items
Answer Type
Correct Answer
[Evidence Contents] 2 items
Evidence Prompt
Evidence Validation

This is resolved in the I18N branch.  Waiting on merge to close this issue.


Text editor could have some way of getting line number

Currently there doesn't appear to be an easy way to get the line number in the text editor. This might be useful for some purposes eg for reporting bugs.

This (along with other configurations) should happen along with the release of the new editor.

I'm going to close this, since we don't refer to line numbers anymore, so they're not really needed in the editor.


ETA on MathJax v3.0

Hi,
Thanks for answering my other question about the single files. To follow up on it, I tried to find some estimated time of arrival on the release of MathJax v3.0 but the latest update was in a paper back in 2015. For a project I'm working on, we wish to use the single files of MathJax v3 as we intend to have our app work offline.
Is there an ETA on MathJax v3.0? I hope it's not taboo to ask. Thanks

General questions should be posted to the mailing lists at https://groups.google.com/forum/#!forum/mathjax-user and https://groups.google.com/forum/#!forum/mathjax-dev
There is no ETa. For those interested, we'd recommend following the discussions on the dev list or the development in the v3 repository.


Update deps + re-enable compat helper

It looks like compat helper has been disabled and now the deps are a bit behind. For example I'd like to use Static v1. @brenhinkeller Could you re-enable compat helper and run it?

Do you know how to re-enable that? There's some annoying github setting that deactivates automatically it after some time

I think you just click on actions -> Compat Helper, and then as the owner you should have a button to reactivate it. Yes I have the same issues with a few packages of mine.

Oh cool, thanks!

Can you tag a new release with 40d8df7?

Oh sure

Thanks!


Module not loading, suspect client identifier

Hi Jonas,
I'm unable to load the module despite following your instructions and Bysykkel's.
Your link to creating a new client id is no longer available, but from what I gather from Bysykkel's API, this is no longer necessary. (One can simply name the identifier oneself).
Any idea why I'm unsuccessful?

Hi Øystein,
Thank you for your bug report. There had been a few changes to the Oslo bysykkel API since I created this module, but it should be fixed now! Now you don't need the client ID for Oslo Bysykkel, and can simply configure it as Bergen for example (see docs).


SSO Login in argo-workflow failing with HTTP 400 Error with authentication through Microsoft AD (OIDC)

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[X] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
SSO Login in argo-workflow failing with HTTP 400 Error with authentication through Microsoft AD (OIDC)
Summary
We have configured SSO authentication mode with Microsoft AD as OIDC provider. Authentication through Microsoft AD is happening successfully, but while handling a callback we can see error page with HTTP 400 error.
On further investigation into code, issue found to be in below code
https://github.com/argoproj/argo-workflows/blob/aa2b66a5b7d8c3ab2af900a5fbda948b13d14085/server/auth/sso/sso.go#L230C2-L235C3
        cookie, err := r.Cookie(state)
	http.SetCookie(w, &http.Cookie{Name: state, MaxAge: 0})
	if err != nil {
		w.WriteHeader(400)
		return
	}

Here code is looking for a cookie with value of variable state and then setting a Cookie Header with value of state. Post that it is return HTTP 400 Error because cookie named with value of var state wasn't available. If Cookie not found, then while error handling it should set the cookie with name state
Configuration
sso:
      issuer: <issuer-url>
      clientId:
        name: argo-workflow-oidc-secret
        key: client-id
      clientSecret:
        name: argo-workflow-oidc-secret
        key: client-secret
      redirectUrl: http://arog-workflows.my.org.com/oauth2/callback
      rbac:
        enabled: true
      scopes:
        - groups
        - emails

I already fixed and tested the fix, and would like to contribute the fix as a PR.
Version
v3.4.7
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Not Applicable

Logs from the workflow controller
Not Applicable

Logs from in your workflow's wait container
Not Applicable

Per your comment in the PR, do you also want to close this?

I think this can be closed. Seems to be an issue with my environment. I am still trying to figure out, why cookie is not flowing after authentication at microsoft.


simutrans: Fix hash of pak128

Motivation for this change
It seems that https://github.com/NixOS/nixpkgs/commit/9b934a4b699bf2f9bc3d9584102619ff3c96a366 updated the expression for simutrans, but when nix-env -iA nixos.simutrans, it tells me:
fixed-output derivation produced path '/nix/store/b68pr406fns3b29zfnv6ihimmq6bgkmr-pak128.zip' with sha256 hash '0z01y7r0rz7q79vr17bbnkgcbjjrimphy1dwb1pgbiv4klz7j5xw' instead of the expected hash '1x6g6yfv1hvjyh3ciccly1i2k2n2b63dw694gdg4j90a543rmclg'

So I'm updating this hash here.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Outdated.


Import Documentation

Hi,
thanks for this useful plugin.
I was able to export my project without problems.
After editing one file i was using the import statement without any flags.
The console gave me this info of updating 81 files:
INFO - updated elements: 81
Is it possible to only update the one edited file. and soime kind of watcher?
Otherwise the turnaround times for template editing are to long...

So if i only want to edit Section Templates, can i remove everthing from the export except the Sections?
Maybe it is getting a bit faster than?
I stopped a full import of an templatestore export after half an hour

Hi Axel, that is the idea behind the reason why we dropped the fs-cli export all command in version 2.x. If you have bigger projects an export could take very long. So instead of export all at once you would export smaller chunks which is possible since you could export each substore like fs-cli export  path:/templatestore/pagetemplates. See fs-cli help export for more information and examples. I hope that helps.
If you need to discuss the usage of the FS CLI please visit to our community at https://community.e-spirit.com (it is moderated and you get faster feedback). Bugs and feature requests are welcome here. Thanks!


Trailing Dot

Description
Adding support for Files and Directories to contain trailing dot in the names after service version 2022-11-02.
Two new options supported that allow users to specify whether or not to trim the trailing dot in the file/directory name:
x-ms-allow-trailing-dot

if true: Do not trim trailing dot from target URI
if false: Trim trailing dot from target URI

x-ms-source-allow-trailing-dot

if true:  Do not trim trailing dot from source URI on target FE.
if false: Trim trailing dot

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-storage-file-share

/azp run java - storage - tests


fetch: remove use of args from CLI parser

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

See discussion at #15382.

Regarding https://github.com/Homebrew/brew/pull/15382#discussion_r1188024084.
I have also said this in the past, since we are using args somewhere way deep in GitHub which get's passed using **options and is very hard to follow.


update/cleaner scripts - suggestions

updater script shouldn't re-download identical version of local user.js without prompting
might be nice to add another choice to skip the update check and just append user-overrides - i use the script often for that myself cause i'm lazy
suggest changing the names of updater and prefsCleaner so they are positioned first in a file browser by prepending them with an underscore - makes them easier to spot :) -or- rename them userjs-updater and userjs-cleaner to stick them next to user.js

btw, i heavily updated my FF config guide - appreciate any feedback anyone might have - leave it in comments (don't have to log-on)
peace

updater script shouldn't re-download identical version of local user.js without prompting

Can you be more specific?
The updater.sh downloads the user.js once to check the version and then shows this prompt:
Continue Y/N?

...and finally downloads the file (again) to disk. Is that what you are referring to?

might be nice to add another choice to skip the update check and just append user-overrides - i use the script often for that myself cause i'm lazy

Indeed. :thumbsup: I'll try to do this as soon as I can if @earthlng agrees. I'll also summon @overdodactyl and @ema-pe, just in case.

suggest changing the names of updater and prefsCleaner so they are positioned first in a file browser by prepending them with an underscore - makes them easier to spot :) -or- rename them userjs-updater and userjs-cleaner to stick them next to user.js

The URLs to the raw content would change, and that would break the self-update feature and the links on the wiki (and everywhere else). You can rename your local copies yourself, though. The Windows version of the updater should work no matter what you name it, and the Linux/Mac version only needs to be updater.sh if you use the self-update feature, otherwise you can rename it.

updater script shouldn't re-download identical version of local user.js without prompting

Can you be more specific?
The updater.sh downloads the user.js once to check the version and then shows this prompt:

ah, right - it needs to grab the script to check the version - probably isn't worth mentioning give it's a minor issue, but what i would do is just keep a text file in the repo with a version string in it and have the updater grab that, compare versions, then offer a choice if a new version is available, assuming you can do a compare in a script
thanks!

what i would do is just keep a text file in the repo with a version string in it and have the updater grab that

Since both updaters are under 10 KB (4.1 for *nux, 9.46 for windows), I don't think the benefits of keeping a versioning file would be worth it for the following reasons:

It clutters the main repo
Whenever an update is made, the version would have to be changed in multiple locations.  In my mind, this is unnecessary maintenance and error prone (unless we write another script to automate version bumps, but again, not worth the effort in this case I don't think)

Thanks @claustromaniac for the ping!

updater script shouldn't re-download identical version of local user.js without prompting

I agree with you. The script should download the user.js to a temporary file (using mktemp), and then compare the local version with the downloaded version. But the user.js itself is a small file, so I don't think that this way worth it.

suggest changing the names of updater and prefsCleaner so they are positioned first in a file browser by prepending them with an underscore - makes them easier to spot :) -or- rename them userjs-updater and userjs-cleaner to stick them next to user.js

This would breaks existent scripts and all links pointing to them. It's a terrible idea!

has already been answered: it needs to grab the user.js to check the version
just run cat user-overrides.js >> user.js. I don't think we need an option for that
we're definitely not renaming the files


Implement Service broker

Description:
It is required to have a Service Broker to provisioning the services offered by the APIM. This enables a single interface which can be used by platforms such as Pivotal to provide our services in a platform-specific way. The service broker should adhere to the Open source Service Broker API specification.
Affected Product Version:
WSO2 API Manager v2.6.x

Since, the initial version is expected to be delivered with WSO2 API Management version 2.6.x, changing the issue title.


IODataEndpoint must support priority/loading order

When using multiple MEF plugins the load order of these plugins is not guaranteed. As existing plugins do not specify this Priority the lowest priority should be 0 and the highest priority should be int.MaxValue.
See also:

Overriding MEF Metadata
How does MEF determine the order of its imports? (less recommended way)

Excerpt from the above mentioned MSDN article:
public interface IPluginMetadata
{
    string Name { get; }
    [DefaultValue(0)]
    int Priority { get; }
}

...

[ImportMany]
public Lazy<IPlugin, IPluginMetadata>[] Plugins { get; set; }

...

Plugins.OrderByDescending(lazy => lazy.Metadata.Priority);

resolved by caafdca4d0b1e54f9414565ae2504e90b13035be


N15: rymd

For #320.
If it's too late it's cool, I will submit next time instead :D

Merged, thanks! Good luck with the game :)


[Addition]: PanterX is witnessing over 30km

Hotspot b58 Addresses
1158dZgG3YmVVxsqZmmfNm6Lmxp4Z4kvPk4hkLspUtAa5fH9xZn
112V93ftcckwQqY8uMM79LGkomkNV25qy7nBEH9UUN8kSLdMNGzx
112qRMK5NVhEWdY9CxQkqM6dy2NhcfejCbH8keb2mvp98pAdFiy4
11kEsgEUjsLR5JoGZEheTMkRDHp9fdGr5ZUGyasjq6j7pB37iSF
114jnXcoDDkkfSuakDEcATgV9p5BNaMYucqqgM6DM6aUfwimtx1
112ArvtgEaLJZ6YJnvG4qwwdoi2R3Tbe4JSaPNHqJAEF2LNz2fC
112J6nzgMT8aoTd4nSsVPuWoaDFtMGdmgVQn79cc1Mj5UvgyTsDA
Discord Handle
No response
Reason(s)
From what I've learnt from the wiki, lora can't go over 20kms unless they have a communication tower or something
These hotspots are all in the mountains and still can witness over 20kms, looks rather suspicious
They all have 1.2dbi antenna and 0 elevation

they can over 30 km with amplifier, that is legal and tolerated by HNT team

they can over 30 km with amplifier, that is legal and tolerated by HNT team

But they in the mountains, shouldn't rock block signals? I can't find any visible antenna on the hill.

but his RSSI was too high, i think not he false, must be something wrong in Helium System, as far as i know, china man are kind person, never cheat, pure heart, humble , honest in this world,  everything can be wrong except china. i urge Helium team do double checking to make sure their system running properly.

It definitely looks like a farm. But LoRa can reach much farther than 20 Kms, As of recent, earnings are capped for distances over 100 Kms.


data: project addition by Manoj Sai

Add a new project to the list
Hey, I would like to propose the inclusion of a new open-source project for the GSSoC'23 list.
The core focus of this project revolves around real-time tracking of cryptocurrency prices through the utilization of APIs.
Code of Conduct

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

Completed. Thanks for your contributions 🎉 ❤


Add Zsh completion

Closes #54 (only for Zsh, as that's the one I use).

Using https://docs.rs/clap_complete/latest/clap_complete/ would be nicer and would support more shells (bash,elvish,fish,powershell,zsh)
https://github.com/crowlKats/clap/blob/master/clap_complete/examples/completion-derive.rs

Yeah but does it know how to auto-complete for sudo-like command wrappers? I couldn't find it in the docs.

Maybe
https://docs.rs/clap/latest/clap/enum.ValueHint.html#variant.CommandWithArguments
https://github.com/clap-rs/clap/blob/14fd853fb9c5b94e371170bbd0ca2bf28ef3abff/clap_complete/examples/completion-derive.rs#L56-L58
https://github.com/search?q=%2FValueHint%3A%3ACommandWithArguments%2F+lang%3Arust+NOT+is%3Afork&type=code
https://github.com/clap-rs/clap/blob/14fd853fb9c5b94e371170bbd0ca2bf28ef3abff/clap_complete/src/shells/zsh.rs#L408
https://github.com/clap-rs/clap/blob/14fd853fb9c5b94e371170bbd0ca2bf28ef3abff/clap_complete/tests/snapshots/value_hint.zsh#L40

Ah nice, I was looking for _command_names.


[Tooltip] Performance issue when lots of tooltips are used in a table

It seems like adding the <Tooltip> component in my table cells is causing some performance issues. I've used React Profiler to debug this and it's pointing to Popper as taking up the most rendering time which I believe is what MUI uses for tooltips. Also, when I used the Chrome performance debugging tool I can see the blocking time is 3 times bigger when using Tooltips.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Table becomes laggy when tooltips are used.
Expected Behavior 🤔
Table remains performant when tooltips are used.
Steps to Reproduce 🕹
This isn't an exact demo of my own use case, I just forked one of the demos, but it shows how the Tooltips slow things down when clicking on "Select all" checkbox. In my own use case the performance hit is a bit more severe as I'm filtering the table at the same time.
With tooltips: https://codesandbox.io/s/material-demo-forked-fs4zu?file=/demo.tsx:10280-10308
Without tooltips: https://codesandbox.io/s/material-demo-forked-wkdkk?file=/demo.tsx:11145-11234
Steps:

Click the "select all" checkbox in left top

Context 🔦
I have a table with 50 rows and 9 columns, each cell has an icon and tooltip. When I filter the table it's very laggy but once I remove the tooltips it's perfectly fine.
Your Environment 🌎
  System:
    OS: macOS 11.4
  Binaries:
    Node: 14.15.5 - ~/.nvm/versions/node/v14.15.5/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.11 - ~/.nvm/versions/node/v14.15.5/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
  npmPackages:
    @material-ui/core: ^4.11.3 => 4.11.3
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/styles:  4.11.3
    @material-ui/system:  4.11.3
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react: ^17.0.3 => 17.0.3
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    typescript: ^4.2.3 => 4.2.3

I also noticed that the blocking time is reduced if I use a simple
<Tooltip title="Person status">
   {person?.status}
</Tooltip>

instead of an Icon:
<Tooltip title="Person status">
   <CheckCircle />
</Tooltip>

I'm guessing a more complex child causes the rendering time to increase?

Performance is similar in V5: https://codesandbox.io/s/material-demo-forked-etgwf?file=/demo.tsx

Replacing md-tooltip with react-tooltip actually brought the blocking time from 1557ms down to 437ms so it must be something to do with Popper. I'd obviously rather not install another tooltip package though.

@cmacdonnacha Do you benchmark in development or production? I would suspect the difference of performance between md-tooltip and react-tooltip to come from emotion. If this is confirmed, then it could be relevant for dev that want high performance to use the unstyled version of the tooltip.

Hey @oliviertassinari I benchmark in dev while debugging but also tried production. In dev the blocking time was 1557ms and in production it was 472ms which is much better but there's still a noticeable lag to the human eye when filtering a table with 50 rows and 9 columns (450 tooltips). The unstyled version sounds good, is this something that I can try out or is it in progress?

For unstyled, @michaldudak is leading the effort in #27170, we accept contributions from the community.
Now, the demo renders 1,600 tooltips. We have never designed the component for this amount of instances, and I don't think that we should start either now. 500 is about the limit we consider valid. You can check our data grid component that implements virtualization and memorization to make this use case fast. I'm actually surprised that you didn't face an issue with the table component too.
I have also opened #27290 as from what I can benchmark, we also spend time on the
 components.

No problem thanks, switching to react-tooltip did the trick to be honest to we're happy enough. Popper must be a lot heavier. We have pagination where the user can choose between 15, 30 and 50 rows and it now performs well even at 50. Thanks for taking the time 👍

The problem is that tooltip should be rendered only on mouse over/enter
I wrote for myself a wrapper component
`import { useState } from 'react';
import Tooltip, { TooltipProps } from '@mui/material/Tooltip';
export default function CustomTooltip({ children, ...rest }: TooltipProps) {
const [renderTooltip, setRenderTooltip] = useState(false);
return (

 !renderTooltip && setRenderTooltip(true)}
        className="display-contents"
    >
        {!renderTooltip && children}
        {
            renderTooltip && (
                <Tooltip {...rest}>
                    {children}
                </Tooltip>
            )
        }

);

}
`

I used controlled tooltip to solve this issue.

Try this. when user hover on tooltip content then it's not unexpectedly hides.
`const CustomTooltip = ({ title, children, overlayClassName, ...rest }) => {
const [renderTooltip, setRenderTooltip] = useState(false);
const closeTimeoutRef = useRef(null);
if (!React.isValidElement(children)) {
console.error(
'CustomTooltip expects a single valid React element as a child.'
);
return null;
}
// Clear any active close timeout
const clearCloseTimeout = () => {
if (closeTimeoutRef.current) {
clearTimeout(closeTimeoutRef.current);
closeTimeoutRef.current = null;
}
};
// Start the close timeout
const startCloseTimeout = () => {
clearCloseTimeout();
closeTimeoutRef.current = setTimeout(() => {
setRenderTooltip(false);
}, 500);
};
// Handle mouse enter on the child element
const handleMouseEnterChild = (e) => {
clearCloseTimeout();
if (!renderTooltip) setRenderTooltip(true);
if (typeof children.props.onMouseEnter === 'function') {
children.props.onMouseEnter(e);
}
};
// Handle mouse leave on the child element
const handleMouseLeaveChild = (e) => {
startCloseTimeout();
if (typeof children.props.onMouseLeave === 'function') {
children.props.onMouseLeave(e);
}
};
// Handle mouse enter on the tooltip content
const handleMouseEnterTooltip = () => {
clearCloseTimeout();
};
// Handle mouse leave on the tooltip content
const handleMouseLeaveTooltip = () => {
startCloseTimeout();
};
return renderTooltip ? (
<Tooltip
{...rest}
title={
title && (

{title}

)
}
destroyTooltipOnHide={true}
overlayClassName={classNames(
{ [overlayClassName]: overlayClassName },
'headerTooltip'
)}
>
{cloneElement(children, {
onMouseEnter: handleMouseEnterChild,
onMouseLeave: handleMouseLeaveChild,
})}

) : (
cloneElement(children, {
onMouseEnter: handleMouseEnterChild,
})
);
};
`

Try this. when user hover on tooltip content then it's not unexpectedly hides.
`const CustomTooltip = ({ title, children, overlayClassName, ...rest }) => {
const [renderTooltip, setRenderTooltip] = useState(false);
const closeTimeoutRef = useRef(null);
if (!React.isValidElement(children)) {
console.error(
'CustomTooltip expects a single valid React element as a child.'
);
return null;
}
// Clear any active close timeout
const clearCloseTimeout = () => {
if (closeTimeoutRef.current) {
clearTimeout(closeTimeoutRef.current);
closeTimeoutRef.current = null;
}
};
// Start the close timeout
const startCloseTimeout = () => {
clearCloseTimeout();
closeTimeoutRef.current = setTimeout(() => {
setRenderTooltip(false);
}, 500);
};
// Handle mouse enter on the child element
const handleMouseEnterChild = (e) => {
clearCloseTimeout();
if (!renderTooltip) setRenderTooltip(true);
if (typeof children.props.onMouseEnter === 'function') {
children.props.onMouseEnter(e);
}
};
// Handle mouse leave on the child element
const handleMouseLeaveChild = (e) => {
startCloseTimeout();
if (typeof children.props.onMouseLeave === 'function') {
children.props.onMouseLeave(e);
}
};
// Handle mouse enter on the tooltip content
const handleMouseEnterTooltip = () => {
clearCloseTimeout();
};
// Handle mouse leave on the tooltip content
const handleMouseLeaveTooltip = () => {
startCloseTimeout();
};
return renderTooltip ? (
<Tooltip
{...rest}
title={
title && (
{title}
)
}
destroyTooltipOnHide={true}
overlayClassName={classNames(
{ [overlayClassName]: overlayClassName },
'headerTooltip'
)}

{cloneElement(children, {
onMouseEnter: handleMouseEnterChild,
onMouseLeave: handleMouseLeaveChild,
})}
) : (
cloneElement(children, {
onMouseEnter: handleMouseEnterChild,
})
);
};

@soliyapintu can you please format the code and put it in a code block

@enoh-barbu  Done

@soliyapintu maybe instead of using timeout, what about listening to onClose event of Tooltip

@enoh-barbu I am utilizing a timeout mechanism to delay the unmounting of the tooltip component, ensuring it is removed from the DOM after a specified duration.


KYLIN-3700 Quote sql identities when creating flat table

Can one of the admins verify this patch?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@70f15d7). Click here to learn what that means.
The diff coverage is 22.14%.

@@            Coverage Diff            @@
##             master     #362   +/-   ##
=========================================
  Coverage          ?   23.58%
  Complexity        ?     4838
=========================================
  Files             ?     1134
  Lines             ?    68344
  Branches          ?     9705
=========================================
  Hits              ?    16122
  Misses            ?    50656
  Partials          ?     1566

Impacted Files
Coverage Δ
Complexity Δ

...k/datasource/framework/SourceConnectorFactory.java
57.89% <ø> (ø)
1 <0> (?)

...java/org/apache/kylin/metadata/model/TableRef.java
51.16% <0%> (ø)
11 <0> (?)

...ain/java/org/apache/kylin/job/JoinedFlatTable.java
0% <0%> (ø)
0 <0> (?)

...ava/org/apache/kylin/metadata/model/TableDesc.java
46.01% <0%> (ø)
27 <0> (?)

...pache/kylin/source/hive/GarbageCollectionStep.java
0% <0%> (ø)
0 <0> (?)

...a/org/apache/kylin/common/util/HiveCmdBuilder.java
83.33% <100%> (ø)
12 <0> (?)

.../kylin/source/jdbc/extensible/JdbcHiveMRInput.java
89.79% <100%> (ø)
3 <0> (?)

...e/kylin/sdk/datasource/adaptor/DefaultAdaptor.java
21.34% <2.63%> (ø)
12 <0> (?)

.../apache/kylin/job/util/FlatTableSqlQuoteUtils.java
21% <21%> (ø)
8 <8> (?)

...in/sdk/datasource/adaptor/AbstractJdbcAdaptor.java
51.04% <22.22%> (ø)
14 <2> (?)

... and 6 more

Continue to review full report at Codecov.

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

Local CI pass.

Pull Request Test Coverage Report for Build 3896

72 of 244 (29.51%)  changed or added relevant lines in 15 files are covered.
6 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.006%) to 25.941%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-metadata/src/main/java/org/apache/kylin/metadata/model/TableRef.java
0
1
0.0%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/framework/JdbcConnector.java
2
3
66.67%

source-hive/src/main/java/org/apache/kylin/source/hive/GarbageCollectionStep.java
0
1
0.0%

source-hive/src/main/java/org/apache/kylin/source/hive/HiveInputBase.java
4
5
80.0%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/framework/conv/SqlConverter.java
7
9
77.78%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/framework/conv/DefaultConfiguer.java
6
9
66.67%

core-metadata/src/main/java/org/apache/kylin/metadata/model/TableDesc.java
0
6
0.0%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/framework/conv/ConvSqlWriter.java
5
12
41.67%

source-jdbc/src/main/java/org/apache/kylin/source/jdbc/JdbcHiveMRInput.java
3
11
27.27%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/adaptor/AbstractJdbcAdaptor.java
4
18
22.22%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
1
78.12%

core-job/src/main/java/org/apache/kylin/job/JoinedFlatTable.java
2
0.0%

datasource-sdk/src/main/java/org/apache/kylin/sdk/datasource/adaptor/DefaultAdaptor.java
3
35.51%

Totals

Change from base Build 3894:
-0.006%

Covered Lines:
17690

Relevant Lines:
68193

💛  - Coveralls


Grant Triage permission level to @aurel32

Nomination
Grant Triage permission level to @aurel32
GitHub User
Provide the following information about the GitHub user:

Full Name: Aurelien Jarno<EMAIL_ADDRESS>GitHub username: https://github.com/aurel32

Supporting Documents
https://github.com/zephyrproject-rtos/zephyr/pulls?q=is%3Apr+author%3Aaurel32+

@aurel32

@aurel32 already has triage permission.

@aurel32 I am actually surprised that you are not in the MAINTAINERS file given the amount of contributions you have made.
Could you open a PR adding yourself as a collaborator for one of the areas you have been involved in so that we can add you as a collaborator?

@aurel32 I am actually surprised that you are not in the MAINTAINERS file given the amount of contributions you have made.
Could you open a PR adding yourself as a collaborator for one of the areas you have been involved in so that we can add you as a collaborator?

Ok, let me close this issue and we'll check this.


can't import .speech_py_impl

from . import speech_py_impl as impl
ImportError: cannot import name 'speech_py_impl' from 'main'

never mind


[Do Not Review] update-courses workflow

Summary

This pull request updates and fixes the update-courses workflow.

Test Plan

None. I tested the action on this branch and it worked.
Note: we shouldn't test this too frequently since it makes a bunch of api calls to the course roster api.

Is there a reason you don't want this reviewed?

@zachary0kent forgot to update the title, whoops. Feel free to review.


Remove generics from class in core that is about to go away

Linux Build 6929 is now running using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4

Windows Build 2004 is now running using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4

Linux with security manager Build 1827 is now running using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4

Linux with security manager Build 1827 outcome was SUCCESS using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4
Summary: Tests passed: 864, ignored: 311 Build time: 0:06:11

Windows Build 2004 outcome was SUCCESS using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4
Summary: Tests passed: 2910, ignored: 372 Build time: 0:49:33

Linux Build 6929 outcome was FAILURE using a merge of 9cbfcc835db5fef47f1f7498e8187510983523c4
Summary: Tests failed: 1, passed: 2907, ignored: 372, muted: 2 Build time: 0:50:56
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>


Does this work with Git Pages?

Thinking of using this template as it is lovely, but not all Jekyll blogs can be hosted there.
Thanks!

Looks like it does! Thanks!


[Security] A potential risk of kubecost makes a worker node get the token of any Service Account

Kubecost Helm Chart Version
1.107
Kubernetes Version
s
Kubernetes Platform
GKE
Description
Summary
The Kubecost in GKE gave excessive authority when defining Service Account named "kubecost-1-cost-analyzer-serviceaccount-name-dff5" "kubecost-1-cost-analyzer-prometheus-serviceaccounts-server-name-e82d" and "kubecost-1-deployer-kvsqj". Besides, these Service Accounts are mounted into pod, witch makes it possible for attackers to raise rights to administrators.
Detailed Analysis

I deployed Kubecost  in the marketplace of Google's GKE cluster by default.

The clusterrole named "default:kubecost-1:cost-analyzer.serviceAccount.name-r0" defines the "*" verb of "pods, deployments, replicationcontrollers and nodes". And this clusterrole is bound to the Service Account named "kubecost-1-cost-analyzer-serviceaccount-name-dff5". The Service Account is mounted into the pod named "kubecost-1-cost-analyzer-789fc48778-xgpkg".

The clusterrole named "default:kubecost-1:cost-analyzer.prometheus.serviceAccounts.server.name-r0" defines the "*" verb of "pods, jobs, deployments, statefulsets, replicationcontrollers and nodes". And this clusterrole is bound to the Service Account named "kubecost-1-cost-analyzer-prometheus-serviceaccounts-server-name-e82d". The Service Account is mounted into the pod named "kubecost-1-prometheus-server-6f9d5c9989-l972j".

The clusterrole named "default:kubecost-1:deployerServiceAccount-r0" defines the "*" verb of "clusterroles and clusterrolebindings". And this clusterrole is bound to the Service Account named "kubecost-1-deployer-sa". The Service Account is mounted into the pod named "kubecost-1-deployer-kvsqj".

Attacking Strategy
If a malicious user controls a specific worker node which has the pod mentioned above, or steals one of the SA token mentioned above.He/She can raise permissions to administrator level and control the whole cluster.
For example,

With the "*" verb of "clusterroles and clusterrolebindings", attacker can elevate privileges by creating a clusterrolebinding resource and binding cluster-admin to their own Service Account.

With the "*" verb of "pods, jobs, deployments, statefulsets, replicationcontrollers", attacker can elevate privileges by creating a pod to mount and steal any Service Account he/she want.

With the "*" verb of nodes, attacker can hijack other components and steal token by adding a "NoExecute" taint to other nodes.

Mitigation Discussion

Developer could use the rolebinding instead of the clusterrolebinding to restrict permissions to namespace.
Developers could define precise permissions for workload resources, including pods, deployments, jobs, statefulsets, replicationcontrollers , rather than using wildcard (*).
The "kubecost-1-deployer" appears to be used for initialization, and developers can delete resources such as the corresponding pod or Service Account after they are no longer needed.

A few questions

Is it a real issue in Kubecost?
If it's a real issue, can Kubecost mitigate the risks following my suggestions discussed in the "mitigation discussion"?
If it's a real issue, does Kubecost plan to fix this issue?

Reporter list

Xingyu<EMAIL_ADDRESS>me)
Nanzi Yang(952508578nanziyang<EMAIL_ADDRESS>Xunqi<EMAIL_ADDRESS>Xin<EMAIL_ADDRESS>Wenbo<EMAIL_ADDRESS>Jinku<EMAIL_ADDRESS>
Looking forward to your reply. Regards Xingyu Liu
Steps to reproduce

Deploy the kubecost by default in GKE.
Use kubectl get sa to get the list of service accounts.
Use kubectl get rolebinding,clusterrolebinding --all-namespaces -o jsonpath='{range .items[?(@.subjects[0].name=="SERVICE_ACCOUNT_NAME")]}[{.roleRef.kind},{.roleRef.name}]{end}' to get the clusterrole related to the service account, and view the permission definition.

Expected behavior
This is a configuration error.
The Service Accounts mentioned above are given excessive authority, witch makes it possible for attackers to raise rights to administrators.
Impact
No response
Screenshots
No response
Logs
No response
Slack discussion
No response
Troubleshooting

[X] I have read and followed the issue guidelines and this is a bug impacting only the Helm chart.
[X] I have searched other issues in this repository and mine is not recorded.

This issue is related to the Kubecost listing on GCP Marketplace hence transferred to its parent repo. The configuration is found here which is specific to the Marketplace listing and, as pointed out earlier, not part of the main chart. This may have been a requirement for the deployment to succeed in GCP because it's the only place where the differences appear.

whoops. sorry for the accidental close. I think this is appropriately filed now but there's not much we can do on our side.

Hi @sparkEchooo as noted this is not related to kubecost and is a function of the GCP marketplace.

Is there a place to file this against GCP marketplace or a related repo?

@alexkubecost  is there someone on the GCP Marketplace team we could share this with?

@chipzoller actually, do you know how to quickly test whether that's actually a requirement on the marketplace?

Hi there,
If you're looking to update Kubecost on the GCP Marketplace, this might help: https://cloud.google.com/marketplace/docs/partners/kubernetes/maintaining-product

Thank you @sparkEchooo we will look at updating this in https://github.com/kubecost/gcp-marketplace/blob/main/kubecost/schema.yaml#L84-L158

cc @cliffcolvin let's file a ticket for internal tracking


Release sqly to Windows, Mac, Linux

What
sqly uses CGO, so GoReleaser is difficult to set up (needs to be cross-compiled). Therefore, we are now only releasing binaries for Linux. To encourage more people to use sqly, we will increase the variety of release binaries.
Support OS

Windows
Mac
Linux

Architecture

amd64
aarch64

Package Manager

Homebrew
apt
rpm

How
Modify the GoReleaser configuration file
Checklist

[ ] Finish implementation of the issue
[ ] Test all functions
[ ] Have enough logs to trace activities
[ ] Notify developers of necessary actions

Fix by #57


commons-lang EoS, ESW4

commons-lang EoS, ESW4 -> Not for new design
swap to: commons-lang3

Fixed!


Own position not clonable. Intended?

If you own positions, you can't clone.

Why should we have this behavior?
Why do we restrict buttons for navigation?
Why do we force the user to manually navigate (forces a reload of the whole app incl. redux store)?

Do we want to adjust this or is this an intended behavior?

Cloning your own position is kind of pointless. This is by design.


Possible incorrect variable reference.

Sorry if this is not a real bug.  Current code at https://github.com/Polymer/polymer/blame/master/lib/utils/mixin.html#L54 checks for mixin.__id, then sets mixin.__dedupeId.  Seems like the same property should be used all the time.  This bug report is based purely on my belief that "this looks wrong", I have not seen it cause trouble in real life.
This code was originally added by @sorvell:

https://github.com/Polymer/polymer/commit/ef695031e2e9e07b6dfc481d4058ae1ac5ff57e0#diff-37d29f6fc5721ddc3d2248a84cfcc681R117

Yeah, that seems suspicious. Thanks!

The __dedupeId is set on mixin function creation, so the check doesn't matter.
The caching functionality also makes sure that any funky nesting of dedupingMixin will end in the same output class.
Since the check doesn't work anyway, I'll remove it.


TypeError: Cannot read property 'getRepositoryRoot' of null

HEAD, running out of workspace
I see the following errors in the console.
[28049:0728/105243:INFO:CONSOLE(31)] "TypeError: Cannot read property 'getRepositoryRoot' of null
    at OpenInDiffAction.isEnabled (file:////home/aeschli/workspaces/vscode/out/vs/workbench/parts/git/browser/gitActions.contribution.js:47:52)
    at OpenInDiffAction.Object.defineProperty.set [as input] (file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/parts/editor/baseEditor.js:433:37)
    at file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/parts/editor/baseEditor.js:331:34
    at Array.forEach (native)
    at FileEditorActionContributor.EditorInputActionContributor.getActions (file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/parts/editor/baseEditor.js:330:31)
    at file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/actionBarRegistry.js:242:61
    at Array.forEach (native)
    at ActionBarRegistry.getActionBarActionsForContext (file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/actionBarRegistry.js:239:41)
    at TabsTitleControl.TitleControl.getEditorActionsForContext (file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/parts/editor/titleControl.js:221:77)
    at TabsTitleControl.TitleControl.getEditorActions (file:////home/aeschli/workspaces/vscode/out/vs/workbench/browser/parts/editor/titleCont

Happens during shutdown.


[Bug]: Invalid Player Data Lockout on 1.20.1

Minecraft Version
1.18
Mod Version
1.20.1-1.6.0
Is Compressium Loaded
Not Loaded
What happened?
When loading Create Compression 1.6.0 with Quark 4.0-433, new and old worlds will load and immediately kick the player yielding an 'invalid player data' error message. According to Quark devs recipe implementation may be causing the fault. Log attached, see line 3039.
Link to issue from Quark end:
https://github.com/VazkiiMods/Quark/issues/4635#issue-2116755284
latest.log

Should be fixed in later versions. I think it was recipes that had errors in them and they were irrelevant to this mod


Test utilities for creating trust lines, assets, issuance, etc for accounts

We still need to add test utilities for creating trust lines for accounts.
The main use case of these test utilities is to give people the ability to exercise import and export with tokens that are linked to assets.

env.accounts().set_trust_line(...)

env.deployer().with_source_account(...).deploy_token(...)
env.deployer().with_source_account(...).deploy_token_for_issued_asset(...)
env.deployer().with_source_account(...).deploy_token_for_native_asset(...)

More context in this duplicate issue - https://github.com/stellar/rs-soroban-sdk/issues/826.

Closing as we no longer have an immediate need for these in contract tests since contract tests use contract addresses for testing. Please reopen if we discover otherwise.


As a CIF admin user, I want to hard delete attachments, so that I'm not keeping files I don't need

Description:
In #1462, we created an attachment form. When a user is creating a project for the first time and deletes an attachment, the attachment should be hard deleted. #1462 hard deletes the form_change record. This ticket is about hard deleting the actual attachment from google storage. (Once a project has been committed, we only soft delete so we can keep a change log.)
Acceptance Criteria:
Given I am a CIF admin user
When I am creating a project and I delete an attachment ~or discard my entire revision~
Then my attachments are deleted from google storage
Development Checklist:

[x] Hard delete from google storage (check out CIIP's deleteRouter and hard delete functionality for an example)
[ ] e2e test cleans up uploaded test files:

[x] Add assertions. Can use something like this if you like:

    cy.findByText("1dummy.pdf").should("be.visible");

[ ] give CI the env variables necessary for upload (at least the storage dev json, maybe more)

[x] delete the uploaded test file (1dummy.pdf) from google storage after the test

[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Hey team! Please add your planning poker estimate with Zenhub @dleard @gurjmatharu @JoshLarouche @mikevespi @sam-warren @Sepehr-Sobhani

@patriciarussellCAS, to test this, create a new project, go straight to the attachment form, add an attachment, and then delete it. If it works, the attachment has been hard deleted (if you'd like me to show you the file disappearing from the google bucket, I can screenshare with you as you test).

Thanks @BCerki - it looks like I could use some help on this one as well. I can't seem to be able to delete the attachment from the project (soft delete).

@patriciarussellCAS , this should work now


Create travis configuration file

PR to test the Travis configuration file (WIP)

For review please :)

Fix #2201 (along with https://github.com/matrix-org/matrix-android-sdk/pull/267)


CI is not entirely running

As a developer, I'd like to dive into quarantined/skipped tests in the CI plans, so we could fix and run them on incremental code commits.

see https://github.com/spring-cloud/spring-cloud-deployer-cloudfoundry/blob/ea5d9e078103b47eea1c9bd1e86f918381dc190e/src/test/java/org/springframework/cloud/deployer/spi/cloudfoundry/CloudFoundryTaskLauncherIntegrationTests.java#L69


Tinkers Construct bow broken

Minecraft version & Mod Version:
Minecraft 1.12.2
Cyclic-1.12.2-1.15.11
Single player or Server:
Server
Describe problem (what you were doing / what happened):
Here:https://github.com/SlimeKnights/TinkersConstruct/issues/3544
Crash log (if any):
(If this is a suggestion and not a bug report, delete all this and just write your suggestion!)

To elaborate, when any ranged weapon is fired, it has its' NBT data reset.
Tested with just Tinkers' Construct, Mantle, JEI and Cyclic version 1.12.2-1.15.11

Yes is true, thanks for the report. fix coming out soon https://github.com/PrinceOfAmber/Cyclic/issues/848


feat request: .bru file formatting option for vscode

Hi,
I have just started using bru and while I was migrating requests from postman to .bru files, I saw that there is no option to format the files.
It would be great if we could plan and fit this somewhere in the timeline.

This would be absolutely fantastic and a must have to keep our source files consistent, please consider!


Implement batch binary inputs

Similar to https://github.com/lexicalunit/nanodbc/pull/214 this adds binding support for std::vector<std::vector<uint8_t>> inputs, which allows you to bind batches of arbitrary binary data. We could not use the bind_strings() for this as there could be embedded nulls in the data, as pointed out by https://github.com/lexicalunit/nanodbc/issues/209.

Tests seem to be working for everything but MS-SQL, I will try and figure out what needs to change tomorrow, if you have any idea what might be wrong let me know.

@jimhester unfortunately I have the least amount of experience of all with MSSQL. Thank you for looking into it and all your effort improving this library :)

Tests now passing, MS-SQL must need a default size for varbinary, or have a default less than 4.

@jimhester I'm going to submit PR fixing the conflicts.

LGTM and if @lexicalunit approves, I can merge it.

It is ready if it looks good to you!


[content]: Sidebar is not scrollable

Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
When sidebar is sticky and there is ToC fragment in it, it's not scrollable.
What you expected to happen:
The sidebar should be scrollable even if it's sticky.
How to reproduce it (as minimally and precisely as possible):
Enable sticky option in sidebar config and use ToC inside it.
Anything else we need to know?:
Environment:

Syna Theme version:  0.15.0
Hugo version:  Hugo Static Site Generator v0.55.0-4333CC77F/extended linux/amd64 BuildDate: 2019-04-08T17:05:23Z
Others:

So this means we can't make the sidebar scrollable itself?
Thought it might be able to work similarly to https://stripe.com/docs on smaller screens. Their left sidebar is scrollable vertically, if it's overflowing. It's still sticky towards the content so.
Or maybe my use of the term sticky is not correct.


No data other than Position and Last Update

Greetings
I came across this cool project and jumped right on it since my mesh is growing fast and setting all nodes up in HA is quite a chore. Setup seems quite straight forward, I run an EMQX cluster for various other projects and HA has a connection to this cluster already. However I've set up three different Meshtastic nodes and none of them populate battery, enviromental stuff or anything else. Just Position and Last Update.
I use a private primary channel for all my telemetry and I've used that key from the app but it has no effect. I also use version 2.5.7 or above on all my Meshtastic nodes.
The diagnostic log from the integration gives
2024-11-25 20:36:20.204 WARNING (MainThread) [homeassistant.components.mqtt.sensor] Invalid state message 'unknown' from 'msh/EU_868/2/json/HoffChannel/!7c5cb244'
2024-11-25 20:36:20.204 WARNING (MainThread) [homeassistant.components.mqtt.sensor] Invalid state message 'unknown' from 'msh/EU_868/2/json/HoffChannel/!7c5cb244'
2024-11-25 20:36:20.206 WARNING (MainThread) [homeassistant.components.mqtt.sensor] Invalid state message 'unknown' from 'msh/EU_868/2/json/HoffChannel/!7c5cb244'

It looks like you're using the json topic, this integration uses the protobuf topic. You may want to try msh/EU_868/2/e/HoffChannel/!7c5cb244 instead.

Correction. That is the channel I'm using for the config in HA. msh/EU_868/2/e/HoffChannel/!7c5cb244 is the value entered.

I've fiddled with different combinations, for troubleshooting. Channel key, no channel key, no JSON MQTT on the node, add a new node. So far same result. Nothing

Do you see a protobuf (binary) data coming to your MQTT server on that topic(s)? Using MQTT Explorer or something

Yes, there is protobuf data coming to MQTT. I haven't made any attempt at reading it though.

Should work then (works for me). Have you tried enabling debug logs for the integration? It dumps all types of protobuf messages it receives

The debug log grows quickly, I've got alot going on with my Home Assistant, but nothing I can find specifically to this integration.

you can only filter messages from custom_components.mtastic_mqtt if it helps.
the messages above look as expected, it seems that data is coming

I agree. Looks like Home Assistant is getting something. I have no clue how to proceed or which information to give you. I run HA as a docker instance, version 2024.11.3.
Damn. It would have saved me alot of time if this integration worked.

Oh my God! No I only assumed they would enable themselves once data was processed.
I went and enabled them all and, well, there it is.


Roll meta/pedantic

Unpin meta, fix up callsites.
Last time I tried this, it broke some customer tests. Will have to see if that's still the case.
https://github.com/jocosocial/rainbowmonkey/pull/328

Note that we are currently considering rolling back this release. There are a lot of trade-offs and no decision as of yet what will happen, but I would hold of on depending on 1.2.1 until a decision has been reached.

It looks like we will in fact be rolling this back (hopefully today?)

Thanks Jake.  Is there a bug to follow for it?

https://github.com/dart-lang/sdk/issues/42635

I'll open a new PR that unpins and rolls to the newer meta.


Hi, I'm a member of cdnjs team

Hi, I'm going to host this lib on cdnjs.
But I meet a problem.
I downloaded this lib from npm.
I tried to minify the files in the dist folder.
But I failed.
I try 3 minify tools but still cannot minify it.
Could you help me to minify it?
And if you finish it, please update to npm.
Because we prefer to use npm auto-update.
Thank for your help!
https://github.com/cdnjs/cdnjs/pull/8444

How are you minifying? What errors?

@x09326 cdnjs isn't one of our target distribution methods. If you wish to implement this we suggest that you mirror the bower distribution. This is typically a foundational library which other (larger) tools consume. Thank you for your interest!


Automatically create /relationships/{relatedItem} route

Hey,
so to follow the json api specs a route call to /relationships/{relatedItem} should return one of 4 very simple results: http://jsonapi.org/format/#fetching-relationships
As every resource with relationships should have that and it is exactly the same for all of them, I think it would be a very good candidate for automation.
Maybe one could set a config option and if it is set to true, those routes & results could be automatically created?

I'm not sure it would be that simple...
Plus I don't want to build in too much automation when it comes to routes.

Hmm, I guess since you would need to allow push to those routes as well, it makes sense, I was not thinking of this.


Typo "Azure Blob storage service"→"Azure Blob Storage"

https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/back-up-multiple-databases-to-azure-blob-storage-powershell?view=sql-server-ver15
https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/relational-databases/backup-restore/back-up-multiple-databases-to-azure-blob-storage-powershell.md
#PingMSFTDocs

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @hyoshioka0128 ! This looks great. I added one tiny suggestion for you to review if that makes sense.
Kendra from the Database Docs team

Hi,
Just checking back in on this. The suggestion I made wasn't incorporated-- is that something you can add to the commit?   There is an extra "the" in the following sentence:

An Azure storage account and SQL credential are required prerequisites and for all backup and restore operations to the Azure Blob Storage.

I believe this should be:

An Azure storage account and SQL credential are required prerequisites and for all backup and restore operations to Azure Blob Storage.

Thanks,
Kendra

@LitKnd - Thanks! I overlooked it. I also accepted.

Hi @hyoshioka0128 ,
It still shows that there was not a second commit. I think the process with the suggestion is a bit confusing.
It is not a big deal and I can circle back and clean up that one word after :)
Thanks again for your submission and for making our docs better.
Kendra
#sign-off

Closing and reopening as I think maybe some automation got stuck.
#please-close

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

I removed "the" where indicated. Thanks, all.

@ktoliver - Thanks!


Directory is read-only making status directory

I assume this should work:
github.com/docker/pinata/pr/3661/status/ci> mkdir pinataci
Directory is read-only

Not needed now we have #184.


development oriented dockerfile + docker-compose for easy usage

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
a new dockerfile for development, running nodejs. mounted the src folder to the local folder for easy development

What is the current behavior? (You can also link to an open issue here)
currently there is just a dockerfile for production usage. as default, the url will be <IP_ADDRESS>:3000

What is the new behavior (if this is a feature change)?
allows developing using dockerfile and docker-compose

Other information

Agree with @katallaxie - While I docker everything under the sun, many still use vagrant or don't containerize at all. This as examples in the readme would accomplish the same thing while allowing flexibility to implement without the merge headaches as everyone's compose stack is going to vary significantly.

@benyitzhaki - This type of information is valuable & should be in a readme / docker.md. Given the situational nature of Docker, it's not something I would merge into a starter repo.
We would on the other hand certainly appreciate a doc covering your proposed Docker Stack configuration as a starting point for those that are new to Docker


Figure out how OPA/OPA Gatekeeper reads arguments for policies

Given an OPA-based policy, figure out what arguments it takes, and how they should be provided to it by burrego, and by extension, the policy-evaluator.
Acceptance criteria

We know and document what structure it accepts as input/data and how it should be structured.

I'm documenting everything here: https://gist.github.com/ereslibre/873df64decf209c6dc90376327d1e07d

Considered done.

Copied the gist contents to the policy-evaluator Wiki, that I believe is a better place for this information: https://github.com/kubewarden/policy-evaluator/wiki/OPA-Gatekeeper


Fix deprecated function calls

I believe this should fix #89.
This PR silences compile warnings by replacing calls to the deprecated Swift functions flatMap and deallocate(capacity: Int) with more current versions of those functions.

@simonbilskyrollins Thank you!


Remove (abandonded) container-interop/container-interop dependency

Hi,
Now that https://github.com/container-interop/container-interop/issues/94 has been done, composer update gives this mildly annoying message:
Package container-interop/container-interop is abandoned, you should avoid using it. Use psr/container instead.

It's trivial in the greater scheme of things, but it'd be nice if this could be remedied.

There's already an open issue for this from quite some time ago: https://github.com/Behat/Behat/issues/1110
It's unfortunate that this deprecation was known about for two years and nothing was done about it...

As I already said on linked issue, this is considered to be a bc break, even though it's an acceptable one.
Ping @ciaranmcnulty, @stof and @jakzal

Fixed in #1281.