Missing Close() in gvisor-tap-vsock, or tcpproxy bug?

We cannot use the latest github.com/inetaf/tcpproxy commit because of https://github.com/containers/gvisor-tap-vsock/commit/61dc4e1eb260427d9a39ccaeeb75fe85be7dcccc which causes a regression in podman https://github.com/containers/podman/issues/23616
My feeling is that this revert is either hiding a gvisor-tap-sock bug which has been present for a long time, or it's avoiding a newly introduced bug in inetaf/tcpproxy. In either cases ,it would be good to understand better what caused the issue leading to the revert. The podman bug has a reproducer for it.

This can be reproduced with podman machine by following these steps (I tested on a mac):

if podman was installed with their installer, replace /opt/podman/bin/gvproxy with the binary you want to test
podman machine stop && podman machine start
podman run -it -rm -p 8111:8111 ubi9
in the container, yum install nmap-ncat followed by nc -l -k -v 8111
in another terminal on the mac, echo hello | nc localhost 8111
if this command does not return without ctrl+c, then you are seeing the bug
you can also run it multiple times in a row, and then check  lsof -nP -iTCP | grep 8111, there will be multiple lines when the bug occurs

@cfergeau I make some investigation on this, it look like that problem is in recent version of /inetaf/tcpproxy
The problem is in
https://github.com/inetaf/tcpproxy/blob/3ce58045626c8bc343a593c90354975e61b1817a/tcpproxy.go#L404-L408
If you look on https://github.com/containers/gvisor-tap-vsock/commit/61dc4e1eb260427d9a39ccaeeb75fe85be7dcccc it is removing second <-errc, which is added in newer version. For me, that second channel receive is never resolve, so function HandleConn is never return and connections is never closed.
So if I remove that second <-errc in newest version it fix the issue.
Look like one of go proxyCopy calls is never returns(put anything in the errc channel), going to look deeper in to the code


Map Area Actually Accessible

Liberty Falls grassy area outside bowling alley is actually accessible and contains an possible EE interactable item

We should update the map SVG to remove the coloured hashing.

will remove the hashes


Rename Norm Step 'norm' to 'transform'

Current norm step not only to normalization but a lot of transforming supported actually. By adding 'shifu transform' and which is the same as 'shifu norm'

DONE in develop branch


Customize the output folder path based on probem tag list

🚀 Feature Proposal
For example, if problem A has the following tags:
BFS, DFS ...

User could configure that the output folder for this problem, for example, the solution code file, will reside in bfs folder
Motivation
This is to help users to categorize the problems better

It turns out that this is already achieved based on what we have, ref: https://github.com/LeetCode-OpenSource/vscode-leetcode/wiki/Customize-the-Relative-Folder-and-the-File-Name-of-the-Problem-File#customize-for-the-output-folder-name


How to get finer widget slider control? In particular for HoloMaps and DynamicMaps

I would like to have finer control over the slider for HoloMaps and DynamicMaps. If my HoloMap is for example comprised of 500 objects, it is not possible (?) to jump from one image to another by incremental values. I would at least like to be able to manually input this value next to the slider. Is that possible in any way?
Same example as in Issue #2970, with n_a=500:

import holoviews as hv
import numpy as np
hv.extension('bokeh')

# create HoloMap object with varying slope
n_a = 500 # number of slope changes
lower_slope_limit = 0.4
upper_slope_limit = 1.2
redim_range = np.r_[np.repeat(9.0,15),np.array([10.0,12.0, 14.0, 17.0, 21.0])]

# let a vary between lower and upper_slope_limit
a_var = np.linspace(lower_slope_limit,upper_slope_limit,n_a)
y_list = []

for i in range(n_a):
    y_list.append(hv.Curve((x,fct(a_var[i],x,b))))
# create HoloMap object
dict_y = {i:y_list[i] for i in range(n_a)}
hmap_y = hv.HoloMap(dict_y, kdims = ['a'])

hmap_y

Even by heavily zooming into the Jupyter Notebook, moving the mouse by one pixel results in a jump of 4 units on the slider. Although I can highlight the slider's output values, I cannot change them with keyboard input.
Same issues with DynamicMaps.

Seems to work on my Windows machine using the arrow keys.

It indeed works for me too with the arrow keys! Thanks! Not sure why I didn't think of trying it that way...


Can optimize.minimize(obj_func, x0) handle an x0 which is a dictionary ?

This is not a bug report.
As indicated in the title, is it possible to enter a hashtable of parameters to optimize ? If not, could you please kindly tell me if you know some other packages can handle this ?
Like:
<<x0 = {'i': 1, 'j': 2, 'k': 3}
new_x = optimize.minimize(obj_fun, x0, method ='L-BFGS-B', bounds=x_b,
                           tol=tol)>>

Regards,
Niko

The lmfit package might meet your needs. But you'll need to convert your dict to a Parameters instance first.


Redirect DebugSession logs to BSP client

In DebugAdapterPlugin (the sbt plugin) the startMainClassDebugSession, and similar tasks, start the DebugSession in a future then respond with its address. The thread is started here.
The DebugSession logs with the stream.value.log but that does not log anymore after the task returned. Ideally those logs should be redirected to the BSP client that started the debug session.
A potential solution is to use sbt BackgroundsJobServive to manage the lifetime of the server. By doing so we should have a logger that survives the task. Will it redirect to the BSP client though? If not that could be reported and implemented in sbt.

Fixed by https://github.com/scalacenter/scala-debug-adapter/pull/266


numpy not in requirements.txt

numpy not in requirements.txt ...you should add it in.

Hi @exquest I am no longer actively maintaining this project, though PRs are welcome!


AkNN Queries

I have a set of 1MM points. For each point, I want to find its 5 nearest neighbours. (The All nearest neighbours problem.)
I can do this in traditional postgresql + PostGIS extensions:
SELECT *
FROM (
  SELECT
          a.id,
          b.id AS nth_id,
          ST_Distance(a.geom, b.geom) AS distance,
          ROW_NUMBER() OVER (PARTITION BY a.id ORDER BY ST_Distance(a.geom, b.geom)) AS nn_row
  FROM a, b
  WHERE a.id <> b.id
) c
WHERE c.nn_row <= 5

While I was able to get this query to work with Spatial SQL for a small set, it died on 10K records, which suggests I'm not building a scalable solution.
Question: is there a recommended approach? Is there an index that lends itself well to AkNN queries? Does Spatial SQL even add indexes itself? What about spatial joins?

@jiayuasu is that your way of saying the query above is basically the best I'm going to be able to do using GeoSparkSQL?

@mklaber The query you gave me doesn't seem to be a spatial query except you call "ST_Distance". So its performance depends on Spark itself.
Your query uses PARTITION BY, ORDER BY, and a self inequality join. This query is very slow for sure since the data can be huge.


Calendar Dates not visible on some devices for Adhoc build

The following informations are requested in a bug report
I am using this library since last 1 and half year. Scenario is as follows :
Some of the iOS distribution build dose not show dates at all. It's an working code till last XCode update. One More thing to mention here is, I'm distributing build to client side (.ipa) it only happens at client end, at our end this scenario never happened. Because of this it's more difficult to solve

Integration method.(cocoapods)

Full steps to reproduce. Regular way just opened calendar.

Device modal and iOS version.  e.g. iPhone 6s/X/7+ iOS12.0/12.0.1

Xcode version.  e.g. Xcode 10.0

FSCalendar version. e.g. FSCalenda 2.7.9

below is the implementation

FSCalendar calendar = [[FSCalendar alloc] initWithFrame:CGRectMake(0, 0, self.view.frame.size.width, self.view.frame.size.height)];
calendar.backgroundColor = ColorName.altWhiteColor;
calendar.dataSource = self;
calendar.delegate = self;
calendar.pagingEnabled = NO; // important
calendar.allowsMultipleSelection = enableMultiSelection;
calendar.firstWeekday = 1;
calendar.swipeToChooseGesture.enabled = YES;
UIPanGestureRecognizer scopeGesture = [[UIPanGestureRecognizer alloc] initWithTarget:calendar action:@selector(handleScopeGesture:)];
[calendar addGestureRecognizer:scopeGesture];
calendar.appearance.headerTitleColor = ColorName.altBlackColor;
calendar.appearance.headerTitleFont = [UIFont fontWithName:FONT_REGULAR size:myDelegate.FONT_MEDIUM];
calendar.appearance.headerDateFormat = @"MMMM yyyy";
calendar.appearance.weekdayFont = [UIFont fontWithName:FONT_REGULAR size:myDelegate.FONT_MEDIUM];
calendar.appearance.weekdayTextColor = ColorName.altBlackColor;
calendar.appearance.separators = FSCalendarSeparatorInterRows;
calendar.appearance.todayColor = ColorName.altBrownColor;
calendar.placeholderType = FSCalendarPlaceholderTypeNone;
calendar.appearance.borderSelectionColor = ColorName.altBrownColor;
calendar.appearance.titleSelectionColor = ColorName.altBlackColor;
calendar.appearance.selectionColor = ColorName.altClearColor;
calendar.calendarHeaderView.needsAdjustingMonthPosition = true;
calendar.calendarHeaderView.
calendar.appearance.caseOptions = FSCalendarCaseOptionsWeekdayUsesSingleUpperCase|FSCalendarCaseOptionsHeaderUsesDefaultCase;
[self.view addSubview:calendar];
self.calendar = calendar;

Does this happen if you distribute the app with Xcode 9.4?

Nope, it started after updating XCode to 10.0

From the Xcode 10.1.beta.3 release notes,  there are also other IPA issues such as "iOS9 crash". Since this is not a stable release, my advice is to archive your app with Xcode9.4, and wait for another stable Xcode release.

Ohh okay, I'll try this from another XCode. And let you know the result.
Thanks for help and quick replies.

I forgot to tell you one more thing about all this issue. I have used library to create one more calendar with different UI in same app and it's working on client side too. above is the one which is not working other than that throughout the app FSCalendar view is rendering.
I'm attaching file Which is I'm using currently. Please have a look. Please help me to sort this out.
ShowCalenderViewController.txt

I exported build from XCode 9.2 but it still same on client side. but on my phone it's working well.
they have 6s/7+/X and I have 6s plus & 7.

Can you upload a full example?

Can you upload a full example?
I have attached full code for the Calendar. You can use same code to open calendar.

Assignment to readonly property
The above error is showing .when i update the pod to recent version but it is working for previous versions.
the below is my code.
calendar.minimumDate=[dateFormat dateFromString:dateStr];
calendar.maximumDate=[dateFormat dateFromString:@"2099-12-31"];

Assignment to readonly property
The above error is showing .when i update the pod to recent version but it is working for previous versions.
the below is my code.
calendar.minimumDate=[dateFormat dateFromString:dateStr];
calendar.maximumDate=[dateFormat dateFromString:@"2099-12-31"];

You should use delegates for this before loading calendar view .

(NSDate *)minimumDateForCalendar:(FSCalendar *)calendar {
return self.minimumDate;
}

(NSDate *)maximumDateForCalendar:(FSCalendar *)calendar {
return self.maximumDate;
}


[Bug]: Delete depricated folders and files.

What bug you encountered?
Task to do

[ ] Make sure #501 and #502 are completed, then only start this task.

FOR GSSOC - LEVEL1
Show us the trouble with screenshots

Which browsers are affected?
No response
Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSoC'23 contributor
[ ] I want to work on this issue

Hey @PiyushKalyanpy
I would work on this issue.
Please assign this to me under GSSOC'23

@s2sharpit, done.

Hey @PiyushKalyanpy, Can I work on it now?


Add column ordering classes

Column ordering will be available when table-row is used.
Column ordering will be available for all screen sizes as well as at specific media breakpoints.

Completed.


Set num_beams of run.py is 4, the result has 4 outputs , but transfromers has 1 output

【TensorRT LLM:】

use chatglm2-6b models
build.py --max_beam_width=4
run.py --num_beams=4
result has 4 outputs， and output[0] is not the best output

Output [Text 0 Beam 0]: xxxxx
Output [Text 0 Beam 1]:  xxxxx
Output [Text 0 Beam 2]:  xxxxx
Output [Text 0 Beam 3]:  xxxxx
【Hugging Hace Transformers】
But transformer ony has one output.
Output [Text 0 Beam 0]: xxxxx
Is it a bug for TensorRT LLM?

TensorRT-LLM/examples/run.py
TensorRT-LLM/examples/chatglm/build.py
version:0.6.0

try fix bug: set beam_width is 1, not use 4
main/tensorrt_llm/runtime/generation.py
def finalize_decoder(self,
context_lengths,
batch_size,
beam_width,
scfg,
in_progress=False):
final_output_ids = None
if self.mapping.is_last_pp_rank():
# output shape of self.gather_tree: [batch_size, beam_width, output_len]
beam_hyps_args = [
self.beam_hyps_output_ids_tgt,
self.beam_hyps_sequence_lengths_tgt,
self.beam_hyps_cum_log_probs, self.beam_hyps_normed_scores,
self.beam_hyps_log_probs, self.beam_hyps_min_normed_scores,
self.beam_hyps_num_beams, self.beam_hyps_is_done
]
if scfg.use_beam_hyps and in_progress:
# self.gather_tree modifies these args.
# In streaming mode, this results in incorrect decoding in the following steps.
beam_hyps_args = copy.deepcopy(beam_hyps_args)
##################################################
#################### start test bug ##############
beam_width = 1 # if set beam_width to 1, the final result has 1 output, and the output[0] is the best output
#################### end test bug ##############
##################################################
final_output_ids = self.gather_tree(
self.sequence_length_buffer, self.output_ids, self.parent_ids,
self.end_ids, context_lengths, self.cum_log_probs,
*beam_hyps_args, self.finished, self.length_penalty, batch_size,
beam_width, self.max_seq_length, scfg.use_beam_hyps)
    # Communicate ranks in Pipeline Parallelism
    if self.mapping.has_pp():
        final_output_ids = self.pp_communicate_final_output_ids(
            final_output_ids, batch_size, beam_width)

    return final_output_ids

If you don't set num_return_sequences in HF, it will only return the first one sentence although it will generate beam_width sentences in beam search. You could see more details on HF document.

Excuse me, may I ask： Which parameter has the same function in TensorRT-LLM?
I want to need the same result when use TensorRT-LLM and  HF transfomers
When I set num_beams to 4, TensorRT-LLM has 4 output, but I only need one output.
And sometimes，the output[0] of TensorRT-LLM  is  correct, but sometimes the output[3] is correct.
I thank the result is not in descending orderd， so I can not always get the correct output by use the output[0]

The results are ordered. Sometimes, the outputs[0] of HF and TRT LLM are different because precision issue, it is expected and not a bug.


I translated chapter 6 in italian and updated the comments in italian in tour of rust and used Rust 2021.

This was submitted to upstream as https://github.com/richardanaya/tour_of_rust/pull/509.


Mac OS double click not working

Double click works well in Windows, but in Mac it does not work. Single click and right click works fine. My Mac version is Ventura.
simulator.SimulateMousePress(MouseButton.Button1);
simulator.SimulateMouseRelease(MouseButton.Button1);
simulator.SimulateMousePress(MouseButton.Button1);
simulator.SimulateMouseRelease(MouseButton.Button1);

Hi! Thanks for posting this issue! I will look into it, but in the meantime, as a workaround, could you please try it with a small delay between the clicks to see whether it works?

Ok, I've tried to reproduce the issue and it really is a bug. Two mouse events are actually emitted (which can be verified with a global hook), but applications simply ignore the fact that it's a double-click. There is a way to tell applications the number of clicks so I'll add overloads of SimulateMousePress and SimulateMouseRelease which will include the number of clicks.
They will most probably have the following form:
// The second parameter specifies the number of clicks - this way applications will understand that it's a double-click
simulator.SimulateMousePress(MouseButton.Button1, 1);
simulator.SimulateMouseRelease(MouseButton.Button1, 1);
simulator.SimulateMousePress(MouseButton.Button1, 2);
simulator.SimulateMouseRelease(MouseButton.Button1, 2);

Hi! Thanks for posting this issue! I will look into it, but in the meantime, as a workaround, could you please try it with a small delay between the clicks to see whether it works?

I have tried with delay and it still had the same issue.

Ok, I've tried to reproduce the issue and it really is a bug. Two mouse events are actually emitted (which can be verified with a global hook), but applications simply ignore the fact that it's a double-click. There is a way to tell applications the number of clicks so I'll add overloads of SimulateMousePress and SimulateMouseRelease which will include the number of clicks.
They will most probably have the following form:
// The second parameter specifies the number of clicks - this way applications will understand that it's a double-click
simulator.SimulateMousePress(MouseButton.Button1, 1);
simulator.SimulateMouseRelease(MouseButton.Button1, 1);
simulator.SimulateMousePress(MouseButton.Button1, 2);
simulator.SimulateMouseRelease(MouseButton.Button1, 2);

Thank you very much for your response. I attempted the solution you provided, but I encountered an error. I believe I may have made a mistake. Could you please review this?
My Code:
using SharpHook;
using SharpHook.Native;

class Program
{
    static void Main()
    {
        Thread.Sleep(5000);
        var simulator = new EventSimulator();

        simulator.SimulateMouseMovement(2480, 645);
        Thread.Sleep(500);
        simulator.SimulateMousePress(MouseButton.Button1, 1);
        simulator.SimulateMouseRelease(MouseButton.Button1, 1);
        simulator.SimulateMousePress(MouseButton.Button1, 2);
        simulator.SimulateMouseRelease(MouseButton.Button1, 2);
        Thread.Sleep(1000);
        Console.WriteLine("done");
        Console.ReadLine();
    }
}

Error:
/Users/macmini/Projects/test/test/Program.cs(19,19): Error CS7036: There is no argument given that corresponds to the required parameter 'button' of 'EventSimulator.SimulateMousePress(short, short, MouseButton)' (CS7036) (Test)
got this same error for line 13,14,15,16

Well, yes, the code above will lead to an error, because I haven't yet implemented this :)
I will release version 5.1.0 shortly which will contain the methods I've described.

Alright, thank you!

Version 5.1.0 which contains the fix has been released today. Now simulating multiple clicks on macOS looks like this:
// The second parameter specifies the number of clicks - this way applications will understand that it's a double-click
simulator.SimulateMousePress(MouseButton.Button1, 1);
simulator.SimulateMouseRelease(MouseButton.Button1, 1);
simulator.SimulateMousePress(MouseButton.Button1, 2);
simulator.SimulateMouseRelease(MouseButton.Button1, 2);


Adding MinimumStake to the consensus parameters

Describe the problem you'd like to have solved
Adding MinimumStake to the consensus parameters prevents creating dummy validators, specially in the Mainnet.
Spammers might create thousands of validators with small stakes. This has no effect on the consensus mechanism or the sortition algorithm.
Describe the ideal solution
Adding a new field in the consensus parameters for MinimumStake. The default value can set to 1 PAC coin.

is 1 PAC make sense?
because its still easy to make dummy validators!?


mp3 mime & Upload Progree

Hi, I tried to use File Upload for mp3 uploading, limiting file upload by
'mimes' => 'mp3',
doesn't work.
and Is there option to see upload progree?

I can't add mp3 files with Laravel 4.2 with mimes=>'mp3'.

I got it working by changin 'mimes' => 'mp3' to 'mimes' => 'mpga'.


Implement PSR-1 and PSR-2

Implement the PSR 1 and 2 to ease the implementation of future features.

PSR-1 https://www.php-fig.org/psr/psr-1
PSR-2 https://www.php-fig.org/psr/psr-2

Currently the repo don't follow any coding standard.

Merged pull request, starting from now PSR-1 and PSR-2 will be a must in order to accept any PR


Add support for enhancements to Source Import API

announcement: https://developer.github.com/changes/2016-05-03-source-import-api-enhancements-for-working-with-git-lfs/

I believe this depends on #291 so I will leave it alone for now.


Set and enforce a maximum storage TTL for datastreams

While support for using a maximum period for datastreams data retention in a given realm is already present in DUP/AppEngine since 0.10, there was no support for setting its value.  Add it.
The value (in milliseconds) can be specified in Housekeeping API at realm creation, or changed with a realm update. Defaults to none, as before.

Based on https://github.com/astarte-platform/astarte_rpc/pull/81


Missing error on static vs. non-static setter/member

It is a compile-time error if a class contains a static getter and a non-static member with matching name, or vice versa.
Caught by language_2/bad_override_test.

I think this issue can be closed. We've implemented the stuff from https://github.com/dart-lang/sdk/issues/33235#issue-326617285. Those should be the new rules.
Re-open if I'm wrong.


user menu popup is not available on the site setup pages

The user icon is gone from the left sidebar when I go to the site setup

The user icon is missing because it is included with the "DefaultViewButtons". If we remove this condition "!this.props.hideDefaultViewButtons && " it will make the user icon always visible in the toolbar(if toolbar is present) no matter which webpage you visit on the site. Let me know your thoughts on this bugfix.


Read download directory location from the OS

WebTorrent uses ~/Download as a download directory, as decided in https://github.com/feross/webtorrent-desktop/issues/53#issuecomment-193098170, but location may change depending on user's locale or be edited by hand.
On Linux there's XDG spec for specifying how to get directories’ locations (xdg package looks promising (I haven't used it nor looked at the code)). Don’t know how to do that on other platforms.

Fixed on master


Simplify Broadway by removing pod manifests

remove tasks and pod manifests from playbooks

+1

+1 but see comments @macat


Can't create router if I put value in Fault HTTP Abort Code field

date - 12/4
Steps:

Go to create Router
Fill in info and check on Fault checkbox
Put info in Percentage, Delay & Abort code  field

Results:  No matter what I put in the abort code it gives me an error that basically says "body must be of type integer: "string""
"Router.rio.cattle.io "faulttets2" is invalid: []: Invalid value: map[string]interface {}{"apiVersion":"rio.cattle.io/v1", "kind":"Router", "metadata":map[string]interface {}{"creationTimestamp":"2019-12-04T21:32:54Z", "generation":1, "name":"faulttets2", "namespace":"default", "uid":"a1b31532-16dd-11ea-8abc-42010a800087"}, "spec":map[string]interface {}{"routes":[]interface {}{map[string]interface {}{"fault":map[string]interface {}{"abortHTTPStatus":"404", "delayMillis":50, "percentage":50}, "to":[]interface {}{map[string]interface {}{"uuid":"T4gX6EhxJt0jJQKo"}}, "uuid":"WPkMlxt0J9hEeBMl"}}}, "type":"rio.cattle.io.v1.router"}: validation failure list:↵spec.routes.fault.abortHTTPStatus in body must be of type integer: "string""
status: 422
type: "error""

Date - 12/5
Verified fixed


BOSH-lite manifest template allows custom users

We would like to be able to add extra users to our bosh-lite deployment.
Other infrastructure templates support this.

Hi,
As there hasn't been any activity on this pull request for a week I'm going to close this for now. Feel free to open a new pull request if you have a fix for this issue.
Thanks,
Al

Yeah, I lost track of this, but your original point stands, I don't see how to make it work.
Thanks.


Add in preprocessing hook to add additional key/value pairs

We need to add additional key/value pairs to the log message for our logging flow.  Namely we want to auto-add the app name.  Anyway, this is a generic preprocessing hook that allows any modification to the data right before it is shipped to the JSON formatter.

johnnyb:master


false-positive with "static" dependencies

Sometimes, we have a static dependency that we read from e.g. react context, like an api:
const useFoo = () => {
  const api = useApi();
  return useQuery({
    queryKey: ['foo'],
    queryFn: () => api.fetchFoo(),,
  })
}

this api is injected via react-context, but it's stable and not really changing. We mainly have it context to provide a different API for testing.
The eslint-plugin-query complains here rightfully that api should be added to the QueryKey, but we can't really do that - it's an axios instance that is not serializable. It's also not intended to be added to the key. For us, it's essentially the same as:
import api from 'api'

const useFoo = () => {
  return useQuery({
    queryKey: ['foo'],
    queryFn: () => api.fetchFoo(),,
  })
}

Of course, the linter doesn't know that this dependency is "stable". Maybe we could have an option on the eslint plugin that defines known exceptions? @Newbie012 what do you think?

when I wrote the first POC, I actually supported some kind of ignoredKeys, but I eventually dropped it since I think the rule should ignore member expression nodes where the deepest node is a call expression (e.g. a.b.c.d(). In fact, I thought I wrote a test for it.
Hopefully I'll be able to raise a PR in The/Wed (on a trip so I won't be near my computer)

i've run in to the same thing when i use constant values. i was expecting this to work the same way as a useEffect dependency list
const CONST_VAL = 1;
const useFoo = () => {

  // queryKey eslint error: The following dependencies are missing in your queryKey: CONST_VAL
  const testQuery = useQuery({
    queryKey: ['foo'],
    queryFn: () => CONST_VAL,
  });

  // no react-hooks error when using const
  useEffect(() => {
    const newVal = 1 + CONST_VAL;
  }, []);
};

@samMatenaer this is a different issue. constants defined outside the component should indeed be ignored.

@TkDodo Maybe I did something wrong, but I was unable to reproduce this issue (there's even a test to cover it). I also wrote another test to be sure - https://github.com/TanStack/query/pull/5218

interesting @Newbie012. The question is, why doesn't this error? api coming from useApi could just as well be something that is a reactive dependency, which should be included. For example, something like this:
const useFilters = useSelector(store => store.filters)

const useFoo = () => {
  const filters = useFilters();
  return useQuery({
    queryKey: ['foo'],
    queryFn: () => fetchFoo(filters)
  })
}

This should definitely error. Is the difference in how those things are used? Like filters is passed to a function, while in the api example, we merely invoke a function on it?

oh yeah, that seems to be it. I wrote a test that errors on fetchFoo(filters), but succeeds on filters.fetchFoo(). I think that's fine? It basically means we're treating anything that returns functions as static, which might not be entirely true. Our api could be a function that's wrapped in useCallback and has itself a reactive dependency, like a baseURL that could change. But it's debatable if we'd want to error on those as well. I think the react exhaustive deps linter would error on those. If we want that as well, we'd need the "allowList" to list exceptions. If not, I think we are fine with the current implementation.

It would make sense that fetchFoo(filters) will error while filters.fetchFoo() won't, since filter is a meaningful value that we want to "react" when it changes, while it's not (mostly) the case with functions.
In rare cases such as changing the base URL or the Authorization header, I would prefer explicitly resetting the query cache.


Add the GinkgoHelper

Which issue this PR addresses:
This is a small PR to improve the readability of E2E test output by using the GinkgoHelper(). I noticed this feature while doing https://issues.redhat.com/browse/ARO-5321. The details are here but the tl;dr is we get more informative/clearer stack traces if there is an error in the helpers.
Test plan for issue:
The current E2E tests.
Is there any documentation that needs to be updated for this PR?
Is there any documentation that needs to be updated for this PR?
No. I think having this in the existing helpers is enough documentation.

/azp run ci,e2e


[BUG] Placeholder Text for QPlainTextEdit not Greyed Out

Description
The placeholder text for a QPlainText edit is rendered the same as the regular text, making it difficult to visually distinguish it from real text. This will likely also affect QTextEdit.
Potentially related to #41.

Weirdly, this only affects PyQt6. PyQt5 renders it properly.

This seems to only affect Qt6, and it is due to the use of hard-coded colors, ignoring the QPalette color role for PlaceholderText. This seems to a relevant bug on the Qt issue tracker. An example workaround (which works properly for Qt5, but does not work for Qt6) further supports the idea this is a Qt bug.


Add 0000-01-02-skiquiz.md

commit my first file
changed Create to Add in title, does thsi change commit?

Done


[WIP] Add GitHub Export Feature for Challenges

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Breaking change (fix or feature that would change existing functionality)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue Closes #5138

Description

Add new key to the user model (common/models/user.json) - isGithubRepoCool. This will hold if the user has allowed access to their github repos.
Add new section to the views of showBonfire, showHTML and showJS: Checks if the user has linked their github repos, if no: button to link, if yes, option to save to github and submit/continue.
New Event (click) handler for the new button, sends calls to submit (current FCC API) and to github (see below).
New Endpoint github-export/, this is implemented in server/boot/challenge.js. Makes a call to github to create a new repo, named Free-Code-Camp-Solutions, it doesnt matter if it already exists, it will then commit a new file with the file name being the challenge name + the date, and the contents is the solution formatted like normal code in a .md file.
Add Passport Provider github-repo, with an extra scope of repo, this is to allow users that wont use the feature to not have to give repo access.
Adds check to see if the accessToken from github has repo access, if yes, sets isGithubRepoCool to true, and updates the users profile.

I think thats it, big thanks to @raisedadead,
Feedback would be great

Just updated as I forgot to return next in one of the functions

@adamisntdead not sure why the checks haven't passed.
Can you rebase this off staging once?
git checkout <pr-branch>
git pull --rebase upstream staging
git push origin -f

And on that note thanks a lot for this pull request. Good work. Will QA and get back.

Updated - should pass everything now

Is there any changes I should make to the code? @BerkeleyTrue

@bugron I fixed most of what you said, bar the .save() thing, as I am not quite sure whats thats about - direction please 😜  @BerkeleyTrue Will update the commit

Also
Fix Travis Build Error

fixes

can be removed from commit message.

Just noticed a bug that means users have to refresh when they come back to the page, will try and fix and update the pr

Any other changes that need to be changed before the pull is merged?

Whats the status on this?

@adamisntdead sorry for the delay in looking at this, we are currently trying to land react into production as soon as we can. It's kind of a priority for the upcoming challenges overhaul, nevertheless please hang on tight, will get back.
Again sincere thanks for the implementation. I have also dropped you a PM.

No problem! Just wanted to see if I had more changes to make :)

:sparkles:  AWESOMENESS! :sparkles:
Just tested the functional scope and usecase of the feature:

User with existing GitHub Account and already on FCC

Displayed the additional permissions dialog.

User signed up first time via email

Displayed the default dialog for "with repo acess".

Now coming to the problems:

I jumped to a random challenge that I had solved earlier and tried saving I could not save.
I feel a slight UX should be after the user comes back from linking GitHub repo access he should be shown the move to next challenge modal directly
Add a Keyboard shortcut (Ctrl + Shift + Enter) for Save action

Will do more stress testing and get back.
@adamisntdead thanks again for your patience with this, let me know if you need any assitance.

Okay, away at the moment, will try fix some of that when I get back, thanks for the feedback, and let me know how stress testing goes :+1:

Just wondering, now that react is on the 'staging' branch, is there changes to the authentication system?

I don't think so

okay, I am gonna go back onto this in the next few days, get a couple new things in, and update the PR

Theres a good few conflicts, so I might make a new branch, and re-write this, I will be able to use alot of the old stuff, more frontend stuff I will need to fix, so I might do that and make a new PR, just gonna look through the new codebase first and then I will get back 👍

You need not close the pull request. I left you the steps on Gitter.

Just looking through the new reactifaction of FCC, just thinking about design for this feature? another bar ontop of it?
Not quite sure, all suggestions are helpful

@adamisntdead Are you still working on this. This PR is stale with 30 days of inactivity.

@BerkeleyTrue I will keep working on this, but I am waiting until the release of React and possibly the new challenges / editor, as to make sure I am not doing work that will just have to be redone.
If theres a problem with that just say and I can work on it now 👍

There aren't major changes to infrastructure coming. But if you are waiting for new challenges, please close this PR until ready.

@adamisntdead, React is live on staging, if you wanna reopen this PR 😄


Link identifiers to declarations / assignments.

function Foo() {};

Foo.prototype.bar = function () {};

var foo = new Foo(...);

// later in the file
foo.bar();

Linkify the foo part of foo.bar to the var foo = ... line.
Linkify the bar part of foo.bar to the prototype.bar = ... line.
Tern runs in the browser, and already accomplishes this. (demo)

This feature would transform github.com into an IDE 🚀  This is out of scope for this project, sorry. If you find an extension like this please add it here

I'm not proposing editor features, just additional links. Adding links to JS code on GitHub seems to be exactly the scope of this project.

The Tern demo I linked to is indeed IDE like, but I'm just referring to the "jump to" shortcut they offer (alt-. I believe). We could use tern to gather the same sort info that editor is using for the jump to command, and use it to linkify.

@jamestalmage Have you seen https://chrome.google.com/webstore/detail/sourcegraph-chrome-extens/dgjhfomjieaadpoljlnidmbgkdffpack?hl=en ? It's very useful. The service itself is cool too: https://sourcegraph.com

Try hovering and clicking stuff here<EMAIL_ADDRESS>

@jamestalmage I was aware that you were referring to the "jump to" functionality. I still think that this functionality is out of scope for the following reason. To provide this functionality in a proper way we need an AST representation of the current file + all linked files, dependencies, core modules ... I'm not saying that this is impossible, but definitely not easy to do. As @sindresorhus mention, there are already great tools available which allows you to do that.

Sure. I wasn't aware of sourcegraph. I am trying it out now, but it doesn't seem to work very well on GitHub (I can't get it to work at all, actually). It also requires that you submit the repository to their service for server side processing. I want something that just works quickly.

all linked files, dependencies, core modules

That seems less relevant to me than the current file. I mostly want to be able to see foo = bar.baz, and be able to quickly find the declaration for bar. That would be doable with some very basic AST tools. Tern adds support for being smart about (for example) linking this.someFunc() to the appropriate declaration on the prototype. Yes, linking to additional files would make it more robust, but (as you said) difficult. Still, I think the low hanging fruit (parsing just the current file) adds a ton of value, and would "just work" in a way sourcegraph doesn't.

@jamestalmage Maybe open an issue on https://github.com/sindresorhus/module-requests, requesting it then?

@sindresorhus - done
@stefanbuck - Can you add a license to the repo?


ERR Message ready() exception: Error: Contact.load(): id not found

Description
Get the latest codes, https://github.com/wechaty/wechaty/commit/eb8d79fac64ac46c6709dace79e388756d8ba170.
cd wechaty
npm install
npm start

Expected behavior
No error messages.
Actual behavior

Log trace
But the app is launched and service well. The incoming message is printed, not sure if the message has further impact.
Environment
OS: macOS Sierra
NodeJS: 6.9.1

Id is undefined at this point
ERR Message ready() exception: Error: Contact.load(): id not found
    at Function.load (/Users/hain/ai/wechaty/src/contact.ts:337:13)
    at Message.<anonymous> (/Users/hain/ai/wechaty/src/message.ts:415:29)
    at next (native)
    at /Users/hain/ai/wechaty/dist/src/message.js:7:65
    at __awaiter (/Users/hain/ai/wechaty/dist/src/message.js:3:12)
    at Message.ready (/Users/hain/ai/wechaty/dist/src/message.js:195:16)
    at PuppetWeb.<anonymous> (/Users/hain/ai/wechaty/src/puppet-web/event.ts:295:13)
    at next (native)
    at /Users/hain/ai/wechaty/dist/src/puppet-web/event.js:7:65

But I can not reproduce this error.

I had seen this bug now and then. will check it later.

@Samurais this exception is caused by calling this.say() before bot login. fixed.


Error page content updated as per Roz suggestions.

Lots of people complaining that their link is "invalid" when probably it's expired.
Updates to the wording to help users understand what is going on.

👍 :+1:


[RFC][Bridge] Add support for JS async functions, backed by RCT_EXPORT_PROMISE

Adds support for JS async methods and helps guide people writing native modules w.r.t. the callbacks. With this diff, on the native side you write:
RCT_EXPORT_PROMISE(getValueAsync:(NSString *)key)
{
  NSError *error = nil;
  id value = [_nativeDataStore valueForKey:key error:&error];

  // "resolve" and "reject" are automatically defined blocks that take
  // any object (nil is OK) and an NSError, respectively
  if (!error) {
    resolve(value);
  } else {
    reject(error);
  }
}

On the JS side, you can write:
var {DemoDataStore} = require('react-native').NativeModules;
DemoDataStore.getValueAsync('sample-key').then((value) => {
  console.log('Got:', value);
}, (error) => {
  console.error(error);
  // "error" is an Error object whose message is the NSError's description.
  // The NSError's code and domain are also set, and the native trace is
  // available under nativeStackIOS
});

And if you take a time machine or use Babel w/stage 1, you can write:
try {
  var value = await DemoDataStore.getValueAsync('sample-key');
  console.log('Got:', value);
} catch (error) {
  console.error(error);
}

For now the macro is defined as RCT_EXPORT_PROMISE_EXPERIMENTAL since I'd like to merge this and get real-world feedback on the API before committing to it.
Fixes #172
Makes #186 less relevant

One thing I'd like to discuss is the macro API. I'm not very satisfied with RCT_EXPORT_NULLARY_PROMISE, which exists solely to support selectors that don't have any parameters since adding the resolver & rejecter parameters is syntactically different than when adding them to selectors with parameters (method -> method:(RCTPromiseRejecterBlock)reject... vs. method:(id)arg -> method:(id)arg __rct_rejecter:(RCTPromiseRejecterBlock)reject...).
Another idea is to require the resolver & rejecter parameters to be manually declared. I like the simplicity of this despite the extra typing.
RCT_EXPORT_PROMISE(getValueAsync:(NSString *)key
                        resolver:(RCTPromiseResolverBlock)resolve
                        rejecter:(RCTPromiseRejecterBlock)reject)
{
}

[If we were to go this route, I'd want to modify the JS bridge code that currently assumes the order of callbacks to be (onFail, onSucc) and change it to (onSucc, onFail) so that the Obj-C selectors take (resolve, reject) which matches the order of args when creating a JS Promise. I believe this is a safe change since the order isn't enforced and modules currently do whatever they want.]

@ide I'd say go for the more verbose but declarative macro approach. Macros that begin to automagically make scoped variables available start to erode clarity and make debugging harder.

Switched to the more explicit API for now. If we want implicit resolve/reject that can be added on top as another macro anyway. Usage now looks like:
RCT_EXPORT_PROMISE(getValueAsync:(NSString *)key
                        resolver:(RCTPromiseResolver)resolve
                        rejecter:(RCTPromiseRejecter)reject)
{
  resolve(@"whatever");
}

The onFail and onSucc callbacks in the message queue have now been flipped to be (onSucc, onFail) to match (resolve, reject).

cc reviewers @nicklockwood @sahrens @vjeux

@ide convinced me that it's the right way to model all our one-shot asynchronous api to use promises.

They are standard
They provide an explicit and standard way to handle errors
We can now use async/await to work with them!

Right now, we've got as many versions of asynchronous calls as there are ways to do it. Moving to Promise seems like a clear win all across the board from the JS side of things.

I'm cautiously in favor of this idea. Some thoughts on the implementation:
The RCTPromiseRejecter callback for handling errors is a good idea, but I've been wanting to introduce something like this as a general solution for error callbacks, replacing the existing RCTMakeError() mechanism, which is inadequate anyway as it doesn't enforce any kind of standard for domain/code info. So let's just add an RCTResponseErrorBlock (or whatever) to complement RCTResponseSenderBlock (which I now realise is a terrible name anyway) and allow it to be used in any callback.
The automatic resolve/reject declaration idea you had originally was nice, but if that's not workable, then there's not really any need to have a new macro for promises. Instead of declaring a method to be of type promise, and then validating that the arguments meet the criteria, just let any method with a success and error callback be used as a promise. It doesn't seem like the actual calling mechanism is any different on the native side.
On the JS side, when enumerating over the exported module methods we can identify methods that meet the criteria to be a promise, and either add a second function with promise semantics, e.g.
MyNativeModule.getValue() // the original exported function
MyNativeModule.getValuePromise() // promise-ized version added by BatchedBridgeFactory.js

Or, since functions are objects anyway, we could add a property, something like:
MyNativeModule.getValue() // the original exported function
MyNativeModule.getValue.promise() // promise-ized version added by BatchedBridgeFactory.js

Idea: one thing we can do is to turn everything with a callback (except for event listeners) into a promise by default since the two don't APIs don't clash:
AsyncStorage.getValue(someData, func, func) // old
AsyncStorage.getValue(someData).then(func).catch(func) // new
AsyncStorage.getValue(someData, func, func).then(func).catch(func) // mix of old and new

then, whenever we don't have any non-promise call sites anymore, we can just turn off the old way of doing things. To ease the transition we can throw a warning if you call it the old way.
The advantage of this is that we don't need to change the ios/android side of things. we just assume that 1 callback is only error and 2 callbacks is success then error (or the opposite i never remember).
If we are to change this as the bridge level then we also need to change android which you don't have access.

@vjeux that sounds like a great idea. Although why ever deprecate calling the non-promise way? Having the ability to seamlessly switch between Promise and function-style calling conventions for the same API sounds pretty sweet to me.

@nicklockwood if you're using callbacks, then we allocate a promise object that's never going to be used? Also, having two ways to do the same thing often not a desirable property to have in a system.

@vjeux can't it be allocated lazily?
I agree about it being bad to have two ways to do the exact same thing, but these aren't exactly the same. I see this more like how ES6 provides both regular functions and arrow functions. Arrows are better for many purposes, but it wouldn't be a good idea to deprecate function() syntax and mandate the use of arrows.

@nicklockwood: if I understand the motivation behind RCTResponseErrorBlock it's to support NSError -> JS Error conversion -- do I have that right? Here's a proposal if so: the bridge could marshal NSErrors in general, so you'd even be able to write senderBlock(@[someObject, someNSError, someNSNumber]) so we wouldn't need RCTResponseErrorBlock. We'd still want RCTPromiseResolver and RCTPromiseRejecter because they enforce that the resolver should take only one argument and the rejecter should take an error.
@vjeux:

we just assume that 1 callback is only error and 2 callbacks is success then error (or the opposite i never remember).

Modules in the RN ecosystem are doing everything right now: only error callback, only success callback, (onSuccess, onError), (onError, onSuccess). So I think it might be a big bandaid to rip if we make assumptions about the callbacks.
For now I am in favor of having async functions (i.e. those that return promises) separate from normal functions. It's simpler and sidesteps all backwards compatibility issues. Node was trying to do something similar and backed off for a couple of reasons (latest proposal I heard a few months back was to make ES6 modules expose a Promise-only API if you import them and expose the legacy callback API if you require() them). We can still add a warning to normal functions if we want to deprecate them but I think it is too early to make the call that every bridged method must be async.

@ide, that makes sense to me. I like the idea of the bridge automatically resolving NSErrors into a standard format (in fact, that could apply to any type of object - maybe we need a whole set of reverse RCTConvert functions...)
And yes, it would also make sense to keep RCTPromiseResolver and RCTPromiseRejecter (maybe RCTPromiseResolveBlock and RejectBlock for consistency?), but we still wouldn't need the RCT_EXPORT_PROMISE() macro, right? We'd just check if an exported method had both of those in its argument list and treat it as a promise if so.

we still wouldn't need the RCT_EXPORT_PROMISE() macro, right?

Yeah. It's a question of how explicit we want to be and if supporting different function kinds (official term from the es spec) is important, which is why I added the struct field. Other function kinds are generators and constructors.

Happy for it to be explicit, this way we can do a per method migration. It's probably safer than a global migration :)

A summary of where the diff is at:
Obj-C API

RCT_EXPORT_PROMISE_EXPERIMENTAL requires explicit resolve & reject blocks. This makes handling methods with parameters and without parameters consistent. Can later add a macro that implicitly defines the resolve & reject parameters if desired.
Block types are named RCTPromiseResolveBlock and RCTPromiseRejectBlock. ResolveBlock takes one object, RejectBlock takes one NSError.
Both the resolve and reject blocks must be declared in the method signature. Can later make it so you only need to declare the resolve block (i.e. the method never fails) if it turns out that's convenient. Starting out simple for now; easier to add convenience later than to take it away.

Obj-C implementation

Function kind (normal, async) is explicitly recorded. Pro: provides a pattern for adding new function kinds like generators. Con: static libs need to be rebuilt once.
NSError -> JS Error conversion is handled only for rejected promises. When there is an Obj-C object -> JS object converter that can handle custom types, we can add support for NSError and treat promise rejection the same as any other native -> JS callback. Building the generic converter requires changing the JSON encoder so that it calls a method like -[id<JSONSerializable> toJSON] or +[RCTJSConvert Type:] on non-Foundation objects, so I want to defer that.

JS API

The new functions return promises, which are part of ES6 and are compatible with ES7 async functions.
When ES7 async/await is natively supported by JSC, we can just add the async keyword to the function created in BatchedBridgeFactory.js.
Async functions are separate from normal functions for now. That is, functions that take callbacks are not automatically promisified nor the other way around. If we come up with a good heuristic for promisification it should be pretty straightforward to implement it in BatchedBridgeFactory.

JS implementation

The global Promise implementation is used. Pro: can inject in custom Promise implementations that support long stack traces and other features. Cons: then() handlers run after plain callbacks and are not batched. If this causes problems we can swap out the Promise implementation.
In a follow-up diff I will batch the setImmediate handlers. Better to commit this separately so it's easier to bisect to.

Unless I missed a blocker I think this is shippable as an experimental API and it'd be helpful if a couple of FB's modules were converted so we can learn what the issues are.

I like the idea of reverse RCTConvert - then we could return proper Map, Error, and other objects.

@vjeux, @ide the reason I'm not keen on having an explicit promise macro is that we'll end up with a proliferation of different macros because we need four macros for each different method type:
RCT_EXPORT_XXX
RCT_REMAP_XXX
RCT_EXTERN_XXX (for Swift)
RCT_EXTERN_REMAP_XXX

The macros were supposed to make exporting methods easy and obvious, but as we add more and more it becomes confusing as to which one to use in what situation.

@nicklockwood this is my brief plan: remove RCT_EXPORT_PROMISE and the FunctionKind entry in the data segment. RCTBridge will infer that an RCT_EXPORT_METHOD method is a promise method if it sees RCTPromiseResolve/RejectBlock parameters in the signature. The JS side of the batched bridge can enforce that the last two arguments must be the resolver & rejecter. Does this plan earn the checkmark?

@ide works for me. I'd be OK with enforcing the param usage on the native side instead if that makes sense. Since it's an error in the native code to send the wrong params it should probably be an assertion rather than a redbox.

(To be clear when I say "enforce on native side" I mean enforce that if any included arguments are an enforcer or rejecter, they must be the last two. I don't know if that's what you meant.)

@nicklockwood params are now enforced in RCTBridge.m and the function kind is inferred from the parameters. added a test plan to the commit too.

The JS part looks good to me, thanks!

I just noticed this wasn't imported into Differential - can someone summon the bot?

@facebook-github-bot import

Thanks 🙌🏻

@nicklockwood could you take a look at the Obj-C side when you have a chance?


Index calculation in 2D and 3D examples fixed.

The examples did not support asymmetric data matrices due to wrong index computation.
j+i*N0 should be j+i*N1, since i is walking in [0..N0). Same for 3D example.
This should be compatible to PR #157 .

This change is

Thank you for contribution; this is merged manually in the develop branch, please issue future PR against develop branch of clFFT


Gracefully handle errors during task launching

See the JIRA description for full details.
JIRA issues: DCOS-39102

this solution should be back ported to releases/0.3 and forward ported to master 0.5


Fixed #21039 -- Introduce AddIndexConcurrently operation for PostgreSQL.

Basically a follow-up to #10901 where feedback has been addressed.

@charettes There are tests that fail, and I'm not really sure how to fix them. They all relate to the pony_pink_idx already being there, so it can't be created twice. The state (applied/unapplied) of the migration is just being reset in the tearDown method.

...IMO adding the concurrently argument (and **kwargs) is the right direction...

Super. 👍 Was just checking. 😉

@felixxm Thanks :+1: Your comments should have been addressed. Unfortunately, I didn't notice your import changes commit, so it's gone :/

@atombrella Thanks :rocket: ! I made few changes:

fixed missing comments,
reverted some unnecessary changes,
added notes about caveats and updated docs,
pushed minor edits.

@dtao Thanks :star2:


Add ability to set specific labels into a specific Github issue

Related to https://github.com/Azure/azure-sdk-tools/issues/3858
This should work independently of the meeting type and if the issue was created by the Scheduling tool or provided by the user

Now the GitHub Create flow has an optional parameter to specify any labels to add into the issue. We can now proceed to ask stakeholders how they want to specify the issue, or design what would be the best way to implement this feature (if required).


fix: Logo on Login screen

Summary
Logo on the login screen is hardcoded. The proposed change uses the configured logo if available.
Checklist

[ ] Tested and/or added tests to validate that the changes work as intended, if applicable.
[ ] Updated documentation in README.md, if applicable.

Does that really make sense though?
I understand wanting to have to user logo on the page, but if there's an authentication page, wouldn't users want to know what they're authenticating to?
I'd be willing to meet in the middle and have some kind of <custom logo> | <Gatus' logo> design, but I feel just having the custom logo may be a bit confusing for the end user


Runtime Performance

Hello there,
thanks for providing this nice little library! I am currently evaluating it so I can perhaps use it for the evaluation of XRF spectral data. The results look promising, but I am wondering about runtime performance. It takes around 2 seconds to process a spectrum of 8k channels on my machine, which really adds up when doing regression tests for a collection of hundreds or thousands of test spectra.
I use the following script for profiling:
import numpy as np
import pybeads as be
import cProfile
import pstats

def calculate_background(y: np.array, fc=0.006, d=1, r=15, amp=0.1, lam0=0.5, lam1=5, lam2=4, nit=15, pen='L1_v2'):
    return be.beads(y, d, fc, r, nit, lam0 * amp, lam1 * amp, lam2 * amp, pen, conv=None)

if __name__ == "__main__":
    cProfile.run('calculate_background(data)', 'stats.raw')

    file = open('stats.txt', 'w')
    profile = pstats.Stats('stats.raw', stream=file)
    profile.sort_stats('cumulative')
    profile.print_stats()
    file.close()

https://gist.github.com/mnagel/70dd8d3d6228356fb470e4dfab38f639 contains the script including demo data.
The profiling output looks like this for me:
Wed Mar  3 11:52:12 2021    stats.raw

         60135 function calls (59988 primitive calls) in 1.820 seconds

   Ordered by: cumulative time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.000    0.000    1.820    1.820 {built-in method builtins.exec}
        1    0.000    0.000    1.820    1.820 <string>:1(<module>)
        1    0.000    0.000    1.820    1.820 pybeads-perftest.py:410(calculate_background)
        1    0.097    0.097    1.820    1.820 venv\lib\site-packages\pybeads\__init__.py:6(beads)
        1    0.000    0.000    1.157    1.157 venv\lib\site-packages\pybeads\__init__.py:158(make_diff_matrices)
    86/84    0.002    0.000    1.152    0.014 venv\lib\site-packages\scipy\sparse\coo.py:128(__init__)
    70/68    0.001    0.000    1.144    0.017 venv\lib\site-packages\scipy\sparse\dia.py:78(__init__)
        3    1.135    0.378    1.135    0.378 {method 'nonzero' of 'numpy.ndarray' objects}
       32    0.004    0.000    0.233    0.007 venv\lib\site-packages\pybeads\__init__.py:150(linv)
       32    0.001    0.000    0.208    0.007 venv\lib\site-packages\scipy\sparse\linalg\dsolve\linsolve.py:84(spsolve)
       32    0.203    0.006    0.203    0.006 {built-in method scipy.sparse.linalg.dsolve._superlu.gssv}
       91    0.165    0.002    0.165    0.002 {built-in method builtins.sum}
      124    0.001    0.000    0.111    0.001 venv\lib\site-packages\scipy\sparse\base.py:457(__mul__)
      109    0.000    0.000    0.110    0.001 venv\lib\site-packages\scipy\sparse\base.py:350(dot)
       16    0.000    0.000    0.084    0.005 venv\lib\site-packages\pybeads\__init__.py:70(<lambda>)
       61    0.001    0.000    0.080    0.001 venv\lib\site-packages\scipy\sparse\compressed.py:491(_mul_sparse_matrix)
       31    0.000    0.000    0.061    0.002 venv\lib\site-packages\scipy\sparse\base.py:542(_mul_sparse_matrix)
...

Can you confirm that these numbers look reasonable and are to be expected?
Is there any way to improve speed?
Best Regards
Michael

I submitted a PR that creates the differential matrices without the sparse->dense->sparse conversion. This reduces the cost of the make_diff_matrices function such that caching is no longer necessary.
To illustrate, I used the data from the gist you posted and ran 100 beads calculations using the current pybeads version and the version from my PR. Caching was done by placing the lru_cache decorator from functools above the make_diff_matrices function. The results are below, with times in seconds:

version
non-cached
cached

current version
2.127 +- 0.038
0.522 +- 0.186

new version
0.526 +- 0.034
0.548 +- 0.055


CBR:  ComicRack tags work, CBL tags do not

I hope this is the right place.  Thanks for all your work on this software, it's really slick!
I get the error: The tag save operation seemed to fail! when I try to Save Tags, using ComicBookLover style on CBRs.  ComicRack tags work fine.
I am running
ComicTagger v1.5.0 (from binary installer)
WinRAR 6.11 64-bit
Win 10 21H2 64-bit
I tried an earlier version of ComicTagger v1.4.8, various path/reinstall things with WinRAR (I didn't realize it was a problem with CBL at first, and people seemed to have issues with RAR installs.)
I'm ok using CR tags, but it took me a while to figure out that I could. CR tags save fine with CBR files, but not CBL.  But I thought I'd report it in case it's an issue.
If CBL is inherently incompatible with CBR, my apologies, I'm new to all of this.  Thanks very much!

They're supposed to work, I just don't test them much...

There is a log located at %APPDATA%\ComicTagger\logs can you attach it to this ticket?

ComicTagger.log
Activities:
Search-then-Save Tags CBL
Auto-Tag CBL
Search-then-Save CR

(Thanks!  I don't mind using CR tags, it was just that CBL was the default when it loaded for the first time and it took a bit to realize that I needed to change it.)

Fixed in the latest release


Not respecting the selected virtualenv kernel

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
If I select try to run a kernel from a virtualenv, VSCode instead falls back to the global installation (where jupyter-notebook is not installed).
I can recreate this from scratch using a new virtualenv with just pip install jupyter notebook.
In the virtualenv, I can run jupyter-notebook, and VSCode will happily connect to the kernel if I choose "Select another Kernel > Existing Jupyter Server".
VS Code Version
Version: 1.76.1 Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b Date: 2023-03-08T16:48:08.231Z (2 days ago) Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: <IP_ADDRESS>-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: Yes
Jupyter Extension Version
v2023.2.1200692131
Jupyter logs
https://gist.github.com/zakandrewking/9257c732336c48781745ba0078e683aa

Coding Language and Runtime Version
Python 3.11.2
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

You may need to run the command Jupyter: Select Interpreter to start Jupyter Server if I understand the issue correctly, although I'm surprised that we don't use the selected kernel if jupyter server is available there.
The interpreter we use for starting jupyter server isn't necessarily the same as the interpreter used to run the kernel.

That worked! thank you (might be nice to have this in the docs, if other people get the same behavior)


specs-go: Image.Created uses a string type

We have a time field that is a string. Let's help ourselves not make mistakes and make sure this is a proper time.Time or derivative type that does the right validation.

Looks like https://github.com/opencontainers/image-spec/blob/master/specs-go/v1/config.go#L56 also has this issue.

Not that the default time.Time is sufficient here, since it uses rfc3339.

I'm working on this.

#534 is merged


Support distribution on Linux via Linuxbrew

Check list

[x] I have read through the README
[x] I have searched through the existing issues

Environment info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Others:

Version
N/A
Problem / Steps to reproduce
Running brew tap wxfr/csview && brew install csview on Linux with Linuxbrew, does not result in a working csview.
I looked at the homebrew-csview repository, and the darwin binary is hard coded there.
I'm not sure if it's possible, but is there a way that you could support distributing on Linux via Linuxbrew?

Hi @vamega Can linuxbrew and homebrew share the same formula? I'm happy to add support for linuxbrew but I'm not familiar with it. PRs or any help are welcomed!

I'm going to investigate that.
I'm only minimally familiar with homebrew packaging myself.
Thanks for the great tool


[Firebase/Auth][I-AUT000015] The UIApplicationDelegate must handle remote notification for phone number authentication to work (7.4.0, SwiftUI)

Step 0: Are you in the right place?
Yes. And thank you for building this, Firebase makes for delightful realtime experiences.
[REQUIRED] Step 1: Describe your environment

Xcode version: 12.3
Firebase SDK version: 7.4.0
Installation method: CocoaPods
Firebase Component: Auth

[REQUIRED] Step 2: Describe the problem
When I try to call PhoneAuthProvider.provider().verifyPhoneNumber, it tells me that The UIApplicationDelegate must handle remote notification for phone number authentication to work
I am using SwiftUI with UIApplicationDelegateAdaptor. I have verified that I followed all of the instructions from the official documentation and with these steps:

Create a Firebase project and set up PhoneNumber Auth

Add your iOS app to the Firebase project, download and add GoogleService-Info.plist to your project

In Xcode, select the application target and enable the following capabilities:

Push notifications
Background modes > Remote notifications
Create and register an APNS authentication key on the Apple developer portal

Upload the key to Firebase (under Project Settings > Cloud messaging in the Firebase Console)

Add the Firebase project's reversed client ID to app's URL schemes

In Info.plist, set FirebaseAppDelegateProxyEnabled to NO

Implemented the AppDelegate as follows:

**Note that we're also using Messaging which we also forward notifications to, no problem. I also tried removing all of the Messaging integration to see if there was interference, but it didn't resolve the issue. **
Relevant Code:
  func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
    print("\(#function)")
    Messaging.messaging().apnsToken = deviceToken
    Auth.auth().setAPNSToken(deviceToken, type: .sandbox) // Ive tried prod and just setting it directly
    print(deviceToken)
  }

  func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable : Any], fetchCompletionHandler completionHandler: @escaping (UIBackgroundFetchResult) -> Void) {
    print("\(#function)") // This never prints, nor breakpoint hit
    if Auth.auth().canHandleNotification(userInfo) {
        completionHandler(.noData)
        return
    }
    Messaging.messaging().appDidReceiveMessage(userInfo)
  }

  func application(_ application: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey : Any]) -> Bool {
      print("\(#function)")
      if Auth.auth().canHandle(url) {
        return true
      }
      return false
    }

  var body: some Scene {
    WindowGroup {
      ContentView(viewModel: .init(context: context))
        .environmentObject(context)
        .onOpenURL { url in
          print("Received URL: \(url)")
          Auth.auth().canHandle(url)
        }
    }

Digging further, I found a reference to this codepath in Firebase which generates this warning: https://github.com/firebase/firebase-ios-sdk/blob/31a2acb7497eaaeae38b7ceb17edcab09d7f2866/Firebase/Auth/Source/FIRAuthNotificationManager.m#L107-L120
So I put this code right before the call to PhoneAuthProvider to see if my app delegate responds to the selector, and it returns true:
let responds = UIApplication.shared.delegate?.responds(to: #selector(UIApplicationDelegate.application(_:didReceiveRemoteNotification:fetchCompletionHandler:)))
      print("Responds? \(responds)")

So, the app delegate, from within my application's context, is able to verify that selector.

@chrysb Sorry you experience the issue. It looks like UIApplicationDelegateAdaptor affects the way respondsToSelector: for the UIApplication delegate works which can affect Firebase SDKs functionality. We are working on designing a long term fix and will look for a workaround for the current issue.
In the meanwhile the only workaround I can see is to avoid using UIApplicationDelegateAdaptor so far.

@chrysb Sorry you experience the issue. It looks like UIApplicationDelegateAdaptor affects the way respondsToSelector: for the UIApplication delegate works which can affect Firebase SDKs functionality. We are working on designing a long term fix and will look for a workaround for the current issue.
In the meanwhile the only workaround I can see is to avoid using UIApplicationDelegateAdaptor so far.

@maksymmalyhin Thanks, I'm glad I'm not crazy... I bashed my head for a while :)
I look forward to the fix or workaround — because now we're going to have to fallback to using a different Auth provider and implementing our own phone number verification flow using Twilio 😅
Appreciate your super fast response!

@maksymmalyhin Thanks, I'm glad I'm not crazy... I bashed my head for a while :)
I look forward to the fix or workaround — because now we're going to have to fallback to using a different Auth provider and implementing our own phone number verification flow using Twilio 😅
Appreciate your super fast response!

@chrysb I tried to follow the particular steps you shared but was not able to reproduce the issue you have. I guess there are some missing pieces not described in the ticket. Could you please share a sample project where the issue is reproducible so we can help you with a workaround for your case and make sure it is covered by our intended fix?
Most of the issue we discovered so far are related to interacting UIApplicationDelegateAdaptor with Firebase app delegate swizzler, so I guess your issue may be slightly different.

@chrysb I tried to follow the particular steps you shared but was not able to reproduce the issue you have. I guess there are some missing pieces not described in the ticket. Could you please share a sample project where the issue is reproducible so we can help you with a workaround for your case and make sure it is covered by our intended fix?
Most of the issue we discovered so far are related to interacting UIApplicationDelegateAdaptor with Firebase app delegate swizzler, so I guess your issue may be slightly different.

I would also suggest to check https://github.com/firebase/firebase-ios-sdk/blob/master/docs/firebase_in_libraries.md and presence of messages like the following:
objc[40943]: Class FIRApp is implemented in both
~/Library/Developer/Xcode/DerivedData/FrameworkTest-apqjxlyrxvkbhhafhaypsbdquref/Build/Products/Debug-iphonesimulator/DynamicFramework.framework/DynamicFramework
(0x10b2a87f8) and
~/Library/Developer/CoreSimulator/Devices/4821F959-24A6-4D78-A102-4C5703103D99/data/Containers/Bundle/Application/F017D210-113A-4DAF-9E17-BDE455E71E06/FrameworkTest.app/FrameworkTest
(0x10ad2d348). One of the two will be used. Which one is undefined.

I would also suggest to check https://github.com/firebase/firebase-ios-sdk/blob/master/docs/firebase_in_libraries.md and presence of messages like the following:
objc[40943]: Class FIRApp is implemented in both
~/Library/Developer/Xcode/DerivedData/FrameworkTest-apqjxlyrxvkbhhafhaypsbdquref/Build/Products/Debug-iphonesimulator/DynamicFramework.framework/DynamicFramework
(0x10b2a87f8) and
~/Library/Developer/CoreSimulator/Devices/4821F959-24A6-4D78-A102-4C5703103D99/data/Containers/Bundle/Application/F017D210-113A-4DAF-9E17-BDE455E71E06/FrameworkTest.app/FrameworkTest
(0x10ad2d348). One of the two will be used. Which one is undefined.

Hi Maksym,
Thanks for looking into this! I'm not sure I'll have the time to create a sample project to repeat all of these steps, but I'll certainly be happy to test the new update and see if the issue is resolved. For now, we're going to stick with a different default auth and verify phone numbers via Twilio.
Loving Firebase! Keep up the great work :)

Hi Maksym,
Thanks for looking into this! I'm not sure I'll have the time to create a sample project to repeat all of these steps, but I'll certainly be happy to test the new update and see if the issue is resolved. For now, we're going to stick with a different default auth and verify phone numbers via Twilio.
Loving Firebase! Keep up the great work :)

@chrysb I've encounter the same issue today.  I think you probably used:
   init() {     FirebaseApp.configure()   }
instead of
  func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {     FirebaseApp.configure()     return true   }
I've got the same error if I missed didFinishLaunchingWithOptions.

@chrysb I've encounter the same issue today.  I think you probably used:
   init() {     FirebaseApp.configure()   }
instead of
  func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {     FirebaseApp.configure()     return true   }
I've got the same error if I missed didFinishLaunchingWithOptions.

@chrysb I've encounter the same issue today. I think you probably used:
 init() { FirebaseApp.configure() }
instead of
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool { FirebaseApp.configure() return true }
I've got the same error if I missed didFinishLaunchingWithOptions.

You're right - I am calling FirebaseApp.configure() somewhere else. Thanks for the tip!


Missing directories in template app gives error when compiling on MacOS.

I downloaded and tried compiling the emulator.  I was was getting an error when the Makefile tried to copies files to the missing directories.
Under /aquarius-plus/System/emulator/macos/AquariusPlusEmu.app/Contents
I created two directories MacOS and Resources
Also, since I didn't like not having an icon I created one called AquariusPlusEmu.icns (as listed in the .plist file) and added it to the Resources directory.
After doing this it the build completed successfully.

Thanks for reporting this. Git doesn't commit empty directories. So I will change the makefile to create the missing directory. Can you share the icon you made, then I will include it in the repository?

AquariusPlusEmu.icns.zip
Had to zip it.

Thank you! I've added it to the repo and fixed the issue.


webpack compliance

While trying to use this otherwise great module with webpack, I get a Cannot find module 'bluebird' error.
Looks as if the browserified version basically loads well in webpack, but it avoids webpack's static require substitution. :(

My temporary solution was to add a resolve.alias in webpack configuration like so:
alias: {
        'bluebird-retry': 'bluebird-retry/lib/bluebird-retry'
    }

@amir-arad Do you have any suggestions as to how I could change the library to be more amenable to webpack? I'm not familiar with what needs to be done but I'd welcome a PR with suggested changes to make this work.

@demmer I have the opposite problem: there's some browserify magic in the module (from PR #21 ) that I don't really understand...


Move initializer to instance initializers

Not ready for merge, just for discussion.
The addon breaks in Ember 2.0 because you can't lookup from the container in application initializers anymore.
Moving to an instance initializer works, but that receives an application vs the container.
This obviously isn't backwards compatible, so we'll probably need to add back an application initializer and only run that if we're not on Ember 2.0?

@rlivsey sorry it took me so long to get back to you. thanks for the PR.
I think we can have support for both?
// bootstrap bugsnag
export default function (source) {
  if (typeof Bugsnag === 'undefined') { return; }

  source = source.container || source;

  if (currentEnv !== 'test' && Bugsnag.notifyReleaseStages.indexOf(currentEnv) !== -1) {
    Ember.onerror = function (error) {
      Bugsnag.context = getContext(source.lookup('router:main'));
      Bugsnag.notifyException(error);
      console.error(error.stack);
    };

    Ember.RSVP.on('error', function(error) {
      Bugsnag.context = getContext(source.lookup('router:main'));
      Bugsnag.notifyException(error);
      console.error(error.stack);
    });

    Ember.Logger.error = function (message, cause, stack) {
      Bugsnag.context = getContext(source.lookup('router:main'));
      Bugsnag.notifyException(generateError(cause, stack), message);
      console.error(stack);
    };
  }
};

// application initializer
import bootstrapBugsnag from '../utils/bootstap-bugsnag';

export default {
  name: 'bugsnag-error-service',
  initialize: bootstrapBugsnag
};

// application instance initializer
import bootstrapBugsnag from '../utils/bootstap-bugsnag';

export default {
  name: 'bugsnag-error-service',
  initialize: bootstrapBugsnag
};

Application and application instance initializers are exactly the same but I don't think there's a way to avoid this duplication, please tell me if you know of one.

No, they're not the same. The concept of lookup does not exist in an application initializer. Can we merge this?

Do we only need to use instance initializers here? I don't think we're supporting pre 1.12, correct me if I'm wrong @twokul.
This should work in >= 1.12 and Ember 2. If anyone wants to fix these conflicts, I'm happy to merge.

Didn't see this was actually done in https://github.com/zestyzesty/ember-cli-bugsnag/commit/16fba09531522321422183cecf662c5c4550dc27.


Back button doesn't work

To reproduce: add a couple terms, delete a couple terms from the query, and then press the back button.  The URL changes in the status bar, but the application doesn't update what's shown on the page.

FINALLY figured this one out!  4bfcf1795f1019a2f005e2b6c42fb84aa66c07c3


doghouse: Use shared http.RoundTripper

[x] Updated Unreleased section in CHANGELOG or it's not notable changes.

// The provided tr http.RoundTripper should be shared between multiple
// installations to ensure reuse of underlying TCP connections.
https://github.com/bradleyfalzon/ghinstallation/blob/81f7095e75089d688962bb75ba9814748d90f004/transport.go#L72-L73

Potentially related with https://github.com/reviewdog/reviewdog/issues/681, but probably not.


update to work with latest Rust nightly

fixes https://github.com/iron/iron/issues/315

Awesome, thanks!


depth from polarisation

Dear prof. William A. P. Smith  @waps101
Thank you for sharing the codes. I have a question about it: I saw the results of surface normals in your amazing paper. How can we estimate surface normals from these codes?

I recommend using the following function from another of my repositories:
https://github.com/waps101/polarisation_optimisation/blob/master/utils/depthnormals_mask.m
This computes a normal map from a height map via finite difference derivatives. Apply this to the height map you get from shape-from-polarisation.


Arithmetic operators are allowed with some union types

Description:
The below invalid sample compiles runs and gives the correct output
public function main() {
    float|decimal a = 44.3d;
    float b = 2;
    float c = a * b; // 88.6
}

However, if we interchange the order of union it will fail at compile time
public function main() {
    decimal|float a = 44.3d;
    float b = 2;
    float c = a * b; // error operator '*' not defined for '(decimal|float)' and 'float'
}

Result in a compilation error on Swan Lake Update 1 and later versions. Keeping the issue open to add tests.


Rearrange snackbar msgs to avoid overlapping each other

The overlapping is seen when user denies Camera Permission and clicks on "Detect Text." The snackbar with message "Tap to capture. Pinch/Stretch to zoom" overlaps with the snackbar's message "Access to the camera is needed for detection." As a result, user is unable to press "OK" to request permission again.

I signed it!


MCScanX: not found

Hi CJ-Chen, Thanks for developing this tool.
I having an issue when I try to use Quick Run MCScanX Wrapper.
error log here:
[Debug...All Standard Error Info will show as following:...]
Curr log file:/tmp/TBtools.14595798488989250861.20210723103734.log
Curr java version:11.0.11
Curr TBtools version:1.09854
Maxmum Memory for Curr TBtools:<PHONE_NUMBER>
curVersion:1.09854:force
Fetch Location:200
Factor:0.1516546094367225
sh: 1: MCScanX: not found
sh: 1: duplicate_gene_classifier: not found
Exception in thread "Thread-5" java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
Show me that TBtools can't find MCScanX and duplicate_gen_classifier, but already installed and added to my path how could fix this issue?
Thanks.

Hi CJ-Chen, Thanks for developing this tool.
I having an issue when I try to use Quick Run MCScanX Wrapper.
error log here:
[Debug...All Standard Error Info will show as following:...]
Curr log file:/tmp/TBtools.14595798488989250861.20210723103734.log
Curr java version:11.0.11
Curr TBtools version:1.09854
Maxmum Memory for Curr TBtools:<PHONE_NUMBER>
curVersion:1.09854:force
Fetch Location:200
Factor:0.1516546094367225
sh: 1: MCScanX: not found
sh: 1: duplicate_gene_classifier: not found
Exception in thread "Thread-5" java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
Show me that TBtools can't find MCScanX and duplicate_gen_classifier, but already installed and added to my path how could fix this issue?
Thanks.

I solve the issue   "sh: 1: MCScanX: not found" "sh: 1: duplicate_gene_classifier: not found" making a soft link
sud ln -s /  /usr/bin. But I still have something weir at the end of the log
Debug...All Standard Error Info will show as following:...]
Curr log file:/tmp/TBtools.5396513406862413497.20210723140923.log
Curr java version:11.0.11
Curr TBtools version:1.09854
Maxmum Memory for Curr TBtools:<PHONE_NUMBER>
curVersion:1.09854:force
Fetch Location:200
Factor:0.4252665337415543
Reading BLAST file and pre-processing
Generating BLAST list
0 matches imported (69 discarded)
0 pairwise comparisons
0 alignments generated
Pairwise collinear blocks written to ./psal.blast.collinearity [0.014 seconds elapsed]
Writing multiple syntenic blocks to HTML files
NZ_CP011849.2.html
NZ_CP011850.1.html
NZ_CP011851.1.html
NZ_CP011852.1.html
NZ_CP013669.1.html
Done! [0.009 seconds elapsed]
Reading BLAST file and pre-processing
Generating BLAST list
0 matches imported (69 discarded)
0 pairwise comparisons
0 alignments generated
Type of dup	Code	Number
Singleton	0	3574
Dispersed	1	0
Proximal	2	0
Tandem	3	0
WGD or segmental	4	0
Exception in thread "Thread-5" java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
Do you know to what is referring?
Thanks.

Please check whether IDs are consistent in gff and blast file.


Pip install already but still like this

╰─ pip install diffusers
Requirement already satisfied: diffusers in c:\users\administrator\miniconda3\lib\site-packages (0.16.1)
Requirement already satisfied: Pillow in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (9.5.0)
Requirement already satisfied: filelock in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (3.12.4)
Requirement already satisfied: huggingface-hub>=0.13.2 in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (0.17.3)
Requirement already satisfied: importlib-metadata in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (6.8.0)
Requirement already satisfied: numpy in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (1.26.0)
Requirement already satisfied: regex!=2019.12.17 in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (2023.8.8)
Requirement already satisfied: requests in c:\users\administrator\miniconda3\lib\site-packages (from diffusers) (2.29.0)
Requirement already satisfied: fsspec in c:\users\administrator\miniconda3\lib\site-packages (from huggingface-hub>=0.13.2->diffusers) (2023.9.2)
Requirement already satisfied: tqdm>=4.42.1 in c:\users\administrator\miniconda3\lib\site-packages (from huggingface-hub>=0.13.2->diffusers) (4.66.1)
Requirement already satisfied: pyyaml>=5.1 in c:\users\administrator\miniconda3\lib\site-packages (from huggingface-hub>=0.13.2->diffusers) (6.0.1)
Requirement already satisfied: typing-extensions>=<IP_ADDRESS> in c:\users\administrator\miniconda3\lib\site-packages (from huggingface-hub>=0.13.2->diffusers) (4.8.0)
Requirement already satisfied: packaging>=20.9 in c:\users\administrator\miniconda3\lib\site-packages (from huggingface-hub>=0.13.2->diffusers) (23.0)
Requirement already satisfied: zipp>=0.5 in c:\users\administrator\miniconda3\lib\site-packages (from importlib-metadata->diffusers) (3.17.0)
Requirement already satisfied: charset-normalizer<4,>=2 in c:\users\administrator\miniconda3\lib\site-packages (from requests->diffusers) (2.0.4)
Requirement already satisfied: idna<4,>=2.5 in c:\users\administrator\miniconda3\lib\site-packages (from requests->diffusers) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\users\administrator\miniconda3\lib\site-packages (from requests->diffusers) (1.26.16)
Requirement already satisfied: certifi>=2017.4.17 in c:\users\administrator\miniconda3\lib\site-packages (from requests->diffusers) (2023.5.7)
Requirement already satisfied: colorama in c:\users\administrator\miniconda3\lib\site-packages (from tqdm>=4.42.1->huggingface-hub>=0.13.2->diffusers) (0.4.6)

You might want to try using pip install with the --force-reinstall option as shown below:
pip install --force-reinstall -r requirements.txt

im try
On Sun, Oct 1, 2023 at 4:28 PM Uminosachi @.***> wrote:

You might want to try using pip install with the --force-reinstall option
as shown below:
pip install --force-reinstall -r requirements.txt
—
Reply to this email directly, view it on GitHub
https://github.com/Uminosachi/inpaint-anything/issues/25#issuecomment-1742020604,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4D3PSKQXKXMZCMADIOXSDX5EZTHANCNFSM6AAAAAA5OF2QYI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Request to include the ability to list multiple primary calibrators

This request is for the ability to list multiple primary calibrators in the template file (e.g., in 'template.cfg': primary=1934-638,0823-500) so that the primary calibration stages can be run on all primary calibrators (if multiple exist).
This change would occur in the primary calibration stages located in the 'run_cal.py' script.
The ability to list multiple calibrators is required in the case where both primary calibrators (1934-638 and 0823-500) are present in the source list (e.g., because the data to be calibrated are from multiple observing runs where different primary calibrators were used).
This is already functional for the secondary calibrators, so this change would involve copying this existing functionality and applying it for the primary calibrators.
Currently, the code reads:
       for i, source in enumerate(slist):
            frqid = int(source[-4:])
            if frqid != frqb:
                continue
            if prical in source:
                pricalname = source
            elif seccal != "" and any([sc in source for sc in seccal.split(",")]):
                seccalnames.append(source)
            elif seccal_ext in source and seccal_ext != "":
                ext_seccalname = source
            elif polcal != "" and any([pc in source for pc in polcal.split(",")]):
                polcalnames.append(source)
            elif target_ext != "" and any(
                [es in source for es in target_ext.split(",")]
            ):
                ext_targetnames.append(source)
            else:
                targetnames.append(source)
                src_to_plot.append(source[:-5])

To include the ability to list multiple primary calibrators, the code could be changed to e.g.:
       for i, source in enumerate(slist):
            frqid = int(source[-4:])
            if frqid != frqb:
                continue
            if source.split('.')[0] in ['1934-638','0823-500']:
                pricalname = source
            elif seccal != "" and any([sc in source for sc in seccal.split(",")]):
                seccalnames.append(source)
            elif seccal_ext in source and seccal_ext != "":
                ext_seccalname = source
            elif polcal != "" and any([pc in source for pc in polcal.split(",")]):
                polcalnames.append(source)
            elif target_ext != "" and any(
                [es in source for es in target_ext.split(",")]
            ):
                ext_targetnames.append(source)
            else:
                targetnames.append(source)
                src_to_plot.append(source[:-5])

Thanks!

Relevant line is here: https://github.com/AlecThomson/quocka/blob/5818be4d070176a940e177df367c18461a09f19e/quocka/core/run_cal.py#L296

There's a few things here that will need a bit more thought. The calibration strategy currently relies on a single primary calibrator - so we'll need some method to determine which cal to choose. Naively, we could just select the primary closest in time to the secondary, but there may be some gotchas there. Tagging @gheald, @tjgalvin, @zhangxiang-planet

My immediate thought here is that we might be lucky and not have to worry about this. The 0823-500 source is known to be variable, so it should ideally not be used to establish the absolute flux scale in the same way 1934-638 is capable of doing. Any differences between the observed 0823-500 and its stored model would be absorbed into the bandpass solutions and carried through to the sources you copy the table through to.
In my experience, 0823-500 is observed when 1934-638 is below the horizon when observing starts and ATCA needs to have its set on online solutions derived (the dcal/pcal/acal steps). It makes sense as well to spend a few moments to observe 0823-500 to get a bandpass solution as a just in case.
Is the idea here simply to use a set of better bandpass solutions that are closer in time to the source? Was this perhaps prompted by some bad 1934-638 solution?

Noting that the observing strategy was just as @tjgalvin describes - i.e. 0823-500 only used when 1934-638 not high enough for setup purposes, but not intended to be used for primary calibration unless there are extenuating circumstances.
However I can imagine cases where we didn't get 1934-638 as planned for some reason, and then I would think bootstrapping 0823-500 from another observation (close on the calendar) would be useful to avoid the variability aspect.

In our previous QUOCKA data processing, only 1934-638 has been used as the primary calibrator.
However, after a few calibrating tests, we confirmed that 1934-638 was obviously the better flux calibrator, and we decided to use part of the set up observation on 1934-638 as the primary calibrator observation.

Thanks for the discussion, all! This makes a lot of sense.
For now @Sarah-Bradbury, I think we should continue using 1934-638 (if available) and only use 0823 if its not available.


mpifileutils using old mechanism for querying lustre striping of file

Run dwalk on a lustre 2.10 or 2.12 client.
The lustre client's console log reports this warning:
2020-06-02 13:21:48 [2265774.790703] Lustre: dwalk: using old ioctl(LL_IOC_LOV_GETSTRIPE) on [0x50003e49e:0x3:0x0], use llapi_layout_get_by_path()

The recommended interface, llapi_layout_get_by_path(), is available in Lustre >= 2.7.0.  See llapi_layout(7) for details.
mpifileutils should switch to using it.
I don't recall how it works, but I recall there being some mechanism to prevent this message from being emitted repeatedly.  Testing an mpifileutils change repeatedly may require use of a unique file each time, or umount and remount the lustre client to clear a flag.

Thanks, @ofaaland .  I'm trying to remember why dwalk would be making a call about lustre striping.
What version of mpiFileUtils were you using here?
Did you specify any command line options?

Hi @adammoody , sorry for missing such basic information in the bug report.  I'll reproduce it and get you more complete information.

Hi @ofaaland , did you get a chance to investigate this further?  If it's within mpiFileUtils, we'll fix it.  It's possible it might be coming from within MPI I/O, in which case, I'd like to forward this on to the MPI I/O developers.  I might have to work with you to narrow that down.

Hi Adam,
No, I forgot, thanks for the reminder.  I'll get back to you soon.
-Olaf

From: Adam Moody<EMAIL_ADDRESS>Sent: Thursday, July 2, 2020 3:25 PM
To: hpc/mpifileutils
Cc: Faaland, Olaf P.; Mention
Subject: Re: [hpc/mpifileutils] mpifileutils using old mechanism for querying lustre striping of file (#340)
Hi @ofaalandhttps://github.com/ofaaland , did you get a chance to investigate this further? If it's within mpiFileUtils, we'll fix it. It's possible it might be coming from within MPI I/O, in which case, I'd like to forward this on to the MPI I/O developers. I might have to work with you to narrow that down.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/hpc/mpifileutils/issues/340#issuecomment-653244575, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB73C47764WEKYKJ65SORZDRZUCNVANCNFSM4NVFBTMQ.

Hi Adam,
I'm unable to reproduce the issue with mpifileutils-0.10 (most recent in TCE as far as I can tell on oslic).  I see via nm that libmfu.so is using the correct function, llapi_layout_get_by_path().  I think I must have been using an old version, sorry for the bad report.
Closing this issue.


Try to add formatter-maven-plugin to ensure file are well formatted.

I tried formatter-maven-plugin.
But for now this is a failure as it does not exactly format as my eclipse IDE ...
This is an interesting track but don't want to take more time one this for now.

Done with #1281


BITMAKER-2971 estela notification improvements

Description
Add notifications module improvements
Issue
* Github Issue ID.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] My code follows the style guidelines of this project.
[ ] I have made corresponding changes to the documentation.
[ ] New and existing tests pass locally with my changes.
[ ] If this change is a core feature, I have added thorough tests.
[ ] If this change affects or depends on the behavior of other estela repositories, I have created pull requests with the relevant changes in the affected repositories. Please, refer to our official documentation.
[ ] I understand that my pull request may be closed if it becomes obvious or I did not perform all of the steps above.

@raymond1242 Check this PR pls


Crashing

I tryed to run it but it crashes, i added one extra line on the start ''input()'' that waits for a input to run the things after it, and i think the problem is your code, would like a response or something, im kinda new to python so i dont really know some parts of the code but mostly i can understand

it does work on repl.it but not in terminal

I just dint install requests module lol, make sure to do ''py -m pip install requests'' in terminal (NOT PYTHON TERMINAL) when installing requests module


was RenderingServer.black_bars_set_margins removed intentionally in Godot 4.0 beta 2

Godot version
4.0 beta 2
System information
Windows 10
Issue description
was RenderingServer.black_bars_set_margins removed intentionally?
Steps to reproduce
try running a project with code
Minimal reproduction project
No response

Which version was that method removed in?

Any plans to re-add this?
It would make sense as part of the Window class, setter/getters for black_bar_bottom, black_bar_top, black_bar_left, black_bar_right. Useful for drawing the game at a lower fixed resolution than the window size.

It would make sense as part of the Window class, setter/getters for black_bar_bottom, black_bar_top, black_bar_left, black_bar_right. Useful for drawing the game at a lower fixed resolution than the window size.

If you're looking for integer scaling, this is implemented in 4.2: https://github.com/godotengine/godot/pull/75784

Oh no that's not the problem, you can already set Window.content_scale_factor to integer values in 4.1. The point "black bars", or margins would be to have the aspect ratio of the viewport be different than the aspect ratio of the screen. (Since you can't control the size of the window, for example when in fullscreen.)


@import '3-sections/-sections-dir' (Not working)

Hello all,
I'm french so I'm sorry for my english :smile:
I started the last 3 days the DevTips Artitsit template tutorial. After several hours to install all the programs I'm now in the coding phase (part 4).
I created the same structure and my {% include header.html %} is working but for the CSS part I've some challenge.
If I add this code in my all.sass the css works

all.sass

---
---
body
	background-color: red

but if I add these the CSS NOT working, in the _site the file 'all' in not converting to .css but stay as a .sass

all.sass

@import '3-sections/-sections-dir'

_-sections-dir.sass

@import 'header'

header.sass

body
	background-color: pink

Here is my configuration file so far:

_config.yml

# Build settings
port: 8000
sass:
	sass_dir: _sass

Thanks for your help,
Damien

I hit this at the beginning also, try putting this in your _config.yml:
markdown: kramdown
permalink: pretty
highlighter: rouge

port: 8080

include: ['_includes/work']
exclude: ['the_design.psd']

sass:
  sass_dir: assets/css
  style: :nested

It's what I had to do before it worked for me.

@wiafe Thanks for your help but I still not working ....
also when I restart Jekyll here is the message that I have
MacBook-Damien:Website taber$ jekyll serve --watch
jekyll 2.5.3 | Error:  (/Users/taber/Website/_config.yml): found character that cannot start any token while scanning for the next token at line 6 column 1

_config.yml

markdown: kramdown
permalink: pretty
highlighter: rouge
port: 8000
sass:
	sass_dir: assets/css
	style: :nested

Thanks,
Damien

@dmenu Take out the highlighter I use that because I'm using jekyll on a PC.

@wiafe I style have the same error... :disappointed:

@dmenu Can you upload or share with me what you have so I can look over it?

@wiafe I sent you an eamil with my skyppe ...

@dmenu Sadly don't have skype on here can you upload it to google drive by chance and share?

Here is the code :)
Le 18/02/2015 à 7:40 AM, Randy Wiafe a écrit :

google drive

@wiafe I'll sent you a Zip on your email adresse :)

Go into index.html and type the --- up on top
---
---
<!DOCTYPE html>

I still have the have the same problem with the  _config.yml ...
:/
Le 18/02/2015 à 8:00 AM, Randy Wiafe a écrit :

Go into index.html and type the --- up on top

—
Reply to this email directly or view it on GitHub.

After several tests I saw that the .scss is working but not the .sass .. ??

Bonjour @dmenu is possible for you to send me your code so i can look over and see if i find the error.

@zeldanerd Yes do you have an email adress ? thanks, Damien

Yes you can contact me at<EMAIL_ADDRESS>

@dmenu @zeldanerd were you guys able to figure it out?

@waife @dmenu I still haven't but he has scss working. do want to code using .sass dmenu?

honestly if he wants to code his css .sass it's an easy fix to make it modular

@wiafe @zeldanerd at the moment I'm not able to find the solution for the .sass. My end goal is to have a website in html + css. Thanks for your help. Damien

Hey guys. Thanks for being so helpful. This is amazing. I am so appreciative :)
Can I have a look at your project?

@travisneilson Thanks for your help Travis. I just sent you an email .. Best regards, Damien

Got your email. Here is my take on it. I made a video.
http://youtu.be/98bfoRDligs
Hope its helpful :)

@travisneilson @wiafe @zeldanerd Thanks all for your help ... I'll continue all the serie ...  :+1: :)

Anytime! I'm glad I can help. And it was really cool to see others rushing in to support also. Thanks @zeldanerd and @wiafe — you rock!

@dmenu @dmenu No problem, I love to help others. Dmenu, If you ever need anymore help don't hesitate to ask for help. Travis its a pleasure, if it wasn't from all the help you have provide us, I don't think I would have even know how to fix his issue. :+1: :)

HI Everyone,
Having the same problem. Any help would be appreciated.
Thanks.