INCORRECT handling of () parens and ; semicolon

These are two major BUGS that make luamin produced code incorrect. Given that these are very commonly used syntactical elements, this needs to be fixed promptly.

In LUA if you put parens around a function call that returns a list of values, it means extract only the first return from the list. BUT luamin simply removes the parens as superfluous, thereby changing/breaking the code. As it states in the LUA manual:

"Any expression enclosed in parentheses always results in only one value. Thus, (f(x,y,z)) is always a single value, even if f returns several values. (The value of (f(x,y,z)) is the first value returned by f or nil if f does not return any values.)"

luamin removes syntactically significant semicolons such as those described in the LUA manual here:

Lua has empty statements that allow you to separate statements with semicolons, start a block with a semicolon or write two semicolons in sequence:

stat ::= ‘;’

Function calls and assignments can start with an open parenthesis. This possibility leads to an ambiguity in Lua's grammar. Consider the following fragment:
 a = b + c
 (print or io.write)('done')

The grammar could see it in two ways:
 a = b + c(print or io.write)('done')

 a = b + c; (print or io.write)('done')

The current parser always sees such constructions in the first way, interpreting the open parenthesis as the start of the arguments to a call. To avoid this ambiguity, it is a good practice to always precede with a semicolon statements that start with a parenthesis:
 ;(print or io.write)('done')

Are there any plans to fix these bugs? We have two constructions that fail as the parser strips off parentheses for our code, including the following:
(print or io.write)('done') -> print or io.write('done')
hello = (function() return "hello" end)() -> hello = function() return "hello" end()

Are there any plans to fix these bugs? We have two constructions that fail as the parser strips off parentheses for our code, including the following:
(print or io.write)('done') -> print or io.write('done') hello = (function() return "hello" end)() -> hello = function() return "hello" end()

Evidently, the developer has completely abandoned his code. It's a shame. But I have received NO response of any kind since my original post about a year ago.

I've made a PR that fixes the first issue you describe, but I'm struggling to understand your second issue. Are you saying the rewriter should always be assuming the second scenario instead? If the rewriter is given ambiguous syntax, it can't reasonably be expected to figure out what the user intended. I don't think the rewriter can produce such illegal syntax itself either, so I'm not sure what the issue to fix here would be

luamin removes  SYNTACTICALLY SIGNIFICANT UNAMBIGUOUS semicolons ';'
For example if you give it this:
Assuming that d and e are different functions:
a = b
;(c and d or e)(f)
Should do the following: 1. set a equal to b, 2. if c is true then execute d(f), otherwise execute e(f)
BUT LUAMIN REMOVES THE SEMICOLON! And then it becomes
a = b(c and d or e)(f)
Which attempts to execute b as a function with argument (c and d or e) and so on. TOTALLY WRONG...

BUT LUAMIN REMOVES THE SEMICOLON!

Turns out this is a bug with the version of luaparse used by luamin (0.2.1), which is responsible for the ignored semicolon. Unfortunately, upgrading doesn't seem to be an option as the latest version (0.3.1) removes the .inParens property of expressions that luamin currently relies upon for other stuff, making this a hard-to-fix issue

I was infact misreading stuff, and have managed to come up with a fix, which I've put in my current PR. This fixes your given case as well as similar expressions that would suffer the same issue


[FORK] Decide on digital assets

To ensure operations and releases we would require:

[x] github organization and repo
[x] documentation account - readthedocs.org
[x] pypi account with registered package name

Optional

[x] domain name to host documentation under
[x] email account
[ ] anaconda/conda-forge account to release conda packages #33
[x] linkedin account
[x] twitter account

We have all of the above except for conda, which has its own issue. #33


Conversion fails with values '08' or '09' in day or month

The leading 0 is interpreted as the start of an octal number by the expr utility which executes double-bracketed expressions by the Shell Arithmetic Expansion.
As a result, when 08 or 09 appear in an expression, they are misinterpreted as invalid octal numbers by expr:
$ echo $(( 09 + 1 ))
-bash: 09: value too great for base (error token is "09")

or more obscurely in dash:
$ echo $(( 09 + 1 ))
dash: 1: arithmetic expression: expecting EOF: " 09 + 1 "

The expr utility does not suffer of this issue:
$ expr 09 + 1
10

bash supports an explicit base, as a prefix followed with #, in arithmetic expansion, e.g.
$ echo $(( 10#09 ))
9

This is not supported in dash:
$ echo $(( 10#09 ))
dash: 1: arithmetic expression: expecting EOF: " 10#09 "


Add functionality overview to interpreter module docstring.

Intended to be a basic intro to the purpose and structure of the interpreter module. We could perhaps reuse some or all of this in the ReadTheDocs description of the interpreter — thoughts?

Looks good to me. You forgot the copyright header.
Once we're cofortable with having this in public docs the description of the compiler can change from "library that simplifies database querying and exploration" to "a schema indirection layer for arbitrary data sources" or something similar.

I suppose technically the diff coverage is 0% because nothing ever imports that file with no executable code in it. But also, as a vacuous truth, technically all executable code in the module I added is executed in tests, so maybe the diff coverage is 100% instead 🤔


add auto-complete support

https://www.construct.net/en/make-games/manuals/addon-sdk/guide/defining-aces
Adding type for Auto Complete ID

Feature implemented:
If autocompleteId is set to true, a generated ID will be set based on the ACE ID and param ID:

If autocompleteId is set to a string, the string will be added, always prefixed by the plugin ID:

An extra option was added, to output the IDs as MD5 hashes:


Frozen While Getting Links

Hi. This plugin doesn't work for me either, although I haven't noticed any other issues when working with my vault.

Originally posted by @jsmm in https://github.com/nmcarp99/Obsidian-Auto-Definition-Link/issues/1#issuecomment-1969665198

Can you check your console for any errors?

Closed due to no response


DeprecationWarning: Tapable.apply is deprecated. Call apply on the plugin directly instead

(node:58259) DeprecationWarning: Tapable.apply is deprecated. Call apply on the plugin directly instead
    at Walker.file (manifest-revision-webpack-plugin/index.js:149:30)

node:58259) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
    at ManifestRevisionPlugin.apply (manifest-revision-webpack-plugin/index.js:178:14)

Looks like there's a PR
https://github.com/nickjj/manifest-revision-webpack-plugin/pull/48

Your plugin is broken on Webpack 5 because of this warning @nickjj

@braco does #48 fix this?

Believe so, but I switched to @5kyc0d3r fork:
https://github.com/5kyc0d3r/flask-webpack-fork
that uses
https://github.com/danethurber/webpack-manifest-plugin
Might be a good migration recommendation if you want to let these projects go?

Yeah I would switch to a different library. I really should archive this project as I haven't used it in a very long time and I don't like seeing so many people try to use it and then it blows up since it's not compatible with newer version of Webpack.
My personal opinion is that the md5 hashing of files should really be controlled by whatever web framework you use since your web framework's template system needs a manifest file in the end to do the look up.
You need both halves (the manifest file and template helpers), so you might as well do it all with your web framework since having a manifest file get generated with webpack isn't enough on its own.
This is what Rails, Django, Phoenix and now Flask does (well, with Flask I wrote an extension to do it).


{AppConfig} Migrate to Track 2 Mgmt SDK

Description
This PR upgrades the azure-mgmt-appconfiguration library to version 1.0.1, which is the new track 2 management plane SDK.
Changes in Track 2 SDK:

ErrorException has been removed. The SDK now throws HttpResponseError instead.
Most client APIs exposed by the SDK now start with begin_.
id cannot be passed directly to regenerate_key method. It needs to be wrapped in the new model RegenerateKeyParameters.
List/regenerate credentials returns an ApiKey object, which does not need to be converted to JSON object.

Testing Guide
History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

@shenmuxiaosen can you please help review these changes?

AppConfig

@avanigupta I am writing a document of how to migrate to Track 2 SDK. You are welcome to contribute to it.
https://github.com/Azure/azure-cli/pull/16330

Wait for @shenmuxiaosen's comment


[multistage] hintable option framework & dynamic broadcast hint

Details

add hintable option framework

indicates the hint applicable node (aggOptions, joinOptions are added for now)
each hint support arbitrary k-v options (e.g. joinOptions(join_strategy='dynamic_broadcast', colocated_by_join_keys='true')

also added the dynamic_broadcast hint and rel optimizer rule

this helps execute queries similar to (IN_SUBQUERY)

also sanitized agg hint options and tests.

Examples

hint with hint name:

SELECT /*+ skipLeafStageGroupByAggregation */
  a, sum(b)
FROM tbl
GROUP BY a

hint with hint options on the specific node

SELECT /*+ joinOptions(join_strategy='dynamic_broadcast', colocated_by_join_keys='true') */
  a, b
FROM tbl
WHERE b BETWEEN 10 AND 100
  AND c IN (SELECT d FROM tbl2 WHERE e > 10)

Extensibility
with this hint strategy framework we can extend easily.

adding more hintable node, such as hint on WindowNode

we can simply add a windowOptions type to PinotHintOptions class

adding more generic option keyword, such as support partition_by='col1,col2' on aggregate and table node.

we can simply add generic k-v option keys to the PinotHintOptions.aggOptions sub-class to indicate that a group by should be partitioned by "col1,col2" instead of the group set.

adding some completely unknown keyword

the entire options framework is a Map<String, String> basis, so we can directly extract the string value, such as on a plugged-in ruleset from some fork. we can simply extract it via String key to get the String value

Codecov Report

Merging #10772 (55e9528) into master (579082c) will decrease coverage by 50.76%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10772       +/-   ##
=============================================
- Coverage     64.40%   13.65%   -50.76%
+ Complexity     6446      439     -6007
=============================================
  Files          2098     2103        +5
  Lines        113315   113562      +247
  Branches      17204    17262       +58
=============================================
- Hits          72984    15504    -57480
- Misses        35082    96788    +61706
+ Partials       5249     1270     -3979

Flag
Coverage Δ

unittests1
?

unittests2
13.65% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...he/pinot/query/planner/plannode/AggregateNode.java
0.00% <0.00%> (-89.48%)
:arrow_down:

...org/apache/pinot/query/mailbox/MailboxService.java
0.00% <0.00%> (-77.15%)
:arrow_down:

...ot/query/runtime/operator/MailboxSendOperator.java
0.00% <0.00%> (-87.94%)
:arrow_down:

...query/runtime/operator/exchange/BlockExchange.java
0.00% <0.00%> (-90.33%)
:arrow_down:

...y/runtime/operator/exchange/BroadcastExchange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../query/runtime/operator/exchange/HashExchange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...uery/runtime/operator/exchange/RandomExchange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...y/runtime/operator/exchange/SingletonExchange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ot/query/runtime/plan/OpChainExecutionContext.java
0.00% <0.00%> (-96.16%)
:arrow_down:

... and 1444 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

CC

@vvivekiyer and @somandal who visited the hintable framework previously on aggregate and window functions
@ankitsultana for the colocated options.

syntax for hints seems a bit verbose.. can we follow spark or postgres model
https://spark.apache.org/docs/latest/sql-ref-syntax-qry-select-hints.html

syntax for hints seems a bit verbose.. can we follow spark or postgres model
https://spark.apache.org/docs/latest/sql-ref-syntax-qry-select-hints.html

There will always be the option to make top-level hint instead of going through the option k-v route. it will definitely be less verbose
However the current arbitrary key-value options support will make it more flexible to extend in both plan time and runtime optimization code as it doesn't require a fixed set of hints registered

I am also reviewing this today

addressed all comments and we have a basic understanding on the hint option framework.
will merge and will address any follow up comments later. thx


Flattening XML in a DataFrame

I am trying flatten variety of XMLs using DataFrames. I’m using spark-xml package which is automatically inferring my schema and creating a DataFrame.
I do not want to hard code any XPaths in DataFrame as I do not know the tag name before hand and each might be lot more depth. I simply want to flatten any type of XML and then write output data to a hive table.
Example XML and expected output is given below.
Sample XML:
<emplist> <emp>    <manager>    <id>1</id>    <name>foo</name>     <subordinates>       <clerk>         <cid>1</cid>         <cname>foo</cname>       </clerk>       <clerk>         <cid>1</cid>         <cname>foo</cname>       </clerk>     </subordinates>    </manager> </emp> </emplist>
Expected output:
id, name, clerk.cid, clerk.cname
1, foo, 2, cname2
1, foo, 3, cname3

I see. Is this related with https://github.com/databricks/spark-xml/issues/91?

I am closing this for now. It seems a duplicate of it. Please feel free to reopen if you think this is a different issue with this.


Add a common test clients file

The common clients file provides access to kubeclient which can be used by all the other repos

/assign @jessiezcc

/lgtm

/assign @mattmoor
need approval for  vendor updates and updates to GoPkg.*

/lgtm

/approve


test.osmand.net/gpx/get-analysis - 502 error

cloned web, resources
cd web/map && run yarn install && yarn start # and turned to test.osmand.net in setupProxy.js
The map works fine, but with a problem at start screen:
In one of my browsers, I have got: Runtime error, Request failed with status code 502
After analytics, I've got reason: /gpx/get-analysis (on test.osmand.net) fails with 502 code.
I've saved get-analysis request as "node fetch":
How to reproduce:
node test-502.txt
[test-502.txt] (https://github.com/osmandapp/web/files/11653918/test-502.txt)
Please check and fix /gpx/get-analysis on test.osmand.net
PS. Seems, the Map uploads my tracks every time when I loaded Map page. Tracks might be huge, even with my test gpx, it takes ~600kb upload every time I load Map. Is it really needed?

Additional track visibility problem (caused by this bug):

Turned off track visibility (error 502 disappears when tracks are non-visible)

When I try to press "Turn on" switch, error 502 comes again and track keeps non-visible


add support for custom performance entries

What?
This PR adds the support for fragment teams to add custom metrics that looks similar to PerformanceEntry that can be retrieved via tailor in addition to the hooks it supports.
Pipe.addPerfEntry("time-to-meaningful-paint", 2000.00) // done from some fragment on some page

Pipe.getEntries()
// [{
   name: "time-to-meaningful-paint",
   duration: 2000.00,
   entryType: "tailor",
   startTime: // start time relative to navigation start
}]

Why?
Browsers right now does not expose an API for creating custom PerformanceEntry and make them available on PerformanceTimeline.
why not perfomance.measure(User Timing)?

User Timing - mark and measure does not allow a way for pushing custom timing information. If you already have a metric and want to pass that information to PerformanceEntry you cannot do that right now with User Timing API.

why not extend PerformanceEntry?
Even if we hack and extend the PerformanceEntry object, there is no way to retrive the custom entries that are added.
var customEntry = {};
customEntry.prototype = PerformanceEntry;
customEntry.name = "ttfmp";
customEntry.duration = Number(paint); // custom paint timing
customEntry.entryType = "tailor";
customEntry.startTime = performance.now();

// retrive entries
performance.getEntries();
// returns []

Future
There is a existing issue and proposal in w3c web perf group on exposing the API. So once its landed, we can fallback to that or continue to use them for older browsers.
Issue - https://github.com/w3c/charter-webperf/issues/28
Proposal - https://docs.google.com/document/d/1_zm9JB-Ul_fOtAMnF6yBcmvNL3m4-k4ram4pdMIcIug/

:+1:

:+1:

👍


[Semantic API] references() not working for key specifier in a table

Consider the following:
type Foo record {
    readonly int x;
    int y;
};

public function main() {
    table<Foo> key(x) tb = table key(x) [
        {x: 1001, y: 20}
    ];
}

If I look up the references of the field x, I only get the definition and the reference in the mapping constructor. I think this should ideally be returning the references in the key specifiers as well.

The symbol information in the table key specifier is missing.

This issue should be fixed at the compiler FE side. Let's check for possible solutions at compiler level.


Now use epoll so we can wake up readEvents

I like how you separated the poller out into a separate file. But man, this makes it so much more complex.

Should there be inotify_poller_test.go?


install  error

runnng homebrisge on raspian, installing package gives me this error
pi@homebridge:/var/lib/homebridge $ npm install<EMAIL_ADDRESS>npm WARN saveError ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No README data
npm WARN homebridge No license field.

<EMAIL_ADDRESS>updated 1 package and audited 252 packages in 4.398s

9 packages are looking for funding
run npm fund for details
found 25 vulnerabilities (9 low, 16 moderate)
run npm audit fix to fix them, or npm audit for details
pi@homebridge:/var/lib/homebridge $

NPM's complaining that there's no package currently instantiated in the current working directory. I think plugins are supposed to be installed globally with npm install -g instead of npm install.
Try first uninstalling the plugin from the local directory with npm uninstall homebridge-alarm-listener, and then installing globally with npm install -g homebridge-alarm-listener.

here is the log after doing above
pi@homebridge:/var/lib/homebridge $ npm uninstall homebridge-alarm-listener
npm WARN saveError ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/var/lib/homebridge/package.json'
npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No README data
npm WARN homebridge No license field.
removed 1 package and audited 232 packages in 4.738s
9 packages are looking for funding
run npm fund for details
found 19 vulnerabilities (7 low, 12 moderate)
run npm audit fix to fix them, or npm audit for details
pi@homebridge:/var/lib/homebridge $ npm install -g homebridge-alarm-listener
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! syscall access
npm ERR! path /usr/local/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR!  [Error: EACCES: permission denied, access '/usr/local/lib/node_modules'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/usr/local/lib/node_modules'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR!


.Net: ToolCallBehavior support with custom IChatCompletionService implementation

Hi team,
We are implementing IChatCompletionService using a custom proxy and it could not handle ToolCallBehavior EnableFunctions or ToolCallBehavior RequireFunction because the properties are either private or internal, any suggestion or workaround?
Thanks!

Hi @dsp05
can you share some information about your use case?
We have provided ToolCallBehavior to support some OpenAI specific functionality and wanted to allow for extending this ourselves in the even OpenAI support new types of tools.

FYI @stephentoub

We are implementing IChatCompletionService using a custom proxy

Can you elaborate more on this?
The intent was for these types to be specific to the OpenAI connector, and to have more general types/settings eventually at the base PromptExecutionSettings layer that could apply broadly to more connectors (right now only AutoInvokeKernelFunctions is supported at that level).
And as Mark started, details about the configuration have been kept private for now mainly to enable some wiggle room as the underlying Azure.AI.OpenAI SDK matures. Eventually it'd be fine I expect to make more public, but I'd be a tad hesitant to do so now.
It'd be helpful to better understand the use case you have.

Hi team, thanks for the reply!
We use a proxy class built on Azure.AI.OpenAI SDK to call AOAI, which has some extra functionalities e.g. load balancing and throttling. We use it to implement an IChatCompletionService and pass it to a Kernel or KernelBuilder.
My question is when the caller sets the OpenAIPromptExecutionSettings.ToolCallBehavior, for EnableKernelFunctions and AutoInvokeKernelFunctions, the IChatCompletionService implementation can get the functions from the kernel and create the payload and send to the proxy class, but for EnableFunctions and RequireFunction, they can be created using public methods but external implementations of IChatCompletionService can't get the functions and create the payload because the properties and methods are not public.

which has some extra functionalities e.g. load balancing and throttling

Is there a reason you implement this around AOAI rather than as an HttpClientHandler that you give to AOAI?

Thanks for the suggestions! Unfortunately, it has to be like this, and we already have several layers around the AOAI client and corresponding factory classes. If I understand correctly, replacing it with an AzureOpenAIChatCompletionService will require a lot of refactoring and contract changes.
As a short-term plan, I think we can avoid using EnableFunctions and RequireFunction, or maybe reflection if really needed... What would be the future plan for IChatCompletionService and ToolCallBehavior? Will developers still be able to use their own IChatCompletionService implementation and have a way to get the functions from ToolCallBehavior?

What would be the future plan for IChatCompletionService and ToolCallBehavior?

Right now, ToolCallBehavior is specific to the OpenAI connector: it's part of the namespace and assembly for AzureOpenAIChatCompletionService and OpenAIChatCompletionService. The intent was that these could surface everything that OpenAI supports, whereas IChatCompletionService is the lowest-level contract, doesn't necessarily support function calling, or if it does doesn't necessarily support it in the same way that OpenAI does (e.g. the idea of having a single function that the tool is required to invoke).
Every IChatCompletionService implementation conforms to that contract, but also has its own specializations, its own settings that are exposed on settings types related to that specific implementation. It's not expected that the settings types for custom implementation A make sense to custom implementation B.
I can imagine (no promises) in the future that the concrete types that Microsoft.SemanticKernel.Connectors.OpenAI.ToolCallBehavior produces could be made public and with the various settings configured on them.  I can also imagine that more general versions of these are exposed for any connector that supports some variation of function calling, though it's not clear to me at the moment what that would look like, since beyond "here are some functions you might be able to use" (which is already supported by setting a property on the base PromptExecutionSettings), there's likely to be significant variation in what different models/services support.
Your specific case seems to be trying to support everything AzureOpenAIChatCompletionService supports, duplicating all of its implementation, in order to layer in additional functionality.  That's fairly niche, and also something I'd discourage if you can achieve it in other ways.  It'd be better to not have to reimplement all of that logic (which is likely to evolve with additional support over time), and instead just wrap it or plug into its extensiblity, e.g. providing a custom HttpMessageHandler that supports throttling and/or load-balancing.  There's already existing .NET libraries that provide similar support and that can be plugged in via the DI system, e.g. https://www.nuget.org/packages/Microsoft.Extensions.Http.Resilience#readme-body-tab that provides retries, rate limiting (throttling), timeouts, circuit breaking, etc. Using that doesn't require replacing AzureOpenAIChatCompletionService; you just configure the services for the Kernel to use that, and it'll automatically be injected into the HttpClient handlers that AzureOpenAIChatCompletionService uses and passes to OpenAIClient.


Add beta tag if target has a beta URL.

:shipit:

It's okay.  I like the Minecraft Beta tag better - more subtle, and this looks a bit squished up in the corner there...  Don't worry about changing for now, but let's see if we can do this more elegantly in the future.


Vectorizer C5002 reason code 1204

I noticed that compiler emitted the following message during build:
code.cpp(161) : info C5002: Loop not vectorized due to reason: "1204"
I was not able to find any information about this reason code. I have described the issue in detail on stackoverflow.
I'm using VS Community 2019 16.7.7 on Windows 10

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

ID: 7f2ca534-d8f2-9608-9ad5-6d1773195a69
Version Independent ID: e2d87bb9-5f1c-ea08-8ce9-045072d87734
Content: Vectorizer and parallelizer messages
Content Source: docs/error-messages/tool-errors/vectorizer-and-parallelizer-messages.md
Product: visual-cpp
Technology: cpp-diagnostics
GitHub Login: @corob-msft
Microsoft Alias: corob

@maxim-komlik
Thanks for the report. This appears to be a duplicate of issue #2467, which has some additional info. An update should appear with the relevant info by tomorrow sometime.


Struct objects gets destroyed randomly

May be related to GC

I have determined one case where random numbers appear, have fixed it with reduce


refactor: add 'force' svar and factor out cm cond

This more modular setup allows for users to control precisely when they use mtriggers. Mainly for those without srconfigs running Any% or anybody doing TASing.

I like the idea of this PR, but the implementation is... weird? It makes some changes for no good reason. In particular, there's no advantage to special-casing the support for srconfigs; it neither helps srconfigs users nor other people, and I'd prefer any stuff in srconfigs support to be handled actually within srconfigs. Could you change the PR so it uses the following logic? This is flexible but retains back-compat and doesn't unnecessarily integrate with srconfigs.
sar_on_load svar_set __mtriggers_enable 0
sar_on_load cond "(cm | ?force_mtriggers=1) & !?no_mtriggers=1" svar_set __mtriggers_enable 1

Sure, but I feel like no_mtriggers isn't a great solution going forward, just because it's logically convoluted -- 'if there's not no mtriggers enable them'

Also the functionality of force_mtriggers is meant to be independent of anything the configs are doing (your ver. can't force them off)

I mean... It can, just set 'no_mtriggers'. All mine does is splits the functionality - I agree it's a slightly worse method than one svar but back compat is at least sorta important here - no_mtriggers doesn't seem confusing to me at all, it just disables mtriggers. Only issue is that it's just slightly redundant compared to a single svar but no biggie


[Feature] helmfile support

Describe the solution you'd like

https://github.com/helmfile/helmfile
Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases in one shot.
helmfile base helm. He can better manage the helm. Currently, it has been integrated by jenkins and gitlab.

As far as I can see, this project dose same thing that fluxcd can do better. But still interested in how can it integrated with KubeVela.


Stronger typing for cirq.resolve_parameters

Is your feature request related to a use case or problem? Please describe.
Currently the type of cirq.resolve_parameters is:
def resolve_parameters(
        val: Any,
        param_resolver: 'cirq.ParamResolverOrSimilarType') -> Any:

Since the result is Any, we lose type information whenever we resolve parameters. However, for many important cirq objects (gates, operations, moments, circuits) it is typically the case that resolving parameters returns an object of the same type. To avoid losing type information it'd be nice to have a signature like:
def resolve_parameters(
        val: T,
        param_resolver: 'cirq.ParamResolverOrSimilarType') -> T:

Describe the solution you'd like
Not sure the best way to do this. We probably need a separate top-level method for type-preserving parameter resolution, and a separate _special_method_ that classes can implement to indicate that their type is preserved under parameter resolution. It would seem to me desirable to make type-preserving resolution be the default since as I said that is most common for cirq types; the exceptions are low-level things like sympy symbols whose type can obviously change when resolved, but which are not cirq types and typically don't need to be resolved directly. One possibility would be to leave cirq.resolve_parameters as it is and add cirq.resolve as a type-preserving resolution function.
[optional] Describe alternatives/workarounds you've considered
Can use type casts to recover type information after resolution, but this is ugly and error-prone. Can also have more specifically typed methods on particular classes that can be called instead of the generic cirq.resolve_parameters protocol, but this adds boilerplate and highlights the problem with the resolution protocol itself.
What is the urgency from your perspective for this issue? Is it blocking important work?
P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle
I think the actual amount of work needed to implement this will be modest, once we settle on a strategy.

Cirq Cynque discussion: consensus: let's do this, and let's just change the type signature


isAllDigits might be obsolete

The isAllDigits function was used to provide an allDigits validator on String.
In pull request #5, the allDigits validator is rewritten using the newly introduced any validator with and the help of the Char::isDigit predicate. That might imply that the isAllDigit function and the underlying regular expression are obsolete.
Currently it is still be used, albeit in a test of the function itself.
I would propose to remove the function and the underlying regular expression from the code base.

It is not obsolete, because it is also used as a function in

isLuhn
'isMod10`

We will place the definition closer to the usage


⚠ GitHub has degraded performance

In 664dbfa, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 172 ms

Resolved: GitHub performance has improved in 764a10c after 23 minutes.


Dev

Q
A

Bug fix?
no - yes?

New feature?
no - yes?

New sample?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to Dev branch.

Hi @JAmidan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;


convert and preview commands crash on certain Markdown pages

Description
When rendering Swift compiler documentation the diagnostics formatting code crashes on certain Markdown pages.
Checklist

[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
No crashes.
Actual behavior
Swift/StringCharacterView.swift:158: Fatal error: String index is out of bounds
Steps To Reproduce

Clone https://github.com/apple/swift.git
Install a recent development snapshot of Swift, I'm using swift-DEVELOPMENT-SNAPSHOT-2023-07-23-a.
Run DocC from this snapshot this way (assuming swift is the clone from step 1):

docc preview --allow-arbitrary-catalog-directories swift/docs

Swift-DocC Version Information
swift-DEVELOPMENT-SNAPSHOT-2023-07-23-a
Swift Compiler Version Information
Apple Swift version 5.9-dev (LLVM 9b562f55c38e378, Swift b4ee68bd37c4f7d)
Target: arm64-apple-macosx14.0

The code that crashes is in the new diagnostics formatter (#535). cc @arthurcro if you have any ideas 🙂

Thank you for the heads up, I’ll take a look asap! 🙂

@arthurcro this is still reproducible on main with f70b3ea, I'm reopening the issue

@arthurcro this is still reproducible on main with f70b3ea, I'm reopening the issue

Thank you for reopening the issue and apologies for the inconvenience.
The crash is surprising, I did not face any crashes when I tested it after implementing the fix. Did you change anything this time compared to the steps mentioned in the Steps to reproduce ?

I didn't, potentially more docs were published in the docs directory in question. But this crash looked similar if it wasn't the same as the original issue, so I felt that reopening this one would work better than creating a new one.

Hi! 😄 I'm unfortunately unable to reproduce the issue on main with the latest docs from https://github.com/apple/swift.
@franklinsch @d-ronnqvist could you check if you can reporduce if you have some time? 😊

Reproduced again with main DocC, checkout this commit with the docs: https://github.com/apple/swift/commit/1de261bb28b99c6d63a325fef84c854415ab7a32

Great! I can reproduce with this commit, thank you! 🙇🏻

Hi! :wave: After some investigation, I've identified what seems to be the underlying cause of the problem.
Interestingly, the issue doesn't seem to be directly caused by the improved default diagnostic formatter, even though the formatter does highlight it.
While I might not have captured all the details accurately, here's my understanding so far:
When using:
`` my content ``

DocC will see this as a symbol link.
For this specific crash, when using:
  for the target platform and verify diagnostics, like ``swift -frontend -typecheck -verify
%s``

DocC will try to resolve this symbol link as a TopicReference but it will eventually fail.
https://github.com/apple/swift-docc/blob/f70b3ea281773121a468d9c0966ab8a34bba58d2/Sources/SwiftDocC/Semantics/MarkupReferenceResolver.swift#L161
To resolve the symbol link and eventually emit a diagnostic for this resolution error, DocC uses the symbol link SourceRange provided by MarkupData.swift from swift-markdown.
This source range is used as the diagnostic's source range in case of resolution error. It's then used by the default diagnostic formatter to highlight the unresolved reference. If the source range does not match the actual content of the source file, it crashes.
If we look at your crash, we get a SourceRange 253:56-253:97 while if we look at the source file content, we should be getting 253:56-254:5.  It seems we are getting an incorrect source range for some symbol links.
I hope that made sense.
@d-ronnqvist I'm not sure how to proceed to fix this issue. Could you advice possible next steps? 🙇🏻

Thanks for pointing it out. Maybe you can help file up a issue with some minimum reproducible input to Swift-Markdown so that I can help to look at it on the Markdown module side. (QuietMisdreavus should have some better insights on such problem. But it looks like she is busy now and will back September 18)
Also to know that there are several other issues about SourceRange parsing like https://github.com/apple/swift-markdown/issues/71. I have tried to fix it, but the CodeReview process is pending for some unknown reason.

I'm also frequently encountered this locally. This should definitely be a block issue for release/5.10 since it may crash a lot of downstream user.
Maybe we can discuss it in next DocC workgroup. cc @franklinsch @QuietMisdreavus
IMO, We should either fix it before 5.10 release or revert relevant PR until we fix the issue.

I hope that made sense. @d-ronnqvist I'm not sure how to proceed to fix this issue. Could you advice possible next steps? 🙇🏻

For the problem you found, I've open a PR to fix it. https://github.com/apple/swift-markdown/pull/151 cc @arthurcro
And there is another crash cause, I've opened a new issue on swift-docc to track it. #729

Both bugfix PR is merged into main. The cherry-pick to release/5.10 is still in progress.

https://github.com/apple/swift-docc/pull/746
https://github.com/apple/swift-markdown/pull/156

If you are still encountering such crash on the toolchain, feel free to reopen the issue. @MaxDesiatov


Client Wallet support

https://docs.mangopay.com/endpoints/v2/client-wallets#e272_view-a-client-wallet
Does the ruby gem support client wallet yet? Don't see it here: https://github.com/Mangopay/mangopay2-ruby-sdk/tree/master/lib/mangopay
I need to do a GET to retrieve the balance.

Found it https://github.com/pvp-technologies/mangopay2-ruby-sdk/blob/master/lib/mangopay/client.rb#L38-L40


added watch backoff when waiting for events

Initial back off timer is 5 seconds, back off factor is 1.5 - up to 1 minute delay.
Each event resets the back off timer to 5 seconds.

@sbabitz What else do you think you are missing in the exponential backoff scheme here?


Line position after ctrl+click in problemMatcher output is not correct if VS connected remotely.

After ctrl+click file opened correctly, but position always is first line.
If open the same project with VSCode 1.34 all ok.

VSCode Version: 1.35.0-insider
OS Version: Windows 10

Steps to Reproduce:

Make build task for makefile and c/cpp file

Make error in c/cpp file code

Run build task

Ctrl-click on problem line.

VSCode open proper file, but line position is always 1
"tasks": [
{
"label": "make",
"type": "shell",
"command": "make",
"group": {
"kind": "build",
"isDefault": true
},
"problemMatcher": {
"owner": "cpp",
"fileLocation": [
"absolute"
],
"pattern": {
"regexp": "^(.):(\d+):(\d+):\s+(warning|error):\s+(.)$",
"file": 1,
"line": 2,
"column": 3,
"severity": 4,
"message": 5
}
}
}
]

test.cpp
#include
int main()
{
std::cou t << "Hello world\n";
return 0;
}
makefile
all: test
CXX=clang++
CXXFLAGS=-g -O0 -std=c++14
-fno-exceptions
test: ${PWD}/test.cpp makefile
$(CXX) $(CXXFLAGS) $(LDFLAGS) ${PWD}/test.cpp -o $@
clean:
$(RM) -rf *.o test

I tested this with the hello world sample without tasks. In the terminal I just ran echo "src/extension.ts:15" while connected to a remote and not while connected to a remote. Only while not connected does it go to the correct line when ctrl+click.

/duplicate https://github.com/microsoft/vscode-remote-release/issues/136


MES Factory gradient support

Summary
Updating the MES Factory methods to support the new gradient framework.
This PR addresses Issue #1398
Details and comments

The existing parameters to the factories, such as expectation, all have setter/getters. I think for consistency gradient should have them too.

good catch, thanks

In looking at the setters/getters now that you have done these I notice the original ones for initial_point, expectation, optimizer that default to None in factory constructor do not allow show that None is a valid value to set these too, via setter, or one would expect to have None back from getter, ie. are Optional like you just did for gradient. I think it should be valid to set to None so you go can back to default. Either way the getter needs to show Optional. Maybe this should/could be done in a separate PR but since its just typehints maybe it can be added/fixed here?


DNS issues when connecting to redis

We are having some trouble with oauthd and redis. If the redis server dns changes (pods moving around in Kubernetes for example) then looks like outhd is unable to reconnect to the new IP. Are dns lookups to redis cached by any chance?

Hi, we changed node-redis for ioredis in 1.0.0-rc.1. Please tell me if it fixes this issue on your side

Great news, thanks. I'll let you know if the issue still exists with the upgrade.


Return values from Vector4 may have been disturbed

In #53 @veillette said:
There is a subtle difference between dividedScalar and divideScalar.
dividedScalar returns a new Vector4 whereas divideScalar mutates the vector.
Before the fix, 6d72717, it used to return a new Vector4
And I think I am the one who did the faulty commit.

This was addressed in https://github.com/phetsims/dot/commit/d2bc7ad84d37b5adcc50efd7879eecfaa616a205

In addition, I checked that the normalized methods in Vector2, Vector3 were correct.

I found that Vector4 is not used in any of our sims.:(.
In any case, I'm glad we caught this bug. Closing


Fix for Spark < 1.6

This one line PR fixes a crash when doing spatial partitioning in Spark versions < 1.6.
The fix is to use JavaRDD.rdd().partitions().length rather than JavaRDD.getNumPartitions() for Spark <1.6 compatibility.  This safely gets the number of partitions for this RDD for all versions of Spark 1.X.  (1.0.0 through 1.6.X).
Note JavaRDDLike has a partitions() method but it is not available in Spark 1.0.0 so I used this approach.
Request: when releasing a new version for 1.X could you please tag the branch with a tag?  It seems only the mainline releases get tags on master.  Thanks...

Hi @invadergir ,
Thanks for finding this! The 1.X test was tested on Spark 1.6 so that I didn't find the bug.
This PR is accepted now.


MAINT: use TFP parameter names

~WIP; do not merge.~ Ready for review.
Looks like the general (if begrudging, depending on who you talk to) consensus is to adhere to TFP parameter naming.

Also, as @twiecki points out, I haven't ported the example notebooks (like radon) yet. I'll add to this PR in the next few days. Sorry for the delay!

@twiecki just reran the radon and eight schools notebooks. The eight schools notebooks actually raises some errors when you try to visualize the trace, so I didn't run all the cells, but everything up to (and including) the sampling works fine.

Thanks @eigenfoo!


[Network] az network application-gateway: Support OCSP revocation check on client certificate

Related command

az network application-gateway create
az network application-gateway update
Description

Resolves: https://github.com/Azure/azure-cli/issues/24011
Need to complete az network application-gateway ssl-profile in the future.
Testing Guide

az network application-gateway update -n ethan-ag --ssl-profiles [0].client-auth-configuration.verify-client-revocation=OCSP

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network


Missing (polymorphic) refinements for vec set/get

The following should pass but do not.
#![feature(allocator_api)]
#![feature(associated_type_bounds)]

use std::ops::Index;

#[path = "../lib/vec.rs"]
mod vec;

#[flux::sig(fn(xs: &Vec<i32{v: v > 55}>[100]) -> i32{v:v > 55})]
fn test_get(xs: &Vec<i32>) -> i32 {
    xs[0]
}

#[flux::sig(fn(xs: &mut Vec<i32{v: v > 55}>[100]) )]
fn test_set(xs: &mut Vec<i32>)  {
    xs[0] = 66
}

Did some digging. The reason for this is that in the signature of index (and index_mut) the type variable T (of items) appears in a bound so we don't generate refinements when instantiating it. More specifically, the signature of index is
fn index<T, I, A>(z: &Vec<T, A>, idx: I) -> <I as SliceIndex<T>> ::Output
where
    I: SliceIndex<[T]>,
    A: Allocator

Since T appears under I: SliceIndex<[T]>  we don't generate refinements for the instantiation.
Unclear if there's an easy workaround. Contrary to other traits where we can make an exception based on the trait definition, in this case, the "parametricity" of T comes from the implementation of SliceIndex<[T]> for usize.


error POST API calls entry/mark [Credentials are required]

Describe the bug
when send POST request to mark entry as read, it throws: Credentials are required to access this resource.
To Reproduce
URL: http://<IP_ADDRESS>:8082/rest/entry/mark?apiKey=bdee4e0f1ef6a75da23559b055e1847e51adbf22

BODY(json): {"id":"3","read":true}

why?

The API key can currently only be used for read-only operations. For other operations you need to use Basic Authentication.


Helper function create_dataset will not work for explorer steps

I think create_dataset will not work for explorer steps, given that you have to specify ds_explorer.add(tb_garden, formats=["csv"]). I suppose one solution would be to include formats as an argument of create_dataset.
Additionally (not totally sure if it's a good idea), create_dataset could add the formats=["csv"] by default if the step is an explorer step.

Passing formats works well, doing it implicitly could be tricky. Since this is a one-liner, I'm gonna wait until someone does it as part of their explorer work.


Supply numeric index

This issue is to supply a index (a binary tree with leaf nodes which have a value chain  ) to numeric data type column which may be numeric dimension or metric ones.  The index can be configurable to a numeric column. And this is also a start point to support date time type. The PRs will be split into several small parts . Please wait.

Is this about creating indexes for numerical columns for faster filtering?
I couldn't really understand the design/plan from the description given. It would be nice if you could elaborate some more or maybe your PR would have that.


Fix: Lots of properties are not working in fluent-design-system-provider

Pull Request
📖 Description
The units for these properties were incorrect and could not be applied even when values were set, due to the absence of measurement units: px. Therefore, it was decided to change their data type to string, allowing users to determine both the value and unit type as needed, while also maintaining consistency with the official FluentUI property types (ref: https://github.com/microsoft/fluentui/blob/57de08c18915440cdc54a1242bbdf948e2b0f562/packages/web-components/src/design-system-provider/index.ts#L426).
For example, if the TypeRampMinus1FontSize property was assigned a value of float 12, but did not include a unit such as "px" or "em", the value would not be applied correctly in the user interface. By changing the data type to string, users can now include the appropriate unit of measurement along with the value, providing greater flexibility in how the properties can be used.

🎫 Issues

👩💻 Reviewer Notes

📑 Test Plan

✅ Checklist
General

[ ] I have added tests for my changes.
[ ] I have tested my changes.
[ ] I have updated the project documentation to reflect my changes.
[x] I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

[ ] I have added a new component
[x] I have modified an existing component

⏭ Next Steps

@microsoft-github-policy-service agree


Edge's screen reader skips alerts

By default, Microsoft Edge's screen reader "Read Aloud" seems to skip directly to the main content of the page and does not provide any settings to prevent this.
From this comment on the main a11y improvements branch:

Should these alerts be read first before the site's main content? I think that would be useful in scenarios where we experience technical issues but have important announcements/workarounds through the alerts. Would it be possible to do this? Would there be issues or disadvantages to having the alerts always be selected/read first?

It's definitely important to read alerts in all contexts. We can adjust the structure of the base template to have the alerts inside of the main tag, wrap the rest of the body inside a tag with an id like content, and change the target of the "skip to main content" button to skip to that new body instead. Then we can test whether Edge snaps to the outer main tag, or the inner content.


Add missing material component to Water Walk spell

I'm closing this because it appears that upstream is active again.

It's active because I'm one of the maintainers now. 😄


Are BERT Squad models supported

I am not sure how to pass the inputs to the BERT Squad  model session in onnx web runtime.
these are the inputs:
unique_ids_raw_output___9:0
name: unique_ids_raw_output___9:0
type: int64[unk__475]
segment_ids:0
name: segment_ids:0
type: int64[unk__476,256]
input_mask:0
name: input_mask:0
type: int64[unk__477,256]
input_ids:0
name: input_ids:0
type: int64[unk__478,256]
An example would be helpful
Thanks!

we don't have an example of BERT squad model, but since there are some common steps for inferencing ONNX models, I can share you some general idea. Here are the general steps:

verify inputs/outputs names and types of the exported ONNX model. you can use Netron to do this.
in your JS code, create or get typed array for each inputs. specifically, in your case, you need to create 5 BigInt64Arrays. make sure the length of the array matches your input tensor shpae. Fill your data into the typed array.
create tensors for each inputs. ( see how to create tensors )
create a JS object as the feed. keys are the input names and values should be the corresponding tensors.
feed the input to inferenceSession.run and you get the output.
use your output name as a key to access output tensor, and use it.

for examples of using ORT JS API , please refer to https://github.com/microsoft/onnxruntime-inference-examples/tree/main/js


Greater control/override of utils/dates.js

Do you want to request a feature or report a bug?

Feature

What's the current behavior?

Utilities currently override props passed to BigCalendar misrepresenting expected outcome.

What's the expected behavior?

If I pass the getNow() prop a function that returns a date for today in a desired timezone (eg  getNow={() => moment('2018-08-22 15:30:00').toDate()})), it will render the time indicator on the returned date.

Details
Currently, in lieu of complete time zone support, there are a number of workarounds to fix certain, but not all, problems. My current issue lies with the getNow() prop that can be used to place the time indicator. However, the time indicator's position is determined by the below function in TimeGrid.js, which checks against the today() method in utils/dates.js. This uses new Date() to detemine what 'today' is, which will default to use the time zone of the machine currently accessing the page.
Because of this, I am unable to accurately place the time indicator as desired, even if I set the getNow() prop to return the desired date. For example, if I set getNow() to return a JS Date for MST and am accessing from a machine in Australia, the today() method will check against a new Date() in relation to Australia, not MST, placing the time indicator a day ahead. The expected behavior of the getNow() prop would be to force set or adjust how the current date/time is rendered on the calendar. Unfortunatley, this is overriden by the today() method.
If anyone has any work around for this or an idea of how to manipulate the dates utilities, that would be amazing. Thanks in advance!
utils/dates.js
https://github.com/intljusticemission/react-big-calendar/blob/d1e90b148a0be2b71f2c1887b196cf5df088535c/src/utils/dates.js#L144-L146
src/TimeGrid.js
https://github.com/intljusticemission/react-big-calendar/blob/d1e90b148a0be2b71f2c1887b196cf5df088535c/src/TimeGrid.js#L325-L355

Also check #118


Fixed #334.

Repaced namespace mqtt with MQTT_NS.
User can define your own namespace name.

Codecov Report

Merging #360 into master will not change coverage.
The diff coverage is 64.47%.

@@           Coverage Diff           @@
##           master     #360   +/-   ##
=======================================
  Coverage   86.24%   86.24%
=======================================
  Files          37       37
  Lines        6207     6207
=======================================
  Hits         5353     5353
  Misses        854      854


called with unexpected argument 'orgPackages' on the latest nixpkgs

while using home-manager module
error: anonymous function at /nix/store/xpifs2w4s1cwkvc68sp89rrg475zwq81-source/pkgs/top-level/emacs-packages.nix:58:53 called with unexpected argument 'orgPackages'

       at /nix/store/xpifs2w4s1cwkvc68sp89rrg475zwq81-source/lib/customisation.nix:69:16:

           68|     let
           69|       result = f origArgs;
             |                ^
           70|
(use '--show-trace' to show detailed location information)

meanwhile, nixpkgs:

pkgs.emacsPackages.orgPackages is removed
because org elpa is deprecated. The packages in the top level
of pkgs.emacsPackages, such as org and
org-contrib, refer to the ones in
pkgs.emacsPackages.elpaPackages and
pkgs.emacsPackages.nongnuPackages where the
new versions will release.

See also https://github.com/vlaci/nix-doom-emacs/issues/401

Can I have your config to play with it myself? Or a reproducer?

Maybe the bug is that there is no bug.. At least in this repo.
    doom-emacs-nix = {
      url = "github:vlaci/nix-doom-emacs";

Ha, typo (I copied that from the other issue, not my config). I did experience this same issue with doom-emacs.url = "github:nix-community/nix-doom-emacs";.

Closing this since the issue seems to be fixed. Reply here if you want me to reopen it.


Update Vagrantfile

Why you remove config.vm.box_url  config from Vagrant file?

Same as https://github.com/majidgolshadi/farmer-server/pull/2.

Thank you


Write a Java program to check anagram string

Description
Write a Java program to check anagram string
Two strings are said to be anagrams if they make a meaningful word by rearranging or shuffling the letters of the string. In other words, we can say that two strings are anagrams if they contain the same characters but in different order.
Input  : pan, nap
Output : Anagram Strings

Contributed by - @sahdev77

How to contribute

Save the solution in WriteAProgramToCheckAnagramString.java file
Add WriteAProgramToCheckAnagramString.java file in program/write-a-program-to-check-anagram-string folder

!assign


Switching to symlinks for local system support.

Fixes the problem mentioned in #44 and is generally safer than using absolute paths.

ugh. sorry hold on.


merge from template-node-app

.github/workflows/ci.yml

chore(deps): add 18.0.0 (jobs.test.strategy.matrix.node-version)

:tada: This PR is included in version 5.0.105 :tada:
The release is available on:

npm package (@latest dist-tag)
v5.0.105
GitHub release

Your semantic-release bot :package::rocket:


Dota 2 Profile addition - Last Hits

What are you experiencing an issue with?

[ ] Aurora
[x] Aurora supported game, (Dota 2)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[x] Enhancement suggestion
[ ] Device issue
[ ] Other, (Fill in another type of issue here)

Suggested behavior:
Suggestion for last hits to flash keyboard gold

Bump.


Add script to use RGB LED as Nginx request monitor

It seems switching the GPIO pin on which the ACT LED operates is as easy as setting the following inside /etc/config.txt:
# Use a different GPIO pin for ACT LED.
dtparam=act_led_gpio=XX

...where XX is the pin to be used.
Is there a way to set this dynamically? Or failing that, some way to control the LED using a script that monitors CPU usage or something (so we can emulate the ACT status)?

Also, to switch the ACT LED to work with different triggers (the default is mmc0, or 'MultiMedia Card 0', a holdover from the old pre-SD days), you can set a new trigger like so:
echo cpu0 | sudo tee /sys/class/leds/led0/trigger

To see all available triggers, run sudo cat /sys/class/leds/led0/trigger, which should give something like:
$ sudo cat trigger
none mmc0 timer oneshot heartbeat backlight gpio [cpu0] cpu1 cpu2 cpu3 default-on input

Watching cpu0 is much more interesting than mmc0 for an application like the Dramble, which is heavy on CPU usage, at least when distributing hundreds of HTTP requests on the servers with no disk access required after the first request is complete.

I changed the title/direction of this issue. Since this is a web request cluster, I'm going to tie the LEDs to Nginx requests, as directed to /var/log/nginx/access.log. Working on that now.
Yes, this slows down the cluster a tad, since it's writing to disk, and disk is sloooow... but the visualization is just so darn awesome!
To kill the running script: ansible all -a "pkill python" -s.


fix typo in ci

fix typo like https://github.com/mackerelio/mackerel-agent-plugins/pull/871/files
upgrade golangci-lint-action's version to fix lint

Thanks!


osCommerce <IP_ADDRESS> allows to execute several file types.

Brief of this vulnerability
osCommerce use .htaccess file for preventing to execute php and html files.
But it is not complete set to preventing all of malicious files.
As the result, Adversary can upload several types of malicious file.
This vulnerability needs the admin credentials, but this vulnerability can be used  to compromise web server that osCommerce installed.
Test Environment

Apache/2.4.18 (Debian)
PHP 5.6.38-2+ubuntu16.04.1+deb.sury.org+1 (cli)

Tested version
<IP_ADDRESS> (Downloaded from Official Site)
Payload & Reason of vulnerability

upload point

Page : Admin page > Catalog > Categories / Products > New Products
Upload malicious files via product images elements.
Found Harmful Files is listed below.

PHP Code Execution

Description of vulnerability
.htaccess file located in http://[ host ip ] /oscommerce2/catalog/images/ directory.
It prevents to execution of several dangerous extensions.
But its regular expression do not prevent pht extensions.
As a result, php script with pht extension can be uploaded and executed.

ps. If osCommerce runs on PHP 7.1+ environment, phar extension also can be executed in the server.
This vulnerability reserved to CVE-2018-18572.

Handle the arbitrary file to execute as PHP script

Description of vulnerability
Upload File filter can not prevent to upload new .htaccess file.
So, adversary can change the .htaccess file.
If .htaccess file changed, all of the PHP-supported file can be executed.
Even file that has arbitrary extension and PHP script can be executed.

This vulnerability reserved to  CVE-2018-18573.

Execute HTML using SVG file format

Description of vulnerability
.htaccess file in http://[ host ip ] /oscommerce2/catalog/images/ directory banned html extension, but there are several extensions that HTML can be executed.
One of the extension string is svg.
If adversary assemble SVG file and HTML file to SVG file, that assembed SVG file can be execute HTML in client browser.

Execute HTML using EML file format ( IE only )

Description of vulnerability
.htaccess file in http://[ host ip ] /oscommerce2/catalog/images/ directory banned html extension, but there are several extensions that HTML can be executed.
eml extention is not executed in other browsers, but only Internet Explorer render HTML elements in eml file.

Execute HTML using Strange file extension or No extension

Description of vulnerability
.htaccess file in http://[ host ip ] /oscommerce2/catalog/images/ directory banned html extension, but there are several extensions that HTML can be executed.
The file that has no extension or strange extension can be rendered in web browsers.

Vulnerability 1 and 2 are about PHP Code execution via arbitrary file upload, and others are about HTML Execution (related with XSS).
These vulnerabilities needs administrator credentials, but I  still think it is vulnerable.
I did not upload test payloads due to abusing problems.
If you needs to fix these vulnerability, please announce me your mail.
Thank you.

I also got the CVE for 3,4,5 vulnerability - CVE-2018-18966 ( eml ), CVE-2018-18964 ( svg ), CVE-2018-18965 (strange file extension / no extension).

Hi @Hexife !
Is this issue was already fixed in further versions ?
Thanks :)

Hello!
I tested it again in 2.4.2 version, and confirmed that the vulnerabilities are not patched yet.


DBZ-598 Metrics expose the list of captured tables

https://issues.jboss.org/browse/DBZ-598

LGTM, @jpechane. I suppose you tested it manually using some JMX client?

Cool thing. Going forward I hope we can unify these JMX options across connectors. Should look into that once the Oracle PR is merged. Thanks, @jpechane!


Hexagonal_Lattice_Graph()

Adds the function hexagonal_lattice_graph(m::Int64, n::Int64; periodic=false) which creates a graph corresponding to the hexagonal tiling of a plane.
See the networkx function: https://networkx.org/documentation/stable/reference/generated/networkx.generators.lattice.hexagonal_lattice_graph.html for the Python version. This new function is identical to that.

Great, thanks! Could you add a short test? Something like constructing a small graph and checking it has some of the correct edges, for example.

Sure! Just added a test. Can then expand on it as I add in new Named Graph Generators (likely to add ones we might want to simulate some Physics on - Triangular, Kagome, Unit Disk etc)

Codecov Report

Merging #35 (eb3e285) into main (556a87f) will increase coverage by 0.48%.
The diff coverage is 96.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
+ Coverage   79.65%   80.14%   +0.48%
==========================================
  Files          19       20       +1
  Lines         821      846      +25
==========================================
+ Hits          654      678      +24
- Misses        167      168       +1

Impacted Files
Coverage Δ

src/NamedGraphs.jl
100.00% <ø> (ø)

src/Graphs/generators/namedgraphs.jl
96.00% <96.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Great! This will be really useful to have, and it's nice to see how easy it is to define different lattices.
In ITensors.jl we have similar constructors which create so-called "Lattices": https://github.com/ITensor/ITensors.jl/blob/main/src/physics/lattices.jl (which are basically very simple graph types with some metadata and integer vertex labels, if we try to map it to our more modern graph parlance). I think this is a nicer design and should supersede those types (even for DMRG), since it is based on a fully fleshed out graph type and supports tuple vertices which are easier to work with for 2D lattices.@emstoudenmire probably this is of interest to you.

Yes, very nice to have.
The main thing needed to supersede the "lattice functions" in ITensors.jl would be that the vertex numbering of these new graph structures would map onto a good MPS path for DMRG calculations. Maybe that's a pretty natural thing to insist on, unless there's a need for another kind of ordering of the vertices?

@emstoudenmire that raises an interesting point because I think ideally this would ideally be dealt with by some sort of function map_to_path(g::AbstractGraph; kwargs) which takes an arbitrary graph and determines an optimal ordering of the vertices (probably just by analysing the adjacency matrix of g) for the MPS based on some kwargs criteria. This is discussed a bit in issue https://github.com/mtfishman/ITensorNetworks.jl/issues/19.
I think we could employ several simple options to start with: such as bandwidth minimisation (with Cuthill Mckee or some more sophisticated cost-function) and minimising the average path length (along the MPS) between neighbours of g.

I agree with the above points. Just for completeness:
In order for this to replace the "Lattice" types in ITensors.jl, as Miles pointed out you would still need to define a linear ordering of the vertices which would define the MPS site ordering. But I think that is an advantage of this design, since it decouples the lattice from the MPS ordering, and therefore the same lattice definitions can be used in a variety of algorithms and contexts (such as DMRG, TTN, PEPS, etc.). It also makes it easier to try out more exotic MPS orderings such as Hilbert curves (like in https://arxiv.org/abs/2105.02239).
As Miles said, we would want to define some simple default orderings for basic lattices (like the snake pattern for square and square-like lattices), and then we can have automated graph-based functions to determine orderings like Joey pointed out.
Interestingly, I think many basic orderings we use in DMRG can be "derived" by calling general graph functions, for example a depth-first search of a grid graph gives a snake pattern:
using GeometryBasics
using NamedGraphs
using ITensorNetworks
using ITensorUnicodePlots

dims = (4, 6)
g = named_grid(dims)
T = ITensorNetwork(g; link_space=2)
layout(g) = [Point(Tuple(CartesianIndices(dims)[v])) for v in  vertices(g)]
@visualize T layout=layout edge_labels=fill("", ne(T))
t = dfs_tree(T, (1, 1))
@visualize t layout=layout edge_labels=fill("", ne(t))

which outputs:

    ⠀⠀T(1, 6)⣀⣀⣀⣀⣀⣀⣀T(2, 6)⣀⣀⣀⣀⣀⣀T(3, 6)⣀⣀⣀⣀⣀⣀⣀T(4, 6)
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀T(1, 5)⠒⠒⠒⠒⠒⠒⠒T(2, 5)⠒⠒⠒⠒⠒⠒T(3, 5)⠒⠒⠒⠒⠒⠒⠒T(4, 5)
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀T(1, 4)⣀⣀⣀⣀⣀⣀⣀T(2, 4)⣀⣀⣀⣀⣀⣀T(3, 4)⣀⣀⣀⣀⣀⣀⣀T(4, 4)
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀T(1, 3)⠒⠒⠒⠒⠒⠒⠒T(2, 3)⠒⠒⠒⠒⠒⠒T(3, 3)⠒⠒⠒⠒⠒⠒⠒T(4, 3)
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀T(1, 2)⣀⣀⣀⣀⣀⣀⣀T(2, 2)⣀⣀⣀⣀⣀⣀T(3, 2)⣀⣀⣀⣀⣀⣀⣀T(4, 2)
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀T(1, 1)⠒⠒⠒⠒⠒⠒⠒T(2, 1)⠒⠒⠒⠒⠒⠒T(3, 1)⠒⠒⠒⠒⠒⠒⠒T(4, 1)

    ⠀⠀t(1, 6)⣀⣀⣀⣀⣀⣀⣀t(2, 6)⣀⣀⣀⣀⣀⣀t(3, 6)⣀⣀⣀⣀⣀⣀⣀t(4, 6)
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀t(1, 5)⠒⠒⠒⠒⠒⠒⠒t(2, 5)⠒⠒⠒⠒⠒⠒t(3, 5)⠒⠒⠒⠒⠒⠒⠒t(4, 5)
    ⠀⠀⠀⠀⠀⡇
    ⠀⠀t(1, 4)⣀⣀⣀⣀⣀⣀⣀t(2, 4)⣀⣀⣀⣀⣀⣀t(3, 4)⣀⣀⣀⣀⣀⣀⣀t(4, 4)
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀t(1, 3)⠒⠒⠒⠒⠒⠒⠒t(2, 3)⠒⠒⠒⠒⠒⠒t(3, 3)⠒⠒⠒⠒⠒⠒⠒t(4, 3)
    ⠀⠀⠀⠀⠀⡇
    ⠀⠀t(1, 2)⣀⣀⣀⣀⣀⣀⣀t(2, 2)⣀⣀⣀⣀⣀⣀t(3, 2)⣀⣀⣀⣀⣀⣀⣀t(4, 2)
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸
    ⠀⠀t(1, 1)⠒⠒⠒⠒⠒⠒⠒t(2, 1)⠒⠒⠒⠒⠒⠒t(3, 1)⠒⠒⠒⠒⠒⠒⠒t(4, 1)

So there may be simple heuristic algorithms like that we can use that automatically determine standard linear orderings for basic lattices, which then may generalize reasonably well to other lattices.


RBCD attack without a SPN but using a computer account instead

I can successfully execute an RBCD attack without involving an existing SPN and instead using a computer account I added just before this using the tool at https://github.com/tothi/rbcd-attack. I tried the same attack using your command "setRbcd" but at the stage when the silver ticket is requested Impacket fails. I didn't actually expect your tool to work since it seems it requires an SPN which I did not input. Still, I wanted to try this before contacting you. I guess this is more of a feature request than a bug report. Can your tool support this attack without needing an SPN? This would lessen the number of requirements needed for this attack to work since anyone can add computers to a domain.

Very good! Now this works!


Consuming material2

Hi, knowing this package is in early stages, can you please provide steps on how we can consume material2 in ng2? maybe a hello world sample app?

Would be nice, Can't wait for alpha 0

I've opened an issue for this like an hour ago. I guess these could me merged.

There's a demo app, have a look at some running instructions here -> https://github.com/angular/material2/blob/master/DEV_ENVIRONMENT.md

Everything is fine until I run ng build, I receive the following exception:
...\LearnAngular\upstream> ng serve
Cannot find module 'ts-node/register'
Error: Cannot find module 'ts-node/register'
    at Function.Module._resolveFilename (module.js:326:15)
    at Function.Module._load (module.js:277:25)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (...\LearnAngular\upstream\angular-cli-build.js:5:1)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)

Which version of node are you on?
I think I had that in 5.1 but it disappeared in 5.6
Might be the same issue
On Tuesday, 23 February 2016, BinaryLeopard<EMAIL_ADDRESS>wrote:

Everything is fine until I run ng build, I receive the following
exception:
...\LearnAngular\upstream> ng serve
Cannot find module 'ts-node/register'
Error: Cannot find module 'ts-node/register'
at Function.Module._resolveFilename (module.js:326:15)
at Function.Module._load (module.js:277:25)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
at Object. (...\LearnAngular\upstream\angular-cli-build.js:5:1)
at Module._compile (module.js:398:26)
at Object.Module._extensions..js (module.js:405:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Module.require (module.js:354:17)
at require (internal/module.js:12:17)
—
Reply to this email directly or view it on GitHub
https://github.com/angular/material2/issues/92#issuecomment-187451889.

--

Gregory Bataille

I'm using v5.3.0

Got the build working; not sure what fixed it, apparently the npm install did run correctly the first time.

We'll publish to npm once the alpha.0 is ready. The announcement will probably be on Twitter, so stay tuned!


Propagate errors in tls_config instead of unwrap/panic

Motivation
We ran into tls_connector failing and causing our app to panic and shutdown as it seems there wasn't any way to avoid panicking in tls_config.

Solution

So after talking to @LucioFranco briefly tls_config now returns a Result instead and propagates errors to the caller, where they have to be handled.
This is a bit of an intrusive change to the API here. could alternatively introduce an additional tls_config function that does the error handling and keep the existing unwrapping one, to allow it to become an additive opt-in minor semver change instead?

This seems :+1: to me @jen20 thoughts?

@repi looks like a CI failure https://github.com/hyperium/tonic/pull/385/checks?check_run_id=831660623#step:7:139

Sorry, I didn't see this until now - this looks great to me.

Note that Cargo's modified SemVer logic treats 0.2.2 as a compatible update from 0.2.1 and thus this release of tonic causes a break.  Trivial to fix but perhaps yanking and releasing as 0.3.0 would be better?

@fujiapple852 you're right.....sigh will do that today.

Getting a 0.3.0 release out right now. @fujiapple852 thanks for pointing this out!


[FormControl] Issue 13246 revert

Work Completed:

Reverts changes made for Issue-13246 by removing the zIndex: 0 added to the root style of the FormControl component.

[x] I have followed (at least) the PR section of the contributing guide.

Thank you. Sometime, doing nothing is better. I'm glad we tried.

Haha, I hear that.  Thanks for letting me play!


Create an article explainin how to contribute to the project

In order to contribute anything to the project (code, assets, readme files), developer needs to clone the repository on her computer. Write Wiki article explaining how to do it

link for article page
https://github.com/Quit975/DuckyGame/wiki/Contributing-to-Ducky-Game-project


Kinesis Form Split Touchpad Keyboard: Function Key Behavior and External Monitor Brightness Control Issues on MacBook Pro

I'm experiencing two issues with my Kinesis Form Split Touchpad keyboard on my MacBook Pro:

Function Key Behavior:

The keyboard doesn't respect macOS's function key behavior settings.
Expected behavior: Pressing F9 and F10 keys should adjust brightness without using the Fn modifier key, as per macOS settings.
Actual behavior: Fn modifier key is required to use F9 and F10 for brightness adjustment.
macOS setting "Use F1, F2, etc. keys as standard function keys" is turned OFF, which should allow direct brightness control.

Brightness Control:

The brightness adjustment keys only affect my MacBook Pro's screen brightness.
They do not adjust the brightness of my external monitor, regardless of which display is currently active.
Expected behavior: Brightness controls should adjust the active display, including the external monitor.

System Information:

Keyboard: Kinesis Form Split Touchpad
Computer: MacBook Pro 14-inch (November 2023 model)
macOS Version: Sonoma 14.6.1 (23G93)
Function Key Setting: "Use F1, F2, etc. keys as standard function keys" is OFF (see attached screenshot)

Steps to Reproduce:

Connect Kinesis Form Split Touchpad keyboard to MacBook Pro
Ensure "Use F1, F2, etc. keys as standard function keys" is OFF in System Settings
Press F9 or F10 key (without Fn modifier) - brightness does not change
Press Fn + F9 or Fn + F10 - brightness changes on laptop screen only, not on external monitor

Expected Behavior:

F9 and F10 keys should adjust brightness without needing the Fn modifier
Brightness controls should affect the active display, including external monitors

Actual Behavior:

Fn modifier is required to use F9/F10 for brightness adjustment
Brightness adjustment only affects the laptop screen, not the external monitor

Any assistance in resolving these issues would be greatly appreciated.

Hi, this repository is only for the Advantage 360 Pro only, not the Form. Furthermore the setting you mention is most likely exclusively for Apple branded keyboards and thus the form will not respect it. The Form's Fn key is not equivalent to the apple Fn key

Hi @mkwng


Provision for diversity_penalty in vLLM generation?

Is there a way to reproduce results to huggingface's generation with the parameter diversity_penalty present here.
diversity_penalty helps to generate diversity in the output when using beam_search. The current implementation of vLLM doesn't allow for this and returns similar outputs across all of its beams. Is there a method to replicate something similar with vLLM?

This is achieved using repetition_penalty in the SamplingParams


Use XmlTextReader everywhere

This API wasn't in .NET Core when we originally ported but is now available in
all of our .NET Core targets. Using it everywhere improves programmatic editing
of MSBuild files.
Closes #1401.

@dotnet-bot test Windows_NT Build for CoreCLR please
Not sure why it failed. Seems like Tasks unit tests failed but I didn't see a failure in the log. https://ci2.dot.net/job/Microsoft_msbuild/job/master/job/innerloop_Windows_NT_CoreCLR_prtest/658/

@dotnet-bot test Windows_NT Build for CoreCLR please


Add telemetry event for FZ editor

Summary of the Pull Request
Added telemetry on zone settings change event

PR Checklist

[x] Applies to #1254

I think we should add an entry for the number of active zonesets.


Fix shell portability issues

We had problems with seed-my-ontology-repo.pl on Debian and Ubuntu because of some Bash-isms that aren't supported by /bin/sh.  Constructs like "subsets/*{obo,owl}" were failing.

Thanks!
Because I am so weirdly attached to my lazy bashisms I wrote an expander in the perl. Abstraction just to save a few repetitive lines not sure that's wise..
My fixes are in a branch that will be released soon

Great.  I've tested the current master branch and it works for me on Debian.


[Question] Editor/plugin with support for embedding external markdown

"Write it using your favorite text-editor or IDE (we love VSCode)."

Which plugin do you use when editing an openAPI repo? For large project and multiple contributions, externalizing the markdown makes a lot of sense.
I'm currently using the OpenAPI (Swagger) Editor (42crunch.vscode-openapi) with the Redoc rendering setting. This crashes when adding references to external markdown files.
Do you have any preferred workflow and toolset that doesn't involve a lot of copy/pasting and commenting out the API definition while working with the openapi-repo structure?

I was wondering about the same. I was using Stoplight Studio, cause that's quite amazing and free, but openapi-cli does some opinionated proprietary splitting which other tools do not consume.
However, you can do with VS Code + these two extensions:
https://marketplace.visualstudio.com/items?itemName=42Crunch.vscode-openapi
https://marketplace.visualstudio.com/items?itemName=proohit.openapi-snippets


Warnings when combining enums inside function parameter field of type Control.FlagSizes

Tested versions
v4.3.stable.custom_build [77dcf97d8]
v4.3.stable.mono.official [77dcf97d8]
System information
Godot v4.3.stable (77dcf97d8) - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; <IP_ADDRESS>94) - AMD Ryzen 7 2700X Eight-Core Processor (16 Threads)
Issue description
I wanted to create a custom function to create various control nodes and I didn't know how to do it.
On the official Discord someone helped me and I learned about this '|' operator to combine the enums for the SizeFlags.
But that brought up warnings despite working perfectly, and when doing the combination outside the function it worked perfectly without warnings.
(would be nice if the documentation showed how to combine these enums - I had no idea you can even do that)
Looks similar to the warnings in issue #76223
Steps to reproduce

Create a function with a 'Control.FlagSizes' type as a parameter.
Call the function (or enter default value) with an enum mixture: Control.SIZE_SHRINK_END | Control.SIZE_EXPAND

The warnings you get are:

Minimal reproduction project (MRP)
Make a new Control scene, add a child VBoxContainer and then add a child PanelContainer and Just copy the following:
extends Control

@onready var panel_container: PanelContainer = $VBoxContainer/PanelContainer

func _ready() -> void:
	panel_container.size_flags_vertical = Control.SIZE_SHRINK_END | Control.SIZE_EXPAND # no warning

func change_container_sizing(vertical: Control.SizeFlags = Control.SIZE_SHRINK_END | Control.SIZE_EXPAND) -> void:
	panel_container.size_flags_vertical = vertical

func call_function() -> void:
	change_container_sizing(Control.SIZE_SHRINK_END | Control.SIZE_EXPAND)
	var not_enum: int = Control.SIZE_SHRINK_END | Control.SIZE_EXPAND # no warning
	change_container_sizing(not_enum) # no warning

Bitwise operations on enums result in int, like SomeEnum | SomeEnum == int. The reason is simple: when you use bitwise OR on two or more different elements of an enum (e.g. 1 | 2), it is not a fact that the result (e.g. 3) belongs to the enum.
Enum as a type hint is only suitable for exact values. The result of bitwise OR operation on elements of an enum T is a new type BitField[T]. The set of its valid values is a set of all possible flag combinations. For example, if we have enum MyEnum {A = 1, B = 2, C = 4}, then the type BitField[MyEnum] will have the following valid values: 0; 1, 2, 4; 1 | 2 = 3, 1 | 4 = 5, 2 | 4 = 6; 1 | 2 | 4 = 7.
The core supports BitField<T>, you may have seen it in the documentation as BitField[T], but unfortunately GDScript does not support it at the moment. So you have to specify int for parameters that are bitmasks.


Unable to run the SNLI in pytorch examples

🐛 Bug

To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/pytorch/examples
pip install -r examples/snli/requirements.txt && python3 examples/snli/train.py

Observed below error :
python3 train.py --epochs 1 --dev_every 1 --no-bidirectional --dry-run
CATraceback (most recent call last):
File "train.py", line 9, in
from torchtext import data
File "/opt/conda/lib/python3.6/site-packages/torchtext/init.py", line 42, in
_init_extension()
File "/opt/conda/lib/python3.6/site-packages/torchtext/init.py", line 38, in _init_extension
torch.ops.load_library(ext_specs.origin)
File "/root/.local/lib/python3.6/site-packages/torch/_ops.py", line 105, in load_library
ctypes.CDLL(path)
File "/opt/conda/lib/python3.6/ctypes/init.py", line 348, in init
self._handle = _dlopen(self._name, mode)
OSError: /opt/conda/lib/python3.6/site-packages/torchtext/_torchtext.so: undefined symbol: _ZN5torch3jit17parseSchemaOrNameERKSs
Environment

OS:UB-18.04
Python version: 3.6
PyTorch version:1.7.0a0+fc1103a
CUDA/cuDNN version:
GCC version:7.5.0
Any other relevant information:

Additional context

This doesn't seem to be a PyG issue. Can you clarify?


SAN for SFB deployment

I have 3 servers
1- SFB Front End
2- Edge for external access
3-reverse proxy
I want to export the private key I have only .pem and .der files
I have created the following but no pfx file found to export/import to different servers
I need SAN cert for my lab please help
SFB front end + reverse proxy servers
lyncweb.domain.com
lyncdiscover.domain.com
dialin.domain.com
meet.domain.coom
Edge servers
sip.domain.com
av.domain.com
webconf.domain.com

Thanks,
Yousef

I found the pfx in C:\Central_SSL :) I took the main and the password was blank

Thanks for posting the solution!


Add Token introspection and Caching

As per Indigo IAM best practices:

Tokens will now be introspected for temporal validaty (issued in the past, expires in the future) and that they are from one of possibly many 'trusted' IAM as defined by the IAM_HOSTNAME_LIST in apel_rest/settings.py file.

Tokens are verified by getting the public key of its trusted issuer.

Tokens are now cached for 5 minutes on a successful request to reduce load on the IAM.

docker.run_on_entry.py and yaml/apel_rest_interface have also been changed to allow deployment with support for multiple IAMs
Tests have also been added for the TokenChecker class and existing CloudRecordSummaryView tests have had this new functionality mocked away as they use garbage tokens.

codacy mostly complains because I am accessing private methods in tests.
It does also say a class method could be a function, thoughts?

I have reduced some of the codeclimate repetition, but the remaining ones aren't the same payload, just awfully similar as they what happens when fields are omitted from the token or if the times are wrong.

As this is the last PR for the moment, do you want to resolve the conflicts and rebase before I review?

rebased

I think I have fixed/commented on all your comments now

changes made, when I rebase to update the branch I will squash the previous three commits into existing commits that half fixed the problem ( i.e squashing 4845009 into caae6a4)

OK.

I have rebased, but that has dismissed your review


[Feature] Customizable start date for shopify__calendar

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Currently the Shopify__calendar has a start date of 1/1/2019. I have orders and customers from 2018. Under the current structure customer_chort has customers showing 0 orders in month 1.  To be in a given cohort you need to have at least 1 order in month 1 since that is what qualifies you.  These customers had their first order in 2018 but their cohort_month 1 is calculated starting 1/1/2019.  I've attached sample data to illustrate the scenario.  I've removed the customer_id everything else is as created by the dbt package.
customer_cohorts_example_data.csv
Describe alternatives you've considered
I could clone the repository and modify it, but I'm just learning this stuff so I'd prefer a variable or earlier start data for the spine.
Are you interested in contributing this feature?

[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[X] No.

Anything else?
No response

Hi there @brian-equilife thanks for taking the time to open this!
I think making this start_date customizable would definitely be beneficial to everyone using the package! IMO we should make a shopify__calendar_start_date variable, with the default value remaining 2019-01-01 so as to not to have a breaking change on our hands.
if that sounds good to you, the team can work on slotting this into an upcoming sprint

That sounds amazing.  Thank you @fivetran-jamie

Addressed in the latest release!


[HTM-932] Fix map shift for web mercator projection

The OpenLayers projection was initialized with the extent set to the max extent the admin configured for the app. This is obviously wrong, but even if the app max extent was set to the EPSG:3857 extent in the admin (or the code would use the projection extent from /api/app/.../map member crs.bounds), there would be a mismatch for the latitude range (official EPSG:3857 goes from [-85.06, 85.06] but the projection extent for OL should be [-90.0, 90.0].  As a fix just use the string as projection instead of creating a new OL Projection. OL recognizes the 'EPSG:3857' string and uses the correct extent. For other projections such as EPSG:28992 this change does not seem to matter.
Also actually applies the max map view extent.
TODO:

[ ] Resolutions are still calculated from app max extent

Projection extent does not equate to tile grid extent. Resolutions can't be calculated from projection. For now just do not set View.resolutions at all, we don't use fixed resolutions anyway. Services have tile grids.


[docs] Update list of resources

Description
Update the list of online resources for TornadoVM.
Problem description
If the patch provides a fix for a bug, please describe what was the issue and how to reproduce the issue.
Backend/s tested
Not applicable

[ ] OpenCL
[ ] PTX
[ ] SPIRV

OS tested
Not applicable

[ ] Linux
[ ] OSx
[ ] Windows

Did you check on FPGAs?
Not applicable

[ ] Yes
[X] No

The format is fixed. The PR is ready for review.


kata-env: Fix display of debug options

The runtime and hypervisor Debug options were always showing as
false (although all debug options in configuration.toml were
correctly honoured).
Note: Also moved location of FactoryConfig in RuntimeConfig as the
malign linter was complaining:
virtcontainers/pkg/oci/utils.go:102:20:warning: struct of size 408 could be 400 (maligned)

Original-master-commit: https://github.com/kata-containers/runtime/commits/23a35c84c92e6ce73366edc575ae875ba4d77473
Fixes #724.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

LGTM
CI leaves again


selections is not correct if the target elements have zoom style property

Do you want to request a feature or report a bug?
Yes, there is a bug
What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and create a JSFiddle.

DEMO: https://jsfiddle.net/ns8f43wy/1/
What is the expected behavior?
Your environment:
Selection-version: 1.3.0
Browser-version: Google Chrome 78.0.3904.97
Operating-system: macOS 10.15

Thanks for the report!
Although I'd call it feature since this wasn't considered nor intended for usage in a zoomed context.
I'll take a look at it :)

This feature is non-standard as I just found out wherefore I won't add it.
Browsers will handle it differently and it also supports values which would difficult to resolve.


Fix dead links and apply template

closes #9470

fix dead links to getting-started-guides/*
apply templates/concept template
add note shortcodes

preview is here
original

/assign @tengqm

Changes look good to me. Pls fix the conflict.

OK, I will rebase this soon.

/lgtm
/approve


TRANSFER | Account Balance not Updated

Original ticket: https://github.com/harmony-one/chrome-extension-wallet/issues/102

Based on your description, the funds are deposited in the (contract) address but the balance in the explorer is not updated. It seems to be an issue with the explorer, which I can't do anything about. Can you ask them to reopen the original ticket and transfer it to an appropriate place where the explorer is developed?
Did you see correct balance on ONE Wallet UI?

Closed for now. Let me know if the one wallet UI is showing incorrect balance.


Allow taking single stacks using Shift+Right click

Sometimes I want to quickly take a single or a few stacks from a dank container but not fill my entire inventory with cobblestone. This PR adds the functionality to quickly move one stack (64 for most items, 16 for enderpearls etc...) from the dank inventory to the player inventory by right clicking while holding shift.

This can already done with a regular left click


Refactor Event Processor Client load balancing algorithm to improve performance

PR to close #7545. Tests were written before any refactoring and coverage of the various FindAndClaimOwnershipAsync scenarios was verified.
Also added changes to close #8844
Before and After profiling of running the RunAsync loop on a 100ms ShortLoadBalanceUpdate for 30 seconds:
Previous heap snapshot diff

New heap snapshot diff

Previous GC activity

New GC activity

Previous CPU sample

New CPU sample

Can one of the admins verify this patch?

Thank you for your contribution, @christothes.  I haven't yet taken a look over the changes, but I wanted to let you know that the thoroughness and attention to detail in the summary itself is fantastic, and very much appreciated.
I'll give things an initial pass, and also apologize that we'll probably be a bit slow to engage for the next week or so due to deadlines and the holidays.  I also wanted to call out that we've got a late breaking design change that we're currently making to the Event Processor, which is likely to delay things a bit;  while the overall load balancing should still be close in form, the hierarchy is moving around a bit.  I would definitely see these changes as relevant and highly desirable, so please bear with us, if you'd be so kind.   We'd love to work with you on getting them integrated.

@kinelski: As the primary driver for the load balancing area, would you be so kind as to take point on the review and on planning how we can integrate the improvements into the new design?

Thank you for your contribution, @christothes. I haven't yet taken a look over the changes, but I wanted to let you know that the thoroughness and attention to detail in the summary itself is fantastic, and very much appreciated.
I'll give things an initial pass, and also apologize that we'll probably be a bit slow to engage for the next week or so due to deadlines and the holidays. I also wanted to call out that we've got a late breaking design change that we're currently making to the Event Processor, which is likely to delay things a bit; while the overall load balancing should still be close in form, the hierarchy is moving around a bit. I would definitely see these changes as relevant and highly desirable, so please bear with us, if you'd be so kind. We'd love to work with you on getting them integrated.

Sure thing!

@jsquire I took a crack at merging my changes back in to the new EventProcessorBase. I also tried out a slight variation on the CreateConnection pattern and introduced the EventHubConnectionFactory. Please let me know what you think.

@jsquire I am very impressed from the work of @christothes . While trying to understand his work and being aware your are under a heavy workload now, I tried to put down a couple of nits as I think you would have done and ultimately considering that:

Imitation is the sincerest [form] of flattery (Charles Caleb Colton)

Hi @christothes:
Thank you for bearing with us.  There was a lot of churn in this area that we needed to push through for the pending release.  The last of the structural and feature changes should now be merged, so we're back to stable.   We've got a couple of tasks that we need to close out for release over the next day or so, and then @kinelski and I will loop back around and start working through things to help get this incorporated.
Thank you, again, for your contribution and patience.

Thanks for the update @jsquire. I have a local version of this branch with the merge issues resolved. It just needs a bit more work on the mocking approach, which has changed quite a bit in response to the structural changes. I should be able to push something by end of week.

@kinelski Thanks for the extensive review - I got most of them resolved, I think.

@kinelski Thanks, I think we are good now.

Just left one more comment regarding an indentation issue I happened to find. Other than that, it looks good to me! Thanks for the patience.
I'll just wait for @jsquire's review and, after that, we should be able to get it merged.

Thanks!  just pushed the indentation fix.

Thanks! just pushed the indentation fix.

Thank you! We are good now. Please give us a final thumbs up and we can merge it!

Thank you! We are good now. Please give us a final thumbs up and we can merge it!

Hope that you don't mind; I noticed things were ready and stepped in for the merge.
Thanks to you both for working through things to bring this in.   I cannot thank @christothes enough for being patient and understanding as we churned most of this area for the last release;  the amount of time and effort to just keep these changes free of conflicts was significant.   We very much appreciate not only your contribution, but your graciousness and professionalism throughout.


Confirm Content from old Wiki is in new Pages - Adding a new Field to the Rollup Definition

https://github.com/SFDO-Community/declarative-lookup-rollup-summaries/wiki/Adding-a-new-Field-to-the-Rollup-Definition
Confirm that all the information on this page already exists in the new pages site. If not, either create a Page or comment on this issue that it needs doing.

I don't actually understand what this page is talking about and, therefore, don't think it needs to be transferred...
Confirm this and close @sharicarlson13 or @cpra12 ?

@mkolodner I don't think it needs to be transferred, but I don't think it should to be deleted in the development repo. It seems to be documentation for the developers who are working on the app.


Test fault handle new error messages for unathorized container access

please squash your commits. Why do you have a "merge" in your commits ?


Add log verbosity configuration and move the log in controller.go to debug level

Currently, we print a log message for each span:
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/61ff124646105a2058863b17da1815d8d42d78b3/internal/pkg/opentelemetry/controller.go#L54
We should change that to have a debug level.
We don't have a configuration for verbosity. We probably should add support for configuration via:

command line arguments
InstrumentationOption
Enviroment variable (?)

This will need to be modified:
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/61ff124646105a2058863b17da1815d8d42d78b3/instrumentation.go#L70-L83

@MrAlias @pellared  I'd be happy to hear your thoughts on this.

Can we add the logger as an Instrumentation option? I saw this comment about it:
https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/02686f0a149b13fec4da73b9d40233a372fbd13b/instrumentation.go#L90-L94
The log line mentioned in my first comment is the one I worried about since we currently have huge amounts of logs, so adding a verbosity option seems helpful (using the debug level for tests and development).

@RonFed is this open for contribution?

@khushijain21 Sure

@vitorhugoro1 yes, you can go ahead

@vitorhugoro1 I think we need to support the first 2, and not sure about env var.
@MrAlias What do you think?

Regarding env var I think we should support OTEL_LOG_LEVEL per https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/sdk-environment-variables.md#general-sdk-configuration


0.14.2 tag/release is missing

It seems like you forgot to push the 0.14.2 tag, can you please do so?

related: #129