Design System: Input Variant

Feature Description
Now that the editor's getting redesigned (yay!) we're noticing some additions to the new designs that weren't sketched out as components in the design system that we originally based all of our work on. There are inputs in the editor that have a label (either text based or icon w/ aria-label) that are right aligned inside the input.
Alternatives Considered

Additional Context
Screenshots of panels in figma as of Feb 11, 2021

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Input variant should be added to design system
Should have storybook
Any relevant tests
Should have RTL version
Should be accessible
Should meet i18n requirements

Implementation Brief
This can probably be a variant on the existing input.

@barklund - any other variants I missed? I just went through figma and I'm not seeing anything centered? Screenshot/link if I missed them, please?

@barklund - any other variants I missed? I just went through figma and I'm not seeing anything centered? Screenshot/link if I missed them, please?

There's the search input in the element library. It's basically just an input with an icon prepended to the placeholder and nothing else special about it:

But as I discussed with @miina elsewhere, we'd ideally be able to create this where we need it by just passing the icon along with the text as placeholder and then style the input centered with a className (so we can use S-C to style it). I don't think it requires a special variant, rather just the ability to customize existing variants.

The search input has one more detail: when the input is active and has text in it, the icon is displayed on the left (see the main component design):

I'm guessing the same search input will be used in the dashboard as well?

Cool! I have the search separate since it behaves differently, PR here: https://github.com/google/web-stories-wp/pull/5844 it's just taken a lot of back and forth because I keep getting my attention stolen 😝
@samwhale is adding an input variant that allows icons: https://github.com/google/web-stories-wp/pull/6355
Thoughts welcome!

Added a new ticket to track extra variants that are needed:

Unit
Number
Allow empty

https://github.com/google/web-stories-wp/issues/6414


Added Support to detect CheckMFA cases in IAM Event Handler

This PR adds support for issue #2 , in which the IAM Event Handler is unable to detect the case of CheckMfa.
Reason for this issue to occur which have now been fixed:

In the event being passed to Lambda, instead of ARN in the userIdentity, userName is being passed.
The IAM Event Handler did not have a case to detect CheckMfa.

Added support for Google Groups, including clickable card to check activity.

@groovyBugify


[Quick Search] 可否加入谷歌学术快捷搜索指令

Extension
https://www.raycast.com/iwfan/quick-search
Description
可否加入谷歌学术快捷搜索指令？
进一步的，是否可以开放自定义设置，通过用户填写url+{queary}的方式实现
感谢作者！
Who will benefit from this feature?
No response
Anything else?
No response

Hi @FLIER001 Sorry for the slow response.
You can use the Quick Links feature to customize search URL.

@raycastbot close this issue


Define parameters to facilitate cloning a database to a nonprod env.

I'll need to make some changes to this PR.


How is this done with hundreds or thousands of devices when the example requires you to know/hard code the connection string to each device in advance?

In the SimulatedDevice project that is referenced in this example, we're told to manually hard code our connection string from the results of running "az iot hub device-identity show-connection-string --hub-name {YourIoTHubName} --device-id MyDotnetDevice --output table".
Even if it weren't considered poor practice, we can't hard code the connection string like in the example because we won't have just a single device and each device's connection string is different.  Without this connection string there is no way we can create the DeviceClient on the edge device and thus cannot run the ReceiveAsync() method to receive messages from the Cloud/IoTHub.
How does one get the device's connection string at runtime to create the DeviceClient?

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

ID: ba79df4d-c64b-7950-3ae9-6f28ea94409b
Version Independent ID: 7ad0c568-0df2-3be8-f221-0fb846bf575c
Content: Cloud-to-device messages with Azure IoT Hub (.NET)
Content Source: articles/iot-hub/iot-hub-csharp-csharp-c2d.md
Service: iot-hub
GitHub Login: @robinsh
Microsoft Alias: robinsh

@mikehutter , Thank you for your feedback. We will investigate and get back to you shortly.

@mikehutter Great question. Please see IotHubConnectionStringBuilder Class It Builds a connection string for the IoT Hub service based on the properties populated by the user. Do let us know if you have further questions.

We hope that addresses your question.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


.github: switch to codecov.io

coveralls doesn't work from GitHub actions. Its "github" service type
uses the GITHUB_TOKEN from the action, which only has read access when
invoked from a forked repository.
codecov gets this right: it validates that an uploaded coverage file
originated from a GitHub action run by asking GitHub, and then uses its
OAuth credentials (through the Marketplace App) to comment and set
status.
Also, coveralls requires a third-party package to convert go's coverage
report to a format it understands. codecov detects the format
server-side. It also handles go's coverage format better: it highlights
lines with "some coverage" in yellow (coveralls has no concept of this).

Seems this is working as expected. I'll request some reviews from people that are most affected by this change. Please wait for all of them to chime in before merging.

Sounds reasonable to me. We should also update the readme.

@teg

Sounds reasonable to me. We should also update the readme.

Thanks! Pushed an update to change the link.
@jrusz

Looks good, it's nice that I can see the report among the other check and get a link to it from there.

It seems to only do that after all CI runs have finished, even though I've told it not to in the config file. Not sure what's going on yet.

It seems to only do that after all CI runs have finished, even though I've told it not to in the config file. Not sure what's going on yet.

Ah now I see that. It would be better if it could show right away...

The idea looks good to me. I wanted to investigate further how the reports look like, but I found out I can't access the reports for individual files (_File/folder was not found on base commit. No compare to display. _) - will this change with further commits? It also seems that the reported coverage lowered, but I guess that's just a matter of how the coverage is calculated.

The idea looks good to me. I wanted to investigate further how the reports look like, but I found out I can't access the reports for individual files (File/folder was not found on base commit. No compare to display. ) - will this change with further commits?

You need to be logged in to see details. Not many are there yet, because there's nothing to compare to yet. Once we have results uploaded for master, the interface will be more useful.

It also seems that the reported coverage lowered, but I guess that's just a matter of how the coverage is calculated.

Yeah... for example, codecov deals with golang's cover output more correctly by not counting lines that have partial coverage. Not sure what's correct, but it is different.


"Missing return statement" error on abstract method

With NTI (new type inference) the compiler complains about abstract methods not having a return statement.
input0:125: WARNING - Missing return statement. Function expected to return number.
AbstractMassObject.prototype.getBottomBody = function() {};
                                             ^^^^^^^^^^^^^

0 error(s), 1 warning(s), 98.5% typed

Here is a simplified example which produces the error in https://closure-compiler-debugger.appspot.com with CHECK_TYPES_NEW_INFERENCE and CHECK_MISSING_RETURN options added.  Try clicking here to see this code in the online closure debugger.
/**
 * Base namespace for the Closure library.  Checks to see goog is already
 * defined in the current scope before assigning to prevent clobbering if
 * base.js is loaded more than once.
 *
 * @const
 */
var goog = goog || {};

/**
 * Inherit the prototype methods from one constructor into another.
 *
 * Usage:
 * <pre>
 * function ParentClass(a, b) { }
 * ParentClass.prototype.foo = function(a) { };
 *
 * function ChildClass(a, b, c) {
 *   ChildClass.base(this, 'constructor', a, b);
 * }
 * goog.inherits(ChildClass, ParentClass);
 *
 * var child = new ChildClass('a', 'b', 'see');
 * child.foo(); // This works.
 * </pre>
 *
 * @param {!Function} childCtor Child class.
 * @param {!Function} parentCtor Parent class.
 */
goog.inherits = function(childCtor, parentCtor) {
  /** @constructor */
  function tempCtor() {}
  tempCtor.prototype = parentCtor.prototype;
  childCtor.superClass_ = parentCtor.prototype;
  childCtor.prototype = new tempCtor();
  /** @override */
  childCtor.prototype.constructor = childCtor;

  /**
   * Calls superclass constructor/method.
   *
   * This function is only available if you use goog.inherits to
   * express inheritance relationships between classes.
   *
   * NOTE: This is a replacement for goog.base and for superClass_
   * property defined in childCtor.
   *
   * @param {!Object} me Should always be "this".
   * @param {string} methodName The method name to call. Calling
   *     superclass constructor can be done with the special string
   *     'constructor'.
   * @param {...*} var_args The arguments to pass to superclass
   *     method/constructor.
   * @return {*} The return value of the superclass method/constructor.
   */
  childCtor.base = function(me, methodName, var_args) {
    // Copying using loop to avoid deop due to passing arguments object to
    // function. This is faster in many JS engines as of late 2014.
    var args = new Array(arguments.length - 2);
    for (var i = 2; i < arguments.length; i++) {
      args[i - 2] = arguments[i];
    }
    return parentCtor.prototype[methodName].apply(me, args);
  };
};

/**
* @interface
*/
var SimObject = function() {};

/**
@return {string}
*/
SimObject.prototype.getName;

/**
* @param {string=} opt_name
* @constructor
* @struct
* @abstract
* @implements {SimObject}
*/
var AbstractSimObject = function(opt_name) {
  /**
  * @type {string}
  * @private
  */
  this.name_ = opt_name || 'SIM_OBJ';
};

/** @inheritDoc */
AbstractSimObject.prototype.getName = function() {
  return this.name_;
};

/**
* @interface
* @extends {SimObject}
*/
var MassObject = function() {};

/**
@return {number}
*/
MassObject.prototype.getBottomBody;

/**
* @param {string=} opt_name
* @constructor
* @abstract
* @struct
* @extends {AbstractSimObject}
* @implements {MassObject}
*/
var AbstractMassObject = function(opt_name) {
  AbstractSimObject.call(this, opt_name);
};
goog.inherits(AbstractMassObject, AbstractSimObject);

/** @inheritDoc @abstract */
AbstractMassObject.prototype.getBottomBody = function() {};

/**
* @param {string=} opt_name
* @constructor
* @final
* @struct
* @extends {AbstractMassObject}
*/
var PointMass = function(opt_name) {
  AbstractMassObject.call(this, opt_name);
  /**
  * @type {number}
  * @protected
  */
  this.height_ = 1;
};

/** @inheritDoc */
PointMass.prototype.getBottomBody = function() {
  return -this.height_/2;
};

var pm = new PointMass('mass1');
console.log(pm.getName()+' '+pm.getBottomBody());

Here is a simplified repro case.
The problem is with @inheritDoc. When NTI sees it, it ignores everything else in the jsdoc, so it ignores @abstract. If you remove the inheritDoc, then you get the expected warning.
I'll fix this in NTI, but in general it's an anti-pattern to have the type information of a method be computed as a combination of jsdocs; @override and @inheritDoc should be used without other jsdoc tags. For classes implementing interfaces, class methods inherit the signature of the interface methods without the need of any jsdoc annotations.

Removing @inheritDoc and leaving just @abstract fixes it for me.
I never knew that about class methods inheriting the interface signature automatically.  This means I can remove almost all the @inheritDoc tags in my code, which is nice, but I think it will be more clear to leave the @inheritDoc tags for human readers.
I have only one error in my code with NTI now, I'll submit that as a separate issue.

I never knew that about class methods inheriting the interface signature automatically.

They do, and similarly a subclass inherits type signatures from its superclass without the need of annotations.
Basically, the only benefit of @override/@inheritDoc is that if you use it on a method that doesn't override anything, you get a warning. This can catch typos such as a method named foobar1 in the superclass and mistakenly named foobar2 in the subclass.

FYI I've updated the wiki entries about @inheritDoc and @override with this info:

This tag is not required when a class extends a superclass or implements an interface - in those cases the documentation is automatically inherited. This tag is mainly useful to catch typos such as a method named foobar1 in the superclass and mistakenly named foobar2 in the subclass.

I also update the Using NTI wiki page with a note about the --jscomp_error=newCheckTypes option.


Sending div to capture returns view instead

The 0.5 alpha 1 version correctly captured the div or html element sent to html2canvas.  I saw that in 0.5 beta 4 there was a change so the scrolled window could be captured.  Unfortunately, that feature is on by default now with no option setting to return to capturing a complete div or element.  I'm sending an element id="contents" via jQuery to the function like so - html2canvas($('#contents'), {.  I have to scroll the window down a bit in order to activate the function that calls h2c.  When I do that and don't scroll back up, the resulting captured image is also scrolled down with the top of the contents element cut off.  This was not occurring in 0.5 alpha 1 and I've switched back to using it instead.  I reviewed the changed code in 0.5 beta 4 and it appears that options.type is never set.  There's a statement .... { type: "view"..., but that doesn't set options.type.  I attempted to modify the code accordingly, but the other part of the code that was changed still took the view rather than the div element.  In this if statement,
if (options.type === "view") {             canvas = crop(renderer.canvas, {width: renderer.canvas.width, height: renderer.canvas.height, top: 0, left: 0, x: 0, y: 0});         } else if (node === clonedWindow.document.body || node === clonedWindow.document.documentElement || options.canvas != null) {             canvas = renderer.canvas;         } else {             canvas = crop(renderer.canvas, {width:  options.width != null ? options.width : bounds.width, height: options.height != null ? options.height : bounds.height, top: bounds.top, left: bounds.left, x: 0, y: 0});         }
it appears that even if options.type is set to something other than "view", it will still return the view instead of the div contents as was the previous behavior...at least by the resulting rendered image that's returned.
Is there a way to ensure the html element I'm passing to h2c is rendered despite the window being scrolled like the behavior in 0.5 alpha 1?  This is for a web page on a desktop vs mobile device.

Is this still an issue with v1.0.0? If so, could you please share an example on jsfiddle.


Storysource addon - allow prism configuration

If you are reporting a bug or requesting support, start here:
Bug or support request summary
Have added Storysource and was expecting to be able to configure Prism syntax highlighting - eg. choose the theme, tweak the highlight style and so on. However I can't find anything in the docs about that - I can see the Prettier settings but nothing about Prism? That all seems hard-coded. This is an issue as the chosen theme is really hard to read and clashes badly with our own design.
Not sure if I'm just missing something, or if this is a feature request...
Steps to reproduce
n/a I think
Please specify which version of Storybook and optionally any affected addons that you're running

"@storybook/react": "^3.3.15",
"@storybook/addon-storysource": "^3.4.11",

Affected platforms
n/a I think
Where to start
n/a I think
Acceptance criteria

Ability to choose theme for Prism when using Storysource
Ability to configure/extend the styles applied to the Story tab, eg. the highlight style

BTW, @ndelangen and Co are working on overhaul UI changes, where this is addressed, but it will take some time to finish.

The UI overhaul will include theming for all syntax highlighting inside storybook.
https://github.com/storybooks/storybook/pull/4086

Thanks for the advice. If I get time I'll take a look at a PR (won't be right away, just to be honest :)).


Conversion issue

https://colab.research.google.com/drive/1oNxfvx5jOfcmk1Nx0qavjLN8KtWcLRn6?usp=sharing#scrollTo=b5Z1QFooGIW8
Hi
I am working on this project and I want to test it. The code works fine until the conversion starts. I receive multiple errors.
Can you please help with this and try to check the code ?
Thank you very much

@tersekmatija @HonzaCuhel do we have any working classification notebook?

Thank you very much for all your support and guidance

Hi @martin0496,
I'll look into it. Did it work for you last week?
Best,
Jan

@HonzaCuhel
I tried it for the first time today.
When I run the mo command it was not found that is why i installed openvino-dev using pip. After some research i found that the problem is related to versions. how can I solve it and make it run to achieve the final blob model ?
Thank you very much for the support

@HonzaCuhel
if we are installing a specific version of openvino to do the conversion, why we use the !mo command ?
because when I try to run it, the error is " mo command not found"
I will be very grateful if you can check the conversion part. THank you very much for all your support and guidance

Hey @martin0496 , can you give this notebook a try? Note you will have to restart the runtime after the first 2 packages get installed. Let me know if this works.

@HonzaCuhel @tersekmatija
Thank you very much. The conversion works fine and the final format is correct. Great Tutorial!

@martin0496 I am glad to hear that we were able to solve the issue!


Add CORS support

Closes #62.

@wetneb - thanks very much for this - I've re-opened #62 to remind me to reimplement this in the updated version of findthatcharity (see dev.findthatcharity.uk)
The reconciliation API docs are very useful - I'm going to check my implementation against them.


osbuild: new stage 'cacert'

This pull request adds a new stage called 'cacert' to the osbuild package. It also includes file changes to support the CACustomization feature, which allows users to specify a list of certificates for the CA (Certificate Authority). The changes include updates to the Customizations struct, the osCustomizations function, and the OSCustomizations struct. Additionally, a new function called parseCerts is added to parse the certificate strings. The changes also include updates to the serialize and prependKernelCmdlineStage functions in the OS struct. Finally, a new file called ca_stage.go is added to the osbuild package, which contains the implementation of the NewCAStageStage function.
Needs: https://github.com/osbuild/osbuild/pull/1854

Sure, amended all remarks. If you don’t mind, I am keeping one commit for easier work from my side, multiple commits rebasing is a pain to work with this isn’t a big PR by any means. I will split it after the code is ready.

I have extracted the checking code + test into separate package cert and implemented an explicit check method. The error is now explicit, no warnings.

Amended the recommended changes, fixed tests.
Let me know where and how to add a test for this.
REMINDER: For myself - the commit should be split as requested.

Rebased, hopefully it passes now.

Any other comments? I would love to get this in.

I think the MTLS change kicked in and now breaking tests I need to fix this prior this PR:
internal/cloudapi/v2/server.go:231:55: cannot convert source (variable of type ostree.SourceSpec) to type worker.OSTreeResolveSpec

For the record, tests are broken due to other change that needs to be merged first.

Rebased, images library is now updated and it works fine.

I think those failures are not relevant?!?

I don't know what the failures mean TBH :(

The failures are because there's a file source reference in a stage without it appearing in the manifest's sources.
Generating a manifest from this branch and inspecting it, I see the same:
› go run ./cmd/gen-manifests --distros rhel-9.5 --arches x86_64 --types qcow2 --config ./test/configs/all-customizations.json --output ./manifests --metadata=false
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/centos-10.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/centos-9.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/fedora-39.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/fedora-40.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/fedora-41.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-10.0.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-7.9.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.10.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.4.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.5.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.6.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.7.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.8.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-8.9.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.0.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.1.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.2.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.3.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.4.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.5.json
INFO[0000] Loaded repository configuration file: /home/achilleas/projects/osbuild/images/test/data/repositories/rhel-9.6.json
'-config' was provided, thus ignoring '-config-map' option
Collecting jobs
Collected 1 jobs
Initialised 16 workers
Submitting 1 jobs... done
Starting job rhel_9.5-x86_64-qcow2-all_customizations.json
WARN[0000] Failed to load consumer certs: no consumer key found
No match for group package "iwl5150-firmware"
No match for group package "iwl6050-firmware"
No match for group package "firewalld"
No match for group package "iwl7260-firmware"
No match for group package "dracut-config-rescue"
No match for group package "iwl105-firmware"
No match for group package "iwl2000-firmware"
No match for group package "iwl100-firmware"
No match for group package "iwl6000g2a-firmware"
No match for group package "iwl1000-firmware"
No match for group package "iwl3160-firmware"
No match for group package "iwl135-firmware"
No match for group package "iwl2030-firmware"
No match for group package "iwl5000-firmware"
Finished job rhel_9.5-x86_64-qcow2-all_customizations.json
 == Jobs == Queue:    0  Active:    0  Total:    1
RPM metadata cache kept in /tmp/rpmmd

› osbuild --inspect ./manifests/rhel_9.5-x86_64-qcow2-all_customizations.json
Traceback (most recent call last):
  File "/usr/bin/osbuild", line 8, in <module>
    sys.exit(osbuild_cli())
             ^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/main_cli.py", line 136, in osbuild_cli
    manifest = fmt.load(desc, index)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/formats/v2.py", line 379, in load
    load_pipeline(desc, index, manifest, source_refs)
  File "/usr/lib/python3.12/site-packages/osbuild/formats/v2.py", line 353, in load_pipeline
    load_stage(desc, index, pl, manifest, source_refs)
  File "/usr/lib/python3.12/site-packages/osbuild/formats/v2.py", line 322, in load_stage
    load_input(name, desc, index, stage, manifest, source_refs)
  File "/usr/lib/python3.12/site-packages/osbuild/formats/v2.py", line 277, in load_input
    raise ValueError(f"Unknown source reference(s) {unknown_refs}")
ValueError: Unknown source reference(s) {'sha256:4c4e8c734e4ee3a117ca8f9363ba7b706d02bfc8f297c00b02ce02babddef51c'}

For the record, the missing file is the CA file that needs to be copied:
{
          "type": "org.osbuild.copy",
          "inputs": {
            "file-4c4e8c734e4ee3a117ca8f9363ba7b706d02bfc8f297c00b02ce02babddef51c": {
              "type": "org.osbuild.files",
              "origin": "org.osbuild.source",
              "references": [
                {
                  "id": "sha256:4c4e8c734e4ee3a117ca8f9363ba7b706d02bfc8f297c00b02ce02babddef51c"
                }
              ]
            }
          },
          "options": {
            "paths": [
              {
                "from": "input://file-4c4e8c734e4ee3a117ca8f9363ba7b706d02bfc8f297c00b02ce02babddef51c/sha256:4c4e8c734e4ee3a117ca8f9363ba7b706d02bfc8f297c00b02ce02babddef51c",
                "to": "tree:///etc/pki/ca-trust/source/anchors/27894af897dd2423607045716438a725f28a6d0b.pem",
                "remove_destination": true
              }
            ]
          }
        },

It looks like it works fine:
go run ./cmd/gen-manifests --distros rhel-9.5 --arches x86_64 --types qcow2 --config ./test/configs/all-customizations.json --output ./manifests --metadata=false

sudo osbuild ./manifests/rhel_9.5-x86_64-qcow2-all_customizations.json --export build --export os --export image --output-directory /tmp/osbuild-test --store /tmp/osbuild-test

lzap@dev:/tmp/osbuild-test/os/etc/pki/ca-trust/source/anchors$ cat 27894af897dd2423607045716438a725f28a6d0b.pem
-----BEGIN CERTIFICATE-----
MIIDszCCApugAwIBAgIUJ4lK+JfdJCNgcEVxZDinJfKKbQswDQYJKoZIhvcNAQEL
BQAwaDELMAkGA1UEBhMCVVMxFzAVBgNVBAgMDk5vcnRoIENhcm9saW5hMRAwDgYD
VQQHDAdSYWxlaWdoMRAwDgYDVQQKDAdSZWQgSGF0MRwwGgYDVQQDDBNUZXN0IENB
IGZvciBvc2J1aWxkMCAXDTI0MDkwMzEzMjkyMFoYDzIyOTgwNjE4MTMyOTIwWjBo
MQswCQYDVQQGEwJVUzEXMBUGA1UECAwOTm9ydGggQ2Fyb2xpbmExEDAOBgNVBAcM
B1JhbGVpZ2gxEDAOBgNVBAoMB1JlZCBIYXQxHDAaBgNVBAMME1Rlc3QgQ0EgZm9y
IG9zYnVpbGQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDeA7OcWTrV
gstoBsUaeJKm8nelg7Lc0WNXH6yOTLsr4td4yHs0YOvFGwgSf+ffV3RAG1mgqnMG
MgkD2+z+7QhHbHHs3y0d0zfhA2bg0KVvfCWk7fNRPHY0UOePpXk245Bfw3D0VTpl
F7nePk1I7ZY09snPWUeb2rjKXzYjKjzM0h27+ykV8I8+FbdyPk/pR8whyDqtHLUa
XfFy2TFloDSYMkHKVd38BnL0bj91x5F+KsZkN4HzfbYwxLbCQfOSgy7q6TWce9kq
Lo6tya9vuvpWFm1dye7L+BodAQAq/dI/JMeCfyTb0eFb+tyzfr5aVIoqqDN+p9ft
cw4OefpHbhtNAgMBAAGjUzBRMB0GA1UdDgQWBBRV2A9YmusekPzu5Yf08cV0oPL1
wjAfBgNVHSMEGDAWgBRV2A9YmusekPzu5Yf08cV0oPL1wjAPBgNVHRMBAf8EBTAD
AQH/MA0GCSqGSIb3DQEBCwUAA4IBAQCgQZ2Xfj+NxaKBZgn2KNxS0MTbhzHRz6Rn
qJs+h8OUz2Crmaf6N+RHlmDRZXUrDjSHpxVT2LxFy7ofRrLYIezFDUYfb920VkkV
SVcxh1YDFROJalfMoE6wdyR/LnK4MJZS9fUpeCJJc/A0J+9FK9CwcyUrHgJ8XbJh
MKYyQ+cf6O7wzutuBpMyRqSKS+hVM7BQTmSFvv1eAJlo6klGAmmKiYmAEvcQadH1
djrujsA3Cn5vX2L+0yuiLB5/zoxqx5cEy97TuKUYB8OqMMujAXNzF4L3HJDUNba2
AhEkFozMXwYX73TGbGZ0mawPS5D3v3tYTEmJFf6SnVCmUW1fs57g
-----END CERTIFICATE-----

Rebased.

Forgot to run prepare-source.sh fixed, rebased.


Configurations for awesome-list compatibility

There are several requirements for being added to awesome-list , some of them require changing repo settings while some are file changes. I'll open the necessary PRs for file changes and post relevant ones under this issue. You can also check the requirements here
At the end of this milestone, we can apply to the awesome-list and present this repo there.
Here is the list:

[ ] Rename this repo to awesome-cosmwasm. Repository renaming
[ ] Add "awesome-list" and "awesome" as GitHub topics. Adding GitHub topics
[ ] Create a GitHub action to check every PR for awesome-lint automatically. Instructions
[ ] Rename master branch to main.

@uint

I changed the list above to a TODO list. Hope you don't mind!


Issues with get / findfirst methods

Hi,
I'm having troubles with using get or findfirst methods.
When i try to input a "if get... then" in my extension (OnRunOnAfterInvoiceRounding in Purchase header), the program won't ignore the error and will display a "this record already exists" error message through the ErrorMessageHandler.ShowErrors(); in SendToPosting method in Puchase Header.
I would have joined some screen shots but i seem to have issues with the web site.
I just don't understand why the management of get or find statements seems to differ from dynamics nav, because it's not the first time i'm having this kind of problem on bc. Why do get or findfirst statements display "this record already exists" errors ?
Can't we use "if get" statements anymore ?
Thanks for your help

Hi @VMotin,
Since, it indeed seems to not be an AppExtension issue and we would like to start investigating it, could you please follow our bug creation pattern: https://github.com/microsoft/AL/blob/master/ISSUE_TEMPLATE so we can be most useful. Thank you!

Yeah, at least the compiler and server versions, and the (minimised) event subscriber code that causes the problem.

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.


Pip widget issue

Yeah now that's working fine. But still, the pip widget doesn't make returns the pip child instead it returns same widget in pip. Can you please check and the simple pip works fine on this case. this plugin doesn't work as expected.

Hey, can you please provide a minimal reproducible sample?

Closing this as a duplicate of #1


Fix compiler warning and signedness issue

🦟 Bug fix
Fixes #
Summary
This commit fixes a compiler warning I was getting with regard to signed and unsigned types. On line 794 of Discovery.hh we use the recvfrom but we use an unsigned int to check if the error is correct or not. By default recvfrom returns an ssize_t not a uint16_t. It seems a fix for this has landed in garden but has not been backported to citadel or fortress.

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

Windows doesn't like this because it doesn't have the ssize_t type:
C:\J\workspace\ign_transport-pr-win\ws\gz-transport\include\gz/transport/Discovery.hh(791,9): error C2065: 'ssize_t': undeclared identifier (compiling source file C:\J\workspace\ign_transport-pr-win\ws\gz-transport\src\NodeShared.cc) [C:\J\workspace\ign_transport-pr-win\ws\build\ignition-transport8\src\ignition-transport8.vcxproj]

I've switched to int64_t as a compromise. See a9f5d82


Early stopping when validation is disabled

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
Fixes #1201 (right now it's just just a check that the proposed fix by @Dunrar passes the unit tests).
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@jeremyjordan @neggert I think you guys worked on callbacks and early stopping. Is it ok to do this change here? Basically what we want (according to @williamFalcon) is that early stopping will work on the training metrics if no validation loop is defined (or it is disabled).
If you agree with this change, then I will add a unit test for the case I described.

@awaelchli yeah i think that looks fine!

Thanks for looking at it already. I added a test and properly documented the behaviour. Could you review it again?


Travis integration. Closes #54

Travis integration closes #54
Add CI integration.
Use tox for running tests within different environments
Due to bug in tox there is a workaround with passing envvar to tests command.

Review request: @webknjaz

@anxolerd Plz sync updated config/test/app.yml from original branch

Moved tox dependency from dev requirements to test requirements in 6e2b48b
Updated testing config from api-for-admin branch in 2a985ea


After CDK Publish, Auto-Generate PR to Bump CDK in Connector Builder Repo

Example PR here:

https://github.com/airbytehq/airbyte-platform-internal/pull/14584

Created from code here:
https://github.com/airbytehq/airbyte/pull/48470/files#diff-3249d7445228172f9b36422eb8685d1b2def3c8953331f8d393756c64d9be7e9L285-L388
  update-connector-builder:
    needs:
      - bump-version
      - bump-manifest-source
    runs-on: ubuntu-latest
    steps:
      - uses: actions/setup-python@v4
        with:
          python-version: "3.10"
      - name: Checkout Airbyte Platform Internal
        uses: actions/checkout@v3
        with:
          repository: airbytehq/airbyte-platform-internal
          token: ${{ secrets.GH_PAT_MAINTENANCE_OCTAVIA }}
      - name: Update CDK version
        run: |
          PREVIOUS_VERSION=$(cat oss/airbyte-connector-builder-resources/CDK_VERSION)
          sed -i "s/${PREVIOUS_VERSION}/${{needs.bump-version.outputs.new_cdk_version}}/g" oss/airbyte-connector-builder-server/Dockerfile
          sed -i "s/${PREVIOUS_VERSION}/${{needs.bump-version.outputs.new_cdk_version}}/g" cloud/airbyte-connector-builder-server-wrapped/Dockerfile
          sed -i "s/airbyte-cdk==${PREVIOUS_VERSION}/airbyte-cdk==${{needs.bump-version.outputs.new_cdk_version}}/g" oss/airbyte-connector-builder-server/requirements.in
          echo ${{needs.bump-version.outputs.new_cdk_version}} > oss/airbyte-connector-builder-resources/CDK_VERSION
          cd oss/airbyte-connector-builder-server
          pip install pip-tools
          pip-compile --upgrade
      - name: Create Pull Request
        id: create-pull-request
        uses: peter-evans/create-pull-request@v6
        with:
          token: ${{ secrets.GH_PAT_MAINTENANCE_OCTAVIA }}
          commit-message: "chore: update CDK version following release"
          title: "chore: update CDK version following release"
          body: This is an automatically generated PR triggered by a CDK release
          branch: automatic-cdk-release
          base: master
          delete-branch: true
      - name: Post success to Slack channel dev-connectors-extensibility
        uses<EMAIL_ADDRESS>        continue-on-error: true
        with:
          channel-id: C04J1M66D8B
          payload: |
            {
                "text": "A new version of Python CDK has been released!",
                "blocks": [
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": "A new version of Python CDK has been released with <https://github.com/airbytehq/airbyte/blob/master/airbyte-cdk/python/CHANGELOG.md|changelog>: ${{ github.event.inputs.changelog-message }}\n\n"
                        }
                    },
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": "A PR has also been created for the <${{ steps.create-pull-request.outputs.pull-request-url }}|Connector Builder>\n"
                        }
                    },
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": "See details on <https://github.com/${{github.repository}}/actions/runs/${{github.run_id}}|GitHub>\n"
                        }
                    }
                ]
            }
        env:
          SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN_AIRBYTE_TEAM }}
      - name: Post failure to Slack channel dev-connectors-extensibility
        if: ${{ failure() }}
        uses<EMAIL_ADDRESS>        continue-on-error: true
        with:
          channel-id: C04J1M66D8B
          payload: |
            {
                "text": ":warning: A new version of Python CDK has been released but Connector Builder hasn't been automatically updated",
                "blocks": [
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": "A new version of Python CDK has been released with <https://github.com/airbytehq/airbyte/blob/master/airbyte-cdk/python/CHANGELOG.md|changelog>: ${{ github.event.inputs.changelog-message }}\n\n"
                        }
                    },
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": ":warning: Could not automatically create a PR for Connector Builder>\n"
                        }
                    },
                    {
                        "type": "section",
                        "text": {
                            "type": "mrkdwn",
                            "text": "See details on <https://github.com/${{github.repository}}/actions/runs/${{github.run_id}}|GitHub>\n"
                        }
                    }
                ]
            }
        env:
          SLACK_BOT_TOKEN: ${{ secrets.SLACK_BOT_TOKEN_AIRBYTE_TEAM }}

There are 2 separate things at play here

the version of the CDK used in the builder: this is done via the autogenerated PR and merged manually
the SDM version used by running syncs: we auto-update the version so that it mirrors more of a cloud-like experience of getting new updates automatically. This is handled by the DeclarativeSourcesUpdater which keeps a list in the db of the latest version for each major version.

Closing as complete. Was shipped a little while ago...


REQ: Github actions with artifact uploads

Hello, can you enable github actions for commits and pull requests with artifact uploading?
this is free for all public repos (this is one of them) and has two benefits, it allows users to download the latest builds of the latest commits right from github. and allows automated building (and testing) of any pull requests that might get made.
thanks in advance for any consideration towards this.

Hello, thanks for your suggestions. However Daijishō is currently closed source.


Added wiring diagrams, datasheet and comments on code

Added Datasheet of PZEM004T
Added Wiring diagram
Added comments for RX, TX on Arduino

Hey, I am maintaining the PZEM004T-v30 library https://github.com/mandulaj/PZEM-004T-v30 which is very similar in terms of the hardware. I have many users being confused about the wiring. Would you mind adding your drawing also there so that the confusion can be resolved for once. Thank you

Hi,
I have pushed the diagram many years back on my branch and a pr.
Which I got 0 reply to merge to master. That would help wiring diagram for
resolve Confusion
Thnks
On Sat, Jan 15, 2022, 01:01 Jakub Mandula @.***> wrote:

Hey, I am maintaining the PZEM004T-v30 library
https://github.com/mandulaj/PZEM-004T-v30 which is very similar in terms
of the hardware. I have many users being confused about the wiring. Would
you mind adding your drawing also there so that the confusion can be
resolved for once. Thank you
—
Reply to this email directly, view it on GitHub
https://github.com/olehs/PZEM004T/pull/18#issuecomment-1013550711, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMDKQ4VHQVTGGMZ2ODNN4TUWC2MLANCNFSM4DM342KA
.
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.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yeah so would you like to add it to my library instead. I am not going not going to ignore the pull request 😉

Hi. I'm sorry, I completely forgot about this request.
The reason I didn't accept it at the first place was that it not only adds datasheets as stated in the title, but also modifies example's workflow.
These changes should be split to different PR's.
Also I doubt I can accept example's changes without further discussion. With these changes, when AC power is off, there will be last positive reading in the freezed log. This can be confusing.

Hello @olehs, @mandulaj,
all lib devs in one place, huh :) Just wanted you to suggest adding a links to docs and pages in different repo's. Would be much easier for users to search for connection diagrams and proper libs. I.e. Oleh has a very nice WiKi pages describing hardware setup with esp8266. I've made a 3-phase setup diagram not so long ago. Also I found a really good repo with PZEM's reverse-engineered schematics.
This is all scattered pieces of information, would be nice to have references one to another.
Cheers!

When I originally wrote my version of the library this was my goal. Just haven't had the time to sit down and collect all the pieces. If you have time and motivation then you are welcome to take the initiative 😇

Time is the most precious resource for all of us :) OK, I may come up with a list of "useful links" next time.


[hamilton] add low level command to rotate iSWAP

just checking: should this be under unsafe?

just checking: should this be under unsafe?

i put it under unsafe because if you rotate it can hit things, especially if you are near the edge of the deck

by this logic, essentially all iswap commands should be unsafe. where do you draw the line here?

by this logic, essentially all iswap commands should be unsafe. where do you draw the line here?

hmm, my impression was that normal iswap commands where careful about not moving off deck? If not happy to move into star. Also makes me wonder if the hotel commands deserve to be in unsafe as well? I'm not sure where the line should be either 😄

we use the move_plate command primarily for moving plates into the deck-adjacent plate reader.
did you damage the robot developing the hotel commands?

did you damage the robot developing the hotel commands?

No, but I could have if I wasn't paying close attention.
In general, I don't see a strong separating line on the danger of various commands. My only opinion is that if we are going to make a separation, then using an unsafe attribute is better (since it is more explicit) than a flag.

No, but I could have if I wasn't paying close attention.

I'd say that rotating the iSWAP has behavior is exactly as you expect, so it's not necessarily unsafe. When calling it, there are no unexpected side effects. Can that be the dividing line? (still largely subjective - this can be a heuristic)

My only opinion is that if we are going to make a separation, then using an unsafe attribute is better (since it is more explicit) than a flag.

You convinced me of this. Current discussion is just around what should go in there.

No, but I could have if I wasn't paying close attention.

I'd say that rotating the iSWAP behavior is exactly as you expect, so it's not necessarily unsafe. When calling it, there are no unexpected side effects. Can that be the dividing line? (still largely subjective - this can be a heuristic)

My only opinion is that if we are going to make a separation, then using an unsafe attribute is better (since it is more explicit) than a flag.

You convinced me of this. Current discussion is just around what should go in there.

cool, will move this to the main STAR!

great change, setting the structure for further documentation of Hamilton STARs that will encourage more people to hack on it


Divergent behavior from bevy_input when holding mouse button over egui window

Which feature is frustrating to use or confusing?
I don't know whether this is intentional or a bug, but I encountered the following scenario:

I have an action Foo that is bound to MouseInput::Right
I draw windows on top of my game using bevy_editor_pls
For my PrimaryWindow, I set cursor.grab_mode = CursorGrabMode::Locked as well as cursor.visible = false
I do stuff on ActionState::pressed(Foo)
While holding the right mouse button, I "move" my mouse over the bevy_editor_pls window. I put move in quotation marks since the cursor is locked and invisible, so I don't actually see anything moving.

LWIM treats this as if I released the right mouse button, reporting false on ActionState::pressed(Foo) and true on ActionState::just_released(Foo). Meanwhile, Input<MouseButton>::pressed(MouseButton::Right) stays true during the whole process.
Expectation
Either for LWIM and bevy_input to behave the same way or the divergent behavior to be documented for InputKind::Mouse and/or ActionState::pressed

If you have the egui feature of leafwing-input-manager enabled, this might be the code causing this:
https://github.com/Leafwing-Studios/leafwing-input-manager/blob/814425909cb48c6db418da6ef4fe8b47a029e501/src/systems.rs#L98-L104
Not sure the best solution, perhaps add a check for grab mode in that code so it doesn't do that if the cursor is locked or something.


Update Godeps for Shopify/sarama

sarama merged a pull request to address the ../../Shopify/sarama/snappy.go:7:2: cannot find package "github.com/golang/snappy/snappy" issue that has cropped up again.

Thanks. I'll need to take some time to review this one carefully, however. Shopify has a habit of massively changing the interface for sarama on a whim. It caused serious problems when I updated it last time.

Let me know if there is anything I can do to help out.

Thanks very much for the contribution!


CocoaPods could not find compatible versions for pod "GTMSessionFetcher/Core"

[!] CocoaPods could not find compatible versions for pod "GTMSessionFetcher/Core":
  In Podfile:
    firebase_auth (from `.symlinks/plugins/firebase_auth/ios`) was resolved to 4.2.6, which depends on
      Firebase/Auth (= 10.3.0) was resolved to 10.3.0, which depends on
        FirebaseAuth (~> 10.3.0) was resolved to 10.3.0, which depends on
          GTMSessionFetcher/Core (< 4.0, >= 2.1)

    mobile_scanner (from `.symlinks/plugins/mobile_scanner/ios`) was resolved to 3.0.0, which depends on
      GoogleMLKit/BarcodeScanning (~> 3.2.0) was resolved to 3.2.0, which depends on
        MLKitBarcodeScanning (~> 2.2.0) was resolved to 2.2.0, which depends on
          MLKitCommon (~> 8.0) was resolved to 8.0.0, which depends on
            GTMSessionFetcher/Core (~> 1.1)

GTMSessionFetcher/Core is not compatible with firebase_auth.

Create MLKitVision.podspec.json in ios folder taking file from example
Create MLKitCommon.podspec.json in ios folder taking file from example
Inside your Podfile you have to search for target 'Runner' and inside it you have to add the following lines:

      pod 'MLKitVision', :podspec => 'MLKitVision.podspec.json'
      pod 'MLKitCommon', :podspec => 'MLKitCommon.podspec.json'

Run pod install
build the app


how to inject compiletime objects using vscode without WurstWE?

thx

add
-runcompiletimefunctions
-injectobjects

to your wurst_run.args file next to your map.

@Frotty is this feature documented?

it will be in the new manual

There will be a new manual?
On Jun 28, 2017 13:15, "Frotty"<EMAIL_ADDRESS>wrote:

it will be in the new manual
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/peq/wurst4vscode/issues/22#issuecomment-311630104,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBakgAxWhUYk9QVNhVeC3pwq_gZQ2vPks5sIjW_gaJpZM4OG7fp
.

I dont know why but when I run map with VSCode, it injects nothing and ignores compiletime funcs.
wurst_run.args contains
-runcompiletimefunctions
-injectobjects

and is in the same folder as the map.

When I use Sharpcraft World editor and save map with:

it adds import and does compiletime funcs. And I dont undesrtand why I can do it with Sharpcraft WE but cant do it with VSCode


envoy-image: updated Envoy image with a fix for auth tracing and lates upstream code

Description
This PR updates Ambassador with a new Envoy image that contains a bug fix for ext-authz tracing as well as the latest Envoy upstream code.
Related Issues
https://github.com/datawire/ambassador/issues/1414
Testing
I performed a manual test for the bug fix. HTTP auth tracing works exactly like the gRPC auth which already has tracing built into the client.
Todos

[ ] KAT test

W00t. 🙂


About mjrl_env

Is the mjrl_envs package integrated into the mjrl package?I can't find it in your link

mjrl_envs is in the "touch" or "v0.1real" branch in robohive


Unable to verify signature value

Hi,
We are working on UPI integration where we need to sign xml message before API call. We are using this library to sign xml. The signature is verified at our level but not getting verified at API level. They are verifying signature using java code. Can anyone help us. Below is the java code shared by API development team :
package olivecrypto.upi.xml;

import java.io.FileInputStream;
import java.io.StringReader;
import java.security.PublicKey;
import java.security.cert.Certificate;
import java.security.cert.CertificateFactory;

import javax.xml.crypto.dsig.XMLSignature;
import javax.xml.crypto.dsig.XMLSignatureFactory;
import javax.xml.crypto.dsig.dom.DOMValidateContext;
import javax.xml.parsers.DocumentBuilderFactory;

import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import org.xml.sax.InputSource;

public class VerifySignature {
    PublicKey publicKey;

    public VerifySignature(String cer) throws Exception {
        CertificateFactory certFact = CertificateFactory.getInstance("X509");
        Certificate cert = certFact.generateCertificate(new FileInputStream(cer));
        publicKey = cert.getPublicKey();
    }
    public boolean isXmlDigitalSignatureValid(String signedXml) throws Exception {
        boolean validFlag = false;
        System.out.println("signedXml" + signedXml);
        DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
        dbf.setNamespaceAware(true);
        Document doc = dbf.newDocumentBuilder().parse(new InputSource(new StringReader(signedXml)));
        System.out.println("doc" + doc);
        NodeList nl = doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
        if (nl.getLength() == 0) {
            throw new Exception("No XML Digital Signature Found, document is discarded");
        }
        DOMValidateContext valContext = new DOMValidateContext(publicKey, nl.item(0));
        XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM");
        XMLSignature signature = fac.unmarshalXMLSignature(valContext);
        validFlag = signature.validate(valContext);
        return validFlag;
    }
}

Hi @kumarakmuz
I was able to successfully validate a signed (by this PHP package) XML file using Java.
Algo: SHA512

Make sure to use the correct certificate file. It works with a PEM for the public key but not with a P12 file in Java.
Also use SHA512 and not SHA1 to sign the XML files, because SHA1 is "forbidden" for security reason in the Java ecosystem.
Can you try that?

We are using sh256 is it ok na ?

We are using sha256 is it ok

Yes, this is OK.

Our PHP code

Note, that this PHP package must be used with the composer autoloader in order to work correctly.
Try the following example:
<?php

require_once __DIR__ . '/vendor/autoload.php';

use Selective\XmlDSig\Algorithm;
use Selective\XmlDSig\CryptoSigner;
use Selective\XmlDSig\PrivateKeyStore;
use Selective\XmlDSig\XmlSigner;

// The xml contents you want to sign
$xmlContents = '<?xml version="1.0"?><root></root>';

$privateKeyStore = new PrivateKeyStore();

$algo = Algorithm::METHOD_SHA256;

$privateKeyFile = 'path/to/file.p12';
$password = 'secret';

$privateKeyStore->loadFromPkcs12(file_get_contents($privateKeyFile), $password);

$algorithm = new Algorithm($algo, $algo);
$cryptoSigner = new CryptoSigner($privateKeyStore, $algorithm);
$xmlSigner = new XmlSigner($cryptoSigner);

$signedXml = $xmlSigner->signXml($xmlContents);

file_put_contents('signed.xml', $signedXml);

Then give that signed XML file your API development team for validation.

API team using our .cer file to verify signature.

Without code example it's hard to help here.
In Java I have successfully used a PEM file for the validation with the the public key. Maybe try this.

Can you connect with us through google meet ?

You have installed an older version 2.4. The latest version of this package is 3.1.
Check your composer.json file and upgrade to ^3 or reinstall the new package version with
composer require selective/xmldsig "^3"

ok and other things will remain same ?

Unfortunately, I do not offer free Java code consulting, but I can send you my working Java code for a small fee if you are interested.

Unfortunately, I do not offer free Java code consulting, but I can send you my working Java code for a small fee if you are interested.

ok, No issue we can pay. Kindly plan to connect

@kumarakmuz You can contact me here: https://twitter.com/dopitz

Kindly share your skype id so that we can connect

Ok, here you can find my Skye ID: https://odan.github.io/about.html#contact


Softened spring dependencies

Fewer dependencies, but still requires spring auto configure so that the
endpoint bean can be disabled by default.
Uses compileOnly to require application using this module to supply concrete
versions.
@cfieber, @ttomsu
This is intended to complement the PR I'm sending to kork. It works for me, but is it correct?

@cfieber can you have a look so I can ensure this gets into Brian's release?

Closing in favor of #340.


Datamanager feature: update(key, object, forceCreate)

Please do not update the README or Change Log, we will do this when we merge your PR.
This PR:
Adds a new feature
Describe the changes below:
This adds an update method that will take an object and update the existing object in the datamanager with the fields in the object passed in.
Example:
this.data.set('test', {x:10, y:20});
this.data.update('test', {x:20});

var newTest = this.data.get('test');
//newTest.x = 20, newTest.y = 20

I for one would like this to be added 💃

I think this needs eslint --fix.

eslint issues aside, you can already do this:
this.data.set('test', {x:10, y:20});

this.data.values.test.x = 20;

var newTest = this.data.get('test');
//newTest.x = 20, newTest.y = 20

datamanager has frozen feature, you can't do this by a update method.

Thanks for this PR, however, I'm afraid I'm going to close it off, as it doesn't pass the eslint check and you can already do this via the values property of the Data Manager.


Update woodcutting leprechaun event to use new notification system

I wanted to customize this event's notification, but I couldn't without the change in this PR. 😄

That is odd, it must have got missed when I converted them all earlier.


Just for to understand!

Hi,
Is it possible to offer newcomers like me a very basic explanation of how to use your code?
I would like to have the description of each complete passage, how and where to add the code.
es: Where to insert the unzipped folder? - How to retrieve .js and .css files? - What to write on the html page?
I'm sorry, I tried to enter the codes that appear in the Tabs, but there was no result.
Thank you!

Hello @giusbome,
I created a basic project using granim here.
You can download it by clicking on the download icon in the header to see how it works.
(note: the 'package.json' file is useless here).


Create view to test out Gomoku AIs

View hierarchy:
--- Title ---
Selection of AI
Game settings
Start Game button
The game
Debug info

Added with #6d55442


code indentation corrupted!!

Thanks for looking over my code. I've made a major update, and in addition to better performance, the indentation is fixed now. Let me know if you see other issues.


How to Review a Pull Request (Linter Configuration)

(Credit: @gunnarmorling)
In an effort to improve slash commands, I've come across this: https://github.com/bwmarrin/discordgo/pull/856. There are 11 reviewers (@eaglemoor @CarsonHoffman @MrFlynn @iopred @chanbakjsd2 + more)... Yet when you try to implement slash commands, an example that is prone to security issues (and other code smells) is provided. This is because every maintainer was so focused on naming variables (important), and small stylistic changes (less important) that they forgot to ask questions about the actual code. Don't take this personal, @Strum355.
There are 40 pull requests, but most of them look like this: https://github.com/bwmarrin/discordgo/pull/1005. 7 months later... Nothing. It's understandable for you to miss pull requests. It's understandable to not check the repository every day. You aren't obligated to maintain the repository. However, when simple things like this go unmerged, it hints at inefficiency in your review approach. This post identifies the issues that cause this inefficiency and provides a solution to change this.
Creating an amazing environment for Go programmers in the Discord Go scene results in more resources and people that provide benefits to this library. It's in your best interest to make fixes and features easy to implement. In return, you receive better features, more performance (https://github.com/bwmarrin/discordgo/pull/959), and more maintainability.
@LaevusDexter, grab the popcorn.
What's the first issue?
Who here actually uses slash commands? If you are, please let me know because I look forward to crashing your bot. However, I don't actually believe I'll be crashing any bots because I don't believe you use slash commands. The main point being that there is no way anyone who uses a slash command bot is fine with using option indexes. Even if you use a map in your private codebase, it doesn't make sense to encourage what's already been explained here: https://github.com/bwmarrin/discordgo/issues/1126.
What's the next issue?
There are over 200 occurrences of naked returns and whatever is provided in the pull request below this post: I wonder how many issues can be solved by handling variables correctly. That's not a question... There is a 3000 line file with who knows what in it. The repository is full of unchecked errors, ineffectual assignments, and loads of unnecessary err =,\n if err statements. There are over 40 TODO statements and more — incorrectly labeled — deprecated ones...  I'm not even making this statement as an insult. It's really the worst. Luckily, we can fix this.
Solution 1
The first solution starts with standardizing the codebase. The issue with @Atrox's statement about @FedorLap2006 following projet guidelines is that there are no guidelines: golint has been deprecated for a while... I've added basic linter settings that can be used to ensure no stylistic bonanzas in PRs. That includes a style preset (that bans naked returns), misspell (to assist foreign speakers), and other linters. I've created a pull request to address these but there is too many issues for one person to fix. After these issues are fixed, all a potential contributor will have to do is run golangci-lint run --fix before creating a pull request.
However, there are still some questions we need to answer: For example, do we enforce named return variables in the code? Go even states themselves:

Naked return statements should be used only in short functions, as with the example shown here. They can harm readability in longer functions.

Do we use whitespace linter (wsl), magic number detector (gomnd), lll, wrapcheck, or any of these linters? Error checks and gosimple would be great. Everything with the # Recommended label in golanci.yml in https://github.com/bwmarrin/discordgo/pull/1131 would be amazing.
Solution 2
The next solution requires a line to be drawn on how tagging is done. Go modules use tags for a reason. Semver is a standard that can be used to label versions. Using both eliminates issues with backwards compatibility, but that shouldn't be an issue right now. Why are we using Go 1.13 (from 2019)? It's 2022 and Go 1.18 is around the corner.
Deprecating functions is fine, but avoiding features that "would be good but <insert reason equal to we've always done it this way>" is NOT GOOD. Don't use a pen and paper in the era of calculators. Don't be discord.py. Features like Application Commands (April, 2022) are coming and Discord isn't going to stop them just because a non-professional has to change his code.
I'm not saying that this has happened in this repository, but that it's a direction we should not encourage.
Note
Don't take the post personally. I could be artificial ("nice") but there's no point.  Do we pull? Do we fork? Find out on the next episode of Discordgo.

First, I'd like to thank you for the time you may have put into this.  Some of the issues you've brought up are definitely issues with this library and talking about them and future goals isn't a bad thing.  However, this isn't a specific bug/feature and as such should be moved to the Github Discussions :)  So if you'd like to continue this please start up a discussion there.


add tests for already implemented API

there is a Firefox on Travis, but one can't control its version (?), so I'm going to use a dockerized version
prefer tests on top of page.setContent() to not rely on HTTP

🎉


Add --tags to git fetch

The test scenario isn't being added with this PR as it'll take a bit of time. The scenario is this:

Restore into the default .assets directory from an existing tag.
Push another tag from somewhere else
Try to restore that tag into the default .assets directory from step 1. <-- this step will fail

The problem is that restore does a git fetch origin which won't pull new tags. The fix is just to change it to git fetch --tags origin which will get the tags.

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests


Problems generating BakedLightMaps by code

Godot version:
ba134d44b8a5d87cf3694dd8858ec2a495bf6c11
OS/device including version:
Ubuntu 18.04
Issue description:
While trying to call the function BakedLightMap,Bake() i get in the console
ERROR: write_variant: Resource was not pre cached for the resource section, bug?
At: core/io/resource_format_binary.cpp:1508.

I debugged athe code and detected that the problem happens in
https://github.com/godotengine/godot/blob/ba134d44b8a5d87cf3694dd8858ec2a495bf6c11/core/io/resource_saver.cpp#L74
This happens while BakedLightMap tryes to save the ImageTexture in disk.
I guess that this issue is related to #18801, but as they are 2 totally diferent situations i decided to open a new issue.
Steps to reproduce:
Bake a lightmap by code.

This needs to be re-made in 3.2 with Vulkan, will kick there

Seems fixed in 3.2.4 beta3 (no error on calling bake()).
Can't test in 4.0, because bake() method doesn't exist for some reason (even though you can see it in online docs)
If you can still reproduce, provide a minimal reproduction project.


[PRS4] check

Class Database\Factories\Planning\TaskFactory located in ./database/factories/Quality/Planning/TaskFactory.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Models\Admin\Announcement located in ./app/Http/Controllers/Admin/Announcement.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\Auth\RegisteredUserController located in ./app/Http/Controllers/Auth/RegisteredUserController old.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Requests\Products\StoreStockLocationProductsRequest located in ./app/Http/Controllers/Products/StoreStockLocationProductsRequest.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\OSH\IncidentsController located in ./app/Http/Controllers/osh/IncidentsController.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\OSH\ConformitiesController located in ./app/Http/Controllers/osh/ConformitiesController.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\OSH\RisksController located in ./app/Http/Controllers/osh/RisksController.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\OSH\TrainingsController located in ./app/Http/Controllers/osh/TrainingsController.php does not comply with psr-4 autoloading standard. Skipping.
Class App\Http\Controllers\UsersController located in ./app/Http/UsersController.php does not comply with psr-4 autoloading

Lots of files on production server misplaced


docs(dpg): error property is printed as part of response parsing codes in generated examples

Description
See the original discussion. During example generation, we found that there are error-related properties defined in non-failure responses. So those properties are printed as part of the response parsing codes in the generated examples, like below:

/// Console.WriteLine(result.GetProperty("startTime").ToString());
/// Console.WriteLine(result.GetProperty("endTime").ToString());
/// Console.WriteLine(result.GetProperty("status").ToString());
/// Console.WriteLine(result.GetProperty("error").GetProperty("code").ToString());

For example, here is the OperationResponse.error property (see definition) of an LRO ClassificationRules_TagClassificationVersion. It's part of a LRO response, though the operation does define a separate error response.
Some open questions which we need to find the answers:

Is it common pattern or just LRO?
If it's LRO, is it by design?
Based on the conclusion above, how do we handling the error properties when generating examples?

Personally, I think this is an issue in the original swagger definition: https://github.com/Azure/azure-rest-api-specs/blob/1c7df99f6a84335cfd7bf5be8c800d72c1dddbc2/specification/purview/data-plane/Azure.Analytics.Purview.Scanning/preview/2018-12-01-preview/scanningService.json#L2019-L2023
They should not mix the error information into a successful response. I suggest we should add a linter rule to warn if an error property is found in a successful response.


Limit image height in background picker

When a background is too tall, you're unable to change the background since it continues off the screen, bringing the buttons with them. I fixed this by temporarily moving the tall wallpapers from /usr/share/backgrounds and setting a new wallpaper, but setting a max height for the preview or at least being able to use the arrow keys to cycle through them would be better.

Currently experiencing the same issue. Thanks for the temporary fix @Mrfiregem.

Should have been fixed on 3.2.0


Re-enable support for \Z in regular expressions on the GPU

Fixes #4532.
This re-enables support for the \Z string anchor in regular expressions on the GPU. In the default mode of regular expressions in Spark (Java), \Z is actually a synonym for $. The behavior differs only from $ when the MULTILINE or UNIX_LINES flags are enabled in Java (in that \Z maintains the same behavior while $ changes to matching ends of lines and not the end of the string).
This branch also includes a fix for an edge case that came up during fuzz testing for \Z that involves matching groups at the end of the string. In this case, it can now capture the line terminator at the end of the string.
Also, a documentation fix is included that was not updated earlier when $ was re-enabled.

build

build


App crashed when nesting components in NavigationContainer

The application through expo crashes when I touch any component that has been nested in a NavigationContainer. So far, this happens when I use the Stack.Navigator
I am using these relevant packages from the dependencies
{
    "react": "~16.9.0",
    "react-dom": "~16.9.0",
    "react-native": "~0.61.4",
    "react-native-safe-area-context": "^0.7.3",
    "@react-navigation/native": "^5.0.8",
    "@react-navigation/stack": "^5.1.1",

    "@eva-design/eva": "^1.4.0",
    "@ui-kitten/components": "^4.4.1",
}

Also, I am running my application on through Expo App installed on Android 7.0
To Reproduce
To reproduce the bug, create any UI Kitten component and nest it in the NavigationContainer. To start you of, mine looks something like this:
SampleScreen.js
import React, { useState } from 'react'
import { Layout, Input, Button } from '@ui-kitten/components'
import { SafeAreaView } from 'react-native-safe-area-context'

export default () => {
    const [ number, setNumber ] = useState('')

    return (
        <SafeAreaView>
            <Layout style={{ flex: 1 }}>
                <Text>Your number is: {number}</Text>
                <Input placeholder='Enter a number' keyboardType='numeric' value={number} onChange={setNumber(number)}/>
            </Layout>
        </SafeAreaView>
    )
}

and in the App.js
import React from 'react'
import { SafeAreaProvider } from 'react-native-safe-area-context'
import { ApplicationProvider } from '@ui-kitten/components'
import ErrorBoundary from './src/components/error_boundary'

import { NavigationContainer } from '@react-navigation/native';
import { createStackNavigator } from '@react-navigation/stack';

import SampleScreen from './src/screens/SampleScreen'

const Stack = createStackNavigator();

export default function App() {
    return (
        <SafeAreaProvider>
            <ApplicationProvider>
                <ErrorBoundary>
                    <NavigationContainer>
                        <Stack.Navigator headerMode='none'>
                            <Stack.Screen name='Sample' component={SampleScreen} />
                        </Stack.Navigator>
                    </NavigationContainer>
                </ErrorBoundary>
            </ApplicationProvider>
        </SafeAreaProvider>
    )
}

If you so much as breath 😅 (I mean touch) the app at this point. It crashes
Environment information
This was the output obtained form running npx envinfo --preset react-native
PS X:Path\to\Project>npx envinfo --preset react-native
  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 12.14.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: ~0.61.4 => 0.61.5

@iam-kevin this one?

Because in react-native you should use onChangeText instead of onChange 👍
See the code in live examples

Putting aside the onChange property, even when there is just the <Input placeholder="Type here" /> The application still crashes. This only happens when the components are wrapped in the NavigationContainter

@iam-kevin what is a stack trace?

No stackTrace was ever printed. It only showed that the app has crashed.
I was able to resolve the problem. This had nothing to do with the @ui-kitten/components
After reviewing the documentation for the react-navigation, It seems I had forgotten to add
import 'react-native-gesture-handler`

at the root of my application.
After that, everything worked out alright


Store backups in /tmp

It would be a really nice feature to store originals of all modified pacfiles in /tmp.
Example use case:
I completely F'd my shadow file during merge and it would be really nice to sideload my filesystem (because I can't log in now) and just cp /tmp/etc/shadow /etc/shadow.

Thank you for the suggestion @mcp292. I'll consider it, maybe having a "backup" folder could be of use, indeed.
Note, though, that the "/tmp" folder is usually a temporary mount point and its contents are deleted at each shutdown.

Right thank you for the reminder! I was remembering it as being deleted after a number of days, but that might've been what I set up on my local ~/tmp. In any case, the solution to my problem was finding a /etc/shadow- backup file. I don't know who created it, but am trying to find out. Maybe take a similar, but more consistent, approach.


Multiple Websites

Hey,
This is a small suggestion. I think it should be possible to put multiple XenForo websites / accounts on it. So, I could put both my MacRumors account and my Spigot account. I additionally could put both my normal Spigot account and my two alternate Spigot accounts.
Just a small suggestion so we do not have to install six different versions of this (I have about 8 XenForo accounts/sites I use on a daily basis).
Cheers,
Saphiria

This is already planned.
Is MacRumors a XenForo site? O.o

Yes! Probably the main reason I signed up. I love their add-on (probably custom) that lets them post very neat news articles with the comments.
Glad to hear it is planned! 👍 I have a lot of Spigot accounts and it will be nice to know when I need to check the alts.

Added the ability to add multiple accounts from #9, just not implemented elsewhere.

UI now supports multiple accounts.

This is pretty much fully implemented at this point, closing issue.


fix the missing source maps for the minified UMD bundle

instruct UglifyJS to add a //# sourceMappingURL=vaadin-router.umd.min.js.map comment to the end of the minified UMD bundle (see https://github.com/mishoo/UglifyJS2/issues/1905 for details)
specify the input source map as described in https://github.com/mishoo/UglifyJS2#composed-source-map

This change is

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable


Unit Tests for SQS - Push support for SQS utilizing SNS - Overhaul of SubscribeCommand - Addition of UnsubscribeCommand and UpdateCommand - Move setContainer to Job base class and more

This PR has grown out of a few other proposals/PRs from myself and @SammyK (#3759, #3778, #3784, #3789) so I'd like to get some more eyes on the additions/deletions/changes that are included in the branch.
First, a little background on this. I started out by writing unit tests for SqsQueue and SqsJob since there were none and also made a couple other small changes. @taylorotwell wanted me to submit just 1 PR to cover those few things. Then, @SammyK proposed (and implemented) adding push support for SQS, so I wanted to get that included since there were going to be merge conflicts.  So, I made him a contributor to my fork.  @SammyK  then created a branch and pushed his changes into my fork.  To squash my 23 commits that could be seen in the original PR #3860, I just manually copied over the 19 files and committed to the branch @SammyK had created (this branch).
I'd like to make sure this is all worthy of being included in the core of the framework and make sure any issues that people see are addressed so I can get everything ready to be merged.  Thanks for taking the time.

So what ever happened to allowing push queue support for SQS?
 Any suggestions how to get this done with laravel 5.1?

@kfuchs It's been a while since I've implemented push queues with SQS. I've posted a gist explaining how to do it in Laravel 4.2. I'm sure it wouldn't be too hard to make it 5.1 compatible with a little tweaking though.

@taylorotwell  any chances to start a discussion if this could be integrated nevertheless you decided to not do so? this would enable to run laravel in AWS Elastic Beanstalk out of the box, which would be really great. Laravel should be as elegant and straight forward as possible. imo this would add to this. i doubt pushing people to use a special infrastructure is the right way, even if it is one way to do. as iron.io push queues are supported too i guess it would only make sense to extend push queue support to sqs as well.


Roll Flutter Engine from f365c9f5dce3 to 0a7660c3cf11 (1 revision)

https://github.com/flutter/engine/compare/f365c9f5dce3...0a7660c3cf11
2024-11-18<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from K-3yXpPmmu1f0idCa... to io00npG_eDCYC7bac... (flutter/engine#56673)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from K-3yXpPmmu1f to io00npG_eDCY
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Footer social links updated as per your information

Description:
The social links in the footer of site has been updated according to your information
Screenshot:

why did you update on only homepage?? @9AB5 update this every page

@mdazfar2 Okay, I will update this in every page

@9AB5 You updated only the homepage, but as you know, the footer is available on all pages, so please update the footer on every page.

@mdazfar2 I have updated the footer social links to every page of site
Screenshot:

@9AB5 update your sync fork and also resolve your conflict

@mdazfar2 Okay, I will resolve the conflict and sync fork

@mdazfar2 I have resolved the conflicts

Hello @9AB5, can you please close your PR as it is overlapping and has many conflicts?


Unexpected return type when adding constructor method by Java template

When I try to simply add a empty constructor method to a test class by using Java template in my customized recipe, after code refactoring, the constructor is generated but with a returned type 'Template' which is not expected there:
Here is my code snippet of my recipe:
final JavaTemplate template = JavaTemplate.builder("public TestClass() {\n" +
                    "        \n" +
                    "    }").build();
classDeclaration = classDeclaration.withBody(template.apply(new Cursor(getCursor(), classDeclaration.getBody()),
            classDeclaration.getBody().getCoordinates().firstStatement()));
System.out.println(TreeVisitingPrinter.printTree(getCursor()));
return classDeclaration;

And the output is like this:

I tried to add a merbership method to a class, it works good. Not sure is this an issue when adding contructor method? Or probably I didn't handle it correctly...
Btw, my case is trying to add some constructors definition for some code refactoring requirement. e.g. add protected access constructor instead of leave it with a default public constructor to some classes.

Thank you for reaching out. I suspect that your template may work properly if you call the contextSensitive() method on JavaTemplate.Builder. This is always required when your template references variables or types which aren't part of the template themselves or one of the template parameters. Let me know if this doesn't help.

@knutwannheden it works after add contextSensitive(). thank you!


Add basic command list to help

This PR adds a basic list of available commands when ::help is used with no argument.

This is my first time using Kotlin - any feedback or corrections are appreciated.

You should remove the comments. The meaning of the code is already easy to comprehend from just reading the code.

All set. Let me know if there's anything else; otherwise, thanks for the helpful comments!


Change direction without releasing previous direction key

(Suggested by GMPranav at itch.io)
Just a small feedback. Make the actions buffer as much as possible. For example if I am facing left and I want to run right, I should be able to just hold 'D' and he should turn and start running right automatically.

Version 1.4.5, just released, implements this enhancement proposal.
So, I'm closing this issue.


[FEATURE] Add Component Footer to NextJs Project

Description
#1944
components/footer.js
Please assign it to me.
Screenshots

Additional information
No response

I'd like to work on this

can i work on this issue

Footer component has been added to Storybook
Please create specific issues for any future work


Add tmux support

This adds a --tmux option allowing for git-radar to be used in a tmux status prompt.

Works for me.
I had to tweak status command, otherwise git-radar would always run in the same directory, regardless of pane:
set -g status-right '#(cd "#{pane_current_path}" && ~/src/git-radar/git-radar --tmux)'

Also also had an issue where the lightning character added also created a newline breaking the status line. This did not happen with any other emoji:

As a workaround I disabled "use unicode version 9+ widths" setting in iTerm.


add dynamic hoursRemaining when under a day to cutoff

addresses: https://github.com/macadmins/nudge/issues/318

The next version of nudge will go back to days remaining if a negative integer daysRemaining integer is detected.


Add price endpoint

Add endpoint /api/v1/chain/{chainId}/tokens/{address]
It should return:

{
  "ethPrice": "<stringified int>",
  "usdPrice": "<stringified int>"
}

ethPrice: should be the price of the asset in the base currency of the network.
usdPrice: should be the price in USD for the asset.

Tested and verified locally, thanks!


Introduce Value_Type.Null, fix edge cases for read_many

Pull Request Description

Closes #6281

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
[x] Unit tests have been written where possible.
[x] If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
or the Snowflake database integration, a run of the Extra Tests has been scheduled.

If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

Changes affect Snowflake so I'm running the Extra suite:

https://github.com/enso-org/enso/actions/runs/12145121839

I expect it to fail because it is failing on develop. Yet I want to see if there are no more failures than what is expected.

Followup to fix Nothing * Nothing: #11751

Followup to fix Nothing * Nothing: #11751 and Nothing in expressions in DB #11757.

I think we could merge this PR and then improve the missing bits from these 2 tickets in a follow-up PR.

I've rebased on latest develop and noticed there are some test failures because of other changes. I will try to fix these soon, but it shouldn't change the shape of the overall changes that much.


Experiment about DataCollector Idea

Here are some idea about DataCollector.
This is very crappy code just to share :

ideas
detect and begin to discuss about some issue.

I think maybe a first version of the code could contains only :

ManualDataCollector
maybe remove the support of several DataCollector.
I don't know if we keep DataCollectorManager ?

Then with this ManualDataCollector this should be enough for :

write unit test
add some CLI commands to leshan client demo

About CLI, we can imagine to add a collect interactive command (e.g. : collect /3/0/1 /3/0/2)
And also add an option to send  interactive command which is send --collected-data.

Data Collector was replaced by Data Sender. (See #1274)


Remove-DbaAgentSchedule - Complete rewrite

Type of Change

[x] Bug fix (non-breaking change, fixes #6890 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Now using same pattern as Remove-DbaDbSequence, but we have to wait on a decision about the output properties to finish this, see #7408.

@sanderstad - can you take a look and approve? 🙇🏼

Thank you both!


[Question]: How to create a multiDocagent using function call with bedrock llms

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I want to create multi document agents using function calling as shown in here structuredPlannerAgent, but with bedrock llms ("anthropic.claude-v2",
"anthropic.claude-3-sonnet-20240229-v1:0")
but i am getting an error that these models don't support function calling.
i checked the Settings.llm.metadata.is_function_calling_model is False

is it possible to make the Settings.llm.metadata.is_function_calling_model  :  True and use the above-mentioned models for function calling
Or suggest some Bedrock llms that can be used for Function Calling to use in structuredPlannerAgent
Or is there any other way to use above mentioned models and create multi document agents.

I tried this  Multidocagents as well, but with ReActAgent instead of OpenAiAgent.
but the output is not as expected. I can't use Openai api and i have to go with bedrock llms.
basically, i am trying to create the following workflow.

You need to use the ReactAgentWorker, since the bedrock LLM class doesn't implement the FunctionCallingLLM class

from llama_index.core.agent import (
    StructuredPlannerAgent,
    ReActAgentWorker,
)

# create the react agent worker for reasoning
worker = ReActAgentWorker.from_tools(
    [lyft_tool, uber_tool], verbose=True
)

# wrap the worker in the top-level planner
agent = StructuredPlannerAgent(
    worker, tools=[lyft_tool, uber_tool], verbose=True
)

Hi @logan-markewich,
thank you
it worked with ReactAgentWorker.
but i am getting response sometimes in English and sometimes in different language (maybe French/ Latin 😂)
could you tell me why this is happening. Or should i change anything.
thankx

hi,
after experimenting for some time, now i am getting all responses in English.
But it is taking 1.5 to 2 min to return the response.  Is this normal response time?.
Is there a way to reduce the response time.
Thank you.

The response time depends on the LLM being used, how many LLM calls are being made, and how much text the LLM is writing.
Typically there is
1 LLM call to either call a tool or respond
1 tool call (which could involve 1+ LLM calls)
1 LLM call to either respond using the tool response or call another tool
and so on

Thank you @logan-markewich


is this really licensed lol am i gonna get sued

im like giving these cheats to my friend and stuff and im confused if im gonna get sued lol

You aren't going to be sued lmao, you have full permission to do whatever you want with the script. The only catch is that I am not liable to the harm caused.


Update cloudbuild.unit_tests.yaml

The unit tests timed out after 30 minutes. I commented out all frontend test to see how long the backend test will take. On my dev machine the test takes approx. 15 seconds.  The test came back in 1 min 7 seconds. Next, I will add the jacoco:report.

When I added the jacoco:report the backend test took 1 min 20 s.
With "prepare frontend" the test took 2 min 51 s.
With 'unit test for the front' the test timed out.

I deactivated the unit test trigger for now.

This PR is now obsolete.


How to declare many realms or routers?

Hi,
I have some question, what is best solution to handle many routers or realms with ThruwayBundle?
I want to have something like this
eg.
Realm chat (with auth), Realm public chat (without auth)
or many routers.
How can I do that with ThruwayBundle?
(in main thruway package is so simple)
Thank you so much

Wrong repo, sry


Add replicaRouting compat flag

This will remain experimental for some time.
Note that turning this on in local dev would effectively be a no-op, but rather than allow the flag to be set and continue regular operation, we'll throw an exception.

https://github.com/cloudflare/workerd/compare/1560c005eceb996c33fc2a0a70c4e42d7e84f3ec..619b393cbc722c98489f056021b24eab3b414247 is a rebase on main.


Conjugacy-checking to inspect relationships at the declaration level

Potential for massive improvement in the efficiency of conjugacy checking.

Faster conjugacy checking is now implemented, but I am leaving it as a separate step to allow testing and debugging before we put it in the regular processing.  Now model$checkConjugacy2() should return identical results as model$checkConjugacy().

Closing this since we have now been running the checkConjugacy2 system for a while.


Add tool for NTP checking

Sometimes it is valuable to be able to query an NTP server to determine if it is truly serving NTP and/or there is no firewall blocking your path. Including a tool/package that can do this could be helpful for those needing to troubleshoot their network.
@jiribrejcha has suggested sntp
I have previously used a pure python script leveraging sockets to accomplish a similar task.

Done in https://github.com/WLAN-Pi/pi-gen/commit/3a0e05e87bf52c8fdcefd5c2d32fd60cb2914cb0


[AnimatedImageView] gif repeatCount does not work correctly

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
I load gif with AnimatedImageView and set repeatCount .finite(count: 1) or .once,  it plays two times!
Xcode11.1 + iOS 13.1.3
What
If i set repeatCount repeatCount .finite(count: 0), it did not play;
If i set repeatCount repeatCount .finite(count: 1) or .once, it played two times;
If i set repeatCount repeatCount .finite(count: 2), it played three times;
Reproduce
override func viewDidAppear(_ animated: Bool) {
        super.viewDidAppear(animated)
        self.imageView.repeatCount = .finite(count: 1)
        self.imageView.kf.setImage(
            with: LocalFileImageDataProvider(fileURL: xxxx),
            options: [.forceRefresh]
        )
    }

Other Comment
[Add anything else here]

I can confirm this behaviour for the repeatCount property.
As a workaround i used the AnimatedImageViewDelegate method
animatedImageView(_:didPlayAnimationLoops:)
and the first time the method fires i did what i needed to do after the first end of the gif.

I can confirm this behaviour for the repeatCount property. As a workaround i used the AnimatedImageViewDelegate method animatedImageView(_:didPlayAnimationLoops:) and the first time the method fires i did what i needed to do after the first end of the gif.

but using AnimatedImageViewDelegate doesn't give desired  result because it stops the animation on first frame instead of last frame.

I can confirm this behaviour for the repeatCount property. As a workaround i used the AnimatedImageViewDelegate method animatedImageView(_:didPlayAnimationLoops:) and the first time the method fires i did what i needed to do after the first end of the gif.

but using AnimatedImageViewDelegate doesn't give desired result because it stops the animation on first frame instead of last frame.

In my case the animation stopped after the last frame. I was using version 6.3.0 if it matters.


Updated Readme.md

It's important to have an idea about hacktoberfest before everything. So I added the details of hacktoberfest. Thanks

Appreciate the intent, but unfortunately cannot merge this. Out Blogpost already explains what Hacktoberfest is all about and we don't want to use this repo to point people to non-Microsoft websites.


Awaiting schema build

Hi
My issue is similar similar to #61 .
I am trying to await my type-graphql schema build whilst preserving the apollo server instance between requests.
This is where I am up to so far and my requests seem to work in apollo studio.
import { ApolloServer } from '@apollo/server';
import { startServerAndCreateNextHandler } from '@as-integrations/next';
import { NextApiRequest, NextApiResponse } from 'next';
import 'reflect-metadata';
import { buildSchema } from 'type-graphql';
import { AppDataSource } from '../../src/db';
import TestResolver from '../../src/graphql/resolvers/test.resolver';

let server: ApolloServer | null = null;

const getApolloServer = async () => {
  const schema = await buildSchema({
    resolvers: [TestResolver],
  });

  return new ApolloServer({ introspection: true, schema });
};

const handler = async (request: NextApiRequest, response: NextApiResponse) => {
  try {
    if (!server) {
      if (!AppDataSource.isInitialized) {
        await AppDataSource.initialize();
      }

      const apolloServer = server || (await getApolloServer());

      server = apolloServer;
    }

    return startServerAndCreateNextHandler(server, {
      context: async (req, res) => ({ req, res }),
    })(request, response);
  } catch (error) {
    response.json({
      message: error.message,
    });
  }
};

export default handler;

However I'm getting the following error in my console
An error occurred during Apollo Server startup. All GraphQL requests will now fail. The startup error was: You should only call 'start()' or 'startInBackgroundHandlingStartupErrorsByLoggingAndFailingAllRequests()' once on your ApolloServer.

Do you know if there is a way to preserve the ApolloServer instance between requests without start being called more than once?
I am able to preserve the schema build between requests by reassigning schema within getApolloServer but ideally would be able to preserve the apolloServer
Thanks!

It looks like you're successfully preserving Apollo Server, but you also need to make sure you run only instantiate the integration once, for example:
let nextHandler: ReturnType<typeof startServerAndCreateNextHandler> | null = null;

const getNextHandler = async () => {
  const schema = await buildSchema({
    resolvers: [TestResolver],
  });

  // Instantiate the integration once
  return startServerAndCreateNextHandler(new ApolloServer({ introspection: true, schema }), {
    context: async (req, res) => ({ req, res }),
  });
};

const handler = async (request: NextApiRequest, response: NextApiResponse) => {
  try {
    if (!nextHandler) {
      if (!AppDataSource.isInitialized) {
        await AppDataSource.initialize();
      }

      // Once instantiated, preserve the handler
      nextHandler = await getNextHandler();
    }

    return nextHandler(request, response);
  } catch (error) {
    response.json({
      message: error.message,
    });
  }
};

export default handler;

That works perfectly, thanks Martin!

Glad you got it working!