Create profile on MSM to create an app for adding First party MSA support

https://msm.live.com/wizard/default.aspx

Create and upload certificates for DEK(Decryption key)


Docs related to UseInternalTransaction option is confusing

Have a look at snapshot above. First the language of doc itself is unclear. For instance You can explicitly **specify** the UseInternalTransaction option in SQLServerBulkCopyOptions is unclear whether to set it as true or false. Word specify is not a valid term for boolean field. All the underlined lines above fails to mention the behavior works on which value of the field (true or false?).

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

ID: 48895791-97e3-60f4-9ec8-b98a6e0fb896
Version Independent ID: 1deffd8a-4485-da2c-0742-e8426c8f7e3e
Content: Using bulk copy with the JDBC driver - SQL Server
Content Source: docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

@ankitbko -- Ankit, thank you for your feedback.  Please consider these resources:

DBA Stack Exchange
Stack Overflow

@David-Engel -- David, please look into this issue.

I've updated the content to better reflect what UseInternalTransaction does. Most of that section has been removed since it was inaccurate and unclear.
#please-close


AMP for mx2

Description
We will need to AMP support in order to achieve the best performance with fp16 on NVIDIA GPU. In terms of approach, AMP should rely on custom graph pass functionality in 2.0 and not be monkey patching the frontend for swapping the operators

Hi @szha, could you clarify how this approach (graph pass) would work for the non-hybridized execution? I don't think it would be applied then, which would produce a difference in the behavior. That would negatively impact debuggability of models for example, which is pretty bad.
That said, one of the prerequisites for the graph pass is to remove AMP lists and instead put their content as op's attributes and I believe this should be doable and beneficial.

@ptrendx the reasoning is that we shouldn't need to optimize pure imperative program, because that is designed for model debugging and development, and not for performance.
That said, I recognize that there are still cases where we can't hybridize fully yet and still need performance. One short-term approach could be to utilize the mx.set_np_default_dtype interface. The problem it solves is to switch between fp32 and fp64 as default output data type, as the former is commonly used in deep learning and the later is used in numpy. It should be straightforward to add more data types to it.

It is not just about performance though - AMP changes numerics of the model, so I don't believe it would be great user experience if they got the model to where they liked it, hybridized it and suddenly got different answer.
One way of solving this I guess could be similar to what happens with the storage type (but just on the input side), where the input would be cast before the operator.

Hi @szha, why do you want to implement AMP with a graph pass? Which aspects of the current approach do you expect to improve by switching to a graph pass?
One drawback of the Python-side monkey patching I see is that it is sensitive to how various ops are registered on the client side - NumPy vs legacy, imperative vs hybridized, etc. - ideally, we want to handle this in a uniform way, since we don't really care about these distinctions, as far as AMP itself is concerned.
But I am curious if you have some other deficiencies of the current approach in mind.

@mk-61 mostly cleaner abstraction and feature interaction. Multiple features that rely on monkey patch can't work together.


Widening service status view to accommodate possible FQDNs in that panel

before:

after:

closes #479

Do you also need to adjust the table col widths?  When I messed around with it in my browser, I needed to do something like 50, 25, the 25 to ensure something like "controller-1.c2.lab.solinea.com" fit without wrapping in a full width window on my laptop.

Sorry, I was following the issue ticket too literally and didn't check with an actual fqdn. I will play around with the different widths.

old:

new:

pushing latest changes now.

👍


Force fit on mobile?

I am using iframe-resizer to load my widget on client sites. It works fine on desktop browsing but does not fit on pages in mobile. I set up a simple test page to test functionality on mobile, which works fine: http://www.healthfitchiro.com/wp-content/iframe.html
However, on two different sites where I wanted to test a live-demo, it does not load correctly.
http://www.healthfitchiro.com/alternate-login http://tckayakfishing.com/test-page
This is the widget code that is implemented into client pages:
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
<script type="text/javascript" src="//cdnjs.cloudflare.com/ajax/libs/iframe-resizer/3.5.14/iframeResizer.min.js"></script>
<script type="text/javascript">
document.write('<iframe id="lcembed" name="lcembed" src="https://www.healthfitcorpwell.com/lce/?url=' + document.location + '" width="100%" scrolling="no" frameborder="0" style="overflow:hidden"></iframe>');
$('#lcembed').iFrameResize({log:true, checkOrigin:false, inPageLinks:true, sizeWidth:true});
</script>

Is there a way I can force the iframe to fit into the mobile width on client sites?
PS: I have posted this on StackExchange without much help.

Does adding width: 1px;min-width:100%; to the  In the iFrame help?
On Fri, 2 Jun 2017 at 20:01, produktive<EMAIL_ADDRESS>wrote:

I am using iframe-resizer to load my widget on client sites. It works fine
on desktop browsing but does not fit on pages in mobile. I set up a simple
test page to test functionality on mobile, which works fine:
http://www.healthfitchiro.com/wp-content/iframe.html
However, on two different sites where I wanted to test a live-demo, it
does not load correctly.
http://www.healthfitchiro.com/alternate-login
http://tckayakfishing.com/test-page
This is the widget code that is implemented into client pages:

Is there a way I can force the iframe to fit into the mobile width on
client sites?
PS: I have posted this on StackExchange without much help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/davidjbradshaw/iframe-resizer/issues/490, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAkHEkfLcFrDkqQwEGjD1mOY8GMBnf4Yks5sAE4AgaJpZM4NumZM
.

--
Sent from my iPhone.

It did not help, it unexpectedly caused the page to be too long on mobile somehow without resizing the width. Is there a specific way I need to call those properties? Do you do it right in the tag? <body width="1px" style="min-width:100%">?

Not quite, it needs to be.
<body style="width:1px ;min-width:100%">

Some people have reported that it helps with problems like this. Interested to know if it helps you.

I have updated the code to reflect that and unfortunately no effect. Any other ideas?

Not really, most likely a CSS issue somewhere.

I was finally able to affect some change. There was a div element called wrap that had a set width of 984px, that I changed to 100%. It's not perfect because I suspect other elements have a set width that are larger than I want causing the iframe to overflow but I'll have to track them down. But it is at least somewhat more functional that it was previously.


Dynamic prompts not working in new notebook

I switched to your new notebook (https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast_stable_diffusion_AUTOMATIC1111.ipynb#scrollTo=PjzwxTkPSPHf) and when the 'start stable diffusion' cell runs I get an error that says:
Installed dynamicprompts version (0.27.0) does not match the required version (0.25.2). Please update manually by running: /usr/bin/python3 -m pip install 'dynamicprompts[attentiongrabber,magicprompt]==0.25.2'
Something like this happened with the previous notebook and there the solution for me was adding a cell before 'start stable diffusion' with just this command:
pip install 'dynamicprompts[attentiongrabber,magicprompt]==0.25.2'
But this time when I add that and it gets to 'start stable diffusion' I now get:
Failed reading extension data from Git repository (sd-dynamic-prompts)
Automatic1111 still runs, but it ignores all the {} that have the dynamic prompts and just treats all the options inside those brackets as things separated by commas (I think).
Do you have any idea how to get dynamic prompts working again?  They are a huge part of my workflow these days.
thanks

remove the extension then reinstall it, or simply update it

that worked - thanks!

great!


test: Knative update test dep

Motivation
Update the depedency version of knative-serving-istio, knative-serving-core  from 1.1.2 to 1.3.2
Version bump to 1.3.10 for serving-istio. Added to the readme, hopefully it can help to be clearer which knative release it originated from as we bump the minor versions.
Modification
Checklist

[x] Chart version bumped
[x] README.md updated

This update should've happened in the auto chart bumper (context: #58). Will check why it didn't happen.

Auto chart bumper only upgrades patch versions, for minor and major we still need to update the charts manually for now.


Scrollable dialog with timepicker

Workspace: Jquery 3.2.1, Bootsrap 3.3.7, newest Firefox
Nothing happen, if I click to the botton for the input field.
The container for the clock element is behind the dialog - only visible if the dialog was closed.
dialog = $('#dialog').dialog({
    uiLibrary: 'bootstrap' ,
    autoOpen: false,
    scrollable: true,
    minWidth: 500, maxWidth: 850, height: 600, width: 820
});

$('#form_return_date').timepicker({
	locale: 'de-de',
	mode: '24hr',
	uiLibrary: 'bootstrap'
});

This is fixed in the new development version. Please check the latest build in github located in the dist folder.


$with generate cyclic problem

Laravel Version: 5.4 and 5.3
PHP Version: 5.6
Database Driver  & Version: mysql 5.6

Description:
If I use $with in models related, I received cyclic problem, they not resolvers.
Steps To Reproduce:
Put $with on model Post to relate Comment model...
Put $with on model Comment to relate Post model...
Call Post::paginate() or Comment::paginate(), you will problem..

Reported many times here, this is no bug, you just have to make sure to avoid it.

What?
2017-07-17 12:53 GMT-03:00 Mohamed Said<EMAIL_ADDRESS>
Reported many times here, this is no bug, you just have to make sure to
avoid it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/20106#issuecomment-315779595,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACs-SYflf8I3oH4ct4KzOK8HhelWXCpoks5sO3fVgaJpZM4OaFFG
.

#19479, #18579, #18111, #18063, #1123
It is expected behavior.

Ok, I'll see.
2017-07-17 14:04 GMT-03:00 Clayton Stone<EMAIL_ADDRESS>
#19479 https://github.com/laravel/framework/issues/19479, #18579
https://github.com/laravel/framework/issues/18579, #18111
https://github.com/laravel/framework/issues/18111, #18063
https://github.com/laravel/framework/issues/18063, #1123
https://github.com/laravel/framework/issues/1123
It is expected behavior.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laravel/framework/issues/20106#issuecomment-315816126,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACs-Sc2jzcmprORIVMDc9nJ9nFNkXyVhks5sO5QPgaJpZM4OaFFG
.

Yes, don't do that use it only when it makes sense.
off hand.```

?

The doc should warning this, or show the better way.

2017-07-17 14:08 GMT-03:00<EMAIL_ADDRESS><
<EMAIL_ADDRESS>
> Ok, I'll see.
>
> 2017-07-17 14:04 GMT-03:00 Clayton Stone<EMAIL_ADDRESS>>
>> #19479 <https://github.com/laravel/framework/issues/19479>, #18579
>> <https://github.com/laravel/framework/issues/18579>, #18111
>> <https://github.com/laravel/framework/issues/18111>, #18063
>> <https://github.com/laravel/framework/issues/18063>, #1123
>> <https://github.com/laravel/framework/issues/1123>
>> It is expected behavior.
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <https://github.com/laravel/framework/issues/20106#issuecomment-315816126>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ACs-Sc2jzcmprORIVMDc9nJ9nFNkXyVhks5sO5QPgaJpZM4OaFFG>
>> .
>>
>
>


reworked awkward titles. Fixes RHOARDOC-1352

@Ladicek let me know what you think

@Ladicek fixed, let me know what you think


Problem using forms

Rasa version:
1.2.7
Rasa X version (if used & relevant):
Python version:
3.6
Operating system (windows, osx, ...):
Windows 10
Issue:
The form executes extract_other_slots, it does not extract slots that maps to entities with different name from the slot.
For example, the scenario is a service that give answers about a person. The user enter the name of the person and the chatbot give some information about he/she.
So, the user enters a message like "Jose Alves" and an entity called person is recognized. The form has two slots - parameter and confirmation. The mapping for parameter is the entity person and confirmation are intents that confirm or not the query.
When the form is activated, it reads parameter from the entity person and asks for the slot confirmation. But if the user, instead of confirming que query, changes his mind and enter another name. In this case, the form is already active, will try to extract the confirmation slot, will fail, and then will try to extract other slots. However, when it tries to extract other slots, it has the following check:
# check whether the slot should be filled
# by entity with the same name
should_fill_entity_slot = (
           other_slot_mapping["type"] == "from_entity"
           and other_slot_mapping.get("entity") == slot
           and self.intent_is_desired(other_slot_mapping, tracker)
)

This evaluates to false if the slot maps to an entity with a different name and that's what is said in the comment. But why the slot will be only extracted if it maps to an entity with the same name?
With this code in place, the new name that the user entered in the second time will not be extracted by the form, and the form will ask for confirmation on an old parameter.
In our use case, we need to do this because our parameter in the form can come from different entities. So, commenting out this line - "and other_slot_mapping.get("entity") == slot" - solves our problem.
Error (including full traceback):
The problem is described above. No exception is generated, just a malfuncioning.

Command or request that led to error:
python -m rasa shell --debug --endpoints endpoints-dev.yml

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

Thanks for raising this issue, @tabergma will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

because when you try to extract additional information not related to currently requested_slot from some entity that doesn't have the same name as any slot, how do you which slot this entity should fill?

the code snippet above, is from extract_other_slots method that is responsible to extracting information not related to requested slot. In order to extract requested slot there is extract_requested_slot method

But that's the problem. The method is about extracting other slots, rather than the requested slot.
In validate method, when rasa validates the value of the requested slot, there are these lines (348-350):
extract other slots that were not requested
but set by corresponding entity or trigger intent mapping
slot_values = self.extract_other_slots(dispatcher, tracker, domain)
So, as I understand, rasa will extract the other slots that are required but not requested. However, in the method extract_other_slots, the slots that are mapped to entities are only extracted if the entity has the same name as the slot. And this does't work for our use case, because our slot come from three different entities, it depends on the scenario.

there is exactly the reason why other slots are extracted

So, as I understand, rasa will extract the other slots that are required but not requested.
yes

because our slot come from three different entities it depends on the scenario.
that is exactly the reason why entity name should correspond to slot name, because there is no way to know which slot to populate with recognized entity (e.g. entity number could correspond to several slots)

This is a discussion now, so please post this question on our forum if you want to continue discussion.


[BUG] When koord-manager crashes, the koord-scheduler will fail to start if it is rebuilt.

What happened:

Set the koord-manager webhook configuration's failurePolicy to fail.
Scale the koord-manager's replicas to 0.
Delete the koord-scheduler pod.
The koord-scheduler will fail to start.

What you expected to happen:
The newly created scheduler starts successfully.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

App version:
Kubernetes version (use kubectl version):
Install details (e.g. helm install args):
Node environment (for koordlet/runtime-proxy issue):

Containerd/Docker version:
OS version:
Kernal version:
Cgroup driver: cgroupfs/systemd

Others:

/assign


Failure when comparing against large UInt literal

bug report

Impact: unknown
Other information

Comparing a 32-bit UInt against a large literal results in error message.
val x = UInt(32.W)
when (x === 0xFFFFFFFF.U) {
...
}
Results in:
[error] (run-main-0) java.lang.IllegalArgumentException: requirement failed: UInt literal -1 is negative
[error] java.lang.IllegalArgumentException: requirement failed: UInt literal -1 is negative
If the current behavior is a bug, please provide the steps to reproduce the problem:
See attached testcase to reproduce the issue
What is the current behavior?
Fails with error message
What is the expected behavior?
Process the literal as an unsigned constant rather than a twos-complement constant
What is the use case for changing the behavior?
Awkward to create literals without being able to express them directly
chisel_uint_bug.zip

This is a Scala/Java thing. 0xFFFFFFFF is an Int, so this can't be anything other than -1. E.g., trying that on the Scala REPL:
scala> 0xFFFFFFFF
res0: Int = -1

However! You can do this with either a String or a BigInt. I think both of the following work:
val x = UInt(32.W)
when (x === "hffffffff".U || x === BigInt("ffffffff", 16)) {
  \\...
}

Some additional notes:

You can also use a long, 0xffffffffL.U, though this will break at 64 bits.
For the String-to-UInt conversion, x also works as a hex radix specifier, eg "xffffffff".U

This isn't the first time we've seen this, so it might be worth adding a helpful "did you mean to ..." message for this type of error...

Thanks, string to UInt much cleaner than
Fill(32, 1.asUInt(1.W))


Syntax highlighting is broken for some languages

Opening this to have a referable issue.
As @Alhadis reported there is an issue with separate syntax highlighting engine that is causing syntax highlighting issues…

Something's changed with GitHub's handling of TextMate-powered highlighting. There's now a [runaway-match issue][1] with my [.gitconfig grammar][2], and I distinctly recall seeing no issues with it on GitHub until relatively recently. Compare GitHub's rendering of the file to that of Atom's:

GitHubAtom

This doesn't appear to be an issue with regex engine flavours, or how recent they are. I can see @jtbandes's [example][3] is affected by the same highlighting failing to terminate at the end pattern specified by the TextMate grammar.

This is not an issue with linguist and not likely to be an issue with the grammars we bundle.
An issue has been opened with the team that manages the highlighting engine and I'll keep this issue updated as I hear more.

After looking into the reported examples a bit, I believe one possible root cause of these issues is that (?!\G) is not working in end patterns.
This would explain the following issues:
Swift
class A: B {
  let x: Int
}

Reported at: https://github.com/jtbandes/swift-tmlanguage/issues/10, https://github.com/jtbandes/swift-tmlanguage/issues/12, https://github.com/jtbandes/swift-tmlanguage/issues/13
(?!\G) used here: https://github.com/jtbandes/swift-tmlanguage/blob/f839cb6fde7c5afa1e08c38625c95b80bb05c626/Swift.tmLanguage.yaml#L880

gitconfig
[good]
b = c
[bad]

Reported at: https://github.com/github-linguist/linguist/pull/6603#issuecomment-1867175606
(?!\G) used here: https://github.com/Alhadis/language-etc/blob/f3e265b2c155eded4a1808d4b75136ffbd6406b5/grammars/gitconfig.cson#L317

TOML
[good]
b = c  # comment
[bad]

Reported at: https://github.com/github-linguist/linguist/pull/6603#issuecomment-1868001787
(?!\G) used here: https://github.com/textmate/toml.tmbundle/blob/e82b64c1e86396220786846201e9aa3f0a2d9ca2/Syntaxes/TOML.tmLanguage#L46-L47

Here are a couple others which may I'm not able to trace to a specific instance of (?!\G), so there might be other types of end patterns that also don't work... or maybe the problem is that \G isn't working in general?
class Foo<A, B> where A: Identifiable, B: Identifiable {
  var x: A
}

Reported at: https://github.com/jtbandes/swift-tmlanguage/issues/11
Not entirely sure if this maps to the same issue. The patterns used here are a bit complex and \G is used in both begin and end.
Relevant patterns: https://github.com/jtbandes/swift-tmlanguage/blob/f839cb6fde7c5afa1e08c38625c95b80bb05c626/Swift.tmLanguage.yaml#L735

macro IntroduceArbitraryPeers<T>(_: T) = #externalMacro(...)
macro IntroduceArbitraryPeers<T>(_: T) = #externalMacro(...)

(...)
macro IntroduceArbitraryPeers<T>(_: T) = #externalMacro(...)
macro IntroduceArbitraryPeers<T>(_: T) = #externalMacro(...)

Reported at: https://github.com/jtbandes/swift-tmlanguage/issues/9
Not sure if this relates to the usage of \G or some other end pattern not working. Could be related to this end pattern: https://github.com/jtbandes/swift-tmlanguage/blob/f839cb6fde7c5afa1e08c38625c95b80bb05c626/Swift.tmLanguage.yaml#L1614

let SE0168 = """   illegal
        foo
    illegal"""

Reported at: https://github.com/jtbandes/swift-tmlanguage/issues/7
\G is present, but the pattern uses match, not begin/end. Relevant patterns: https://github.com/jtbandes/swift-tmlanguage/blob/f839cb6fde7c5afa1e08c38625c95b80bb05c626/Swift.tmLanguage.yaml#L2282-L2283

@lildude Just an FYI, \G and (?!\G) are two of the most important idioms in TextMate grammars, as they're essentially all authors have by way of maintaining state and structure, especially in multiline patterns.
It might be that the location of the last match normally dereferenced by \G is getting reset between pattern lookups.

Not sure if this is the right place but tons of problems with Swift files recently...

@Kaspik yes, it was the PR that changed the Swift grammar which first brought this to light.

Also broken for CMake:
# This is a comment
if(${higlighting} STREQUAL "it works")
endif()

versus
# This is a comment

if(${higlighting} STREQUAL "it works")
endif()

Thanks, everyone, for your reports in this thread, and for your patience with these regressions. The issue is indeed the handling of ?!\G tokens; these were provided by a custom fork of PCRE v1, made by someone who’s since departed the company, that had been bitrotting for nine years (and unsurprisingly did not work on Apple Silicon). We’re currently investigating how we can support these tokens without sacrificing speed or maintainability; in the meantime, we’re moving as many languages as we can to use tree-sitter based highlighting.

in the meantime, we’re moving as many languages as we can to use tree-sitter based highlighting

Uh… what languages, exactly? How many? I'm interested in how many of my TextMate grammars might be substituted for a lower-quality or buggier tree-sitter version…

Also, I forgot to ask: why is there an outdated fork of PCRE being used instead of, y'know, something contemporary? This isn't a fault with the TextMate grammar format itself, but the regex engine that powers its pattern-matching. Portable grammars (or at least those that I've written) can leverage a subset of regex features that's supported by both modern PCRE, Perl, and Oniguruma. At no point should a fork be needed…

@Alhadis We have, for some time, been using tree-sitter for C, C#, CSS, Elixir, Gleam, Go, HTML, Java, JavaScript, JSDoc, Nix, PHP, Python, CodeQL, regular expressions, Ruby, Rust, TLA+, and TypeScript. This week I’m hoping to get to C++, .gitconfig and .gitmodules, XML, and R.
As to the technical reasons behind this change, tree-sitter grammars are simply a better fit for the GitHub highlighting service. TextMate grammars made sense for their original use-case, but for the purpose of our highlighting service (a non-interactive, stateless RPC server, very different from any text editor), regular expressions are not competitive, speed-wise, with tree-sitter’s generated C, and speed is one of our most important desiderata, given the scale at which this service has to operate. The speed increase when switching from a TM to TS grammar is noticeable from an end-user perspective. However, as I mentioned above, we’re looking into how we can add back support for \G and ?!\G qualifiers as a stopgap measure.
@jtbandes If you see regressions, we’d be grateful if you’d report them so we can improve the whole tree-sitter ecosystem! VS Code is actually a bit of an exception w/r/t its continued use of TextMate grammars; neovim, Pulsar, Zed, and now Emacs are all using tree-sitter for highlighting. tree-sitter is very much the lingua franca at GitHub for anything parsing-related, and that’s unlikely to change. For what it’s worth, we’ve been very happy with the capabilities of tree-sitter for syntactically rich languages like Ruby (and these syntax highlighting queries are much more concise than the equivalent .tmlanguage JSON files; Ruby’s is only a few hundred SLOC).

Thanks for the update on your continued work on this @patrickt.
You mentioned a few languages on your tree-sitter migration roadmap, but I noticed that Swift (which the original issue was reported about) is not on the list. Where can I follow your progress for the upcoming work?

@tevelee Oops, I forgot to mention: tree-sitter-swift integration landed today. There are a few regressions, but also several bug fixes (e.g. the ones related to multiline strings). I’m working with someone on the Swift team to get to parity (and perhaps beyond!) what we had with the TextMate grammar.

@patrickt Is the Swift stuff using https://github.com/alex-pinkus/tree-sitter-swift or a different grammar? Let me know if any help with that migration is needed — while I have not worked on the tree-sitter side, I have intimate knowledge of the TM grammar and recently updated it with support for highlighting regex literals, as well as some other modern stuff which I believe the tree-sitter grammar currently does not support. If I can be of assistance, drop me an email or DM.

@patrickt Hypothetically, if one were to write a proof-of-concept that demonstrated how TextMate grammars could be used to provide a structured parser grammar based on a combination of their regex patterns and properties associated with scopes that capture groups are tagged with… would that be something of interest to GitHub?

@jtbandes Thank you for your help! We’re using the @alex-pinkus version, yes, and I believe (though don’t quote me on this) he and we have been talking about making it the official Swift grammar in the tree-sitter org. Highlighting of components in regex literals are exactly the kind of thing I don’t want to regress—though it’s EOD for me, so that’s a job for tomorrow morning. I’ll
@Alhadis I think that sounds extremely cool, and I’d like to see your results, but if by “of interest to GitHub” you mean “sufficient for us to prefer TextMate grammars over tree-sitter grammars,” then I’m afraid that the answer is no. If there are missing syntax-highlighting features or developer amenities in tree-sitter as compared to what TextMate provides, then that’s a bug in tree-sitter that we'd very much like to fix.

but if by “of interest to GitHub” you mean “sufficient for us to prefer TextMate grammars over tree-sitter grammars,” then I’m afraid that the answer is no.

No, I mean “sufficient enough to disincentivise mass-migration of existing TextMate grammars to potentially inferior tree-sitter versions”.

If there are missing syntax-highlighting features or developer amenities in tree-sitter as compared to what TextMate provides, then that’s a bug in tree-sitter that we'd very much like to fix.

It's not a bug in tree-sitter. It's the very design of the system itself that feels over-engineered and extremely hostile to grammar developers. I don't doubt that tree-sitter is performant and well-optimised to GitHub's needs, but TextMate's simplicity and flexibility are its key strengths to a grammar author. Moreover, it's not bound by the restrictions of a formal parser grammar, and it lends itself well to informal, unstructured formats like logs and program output.

Be cool man, let's leave this thread to report issues with the grammar.
Thanks @patrickt for the work you put in to syntax highlighting and for the detailed update! It would've been very easy to leave us in the dark so your posts are much appreciated.

No, I mean “sufficient enough to disincentivise mass-migration of existing TextMate grammars to potentially inferior tree-sitter versions”.

I’m afraid not, no. I appreciate your concerns and sympathize with your frustration, but this decision is set in stone at this point. The set of trade-offs with which we are working render us willing to accept temporary regressions (all of which, in my experience, have been trivially fixable) for the several axes on which tree-sitter provides concrete improvements.

MATLAB source is also having issues in that GitHub classifies anything in the document after the first % comment to be a comment.

Review of matlab code is quite challenging on GitHub:

Hey, everyone 👋 Thanks to some absolutely heroic work on the part of @dcreager, we’ve addressed the regressions people have been observing. Please let us know if you spot any further infelicities, and thank you all very much for your patience while we fixed these issues.

@patrickt I was literally about to point out how the regression appears to be fixed. Thanks for all your hard work!

Thanks for your hard work. I’m sad to see Swift.tmLanguage go since it’s my baby, but I guess this will put more pressure on tree-sitter-swift to support all the language features. Maybe I will get around to contributing to it some day.

@patrickt As of now, still seeing some issues with Swift files (like 'lazy', or 'dataSource' / 'delegate'), but overall seems much better! (or current PR just has no specific code that was problematic 😄 )

@Kaspik Those issues would be due to the switch from Swift.tmLanguage to tree-sitter-swift.

Interestingly, I'm still seeing the Swift tmLanguage grammar being used in some places. It looks like it's used for diffs in Markdown files but not Swift files: https://gist.github.com/jtbandes/34a7a9fcc972f1d4d3f3ca6a39b86ccd/revisions

@jtbandes Keen eye regarding Markdown—yes, the fact that embedded Markdown goes through the legacy TextMate path is an implementation detail we hope to fix someday (right now Markdown itself does not go through tree-sitter, which would be a first step, but after that it also requires some thought re. implementation). Thank you also for the Swift grammar test file you’ve written—I hadn’t seen this before, and this will greatly assist getting tree-sitter-swift to parity with what we had in Markdown. I’ve already landed a few fixes (here, here), and am going to knock more out tomorrow and also update the grammar GitHub-side. Hoped to get to that today but, as always, so much to do.

I think having Markdown done through old implementation is actually a good thing because you have direct comparison what's needed and left to be improved in the implementation. The Markdown code above is much easier to read than the Swift file. I wouldn't migrate Markdown till the Swift one fixed.

@lildude I think this can be closed absent further reports of TM grammars breaking.

Thanks @patrickt.

Hey folks, it looks like single-line comments in C++ are broken:

https://github.com/jackma/mcap_mqtt_recorder/blob/main/main.cpp#L26
Although it does work properly in a markdown code snippet and gist:
// Return the stamp property if set, otherwise use the current time
mcap::Timestamp GetTimestampFromProperties(
    mqtt::properties properties, const std::string& stamp_property)

https://gist.github.com/jtbandes/6b632b45e4a88ce178d7c9b7b1810b91

Hi :wave:
Python code blocks in rst are now 100% underline: https://github.com/piskvorky/smart_open/blob/develop/README.rst
Is it a remnant of this issue, or should I create a new one?

Is it a remnant of this issue, or should I create a new one?

This is a whole new issue and nothing to do with Linguist or the original issue. github/markup is the repo responsible for rendering codeblocks in rst files so an issue needs to be logged there or directly with GitHub support.


screeninfo.get_monitors() return an empty list on OSX

Describe the bug
After cloning the repo, installing with pip install -e . and running manimgl example_scenes.py I get an error due to
get_monitors() returning an empty list.
>>> import screeninfo
>>> screeninfo.get_monitors()
[]

But since I am using OS X, I run the example from screeninfo:
>>> screeninfo.get_monitors(screeninfo.Enumerator.OSX)
[Monitor(x=0, y=0, width=1680, height=1050, width_mm=None, height_mm=None, name=None)]

Code:
example_scenes.py
Wrong display or Error traceback:
Traceback (most recent call last):
  File "/Users/eisamar/.virtualenvs/manimgl-s7-qgcON/bin/manimgl", line 10, in <module>
    sys.exit(main())
  File "/Users/eisamar/devel/manimgl/manim/manimlib/__main__.py", line 13, in main
    config = manimlib.config.get_configuration(args)
  File "/Users/eisamar/devel/manimgl/manim/manimlib/config.py", line 237, in get_configuration
    monitor = get_monitors()[custom_config["window_monitor"]]
IndexError: list index out of range

Additional context
If I change manimlib/config.py to use Enumerator.OSX I get a new error on File "/Users/eisamar/devel/manimgl/manim/manimlib/window.py", line 41, in find_initial_position. Changing also that resolves the problem (for me :p).

Can you clarify what you changed besides using Enumerator.OSX to resolve the problem?  I've never successfully used manimgl never mind hacked it.  I'm on Big Sur and python3.8 and the current version of manimgl.  Could a branch be created with this bug fix/workaround?  Thanks!

Can confirm the same happening on python 3.9, OSX Big Sur, should this os info be automatically handled by screeninfo?
If not, a simple wrapper with @martisak fix should do the work
import screeninfo
import platform

def get_monitors():
    if platform.system() == 'Darwin':
        return screeninfo.get_monitors(screeninfo.Enumerator.OSX)
    return screeningo.get_monitors()


Endless fetching firebase-ios-sdk.git

Hello. I am trying to add firebase using SPM for the second day. But beyond this moment I cannot advance. Please tell me what could be the problem

In total, the download has already been going on for about 10 hours

Hi. Thanks to all. After a couple of days, everything worked. But it is not clear what was the reason


Implement scrollOffsets behavior.

scroll-timeline-base.js currently allows setting the scroll offsets array but otherwise ignores it. We should follow the chromium implementation of having start/end timeline update the scroll offsets array entries.

This issue is no longer relevant with the merge of #28 I guess?

Yup, this is fixed. Thanks!


Error: Handlebars partials are not supported

Not much to add here, I can provide stacktrace if you want

@CiriousJoker The issue is probably upstream in the Prettier glimmer parser.
Can you explain what you are trying to do and what errors you get?
Also since partials are deprecated this probably won't ever be fixed anyways :)

Didn't know that partials are deprecated


Feature/create review

This adds functionality to create a review. To test it out:

Log in with an existing user
Change the url to /spilltea
Submit your review data

Next things to add:

[ ] Instead of an alert, we could try to pass a message to the homepage in a query string for a "toast" message.
[ ] Handle editing or deleting an existing review with a /spilltea/:id endpoint

Thanks for the merge from main! I think I'm ready for a review--it still currently uses alerts after the review is submitted, but I think that's ok for now.

Thoughts?
https://www.npmjs.com/package/toastify-js


Debug Wasmer instruction assertion

Testing and debugging for https://github.com/wasmerio/wasmer/issues/1856

PR was merged upstream, thanks


(Urgent) Question on RI cancellation penalty

[Enter feedback here]
Hello team,
I'm looking for someone in charge of RI cancellation policy.
At the moment, there is no RI cancellation fee.
Is there any ETA that MS will start charging cancellation fee?
Is there confirmation at this point that MS will not charge RI cancellation fee after 1 year for 3 years RI?
Thank you. Looking forward to hearing from you.

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

ID: 3f0af130-6b0a-0a7e-5fd9-e67810f66b45
Version Independent ID: 445b1c77-472a-e0f7-45fc-168f4a2454f3
Content: Self-service exchanges and refunds for Azure Reservations - Microsoft Cost Management
Content Source: articles/cost-management-billing/reservations/exchange-and-refund-azure-reservations.md
Service: cost-management-billing
Sub-service: reservations
GitHub Login: @bandersmsft
Microsoft Alias: banders

@bibury - Thank you for providing the document details. It looks like you have an issue with the product itself and this feedback is not related to the docs improvement. In this forum, we focus on improving the docs and feedback related to docs only.
Do you mind posting your question on Microsoft QnA as our engineers and community are actively working on answering questions related to the product on the forum.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


feat: recognize Kubernetes NodePorts and LoadBalancer

This PR closes #1021, recognizes kubernetes NodePorts and LoadBalancer for port-forwarding. Based on the idea of https://github.com/lima-vm/lima/issues/1021#issuecomment-1230898249

I will squash commits  after all reviews are done, for reviewers' convenience.

I think this is fine as-is, but I would like to review this on Monday together with @Nino-K to make sure any remaining additional code we have in the Rancher Desktop version is only required for WSL support on Windows, and not relevant to Lima.


Set-MgUserPhotoContent vs set-userphoto

Does this achieve the same result? Perhaps it should be mentioned in the article?
https://docs.microsoft.com/powershell/module/microsoft.graph.users/set-mguserphotocontent

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

ID: 197acba5-5e7c-4fbe-f7c2-3dd9984ba278
Version Independent ID: 633fe153-b3ce-c1ec-1e61-2fe7a323d436
Content: Set-UserPhoto (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-UserPhoto.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@chrisda Kindly help us with your comment. Thanks

No comment.

@Mike-Crowley, I have no idea what the relationship is between the Exchange *-UserPhoto and Microsoft Graph *-MGUserPhoto[Content] cmdlets are. Nevertheless, I added appropriate links to the Graph cmdlets in the Exchange cmdlet topics.
Thanks for the feedback.
Closing


codegen

early poc for #714
We need to clarify which options should be supported

Replaced by https://github.com/quarkiverse/quarkus-cxf/pull/751


Add support for nbf field

Add nbf standard field to check method.
Not before (nbf): Identifies the time on which the JWT will start to be accepted for processing.

I'm not sure I'm getting this right. May you pls elaborate.


Allow concatenation of datasets with mixed structs

Fixes #6466
The idea is to do a recursive check for structs. PyArrow handles it well enough.
For a demo you can do:
from datasets import Dataset, concatenate_datasets

ds = Dataset.from_dict({'speaker': [{'name': 'Ben', 'email': None}]})
ds2 = Dataset.from_dict({'speaker': [{'name': 'Fred', 'email'<EMAIL_ADDRESS>print(concatenate_datasets([ds, ds2]).features)
print(concatenate_datasets([ds, ds2]).to_dict())

Now both the features and the rows are fixed.
I note that Sequence suffers from the same problem, so I can fix that in a future PR once this one is merged.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

friendly bump


Working solution to node-red-contrib-ewelink does not anymore connect

Hi,
Many of you have realized that it is no longer possible to connect and therefore control your ewelink modules from node-red-contrib-ewwelink. This is due to the obsolescence of the authentication method used, now replaced by OAUTH2. "domesticstreamers " posted an update with OAUTH in project node-red-contrib-ewelink-apikey. It's available at https://flows.nodered.org/node/node-red-contrib-ewelink-apikey but the code is not on Git. To make it work, you will need an API key, to be created at https://dev.ewelink.cc/, and enter it in the config node. For the rest apparently it seems to work like node-red-contrib-ewelink. I only tested it on Sonoff DIY switches.
node-red-contrib-ewelink  must be uninstalled first before installing node-red-contrib-ewelink-apikey. Backup your flows!
It would be great if the initial project and documentation was updated with these modifications.
In any case thanks to https://flows.nodered.org/user/domesticstreamers for these modifications.

Hi,
Many of you have realized that it is no longer possible to connect and therefore control your ewelink modules from node-red-contrib-ewwelink. This is due to the obsolescence of the authentication method used, now replaced by OAUTH2. "domesticstreamers " posted an update with OAUTH in project node-red-contrib-ewelink-apikey. It's available at https://flows.nodered.org/node/node-red-contrib-ewelink-apikey but the code is not on Git. To make it work, you will need an API key, to be created at https://dev.ewelink.cc/, and enter it in the config node. For the rest apparently it seems to work like node-red-contrib-ewelink. I only tested it on Sonoff DIY switches.
node-red-contrib-ewelink must be uninstalled first before installing node-red-contrib-ewelink-apikey. Backup your flows!
It would be great if the initial project and documentation was updated with these modifications.
In any case thanks to https://flows.nodered.org/user/domesticstreamers for these modifications.

Why isn't the code public in GitHub? It doesn't feel very secure...

For anyone trying to find a solution, I can recommend this module: node-red-ewelink-v2-oauth
Working and well documented.
https://github.com/FloFlal/node-red-ewelink-v2-oauth/blob/main/docs/index.md


'-' inserted in place of spaces with negative shift

This is caused because spaces are represented by number 32 on the Ascii table.
When the number 32 is found in this if statement:
else if (e + key < 97) {
      arr.push(122 + (key + (e - 96)));
      arr.shift();
    }

it takes 32 deducts 96 and adds the key, -13 in the case of my test, then adds 122 which equals 45 or - on the Ascii table.

My solution to this issue is to check explicitly for 32 and if found return the same character.
This if statement will be inserted at the top of this section.
//Check for spaces
     if (e === 32) {
       arr.push(e);
       arr.shift();
       }


bio-gappa: 0.8.4 -> 0.8.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/lczech/gappa/releases.
meta.description for bio-gappa is: Toolkit for analyzing and visualizing phylogenetic (placement) data
meta.homepage for bio-gappa is: https://github.com/lczech/gappa
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.8.5 with grep in /nix/store/0dx2kcm937ds86zvhlillmjsfgrpk5s1-bio-gappa-0.8.5
found 0.8.5 in filename of file in /nix/store/0dx2kcm937ds86zvhlillmjsfgrpk5s1-bio-gappa-0.8.5

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bio-gappa

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0dx2kcm937ds86zvhlillmjsfgrpk5s1-bio-gappa-0.8.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/6086df8d4d348f50eb6e47fa8a91fc8a57f6f6b1#bio-gappa

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0dx2kcm937ds86zvhlillmjsfgrpk5s1-bio-gappa-0.8.5
ls -la /nix/store/0dx2kcm937ds86zvhlillmjsfgrpk5s1-bio-gappa-0.8.5/bin

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

x86_64-linux

:white_check_mark: 1 package built:

bio-gappa

Maintainer pings
cc @bzizou for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Partial fix for #3676 - fix race in ElementMetadata

The accessor for ElementMetadata can sometimes return null when
concurrently accessed. This change solves this issue by precomputing all
type-related facets of ModelMetadata. This also adds a ElementType
property to ModelMetadata to maintain the current separation of concerns
as ModelMetadata is unaware of the metadata provider.

A simpler fix for the race part of #3676 would move a single line to the end of the ElementMetadata getter. Need to improve the description to cover what you're actually doing: Setting all Type-related properties in ModelMetadata up front, removing lazy initialization of a half-dozen or so properties. I don't object to the change but it is only "inspired by #3676".

:shipit: with broader commit description

This change solves this issue by precomputing all type-related facets of ModelMetadata.

Already in the commit description. I'll update it to be clearer.


Console: Lorank8 gateways

This is a feature request for the Console.
See: https://github.com/TheThingsNetwork/ttn/issues/427
Please add the following to the console:

When a user registers a new gateway
Check if it is registered via the Bridge
Check if it is a Lorank8 gateway
Display a warning saying:

You are using a Lorank8 gateway. By default this gateway sends status messages in a format unsupported by TTN. Please change the status message format in the configuration of your gateway from ideetron_concise to semtech.

The same message should be displayed if the gateway ID starts with "eui-1dee".


Type error when using two async actions on one reducer

I'm receving a type error on one of my reducers and I don't know what to do:
Argument of type '() => PayloadAction<"USER/AUTH/RENEW", RequestPayload>' is not assignable to parameter of type '((...args: any[]) => PayloadAction<"USER/PERMISSION/SET_LOCATION", PermissionInfo> | PayloadAction<"USER/PERMISSION/SET_LOADING", boolean> | ... 11 more ... | EmptyAction<...>) | ((...args: any[]) => PayloadAction<...> | ... 12 more ... | EmptyAction<...>)[]'.
  Type '() => PayloadAction<"USER/AUTH/RENEW", RequestPayload>' is not assignable to type '(...args: any[]) => PayloadAction<"USER/PERMISSION/SET_LOCATION", PermissionInfo> | PayloadAction<"USER/PERMISSION/SET_LOADING", boolean> | ... 11 more ... | EmptyAction<...>'.
    Type 'PayloadAction<"USER/AUTH/RENEW", RequestPayload>' is not assignable to type 'PayloadAction<"USER/PERMISSION/SET_LOCATION", PermissionInfo> | PayloadAction<"USER/PERMISSION/SET_LOADING", boolean> | ... 11 more ... | EmptyAction<...>'.
      Type 'PayloadAction<"USER/AUTH/RENEW", RequestPayload>' is not assignable to type 'PayloadAction<"USER/PERMISSION/SET_LOCATION", PermissionInfo>'.
        Type '"USER/AUTH/RENEW"' is not assignable to type '"USER/PERMISSION/SET_LOCATION"'.

I'm using 2 actions from with similar type signatures generated from createAsyncActions one is:
export const renew = createAsyncAction(
  ['USER/AUTH/RENEW', (): RequestPayload => ({
    client: 'user',
    request: {
      method: 'POST',
      url: '/renew',
    },
  })],
  ['USER/AUTH/RENEW_SUCCESS', (response: AxiosResponse<LoginResponse>): AxiosResponse<LoginResponse> => response],
  ['USER/AUTH/RENEW_FAIL', (error: AxiosError): AxiosError => error],
)<RequestPayload, AxiosResponse<LoginResponse>, AxiosError>();

and the other
export const renew = createAsyncAction(
  ['USER/AUTH/LOGIN', (data: Login): RequestPayload => ({
    client: 'user',
    request: {
      method: 'POST',
      url: '/login',
      data,
    },
  })],
  ['USER/AUTH/LOGIN_SUCCESS', (response: AxiosResponse<LoginResponse>): AxiosResponse<LoginResponse> => response],
  ['USER/AUTH/LOGIN_FAIL', (error: AxiosError): AxiosError => error],
)<RequestPayload, AxiosResponse<LoginResponse>, AxiosError>();

this is the reducer with the error
const reducer = createReducer(INITIAL_STATE)
  .handleAction(actions.login.success, (state, { payload }) => ({
    ...state,
    data: payload.data.user,
    token: payload.data.token,
    loading: false,
  }))
  .handleAction(actions.login.request, state => ({
    ...state,
    loading: true,
  }))
  .handleAction(actions.login.failure, state => ({
    ...state,
    loading: false,
  }))
  .handleAction(actions.setUser, (state, { payload }) => ({
    ...state,
    data: payload,
  }))
  .handleAction(actions.setToken, (state, { payload }) => ({
    ...state,
    token: payload,
  }))
  .handleAction(actions.renew.request, state => state)
  .handleAction(actions.renew.failure, state => state)
  .handleAction(actions.renew.success, (state, { payload }) => ({
    ...state,
    data: payload.data.user,
    token: payload.data.token,
  }))
  .handleAction(actions.reset, () => ({ ...INITIAL_STATE }));

export { reducer };

This is the other action cited on the error:
export const setLocation = createAction('USER/PERMISSION/SET_LOCATION')<PermissionInfo>();

I have 3 more reducers, one of them is using a single async action with no problems. When I tried to add two and the auth reducer everything exploded and I don't know why.
I'm using the same configuration on the codesandbox and changing the order of the handleActions just change on which one it will show the error.

Hey @brunoti, I cannot help you report is not complete. Please use the template.


Noting a macOS 15 Beta 3 crash

We're working through MLX support over in WhisperKit and noticed a crash that happens on macOS 15 but not 14. It occurs on this particular test, oddly many of the other tests still pass.
How to replicate:
git clone https://github.com/argmaxinc/WhisperKit.git
cd WhisperKit
git checkout mlx-support
make setup
make download-mlx-models
xcodebuild test -only-testing WhisperKitMLXTests/MLXUnitTests -scheme whisperkit-Package -destination "platform=macOS"

Or to run them in xcode,
xed .

And open up the tests, then run the MLXUnitTests suite, particularly testEncoderOutput

This throws the following assert:
template <class _Tp, class _Allocator>
_LIBCPP_CONSTEXPR_SINCE_CXX20 inline _LIBCPP_HIDE_FROM_ABI typename vector<_Tp, _Allocator>::const_reference
vector<_Tp, _Allocator>::operator[](size_type __n) const _NOEXCEPT {
  _LIBCPP_ASSERT_VALID_ELEMENT_ACCESS(__n < size(), "vector[] index out of bounds");
  return this->__begin_[__n];
}

Where __n is 3 and I cant tell what size() is but I would assume less than or equal to 3.

This is probably a dup of https://github.com/ml-explore/mlx-swift/issues/104, which is fixed in MLX core and should be picked up in swift in the next release (week or so).

Ah great, will use -configuration Release in the meantime.


After a couple of hours of not using the runner, it will become offline

So after everything is up an running, did run some jobs, all is good but then, after not using the runner for some hours, it wil become offline, and I will have to delete the runner pool and delete the runner from github so that it gets recreated. Is there some setting like idle timeout or something like that? I do have the minimum runner set to 1 in my CRD

Hello?

What does the logs of the pod say? I am no longer working with tietoevry, and no longer have write-access to the repo - but might be able to shed some light on what is wrong.

Hi @davidkarlsen
we have these in our logs of the pod
# Runner removal

Cannot connect to server, because config files are missing. Skipping removing runner from the server.
Does not exist. Skipping Removing .credentials
Does not exist.

Cannot connect to server, because config files are missing.

BTW: Love traktor ;-)

@davidkarlsen just wanted to confirm that we don't see any issues since one week, looks like it helped, thank you!

@davidkarlsen it happened again, even with the restartPolicy: Never.
In the meantime, until a fix is found I unded up setting a cron that runs every day inside kubernetes to delete the pod. This way a new one is spawned and is automatically registered in github.
I know its not a real solution, it just helps us to focus on different things that are more urgent.
apiVersion: batch/v1 kind: CronJob metadata:   name: delete-runner-pod spec:   schedule: "00 22 * * *"  # Schedule to run daily at midnight Berlin time   jobTemplate:     spec:       template:         spec:           containers:           - name: kubectl             image: bitnami/kubectl  # Using a kubectl container image             command:             - /bin/sh             - -c             - kubectl get pods --no-headers=true | awk '/^runner-pool-pod-/ {print $1}' | xargs -I {} kubectl delete pod {} --grace-period=0 --force           restartPolicy: OnFailure       ttlSecondsAfterFinished: 120


Explicitly state minimum NodeJS version supported

This PR makes it explicit which version of NodeJS is required to run the ndt7 client. NodeJS < 10 does not support URL and probably other features that the code uses.
This also allows us to remove the dependency on workerjs, as Node >= 10.5.0 has native support for workers via the workers_thread module.

This change is

Should we look at raising the minimum version to Node.js 12? According to the official Node.js release schedule, Node.js 10 has been EOL since the release of Node.js 16 on 2021-04-20, making Node.js 12 the oldest LTS version.
Users looking to use an EOL version can always install the package with --ignore-engines or an equivalent flag based on their package manager of choice and patch whatever APIs they need.

I had just looked at which features we use / what's the minimum version of NodeJS that supports them. If the users can still use EOL versions if they really need to then defaulting to >=12 sounds good! Thanks.

.travis.yml should be updated accordingly to reflect whatever version is eventually decided upon:
https://github.com/m-lab/ndt7-js/blob/fa6a78dff2c1ff391581db62cc957ce113fed406/.travis.yml#L3-L4

diff --git a/src/ndt7.min.js b/src/ndt7.min.js
index 957ddd1..2b0e47c 100644
--- a/src/ndt7.min.js
+++ b/src/ndt7.min.js
@@ -1 +1 @@
-[…]
+Promise { <pending> }

diff --git a/src/ndt7.min.js b/src/ndt7.min.js
index 957ddd1..2b0e47c 100644
--- a/src/ndt7.min.js
+++ b/src/ndt7.min.js
@@ -1 +1 @@
-[…]
+Promise { <pending> }

It appears that an asynchronous operation was used to produce the contents of the output file but it was never awaited upon.

Ah, interesting. It seems that comes from minify (minify --js < src/ndt7.js), rather than our code. Updating to a more recent version of minify (7.0.2) fixed it, going back to the previous version breaks it again. The most recent versions of minify require node >= 14, but minify 6.x works with node 12 and does not cause this issue. I've updated it, which has fixed the build.

Based on the changes made to package-lock.json, this PR supersedes #31 and should therefore close #30 once merged. Additionally, the superseded PR will have to be manually closed.
It also appears that the PR will resolve the issue for which #5 was created to fix.

Agreed. I've changed the PR description to close #30 and will close #31 and #5 manually once it's merged.
Re. the value for engines > node, I've set it to >=12 as that seems to be what we want, compatibility-wise.
Any further thoughts on this PR?

I've never seen an engine version declared specifically to its initial LTS version but I find it to be quite informative in its intention.
Sourcegraph shows 34+ results for >=12.13.0 (query) compared to 500+ results for >=12 (query). While >=12 is undoubtably the conventional way projects have declared their support for Node.js 12 (LTS or not), an exact minimum version is beneficial in explicitly providing contributors with a version to develop and test against.
If it isn't too close to the bike shed in our backyard, I believe there is merit in declaring >=12.13.0 as long as our tooling supports it. Off the top of my head, we may need to make an accommodation for Travis CI because its configuration file only takes into account major versions for node_js.

@RA80533 got it, I left it as >= 12.
As a general policy, we never merge a PR without explicit approval. Would you be willing to approve this one?

GitHub’s UI isn’t very clear on this but I believe required reviewers must have write permissions to the repository for their approvals to count. I did, however, approve the changes nonetheless.


Update wait docs

Adds a quick explainer about the ~ in the continue on failure example. Mentions that it's an explicit null character, that it's not required, and that we recommend its use to prevent other things getting in between the wait and the continue lines.
I'm a little unsure of the wording I've used, do you have any feels about it @toolmantim?
Closes #222

Do we have any YAML examples of what errors/situations it tries to protect you from?

I believe this is also valid:
- wait: true
  continue_on_failure: true

I initially used the ~ character because I just thought it looked nicer, and was a bit more "correct". It essentially is saying "This key exists, and I have nothing further to say"
These examples aren't valid YAML:
- wait:
  continue_on_failure: true

- wait
  continue_on_failure: true

A longer explanation around ~ would be something like:
Buildkite looks at the keys defined in a step to infer what sort of step it is. For example, if Buildkite sees a command key, we assume it's a command step. And we use the contents of that key as the command to run on an agent.
steps:
  - command: "blah.sh" # This object has a key "command", therefor we treat it as a "command" step

Wait steps are special because you can just use a literal string "wait" to define a wait step:
steps:
  - wait

The wait key itself doesn't require any configuration, so when defining a wait step with additional properties, you need to set (something) as the value since without a valid, it's invalid YAML. We chose ~ because it's short and sweet, but true works (as well as your favourite emoji:)
steps:
  - wait: true
    continue_on_failure: true
  - wait: ~
    continue_on_failure: true
  - wait: "I like pie"
    continue_on_failure: true
  - wait: ⚽
    continue_on_failure: true

(there's a brain dump on stuff, feel free to chop/change/ignore all the things!)

Thanks for the braindump! Every validator I've tried finds this to be valid YAML, which is what had me confused:
- wait:
  continue_on_failure: true

Yup, totes valid yaml! Perhaps it was an issue with the golang yaml parser initially @keithpitt? For instance, it doesn't actually understand that ~ is null 😅

Thanks for the braindump! Every validator I've tried finds this to be valid YAML, which is what had me confused:

wait:
continue_on_failure: true

You're 100% correct, that is valid YAML. I think my computer busted itself, and I was having Golang memories (as @lox suggested).
So you're right, this is also totally valid:
- wait:
  continue_on_failure: true

It's completely server side, so no agent agents. Do you mean, make the value-less the new default?

Yeah, value-less as the default would be ❤ I think!

I think I prefer the semantics of:
  - wait: ~
    continue_on_failure: true

Mostly because the value-less option just looks miss-configured:
- wait:
  continue_on_failure: true

Feels to me like it's missing some configuration, and doesn't read as nice. At least the ~ is something, and once peeps learn what it means, it makes sense. It also looks a lot like this:
- wait:
    continue_on_failure: true

Which is still a valid pipeline, but that syntax won't be around forever (since it's a little confusing). I'm also unsure what auto-indenters/formatters in editors do with the value-less option. Since whitespace is significant, it's probably hard for editors to know what the intention is.
I'm happy to be convinced that a value-less option is better though!

I think I'm most keen on the - wait: ~ or having the second line indented. Having nothing after the wait, and then having the next line be on the same indent level makes it look like something is missing to me.

Now we have a similar nesting in our new plugin syntax, as far as left whitespace indenting goes, perhaps we should settle on the nested one? That’s the one you’re suggesting yeah @harrietgrace?
- wait:
    continue_on_failure: true

Yep, that's the one I was talking about @toolmantim 👍🏻


exception thrown on global rs::context construction using statically linked libs

An error occurs in a simple 10 line program when using statically linked librealsense, on windows, and seems to happen when rs context is constructed in a global outside of main.
Using statically linked versions of the realsense libraries, an error occurs in the following short program:
#define NOMINMAX
#include "../../include/librealsense/rs.hpp"
#include "../../include/librealsense/rsutil.h"

#ifdef _WIN64
#ifdef _DEBUG
#pragma comment(lib, "../../librealsense.vc14/realsense-s/obj/Debug-x64/realsense-sd.lib")
#else  // release x64
#pragma comment(lib, "..../../librealsense.vc14/realsense-s/obj/Release-x64/realsense-s.lib")
#endif // _DEBUG vs release for x64
#else  // we have _WIN32
#ifdef _DEBUG
#pragma comment(lib, "../../librealsense.vc14/realsense-s/obj/Debug-Win32/realsense-sd.lib")
#else  // release 32
#pragma comment(lib, "../../librealsense.vc14/realsense-s/obj/Release-Win32/realsense-s.lib")   // pragma easier than using settings within project properties
#endif // _DEBUG vs release for Win32
#endif // _WIN64 vs _WIN32

rs::context ctx;  // in global scope this causes 'access violation' and throws exception on program startup
int main(int, const char**)
{
	return 0;
}

But putting the context on the stack, constructing after main is invoked, then the bug does not happen:
int main(int, const char**)
{
	rs::context ctx;  // fine when on the stack here
	return 0;
}

So this indicates something isn't handled properly during the construction of the rs::context within the global scope of a program.
The cause of the error appears to happen during a mutex/lock operation:
    Exception thrown at 0x536039E3 (msvcp140d.dll) in unit_test_g_ctx_construction.exe: 0xC0000005: Access violation reading location 0x00000000.

The call stack at runtime:
          testrs.exe!rs_context::acquire_instance() Line 38	C++
          testrs.exe!rs_create_context(int api_version, rs_error * * error) Line 48	C++
          testrs.exe!rs::context::context() Line 173	C++
          testrs.exe!`dynamic initializer for 'ctx''() Line 21	C++

The project file used for this test was a newly created project file from vs2015 with all default settings.  hence the include pathing and library pragmas at the beginning of the source code shown above.
I can push this unit test into a github branch if you are not able to reproduce.

Required Info

Camera Model
all cameras R200, F200 and SR300

Firmware Version
all

Operating System & Version
PC

Kernel Version (Linux Only)

Build System
VS2015

Hi, what you are reporting makes sense, since the rs::context is managed like a singleton but not really. Originally, librealsense included a limitation allowing only a single instance of context at any given time. Later down the line, my team has somewhat relaxed this restriction based on feedback from ROS community, allowing context to be ref-counted. We intentionally avoided something like Mayers singleton, in order to provide deterministic destruction (once last instance of context is destroyed, we would like all RealSense resources to be deallocated). This might have caused issues when linking statically. This is a purely software issue and hence can be investigated and fixed.

For best support, post issues in the RealSense Community.
Hello,
Do you still need help with this issue?
Best regards,
Jesus
Intel Customer Support

You can close this issue.
Thanks
On Fri, Oct 6, 2017 at 4:42 PM Jesus Garcia<EMAIL_ADDRESS>wrote:

For best support, post issues in the RealSense Community
https://communities.intel.com/community/tech/realsense.
Hello,
Do you still need help with this issue?
Best regards,
Jesus
Intel Customer Support
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/428#issuecomment-334893854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvVvD8fjC2Wth6GHLJ2YiACIhD4Z9Xmks5sprrWgaJpZM4LzGFd
.

We're ok now.  Thanks


The Tenets of Good from champion dedication doesn't grant holy trait to the character or their strikes

The Tenets of Good feature from champion dedication doesn't grant holy trait to the character or their strikes

Not able to reproduce: please provide foundry and system versions. If you used an importer module, we won't be able to assist.


Missing License Information In Nuget metadata

Hi,
Could the license information be added to the nuget information?
it is good to add it so it will be shown in Visual Studio nuget management.
for example, Iuse the following ```MIT''' in my nugets:
<PropertyGroup>
	<PublishRepositoryUrl>true</PublishRepositoryUrl>
	<IncludeSymbols>true</IncludeSymbols>
	<SymbolPackageFormat>snupkg</SymbolPackageFormat>
	<ContinuousIntegrationBuild>true</ContinuousIntegrationBuild>
	<PackageLicenseExpression>MIT</PackageLicenseExpression>
	<RepositoryType>git</RepositoryType>
	<Nullable>enable</Nullable>
	<LangVersion>latest</LangVersion>
</PropertyGroup>

Great. thansk for the fast response.
btw I'm not sure both 	<PackageLicenseExpression>MIT</PackageLicenseExpression>  and the <PackageLicenseFile>LICENSE</PackageLicenseFile> are compatible together.. maybe the PackageLicenseFile is no longer needed?

Huh, yeah, you're right. I can just the remove the license file altogether.

Ignore my last edits :)

What do you mean? PackageLicenseFile really isn't needed if PackageLicenseExpression is present.

I  accidentally re-edit my orginal message. Yeah it is not needed if expression is used

I've just released version 5.0.0 which fixes this issue so it can be closed now.


view HoC is blocking react-router V4

I've been putting together an application and noticed this morning that when I have a component wrapped with view, it loses the ability to work with react router v4.
After some digging, it appears as though this bit of documentation explains what's happening.
I've been able to patch around this by wrapping my components using their withRouter HoC or wrapping the component in an empty <Route />, but apparently this is redundant and not optimal according to their documentation.  Is there any way this project can propagate whatever react router (and likely others) needs to continue functioning?

Hi!
This affects every library, which uses shouldComponentUpdate for performance optimizing (which means pretty much every state management library, including Redux and Mobx). The link you copied has everything you need to workaround this though. You should wrap blocked components with withRouter().
The issue should be fixed in react-router, they use the old context API and inherit the major flaw of it (why it was replaced). I think they will migrate to the new API and remove this mess in a later version, but until then you should use the withRouter workaround. It does not pose any practical problems or performance bottlenecks and it is the most widely used solution for having a state management library and React Router in the same project.
(P.S: I am soon releasing react-easy-stack with its own Router, which won't have this issue).

Awesome! Thanks for all the insights.
Will your router support nested and relative routes?  Anywhere I can read up more on it, especially in contrast to RRv4?

Yep, it will. You will have to wait a little bit more for the read up as I am still working on the docs. Sorry for being so secretive, but I don't want to leak it out unfinished.

Totally understand. Hopefully it'll be an easy transition from RRv4 if I like it! 😁


fix(48024) Scanner optimizations based on character frecuency

Fixes #48024
A peer-commit review is recommended:

b24034f: Merges shebang check with hash check.
59e0c4f: Make identifier check the first thing to execute.
f7e363e: Create a fast path for whitespace (32). Also, defer the other whitespace like character to the default block, since there was a call to isWhiteSpaceSingleLine there already and that cover all the removed character checks. Minor note, that function also checks for CharacterCodes.nextLine which wasn't checked before but after running all the test suite I found that nothing broke.
a790e00: Move digits check up.
f2b4439 & 29e8f74: Are just copying and pasting the checks in the order of occurrence.
0e07955 & ed5d47e: I tried to search every meaningful function that would check for either lowercase or uppercase letters and ensure that lowercases were checked first.

@typescript-bot perf test this faster

b24034f seems fine as code cleanup, but I don't really see any perf impact from the reordering changes?  Intuitively, this seems reasonable, since I believe only very small switches are evaluated as repeated equality checks.
Also, as a general rule, when making a subtle change to improve performance, I find it helpful to add an explanatory comment so someone doesn't inadvertently undo it in the future.

My feeling on this is that it's about equal thirds unobjectionable cleanup (patternMatcher.ts), speculative improvement (the simple reorderings), and then... risk (handleWhiteSpaceLike)? I really don't want unforeseen correctness breaks in trade for unmeasurable gains.
This should be in-principle measurable by parsing an enormous file (tsserver.js?) directly with the API and measuring the time taken. If the gain can't show up there then I don't think it exists.

@RyanCavanaugh the handleWhiteSpaceLike change (introduced in f7e363e) has the same semantic behaviour as before, perhaps should I rename it or add some comment to make it more clear?
@amcasey I can add a comment above the switch statement saying some like:
The order of the case statement is reliant upon character frequency, more common characters are checked first

Additionally, above the isWordChar function, I could add:
Since lowercase letters are more common than uppercase ones  they are checked first

We've tried super hard to measure any effect here and can't find any. Given nonzero risk associated with this, I'm going to decline the PR as a whole. I'd take 0e0795507170f9641ff5ea8bb1a48f7c5dd7c593 as a separate PR since it's the only thing I'd consider to be identifiable as both absolutely-assuredly-semantically identical while also being something we can say for sure the runtime can't plausible optimize on our behalf already.


Too many significant digits when suggesting next experiment

The front end tends to suggest new settings to a silly high number of significant digits (though only for parameters whose upper/lower limits involes a non-integer number?), like shown below:

An easy fix would be to round to three significant digits by default, or alternatively 1/1000th of the length of the dimension in question (so if your limits are 0 and 20, you round to the nearest 0.02).

Solved in API backend


Document request body contents sent to CRD conversion webhooks, in more detail

This is a Feature Request

What would you like to be added

We recently ran into a scenario where we saw the API Sever send partial/empty object to a conversion webhooks. The issue here is that our team took an invariate that the APIserver will first validate the an object that is created/updated first before it is sent to a CRD conversion webhooks. This turned out to not necessarily be true for server side apply where resource can be pruned and an object that is not valid will be sent to a conversion webhooks.
It would be helpful to document the order of operation the API server will use when converting CRDs between resources, and the requirements need for CRD conversion webhooks to work successful with API Server: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#webhook-conversion
Why is this needed
Users implementing conversion webhooks will need to understand the contract and expectation around the action the request object that will need to be sent by the API Server.
Comments

/wg api-expression

/sig api-machinery

/assign


VM needs new dependencies

Without these packages, the make command fails
xz
pcre-devel
complaint about PCRE not being present
tcl-devel
checking for Tcl configuration... configure: error: Can't find Tcl configuration, install the TCL dev package
libxml2-devel
configure: error: An XML parser (expat or libxml2) is required.

Also need libyaml-devel.
@cmc333333: If you pull down the latest from master and install that libyaml-devel dependency, I think it should hopefully fix the issues you were seeing earlier. Basically, the build error we were seeing was a bit of a red herring due to several odd issue, but it should be fixed by https://github.com/NREL/api-umbrella/commit/76807831d8685493c87f200f8dab920ad6e2973f

libuuid-devel too.

For future search, the error message around libuuid-devel was
0151015T205502.118841: 2015/10/15 20:55:01 [error] 8197#0: init_worker_by_lua_file error: ...vagrant/api-umbrella/vendor/share/lua/5.1/resty/uuid.lua:29: libuuid.so: cannot open shared object file: No such file or directory

Ran through this from a fresh vagrant image. Dependencies as a checkbox list

[ ] xz
[ ] libyaml-devel
[ ] tcl-devel
[ ] libxml2-devel

All of these should be part of the vagrant setup now.


1 use create ap on dan

@stephanieder can you merge after the end of realease 19Q4R01 validation

ok


CLOUDP-213013 Spike docker compose

⚠ DO NOT MERGE ⚠

Proposed changes
Spike on replacing podman with docker compose

Jira ticket: CLOUDP-213013

https://github.com/mongodb/mongodb-atlas-cli/assets/1765216/32c1bc7e-22d7-4752-9923-e15d68777dee
Checklist

[ ] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[ ] I have run make fmt and formatted my code

Further comments

To try you can basically download the binary for your platform in:

linux x86_64 (deb, rpm, tar)
linux arm64 (deb, rpm, tar)
mac (arm64, x86_64)
windows (exe, msi)

Notes: the code is not finished there will be bugs


Updated PR implementing requested changes from #2197

This PR is an update to an older open PR, https://github.com/huginn/huginn/pull/2197, that has had no activity since January. It implements a minor change as requested by @dsander.

@dsander Sorry, I know this is a very old PR at this point, but I'm still left wondering what the current default behavior is.
I'm still not any more familiar with Ruby than I was two year ago, so I'm hoping you will explain the behavior created in the statement below.
https://github.com/huginn/huginn/blob/413b54c685910209f956026cbfdfb037cdfd7e49/app/models/agents/twitter_stream_agent.rb#L225-L226

@zoomequipd That code returns (exits) the method if data inside status["retweeted_status"] is "something" and if it an instance of the class Hash. Which means that no Events are emitted for tweets that are retweets.


Get hmac.c(116): OpenSSL internal error, assertion failed: j <= (int)sizeof(ctx->key)

tdlib 1.6.0
openssl 1.1.1g
golang 1.14.7
https://github.com/zelenin/go-tdlib 0.2.0
Some strange things appear. I build small example from go-tdlib and it just works, but as soon I try to incude the same peace of code into my primary app - this error occur.
[14][t 3][1601424885.389991999][Scheduler.h:155][!MultiTd][&actor]      MultiTd:0x2c7bac0:0x2c6eed0 Event::Custom
[14][t 3][1601424885.390005827][ActorInfo.h:172][!MultiTd][&actor]      Start run actor: Td:0x7fdc500017f0:0x7fdc500018f0
[ 3][t 3][1601424885.390019655][Td.cpp:3592][#1][!Td][&td_requests]     Receive request 3: getAuthorizationState {
}
[ 3][t 3][1601424885.390041590][Td.cpp:4722][#1][!Td][&td_requests]     Sending result for request 3: authorizationStateWaitEncryptionKey {
  is_encrypted = false
}
[14][t 3][1601424885.390068293][ActorInfo.h:178][#1][!Td][&actor]       Stop run actor: Td:0x7fdc500017f0:0x7fdc500018f0
[14][t 3][1601424885.390082359][ActorInfo.h:178][!MultiTd][&actor]      Stop run actor: MultiTd:0x2c7bac0:0x2c6eed0
[14][t 3][1601424885.390095711][Scheduler.cpp:352][!ServiceActor][&actor]       Add to mailbox: ServiceActor:0x2c6ef20:0x2c6eed0 [Event:3]
[14][t 3][1601424885.390108347][ActorInfo.h:178][!ServiceActor][&actor] Stop run actor: ServiceActor:0x2c6ef20:0x2c6eed0
[14][t 3][1601424885.390120745][Scheduler.cpp:463][&actor]      Run mailbox : finish 4
[14][t 3][1601424885.390132666][Scheduler.cpp:454][&actor]      Run mailbox : begin
[14][t 3][1601424885.390144348][ActorInfo.h:172][&actor]        Start run actor: ServiceActor:0x2c6ef20:0x2c6eed0
[14][t 3][1601424885.390156746][Scheduler.cpp:268][!ServiceActor][&actor]       ServiceActor:0x2c6ef20:0x2c6eed0 Event::Yield
[14][t 3][1601424885.390170097][ActorInfo.h:178][!ServiceActor][&actor] Stop run actor: ServiceActor:0x2c6ef20:0x2c6eed0
[14][t 3][1601424885.390187502][Scheduler.cpp:463][&actor]      Run mailbox : finish 4
[14][t 3][1601424885.390200615][Scheduler.h:352][&actor]        Run events 0 [pending:0][actors:4]
[14][t 3][1601424885.390213490][Scheduler.cpp:454][&actor]      Run mailbox : begin
[14][t 3][1601424885.390225649][Scheduler.cpp:463][&actor]      Run mailbox : finish 4
[ 3][t 0][1601424885.390545607][Client.cpp:276][&td_requests]   End to wait for updates, returning object 3 0x2c84610
[ 3][t 0][1601424885.390755415][Client.cpp:270][&td_requests]   Begin to wait for updates with timeout 60.000000
[14][t 0][1601424885.391037941][Scheduler.cpp:336][&actor]      Send to MultiTd:0x2c7bac0:0x2c6eed0 on scheduler 0: [Event:7]
[13][t 3][1601424885.391081095][PollableFd.h:133][&fd]  [fd:7] add flags from poll [R]
[13][t 3][1601424885.391183615][PollableFd.h:168][&fd]  [fd:7] notify [observer:0x2c6edb0]
[14][t 3][1601424885.391279697][Scheduler.cpp:352][&actor]      Add to mailbox: ServiceActor:0x2c6ef20:0x2c6eed0 [Event:3]
[14][t 3][1601424885.391293526][Scheduler.h:352][&actor]        Run events 0 [pending:0][actors:4]
[14][t 3][1601424885.391299725][Scheduler.cpp:454][&actor]      Run mailbox : begin
[14][t 3][1601424885.391309261][ActorInfo.h:172][&actor]        Start run actor: ServiceActor:0x2c6ef20:0x2c6eed0
[14][t 3][1601424885.391317606][Scheduler.cpp:268][!ServiceActor][&actor]       ServiceActor:0x2c6ef20:0x2c6eed0 Event::Yield
[14][t 3][1601424885.391323328][Scheduler.cpp:83][!ServiceActor][&actor]        Receive [Event:7]
[14][t 3][1601424885.391328096][ActorInfo.h:172][!ServiceActor][&actor] Start run actor: MultiTd:0x2c7bac0:0x2c6eed0
[14][t 3][1601424885.391332626][Scheduler.h:155][!MultiTd][&actor]      MultiTd:0x2c7bac0:0x2c6eed0 Event::Custom
[14][t 3][1601424885.391338825][ActorInfo.h:172][!MultiTd][&actor]      Start run actor: Td:0x7fdc500017f0:0x7fdc500018f0
[ 3][t 3][1601424885.391344786][Td.cpp:3592][#1][!Td][&td_requests]     Receive request 4: checkDatabaseEncryptionKey {
  encryption_key = bytes [0] { }
}
[ 7][t 3][1601424885.391387701][Td.cpp:4313][#1][!Td][&td_init] Begin to init database
[ 7][t 3][1601424885.391401291][TdDb.cpp:390][#1][!Td][&td_init]        Start binlog loading
[13][t 3][1601424885.391434431][NativeFd.cpp:114][#1][!Td][&fd] [fd:18] create
[13][t 3][1601424885.391441822][FileFd.cpp:374][#1][!Td][&fd]   Trying to lock file "/home/usertelegram/database/td.binlog"
[13][t 3][1601424885.391448021][FileFd.cpp:346][#1][!Td][&fd]   Lock file "/home/usertelegram/database/td.binlog"
[13][t 3][1601424885.391500950][NativeFd.cpp:114][#1][!Td][&fd] [fd:19] create
[13][t 3][1601424885.391509056][FileFd.cpp:374][#1][!Td][&fd]   Trying to lock file "/home/usertelegram/database/td.binlog.new"
[13][t 3][1601424885.391515017][FileFd.cpp:346][#1][!Td][&fd]   Lock file "/home/usertelegram/database/td.binlog.new"
hmac.c(116): OpenSSL internal error, assertion failed: j <= (int)sizeof(ctx->key)

These lines make me wonder about the real reasons of openssl misbehaviour.
is_encrypted = false
encryption_key = bytes [0] { }

Any tips are very appreciate.

Check that your app depends only on one OpenSSL library and doesn't try to link in two different incompatible versions of the OpenSSL.

Yep, I saw other related issues and already checked linked libraries.
        linux-vdso.so.1 (0x00007ffd0eb98000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1d1a5f1000)
        libtdclient.so.1.6.0 => /usr/lib64/libtdclient.so.1.6.0 (0x00007f1d1972f000)
        libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/libstdc++.so.6 (0x00007f1d194b8000)
        libssl.so.1.1 => /usr/lib64/libssl.so.1.1 (0x00007f1d19423000)
        libcrypto.so.1.1 => /usr/lib64/libcrypto.so.1.1 (0x00007f1d19144000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f1d1913e000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f1d1911f000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f1d18fd5000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f1d18fcb000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f1d18de8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f1d1a657000)
        libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.3.0/libgcc_s.so.1 (0x00007f1d18dce000)

openssl version
OpenSSL 1.1.1g  21 Apr 2020

Even more, I don't have any openssl-compat (or any other openssl versions) binaries on my system either.
@levlam Any thoughts ?

Update. It seems I've found the real problem.
I use https://github.com/confluentinc/confluent-kafka-go that has prebuilt librdkafka libraries inside. After I disable it - openssl error gone.

@livelace Then librdkafka is likely to statically link a different OpenSSL version.

Yep, true story. I just build my application with "-tags dynamic" and use librdkafka from my host.
It's less portable, but works.


Enhance default spaces

This PR updates the Default Spaces section on the Create page;
it adds an environment to the existing default space
and adds two new default spaces to choose from:
a space-themed one
and an island-themed one
To test:
on the Create page, make sure that all three default space options are displayed correctly (incl. the preview)
ensure that each default space can be created
each created space should load as expected
other functionality should not be affected

Ready for review (after VR menu fix)
Changes are deployed on the mainnet

Tested on alexStaging approving

Tested on alexStaging looks good


Socket timeout

Codecov Report

Merging #337 into master will decrease coverage by 0.68%.
The diff coverage is 43.47%.

@@             Coverage Diff              @@
##             master     #337      +/-   ##
============================================
- Coverage     83.73%   83.05%   -0.69%
+ Complexity      443      442       -1
============================================
  Files            62       64       +2
  Lines          1402     1416      +14
  Branches        190      194       +4
============================================
+ Hits           1174     1176       +2
- Misses          124      133       +9
- Partials        104      107       +3


vendor/autoload.php not found

PHP Warning:  require(/vendor/autoload.php): failed to open stream: No such file or directory in /artisan on line 18

Did you do composer install after cloning this repository?
Then the vendor directory should exist
After that ... check if /vendor/autoload.php exists

Becarefull about the php version. Because current this project using php version 7, if you are using 8. After clone you need to delete composer.lock file and composer install again.


Missing input elements from Form event in Submit handler

Describe the bug
Testing a component that contains a form with Vitest and React Testing Library in a Next project leads to a submit event that doesn't contain the input elements that are part of the form itself.
Reproduction
I recreated the issue with a minimal example here
If you try to interact with the form from the ui preview you should see the input field content be printed to the console.
If you try to run npm run test you'll see an error because event.currentTarget doesn't contain an element called "field".
System Info
System:
  OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
  CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1265U
  Memory: 5.91 GB / 7.58 GB
  Container: Yes
  Shell: 5.2.15 - /bin/bash
Binaries:
  Node: 22.1.0 - /usr/local/bin/node
  npm: 10.7.0 - /usr/local/bin/npm
  pnpm: 9.1.0 - /usr/local/bin/pnpm
npmPackages:
  @vitejs/plugin-react: ^4.2.1 => 4.2.1
  vitest: ^1.6.0 => 1.6.0

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This looks like a jsdom issue since it works on happy-dom. You would probably need to report it there to see if this is supported.
https://stackblitz.com/edit/stackblitz-starters-mzb5tx?file=components%2Fhappy-dom.test.tsx
stdout | components/jsdom.test.tsx > repro jsdom
[handleSubmit] field.value =  undefined

stdout | components/happy-dom.test.tsx > repro happy-dom
[handleSubmit] field.value =  abc123

Link to the happy-dom issue: https://github.com/jsdom/jsdom/issues/3715
Closing this as I don't see any reason to keep this open in Vitest.


Carina args

Have a CARINA_USERNAME and CARINA_APIKEY why dontcha?

Addresses #35, thanks for the suggestion in the tutorial @annegentle.

Backwards compat in action, complete with warnings that don't affect sourcing creds directly:
$ eval "$( carina credentials wat )"
Warning: use of RACKSPACE_USERNAME and RACKSPACE_APIKEY environment variables is deprecated.
Please use CARINA_USERNAME and CARINA_APIKEY instead.


Check for 'libsystemd >= 209' when checking the availability of sd-journal APIs

When checking if we have the development files for libsystemd's journal APIs, check for 'libsystemd >= 209' rather than 'libsystemd-journal'.  Starting with that version, libsystemd-journal was merged into
libsystemd, and the .pc file is no longer packaged in newer Debian and Ubuntu.
I think this will fix what we're seeing in https://github.com/docker/docker/pull/13707#issuecomment-182709361, but I'm admittedly still waiting for my build box to finish up to be sure.

Job: Docker-PRs-WoW-TP4 FAILED:

---
	      56	docker-1.11.0-dev.exe.md5
  0%
100%
	    New File  		      88	docker-1.11.0-dev.exe.sha256
  0%
100%
	    New File  		  27.1 m	docker.exe
  0.0%
  3.6%
  7.3%
 11.0%
 14.7%
 18.3%
 22.0%
 25.7%
 29.4%
 33.1%
 36.7%
 40.4%
 44.1%
 47.8%
 51.5%
 55.1%
 58.8%
 62.5%
 66.2%
 69.8%
 73.5%
 77.2%
 80.9%
 84.6%
 88.2%
 91.9%
 95.6%
 99.3%
100%

------------------------------------------------------------------------------

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :         1         0         1         0         0         0
   Files :         4         4         0         0         0         0
   Bytes :   54.36 m   54.36 m         0         0         0         0
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00

   Speed :<PHONE_NUMBER> Bytes/sec.
   Speed :            67955.636 MegaBytes/min.
   Ended : Wednesday, February 17, 2016 9:55:19 PM

+ ec=0
+ set +x
INFO: Linking the built binary to /d/CI/CI-d1
---

Won't this break on the older platforms where libsystemd-journal is currently working?

(wheezy, trusty, etc)

Won't this break on the older platforms where libsystemd-journal is currently working?

indeed.

On jessie, pkg-config finds the same results for both libsystemd and libsystemd-journal.
Precise has neither.
On trusty and wheezy we find libsystemd-journal, but not libsystemd.
And on stretch and wily we find libsystemd, but not libsystemd-journal.
I'm really not liking the OS-level packaging of these, but this isn't going work around all of it.


Website suggestion - instance status checker

I think it would be nice if there was a way to check if an e4mc instance is active. When I want to see if I can hop on minecraft late at night, in the past I would just use nmap to check if my friend's IPs were open to port 25565. But now that they have switched to using e4mc, it seems that there is no way to do that without booting up minecraft just to check. So if you could add a little page that lets you type in an address to check if it's online, that would be really nice!

https://status.e4mc.link/
Idk if this is exactly what you meant but this exists

No, I mean to check if an individual instance is up. Like, say 5 hours ago my friend started a server uncle-sense.us.e4mc.link, a way to check that Uncle Sense is still alive without starting up Minecraft and trying to connect.


[NEW ALGORITHM] BASIC PROGRAMMING FOR BEGINNERS WHICH HELPS TO UNDERSTAND ABOUT C LANGUAGE

Description:
Basic topics for beginners
Checklist:

[ X] Contributor in GSSoC-ext
[ ] Want to work on it

Additional Information:
Provide any other relevant information or resources regarding the algorithm.

@pankaj-bind Please assign me this issue.

@pankaj-bind Hi! I’d love to contribute to this issue by providing clear and beginner-friendly C programming concepts and examples. Please assign this task to me, and I'll ensure it's done effectively!


Tensorflow GPU setup issue on Ryzen 5 + 2080 RTX GPU + Ubuntu 18.04

Hi Team,
I am trying to setup tensorflow-gpu on my new machine with configuration AMD Ryzen 5 2600 + 2080 RTX GPU + Ubuntu 18.04. I have tried tensorflow-gpu docker, tensorflow build from source.
In docker image, it was exiting after first epoch without any error.
And in other approach we are getting following errors:
ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory.
InvalidArgumentError (see above for traceback): Cannot assign a device for operation MatMul: Operation was explicitly assigned to /device:GPU:0 but available devices are [ /job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_CPU:0, /job:localhost/replica:0/task:0/device:XLA_GPU:0 ]. Make sure the device specification refers to a valid device.
[[node MatMul (defined at test.py:6)  = MatMul[T=DT_FLOAT, transpose_a=false, transpose_b=false, _device="/device:GPU:0"](a, b)]]
Please assist with right steps to setup tensorflow gpu on Ryzen 5 + 2080 RTX GPU + Ubuntu 18.04 machine. Quick response will be really appreciated.
Regards,
Ankit Aggarwal

It looks like you haven't used a template to create this issue. Please resubmit your issue using a template from here. We ask users to use the template because it reduces overall time to resolve a new issue by avoiding extra communication to get to the root of the issue. We will close this issue in lieu of the new one you will create from the template. Thank you for your cooperation.


AAD Authentication is blocked

Describe the bug
Accessing an endpoint implementing AAD authentication is not possible from within the TRE as *.msftauth.net is not allowed in the firewall
Steps to reproduce

Open a browser from within a workspace VM and try to access a URL implementing AAD authN. Note that the target URL should be allowed from within the TRE (workspace firewall rules)
See the error about some msftauth.net not being reachable

Ah, aadcdn.msftauth.net is specified in the AML workspace service. What service are you trying to access?
Either we move all these AAD rules up to the workspace, or add that rule to the Guacamole workspace service/workspace service you are trying to access.

SQL Server with AAD AuthN.
I'm guessing that the AzureActiveDirectory service tag doesn't include all the things that are required for interactive user AuthN.
Isn't it reasonable to support interactive AAD auth across all the TRE and have it opened from the get go?

On the second point, it is probably cleaner to be workspace or service specific, we do come across use cases where from within the VM ZERO internet access should be allowed.
I've got a similar issue now with an ADFS URL required for login. It might make sense for this one to be added to the custom(er) workspace template.
It would be nice to have a way to set default firewall rules - like AAD, ADFS, any other set of rules across the TRE. Actually can we now do this using a shared service API? @damoodamoo?
That might be a better option, post firewall deploy add a set of default rules using the API.


Update test stepts to only install required packages dependencies

Changed

Updated  test stepts to only install required packages dependencies.

Codecov Report

Merging #274 (304b204) into master (94582e6) will increase coverage by 4.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #274      +/-   ##
==========================================
+ Coverage   94.46%   98.53%   +4.07%
==========================================
  Files          90       68      -22
  Lines        1065      887     -178
  Branches      143      109      -34
==========================================
- Hits         1006      874     -132
+ Misses         55       13      -42
+ Partials        4        0       -4

Flag
Coverage Δ

iocuak
98.52% <100.00%> (+0.51%)
:arrow_up:

iocuak-common
?

iocuak-decorators
?

iocuak-models
?

iocuak-reflect-metadata-utils
?

porygon
98.30% <ø> (ø)

porygon-typeorm
98.67% <ø> (ø)

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

Impacted Files
Coverage Δ

.../services/api/ContainerServiceApiImplementation.ts
100.00% <ø> (ø)

...a/services/api/MetadataServiceApiImplementation.ts
100.00% <ø> (ø)

...ing/models/api/bindingScopeToBindingScopeApiMap.ts
100.00% <100.00%> (ø)

...rc/binding/utils/api/convertBindingToBindingApi.ts
100.00% <100.00%> (ø)

...-decorators/src/classMetadata/decorators/inject.ts

...src/classMetadata/utils/getDefaultClassMetadata.ts

...ls/src/reflectMetadata/utils/getReflectMetadata.ts

...ls/src/reflectMetadata/models/bindingReflectKey.ts

...models/src/classMetadata/utils/getClassMetadata.ts

...es/iocuak-models/src/binding/models/BindingType.ts

... and 13 more

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