Builder: Can not change project folder choice (Failure)

Hi,
When you try to save the project, a folder selection window has opened but it does not work, you can not select any other location to save the project (top folder, or any other shortcut such as My Computer).
If I try to create a folder in the current directory, a fatal error message appears ("Failure").

Thanks for reporting the Builder save dialog behavior.
In recent versions of the Builder (after 0.11.0-beta4), I understand that the Builder project save dialog was altered to default to the Arduino libraries folder, and enable the creation / selection of any subfolders below that. If I recall correctly, Paul (the Builder developer) had implemented it this way to help ensure that round-trip edits between the Builder and the Arduino IDE would be seamless and minimize the chance for accidental overwrites. I'll let him clarify it better as I believe this was an important decision point.
As for creating sub-folders, I just tested it again on my side and didn't observe the error. I assume you have write permission to this folder? If you could email the crash log to<EMAIL_ADDRESS>we should be able to track it down for you.
thanks!

Hi,
I think I've already found the cause of this error,
I am using Windows 10 x64, my Java is x64.
I tried to install the GUI again, but this time I selected the Arduino IDE's Java folder (1.8.9).
And I also selected the C: \ folder for the projects, now I have more freedom, but I still can not choose D: \ and this is horrible. If I needed to select an external drive (pendrive) could no longer save. For it is another letter of unity.
Note: The Arduino IDE is ok, everything normal.
Thank you.

Hi,
I have made use of B4A, a type of code generator for Android, which generates full app, the B4A is well mature already.
This developer has also got another application that works with the Arduino, if it is called B4R, maybe you can talk and join forces, it seems the application of B4R does not have the graphical part, (precisely the strength of B4A).
Take a look: https://www.b4x.com/b4r.html
I commented there in the B4R forum about this project, I hope it will make sure that you join forces, the graphic part for Arduino was what was missing!
https://www.b4x.com/android/forum/threads/no-designer-how-are-tft-screens-made-do-you-know-guislice.104755/

I asked previously about user selection of prj/ino folder locations. I received the following response from Paul:
As long as its in or a sub directory of your registered project folder.
What I have done is open the General Tab of the Builder Edit Preferences window and enter the path to my  top-level folder which I call "Arduino" as the new Project Directory. All of my Arduino sketches are various sub-folders under the "Arduino" folder.
When I start a new sketch/project, I first give a new folder the desired sketch name, say "Blink". This is a sub-folder under my Project Directory folder, "Arduino". When I start a new sketch/project, I open the "Choose your project folder" window in Builder. The "Folder name:" will default to the Project Folder set up in the Edit Preferences window, in my example, "Arduino".   I change this to the new sketch/project folder I just set up, "Blink".
This seems to work okay. I'd be glad to hear if there are problems with this method.

@ritek1000 First I'm open to changing the folder chooser but final say is with Cal.
As for your issue what makes you think you can't use your pen drive?
Open Builder, edit->options
change project directory from say
c:\users\paul\documents\arduino
to your pen drive I used for a test
f:/foobar
created and compiled a test project (Builder-0.11.0-rc4) it created
f:/foobar/testpendr/testpendr.prj, gen code
f:/foobar/testpendr/testpendr.ino, compiled and ran fine.
Paul--

Thank you Don & Paul for the comments regarding the folder selection.
I would definitely be interested in revising the folder chooser as I think it may be more restrictive than necessary (I suspect I might have inadvertently implied more limitations in earlier discussions than intended!).
In my opinion, the important goals would be to ensure we can support easy round-trip edits (Builder <-> Arduino IDE) and minimize the chance of any accidental overwrites (due to lack of file coherency). I believe the only restriction this implies is that we save new Builder projects to a subfolder with the same name as the Builder project (and any generated sketch file) so as to avoid the IDE creating the folder and relocating the sketch. Do we have any other requirements beyond that? For example, a Builder project named MyCount would be saved in MyCount/MyCount.prj. Theoretically, this subfolder (eg. MyCount) could be placed anywhere on the computer / external drive, though defaulting to the Arduino IDE sketch folder might be a convenient default. Hopefully this change wouldn’t be too much of a hassle; I think it would greatly increase flexibility for users.
rtek1000 — thank you for highlighting B4A / B4R and your thoughts on it; I wasn’t aware of the framework and will take a look.

Hi,
I've tried several softwares, since the 2000s, I was confused by this because in the GUI installation, it asks for a project folder.
But if the user can change the folder after the GUI is installed, it helps.
I think it would be less confusing if it worked similarly to Visual Basic 6, Visual Studio, or SharpDevelop (V4.4), or even B4A (which closely resembles the style of VB). Where the project folder is selected at the time of the first save operation, or at the time of new project creation.
I use a government program that makes use of an unfriendly interface to perform the backup, where the only way to navigate between folders is to open folder by folder, as if it were to navigate in Windows regedit, nor has it an option to "paste" the path I prefer. If the user has to open the settings to select a different folder for each project, I think it follows the same pattern: Not very friendly.
I still have not understood the idea of choosing a project folder during the installation. I think it's bad for the user to limit this way, maybe it could just "remind the user to avoid saving in the wrong place".
Thank you.

Adding to the last several comments, I tried the following two approaches. I added some questions & comments afterwards.
In Builder "Edit Preferences" window General tab, "Project Directory" is set to C:\Users\Arduino
----Approach 1: Start and Save an ino sketch file first, then save Builder file second.----

Started new sketch and named and saved the ino to a level below "C:\Users\Arduino". This automatically created a folder of the same name as the sketch ino file.
Opened Builder and added an element.
Saved Builder to folder created by Arduino IDE in Step 1. Pressed "Generate Code" which opened a message box indicating success.
Opened sketch. Builder had not added any element code.

---Approach 2: Start and Save Builder file first, then save ino sketch file second.---

Since there is no option in Builder to assign a file name to the .prj file, I first set up a folder using Windows Explorer with the desired project/sketch name as a subfolder of C:\Users\Arduino.
Created an element with Builder.
Used the Builder "Choose your project folder" window to locate the folder I set up in Step 1 and saved the .prj file.
Builder created a sketch of the same name and successfully added element code to the sketch ino file.
//-----Comments---

I understand that for technical reasons all sketches with Builder code must be subfolders of the "Project Directory" folder in Preferences. Somehow I think this requirement needs to be made clearer since, in general, most applications allow the user to place folders and files anywhere they choose.
I realized from the SimpCount example in the Wiki Walkthrough that Approach 1 apparently won't work, that is, the user can't start with a ino sketch file then added a Builder prj file. Perhaps some sort of error message: "NOTE: Builder project folder and file must be created first. Builder will then create a sketch file of the same name."
If Approach 2 must be used - Builder first, sketch second - perhaps the Builder Save as Project... window could allow the user to assign the desired file name which would create a .prj file in a folder of the same name. Isn't this the way the Arduino IDE works?

@DonpK I've removed the restriction that you must create projects in "projects folder" in release
builder rc5.  The need to create sub folders will still exist.  The windows installer will still ask
for a project directory.   The file chooser has to open up somewhere after all.  Don't like the starting
spot you can change it later.
The reason for creating sub folders first is due to experience with builder betas 1-4.
They allowed project ".prj" files to be created first, anywhere you wanted.
The problem came up later.   compile the generated .ino file and arduino refused unless it was allowed
to place it inside a sub folder of the same name.  Agree and the .ino file is moved into the new
sub folder.  It gets compiled and runs and eveything is fine.  Unless you want to go back to the builder
and make some changes.   The ".prj" file isn't copied by the Arduino IDE so it's now one level up from your ".ino" file.   Open builder, find your ".prj" file open it and make some change, generate code
and it's now created a new ".ino" file above the new sub folder Arduino IDE created.  You now have two
".ino" files.
   So I made my choices with that in mind.

Hi,
Ok thanks for commenting,
[Off topic]:
I would like to suggest this same kind of possibility to create graphical part, for Python Tk and for Processing.
(Are different projects, but similar to B4A (Android), B4J (Java), B4I (IOS). It can be GUIslice for Processing, GUIslice for Python Tk).
For Python Tk, maybe it's off course, but can turn out to be a very accessed project, mainly by the Raspberry Pi board community. And Processing is directly related to Arduino project.
See:
[Create Button in Processing]

Button.
(Goal: Click on one of the colored shapes in the center of the image to change the color of the background.)
int rectX, rectY;      // Position of square button
int circleX, circleY;  // Position of circle button
int rectSize = 90;     // Diameter of rect
int circleSize = 93;   // Diameter of circle
color rectColor, circleColor, baseColor;
color rectHighlight, circleHighlight;
color currentColor;
boolean rectOver = false;
boolean circleOver = false;
void setup() {
size(640, 360);
rectColor = color(0);
rectHighlight = color(51);
circleColor = color(255);
circleHighlight = color(204);
baseColor = color(102);
currentColor = baseColor;
circleX = width/2+circleSize/2+10;
circleY = height/2;
rectX = width/2-rectSize-10;
rectY = height/2-rectSize/2;
ellipseMode(CENTER);
}
void draw() {
update(mouseX, mouseY);
background(currentColor);
if (rectOver) {
fill(rectHighlight);
} else {
fill(rectColor);
}
stroke(255);
rect(rectX, rectY, rectSize, rectSize);
if (circleOver) {
fill(circleHighlight);
} else {
fill(circleColor);
}
stroke(0);
ellipse(circleX, circleY, circleSize, circleSize);
}
void update(int x, int y) {
if ( overCircle(circleX, circleY, circleSize) ) {
circleOver = true;
rectOver = false;
} else if ( overRect(rectX, rectY, rectSize, rectSize) ) {
rectOver = true;
circleOver = false;
} else {
circleOver = rectOver = false;
}
}
void mousePressed() {
if (circleOver) {
currentColor = circleColor;
}
if (rectOver) {
currentColor = rectColor;
}
}
boolean overRect(int x, int y, int width, int height)  {
if (mouseX >= x && mouseX <= x+width &&
mouseY >= y && mouseY <= y+height) {
return true;
} else {
return false;
}
}
boolean overCircle(int x, int y, int diameter) {
float disX = x - mouseX;
float disY = y - mouseY;
if (sqrt(sq(disX) + sq(disY)) < diameter/2 ) {
return true;
} else {
return false;
}
}

Source: https://processing.org/examples/button.html
[Create Button in Python Tk]

from tkinter import *
class Window(Frame):
def __init__(self, master=None):
    Frame.__init__(self, master)
    self.master = master

    # widget can take all window
    self.pack(fill=BOTH, expand=1)

    # create button, link it to clickExitButton()
    exitButton = Button(self, text="Exit", command=self.clickExitButton)

    # place button at (0,0)
    exitButton.place(x=0, y=0)

def clickExitButton(self):
    exit()

root = Tk()
app = Window(root)
root.wm_title("Tkinter button")
root.geometry("320x200")
root.mainloop()

Source: https://pythonbasics.org/tkinter-button/

@rtek1000  Before getting into Python I would like to stress that constructive criticism is always welcome. In my earlier post I was only trying to say is that my goal is to keep things as simple for users as possible without needlessly imposing restrictions on how they work.   That is the lens I use for any changes I make.
Now for Python.   I think it would be fairly easy to supply difference language mappings to the builder.
It's actually designed that way.   I'm just not sure that I could add any value to what is already out there.
Now I haven't done much with python over the years so maybe someone could educate me.
Doing a quick google search shows at least two decent GUI builders for Python.
ActiveState GUI Builder (using grid layout)
http://spectcl.sourceforge.net/
and the faq and how to get source:
http://aspn.activestate.com/ASPN/Mail/Message/komodo-announce/3355346
PAGE v3.0 by Stewart Allen (using placer layout)
http://page.sourceforge.net/
I'm sure there are more that would be revealed with a more detailed search.
Of course, again I don't really know the strengths or weaknesses of what is available.

@rtek1000 -- thanks for the suggestions regarding alternate targets for the Builder. The way Paul designed it makes it quite flexible in generating different output formats.
I am going to close this issue as the primary topic/concern regarding the ability to change the Builder project folder has been addressed (and included in the upcoming Builder 0.11.0-rc5). If you would like to continue the other discussions, please open a separate issue. thanks!

Thank you.


Llama v2 70b

can you bring in the main exllama's support for 70b and cut a release please?

Give me a sec, will be done soon.

Wheels are uploaded: https://github.com/jllllll/exllama/releases/tag/0.0.7


[cluster_test] Tag client, faucet images with nightly_tested

Summary

We lookup the upstream_xxxxxx tag on libra_e2e and tag client and faucet images using it
Make fn tag_image() generic enough so that it can be used in multiple places
Update fn tag_tested_image() so that it tags client, faucet images in addition to libra_e2e
Create fn get_upstream_tag() which fetches the upstream_xxxxxx tag for libra_e2e:nightly image
Refactor the logic of fetching images into fn get_images()

Testing

Tested using a test tag ankush_test_tag and verified that libra_e2e, libra_client and libra_faucet got tagged correctly

Closes https://github.com/libra/libra/issues/1277

@bors-libra r+

:pushpin: Commit 8ecfcc1 has been approved by andll

:hourglass: Testing commit 8ecfcc1c4c8363c2c357448c207477aebcb78053 with merge 33959fe46f4a41006ca7a3ffa5183fdbfde42bc7...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: andll
Pushing 33959fe46f4a41006ca7a3ffa5183fdbfde42bc7 to master...


fix: bump pg-data-sync version due to rds at 12.5 now.

use pg-data-sync:12 image which is based on postgres 12 which matches rds version.

Oops, sorry for not merging sooner!! 🙌


stretch set to install gazebo9 in base.yaml

Hi,
I thought stretch could only install gazebo 7. In https://github.com/ros/rosdistro/blob/3fdab7657c8e10c29edb9c34538b09b118f5593a/rosdep/base.yaml, it is setting it to gazebo9. When trying to install ROS kinetic, it wont allow gazebo9 to install and therefore causing errors. Is there a way of changing it back to gazebo7?
I'm using raspbian Stretch on raspberry pi 3b+

If you ask for gazebo7 you can get gazebo7 we changed the default to be gazebo9. More info on the change is here: https://github.com/ros/rosdistro/pull/19843
You can always setup your own rosdep rules to override our defaults if you need something different for your platform.


Enhanced queries/filters

@solnic I'm not sure why I asked you about filters since they were already there. Anyway, I decided to improve them. Are you OK with renaming queries to filters? It's internal so affects nothing, it just looks better: if filter.(payload) vs if query.(payload).
In my current plan to support subscribe(:foo, log_level: %i(info warn error)) that is array filters

Looks good. We could also support advanced filters via dry-logic predicates (something to consider, defo not in this PR).

I love it 👍

@solnic @timriley how about adding support for procs?
subscribe(:foo, log_level: -> level { %i(info warn error).include?(level) })

Strongly in favor!

On 19 Feb 2019, at 7:50 pm, Nikita Shilnikov<EMAIL_ADDRESS>wrote:
@solnic @timriley how about adding support for procs?
subscribe(:foo, log_level: -> level { %i(info warn error).include?(level) })
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


refactor config loading

This rewrites the reloadConfig to using chained Promises, and then uses that to chain registration of the navigation listener, to happen after initial config load

Covered in #5


Closes #195

Description
Added Oddish vs. Evenish Solution
Issue No.- #195

Type issue number after hash(#)

Checklist

[ ] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

Invalid PR


Improved geometry tracking

Instead of calculating all of the linescans at the start in the makeScene function, we should keep track of individual module relative position in the scene, then calculate the linescan on the fly based on the user's query of a certain module, with a certain number of points.  Right now, if you want to query row 1, then query row 3, you need to re-create the scene.

This would fix #25 as well.

v_2_5 fixes this


Login without a region.

The API has the option to log in without specifying a region.
Let's add support for that as it will make the login process more straightforward.

Saw that you did most of the work, so I have added the small needed changes to this already open pr
https://github.com/ianmaciel/dart_ewelink_api/pull/19


Systemwide Pointers To Active Version of PowerShell Core

OpenSSH just got a new parameter for specifying the default shell - but it appears it must be full path specified: https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH
It is not clear whether it can receive an environment variable (but should be able to in my opinion).
This issue https://github.com/PowerShell/PowerShell/issues/1354 is asking for a pointer to the default powershell core remoting end point.
I'm not sure I understand not enabling PowerShell Core's configuration to self-publish what active version or folder should be used for these activities.
The alternatives to these would seem to be confusion in one or more of these ways:

Everyone creating their own mechanisms for tracking the desired version of powershell core they want to be primary
Everyone creating their own mechanisms for probing the latest version of PowerShell core (e.g. when a full path is required like OpenSSH DefaultShell)
Inability to find latest PowerShell Core when running a bit of probing code does not work (OpenSSH DefaultShell)
Lack of simple coordination between wiring up various components to powershell core - even ones out of the same open source team.

Among other problems, relying on the path does not allow for Windows PowerShell to be the system level powershell while all stipulated uses of PowerShell Core have a way to easily find (a) that is present (especially if at a custom path) and (b) what is the active version.
The implementation does not need to be heavy handed, for instance:

Any pointers could be standardized environment variable names that are optional (but can be relied upon as the authoritative source when they do exist).  [That said I would prefer they always exist because it serves as a possible easy "is Powershell core installed" check - even when using custom install folders for powershell core (and yes I would assume the risk that someone uninstalled without cleaning the var by doing a test-path)]
They could (SHOULD) require a special switch in the PowerShell Core installer to be changed to the version being installed (so that one can push and test a prospective version before making it primary)
Any new, interface points like OpenSSH's "DefaultShell" would be more likely to be built the first time around to allow an environment variable if it was known that PowerShell Core had an authoritative one in which it published the active version.
If an individual chose to they could include the active powershell core environment variable on their path to prevent the need for constant path add/removes (something that is frequently done incorrectly)

I am considering adding the ability to optionally set one or more "active powershell core" pointer environment variables (https://github.com/DarwinJS/ChocoPackages/issues/44) and it would be great if it was to a name agreed on this project - otherwise I can simply implement it as a custom value-add of using the chocolatey package to install powershell core.
Apologies if this has been handled somewhere and I've missed it.

In beta.9, the msi installer will add $pshome to %PATH% so you should be able to just rely on pwsh to start PSCore6.  In the future, we have a different tracking issue to determine how to support enumerating and starting side-by-side versions of PSCore6.

Hmm - yeah I can't add the $pshome reference to the openssh key which claims it needs a full path.  The openssh installer also runs in Windows PowerShell by default - so also won't know what $pshome is.
This approach, nor the one in https://github.com/PowerShell/PowerShell/issues/4836, seems to allow an administrator to stipulate a system level version for compatibility - regardless of who might install new additional versions beyond a known compatible one.

@DarwinJS Can we close the issue? Seems we have a stable distribution model now.

Yes it looks good now.  Thanks!


Scoped module declarations

🔍 Search Terms
scoped module declarations, scoped globals, scoping global types
✅ Viability Checklist

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
In todays web ecosystem that's getting more complex and feature-rich it's very hard to get the desired functionality by declaring normal modules. I will cover one primary example so you can understand the issue and how it would be solved, primarily through vitest global test context. Vitest offers you a way to use setup files to inject functions/other utilities into their context by using a beforeEach hook. The way you would type what you passed into it is like the following:
declare module "vitest" {
    export interface TestContext {
        foo: typeof foo
        bar: typeof bar
    }
}

this makes it globally available in all test suites. BUT, here's the problem. let's say you add integration tests as well, and you have another setup file that adds the following to the test context:
declare module "vitest" {
    export interface TestContext {
       integration: typeof integration
    }
}

Well, this creates an issue where whenever you try to access these globally defined contexts you have no idea if they are actually defined in the context they are running in, because the normal test suite has foo and bar, and the integration test suite has integration defined in the context. If you try to use foo in integration tests TS wouldn't complain but this would fail.
My idea is the following
// Define a unique `scope` keyword that scopes the following module augmentation to specific files that match a glob pattern
declare module "vitest" scope "**/*.unit.test.*" {
    export interface TestContext {
        foo: typeof foo
        bar: typeof bar
    }
}

This would override the module ONLY in files that match the scope, namely, in this case .unit.test.* files and then if we tried to use the foo or bar functionalities inside of there it wouldn't work. So to fix the problem from above, one would simply do the following:
// This overrides the unit.test suite
declare module "vitest" scope "**/*.unit.test.*" {
    export interface TestContext {
        foo: typeof foo
        bar: typeof bar
    }
}
// This overrides the integration.test suite
declare module "vitest" scope "**/*.integration.test.*" {
    export interface TestContext {
        integration: typeof something
    }
}

now in your integration tests you could do:
it("works", ({ integration }) => {
  // this is defined
  integration.something
})

and in your unit tests:
it("works", ({ renderDevTools, integration }) => {
  // this is defined
  renderDevTools
  // this is NOT defined and Typescript would complain
  integration
})

other useful usecases:

*.server.ts => make window object undefined
*.client.ts => make process object undefined
help framework authors / normal users declare globals in specific files where they are exposed
help framework authors / normal users inject custom utilities into specific functions/files

📃 Motivating Example

Allows you to create multiple overrides in specific contexts giving you actual typesafety instead of a potential footgun
Allows framework authors to exclude/include specific utilities/globals in places where they should be included/omitted for you, without you needing to guard against it (like window and process objects in SSR frameworks like Remix/React Router and Next.js)
Allows third party tooling to provide you with scoped globals without you having to configure anything manually
and more...

💻 Use Cases

To make process object undefined in client only files
To make window object undefined in server only files
There are no workarounds for this, the only thing you could do is mark the object as undefined so you don't forget to add a ? in front of it so it doesn't crash your application if used somewhere where it's not supposed to be used

The current workaround to achieve this behavior would be to include multiple tsconfig.json files that import different module declarations, but a first-party solution would be much nicer to have!

This isn't really practical (or even well-defined in my opinion). Certainly for expression-level code, you could say that foo is only accessible in certain files, but the type-level interpretation of this is confusing.
To simplify to something shorter, let's say we do
/* Ambient declaration */
declare module "SomeModule" scope "foo/*.ts" {
  interface SomeModule {
    foo: string;
  }
}

/* foo/something.ts */
import { barFunc } from "../bar/other.js"
import { SomeModule } from "SomeModule"

// Is this a legal call?
barFunc(SomeModule);

/* bar/other.ts */
export function barFunc(x: { foo: string }) {
  console.log(x.foo);
}

Should we interpret the relation from SomeModule -> { foo: string } in the context of foo (it passes), or bar (it fails) ? There are certainly arguments both ways here, and no matter which way you land, 30% of devs are going to call this broken based on the actual semantics of how bar is executing.
Currently, type operations are location-agnostic, so we'd have to completely revamp the checker so that all operations also have a "where it happened" parameter, which would also render type result caching basically useless since any new file could have a different view of any type.
It's also very confusing that you could have a setup like
/* Ambient declaration */
declare module "SomeModule" scope "stringland/*.ts" {
  interface SomeModule {
    foo: string;
  }
}
declare module "SomeModule" scope "numberland/*.ts" {
  interface SomeModule {
    foo: number;
  }
}

so that two different references to the same type SomeModule are now somehow incompatible.
The only way to make this make sense is to run the compilations separately, which is exactly what the tsconfig-based solution is. It's certainly possible that could be made more ergonomic, but I don't think this is the right solution to the problem at hand.

As I have no intimate knowledge of TypeScripts' inner workings, I didn't expect it would create such issues with caching.
I get where you're coming from with the first example, and I'd love to see if there's a way to find a more ergonomic solution that doesn't cause you to have to rework TypeScript from the ground up.
Would this be maybe achievable through some other means but with the same functionalities?
For example, would it be possible to maybe define tsconfig.workspaces.json, which would support this functionality, make it more ergonomic and easier to set up while still maintaining the functionality of being able to scope files?

While I wished we had something like that in TS, I do recognize the issues this would bring in the proposed form. Perhaps an alternative would be to make it possible for editors (like VSCode) to run multiple tsconfig.json files simultaneously in the same root directory. The problem I see with that approach is performance for large projects, because suddenly you'd have to run the TS server 2 or 3 times for each configuration, where already one might be causing the editor to struggle.
Perhaps TS could somehow share context/cache between multiple servers for types that are unaffected by the differences in the configuration (perhaps that could be enforced by forcing both configs to extend from the same base config).
One thing that is impossible to do today AFAIK is do what OP mentioned - have one subset of test files use a different global types when they're siblings in the filesystem directory. Would be great if there was a way to solve this.


[server] ensure per-client subscription is added when creating a proxy client

Description
In sensu/sensu-settings#40 we added per-client subscriptions which are a requirement for per-client native silencing added in 0.26, but this implementation doesn't cover proxy clients.
When processing events, the server calls retrieve_client to request client data from the registry using the client name. If a client with is not defined, we create a minimal entry in the client registry to represent the proxy client.
This change ensures that per-client subscriptions are added when a proxy client is registered.
Related Issue
Closes #1439
Motivation and Context
Fixes per-client silencing for proxy clients.
How Has This Been Tested?
Added a unit test to ensure proxy clients are created with a per-client subscription.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Not sure what we should do to handle this for existing proxy clients... cc/ @portertech

@cwjohnston this fix is sufficient :+1: Existing JIT clients will need to be deleted or updated (via POST /clients) to have the client sub required for client silencing. Any attempts to bridge the transition/upgrade would create a performance impact, requiring client inspection on registry update etc.


iOS doesn’t turn on bluetooth if disabled when Scanner is opened

Describe the bug
On entering the scan screen on ios side the device asks for bluetooth permission "Bluetooth is used to allow sharing VCs with another device". The expected behaviour post this is to ask the user to turn on the bluetooth.
Steps to reproduce the behaviour:

Install the app. Allow the local network request.
Add id. keep the bluetooth off
go to the scan screen. You will receive "Bluetooth is used to allow sharing VCs with another device" allow it.
now if you check, the bluetooth will not be enabled.

Expected behaviour
Post giving the permission to use bluetooth, the app should request to turn on bluetooth.
Screenshots

Smartphone (please complete the following information):
Device: iPhone 11
OS: iOS 16.2j
Inji app version: [0.4.1]
MOSIP Version: [e.g. 1.0.0]
MOSIP server: https://api.collab.mosip.net/

The following change is available on branch=0.9 & on branch=develop as part of the 17th March, 2023 release.
PR for mosip/inji(branch=develop): https://github.com/mosip/inji/pull/655,
commit: https://github.com/mosip/inji/commit/aff1c4f7b96d27f1c8f54e62d3f03a7086473f35
PR for mosip/inji(branch=0.9): https://github.com/mosip/inji/pull/653
commit: https://github.com/mosip/inji/commit/4c2ca4b0ea400cb29cb59ee6a87106e2542023da

Tested this issue in the new build, the issue is not observed anymore, when the Bluetooth is turned off, the camera is not opening, it is working as expected, hence closing the bug
Screenshot :
https://user-images.githubusercontent.com/102220709/227188780-5c57b169-8312-4c8d-81ac-3ebc91f6461c.mp4
Tested on :
Device: iPhone 11
OS: 15.4.1
Inji app version: 0.4.1 (29) in test flight
MOSIP Version: 1.2.1
MOSIP server: qa-121.mosip.net


fix: Use named import for MUI components

Summary
Fix breaking imports
Single Cell Team noticed that importing SDS Autocomplete throws the following error:
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

And the root cause seems to be SDS TS -> JS transpiler didn't take ESM syntax into account when transpiled the code to CJS, so it resulted in importing the whole module instead of the intended module default export.
For example,
// packages/components/dist/index.cjs.js
var Autocomplete = require('@mui/material/Autocomplete');

Autocomplete is the whole module object, when we just want Autocomplete.default
// we got the whole export module
Autocomplete {
  autocompleteClasses: [Getter],
  createFilterOptions: [Getter],
  default: [Getter],  // <--------------- we just want this, which is what ESM syntax does, but not for CJS
  getAutocompleteUtilityClass: [Getter]
}

The solution is to avoid importing MUI components through their component directories and use import { Autocomplete } from '@mui/material' instead, like so:
import { Autocomplete } from "@mui/material";

This way the transpiled cjs file will have the correct export:
var material = require('@mui/material');
var Autocomplete = material.Autocomplete; // This is the default export component we want

Checklist

[ ] Default Story in Storybook
[ ] LivePreview Story in Storybook
[ ] Test Story in Storybook
[ ] Tests written
[ ] Variables from defaultTheme.ts used wherever possible
[ ] If updating an existing component, depreciate flag has been used where necessary
[ ] Chromatic build verified by @chanzuckerberg/sds-design

Aww really appreciate your kind words, Masoud! Right back at you ❤❤❤!!


xf_verify_certificate() fgetc read fails

Hello, sorry for my english, function xf_verify_certificate() may produce infinity loop if run non interactive with closed STDIN (start-stop-daemon).
feof(stdin) checks for EOF, fgetc() return EOF on error.
Need to check ferror(stdin) or answer==EOF for reads success.
Patches(git diff): https://github.com/koi8-r/Patches/tree/master/FreeRDP
Example: https://gist.github.com/koi8-r/cfe0e23318e1d2b1730e
Example with xfreerdp exec: https://gist.github.com/koi8-r/da3cfb07a9272572b059
PS: May be clearerr before fgetc, or best answer==EOF.

Closing due to lack of activity.
Reopen/create a new issue if still relevant.


[ko] Unnecessary item is displayed in left-side navigation menu

This is a Bug Report

Problem:
[ko]
In https://kubernetes.io/ko/docs/reference/setup-tools/kubeadm/,
unnecessary item is displayed in left-side navigation menu.

English version

Korean version

Proposed Solution:

~Add content/ko/docs/reference/setup-tools/kubeadm/generated/_index.md~

---
title: "Kubeadm Generated"
weight: 10
toc_hide: true
---

Page to Update:
https://kubernetes.io/ko/docs/reference/setup-tools/kubeadm/

/language ko
/assign

Adding content/ko/docs/reference/setup-tools/kubeadm/generated/_index.md does not resolve this issue.
(PR #27134 adds that file, but the menu item remains in the deploy preview.
Is there anyone that has an idea?

/triage accepted

Is there any possibility that adding no_list: true can resolve this issue?
(Ref for no_list: true: here)

@jihoon-seo Thank you for the bug report.
In my perspective, this bug is related with layout of website. (toc_hide seems not applied for all localized contents)
Let me check where the bug is from.
I suspect~
this file.
./layouts/partials/sidebar-tree.html

@jihoon-seo I found a way to resolve this. after some test I will make a PR. Thank you for the bug report!


Minor: Added reference to cloned physical expression

Which issue does this PR close?

Closes #.
Rationale for this change
While working on one of the sqllancer bugs, noticed that an expression wasn't receiving reference although it should expect one.

What changes are included in this PR?
Added reference

Are these changes tested?
Yes

Are there any user-facing changes?

Sorry is someone able to close this, I didn't catch that it was being dereferenced immediately

@jonathanc-n author of the PR should be able to close it


Initial commit for ScriptDefinition

Add a parameterset called ScriptDefinition. This parameterset has a parameter called ScriptDefinition which takes in a script in the form of a string. Rename the default parameter set to File.

Hi Quoc. Are the failing tests taken care of?

looks good..
I am assuming there are no breaking changes here.

The only thing that may cause a breaking change is the ParameterSet. But I put the file path into the default parameter set so that shouldn't break any thing that depends on scriptanalyzer.

great. then we can leave the major version as is

merge..

Merged. Thanks


Test issue

This is a test issue and things need to be done....

Closing out -- was just for testing!


"Unable to load vulnerability database"

safety version: 1.9.0
Python version: 3.7
Operating System: Windows 10

Description
Savety does not work and only outputs "Unable to load vulnerability database".
Maybe this is just a temporary issue (or something local?).
If this is not an issue for anyone else, then please point that out and just close this issue.

It now only works sporadically.

It seems to work again.

Hello @Spenhouet / Sebastian.
Our service was down twice for less than a minute yesterday. We were also down for a third time, and this was for about one full minute. It could be that you were trying to access our service exactly at those moments, or perhaps there indeed was some local issue for you.
In any case, I'm glad to see that everything is working again for you now.
Tristan


Paket.pack: add support for nuget dependencies conditional on target framework

As of Nuget 2.0, support for package dependencies that that are bound to specific target frameworks has been included. For instance:
<dependencies>
   <group>
      <dependency id="RouteMagic" version="1.1.0" />
   </group>

   <group targetFramework="net40">
      <dependency id="jQuery" />
      <dependency id="WebActivator" />
   </group>

   <group targetFramework="sl30">
   </group>
</dependencies>

I'm not entirely sure how this feature would fit in with the design philosophy of paket, but I'd be interested to see having something like this added to the paket.template syntax.

First question: how could this look in our current paket.template syntax?
/cc @mavnn

I guess it could be worked out like this:
dependencies
    RouteMagic 1.1.0
dependencies targetFramework=net40
    jQuery
    WebActivator

I have a few misgivings on the compatibility of this feature with the overall paket design philosophy. For example:
dependencies targetFramework=net35
    Newtonsoft.Json ~> 4.0
dependencies targetFramework=net40
    Newtonsoft.Json ~> 5.0

requires that two separate versions of the same package be present in one environment, which AFAIK is not supported by paket.

yes.
dependencies targetFramework=net35
    Newtonsoft.Json ~> 4.0
dependencies targetFramework=net40
    Newtonsoft.Json ~> 5.0

would be problematic, but only if your app uses both targetFrameworks. If not you can resolve the conflict with paket.

with new TFM (target framework monikers) and .NET Core that's going to be really useful (needed?) because for some frameworks the library/app depends on different packages.
Some examples:

some bcl assemblies are split in multiple assemblies/packages. So in .net 4.5 is a package, in .net core multiple packages
FSharp.Core for .NET Core in a different package ( Microsoft.FSharp.Core.netcore ) instead of FSharp.Core package (but that should be temporary i hope)

for example Chessie fsprojects/Chessie#43 ( .NET 4.6 and .NET Core with dnxcore50 atm but i am going to move it to netstandard asap )

We need this too since we have Xamarin packages (which of course use multiple frameworks, and our iOS frameworks obviously can't depend on Android dependencies).

I have a need for this as well. But I'll also have to specify empty groups to be able to end up with the following:
<dependencies>
    <group targetFramework=".NETFramework3.5">
        <dependency id="TaskParallelLibrary" version="1.0.2856" />
    </group>
    <group targetFramework=".NETFramework4.0" />
</dependencies>

Maybe this could then become:
dependencies targetFramework=net35
    TaskParallelLibrary >= 1.0.2856
dependencies targetFramework=net40

Type OptionalPackagingInfo at TemplateFile.fs has Dependencies and FrameworkAssemblyReferences, instead of having a list, they should have a map or tuple of groupname*list pairs.
The framework assemblies also have this targetFramework:
<frameworkAssemblies>
  <frameworkAssembly assemblyName="mscorlib" targetFramework=".NETFramework4.6.3" />
  <frameworkAssembly assemblyName="System.Core" targetFramework=".NETFramework4.5" />
  <frameworkAssembly assemblyName="System.Core" targetFramework=".NETFramework4.6.3" />
</frameworkAssemblies>

I see #2428 was merged, I haven't been able to figure out a way to generate:
<group targetFramework="net451" />

Basically specify no dependencies for a target framework.

@seanamosw Please open a new issue if this is still the case.


Bug: REVISION variable not up to date in Makefile-options

This is kind-of the same issue like in BoCA: https://github.com/enzo1982/BoCA/issues/8
In https://github.com/enzo1982/smooth/blob/master/Makefile-options, the REVISION is set to 0, although the latest shipped version is 0.9.6.
This is probably not an issue for most people, but it leads to incorrect file names for libraries which is a (small) problem for people packaging smooth (I am doing this for macports).
I think it should be set to 7, assuming the upcoming version is 0.9.7.

Please see my answer in enzo1982/BoCA#8. It's the same here, compatibility level, not release micro version number.


Made some changes in accordance with clippy

Made some changes in accordance with clippy

Don't do it，because I just adjusted some tips that might cause performance problems, and I didn't make adjustments for some insignificant problems.


Interferences with ray test

I was trying to use interferences_with_ray unsuccessfully. After some debugging I realized I needed to call update after inserting the objects for them to be found. I added this test to find the problem, and I think it might be useful for more people to have it in the project.

Thanks @seppo0010


1.69.4 is not thread-safe

This recent optimization took out the mutex for synchronizing stdin access. Although it indeed has a little performance gain on MRI for linux and mac, it turns out stdin.write with multiple arguments is not thread safe on MRI for windows or JRuby, which causes corrupted decoding of messages due to incorrect order of data sent.
https://github.com/ntkme/sass-embedded-host-ruby/blob/80d5b01adbff582c35c739f3825ba2f261b23443/lib/sass/embedded/connection.rb#L62

There is no difference on dart-sass itself in terms of 1.69.3 and 1.69.4. So if you run into this problem, please stay on 1.69.3 until the next version of sass-embedded is released.

1.69.5 with the fix is now available.


Construct full URI before checking existence

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/cherrypick release-0.11


Querying duplicated fields regression from 6.4.1

Hi Folks, just wanted to note a small regression we are seeing when upgrading from 6.4.1 to 7.x around duplicated fields and contains/in linq queries when the field is nullable.
So given this document:
public class Person
{
    public Guid Id { get; set; }

    [DuplicateField]
    public Guid? ChildId { get; set; }
}

In 6.4.1 both of these tests pass, but in 7.8 they second one now fails.  Based on the error message I'm guessing this will be resolved at some point 😁 but just wanted to raise it as it's been an area where we've needed to update code in a few places as part of the upgrade to v7 for our codebase.
[Fact]
    public async Task filtering_by_null_ids_works()
    {
        var p1 = new Person { ChildId = Guid.NewGuid()};
        var p2 = new Person { ChildId = Guid.NewGuid()};
        theSession.Store(p1,p2);
        await theSession.SaveChangesAsync();
        Guid?[] ids = [p1.ChildId];
        var results = await theSession.Query<Person>()
            .Where(x => x.ChildId.In(ids))
            .ToListAsync();
        results.Single().ChildId.ShouldBe(p1.ChildId);
    }

    [Fact]
    public async Task filtering_by_non_null_ids_using_value_fails_regression_from_641()
    {
        var p1 = new Person { ChildId = Guid.NewGuid()};
        var p2 = new Person { ChildId = Guid.NewGuid()};
        theSession.Store(p1,p2);
        await theSession.SaveChangesAsync();
        Guid[] ids = [p1.ChildId.Value];
        var results = await theSession.Query<Person>()
            .Where(x => x.ChildId!.Value.In(ids))
            .ToListAsync();
        results.Single().ChildId.ShouldBe(p1.ChildId);
    }

Here's the error message & stack trace:
Marten.Exceptions.BadLinqExpressionException
Marten does not (yet) support the method Value in duplicated field querying
   at Marten.Linq.Members.DuplicatedField.FindMember(MemberInfo member) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Members/DuplicatedField.cs:line 236
   at Marten.Linq.Parsing.LinqInternalExtensions.MemberFor(IHasChildrenMembers collection, Expression expression) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/LinqInternalExtensions.cs:line 96
   at Marten.Linq.Parsing.Methods.IsOneOf.Parse(IQueryableMemberCollection memberCollection, IReadOnlyStoreOptions options, MethodCallExpression expression) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/Methods/IsOneOf.cs:line 25
   at Marten.Linq.Parsing.WhereClauseParser.VisitMethodCall(MethodCallExpression node) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/WhereClauseParser.cs:line 92
   at Marten.Linq.Parsing.WhereClauseParser.Visit(Expression node) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/WhereClauseParser.cs:line 41
   at Marten.Linq.SqlGeneration.Statement.ParseWhereClause(IReadOnlyList`1 wheres, IMartenSession session, IQueryableMemberCollection collection, IDocumentStorage storage) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/SqlGeneration/Statement.WhereParsing.cs:line 57
   at Marten.Linq.CollectionUsage.BuildTopStatement(IMartenSession session, IQueryableMemberCollection collection, IDocumentStorage storage, QueryStatistics statistics) in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/CollectionUsage.Compilation.cs:line 38
   at Marten.Linq.Parsing.LinqQueryParser.BuildStatements() in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/LinqQueryParser.Statements.cs:line 32
   at Marten.Linq.Parsing.LinqQueryParser.BuildListHandler[T]() in /Users/alexhenderson/dev/jasperfx/marten/src/Marten/Linq/Parsing/LinqQueryParser.Handlers.cs:line 70
   at Marten.Linq.MartenLinqQueryable`1.ToListAsync[TResult](CancellationToken token)
   at LinqTests.Bugs.Bug_3xxx_trouble_with_repeated_include_and_document_with_duplicated_field

It was just a gap in our existing test coverage. LINQ is the gift that never stops giving.

hehe I figured as much 😄  not super urgent as it can be worked around of course, just thought I would flag it up as a minor thing.  All that being said the LINQ support in Marten is amazing in what it does support!


scarab: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fifty-six/scarab/releases.
meta.description for scarab is: Hollow Knight mod installer and manager
meta.homepage for scarab is: https://github.com/fifty-six/Scarab
meta.changelog for scarab is: https://github.com/fifty-six/Scarab/releases/tag/v<IP_ADDRESS>
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/bfmzx6dmksahn84g1v6z97jqxlsq1s3n-scarab-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/bfmzx6dmksahn84g1v6z97jqxlsq1s3n-scarab-<IP_ADDRESS>

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
scarab

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bfmzx6dmksahn84g1v6z97jqxlsq1s3n-scarab-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bfmzx6dmksahn84g1v6z97jqxlsq1s3n-scarab-<IP_ADDRESS>
ls -la /nix/store/bfmzx6dmksahn84g1v6z97jqxlsq1s3n-scarab-<IP_ADDRESS>/bin

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

1 package built:

scarab

Maintainer pings
cc @huantianad for testing.

Would you be OK to backport this to release-22.11 please?


Allow the server to be started with no certificate for testing

The ca, cert, and key properties are optional in the configuration, but at the moment they are required by the start() method. If they are not provided, _addTls() throws a File Not Found exception.
This patch starts the server in insecure mode if no values are provided for these config parameters.

Good suggestions， thanks!


Create example program: Adaptive Quantum Phase Estimation

e.g. https://arxiv.org/abs/2206.12950

We should implement the adaptive random walk phase estimation algorithm from https://arxiv.org/abs/2102.01682 that uses branching on mid-circuit measurements and dynamic rotation angles.
Copying the numbers from https://arxiv.org/abs/2206.12950, the Guppy code for a basic example on a single qubit could look something like this:
@guppy
def random_walk_phase_estimation(
   eigenstate: Callable[[], qubit],
   controlled_oracle: Callable[[qubit, qubit, float], tuple[qubit]],
   num_iters: int,
   reset_rate: int,
   mu: float,
   sigma: float
) -> qubit:
   """Performs the random walk phase estimation algorithm on a single qubit for some
   Hamiltonian H.

   Arguments:
      eigenstate: Function preparing the eigenstate of e^itH
      controlled_oracle: The oracle circuit for a controlled e^itH
      num_iters: Number of iterations to run the algorithm for
      reset_rate: Reset the eigenstate every x iterations
      mu: Initial guess for the eigenvalue
      sigma:
   """
   mu_init, sigma_init = mu, sigma
   tgt = eigenstate()

   for i in range(num_iters):
      aux = h(qubit())
      aux = rz(h(aux), 1 - mu/sigma)
      aux, q = controlled_oracle(aux, tgt, 1 / sigma)
      if measure(aux):
         mu += sigma * sigma_init
      else:
         mu -= sigma * sigma_init
      sigma *= mu_init

      # Reset the eigenstate every few iterations to increase the fideltity of the algorithm
      if i % reset_rate == 0:
         free(tgt)
         tgt = eigenstate()
   return mu * 2

@guppy
def main() -> int:
   # As an example, use the Hamiltonian H := a*Z such that e^itH = rz(t*a).
   # The eigenstates of H are |0> and |1> with corresponding eigenvalues +- a*pi
   a = -0.5
   controlled_oracle = lambda q1, q1, t: crz(q1, q2, a * t)
   eingenstate = lambda: x(qubit())
   num_iters = 24  # To avoid underflows
   reset_rate = 8
   mu = 0.7951
   sigma = 0.6065

   eigenvalue = random_walk_phase_estimation(controlled_oracle, eingenstate, num_iters, reset_rate, mu, sigma)
   output("eigenvalue", eigenvalue)
   return 0

This would be my ideal way of implementing the algorithm. There are a few things to note:

range is not implemented yet (could be replaced with a while loop)
Makes heavy use of dynamic qubit allocation (could be refactor to take two static qubits as input)
Uses closures to provide the eigenstate and oracles (could be inlined in this example)


How to perform a project search for a symbol for certain file types?

When pressing SPC *, I can make a search for current symbol in project very easily. This is great. However, how can I narrow down the search to a specific file type list? E.g. I want to search for a symbol declaration in .h file, but the search result contains many usages of this symbol in .cpp file. How can I narrow down the search to only .h file?

Add -- -t h or -- -g '*.h' to the end of your search query. Arguments after a -- delimiter are passed directly to rg. You can run rg --type-list to see what types (for -t) it supports.

On a separate note: you have consistently ignored the issue templates in your issues, and disregarded requests to include your M-x doom/info.
Please include your M-x doom/info in every issue you create.


Create test for calculating interpolated value derivatives

The test CalculateInterpolatedValues exists for verifying that interpolation of the generalized coordinates is correct, but there isn't a similar check for calculation of the derivatives of the shape functions, including application of the Jacobian. The new test would check the interpolation to get strain (u') and change in rotation (q').

This was completed with the code restructuring PR #129


WILL NOT MERGE: library versioning and navigation prototype

A proof of concept for how we can render a library version table and optimal navigation among a library's assets at a specific (not-latest) version.
Would close the following issues if merged:
Ref #594
Ref #523
Ref #554
Ref #543
Ref #560
Ref #490
Ref #565
Ref #576
Ref #679
Ref #504

Most of the issues referenced have been closed, so closing this PR since main branch is mostly caught up.


Fix for failing POST methods

Previously, trying to add or remove a user from a list failed with an error
{"errors":[{"code":112,"message":"You must specify either a list ID or a slug and owner."}]}

This was despite passing both slug and owner as parameters to the setPostFields method.
After a lot of experimentation, it turns out that these endpoints required the data to be sent as application/x-www-form-urlencoded rather than multipart/form-data for the parameters to be recogised.
However, fixing this threw up another problem:  I was now receiving this error for both endpoints:
{"errors":[{"code":32,"message":"Could not authenticate you."}]}

It turns out that the POST parameters were not being correctly used to assemble the oAuth base string which is required for authenticated requests.
This pull request fixes both of these issues.
One thing to note, because of the change, you must call setPostFields before the buildOauth method like this:
        $json = $twitter
                ->setPostfields( $postFields )
                ->buildOauth( $url, $requestMethod )
                ->performRequest();

Hi, thanks very much for this PR. It seems to clear up a lot of issues. The problem is the requirement of setting the POST variables first.
This is effectively an interface, or API change, which would break compatibility for the many many people who currently use this. They'll do a composer update and it'll break their code.
Could you make this work with the current fluent interface API and then I'll run some tests and take a look.

I've added some logic that with rebuild the oAuth parameters upon setting post fields.  That means it can be used either before or after the buildOauth method.
        $json = $twitter
                ->setPostfields( $postFields )
                ->buildOauth( $url, $requestMethod )
                ->performRequest();

        $json = $twitter
                ->buildOauth( $url, $requestMethod )
                ->setPostfields( $postFields )
                ->performRequest();

I've just added another fix:  parameters were not being correctly encoded.  As per Twitter's guidelines (https://dev.twitter.com/oauth/overview/creating-signatures), parameters should be percent encoded before being added to the base string (where they are encoded again).
Before this fix, sending a parameter such as this would fail:
screen_name=user1,user2
With this fix, this parameter works as expected.

Hi @J7mbo -- did you have time to review this pull request?
Can I also suggest, after merging to master, you tag a 1.0.0 version?  That will make future improvements and bug fixes easier to track.

Hey Glen, I'm planning on taking a look this weekend. I agree on the tagging and also travis support with tests for each endpoint.

I've been taking a look at this today. I pulled your branch and I've been working on it here. I also added some tests.
With all these changes, we still are having issues with media/upload which I was rather hoping this PR would address. The small change seems to be form/multipart as a header but adding that makes no difference. Here's the failing test.
If we can work on getting this sorted too, I'll happily merge the PR as it'll have fixed the failing POST methods... and we can add more tests for each endpoint to prove it works.

I've got a fix for this, but I can't push it as I don't have access to the branch:
ERROR: Permission to J7mbo/twitter-api-php.git denied to glenscott.
Can you give me access please?

You can push the branch on your own fork and I'll fetch it from there :+1:

This fix at least gives you a valid response back -- I also had to change your test to look for image/png since it was escaped in the JSON encoded response.

It seems like it's working now, and I fixed the test as you suggested. Thanks a lot for your help on this one :-) Just getting travis working correctly and I'll merge over


⚠ Samsung has degraded performance

In 304439c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2711 ms

Resolved: Samsung performance has improved in bdaf6f2.


Hotfix multibyte lists #378

Hotfix multibyte lists #378

Hi, thanks for the PR!
There was some similar work done in #513, so I'm going to close this in favour of that since it aims to bring multibyte support to all the structures in Parsedown (I think it's probably about time we patch this everywhere). I hope this makes sense :)


Remove dependency on full DependencyInjection package

An Interfaces package was recently spun off from the main DI package (see https://github.com/aspnet/DependencyInjection/pull/195). EF should drop its dependency on the full package and take the Interfaces dependency instead. This will require a little bit of refactoring in the EntityFrameworkServiceCollectionExtensions class, but shouldn't be anything too bad.

Sending back to triage. We have code paths (notably the happy path for not web apps) that fully create the service collection and build a service provider from it. It doesn't look like this can be done using just the interfaces.
We also ActivatorUtilities for creating DbContext instances when AddDbContext is used.


Unable to run, if console is not present

Prerequisites

[x] Did you read FAQ section in readme.md?
[x] Did you test with the latest releases or commit ?
[x] Did you search for existing issues in Issues?

Description
I am unable to call the script from a PHP app. I guess it want's a console, but none is present, obviously. It fails with the following:
Traceback (most recent call last):
  File "/var/www/music/bin/PixivUtil2/PixivUtil2.py", line 1419, in <module>
    main()
  File "/var/www/music/bin/PixivUtil2/PixivUtil2.py", line 1221, in main
    set_console_title()
  File "/var/www/music/bin/PixivUtil2/PixivUtil2.py", line 928, in set_console_title
    PixivHelper.set_console_title(set_title)
  File "/var/www/music/bin/PixivUtil2/PixivHelper.py", line 376, in set_console_title
    sys.stdout.write(f'\33]0;{title}\a')
  File "/usr/local/lib/python3.7/dist-packages/colorama/ansitowin32.py", line 41, in write
    self.__convertor.write(text)
  File "/usr/local/lib/python3.7/dist-packages/colorama/ansitowin32.py", line 162, in write
    self.write_and_convert(text)
  File "/usr/local/lib/python3.7/dist-packages/colorama/ansitowin32.py", line 184, in write_and_convert
    text = self.convert_osc(text)
  File "/usr/local/lib/python3.7/dist-packages/colorama/ansitowin32.py", line 257, in convert_osc
    winterm.set_title(params[1])
AttributeError: 'NoneType' object has no attribute 'set_title'

Steps to Reproduce
Raspberry Pi 4, with Raspbian OS (linux)

get php 7.4
run snippet bellow:

<?php

shell_exec("/usr/bin/python3 /pathToPixivUtil2/PixivUtil2.py -s 8 -p y --sp=1 --ep=1");

get the error above

Expected behavior: run
Actual behavior: fail :)
Versions
20210421

well it supposed to be run from console. I don't use linux so I have no idea how to fix it.

I think you can reproduce it on a windows machine as well.

windows won't even hit that line
https://github.com/Nandaka/PixivUtil2/blob/master/PixivHelper.py#L369-L377


docs: Write error map elements to log for custom predicate

Per b/313661644

Hi @grayside, @averikitsch, could one of you pls review this PR soon? thanks!

@camiekim do you need me to merge as well or did you want to?

Thanks, @iennae. In the future, I'll make sure to include more context instead of just pointing to the bug and CL.


repairbox "download" command doesn't work as expected

The command  repairbox download bug manybugs:libtiff:2005-12-14-6746b87-0d3d51d
(same as mentioned in documentation)
throws error
usage: repairbox [-h] [--version]
{build,upload,download,install,uninstall,list,execute,launch}
...
repairbox: error: unrecognized arguments: manybugs:libtiff:2005-12-14-6746b87-0d3d51d

New CLI addresses this issue.


Make getindex on MetricProblem return a MetricProblem

It was previously returning a Problem. After a conversation with @pwochner, concluded that it should return a MetricProblem instead. I assumed the return value should have the same cost_function.
Care should be taken when merging with #13. One of the tests will clash and will need changing.

@mhauru would you mind syncing your fork's master branch and rebasing this PR on it?

Done


Add support for Laravel 6

This PR adds support for the upcoming Laravel 6.0 release. We had to upgrade to phpspec 5 for development, because<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>

I like it, but if we drop support for older PHP/Laravel versions we would need to release a new major version of the package.
That would mean everyone needs to go through the upgrade process or not ger future updates.

@felixkiss I see, however, bugfix support for Laravel 5.4 has ended over 2 years ago. I think that supporting from Laravel 5.5 and upwards is easier, especially given that allows us to bump the PHP version requirement to >=7.

Maybe now with Laravel 6 released it is a good time to release a new major version of this package as well. I’m guessing people will be checking many packages during the upgrade process.
What would you do?

I think dropping support for <5.5 is mandatory for the health of this project. But then there are two options regarding versions up until 5.8.

Mark a new major version with support for only ^6.0, or
Mark a new major version with support for >=5.5.* and ^6.0

I think keeping support for lower versions is fair for the community and I personally don't think supporting them for now is that much work. So I would go for option 2.

Right, so we have one last issue. The \Illuminate\Contracts\Translation\Translator interface was changed in https://github.com/laravel/framework/pull/29529. It was changed from Translator::trans() to Translator::get(). This causes the build for Laravel 6 to fail. They mention that the helper function __() was not changed. How should we adapt this change in this package, @felixkiss?

Yeah, I noticed that yesterday on the failing Travis builds. Is the helper function part of one of the packages we require?
If not, I could also see us releasing version 4.0 as Laravel 6 only. That would certainly make maintaining life easier.

The trans() helper is only available in the laravel/framework package. Maybe we could investigate how another rule package would solve this?
I see that https://github.com/spatie/laravel-validation-rules uses Rule objects instead of extensions, but that would still result in a breaking change.

Either check if method exists like I did here or only support Laravel 6.0 in the new version.

@felixkiss I've used method_exists so we can create a minor release that adds support for ^6.0.

Thanks for the work @erikgaal! I think I can look at this tomorrow.

@felixkiss You could release this as a new minor version, as it is backwards compatible and the version constraint still allows for Laravel versions 5.*. I think we should clean up and remove the version dependent code in the future and release a new major version with support for only ^6.0.

Thanks @erikgaal!


Added SimpleCompact Profile

@svr333 Can you confirm that the Like Button is visible in the profile and that it is not a square box.
Thanks.

Yes, i can confirm that like button is not a square. It shows a red heart when liked and empt heart when not liked. Font family is "Segoe Fluent Icons"

Okay cool.  Looks like my computer is not loading it correctly.


SPM command plugin the library '...' requires macos 10.13

I am new to Sources and setting up using SPM command plugin.

In the Package.swift file .package(url: "https://github.com/krzysztofzablocki/Sourcery.git", revision: "3a9e5f1014ac09b30727c01d2a0e1531dac30948") (use commit of 1.9.2 release, due to https://github.com/krzysztofzablocki/Sourcery/issues/1102 issue.)

$ swift package plugin --list output ‘sourcery-command’ (plugin ‘SourceryCommandPlugin’ in package ‘Sourcery’)

Running swift package --allow-writing-to-package-directory sourcery-command failed with error
error: the library 'ArticleCardFeature' requires macos 10.13, but depends on the product 'ComposableArchitecture' which requires macos 10.15; consider changing the library 'ArticleCardFeature' to require macos 10.15 or later, or the product 'ComposableArchitecture' to require macos 10.13 or earlier. and the same error for every  feature module.

Do I miss something in configuration?

Same issue, adding macOS made it go away, so it's not an underlying issue
[REDACTED] VoiceControl % swift package --allow-writing-to-package-directory sourcery-command
warning: 'swift-async-algorithms': [REDACTED]Modules/VoiceControl/.build/repositories/swift-async-algorithms-c3a8d752 is not valid git repository for 'https://github.com/apple/swift-async-algorithms', will fetch again.
Fetching https://github.com/apple/swift-async-algorithms from cache
Fetched https://github.com/apple/swift-async-algorithms from cache (0.06s)
warning: 'swift-async-algorithms': [REDACTED]Modules/VoiceControl/.build/repositories/swift-async-algorithms-c3a8d752 is not valid git repository for 'https://github.com/apple/swift-async-algorithms', will fetch again.
Fetching https://github.com/apple/swift-async-algorithms from cache
Fetched https://github.com/apple/swift-async-algorithms from cache (0.05s)
error: the library 'VoiceControlProtocols' requires macos 10.13, but depends on the product 'AsyncAlgorithms' which requires macos 10.15; consider changing the library 'VoiceControlProtocols' to require macos 10.15 or later, or the product 'AsyncAlgorithms' to require macos 10.13 or earlier.
error: fatalError

    platforms: [
        .iOS(.v17),
        .macOS(.v14) <-- works fine after adding this, but not on iOS alone
    ],

I can imagine that this could be a problem if it's a UI related iOS module.

Yeah this issue isn't related to Sourcery itself.
When you have Package.swift, you aren't actually saying that your app doesn't support macOS by writing .iOS only in platforms, this is just information what minimum version you support, if one is not provided for any platform Apple supports, it just uses default value for it, e.g. if you only had iOS it will still try to build your product for Mac when running build commands from command line, it's PITA but that's how SPM works currently


Pass in an normal object as a Config

This adds the ability to pass in a custom config that is just a plain object.  A user can still create a KubeConfig object and pass that in.   This update would allow a user to pass in a normal object instead of going through the process of creating their own KubeConfig object.

Pull Request Test Coverage Report for Build f347de11-ddb7-4119-9b38-3bb7d68b6690

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 76dd6a15-4866-4fab-ab2d-7434d0d05613:
0.0%

Covered Lines:
77

Relevant Lines:
77

💛  - Coveralls

@lance this might be relevant to what you were asking about


Allow to specify a default value on placeholder

I want to support that allow to specify a default value on placeholder as follow:
<dataSource type="POOLED">
  <property name="username" value="${db.username:postgres}"/>
  <property name="password" value="${db.password:Postgres}"/>
</dataSource>

This solution has been supported by the Spring Framework , logback, etc...
Note that : We should take to consider the : character has been used as placeholder key. (for backward compatibility)
What do you think this enhancement ?

For prototype see https://github.com/mybatis/mybatis-3/commit/241ba45d85af2eaf892631405885a4bddbe72427. In this changes, I does not take to consider backward compatibility yet.

I've updated the prototype via cbc6fe07d36a2ad7cfdeb90767809ff9601baeb7. In this version, backward compatibility has been taken to consider.
By default this feature is disabled .
When using this feature, a special property will specify as follow:
<properties>
    <property name="org.apache.ibatis.parsing.PropertyParser.enable-default-value" value="true"/>
</properties>

@emacarron @eddumelendez
Thanks for your reaction !!  I will submit a PR after adding some improvement.

I've improved the prototype via 0f057c2e30616e6fbf6975886e9ebf1ac3a7ffc3.
In this change, support to customize a separator characters.
When customizing separator characters(default is ":"), a special property will specify as follow:
<properties>
    <property name="org.apache.ibatis.parsing.PropertyParser.default-value-separator" value="?:"/>
</properties>

If ":" character has been used as placeholder key already, this mechanism is effective as follow:
<dataSource type="POOLED">
  <property name="username" value="${db:username?:postgres}"/>
  <property name="password" value="${db:password?:Postgres}"/>
</dataSource>

and If ternary operator has been used using OGNL in your sql already, this mechanism is effective as follow:
@Select("SELECT * FROM ${db.schema?:prod}.${tableName == null ? 'global_constants' : tableName}" ORDER BY ${orderByColumns})
List<SysConstant> findAll(@Param("tableName") tableName, @Param("orderByColumns") String orderByColumns);

Looks like a handy feature. Thank you :)

Hi @harawata , thanks for your reaction !! I will gh-853 merge at later.

Hi guys, I've fixed via gh-853. If my fix has problems, please reopen this issue.
Thanks.


Feature/383 course description

Critical Changes
Changes

Added a new field for Course Description. The new field is labeled Extended Description and will allow much longer Course descriptions.
The Course Description field will be removed from the Course page layout in favor of the new Extended Description field.

Issues Closed
Fixes #383

This PR includes additional metadata, mostly required flags, (including the required flag). This is to include the metadata changes retrieved from running retrieve_src command in CumulusCi 2.

Screenshot of the new section in HEDA Settings to run the copy procedure.


Setup shared folder for Vagrant output

Vagrant shared folders usually copy what's on the host to the guest. We want a shared folder that will contain the contents of the samvera-mgmt/hyrax github repo (that's checked out as a part of the build) -- so contents that are shared from the guest to the host.

Solved with SSHFS... requires installing that on host + vagrant sshfs plugin, but it handles it more cleanly than the other vagrant share/sync options. Additional requirements documented in README.


bump SDK dep to v0.43.0-rc1

Description

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

merging since it is just a dependency bump and the tests pass


Enable detection of loss of data when pulling logcat data.

WA currently supports 2 methods of retrieving logacat data, a single capture at the end of a job or via periodic polling.
Currently this needs to be configured manually however we could insert a marker at the start of the workload to detect and warn the user if the logcat buffer has wrapped and lost data.
It would also be worth investigating the use of the --wrap option (https://developer.android.com/studio/command-line/logcat#options) to allow for optimizing the polling period.

Implemented in https://github.com/ARM-software/workload-automation/pull/1119


[android] use OTBR_CONFIG_ANDROID_ENABLE for android platform

Current code uses __ANDROID__ for determine the Android platform while that flag
is also available on android-based but non-aosp devices. To avoid misconfiguration,
this commit uses OTBR_CONFIG_ANDROID_ENABLE for selecting the standard
Android devices. This is consistent with the
OPENTHREAD_POSIX_CONFIG_ANDROID_ENABLE in the openthread/ repo.

This supersedes https://github.com/openthread/ot-br-posix/pull/2328

@wgtdkp any ETA for this PR?


IBM Semeru fails to install ARM64 build: Unsupported architecture for IBM Semeru: arm64, the following are supported: x64, x86, ppc64le, ppc64, s390x, aarch64

Description:
The action fails to install Semeru arm64.
I guess the installer should use .distributionArchitecture() instead of .architecture: https://github.com/actions/setup-java/blob/9eda6b51cc4f6ee99be3dd5537b85e389e47bda9/src/distributions/semeru/installer.ts#L36C47-L36C59
For example, Microsoft installer uses .distributionArchitecture(): https://github.com/actions/setup-java/blob/9eda6b51cc4f6ee99be3dd5537b85e389e47bda9/src/distributions/microsoft/installer.ts#L51
Run actions/setup-java@v3
  with:
    java-version: 17
  17

    distribution: semeru
    java-package: jdk
    check-latest: false
    server-id: github
    server-username: GITHUB_ACTOR
    server-password: GITHUB_TOKEN
    overwrite-settings: true
    job-status: success
    token: ***
  env:
    ACTIONS_STEP_DEBUG: true
    ACTIONS_RUNNER_DEBUG: true
    TZ: UTC
Installed distributions
  Trying to resolve the latest version from remote
  Error: Unsupported architecture for IBM Semeru: arm64, the following are supported: x64, x86, ppc64le, ppc64, s[3](https://github.com/pgjdbc/pgjdbc/actions/runs/7002337194/job/19045932738#step:4:3)90x, aarch6[4](https://github.com/pgjdbc/pgjdbc/actions/runs/7002337194/job/19045932738#step:4:4)

Task version:
Download action repository 'actions/setup-java@v3' (SHA:0ab4596768b603586c0de567f2430c30f5b0d2b0)
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[ ] Hosted
[x] Self-hosted

Expected behavior:
JDK should install.
Actual behavior:
Resolution fails with Unsupported architecture for IBM Semeru: arm64, the following are supported: x64, x86, ppc64le, ppc64, s390x, aarch64

Hi, @vlsi 👋 Thanks for the issue, we will take a look!

@vlsi, actually, Semeru supports only these types of architectures: x64, x86, ppc64le, ppc64, s390x, aarch64. You can check it on their official web-site: https://developer.ibm.com/languages/java/semeru-runtimes/downloads/. I think that in your case, you may use aarch64 which is basically the same as arm64. I'm closing this issue now, if you have any additional questions feel free to reach out.

@IvanZosimov , could you please double-check?
The issue is that setup-java action attetempts to use arm64 by default.
In other words: the documentation for actions/setup-java reads that the default architecture is derived from the runner machine.
In practice, actions/setup-java fails if running at arm64 machine and installing semeru.
The root cause is that nodejs returns arm64 while the action misses to treat it as aarch64.

@IvanZosimov , check this: https://github.com/actions/setup-java/blob/9eda6b51cc4f6ee99be3dd5537b85e389e47bda9/src/distributions/microsoft/installer.ts#L51-L52
microsoft/installer.ts uses this.distributionArchitecture() which makes arm64 -> aarch64 conversion: https://github.com/actions/setup-java/blob/9eda6b51cc4f6ee99be3dd5537b85e389e47bda9/src/distributions/base-installer.ts#L190-L191
The conversion is missing in semeru/installer.ts, so it causes semeru installation failure.

Thanks for clarification, @vlsi I'll check that and get back to you with updates.

@IvanZosimov any update on this? still occurs today

Hello @vlsi,
We have addressed this issue in PR #677.
Please verify if this resolves your concern.
Please feel free to reach out to us for any other issues.


"Get-WinEvent -FilterHashtable" - Array Length Limited To 20

Steps to reproduce
When using "Get-WinEvent -FilterHashtable", it appear that if an array is used for the value in the key/value pair, the array length is limited to 20 items.
I think this limit shouldn't be there, to allow for arrays longer than 20.  If it's not possible to remove the limit for some reason, PowerShell should display an error when the limit is exceeded.  As it is currently, the user is unaware that the script is silently broken.
Expected behavior
In the below example, the Event ID range is from 1 to 21.  As the array length doesn't exceed 20 items, the script works correctly and returns results.

Actual behavior
In the below example, the Event ID range is from 1 to 24 (which is the Event ID range for Microsoft Defender Exploit Protection events).  As the array length exceeds 20 items, the script doesn't return any results – even though there are events stored in the event logs.  The user is unaware that the script is broken in this scenario.

Code from above screenshots
# Timescale
$StartTime = (Get-Date).AddDays(-35)

# Defender events
$Defender = Get-WinEvent -FilterHashtable @(

    # ExploitProtection
    @{
        "StartTime"        = $StartTime
        "LogName"          = "Microsoft-Windows-Security-Mitigations/KernelMode"
        "ProviderName"     = "Microsoft-Windows-Security-Mitigations"
        "ID"               = "1".."24"
        SuppressHashFilter = @{
            "ProcessPath" = "\device\harddiskvolume4\windows\system32\svchost.exe"
        }
    }
)

# Output
@($Defender; ) |
Sort-Object -Property TimeCreated |
Format-List -Property TimeCreated, Message, ID

Environment data
Name                           Value
----                           -----
PSVersion                      7.0.0
PSEdition                      Core
GitCommitId                    7.0.0
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Did you check that this works for array with less 20 items?
If so I guess it is undocumented underlying API limitation.
Adding a check and issue an error message is simple.

I've just realised that it's actually 23 or more, not 20.  So if the array count is 22 or less it works OK, if the array count is 23 or more it doesn't work OK.
The first screenshot has an array count of 21 (1..21); therefore if you look in the Terminal pane in that particular screenshot you can see it is returning results as expected.
The second screenshot has an array count of 24 (1..24); meaning it doesn't work as expected.
Therefore to clarify, using the following ranges will return results correctly:
2..10 (Array count = 9)
5..10 (Array count = 6)
1..22 (Array count = 22)
10..31 (Array count = 22)
Using the following ranges won't return any results, even though there are events in the log for Event ID 10:
1..35 (Array count = 35)
5..30 (Array count = 26)
1..23 (Array count = 23)
10..32 (Array count = 23)
Using "Get-WinEvent -FilterXML" works fine, it's just trying to use "-FilterHashtable" to do the same thing as "-FilterXML" that's problematic.  For example, the below using "-FilterXML" works fine:
PS1 File:
01 Defender - FilterXML.zip

In addition, the above example is using a range operator just for Event IDs (1..24).  However, as "Get-WinEvent" is dealing with Event Logs, the range operator may be used for other things that need to be longer as well.  For example, when looking at Windows Firewall event logs, it could be looking at a range of Source/Destination Port numbers.
To give an example, when using "-FilterXML" – rather than "-FilterHashtable" – it's possible to have multiple specific suppress filters, which allows creating a whitelist (collect all the events and then whitelist by suppressing the ones you don't want to see), however with "-FilterHashtable" that doesn't appear to be possible in the same way.
Using "-FilterXML" it will look something like this:
PS1 File:
02 Firewall - FilterXML.zip

Using "-FilterHashtable", something similar can be achieved by doing something like this:
PS1 File:
03 Firewall - Hashtable 01.zip

However, when using "-FilterHashtable", the problem is when you need to suppress firewall events where it's not possible to suppress a particular "DestPort" (like old delayed replies from DNS servers – as they are replying to random destination ports in the 49152–65535 range, rather than a specific port).

If you try to add a another field (such as "SourcePort") to be suppressed as well, this won't work because the event would need to have both one of the values in the "DestPort" and also one of the values in "SourcePort" in order for it to be suppressed.  As this isn't the case for most of the events, it will return almost the whole inbound event log:
PS1 File:
05 Firewall - Hashtable 02.zip

Another option would be to use the 49152..65535 range operator.  Although not ideal, I'm unable to find another way.  However, due to the hashtable arrays being limited, this won't work either.  At least it is something I wanted to try; I don't know what the performance would be like if it did work:
PS1 File:
06 Firewall - Hashtable 03.zip

@DesertBear does using something like "49152-65535" for the DestPort work for this application?

Unfortunately, that doesn't work.  When dealing with Windows Event Logs, you're stuck dealing with the data exactly as it appears in the event log XML.  So when using "49152-65535" for the "DestPort", it won't recognise it as a range, but instead reads it literally and checks to see if "49152-65535" matches "61457" – which it obviously doesn't.

On this page it mentions:

If the XPath expression is a compound expression that contains more than 20 expressions or you are querying for events from multiple sources, then you must use a structured XML query.

The limitation on the number of expressions applies to each of the XPath queries within each select/suppress element in a structured XML query. In order for your example to work, -FilterHashTable would need to either understand ranges and translate them into min <= x <= max queries, or it would need to create multiple select/suppress elements to stay under the 20 expression limit.


Provide shortened aliases for common kubectl commands like switching namespace

What would you like to be added?
I suggest to add shortened aliases for most used commands in kubectl tool like this:

switch namespace:

kubectl set ns my-namespace
# alias of full command: kubectl config set-context --current --namespace=my-namespace

query in all namespaces:

kubectl get pods -A
# alias of full command: k get pods --all-namespaces

display wide information:

kubectl get pods -W
# alias of full command: kubectl get pods -o wide

configure access to new cluster as single command:

kubectl config set my-cluster -S https://<IP_ADDRESS> -CA fake-ca-file -U developer -CC fake-cert-file -CK fake-key-seefile -N frontend
# alias of bunch of commands:
kubectl config set-cluster my-cluster --server=https://<IP_ADDRESS> --certificate-authority=fake-ca-file
kubectl config set-credentials developer --client-certificate=fake-cert-file --client-key=fake-key-seefile
kubectl config set-context dev-frontend --cluster=my-cluster --namespace=frontend --user=developer

Last command alias looks not such short, but it's much easier to execute a single command, instead of three ones!
The above are only examples of common long-typing commands from my perspective.
And via this feature request I want to start discussion about adding practice to provide shortened aliases for most of common kubectl commands to extend the life of the keyboards of all Kuberbetes users :)
Why is this needed?
Most often, I and, it seems to me, most other Kubernetes users are typing manually  a lot of kubectl commands with different arguments multiple times every day.
That's good that Kubernetes provides commands and arguments, that are clear without any additional description.
But when we typing them every day, we spend too much time to unnecessary keyboard presses.
In most other tools It's common practice to provide shorten versions of common commands and arguments, to safe users time and extend the life of their keyboards.
So let's think about Kubernetes users and their keyboards too, and provide shortened (abbreviated) aliases for most used commands!
/sig cli

We might have a solution for this in the future with https://github.com/kubernetes/enhancements/issues/3104
For now we recommend handling this in bash. Have a look at https://github.com/ahmetb/kubectl-aliases.
/close

Sorry to necropost but I wrote a bash script that aliases all the commands, resources, and options, plus a few other things.
https://gitlab.com/gnufred/k


ISPN-10011 Add JSON logging in server

jboss-logmanager is not the most flexible tool, even though they tried hard and StructuredFormatter and friends are fairly configurable. But it still lacks the most basic thing: removing unwanted fields. I tried also integrating other loggers but it gets too involved so returned to jboss-logmanager, but with a custom formatter.
https://issues.jboss.org/browse/ISPN-10011

Thanks @anistor


Updated local_installation.md for windows support

I added one piece of code in documentation that windows10 users can use to enable Linux Subsystem in Windows and continue to use linux commands given through Pachyderm docs

@anuragsoni9 Just to follow up here on our discussion in Slack, it would be great to add this information to all the places where pachctl installation is mentioned. Again, no pressure, but if you feel lead to add this, it's mentioned in the following:
http://pachyderm.readthedocs.io/en/latest/deployment/google_cloud_platform.html
http://pachyderm.readthedocs.io/en/latest/deployment/amazon_web_services.html
http://pachyderm.readthedocs.io/en/latest/deployment/azure.html

Hello @dwhitena  ,
I think I am able to correctly add all the doc changes  you mentioned into this pull request.
Please verify.


Not able to download jboss package from mentioned link for Unix platform

SUMMARY

ISSUE TYPE

Bug Report

COMPONENT NAME

ANSIBLE VERSION

CONFIGURATION

OS / ENVIRONMENT

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

I was mistaken.. please ignore..