Can't Specify Top-K retrieved Documents in Multimodal Retrievers using Invoke()

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
# Check retrieval
query = "What are the EV / NTM and NTM rev growth for MongoDB, Cloudflare, and Datadog?"
docs = retriever_multi_vector_img.invoke(query, limit=6)

# We get 4 docs
len(docs)

Error Message and Stack Trace (if applicable)
No response
Description
retriever_multi_vector_img.invoke(query) no longer has a method to limit or increase the amount of docs returned and subsequently passed to the LLM. This is defaulted at 4 and no information can be found on the issue.
You can see the incorrect use in this cookbook: https://github.com/langchain-ai/langchain/blob/master/cookbook/Multi_modal_RAG.ipynb
# Check retrieval
query = "What are the EV / NTM and NTM rev growth for MongoDB, Cloudflare, and Datadog?"
docs = retriever_multi_vector_img.invoke(query, limit=6)

# We get 4 docs
len(docs)

Where 6 was the limit and 4 is returned. How can we enforce more docs to be returned?
System Info
Using langchain_core 0.2.8

try following, get the top k result
retriever_multi_vector_img = vectorstore.as_retriever(
search_type="mmr",
search_kwargs={'k': 3, 'fetch_k': 5}
)
then,
retriever_multi_vector_img.invoke(question)


PUT scores

ensure that the scores are updating properly

put scores is working properly

are there any other requirements needed?


UI Changes

Font changed to match with Avian Brand kit.
Site colors Updated to Avian Brand kit.
Footer Updated

Looks good code-wise, we can improve UI later. I will also fix the commits to contain your name.

I merged it lol.

No problem, I already fixed it. All good to go!

Thanks bro


add hybrid require mode and support for roblox-ts modules

Closes #240 and #241
This adds a new require mode called hybrid which attempts to parse via the Roblox require mode initially (i.e. script.Parent), then parsing via the regular path require mode, if Roblox fails.

[x] add entry to the changelog

going to remake this pr in a more modular format...


Dev

refactor

set nr-labs-components dependency to be fetched from npm repository
remove helpModalOpen && condition in JSX before modal component

This looks good - just a couple of changes:

update to package.json to use the latest version of nr-labs-components (i think it's 1.21.2)
there has to been a change to embedding gdrive hosted images which is breaking the labs logo in the help modal. This URL seems to work, so update the logo src to: https://drive.google.com/thumbnail?id=1BdXVy2X34rufvG4_1BYb9czhLRlGlgsT


Disconnect sometimes

Hello,
Your integration work but disconnect sometimes like atome.
Can we do reload if 30 minutes without change ?
If yes, how please ?

If it seems to be stuck, you can make an HA automatisation and force a reload with Home Assistant Core Integration: reload_all (service section)
Internally, keyatome performs retry (i.e. log on server) once if a command does not respond .
Automatically reconnect every 1h30.
Can you show me the "Diagnostic" sensor curve ?
Thanks in advance

Any news ?

Hello,
I'm waiting for it to start again to tell you the problem.
it is not possible that it is displayed as an integration with the "Reload" button?
Thank you

Voici le problème qui recommence:
https://i.postimg.cc/qh95VsYn/Capture.png

Est-ce que vous pouvez récupérer qqch dans les traces ?
Qu'est-ce que le senseur statistics ?

Can I do debug info ?

yes

Please can you look in diagnostic, if there is something on server side ?

How do I download the diagnostic?  I don't see KeyAtome as an integration

i can't find KeyAtome in Integration page. So i can't find config_entry to do reload like that:
http://localhost:8123/api/config/config_entries/entry/XXXXXXXXX/reload
Can you update it to see it in integration page ?

Thank you !
I have configured with yaml. i just do with config flow !
i can do now reload integration !

great I will close the issue. If ok with you


Updating display of application status on pet

Describe your change in plain English.
Updating display of application status on pet for adopter
Staff view

Adopter view
https://github.com/rubyforgood/pet-rescue/assets/34173394/e78d81bb-25ec-4402-aac7-c53afc492d88
Link to the issue
Resolves #40

Only weird thing is that one of the statuses ends up being "Application Adoption Pending" - not sure if that's clear for the adopter?


[radio-button] Unable to one-way bind to a property accessible only via a getter

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Radio button selection should work when its value is one-way bound to a property readable only via get property()
What is the current behavior?
It's impossible to select or deselect a radio button.
What are the steps to reproduce?

Open this plunker
Notice that the 3rd radio group cannot be interacted with. This is true of all radio groups whose buttons are one-way bound to a model property declared like

get options_3(){
    return [
        { name:'One', value:1},
        {name:'Two', value:2}
];};

And bound with a template like
<md-radio-group name="group_3">
<md-radio-button *ngFor="let o of options_3" [value]="o.value">{{o.name}}</md-radio-button>
</md-radio-group>

What is the use-case or motivation for changing an existing behavior?
It's a bug
Which versions of Angular, Material, OS, browsers are affected?
Angular 2 rc.5, Material alpha 7-2, Win 7 x64, Firefox 48
Is there anything else we should know?
This is a regression. I noticed the bug after upgrading from Angular 2 rc.4, Material alpha 6 to the versions above.

The problem is get options_3 returns a new map whenever options_3 is called. In that case, the md-radio-group will generate a new list of md-radio-button.
Clicking on the radio buttons (and other activities) will trigger the options_3 function and cause the existing radio buttons to be replaced by new ones. The new buttons haven't received any selection event, so they behave like not clickable.

The correct way to do it is your get options_2 if you really need a function in the *ngFor loop. Closing this issue.


Color Correction

Provide an optional parameter to color correct the resulting imagery to better reflect images such as the following:

@jakiestfu what color correction techniques are you using above?

@ngoldman From the wiki article:

Example of a Rayleigh-corrected, true-color full disk image created from the AHI sensor.

This would be awesome.
Is it doable ?

@mdcarter color correction, yes, but Rayleigh Correction, not sure...

Just a layman's observation based on reading Correction of Rayleigh scattering effects in cloud optical thickness retrievals, in order to correct for Rayleigh scattering (which affects the optical density of clouds), it's necessary to measure the density more directly.
They mention using images taken at different wavelengths, and they also talk about using images taken at different angles, both of which are not available from a single flat image.
As it looks like the source that himawari.js pulls from is a single flat image, calculating Rayleigh scattering correction may not be technologically possible.

The question is: what colour correction methods can get close enough to the same result?

You're not going to be able to get quite the same result as above working with a single full disk image but you could use @celoyd's color tweaks suggestions from his Himawari 8 animation tutorial as a starting point. He's using convert which is a part of ImageMagick, so that tool is already available to this project with its current dependencies.

@ngoldman do you think you could provide a sample picture or some code that outputs that picture?

This code works fine, however, it doesn't do much to the image other than brighten and add contrast:
convert original.jpg -channel R -gamma 1.2 -channel G -gamma 1.1 +channel -sigmoidal-contrast 3,50% updated.jpg

original.jpg, updated.jpg

it doesn't do much to the image other than brighten and add contrast

Right. It tones down blues (and greens) too, but it is extremely simple compared to what CIRA RAMMB has done to the image on Wikipedia. Their code is based on what’s used with MODIS and VIIRS, which is nontrivial. They have a paper in review, so more details should be public soon. I’m pretty confident that it’s more complex than anything that makes sense to implement here. (But skip to the “However” heading for some ideas.)
Rationale for simple adjustment
We don’t have good access to data for complex adjustment
Our options are limited because we don’t have the bands that CIRA does. They’re able to calculate optical depth, cloud height, etc., from information that’s at best only kinda present in the RGB PNGs we’re looking at. And they can mix some of the NIR channel into the green channel to account for the green band being to the < λ (blue) side of the 550 nm peak visible reflectance of chlorophyll.
Sidebar: Why? Because the data is produced by the government of Japan, and they haven’t licensed and distributed it that way, as far as I can tell. I’ve signed up for their P-Tree service, but its TOS is vague and refers to other lengthier and confusinger TOSes. They seem to imagine forecasters, researchers, and resellers as the only potential users – which is completely understandable, but frustrating in our position.
So while I’m very grateful that they’ve done as much as they have to license and distribute this data – they’ve clearly worked hard to serve their intended users well – I would like to convince them to do a little more. I don’t have the language skills, the contacts, or (at the moment) the time to make a persuasive case for truly open data here. If someone else does, I’d be happy to contribute some sort of amicus brief based on professional experience with these issues. End sidebar.
We just don’t have the raw information that CIRA RAMMB does. If we could get it, it’s not clear (to me, yet) that we could “publish” it.
We don’t necessarily want complex adjustment
However! CIRA’s path is not necessarily ideal. While I would use the NIR→green trick if I could, everything else they’re doing is more science- than esthetics- or realism-oriented. A person in space would see Rayleigh scattering making the atmosphere bluer toward the horizon, for example, and BRDF effects, both of which the correction deliberately and efficiently removes. They would also see the halo of the atmosphere, which CIRA’s correction cuts out, and they would not see the smudgy artifacts that the correction sometimes introduces near the terminator (dawn and dusk): look west of India in the example image at full size. What CIRA’s doing is extremely impressive, cutting-edge correction. But it’s not necessarily what makes sense here – at least as I’ve been envisioning it.
However
I’m all for experiments more elaborate adjustment!

what colour correction methods can get close enough to the same result?

You can model the atmosphere as a spherical shell of known radii (in pixel dimensions) and do some very light trig to find the distance for which a given pixel’s ray intersects it, then use that field to weight a correction. And you can add low-res gridded elevation data (e.g.) to account for the fact that, for example, the Tibetan Plateau extends above most of the optical atmosphere. Instead of estimating, you can look up measured optical depth, from MODIS or from ground-based weather reports. Or you could pull in something like 6S, which is a standard atmospheric corrector that’s actually related to what CIRA is using. It’s really just a question of how far you want to go.
So
That’s why I’m pretty happy to use a simple/simplistic static adjustment. For input to ffmpeg, incidentally, I’ve been using this:
convert -gamma 1.33 -channel B -gamma 0.9 -channel G -gamma 0.975 +channel -sigmoidal-contrast 3,33%

Which is a bit light and low-contrast by itself, but whatever random color profiles ffmpeg makes up seem to put it about where I want it.
Just one last point and I’ll give you back the mic
You can download CIRA’s images if you prefer them for any reason! There could even be flags to produce, say:

CIRA
NICT
NICT with basic correction
NICT with experimental correction

Okay, I’ll be quiet now

Thanks @celoyd for taking time to get into the details! :grin: :ok_hand: :100:

Re: hue correction:
I just ran convert -gamma 1.33 -channel B -gamma 0.9 -channel G -gamma 0.975 +channel -sigmoidal-contrast 3,33%, and got the following image:

The image at the top of this issue has quite a bit more green and Australia is noticeably different.
Is there a more correct colouring?

The image at the top of this issue has quite a bit more green and Australia is noticeably different.

Yes. This is mainly because CIRA does NIR→green mixing to account for the green channel not being on the chlorophyll peak.

Is there a more correct colouring?

Of the two, or theoretically? Could you be more specific?

Is there a more correct colouring of the two.
If it's the top image as it seems to be, it would get closer by adding some green and nudging down the red a bit, but that's just off the top of my head.


Notifications for both firing and resolved items doubts

Hi,
When an alert is active, the alertmanager will send out notifications periodically (as per the group_wait or group_interval value) whenever new items are firing for that group but also when items got resolved in that group.
AFAIK the fact that it also sends separate notifications when items get resolved in the group for an active alert is not related to the global send_resolved flag, but I was wondering if there was a way to disable these notifications. (We're currently receiving lots of emails because of it.)
I've written down the following scenario and listed some questions where I don't understand the behaviour. I've tried to make it as clear / simple as possible, only using 1 target / 1 metric (2 label values) / 1 alert definition and the following configuration
ALERT metric1_down IF metric1 == 0
scrape_interval: 5s
group_wait: 30s
group_interval: 5m
repeat_interval: 24h

Every block below indicates a change in the alerting (new alert fired / alert getting resolved). I've included the timestamps of the actions that have happened and listed down the areas where I'm still missing something. I started with a clean prometheus / alertmanager with no previous alerts.
I've written down my assumptions and my questions.
metric1{v=a}  == 0 FOR 1min

06:24:30 : metric1_down{v=a} pending
06:25:38 : metric1_down{v=a} firing (due to alert specifiying FOR 1min)
06:26:12 : receive notification :  firing(metric1_down{v=a})

Assumption : Notification is sent after the interval following 06:25:38 + the  group_wait: 30s)
metric1{v=b}  == 0 FOR 1min

06:27:30 : metric1_down{v=b} pending
06:28:40 : metric1_down{v=b} firing
06:31:12 : receive notification :  firing(metric1_down{v=a} and metric1_down{v=b})

Assumption :  Alertmanager now waits group_interval: 5m after the previous email was sent. Does not use group_wait
metric1{v=a}  == 1

06:31:50 : metric1_down{v=a} alert disappears
06:36:12 : receive notification :  firing(metric1{v=b}) and resolved(metric1{v=a})

Assumption: it again waits group_interval: 5m after the previous email was sent
Q1 : Is there a way to resolve this email ? I already now metric1_down{v=b) is firing. Don't want a notification that metric1_down{v=a) is resolved
metric1{v=b}  == 1

06:38:50 : metric1_down{v=b} alert disappears
06:41:12 : no slack / email saying everything resolved

Assumption : everything was resolved, no alerts active anymore and send_resolved=false so no email is sent ?
metric1{v=a}  == 0 FOR 1min

06:43:00 : metric1_down{v=a} pending
06:44:10 : metric1_down{v=a} firing
06:46:25 : receive notification :  firing(metric1_down{v=a}) , resolved(metric1_down{v=b})

Q2 : A bit surprised to see "resolved(metric1_down{v=b}) in this notification. at 06:41 everything as resolved and the system was ok. Also unclear why it got sent at 06:46:25. Does it take into account group_interval or group_wait here ?
metric1{v=a} == 1

06:48:30 : metric1_down{v=a} alert disappears

Assumption : Alertmanager considers the system healthy now ? ... all issues have been resolved.
metric1{v=b} == 0 FOR 1min

06:56:30 : metric1_down{v=b} pending
06:56:37 : metric1_down{v=b} firing
07:01:30 : receive notification :  firing(metric1_down{v=b}), resolved(metric1_down{v=a})
07:11:30 : receive notification :  firing(metric1_down{v=b})

Q3: 07:01:30 - Was not expecting it to say resolved: metric1{v=b}) in the 07:01:30 msg. Same as Q2
Q4 : 07:11:30 -  Not sure why this email is sent. Adds little value. I already know metric1_down{v=b} is firing. Why is this sent 10 minutes after the previous one ?
If you've made it this far thanks a lot ! :) Would appreciate some feedback to get a better understanding of it.

Q1 : Is there a way to resolve this email ? I already now metric1_down{v=b) is firing. Don't want a notification that metric1_down{v=a) is resolved

With send_resolved disabled, there shouldn't have been mention of the resolved alert in any emails.

Does it take into account group_interval or group_wait here ?

It's within 5m, so group_interval still applies.
Is your alertmanager or prometheus under heavy load?

No heavy load ... we're using the email and slack notifier and from the docs / code the send_resolved should be false.
With the script below, and a group_interval=2m I'm getting the following mails/slack msgs:

10:23 - firing a1/a2  (30 seconds after a1 was raised, as expected)
10:25 - firing a1/a2/a3/b1/b2/b3  (2mins after first email, as expected due to group_interval)
10:29 - firing b3 / resolved b1,b2,a1,a2,a3 (no idea why this came 4 minutes after the previous mail)
10:32 - firing b3 (no idea why this is sent)

curl -XPOST -d'[{"labels":{"alertname":"a1"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; sleep 15
curl -XPOST -d'[{"labels":{"alertname":"a2"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; sleep 15
curl -XPOST -d'[{"labels":{"alertname":"a3"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; sleep 15
curl -XPOST -d'[{"labels":{"alertname":"b1"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; sleep 15
curl -XPOST -d'[{"labels":{"alertname":"b2"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; sleep 15
curl -XPOST -d'[{"labels":{"alertname":"b3"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date ; echo "done... now looping b3 for keepAlive"
while true; do  curl -XPOST -d'[{"labels":{"alertname":"b3"}}]' http://localhost:9093/alertmanager/api/v1/alerts; date  ; sleep 15; done

Can you share your full alertmanager config for that?

Sure...
global:
  smtp_smarthost: 'xxx'
  smtp_from: 'xxx'
  smtp_auth_username: 'xxx'
  smtp_auth_password: 'xxx'
  slack_api_url: 'xxxx'
# The root route on which each incoming alert enters.
route:
  # The root route must not have any matchers as it is the entry point for
  # all alerts. It needs to have a receiver configured so alerts that do not
  # match any of the sub-routes are sent to someone.
  receiver: 'team-xxx-mails'

  # The labels by which incoming alerts are grouped together. For example,
  # multiple alerts coming in for cluster=A and alertname=LatencyHigh would
  # be batched into a single group.
  group_by: ['group']

  # When a new group of alerts is created by an incoming alert, wait at
  # least 'group_wait' to send the initial notification.
  # This way ensures that you get multiple alerts for the same group that start
  # firing shortly after another are batched together on the first
  # notification.
  group_wait: 30s

  # When the first notification was sent, wait 'group_interval' to send a batch
  # of new alerts that started firing for that group.(with the shell script. The other scenario was executed with group_interval: 5m)
  group_interval: 2m

  # If an alert has successfully been sent, wait 'repeat_interval' to
  # resend them.
  repeat_interval: 24h

  # All the above attributes are inherited by all child routes and can
  # overwritten on each.

  # The child route trees.
  routes:
  - match:
      job: Controllers
    receiver: team-xxx-mails

receivers:
- name: 'team-xxx-mails'
  email_configs:
    - to: 'xxx'
      html: '{{ template "xxx.email.default.html" . }}'
      headers:
        subject: '{{ template "xxx.subject" . }}'

    #require_tls: false
  slack_configs:
  - channel: '#notify-xxx-dev'

templates:
 - '/etc/alertmanager/template-vars.tmpl'
 - '/etc/alertmanager/templates/xxx.tmpl'
 - '/etc/alertmanager/templates/yyy.tmpl'

@brian-brazil : if you need me to do some further testing just let me know...
Here's some debug logging output. From this output I got 4 mails where I expected only 2 mails.
The last 2 mails are redundant, as they both say that alert b3 is active (I knew that from the second mail).
time="2017-01-03T15:25:37Z" level=debug msg="Received alert" alert=a1[f00e214][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:25:52Z" level=debug msg="Received alert" alert=a2[f004214][active] component=dispatcher source="dispatch.go:168"
** MAIL ** time="2017-01-03T15:26:07Z" level=debug msg="flushing [a1[f00e214][active] a2[f004214][active]]" aggrGroup=cbf29ce484222325 source="dispatch.go:405"
time="2017-01-03T15:26:07Z" level=debug msg="Received alert" alert=a3[f008214][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:26:22Z" level=debug msg="Received alert" alert=b1[e75cf84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:26:37Z" level=debug msg="Received alert" alert=b2[e75af84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:26:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:26:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:27:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:27:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:27:37Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:27:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
** MAIL ** time="2017-01-03T15:28:07Z" level=debug msg="flushing [a2[f004214][resolved] a3[f008214][active] b1[e75cf84][active] b2[e75af84][active] b3[e756f84][active] a1[f00e214][resolved]]" aggrGroup=cbf29ce484222325 source="dispatch.go:405"
time="2017-01-03T15:28:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:28:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:28:37Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:28:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:29:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:29:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:29:37Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:29:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
** MAIL ** time="2017-01-03T15:30:07Z" level=debug msg="flushing [b1[e75cf84][resolved] b2[e75af84][resolved] b3[e756f84][active]]" aggrGroup=cbf29ce484222325 source="dispatch.go:405"
time="2017-01-03T15:30:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:30:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:30:37Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:30:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:31:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:31:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:31:37Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:31:52Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
** MAIL ** time="2017-01-03T15:32:07Z" level=debug msg="flushing [b3[e756f84][active]]" aggrGroup=cbf29ce484222325 source="dispatch.go:405"
time="2017-01-03T15:32:07Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"
time="2017-01-03T15:32:22Z" level=debug msg="Received alert" alert=b3[e756f84][active] component=dispatcher source="dispatch.go:168"

Our operators are only interested in the first 2 emails. (as they know now that they need to investigate a1,a2,a3, b1,b2,b3). The third / fourth email is noise to them.
According to you with send_resolved: false should the alertmanager only be sending out the first 2 mails ?

Is this only happening with email, and are you sure the config is what the alertmanager has loaded?

Using Slack, Email and webhoks. For every email there is also a slack and a webhook call. So don't think that it's related to the receivers.
I've verified that the correct config is loaded via the alertmanager status page
Tried it with both 0.50 and 0.51 (using Docker)
Can you reproduce it using the curl commands above ?

@brian-brazil : Could this be the problem ?
https://github.com/prometheus/alertmanager/blob/master/notify/impl.go#L82
// Notify implements the Notifier interface.
func (i *Integration) Notify(ctx context.Context, alerts ...*types.Alert) (bool, error) {
	var res []*types.Alert

	// Resolved alerts have to be filtered only at this point, because they need
	// to end up unfiltered in the SetNotifiesStage.
	if i.conf.SendResolved() {
		res = alerts
	} else {
		for _, a := range alerts {
			if a.Status() != model.AlertResolved {
				res = append(res, a)
			}
		}
	}
	if len(res) == 0 {
		return false, nil
	}

	return i.notifier.Notify(ctx, alerts...)
}

First time I'm looking at GO code, but shouldn't it be passing along the filtered alerts (res) instead of the original alerts (alerts) to the notify function ?

Great, that looks to be it. Didn't notice that when I was perusing the code.

Perfect. I've never used Go and don't know how high prio this is but what
are the chances somebody from the core team doing a PR ? I can do the
codefix but would lose a lot of time figuring out how to write the tests in
go and such...
But more than happy to test / validate and give feedback.
On Wed, 4 Jan 2017 at 01:17, Brian Brazil<EMAIL_ADDRESS>wrote:

Great, that looks to be it. Didn't notice that when I was perusing the
code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/alertmanager/issues/591#issuecomment-270262926,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWPFo1Er-cQFqqWrqwy80HLMWjm6c0Lks5rOuUKgaJpZM4LZYH2
.

Thanks for the detailed report and discussion, I'll prepare the fix and some tests around this shortly!


docs: update Azure Service Principal / IPAM documentation

When installing Cilium in an AKS cluster, the Cilium Operator requires an Azure Service Principal with sufficient privileges to the Azure API for the IPAM allocator to be able to work.
Previously, the az ad sp create-for-rbac was assigning by default the Contributor role to new Service Principals when none was provided via the optional --role flag, whereas it now does not assign any role at all. This of course breaks IPAM allocation due to insufficient permissions, resulting in operator failures of this kind:
level=warning msg="Unable to synchronize Azure virtualnetworks list" error="network.VirtualNetworksClient#ListAll: Failure responding to request: StatusCode=403 -- Original Error: autorest/azure: Service returned an error. Status=403 Code=\"AuthorizationFailed\" Message=\"The client 'd09fb531-793a-40fc-b934-7af73ca60e32' with object id 'd09fb531-793a-40fc-b934-7af73ca60e32' does not have authorization to perform action 'Microsoft.Network/virtualNetworks/read' over scope '/subscriptions/22716d91-fb67-4a07-ac5f-d36ea49d6167' or the scope is invalid. If access was recently granted, please refresh your credentials.\"" subsys=azure
level=fatal msg="Unable to start azure allocator" error="Initial synchronization with instances API failed" subsys=cilium-operator-azure

We update the documentation guidelines for new installations to assign the Contributor role to new Service Principals used for Cilium.
We also take the opportunity to:

Update Azure IPAM required privileges documentation.
Make it so users can now set up all AKS-specific required variables for a Helm install in a single command block, rather than have it spread over several command blocks with intermediate steps and temporary files.
Have the documentation recommend creating Service Principals with privileges over a restricted scope (AKS node resource group) for increased security.

Related: https://github.com/cilium/cilium-cli/pull/718.

Argh, I pushed the wrong commit. Will fix in a bit.

Ideally I would like to have these instructions backported at least to 1.11, but IIRC we never update the documentation associated to already stable releases (i.e. https://docs.cilium.io/en/v1.11/ is frozen to whatever state it was in at the time of 1.11.0).

Backport away. I think it's only https://docs.cilium.io/en/stable/ (distinct from https://docs.cilium.io/en/v1.11/) which is frozen.

Note to TopHat / backporter : this won't apply cleanly on top of v1.9 because of the Getting Started Guides rework. The changes should to k8s-install-helm.rst should be applied to k8s-install-aks.rst instead.

This is a documentation-only change, no need to run CI suite. Reviews are in, marking ready to merge.


Issues with project setup

Hi,
Everytime I install your library I got these errors
BTW my minimum target is iOS 15 !

I'm gonna need a sample project I'm afraid. Multiple other projects (not only mine) are using this without issue on iOS 13+ (and other  platforms) so it'll be some weird setup most likely.

@X901 maybe you're using old Xcode version (lower 13.2)?

@X901 apple back ported concurrency to iOS 13 only in Xcode 13.2: https://developer.apple.com/documentation/xcode-release-notes/xcode-13_2-release-notes#Swift
So there is no bug.

Oh good catch @anivaros and thank you for helping out! I had considered Xcode version but I had forgotten that the backport came later 👍👍👍


fix: logout if user not found

:tada: This PR is included in version 2.1.0-beta.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


The prompt should be in Chinese, please check the whole system

提示语应是中文，请全局自查

#275 Fix:i18n:modify language package, delete redundant keys, and modify incorrect keys


Community Provider #3

Weight the form to get quickly to easy answers, give explanation for others and a choice.

This is now in a new form


Make search API space aware.

To link a work item, user can search using text in search box. Currently it returns all possible work items irrespective of space.

Grey area. Not sure if we need this now.

Yes, We are going to make search API to consider space_id.
Task is in progress.


AWS::ElasticLoadBalancingV2::TargetGroup not supported ?

The resource type AWS::ElasticLoadBalancingV2::TargetGroup is not supported ?
config file looks like
resourceTypes = ["AWS::ElasticLoadBalancingV2::TargetGroup"]
endHour = 0
startHour = -8
endTimeStamp = "2017-08-21T01:01:01Z"
startTimeStamp = "2017-06-20T01:01:01Z"

tag.json file look like
{
	"TagFilters": [
		{
			"Key": "Name",
			"Values": ["tf-ws-tg"]
		}
	]
}

and the output
grafiti  delete -f example-tags-input.json
{"level":"info","msg":"Using config file: /home/foysal/.grafiti.toml","time":"2017-08-21T16:10:45-04:00"}
{"level":"info","msg":"using log level 'info'","time":"2017-08-21T16:10:45-04:00"}
{"level":"info","msg":"logging to stderr","time":"2017-08-21T16:10:45-04:00"}
Error: delete: rgta: get resources: InvalidParameterException: Unsupported ResourceType -
	status code: 400, request id: d0e07fa3-86ac-11e7-af7d-3f11a27350d4

Help is very much appreciated

The resource group tagging API does not support AWS::ElasticLoadBalancingV2::TargetGroup resources, according to the error message returned. Furthermore, grafiti only supports classic load balancers as of now. You won't be able to delete TargetGroups using grafiti until TargetGroup-specific API calls are implemented, and this feature is not on the roadmap.


fix for callback in release build

fix for [ERROR:flutter/shell/common/shell.cc(93)] Dart Error: Dart_LookupLibrary: library 'package:untitled/location_callback_handler.dart' not found.
By adding @pragma('vm:entry-point') before a class/ function, we let compiler know that the native code can access it

Changes already merged in PR #66
No need to merge this PR.


Fixes #25. Remove the deploy.root from the deployed file path

This looks good to me, going to wait until tomorrow to merge/release it.


Adding exponenctial backoff to all errors of request not only http 5xx

Tests are still failing...

I know but when i opened travis there was no error in the log :)
st 6. 12. 2017 v 18:36 odesílatel Jan Čurn<EMAIL_ADDRESS>napsal:

Tests are still failing...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Apifier/apify-client-js/pull/47#issuecomment-349716579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkTcT_yXq3Ct87-Rs62jgobgtHEdGjBks5s9tCKgaJpZM4Q37ko
.

https://github.com/mochajs/mocha/issues/3044 for tomorrow, mocha test succeeds but doesn't exit - bug or feature of new mocha v4

Yeah, I found this new feature of mocha the hard way in proxy-chain NPM :)


Beastmaster Offset

It offsets the menu of beastmaster (AKA it moves the actual position of the menu buttons to the left a ton, being in a different place than the visual button locations), I know it's this mod because I disabled it and Beastmaster reset, it happens in all rooms, and it is just these 2 mods.

Here is a video of what I am seeing: https://www.youtube.com/watch?v=eQ0Ff7IzG3A
It looks normal to me. Or can you point out where the bug happens in the video? It is also strange that it happens in all rooms. Camera scroll is disabled by default in one-screen rooms.
Maybe you can provide the debug logs as described in the section BUG REPORTS. There might be things that the game is complaining about in these logs.

Will do, I don't know where debug logs are though...

The relative paths are describes in the section BUG REPORTS. Your Rain World folder path is something like: ..\Steam\SteamApps\common\Rain World\

All the sudden when I need an example it wants to work... Thank you for helping though.


Derive working with single derived property, but failing with two

Summary
Have a hard time describing the issue, because if I had figured out what's exactly going on I would be doing a pull request instead of a bug report, however I do have a decently clean MVE:
const createItem = (id: string, store: any): any => {
  let itemProxy = proxy({
    id
  });
  derive(
    {
      // commenting out the `isSelected` derived property magically causes the `isHovered` property to work
      isSelected: (get) => {
        return get(store).selected === get(itemProxy).id;
      },
      isHovered: (get) => {
        return get(store).hovered === get(itemProxy).id;
      }
    },
    { proxy: itemProxy }
  );
  return itemProxy;
};

const store = proxy({
  selected: (undefined as unknown) as string,
  hovered: (undefined as unknown) as string,
  byId: {} as Record<
    string,
    {
      id: string;
      readonly isHovered: boolean;
      readonly isSelected: boolean;
    }
  >
});

store.byId.a = createItem("a", store);
store.byId.b = createItem("b", store);

const nextTick = (t = 0) => new Promise((resolve) => setTimeout(resolve, t));

console.group("setting hovered to item A");
store.hovered = "a";
await nextTick();
console.log("a.isHovered", store.byId.a.isHovered); // true
console.log("b.isHovered", store.byId.b.isHovered); // false
console.groupEnd();

console.group("setting hovered to item B");
store.hovered = "b";
await nextTick();
console.log("a.isHovered", store.byId.a.isHovered); // false
console.log("b.isHovered", store.byId.b.isHovered); // false, should be true
console.groupEnd();

Link to reproduction
https://codesandbox.io/s/laughing-gates-mo58dj?file=/src/index.ts

For whatever it is worth, when sync: true is passed to the derive the issue seems to not get triggered.

Hmmm, it sounds like a bug. Probably a tough one.
Looks like there are two derived states with circular structure.
Hope someone can dig into it.

Still trying to wrap my head around what's happening, but just going to share what I got:
After initialization of the store the pendingCount in the sourceObjectEntry for byId.b ends up as -4.
store.byId.a = createItem('a', store);
store.byId.b = createItem('b', store);

await time();

console.log(
  // added the getSourceObjectEntry function for debugging
  unstable_deriveSubscriptions.getSourceObjectEntry(store.byId.b).pendingCount
); // -4

What seems to happen is that at the time of the store.byId.a assignment store.byId.b of course does not yet exist, so markPending only gets executed for the already existing subscriptions.
Execution order as far as I understand it is:

store.byId.a assignment
markPending store.byId.a only
store.byId.b assignment
unmarkPending BOTH store.byId.a and store.byId.b

Thus waiting a tick between store.byId.a = and store.byId.b = causes the issue not to trigger.
store.byId.a = createItem('a', store);
await time();
store.byId.b = createItem('b', store);

A solution that might work is to make a shallow copy of the subscriptions before the subscription.promise = Promise.resolve().then, but I am far from sure whether that wouldn't have other unintended consequences. Definitely need to check out the entire library and run the unit tests against it at the very least, but would love some feedback whether that does or doesn't sound reasonable.

@DavidMulder0 Hey, have you figured this out? I am experiencing the same issue and its pretty hard to wrap the head around the source code, would be helpful if you can give me a headstart

I have the same problem as well! After a VERY cursory look, I'm not sure what the point of running without {sync: true} is. It seems like the difference is just:
if (notifyInSync) {
  unmarkPending(sourceObject)
} else {
  subscription.p = Promise.resolve().then(() => {
    delete subscription.p // promise
    unmarkPending(sourceObject)
  })
}

What's the objective of {sync: false}?

With sync, batching is disabled, which causes too many updates in some cases, possibly dropping performance.

Alright, that's reasonable. Just throwing {sync: true} into my code actually made a bunch of things crash. The workaround I'm using for now is
const state = derive({
  derived: (get) => {
     ...
     return {
       property1: ...,
       property2: ...,
     }
  }

I was also attempting derive state from 2 separate proxy objects. For that, I've just created a third proxy object, which I update with watch, which doesn't seem to have the same problems.

btw, here's an RFC related to this issue: #792

Transferred to: https://github.com/valtiojs/derive-valtio/issues/2


The header method does not work on client side react app

Overview
Follow up from https://github.com/Shopify/signage/pull/84
The header method described in the quilt rail doc has value on the server side render but does not have value on client side.
I am not sure what the solution is, but we should at least update the doc to included a serialization step when using header such as the example here.
Consuming repo

What repo were you working in when this issue occurred?

...
Labels

[ ] Add the Type: Bug label to this issue.

Area

[ ] Add any relevant Area: <area> labels to this issue

Scope

Is this issue related to a specific package?

[ ] Tag it with the Package: <package_name> label.

Checklist

[ ] Please delete the labels section before submitting your issue
[ ] I have described this issue in a way that is actionable (if possible)

The reason it doesn't work is because useRequestHeader uses the NetworkContext (which only exists on the server) directly. To make this work on the client we would need to do some kind of serialization shenanigans; either of all the headers on the request, which seems like overkill, or keeping track of the ones that have been used and serializing those.

To make this work on the client we would need to do some kind of serialization shenanigans;

Don't we do this already for the client in react-server-webpack-plugin. Is the issue that signage wasn't using the latest @shopify/react-server and @shopify/sewing-kit

Don't we do this already for the client in react-server-webpack-plugin. Is the issue that signage wasn't using the latest @shopify/react-server and @shopify/sewing-kit?

We don't currently serialize all of the requests headers, no. We just added serialization for the data sent by the rails server. This issue is specifically talking about headers accessed via useRequestHeader.

Note that serializing all request headers isn't actually desirable, we would want to do something like serialize only the ones that are used. Even then there are obvious issues with components that are conditionally rendered not being able to access the headers either way though, so we would need to document the "rules" for this well.

We don't currently serialize all of the requests headers, no. We just added serialization for the data sent by the rails server.

We call headers.merge(data) in rails server. Should we not be doing this?
https://github.com/Shopify/quilt/blob/ffd199ed67de3cadbc69e109fdd752f9394af84b/gems/quilt_rails/lib/quilt_rails/react_renderable.rb#L43

Doing so would means adding literally every header from the HTTP request

Why would this be grabbing every header? My understanding is that it only grabs the headers which the consuming app explicitly gives us.


Add integration tests for BTF relocations

We should add integration tests for BTF relocations. These could be one small program written in C for each relocation type (struct field, array field, bitfield, etc).
Each test should define and load its "target BTF", with the final layout for the thing being relocated and tested. Then it should have a local definition for the thing being relocated with an incompatible layout. The test should check that after relocation, the layout matches the target BTF.

I'm very interested in giving this a try. My only caveat is that I'm a few weeks out from having time for it as my life is wrapped up in Kubecon right now, so if there's anyone else who needs to take it in the meantime please do. Otherwise my intention will be to have a go at it after Kubecon.

Done, I think.


api docs: Document POST /mark_(all|stream|topic)_as_read.

Testing Plan: test-api, mypy and lint checks passed locally. Made sure that the docs display properly.

Merged, after a few small tweaks to the descriptions.  Thanks @YagoGG!


build with development mode set & dest folder fails

Version
3.0.0-beta.6
Reproduction link
https://github.com/capsur/cc-setup
Steps to reproduce
yarn build -- --mode=development --dest=test
What is expected?
Project is built in development mode and output goes into test folder
What is actually happening?
vue-cli-service build --mode=development --dest=test

-  Building for development...\node_modules\@vue\cli-service\lib\commands\build\index.js:69
            args[0][0].to = dest
                   ^

TypeError: Cannot read property '0' of undefined
    at config.plugin.tap.args (\node_modules\@vue\cli-service\lib\commands\build\index.js:69:20)
    at Object.tap (\node_modules\webpack-chain\src\Plugin.js:19:22)
    at api.chainWebpack.config (\node_modules\@vue\cli-service\lib\commands\build\index.js:68:33)
    at webpackChainFns.forEach.fn (\node_modules\@vue\cli-service\lib\Service.js:135:40)
    at Array.forEach (<anonymous>)
    at Service.resolveChainableWebpackConfig (\node_modules\@vue\cli-service\lib\Service.js:135:26)
    at Service.resolveWebpackConfig (\node_modules\@vue\cli-service\lib\Service.js:139:48)
    at PluginAPI.resolveWebpackConfig (\node_modules\@vue\cli-service\lib\PluginAPI.js:117:25)
    at api.registerCommand.args (\node_modules\@vue\cli-service\lib\commands\build\index.js:86:27)
    at Service.run (\node_modules\@vue\cli-service\lib\Service.js:129:28)
error An unexpected error occurred: "Command failed.
Exit code: 1

For comparison: vue-cli-service build --mode production --dest test works without any issues

I too am experiencing the same issue.
package.json
//snip
 "scripts": {
    "dev": "vue-cli-service build --mode development --dest builds/dev",
//snip

npm run dev  yields the same error as you reported.
I (however) have no luck when trying just vue-cli-service build --mode development --dest builds/dev (or just "... --dest dev" in case it was the path separator that was causing problems.)
Either reports the same error.


Plugin logs do not wrap

The plugin generates log output to /var/log/calico/kubernetes/calico.log but this log doesn't have any log wrapping which can lead to giant logfiles.
We should follow the example of the other Calico component logs, and put plugin logs in their own directory.
For example,
/var/log/calico/kubernetes/exec-plugin/current.log

The cheapo fix is to just use a RotatingFileHandler logger, rather than a FileHandler.

Used the builtin rotating file handler instead of the svlogd process. Logs fill at 10M and 5 rotations are saved.


Floating action button should be positionable in the upper leftish

I have widget (Icon + InkWell) that I position halfway outside of its parent using Transform. Widget is displayed correctly but the part of it that is outside of the parent does not receive onTap events.
@abarth

Yes, this is a deep issue that we haven't fully sorted through.  I'd be interested in learning more about your use case here to help sort out what we should do.  Can I come by and look at your app tomorrow?
@Hixie

Sure, I can show you tomorrow. I do have a work-around for it as well. Actual FAB if set as the MaterialPage.FloatingActionButton, well transformed, still stays clickable ( Probably because its parent is the full view port ). Anyway, I can calculate, based on view port height, how much I need to move the default page FAB to be where I need it to be.

Are you trying to position the FAB similar to what's in this image?
https://material-design.storage.googleapis.com/publish/material_v_4/material_ext_publish/0Bx4BSt6jniD7S2NiZlNhcDUxSTA/patterns_actions_fab_content2.png
If so, we just need to teach the FAB how to be positioned there.  The FAB needs to float above the toolbar and the body in order for it to be at the proper elevation anyway.

Sort of, in my case I have an image instead if the toolbar on top.

@HansMuller was working on this, but I think he's taking a break to make tabs more awesome.

Do we still plan to do this?
@HansMuller @Hixie

I think we should still do it although AFAIK we haven't had an app developer request it.

We have no current customers requesting this. We will close it until we have demand. This should be relatively easy to do once we decide to do it.

If a simple developer like me kindly requests this feature does that count as a "customer request" ?
:-)

I second this request. For my purpose, it feels more intuitive to have at the top right of the screen than the bottom right.

This can be done with the Scaffold's floationActionButtonLocation property and a custom FloatingActionButtonLocation class.
You should take a look at how the default locations are defined in packages/flutter/lib/src/material/floating_action_button_location.dart

@jerzykiler It does. Turns out we've implemented this since then though, as @HansMuller says. :-)

See https://docs.flutter.io/flutter/material/Scaffold/floatingActionButtonLocation.html


feat: upstream congr! from Mathlib

This is a preliminary step to upstreaming convert.
We should later think about combining this with the standard congr.
There is still a builtin problem here, that you can not use congr! (config := ...) without import Lean.Meta.Tactic.Congr!. We need to move the config structure into e.g. Init/MetaTypes.lean, and then an update-stage0, but I haven't got it to work.
This is stacked on top of #3671 and #3672, and I'll wait for those to merge.

Oh wow, I wasn't expecting congr! to be upstreamed.  That should be fine, but I've been thinking of simplifying it now that we've now seen it in action for a while in mathlib. (And I'm looking forward to congr one day being able to do everything congr! can do!)
By the way, I have an open PR to add that LawfulBEq instances are equal: https://github.com/leanprover-community/mathlib4/pull/11179

Oh wow, I wasn't expecting to see that congr! was being upstreamed! That should be fine, but I've been thinking of simplifying it now that we've now seen it in action for a while in mathlib. (And I'm looking forward to congr one day being able to do everything congr! can do!)
By the way, I have an open PR to add that LawfulBEq instances are equal: leanprover-community/mathlib4#11179

@kmill, I don't think it is super urgent, so if you think there is good reason to delay moving it to allow for a refactor, I think we can do that. I'm happy with moving it as is and updating later, however.

I don't have any good reason to delay merging it, and I'm not sure when I'd get around to refactoring it, so carrying on with upstreaming seems fine to me. (Thanks!)

We decided not to proceed at this point. @kmill is refactoring the Mathlib implementation in the meantime.


Add ratelimit to the API

Description
Current API has no ratelimiting, should be added before hosting it
Ideal solution
Implementing the slowapi lib might be a good way of solving this issue.

Can  i take this one

Of course! I'll assign you this issue

@ConnorAhern Lets wait for @gkydev to give us an update of his progress, since he was the originaly assigned to this issue.

Alright


Issue 1487 Improve TempDirBooter and Tmp related cleanup [in progress]

Pull Request Description
This pull request closes #1487

[ ]  Throw an exception in TempDirBooter if System.getProperty("java.io.tmpdir") == null
[x]  org.carlspring.strongbox.booters.TempDirBooter#createTempDir made private.
[x] Default Paths.get(propertiesBooter.getVaultDirectory(), "tmp") is not used - java.io.tmpdir is specified.
[x]  java.io.tmpdir locks using ILock instead of LockFile
[x] org.carlspring.strongbox.booters.PropertiesBooter#tempDirectory is dropped since it is not almost anywhere
[x] if (System.getProperty("java.io.tmpdir") == null) { System.setProperty("java.io.tmpdir", getVaultDirectory() + "/tmp"); } is dropped from org.carlspring.strongbox.booters.PropertiesBooter .

Acceptance Test

[x] Building the code with mvn clean install -Dintegration.tests still works.
[x] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[x] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[x] The tests in the strongbox-web-integration-tests still run properly.

Questions

Does this pull request break backward compatibility?

[ ] Yes
[x] No

Does this pull request require other pull requests to be merged first?

[ ] Yes
[x] No

Does this require an update of the documentation?

[ ] Yes
[x] No

Tasks

[ ] we should throw an exception in TempDirBooter if System.getProperty("java.io.tmpdir") == null (is it even possible ?)

[ ]  org.carlspring.strongbox.booters.TempDirBooter#createTempDir should be private
we should not use defaults as Paths.get(propertiesBooter.getVaultDirectory(), "tmp") - java.io.tmpdir has to be specified

[ ] we should not use defaults as Paths.get(propertiesBooter.getVaultDirectory(), "tmp") - java.io.tmpdir has to be specified

[ ]  java.io.tmpdir creation should be locked similarly to #1457 (see related task description)

[ ] org.carlspring.strongbox.booters.PropertiesBooter#tempDirectory should be dropped as it is not used almost anywhere

[ ] if (System.getProperty("java.io.tmpdir") == null) { System.setProperty("java.io.tmpdir", getVaultDirectory() + "/tmp"); } should be dropped from org.carlspring.strongbox.booters.PropertiesBooter - we shouldn't set up this value in Runtime.

Hi @TheKeySpammer thanks for your contribution!
Could you please fill in the template upon submitting the PR?
FYI, in future PRs you can also add your second comment as part of the Pull Request Description. :)

Hi @TheKeySpammer thanks for your contribution!
Could you please fill in the template upon submitting the PR?
FYI, in future PRs you can also add your second comment as part of the Pull Request Description. :)

My apologies. I will make amends ASAP and will keep this in mind for my future PRs

@TheKeySpammer ,
Could you please also confirm, if all the acceptance tests are passing (by checking those boxes as well)?

Hi @TheKeySpammer,
I noticed you have merged the upstream changes. Please checkout our Rebase vs Merge guide? We prefer rebase over merge as it removes the noise from the logs and makes it much easier to follow what has changed.
Would you mind resetting this PR to a9c927c and then doing a rebase? Thanks in advance! :)

How is this pull request coming along? Is it ready for revieing, @TheKeySpammer ? :)

I am almost done, but I am stuck with the first task. I asked for suggestion on the issue page but haven't received a response yet. I need a little help with that issue so that I can complete the pull request.

I am almost done, but I am stuck with the first task. I asked for suggestion on the issue page but haven't received a response yet. I need a little help with that issue so that I can complete the pull request.

Could this ever be null?

The value can be null only if changed at runtime. Otherwise this value is fetched by jre from OS.

The value can be null only if changed at runtime. Otherwise this value is fetched by jre from OS.

So, then it's reasonably safe to assume that this won't be null and we can ignore this. (@sbespalov , @TheKeySpammer , @bono007 : What are your thoughts on this?).
@TheKeySpammer : Could you please rebase your pull request? Thanks! :)

Should I remove TempDirBooter and all related code?

Should I remove TempDirBooter and all related code?

@TheKeySpammer yes please

@carlspring , can we merge this PR ?

Yes, thanks for reviewing and for all of your efforts, guys! :)

@TheKeySpammer : Thanks for your patience and understanding! :)


Wrong option values

Hi,
Although I am setting numberOfShards = 1 and numberOfReplicas = 0 at appsettings file, serilog continue to use default values 20 for the numberOfShards  and 10 for the numberOfReplicas. I attached appsettings and elasticsearch screenshots.
var conf = new ConfigurationBuilder()
                .SetBasePath(env.ContentRootPath)
                .AddJsonFile($"appsettings.{env.EnvironmentName}.json", reloadOnChange: true, optional: true)
                .Build();
Log.Logger = new LoggerConfiguration().ReadFrom.Configuration(conf)
                .Enrich.WithMachineName()
                .CreateLogger();

Be aware that it only applies to newly created indexes and that it needs to be available in the template mapping. So first thing to check is to see if the template has been altered to include your new settings. Then it will apply to a newly created index. You do have overwriteTemplate set to false in your code, so it will not update an already existing template which might be the cause of your issue.

Setting overwriteTemplate = true solved my issue. Thank you very much for your help.


Using dotnet core

Hi
I'm trying to change my project from Mono to dotnet on Linux, Windows and macOS.
I get this error on Linux:
Unable to load shared library 'intl' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libintl: kan ikke åbne delt objektfil: Ingen sådan fil eller filkatalog
   at Mono.Unix.Catalog.bindtextdomain(IntPtr domainname, IntPtr dirname)
   at Mono.Unix.Catalog.Init(String package, String localedir)

Why is the DLL not referencing the correct files on the OS ?
dotnet can not use the "Mono.Unix.dll.config" file. So how is this going to work ?

If I rename "libMono.Unix.so" to "libintl.so" it works. Is that the intention ?

That sounds like you might be trying to use a platform with an incompatible build of libc. What linux distro is it?

That sounds like you might be trying to use a platform with an incompatible build of libc. What linux distro is it?

I had the same problem, I notice that the solution of the person who made this issue only interferes in the execution of the program, the intenationalization does not work at all.
I'm using MX-Linux 23. I couldn't find the libintl.so library on the system, I only found this other file:


fixed duplicate key + engines syntax error in package.json

My editor was complaining about two errors in package.json:

typings key was duplicated.
engines key had an invalid value: array instead of object. As I don't know what the minimum supported node version is, I put "*".

Codecov Report

Merging #1093 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1093   +/-   ##
========================================
  Coverage    70.47%   70.47%
========================================
  Files            1        1
  Lines        14181    14181
  Branches      4789     4789
========================================
  Hits          9994     9994
  Misses        4187     4187

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 af51018...990022d. Read the comment docs.

Thank you!


Enable auto scan in notification handler

In integration mode the switch is an attribute of project.
In standalone mode the switch is by env var "ENABLE_HARBOR_SCAN_ON_PUSH"

keep open until integration with Admiral PMS is done.

Closing it as I have verified it on integrated mode.


trac_ik: 1.6.1-7 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository trac_ik to 1.6.1-7:

upstream repository: https://bitbucket.org/traclabs/trac_ik.git
release repository: https://github.com/traclabs/trac_ik-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.7
previous version for package: 1.6.1-6

Closing as this looks like it was superseded by #29399 (in the future, please close out old PRs when opening new ones).


Make updates for new compute studio criteria

@jdebacker I made a couple updates to these files to meet the new compute studio criteria. Mostly this just involved renaming the files, but I did make two substantive changes to get the tests to pass. I'll leave comments where I made these changes.

Thanks for the PR @hdoupe ! Merging.


sending messages

Hello! Is there any plan to support sending messages to the queue?

I don't have much time to devote to this client library since it's relatively infrequently used - but I would happily merge a PR that added the basic commands to send PUB (it wouldn't be that difficult).


[WIP] Update syntax for using from Swift3 project

I cannot use GPUImage from Swift3 project because of old public access modifier cannot be accessed from another module. So, I wanted to change public to open, along with this change I applied the latest Swift Syntax conversion.
I DID

🌟  Applied recommended setting changes.
🌟  Convert to Swift3 syntax.
⭐  a few modifications for covering auto-change mistakes.

for iOS.
IDIDNT

I didn't change for Mac OS.
I didn't change for sample projects.

I will close because fixes are not comprehensive and I think it is better that the owner change things around project settings.

You might have missed it, but I had been maintaining a swift3 branch that I just merged into the master. That should have been kept up to date with Swift 3 during the evolution, and should be correct for Mac, iOS, and Linux now.

Oh, thanks! I missed it!


Adding Static Objects

Is there a way to add static objects into the scene? i.e. immovable objects such as thin cylinders or rectangles that a rope or cloth can collide with?

Nevermind, it seems to be doable with just add_box, it seems that separate code is need to handle the collisions well.

@wilson1yan Could you please post your solution to add a box that handles collisions?


Bnd 6.2.0

Update bnd maven plugins to 6.2.0 and move to use the new jar and test-jar goals of
bnd-maven-plugin.
Closes https://github.com/assertj/assertj-core/pull/2506

cc: @rotty3000

thanks @bjhargrave!

@bjhargrave we have a different configuration in assertj-guava based on the maven-bundle-plugin.
I guess we could use the bnd-maven-plugin instead, right?

I guess we could use the bnd-maven-plugin instead, right?

Yes, I'll make a PR.


perf: reduce allocations in unused variable linter

Unlike #2471 I do have a reason and two data points that actually back this one up! I measured the most memory allocating functions using valgrind's DHAT tool while running a recent lean nightly on std4's biggest file (Std/Data/List/Lemmas.lean). The DHAT viewer shows that (among other things) this forEachExprWhere call is responsible for a significant chunk of allocations:

The initial count of total allocations was (a second run yielded almost identical numbers):
==3641472== Total:     2,524,478,041 bytes in 964,045 blocks

Judging from the doc-string in the implementation of forEachExprWhere it should only be favored over forEachExpr if the proposition (in this case isFVar) doesn't hold for many subterms. However there are of course a ton of subterms that are free variables here. So I decided to try and switch this to forEachExpr instead which yielded:
==3644111== Total:     1,750,132,393 bytes in 952,715 blocks

on the same file, the allocation chunk also disappeared from my measurements. I furthermore measured std4 compilation time and did get a measurable speedup in:
before:
lake build  369.35s user 14.23s system 446% cpu 1:25.95 total

after:
lake +lean4 build  288.33s user 12.46s system 436% cpu 1:08.92 total

I thus again request someone with privileges to give the bench run a try^^

✅ Mathlib branch lean-pr-testing-2491 has successfully built against this PR. (2023-08-31 05:27:37)

Here are the bench results from Mathlib: http://speed.lean-fro.org/mathlib4/compare/93695581-e592-41ad-9a6a-53fe2cce9e75/to/5b225066-90b6-4cd2-94f1-9aabc1be69ef. Seems okay, saves 0.6% wall-clock, essentially all from linting.

Scott, did you use your personal API key for the bot again?

Nice analysis. We should point this out in the forEachExprWhere docstring as well, not just the module docstring. But that can go into a different PR.

@Kha, I wonder why linting did not show as a significant change? The change is well above the 10 standard deviations (its 85.6 stddev) and 1% threshold (its 12.8%) in the formula.


Issues with commons-csv:1.5.2-marklogic in mlcp 11.0.0

When I try to run a mlcp task in gradle using mlcp:11.0.0, I get the following error:
Could not resolve all files for configuration ':mlcp'.
   > Could not find org.apache.commons:commons-csv:1.5.2-marklogic.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/apache/commons/commons-csv/1.5.2-marklogic/commons-csv-1.5.2-marklogic.pom
       - https://developer.marklogic.com/maven2/org/apache/commons/commons-csv/1.5.2-marklogic/commons-csv-1.5.2-marklogic.pom
     Required by:
         project : > com.marklogic:mlcp:11.0.0
   > Could not find org.apache.commons:commons-csv:1.5.2-marklogic.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/org/apache/commons/commons-csv/1.5.2-marklogic/commons-csv-1.5.2-marklogic.pom
       - https://developer.marklogic.com/maven2/org/apache/commons/commons-csv/1.5.2-marklogic/commons-csv-1.5.2-marklogic.pom
     Required by:
         project : > com.marklogic:mlcp:11.0.0 > org.apache.jena:jena-arq:2.13.0

This is the build.gradle file:
plugins {
  id 'com.marklogic.ml-gradle' version '4.5.1'
}

repositories {
  mavenCentral()

  maven { url "https://developer.marklogic.com/maven2/" }
}

configurations {
  mlcp
}

dependencies {
  mlcp "com.marklogic:mlcp:11.0.0"
}

task sampleTask(type: com.marklogic.gradle.task.MlcpTask) {
  classpath = configurations.mlcp
  command = "IMPORT"
  database = "Documents"
  input_file_path = "./dataSource.json"
  input_file_type = "delimited_json"
}

It works when I use om.marklogic:mlcp:<IP_ADDRESS>

Working on it. Thanks for filing the issue!

commons-csv-1.5.2-marklogic now presents under https://developer.marklogic.com/maven2/org/apache/commons/commons-csv/1.5.2-marklogic/, verified that this issue has been fixed. Closing it. Thanks again for filing!


Setup simple workflow

... to verify that PRs build as expected.
This was created with the auto-setup by GitHub Actions.
Flags for batch-mode and avoiding artifacts download logs were added.
Currently the master branch does not build successfully.

Thanks!


usleep returns ESTOP when schedule timer failed

What problem does this PR solve?
Issue Number:
Problem Summary:
_add_sleep_event失败后，bthread_usleep并没有真正sleep，只是重新调度了，这时候应该返回错误。
What is changed and the side effects?
Changed:
Side effects:

Performance effects(性能影响):

Breaking backward compatibility(向后兼容性):

Check List:

Please make sure your changes are compilable(请确保你的更改可以通过编译).
When providing us with a new feature, it is best to add related tests(如果你向我们增加一个新的功能, 请添加相关测试).
Please follow Contributor Covenant Code of Conduct.(请遵循贡献者准则).

LGTM


Configure which schemas models are materialized in

Semi-related: https://github.com/analyst-collective/dbt/issues/198
This would be useful for both organization and permission configuration

+1!

This would be great to have in addition to default target as right now in profiles.yml .
I imagine this to be something like a configuration value for model.
{{
  config(
    materialized = 'table',
    schema = 'dbt'
  )
}}```

`schema` keyword is also used for `schema.yml` but should be clear enough from context what is being referenced.

Would it be possible to pass the schema as either a string or a dictionary that was keyed on target name (ie, dev/prod) this would potentially allow for schema targets to be configured without breaking multiple environments?

This directly approaches my use case @ https://getdbt.slack.com/archives/C0VLZM3U2/p1497459181879656

Happy to report that this has been merged into development and will be available in dbt 0.9.0.
We'll be publishing our second 0.9.0 alpha release (including this feature) in the next day or two -- please let me know if you're interesting in trying it out!
Relevant docs: https://dbt.readme.io/v0.9/docs/using-custom-schemas


[Extensions] Added Descriptions & Consideration for each extensions

Description
This PR fixes #1703
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Captain @vishalvivekm, I have added this to the agenda items for discussion on the Website Dev call.


Documentation failure

sphinx-argparse depends on CommonMark>=0.5.6 while ReadTheDocs uses recommonmark, which depends on CommonMark<=0.5.4.
The latter is installed later, so ReadTheDocs is failing here:
Command-Line Arguments
~~~~~~~~~~~~~~~~~~~~~~

.. argparse::
   :ref: fmriprep.cli.run.get_parser
   :prog: fmriprep
   :nodefault:
   :nodefaultconst:

Opened an issue: rtfd/recommonmark#78

Even if they do release an update, I think we're going to have an issue as long as something induces pip to try to upgrade setuptools, which fails sometimes, maybe (see fix-docs builds)?
I guess as long as the failures are stochastic instead of permanent, we can just keep rebuilding until something works.

Seems to be building (http://fmriprep.readthedocs.io/en/fix-docs-579/), but now we get a bunch of these:
WARNING: /home/docs/checkouts/readthedocs.org/user_builds/fmriprep/checkouts/fix-docs-579/docs/workflows.rst:15: (WARNING/2) Exception occurred in plotting workflows-1
 from /home/docs/checkouts/readthedocs.org/user_builds/fmriprep/checkouts/fix-docs-579/docs/workflows.rst:
Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/nipype/sphinxext/plot_workflow.py", line 464, in run_code
    exec(code, ns)
  File "<string>", line 25, in <module>
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/fmriprep/workflows/base.py", line 158, in init_single_subject_wf
    ignore_aroma_err=ignore_aroma_err)
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/fmriprep/workflows/epi.py", line 143, in init_func_preproc_wf
    name='discover_wf')
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/fmriprep/workflows/confounds.py", line 62, in init_discover_wf
    percentile_threshold=.05),
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/niworkflows/common/report.py", line 45, in __init__
    super(ReportCapableInterface, self).__init__(**inputs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/niworkflows/nipype/algorithms/confounds.py", line 487, in __init__
    super(TCompCor, self).__init__(*args, **kwargs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/niworkflows/nipype/algorithms/confounds.py", line 376, in __init__
    super(CompCor, self).__init__(*args, **kwargs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/niworkflows/nipype/interfaces/base.py", line 774, in __init__
    self.inputs = self.input_spec(**inputs)
  File "/home/docs/checkouts/readthedocs.org/user_builds/fmriprep/envs/fix-docs-579/lib/python3.5/site-packages/niworkflows/nipype/interfaces/base.py", line 364, in __init__
    super(BaseTraitedSpec, self).__init__(**kwargs)
traits.trait_errors.TraitError: Cannot set the undefined 'pre_filter' attribute of a 'TCompCorInputSpecRPT' object.

Seems like nipype is outdated in readthedocs, isn't it? @effigies

Might need to upgrade to niworkflows>=0.1.4. #587 includes it, but the tests are still running. (Crashed because pypi package wasn't ready when they started.)


Mangrove harvester tooltip inaccurate?

Hello. first off I'd like to thank you for this awesome mod.
Secondly, the tooltip on my mangrove harvester says i should be getting .5/s Green Wood & .1/s Wood yet i only get one or the other every 10 seconds or so. is this intended?
also since mangrove harvesters are 'burner' only machines is there any plans on making an electric upgrade later? if not would you consider making the better fuel types make it run faster? like use their vehicle acceleration/top speed rates?
thanks in advance.

I found this odd during development. I suspect a bug in factorio that's outside of my control, but maybe I missed something. I've raised the subject here https://forums.factorio.com/viewtopic.php?f=34&t=63734 and will see what other modders/devs say.
Regarding mangrove harvesters being burners: this was largely to justify them having no module slots, as well as to add some logistical challenge in supplying fuel. Since the output can also be used as fuel, and a single raw wood provides a lot of energy compared to a single solar panel, it could be overpowered as an infinite resource. Even with all the extra infrastructure needed for steam engines. Modules really throw off the balancing for it. It also happens to be realistic, logging is done by big vehicles.
There isn't a mechanic in factorio to have a mining benefit equivalent to vehicle acceleration. I could do something with fuel categories though. So how about an "Atomic Mangrove Harvester" which takes uranium cells: gives a good speed boost and lasts a very long time, but has the added logistical challenge that you have to recover spend fuel cells!
"Atomic Mangrove Harvester" should be the name of a rock band 🤣

There isn't a mechanic in factorio to have a mining benefit equivalent to vehicle acceleration. I could do something with fuel categories though. So how about an "Atomic Mangrove Harvester" which takes uranium cells: gives a good speed boost and lasts a very long time, but has the added logistical challenge that you have to recover spend fuel cells!

I've not checked but if your harvesters are of the miner class then you can make a set of research specialized based on their group to increase their efficiency and/or speed.  If they are some other form of entity then it's less simple.
I actually quite like the idea of them being slow harvesting, after all I think about it as the trees regrowing and that takes time, if you want more then make more water area or use a wood mod (I use AngelBob's with algae for making wood-like things for most uses for example so I'd actually quite prefer early game trees like that to be fairly slow).

I actually quite like the idea of them being slow harvesting, after all I think about it as the trees regrowing and that takes time, if you want more then make more water area or use a wood mod (I use AngelBob's with algae for making wood-like things for most uses for example so I'd actually quite prefer early game trees like that to be fairly slow).

That's very much the spirit of it. As a natural resource it needs sustainable management and in real life mangroves are most susceptible to land reclamation.
What I want is to make people think about obliterating the waterways with landfill... It should be a trade off and maybe some players will landfill only what they need. I suspect otherwise once people "beat" the maze and remove it, the gameplay might revert too much to vanilla and cause a loss of interest. On the other hand I don't want to punish landfill as a late game reward. It'll be interesting to see how people react to the current balance. Probably best to adjust from there. It's much harder to justify removing a mining tier than adding a new one.


Not compiled with GPU offload support

What is the issue?
Trying to use ollama like normal with GPU. Worked before update. Now only using CPU.
$ journalctl -u ollama
reveals
WARN [server_params_parse] Not compiled with GPU offload support, --n-gpu-layers option will be ignored. See main README.md for information on enabling GPU BLAS support | n_gpu_layers=-1

I do not manually compile ollama. I use the standard install script.
Main README.md contains no mention of BLAS

OS
Linux
GPU
Nvidia
CPU
Intel
Ollama version
0.1.38

Hi @oldmanjk sorry about this. May I ask which model you are running? and on which GPU?

I think I got the same issue.
Running llama2:latest and llama3:latest on my GTX 1660 SUPER.
Worked before, now I updated to the latest Ollama and it seems that it mostly uses CPU which is way slower.

Has anybody an idea of the code we need to remove to stop it ignoring our  num_gpu settings (again, sigh...)?

It's at the bottom of  llm/memory.go:
        //if memoryRequiredPartial > memoryAvailable {
        //      slog.Debug("insufficient VRAM to load any model layers")
        //      return 0, 0, memoryRequiredTotal
        //}

got the same issue here on openSUSE Tumbleweed. one thing i noticed is, it uses the GPU for a moment then gone...
Screencast_20240518_221101.webm

We've recently introduced ollama ps which will help show how much of the model has loaded into VRAM.
We've fixed a few bugs recently around num_gpu handling in some of our prediction logic, but I'm not sure that addresses your comment @jukofyork.   Can you explain what you're trying to do?  The goal of our prediction algorithm is to set num_gpu automatically based on the available VRAM.  There is a minimum requirement for models and if we can't even allocate that minimal amount, then we will fall back to CPU.  If we can satisfy the minimal amount, but not load the full amount, we will partially load on the GPU.  Are you trying to set a lower value to preserve more space on the GPU, or did we predict incorrectly and you're trying to specify more layers?  If our prediction was right, and you still push higher, we'll likely OOM crash by trying to allocate too many layers on the GPU.

@oldmanjk the log you attached above seems to show a 2nd attempt where we fell back to the runners/cpu_avx2/ollama_llama_server CPU, after most likely unsuccessfully running on the GPU.  Can you share a complete log so we can see what went wrong?
sudo systemctl stop ollama
OLLAMA_DEBUG=1 ollama serve 2>&1 | tee server.log

Hi! Here is my equivalent issue and log file.  See main README.md for information on enabling GPU BLAS support | n_gpu_layers=-1 tid="126402163820352" timestamp=1721613337
INFO [main] build info | build=3337 commit="a8db2a9ce" tid="126402163820352" timestamp=1721613337
INFO [main] system info | n_threads=6 n_threads_batch=-1 system_info="AVX = 1 | AVX_VNNI = 0 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | AVX512_BF16 = 0 | FMA = 1 | NEON = 0 | SVE = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | SSSE3 = 1 | VSX = 0 | MATMUL_INT8 = 0 | LLAMAFILE = 0 | " tid="126402163820352" timestamp=1721613337 total_threads=6
INFO [main] HTTP server listening | hostname="<IP_ADDRESS>" n_threads_http="6" port="34295" tid="126402163820352" timestamp=1721613337

ollama-cleaner.log

We've fixed quite a few prediction bugs since 0.1.38, so I'm going to close this one out.  If you're still hitting OOM's on 0.3.4, please share what model you were trying to load, and the server log and I'll reopen.

I'm having this issue when trying to run llama3.1:70b with an rtx 3080 and 64GB RAM. It seems that the ollama_llama_server.exe shipped with the latest windows download from the website doesn't have GPU offloading enabled? I get the same error described above.
WARN [server_params_parse] Not compiled with GPU offload support, --n-gpu-layers option will be ignored. See main README.md for information on enabling GPU BLAS support | n_gpu_layers=-1 tid="107816" timestamp=1726533930

I'm having this issue when trying to run llama3.1:70b with an rtx 3080 and 64GB RAM. It seems that the ollama_llama_server.exe shipped with the latest windows download from the website doesn't have GPU offloading enabled? I get the same error described above.
WARN [server_params_parse] Not compiled with GPU offload support, --n-gpu-layers option will be ignored. See main README.md for information on enabling GPU BLAS support | n_gpu_layers=-1 tid="107816" timestamp=1726533930i

i also have the same issue :(

There is definitely an issue with the latest binaries, at least on windows. My ollama instance running on my linux server with a gtx 1070 and 32gb ram is able to run llama 3.1 with an excel file, offloading accordingly and providing a response, but my windows PC with RTX 3080 and 64GB ram is giving me an out of memory error.

@Shadowfita @KaloyanGeorgiev99 can you share more complete server logs?   This scenario most likely occurs when we're trying to recover from a prior crash failing to start the GPU runner, then fall back to the CPU runner but incorrectly pass a GPU related flag.  I'd like to see what the earlier error(s) were leading up to this.

If you're still seeing the problem, please upgrade to the latest release, and if that doesn't clear it up, share a more complete server log so I can see why the prior runner crashed and I'll reopen the issue and investigate.


Duplication bug with Lootr chest in minecart

So far every Lootr chest minecart I've come across in Enigmatica 6 has reset its inventory to its initial state after closing the inventory, leading to infinite duplication of its dungeon loot.
1.

2.

3.

If you aren't using version <IP_ADDRESS>, please report this to the Enigmatica 6 developers as they should update the version available in the pack. A fix for this was released over three weeks ago.


Prepare for Senzing release 2.0.0

See https://github.com/Senzing/docker-compose-demo/issues/96

Pull requests:

https://github.com/Senzing/ibm-openshift-guide/pull/23


hyper-v machine create fails on mobaxterm

its a really unhelpful error too:
[svend_000.big] ➤ ./machine.exe create --driver=hyper-v test
time="2015-02-09T10:23:09+10:00" level="info" msg="Creating CA: C:\\Users\\svend_000\\.docker\\machines\\ca.pem"
time="2015-02-09T10:23:09+10:00" level="info" msg="Creating client certificate: C:\\Users\\svend_000\\.docker\\machines\\.client\\cert.pem"
time="2015-02-09T10:23:10+10:00" level="error" msg="Error creating machine: exec: \"\": executable file not found in %PATH%"
time="2015-02-09T10:23:10+10:00" level="warning" msg="You will want to check the provider to make sure the machine and associated resources were properly removed."
time="2015-02-09T10:23:10+10:00" level="fatal" msg="Error creating machine"
                                                                                ✘
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[2015-02-09 10:23.10]  ~
[svend_000.big] ➤ pwd
/home/mobaxterm
                                                                                ✔
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[2015-02-09 10:26.09]  ~
[svend_000.big] ➤ cd Downloads
                                                                                ✔
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[2015-02-09 10:26.11]  ~/Downloads
[svend_000.big] ➤ mv docker-machine_windows_amd64\ \(1\).exe docker-machine_windows_amd64-nightly.exe
                                                                                ✔
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────
[2015-02-09 10:26.28]  ~/Downloads
[svend_000.big] ➤ ssh
ssh                    ssh-agent.exe          ssh-keyscan.exe        sshpass.exe
ssh.exe                ssh-copy-id            ssh-nocompression      ssh-pkcs11-helper
ssh-add                sshd.exe               ssh-noencryption       ssh-pkcs11-helper.exe
ssh-add.exe            ssh-keygen             ssh-pageant.exe
ssh-agent              ssh-keygen.exe         sshpass

I think this is even more reason to get a "recommended" environment up for each platform.  I'm not sure we will be able to support every possible combination of shell and terminal in the wild.  That error looks path related to me.

@SvenDowideit can you run with --debug? There are some log.Debugfs that would be helpful, thanks.

agreed wrt the recomended env - once I get any one of them working with Hyper-V, I'll document that :)
@jeffmendoza with --debug
[svend_000.big] ➤ ./machine.exe --debug create --driver=hyper-v test510
time="2015-02-10T12:42:15+10:00" level="debug" msg="[executing ==>] :  @(Get-Command Get-VM).ModuleName"
time="2015-02-10T12:42:15+10:00" level="debug" msg="[stdout =====>] : "
time="2015-02-10T12:42:15+10:00" level="debug" msg="[stderr =====>] : "
time="2015-02-10T12:42:15+10:00" level="error" msg="Error creating machine: exec: \"\": executable file not found in %PATH%"
time="2015-02-10T12:42:15+10:00" level="warning" msg="You will want to check the provider to make sure the machine and associated resources were properly removed."
time="2015-02-10T12:42:15+10:00" level="fatal" msg="Error creating machine"

@ahmetalpbalkan @johngossman Can you please take a look at this and see if you can dupe?

cc: @jstarks @jhowardmsft

Fixed with https://github.com/docker/machine/pull/2658


404 error to GCC MCAS page

Is the documentation / links still in progress?
They're currently hitting a 404.

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

ID: 24ac1d0d-1f97-1bbf-732b-c65bb89170b1
Version Independent ID: a28b78cc-7b30-b5f2-29a5-dd35111e05a0
Content: Microsoft Cloud App Security for US Government GCC High
Content Source: CloudAppSecurityDocs/editions-cloud-app-security-gcc.md
Service: cloud-app-security
Product: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@cperrin10  Thanks for reporting the issue. We've submitted a documentation change based on your suggestion, and the updated article should be live by tomorrow. Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.


[website] Open Tech lead - Core role

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

Preview: https://deploy-preview-42189--material-ui.netlify.app/careers/react-tech-lead-core/

We target role IC6 or above, should it maybe be IC5 and above?

@mnajdova I think we need to start thinking about how we will reopen this role. Docs-infra and Core Tech Lead looks to me like two full-time roles. Today, Jan covers both responsabilites, but I think this is overwhelming (impossible to cover by a single person), so there is a need to pick a side.

As a side note on this, as it's related to staffing. I think we can define "correctly staffed in the core team" with:

2020 level of all the metrics from the KPI board. https://www.notion.so/mui-org/KPIs-1ce9658b85ce4628a2a2ed2ae74ff69c#c02a5c878ee846e1b23b2918a5bdd4aa.

For example, (for the ratio and PR volume): https://tools-public.mui.com/prod/pages/communityPerMonth

(issue starting around 2021).

The sum of the contributions stats of the maintainers match the sum of what we could sustain in the past (during the high growth phase in % market share in React, for example, this was sustained from 2018 to 2021:

2a. https://ossinsight.io/analyze/eps1lon

2b. https://ossinsight.io/analyze/oliviertassinari

(interactions happening on Twitter or Stack Overflow counts very much as well, but it's not visible in ossinsight, internal org Slack or internal meetings should likely be significantly discounted, it's not useful by the community, especially when discussing controversial topics, it's precisely the value of having this open).
The sum average was above 1,000 issue comments and 1,000 PR reviews per month (retaining high-quality contributions, no making tradeoffs on this). So this level would be outstanding IMHO.
I think it was amazing we could do this with only two people back in the days, the fewer people you need to do this, the fewer the information is spread between minds, the fewer connections are lost, the better the depth of the execution. So overall, it's not just about target, but also getting there with the smallest possible team.
Now, I don't think we can realistically reproduce this, not with the current organization, it was an anomaly. It's really hard to achieve this with a team of two: I assumed that both Sebastian and I were working 80+ hrs/week, we were not really paid for it during those times (what mattered was a sense of ownership and having a lot of fun), and we were both Vercel hiring targets.
It's also worth mentioning that other projects have found success with 50% of those metrics. Instead, they chose to spend the extra time on Twitter or with the community on Reddit, conferences, etc. So those contributions metrics are definitely not the only way.
From a team organization perspective, decisions were very centralized, I would green-light almost everything, this allowed us to move fast and with decisiveness, I would make mistakes sure, but correct them quickly. Our timeout to merge PRs without reviews was 3 days, this was going faster as well than today.

I don't know exactly where we are with this 2. metrics today. I think we should measure this. This should be possible with a custom OssInsight SQL query / API request. Since Material UI focus got split into Base UI + Pigment CSS + MUI System + Joy UI + Material UI, all of "Core" counts.
As a target, I think we could start to set a target at 50% of this so 500/month. If we are above, great, them to me it's only a matter of keep up with all of those GitHub issues, we don't have that many open/month, and yet, it starts to go over 2k. If we are below, we work on filling the gap, and then see how this feels. See if we need to go further or it's enough.
Task created: