PhantomJS fails to redirect when redirect URL has special character

I am using phantomJS 2.0 on windows together with PHP.
When I try page.open with this url:
"http://www.webhallen.com/se-sv/film/dvd/148610-galpagos?atcl=start:viewed"
The server responds with a redirect to:
http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
(In firefox the HTTP header location says: "/se-sv/film/dvd/148610-galápagos")
However, phantomJS is messing upp the special character "á" and the redirect URL becomes:
"http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos"
When phantomJS tries to load this URL the server will respond with the same redirect URL again (The server is setup to respond with a redirect to "http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos" for all URLs that starts with "http://www.webhallen.com/se-sv/film/dvd/148610").
The scripts is now stuck in an infinite redirect loop.

var args = require('system').args;

var res = new Object();
res.content = "";
res.error = "";

var page = require('webpage').create();

/* timeout to exit script after 10 seconds */
window.setTimeout(function() { res.error = res.error + "TIME TO STOP! "; console.log(JSON.stringify(res)); phantom.exit();  } , 10000);

page.onResourceRequested = function(requestData, request) {
    res.error = res.error + "REQUEST: " + requestData.url + "\r\n";
};

page.onResourceReceived = function(response) {
    res.error = res.error + "RESPONSE: " + response.url + "\r\n";
};

page.open(args[1], {  encoding: "utf8" }, function(status) {
    if (status !== 'success') {
        res.error = res.error + 'No success...' + status;
    } else {
        res.error = res.error + 'SUCCESS!';

        res.content = page.content;
        console.log(JSON.stringify(res));
        phantom.exit();

    }
});

Output from script:
REQUEST: http://www.webhallen.com/se-sv/film/dvd/148610-galpagos?atcl=start:viewed
RESPONSE: http://www.webhallen.com/se-sv/film/dvd/148610-galpagos?atcl=start:viewed
REQUEST: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
RESPONSE: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
REQUEST: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
RESPONSE: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
REQUEST: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos
RESPONSE: http://www.webhallen.com/se-sv/film/dvd/148610-gal�pagos

I believe this is another manifestation of bug #12216.  If so, that is fixed by pull request #12233, which will be included in the upcoming 2.0.1 release.  If you are able to build and test the development sources and confirm whether your problem is solved, that would be helpful.  I am going to close this bug report now, but if your problem is not solved, feel free to reopen it.

@zackw i dunno if im doing it wrong but im getting this old error by doing this:
var system = require('system');
var page = require('webpage').create();
var args = system.args;

page.onResourceRequested = function(requestData, request) {
    console.log("requestData.url: ", requestData.url);
};

page.onResourceReceived = function(response) {
    //console.log("response.url: ", response.url);
};

if (args.length === 1) {
	console.log('Try to pass some arguments when invoking this script!');
	phantom.exit(1);
} else {
	var url = args[1];

	console.log("url: ", url);

	page.open(url, {
		encoding: 'utf8'
	}, function(status) {
		// Check for page load success
		if (status !== "success") {
			console.log("Unable to access network");
			phantom.exit(1);
		} else {

			console.log("url: ", url);
			//phantom.exit(0);
		}
	});
}

The url i put in is:
https://bolighed.dk/håndværker
The url i get out is:
requestData.url:  https://bolighed.dk/h%EF%BF%BDndv%EF%BF%BDrker
It seems like its bugging with Æ, Ø or Å


There does not seem to be support for multi-way connection structures

Prerequisites
Please make sure to check off these prerequisites before submitting a bug report.

[√] Test that the bug appears on the current version of the dev-branch. Make sure to include the commit hash of the commit you checked out.
[√] Check that the issue hasn't already been reported, by checking the currently open issues.
[√] If there are steps to reproduce the problem, make sure to write them down below.
[√] If relevant, please include the ONNX files, which were created directly before and/or after the bug.

Quick summary
I had an error trying to do a multi-branch convolution.
Details
In my network, after the main branch is convolved, I need to convolve multiple branches separately, and then merge the results of the convolution using the concat operation (this step is not necessary).
Everything from generating the onnx file to converting it to the hls node worked fine, but an error of "cycle-free graph violated: partition depends on itself " was reported when model.transform(CreateDataflowPartition()) was executed.
I did some qualitative tests to find out what caused my problem.
I have tried the hls node processing flow of Resnet-50 and conducted various tests, please refer to https://github.com/Xilinx/finn/issues/863#issue-1822075914 and https://github.com/Xilinx/finn/issues/860#issuecomment-1649853296 for details.
And I did a simple two-way connection test, but it still reported the same error, the onnx file is as follows:

Previously, the "add" node could be converted to "streamadd" normally, but it still reported an error.
I tried to modify the convolutional flow in the branch to keep only the convolution at the end of both branches (with bn and relu operations removed), but it still reported an error and even kept the "add" node.
Below is the onnx file for a test I did.
I tried to use the QuantIdentity() function to replicate the results of the upper convolutions for a multi-branch effect, and the add operation for the merge operation

I went on to try to use QuantIdentity() to replicate the results of the upper convolutional layer to achieve a multi-branch effect, using a convolutional path to process each branch, and using concat to merge the branches.

Unfortunately, the multiple approaches I tried stuck with model.transform(CreateDataflowPartition()), and they all gave the same error.
Therefore, I am here to ask if there is any reasonable way to achieve the operation of multiple branches.
Thanks again
Best wishes to you.

Hi, I also have the same problem. I have tried the hls node processing flow of Resnet-50, but it doesn't work. How did you solve the multi-branch problem in the end?

Hi, I also have the same problem. I have tried the hls node processing flow of Resnet-50, but it doesn't work. How did you solve the multi-branch problem in the end?

I am sorry to tell you that I did not solve the multi-branch problem, I chose to adjust the network to avoid this phenomenon.
But my problem is multi-branch and double-chain branches, which should work fine for the normal resnet structure, you can refer to the processing steps in finn for details.


Security Issue: Requires Root Privs

Operating system
Parabola GNU/Linux-libre
Description
I have my user added to the kvm group, and also rootless podman is setup, it should work without root privs.

Screenshots (optional)
No response

I was able to get this image working on rootless docker by editing /etc/subgid. On my system, my username is nate, and the kvm user has gid 104, so I added this line.
nate:104:1

I wrote a very short script to do this process automatically (requires root privileges).
#!/bin/bash

read -p "Enter your username: " DOCKER_USER

KVM_GROUP="$(cat /etc/group | grep ^kvm | awk -F: '{print $3;}')"
printf "%s:%s:1\n" "$DOCKER_USER" "$KVM_GROUP" >> /etc/subgid

If this doesn't work, you may need to add the kvm group to your container. First, find the group that the host kvm group maps to.
#!/bin/bash

read -p "Enter your username: " DOCKER_USER

KVM_GROUP="$(cat /etc/group | grep ^kvm | awk -F: '{print $3;}')"
KVM_MAPPED_GROUP=1
while read MAPPING ; do
	if [ "$(printf "%s\n" "$MAPPING" | awk -F: '{print $2;}')" -eq "$KVM_GROUP" ] ; then
		break
	fi
	MAP_SIZE="$(printf "%s\n" "$MAPPING" | awk -F: '{print $3;}')"
	KVM_MAPPED_GROUP="$(expr "$KVM_MAPPED_GROUP" + "$MAP_SIZE")"
done < <(grep "^$DOCKER_USER" /etc/subgid)

echo "KVM group: $KVM_MAPPED_GROUP"

Then, in your docker-compose.yml file, add the following lines:
services:
  qemu:
    # ...
    group_add:
      - [the group number from the previous step]


graph api and file structure change

Description
Please include a summary of the change. For large or complex changes please include enough information to introduce your change and explain motivation for it.
Changes proposed in this pull request:

/intelci: run


Adding CurrencyPairBaseQuote USDTUSD

Description
This PR adds a USDTUSD as a new CurrencyPairBaseQuote
Related issues
Currency base quote is required to enable the following PR:
https://github.com/celo-org/celo-monorepo/pull/9939

LGTM would like to get this in asap, thanks

This was merged on https://github.com/celo-org/celo-oracle/pull/133, closing this


Dictionary and Code Refactoring

See commit descriptions for overview of what I did.

Could you:

Rename the subpanel folder to components or subcomponents
Rename the .tsx file names to be PascalCase + export the same name e.g. Dictionary.tsx should have export default Dictionary;
Decide whether to go with -btn or -button for all class/id names
Make the headword for dictionary a bit smaller
See: https://github.com/airbnb/javascript/tree/master/react#naming


dotnet README incorrect

The dotnet README.md refers to a dotnet_release target in the make file. This target does not exist.

hi,
Which file are talking about ? in the repository or file shipped in an archive ?


WindowBase|WindowSDL: Add drop position for all on_drop_xxx events

Adds dispatching of the drop position (in coords relative to the window left/top) with all on_drop_xxx events. Documentation about the events is updated. This is a follow-up on https://github.com/kivy/kivy/pull/7786.

Maintainer merge checklist:

[x] Title is descriptive/clear for inclusion in release notes.
[x] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[ ] Applied the release-highlight label to be highlighted in release notes.
[x] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[x] Properly documented, including versionadded, versionchanged as needed.

Maybe we need more in the doc for case when/if the drop is not coming from the mouse.

Maybe we need more in the doc for case when/if the drop is not coming from the mouse?

Possibly. But we can always update it later if we figure out it's possible to get a drop without the mouse!? It's up to you.

looks good,  LGTM!

@akshayaurora please make sure to squash before merging, especially if there are multiple commits that are not separate features.
@pythonic64 it may be a good idea to mark PRs as WIP until you feel it's ready to merge so we don't merge before you're ready if you're still considering changes. We can still review it before that though. There's a button that makes it a draft to block merging until you're ready!

@matham At the time of the creation the request looked ready to me, but now I think we should have added *args to those events, just in case that SDL might pass a drop origin.


⚠ Bofrost.at has degraded performance

In 4f5561a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2654 ms

Resolved: Bofrost.at performance has improved in 5deba41.


Inform the version of the documentation in the url.

The Vue.js documentation is excellent, we use it daily to help answer questions and articles.
But the url documentation always points to the latest version, this way over time all references documentation will refer to the wrong destination.
I propose that the url /guide and /api start to have a prefix, so no link will break over time.
/v2/guide and /v2/api
or
/guide/v2 and /api/v2

I can see the reasoning behind this, but it would be a difficult transition to make. In the immediate future, every link would break. 😕

I suppose so, anyway is a suggestion

Quick update: I've been thinking more about this and believe I have a transition plan that will work out, so it will probably be happening.

It is very good to hear @chrisvfritz! tk

@chrisvfritz If you need some help in the process, I am available

Thanks! And just a heads up: it might be a few weeks until this is live, as there's some coordination I'll need to do with Evan, which will be easier once he's back in the USA (and on faster Internet 🙂 ).


CHEBI:34967 please define

Could CHEBI:34967 - SR141716 please be curated and defined.

Now curated. Thanks

Now curated. Thanks


[Bug] SelectedUnstaged won't be clear after discard

[Bug] SelectedUnstaged won't be clear after discard
similar to https://github.com/sourcegit-scm/sourcegit/pull/325

You can test if these two commits solved your problem

LGTM


Unable to start grafana deployment if namespace has a ResourceQuota. (Init containers not defining resources.limits)

When testing out this operator we ran into a problem where the init containers are created without resources.limits/requests. As such when a ResourceQuota is defined on the namespace it is unable to start.
To reproduce apply the following resource quota to a namespace and attempt to deploy the grafana operator. (you will need to apply limits to the operator deployment.)
---
apiVersion: v1
kind: ResourceQuota
metadata:
  name: resourcequota-cool-namespace
  namespace:  a-cool-namespace
  annotations:
    sendgrid.com/generated-by: k8s-access-control
spec:
  hard:
    limits.cpu: "20000m"
    limits.memory: "20000Mi"

> kubectl describe rs grafana-deployment-55965d754d

Name:           grafana-deployment-55965d754d
Namespace:      a-cool-namespace
Selector:       app=grafana,pod-template-hash=55965d754d

<snipped for brevity>

Pod Template:
  Labels:           app=grafana
                    pod-template-hash=55965d754d
  Annotations:      prometheus.io/port: 3000
                    prometheus.io/scrape: true
  Service Account:  grafana-serviceaccount
  Init Containers:
   grafana-plugins-init:
    Image:      quay.io/integreatly/grafana_plugins_init:0.0.2
    Port:       <none>
    Host Port:  <none>
    Environment:
      GRAFANA_PLUGINS:
    Mounts:
      /opt/plugins from grafana-plugins (rw)
  Containers:
   grafana:
    Image:      grafana/grafana:6.5.1
    Port:       3000/TCP
    Host Port:  0/TCP
    Args:
      -config=/etc/grafana/grafana.ini
    Limits:
      cpu:     500m
      memory:  1Gi
    Requests:
      cpu:      100m
      memory:   256Mi

<snipped for brevity>

Conditions:
  Type             Status  Reason
  ----             ------  ------
  ReplicaFailure   True    FailedCreate
Events:
  Type     Reason        Age                From                   Message
  ----     ------        ----               ----                   -------
  Warning  FailedCreate  42m                replicaset-controller  Error creating: pods "grafana-deployment-55965d754d-nfq9j" is forbidden: failed quota: resourcequota-cool-namespace: must specify limits.cpu,limits.memory
  Warning  FailedCreate  42m                replicaset-controller  Error creating: pods "grafana-deployment-55965d754d-klxh5" is forbidden: failed quota: resourcequota-cool-namespace: must specify limits.cpu,limits.memory
  Warning  FailedCreate  42m                replicaset-controller  Error creating: pods "grafana-deployment-55965d754d-sprc6" is forbidden: failed quota: resourcequota-cool-namespace: must specify limits.cpu,limits.memory
  Warning  FailedCreate  42m                replicaset-controller  Error creating: pods "grafana-deployment-55965d754d-r48fz" is forbidden: failed quota: resourcequota-cool-namespace: must specify limits.cpu,limits.memory
< and so on>

As a work around you can apply a LimitRange to add default limits to all containers in the namespace, but this is a namespace global policy and it wont work for everyone.
---
apiVersion: v1
kind: LimitRange
metadata:
  name: a-pretty-rad-workaround
spec:
  limits:
  - default:
      memory: 8000Mi
      cpu: 2000m
    defaultRequest:
      memory: 256Mi
      cpu: 100m
    type: Container

I've opened PR #209 as one potential fix that provide the least amount of "friction" in terms of the Grafana CRD spec.
I've also prepared another commit that is slightly more flexible in that you can specify limits for initContainers vs containers but this commit slightly changes the CRD spec so you'd just need to mention this in the next release changelog for users.

Thank you very much @stgarf , the PR looks reasonable. I wonder if it's usually ok to apply the same requests and limits to the init container? Might look into how other operators handle that. Regarding your other PR, as long as we only add optional fields to the CRD there should be no upgrade conflicts.

I wonder if it's usually ok to apply the same requests and limits to the init container? Might look into how other operators handle that. Regarding your other PR, as long as we only add optional fields to the CRD there should be no upgrade conflicts.

@pb82 Having the same requests limits is probably okay but I’d say in the majority of cases its probably a naive way of solving the problem because initContainers typically are short lived and don’t need many initial resources for their tasks.

@pb82 👋, I've pushed a commit to add an optional initResources field to the spec which I think this is the cleanest way forward.


Getting None.get when providing an invalid host or port

I tried creating a function to create URIs looking like this:
    private def getUri(path: String*): F[Uri] =
      UriTemplate(
        scheme = Uri.Scheme.https.some,
        authority = Uri.Authority(host = Uri.RegName(ctx.provider)).some,
        path = path.toList.map(PathElm.apply)
      ).toUriIfPossible.liftTo[F].adaptErr(_ => InvalidUri)

When executing my code I end up with following stacktrace:
java.util.NoSuchElementException: None.get
      at scala.None$.get(Option.scala:627)
      at scala.None$.get(Option.scala:626)
      at org.http4s.ember.client.internal.ClientHelpers$.getAddress$$anonfun$1(ClientHelpers.scala:220)
      at delay @ org.http4s.ember.client.internal.ClientHelpers$.getAddress(ClientHelpers.scala:220)
      at map @ org.http4s.ember.client.EmberConnection$.apply$$anonfun$1(EmberConnection.scala:46)
      at of$extension @ org.typelevel.keypool.KeyPool$Builder.build(KeyPool.scala:373)
      at flatMap @ org.http4s.ember.client.EmberConnection$.apply(EmberConnection.scala:46)
      at <* @ org.http4s.ember.client.EmberClientBuilder.$anonfun$1(EmberClientBuilder.scala:246)

as I'm not failing at the URI creation (I'm getting a Success), but later on in the process.
I'm using http4s version 1.0.0-M39 but the issue seems to be on 0.23 as well: https://github.com/http4s/http4s/blob/series/0.23/ember-client/shared/src/main/scala/org/http4s/ember/client/internal/ClientHelpers.scala#L246

Did you want a more specific error? The host type of ip4s does recognize the host which is how we reference who we call.
Or is Uri too permissive and we need a secondary layer of validation to confirm it's a valid Uri for a backend.

To give you some more context on that issue I initially had misconfigured the value for ctx.provider to https://someapi.com/oauth/token instead of just someapi.com in the first code snippet, resulting in an uri being https://https://someapi.com/oauth/token/oauth/token.
With that, .toUriIfPossible.liftTo[F].adaptErr(_ => InvalidUri) wouldn't fail, and I would instead get the None.get error later on shown above, which I found somewhat misleading.
I don't really have a strong opinion on whether the change should be more towards the uri validation or raising a custom error instead of performing None.get, or both.


fix_convert

The method signature is in accordance with the interface.

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
no

Fixed issues
no

Merged. Thanks!


Can i create an invoice using this package?

Hello, I was wondering if this package supports invoice creation because
I am trying to create an invoice using the YouCan Pay API, but I need an Authorization Bearer TOKEN to do so. To obtain this token, I need to call the following API route: https://api.youcanpay.com/oauth/token.
This API call requires the following parameters:

client_id
client_secret
grant_type
code

I have been unable to locate the values for these parameters in the YouCan Pay dashboard. Could you please guide me on where to find this information or how to obtain these credentials?
docs: https://youcanpay.com/docs/api#create_an_invoice

Hello,
I think that API is used by the Youcan team, this is just an assumption.
Try contacting their support

@mehdibo thank you for the reply,
their support is almost non-existent  😅


Fix errors being thrown as strings within NextJs server actions

PR: https://github.com/gptscript-ai/desktop/pull/394

The easiest way to test this is from the Chat view.
Add a tool from a URL. In the text box, enter something that is not a URL, like hello. If you see a red error appear on the page, then this is working. If no error appears, then it is broken.

Tested with electron build - 54ecc2c334
Following error is presented to the user when bad url is used when adding tools using `Add Tool from URL" option.


Write up a better README

Includes more information about the library, how to quickly add it to your project, and a detailed usage example for both the library and the binary.

Coverage remained the same at 77.978% when pulling 5ccd7ef9ac7c9f007009235919d1153b6f91bfd8 on jonhoo:better-readme into 3f4696108ebf597a92d482ec453f6bcffe7d71b7 on gimli-rs:master.

Note that this probably shouldn't be merged until #7 has also been merged, as the README example discusses functions and relies on a three-tuple being returned from Mapping::locate.

Coverage remained the same at 77.978% when pulling 5ccd7ef9ac7c9f007009235919d1153b6f91bfd8 on jonhoo:better-readme into 3f4696108ebf597a92d482ec453f6bcffe7d71b7 on gimli-rs:master.


Moves the open web browser to the client

This PR moves function for opening the web browser to the client because opening HTML will be used for future command arf-to-report.

LGTM, works, merging!


[ios] fix incorrect initial text inset of textarea

Fix http://dotwe.org/vue/d4a31131178b9ab11f6dd05e5792a171

Brief Description of the PR
<textarea>component has incorrect text insets upon initialization, and it doesn't become correct until the border/padding changes which will trigger an update of insets.
Checklist

Demo:
http://dotwe.org/vue/d4a31131178b9ab11f6dd05e5792a171
Documentation:

LGTM

LGTM


Support for the deployed bytecode (.bin-runtime)

Description
This pull request adds an option to export the deployedBytecode artifact (.bin-runtime).
An includeDeployed option is added, which spawns a deployed/ folder inside the output directory.
Type of change

[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] I have tested my code in a separate Hardhat environment
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have commented my code, particularly in hard-to-understand areas

If we're going to support both initcode and runtime code, I think we should treat them as separate outputs of equal significance.  That is, we should not nest the runtime code folder inside of the existing output folder.
Two ways to do this:

output to separate folders (./init_bytecode/ and ./deployed_bytecode/)
output to the same folder, and add a suffix to each file (./bytecode/Contract__init.bin and ./bytecode/Contract__deployed.bin)

The first option would require duplicating the path option.
Then, I'd like to replace the includeDeployed option with its inverse, for each output type: skipInitBytecode and skipDeployedBytecode.  These would default to false.
We could go further, and duplicate most of the existing configuration options so that they can be set separately for each output type, but I think that might be excessive.
What do you think?


New windows inherit/merge environment from existing windows

Issue Type: Bug

Open two tabs in a terminal emulator
In tab 1: export TEST_VAR=1
In tab 2: export TEST_VAR=2
In tab 1: code --new-window .
In tab 2: code --new-window .
In Code window 2 terminal: echo $TEST_VAR
TEST_VAR has the value 1, not 2. This is wrong.
Using --sync off helps some, as tab 2 will get its own value for TEST_VAR, but it will still inherit any values in tab 1's environment that are not overwritten.
This is a disaster for my workflow, as I have different tabs with different environments set up to work on different programs.
Please tell me there is a way to turn this off completely.

VS Code version: Code 1.49.2 (e5e9e69aed6e1984f7499b7af85b3d05f9a6883a, 2020-09-24T16:26:09.944Z)
OS version: Linux x64 3.10.0-1062.4.1.el7.x86_64

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

Fixed as outlined in https://github.com/microsoft/vscode/issues/108804#issuecomment-731230574 for November.

\closedWith 6f3fcd2ce0002ffd876b7b43bff42a912edddaae


feat: Using lifecycle nodes to their full potential

Similar to this PR, pressing and releasing the estop on our robot causes communication with the hardware interface to be cut off.
Based on my understanding of the lifecycle nodes concept, deactivating and reactivating the hardware should restore communication.
Implementing this functionality would align the hardware interface more closely with the intended behavior of lifecycle nodes.

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

Thank you for the detailed review, @samuelsadok!
When cycling the active state of the hardware interface, the behavior aligns with what you described in Variant 3.
For more context, perform_command_mode_switch() is invoked only during the initialization of the hardware controller when it specifies the control modes of the hardware interfaces (e.g., during launch) or when a mode change is explicitly requested—via terminal or another node. In scenarios where the control mode remains constant, such as when only velocity control is required, perform_command_mode_switch() is typically called just once.
There are some screenshots below of our terminal to demonstrate this behavior on our robot.
I forgot to add some context, the interfaces and controllers are indeed managed nodes. This source code confirms that SystemInterface (the parent class of ODriveHardwareInterface) inherits from LifecycleNodeInterface.
For your high-level comments: you’re absolutely correct. I’ll revise the PR description to clarify the focus on restoring the CLOSED_LOOP_CONTROL state rather than "restoring communication." I’ll also clean up the git history.
Thanks again for your feedback!
Initialization of the interfaces and the controller (showing when perform_command_switch() and on_activate is called with the proposed code)

On cycling the active state of the ODrives

For more clarity, here is another screenshot where I added a print for when the code is in on_activate() or in perform_command_mode_switch() and used grep to only see the parts of interest.

I see, that clears things up, thanks for the elaboration. So it seems that the active/inactive state is mostly independent from the "command mode". Extrapolating from this, I would assume that perform_command_mode_switch() could even be called while the hardware interface is inactive.
In that case I suggest the following change:

Add a new state variable bool active_
on_activate() and on_deactivate() set this to true/false
set_axis_command_mode() takes into account active_, and if it's false, treats it as an IDLE request. The function also takes care of sending all messages related to a state change (set control mode, clear errors, request state).
set_axis_command_mode() called from on_activate(), on_deactivate() and perform_command_mode_switch().

This way, on the first call to on_activate() the CLOSED_LOOP_CONTROL request is deferred to perform_command_mode_switch(), but on a subsequent on_deactivate()/on_activate() cycle, CLOSED_LOOP_CONTROL is requested immediately. At each point we send a consistent set of messages and it also works if perform_command_mode_switch() is called while inactive.


Redirect to error page on visiting a forbidden link

As the title states. Needs work both on the client and the backend side.

Abhi ke liye I'm closing this. Ugh.


Add simplified collision boxes

This PR adds simplified collision boxes for the robot model. This was achieved using the tool provided by bitbots https://github.com/bit-bots/simplify_urdf_collision.
Optimal bounding boxes generated:

Needs to be tested (Perhaps use of simple controller). I might also add more comments where necessary then good to go!


Undefined va_list usage in syslog_android.cc

Hi all,
I was testing some code on Android using Dart 2.13.0 and involving the Syslog::VPrint and Syslog::VPrintErr functions and realised the code was crashing with a SIGSEGV inside the call to __android_log_vprint, specifically while dereferencing a pointer retrieved as first argument from the va_list.
The issue is related with the fact that the same va_list is being used first by vprintf, effectively consuming all the arguments and leaving the va_list in a modified state and then by __android_log_vprint which will start the parsing of the arguments where vprintf left, therefore accessing "undefined" values that will be subsequently used as pointers (in my case).
If I'm not mistaken about the described behaviour, the issue seems to be affecting multiple Dart VM versions.

Good catch! We shouldn't be reusing the same va_list between the two prints.


Fix UV circuits not being recognized by compAL recipe generator

Superseded by https://github.com/GTNewHorizons/GoodGenerator/pull/119


DOC: Output Parsing for human readable text.

Issue with current documentation:
Hello,
i have implemented langgraph using supervisor but i did not see any way to output parse the data.
my output looks like this:

{'supervisor': {'next': 'text_to_sql'}}
----
{'text_to_sql': {'messages': [HumanMessage(content='SELECT tld, COUNT(tld) AS tld_count FROM premium_db.premium_inventory GROUP BY tld;', name='text_to_sql')]}}
----
Python REPL can execute arbitrary code. Use with caution.
{'supervisor': {'next': 'text_to_sql'}, 'sql_to_python': {'messages': [HumanMessage(content='FINISH: The data has been visualized using different colors for each TLD. The chart should now be displayed on your screen.', name='sql_to_python')]}}
----
{'supervisor': {'next': 'FINISH'}, 'text_to_sql': {'messages': [HumanMessage(content='Your only task is to create sql query and do not worry of visualisation of the data.', name='text_to_sql')]}}
----

How would i make this end user readable?
Idea or request for content:
No response

You'd pick a UI element for deach event, so for instance:
          print(f'Next step: {event["supervisor"]["next"]}')
...

Hi there! this issue has been stale for a few months so I'm going to close it. Feel free to re-open if you still have any issues


Remove next-session

Remove vestigial next-session code from the application

All traces of next-session have been removed from the code base. - CLOSED


Question: shops and stores

There are 89 "store" and 50 "shop" presets - is there any rule why some of them are shops and some stores?

@maro-21 These words are generally synonyms, but culturally one may be preferred over the other for a given type of businesses. In the US "store" is more common, while I think "shop" is more common in the UK. To my American ears, "Department Shop" or "Shoe Shop" just sound off.
Since iD's default language is American English, we try to use terms that make the most sense here.

So shouldn't shops be renamed to stores?

@maro-21 I wasn't clear, but I mean some places are still often called shops even if "store" is more common, and often it doesn't matter which.


Secrets Injector failing to create with error 'serviceaccount "secrets-injector" not found'

Your environment

Chart Version:  1.0.1

Helm Version: v3.13.1

Kubernetes Version: 1.28
What happened?

What did you expect to happen?
Secrets-injector is failing to deploy with the error
 pods "secrets-injector-59b74b5b5-" is forbidden: error looking up service account onepassword/secrets-injector: serviceaccount "secrets-injector" not found

Deployment is being created first before the serviceaccount.
deployment.yaml is annotated with pre-install while the permissions.yaml is not.
  annotations:
    helm.sh/hook: pre-install
    helm.sh/hook-weight: "1"

Steps to reproduce

helm install --set injector.applicationName=injector injector 1password/secrets-injector

Notes & Logs

And if you have auto sync enable in argocd for example this leads to eternal loops - I can't believe how bad this chart is, I even raised it with 1password and hear nothing.

Btw. this remains a problem - I suppose it's unlikely to be fixed so if you're using kustomize to deploy this helm chart, the below patch will make it work. There are surely other ways as well, but this was a quick fix.
`patches:

patch: |-

op: remove
path: /metadata/annotations/helm.sh~1hook
op: remove
path: /metadata/annotations/helm.sh~1hook-weight
target:
kind: Deployment
name: secrets-injector`


data URIs don't trigger onEnd

Hmm, what's your use-cases for using data URIs with h-include?

I don't think there is a strong use-case. I'm using them when I want to grab different parts of the same included file to update different parts of the DOM. Something like:
<h-include id="breadcrumbs"></h-include>

other stuff

<h-include id="content"></h-include>

```

There's other ways to satisfy this use-case and hinclude would be simpler if it just didn't support data-URIs. But if the support stays in then it should call `onEnd()`. And `extractFragment`, etc - definitely simpler to remove them as a supported scheme.

Right now, I think we should do a check for data: and throw a 'not supported' exception.

Closing this in favour of https://github.com/gustafnk/h-include/issues/31


Extract shopping logic to utils

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[x] Refactoring

What's new?

[x] PR closes #1841
[ ] <brief_description_of_what_I've_added>

[x] Refactor hardcoded actions into Interaction (from minimark)
[x] Refactor create remark to createInteraction (guess them import ;D)
[x] Refactor that mess in submit with MetaTransactionMixin (check other component how to use it)
[x] Use 🧹 and if you see some functions which are defined on the bad place, please put them in the correct file
[ ] Write unit tests for the functions and the AvailableAction.vue (file)

I could not complete the unit test for AvailableAction.vue because I'm having some weird issues with testing vue components : )
It would be great if someone could continue to write the unit test.
Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[x] I've tested PR on mobile and everything seems works
[x] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

we have another AvailableActions in /components/unique/Gallery/item/, wouldn't it be a good idea to change it too

I don't know why there are two almost the same components named 'AvailableActions'.

I think one is used for Rmrk and the other one for Statemine, Westmint, Bsx. it would be good to unify all this
For changes concerning vitest, I wouldn't do it in this pull request, feel free to open an issue with your problem

I think one is used for Rmrk and the other one for Statemine, Westmint, Bsx. it would be good to unify all this

Could we open another issue to handle this unification of these two components?
I think it's not in the description of the original issue and maybe will cost much more time : )

Could we open another issue to handle this unification of these two components?

@Jarsen136 resolve conflicts?

@Jarsen136 resolve conflicts?

Done. I have just solved the conflicts.

pay 200 usd

😍 Perfect, I’ve sent the payout
💵 $200 @ 72.89 USD/KSM ~ 2.744 $KSM
🧗 Caiv9TbPz68q5dC8EcHu5xKYPRnremimGzqmEejDFNpWWLG
🔗 0x5768bd11a0e06bb79218b9522e3d9726a4a39d79059a30a3aa68aff28dab01de
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


[notification hubs] Update WNS type to windows

Packages impacted by this PR

@azure/notification-hubs

Issues associated with this PR

#27695

Describe the problem that is addressed by this PR
Updates the platform from wns to windows
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Yes
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-notification-hubs


Sync tabs and persist choice on localStorage.

These changes will open Windows tabs on Windows by default, and the choice will be persisted on local storage.

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr465.previews.kube001.services.stellar-ops.com


Feature Show Logged in account email or client ID for azd auth login and azd auth login --check-status

closes #1745

Exported auth.Manager.GetSignedInAccount()
Got the email and displayed it in the message.
Handel err in getting the account by printing the logged in message and logging the error.
Handel service principal empty account.
Implement a function to get client id for service principal
Got the client id for service principal and displayed it.
Handel empty client id.

Full flow of azd auth login and azd auth login --check-status with normal account

Full flow of azd auth login and azd auth login --check-status with service principal

@ellismg I learned about service principal and handled their exception.

Let me think about it and get back to you, I found that there is a difference between logging in and checking the status so, I will try to make the whole code more consistent as it's as confusing to me as it is to you.

@ellismg @vhvb1989 are we still looking into this enhancement and is the PR still valid?


Update update-statistics.md

Corrected link, so that it matches the link text.

@WilliamDAssafMSFT
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@sommarskog I'm going to merge both your suggestions (#9742 and #9743) into an internal PR. You'll still get credit.


[Core] Rename utils/children.js

[x] PR has tests / docs demo and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Rename utils/children.js to utils/childUtils.js
Convert to named exports, update imports and usage

In hindsight, the rename probably wasn't strictly necessary given named exports. Either way, this allows a pascalCase import without conflicting with the children prop.

That looks good to me. I'm not sure to understand the use case for createChildFragment for the FlatButton and RaisedButton, but anyway.

Neither did any of us! :laughing:


Add Pixel Perfect Collision Without Rotation

Added Pixel Perfect Collision to the image.h
Added basic collision check to be used in PPC function to utils.h

Can you delete rotation parameters if no rotation is calculated yet. You can add them back, when you add rotation calculation.


Introducing product categories

Problem description
Currently our APIs are organized into sub-projects, later it might be changed to working groups with the related APIs, but there's still no organization of the APIs from the product view, what the developers will see when using Camara APIs.
Possible evolution
I'd like to propose the introduction of product categories, like device, home, network etc.

They could be used for naming the APIs as a prefix, e.g. device-connectivity.yaml, device-geofencing.yaml.
The category could be also added to the info field of the OAS, like x-category: device
Also for naming the events the short product category name could be used instead of the long API name

Alternative solution
Additional context

HI Akos. At product level there is a category proposal followed by Use Cases, which i'm pretty sure that will not be valid for CAMARA where the names are more specifying the functionality implemented by the API than the service that is solved with it.
Additionally, APIs are evolving in some cases, changing their scope (e.g. mobile to also fixed), not sure how this will evolve and be maintained over the time.
I'd propose that, for the time being, we fix the already open and even agreed discussions in the particular APIs, e.g. https://github.com/camaraproject/DeviceStatus/issues/125, for been able to get solutions on existing issues asap.


SMB Password written to agent log

When the SMB deployer fails, the password is written in clear text to the agent log. This could be a security problem.

Bitbucket: https://bitbucket.org/nskvortsov/deployer/issue/6
Originally reported by: knatten
Originally created at: 2013-01-23T17:35:41.251

removed passwords from debug info

Original comment by: Nikita Skvortsov


lwm2m_handle_packet trying to free a NULL payload pointer

lwm2m_handle_packet frees the payload on line 644 without taking into consideration that the payload may not exist, for example in case the client has to send a message without payload (which often happens during the bootstrap phase and connection to the LwM2M server).
See: https://github.com/eclipse/wakaama/issues/707

I don't think that this is necessary. lwm2m_free just calls the free function from the standard library.

Closing due to the reasons given by @LukasWoodtli.


upscaler: 1.4.0 -> 1.4.1

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

I did see this update, but wanted to see whether ryantm bot would pick it up, seems that is not the case. So i'll update when i see it in the future.

r-ryantm will always update packages with a (working) updateScript that build...eventually
The backlog of packages to run update checks for is pretty big, so it can take some time for it to come back around to your package. You can see this in the logs of this package for example, where the last check was November 20th (before the tag was made)
Cases like that are why it's still helpful to manually bump packages -- which ./maintainers/scripts/update.nix is really great for BTW. r-ryantm is just another tool to help you out


feat(theme-default): Updated codeblock - fix copyBtn Icons && updated wordWrapBtn animations for equality between both buttons

Summary
https://github.com/web-infra-dev/rspress/assets/69188140/f2426fd8-caad-45e7-af85-f19eb5e03d3b
Related Issue
resolves #612

Checklist

[x] I have added changeset via pnpm run change.
[x] I have updated the documentation.
[ ] I have added tests to cover my changes.

Thank you 👍🏻


make some manifests in docs/high-availability v1

@nikhiljindal @bgrant0607 @brendanburns

LGTM. Thanks!

LGTM


Feature Request: Arm & Disarm without code

Hi, first and foremost thank you for this custom integration, without it the Securitas alarm system lacks... a lot.
I have also installed a custom alarm panel with the "Alarmo" custom component, and also a Visonic alarm system with another custom integration, both integrations allow the arming and disarming of each system without the need to enter any codes on the keypad.
Since the default "code_disarm_required" was "false" I commented out the code option in the configuration file (code: !secret securitas_direct_code) to have the code value empty and, surprisingly .... it works! , however the "code_format" attribute is still set to "number", so the keypad still pops up in the alarm panel when trying to arm or disarm, the other integrations have this set to "null" and thus they don't show the keypad.
I've modified the alarm_control_panel.py file from the component to return a None value for the "code_format" function, however I'm not a developer and can't go much further.
Is there a way to modify this integration to return None:
return None
Instead:
return alarm.FORMAT_NUMBER
in the event the code variable from the configuration is not set?
My solution is very crude and temporary and I would very much like to have this feature merged into the main version to be able to arm/disarm every alarm panel with a button click since I'm the only one that has access to my HA instance.
Thanks in advance, best regards.

I'll second this request as my alarm system does not have a code

Let me take a look!

@DNKROZ
I had same issue where alarm control panel would popup a keypad to enter code even if I had unset the "code" key in the configuration.yaml. I managed to set code_format to null by adding it in my customize.yaml file.
Here is an excerpt of my customize.yaml file:
alarm_control_panel.name_of_my_entity:
friendly_name: "xxxx"
Assuming code is unset in configuration.yaml...
When code format is set to no_code the panel will display a field to enter
the pin code instead of a keypad.
When set to null neither field nor keypad are displayed....
code_format: null
Cheers,

Hi @jpg1961
Setting up code_format to null in the customize.yaml file works like a charm, thank you!
Still, would be great to have it as a feature from the integration itself, but this is a great solution for the time being
Best regards.

Hi @DNKROZ,
Actually, the integration uses home assistant control panel components and inherits from its  code_format variable.
So I guess updating the securitas-direct-new-ap integration documentation instead of adding a feature would fit the bill ;-D.
Cheers,

Sorry, I have been unable to reproduce this. I'm on <IP_ADDRESS>, can someone tell me how to remove the keypad so I don't need to input a code?

This should be working since a few releases ago


Create kadai.txt

Kagoshima University
The university's homepage is

https://www.kagoshima-u.ac.jp/ (Japanese)
https://www.kagoshima-u.ac.jp/en/ (English)

Student emails are using ID + @kadai.jp, you can find details from this page(Japanese).

@idiotWu Pull request merged. Thank you!


Wall sprites

The wall sprites was more detailed in the original game. I think it will be worth to draw some sprites for them in pacmacs.
There should be 14 wall sprites overall if I was not mistaken (for various wall connection variants). Also you should implement a sprite selection logic for drawing the wall.
The following picture should render all of the walls with different sprites:
##

###  #
###  #
###

#

It will dramatically improve the game atmosphere.

It's actually really easy to do using xpm pixel-level access without drawing any sprites manually:

But it's not that easy on Windows because of this bug #59 I think we have to investigate it further.

Once we have finished this, we need to make another animation video for the README


CAD-517:  more structured-vs-plain fixing

deal with structured-ness in renderTextMessage, which covers all scribes, not just FileSk
factor formatters a bit

checklist

[x] compiles (cabal new-clean; cabal new-build)
[x] tests run successfully (cabal new-test)
[ ] documentation added and created (cd docs; nix-shell --run make)
[ ] link to an issue
[ ] link to an epic
[ ] add estimate points
[ ] add milestone (the same as the linked issue)

bors r+


HeadObject validation does not honor all validation parameters

Hi! This issue appears related to https://github.com/spulec/moto/issues/2263
Observed Behavior
I'm using unittest to write a test that will ensure validation on HeadObject calls work as expected. My setUp function includes the following code:
TEST_BUCKET = "fake_bucket"
TEST_KEY = "fake.csv"

@mock_s3
class TestVerifyS3Object(unittest.TestCase):
    def setUp(self):
        # Some other code ...
        self.s3_client = boto3.client("s3", region_name="us-east-1")
        self.s3_client.create_bucket(Bucket=TEST_BUCKET)
        self.s3_client.upload_file(Filename=tmp_file, Bucket=TEST_BUCKET, Key=TEST_KEY)

My unit tests have attempted both of the following:
        with self.assertRaises(botocore.exceptions.ClientError):
            self.s3_client.head_object(Bucket=TEST_BUCKET, Key=TEST_KEY, IfMatch="foo")

and
        with self.assertRaises(botocore.exceptions.ClientError):
            self.s3_client.head_object(
                Bucket=TEST_BUCKET, Key=TEST_KEY, IfUnmodifiedSince=datetime.datetime.utcnow())

Both result in AssertionError: ClientError not raised
I am invoking the tests locally using nose==1.3.7, and using moto==1.3.14 which I installed using pip.
Expected Behavior
When I run the function I'm testing in a real environment using boto==2.49.0, boto3==1.11.8, and botocore==1.14.9, this code raises a botocore.exceptions.ClientError:
In [17]: try:
    ...:     client.head_object(
    ...:         Bucket=TEST_BUCKET, Key=TEST_KEY, IfMatch="foo",
    ...:     )
    ...: except botocore.exceptions.ClientError as e:
    ...:     print(e)
    ...:
An error occurred (412) when calling the HeadObject operation: Precondition Failed

This error response also happens when I execute this code in a lambda.
Suspected Reason
I did a little digging and have one idea as to why. I am admittedly not too familiar with this codebase but I hope this is helpful:
The _key_response_head method only looks at the If-Modified-Since header in the request, when actually there are several validation headers that may be passed to the head_object operation.
If so...
If this is the case, then I imagine something similar to https://github.com/spulec/moto/pull/2276/files would be necessary. If it is that simple, I'd be willing to take this on.
Thanks for reading!

Thanks for opening! I believe your diagnosis is correct and that we don't validate on any of the other headers.
If you get a chance, a PR would be great!

This is now fixed as of moto >= 1.3.16.dev5


Compatibility with  numpy 1.24

With the latest release of numpy 1.24.0, numpy deprecated and removed np.int. This PR replaces np.int with np.int_. The change was tested using numpy 1.23.5 and numpy 1.24.1 with Python 3.10.9.
If you merge the PR, please release a new version of pyGAM on pypi.
Closes #326

Having the same problem. If I understand correctly, just using int instead of np.int should solve the problem. Is there any advantage for np.int_?

According to the numpy documentation, int is interpreted as np.int_. I make this change.

Thanks! This is how I'm reading numpy's message. 😀

@dswah Could you approve?

Looks like the necessary changes were made to the main code and a new version released recently. I will close the PR.
Thank you for getting the new version out.


upgrade from old version

Good day! Tell me is there a mechanism to update the software without reinstalling? Or do you need to uninstall and then reinstall the software?

Hi, yes there are some limitations with the actual installer which makes it necessary to uninstall before installing a new version. I will improve that into the next version.

Thanks


Wild-card linking

Checking the build output (of some project) (with a high verbosity) reveals that, simply all libs in the ..\vcpkg\installed\x64-windows-static\lib folder get fed to the linker with a wild-card *.lib .
This, IMHO, is asking for trouble, but at the very least dis-allows for some more fine-grained approach to linking libraries.

This issue hasn’t been updated in a year; if it is still an issue, please reopen this issue.


Some TxROM games hang at the title screen

e.g. Super Mario Bros 3 - The checkered floor tiles don't appear correctly either. Just the red curtain and it hangs upon load. No crashes or errors in the console.
Krusty's Funhouse goes to black screen after the initial credits

Issue was IRQ trigger timing from TxROM mapper


Increase timeout on logging test

I noticed another autoconfiguration logging test flake: https://api.travis-ci.org/v3/job/457015991/log.txt
Increase the timeout of the test from 30s to 60s now. This now matches the timeout of the logging sample.
passed 20/20 runs locally.

Codecov Report

Merging #1242 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1242   +/-   ##
=========================================
  Coverage     67.84%   67.84%
  Complexity     1319     1319
=========================================
  Files           186      186
  Lines          5387     5387
  Branches        547      547
=========================================
  Hits           3655     3655
  Misses         1497     1497
  Partials        235      235

Flag
Coverage Δ
Complexity Δ

#integration
?
?

#unittests
67.84% <ø> (ø)
1319 <ø> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


[improve] [broker] Print warn log if compaction failure

Motivation
Now exceptions that happen in the flow of compaction task are collected into variable currentCompaction and don't print any log.
When compaction doesn't work, two reasons come to mind:

the task skipped by rules.
the task failed.

We can't determine which causing the problem if there has no log, this increases the difficulty of troubleshooting.
The API pulsar-admin topics compaction-status <topic> lets us see what happens when the last compaction executes, But it can not help us know if there were previous missions that failed.
Modifications
Print warn log if compaction fails.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

https://github.com/poorbarcode/pulsar/pull/63

/pulsarbot rerun-failure-checks

Codecov Report

Merging #19405 (6cb2ff6) into master (39dd1cd) will increase coverage by 30.22%.
The diff coverage is 76.31%.

@@              Coverage Diff              @@
##             master   #19405       +/-   ##
=============================================
+ Coverage     32.36%   62.59%   +30.22%
- Complexity     6355    25663    +19308
=============================================
  Files          1648     1830      +182
  Lines        123990   133944     +9954
  Branches      13523    14737     +1214
=============================================
+ Hits          40129    83838    +43709
+ Misses        77958    42381    -35577
- Partials       5903     7725     +1822

Flag
Coverage Δ

inttests
24.88% <71.05%> (+0.07%)
:arrow_up:

systests
25.58% <18.42%> (-0.11%)
:arrow_down:

unittests
59.78% <42.10%> (+42.24%)
:arrow_up:

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

Impacted Files
Coverage Δ

...va/org/apache/pulsar/broker/service/ServerCnx.java
54.24% <53.84%> (+17.13%)
:arrow_up:

.../org/apache/pulsar/broker/admin/AdminResource.java
74.93% <87.50%> (+31.90%)
:arrow_up:

...sar/broker/service/persistent/PersistentTopic.java
64.30% <100.00%> (+13.02%)
:arrow_up:

...ker/loadbalance/impl/LeastLongTermMessageRate.java
73.33% <0.00%> (-11.12%)
:arrow_down:

...r/service/AbstractDispatcherMultipleConsumers.java
70.96% <0.00%> (-9.68%)
:arrow_down:

...r/service/schema/DefaultSchemaRegistryService.java
0.00% <0.00%> (-6.25%)
:arrow_down:

...in/java/org/apache/pulsar/PulsarBrokerStarter.java
28.14% <0.00%> (-3.00%)
:arrow_down:

.../apache/pulsar/broker/loadbalance/LoadManager.java
58.33% <0.00%> (-2.78%)
:arrow_down:

.../apache/pulsar/client/impl/ClientCnxIdleState.java
68.88% <0.00%> (-2.23%)
:arrow_down:

...xtensions/channel/ServiceUnitStateChannelImpl.java
0.96% <0.00%> (-0.01%)
:arrow_down:

... and 1224 more


Worker thread

Made the changes to send data from worker thread to main thread to update the UI.

Removed the .settings file


--convert-3to4 doesn't upgrade Light2D Blend Mode mode -> blend_mode

Godot version
v4.0.2.stable.official [7a0977ce2]
System information
Linux Ubuntu 22.04 with Unity desktop
Issue description
Upgrading a Godot 3 project to Godot 4 (via GUI or godot4 --convert-3to4) does not upgrade the Light2D mode member to blend_mode.
As a result, after opening the upgraded project, all non-Add blend modes have been lost. Subtract, Mix and Mask are all reset to Add blending mode.
Note: Mask has been removed and now requires CanvasItem clipping, which is a much more complex upgrade. I suppose we can print some warnings in the console (and if possible, in some popup when upgrading via GUI) to warn user that they need more work to upgrade this feature usage to Godot 4. It should be added on conversion doc side too, but this task has already been added on https://github.com/godotengine/godot-docs/issues/5121
At least Subtract and Mix should be upgraded correctly.
Steps to reproduce

Add some lights with different blending modes in the project... or just download the MRP below
Run godot4 --convert-3to4 or upgrade project via GUI
Observe that blending modes were lost.

Hint: for a quicker check without opening Godot, use the MRP which is under Git, run godot4 --convert-3to4 in the console and check the Git diff to see that mode has not been renamed blend_mode.
Minimal reproduction project
v3.5.2 - convert 3to4 Light2D Mix Blending Mode reset to Add.zip

The convertor doesn't have advanced heuristics to detect when mode is used in the context of Light2D in your scripts. As the term has a very wide usage and can be mistaken in other contexts, we cannot add such a rename to the convertor. As explained in the popup before you run it, it works on the best effort principle, and such a change is outside of its capabilities.

Followed this thread and followed its conclusions to make a PR to fix this issue (though it seems I had to create a _set() rather than _get() method).


Bring all auth-related models into same namespace

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.42%. Comparing base (96ae232) to head (c8b0462).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
+ Coverage   99.41%   99.42%   +0.01%
==========================================
  Files          85       85
  Lines        2222     2267      +45
==========================================
+ Hits         2209     2254      +45
  Misses         13       13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[FEATURE REQUEST] Support endpoints field in the config endpoint

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
The endpoints field was introduced in Iceberg REST spec recently to describe the server capabilities.
https://github.com/apache/iceberg/blob/c0d73f4ef5c16401bdfd62e1745faf2fbbf62177/open-api/rest-catalog-open-api.yaml#L150
Describe alternatives you've considered
No response
Additional context
No response

Hi @flyrain , I am interested in working on this feature :)

And I have a question about the rule for adding API endpoints: do we mainly based on the access control privileges?
For example:

if a user with NAMESPACE_LIST privilege, add these into endpoints

GET /v1/{prefix}/namespaces
GET /v1/{prefix}/namespaces/{namespace}
GET /v1/{prefix}/namespaces/{namespace}/tables
GET /v1/{prefix}/namespaces/{namespace}/tables/{table}

if a user with NAMESPACE_CREATE, add this into endpoints

POST /v1/{prefix}/namespaces

if a user with NAMESPACE_DROP , add this into endpoints

`DELETE /v1/{prefix}/namespaces'

I don't believe it emits endpoints based on privileges; it should simply list all available endpoints. Even if a client lacks the privilege for a specific endpoint, they would still receive the full capabilities of the server.

I don't believe it emits endpoints based on privileges; it should simply list all available endpoints. Even if a client lacks the privilege for a specific endpoint, they would still receive the full capabilities of the server.

Thanks for the clarification! That approach makes a lot more sense—my earlier idea was probably overcomplicating things.

Hi @flyrain, I created a draft PR as the POC of this feature. However, I’d like your suggestion on one thing: the endpoints-related feature in Iceberg hasn’t been released yet (current version 1.6.1) and is planned for 1.7.0. I’ve temporarily extended some necessary classes as a workaround. Would you suggest we proceed with the current approach, or would it be better to pause development and continue once 1.7.0 is released and integrated with Polaris?

I'd recommend to wait for iceberg 1.7.0. It's not urgent as clients probably also wait for 1.7.

Hi team, we can close this issue as it has been solved in #442


How to access variables in project.pbxproj ?

I want to add Crashlytics to my project.
One of the steps is "Add a Run Script Build Phase". I should add line:
"${PODS_ROOT}/Fabric/run" <FABRIC_API_KEY> <BUILD_SECRET>
So, FABRIC_API_KEY and BUILD_SECRET I'd like to configure via .env-file (to set up different Crashlytics-accounts for different environments).
In project.pbxproj it looks like:
BCC7406A1F35F118000AEAAA /* ShellScript */ = {
			isa = PBXShellScriptBuildPhase;
			buildActionMask =<PHONE_NUMBER>;
			files = (
			);
			inputPaths = (
			);
			outputPaths = (
			);
			runOnlyForDeploymentPostprocessing = 0;
			shellPath = /bin/sh;
			shellScript = "\"${PODS_ROOT}/Fabric/run\" <FABRIC_API_KEY> <BUILD_SECRET>";
};

@GantMan , I'm not very familiar with XCode,  because it's my first RN-project.
Also I should add <FABRIC_API_KEY> to Info.plist file. According to react-native-config documentation, I have access to variables from my .env-file in Info.plist. Am I right?

@pedro do you have any solutions for my case?

@NachtRitter I achieved similar thing using this little over-complicated, but didn't find anything easier, because BuildDotenvConfig.ruby just deletes /tmp/envfile after it's processed.

use export in .env.* files so you can use the values as environment variables in your build script:

export ABC=1

backup env file name in scheme pre-action script (reading $ENVFILE in the build script didn't work for me for some reason)

if [ -n /tmp/envfile ]
then
  cp -f /tmp/envfile /tmp/my_envfile
else
  echo ".env" > /tmp/my_envfile
fi

run the envfile in build script to get your variables set as environment variables so as you can use them in the script

envfile=$(< /tmp/my_envfile)
source $PROJECT_DIR/../$envfile
echo $ABC

hi @NachtRitter , my pr #349 allows reading values from env file in Build settings. please give it a try, thanks

@maxkomarychev Thanks, however I'm not working currently with React Native projects. So maybe someone else will check it


Is the implementation of ProxylessNAS available?

Thank you for sharing your great work!
I'm trying to compare the results of the experiment of ProxylessNAS (Table 5) in your paper with other HW-NAS methods.
So I would like to use the same hyperparameters and experimental setup as in the paper.
On the OpenReview website, AnonReviewer3 said,

It looks like the source code includes -- among other things -- (i) a reproduction of the FBNet search space, (ii) code for obtaining on-device benchmark numbers, (iii) a simple API for querying the inference times and energy usages of FBNet and NASBench-201 architectures, and (iv) implementations of the ProxylessNAS and FBNet search algorithms.

but I couldn't find the implementation of ProxylessNAS mentioned here.
Could you tell me where the implementation is, or what hyperparameters / experimental setup you used are?

Thanks for your interest in HW-NAS-Bench!
Because ProxylessNAS has already released its official codebase here, we are not considering including it in our code release currently. However, we are happy to provide more details about it.
During search, we set the total epochs as 120 (pretrain_epoch as 30), batch_size as 128, and lr 0.05.
After search, we use total epochs as 300, batch_size as 196, and lr 0.02 to train the model from scratch.
BTW, we suggest you can first try our searched architectures listed below with your training and inference code to check the implementation.

Architecture searched when targeting Raspi 4: 'skip', 'k3_e3', 'skip', 'skip', 'skip', 'k5_e3', 'k3_e3', 'k3_e1', 'k3_e3', 'k5_e6', 'k3_e3', 'k3_e3', 'k3_e1_g2', 'k5_e6', 'k5_e1', 'k5_e1', 'k5_e1', 'k5_e3', 'k5_e1_g2', 'k5_e1', 'k5_e1', 'k5_e3'
Architecture searched when targeting Edge GPU: 'k5_e3', 'k5_e6', 'skip', 'skip', 'skip', 'k5_e6', 'skip', 'skip', 'skip', 'k5_e6', 'skip', 'skip', 'skip', 'k3_e3', 'k3_e1', 'k5_e1', 'k3_e1', 'k5_e6', 'k5_e3', 'k5_e3', 'k5_e3', 'k5_e6'
Architecture searched when targeting FPGA: 'k5_e1', 'k5_e3', 'skip', 'skip', 'skip', 'k5_e3', 'k3_e1', 'k3_e1_g2', 'k3_e1_g2', 'k5_e6', 'k3_e1_g2', 'k3_e1', 'k3_e1_g2', 'k5_e6', 'k5_e1_g2', 'k5_e1_g2', 'k3_e1_g2', 'k5_e3', 'k5_e1_g2', 'k5_e1_g2', 'k5_e1_g2', 'k5_e6'

Note: 'k' indicates the kernel size, 'e' indicates the expansion ratio and 'g' indicates the group number (g=1 will be ignored). Also, a more detailed visualization is shown in the attached figures.

Thanks for your quick response and for sharing the details!
Following your advice, I will start by checking the training code using the searched architectures.
Thanks again for your excellent work!


WoltModalSheet.show does not not reflect the state in real time kindly assist, how can one use statefulbuilder

Can you please add more description?

Hi @leadpresence, I was trying to setState as well but it seems to be not be updating the state inside the modal. Using ValueListenableBuilder instead works

Hi,
The v0.8.0 has improved the Readme and added this section to explain the state management at modal level.


component selection will not fully override a strict selection by a platform

Expected Behavior
Provide some way of dealing with a strict override using component selection
hibernate-jpa-modelgen = {
  module = "org.hibernate.orm:hibernate-jpamodelgen",
  version = "6.4.+",
  strictly = true,
  reject = { reason = "...", version = "6.5.+", expiration = "6.6+" },
}

related

#29417

Current Behavior (optional)
configurations.configureEach {
  resolutionStrategy {
    componentSelection {
      all {
        if (candidate.module == "hibernate-jpamodelgen" && candidate.version.startsWith("6.5")) {
          reject("https://hibernate.atlassian.net/browse/HHH-18203")
        }

> Task :jpa:dependencyInsight
org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final FAILED
   Selection reasons:
      - By constraint: dependency was locked to version '6.5.2.Final'
   Failures:
      - Could not find org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final.

org.hibernate.orm:hibernate-jpamodelgen:{strictly 6.5.2.Final} -> 6.5.2.Final FAILED
\--- annotationProcessor

org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final FAILED
+--- annotationProcessor
\--- org.springframework.boot:spring-boot-dependencies:3.3.0
     \--- annotationProcessor (requested org.springframework.boot:spring-boot-dependencies:3.+)

org.hibernate.orm:hibernate-jpamodelgen:6.4.+ -> 6.5.2.Final FAILED
\--- annotationProcessor

configurations.configureEach {
  resolutionStrategy {
    componentSelection {
      all {
        if (candidate.module == "hibernate-jpamodelgen" && candidate.version.startsWith("6.5")) {
          reject("https://hibernate.atlassian.net/browse/HHH-18203")
        }

> Task :jpa:dependencyInsight
org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final FAILED
   Selection reasons:
      - By constraint: dependency was locked to version '6.5.2.Final'
   Failures:
      - Could not find org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final.

org.hibernate.orm:hibernate-jpamodelgen:{strictly 6.5.2.Final} -> 6.5.2.Final FAILED
\--- annotationProcessor

org.hibernate.orm:hibernate-jpamodelgen:6.5.2.Final FAILED
+--- annotationProcessor
\--- org.springframework.boot:spring-boot-dependencies:3.3.0
     \--- annotationProcessor (requested org.springframework.boot:spring-boot-dependencies:3.+)

org.hibernate.orm:hibernate-jpamodelgen:6.4.+ -> 6.5.2.Final FAILED
\--- annotationProcessor

hibernate-jpa-modelgen = { module = "org.hibernate.orm:hibernate-jpamodelgen", version = "6.4.+" }

dependencies {
  annotationProcessor(platform(libs.spring.bom))
  annotationProcessor(libs.hibernate.jpa.modelgen)

Context
current fix for every module, write a plugin specific to library that only contains the following and apply it to every subproject that needs this dependency. As a solution that will be hard to read and seems like poor code design.
  annotationProcessor(libs.hibernate.jpa.modelgen) {
    because("https://hibernate.atlassian.net/browse/HHH-18203")
    version {
      strictly("6.4.+")
    }
  }

alternatively, works and is a reasonable design but doesn't support "because/reason"
hibernate-jpa-modelgen = { module = "org.hibernate.orm:hibernate-jpamodelgen", version.strictly = "6.4.+" }

current gradle version: 8.7

This is the intended behavior, and there’s no plan to change it. This issue will be closed.

If you reject the only version seen while doing dependency resolution, Gradle will fail resolution. You will need to provide an alternative version that is not rejected. There is no reason for Gradle to invent a version on its own.
This is not about the suggested syntax which is covered in #29417


pwsh?

According to https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=example#pwsh, there is pwsh alias. However, it's not mentioned here.

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

ID: a0e444c2-69c6-4d71-6fd0-94d0f4097d3a
Version Independent ID: 3a727833-1cc3-c2fb-c5b3-22605eee2721
Content: PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/powershell.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

My guess on reading between the lines and seeing some examples is that the pwsh alias would run Powershell Core, while the powershell alias runs non-core Powershell (what the heck do we call that, classic? desktop? legacy? old?)
And then I'm further guessing that if you're running the PowerShell task without the alias, and either don't specify pwsh or set it to false, that it will run non-core Powershell, and if you set it to true it will run with Powershell Core.
Digging into the source code, and finding some closed issues referencing pwsh confirms my belief.

@FISHMANPET I suspect you're right, but documentation can definitely be improved to highlight the differences between the shortcuts, as well as describe pwsh flag, which is only mentioned commented out in the sample and not explained anywhere.

Yes. In fact every Pipeline task in these docs list parameter names and then in a table describe (some of) them by a human name instead of a machine name. Please update all the tables to actually include a column for that actual task parameter name in addition to the human readable names so we know what parameter name is being described.


Adds config to add package of the the working file to guru scope

Migrate codes from https://github.com/alvarolm/GoGuru , make it easier to pass guru's scope param.

IMO GoGuru has nic UX, maybe depend on it is a better option.

Nice. Thanks -:)


Fix image on "getting started with WDL" page

In this section https://docs.dockstore.org/en/develop/getting-started/getting-started-with-wdl.html#testing-locally there is an image showing the steps of what the CLI does. One box says "execute tool with inputs using CWL" even though the page is about WDL. Need to make a corrected image for WDL to use on this page.
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Seabright Sprint 28 Cuttlefish
┆Issue Number: DOCK-1193

Looking good


About merge(mul) problem

My script is below:

imodel= {};
for input_index,in_feat_dim in enumerate(v_set.invector_dimension):
    imodel[input_index] = Input(shape=(in_feat_dim,))

modelx = merge([imodel[0], imodel[1],imodel[2]], mode='concat' )
modelx = Dropout(0.2)(modelx)
modelx = Dense(hidden_layer1, activation='relu')(modelx)
modelx = Dropout(0.5)(modelx)
modelx = Dense(hidden_layer2, activation='relu')(modelx)
modelx = Dropout(0.5)(modelx)
modelx = Dense(hidden_layer3, activation='relu')(modelx)
modelx = Dropout(0.5)(modelx)

modelx = Dense(v_set.target_dimension, activation='sigmoid')(modelx)
modelx = merge([modelx,imodel[0]], mode='mul' )

model = Model(input = [imodel[0], imodel[1],imodel[2]],output = [modelx])

In this script, Output is mul ( imodel[0] and sigmoid(~= 0<x<1 mask)).
So output is smaller than imodel[0].
But I checked number, some output is bigger than imodel[0]. why this problem is occurred????
below is my check script:
output  =  model.predict([input_data[0],input_data[1],input_data[2]])
np.maximum(input_data[0],output) == input_data[0]
or
np.maximum((input_data[0] - output) ,0.0)

if your input  input_data[0] (you mentioned it also imodel[0]) < 0, then the output is bigger than the imodel[0]....................


io/i2c: revert a couple of commits related to multiple i2c paths

Actually it should be only on /dev
This reverts commit c06a3acd8ebf948d23683f023d5b58ffb87c43c8
and commit 4c200f23b560833e77f8d52400ba15ed1017d691

I'm all for it

:+1:

merged, thanks


BCMOHAD-15906||Adjusted size and updated unassign functionality

@ahshaik1 @anudishCGI We want to do a pass on the code next week to ensure all debug statements are removed and proper commenting exists on all associated methods. I will setup a ticket with @NataliaNikishina -- We will do this along with working on general improvements on test class coverage.


howto repeatuntil

revert to schema.json
replace depricated methods and fix warnings
add timeout for CI issues
fix set-signal incrementing expected signal count and move docs
how to repeat until a condition is met

Documentation looks ok, but we need a common base for the commits e.g. a git mv one to make it easier to review


rasterio install crashes if numpy is not already installed

This is a common problem and it is particularly painful because it causes CI spurious crashes.

As of 72552d8 rasterio and fiona are extras_require so we don't need to handle the case automatically. The user should follow the rasterio setup-time instructions.


fix scaling issues on bar graph

merge this pull request to fughz/ExtHoloGraphLibrary.
Thanks :+1:


Maze Game

A simple project using HTML, CSS, and JavaScript.
Let's Play Together.✨

Hey!!!
I didn't get you
What type of card ? What it is ?
On Tue, Oct 5, 2021, 00:13 Nikhita @.***> wrote:

@.**** requested changes on this pull request.
Just make a card of the game in the home page as well and link it to the
maze game.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Nikhita28/ChillZone/pull/23#pullrequestreview-770649838,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUHQTDL4KEB7YZVU75GKWO3UFHYVRANCNFSM5FJ77RNQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Hey!!! I didn't get you What type of card ? What it is ?
…
On Tue, Oct 5, 2021, 00:13 Nikhita @.> wrote: @.* requested changes on this pull request. Just make a card of the game in the home page as well and link it to the maze game. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUHQTDL4KEB7YZVU75GKWO3UFHYVRANCNFSM5FJ77RNQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

She just meant that add the link to play the game on the main page of website.

Okaysss
On Tue, Oct 5, 2021, 15:05 VIDHI BHATT @.***> wrote:

Hey!!! I didn't get you What type of card ? What it is ?
… <#m_-5134694677415375174_>
On Tue, Oct 5, 2021, 00:13 Nikhita @.*> wrote: @.** requested changes
on this pull request. Just make a card of the game in the home page as well
and link it to the maze game. — You are receiving this because you authored
the thread. Reply to this email directly, view it on GitHub <#23 (review)
https://github.com/Nikhita28/ChillZone/pull/23#pullrequestreview-770649838>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUHQTDL4KEB7YZVU75GKWO3UFHYVRANCNFSM5FJ77RNQ
. Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
She just meant that add the link to play the game on the main page of
website.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Nikhita28/ChillZone/pull/23#issuecomment-934238733,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUHQTDNM2EX576PAHOZZIUDUFLBGRANCNFSM5FJ77RNQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


socket.on isn't responding

I can't seem to get the socket.on to work with sails running as a separate back-end. I am running sails 0.11.4 and the .get calls are working fine, but .on doesn't seem to be doing anything. Any hints or tips are more than welcome.
Front-end code:
//this works fine
 $sails.get('/order', function(message){
     console.log(message);
      });
//this doesn't do anything
      var orderHandler = $sails.on("order", function(message) {
        console.log(message);
      });

Backend config:

Sessions disabled (.sailsrc)
autoWatch in blueprints enabled

Never mind, the error was caused by the person sitting in front of the computer. I wasn't using blueprint routes.


Landscape Left and Right  Orientation Issue

Please help to support orientation perfectlly. I am getting issue in orientations

I can see same issue.

@daliborristic883 How to solve the issue?

Same here the preview layer is halved and the view rotates.
Any solution?

I am facing same issue but found the solution after so many days.
The main issue of the orientation is in the CameraManager.swift file (Custom or cocoapod file), and you have to do changes in this file.
If you are using cocoapod of the CameraManager then you have to unlock this file to do changes.
Here is the solution of the landscape left and landscape right orientation issue :
In CameraManager.swift file, there is one function named "_videoOrientation", you will see switch case of deviceOrientation and in
case .landscapeLeft: it will return .landscapeRight and also
case .landscapeRight: it will return .landscapeLeft
So, the issue is here, you need to do below changes in that cases, and the changes are :
case .landscapeLeft:
return .landscapeLeft
case .landscapeRight:
return .landscapeRight
after you done with changes, you will check the orientation issue is fixed.
Guys, hope you will get the solution from this.

Thanks @hiteshcmarix !


No way to disable automatic refund when order is canceled

How can I disable the automatic refund when a order is canceled in Magento?
If we change something in a order it will create a copy of the order and cancel the previous one automatically refunding the payment.
In settings there's a option to ignore refunds from Adyen->Magento but how can Magento do not send refund requests to Adyen automatically?

Hi Nuno,
By default it will do a cancel-or-refund request to Adyen if you cancel an order in magento with a Adyen payment method used. We could make a setting that you can turn this off. What I do not understand is why you are changing the order ?
Regards,
Rik
Adyen

Hi Rik,
Sometimes customers order items that are not in stock and we propose a similar product that do not affect the total amount, usually it's the same product but with a different color, we need to edit the order to change the SKU to ship and by doing that the original order is canceled.
If you want you can merge the changed that I did, added a option on settings and on the Observer.php function it will check that variable.
Regards,
Nuno Gato
Robosavvy

Hi Nuno,
Thanks for your explanation. Yes creating a setting that is by default set to enabled is an good solution. If you can do a PR of this that would be great.
Regards,
Rik
Adyen

Hi Nuno,
I accepted your pull request see #523
Regards,
Rik
Adyen


strange generated HTML

Describe the bug
When looking into the HTML the SunEditor generates, I am surprised by the amount of "strange" HTML code I find.
To give some examples

 at the end of a heading (just before the trailing </hx>) or a paragraph
 in paragraphs
lots of unnecessary   (which sometimes lead to strange and unexpected formatting)

To Reproduce
(sorry, I cannot reproduce - there are too many of them and I usually find them long after they have been created)

The unwanted
 tag may be related to https://github.com/JiHong88/suneditor/issues/1317


stdenv/check-meta: change to allowlist and blocklist

Motivation for this change
It felt significant to make this rename...
I haven't thought of the way to make it throw with instructions to change to the new attr, and I still need to make documentation for it. For now it will be a draft until I get back to it. But if anyone wants to finish that go ahead.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I can make a release note later. Will also do nixos option renames.

Too late but why not allowedLicences and forbiddenLicenses?


Fix #163 by skipping HasType for unboxed quantified variables

@Chris-Hawblitzel I'm going to land this, but please review it when you get the chance.

[ ] review by @Chris-Hawblitzel, then delete branch


fix: improve cloning codes

Fix #212
The current implementation will clone the properties defined in instance.
But the headers property defined in prototype in Node.js v16 or higher.
So this PR aims to support prototype inheriting in cloneIncomingMessage.
The final pitfalls is this is not support instanceof IncomingMessage and instanceof PassThrough. If the msw uses those operators,  I think this must not be merged.

Hey, @hrsh7th! Thank you for submitting this fix.

The final pitfalls is this is not support instanceof IncomingMessage and instanceof PassThrough

This may be an issue, as we're exposing the cloned IncomingMessage publicly:
https://github.com/mswjs/interceptors/blob/4563ce7493b696830702877d4a61d0fd44d5feda/src/interceptors/ClientRequest/NodeClientRequest.ts#L238
When the consumer adds a response listener on ClientRequest, they will get the cloned message when using this library. They may have instanceof and other logic around that, which will break with this change if I understand correctly.
Maybe we can think of reusing parts of your solution to preserve the prototype? Would that be possible?

I've tested this locally on node16 re-using the same workflow that the github actions has and it works great!
Regarding the types, this function as it existed before and after this PR forces the type by casting to unknown and then to ClonedIncomingMessage. The stream itself has the same overall shape but it now has the prototype methods added in. If you remove the 'to unknown' part tsc has a way better idea about the type of the stream and it seems like it's been the wrong one for quite some time. Like if you look at the shape of an IncomingMessage vs what's there in main it's not the same at all. I think that's out of scope of this issue for now though.

I'd changed the implementation to support stream instanceof IncomingMessage.
This approach can be broken if both IncomingMessage and PassThrough have the same properties in different implementations. (This fact is the same in the existing implementation. So I think we don't care about it in this PR for now)

I think this PR is ready to review and merge.  👍🏼

Thank you for review, fix and merge!  🎉


Different J_regressor matrix for training and evaluation

I noticed that the regressor matrice to get 3D joints from predicted vertices are different between for training and for evaluation. In training, smpl.get_joints() multiply predicted vertices with J_regressor of SMPL_FILE and JOINT_REGRESSOR_TRAIN_EXTRA to get joints while run_evaluation() uses JOINT_REGRESSOR_H36M. What's the concern here? Thanks!

The joints used in Human3.6M have a slightly different definition than those used by the SMPL body model, so we use a different regressor to accurately recover them from vertices during evaluation.
You can use this definition of joints during training as well, but for simplicity we use a single regressor that is compatible with all training datasets.

Thanks! I have tried to apply both regressors on T mesh and found the joints position are slightly different as you said. It seems that the joints of Human3.6M are more near the skin than the SMPL joints, which located inside the body. Is this consistent with your observation?

Yes, there are only minor differences.


Space between main content last paragraph and footer

In the current apps that implement the new CDS (eds & eforms) the last paragraph on the main content seems to be too close the the footer -see attached image. Should we consider adding a margin-top on the footer so there is a little bit more separation?

Yes.

In the eforms app we added "margin-top: 100px;" on the footer -see below. Is that a good number? More/less?

I suggest using bootstrap classes and not pixel margins - i.e. mt-<1 2 3 4>
, or whatever is necessary)
On Thu, Jan 9, 2020 at 11:16 AM Diego A. Perez Mesa <
<EMAIL_ADDRESS>wrote:

In the eforms app we added "margin-top: 100px;" on the footer -see below.
Is that a good number? More/less?
[image: image]
https://user-images.githubusercontent.com/12786488/72089257-5000ba00-32d1-11ea-83a5-e8ceecda28d6.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Chicago/design-cds-bootstrap/issues/59?email_source=notifications&email_token=AAQEDGIMNZFYPF5OYSOW2SDQ45LYLA5CNFSM4KEPUXZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRCHVY#issuecomment-572662743,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQEDGOCGVM36J4P4QX4ZHLQ45LYLANCNFSM4KEPUXZA
.

--
-- Christian Calderon

@chrisjcalderon beat me to the answer. When in doubt, check the framework first.
@mario-duran (FYI)
Thanks for flagging this, @dpmesa! Sorry the first response was terse- my email github fu in the morning is not great.


Can screen tearing be avoided

Do you happen to know if anything can be done to avoid screen tearing while capturing at higher resolutions?
For instance, if I capture at 2592 x 1944 (~5 MP), I get this kind of artifacts:

Seemingly there's not much that can be done within the class (method GetBitmapMainMain()). This is how the local data buffer is copied from the unmanaged DirectShow buffer - already teared. Any settings for DirectShow maybe, or is there not much hope?

Hey, thank you for the reply! Apologies for writing only now - turns out I was subscribed to notifications, but the e-mail notification checkbox was unchecked 🙄.
Thank you for sharing the other callback for the sample grabber! It does seem to work well (no tearing).
As a minor thing, it crashes after a couple of seconds of running at line
var result = new Bitmap(width, height, System.Drawing.Imaging.PixelFormat.Format24bppRgb);

with
System.ArgumentException: Parameter is not valid.

even though width and height seem appropriate, but it doesn't matter. I'm happy with the rgb24 byte frame anyway.
This is really a neat self-contained 1 file library, @secile !

Thank you for your reply.
I'm glad that using callback works fine.
1st way use sample grabber's GetCurrentBuffer function, and according to the page below, the function can be cause screen tearing problem.
https://docs.microsoft.com/en-us/windows/win32/directshow/isamplegrabber-getcurrentbuffer

Do not call this method while the filter graph is running. While the filter graph is running, the Sample Grabber filter overwrites the contents of the buffer whenever it receives a new sample.

So, using callbacks seems to be the right way. I will fix future release.
One thing worry about is you reported that app crashed after a couple of seconds of running.
On my PC, running for 3 hours did not cause any problems.
Is this problem still happening?

It only happens for 3840 x 2160 and 2592 x 1944. The version using the grabber's function doesn't crash... but aside from tearing it's also a bit more dragging.
With the callback, after the first exception is thrown all future bitmap allocation attempts throw the same exception. I'm planning to investigate at some point and come back if things become clear.


Misunderstood parameter of NCBI BLAST impacts the correctness of bioinformatics workflows

NCBI-BLAST is used internally by QIIME2 as I understand it. Does this recent publication affect any part of QIIME2?
https://academic.oup.com/bioinformatics/advance-article/doi/10.1093/bioinformatics/bty833/5106166

Thanks for asking @danwiththeplan .
The short answer is yes but no. Yes because we use BLAST+ in a few places, but no because those are all fairly thin BLAST wrappers where we intentionally expose BLAST functionality directly (including the max_target_seqs param). And because there are alternative methods available, as I will explain below.
The long answer. We have been familiar with that BLAST+ issue for a while now, and there has been a bit of discussion of that on the QIIME2 forum. This is used by QIIME 2 in two places, but only the first will actually impact users:

q2-feature-classifier has a classify-consensus-blast method, which uses BLAST+ for sequence alignment against a reference database, followed by a LCA consensus taxonomy method. That method will be impacted because it uses the max_target_seqs parameter explicitly  via the maxaccepts parameter. However, this parameter can be switched off (I believe, by setting to 0) or set to a very high value to mitigate this effect; increasing the perc_identity parameter value will also mitigate this effect. The default setting for max_target_seqs is 10, which is already reasonably high with amplicon reference databases, and performs quite well according to our benchmarks. We also have an open issue to make this behavior more transparent in q2-feature-classifier even if it is not in the BLAST+ docs! Finally, for any users who are concerned that this parameter is bad news for them but insist on using an alignment-based taxonomy classifier, they can instead use the classify-consensus-vsearch method, which uses vsearch for alignment but otherwise works the same and performs very similarly. The vsearch docs are much more explicit and as far as I know the maxaccepts parameter does work as everyone on the planet would intuitively expect this parameter to work!

q2-quality-control uses BLAST+ for alignment in the exclude-seqs method. However, that is a filter exclusion method used to remove (or retain) sequences that match a set of reference sequences within X percent identity, so it does not matter WHAT the sequence is aligning against, just as long as there is something similar enough in the database! So the max_target_seqs param is actually set to 1 for that method for that reason. The onus is on the user to make sure that they are using an appropriate reference database (e.g., that really does represent sequences they want to exclude/keep)

For both of these, the intention is to wrap BLAST as faithfully as possible for the alignment step — the reason being that most users are probably more familiar with BLAST than they are with QIIME. So we don't want to tinker with how these parameters behave, so that the method does just what users "want" (in quotes because obviously the BLAST+ max_target_seqs param does not really do what most users want/expect based on the BLAST+ docs description!).
I hope that makes sense! I will close this issue because this is not a QIIME-wide issue, but please feel free to reply even once it is closed. If you have ideas for improvement or additional concerns, please either open an issue in the appropriate GitHub repo (now that you know the plugins that use BLAST+), or take to the forum for more general discussion.
Thanks!

Great clarification thanks.