Draft: Add a symbol to verified events

This is an experiment with types:
import { verifiedSymbol, verifySignature, type Event } from 'nostr-tools'

const event: Event = { ... };

console.log(event[verifiedSymbol]) // `undefined` - the event has not been verified or rejected

verifySignature(event) // true

console.log(event[verifiedSymbol]) // `true` - the event has now been verified

verifySignature(event) // true, returns immediately instead of calling `schnorr.verify`

Now calling verifySignature(event) will set a [Symbol(verified)]: true on the event, so calling verifySignature multiple times on the same event will have no effect.
You can also guard functions to only allow verified events:
function validateAuthEvent(event: VerifiedEvent): event is VerifiedEvent<27235> {
  // do stuff with the verified event...
}

const event: Event = { ... }

validateAuthEvent(event) // type error
validateAuthEvent(verifySignature(event)) // pass

A good thing about symbols is that they're unique to the session, so you cannot spoof them. You have to import the symbol from nostr-tools to use this functionality directly, and the symbol will be dropped from JSON.stringify.

The main problem this solves is that verifySignature is computationally expensive, but sometimes you want a function to guarantee that the event is verified from any source, especially when building libraries. Sometimes you need to build layers where the signature is valid at every step.
This allows you to call it as many times as you want in your code while expending the effort only once.

This is very cool. Does it make sense to do the same for hashing the event into its id?

This is very cool. Does it make sense to do the same for hashing the event into its id?

That's a good point. I think [verifiedSymbol]: true should mean the id and sig are both valid, rather than introducing a new symbol for the id.
Fortunately the verifySignature function already recomputes the event ID instead of just trusting event.id. But it doesn't force the id to actually be valid.
We should either make verifySignature mutate the id if it's wrong, or return false. Probably the latter.


[BUG]: Check constraint does not get excluded on exclude []

on the following schema:
schema "public" {
}
table "table" {
  schema = schema.public
  column "id" {
    null    = false
    type    = uuid
    default = sql("gen_random_uuid()")
  }
  column "kind" {
    null = false
    type = text
  }

  primary_key {
    columns = [column.id]
  }

  check "CHK_kind" {
    expr = "((kind = 'affirmation') OR (kind = 'reversal'))"
  }
}

with the following atlas.hcl config:
env "fromdbs" {
  src = "./schema_constraint.hcl"

  // note the url is for the dev db which should only be used when modifying migrations
  url = "postgresql://postgres:password@localhost:6432/fromdb?sslmode=disable"

  exclude = ["*.*.CHK_kind"]
}

atlas schema inspect --env fromdbs > without_cons.hcl

Constraint is still there.
I expect the constraint to be filtered also

I have created a merge request for this one.

Thanks for reporting this and for the contribution, @andreimc. It's appreciated 🙏


Added a default Error 404 Page

Fixes: #177
Additional Info:

Added 404.html template.
Made the required changes in the urls.py & views.py file..

Screenshot:

@harsh-9in, @Kajol-Kumari Have a look.


Fix tests to run offline.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
Some tests do not work if you are offline, attempting to check out actual repositories and such. This fixes that.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2131 (e535d7b) into main (7940888) will increase coverage by 5.17%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #2131      +/-   ##
===========================================
+ Coverage   94.82%   100.00%   +5.17%
===========================================
  Files         154         6     -148
  Lines        4079       105    -3974
  Branches       19        19
===========================================
- Hits         3868       105    -3763
+ Misses        211         0     -211

Impacted Files
Coverage Δ

src/assemble_workflow/assemble_args.py

src/test_workflow/integ_test/integ_test_runner.py

src/manifests/input_manifests.py

src/run_bwc_test.py

src/assemble_workflow/bundle_file_location.py

src/paths/script_finder.py

src/test_workflow/integ_test/local_test_cluster.py

src/test_workflow/bwc_test/bwc_test_suite.py

..._workflow/perf_test/perf_test_runner_opensearch.py

src/system/working_directory.py

... and 138 more

Continue to review full report at Codecov.

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


Configure OpenAI endpoint

There are many tools/services that provide "OpenAI Compatable" endpoints in a bring-your-own-ai sort of way. Even moreso in corporate environments where we may have GPT-4 completion access that don't share or store corporate data provided on different endpoints (ie. From Azure).
Can the OpenAI endpoint be configurable so it transparently "just works" with any OpenAI-compatable endpoint?

Yes that is definitely feasible and probably relatively easy.  if you want to submit a PR, you could just create a setting to change the following from a string to a talon setting https://github.com/C-Loftus/talon-ai-tools/blob/62a1ad117ef5433462eb6dddb59bd6150683688f/GPT/gpt.py#L64  and then the user can specify the Talon setting for the url in a talon file
only thing I will say is sometimes the default system prompt is a bit different,  for instance for llamafiles I have to specify ( I don't know if this is a similar thing with azure I do not use that at all)
'messages': [
                    {
                        "role": "system",
                        "content": "You are an assistant helping an office worker to be more productive."
                    },
                    {
                        'role': 'user',
                        'content': f"{prompt}:\n{content}"
      }

Thanks for the reply!!
For Azure at least they provide direct access to OpenAI models for enterprises. So it's the same model.
Is there any weirdness if this points at an endpoint of that uses GPT-4?

I don't think so, but I'm honestly not sure since I haven't tested much with GPT-4 in general. (For personal use, a lot of people don't get access to it unless they have paid over a certain threshold, which my usage is not at yet.)
If you create a pull request to support this, I would be happy to merge. That being said, I will probably not implement this on my own since I don't have any endpoints to test with.
This is generally a good idea though and would help reduce some of the duplicate code I have for the llamafile anyways.

@douglasg14b  I believe I generalized this to support Azure and any compatible endpoint. Can you check out https://github.com/C-Loftus/talon-ai-tools/pull/24 and see if it works with your azure endpoint?  (you can use the gh cli tool to do this very easy if you aren't familiar)  If you can't test that is okay, since I tested and it works with local llamafiles, so at the very least that pull request is not a regression

Closing since I think this is addressed. Will reopen if we get the chance to test and find it doesn't work for some reason


in IOS9 Safari does not work FB and G+ login popups

I have problem with satellizer on mobile devices. Have read all previous threads and didn't find answer on this issue.
No problems with desktop devices
Tested this on iPad with IOs9 safari, and also android 6 / firefox.
Facebook popup opens, I enter my credentials in it, after submit it just closes and nothing happens.
My function:
function authenticate(provider) {
    console.log(provider);
    return $auth.authenticate(provider);
}

I can see console.log dump with "facebook" before auth.
Code that i'm running:
MyService
    .authenticate(provider)
    .then(onAuthSuccess)
    .catch(onAuthError);

onAuthSuccess and onAuthError are called only on desktops, but not on mobile devices ( tested on Ipad IOS9 Safari ),
looks like promise from .authenticate(provider) isn't returned on mobile devices.

+1
having the same issue
it seems to work on mobile Chrome though (iOS + Android)

Hi all -
I haven't resolved the issue but I have found some interesting behavior...
I am not super familiar with satellizer's code base so I am hoping someone could shed some light here to solve this issue for what seems like a lot of people!
In certain mobile browser versions, the main app tab seems to go "dormant" and doesn't see that the satellite oauth popup tab has returned with the ?code param.
I am seeing this on iOS Safari and Android Firefox.
Chrome does not have this issue in either iOS or Android.

user clicks on button to fire authenticate for FB/Google

satellite opens a new tab to auth with FB/Google and automatically navigates to it

user enter login info for FB/Google

satellite fires redirect to my specified redirect page with ?code param

EXPECTED BEHAVIOR:

satellite polls the 2nd tab (my redirect page) and then automatically closes it
user is brought back to original browser tab and is logged in to my app

ACTUAL BEHAVIOR:

the 2nd tab is not automatically closed and stays open indefinitely

BUT, what I notice is that after step 2,
A) if I MANUALLY navigate back to the original browser tab (WITHOUT closing the oauth tab), the original browser tab wakes up, the promise from auth.authenticate() is successfully resolved, and my user gets logged in
B) if I CLOSE the redirect tab (the one that has the ?code parameter), and am brought back to the original browser tab, nothing happens (presumably because it can no longer find the popup with the ?code param value)
For reference, here is my authProvider config for FB & Google. And this seems to occur on both Satellite 0.14 and 0.15.4
$authProvider.facebook({
name: 'facebook',
url: '/auth/facebook',
authorizationEndpoint: 'https://www.facebook.com/v2.5/dialog/oauth',
redirectUri: window.location.origin + '/auth/callback/index.html',
requiredUrlParams: ['display', 'scope'],
scope: ['email'],
scopeDelimiter: ',',
display: 'popup',
oauthType: '2.0',
popupOptions: { width: 580, height: 400 }
});
$authProvider.google({
url: '/auth/google',
authorizationEndpoint: 'https://accounts.google.com/o/oauth2/auth',
redirectUri: window.location.origin + '/auth/callback/index.html',
requiredUrlParams: ['scope'],
optionalUrlParams: ['display'],
scope: ['profile', 'email'],
scopePrefix: 'openid',
scopeDelimiter: ' ',
display: 'popup',
oauthType: '2.0',
popupOptions: { width: 452, height: 633 }
});

haha, directly related to #829

@chungconscious Did you found any resolution for this problem?

@Machecek - nope


Pass Content-ID to mailgun API

This is necessary for example to show inline image attachments in mail

I still need to test this... so don't merge yet.

huh... it created pull request to my own fork :D ok.. I myself promise I'm not going to merge this yet


help: resolution: 512 --> resolution: 128, train error!

The same data, my training in controlnet code is ok.
raceback (most recent call last):
File "/root/autodl-tmp/uni-controlnet/src/train/train.py", line 69, in
main()
File "/root/autodl-tmp/uni-controlnet/src/train/train.py", line 65, in main
trainer.fit(model,dataloader,)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 529, in fit
call._call_and_handle_interrupt(
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 42, in _call_and_handle_interrupt
return trainer_fn(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 568, in _fit_impl
self._run(model, ckpt_path=ckpt_path)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 973, in _run
results = self._run_stage()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 1016, in _run_stage
self.fit_loop.run()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/fit_loop.py", line 201, in run
self.advance()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/fit_loop.py", line 354, in advance
self.epoch_loop.run(self._data_fetcher)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 133, in run
self.advance(data_fetcher)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/training_epoch_loop.py", line 218, in advance
batch_output = self.automatic_optimization.run(trainer.optimizers[0], kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 185, in run
self._optimizer_step(kwargs.get("batch_idx", 0), closure)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 260, in _optimizer_step
call._call_lightning_module_hook(
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 144, in _call_lightning_module_hook
output = fn(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/core/module.py", line 1256, in optimizer_step
optimizer.step(closure=optimizer_closure)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/core/optimizer.py", line 155, in step
step_output = self._strategy.optimizer_step(self._optimizer, closure, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/strategies/strategy.py", line 225, in optimizer_step
return self.precision_plugin.optimizer_step(optimizer, model=model, closure=closure, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/plugins/precision/precision_plugin.py", line 114, in optimizer_step
return optimizer.step(closure=closure, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/optim/optimizer.py", line 280, in wrapper
out = func(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/optim/optimizer.py", line 33, in _use_grad
ret = func(self, *args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/optim/adamw.py", line 148, in step
loss = closure()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/plugins/precision/precision_plugin.py", line 101, in _wrap_closure
closure_result = closure()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 140, in call
self._result = self.closure(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 126, in closure
step_output = self._step_fn()
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/loops/optimization/automatic.py", line 307, in _training_step
training_step_output = call._call_strategy_hook(trainer, "training_step", *kwargs.values())
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 291, in _call_strategy_hook
output = fn(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/pytorch_lightning/strategies/strategy.py", line 367, in training_step
return self.model.training_step(*args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./ldm/models/diffusion/ddpm.py", line 443, in training_step
loss, loss_dict = self.shared_step(batch)
File "/root/autodl-tmp/uni-controlnet/./ldm/models/diffusion/ddpm.py", line 837, in shared_step
loss = self(x, c)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./ldm/models/diffusion/ddpm.py", line 849, in forward
return self.p_losses(x, c, t, *args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./ldm/models/diffusion/ddpm.py", line 889, in p_losses
model_output = self.apply_model(x_noisy, t, cond)
File "/root/autodl-tmp/uni-controlnet/./models/uni_controlnet.py", line 59, in apply_model
local_control = self.local_adapter(x=x_noisy, timesteps=t, context=cond_txt, local_conditions=local_control)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./models/local_adapter.py", line 401, in forward
local_features = self.feature_extractor(local_conditions)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./models/local_adapter.py", line 157, in forward
local_features = self.pre_extractor(local_conditions, None)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/root/autodl-tmp/uni-controlnet/./models/local_adapter.py", line 27, in forward
x = layer(x)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/conv.py", line 463, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/root/miniconda3/envs/controlnet/lib/python3.10/site-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Given groups=1, weight of size [32, 21, 3, 3], expected input[64, 6, 128, 128] to have 21 channels, but got 6 channels instead

+1


Add github link of this repo on website

Doing this may attract developers.

Awesome, we surely need one.
Here's the link of git ribbons that i came accross https://github.com/blog/273-github-ribbons
Up for it @Prakash2403 ?

I don't know HTML, CSS either 😄

Can I do this one? @Anshuman-Verma


Fixes and Installation Split

I tested everything. Please find the image here : https://registry.hub.docker.com/u/alexandrasandulescu/owtf-docker-mm/dockerfile/


Integration tests failing?

In trying to move the hard-wired files to a separate directory, I found I could not get the integration tests to pass, even on the current master.  Before I go digging, is anyone else having this problem?  (Trying to rule out my setup.)  I am running go test github.com/golang/dep/cmd/dep on go1.7.4 windows/amd64.
FWIW, I notice appveyor produced the same error on my PR - it can't remove a temp file because it is in use by another process.  Another data point is that on my PC, at least, the process ends thinking it is still running git (asking me for a password) which had clearly been launched during the test.  I'd suspect that as being the "other process".

@jessfraz any ideas here?

Has the file not been closed?
On Thu, Feb 2, 2017, 17:31 Peter Bourgon<EMAIL_ADDRESS>wrote:

@jessfraz https://github.com/jessfraz any ideas here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golang/dep/issues/214#issuecomment-277139788, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYNbBo4XaZV_K2n4_Dxl-lqlTGaELgmks5rYoN7gaJpZM4L0B5w
.

FWIW, I have it nailed down to specifically the RemoveTest, lines 90 and/or 114.  (Each launch a process/thread that does not terminate.)  Both try to 'remove' github.com/not/used.  (Note: line 82 go remove -unused runs fine, even with github.com/not/used present.)  In remove.go, it appears to be line 181 (s.Solve()) that launches the non-terminating processes, but I can't yet confirm it.

The s.Solve() call could initiate some processes that don't complete. Improved process management is one of my ongoing goals in gps...though there is handling in place that should prevent the test from ending before all subprocesses have terminated.
What's path to the tempfile that it's complaining about not being able to remove?
@mattn's already been great in help tracking down some of these issues, and I had someone get me access to a windows box recently so that I could work on it more directly, too. Hopefully we can get these all hammered out soon :/

The "file in use" is always (tempdir)\src\github.com\golang\notexist.  The two Runs that cause the issue don't actually reference this directory, though.  The first is remove github.com/not/used and the other is remove -force github.com/pkg/errors github.com/not/used.  I'll dig some more today.

Yes, seems to be running multiple tests. Sometimes running git on the directory when the error occured.

Okay, I've tracked it down.  During the TestRemove test in gps/deduce.go, line 558, maybeSource.try is being called inside a closure with an internal go routine:
srcfut := func(mb maybeSource) partialSourceFuture {
	return func(cachedir string, an ProjectAnalyzer) sourceFuture {
		var src source
		var ident string
		var err error

		c := make(chan struct{}, 1)
		go func() {
			defer close(c)
			src, ident, err = mb.try(cachedir, an)
		}()

		return func() (source, string, error) {
			<-c
			return src, ident, err
		}
	}
}

This leads to gps/vcs_source.go line 147 in doListVersions() calling an external "git ls-remote repoName" command.  But in the remove test, the repoName is github.com/not/exist.  On Windows with no RSA token set, this process hangs asking for a GitHub password.  The hanging process ties up the directory, so cleanup() can't clean up and we get the failure.
Not sure what to do about it, but that git ls-remote command in doListVersions() is definitely what's killing the integration tests on my machine, anyway.

Great sleuthing @tro3! (side note, I'm curious what you did to track that down
I'm guessing it's not just on Windows where we have an underlying problem with calls hanging on a password request. The only difference on *nix-y platforms is that such hanging calls don't appear to cause the same issues with directory handles, so it doesn't result in test failures.
The more general solution to safety in this realm is probably sdboyer/gps#159, or at least sdboyer/gps#84, but there's still a bit of work between here and there. It's also...annoying, as I thought that sdboyer/gps#141 would have taken another step to address this. (Clearly not on Windows, but it's the same general problem)
Meanwhile, I'm going to see if just changing around the upstream path of the nonexistent repo can help us out.

I set up a more direct test case, targeting removeCommand with proper setup instead of the build-and-run pattern.  Then I was able to get to it through a combo of debugger and good old-fashioned test code insertion.  Glad it paid off.

Underlyign issue is worked out


[Keyvault] adding ec key support for key create command

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

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

View a preview at https://prompt.ws/r/Azure/azure-cli/6169
This is an experimental preview for @microsoft users.

@tjprescott Could you review these changes?  The CI failure seems to be an issue with finding the latest release tag on the keyvault-preview branch.  I've tried syncing the tags, but this doesn't seem to fix the failure.


chore: cleanup

We probably need to this sooner or later...
// TODO:
// - if "not found", then don't render layouts after the closes not-found
//   - so we probably want to write this recursively with the information of RouteModuleTree
// - we want to use less-general RouteModuleTree based match, but
//   but that would prevent it to reuse for other
//   e.g. `route.js` match or preload match

But, before that, we probably need to cleanup "prefix" concept and replace it with "route id" or something.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#506  👈
#505
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @hi-ogawa and the rest of your teammates on  Graphite

Superseded by

https://github.com/hi-ogawa/vite-plugins/pull/509
https://github.com/hi-ogawa/vite-plugins/pull/507


Duplicate resources are displayed after resource creation

Describe the bug
Duplicate resources are displayed after resource creation.
Steps to reproduce
Create a resource and save as draft.

Environment

Walrus version:
UI: dev-d69ebcc
Server: dev-ee6f735

Environment

Walrus version: main ab30b62917ad1ab35c43d37fb7a646efbd9a1572
UI version: dev-2d14c4a

Test Result: pass


feat: add placeholderData to queryObserver

Trying my hand at a bit of Typescript! I feel so out of my element here... but hopefully not for long. 😉
This PR is clearly incomplete, but actually works as a solution in my codesandbox from #1158.
Thoughts here?

Great to see you are digging into it! I kind of like the placeholderData but do have two questions:

What are the benefits over using:

const { data = 'initial' } = useQuery()

The success status does not feel correct to me as the query has never been completed. It removes a bit of insight into the actual status of the query. Maybe it should be loading while having data?

1

You don't have to destructure to get the ease of setting the default.
You can hoist the placeholder data into a custom hook or configuration object, which is way more
composable/portable than scripting into the default value at every usage
It does not take care of the added state overrides needed to display the data.

2

Keep in mind, we're not changing the status of the query, just the observers interpretation of the query, much like isStale.
The data you're providing should be roughly compatible with any actual data you're displaying, so isSuccess is a pretty safe bet, especially when you consider that the user is opting into the placeholder data. Similar to initialData they can and should expect it to be treated like normal data while it's being filled.
Adding yet another state to the already complicates existing template flows for almost every user. isIdle was already difficult enough for most people to handle when we introduced it, and I think this would similarly add a weird step for users where it's unnecessary. eg.

return query.isLoading ? 'Loading' : query.isError ? 'Error' : 'Show Data JSX'

// Becomes

return query.isPlaceholder
  ? 'Show Successful JSX'
  : query.isLoading
  ? 'Loading'
  : query.isError
  ? 'Error'
  : 'Show Successful JSX'

Empirically, I can see how adding another state would make technical sense, but where successful and placeholder states are (and should be) almost identical in templating logic, I see more negatives (breaking everyone's templates who uses it) with introducing the new state.

Yeah a placeholderData option can indeed provide some additional convenience. I'm in favor of adding it. My main doubt is about the status property, which does not really seem to indicate the query has executed successfully anymore. It's becoming more of a flag to indicate data is not undefined instead of reflecting the current query status. It's one of the reasons why I think why value checking is more flexible and correct:
const { data } = useQuery()

if (data) {
  return
{data}

}

If you also want to know what kind of data it is:
const { data, isPlaceholderData } = useQuery()

if (data) {
  return
{data}

}

Hmmm. That would create a lot of upheaval from the current documentation, but if it's the right thing to do, we should discuss it thoroughly to make sure we're making the right move. It would be a relatively large change conceptually from what it's been in the past.

I think the whole data checking approach fits this situation pretty well, but it's when we get into showing/persisting errors and data that the approach rubs me the wrong way.

From a maintainer perspective, it costs us very little to just keep things the way they are and add the feature. It doesn't break anyone in v2 or v3 and it's pretty clear what the option is doing in the docs. We can always reformat things in the future, but my guess is that no one would even bat an eyelash at the placeholder/isSuccess combo for quite a long time.
In contrast, changing everything to be data/error/loading checking as a primary means of templating would be a ton of work  today and probably create a lot of churn for little payoff IMO.

Yeah I agree let's keep the value/status checking discussion in https://github.com/tannerlinsley/react-query/pull/1108. It should not be blocking this feature. Wouldn't a isPlaceholderData flag be handy if you want to show a loader or maybe a bit different design while rendering placeholder data?

Added

I'm guessing this will need to be manually added to v3 as well.

:tada: This PR is included in version 3.2.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

It's not clear from the docs if setting placeholderData means the hook won't suspend even when isLoading and suspense are both true.


Cannot import ECS Service - diffs on taskDefinition

I have a Service:
const testService = new aws.ecs.Service("test", {
    cluster: mainCluster.id,
    desiredCount: 1,
    iamRole: ecsServiceRole.name,
    loadBalancers: [{
        containerName: "ghost",
        containerPort: 2368,
        targetGroupArn: testTargetGroup.id,
    }],
    name: "tf-example-ecs-ghost",
    taskDefinition: ghost.arn,
}, {dependsOn: [frontEnd, ecsServiceRolePolicy]});

This is converted from the following Terraform:
resource "aws_ecs_service" "test" {
  name            = "tf-example-ecs-ghost"
  cluster         = "${aws_ecs_cluster.main.id}"
  task_definition = "${aws_ecs_task_definition.ghost.arn}"
  desired_count   = 1
  iam_role        = "${aws_iam_role.ecs_service.name}"

  load_balancer {
    target_group_arn = "${aws_alb_target_group.test.id}"
    container_name   = "ghost"
    container_port   = "2368"
  }

  depends_on = [
    "aws_iam_role_policy.ecs_service",
    "aws_alb_listener.front_end",
  ]
}

The Terraform has the following in it's .tfstate:
                "aws_ecs_service.test": {
                    "type": "aws_ecs_service",
                    "depends_on": [
                        "aws_alb_listener.front_end",
                        "aws_alb_target_group.test",
                        "aws_ecs_cluster.main",
                        "aws_ecs_task_definition.ghost",
                        "aws_iam_role.ecs_service",
                        "aws_iam_role_policy.ecs_service"
                    ],
                    "primary": {
                        "id": "arn:aws:ecs:us-west-2:153052954103:service/tf-example-ecs-ghost",
                        "attributes": {
                            "capacity_provider_strategy.#": "0",
                            "cluster": "arn:aws:ecs:us-west-2:153052954103:cluster/terraform_example_ecs_cluster",
                            "deployment_controller.#": "1",
                            "deployment_controller.0.type": "ECS",
                            "deployment_maximum_percent": "200",
                            "deployment_minimum_healthy_percent": "100",
                            "desired_count": "1",
                            "enable_ecs_managed_tags": "false",
                            "health_check_grace_period_seconds": "0",
                            "iam_role": "tf_example_ecs_role",
                            "id": "arn:aws:ecs:us-west-2:153052954103:service/tf-example-ecs-ghost",
                            "launch_type": "EC2",
                            "load_balancer.#": "1",
                            "load_balancer.4095830738.container_name": "ghost",
                            "load_balancer.4095830738.container_port": "2368",
                            "load_balancer.4095830738.elb_name": "",
                            "load_balancer.4095830738.target_group_arn": "arn:aws:elasticloadbalancing:us-west-2:153052954103:targetgroup/tf-example-ecs-ghost/cb706fb72030d5d9",
                            "name": "tf-example-ecs-ghost",
                            "network_configuration.#": "0",
                            "ordered_placement_strategy.#": "0",
                            "placement_constraints.#": "0",
                            "placement_strategy.#": "0",
                            "platform_version": "",
                            "propagate_tags": "NONE",
                            "scheduling_strategy": "REPLICA",
                            "service_registries.#": "0",
                            "tags.%": "0",
                            "task_definition": "arn:aws:ecs:us-west-2:153052954103:task-definition/tf_example_ghost_td:1"
                        },
                        "meta": {},
                        "tainted": false
                    },
                    "deposed": [],
                    "provider": "provider.aws"
                },
                "aws_ecs_task_definition.ghost": {
                    "type": "aws_ecs_task_definition",
                    "depends_on": [
                        "data.template_file.task_definition"
                    ],
                    "primary": {
                        "id": "tf_example_ghost_td",
                        "attributes": {
                            "arn": "arn:aws:ecs:us-west-2:153052954103:task-definition/tf_example_ghost_td:1",
                            "container_definitions": "[{\"cpu\":256,\"environment\":[],\"essential\":true,\"image\":\"ghost:latest\",\"logConfiguration\":{\"logDriver\":\"awslogs\",\"options\":{\"awslogs-group\":\"tf-ecs-group/app-ghost\",\"awslogs-region\":\"us-west-2\"}},\"memory\":512,\"mountPoints\":[],\"name\":\"ghost\",\"portMappings\":[{\"containerPort\":2368,\"hostPort\":8080,\"protocol\":\"tcp\"}],\"volumesFrom\":[]}]",
                            "cpu": "",
                            "execution_role_arn": "",
                            "family": "tf_example_ghost_td",
                            "id": "tf_example_ghost_td",
                            "memory": "",
                            "network_mode": "",
                            "placement_constraints.#": "0",
                            "proxy_configuration.#": "0",
                            "requires_compatibilities.#": "0",
                            "revision": "1",
                            "tags.%": "0",
                            "task_role_arn": "",
                            "volume.#": "0"
                        },
                        "meta": {
                            "schema_version": "1"
                        },
                        "tainted": false
                    },
                    "deposed": [],
                    "provider": "provider.aws"
                },

When I try to import - I get:
    = aws:ecs/service:Service: (import)
        [id=arn:aws:ecs:us-west-2:153052954103:service/tf-example-ecs-ghost]
        [urn=urn:pulumi:luke-import::ecs-alb::aws:ecs/service:Service::test]
        [provider=urn:pulumi:luke-import::ecs-alb::pulumi:providers:aws::default_1_16_0::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
      ~ taskDefinition: "tf_example_ghost_td:1" => "arn:aws:ecs:us-west-2:153052954103:task-definition/tf_example_ghost_td:1"

This appears to be because AWS normalizes the value of the taskDefinition property on a Service to be just <family>:<revision>, even though it accepts an ARN as well.
I suppose the workaround is that I have to figure out how to specify this <family>:<revision> format so that I provide the post-normalization value.  But that's an unfortunate step to require.
Can we make this experience better?

@lukehoban I think we can now close this out due to the improved import experience:
pulumi import aws:ecs/taskDefinition:TaskDefinition test arn:aws:ecs:us-east-1:894850187425:task-definition/archive-handler-95a7a3f0:5
Previewing import (test)

View Live: https://app.pulumi.com/stack72/test-sg-import/test/previews/df7a44c8-785e-4e21-94de-bdc95bb2d42f

     Type                       Name                 Plan
 +   pulumi:pulumi:Stack        test-sg-import-test  create
 =   └─ aws:ecs:TaskDefinition  test                 import

Resources:
    + 1 to create
    = 1 to import
    2 changes

Do you want to perform this import? yes
Importing (test)

View Live: https://app.pulumi.com/stack72/test-sg-import/test/updates/1

     Type                       Name                 Status
 +   pulumi:pulumi:Stack        test-sg-import-test  created
 =   └─ aws:ecs:TaskDefinition  test                 imported

Resources:
    + 1 created
    = 1 imported
    2 changes

Duration: 4s

Please copy the following code into your Pulumi application. Not doing so
will cause Pulumi to report that an update will happen on the next update command.

Please note that the imported resources are marked as protected. To destroy them
you will need to remove the `protect` option and run `pulumi update` *before*
the destroy will take effect.

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const test = new aws.ecs.TaskDefinition("test", {
    containerDefinitions: "[{\"cpu\":4,\"environment\":[],\"essential\":true,\"image\":\"894850187425.dkr.ecr.us-east-1.amazonaws.com/archive-handler-image-f8aa5d0:f8209f19a3e3dac804b58998c542e4146a83098e1dff464bda95925b25fca32e\",\"logConfiguration\":{\"logDriver\":\"awslogs\",\"options\":{\"awslogs-group\":\"archive-handler-44c019f\",\"awslogs-region\":\"us-east-1\",\"awslogs-stream-prefix\":\"container\"}},\"memory\":4096,\"mountPoints\":[],\"name\":\"container\",\"portMappings\":[],\"volumesFrom\":[]}]",
    cpu: "512",
    executionRoleArn: "arn:aws:iam::894850187425:role/archive-handler-execution-2b61e67",
    family: "archive-handler-95a7a3f0",
    memory: "4096",
    networkMode: "awsvpc",
    requiresCompatibilities: ["FARGATE"],
    taskRoleArn: "arn:aws:iam::894850187425:role/archive-handler-task-6824e5c",
}, {
    protect: true,
});

I don't get that diff when importing - if you feel we should reopen this then please do
Paul


TextRNN model details

Hello.
Is there any chance to get some reference to papers (or any other documents) to the TextRNN model?
Thanks in advance.

it is quite simple, so may be no need paper.


Add support for NEO

Name: NEO
HD Derivation Scheme:
Symbol: NEO
Documentation:   NEO
Checklist

[ ] Coin configuration

[ ] coin type / decimals

[ ] recommended block explorer (example)

[ ] Account / Address (https://www.nanode.co/docs#account)

[ ] derived from a seed

[ ] from public key / string

[ ] validation

[ ] Transaction / Block (https://www.nanode.co/docs#block)

[ ] serialization

[ ] signing

[ ] C interfaces

[ ] Validate generated code in Android and iOS projects

[ ] Tests

[ ] Unit test

[ ] integration test ( Java / Swift)

@ArtemGoryunov the links in the issue are still about Nano

@hewigovens thanks, fixed


unable to render inside blender

when i try to render  a simple scene it only exports the scene but it doesn't render in blender. i have to open the scene from project folder to render using appleseed.studio.

Yes, the latest version of the Blender plugin requires the latest version of appleseed which is about to be released. Hold on!

ok thank you :)

Will this new version have AOVs in blender

It won't, but after the 1.8.0 mega-release we will iterate on the various plugins and start filling the gaps.


Decouple identification from reconstruction databases

MOB-typer and recon should be able to optionally take a mash sketch for determining closest neighbor for ID  and cluster assignment purposes only. This would allow users to have custom databases for their own private collections without needing to validate the MOB-recon reconstruction workflow every time they want to add a new plasmid for ID purposes.

MOB-suite v. 3.0.0 now allows for this


APIV2: RawKV MVCC GC

Signed-off-by: ystaticy<EMAIL_ADDRESS>What is changed and how it works?
Issue Number: Ref https://github.com/tikv/tikv/issues/11965
What's Changed:
support RawKV MVCC garbage collection

Check List
Tests

Unit test
Integration test

/run_test

/run-test

/run-test

LGTM

/merge

/run-test

/run-test

/run-test


Feature

Is your feature request related to a problem? Please describe
In mobile next button is visible after scrolling , it could be best it is visible in first view without scroll.
https://github.com/CircuitVerse/CircuitVerse/assets/72077931/9153a852-995b-481a-b4c6-531c5adeb3ee
Describe the solution you'd like
We could fix width and change some content so that next will be visible.
Describe alternatives you've considered
No response
Additional context
No response
Are you working on this?
Yes

I am working on this

@tanmoysrt shall I take this up.


accounts: return InstitutionDetails next to routing number

This was requested by @joshsadler for the UI. It'll include FI information related to each Account.
Example:
$ curl -s localhost:8087/customers/52840ffb2becc6633778e9689e5c9bb50f7ce151/accounts | jq .

[
  {
    "accountID": "375e4036a22b928b4bba4a63eb3ed5c2471be84d",
    "maskedAccountNumber": "******1000",
    "routingNumber": "323274270",
    "status": "validated",
    "type": "Checking",
    "institution": {
      "name": "OREGON STATE CREDIT UNION",
      "routingNumber": "323274270",
      "phoneNumber": "5417144000",
      "address": {
        "address1": "PO BOX 306",
        "city": "CORVALLIS",
        "state": "OR",
        "zip": "97339"
      }
    }
  }
]

Codecov Report

Merging #103 into master will increase coverage by 0.36%.
The diff coverage is 64.91%.


depending on backports-zoneinfo backports.zoneinfo

Expected behaviour:
pip3 install flexget or equivalent should install flexget.
Actual behaviour:
Collecting backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget)
  Could not find a version that satisfies the requirement backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget) (from versions: )
No matching distribution found for backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget)

Additional information:
A dependency error is reported because no suitable version of backports-zoneinfo can be found.  PyPI seems to have no such package, but there is backports.zoneinfo with the expected version number.  Manually adjusting the requirement allows flexget to be installed and to run.
I am assuming that the METADATA file in the package, where I made my edit, corresponds to requirements.txt.  I see that the relevant line in requirements.txt was added just over a month ago with commit 4358202cab5223da65ad90b20679f03cfdd7a8eb .  The commit message is "Try out poetry for dependency management", so I wonder if poetry made the mistake.
Recommendation:
s/backports-zoneinfo/backports.zoneinfo/

This is an issue with old versions of pip. The new packaging standard
normalizes to dashes, but old pip versions don't understand. Should work
fine if you upgrade pip
On Sun, Nov 13, 2022, 21:48 abugher @.***> wrote:

Expected behaviour:
pip3 install flexget or equivalent should install flexget.
Actual behaviour:
Collecting backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget)
Could not find a version that satisfies the requirement backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget) (from versions: )
No matching distribution found for backports-zoneinfo==0.2.1; python_version >= "3.7" and python_version < "3.9" (from flexget)
Additional information:
A dependency error is reported because no suitable version of
backports-zoneinfo can be found. PyPI seems to have no such package, but
there is backports.zoneinfo with the expected version number. Manually
adjusting the requirement allows flexget to be installed and to run.
I am assuming that the METADATA file in the package, where I made my
edit, corresponds to requirements.txt. I see that the relevant line in
requirements.txt was added just over a month ago with commit 4358202
https://github.com/Flexget/Flexget/commit/4358202cab5223da65ad90b20679f03cfdd7a8eb
. The commit message is "Try out poetry for dependency management", so I
wonder if poetry made the mistake.
Recommendation:
s/backports-zoneinfo/backports.zoneinfo/
—
Reply to this email directly, view it on GitHub
https://github.com/Flexget/Flexget/issues/3610, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABNV7OIP7ELO6OYEDK3BSLWIGR6FANCNFSM6AAAAAAR7LHJJY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for the quick answer.  I'm taking that to mean WNF since the code is correct, and the real problem is that my environment was too old.
Be advised that the pip shipped with Debian 10 Buster doesn't seem new enough to handle it.  Debian 11 Bullseye is currently marked "stable", but 10 is "oldstable", and it looks like 9 is "LTS".  So this will affect any of those users, but only if they try to install or update flexget using the pip supplied by the OS.  I don't know how common that is, and I'll just let you figure out whether that's something to worry about.
I'm up and running, though.  I appreciate you keeping up the project.  I've gotten years of use out of flexget, with no end in sight.
Closing.

I've been thinking for a while about changing our docs to have pipx as the
primary install method. I believe that would automatically use a new
version of pip, as well as take care of isolating the install in a virtual
environment and adding flexget to the PATH. Maybe it's time to pull the
trigger on that
On Mon, Nov 14, 2022, 20:15 abugher @.***> wrote:

Thank you for the quick answer. I'm taking that to mean WNF since the code
is correct, and the real problem is that my environment was too old.
Be advised that the pip shipped with Debian 10 Buster doesn't seem new
enough to handle it. Debian 11 Bullseye is currently marked "stable", but
10 is "oldstable", and it looks like 9 is "LTS". So this will affect any of
those users, but only if they try to install or update flexget using the
pip supplied by the OS. I don't know how common that is, and I'll just let
you figure out whether that's something to worry about.
I'm up and running, though. I appreciate you keeping up the project. I've
gotten years of use out of flexget, with no end in sight.
Closing.
—
Reply to this email directly, view it on GitHub
https://github.com/Flexget/Flexget/issues/3610#issuecomment-1314624263,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABNV7PEJFQKLTSC6C7KSBTWILP4HANCNFSM6AAAAAAR7LHJJY
.
You are receiving this because you commented.Message ID:
@.***>


Provide Tooling Support for the Resequencer EIP

Description:
We need to provide WSO2 ESB/EI Tooling support for the Resequencer EIP.
Currently, this is implemented to be used via the Management Console only in WSO2 ESB 4.9.0.
Please refer [1] for further details.
[1] https://docs.wso2.com/display/IntegrationPatterns/Resequencer
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

moved to https://github.com/wso2/product-ei/issues/2458


add network-only ipv6 statistics

Currently, on the "edit" page for a prefix, it shows the statistics for the entire space. In the case of ipv6, when the prefix is shorter than a /64, it would generally be more useful if it only considered the most significant 64 bits.
For example, how many /64s a /51 contains and how many/what percentage of those /64s are used up.
The current statistics however is calculating how many /128s (addresses) have been used up.
Perhaps the cut-off could be specified (defaulting to /64) as its also useful to know how many /56 or /60 (for example) have been consumed out of some larger block). Or alternatively it could show the statistics for each longer 4-bit boundary up to 64. (if the prefix is a /51, then show how many /52, /56, /60, and /64s are consumed); or base it on what longer prefixes are allocated out of the prefix being editied. I think this last one might be best, unless there are no longer prefixes, then it could use the every 4 bits version.
Example of current statistic:
Prefix xxxx:xxxx:1028:e000::/51 contains 1.5111572745182865e+23 addresses out of which<PHONE_NUMBER>1128655000 are in use while 1.5106038721960752e+23 are free, representing a usage of 0.0%.
More useful for us (in this case we allocate /64s from this 51, and don't care what portion of that 64 has been used up, effectively being an infinite amount of space for practical purposes):
Prefix xxxx:xxxx:1028:e000::/51 contains 8,192 /64's out of which 5 are in use while 8,187 are free, representing a usage of 0.0006% (or 0.0% is probably good enough).

This is a conscious design decision. I didn't want to keep statistics for all potential prefix lengths and at the same time I don't want to add a lot of extra "noise", ie having another option to specify what prefix length to keep stats for - it feels like a very niched use case.
The solution is to use pools since pools will calculate statistics not only on free addresses but also on free prefixes of the default-prefix-length.


Add second vaccination astraZeneca

I hope I didn't forget anything 😄

And dont forget the docs!

looks fine for me!

hopefully marlon will merge this request soon ...

tested on my local server, it works fine

Thanks @frauhottelmann for this PR, looks good!
And thank you @Rubber1Duck for reviewing. Great job!


DefaultDevice should be an alias of BestAvailable

DefaultDevice was added as a new name of BestAvailable which is marked deprecated. They should be aliases of each other, not distrinct devices.

Linking for ref: https://github.com/tracel-ai/cubecl/pull/210


Add go.mod heuristics

Description

Checklist:

[x] I am fixing a misclassified language

[ ] I have included a new sample for the misclassified language:

Sample source(s):

[URL to each sample source, if applicable]

Sample license(s):

[x] I have included a change to the heuristics to distinguish my language from others using the same extension.

As for the samples I've provided, they are modified copies of existing samples in the repository.

This won't work as .mod is not associated with the "Go Module" language, and it probably shouldn't be.
A better solution would be to add .go.mod as an extension to the current language definition:
https://github.com/github-linguist/linguist/blob/d190ad88af555bb2ee213aa64205f2b9a97a077d/lib/linguist/languages.yml#L2547-L2557
... though usage isn't anywhere near popular enough for inclusion right now.
Until then, peeps will need to use an override to force the langauge.

though usage isn't anywhere near popular enough for inclusion right now.

What are the criteria for being popular enough?
For the record, almost every Golang repo uses the go.mod files. >900k results in the following search: https://github.com/search?q=path:go.mod&type=code

This won't work as .mod is not associated with the "Go Module" language, and it probably shouldn't be.

A better solution would be to add .go.mod as an extension to the current language definition:

@lildude , thank you for your suggestion!
Most of the current go.mod files are misclassified for AMPL in the search, unless I query path:go.mod language:"Go Module".
As far as I understand, the problem is in the following code:
https://github.com/github-linguist/linguist/blob/a0a6d59bdcb7e4f4b3f549a7256cd8ff685a1d08/lib/linguist/heuristics.rb#L123
... heuristics are applied based on a filename suffix, and they do not depend on the extensions listed in languages.yml.
Could you please elaborate more on how are languages.yml connected with the heuristics.yml and how modifying the languages.yml will fix the problem I see?

What are the criteria for being popular enough?

See https://github.com/github-linguist/linguist/issues/5756, also referenced from the CONTRIBUTING.md file.

For the record, almost every Golang repo uses the go.mod files. >900k results in the following search

Indeed. And Linguist already has support for go.mod files. I was referring to *.go.mod files. There are only 61 files indexed with the .go.mod extension.

Most of the current go.mod files are misclassified for AMPL in the search, unless I query path:go.mod language:"Go Module".

That's only in the search results, which uses a different internal library to detect the language. This internal library happens to feed off Linguist, but not perfectly as it's not a 1:1 match in terms of functionality. The actual files are already correctly identified by Linguist and the syntax highlighter applies the correct syntax highlighting too.
We can confirm this from the first result in your search results: https://github.com/jmoiron/sqlx. This is what the search results show - wrong language and wrong syntax highlighting:

However if you view the file, you get the correct syntax highlighting:

And if we use Linguist to analyse it, we get the correct language:
➜ github-linguist sqlx/
99.74%  220442     Go
0.26%   583        Makefile
➜ github-linguist sqlx/go.mod
sqlx/go.mod: 9 lines (7 sloc)
  type:      Text
  mime type: text/plain
  language:  Go Module
➜

Which aligns with the language stats shown in the sidebar of the repo:

AMPL is considered a detectable language by default in Linguist so if Linguist had incorrectly determined the language as AMPL, it would appear in the results above.
Unfortunately, no amount of tweaking Linguist is going to resolve this issue with what Search is showing. The team that handles Search will need to address this incorrect behaviour.
Please use the "Contact" link at the bottom of the page showing the wrong search results and log a support ticket. The issue will get routed to the correct team to address.

@lildude , it seems like my changes are not required, and the problem is on the GitHub side. Should I report the problem somewhere?

@lildude , thank you for clarifying that! It looks like my changes are not required, and the problem is on the GitHub side. Should I report the problem somewhere?

Yes. From my previous comment 😉:

Please use the "Contact" link at the bottom of the page showing the wrong search results and log a support ticket. The issue will get routed to the correct team to address.

For the record, here is a bug report: https://github.com/orgs/community/discussions/136097


FreeBSD

Hi Folks,
I am a user centos 7 and currently using nginx + pagespeed. In the near future all production machines will migrate to FreeBSD 11. In This I want to ask

Pagespeed Support FreeBSD?
Is there any alternative if no support?

You can find details about work required to support FreeBSD in #308 and current tracking #1073.
I do not know of a good alternative, that runs direly in your local web-server. There are cloud based CDNs with similar capabilities.

There was this FreeBSD port by @mmokhi  for mod_pagespeed, I'm not sure if it has been updated, but if so it could provide a potential alternative.

Unfortunately the https://github.com/mmokhi/mod_pagespeed is out of sync with www/mod_pagespeed Port. Moreover, the Port got deleted on 2020-09-19 and was marked broken Aug 2020.


fix(other): 修复tbinlogdumper表结构导入的bug

关联研发信息
dev_branch: fix/tbinlogdumper_schema_load_bug/#2576
target_branch: v1.3.0


E2E runs in a single invocation of Playwright

Uses a Playwright improvement that just shipped in 1.24.0.
This speeds E2E slightly, and brings it a step closer to the intended vision.

Yes - I keep looking for small ways to make it cleaner, to compensate for the inevitable big bump in complexity to support the matrix (N cases * M targets) testing coming up.


Create wifi_smart_garage_door

This looks like a clone of the loratap (or perhaps the loratap is a clone of this). I've fleshed out the dps with descriptions of what they do for mine - not sure if loratap is the same.
The open/ close timer has been hidden - you can use an automation in home assistant to do this anyway. I've only left it in to help with device recognition (not sure if this is the correct approach).
Also, not sure if this is possible to implement but it would be good with devices like this that are supposed to attach to "dumb" garages to use the travel time. Here's the issue with the current implementation:

The switch is actually just a dumb switch that starts/ stops the garage motor i.e. pressing on will open/ close/ stop the motor depending on the current state.
With the way it's currently implemented, say the garage detects something is in the way while closing (using its maximum force sensor or an IR sensor), it will automatically reverse direction and open fully.
If this occurs HA will be stuck in a permanently "closing" state and the controls will not work.

This would also be good so that a stop feature can be implemented (just in case there is an obstruction and you do need to stop it quickly).

I will modify the loratap config rather than add a new one, but first there are a few queries and tips for future reference.

I will modify the loratap config rather than add a new one, but first there are a few queries and tips for future reference.

Shall I close pull request?
Have made commits to fix those silly typos/ logic. Sorry, I'm very new to this.

I'll close it once the loratap modifications are committed. For now, leave it open for tracking.

You don't seem to have pushed the commit, so I can't see what the final resolution is for that last timer, which had me confused as to what actually was meant.

For the logic changes, it is quite difficult as it involves tracking previous state and timings, while this integration tries to stick to a simple mapping of device values to HA values.  It is a shame so many Tuya cover devices are implemented so simply without proper feedback, and expect the app to use timers to keep track of the closing and opening times - at least this one has a dp that tells the opening/closing time though.

Oops, I stepped out for coffee before hitting commit... done now.
I'll raise an issue regarding my two suggested fixes for the logic.


Comments for members of anonymous return types are not emitted

Search terms
anonymous return types
Expected Behavior
Sorry if this has been covered before but it's hard to search on!
Ideally typedoc should emit comments for anonymous return types, for example:
/** Comments in return type should be emitted */
export function testme1() {
  return {
    /** The foo (should be emitted) */
    foo: "42",
    /** The bar (should be emitted) */
    bar: 42
  };
}

Actual Behavior
These comments are not emitted. Anonymous types as parameters are correctly emitted.
Steps to reproduce the bug
https://codesandbox.io/s/typedoc-anonymous-return-types-4df51?file=/src/test.ts
Environment
    "typedoc": "0.22.10",
    "typescript": "4.1.3"

I think this is a new one, though related to a few other "comment discovery" issues - unfortunately fixing this is going to be annoying... because to fix it we really need to start using symbol.getDocumentationComment... which is usually fine, until someone uses declaration merging or @inheritdoc, and then it doesn't play "nicely"... at least according to how TSDoc says it ought to work... the temptation to say "TSDoc isn't important" is very strong right now...
Alternatively, a fix could be to re-implement the ~1000 lines of code necessary to duplicate how the compiler does comment discovery, stripping out the inheritdoc bits... which will work until something changes in the compiler.

TypeDoc 0.23


Committing offsets on Kafka side for monitoring purposes?

Quickwit ensures exactly-once semantics by storing Kafka offsets in the metastore on a split publish.
We may also want to commit offsets after a split publish on Kafka side too. The benefit would be that Kafka will be aware of the lag of the consumers, it can be helpful for monitoring purposes.
However, I'm not sure if we can do it correctly, we would need to commit offsets on Kafka without interfering with our Kafka consumers.
There is also an alternative: a monitoring dashboard could compare the latest publish offsets by calling the Quickwit API and thus be available to track the lag.

This also has been requested by another user. @yangshike, can you describe your use case? Is it related to retention?

Closed via #3638.


fully connected layer(after crop) without regularization? How it will influence the class prediction?

regularization is added. see network.py.


[fr] transparent samples would be very helpful

Hope some one share basic transparent demos, especially how to sort transparent objects in a WebGPU pass.

There are a lot of possible algorithms for this. They're not WebGPU specific, although many newer algorithms probably would be more possible in WebGPU than in WebGL. If you're looking for techniques, you can check out some Order-Independent Transparency (OIT) techniques online and see what could be implemented. Or you can use CPU-side or GPU-side sorting to execute your draw calls in front to back order, if that works for your application.

The A-buffer sample now shows one algorithm for order-independent transparency.


Typo in architecture.md

Closes #
Proposed Changes

I submit this contribution under Apache-2.0 license.

@idan-gur Thank you for your contribution.


SAM-2914 - Auto submit job doesn't handle extended due dates

It seems like fixing it correct wasn't as bad as I thought it was going to be. There was also a bug in here where assessment wasn't even set until near the very end, so it either was looking at the wrong assessment while it was doing this process or not looking at any assessment at all for double checking dates.

I had an idea of doing adding just the simple check to the query but not 100% sure if that was working right or not.
https://github.com/sakaiproject/sakai/compare/master...jonespm:SAM-2914-query?expand=1

I'm going to close this for the moment so nobody merges. This appears to be working, but when it actually submits on behalf of the user it's marking them as late, which is something I need to fix on Monday.


Update: Cleanup some binding

Current coverage is 100.00%

Merging #85 into master will not affect coverage as of 72bfd99

@@            master     #85   diff @@
======================================
  Files           15      15
  Stmts          128     130     +2
  Branches         0       0
  Methods          0       0
======================================
+ Hit            128     130     +2
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 72bfd99

Powered by Codecov. Updated on successful CI builds.

LGTM

Merging...


[AutoRelease] t2-avs-2024-05-09-24312(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5191
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=978
BuildTargetingString
azure-mgmt-avs
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/5191


Remove java7/8 directories. Currently we do not need any feature from java8.

The final plan is to have fewer packages that users need to depend on and work on any platform with the best performance possible.

Codecov Report

Merging #292 into master will increase coverage by 0.33%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #292      +/-   ##
============================================
+ Coverage     93.57%   93.91%   +0.33%
- Complexity      456      460       +4
============================================
  Files            78       78
  Lines          1774     1774
  Branches        110      110
============================================
+ Hits           1660     1666       +6
+ Misses           84       77       -7
- Partials         30       31       +1

Impacted Files
Coverage Δ
Complexity Δ

...n/java/com/google/instrumentation/stats/Stats.java
60% <0%> (ø)
3% <0%> (+1%)
:arrow_up:

...ogle/instrumentation/trace/TraceComponentImpl.java
100% <0%> (ø)
1% <0%> (?)

...google/instrumentation/stats/StatsManagerImpl.java
100% <0%> (ø)
1% <0%> (?)

...java/com/google/instrumentation/trace/Tracing.java
92.85% <0%> (+14.28%)
7% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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


Audit the pkgng recipe for needed updates

We need to do a code review on the pkgng recipe to see if there are any needed updates or deletions to the recipe.

@martinisoft Seems like we can remove it at this point with FreeBSD 10+ being the only supported release.


Add spectacular auto-documentation page

What is drf-spectacular
It's auto documentation! Produces documentation based on your code, so it's always up to date with your changes. The generation is heavily based on your Serializers, Views, and the urls.py
Check out: https://drf-spectacular.readthedocs.io/en/latest/
Changes

Add type hinting on some Serializers to make spectacular
Add app-names to help add sections in the drf-spectacular
Add some extend_schema on some methods to override inferred documentation by drf-spectacular

Testing
Checkout the following webpages:

https://potato-oomfie.herokuapp.com/api/schema/redoc/#tag/follows/operation/follows_update
https://turnip-oomfie-1.herokuapp.com/api/schema/redoc/#tag/follows/operation/follows_update

omg amazing!! This will help out front end team a lot

To help them out, would you be able to add the user story that goes a long with the endpoint?

I don't know if I covered everything but I've matched the user stories to the methods as best as I could XD
https://turnip-oomfie-1.herokuapp.com/api/schema/redoc/


feat(snapshot/watch): add support for snapshot --watch

Motivation
Closes #911

Solution
and --watch flag for snapshot.
Rn there's no reconfigure, everything is run again, if that should be configurable needs a followup.
CC @transmissions11

woohoo!

Rn there's no reconfigure, everything is run again, if that should be configurable needs a followup.

wdym here?

what I meant was that snapshot --watch will trigger a completely new snapshot run on change. unlike forge test --watch which only executes the tests of the changed file.
But I can also refactor it a bit to make it behave exactly as forge test

ah gotcha yeah no rush from me there


Introduce 3 issue templates and links

Fixes #1096
Intended to streamline the process of opening new kpt issues.
Introduces three issue templates for the kpt repository for:

Feature Requests
Bug Reports
Kpt Questions

Also introduces two links for new issues that link to:

Kpt channel in the kubernetes.slack.com slack server
The Kpt Guides

These links are presented as part of the "New Issue" flow.
Comments on phrasing and styling appreciated.

@runewake2 is this ready for another review?

Yes, my recent changes should address the review comments.

@frankfarzan PTAL


fix(ui): Reverse ToggleIcon

The ToggleIcon works counterintuitive to how you would expect. The chevron direction should indicate what the button SHOULD do, rather that the present state. Currently when the details are hidden, the chevron points up, as if the details view is already seen, and you can hide it, rather than expand it.
The change reverses the chevron direction, so its more intuitive.

To compare, this is the Settings view, which contains sections which can be expanded, with the correct chevron direction:

Meanwhile this is the rotation of the individual alerts when in the expanded detail view:

As you can see the chevron points down, but the details are already shown.


Dumping the AD for import into Bloodhound fails using low priv. accounts in 2.0.4

I can successfully dump my AD for import into Bloodhound using 2.0.1 and a low .priv account.

When I try this in 2.0.4 using the same low priv. account as above and the same AD this partially fails.

When I use the account domainadmin1 (high priv.) dumping works in 2.0.4.

Is all of this intentionally? If not something seems to have broken.

Should be fixed in 2.0.5. Can you please verify?

Great! Assuming the error below is just temporary until the backup feature runs, this works in 2.0.6.

Yes, so the new version tries both methods. The MS-CSRA method is faster when the Remote Registry service isn't running, but apparently that method behaves differently in regards to permissions, probably because of DCOM. So yes, the output is a bit verbose if MS-CSRA fails. Perhaps I could print it only in verbose (-debug) mode :)


📝Install and configure Tailwind CSS

Set up tailwind as suggested in the documentation. Make sure this is running painlessly for dev, it should auto update with the site when developing but remove unused styles when bundling for production.
This should be set up initially with the understanding we will need to make some custom classes and possible using the @apply directive to add them to the DOM.
References #63

https://mxstbr.com/thoughts/tailwind/ This article has some really great advice on getting the most out of tailwind. If used improperly, it can add a lot of unneeded bloat to the project. We will definitely want to have a solid postCSS setup in our build step, but maybe could use some other packages mentioned in this article as well.

Closed by #121


Fix CompletionAfterLoad test

Actually looks like product bug. When adding/removing files, for dependent files we should be going through normal chain via EnqueueItem which does many useful things and not directly calling AnalysisQueue.Enqueue. We does can save on not parsing them, but events should be fired and diagnostics should be updated.

Will look closely on this tomorrow. I remember that code being rather fragile.


[Improvement]: Community Tools panel should scroll verticaly

Affected Version
1.70.12
Bug Behavior
this is not a bug (and yet no form to create an "Improvement")
why dont we split this section into 2 section and scroll them verticaly ?

its not a bug, its fully functional, its just not intuitive from my experience as a user
i know this is not gonna be ended up in your num 1 priority, take your time :)
Expected Behavior

Steps to reproduce

Related Issues
No response
Screenshot(s)
No response
Additional Information
ah yes, please add Improvement issue form for this kind of issue in the future (from me again maybe)

 Vertical Scroll on Community Tools

Hi, sorry for the last response for this. First of all, thank you for expressing your idea for Collapse project!
We have discussed with the core devs for this and we have decided to not implement it as the scrolling works fine now and we don't seem to find it as well translated to the implementation. As we have quite a lot of community tools implemented (maybe more in the future), vertical scrolling Community Tools tab will be quite a scrolling to go through and find the items user wants, so with the scrolling in that tab fixed, we think the current implementation is already quite nice as is.
Though, feel free for anyone to chime in about this in the comments and we'll rethink about it.


dosent save prefrence on new private tab

描述错误 / Describe the bug
not sure if its a bug but to me it is
prefrence of settings not being saved in private tab
重现步骤 / To Reproduce
enable settings in normal tab e.g. ugoira to gif then in private tab its then reset to defaults
浏览器 / Browser
firefox
浏览器日志 / Browser logs
not rly loggable just settings getting restored to default

This is the design of private mode. The localStorage of normal tabs and private tabs are isolated from each other.


Add missing start paragraph tag

Add missing start paragraph tag to the example link in the receive-code view template file so that the resulting HTML is well-structured again

This repository has been closed and moved to laminas-api-tools/api-tools-oauth2; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-oauth2/issues/2.

This repository has been moved to laminas-api-tools/api-tools-oauth2. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone laminas-api-tools/api-tools-oauth2 to another directory.
Copy the files from the second bullet point to the clone of laminas-api-tools/api-tools-oauth2.
In your clone of laminas-api-tools/api-tools-oauth2, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


Fixing an issue when uploading a new map file

Fixing an issue when uploading a new map file as reported in #1250

Coverage remained the same at 35.925% when pulling d46a5cf2d81cc339453bfdce76ac9dd81fcd1ddb on klcodanr:defect/redirect-manager/upload-fail-1250 into da98c8c557fb6e4b718fda2d427b1f30226c3e12 on Adobe-Consulting-Services:master.

Thanks @klcodanr. I'm going to cut a 3.14.8 bug fix release with this in it shortly.


i18n(ko-KR): update preact.mdx

Description (required)

update preact.mdx
#8644

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
guides/integrations-guide/preact.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


A problem during the second phase of training

I have been reading your excellent paper and attempting to replicate your work. However, I encountered a problem during the second phase of training. Is it possible that the second phase is causing an infinite loop? According to the description in your paper, it seems that we only need to compare the results after 200 epochs. Does this mean that the experiment can be paused once 200 epochs have been completed?
I would greatly appreciate your clarification on this matter. Looking forward to your reply.

Thank you for your detailed explanation. I understand your approach and appreciate the information provided.


Support for cameras

I would love for Alarmo to have support for cameras so the push notification can include a snapshot of the room where the alert came from.

I have a setup where Alarmo sends a text message to my monitoring service when triggered. Also, when triggered, a script starts, taking two snapshots with two seconds in between them, and e-mails these to the monitoring service email-alarm receiver. Which allows for photo verification. I have another script starting when an entry delay is started, and when triggered, these pictures are included in the email.

Not ideal but that would work I guess

I use telegram to receive images from the cameras. Just edit the relevant action in YAML and insert the snapshots relating to the trigger.

could include a gif in the notification


Immer patches

Adds functionality to use the immer patches functionality with useMethods.
Fixes #12

Hm, this API feels a bit awkward to me still. What about instead having an overloaded version of useMethods that allows passing an object with methods, patch callbacks, and whatever else in the future?
const [state, callbacks] = useMethods({
  methods,
  patchCallback(patches, inversePatches) {
    // ...
  },
}, initialState);

That makes sense.  The PR was updated to use this API.

Nice work, thanks!


XCODE Swift C++ wrappers

| Camera Model                       | {D415 } |
| Firmware Version                   | (Open RealSense Viewer --> Click info) |
| Operating System & Version |    MacOS  |
| Kernel Version (Linux Only)    |  (e.g. 4.14.13)                                         |
| Platform                                 | MacOs  |
| SDK Version                            |  {  }                          |
| Language                            |  {Swift/C++ }                          |
| Segment			|  {others }                          |
Issue Description
Hi There
I managed to import library into XCODE project and wrap the function for pipeline.start() to use it in swift. here is how I did it:
in a CPP-Wrapper.h
@interface CPP_Wrapper : NSObject
    - (NSObject *)pipeline;
@end

in CPP-Wrapper.mm
@implementation CPP_Wrapper
    - (NSObject*)pipeline {
        rs2::pipeline p;
        p.start();
}
@end

I call this from the AppDelegate:
let p = CPP_Wrapper().pipeline()
And Voila: the camera starts. However, if I add the function :
rs2::frameset frames = p.wait_for_frames();
the timeout error occurs. I think it is not getting any data. If I do the program using CMAKE and only C++ the camera works, so I think there is nothing wrong with the camera, just my code.
Can you please help?

Have you enable the "USB" capability in "App Sandbox" section" in the page"Signing & Capabilities"?
https://developer.apple.com/documentation/xcode/adding_capabilities_to_your_app
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_device_usb

Yes, I think I did. I also checked the boxes for Camera. I still get the same error.

Please double check your code.
I have try call librealsense c API in swift code. it works.
Please find more error detail. for example, you have found the camera before pipeline::start
and please make sure the lifetime of objects in your snippet.

Would you be so kind as to send me an example? It would help a lot.

There is a simple sample code.
https://github.com/mengyui/librealsense/tree/swift/wrappers/swift
It may help you.

@RealSenseCustomerSupport Thanks a lot. That is great. However there are files missing. E.g. Preview Content Assets, and the *.a linker flags are also not available. How Do I create the .a files?
Another thing: Because IU do not have .a files, i embedded a dylib library, that I have been using in my previous project. Its version is 2.32.1. When I run the app with this library I get:

API version mismatch: librealsense.so was compiled with API version 2.32.1 but the application >was compiled with 2.33.1! Make sure correct version of the library is installed (make install)

thanks for the help

If you try to use static library, you can disable BUILD_SHARED_LIBS in cmake phase, when build librealsense2 library.
If you want to use dynamic library, Please try follow this step. I have not test that.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_osx.md#packaging-your-application

@RealSenseCustomerSupport  Thanks a lot. That was really helpful.


test(workflow): preview message

PR was only created to finally test the new preview message behaviour.
Looks like it works 🌟


'WorkbookDocument' object has no attribute 'getData'

'WorkbookDocument' object has no attribute 'getData'

getData is not an attribute, it's a method : getData()


Two multiselect dropdowns not working on IE11.

I have used jquery.multiselect.js and created two multiselect dropdowns one below the other.
One for Career Area and 2nd one for Locations. But, On IE11 2nd dropdown is not working (i.e. It is showing normal multiselect html tag.)
Kindly, reply me if anyone have the solution for this.

This plugin doesn't have support anymore, and its filled with bugs

i want a multi select drop-down which works fine in IE when rendering more than 5 thousand records.
Currently i am using kendo multi-select but on free search it breaks on IE11.
Kindly, reply me if anyone have the solution for this.


Data about Common shelduck are not updated

@EricStienen in https://github.com/inbo/sovon/issues/52#issuecomment-470896617:

I just heard last week that the of Common Shelduck is not up to date at all and that there is more data sitting in a personal database of Nico de Regge. Probably better to not include this species in this session, but add the data in a later stage.

I filter out the data related to EURING code 01730 in a preprocessing step.


The time scrubber missing/not available for certain pods?

I seem to recall the time scrubber being available to use when first using your wonderful service but lately the scrubber has been missing when playing podcasts.  Did something possibly change to break that functionality?

Can you post a link to a Overcast podcast that is having problems. Like https://overcast.fm/itunes617416468/accidental-tech-podcast.


About org files

Hi, there. I noticed the PR in Add org_to_anki GitHub link #8. However, I'm quite misunderstood about this tool, especially what the ".org" file is for. I have a humble suggestion, why not add a little more description in README.md file of your project, so that even new users like me can easily tell what this tool is all about. Thanks!

Hey, that is a very fair point. I had written the readme expecting / project would already know what an org files is. I will add the information to the readme to better explain what it is.
Thanks for the suggestion!

@c-okelly Interesting! I think that's enough. :)


Needs CITATION.cff

Similar to https://github.com/HolyLab/GsvdInitialization.jl/pull/10. @youdongguo, it's worth learning how to do this, so I'm assigning this to you.

have added https://github.com/HolyLab/NMFMerge.jl/pull/19

Tip: you can write "fixes #16" in the commit message and then the issue will be automatically closed.


[BEAM-9296] Clean up and add type-hints to SDF API

R: @chadrik

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

All tests passed. I'm going to merge it. Thanks, Chad!


More prefixes

Redis sink, Hdfs Dataset sink, Trigger source

Can we not call it just a 'redis' sink, this one is a redis-publisher'' sink... We should reserve the word 'redis' for the sink that writes to data structures.

The 'redis' sink does more than PUBLISH. If a key is provided instead of a topic it does write to a data structure. It can also write to a LIST if queue is provided (exactly one is required from topic, queue, or key)

Deja Vu?
https://github.com/spring-cloud/spring-cloud-stream-app-starters/pull/138#discussion_r67230364
Doctor, ( @markpollack ?) I am being ignored. :smile:
Although we should consider to add a Map functionality to that sink as well.

+1 for adding support for writing to HASH data structures as well (either a fixed "field" or an expression for determining the "field" as well as the "value")

It seems less complete the what was in XD no?

XD's redis sink also has topic, queue, or key expressions

Rebased and merged as cf2239b


Fix the dictionary editor

Fix the problem dictionary with int type key can't change key in editor.
Add support to dictionary editor with key type as char, bool, or other number type, and can modify key now.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: D3ZAX:x: liuningliuning seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

It looks like it's this commit https://github.com/stride3d/stride/pull/1108/commits/4aa5c9caee5fb6fdfb79b40fbe546a79fc13670c


remove user automaticaly from active game

Automatic removal of a player from the game after a configured playing time. the interval parameter should be defined in the configuration file.

test cases missing

reviewed with @iav-BjRo


Provide finer control over the "phases" of a bundle deployment

We have just implemented this action and found that while it works fine, for certain environments we would like finer control on the phases of deployment. For example, for production, we would like only to upload the bundle but not deploy it or promote it.
If we could have an action, e.g. arcxp/upload-action that would be ideal.
Another option would be using this same arcxp/deploy-action with an extra parameter, like upload-only: true (which can default to false and behave as it does right now, would work

@luis-ochoa, without disclosing any sensitive internal information, can you help me understand the use case? I want to make sure that I keep your use case in mind as I think through this issue.

Sure.
We want to control how far to go into the deployment process depending on the environment we're deploying to.
For example:

Env
Action(s)
Comment

Development
upload->deploy->promote
Current behavior of arcxp/deploy-action

Sandbox
upload->deploy
No way of doing just this currently

Staging
upload->deploy
No way of doing just this currently

Production
upload
No way of doing just this currently

Then in GHA we could pass a parameter to arcxp-deploy-action (or use a different action altogether) to accomplish the behavior above depending on the environment we're deploying to

This makes a bunch of sense, thanks for the explanation. I'm thinking that now for each of the deploy steps, I can add an input for that step, which defaults to true.
I think that'd look something like:
      - name: Perform the deploy
        if: ${{ success() }}
        uses: arcxp/deploy-action@v1
        with:
          org-id: your-org-here
          api-key: "${{ secrets.YOUR_DEPLOYER_TOKEN_HERE }}"
          api-hostname: api.sandbox.your-org-here.arcpublishing.com
          bundle-prefix: action-demo-1
          deploy: false
          promote: false

This would disable deploy and promote. It'll throw an error if you say deploy:false but promote:true.
Does this sound it would meet your needs?

Absolutely.
That would work.

@luis-ochoa this should be done now. Please note the update to the documentation.
If you notice any issues with this, or it doesn't meet your needs, please open a new issue.
Many thanks!


Only use physical coords internally in bevy_ui

Objective
We switch back and forwards between logical and physical coordinates all over the place. Systems have to query for cameras and the UiScale when they shouldn't need to. It's confusing and fragile and new scale factor bugs get found constantly.
Solution
Use physical coordinates everwhere internally in bevy_ui.
Store physical coords in Node and tear out all the unneeded scale factor calculations and queries.

@atlv24 I ran the UI testbed and a couple more examples. But, now I checked some other random example and there are indeed issues. 😬
So… I've run all the UI examples and this is what I've found:

border width are different (example: borders, ui_texture_atlas)
texture atlas slice border width (example: ui_texture_atlas_slice, ui_texture_slice_flip_and_tile, ui_texture_slice)
border radius are different (example: box_shadow)
text wrapping (examples: grid sidebar text, scroll, text_debug, text_wrap_debug)
wrong text/box (?) alignment, could be because of the wrapping issue (examples: display_and_visibility, text, size_constraints)
overflow clip margin (example: overflow_clip_margin)
a panic! (example: overflow_debug)

I think all of these are fixed now.


Calling an inner function with 'this' in strict mode.

The following code passes jslint but not jshint. Is the use of 'this' realy restricted in the function x()? The besen interpreter runs the code perfectly. and x.call(this) gives the this object to the functions doesn't it?

  /*global console*/

  this.myx = 'mineX';

  (function () {
      "use strict";
      function x() {
          if (this) {
              console.log(this.myx);
          } else {
              console.log(this);
          }
      }

      x();
      x.call(this);
  }.call(this));

great thanks


update msg

What is your Quests version / build number (do not say "latest")?
Quests-5.0.0-rc.4
Describe the problem and how to replicate it.
if i join on my server it tells me with msg to update to Quests-5.0.0-rc.3
install plugin
join server
Any console errors to share?
no

If applicable, can you provide an example quest from quests.yml?
No response

config.yml update-check: false


make some debug assertion failures more informative

In https://github.com/rust-lang/miri/issues/3160, we got a report of a user running into an assertion failure in cargo. Unfortunately the failure message is not very informative. This PR hopefully makes that failure easier to debug.

That CI failure seems unrelated to my PR.

Make sense. Thank you!
@bors r+

:pushpin: Commit 1b3a53ca388569c2f2aad79c24afcdd296a88142 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 1b3a53ca388569c2f2aad79c24afcdd296a88142 with merge fa62a0e5058444ee5fe3d77a4d79408acd0cbbea...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing fa62a0e5058444ee5fe3d77a4d79408acd0cbbea to master...


UI Enhancements

Description

Fix #802

Inferenceservice loading status icon should be spinner rather than an hourglass.
Display a tooltip message when the model fails.
Adding headers to tokens row
In the "Deploy model" modal, change "Configure" button text to "Deploy"
Route itself doen’t refresh with changes automatically
Hide the link from the Model names until metrics are enabled
When inference service is disabled, just change the text to "Internal Service" rather than displaying a route.

How Has This Been Tested?

Merge criteria:

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work

/unhold

I'm approving this. None of my comments are going to really change anything. I'll talk to you tomorrow about the details if you want.
Nice, thanks for the feedback, opening a follow up


Implement the block with mappings + “Map to selection” button

Blocked by #22, implementation is to start when we complete the redesign of this section.

Just to clarify the scope of this issue, according to the mockup, since the 'Terms awaiting creation' table relies on the 'Map to new term' action being implemented, I think this issue include the 'Suggested Terms' table along with the mapping functionality, and issue #27 should include the table holding the newly created terms

Yes, exactly—

This issue: "Suggested terms" table + "Map to selection" button
#27: "Terms awaiting creation" table + "Create and map to new term" button


(Throttled) Too many operations are requested

We are building a very large zone, and we semi-consistently get throttled.
I believe the provider should be handling this specific case?
  Traceback (most recent call last):
    File "/usr/local/bin/octodns-sync", line 8, in <module>
      sys.exit(main())
               ^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/octodns/cmds/sync.py", line 62, in main
      manager.sync(
    File "/usr/local/lib/python3.11/dist-packages/octodns/manager.py", line 769, in sync
      ps, d = future.result()
              ^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/concurrent/futures/_base.py", line 456, in result
      return self.__get_result()
             ^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result
      raise self._exception
    File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
      result = self.fn(*self.args, **self.kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/octodns/manager.py", line 527, in _populate_and_plan
      plan = target.plan(zone, processors=processors)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/octodns/provider/base.py", line 226, in plan
      exists = self.populate(existing, target=True, lenient=True)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/octodns_azure/__init__.py", line 742, in populate
      for azrecord in self._zone_records(rg, zone_name, top):
    File "/usr/local/lib/python3.11/dist-packages/azure/core/paging.py", line 123, in __next__
      return next(self._page_iterator)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/azure/core/paging.py", line 75, in __next__
      self._response = self._get_next(self.continuation_token)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/local/lib/python3.11/dist-packages/azure/mgmt/dns/v2018_05_01/operations/_record_sets_operations.py", line 1106, in get_next
      raise HttpResponseError(response=response, error_format=ARMErrorFormat)
  azure.core.exceptions.HttpResponseError: (Throttled) Too many operations are requested. Current operation is throttled.
  Code: Throttled
  Message: Too many operations are requested. Current operation is throttled.

Without more/better information from Azure I'm not sure how the client could do anything useful automatically. If it told it how long to wait or the rate limit that was violated it could potentially try and work with that, but with it just saying things have been throttled that doesn't really provide enough info.
I found https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/request-limits-and-throttling. It looks like something that spans all Azure services and isn't specific to DNS. Based on that it seems like the Azure client libraries would be the right place to implement handling for being throttled and not something specific done in octodns-azure.
Given that it's per region and not per service I don't know how any one client could really implement anything smarter than a wait and retry since other clients could be competing for the same refilled tokens.

Yeah, from what I could see the SDK should handle this case based on a Retry-After header. I haven't had much luck debugging it as it's hard to make it happen in my test environment because reasons.
I guess the solution I'm looking for from the perspective of this provider is to expose more of Retry configuration in the hopes we can make it work. It looks like currently the retries are very short and just meant to handle transient network issues.
https://github.com/octodns/octodns-azure/blob/14af9bf40b8b23321c6946c8996b8c98e136333a/octodns_azure/__init__.py#L643-L646
Do you think we could expose the rest of the parameters?

There's quite a few options, only reasonable way i could see to do it would be to have a retry_policy dict param that gets passed into the object as **retry_policy so that all of the options would be available w/o having to duplicate everything.

Wow, so apparently RetryPolicy doesn't accept most of it's config options as kwargs, they have to be set as properties after creating the object as is demonstraited in the examples section https://learn.microsoft.com/en-us/python/api/azure-core/azure.core.pipeline.policies.retrypolicy?view=azure-python#examples.
That means the configuration options currently available aren't actually taking effect.

Oh wow, great find - thank you very much!
What an "interesting" API...


Several fixes and cleanups

Restructure towards 64-bit as a first choice.
DVI/MDVI control algorithms updated to divide alpha and beta by num_states
side by side implementations of sync updates in MDVI to ensure vectorized code is right
fixed greedy_policy calculation in MDVI.

I'm going to commit this and the following PR and then continue working.


Testing skeleton. Added scripts to run java and go unit tests in dock…

…er containers.

See also: https://github.com/weaveworks/microservices-demo/issues/171


[tests-only] Bump core commit id for API tests

This will include core PR https://github.com/owncloud/core/pull/38262 "[Tests-only] Adds api tests for renaming received shares" into the test scenarios.
Similar to https://github.com/owncloud/ocis/pull/1189

Note: if you are abut to merge #1368 then please do that first. Then I will rebase here and get fresh CI to check the expected-failures after all those changes.

Note: if you are abut to merge #1368 then please do that first. Then I will rebase here and get fresh CI to check the expected-failures after all those changes.

Rebased - @labkode @ishank011 ready for review.

Rebased - @labkode @ishank011 ready for review.


WIP - Additional alert features

This PR adds the structure needed for us to add features to the alert. Not used for ML (at least not for now), but useful for filtering or annotating.
In this PR, we implement the color evolution calculation, which condition to be calculated and added to the alert is: at least one detection in r-band and one in g-band within N hours. We calculate r-g and g-r.
This N hour threshold can be changed in the configuration.

A few suggestions.

Took care of all of them. I'd suggest taking another quick look to confirm.

Closing, as a similar PR has been merged already