[Code app]: Disable Name and Version fields for edit when app is in deployed state

Description
Steps:

create code app and save it
deploy code app
open Edit form for code app

Actual result: Name and Version are available for edit
Expected: Disable Name and Version fields for edit when app is in deployed state
Use case/motivation
No response
Related issues
No response
Confidential information

[X] I confirm that do not share any confidential information

verified on staging
related issue created #2693


UX flow with initial stacker build failures and rollbacks

Feedback welcome - this is an open discussion item
I wanted to start a conversation regarding this: In stacker, when I run a stacker build on an initial deployment of a brand new stack that happens to fail, the stack itself goes into a ROLLBACK_IN_PROGRESS status eventually ending up in a ROLLBACK_COMPLETE state with no way to run build again.  This is the expected behavior with stacker as it matches cloudformation.
However for a user who is an AWS novice, getting out of this state with stacker... is a different experience than someone uploading templates in the CFN console directly.
I have had several conversations with our in-house development team about their use of Stacker around their user experience they have had with it since a lot of them are using it now for the first time. If a developer with no AWS or CFN experience were to run into this problem, stacker actually appears to hinder their progress moreso vs CFN natively. Let me explain why by going over both flows:
CFN console native UX workflow
In the AWS console, if I were to incorrectly create a template that fails, I get stuck in a ROLLBACK_IN_PROGRESS, followed by a ROLLBACK_COMPLETE state that is unrecoverable. I can then look at the template itself to figure out the problem or the AWS console to determine what needs to be fixed. After resolution and when I got to resubmit, the UI doesn't allow me to perform the "update stack" operations, instead only allows you to select "delete stack", thus walking you through their intended flow of deleting the stack first.
In this flow (although not perfect), a user is pretty much told... you must delete this stack before you can try again. It's the only option, so it's natural for a user to chose it.
Stacker UX workflow
In stacker, when I do a stacker build of that same mistake CFN deployment (via a similar mistake in the blueprint let's say), I get told that the stack is in a ROLLBACK_IN_PROGRESS state, but nothing else.  I can then look at the template itself to figure out the problem, or the AWS console, just like with CFN natively.  When I go to resubmit via stacker build, I get told an unfriendly  An error occurred (ValidationError) when calling the CreateChangeSet operation exception due to the stack being actually in a "ROLLBACK_COMPLETE" state and I have to figure out what is going on and how to fix it.
These are very different experiences.
UX flow issues with stacker
So, I have two issues I can see with the stacker the above workflow:

The user is never told the actual state the stack eventually ends up in. They are shown that a rollback is in progress, but not that they have to do something above and beyond fixing their template due to it actually being in a rollback complete state.

On the next build, the user is sent on a red herring trip to search google for whatever CreateChangeSet operation means.

Both of these result in a bad first experience by a novice user.
Thoughts?

Some ideas thrown around by @troyready and I at Sturdy:

Upload a simple template that will always succeed first before submitting the stack, so the rollback has somewhere to go and allows a update stack operation. Kind of like what serverless does. (They submit a template first to create an S3 bucket, then perform an update against the stack.)

Catch the exception, go interactive, and offer to delete the stack?  I haven't checked the source code, but perhaps only if we know it's a new stack that will end up in that ROLLBACK_COMPLETE state.

Catch the exception, then simply tell a user that the stack might need to manually be deleted due to CFN limitations with some possible AWS CLI command examples.

Related to issue #8

Thanks @GarisonLotus @troyready  - this is definitely a pain point.  Having stacker behave intelligently when a stack goes into a "bad state" is something I'd love to do, but it does introduce some complexity (not that I'm opposed).  Let me think about this some more - but all of your suggestions sound better than our current state.

Is it possible to detect if a stack has failed when running it's initial setup? It's a pretty annoying case that I run into pretty often. I make some mistake in the initial version of the stack, but I have to manually delete it in the console just to re-run stacker after a fix. Since there should be no resources left at all (since they didn't exist before the first run), it should be safe to forcefully re-create the stack.

@danielkza - unfortunately, AWS doesn't give us many options here.  If your initial stack fails, the only option you have, is to delete it... even in the console.  Yes it's annoying, and that's what this issue is asking to fix.
A bunch of developers I work with have chosen Serverless Framework when they had the option, over stacker, because of this issue... so I understand. (Serverless got around this in an interesting way. I'm not sold on their method for stacker however.  Seems wasteful.)

Could we tag the stack with a marker indicating it is the first time it is being run, and delete it automatically if it fails and has the marker?

I think it'd be best to have that be a query to the user to delete it, but yeah I agree that automating it would be good.

Maybe we could overload --force to allow deleting a stacked that failed its initial run.

Fixed in #473


Add support of PING for Pub/Sub

Add support of PING for pub/sub channels
https://github.com/antirez/redis/commit/70e39481ab1a7e43fefec67c31b4fe496cd10723
Discussion about this Redis feature: https://github.com/antirez/redis/issues/420

Done


Rename javalin-cookie-store

When I use ctx.cookieStore. The browser will store a cookie name "javalin-cookie-store". Can I rename it to something else?

I don't remember, but feel free to create a PR to add this functionality :)


Support for various text-based encodings for python and other languages?

Observation
Looking at the implementation of the Python library, I see that only JSON encoding is supported -- and used to generate request signature.
Question
The project's aim is to standardise webhooks across many languages. My question is, are you planning to add support for other text-based encodings such XML, CSV, TSV, YAML, etc., for Python and other languages?

That's a good point, and I think the libraries are indeed too Json centric at the moment. We probably need to add hooks to allow for other deserialization types, or maybe make it completely agnostic to the deserialization in general.


preheat timeout

Bug report:

harbor  p2p preheat  erorr log :
2021-11-29T07:57:45Z [INFO] [/pkg/p2p/preheat/job.go:120]: Get preheat provider driver: dragonfly
2021-11-29T07:57:45Z [INFO] [/pkg/p2p/preheat/job.go:134]: Check health of preheat provider instance: Healthy
2021-11-29T07:57:45Z [INFO] [/pkg/p2p/preheat/job.go:146]: Sending preheat request is successfully done
2021-11-29T07:57:45Z [INFO] [/pkg/p2p/preheat/job.go:170]: Start to loop check the preheating status until it's success or timeout(30m)
2021-11-29T07:57:55Z [INFO] [/pkg/p2p/preheat/job.go:186]: Check preheat progress: Task [40] is , start time=2021-11-29 07:57:45 +0000 UTC
2021-11-29T07:58:05Z [INFO] [/pkg/p2p/preheat/job.go:186]: Check preheat progress: Task [40] is , start time=2021-11-29 07:57:45 +0000 UTC
until  [timeout]
Expected behavior:

How to reproduce it:

Environment:

Dragonfly version:

NAME     	NAMESPACE       	REVISION	UPDATED                                	STATUS  	CHART           	APP VERSION
dragonfly	dragonfly-system	1       	2021-11-29 15:42:05.878012048 +0800 CST	deployed	dragonfly-0.5.21	0.5.21

OS:
CentOS Linux release 7.9.2009 (Core)
Kernel (e.g. uname -a):
Linux  5.4.54-1.0.0.std7c.el7.2.x86_64 #1 SMP Mon Nov 16 10:02:20 CST 2020 x86_64 x86_64 x86_64 GNU/Linux
Others:

cnd.log
manager.log
scheduler.log


allowCommandsAtEnd setting is purely cosmetic with no use

Describe the bug
I couldn't git blame the creator of this issue properly, but whoever made this, must've lost implementation of this setting in code and made this setting do literally nothing.
I could fix this myself, but I am not really sure how should this work in the first place, so I am creating this issue to discuss it.
Screenshots
https://cdn.zneix.eu/y4YYsaf.png

Chatterino version
current master branch 2f5df3db
Operating system
linux-5.10.2.arch1-1

Yeah, seems like toggling that checkbox does nothing. can confirm on windows 10 and age-old commit 529f19a2d
I think it's in there forever, but I never used it. Maybe deleting it might also be a valid option?

Cosmetic checkbox . Is there any consensus on if we're removing it or adding the functionality?

Cosmetic checkbox . Is there any consensus on if we're removing it or adding the functionality?

Guess we/I should look into how easy it actually is to add such thing and either make it do anything or just purge entirely since it does... JUST nothing

This would be a pretty useful ability, particularly given the format/nature of Twitch comments. @zneix Are you still working on this?

If the functionality implementing this setting were to be added, it would need to somehow fit in with command placeholders. Currently a placeholder such as {1} matches the first word after the command trigger, but if the trigger can also be matched at the end it makes no sense to match words after the last word.
One possible way of dealing with this is completely ignoring placeholders in commands that matched at the end, which would need explanation in the wiki entry, but we could also avoid this by deciding to remove the setting.

One possible way of dealing with this is completely ignoring placeholders in commands that matched at the end, which would need explanation in the wiki entry, but we could also avoid this by deciding to remove the setting.

This is a good idea, since when at the end, it's most likely not for expanding upon parameters. My personal use is to auto-expand certain username handles which don't always get picked up by the recent-users popup (since it only populates with usernames that have spoken in chat recently).
I suppose if there was a need it could be made to work by indexing the words in the message starting from the command itself being 0, words preceding the command indexing negative, words following the command indexing positive; if the command is EOL, the index is taken as an absolute value, so
/rule --> "Rules: {1+}"
User1: /rule paper eats rock --> "Rules: paper eats rock"
User2: paper eats rock /rule --> "Rules: rock eats paper"
Not sure of a use case for that, but I'm also not a moderator. Another option is just having the {1+} loop back around to the start of the message, printing the rest of the words as if the command was at the beginning of the message to begin with.
But simplest and likely best logic is your idea to just disregard parameters if the command is EOL.

User2: paper eats rock /rule --> "Rules: rock eats paper"

I think this is unneeded. At least for specific option of also match the trigger at the end of the message. If this functionality is wanted I think it'd be better suited to either have another option or to replace the trigger at the end with also match the trigger at the end of the message in reverse. Like you say, I can't find an actual use case for having placeholders read and printed in reverse.
Is there something in particular stopping us from continuing as is and simply checking if there is a command at the end or not?
For example,
Command Trigger: /testend
Command Function: {1+} | END.
Test: this is the /testend
Output: this is the | END.
Test: /testend this is the
Output: /testend this is the Of course there will be an unrecognized command message displayed instead because / will still be sent and therefore thought of another command


Pluck报Error 1064 (42000): You have an error in your SQL syntax错误

Your Question
type Print struct {
	gorm.Model
	OwnerID   uint    `gorm:"not null;index"`
	OwnerType string  `gorm:"type:varchar(32);not null;index"`
}

printIDs := make([]uint, 0)

if e := db.Model(&Print{}).Where(
	"owner_type = ? AND owner_id IN ?", "cart_products", ids,
).Pluck("id", &printIDs).Error; e != nil {
	return e
}
// Error 1064 (42000): You have an error in your SQL syntax;
// check the manual that corresponds to your MySQL server version
// for the right syntax to use near '?)

换成 map 条件则不再报错：
if e := db.Model(&Print{}).Where(
	// "owner_type = ? AND owner_id IN ?", "cart_products", ids,
        map[string]any{"owner_type": "cart_products", "owner_id": ids},
).Pluck("id", &printIDs).Error; e != nil {
	return e
}

看来问题出在字符串中的❓。

When you use IN  you should provide a slice as a parameter and the IN keyword should be within the parentheses something like this.
err := db.Model(&Print{}).
    Where("owner_type = ? AND owner_id IN (?)", "cart_products", ids).
    Pluck("id", &printIDs).Error

When you use IN you should provide a slice as a parameter and the IN keyword should be within the parentheses something like this.
err := db.Model(&Print{}).
    Where("owner_type = ? AND owner_id IN (?)", "cart_products", ids).
    Pluck("id", &printIDs).Error

不对吧？
文档中没有括号的写法，你这个括号的写法是哪里来的，其他地方我也是根据文档中不带括号的写法来写的，也没有报错。
// IN
db.Where("name IN ?", []string{"jinzhu", "jinzhu 2"}).Find(&users)
// SELECT * FROM users WHERE name IN ('jinzhu','jinzhu 2');

Here is the playground link https://github.com/go-gorm/playground/pull/622, I have added both cases. Please have a look and try to change the way it gives errors, so we can understand the issue.


AnalyzerCommand: Add option to to provide multiple curation files

Resolves #4128.

Added documentation.

I'll also add this option to the evaluator in an upcoming PR.


Warn me when files whith a given hash are found

I want to be sure that no private key is leaked into any of our repositories.
I don't want to provide Gitrob the private key itself, but only its (e.g. SHA256) hash and let Gitrob check that no file has that hash.
Maybe, I should provide Gitrob also the file size, to check the hash only if the filesize matches. I want to avoid Gitrob computing hashes for each file if it is not necessary (e.g. a directory full of big JPG files). Relaying in the filename and/or extension may not be accurate.
Maybe, I can provide a list of sensitive hashes (with hashing algorithm? with size?) in the ~/.gitrobrc file.

I'm not a gitrob maintainer, but wanted to contribute a couple of comments about:

be sure that no private key is leaked

If you want to make sure that no private key is leaked, then do the hashes matter at all? It seems like a hash would be useful for preventing specific keys from being leaked, but not to stop any private key from being leaked.
Even if you had a set of hashes for every single private key used by the organization or any member of the organization, it still wouldn't be foolproof because it wouldn't detect:

Keys that have been converted to a different format (e.g. see Converting Using OpenSSL)
Keys that have been insignificantly modified (e.g. apparently leading and trailing whitespace is ignored)
Keys embedded within other files (e.g. stored in a json "data bag" for use with chef's certificate cookbook, especially if the data bag is not encrypted)

I think it might be better to search for:

Filenames associated with private keys (e.g. *.pem)
Content in configuration files (*.yaml, *.json, *.rb, etc) matching a private key signature (e.g. "-----BEGIN RSA PRIVATE KEY-----")

+1 to @maxlinc


Add ol-touch but keep ol-viewport className.

Currently when displaying a map on a touch device the ol-touch className is added to the viewport. Well this className actually replaces ol-viewport.
In my application I rely on ol-viewport to add styling behavior to element within the viewport and I don't want to add specific css selectors for touch devices.
With this pull request ol-touch is effectively added instead of replacing the existing one.
I've tested manually some examples and haven't seen any weird behavior.
Please review.

LGTM

Looks good to me too.


Cannot build with  GCC 10.1 on Centos 7

Describe your problem
Caused by https://github.com/microsoft/cpprestsdk/issues/1461
Additional context
Add any other context about the problem here.

/cc @lidongze0629


LineDotsLoader

Element type is invalid: expected a string or a class but got : undefined error.
Thanks for this great component though!

@AlisonWonderlandApps Hi, I'm so sorry. That's my fault. I forgot to add this loader into the index.js. I have updated -v0.6.6, you can update it and try again~


Marker Info Window calling onOpen on the draw cycle

Issue Type
[ ] Bug
Description and/or steps/code to reproduce the problem
i think the issue is that we had to muck around with the mark info window rendering (when it's open). I think the current logic will trigger onOpen on every draw cycle if the window is open. I'll open an issue over there to track this
Version of osmdroid the issue relates to:
6.0.1

https://github.com/MKergall/osmbonuspack/issues/320


Skip inconsistent test

Hello!

Summary of PR:
Tagging Doctest has ~1.8% chance to fail, despite working correctly. This PR skips this test.

I was checking out PR #2597, and noticed the tests were failing for it, even though the tests passed when I proposed the changes.
The corresponding Travis CI logs state that it only failed for Python 3.5, while the other four test versions worked. So I dug deeper and found the single test that had failed:
1) FAIL: Doctest: nltk.tag
----------------------------------------------------------------------
   Traceback (most recent call last):
    /opt/python/3.5.6/lib/python3.5/doctest.py line 2190 in runTest
      raise self.failureException(self.format_failure(new.getvalue()))
   AssertionError: Failed doctest test for nltk.tag
     File "/home/travis/build/nltk/nltk/nltk/tag/__init__.py", line 8, in tag

   ----------------------------------------------------------------------
   File "/home/travis/build/nltk/nltk/nltk/tag/__init__.py", line 61, in nltk.tag
   Failed example:
       tagger.evaluate(brown.tagged_sents(categories='news')[500:600])
   Expected:
       0.73...
   Got:
       0.7406290392072382

Naturally I expected this to be because of the pushed changes, but I was unable to reproduce this error.
I dusted off my old Python 3.5 install and dug into the code. The doctest that failed can be found here:
https://github.com/nltk/nltk/blob/54221dec0bae2642d1642d182d8a381c88b86bd0/nltk/tag/__init__.py#L42-L62
The program I used to replicate this doctest is as follows:
from nltk.corpus import brown
from nltk.tag import UnigramTagger

tagger = UnigramTagger(brown.tagged_sents(categories='news')[:500])
out = tagger.evaluate(brown.tagged_sents(categories='news')[500:600])

print(out)

And some sample outputs when running this on Python 3.5:
0.7393364928909952
0.7345971563981043
0.7350280051701853
0.7337354588539423
0.7345971563981043
0.7341663076260233
0.7350280051701853
0.7389056441189142
0.7393364928909952
0.7380439465747523
...

Note: Inconsistent results.
And when running this on Python 3.6 (there are similar results on Python 3.7 and 3.8):
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
0.7345971563981043
...

Note: Consistent results.
I dug deeper, and found out that this inconsistency for Python 3.5 occurs when training a ContextTagger. A ConditionalFreqDist() is created, with FreqDist objects. These are used to, for each token, find the most common tag. (i.e. finding learning that "do" is most frequently a verb)
However, it may occur that the frequency of two tags for a specific token is the same, and then Counter's most_common function is used, which will pick between equally valid options arbitrarily, explaining the difference between the trained models for Python 3.5.
This arbitrary choice is potentially no longer arbitrary starting from Python 3.6 because dict's got an update and were now often insertion ordered, rather than arbitrary like before. This change was an implementation detail which became a fixed property from Python 3.7 onwards.
Regardless, because of this arbitrariness for Python 3.5, we can train models in the doctest which perform better than the expected result. The distribution after 1000 iterations of the above program is the following, with the blue line representing the value 0.74:

Out of a 1000 iterations, the result was within 0.73... 982 times, and above 0.74 18 times. So, there is a ~1.8% chance that this test will randomly fail, despite the UnigramTagger working correctly, and doubtlessly frustrating the hell out of any dev that just pushed changes only to see the tests fail completely out of nowhere.
Considering this test will also break on any change in the brown corpus, even when the UnigramTagger works flawlessly, I suggest skipping this doctest. The commit alongside this PR does so.
Alternative solutions are to replace 0.73... with 0.7... to keep the test in place without there being any chance of it failing arbitrarily.
Important note:
This means that the tests for #2597 do in fact pass, and those tests should be re-run after this PR is merged, or after another solution for this bug is implemented. Have another look at it after resolving this issue!
This bug has been fun to hunt.

Tom Aarsen

Nice description, glad you had fun hunting this down. I'd be in favor of reducing the precision of the test or deleting it altogether. Skipping makes sense to me only if there is a resolution in the foreseeable future (e.g. when you're developing fast but know that you'll have to make the skipped tests work in the next iteration).

@iliakur
I followed the doctest documentation when figuring out the best solution. I'd rather not skip as I do not know whether the UnigramTagger is tested elsewhere.
Initially I tried looking for some syntax that supported a range of answers (e.g. 0.73... - 0.74...). Alternatively I looked for float answers within some margin (e.g. 0.73 ~ 0.01). However, neither of these options exist. I was quite surprised to find this.
I did find doctest.SKIP, which according to the documentation:

Can be useful in contexts where doctest examples serve as both documentation and test cases, and an example should be included for documentation purposes, but should not be checked. E.g., the example's output might be random.

This is why I decided to opt for the SKIP option. (Note: The documentation also mentions that the SKIP can be used for quickly "commenting" out examples, e.g. for quick development or test-driven development, like you mentioned)
Alternatively, the doctest itself can be rewritten into a format that is more difficult to read as documentation, but can be used as a test.
Current doctest
Note: This doctest fails ~1.8% of the time.
>>>tagger.evaluate(brown.tagged_sents(categories='news')[500:600])
0.73...

Alternative doctests
0. Proposed option in this PR: Skipped
>>>tagger.evaluate(brown.tagged_sents(categories='news')[500:600]) # doctest: +SKIP
0.73...

1. Ensuring that we have at least an evaluated accuracy of 73%.
We don't really need an upper bound for the test to pass, after all. A better accuracy shouldn't let this test fail.
>>>tagger.evaluate(brown.tagged_sents(categories='news')[500:600]) > 0.73
True

2. Reducing precision from 0.73... to 0.7....
>>>tagger.evaluate(brown.tagged_sents(categories='news')[500:600])
0.7...

3. Checking whether the evaluation is between 0.725 and 0.744999....
>>>round(tagger.evaluate(brown.tagged_sents(categories='news')[500:600]), 2) in (0.73, 0.74)
True

Options 1 and 3 would require a doctest description to be added before the doctest for additional explanation of what the test means.

If we want to preserve this test, then I would suggest either option 1 or 2.
Option 2 showcases the return type of the evaluate method the best, and is probably best for documentation.

I'm more than happy to receive feedback on what is the preffered option. That is why everyone can comment on Pull Requests after all, and partially why I enjoy open sourced development so much.

@CubieDev thanks for tracking this down!
For the test, you could also use math.isclose. There is also unittest.TestCase.assertAlmostEqual.

@stevenbird
What do you propose?
Perhaps Alternative 2 in my most recent comment is more intuitive than
>>>math.isclose(tagger.evaluate(brown.tagged_sents(categories='news')[500:600]), 0.73, abs_tol = 0.02)
True

or
>>>unittest.TestCase.assertAlmostEqual(tagger.evaluate(brown.tagged_sents(categories='news')[500:600]), 0.73, delta = 0.02)
True

I have no real preference.

@CubieDev, I don't have a strong preference either; happy for you to make the call

@stevenbird I have. I reckon reducing the precision from 0.73... to 0.7... will be the best option.
I have pushed my commit 01e0a7ad22150eb819745a237a475bde14cc4cd9 accordingly.

Great work, thanks @CubieDev


Is redux supported? How?

I'm trying to use this library in the following context:

there's a record that has many fields
I'm displaying a form with inputs for these fields
user would be editing some fields
async refresh process may change (other or same) field data

I wanted to get to the point where:

pristine fields would be updated only by async process
touched fields would be updated only by user

I figured I'd try redux, with data model like so:
// store state
{ record: {f1: "a", f2: "b", ...},
  overlay: {f2: "bbb", ...}}
// map-to-props
displayed = {...record, ...overlay}

At the moment I can't figure out how to marry react-use-form-state API to redux:

onChange is pre-field, and happens before state is changed
issuing redux action directly from formState gives me a react warning*

(*)
Warning: Cannot update during an existing state transition (such as within `render`). Render methods should be a pure function of props and state.

Am I missing something?
Is this library meant to keep data in component state only?

Hi @dimaqq - react-use-form-state is intended to manage form state in the form of a hook - which means it's maintains that state in component itself - it's not intended to be used with other state-management libraries such as Redux.
It might be worth mentioning that react-redux is in the process of introducing hooks APIs: https://github.com/reduxjs/react-redux/releases
Hopefully that will making integrating this library with Redux a bit easier.


IE/Edge exception

Plugin stopped to work on IE11/Edge (used to work before upgrade to v.2).
Reprosteps:
Just open https://ua9msn.github.io/datetime/ in IE/Edge, and see console output
I believe, it is due to the fact that IE does not support Intl.DateTimeFormat.prototype.formatToParts

It also doesn't support Object.assign. Will take a look what could be done.

@ua9msn any updates on the issue?

I thnk this plugin is obsolete. Ive got the plan to public the React version, as soon as I get time
It's useless to support or fix jQuery plugins.


fix(helm): refactor monitoring service

What type of PR is this?

fix / refactor monitoring service for envoy-gateway deployment
What this PR does / why we need it:

deployment needs to expose port for it to be accessible via service
there's no need to expose whole ports field from metrics service
the port on deployment is static as it cannot be adjusted (https://gateway.envoyproxy.io/latest/design/eg-metrics/#envoygatewaymetrics)

Which issue(s) this PR fixes:

N/A

thanks for finding this bug @nipsufn
should we instead be defining the deployment port here https://github.com/envoyproxy/gateway/blob/72fadb7c1dbe7d660c2900527c34f53cfcfce7ac/charts/gateway-helm/values.tmpl.yaml#L15 ? cc @Xunzhuo

It looks to me that .Values.deployment.ports is used in envoy-gateway-service.yaml directly...
If you think about dropping .Values.envoyGatewayMetricsService field then I see couple options:

add monitoring port to .Values.deployment.ports, drop envoy-gateway-metrics-service.yaml and make users scrape metrics against envoy-gateway-service.yaml
add .Values.deployment.monitoringPorts and use that for envoy-gateway-metrics-service.yaml

I'll also template already present .Values.deployment.ports to container spec on the deployment as they are missing.

please fix DCO
BTW, can you also set prometheus annotations?

/retest


Unable to download gopkg.in/yaml.v1 with git 1.7.1

$ go get github.com/spf13/hugo

This would always fail for me on CentOS 6.5 and never complete, though it would work fine in other places. I tracked it down to the 'gopkg.in/yaml.v1' meta package which causes git 1.7.1 to hang. On other hosts with git 1.9.1 it does work.
$ git clone https://gopkg.in/yaml.v1 /path/go/src/gopkg.in/yaml.v1
Initialized empty Git repository in /path/go/src/gopkg.in/yaml.v1/.git/
> hangs here <

The workaround is to first clone the library directly from github into the expected folder before you run go get. Then 'go get' won't hang.
git clone https://github.com/go-yaml/yaml /path/go/src/gopkg.in/yaml.v1
go get -v github.com/spf13/hugo

So I need newer git? Bummer. I'm on debian squeeze right now and it has git <IP_ADDRESS>.

The solution is to use git clone --branch v1 for yaml.v1 and fsnotify.v1, and git clone --branch v2 for yaml.v2. Other than that, installation goes swimmingly.

It kind of sucks that I have to write this special workaround for yaml.v2 since it' not allowed to upgrade git in my production env. IMHO this is gopkg.in fault in not testing with all the possible Git versions others may use.


RFC: Terragrunt scaffolding

This is an RFC for an idea around Terragrunt scaffolding to improve the experience around common workflow tasks in Terragrunt like:

adding a new component
adding a new environment
adding a new module
adding a new account

Link to video [internal only] https://app.slack.com/client/T0PJEPZ2L/CM6RR6JE7

Closing as stale


Migration tool: Apply hint links should be buttons

Also consider changing the text to be clearer.  Maybe something like "Add /?/ hint" etc.
Also: we should only display buttons that will have an effect

Note: after working further with the tool, I no longer think we should only display buttons that will have an effect.  Being able to add a "/?/" comment to confirm that the tool has correctly inferred something to be nullable is sometimes really nice.

Fixed in 5d9eb40f20c1c27cc0df200c179433669e0214a8


Using setTimeout

Why you are using javascript setTimeout method to set target value, for example setTimeout -> $target.val(value.replace(/\d\s$/, '')) ?

This is necessary for certain Android browsers, which don't take kindly to intercepting and redirecting key* events. It's most certainly sub-optimal, but removing it will require a re-architecting the entire plugin.


Add the possibility to dispatch some pdf.js events at the chrome level (bug 1904585)

r=me, but please file a follow-up bug for #18332 (comment); thank you!

https://bugzilla.mozilla.org/show_bug.cgi?id=1904677

/botio integrationtest


Fix padding on UI popups

Leave page and tooltip popups untouched

Also need to choose whether glass background will be applied to none/just search/all popups


Use /usr/bin/env to find the correct path to g++

Building the project fails on nixos (and everywhere else g++ is not in a standard path)

Thank you, this is an important issue. However, for me g++ is not in that path (it is /usr/bin/g++ for me). I think a proper fix would check multiple paths and select the one that works.

using env should get the path to g++ as long as it's in the $PATH
I've built my fork on nixos and arch linux with success

I think this change is superseded by cmake.
@framp Can you verify if you can build now using the updated instructions in compiling.md?

I can confirm this is fixed! Thanks for taking care of this issue ^^
I'm not running nixos anymore (I got tired of ML related packages not being up to date or not working and I switched to Arch Linux) but I ran it inside a VM and g++ is detected correctly

Unfortunately I can't test the full details as I don't have cuda available


added file type check to doc extraction

Currently, if you use DocumentExtraction with a file that isn't a PDF (the only currently supported doc type), e.g. .docx, you get a nondescript 500 error when you check the jobstatus. Changed the code to instead ensure that they are only uploading permissible documents initially.
Current error at JobStatus
{'code': 500,
 'error_type': 'CyclibException',
 'message': 'http://apiserver:5000/async/a376ed6f-a00f-47ea-862a-3b696f896169: {}',
 'content': {},
 'error_class': 'ServiceException'}

Can you add a test that triggers this?


Remove debug mode from concourse scripts

Signed-off-by: Denica Madzhirova<EMAIL_ADDRESS>

Coverage remained the same at 91.295% when pulling 6050d3337f42b7e69c2aa22bd00651cc6faef36e on SAP:remove_debug_from_scripts into 528112ea0bba7bcb23f1ba0d860f9a6f3ab32799 on cloudfoundry-incubator:master.

Coverage remained the same at 91.295% when pulling 6050d3337f42b7e69c2aa22bd00651cc6faef36e on SAP:remove_debug_from_scripts into 528112ea0bba7bcb23f1ba0d860f9a6f3ab32799 on cloudfoundry-incubator:master.

Coverage remained the same at 91.295% when pulling c39cab7a174d560b595d2c13f03f964ec8a8a315 on SAP:remove_debug_from_scripts into 528112ea0bba7bcb23f1ba0d860f9a6f3ab32799 on cloudfoundry-incubator:master.


Streamline installation for OSX and Linux

I think we should be able to reduce installation on OSX and Linux to 2 commands.
$ curl -L https://rack.developer.rackspace.com/rack-`uname -s`-`uname -m` > /usr/local/bin/rack
$ chmod +x /usr/local/bin/rack

This assumes a few things:

We have a proper domain name to replace the Cloud Files CDN domain name
The binaries are saved with capitalized Darwin and Linux to account of the output of uname -s
We provide 32 and 64 bit binaries. If not, we can just drop the uname -m

I also see we mkdir -p /usr/local/bin/ and export PATH=$PATH:/usr/local/bin. What OSX and Linux distros don't come with /usr/local/bin/ already?
I picked this stuff up from the installation instructions for docker-compose.

I like that.
Our "choice" of lowercase versions of Darwin and Linux actually come from go/gimme. We should make it easier for the user though, so that could be accommodated in the build script.
/usr/local doesn't exist on a plain vanilla install of OS X.

I'm really having trouble finding good citations other than some old articles about 32-bit vs. 64-bit, but I'd like to make a leap to say that 64-bit is likely on a developer box.
http://stackoverflow.com/questions/18281235/prevalence-of-64bit-vs-32bit-platforms

/usr/local does not exist on plain OSX installs (it's an xcode / homebrew artifact)
I would prefer NOT to assume the "run a magic curl command" model that docker and others use; our goal isn't for power users, its for support people and others who may hit an error because:
curl -L https://rack.developer.rackspace.com/rack-uname -s-uname -m > /usr/local/bin/rack
fails because they don't have access to the uname binary, or they don't have /usr/local - I'd rather assume they are not native OSX / developer users - or even native cloud users.

Nor do they necessarily have curl.

Correct

Alright. Power users will be able to figure this stuff out themselves anyway. And #58 will make it even easier.


feat: add support for wrapping the allocator with tracy

Useful for profiling memory usage w/ backtraces at allocation and deallocation of every object.
New deps in Cargo.lock are unreachable because of cfg(loom).

Example:


Extended bin pack environment.

This bin pack environment is based on the original bin pack environment with some added extensions:

Items can be rotated (and constraints on allowed rotations can be applied)
Full support constraints can be applied
A value feature can be added to items to allow for optimising for maximising the packed "value" of an items instead their volume (eg. you may have a very large item of low value that is blocking higher value items from being packed if optimisation is made based on volume)
A generator for this extended bin pack environment is also provided.

These developments were made as part of Fares Chouaki's internship in 2023. We would like to extend this environment even further (eg. allow for packing multiple containers) in order to compare end to end RL to column generation methods - this was a critique we obtained when submitting the work for publication, as we are only able to sequentially pack containers with the current code, which is not end to end RL).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: rsjeffers:x: chouakifaresYou have signed the CLA already but the status is still pending? Let us recheck it.


Add contributors to Readme

@all-contributors please add @dafrica1 for code.

@all-contributors please add @naody for code.

@all-contributors please add @AppLixirDev for ideas and projectManagement

@all-contributors please add @Dumbulo for ideas and projectManagement

@all-contributors please add @Dumbulo for ideas and projectManagement


Option to auto ban people who tag everyone or here during the first x minutes of joining

Now logging pings instead, there might be an option to ban for them in the future but it doesn't seem crucial for now.


remove IActivityGenerator, change ActivityGenerator to ActivityFactory

close: https://github.com/microsoft/botbuilder-dotnet/issues/2791

remove IActivityGenerator class.

change ActivityGenerator to ActivityFactory class

remove Generate method and GeneratedFromLG method

add CreateActivity static method which takes the result from Generate method in languageGenerator

modify BindToData method in ActivityTemplate

Pull Request Test Coverage Report for Build 86301

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-1.3%) to 76.295%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/Adapters/TestFlow.cs
1
77.17%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/OAuthPrompt.cs
1
54.8%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
2
50.0%

/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs
2
80.08%

/libraries/Microsoft.Bot.Builder/MemoryTranscriptStore.cs
2
86.09%

Totals

Change from base Build 86287:
-1.3%

Covered Lines:
7882

Relevant Lines:
10331

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

#2791

remove IActivityGenerator class.
change ActivityGenerator to ActivityFactory class
generate method now is a static method

Also please use github keyword, like closes #xxx, to make sure the issue gets closed after this is merged.

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


New lane structure

The current lane structure assumes one record at the longitudinal coordinate of 0m, on each relative lane. E.g. that there would be one record for one lane to the right of the GTU. However, this is not true. For example:

Two acceleration lanes (at merges) can be close together. The lanes leading up the acceleration lanes are both to the right of a GTU on the right-hand lane of the mainline.
If shoulders are included to also possibly have vehicles, for example as they were unable to merge in time, the shoulder too must be considered to the right.

Therefore the lane structure must supply a set of lanes, from which neighboring GTUs and objects can be found. Many perception categories and classes such as lane change incentives rely on taking a single record to the left or right, to derive information in a search starting from this record. These algorithms all need to be updated.

The new LaneStructure builds the structure every time step, but only to a limited range of about 300m downstream and upstream. Longitudinal search has absolute priority over lateral search. Lateral search will skip any lane that was already found longitudinally.
In any upstream search, when a lateral move is made, the relative lane of this laterally found lane remains the same as the lane it is found from. This is because if a lateral move is made, it is the only way the GTU can ever get in interaction with the ego GTU. For example: when the left lane merges with the right lane before reaching an acceleration lane, traffic on this left lane of the two can be laterally considered to be on the same lane as the acceleration lane.
The class can provide:

Leading and following GTU's on all lanes in the structure, sorted near to far.
First leading and following GTU's on all lanes in the structure, sorted near to far. This only contains the first leader, or if there is a split before any GTU, the first leader on each branch. This may repeat, and also applies for followers.
Upstream and downstream LaneBasedObjects of a given type, sorted near to far.

The rolling lane structure has been removed.
Perception categories have been extensively updated to use the new lane structure.
Incentives have been updated to use the new structure. IncentiveRoute uses the shortest path lane change info algorithm from RoadNetwork to go beyond the extent of the lane structure.
Conflicts still use a simple version of lane records, within perception iterables.
Lane records within the lane structure are also simpler, as they are no longer laterally connected. This was only used for lane change info, which is now taken from the network.

Overall the data structure is simpler and more robust. GTU's can now use the shoulder if they need to.

A small test with the short merge demo revealed that where the old lane structure took a total of 3662ms to be created during one hour of simulation, this was only 26ms for the new data structure.


Refine backprop assignments in error message

This PR refines the error message by incorporating information about the assignments. Following is an example of an informative error message:
Code snippet:
func test(x *int) {
	x = nil
	y := x
	z := y
	print(*z)
}

Error message:
Potential nil panic detected. Observed nil flow from source to dereference point:
   -> errormessage/errormessage.go:32:9: literal `nil` dereferenced via the assignment(s):
        -> `nil` to `x` at errormessage/errormessage.go:29:2,
        -> `x` to `y` at errormessage/errormessage.go:30:2,
        -> `y` to `z` at errormessage/errormessage.go:31:2

[closes #83 ]
[depends on #86 ]

Logic LGTM! The only concern I have is memory consumption & artifact size increases.
Let's do a quick profiling & internal performance validations to ensure the consumptions are still within reasonable bounds 😃

Checked with profiling and internal performance validation. Both memory consumption and artifact size within acceptable bounds.


How does the DOCKER version save files on the server?

Because I change presentations anytime and anywhere, I hope that I can directly access the link to see the notes I have written before, instead of having to manually load local files every time.

By default excalidraw is purely local, meaning it does not store anything on the server. Storing to the server is by default enabled in shared scenes, but you would need to roll out your own collaboration to do that. There have been several discussions on this topic https://github.com/excalidraw/excalidraw/issues/1772.


Bluetooth temp sensor

Hello,
I have updated from the MQTT version to esphome. In MQTT, I could write the temperature from a Bluetooth sensor to the unit.
When I want to do this now, I get an error:
This service requires field value, please enter a valid value for value.

Can someone tell me what's going wrong?

Add "| float" before the "}}"

Like this:

This still doesn't work

Like this:

This still doesn't work

Change to yaml mode and then do it like this:
services: esphome.mhi_YOURDEVICENAME_api_room_temperature
data:
value: "{{ states('YOURDEVICENAME') | float }}"

I still get an error:

I found the solution, the indent was the problem:

Thx for the help

Edddydort,
I have copied your solution to use a external wifi temp reading as TRoom value.
The problem is that i need to hit the "call service" button to update the external temperature reading.
Am i doing something wrong?

You need to put this service in automation. And let it publish every 30 seconds or so

Thanks Eddydordt,
I've managed to get it to work allthough it feels like a "way arround".
Would it not be better to directly lead the Troom input to an available temperature entity in HA?
Nevertheless many thanks for your help.

I think ESPHome has the ability to read sensors directly from HA and use them, but then you would need to create the automation in ESPHome. In reality, I don't think it's going to be more reliable since you still need your home assistant to be available.
The only more neat solution would be a wired temperature sensor or a bluetooth sensor which is directly connected to the ESP that controls your AC.. But bluetooth/wifi share the same antenna on ESPHome so it could influence the stability of the connectivity.. And then you still need an automation within ESPHome as there's no native implementation currently.


[OSPO Book] Update 01-chapter.md

fixed some spelling errors
fixed typos
changed Programs to Program

Thanks for the PR @shillasaebi! 🎉


Why swift is Fruit flavoured OCaml

The official doc says:
Swift. Fruit-flavored OCaml! https://reasonml.github.io/docs/en/what-and-why
I want to know why before I can quote it.

I didn't write the words, but I'd guess that it's because Swift was developed at Apple (named after a fruit) and is stylistically similar to Reason/OCaml in many ways.

I don't know why that would be -- Swift is a language which is not very similar to OCaml at all, even if it has some OCaml flavoring with the type inference and discriminated unions

@ubsan I guess we consider it a spiritual descendent of OCaml, by way of Scala.
I think this issue can be closed, @shineli-da ?

Yeah sure. Thank you all.

Or maybe it's Camel flavored fruit?


Added Kali Linux Install Screenshot link

Issue: #2

Installed Kali Linux in Virtual Box
Added Kali Linux Install Screenshot link

Link : https://drive.google.com/file/d/1lWgzEvHQzXcLb5OGcPaPWbrj2cbHSCIk/view?usp=sharing

Hey @ASHTAD123
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!


Add Python Check to CMake

Add Python check to beginning of CMake.
Some depenendencies (glslang) requires Python. It would useful to crash before loading externals with a usefull error message if Python is not found, instead of waiting until some other externals are loaded.
Further, it seems, that VS Projects are broken when trying to continue from incomplete configure when running into this issue.

Shaderfactory was updated. New glslang version doesn't require python anymore.


the keyboard shortcut of clearing the terminal doesn't work rightly

Issue Type: Bug
after I set the keyboard shortcut of clearing the terminal and press the shortcut,there is still previous output in the terminal
VS Code version: Code 1.44.1 (a9f8623ec050e5f0b44cc8ce8204a1455884749f, 2020-04-11T01:48:12.622Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.85GB (9.09GB free)

Process Argv

Screen Reader
no

VM
67%

Extensions (6)

Extension
Author (truncated)
Version

code-runner
for
0.9.17

vscode-filesize
mkx
2.1.4

python
ms-
2020.3.71659

cpptools
ms-
0.27.0

vscode-leetcode
she
0.16.1

vscode-icons
vsc
10.1.1

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Show keyboard shortcuts inside integrated terminal in Screencast Mode (#81537)

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

Show keyboard shortcuts inside integrated terminal in Screencast Mode (#81537)

I'm sure it's not covered by other shortcuts. When I press the shortcut of clearing terminal, the terminal likely has been cleared and there is nothing in the terminal, but then I rurn the code again, the previous output appear int the terminal.

/duplicate https://github.com/microsoft/vscode/issues/75141


Add window controls

From what I can tell, one of the major applications of WindowControls is creating split header bars (like we had in the Slider example at some point). The problem they solve here is allowing the user to select on which side of the window the close button should be shown. This is also why the side field exists.
For this application we need to provide the option to not override GtkSettings:gtk-decoration-layout.

Could you expand what conclusion you want me to draw from this ? Mostly because I can draw multiple.
E.g. the simplest interpretation would be to say "if seq[WindowControlButton].len == 0 then either don't set decoration-layout string or set it to the default-value" (both achieve the same result of having the default value present).
I'm just not sure if you mean that or want me to go in the direction of splitting "WindowControlButton" into "Left" and "right" or want me to abandon the approach with a "WindowControlButton-enum" altogether.

Could you expand what conclusion you want me to draw from this ? Mostly because I can draw multiple.

The main point is allowing the user to explicitly leave/make unset. Note that this unset state is explicity different from adding no buttons. One way to do this is using buttons: Option[seq[WindowControlButton]] (or as below buttons: Option[DecorationLayout]). It needs to explicitly read gtk-decoration-layout if left unset.
Other related changes that might be interesting:

Create a "DecorationLayout" type that has fields for left/right
Make buttons a setter is overloaded to support both DecorationLayout (and immediately calls $ on it) and a regular string

I have just now learned that Headerbar also has a decorationLayout string.
Doing effectively the exact same.
Could it make sense to abandon wrapping WindowControls for the same reason that wrapping Bin was abandoned (it's kinda pointless) and instead add wrapping for decorationLayout to HeaderBar?
Because the way I currently see it nobody should be using the WindowControls widget if they can just use HeaderBar

I've updated the PR to reflect what we just discussed in discord:
This PR is no longer for adding the windowcontrols widget.
It is for adding support of those window controls (including a nicer setter) to Headerbar.
I removed the example since headerbar previously didn't have one so I assume it was deemed too small to be worth an example widget.

I just saw that Gtk.HeaderBar:decoration-layout also overrides GtkSettings:gtk-decoration-layout. So the field should by of type Option[string] to allow for explicitly not overriding the property.

@can-lehmann I'm closing this PR and merging it into #116 .
That PR with AdwHeaderBar also needs decorationlayout and basically all the same hooks, enums and toLayoutString procs etc.
It makes sense to not develop double / have to refactor that after merge and instead combine them right now.
As per your previous statement that you prefer "coupled" PRs to be combined, I am thus combining them.


how to access refs in parent when child component is exported with withStyles?

for eg.
Child.js
//assume there is s as styles object and used in this component
class Child extends Component {
 render() {
  return (

{this.ref = ref}}>Hello

  );
 }
}

export default withStyles(s)(Child);

Parent.js
class Parent extends Component {
 onClick() {
    console.log(this.child) // here access the ref
    console.log(this.child.ref) // undefined
 }
 render() {
  return (

      <Child ref={child => this.child = child} />
      <button onClick={this.onClick.bind(this)}>Click</button>

  );
 }
}

due to with styles the whole this.child ref in the parent component is changed. Please help me out with a workaround for this, dropping the withStyles is not an option.

@divyankkarolia97 It depends on your use case, but you can use the <RootRef /> component or the innerRef property.

WithStyles is supposed to use forwardRef https://github.com/mui-org/material-ui/blob/next/packages/material-ui-styles/src/withStyles/withStyles.js#L49, but when doing
<List ref={node => { this.listEl = node;}}>

this.listEl points to WithStyles {props: {…}, context: {…}, refs: {…}, updater: {…}, jss: Jss, …} instead of the DOM Element. Wrapping in ReactDOM.findDOMNode works to retrieve the dom element, but I thought it was discouraged to use it (https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/no-find-dom-node.md)
I tried innerRef instead of ref, but not doing anything
I don't think https://material-ui.com/api/root-ref/ will help in that situation
https://codesandbox.io/s/43zzzj03x4

I was using<EMAIL_ADDRESS>when using @next, it works, the dom element is returned

@caub :)


Critical vulnerability in shell-quote

react-dev-utils is using shell-quote 1.7.2 which has a vulnerability that has been fixed in 1.7.3

closed and raised as a bug


Feature Request: Respect user's typed case when offering suggestions

Example: the following exist:
./Temp1
./temp2

Then type: cd te<tab>. zsh fills in temp then stops. Press <tab> again, and the suggestions come up as Temp1/ temp2/
Coming from bash, I would expect that specifying the case of the first couple of letters would be enough to identify the desired autocomplete.
In oh-my-zsh, is it possible to have
cd te<tab><tab> autocomplete temp2, then offer temp2/ Temp1/ on an additional tab press?
Similarly;
have cd Te<tab><tab> autocomplete Temp1, then offer Temp1/ temp2/

You need to add setopt menu_complete to your zshrc file. We disable that option in lib/completion.zsh.

setopt menu_complete doesn't address the different cases in the way I described.
What it does do is:
Type: cd te<tab>. zsh fills in Temp1/. Press <tab> again, and the suggestions come up as Temp1/ temp2/
Instead, if user types: cd te<tab>. zsh fills in temp2/. Press <tab> again, and the suggestions come up as temp2/ Temp1/
Another use-case: if ./temp2 and ./temp3 existed, then with cd te<tab> zsh could fill in temp then stop.

Sorry, I misread (twice) your test suite. Here's a list of completion options for zsh, maybe you can find what you're looking for there while I'm trying to find the right combination for you.

I've been messing around with settings and I haven't found a working setup. Perhaps you'll find better luck asking on the zsh mailing list... Sorry :sweat_smile:

I believe the zstyle ':completion:*' matcher-list setting is what you're looking for. It's set here in lib/completion.zsh to do case-insensitive matching. You could override that by re-setting it in your ~/.zshrc file after OMZ is loaded, changing it to a customized one which prefers exact-case matches to case-insensitive matches. (After, not before, or OMZ will just clobber it.)
I think this is what you're looking for, where same-case matches are preferred to differing-case matches. And here's the doco if you want to customize it further. (Which you'll need to do if you want to get Te to fully match Temp1 first, but offer temp2 upon additional tab presses.)
zstyle ':completion:*' matcher-list 'r:|[._-]=* r:|=*' 'l:|=* r:|=*' 'm:{a-zA-Z}={A-Za-z}'

If you want to ignore case-differing matches entirely, you can set CASE_SENSITIVE=true in your ~/.zshrc before loading OMZ.

Similar to #4118, which may also be helpful.

Alright; I did two things:

Installed zsh by itself in a linux VM
went to the mailing list

I found this thread from 2003 where Jesper Holmberg was looking for the same thing.
After going through all the suggestions here, and everything in that thread, the best I've come up with is this:
_cscomplete() {
  _complete
  return 1
}
zstyle ':completion:*:cscomplete:*' group-name case-sensitive
zstyle ':completion:*:complete:*' group-name case-insensitive
zstyle ':completion:*' group-order case-sensitive case-insensitive
zstyle ':completion:*::::' completer _cscomplete _complete
zstyle ':completion:*:cscomplete:*:*' matcher-list ''
zstyle ':completion:*:complete:*' matcher-list 'm:{a-z}={A-Z}'

Going back to the test case:
./Temp1
./temp2
./temp3

Typing cd te<tab> completes temp then stops. Pressing <tab> again does something interesting:
temp2/      temp3/
Temp1/  temp2/  temp3/

It's a little messy, but does meet what I'm trying to do: suggest the case-sensitive completion first, and still offer the case-insensitive options.
As with most things at this level, there is a gotcha: if tEMP4 exists, when te<tab> is typed, tEMP4 will never be suggested, but that seems like a fair trade off.
I'd certainly welcome anyone who can refine this (and have reached out to the mailing list asking the same question), but in the mean time I hope this thread benefits the next person who asks this question.

Closing since it's a ZSH issue, not an Oh My ZSH issue.
@mcornella + @apjanke; thanks for the help.

Thank you Josh for the write-up, I'm sure this will be of much interest.
Let me see if I can improve on it, as well.
Cheers
—
Marc


auto init on package import

If we end up breaking up different parts of "package main" into sub-packages, we have to take care that there is no race condition between init() calls. There doesn't seem to be a way to control the order that they are called in.

Items in the package init function should be strictly package specific, e.g. create a lut for a crc, etc..., so order shouldn't matter, and everything else should be in an exported Init function.


Update guidance for linalg rtol tolerance cutoff to accommodate non-SVD-like algorithms

This PR

resolves https://github.com/data-apis/array-api/issues/216 by updating the guidance for rtol to accommodate non-SVD-like algorithms. Namely, instead of a strict cutoff of less than or equal to, this PR updates the guidance to say "approximately less than or equal to" to allow conforming implementations some wiggle room should they choose a non-SVD-like algorithm for implementing pinv. For matrix_rank, the API is already defined in terms of singular values, so, in practice, an implementation is likely to be SVD-based; in which case, the more strict guidance is likely to hold.
in general, the previous guidance should hold true, given the prevalent usage of LAPACK; however, array libraries should be able to use alternative algorithms in accordance with the design principle to be "implementation agnostic". A future refinement could be to define the tolerance in terms of condition numbers, but that is left to future consideration.

Thanks @leofang!


Cannot "increase liquidity" to already established pool pairing

Hello! I have test erg & ada tokens added to the liquidity pool which I added during beta phase.  I wanted to add more to liquidity just to play around with the feature but page just stays loading.  I am able to reach the "remove liquidity" page just fine but cannot "add liquidity."  Just a heads up...keep up the great work!

Opened up a new liquidity pair for Ergo/Luna Dog (non-beta this time lol) and the "increase liquidity" option seems to be working fine now!


500 server error when entering gene name in "Coordinate or gene name box"

PHP error provided in partialNames.php:
PHP Fatal error:  Call to a member function bind_param() on a non-object in /var/www/give/html/givdata/partialNames.php on line 37

This happens for every gene name out of the box.

After debugging more thoroughly this is due to the prepared SQL query above failing with the error:
Table 'mm10._AliasTable' doesn't exist

So it seems that an _AliasTable is required for the gene name input box, but there is no documentation about this, and the only other place this is used is scripts/geneNameUpdate.py. It would be nice if more information about what columns are expected in the gene annotation tracks is documented. For example, currently, the first column is used for displaying the gene name on the track, and while the UCSC knownGene.txt and the provided knownGene.txt.gz files use the UCSC id in the first column, all the demos use the gene symbol.

I have rewritten the scripts/geneNameUpdate.py script in Go to import the data to avoid installing the Python dependencies for the original script, and the issue persists after importing the NCBI data, creation of the aliases table, and importing the kgXref data from UCSC separately. With all the data imported, there is no longer a 500 error in response to partialNames.php, but there is no data in the response. Will continue to debug what the issue is.

I have a semi-working search box now, at the expense of having the UCSC default gene names on the gene annotation track, but that can be fixed by adding another track with the real gene names and hiding the knownGenes track. However, the SQL query for search is extremely slow at first load.
More severely however, issue #37 occurs when opening specific genes, so I do not think this is due to the bigWig files. For instance, in another set of bigWigs that work perfectly fine at Actb, the browser hangs and is stuck at the exact position as the previously reported issue.

The <gene-coor-input> element was developed quite early (well before the alpha stage of GIVE) so the documentation and back-end support is different from most of the other elements.
Currently it depends on four tables:

_NcbiGeneInfo table to get the gene description corresponding to gene symbols;
_AliasTable table to convert various aliases of the genes to the official gene symbol;
kgXref table from UCSC to translate official gene symbol to UCSC ids;
knownGene table to find genomic coordinates for the gene symbol.

The script scripts/geneNameUpdate.py can automatically populate tables _NcbiGeneInfo and _AliasTable from NCBI public data. However, we haven't been able to document it and are working on it (including moving requirement 3 and 4 to something customizable, so it will not depend on only UCSC gene tracks) before the next release. (This is also a part of #26 so the release should fix them both.)
We saw bugs in bigWig file handling before that only happens at specific genomic regions, where the data does not meet some assumptions. It is also possible that #37 only happens when there is a specific structure in the bigWig file. Will be looking into it but if it's stuck in PineNode.js that will be the most likely reason.

Understood, thanks for the background information. My rewrite of scripts/geneNameUpdate.py in Go works as expected with the GIVE-Docker container.
I'm curious what kinds of assumptions need to be met in the data, is there a particular flag or configuration change you for creating the bigWigs? Thanks.


Could you share the AP under friction coefficient thresholds[0.8,0.4]？

Hi！Hybrid Physical Metric is a great work！But I want to know the experiment result under the same friction coefficient thresholds as 1Billion(0.8and0.4). Could you share your result?If you can, please send it to<EMAIL_ADDRESS>Thanks!

In the GraspNet-1Billion, the relationship between grasp score and coefficient ：s = 1.1- μ. Hence, the coefficient 0.8, 0.4 correspond to grasp score 0.3, 0.7. Note that Hybrid Physical Metric generates new scores, and the grasp scores 0.3, 0.7 does not exactly correspond to friction coefficient in this work (refer to eq.4 in the H. P. M.). The AP (0.3, 0.7) results is in the experiments.


Related project

Hi :)
Did you know about makers? It has similar goals to omake, but incompatible license (I think), might be interesting for comparison and benchmarking.

Oh neat, I did not know about that project. It's definitely much more mature than this project. Yeah, license looks non-free I think, but I believe it would allow me to run it for the purposes of benchmarking. Honestly at the moment I'm trying to get this project into a state where it can start running the GNU Make test suite and I'm putting performance on the back-burner until the basic functionality is there.

Honestly at the moment I'm trying to get this project into a state where it can start running the GNU Make test suite and I'm putting performance on the back-burner until the basic functionality is there.

Totally agree, just wanted to point out that other project for future reference :)


Add note to session docs

Summary
Details and comments
Fixes #742

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.781%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3299

Relevant Lines:
4940

💛  - Coveralls


Add emergency switch support

The new android app comes with an emergency switch to override the protection settings of the BMS. For example if the low voltage protection kicks in and there is an emergency you are able to override the protection state / re-enable discharging.
Command: aa5590eb 6b<PHONE_NUMBER>19ca465d7d09e74c9ec7 # Emergency ON
Command: aa5590eb 6b<PHONE_NUMBER>1ca240f936b60fca39de # Emergency OFF

See #276

Done


Type incompatibility after upgrading pino to 8.6.0

Upgraded pino to latest release, 8.6.0 in a project using Next.js, pino, and pino-http.
A test that assigns the log field on a NextApiRequest as part of its setup now fails with the following error:
Type 'Logger<LoggerOptions | DestinationStream>' is not assignable to type 'LoggerExtras<LoggerOptions>'
I tried to use a mock instead and still encountered the error.

Thanks for reporting!
Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that.
cc @kibertoad for his TS experience

Hey @mcollina
I've noticed the similar behavior after upgrading to latest pino and pino-http, but not sure if the usage is incorrect, but after upgrading to latest pino and pino-http such code no longer works. (Logger and ChildLogger can not casted to same type)
      let childLogger: pino.Logger | null = null;

      childLogger = req.log.child({ test: 'test' });

And then the error looks like this:
TS2322: Type 'Logger<LoggerOptions & ChildLoggerOptions>' is not assignable to type 'Logger<LoggerOptions> | null'.   Type 'Logger<LoggerOptions & ChildLoggerOptions>' is not assignable to type 'Logger<LoggerOptions>'.     Property 'onChild' is missing in type 'BaseLogger & LoggerExtras<LoggerOptions & ChildLoggerOptions> & Record<never, LogFn>' but required in type 'LoggerExtras<LoggerOptions>'.
Previously it was possible to use pino.Logger and child logger from req.log.child as a same type.

@thomas-yaa
The issue resolved for me after upgrading typescript to latest version (4.6 -> 4.8.4)

cc @kibertoad


Add BUILD file for vm/test/emitc and samples/emitc_modules

Also adds iree_c_module bazel rule mirroring CMake side. This does not
add the automatic generation to bazel_to_cmake.


Adding Convenient Effects Covers instead

Would this be possible ? To add convenient effects cover effect instead of the original ones, that would actually take care of the Dexterity save. (Might not be possible actually since CE is giving to the target the cover and all... )

The main issue is that players cannot modify unowned tokens, so it complicates the workflow some.
I dont use CE myself, so I would need a Pull Request to even start.
In short, open to it, but cannot implement myself.


feat: make editor use full container height

Proposed Changes

Related to https://github.com/camunda/camunda-modeler/issues/4342
Make the editor use full container height. It will allow it to focus when clicking anywhere in the container, not only on the text lines.
Checklist
To ensure you provided everything we need to look at your PR:

[X] Brief textual description of the changes present
[ ] Visual demo attached
[ ] Steps to try out present, i.e. using the @bpmn-io/sr tool
[X] Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

It works fine. From the linking perspective, I think it makes sense to also include Related to https://github.com/camunda/camunda-modeler/issues/4342 in the commit body. This will allow us to link the commit without a need to search the PR.

@jarekdanielak Do you go ahead and release this change?


Assets generated by extract-text-webpack-plugin are not compressed

The assets that are created by extract-text-webpack-plugin are not compressed in my web pack builds.
For instance .css files are not compressed. The funny thing is that the .css.map files are compressed.
Has anyone noticed this?
I will post a configuration example tomorrow!

This is my config:
var Compression = require('compression-webpack-plugin')
var Extract     = require('extract-text-webpack-plugin')

var path = require('path')

module.exports = {
  context: path.resolve(__dirname)
, entry: {
    main: [
      './src/index.js'
    , './src/style.css'
    ]
  }
, output: {
    path: path.resolve(__dirname, 'assets')
  , filename: '[name].[hash].js'
  }
, module: {
    loaders: [
      {
        test: /\.css$/
      , loader: 'extract-text-webpack-plugin/loader?extract&remove!css'
      }
    ]
  }
, plugins: [
    new Extract('[name].[hash].css', {
      allChunks: true
    })
  , new Compression({
      asset: '{file}.gz'
    , algorithm: 'gzip'
    })
  ]
}

OK. Let's just say I was tired yesterday. It turns out the css file wasn't gzipped because the ratio wasn't good enough.

@romeovs what settings did you use to get it to work and gzip the css?

You should make sure that the CSS file is large enough for it to be compressed significantly enough for the compression to make sense (otherwise the browser will spend more time unzipping the file than in just receiving it uncompressed).
This is expressed using the ratio option, it defaults to .8 from what I can see. This means that the compressed file should have at most 0.8 times the size of the original file.
Because for really small files, the gzipped one can even be (much) larger than the original, setting the ratio to 1 is not enough. I set it to 4, but to make sure it really always works, you could set it to Infinity.
Hope this helps!
Typed on my smartphone, so will contain errors.

On 15 Mar 2016, at 20:40, CJ Lazell<EMAIL_ADDRESS>wrote:
@romeovs what settings did you use to get it to work and gzip the css?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


Plagiarism

There is a plagiarism here, just changed the logo. https://play.google.com/store/apps/details?id=lk.visual.code.mobile
The picture on Google play is not real, you should download it and take a look.
He even added advertisements in the software to charge.

Hi @du-wen-xuan, like I said earlier, I checked it and there is no plagiarism to me. It's completely different application

Hi @du-wen-xuan, like I said earlier, I checked it and there is no plagiarism to me. It's completely different application

Not sure but this use the IDE source code.

@Gugui322 ok now I see, there was a completely different app before


Light Theme

Did you ever consider releasing a light syntax theme based on the colors? I guess the contrast would be good enough if you'd 'recycle' the colors in front of a light background.

I did mess with a light theme, but it didn't feel star wars anymore.  It just felt like like a variant on base 16 light or something.


(whitelist) olymptrade.com

add to whitelist olymptrade.com

Already did. Can you please report here from now on.


Remove unused test data

I mistakenly tried to add this data with the compliance dataset. It should be removed.
@saupchurch

+1
no longer need these


How to train multi-classes at the same time?

Hi, If I want train it to detect multi classes, what should I change?
model: {
  second: {
    voxel_generator {
      point_cloud_range : [0, -40, -3, 70.4, 40, 1]
      # point_cloud_range : [0, -32.0, -3, 52.8, 32.0, 1]
      voxel_size : [0.2, 0.2, 0.4]
      max_number_of_points_per_voxel : 35
    }

    num_class: 1
    voxel_feature_extractor: {
      module_class_name: "VoxelFeatureExtractor"
      num_filters: [32, 128]
      with_distance: false
    }
.....

I will upload a sample config. you can see the following example first.
model: {
  second: {
    ...
    num_class: 2

    target_assigner: {
      anchor_generators: {
        # fixed-size anchor generator for EVERY class.
      anchor_generators: { # cars
        anchor_generator_range: {
          sizes: [1.6, 3.9, 1.56] # wlh
          anchor_ranges: [0, -40, -1.78, 70.4, 40, -1.78] # carefully set z center
          rotations: [0, 1.57] # DON'T modify this unless you are very familiar with my code.
          matched_threshold : 0.6
          unmatched_threshold : 0.45
        }
      }
      anchor_generators: { # cyclist
        anchor_generator_stride: {
          sizes: [0.6, 1.76, 1.73] # wlh
          strides: [0.2, 0.2, 0.0] # if generate only 1 z_center, z_stride will be ignored
          offsets: [0.1, -19.9, -1.465] # origin_offset + strides / 2
          rotations: [0, 1.57]
          matched_threshold : 0.5
          unmatched_threshold : 0.35
        }
      }
      anchor_generators: { # pedestrian
        anchor_generator_stride: {
          sizes: [0.6, 0.8, 1.73] # wlh
          strides: [0.2, 0.2, 0.0] # if generate only 1 z_center, z_stride will be ignored
          offsets: [0.1, -19.9, -1.465] # origin_offset + strides / 2
          rotations: [0, 1.57]
          matched_threshold : 0.5
          unmatched_threshold : 0.35
        }
      }
      ...
    }
  }
}

train_input_reader: {
  class_names: ["Cyclist", "Pedestrian"]
  ...
  database_sampler {
    database_info_path: "/media/yy/960evo/datasets/kitti/kitti_dbinfos_train.pkl"
    sample_groups {
      name_to_max_num {
        key: "Car"
        value: 8
      }
    }
    sample_groups {
      name_to_max_num {
        key: "Pedestrian"
        value: 4
      }
    }
    sample_groups {
      name_to_max_num {
        key: "Cyclist"
        value: 4
      }
    }
    database_prep_steps {
      filter_by_min_num_points {
        min_num_point_pairs {
          key: "Pedestrian"
          value: 5
        }
        min_num_point_pairs {
          key: "Cyclist"
          value: 5
        }
      }
    }
    database_prep_steps {
      filter_by_difficulty {
        removed_difficulties: [-1]
      }
    }
    global_random_rotation_range_per_object: [0, 0]
    rate: 1.0
  }
  ...
}

eval_input_reader: {
  class_names: ["Cyclist", "Pedestrian"]
  ...
}

@traveller59 Thanks for you advice. I shall try it out

Any update for multi-class detection?

I tried to train the model  with people.config, but the result is not good. Waiting for multi-class detection.

Could you please upload sample.config file to train simulatanously for multiclass detection

@traveller59  Any updates on this?

@chowkamlee81 there is a sample config all.fhd.config in this project.
@jinfagang The people detection need small receptive field. The performance of people detection in car-like config leads to bad performance. we may need a other head from sparse feature extractor for people detection, or a RCNN structure, point cloud of pedestrian can be scaled before get into RCNN.
There is another strange thing: I have submit people detection network result to KITTI test server (for my master thesis) and get bad test performance (a little worse than SECOND v1), but the val performance is better than v1.

@traveller59
Is there any pretrained model for pointpillars?  It would be great if there is a single model for all classes.

@traveller59  i have following queries

can you give a small description of what does the function anchor_generator_stride()  and anchor_generator_range() do
for custom dataset for custom class should we have to use  anchor_generator_range() with values   sizes: [1.6, 3.9, 1.56] and anchor_ranges[], is it default since the custom class object is small object
thanks in advance


Please add log_400_event or log_level (debug) options

Problem
2022-04-01 11:51:33 +0000 [warn]: #0 send an error event to @ERROR: error_class=Fluent::Plugin::ElasticsearchErrorHandler::ElasticsearchError error="400 - Rejected by Elasticsearch" location=nil tag="app.fpm" time=2022-04-01 11:51:26.872353958 +0000
I want to know the reason why, so I need the log_level debug or at least the log_es_400_reason parameter.
Like we have it here - https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/elasticsearch/#elasticsearch-log_es_400_reason
Using Fluentd and ES plugin versions
    repository: ghcr.io/banzaicloud/fluentd
    tag: v1.14.4-alpine-2

OS version - "Alpine Linux v3.14"
Fluentd 1.14.4
AWS ES Service plugin version fluent-plugin-aws-elasticsearch-service (2.4.1)
ES version - AWS OpenSearch 1.1(latest)

@cosmo0920 Hello, sorry to bother you, but do we have a way how to troubleshoot my issue? I just want to know why AWS OpenSearch reject my logs. Thanks.

We are running into an issue where this option would be very helpful.

Hi, @ServerNinja. It looks like this repo is "dead". Unfortunately, our request will not be heard.

Already inherited: https://github.com/atomita/fluent-plugin-aws-elasticsearch-service/blob/master/lib/fluent/plugin/out_aws-elasticsearch-service.rb#L10

Already inherited: https://github.com/atomita/fluent-plugin-aws-elasticsearch-service/blob/master/lib/fluent/plugin/out_aws-elasticsearch-service.rb#L10

Hi, Hiroshi. Actually, I still didn't know how to enable debug and use this log_es_400_reason parameter.
Could you help me with that?
Should my config is like is next:
      awsElasticsearch:
        endpoint:
          url: https://logs.example.com
          region: us-east-1
          assume_role_arn:
            value: arn:aws:iam::12345678:role/logs-full-access
        index_name: app-${kube_app_name}-%Y.%m.%d
        buffer:
          tags: tag, time, kube_app_name
          timekey: 3s
          timekey_wait: 5s
          timekey_use_utc: true
          flush_thread_count: 8

I'll try to clarify and add more context: I use banzai-cloud logging-operator - https://banzaicloud.com/docs/one-eye/logging-operator/configuration/plugins/outputs/aws_elasticsearch/
I use the fluent-plugin-aws-elasticsearch-service plugin as an output for my logs.

So I suppose this log_es_400_reason option should be added from the banzai logging-operator side?
Am I right ?

Yes. Adding log_es_400_reason parameter support is required here:
https://github.com/banzaicloud/logging-operator/blob/c9722ee319584ff75ebda49ef4095b6bf127d7d4/pkg/sdk/model/output/aws_elasticsearch.go

And this issue is not related this repo but, for tracking issue, we leave this issue as-is for now.


UI: increasing the line spacing in the deploy page of a wizard

The spacing between 'Deploying' and the line of the reservation id is too small the text is overlapping

Added spacing between deploying and the workload ID:

verified


⚠ Samsung has degraded performance

In 32a3453, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2315 ms

Resolved: Samsung performance has improved in 80fee50.


(SERVER-252) Add acceptance tests for irb and ruby subcommands

SERVER-252

Without this patch there are no acceptance level tests for the ruby and irb
subcommands.  This is a problem because we need to ensure these commands behave
as expected, particularly when the gem subcommand is used to install third
party libraries.
This patch addresses the problem by installing the hiera-eyaml gem and then
checking that ruby can require 'eyaml'.  In addition, this patch tests the
system level behavior surrounding how subcommands are expected to handle
managed environment variables (GEM_HOME, GEM_PATH, RUBYLIB, RUBYOPT, RUBY_OPTS)
as well as arbitrary user specified environmentvariables (FOO_DEBUG).

It looks like 33cf447 isn't actually related to SERVER-252. We should probably either create a new ticket or just label the commit as (MAINT).

It looks like 33cf447 isn't actually related to SERVER-252. We should probably either create a new ticket or just label the commit as (MAINT).

Fixed.
Also, added a positive assertion for irb and ruby exercising puppet.

Other than @nwolfe's comment about the unused import, this LGTM :+1:

Other than @nwolfe's comment about the unused import, this LGTM :+1:

Cool, unused import has been removed.

:chart_with_upwards_trend: This is looking really good.  Just left a few comments on problems I ran into trying to duplicate the result of the tests with local commands issued on one of my VMs.  Also, interested in hashing out the whole discussion on clearing/overriding/preserving of different environment variables.  You have some great points there.  Wanted to get some other opinions to see where others are on that.

out of curiosity--might we want to target this at stable?

Seems reasonable to me if @erikPrime is onboard.

@erikPrime what say you?  This PR is basically just tests, so it'd just improve our coverage for 1.0.1/3.7.2.

@cprice404 There's more than just tests here as the PR stands, though - specifically, the bit on how environment variables are passed through to the JRuby container via the subcommands.

well, crap.  is there a way to decouple those two changesets, then?  if not, maybe this needs to stay on master, I dunno.

Yeah, maybe we should just pull that commit out of this PR and reconsider our environment support both for the CLI and the production scripting containers as a separate topic?

I'd be good with separating them, too, although I think the tests would need to be rewritten a bit to work for the code as currently implemented.

The tests are tied to the change in behavior in that I didn't want to spend time and effort testing something that isn't behaving well.  My vote is to keep these two commits together and just merge them into master or into stable together.
I'm not sure about the value of adding tests to stable when the behavior of the stuff being tested is or will be significantly different in master.  Adding only tests to stable is basically testing that stable misbehaves as expected.

@camlow325 @nwolfe and I chatted IRL and decided to open another pull request against stable that includes only the tests, no changes in behavior.  I'll leave this pull request open and rebase it to accommodate the new PR.

OK, rebased onto a fake master that assumes #362 is merged into stable, then stable merged up into master.
This will likely need a re-base once #362 is merged in and up.
This PR doesn't have anything to do with SERVER-252 at this point, it's really just about the behavior change around how we handle environment variables.

This pull request is a bit of a mess and should probably be ignored until #362 is merged into stable and up into master.  At that point cec3381 should be rebased onto master.

Yep, that makes sense.  I think it also would be good to cover the environment rework stuff under a new JIRA ticket and expand the scope to include reworking the production ScriptingContainer code to be consistent with that of the subcommand tools.  Sound okay?  If so, @jeffmccune, could you file that ticket?

@camlow325 Filed as SERVER-297

@jeffmccune - This can't be merged.

@KevinCorcoran we need to regroup on goals / implementation path before we bother rebasing this.

@jeffmccune is there a compelling reason not to close this until we've had our round-up meeting?  Trying to clear out our PR backlog.


Class Not Registered

I had successfully built and run the NativeXamlIslands.sln in Visual Studio 2019.  Trying to investigate why my attempted modification fails.  I used the NuGet Package Manager Console to update a few of the packages to the latest versions (as in my modified copy of the sample), and now this unmodified original crashes with winrt::hresult_class_not_registered.  The only thing I changed here was to update the NuGet packages to the latest versions:
Exception thrown at 0x00007FFDBD27A859 in SampleCppApp.exe: Microsoft C++ exception: winrt::hresult_class_not_registered at memory location 0x000000C80E11CF08.
Exception thrown at 0x00007FFDBD27A859 in SampleCppApp.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
Exception thrown at 0x00007FFDBD27A859 (KernelBase.dll) in SampleCppApp.exe: WinRT originate error - 0x802B000A : 'Cannot create instance of type 'Microsoft.UI.Xaml.Controls.XamlControlsResources' [Line: 13 Position: 32]'.
Unhandled exception at 0x00007FFDAA312EC0 (Windows.UI.Xaml.dll) in SampleCppApp.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000002797F19C9E0, 0x0000000000000002).

Prior to that, there was this, but the application marched on until hitting the above.  No idea if this is relevant:
...
'SampleCppApp.exe' (Win32): Loaded 'C:\Windows\System32\propsys.dll'.
Exception thrown at 0x00007FFDBD27A859 (KernelBase.dll) in SampleCppApp.exe: 0x40080202: WinRT transform error (parameters: 0x000000008000000B, 0x0000000080070490, 0x0000000000000014, 0x000000C80E11DD50).
'SampleCppApp.exe' (Win32): Loaded 'C:\Windows\System32\UiaManager.dll'.
...

I grabbed a clean clone, re-applied the NuGet updates, and now it works again.  I am mystified.


Create Labels for ArcMap and ArcGIS Pro

We need to create labels for the different versions of ArcMap and ArcGIS Pro. This will help focus our efforts on which versions of the tools need attention. @lfunkhouser @conklinbd @nfeuerstein

So here I'm not really up to the idea of including a label for the version number, e.g. 10.2, 10.3, 1.0, 1.1. That list could very easily grow without bounds.
But I would be OK with having the app, for example:

ArcGIS Pro
ArcMap
Services (for geoprocessing services)

@mfunk - edited the labels to include: V - ArcGIS Pro, V - ArcMap, and V - Services. Please verify and close.

@jrweakland got 'em. Thanks.


求大佬解答

执行后还是不行啊，邮件配置用outlook测试过可用但是，在服务器上运行后还是不能用。。。

python代码也没问题。求大佬解答

The project of Ruoli is no longer being maintained and maintenance of this project is suspended.
If the issue remains unresolved and is very urgent, please feel free to open this Issue again!


python310Packages.gcal-sync: 4.0.2 -> 4.0.3

Changelog: https://github.com/allenporter/gcal_sync/releases/tag/4.0.3
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 202886 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.google
python310Packages.gcal-sync
python39Packages.gcal-sync


Automatic docking

Is automatic docking supposed to work? I found a service for it and tried:
ubuntu@uwbot-01:~$ ros2 action send_goal /dock irobot_create_msgs/action/DockServo {}
Waiting for an action server to become available...
Sending goal:
     {}

Goal was rejected.

That happens when the dock is visible:
ubuntu@uwbot-01:~$ ros2 topic echo /dock
header:
  stamp:
    sec:<PHONE_NUMBER>
    nanosec: 962197994
  frame_id: ''
dock_visible: true
is_docked: false

Please let me know if this is rather an Icreate3 issue.

The docking action is provided by the Create 3 but it should work. Does the robot do anything when you call the action?
Also can you try placing the robot on the dock and using the undock action? ros2 action send_goal /undock irobot_create_msgs/action/Undock {}

This might be related to using the cyclonedds middleware without setting the correct middleware options: export CYCLONEDDS_URI='<CycloneDDS><Domain><General><DontRoute>true</></></></>'

We were no longer able to reproduce this issue later on. Docking seems to work.


BedrockChat model mistakenly removed in latest version?

System Info
It looks like BedrockChat was removed from the chat_models/init.py when ChatKonko was added in this commit: https://github.com/langchain-ai/langchain/pull/10267/commits/280c1e465c4b89c6313fcc2c0679e3756b8566f9#diff-04148cb9262d722a69b81a119e1f8120515532263a1807239f60f00d9ff2a755
I'm guessing this was accidental, because the BedrockChat class definitions still exist.
@agola11 @hwchase17
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction
.
Expected behavior
I expect from langchain.chat_models import BedrockChat to work

@kaleko Dosu mispoke. It can't make PRs (yet). I agree this looks like a mistake! Are you able to make a PR to fix?

@kaleko
Can you plz close this issue, if the import has been fixed.


librewolf: Remove unnecessary updates files

Hello,
Currently, the LibreWolf package disables auto-update... so while navigating through its container folder, I noticed that there are two .ps1 files: ScheduledTask-Create.ps1 and ScheduledTask-Remove.ps1 initially, I thought they are from Scoop...
25/06/2024  14:09    <DIR>          .
25/06/2024  14:09    <DIR>          ..
25/06/2024  14:09                60 install.json
18/05/2024  15:19    <DIR>          LibreWolf
25/04/2024  01:28           913.408 LibreWolf-Portable.exe
21/05/2024  09:55             3.040 manifest.json
25/06/2024  14:09    <JUNCTION>     Profiles [\??\C:\Users\SegoCode\scoop\persist\librewolf\Profiles]
19/10/2023  22:33             1.506 ScheduledTask-Create.ps1
30/09/2023  21:55               795 ScheduledTask-Remove.ps1

For my surprise, weren't from Scoop, they were from the LibreWolf download itself...
Currently, the manifest removes a file LibreWolf-WinUpdater.exe, and these .ps1 files remain as residue. To avoid confusion and reduce the package size, I propose adding the following to the manifest:
 "Remove-Item \"$dir\\ScheduledTask-Create.ps1\"",
 "Remove-Item \"$dir\\ScheduledTask-Remove.ps1\"",

https://github.com/ScoopInstaller/Extras/blob/master/bucket/librewolf.json#L18

Hm, looks like was already done in #10958 but later rewritten for some reason by #11052.

So, I've seen it, kinda weird... those ps1 scheduledTask files depend on the deleted update executable and I haven't seen any dependency from them by the main run binary. I did a test on a fresh install of Windows 11 and the installation works perfectly without those scheduledTask ps1 files 🤷♂

Maybe have been added again by accident...


Volume mounts on OSX don't seem to work

When running the latest image on OSX Yosemite, Docker 1.4.1 and doing volume mounts, I get errors trying to write to files?  I am mounting the volumes under the /Users directory as is required of boot2docker configured VirtualBox VM.
I had to set the permissions on the mounted volumes to 777 to even get RabbitMQ to start up at all with volumes mounted.  Everything works when no volumes are attached.  I have successfully written to volumes on OSX with other images/containers, just this one doesn't seem to work.  Any ideas for me to try?

I guess this is just an OSX/boot2docker/VirtualBox limitation.  I just tried using a volume container strategy like I would use for database persistence and it resolves the permissions problem on OSX.  Hopefully this will help someone Googling for an answer...


open func.yaml file when clicking on tree view

Fix: #191

Codecov Report

Merging #258 (10cc69e) into main (a04c63d) will decrease coverage by 0.49%.
The diff coverage is 29.41%.

@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
- Coverage   85.22%   84.72%   -0.50%
==========================================
  Files          77       78       +1
  Lines        3140     3156      +16
  Branches      531      534       +3
==========================================
- Hits         2676     2674       -2
- Misses        464      482      +18

Impacted Files
Coverage Δ

.../functions/function-tree-view/functionsTreeItem.ts
33.89% <20.00%> (-2.47%)
:arrow_down:

...tions/function-command/open-yaml-file-in-editor.ts
30.00% <30.00%> (ø)

src/extension.ts
71.21% <50.00%> (-0.67%)
:arrow_down:

src/util/platform.ts
88.23% <0.00%> (-11.77%)
:arrow_down:

src/cli/cmdCli.ts
42.16% <0.00%> (-3.62%)
:arrow_down:

src/util/watch.ts
93.33% <0.00%> (-3.34%)
:arrow_down:

Continue to review full report at Codecov.

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


Missing "src/theme/components" folder in yarn repository

Hi! I don't know is it your error or yarn cache but after today update i have missing src/theme/components folder. On yarnpkg.com in files section this directory absent too.

@phwb Yes, we are looking into it
Kindly follow #1734

Here my solution:
"native-base": "~2.3.0",
"prop-types": "^15.6.1",
"react": "16.3.0-alpha.1",
"react-native": "0.51.0"
delete nativebase from node_module , yarn install and react-native link native-base
hard code ~ replace for ^ and reduce version => ~2.3.0


Android Emulator - Receiving UNEXPECTED commands

I have a nRF Dongle I flashed with the zypher firmware that was mentioned in the documentation.
I am using Android emulator version <IP_ADDRESS>, with a Android 14 Pixel 8 simulator.
Running:
bumble-hci-bridge android-netsim:_:8877,mode=controller usb:0
./emulator -packet-streamer-endpoint localhost:8877 -avd Pickle -no-snapshot-load
When I attempt to toggle BLE on the emulator, I see a lot of proper communication on the bridge, but there are a couple packets that always are breaking, which prevent me from turning BLE on, on the emulator.
Thank you!

After some handling of packets and filtering, I was able to get this working as expected.

It seems that the Android Bluetooth stack isn't happy when the controller it is talking to does not support the HCI_WRITE_LE_HOST_SUPPORT_COMMAND command.
One way around this is to tell the bumble-hci-bridge app to short-circuit this command (always answer SUCCESS).
That command has the following opcode: hci_command_op_code(0x03, 0x006D).
So you can include 0x03:0x006D on the bumble-hci-bridge command-line (the last parameter is a command-short-circuit-list, which is a command-separated list of commands to short-circuit, expressed as hex-value tuple.