Virtual documents: Allow me to provide a description label for the editor

It would be nice to have more control over the description label for a virtual document. Today since we just communicate via custom URIs, the path segment will be used as description, which in most cases is probably not what I want.

Yes - that goes into the editor input version 2 direction.

On the provider we can add another (optional) function like provideLabel(uri:Uri):string

Got some time to reason about this. I am against adding something to the TextDocumentContentProvider and the label of an uri isn't part of the TextDocument e.g. it cannot be retrieved from a document. It should be more like a UriLabelProvider that given a uri can provide some sort of title.
interface TextEditorTitleProvider {
   provideTitle(uri: Uri): string | Promise<string>
}

@bpasero Since the title would now come asynchronously from the extension host I wonder if the input get send an event that title and description need to be updated? I see the input being an event emitter but I don't see an event

@jrieken I already need to update the title in case the editor becomes dirty so I would assume that you could just reuse the EDITOR_INPUT_STATE_CHANGED event to force the editor to update the title from the input.

moving to May due to too many open questions. Ideas is still to separate the data (TextDocumentContentPresentation) from the UI (label, description) but there might be more requirements, like expressing readonly-ness, linking an editor to a parent-editor, adding dynamic commands etc

My current thinking about this:

We add ways to define title and description via the `TextEditorOptions' such that an extension can set/update the ui-representation via the API - this isn't necessarily limited to virtual documents.
We add ways to provide TextEditorOptions when opening an editor via showTextDocument
For the future we still have the possibility to add a TextEditorOptionsProvider-api which would work similar to how language features work.

IMO this is better then the model/UI marriage that happens by adding this functionality to the content provider.

moving to June since this is a bit of work

@bpasero As discussed, supporting now {label: string; description: string; }.

@jrieken can you explain how title would be different from label or description?

It's just a string and would only be the label not allowing you to define the description. That's cos it might look weird having it all configurable:

@jrieken right, maybe we should think about the property names in the API and not just copy what we have in the workbench side. I like the idea of exposing a title for an editor and use that as label in the input. I still think it could be useful to also show the description if someone wants to but it might be less obvious what the description of an editor is and how it shows up. So we could also start small and just have title in the API that translates to label in the workbench.

Done like that. You can set the title and that's it for now.


Regenerate bindings & post patch notes for 2.16

Coming in to support this update seeing as it's long overdue and much needed!
Draft until CI is fixed.

CI... passed?

Forgot to say this is ready for review.


Initialise a react-native project with a specific react-native version

For now, initialise a new rect-native project using react-native-cli can not specify the react-native version that the new project use. react-native-cli can only install the latest version of react-native from npm).
Since that the react-native has a very frequent release cycle (2 weeks) and brings breaking changes in common. We need to do a lot of cross versions verifications for our codes and 3rd packages.
I hope that the react-native-cli init may have an extra argument to specify  the version of react-native that the new project may used.
I've just copied and changed the code from react-native-cli and published to npm as a new tool rninit to do that things, but that would be more convenient if this feature could be added to react-native-cli itself.

@jacobbubu I don't think this can be something in core as we don't support old React Native versions.
You should commit the generated android and ios files to version control and not generate a new project everytime. Genrate a new project only when it's actually new.

Two weeks ago, I tried the gl-react-native on react-native version 0.15 and found that all of the examples provided by gl-react-native did not work.
And then I setup Sinopia as a npm proxy that let me use any of the version of react-native to create testing project. That is not trivia. Well, gl-react-native works fine on its original dependent react-native version.
Such thinks happened again and again when you try the 3rd components that listed on react-parts. You need to do a lot of version traversals to testing their compatibility and availability.
Version control has nothing to do about these things.

@jacobbubu Sorry for the inconvenience. React Native is currently moving in a very fast pace and things break very frequently. Hopefully we'll reach API stability soon enough, but we're not there yet.
If we allow initializing new projects with older versions of React Native, then it would mean that we have to support the old versions in terms of bug reports and questions etc. We are having a hard time managing the bug reports and don't have enough bandwidth to afford supporting older versions for now.
Of course no one is stopping you from creating tools that do these kinds of things, as you already did. That actually addresses your use case and solves your issue.

Also worth noting that you don't have to regenerate the project every time. To change the React Native version you can run the following inside the project,
npm install react-native@version
react-native upgrade

Which is probably a better and easier way.

Yes, that is the way to do better for read-native later than version 0.13.
Thanks!


More depths to allowing languages in DFLT

Need to allow DFLT based languagesystem commands.
Fix the problem that if a sublanguage is used in the DFLT script that all those lookups end up in DFLT dflt. Just treat it all like any other script.

NB The PairPosTable test ttx showed the faultiness of the current code before the fix with one feature listing the lookup twice.

thanks, overall this lgtm.
would be nice to also add an explicit test for this situation of DFLT script, non-dflt language.

also i'm not very happy that we are unilaterally implementing this in feaLib while the Feature FIle spec is not also updated
https://github.com/adobe-type-tools/afdko/issues/438

I agree that the spec should be updated. I do hope that this PR doesn't await that change since it is blocking production. TIA.

@anthrotype I will be updating the afdko feature file spec to match the open type spec sometime in the next few days.

ping

@anthrotype @mhosken I have updated wording for the feature file spec, and a fix for makeotf, but I have another change in feature file spec wording pending ( see issue 1273) and wanted to wait so as to submit both as one update to the feature file spec.

ping2

sorry Martin, I still have some concerns and would like to play with this a bit more. I promise this won't take another week.

@mhosken @anthrotype Note that I made an update to the feature file spec and makeotf code in afdko PR's 503 and 498.

@readroberts I see you added the requirement that

Any other language statements using the 'DFLT' script tag must precede all other language statements.

why exactly is that? feaLib currently doesn't enforce this.

anyway, now it does (d3229d5)

@anthrotype I think you are correct that there is no need to require that "Any other language statements using the 'DFLT' script tag must precede all other language statements." I'd be fine with removing this restriction.


Issue in database session management, creating multiple rows for same session id in session table

What steps will reproduce the problem?
Just enable captcha at login page. showing captcha invalid. captch is not being refresh etc.
What is the expected result?
It's creating a separate entry in session table for each request against same session id, this should not be happen (there should be one entry in session table against one session id)
Note-
When I replaced two files (yii\web\DbSession and yii\web\MultiFieldSession) from old version (Yii2.0.12) then it is working fine.
Additional info

Q
A

Yii version
2.0.24

PHP version
7.1.23

Operating system
Linux

I have the same issue with latest Yii2 (<IP_ADDRESS>). Every click on the UI results in 12 new records in session table.

I have the same issue with latest Yii2 (<IP_ADDRESS>). Every click on the UI results in 12 new records in session table.

@raulrebane Is it reproducible with a clean basic application and minimal amount of changes?

@raulrebane Is it reproducible with a clean basic application and minimal amount of changes?

please close for now. This takes time and I am currently busy. Maybe after month or so

please close for now. This takes time and I am currently busy. Maybe after month or so


Queue does not throw an error if it fails to connect to the provided reference.

If you pass in a firebase ref that for instance doesn't have the correct read permissions when instantiating a Queue it does not throw it just logs the error? There's really no way of responding to this.
https://github.com/firebase/firebase-queue/blob/master/src/lib/queue_worker.js#L598
I can't see a way to tell programmatically if a queue worker subscription has been successfully established.
Should there be a function like Queue.shutdown such as Queue.status() that returns a promise that is resolved once all workers successful subscription to the ref has been made or rejected if it fails?
I realise the QueueWorker would have to have a status function that returns its connection state as well.
A less drastic change would be that the workers are not spawn until the ref connection is tested.
I'm happy to take a crack at a PR for this if you guys have suggestions?
A breaking change suggestion would be that Queue has a function called connect() or spawn(). That you call once you instantiate the object.
Cheers

A couple of other things that I'm not sure how to handle correctly...
If an error is thrown inside (object undefined etc) the processing function a worker is running. Its heavily guarded (which is what you want in a worker) and the error is written to the task. But there is no logging.
In production most of these types of unhandled errors shouldn't happen but it makes things slightly difficult for dev in the case where an error get thrown inside of that processing function you have to track down the errored/retired task and check the error details.
I feel like there should be an option to log out errorDetails inside the worker?


Create noteheads_change_by_layer.lua

New script with the functionality of noteheads_change.lua but with layer filtering, a single menu item and a single confirmation dialog. I now use this always instead of the old script.

Is there a reason you are using FCMCustomLuaWindow instead of FCXCustomLuaWindow? The X version has (among other things) automatic remembering of window position. (Though I discovered it isn't working in the current master branch, but we will fix that.)

FCMCustomLuaWindow instead of FCXCustomLuaWindow?

I noted that @ThistleSifter was migrating some of FCX to FCM and wondered what implications would arise using the "lower" version of LuaWindow. Happy to use either - just testing.

Main I'm interested in if the script needs to have its own window position handling. I think it's built into FCX....

Updated my local library & mixin files to latest /src/ versions and tried FCX - doesn't keep window positions in modal. The private[window].HasBeenShown conditional within local restore_position() suggests it's unique to modeless operation. All of the positioning routines (that I can find) are in the FCM file, not FCX.
Obviously it could be implemented for modal, just a few more steps to add.

PS: also might still be tied to RetainLuaState which I'm not using here.

Stick to FCX for now. I'll replace them in a future PR when I remove the FCXCustomLuaWindow mixin.
Automatic restoring of window position only works with RetainLuaState, since you need a previous position to restore from. For something like this, where it's just being loaded from a config file each time, it will need to be manually handled. At least until automatic populating of the window from a config file is implemented ... maybe ...

No problem. Happy to keep it in-house - only an extra 6 lines of code. FCX version follows.


Update tslint.json for latest versions of tslint

Enforces spaces and double quotes again, and enforces no space before the colon for type definitions.
This should fix part of #3994. I couldn't find an existing rule to cover the no multiple declaration expressions style, so that is missing from this.

Looks great, thanks @weswigham! @danquirk can you take a quick look?

I think the rule changes are all good but I'm inclined to say we shouldn't modify the rules without an accompanying update to the affected code. Ideally the only TSLint violations are things that TSLint doesn't support yet (ex namespaces) plus a very small number of non-standard patterns we might need to evaluate. I was hoping that the former would be taken care of soon (I need to check on TSLint's 1.5 support) to a degree where we could consider turning on the linting by default.

The jake lint task is broken right now. I actually haven't noticed since I've been calling tslint on my files directly.
I think this line needs to be changed to
    var cmd = 'tslint -c tslint.json ' + f;

I'll make a PR for it.
Additionally, it looks like a few other things are wrong with it (not capturing f, for example, so all final error messages report the same file).

How is it broken? Seems to be working fine on my machine:
F:\GitHub\TypeScript [master +5 ~0 -0 !]> jake lint
src/compiler/sys.ts[300, 22]: unreachable code

...<elided>

src/compiler/sys.ts[34, 6]: missing semicolon
FAILURE: Please fix linting errors in src\compiler\sys.ts

SUCCESS: No linter errors in src\harness\harnessLanguageService.ts
<and so on>

usage: node F:\ts\typescript\node_modules\tslint\bin\tslint

Options:
  -c, --config          configuration file
  -h, --help            display detailed help
  -o, --out             output file
  -r, --rules-dir       rules directory
  -s, --formatters-dir  formatters directory
  -t, --format          output format (prose, json, verbose)  [default: "prose"]
  -v, --version         current version

Missing files
FAILURE: Please fix linting errors in src\harness\rwcRunner.ts

etc.
There's no -f in the latest tslint afaik, it just expects the files to be passed last.

Oh I see, they took a breaking change in their cmd line args.

We've merged in #4005, to fix the issue in the conversation above. Now this needs to be merged to enable linting on tabs, quotes, and spaces before colons.

:+1:

Are there code changes needed from these changes?

The tslint isn't actually used in a build (other than jake lint, which wasn't even in the README until recently) yet since the codebase doesn't yet pass the lint, so merging changes to it should be harmless.
#4008 fixes all the linter errors this tslint reports that aren't apparently caused by bugs in tslint (or, more accurately, by tslint not supporting TS 1.6 features yet), afaik.

thanks


Code which must be changed is below the "do not change code below this line".

Challenge Using Objects for Lookups has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

// Setup
function phoneticLookup(val) {
  var result = "";

  // Only change code below this line
  var lookup = {
    "alpha":"Adams",
    "bravo":"Boston",
    "charlie":"Chicago",
    "delta":"Denver",
    "echo":"Easy",
    "foxtrot":"Frank",
    "":undefined
  };

  return lookup[val]; //This code is originally found below as follows:

  // Only change code above this line
  return result;          // This is where the return is initially.
                                // Tests can only be passed if return is modified.
}

// Change this value to test
phoneticLookup("alpha");

@inhll thanks for the issue. Yes, the challenge can be completed as your code describes but the instructions point to you on how to complete the challenge:

Use it to lookup val and assign the associated string to the result variable.

This makes for consistency based on the original seed code for the challenge and focusing more on using objects for lookups, rather than the function aspects of the code. I hope you understand. Closing as a non-issue. Happy coding!

Check it out!!!

Aw yeah! A+ @BariqFitri!


add split treemap algorithm as tile (WIP)

This pull (#71) seeks to add the split algorithm as d3.treemapSplit.
References:

"Ordered and Unordered Treemap Algorithms and Their Applications on Handheld Devices" by BJÖRN ENGDAHL, 2005 (link(pdf))
ggraph implementation by @thomasp85 https://github.com/thomasp85/ggraph/blob/faf8b2011958ecc9be098122619d946f3aed8171/src/treemap.cpp

Examples
http://bl.ocks.org/timelyportfolio/2bbd4cedf597eae6a5e90412d9df1c1f
http://bl.ocks.org/timelyportfolio/e480359ea953d96a38a4466187d3d62b
Todo

[x] add test~s~ (f73f12b)
[ ] refactor to more closely mirror d3 style
[x] document (60cbfed)

Well, technically my implementation is in ggraph and not ggforce but you're forgiven😊

@thomasp85, fixed

This looks a lot like the binary treemap algorithm. I don’t have time at the moment to exactly describe the differences, but it looks to me like even if the output is different, we could reuse optimizations from the binary treemap implementation here. Specifically, that implementation computes the cumulative values of the nodes once (in sums) and then does a binary search to split the current partition. This avoids repeatedly recalculating the sums and doing a linear scan during each recursion; see #44 for context.

I started with binary because it looked closest but then went into get-it-working mode. The sums seems like a very easy optimization, so I will try to implement after focusing on the binary implementation.

A missing return caused my problem.  In 2c56288 I optimized by avoiding repeated calculation of the sum, since we already know the sum for each split list.  I also added a check for non-empty list before recursing spitTree.
Results seem to indicate some success.
optimized bl.ock
treemap split took 31.91999999999996 milliseconds.
treemap split took 28.239999999999895 milliseconds.
treemap split took 9.740000000000009 milliseconds.
treemap split took 15.154999999999973 milliseconds.
treemap split took 11.370000000000005 milliseconds.

non-optimized bl.ock
treemap split took 88.26499999999993 milliseconds.
treemap split took 97.23500000000013 milliseconds.
treemap split took 69.52500000000009 milliseconds.
treemap split took 89.73500000000001 milliseconds.
treemap split took 78.62000000000012 milliseconds.

However, I will explore using parent value as sum to see if we can squeeze some performance out of that.

Regarding the optimization (and please take this with a grain of salt since I’ve only done a cursory look at the code and might not be understanding it correctly): I think you’ll want to avoid calling nodes.slice during each recursive call, too, and instead pass indexes i and j (representing the inclusive start and exclusive end index of the current partition of nodes), as is done in the binary implementation. Also looks like you could compute the initial sum before calling splitTree the first time, rather than checking if sum is null.

@mbostock, is it ok to assume that all hierarchies passed to treemap have been summed?  If so, we can entirely eliminate the null check on sum.
In terms of removing the nodes.slice, I am not sure how I can perform the split with just the indexes, but now that split is working again I will revisit binary again specifically looking at the index pieces.
Thanks!

is it ok to assume that all hierarchies passed to treemap have been summed? If so, we can entirely eliminate the null check on sum.

I’m confused but it’s probably because I am giving you drive-by feedback without looking too closely at the code. Yes, node.sum must be called on root before invoking the treemap. But no, the sum you were computing by adding together the children is not necessarily equal to the parent.value because nodes can have self-values (internal values), which should be visually represented as leftover whitespace for the parent without any overlaid child. My point about the null check was that it looked like the only time splitTree’s sum was null was the first time you called it (before recursing), so you could just compute that sum once when you call splitTree the first time, rather than checking for null on each recursion.

I added a quick speed result in this example for comparison.

I think the main thing this is missing is some optimization. I believe that this implementation would benefit from the tricks used by d3.treemapBinary, which is:

Precompute the sums.

I feel like I still don’t have a grasp as to how this algorithm is different from the binary treemap algorithm. The implementations appear pretty similar… Can you give me a quick summary of how they differ?

So, this does appear to produce nearly identical results to the binary treemap algorithm, except the x and y positions are swapped. I added this to your linked example to compare:
data.each(function(d) {
  var x0 = d.x0, y0 = d.y0, x1 = d.x1, y1 = d.y1;
  d.x0 = y0, d.x1 = y1, d.y0 = x0, d.y1 = x1;
});

Still trying to understand why.

Okay, I have verified that these two algorithms are in fact identical¹, aside from the flipped x and y!
¹ I discovered a bug in my binary treemap implementation where it uses bisection to find the split point, but sometimes it is off by one because it doesn’t test the adjacent node. The fix will be something like this in binary.js:
if (Math.abs(sums[k - 1] - valueTarget) < Math.abs(sums[k] - valueTarget)) --k;

Just to demonstrate, this is the output from the binary treemap with the above fix and x and y swapped:

Okay, the x and y were swapped because the binary treemap uses this test:
if ((y1 - y0) > (x1 - x0)) {
  … split vertically …
} else {
  … split horizontally …
}

Whereas the split treemap uses this test (rewritten slightly for parity):
if ((x1 - x0) > (y1 - y0)) {
  … split horizontally …
} else {
  … split vertically …
}

The difference is when x1 - x0 = y1 - y0: binary was using horizontal, split was using vertical. In our examples the layout size (and root node size) is a square 960×960. This seems like a nice improvement too since it will favor a vertical partition on square nodes.

Closing as fixed, since these turned out to be the same as binary treemaps. TIL!


feat(941210): add regexp-assembly for decontructed regex

add .ra file with the meaning of the regexp
rule tries to match all the possible ways to write 'javascript' using unicode characters, html entities, and javascript escape sequences.

Related issue: #2580

Tests are failing. I'll review once they've been fixed.

@theseion Can you take a 👀 now?


Add Room-related UI components

Codecov Report

Merging #8 (b8bcbda) into master (33a18e9) will decrease coverage by 1.42%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master       #8      +/-   ##
============================================
- Coverage     69.05%   67.62%   -1.43%
  Complexity      398      398
============================================
  Files            72       74       +2
  Lines          1286     1316      +30
  Branches        127      131       +4
============================================
+ Hits            888      890       +2
- Misses          365      394      +29
+ Partials         33       32       -1

Impacted Files
Coverage Δ

...c/main/java/seedu/address/model/room/RoomList.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/RoomCard.java
0.00% <0.00%> (ø)

src/main/java/seedu/address/ui/RoomListPanel.java
0.00% <0.00%> (ø)

...c/main/java/seedu/address/model/person/Person.java
80.76% <0.00%> (+2.33%)
:arrow_up:

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 33a18e9...b8bcbda. Read the comment docs.


Version 6.2.3 - PostgreSQL $$ handling is broken

The changes to the $$ handling seem to have broken the standard behaviour.
In PostgreSQL $$ or anything like $anything$ is used as a replacement for single quotes.
After the update to 6.2.3. the simple following anonymous codeblock is not executed:
do
$$
begin
	raise notice 'test';
end
$$
;

SQL Error [42601]: Unterminated dollar quote started at position 4 in SQL end
$$
. Expected terminating $$

Putting something between $$ like e.g. $f$ makes the statement work:
do
$f$
begin
	raise notice 'test';
end
$f$
;

Many standard PostgreSQL scripts rely on the $$ for quotation, so this can hopefully be fixed as soon as possible.
Greeting
James

Duplicate.
Fixed in the scope of #7050


XmlHelper.FindType: MonoGame.Framework hates being searched through.

When running FEZMod on FEZ 1.11 through Steam, XmlHelper fails finding types in the MonoGame framework, making XmlHelper useless for basically anything. Hopefully "uh. uh duh" (just waiting) will fix it automatically.
(ignore FezCorruption for now; that's FEZ.Secret.mm)
(22:30:56.840) [FEZMod] Failed searching a type in XmlHelper's FindType.
(22:30:56.841) [FEZMod] Assembly: MonoGame.Framework
(22:30:56.842) [FEZMod] The classes in the module cannot be loaded.
(22:30:56.908) [FEZMod] Failed searching a type in XmlHelper's FindType.
(22:30:56.909) [FEZMod] Assembly: MonoGame.Framework
(22:30:56.909) [FEZMod] The classes in the module cannot be loaded.
(22:30:56.927) [Unhandled Exception] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object
  at FezGame.Components.CorruptionHost.ProcessLevelData (FezEngine.Structure.Level levelData) [0x00000] in <filename unknown>:0
  at FezGame.CorruptionMod.FezCorruption.ProcessLevelData (FezEngine.Structure.Level levelData) [0x00000] in <filename unknown>:0
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
  --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <filename unknown>:0
  at FezGame.Mod.FEZMod.CallInEachModule (System.String methodName, System.Object[] args) [0x00000] in <filename unknown>:0
  at FezGame.Mod.FEZMod.ProcessLevelData (FezEngine.Structure.Level levelData) [0x00000] in <filename unknown>:0
  at FezGame.Services.GameLevelManager.Load (System.String levelName) [0x00000] in <filename unknown>:0
  at FezGame.Services.GameLevelManager.ChangeLevel (System.String levelName) [0x00000] in <filename unknown>:0
  at FezGame.Components.Actions.EnterDoor.DoLoad (Boolean dummy) [0x00000] in <filename unknown>:0
  at FezEngine.Tools.Worker`1[System.Boolean].Act () [0x00000] in <filename unknown>:0
  at FezEngine.Tools.PersistentThread.DoActualWork () [0x00000] in <filename unknown>:0
  at Common.Logger.Try (System.Action action) [0x00000] in <filename unknown>:0

After some debugging, it turns out:
Could not load type 'MonoGame.Framework.MonoLive.MonoLive' from assembly 'MonoGame.Framework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.

The FEZ-SDL2 branch of FNA contains a copy of it here. It contains a reference to System.Web.Services, which is not included in the Steam version. This already caused issues, namely #1.
I am not able to find MonoLive in the official MonoGame repository, nor in the master branch of FNA, which means there is a great chance "Uh. Uh Duh" will fix it.

Copying System.Web.dll and System.Web.Services.dll into the Steam FEZ directory as workaround is now confirmed.
(SIDENOTE: Why am I commenting my own issues?!.. well, maybe if someone finds this: Hi!)

Got confirmation that "Uh. Uh Duh" will fix this issue and other issues with assemblies not found that may occur. Supporting FEZMod via MonoKickstart in versions not affected by "Uh. Uh Duh" may become harder, but that would generally only be 1.07 (unless the speedrun community creates a new category for "Uh. Uh Duh"), which is being run outside of Steam (MonoKickstart) anyway.
Ways to fix this issue in versions not affected by "Uh. Uh Duh":

delivering System.Web.Services (confirmed as workaround; causes new unmet dependencies; licensing unknown)
delivering a patched version of MonoGame-SDL2 (definitely killing Ethan's Steam PS4 controller beta and "Uh. Uh Duh" support; licensing unknown)
patching MonoLive dynamically (could kill "Uh. Uh Duh" support due to the differences; could kill everything knowing my patching skills)


M04-L10: Will the dockercompose YAML file need updating / be getting updated?

Contact Details
No response
What happened?
Following the steps in the lab guides...
Receiving multiple errors and warnings after running the pipeline in: Exercise 1: Setup CI pipeline to build eShopOnWeb container / Task 1: Setup and Run CI pipeline
Seems docker compose version is deprecated and there is a "loc string" missing
The only thing I've changed in here is the resource group name and subscription ID: /.ado/eshoponweb-ci-dockercompose.yml
Lab
Integrate Azure Key Vault with Azure DevOps
Relevant screenshots

Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

To follow up - the pipeline did complete with a green tick as if it was successful, however these errors and warnings were all still listed.


logon UPN match their primary SMTP address recommendations are blocking deployment

[Enter feedback here]
can you share more background on the remark at the bottom of the page " It is best practice, however, to have the person's logon UPN match their primary SMTP address."?  Is this just for user convenience or are there technical requirements? I have several customers that are confused about this statement that is a deployment blocker for them.
Thanks
<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f42a1bfc-8920-c16d-f4c9-d29b401b7f6c
Version Independent ID: 979b71da-fdff-238d-41fb-472f1591e51e
Content: Change a user name and email address - Microsoft 365 admin
Content Source: microsoft-365/admin/add-users/change-a-user-name-and-email-address.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@maartenk99 Thank you for your feedback. Ideally, Users will need to understand what their UPN is and that it is the login for all things Office 365 related. There are some prompts that will say “enter your email” but they will in fact need to use their UPN.
Office ProPlus, the iOS versions of Office and OneDrive will prompt the user for their email address for login or activation, they really mean the UPN. So this is more for user convenience.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @maartenk99 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[RORO-4492][JT] add service dashboard page

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.


community: add Ukrainian Terraform telegram community

Discussed in https://github.com/shuaibiyy/awesome-terraform/issues/173.
Maybe we should organize such local communities in a separate block? WDYT?
E.g.
## Local communities (or Language-specific communities)
- [Telegram (Ukrainian speak community)](https://t.me/terraform_ukraine)

?

Thanks @aaabramov!

@chenrui333 Thank you too!


Open Session doesn't register keypresses

What steps will reproduce the problem?
1. Bind Ctrl-Space to File->Open Session
2. Press Ctrl-Space
3. Immediately press enter or press down a few times

What is the expected output? What do you see instead?
The expected result is that it would launch the first selected result when
pressing enter, instead it does nothing.
When pressing down, it sometimes doesn't register, but not always. Up key also
acts weird.

What version of the product are you using? On what operating system?

<IP_ADDRESS> on Windows 7 64bit Enterprise

Please provide any additional information below.

I have a configuration with more than 100 sessions, and use the Open Session
all the time, and this bug has been annoying me for quite some time ;)

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 17 Mar 2014 at 9:21

Closing this issue but all hope is not lost! We still want to help.
See: https://github.com/jimradford/superputty/wiki/Legacy-Imported-Issues on how to help us to help you!


Integration does not work on recent HA versions

Versions

Key
Value

Home Assistant version
2023.11.3

Integration version

Sagemcom F@st model
5566

Sagemcom F@st firmware (optional)

Describe the bug
Sagemcom Fast 5566 (Bell Home Hub 3000).
Admin account with password  and md5 authentication method.
Only see the device, no entities found.
No errors log on debug mode
With home assistant version 2023.8.4, the device could see over 40 entities.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

Please try the latest version (0.2.10) and let me know if it doesn't work.

Hello,
It works correctly with version 0.3.0.
I can see now the entities of the device.
Thank you very much, your work is greatly appreciated
Francois

From: Mick Vleeshouwer @.>
Sent: 07 January 2024 14:18
To: iMicknl/ha-sagemcom-fast @.>
Cc: Fgreg881 @.>; Author @.>
Subject: Re: [iMicknl/ha-sagemcom-fast] Integration does not work on recent HA versions (Issue #74)
Please try the latest version (0.2.10) and let me know if it doesn't work.
—
Reply to this email directly, view it on GitHubhttps://github.com/iMicknl/ha-sagemcom-fast/issues/74#issuecomment-1880146812, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4EQPBU4A7LJNIQ76JNFFW3YNLYINAVCNFSM6AAAAAA7XBRNYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGE2DMOBRGI.
You are receiving this because you authored the thread.Message ID: @.***>


bracketed paste can't work in tmux

It works in xfce4-terminal, but doesn't in tmux in xfce4-terminal. zsh works in both situations so that it isn't tmux's fault.
According to the help, I've set the following options since it's not set by default inside tmux:
if &term =~ '^screen\|^tmux' && exists('&t_PS')
  let &t_BE = "\033[?2004h"
  let &t_BD = "\033[?2004l"
  let &t_PS = "\033[200~"
  let &t_PE = "\033[201~"
endif

Vim doesn't have t_PS and t_PE as options as the doc says. I've patched it so they are options. But it still doesn't work. Bracketed paste mode is enabled and bracketed text is sent to vim (confirmed by strace), but vim doesn't recognize, behaving like there's no bracketed mode.
My test command is:
src/vim -N -u .../vimrc

My Vim's patch level is 300.
The patch I added is:
diff --git a/src/option.c b/src/option.c
index b90d5fdfa..1256ae3cf 100644
--- a/src/option.c
+++ b/src/option.c
@@ -3061,6 +3061,8 @@ static struct vimoption options[] =
     p_term("t_8b", T_8B)
     p_term("t_BE", T_BE)
     p_term("t_BD", T_BD)
+    p_term("t_PS", T_PS)
+    p_term("t_PE", T_PE)

 /* terminal key codes are not in here */

Vim has two kind of terminal options: output code options and key code options.
Currently "let &" cannot be used for key code options.
https://groups.google.com/d/msg/vim_dev/LK_EYUOGI6s/60x9RQskCwAJ

Oh thanks! I switched to exec + set and it worked!
Key code options seem to be very special and it's not easy to notice they are different ones (both can start with t_).


Learning Algorithm as abstract types and new organization of tests

Solves #4 and separate tests in a file for each training algorithm. (I know this package in not maintained, but just in case you're interested 😄)

It now closes #3 also


fontforge: Fix for Linuxbrew

Closes Linuxbrew/linuxbrew#607.

==> make
...
Last 150 lines from /home/travis/.cache/Homebrew/Logs/fontforge/03.make:
/tmp/fontforge20160323-31314-gbascp/fontforge-20150824/fontforge/python.c:6214: undefined reference to `Py_BuildValue'
.libs/libfontforge_la-python.o: In function `PyFF_Glyph_get_vwidth':
/tmp/fontforge20160323-31314-gbascp/fontforge-20150824/fontforge/python.c:6199: undefined reference to `Py_BuildValue'

https://travis-ci.org/Linuxbrew/linuxbrew/builds/117846634


Naïvely customizing form markup

It seems I'm running into some trouble with my forms when I try to do a couple of things.

If I take the exact markup otherwise output by > afFieldInput and insert it inside my #autoForm block helper, the form refuses to submit. beginSubmit and endSubmit are both called but onError gives an expectedBoolean (or similar) error – is this behavior correct? Is there anything I can do to not use > afFieldInput, such as registering my markup with the form somehow?

If I customize the output of > afFieldInput with jQuery in a rendered hook, the form also breaks. Specifically, I want to move some elements around a little and call template.$(".my-input").dropdown() or .checkbox() or other UI library code.

I'm currently reading up on creating custom inputs and other options, but I'd like to hear your opinion about what is happening in my case, as it may be the easiest way to go. Thanks.

Registering a custom input type is best. It's easy to do.


fix: clean up async calls with expired leases

fixes #2214
Changes:

The controller now calls the verb within the lease context, so a failure to heartbeat the lease cancels the grpc call
A new periodic task that cleans up async calls with a state of executing but without a lease

This happens after the lease has been reaped in a separate job
Cleaning up involves:

Scheduling retries/catches according to the policy
Triggering the origin-specific code (eg: fsm async calls need the next event table to be cleared)

Known issues:

If there is a repeating error cleaning up an async call, then it will just repeated fail
Java does not currently have a way to stop execution of the call that gets canceled, so it will always continue even when the async call's lease expires

Java does not currently have a way to stop execution of the call that gets canceled, so it will always continue even when the async call's lease expires

Can you file a ticket for this?


Can I use all 4 PS Cameras upside down?

As the title says it is there any way i can use all of my 4 cameras upside down.
Im asking this because i dont wanna use any tripods and just wanna mount them to my cieling with some tape or somthing. Is it possible?
Cheers Alex

Yes, you can use them upside down they just need to see the bulb.

wont they flip my movements upside down though?

No, i had one of my 3 cameras upside down and it worked just fine. So surely it would work with 4 cameras.

yea but thats the issue, you had one of the three not all of them upside down
Il try and see if it works

Place the cameras in any position you want and the Tracker Pose Calibration(the part with the calibration mat) will determine the orientation of your cameras upside down or not.
The only potential thing to think about in positioning is putting your cameras on their sides as you would then get a larger vertical than horizontal field of view(still not an issue in calibration.)

Oh thats good as thankyou man!


cargo test foo runs tests for mount and ptymaster_drop too

If I run, say, cargo test ptrace to run only tests with "ptrace" in their names, it also runs all the test_mount and test_ptymaster_drop tests. I suppose this is because they define their own main() and don't look at args().nth(1) to see if it should only run a subset of tests, or something?
(They run fast so this isn't really a problem, it's just confusing.)

Yep.  That's how cargo works.  It runs every test program with the argument "ptrace".  If you only want to run the integration tests,  and you want to pass a filter to them, you can use the confusing command line cargo test --test test ptrace


fix: allow to customize config values on create new page

This PR updates the extension to show the properties that can be customized when starting the VM in the create new page (memory, cpus, disksize and pull-secret-file).
They have been removed from the settings page to be in line with the other podman desktop extensions.
So, when clicking on create, it updates the config values of cpus/memory/disksize/pull-secret and if the start now option is true (by default) the VM is also started. Otherwise it just updates the config and register the provider to start/stop/delete the VM into Desktop.
Right now there is no way to customize/update dynamically the minimum value of a config so i had to create 2 entries for both the memory and cpus (one for openshift and one for minishift). They are displayed accordingly to the preset value.

This requires https://github.com/containers/podman-desktop/pull/7659

This should be ready for a review. You need to use the main branch of desktop as this PR requires https://github.com/containers/podman-desktop/pull/7659 to work.
There is just one missing part which is we should hide the create new ... button when the kubernetes connection is registered but it's not easy as i thought so i'm going to tackle it in a different PR.

FYI, the font for the pullsecret is not displayed (testing with https://github.com/containers/podman-desktop/pull/7995)

FYI, the font for the pullsecret is not displayed (testing with containers/podman-desktop#7995)

Nice catch 👍 It is a problem on podman desktop tough, i'm gonna fix it there

2 remarks:

some values for memory (4,5, 4.6 leads to errors but we cannot read the error message). Strange to understand but some values 4,5 and 4,6 or 5 and 5.1 leads to the same setting
when the machine is created, an emty screen is displayed:

2 remarks:

some values for memory (4,5, 4.6 leads to errors but we cannot read the error message). Strange to understand but some values 4,5 and 4,6 or 5 and 5.1 leads to the same setting

When did you face the error with the memory value? When setting the slider or when hitting create?

2 remarks:

some values for memory (4,5, 4.6 leads to errors but we cannot read the error message). Strange to understand but some values 4,5 and 4,6 or 5 and 5.1 leads to the same setting

When did you face the error with the memory value? When setting the slider or when hitting create?

No create as the value set for memory is rejected by HyperV

some values for memory (4,5, 4.6 leads to errors but we cannot read the error message). Strange to understand but some values 4,5 and 4,6 or 5 and 5.1 leads to the same setting

I was not able to replicate it. Tried to set the memory to 4.5 -5 and the vm was started without any problem.
I had an issue that occurred repeatedly when the VM was started and the cli was not able to reach it (ssh: handshake failed). Eventually i clean up everything and re-done the setup + start and worked fine. Maybe you had some similar thing? Can you try by deleting + cleanup + setup + start again?

when the machine is created, an emty screen is displayed:

After some investigation it seems that the problem is not that easy to solve. Basically the create new button that you see in the resources page, it is displayed if the KubernetesProviderConnectionFactory is initialized. And because it does not make any sense to have it once one VM is created, the factory was disposed to hide that button.
As a quick solution I just removed the dispose action. I think we should update podman desktop to provide an enablement clause to allow extensions to decide when the create new button should be visible or not. WDYT?

some values for memory (4,5, 4.6 leads to errors but we cannot read the error message). Strange to understand but some values 4,5 and 4,6 or 5 and 5.1 leads to the same setting

I was not able to replicate it. Tried to set the memory to 4.5 -5 and the vm was started without any problem. I had an issue that occurred repeatedly when the VM was started and the cli was not able to reach it (ssh: handshake failed). Eventually i clean up everything and re-done the setup + start and worked fine. Maybe you had some similar thing? Can you try by deleting + cleanup + setup + start again?

when the machine is created, an emty screen is displayed:

After some investigation it seems that the problem is not that easy to solve. Basically the create new button that you see in the resources page, it is displayed if the KubernetesProviderConnectionFactory is initialized. And because it does not make any sense to have it once one VM is created, the factory was disposed to hide that button. As a quick solution I just removed the dispose action. I think we should update podman desktop to provide an enablement clause to allow extensions to decide when the create new button should be visible or not. WDYT?

I don't understand fully because when I create a Kind cluster (I suppose this is also KubernetesProviderConnectionFactory), I have this screen:

So what is the difference ?

I don't understand fully because when I create a Kind cluster (I suppose this is also KubernetesProviderConnectionFactory), I have this screen:

So what is the difference ?

With the latest commit (remove of the disposable) you should see the same when the creation + start process of crc is completed.
The difference should be about this button

For kind it makes sense to have it always there because you can create X cluster. For crc, you can just create one VM, so it would be great if the create button is hidden when a VM is there.
By disposing the factory we were able to achieve this behavior. But if we dispose the factory, we would see the empty screen as you noted above.

I don't understand fully because when I create a Kind cluster (I suppose this is also KubernetesProviderConnectionFactory), I have this screen:

So what is the difference ?

With the latest commit (remove of the disposable) you should see the same when the creation + start process of crc is completed. The difference should be about this button
For kind it makes sense to have it always there because you can create X cluster. For crc, you can just create one VM, so it would be great if the create button is hidden when a VM is there.
By disposing the factory we were able to achieve this behavior. But if we dispose the factory, we would see the empty screen as you noted above when the start process is completed

I think we are not in sync: I'm talking about the screen that is displayed when the VM has been created: for kind I have to button to return to the Resources page. For CRC I have

I don't understand fully because when I create a Kind cluster (I suppose this is also KubernetesProviderConnectionFactory), I have this screen:

So what is the difference ?

With the latest commit (remove of the disposable) you should see the same when the creation + start process of crc is completed. The difference should be about this button
For kind it makes sense to have it always there because you can create X cluster. For crc, you can just create one VM, so it would be great if the create button is hidden when a VM is there.
By disposing the factory we were able to achieve this behavior. But if we dispose the factory, we would see the empty screen as you noted above when the start process is completed

I think we are not in sync: for kind I have a screen with a button that returns to the Resources page. For CRC I have an empty screen

I think we are not in sync: for kind I have a screen with a button that returns to the Resources page. For CRC I have an empty screen

Have you tried with the latest commit?

I think we are not in sync: for kind I have a screen with a button that returns to the Resources page. For CRC I have an empty screen

Have you tried with the latest commit?

Not yet :)

Not yet :)

Ah ok 👍
This is what you should see (i cut the gif bc it was 3 mins long lol)

I still have an issue with VM start failure not reported but it is not related to this PR so I will open a follow up issue

Yeah, I'll investigate it as well. I'm worried that when using the minimum amount of memory allowed, the conversion is not optimal and the resources given to micro shift are not enough. I'll give this a look when I have some free time


New Outlook

Hi, I have been trying to get this to work with New Outlook.
Have you perhaps had a look at this solution for New outlook?
It is very new still and I am not sure if it would even be possible to manage email signatures in the same way with New outlook.

I've looked into this myself as well.
Outlook seemed to have added the user email to the files and folders related to the signature (in %appdata%\Microsoft\Signatures
It's a bit more hand-work, but I got it working by doing the following:

Create a new signature within the program. (I think you can copy/paste the old one over; Just make sure to do it the regular route)
Close Outlook
Go to the signatures folder and take note of the folder suffixes (_files for example. It's localized.)
Replace the standard user-specific data from the htm, rtf and txt files like usual and also replace the folder references in the htm file to the images, filelist etc
Add the following to the install.ps1, after the foreach loop and before Stop-Transcript file. Replace _bestanden with the proper folder suffix:

$itemNames = Get-ChildItem -Path "$($env:APPDATA)\Microsoft\Signatures\"
foreach ($itemName in $itemNames) {
    if ($itemName.Name -like "*.htm" -or $itemName.Name -like "*.rtf" -or $itemName.Name -like "*.txt") {
        $itemName | Rename-Item -NewName { $itemName.BaseName + " (" + $userObject.Mail + ")" + $itemName.Extension };
    } else {
        $itemName | Rename-Item -NewName { $itemName.BaseName + " (" + $userObject.Mail + ")_bestanden" + $itemName.Extension };
    }
}

That should be enough to make it work again. You can check it by manually executing the install.ps1 script with powershell.

Hi, thanks for the feedback, i had a look at the above, and it makes sense that this would work for the latest versions of Outlook using the Roaming signature.
It seems this however does not work for Outlook New, the Latest version of Outlook a user would use when using Copilot, enabled via the toggle in Outlook classic.
Microsoft Outlook Version 1.2023.1129.100 (Production).
Client Version is<PHONE_NUMBER>2.05 .
To me it seems like you can create a Email signature manually, but this is not stored in %appdata%\Microsoft\Signatures, instead it seems to be stored on OWA only.. and replicates from there to all Outlook clients.. I am not sure if you have seen the same?
To me it seems like there is no way to actually manage a corporate Signature when using Outlook New, unless i am missging something?
https://support.microsoft.com/en-us/office/getting-started-with-the-new-outlook-for-windows-656bb8d9-5a60-49b2-a98b-ba7822bc7627

I've noticed something identical.
I also noticed it to synchronize signatures at some point. I suspect it to be either on (app) startup or when using the toggle to switch between old and new. It's not ideal, but I do wonder if we can use this functionality to push local to cloud somehow.
But as I'm also still missing local archive files, I recommend users at work to stay on "old" for now.


Markdown files and sections broken

Not sure who is maintaining this project, but it is riddled with bugs.
A markdown file that extends a layout and has a section is producing a bug where it is rendering off the page entirely. After closer examination the section is moved into the header tag of the page.
---
extends: _layouts.course
section: content
---

Here is some sample content...

This results in the section being placed above the head tag on the HTML. Bizarre.

Can you publish a repository that demonstrates this issue? I use this feature of Jigsaw on just about every static site I maintain and have never encountered this problem.
This page for example:
https://adamwathan.me/2014/04/12/theres-a-model-hiding-in-your-rest-api/
...is generated from this Markdown:
---
extends: _layouts.post
section: post
title: "There's a Model Hiding in Your REST API"
author: Adam Wathan
date: 2014-04-12
---

Last week I wrote a post for the Vehikl blog about using the constraints of REST to force you to think more critically about how you are modeling your system.

Check it out here:

[http://transmission.vehikl.com/theres-a-model-hiding-in-your-rest-api/](http://transmission.vehikl.com/theres-a-model-hiding-in-your-rest-api/)

...and everything renders in the right spot, not in the head like you are suggesting.

All of the markdown that powers the Jigsaw docs are also setup this way as you can see here:
https://github.com/tightenco/jigsaw-site/tree/master/source/docs
...and everything renders where it's supposed to, so there must be something else at play here.
If you can upload a project that reproduces this I'm happy to take a look.

Thanks @adamwathan. Love the project. Will upload an example that duplicates the issue soon.

@adamwathan the issue has been solved. It was an error on my end. Thanks.

@adamwathan the issue has been solved. It was an error on my end. Thanks.

Actually @adamwathan I thought I fixed it, but the error is still happening. Let me try and make another repo for you.

It's likely that your section name content doesn't match up with your parent template. Post a repo, and I'll be happy to take a look at your code and help you troubleshoot.


Add intro pages

This PR adds an overview and a getting started page to the Docs Guide project.
The getting started is called "how to use this guide" to avoid confusion with the (future) document telling how to create a getting started guide.
Some links in the "Create a doc project" tutorial are changed to use intersphinx, as it wasn't in use when the tutorial was initially written.
Closes #94
Closes #95

On hold until #166 is merged and rebase to see the actual diff in this PR


Feature/1615 - Allow ContentVisitor to view cq:Tag as a "content type" resource

Via request from: http://disq.us/p/1y2x8u4

Pull Request Test Coverage Report for Build 3546

7 of 7 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 42.107%

Totals

Change from base Build 3545:
-0.005%

Covered Lines:
9603

Relevant Lines:
22806

💛  - Coveralls


cleanup linter and typecheck issues for smqtk - [closed]

In GitLab by @Cookt2 on Oct 27, 2020, 16:43
Merges dev/smqtk-linter-changes -> smqtk
Cleans up the latest SMQTK/tinker code to adhere to CI checks.

In GitLab by @Cookt2 on Oct 27, 2020, 16:44
@waxlamp PTAL, this gets the CI green on the smqtk branch.

In GitLab by @Cookt2 on Oct 27, 2020, 16:47
mentioned in merge request !46

In GitLab by @waxlamp on Oct 27, 2020, 18:32
Thanks for doing this, @Cookt2. I was in the midst of fixing the pipeline, and making a few other changes, when this came through, so I'm going to close this in favor of the stuff on smqtk.

In GitLab by @waxlamp on Oct 27, 2020, 18:33
resolved all threads


update dev-base docker image to include a more recent version of python and optional poetry

Noting that this is to track updates to ontobio which require a bump on python version.

Noting that the first run of the new dev-base docker image on pipeline/master has finished without error (as far as we can tell).


Maybe put instance in parameter instead of path

Currently we have to take care not to prefix special paths (like /auth/… or /api/…) with the instance, like we do for most other links.
Idea:
Maybe we could always put the instance in an query string instead (e.g. ?instance=de) this way it would just be ignored for special paths instead of breaking everything.

In contrast to a query string, the instance in the path can be resolved statically (i.e. at compile-time vs. at run-time). This might be a requirement for a i18n library (which we should include at some point). For example, next-translate creates the pages for each language at compile-time. Not sure how i18n added to Next.js v10.0.0 works, there it might also be a requirement to have the information at compile-time.
IMHO: we should have a plan for how to handle i18n in the future (e.g. with a library) before we change the approach.

@inyono i def. agree with your conclusion 👍
Not sure about the first part. It was my understanding, that the query string is also part of a static url (in contrast to e.g. the fragment identifier/hash).


mentions don't work for nonascii characters

it is currently impossible to mention a discord user where the nickname ends or starts with a non-ascii character.
this is because javascript doesn't support unicode properly for word boundaries \b
as used here:
new RegExp(
  `\\b(${matcher})(?=\\b)`
  , "mig"), `<@!${member.id}>`,
);

https://github.com/Half-Shot/matrix-appservice-discord/blob/develop/src/matrixeventprocessor.ts#L87
and this behavior will apparently also not change with the /u flag:
https://github.com/mathiasbynens/es-regexp-unicode-character-class-escapes/issues/1#issuecomment-62251775
so something like this could work
/(?<=\W|^)(${matcher})(?=\W|$)/igmu

not using \w since that doesn't support astral characters?
but idk I'm not too familiar with typescript so you'd probably have to transpile it to something compliant with es5 and of course think around the lookbehind.

I found there were a few issues with using \W|^ so I've gone with:
const WORD_BOUNDARY = "(^|\:|\@|\#|```|\\s|$|,)";
const regex = new RegExp(`(?<=${WORD_BOUNDARY})(${matcher})(?=${WORD_BOUNDARY})`, "igmu");

Which works so long as you don't mind dropping <9.X compatibility, which bothers me. The lookbehind feature is new.

Merged. Please re-open if this is still affecting you @ZerataX

works great, too bad lookbehind is this new. thanks!


Added two new cmdlets, incremented ModuleVersion

Added cmdlet to return/display all checked out files
Added cmdlet to check in all checked out files (useful for migrations to Office 365)
Removed refernce to invalid cmdlet
Incremented to ModuleVersion 1.0.0..2

This change is

Review status: 0 of 5 files reviewed at latest revision, 10 unresolved discussions.

PowerShell/Modules/PFE-SharePoint/PFE-SharePoint.psd1, line 21 at r1 (raw file):

		       "Cmdlets\Get-RegistryCredential\Get-RegistryCredential.psm1",
           "Cmdlets\New-RegistryCredential\New-RegistryCredential.psm1",
           "Cmdlets\Get-CheckedOutFilesInList\Get-CheckedOutFilesInList.psm1"

[Picky] Try keeping the tabulation aligned;

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 2 at r1 (raw file):

<#PSScriptInfo

We should not have a PSScriptInfo block in modules. We should however standardize a comment template at the top of each cmdlet to standardize information about company, description and author. How about something as simple as the following?
<#
Author:        Roger Cormier
Company:   Microsoft
Description: This cmdlet does abcd….
#>

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 44 at r1 (raw file):

    [CmdletBinding()]
    param(
    #SPList Pipebind

Instead of adding information in comments, how about we use the HelpMessage attribute?
[parameter(HelpMessage="Represents the SPListBinding", Mandatory=$true,ValueFromPipeline=$True, ValueFromPipelineByPropertyName, ParameterSetName="ListFromPipeline", position=0))]

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 50 at r1 (raw file):

    )

    Begin

We may want to remove the Begin block since we are not initializing anything in it. Alternatively, we may want to do an additional check to ensure the piped SPList is not null and throw an error if it is.

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 51 at r1 (raw file):

Begin
{

}

Quoted 4 lines of code…
>     Process
>     {
>         $CheckedOutFiles = @{}
>         Write-Verbose "Getting checked out files"

>
Quoted 4 lines of code…
>         foreach( $File in ($List.Items | Where-Object { $_.file.checkoutstatus -ne "None"}))
>         {
>             $CheckedOutFiles.Add($File.url, $File)
>         }

>
>     }
>
Quoted 4 lines of code…
>     End
>     {
>         Return $CheckedOutFiles
>     }

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 2 at r1 (raw file):

<#PSScriptInfo

Same as above.

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 44 at r1 (raw file):

[CmdletBinding()]
param(
[Parameter (Mandatory=$True, ValueFromPipeline=$True, ValueFromPipelineByPropertyName=$True)]

Use HelpMessage to provide additional info on what this does.

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 47 at r1 (raw file):

[Alias ('URL')]
[String[]]$Site,
[Parameter (Mandatory=$False)]

Again, provide HelpMessage to detail what this param is for.

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 75 at r1 (raw file):

                try
                {
                $list.GetItemById(

[Picky] Ensure proper tabulation

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 87 at r1 (raw file):

        $web.dispose()
    }

Dispose of your SPSite here.

Comments from Reviewable

Just make sure you review each comment. If you agree with them and implemented the change, you can always click the Done button instead of putting in a custom message.

Review status: 0 of 8 files reviewed at latest revision, 10 unresolved discussions.

Comments from Reviewable

Ah, I didn't know that, I'm new to reviewable :)

Reviewed 2 of 5 files at r1, 6 of 6 files at r2.
Review status: all files reviewed at latest revision, 10 unresolved discussions.

PowerShell/Modules/PFE-SharePoint/PFE-SharePoint.psd1, line 21 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
[Picky] Try keeping the tabulation aligned;

I checked in my copy locally, and the tabulation is aligned (sent screenshot via e-mail).  Curious why it's not aligned once it gets in github.  Did  notice a missing comma - so fixed that anyway.

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 2 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
We should not have a PSScriptInfo block in modules. We should however standardize a comment template at the top of each cmdlet to standardize information about company, description and author. How about something as simple as the following?
<#
Author:        Roger Cormier
Company:   Microsoft
Description: This cmdlet does abcd….
#>

Removed ScriptInfo and standardized using this template

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 44 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
Instead of adding information in comments, how about we use the HelpMessage attribute?
[parameter(HelpMessage="Represents the SPListBinding", Mandatory=$true,ValueFromPipeline=$True, ValueFromPipelineByPropertyName, ParameterSetName="ListFromPipeline", position=0))]

Implemented HelpMessage attribute, as suggested

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 50 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
We may want to remove the Begin block since we are not initializing anything in it. Alternatively, we may want to do an additional check to ensure the piped SPList is not null and throw an error if it is.

Added logic to check whether or not the list is [Microsoft.SharePoint.SPDocumentLibrary] - exit if not.  This way we don't waste our time processing list types that don't support check-in/check-out features.

PowerShell/Modules/PFE-SharePoint/Cmdlets/Get-CheckedOutFilesInList/Get-CheckedOutFilesInList.psm1, line 51 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…

Begin
{

}

Process
{
$CheckedOutFiles = @{}
Write-Verbose "Getting checked out files"

foreach( $File in ($List.Items | Where-Object { $_.file.checkoutstatus -ne "None"}))
{
$CheckedOutFiles.Add($File.url, $File)
}

}

End
{
Return $CheckedOutFiles
}

Same, added logic in begin to make sure we're actually targetting a document library and not something that doesn't support check-in/check-out

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 2 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
Same as above.

Standardized on the recommended template

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 44 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
Use HelpMessage to provide additional info on what this does.

Implemented

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 47 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
Again, provide HelpMessage to detail what this param is for.

Implemented

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 75 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
[Picky] Ensure proper tabulation

Updated indentation

PowerShell/Modules/PFE-SharePoint/Cmdlets/New-BulkFileCheckIn/New-BulkFileCheckIn.psm1, line 87 at r1 (raw file):
Previously, NikCharlebois (Nik Charlebois) wrote…
Dispose of your SPSite here.

Implemented

Comments from Reviewable

Review status: all files reviewed at latest revision, 10 unresolved discussions.

Comments from Reviewable


upgrade docusaurus to v3

Hello everyone, I am an open-source enthusiast and product manager from @DaoCloud, specializing in maintaining websites and Chinese documentation for open-source projects.
I noticed that the construction of HAMi's documentation and website has just begun, and the Chinese documentation is not yet ready; for example, phrases like "karmada website" have not been adjusted. Coincidentally, I am also one of the main maintainers of karmada/website, so I plan to start with the documentation, first upgrading Docusaurus to the latest version to facilitate subsequent work.
This is my first PR, and moving forward, I hope to contribute by working on HAMi's website.
In fact, my expertise lies in product management. Therefore, in addition to contributing to documentation and technical content, I also hope to leverage my professional background to explore with everyone how to better productize open-source technologies.

Amazing contribution
Thank you very much


NODE-1452: convert codebase to TypeScript

Description
This patch constitutes the first phase of converting the whole codebase to TypeScript

[x] Use git to move all files from lib to a new src directory, preserving history as much as possible
[x] Convert all files in src to use TypeScript with minimal changes to the existing code

use the newly developed ts-convert.sh script to automate as much of the conversion as possible
this first pass will not be ideal, and will likely make heavy use of any

[x] Convert our test runner to use ts-node to run all tests against TypeScript-ified code

Maintain all tests in vanilla JavaScript

[x] Add a prepublish script for using the existing TypeScript "pipeline" script to generate readable transpiled javascript before publishing the module

What changed?
everything
Are there any files to ignore?

It looks like some of the git mvs were screwed up, closing to correct those

reopening, looks like this might just be issues with GitHub's UI


fastlane beta command not generating ipa file

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I executed initialised fastlane init in my ios folder of the app and provided my Apple ID & password. I also provided build_app lane in the Fastfile. But there is error which says Could not find action, lane or variable 'build_app'.
Command executed
fastlane init
fastlane beta
Complete output when running fastlane, including the stack trace and command used
[15:35:02]: -------------------------------------------------
[15:35:02]: --- Step: Verifying required fastlane version ---
[15:35:02]: -------------------------------------------------
[15:35:02]: Your fastlane version 2.28.3 matches the minimum requirement of 2.28.3  ✅
[15:35:02]: ------------------------------
[15:35:02]: --- Step: default_platform ---
[15:35:02]: ------------------------------
[15:35:02]: Driving the lane 'ios beta' 🚀
[15:35:02]: -----------------------
[15:35:02]: --- Step: cocoapods ---
[15:35:02]: -----------------------
[15:35:03]: $ pod install
[15:35:13]: ▸ Detected React Native module pods for RNGestureHandler, react-native-netinfo, and react-native-splash-screen
[15:35:13]: ▸ Analyzing dependencies
[15:35:23]: ▸ Downloading dependencies
[15:35:23]: ▸ Generating Pods project
[15:35:23]: ▸ Integrating client project
[15:35:23]: ▸ Pod installation complete! There are 35 dependencies from the Podfile and 33 total pods installed.
+------------------+----------+
|        Lane Context         |
+------------------+----------+
| DEFAULT_PLATFORM | ios      |
| PLATFORM_NAME    | ios      |
| LANE_NAME        | ios beta |
+------------------+----------+
[15:35:24]: Could not find action, lane or variable 'build_app'. Check out the documentation for more details: https://docs.fastlane.tools/actions
+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | Verifying required  | 0           |
|      | fastlane version    |             |
| 2    | default_platform    | 0           |
| 3    | cocoapods           | 21          |
+------+---------------------+-------------+
[15:35:24]: fastlane finished with errors

[!] Could not find action, lane or variable 'build_app'. Check out the documentation for more details: https://docs.fastlane.tools/actions

 [REPLACE THIS WITH YOUR INFORMATION]

Environment
Below is the output from fastlane env:
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.5

Ruby
2.2.4

Bundler?
false

Git
git version 2.21.0 (Apple Git-122.2)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.14.5 (18F2059)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.3

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.28.3"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    cocoapods

  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
	build_app(scheme: "searchtoiletapp")
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: "searchtoiletapp") # Build your app - more options available
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :release do
    # match(type: "appstore")
    # snapshot
    gym(scheme: "searchtoiletapp") # Build your app - more options available
    deliver(force: true)
    # frameit
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier "searchtoiletapp" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

fastlane gems

Gem
Version
Update-Status

fastlane
2.28.3
💥 Check failed

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
1.5.1

atomos
0.1.3

CFPropertyList
2.3.5

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.14.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.1

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.6

excon
0.71.1

faraday
0.17.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.0

gh_inspector
1.1.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.2.2

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.28

json
1.8.1

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.3.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.6

faraday_middleware
0.13.1

generated on: 2020-01-08

 [REPLACE THIS WITH YOUR INFORMATION]

2.28.3

That is super old, you should install a more recent version.


Possibility to flag a package as broken or out-of-date

Description of the new feature/enhancement
Please implement a way to flag a package as broken or outdated.
As e.g. in AUR: https://aur.archlinux.org/ or Chocolatey

Prevents useless download and installation attempts.
Proposed technical implementation details (optional)

Let WinGet ignore these packages.

Why wouldn't we just remove the manifests?

I meant a standardized process to report such packages. They should then be reviewed, fixed or removed.

Be sure to add a 👍 to https://github.com/microsoft/winget-cli/issues/920
We've been discussing the value of tombstoning or somehow marking manifests as deprecated or obsolete so we can retain useful information like versions, product codes, etc.


System.Linq.Dynamic.Core.Exceptions.ParseException: 'No 'it' is in scope'

Consider Customer class as following:
public class Customer
{
     public int Id { get; set; }
}

Using these codes:
System.Linq.Dynamic.Core.DynamicExpressionParser.ParseLambda(new[] { Expression.Parameter(typeof(Customer), "foo") }, typeof(bool), "foo.Id = 1");
System.Linq.Dynamic.Core.DynamicExpressionParser.ParseLambda(new[] { Expression.Parameter(typeof(Customer), "it") }, typeof(bool), "it.Id = 1");

First line is working fine, but calling second line will raise an exception System.Linq.Dynamic.Core.Exceptions.ParseException: 'No 'it' is in scope'
Are there any story related to word "it"?

The keyword it is reserved and van be used like:
var result = await (_context.Blogs.AsQueryable() as IQueryable).FirstAsync("it.BlogId > 0");


fetch FT metadata from new Token Metadata API

Could the Explorer start fetching FT metadata from the new Token Metadata API? This will fix the current issue caused by the 302 redirection we put in place in the Stacks API from the old endpoints to the new
We should add the metadata API as a configurable ENV var for devs who want to run their own instance.
You will be able to use a TS client once this PR is merged: https://github.com/hirosystems/token-metadata-api/pull/134

This one should be fix now, Thanks Rafa 🙏


SzStandaloneGraph, SzPrefDictComponent, preference changes, datasource colors

These are the associated changed to the sdk-components to support the new pop-out(standalone graph) component. #105

pop out graph icon
new "example/search-in-graph" project to show search integrating directly with graph
new SzPrefDictComponent for displaying pref(s) that are object/key/value based(ie json object)
added dataSourceColors configuration to SzPreferencesComponent
added SzEntityDetailGraphFilterComponent
added SzStandaloneGraphComponent, a embeddable graph components designed to run in it's own context or near-to.
added new SzDataSourcesService class for retrieving the datasources from the api server instance.
modified existing graph code:

properties added
	- showMatchKeyControl
	- showFiltersControl
	- showPopOutIcon
	- dataSourcesFiltered
	- dataSourceColors
	- popOutIconPosition
	- queriedEntitiesColor

methods added
	- popoutClick
	- entityNodecolorsByDataSource
	- entityNodeFilterByDataSource
	- entityNodeColors
	- isEntityNodeInDataSource
	- isEntityNodeInDataSources
	- isEntityNodeNotInDataSources
	- isEntityNodeInQuery
	- setEntityNodeFillColor

event emitters added
	- onPopOutClick
	- onNetworkLoaded

added new layout-rail layout for ... well, exactly what it sounds like, a rail version of the entity detail component. (see screenshot)

Issue number: #105


run the e2e tests on gh gpu actions runner

putting this on hold since GH GPU runners are T4 and flash-attention 2 doesn't support that arch. We could could split out the various flash attention tests, but that wouldn't help much since we'd still have a lot of extra overhead trying to build docker images on cold GH GPU runners without images in the docker cache.

Would sky launch --down --gpus=xxx <command> tick the boxes? It basically runs the job and auto-terminate after it exits. So the billing is for the job duration only (plus a bit of setup time). Plus, use any GPUs as desired potentially with spot to save costs.
You can upload secrets to your repo -> Settings -> Secrets and variables -> Actions -> Repository secrets:

Example of passing in cloud keys in GH Action: https://github.com/skypilot-org/skypilot-catalog/blob/master/.github/workflows/update-aws-catalog.yml#L45-L47


Documentation: Update terminology for latest IntelliJ version

[x] I have read the guidelines for submitting issues

🐛 Describe the bug
Terminology change inside IntelliJ for including a new Gradle project.
⚠ Current behavior
The Dev environment documentation states that you should Select "Import Gradle Project"
✅ Expected behavior
As of at least IntelliJ 2022.2.1, the menu option has changed to "Link Gradle Project"
💣 Steps to reproduce
Follow  the Dev environment documentation and compare to the latest IntelliJ
📱 Tech info
N/A

For trivial changes like that, where you're 90% sure we're going to accept them, and especially if you've already made the changes, no need to create an issue, you can submit the PR directly 😉


Fixes the union deserializer code generation in Go

Fixes: https://github.com/microsoft/kiota/issues/4844
What
When generating Go based SDKs from GitHub's OpenAPI definitions we noticed that the GetFieldDeserializers function was empty for any operations using discriminators and OneOf
Why
It turns out that the issue is in WriteDeserializerBodyForUnionModel or at least why the method body is not getting generated.
So the LINQ statement for Go is:
var otherPropGetters = parentClass
 .GetPropertiesOfKind(CodePropertyKind.Custom)
 .Where(static x => !x.ExistsInBaseType && x.Getter != null)
 .Where(static x => x.Type is CodeType propertyType && !propertyType.IsCollection && propertyType.TypeDefinition is CodeClass)
 .OrderBy(static x => x, CodePropertyTypeForwardComparer)
 .ThenBy(static x => x.Name)
 .Select(static x => x.Getter!.Name.ToFirstCharacterUpperCase())
 .ToArray();

The problem is that for these discriminators the TypeDefinition is not of type CodeClass but of type CodeInterface
When the LINQ is rewritten like this, it works:
var otherPropGetters = parentClass
 .GetPropertiesOfKind(CodePropertyKind.Custom)
 .Where(static x => !x.ExistsInBaseType && x.Getter != null)
 .Where(static x => x.Type is CodeType propertyType && !propertyType.IsCollection && propertyType.TypeDefinition is CodeInterface)
 .OrderBy(static x => x, CodePropertyTypeForwardComparer)
 .ThenBy(static x => x.Name)
 .Select(static x => x.Getter!.Name.ToFirstCharacterUpperCase())
 .ToArray();

[x] Tests have been updated
[x] Change log has been updated
[x] Verified to be working using GitHub's OpenAPI definitions

@baywet we have question regarding the inner workings of kiota to help us have a better understanding on things related to this PR if you have time:
Do union, intersection, and inheritance deserializers map to OneOf, AnyOf, and AllOf usage in OpenAPI? Based on some preliminary testing there does seem to be a correlation. If they do not, then what do union, intersection, and inheritance represent here?
Also, there are other instances of CodeClass being used in CodeMethodWriter.  Instances here and here.  Modifying these cause fairly significant changes in the code that is generated (according to the unit tests).
Our question is, is there a way to definitively determine what the expected output should be?  Since the delta is fairly large here this tells me that either the current source that is generated pre-fix (converting CodeClass to CodeInterface) is currently not working or I am approaching the problem wrong - which my guess is the actual issue here.
Any guidance would be appreciated. Also, let me know what your thoughts are around landing this change, if you approve of it, and then working on the other areas in a separate PR.


RedditAuthentication.TokenAuth() dosent work

When i run:
from Reddit_ChatBot_Python import RedditAuthentication
from Reddit_ChatBot_Python import ChatBot

reddit_authentication = RedditAuthentication.TokenAuth(token="REDACTED")

chatbot = ChatBot(print_chat=True,
                  store_session=True,
                  log_websocket_frames=False,
                  authentication=reddit_authentication
                  )

It returns:
raceback (most recent call last):
  File "/home/anon/r.py", line 13, in <module>
    chatbot = ChatBot(print_chat=True,
  File "/home/anon/.local/lib/python3.10/site-packages/Reddit_ChatBot_Python/chatbot.py", line 22, in __init__
    sb_access_token, user_id = self._load_session(authentication._get_repr_pkl())
  File "/home/anon/.local/lib/python3.10/site-packages/Reddit_ChatBot_Python/chatbot.py", line 225, in _load_session
    self.__r_authentication.authenticate()
  File "/home/anon/.local/lib/python3.10/site-packages/Reddit_ChatBot_Python/reddit_auth.py", line 23, in authenticate
    self._get_userid_sb_token()
  File "/home/anon/.local/lib/python3.10/site-packages/Reddit_ChatBot_Python/reddit_auth.py", line 32, in _get_userid_sb_token
    self.sb_access_token = sb_token_j['sb_access_token']
KeyError: 'sb_access_token'

I know for a fact that the access_token works because i have used it in my own POST requests. And I checked out your code, we are using the same kind of token. Login with Username and Password works so i find that a bit strange.

where did you get the token from?

where did you get the token from

 client_id = 'REDACTED'
    client_secret = 'REDACTED'

    data = { 'grant_type': 'authorization_code',
        'code': code,
        'redirect_uri': 'http://localhost:3000/login/callback'
        }
    headers = {
        'User-agent': 'your bot 0.1 by /u/swedenismycity0403'
        }
    url = 'https://www.reddit.com/api/v1/access_token/'

    r = requests.post(url, data=data, headers=headers, auth=(client_id, client_secret))
    access_token = r.json()['access_token']

I know this works because i've used it to make requests like this:

    headers = {
        "Authorization": "bearer "+access_token,
        'User-agent': 'yourbot 0.1 by /u/swedenismycity0403'
    }
    response = requests.get("https://oauth.reddit.com/api/v1/me", headers=headers)
    print(response.json()['id']) # returns 'swedensimycity0403'

read the first paragraph of the readme

works either with reddit username & password or the api token (not a regular one you get from your registered app as it's not fully scoped)

the only way to get that token is to use either RedditAuthentication.PasswordAuth or by inspecting the requests done by the browser.

I don't get it.
TokenAuth() is extended by _RedditAuthBase. And when you initialize TokenAuth() you use the token variable to assign api.token. api.token stores the access_token you use with oauth, right?
And since api.token is assigned by the token variable in TokenAuth() they must be the same.

I don't get it.
TokenAuth() is extended by _RedditAuthBase. And when you initialize TokenAuth() you use the token variable to assign api.token. api.token stores the access_token you use with oauth, right?
And since api.token is assigned by the token variable in TokenAuth() they must be the same.

RedditAuthBase imitates the reddit mobile app which is btw against the reddit tos. thats how it obtains the fully scoped token.


Calendar example does not match between code and actual component

💬 Question
Hi team, thanks for the excellent work about the UI library, I really love it!
Inside the Calendar component of the doc, there is a section about:

To render custom cells, renderDay, renderMonth and renderYear properties may be used.

From the component, it seems there is some custom rendering of date cell (there is price at the bottom of each date cell)

However the code view does not have the renderDay. Is there a mismatch?
Also, I would like to check with the team if it is possible that we preserve the normal rendering but we append some more content to the cell? e.g. a bar at the bottom of cell. The reason is that I do want to preserve the current rendering but still append some more contents.
UI Kitten and Eva version

Package
Version

@eva-design/eva

@ui-kitten/components

did you find the code?


Training pixart sigma with any aspect ratio?

I have a question: How to train pixart sigma with any aspect ratio (for example: image 960x1280 pixel). Can you describe details in step by step? Thank you!

This part is done during the dataset sampling. You can find it here: https://github.com/PixArt-alpha/PixArt-sigma/blob/f999a89ce86d2dc2b65d01e77602a4d2f4ddec85/train_scripts/train.py#L431

I see that: here is config for aspect ratio.

Can I add any aspect ratio into config ? (example: add 0.625 aspect ratio with 720x1280).
When adding like this, does it decrease performance ?

This part is done during the dataset sampling. You can find it here:
https://github.com/PixArt-alpha/PixArt-sigma/blob/f999a89ce86d2dc2b65d01e77602a4d2f4ddec85/train_scripts/train.py#L431

Of course, you can add any aspect ratio into the config. It'll not cause a decreasing in performance IMO.


release next version

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


./lint.sh --mode=fix issues a warning

warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /Users/tushar/Documents/Projects/tailcall/cloudflare/Cargo.toml
workspace: /Users/tushar/Documents/Projects/tailcall/Cargo.toml

Expectations
Fix the cargo files to make sure there are no warnings issued.

/bounty 15$

/attempt #1109


[MENFORCER-195] [MENFORCER-269] Added tests to validate wildcard support

[MENFORCER-195] [MENFORCER-269] Added tests to validate wildcard support for DependencyConvergence and RequireUpperBound with MNG-6713 (https://github.com/apache/maven/pull/269)
Following this checklist to help us incorporate your
contribution quickly and easily:

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

/ping @rfscholte to see if this should be merged since this is in: https://github.com/apache/maven/pull/269


Refactor fs.fnl to use nvim 0.8 builtins

Hi,
I've seen that in the README was stated that Conjure works with neovim 0.7 or above. I've found in fs.fnl that vim.fse.normalize is been used, witch is a nvim 0.8+ feature so I've updated the minimum version required in the README and plugin/conjure.vim. With this version bump we unlock a lot of functionality that can replace some of the old batteries that were created.
I've also took the liberty to convert the plugin/conjure.vim to lua so we can use vim.notify instead of echoerr. vim.notify can integrate with other plugins and change the displaying of notifications (see example noice.nvim)

Lovely, thanks!

I you are ok with it I can make other PRs to move the code to built in APIs.
I'm quite familiar with neovim std library so I can help.
My question would be do we have a clear minimum nvim version that we are targeting? For reference usually plugin authors supports the current stable release (now 0.10.*) and maybe the previous (now 0.9).

So I've been trying to support as far back as I can without it causing headaches with lots of polyfilling and if statements in the code. There are some branches where I have to support two different APIs but not many. In hindsight I should've collected all version support branches in a specific module that makes it VERY obvious for when those things get removed.
I worry about targeting stable because I'll be fine on Arch but our Ubuntu brothers and sisters might be a little upset about that if we don't have a good reason for it. Version churn for the sake of churn smells a little too npm for my liking so I try to avoid it.
So, that is to say, lets try to support at LEAST the previous version, hopefully further back if possible. But this is all extremely subjective, we have to go with our gut. If we drop support for 0.8 in favour of 0.9 but the code looks identical if you squint and there's no benefit to the user, we shouldn't do it.
If however we get things like first class Lua callbacks and can eliminate all the Vim Script bridge code with string interpolation all over the place, then we should DEFINITELY do that. Which is a thing I did a while back, dropping support for old versions in order to remove the hacky Vim -> Lua callbacks through strings was DEFINITELY worth it. This is just an example to highlight the sort of big improvements I think are definitely worth it, but we can judge it on a case by case basis.
So, please feel free to drop usage of my custom Fennel in favour of built in APIs! If it will break support for older versions though let's weigh that up carefully against the need to move the version support line only when we need to, not because we want to.

Ok, gotcha! I do believe that sticking with 0.8 is really a good sweet spot.

In hindsight I should've collected all version support branches in a specific module that makes it VERY obvious for when those things get removed.

I do believe that centralize the polyfills can be a good thing to make the transition easier in the future.
Also do we bother with native Windows support? Looking at the code we are very UNIX biased. I don't care about it but if you care I can also backport some of the latest fs.* stuff from neovim 0.10 that helps a lot with Windows support.

We should try our best to support windows yeah, we definitely have windows
users. Really I'd like to get the test suite under GH actions and Linux,
Windows, Mac if possible. For now a best effort and hoping is all I've been
doing, but I can't work out how to run it and check things on windows
anyway right now, I'm useless with dev tooling on windows.
On Mon, 23 Dec 2024, 12:17 Luca Saccarola, @.***> wrote:

Ok, gotcha! I do believe that sticking with 0.8 is really a good sweet
spot.
In hindsight I should've collected all version support branches in a
specific module that makes it VERY obvious for when those things get
removed.
I do believe that centralize the polyfills can be a good thing to make the
transition easier in the future.
Also do we bother with native Windows support? Looking at the code we are
very UNIX biased. I don't care about it but if you care I can also backport
some of the latest fs.* stuff from neovim 0.10 that helps a lot with
Windows support.
—
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/pull/630#issuecomment-2559594094, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XP7LJDQ75WBXLL7RHT2G75NTAVCNFSM6AAAAABTU6O23KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGU4TIMBZGQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

I'm useless with dev tooling on windows.

We are in the same boat I'm afraid