[FancyZones] Modern apps snapping fix

Summary of the Pull Request
Changed condition when FZ should ignore the Allow popup windows snapping option for a popup window.

PR Checklist

[x] Closes: #29491
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

Try to snap Calculator with disabled Allow popup windows snapping.
Verify other popup windows behave as expected (Godot menus, Edge menus, start menu are not snapped)

/azp run

For the hotfix, we're reverting the original change instead in https://github.com/microsoft/PowerToys/pull/29532/
The changes in this PR require more thought/tests.

/azp run

Does this need another review?

Does this need another review?

We wanted these changes to be testable on CI, but seems we can't without visible UI. Looks like we'll be committing the changes without the full test set. Will review soon.

What are the windows that should be affected by allowSnapChildWindows? I'd like to test those, since looking at the code it looks like they won't be snapped?

The examples are Notepad++ Find window and Visual Studio's SolutionExplorer window. With child windows enabled you'll be able to snap those windows to the zone.

On tests we should want to test IsProcessable for every case as well.

Do you have more cases in mind?

Do you have more cases in mind?

What do you mean? I'm not seeing calls to Isprocessable in the tests that are added. Am I missing something?

We want to make sure Isprocessable also returns true or false for the cases that we are testing, right?

The examples are Notepad++ Find window and Visual Studio's SolutionExplorer window. With child windows enabled you'll be able to snap those windows to the zone.

Just tested it. It's working indeed :) Thank you!

Does AllowSnapPopupWindows from FancyZonesLib/SettingsConstants.h need to be removed as well?

Does AllowSnapPopupWindows from FancyZonesLib/SettingsConstants.h need to be removed as well?

Thank you for catching that!


REFACTOR: Move VM related node options to new VmNodeOptions class

We currently have VM options defined directly in the node definition.  This happened because we've been so focused on Hyper-V and XenServer provisioning and have ignored everything else for the past year or two.  We already have AzureNodeOptions and will be adding AwsNodeOptions and GoogleNodeOptions soon, so it's really not consistent to treat VM options specially.
We should create a new VmHostingOptions and VmNodeOptions classes and expose this as the NodeDefinition.Vm property.  This will break existing cluster definitions.
I'm also going to rename the other hosting related option classes like AzureOptions --> AzureHostingOptions

DONE for v2.2.0


Rename KMM to KMP

Since Kotlin Multiplatform Mobile (KMM) has been renamed to Kotlin Multiplatform (KMP)
source
I renamed everything from KMM and Kotlin multiplatform mobile to KMP and Kotlin multiplatform without affecting the logic, just labeling that is all
because we can't rename everything since the plugin in Android studio is still called KMM so I didn't rename it, yet
Example of running in a successful state:
Before
./kdoctor
Environment diagnose (to see all details, use -v option):
[✓] Operation System
[✓] Java
[✓] Android Studio
[✓] Xcode
[✓] CocoaPods

Conclusion:
  ✓ Your operation system is ready for Kotlin Multiplatform Mobile Development!

After
./kdoctor
Environment diagnose (to see all details, use -v option):
[✓] Operation System
[✓] Java
[✓] Android Studio
[✓] Xcode
[✓] CocoaPods

Conclusion:
  ✓ Your operation system is ready for Kotlin Multiplatform Development!

I also updated the README.md and the tests and the other messages
I also change one additional thing which is not related to the subject
Before
Shell.values().firstOrNull { it.path == shellPath }

After
Shell.entries.firstOrNull { it.path == shellPath }

Since in Kotlin 1.9.0, it's recommended to use entries instead of values()
in enum classes
there is one thing but I didn't change it
the diagnose should be diagnosis
it doesn't make much difference at least to me so I didn't update it

kdoctor 1.1.0
Kotlin Multiplatform Mobile Plugin: not installed


Uncaught SyntaxError: Unexpected end of JSON input

I am getting this error on reload of the client, otherwise seems to work.

index.html#/:1 Uncaught SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at IncomingMessage.eval (eval at <anonymous> (bundle.js:4112), <anonymous>:108:31)
    at emitNone (events.js:91)
    at IncomingMessage.emit (events.js:188)
    at endReadableNT (_stream_readable.js:975)
    at _combinedTickCallback (internal/process/next_tick.js:80)
    at process._tickCallback (internal/process/next_tick.js:104)
(anonymous)	@	request.js?c6b6:75
emitNone	@	events.js:91
emit	@	events.js:188
endReadableNT	@	_stream_readable.js:975
_combinedTickCallback	@	internal/process/next_tick.js:80
_tickCallback	@	internal/process/next_tick.js:104

Server is running origin/cardano-sl-1.0
front end is running daedalus master
Here is where it is happening in  request.js
   response.on('end', () => {
        const parsedBody = JSON.parse(body);

The this.req.res.statusCode== 404 and is not being checked.
Now there are two files that look very similar:
https://github.com/input-output-hk/daedalus/blob/master/app/api/etc/lib/request.js#L36
and
https://github.com/input-output-hk/daedalus/blob/master/app/api/ada/lib/request.js#L75
Body is empty:

The incoming message is a 404 not found!
IncomingMessage {_readableState: ReadableState, readable: false, domain: null, _events: EventHandlers, _eventsCount: 3…}
statusCode:404
statusMessage :"Not Found"

The request is
"/api/settings/time/difference"
Here is what I found in the _header : .req.socket._httpMessage._header
"GET /api/settings/time/difference HTTP/1.1
Host: localhost:8090
Connection: close"
Posted on Utopian.io -  Rewarding Open Source Contributors

@h4ck3rm1k3, can you provide us with commit hashes for cardano-sl and daedalus repos you are using?

I did in an email
https://github.com/input-output-hk/daedalus/issues/608#issuecomment-352786650

https://steemit.com/ada/@h4ck3rm1k3st33m/first-ada-recieved i got my first ada in my self compiled wallet and node

When the thing is working :+1:
https://localhost:8090/api/settings/time/difference
Returns
 {"Right":0}

I can confirm that the nix build is working on the front end
dupont@debian-build-speed:~/experiments/cardano-sl$ md5sum ./cardano-sl-1.0/bi
n/cardano-node
292c4f4b5710d56b455ee493423b0320  ./cardano-sl-1.0/bin/cardano-node


[BUG] push_to_argilla does not accept missing values for optional TextFields

Describe the bug
When a TextField of a Feedback dataset is not required, it is supposed to accept records that do not have items for the non-required field. However, while pushing such datasets to the server, it throws an error that states that the record has NoneType for the missing item rather than proceeding. Since there might be datasets that do not have items for all fields, it might be better if such datasets are accepted.
Stacktrace and Code to create the bug
# a dataset that has a mandatory field and an optional field
ds = rg.FeedbackDataset(
    fields=[
        rg.TextField(name="text1", required=True),
        rg.TextField(name="text2", required=False),
    ],
    questions=[
        rg.TextQuestion(name="question1", description="This is the first question"),
    ]
)

# this works perfectly as expected
record_with_text2 = rg.FeedbackRecord(
    fields={"text1": "This is the first text", "text2": "This is the second text"},
)

# this would be a possible dataitem that a user would submit, which will raise an error
record_with_no_text2 = rg.FeedbackRecord(
    fields={"text1": "This is the first text"},
)

# no problem adding it to the dataset
ds.add_records([record_with_no_text2])

# this will raise an error
remote_dataset = ds.push_to_argilla(name="my-dataset", workspace="admin")

Exception: Failed while adding the records to the `FeedbackDataset` in Argilla with exception: Argilla server
returned an error with http status: 422
Error details: [{'response': "Wrong value found for field 'text2'. Expected 'str', found 'NoneType'", 'params':
{}}]

Expected behavior
The dataset should be uploaded with the missing values as they are optional. Or, it can be something like NA, as well.

Environment:
│  • Client version: 1.17.0-dev
│  • Server version: 1.14.1
│  • ElasticSearch version: 8.8.2
Additional context
Add any other context about the problem here.

Hi @kursathalat this has already been fixed as of https://github.com/argilla-io/argilla/pull/3846, but thanks for reporting! For context, the issue was the the API was preventing from None or even empty values, and always checking the value, so something like {"required-field": "text", "optional-field": ""} does the work, but from now on, one can do {"required-field": "text", "optional-field": None} and/or {"required-field": "text"}


HiSense('N') not working

line 2254 in autoload/highlighter.vim
let l:cmd = (a:key == 'n') ? '>' : '<'
is not working for me
but when replaced by
if a:key == 'n'
let l:cmd = '>'
else
let l:cmd = '<'
endif
it works, please help

sorry, here is what works
let l:cmd = (a:key =~# 'n') ? '>' : '<'
because it needs to be case sensitive
please fix

It's great! Thank you for finding the problem and solution together. 👍
The fix has been updated. Thanks!


pulumi-bin: 2.21.2 -> 2.22.0

Motivation for this change
Things done

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

[x ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Were there no plugin upgrades?

Result of nixpkgs-review pr 115900 run on x86_64-linux 1

1 package built:

pulumi-bin


Warn user of the right format if there is error when paring parameters

I just found the error reports when sending Menu.popup( window, x, y ) with float point values. Here is the error message:
Uncaught Error: Error processing argument 1.
TypeError: Error processing argument 1.
    at TypeError (native)
    at Menu.popup (/Users/johnny/jwu/atom-test/Atom.app/Contents/Resources/atom/browser/api/lib/menu.js:115:19)
    at callFunction (/Users/johnny/jwu/atom-test/Atom.app/Contents/Resources/atom/browser/lib/rpc-server.js:116:18)
    at EventEmitter.<anonymous> (/Users/johnny/jwu/atom-test/Atom.app/Contents/Resources/atom/browser/lib/rpc-server.js:208:14)
    at EventEmitter.emit (events.js:118:17)
    at EventEmitter.<anonymous> (/Users/johnny/jwu/atom-test/Atom.app/Contents/Resources/atom/browser/api/lib/web-contents.js:99:23)
    at EventEmitter.emit (events.js:118:17)

The error is caused by the following code:
menu.popup(Remote.getCurrentWindow(), 10.2, 10 );

To avoid this, I need to make sure the x, y be integer number before sending them to popup.
I think the low-level API should protect on this, and sending warning message to remind user in sending the right format.

In C++ there is no easy while portable way to get the type name of a type as String, so it is not practical to implement this. I'm closing this as won't fix.


feat(swc/plugin_macro): export new interface for getting plugin schema version (#5060: Part 5)

Description:
Retrying https://github.com/swc-project/swc/pull/5158 for the CI.
This PR adds a new fn in plugin's macro side, returns schema version defined in swc_common at the moment of compilation. To support per-build time flags, also introduces features to the downstream pkg from top level (binding-*).
Changes are based on theoritical workflow I have in mind, which means this is possibly not correct and would require further refactorings. But having each step helps to setting up actual (manually) testable workflow.
Once this goes in, I'll pause bit and try to attempt refactor integration test for the plugin. I feel it's hitting tipping point to worth better ergonomics to test more than simple transformation execution. Probably will need node.js side testing as well for whole integrations.

BREAKING CHANGE:

Related issue (if exists):
#5060

@kdy1 seems PR is ok now?


Updated Blockly with new renderer, field cleanup, fixes

Target
URL

Microbit
https://makecode.microbit.org/app/37d71e8c2bd3843b169576d48038de235b0761e5-ec23236843

Minecraft
https://minecraft.makecode.com/app/0d322a95b0721c40d71302176752943520e69b2e-781d021a96

Adafruit
https://makecode.adafruit.com/app/49ad4aa3ae8e972ebb06795dc6aa5f66cb3806b3-e6efccdb5f

Arcade
https://arcade.makecode.com/app/1cbbf71dad03e60e84616fb0bba16dbdc7ad25bf-0bd8f72393

Known issues (fixing after merge):

Small text field overlap when piano editor is first opened
Insertion marker does not consider child blocks (intentional with new renderer)
(arcade) Image field rendering (white instead of gray transparency)

Non-regression bugs:

Duplicating function does not correctly rename
(Arcade) Color field doesn't highlight selected color

Accompanying PRs:

[x] https://github.com/microsoft/pxt-blockly/pull/269 (Blockly merge)
[ ] https://github.com/microsoft/pxt-microbit/pull/2658 (Microbit field editor fix)
[ ] https://github.com/microsoft/pxt-adafruit/pull/1159 (Adafruit field editor fix)

@riknoll the main blockly dropdown now supports rendering an image (https://github.com/microsoft/pxt-blockly/blob/develop/core/field_dropdown.js#L618), settext has been deprecated entirely, partially combined with doValueUpdate and partially moved back to blockly-core, and since the svg arrow is in blockly-core as well we use their built in updateSize_.
i suspect a bit of this will come back because we need to render selected text for the microbit image dropdown, but for now the base blockly rendering looks reasonable

Toggles look a little weird:


Support for custom event loggers

Description of the bug:
I'd like to implement a custom event logger that sends data about sync / build times to an internal metrics service.
It looks like currently there is some existing code around EventLoggingService and EventLogger that might allow me to do this. However, I'm confused whether this is a supported feature or not.
There is the com.google.idea.blaze.EventLogger extension point, but it doesn't seem to be actually called from anywhere.
I could also implement the EventLoggingService interface, but the comment on that class suggests it's meant to just forward events to EventLogger. So I'm not sure if this is the correct path or not.
I'm opening this as a bug because the code looks like it tries to support this.
Which category does this issue belong to?
Intellij
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
N/A
Which Intellij IDE are you using? Please provide the specific version.
IntelliJ Ultimate 2024.1
What programming languages and tools are you using? Please provide specific versions.
Java
What Bazel plugin version are you using?
N/A
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response

Yeah, so it seems to be unused. Btw quite recently google commited an "intellijext" service for handling these logs here https://github.com/bazelbuild/intellij/commit/3dcb25108628d264da2e933e6231fbeaec8ff706 but I don't know what's the status of that.
If it would work, you could even try to handle the logs in an external application.
@mai93 do you know what's the status of this?


Add tiered caching blog

Closes #3374
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

@pajuric Editorial comments addressed. This blog is ready to publish.

@kolchfa-aws

Editorial comments addressed. This blog is ready to publish.

We still need to add Peter before we publish this blog, right?

Yes, I am waiting for his info and will add it to this PR when it's available.

@sgup432 @peteralfonsi Peter's bio added.

@kkhatua - You are approved to push this live.


Update Models before merging relations

https://github.com/geneontology/go-ontology/issues/12811
We need to update all of the existing models so that they will not contain outdated properties once the merge in the above ticket is completed. Please check the task in the above ticket once the update is complete.

@cmungall I think these 4 updates should do it:
PREFIX directly_activates: <http://purl.obolibrary.org/obo/RO_0002406>
PREFIX directly_positively_regulates: <http://purl.obolibrary.org/obo/RO_0002629>
DELETE {
    GRAPH ?g { ?s directly_activates: ?o . }
}
INSERT {
    GRAPH ?g { ?s directly_positively_regulates: ?o . }
}
WHERE {
    GRAPH ?g { ?s directly_activates: ?o . }
}

PREFIX directly_activates: <http://purl.obolibrary.org/obo/RO_0002406>
PREFIX directly_positively_regulates: <http://purl.obolibrary.org/obo/RO_0002629>
DELETE {
    GRAPH ?g { ?s ?p directly_activates: . }
}
INSERT {
    GRAPH ?g { ?s ?p directly_positively_regulates: . }
}
WHERE {
    GRAPH ?g { ?s ?p directly_activates: . }
}

PREFIX directly_inhibits: <http://purl.obolibrary.org/obo/RO_0002408>
PREFIX directly_negatively_regulates: <http://purl.obolibrary.org/obo/RO_0002630>
DELETE {
    GRAPH ?g { ?s directly_inhibits: ?o . }
}
INSERT {
    GRAPH ?g { ?s directly_negatively_regulates: ?o . }
}
WHERE {
    GRAPH ?g { ?s directly_inhibits: ?o . }
}

PREFIX directly_inhibits: <http://purl.obolibrary.org/obo/RO_0002408>
PREFIX directly_negatively_regulates: <http://purl.obolibrary.org/obo/RO_0002630>
DELETE {
    GRAPH ?g { ?s ?p directly_inhibits: . }
}
INSERT {
    GRAPH ?g { ?s ?p directly_negatively_regulates: . }
}
WHERE {
    GRAPH ?g { ?s ?p directly_inhibits: . }
}

@kltm we should coordinate a time to bring Noctua down while I do this update. Should just take a few minutes.

@balhoff To clarify, this will be:

bring the system down
update the models in-place
destroy/re-create journal
restart system
yes?

Bring the system down
Copy the journal file elsewhere to run SPARQL server
Run update
Stop SPARQL server
Move updated journal in place of old journal
Restart system

Fair enough. Do you want to run the server/migration, or do you have a command for me?

Actually, now that I think about this more I think it would be worth holding off and first implementing a command line to just run the SPARQL update via the minerva jar (instead of starting up the actual Blazegraph server). If you haven't already started kicking people off, we could delay this until tomorrow and I'll create that command first.

Sounds good to me! If what you put in could be generalized to make doing these types of operations in the future more plug-and-play, that would be great--this will probably be a work pattern that comes up a lot.

@kltm yes exactly.

Completed by https://github.com/geneontology/noctua/issues/431


Mitra/update mt5 page for eu

Changes:

...

Type of change

[x] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

please resolve conflicts, thanks :pray:

please resolve conflicts, thanks 🙏

Resolved , thanks 🙏


Feature: Adds Perspective API for spam detection

This feature adds  the Prospective API (https://perspectiveapi.com/) as a new spam detection to Commentoplus
Export following settings in your environment:
export COMMENTO_PERSPECTIVE_KEY=YOUR_API_KEY_FROM_PERSPECTIVE
export COMMENTO_PERSPECTIVE_LIMIT=0.3
export COMMENTO_PERSPECTIVE_LANGUAGE=de
--
COMMENTO_PERSPECTIVE_KEY:
To create a new Perspective API key follow the instructions at https://developers.perspectiveapi.com/s/docs-get-started
COMMENTO_PERSPECTIVE_LIMIT:
The limit defines the minimum value for the Perspective probability summary score. Everything above the value will be flagged  in Commentoplus. (Default 0.5)
COMMENTO_PERSPECTIVE_LANGUAGE:
Configure the language to your requirements. (Default: en)

Great addition! I will be happy to merge this; please could you add the documentation to the README too?

Thanks, I have updated the README.


Animating linear-gradient background-color

🐛 Bug Report
It is not possible to animate background-color with linear gradient value with either renderprops nor the hooks
To Reproduce
Does not work
<Spring
  from={{ backgroundColor: 'linear-gradient(135deg, rgb(185, 198, 109) 0%, rgb(34, 48, 17) 100%)' }}
  to={{ backgroundColor: 'linear-gradient(135deg, rgb(192, 199, 165) 0%, rgb(31, 44, 31) 100%)' }}>
  {props =>
hello
}
</Spring>

Works
<Spring
  from={{ background: 'linear-gradient(135deg, rgb(185, 198, 109) 0%, rgb(34, 48, 17) 100%)' }}
  to={{ background: 'linear-gradient(135deg, rgb(192, 199, 165) 0%, rgb(31, 44, 31) 100%)' }}>
  {props =>
hello
}
</Spring>

Expected behavior
(A clear and concise description of what you expected to happen.)
Link to repro (highly encouraged)
(Please provide either a CodeSandbox demo or an example GitHub repo.)
Environment

react-spring v8.0.27
react v16.10.1

Please try with v9: npm install react-spring@next

It still didn't work with react-spring@next
heres is a codesandbox link
I also found that it could not animate background property is one is from hex to rgb values.

@noushad-pp, could you elaborate more on what you expect to happen? I don't have any issues animating linear-gradient values for a background color.

@noushad-pp Your sandbox works for me.

I also tried animating background property from linear gradient value to a normal rgba() and it also didnt work

That's not expected to work

@aleclarson If you look at the codesandbox, the second div is completely white and thus its not animating

Oh, that's also expected. As this article says:

Because <gradient>s belong to the <image> data type, they can only be used where <image>s can be used. For this reason, linear-gradient() won't work on background-color and other properties that use the <color> data type.


SFC - undefined css vars

Version
3.0.2
Reproduction link
https://codepen.io/talmand/pen/8d7aa90123720c03f09d83f542b34666
Steps to reproduce
Attempt to use a reference to a var that doesn't exist or returns anything but a string.
<template>

hello

</template>

In the CodePen example, inspect the template's div to see that --bgcolor has "undefined" as its value and prevents the fallback value from being used.
What is expected?
If the injection involves anything other than a string it should skip over creating that CSS var to allow for a possible fallback of the CSS var() function to work.
What is actually happening?
If the var being referenced doesn't actually exist then the CSS var is created as --color: undefined, which prevents the CSS var() function fallback from being used. If the var returns anything but a string then that value is used, such as --color: [object Object].

I do have a thought to fix this by adding a type check for strings within "useCssVars.ts" before the setProperty is used to create the CSS vars in the style attribute. It could also possibly allow for a console warning to state what the issue for that particular CSS var. The code I've written to address this works in my quick browser tests, although a proper test is difficult because it requires forcing errors in "useCssVars.spec.ts" which TypeScript obviously wouldn't care for.
Although, I'm not fully convinced this problem needs fixing because of two reasons. Requiring a string doesn't change an invalid value provided to the CSS var still prevents the fallback from working. I also found not using an inline object in the style block's vars attribute in favor of an object I create in the component is far more flexible. In that situation if there's no reference for a CSS var in my object then there's no var created in the style attribute. Thus the fallback of the CSS var() function works.
Another answer is simply, "don't do that".
But it should be a reasonably easy contribution to the project so I decided to inquire if there's any interest.

Is this still an issue? The repo link doesn't work anymore.

I'm not sure at this moment. Shortly after this issue was opened and a PR created the syntax and some of the functionality of the feature changed. So I closed the PR until these changes were more locked down. At this point I wouldn't be against closing the issue to reopen later if it something of this nature still persists.

Sounds good. Thanks for the quick feedback!


v1.6 backports 2020-08-07

#12822 -- daemon: Add hidden --k8s-sync-timeout option (@joestringer)

Once this PR is merged, you can update the PR labels via:
$ for pr in 12822; do contrib/backporting/set-labels.py $pr done 1.6; done

test-backport-1.6


Update version number to v1.4.0

Codecov Report

Merging #262 (28f0d99) into master (5600420) will not change coverage.
The diff coverage is 0.00%.

@@            Coverage Diff            @@
##             master     #262   +/-   ##
=========================================
  Coverage     69.54%   69.54%
  Complexity      766      766
=========================================
  Files           124      124
  Lines          2581     2581
  Branches        325      325
=========================================
  Hits           1795     1795
  Misses          685      685
  Partials        101      101

Impacted Files
Coverage Δ

src/main/java/fridgy/MainApp.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[image_picker] Update app-facing and web analysis options

Switches from legacy analysis options to current analysis options,
fixing all analysis issues it exposed.
Also opportunistically fixes one potential null safety issue highlighted by the warnings.
Part of https://github.com/flutter/flutter/issues/76229
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[x] I signed the CLA.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[x] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

The last commit here is an actual behavioral change. The warnings highlighted that a helper method that was typed to return a nullable value was internally force-unwrapping a nullable value instead of passing that null through, so I fixed it instead of adding an explicit force-unwrap under the assumption that it was a mistake.

Currently looking at this


Add Orleankka

Distributed Computing/Orleankka - Orleankka
Orleankka is a functional API for Microsoft Orleans framework. It is highly suitable for scenarios where having composable, uniform communication interface is preferable, such as: CQRS, event-sourcing, re-routing, FSM, etc. Additional API avaiable for F# called Orleankka.FSharp.

@oboff Thanks.


Page variable is null in blade component when using frontend routing

Description
The $page variable is always null in templates using blade components when using the frontend routing feature of Runway. However, that page states all variables from the cascade are available.
Steps to reproduce
1. Create a resource that uses the RunwayRoutes trait
2. Set the template in the Runway config to a template that uses components inside it eg:
<x-layout :context="$__data">
    Hello, world!
</x-layout>

3. Inside the layout component call:
@props(['context'])
{{ $page->id }}

4. Error: Attempt to read property "id" on null

Is it perhaps because the resources are not part of the pages collection? What would be the proper way to re-use a layout and still be able to set a page's <title>s? Do I have to define a view-only field like title on my resource and save it in the database?

My assumption in the last paragraph was correct, sorry.
I have another question that is somewhat related. Is there a better way to access a resource's fields inside a blade component? Currently, you have to @aware(['id', 'name', 'description', 'etc..']) for every single field of a resource.
Environment
Environment
Application Name: Test
Laravel Version: 11.14.0
PHP Version: 8.3.8
Composer Version: 2.7.7
Environment: local
Debug Mode: ENABLED
URL: local.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Statamic
Addons: 1
Sites: 3 (Nederlands, Deutsch, English)
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.12.0 PRO
Statamic Addons
statamic-rad-pack/runway: 7.7.5

I've got a fix ready which will allow you to use the $page variable, like you can with entries, however it depends on a PR in Statamic Core before it can be merged & released.


Source path with make switch only seems to work if in same directory

Thanks for reporting. Can you include the specific error you are getting?

Sorry, here it is:
[Error: ENOENT: no such file or directory, open 'morphir.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: 'morphir.json'
}

I've also experienced this (but forgot to file an issue).

Ah, I get it now. It's confusing because the source directory and the location of morphir.json are different. I guess I should document that you need to run morphir make in the model project's root.

I actually think as long as you allow the user to specify the path to morphir.json that we need to support executing properly from that location.
Also I think we shouldn't solve this by removing the ability to provide the morphir.json location.

I can take a look at fixing this so that you can run it from wherever. If we agree that is the proper approach.

Sorry, I was a bit confused. Now I remember that you can specify the project path and morphir.json is relative to that. The code looks good to me so it's possible that I just didn't push out the latest to NPM.

Not sure if my description was confusing. I was trying to do an automated build and use a full path to the morphir.json file, but it wouldn't follow the path and only work in same directory.

I was confusing myself :)
Anyway, I pushed a new version to npm (0.3.4), that should fix it.

Can any of you please confirm if this is fixed? My testing shows that it works as expected now.

I use"morphir-elm make src/Morphir/Sample/Apps/morphir.json" and it says "Could not find file at 'morphir.json'"

Can you try morphir-elm make -p src/Morphir/Sample/Apps instead? The -p switch specifies the root directory of the project where it expects to find morphir.json.

This appears have been fixed. Closing.


More metadata is needed for conditional styling

Hi, this is a great library, and thank you for your development and sharing!
I have a feature request.
I want to change the tag Item styling based on its value.
But I think more metadata is needed to achieve this. (currently "disabled" only)
In my use case,
there are  "todo", "in progress", "done"  labels.
and want to change its background and text color in order for users to see what is currently selected.
In this case, something like "value" is good
            classNames={{
              tagItem: ({ value, isDisabled }) => {
                if (value === 'todo') {
                  return 'flex text-sm text-yellow-500 border border-slate-300 rounded shadow-sm mx-0.5'
                }
                if (value === 'in progress') {
                  return 'flex text-sm text-red-500 border border-slate-300 rounded shadow-sm mx-0.5'
                }
                if (value === 'done') {
                  return 'flex text-sm text-green-500 border border-slate-300 rounded shadow-sm mx-0.5'
                }
              },

Hi @AruhaMaeda 👋
Thanks for using our library and thanks for this feature request.
I think your request is really relevant and should be implemented very soon. It will be available in the next release, most likely within the day.

Hi @AruhaMaeda  👋!
Sorry for the delay. I added some features to the project to make the development phase easier.
The functionality is now available. But you have to upgrade to version 1.8.0.
Now use this code.
classNames={{
  tagItem: ({ item, isDisabled }) => {
    if (item.value === 'todo') {
      return 'flex text-sm text-yellow-500 border border-slate-300 rounded shadow-sm mx-0.5'
    }
    if (item.value === 'in progress') {
      return 'flex text-sm text-red-500 border border-slate-300 rounded shadow-sm mx-0.5'
    }
    if (item.value === 'done') {
      return 'flex text-sm text-green-500 border border-slate-300 rounded shadow-sm mx-0.5'
    }
},

Item contains all information of the tag.
https://github.com/onesine/react-tailwindcss-select#all-keys


ASU-499 Add REST API for applications

This PR adds a new endpoint at /v1/applications/ which can be used to POST application data.
The application has one primary applicant, whose information comes from the user profile.
Optionally, it may have an additional applicant, whose information is received as part of the application itself.
Submitting an application requires an authenticated user. Only creating applications (POST) is possible at the moment. Viewing applications with GET or modifying them with PUT, PATCH, or DELETE is not allowed.

Codecov Report

Merging #74 (7b48dac) into develop (7970e0e) will increase coverage by 0.68%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #74      +/-   ##
===========================================
+ Coverage    90.67%   91.35%   +0.68%
===========================================
  Files           42       48       +6
  Lines         1222     1319      +97
  Branches       107      111       +4
===========================================
+ Hits          1108     1205      +97
  Misses          90       90
  Partials        24       24

Impacted Files
Coverage Δ

apartment_application_service/urls.py
100.00% <100.00%> (ø)

application_form/api/serializers.py
100.00% <100.00%> (ø)

application_form/api/views.py
100.00% <100.00%> (ø)

application_form/elastic_helpers.py
100.00% <100.00%> (ø)

application_form/urls.py
100.00% <100.00%> (ø)

connections/__init__.py
100.00% <100.00%> (ø)

connections/apps.py
100.00% <100.00%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


Update cats-effect, cats-effect-testkit to 3.5.5

About this PR
📦 Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-testkit

from 3.4.11 to 3.5.5
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #651.

Superseded by #654.


Finish Scripture Mastery lists

Need to copy the text of the NT, BoM, and D&C scripture mastery passages into the scripture_mastery.xml file.

Closed by c6d0a640894559413292db6e8baff5c3e44fb184.


Personalization missing functions

1st bug
Adding header to the message before adding personalization, creates an empty personalization object within the email object, and when you add following personalization with recipients emails, your interface throws error because the first personalization initialized by adding header doesn't contain TO field! Who wrote this code??? Seriously, this is bad design decision...
2nd I dunno missing feature
$personalization->addHeader("key", "value");

doesn't work like we do it for the single email, we need to do:
$personalization->addHeader(\SendGrid\Mail\Header("key", "value"));

just add wrapper to handle it like it's done for the $email->addHeader(key, value)

If you want to send a newsletter, for example, you want to have the same headers for all the emails:

$email = new \SendGrid\Mail\Mail();
$email->addHeader('List-Unsubscribe', "<$link>");; // <-- this created an empty Personalization object
...

foreach($subscribers as $subscriber)
{
			$personalization = new Personalization();
			$personalization->addTo(new To($subscriber->email, ""));
,,,
}

// throws an error because first $email->addHeader() creates an empty
// Personalization object without defined "to" field
$response = $sendgrid->send($email);

Take a look at addHeader from  sendgrid/sendgrid/lib/mail/Mail.php

    public function addHeader(
        $key,
        $value = null,
        $personalizationIndex = null,
        $personalization = null
    ) {
        $header = null;
        if ($key instanceof Header) {
            $h = $key;
            $header = new Header($h->getKey(), $h->getValue());
        } else {
            $header = new Header($key, $value);
        }

        $personalization = $this->getPersonalization($personalizationIndex, $personalization);
        $personalization->addHeader($header);
    }

You see? It creates an empty Personalization object WITHOUT 'to' field declared, so when you want to send the email blast it fails, because the first Personalization for the sender is this empty header personalization.
Solution?
I have to add the same headers to every Personalization object and cannot add the universal header for the $email = new \SendGrid\Mail\Mail() instance.
Unproductive and bad design. Hard to spot and debug.
Even your own documentation is wrong at this:
https://docs.sendgrid.com/for-developers/sending-email/personalizations
`Some properties can be defined both at the root level of the request body (message level) and at the personalizations level.
For example, the from, subject, headers, custom_arg, and send_at properties can all be defined at the message level or at the personalizations level. `

Ah, I see. Definitely an issue. Will add that to the backlog as well. PRs are welcome.


chore: merge main into codebuild branch

Description of changes
Merge the main to cb to resolve the conflict

CDK / CloudFormation Parameters Changed

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1622 (b6831ce) into cb (8574867) will increase coverage by 0.02%.
The diff coverage is 67.04%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##               cb    #1622      +/-   ##
==========================================
+ Coverage   63.42%   63.44%   +0.02%
==========================================
  Files         371      371
  Lines       21701    21731      +30
  Branches     5177     5186       +9
==========================================
+ Hits        13763    13787      +24
- Misses       7211     7217       +6
  Partials      727      727

Impacted Files
Coverage Δ

...ory-api/src/commands/api/add-graphql-datasource.ts
24.76% <0.00%> (ø)

...gory-api/src/force-updates/force-refresh-schema.ts
18.51% <0.00%> (ø)

packages/amplify-category-api/src/index.ts
30.80% <0.00%> (ø)

...vider-utils/awscloudformation/apigw-input-state.ts
88.00% <0.00%> (ø)

...rmation/cdk-stack-builder/apigw-stack-transform.ts
11.49% <0.00%> (ø)

...-api/src/provider-utils/awscloudformation/index.ts
10.76% <0.00%> (ø)

...ormation/service-walkthroughs/apigw-walkthrough.ts
8.84% <0.00%> (ø)

...mation/service-walkthroughs/appSync-walkthrough.ts
15.36% <0.00%> (ø)

...l-auth-transformer/src/graphql-auth-transformer.ts
94.86% <0.00%> (ø)

...aphql-index-transformer/src/resolvers/resolvers.ts
97.20% <ø> (ø)

... and 19 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Importing JSON with apostrophes in obsidian

Hello,
I am trying to import beast from 5e.tools json. The description of one of the abilities has apostrophes and when imported into obsidian, apostrophes are replaced with ' which is unicode representation of '. Json in question is below
{
	"name": "Regeneration",
	"description": "The troll regains 10 hit points at the start of its turn. If the troll takes acid or fire damage, this trait doesn't function at the start of the troll's next turn. The troll dies only if it starts its turn with 0 hit points and doesn't regenerate."
}

And this is the imported text in Obsidian:
Regeneration: The troll regains 10 hit points at the start of its turn. If the troll takes acid or fire damage, this trait doesn't function at the start of the troll's next turn. The troll dies only if it starts its turn with 0 hit points and doesn't regenerate.
Is there any way to bypass this behavior? I was trying to reproduce it with javascript, but I think it's problem with communication between obsidian and plugin.
Thank you for any replies.

I can't see a don't difference in your report.
Is it all three occurrences of the apostrophe which are being replaced?

Github formatted it automatically, didn't notice, sorry :D
Regeneration The troll regains 10 hit points at the start of its turn. If the troll takes acid or fire damage, this trait doesn't function at the start of the troll's next turn. The troll dies only if it starts its turn with 0 hit points and doesn't regenerate.

Oh, the HTML form of the character. (Unicode world be changing it's binary value to something like 2019)

This issue should be fixed in version 0.31.2


[WIP][SPARK-29032][CORE] Simplify Prometheus support by adding PrometheusServlet

What changes were proposed in this pull request?
Prometheus.io is a CNCF project which is used widely with K8s.

https://github.com/prometheus/prometheus

This PR aims to simplify Prometheus support by adding PrometheusServlet. The main use cases are K8s and Spark Standalone cluster environments.
Note that this PR aims to focus Apache Spark generated metrics. Also, we need to update the document later in a separate PR.
Why are the changes needed?
There exists a few ways to support Prometheus. However, they requires extra configurations and new resources (port number to pull or gateways to push). This PR aims to export Spark's metrics which starts with metrics_ prefix from the existing (1) method natively.

Spark JMX Sink + Prometheus JMX Converter
Custom Sink + Prometheus Pushgateway

Does this PR introduce any user-facing change?
Yes. New web interfaces are added along with the existing JSON API.

Component
JSON End Point
Prometheus End Point

Spark Master
/metrics/master/json/
/metrics/master/prometheus/

Spark Master
/metrics/applications/json/
/metrics/applications/prometheus/

Spark Worker
/metrics/json/
/metrics/prometheus/

Spark Driver
/metrics/json/
/metrics/prometheus/

$ bin/spark-shell
...
Spark context Web UI available at http://localhost:4040
...

$ curl --silent http://localhost:4040/metrics/prometheus/ | head -n5
metrics_local_1568101220707_driver_BlockManager_disk_diskSpaceUsed_MB_Value 0
metrics_local_1568101220707_driver_BlockManager_memory_maxMem_MB_Value 366
metrics_local_1568101220707_driver_BlockManager_memory_maxOffHeapMem_MB_Value 0
metrics_local_1568101220707_driver_BlockManager_memory_maxOnHeapMem_MB_Value 366
metrics_local_1568101220707_driver_BlockManager_memory_memUsed_MB_Value 0

How was this patch tested?
Manually connect the new end-points with curl.
Or, run prometheus --config.file=config.yaml with the following configuration and see through the Prometheus UI.
config.yaml
global:
  scrape_interval:     15s
  evaluation_interval: 15s
  external_labels:
      monitor: 'codelab-monitor'
rule_files:
scrape_configs:
  - job_name: 'spark-master'
    scrape_interval: 10s
    metrics_path: '/metrics/master/prometheus/'
    static_configs:
      - targets: ['localhost:8080']
  - job_name: 'spark-applications'
    scrape_interval: 10s
    metrics_path: '/metrics/applications/prometheus/'
    static_configs:
      - targets: ['localhost:8080']
  - job_name: 'spark-worker'
    scrape_interval: 10s
    metrics_path: '/metrics/prometheus/'
    static_configs:
      - targets: ['localhost:8081']
  - job_name: 'spark-driver'
    scrape_interval: 10s
    metrics_path: '/metrics/prometheus/'
    static_configs:
      - targets: ['localhost:4040']

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15392/
Test PASSed.

Test build #110406 has started for PR 25741 at commit 65cf440.

Hi, @vanzin and @srowen . Could you review this please?

Also, cc @skonto .

Oops. I missed the task metrics. I'll update this PR later.

Test build #110406 has finished for PR 25741 at commit 65cf440.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110406/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15405/
Test PASSed.

Test build #110421 has started for PR 25741 at commit ed543a1.

Test build #110425 has started for PR 25741 at commit 1abf837.

Yes. Prometheus.io is a CNCF project which is used widely with K8s.

https://prometheus.io

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15411/
Test PASSed.

Test build #110421 has finished for PR 25741 at commit ed543a1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110421/
Test PASSed.

Test build #110425 has finished for PR 25741 at commit 1abf837.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110425/
Test PASSed.

Test build #110434 has started for PR 25741 at commit 6104748.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15421/
Test PASSed.

Test build #110436 has started for PR 25741 at commit a47313e.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15423/
Test PASSed.

Test build #110434 has finished for PR 25741 at commit 6104748.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110434/
Test PASSed.

Test build #110436 has finished for PR 25741 at commit a47313e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110436/
Test PASSed.

Test build #110486 has started for PR 25741 at commit 36e2d1b.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15462/
Test PASSed.

Test build #110486 has finished for PR 25741 at commit 36e2d1b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110486/
Test PASSed.

Test build #110491 has started for PR 25741 at commit 8f063cf.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/15466/
Test PASSed.

Test build #110491 has finished for PR 25741 at commit 8f063cf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/110491/
Test PASSed.

Although this is not a long PR, but I decided to split this into two PRs because  PrometheusResource is a new feature aligned with SPARK-23429 (which is added at 3.0.0). That will make the review easier.

Sorry for this change~


World import system

...accepting the format from the export system.

Might want to define an alternate format, which is less JSON-y and more markdown-y. Would have to support export and import for both formats.

Sometimes people want to import a single room (into an existing room or a new one). Allow this.


page.hover seemingly not working

To reproduce:
https://github.com/kemicofa/deno-puppeteer-hover-example
I'm trying to cause a color change on hover over one of the buttons on my website
From:

To:

However, through deno-puppeteer the color stays the same using the following code:
const browser = await puppeteer.launch();
const page = await browser.newPage();

const url = 'https://sweet-snake-49.deno.dev';
await page.goto(url);
await page.setViewport({
    width: 1600,
    height: 1200
});
await page.hover('#left');
await page.screenshot({ path: Deno.cwd() + '/example.png' });

await browser.close();

Closing as this issue is also happening in a nodejs project.


26 develop initial interface

A first version of the initial interface is created. It still necessary to improve code structure (see issue https://github.com/sergiomrebelo/evo-poster/issues/34) and evaluation (see issue https://github.com/sergiomrebelo/evo-poster/issues/36).

If you really want me to comment on them, you should try and leave them open for a bit longer...

I'm not sure it's a good idea to include fonts in the repository. They load the repo a lot, can't really be reviewed, and they can easily be lazily loaded from th eweb. You need to consider the license, too, and include it in the repository.

The typefaces that I selected are open source and available freely on the web. Do you know if there is a way of automatically downloading the files, from the production folder? I think that this can be a nice solution. Anyway, people can download it from the web easily. I can also remove them.

I'm not sure it's a good idea to include fonts in the repository. They load the repo a lot, can't really be reviewed, and they can easily be lazily loaded from th eweb. You need to consider the license, too, and include it in the repository.

The typefaces that I selected are open source and available freely on the web. Do you know if there is a way of automatically downloading the files, from the production folder? I think that this can be a nice solution. Anyway, people can download it from the web easily. I can also remove them.

You can probably use rollup for that. But I don't think it's worth the while to do either. It's going to give you a marginal speed gain, since they will be served from your disk, and only if you do it locally. Google CDNs are going to be faster that whatever you use for hosting in production.


Testing results

Hi Mahmoud,
For my work, one of my tasks is to reproduce the results mentioned in your paper. For this, I am testing the provided pre-trained model on the INETL-TAU dataset (7022 images) with m=7. Since the images are already black-level subtracted as mentioned on the dataset website, I am directly passing resized PNG images (384×256) to the model along with corresponding .json files (illuminant information). I am also using cross-validation but without the G multiplier for testing.  My obtained results are as: Mean: 2.61, Median: 1.77, Best25: 0.57, Worst25: 1.44, Worst05: 2.16, Tri: 1.95, and Max: 28.39.
There is slight variation in results except the Worst25 which has a lot. As per my understanding, one reason could be the random sample selection nature of cross-validation. Is it so? or is there any other important step, I am missing?
Another thing to be mentioned, during the test I didn't mask out the color checker present in the scenes that you mentioned in the paper. Could you please provide details on it, how you did that? Because I think for the masking the coordinates for the color checker in each scene should be known.

Hi,
Thanks for the update. Now the obtained results are almost the same.
However, there is another question. The provided pre-trained model is trained on data_num (m)=7. Does this mean that for testing the data_num should explicitly be equal to 7? Because if I put data_num less or greater than 7, I get the error "RuntimeError: Error(s) in loading state_dict for network:".
Can you please clarify? should the model be trained and tested on the same value of data_num?
Also how encoder blocks are being generated. For example, from visualization in the paper, it appears that for m images encoder blocks will be m.

Yes testing should be performed using the same m, which refers to the number of additional histograms randomly selected + the input histogram. m=7 means we use 6 additional histograms. The number of encoders are equal to m.

Dear Mahmoud,
Thanks for the previous response.
I want to train the model with m=1 (only a single image) on the NUS and Gheleri-Shi datasets without proposed data augmentation. To train the model the input can be either 16-bit or 8-bit but as per your response to one question here on GitHub, it is recommended to use 16-bit which should be black-level normalized. I have a few questions and it would be very kind of you to clear them so that I can start with model training.
Pre-processing of input to model for training:

For black level normalization of the NUS dataset both the black_level and saturation are provided for each camera hence for the normalization I am using: (image-black_level)/(saturation-black_level), following your response to one of the questions, here on GitHub. With this since the pixel range changes to: 0 to 1 hence cv2.imwirte clips them to zero i.e. the resultant image is zero. To avoid this I am normalizing the black-level normalized image to 16-bit (cv2.normalize(normalized_image, dst=None, alpha=0, beta=65535,norm_type=cv2.NORM_MINMAX, dtype=cv2.CV_16U)). I want to ensure this approach is fine i.e. will it affect the training? or is there any other way you have utilized to avoid this nature of cv2.imwrite?

For the Gheleri-Shi dataset:

RGB values for illuminant are given I think these need to be normalized using r+g+b for the json files.
Also, only black-level values are provided for both cameras (saturation is missing or at least couldn't be found) so in that case how has black_level normalization been applied? One way is to use the provided Matlab file in the dataset for removing the black_level (canon1d has 0 and canon5d has 129 black_level value).
Apart from that, this dataset has 12-bit images as described on the dataset website. So should images be normalized to 16-bit or 8-bit after black_level removal as the C5 expects an input of 16 or 8-bit.

Model training on m=1 without data augmentation technique

To start with this as per my understanding only the value of data_num is supposed to be kept to 1 for training the model keeping other parameters default as defined in the script training.py. Is there anything else I should consider?
Is it possible to compare the results of such a model (trained on NUS and Gheleri-Shi dataset with m=1 without data augmentation) to be sure that the ones I will obtain are accurate so that further steps can be taken for my work?

Sorry for the too-detailed questions.
I will be very grateful to you for answering these.


fix(deps): update module github.com/onsi/gomega to v1.35.0

This PR contains the following updates:

Package
Type
Update
Change

github.com/onsi/gomega
require
minor
v1.34.2 -> v1.35.0

Release Notes

onsi/gomega (github.com/onsi/gomega)
v1.35.0
Compare Source
1.35.0
Features

You can now call EnforceDefaultTimeoutsWhenUsingContexts() to have Eventually honor the default timeout when passed a context.  (prior to this you had to expclility add a timeout) [e4c4265]
You can call StopTrying(message).Successfully() to abort a Consistently early without failure [eeca931]

Fixes

Stop memoizing the result of HaveField to avoid unexpected errors when used with async assertions. [3bdbc4e]

Maintenance

Bump all dependencies [a05a416]

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

1 additional dependency was updated

Details:

Package
Change

google.golang.org/protobuf
v1.34.2 -> v1.35.1


Add hook on componentDidMount to scrollToIndex

Fix for #9, proposed at #10

Awesome! Thanks man. 👍

👍

@zachgibson are you able to push a new release?

Yeah I published to npm already.

Damn, i'm having a hard time with this. Can you give me an example to make it work? I have the same visual problem that the #9.
Here is my code :
class PrlxSwiper extends React.Component {
  constructor(props) {
    super(props);
    this.state = {scrollToIndex:1};
  }
  myCustomAnimatedValue = new Animated.Value(0);
  render() {
    console.log("PrxSwiper");
    return (
    <ParallaxSwiper
      ref ={(psref) => {if(this.state.prlxSwiperRef == null){this.setState({prlxSwiperRef:psref});}}}
      scrollToIndex = {this.state.scrollToIndex}
      speed={0.60}
      animatedValue={this.myCustomAnimatedValue}
      dividerWidth={8}
      dividerColor='rgb(0, 132, 153)'
      backgroundColor="red"
      showsHorizontalScrollIndicator={false}
      showProgressBar={false}
      onMomentumScrollEnd={(index)=>{
        console.log("Mise a jour de index");
        if(this.state.scrollToIndex != index){
          this.setState({scrollToIndex:index});
        }
      }}
    >
      {Stacks.map((stack, index) => (
        this.StackPageRendering(stack.key, index)))}
    </ParallaxSwiper>
    );
  }```

I'm a beginner in React-Native so yeah... thanks you!

@gabgagnon What are you trying to do?

I am trying to make the initial index of the parralax Swiper at index 1 instead of 0, but it result to a glitchy view where I only see half of the image. I tried it with the example of the project and the same bug happen. If you can show me an example with the initial state at 1, it would be fantastic!!

So, I found an solution. I wish to keep it to myself like the little Gollum that am I but the solution is pretty simple :)
I added
componentDidUpdate() {
    const { scrollToIndex } = this.props;
    if (scrollToIndex) {
      setTimeout(() => {
        this.scrollToIndex(scrollToIndex, true);
      });
    }
  }

inside ParallaxSwiper.js. I know that this is not the best for some people because the Swiper will always go to the current Index but it solved my problem. :)


Eloquent dev

Basic Info

Info
Please fill out this column

Ticket(s) this addresses
Ticket https://github.com/srl-freiburg/pedsim_ros/issues/48

Primary OS tested on
Ubuntu 18.04 ROS2 Eloquent

Robotic platform tested on
Gazebo simulation of Tutlebot3

Description of contribution in a few bullet points

I migrated pedsim_ros package to ROS2 eloquent.
Agents positions are published as a new frame in the TF tree now, pedsim_tf2 package.
I changed pedsim_visualizer to publish spencer_messages instead of pedsim_msgs because spencer_tracking_rviz_plugin in ROS2 needs that the publisher and the subscription have the same msg type.
I have changed pedsim_visualizer to walls are only published once.
I have added two parameters in pedsim_visualizer, frame_id and walls_resolution. Using walls_resolution you can create more accurate scenarios, it is especially useful for home or industrial scenarios.
I have updated .gitmodules file to point to my spencer forks working on ROS2. I will do the PR in the spencer repos ASAP.

Future work that may be required in bullet points

It is necessary to migrate all launchers.
Support the dynamic reconfiguration.
Update the .gitmodules files to point the original repos in an eloquent branch.

Hi and thanks for the big pull request! I haven't worked with ROS2 yet, so I am curious why you changed the header file extensions (e.g. in pedsim_simulator) from .h to .hpp. Is there a technical requirement in ROS2 / ament that mandates that?

Hi @tlind!
It is a general guideline established by the OSRF and the ROS2 contributors, following the C++ style (.hpp and .cpp) instead of C style (.h and .c). You can check it in the migration guides, for example in the migration guide for rviz to rviz2.


ROSA(4.14) needs support for 7th generation general purpose (m7i), memory optimized(r7i) and compute optimized instance types(c7i)

Which service is this feature request for?
Red Hat OpenShift Service on AWS
What are you trying to do?
Provision cluster utilising M7i or r7i or c7i instance types for worker, infrastructure or master nodes
Describe the solution you'd like
Test OCP 4.14 against m7i, r7i, c7i instance types and update documentation including them as tested instance types

Describe alternatives you've considered
Can customers claim support when they use M7i, r7i, c7i instance types in ROSA as worker, master or infrastructure nodes?
Additional context
Customer will get to leverage latest Intel Xeon 4th generation processors and get better price/performance

@arendej , Can you please link it with any other existing issue already under Development or assign a milestone?

#119

@arendej , I guess this is ready to be closed unless you see something is pending.

@arendej, @wgordon17, Kindly close this issue, I can see these instance types available on https://docs.openshift.com/rosa/rosa_architecture/rosa_policy_service_definition/rosa-instance-types.html


Slider resize issue when changing screen mode

I have the following slider:

        <input type="range" min="0" max="8" value="0" data-rangeslider data-orientation="vertical">
        <output></output>

          Mbps

As you can see the max value is 8.  When I'm in full screen mode, the slider button goes passes 8 ( not in value just position. This only happens when I'm in full screen mode. When I'm in  a smaller window size, or start from a smaller window size and then transition to full screen mode the issue does not persist.  Here is an image:

What exactly do you mean with full screen mode?
Browser > view > Enter Full Screen

or are we talking about https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API

The former. When you go to full screen mode directly in the browser. The issue is there in both Chrome and Safari (10.1.2).

Can you reproduce it with this example as well?

The link doesn't work.

Damn! There you go https://codepen.io/andreruffert/full/meeOav/


Фардзинов Максим Аланович P33222

Changelog entry
...
Changelog category

New feature
Experimental feature
Improvement
Performance improvement
Bugfix
Backward incompatible change
Documentation (changelog entry is not required)
Not for changelog (changelog entry is not required)

Additional information
...

lgtm


Add support for setting owner of MountableFile, default to root

Commons compress changed the default behavior of tar users and groups in 1.21.

1.20 and below, entries default to the root user and group.
1.21, entries default to the current user and group, see https://github.com/apache/commons-compress/blob/d57b8e9068bc0184b783aa488e613f4fcf2140d6/src/changes/changes.xml#L153-L157

This means that testcontainers bumping the dependency to 1.21 caused files uploaded via copyFileToContainer to be owned by the host user rather than root.
This PR:

Reinstates root as the default user. I don't think there are many situations where it makes sense to default to the current user, as that is unlikely to correlate with the user in the container. This is a breaking change, but one where we undo a previous accidental breaking change.
Adds support for MountableFile to select a different user.

Some CI tasks are failing, but before we investigate further, can you please rebase on master and perform ./gradlew :testcontainers:spotlessApply?


Improve the handling of QSL icons

This makes mod icons effectively per-library, while Mod Menu's parent now has an icon, which is stored in the mandatory Quilt Base API
I'd test this, but due to a lack of fat jars (which will be addressed by QFAPI), I couldn't be able to do that

I really should have tested it before PRing


chore: factorize implementation of messages checksum method

They all have the same implementation, so it can be done by internally calling a generic function that lives in message/lib.rs and that accept anytype as long as it implement deserializeToWriter

when there is no payload, keep the hardcoded checksum tho


Explain how Dataplane lifecycle works

People always get confused and we should clarify this documentation. How are dps cleaned up? What are the different levers with configuration?

Split DPs and Datamodel in 3:

Data plane proxy
Data planes on Kubernetes
Data planes on Universal


Generate populatedb_data.json from modified database

What I'm trying to achieve
If I run populatedb and try to overwrite the populatedb_data.json file with the version that results from python manage.py dumpdata product I firstly, get different files. Second, if there have been no modifications to the sample data that is generated, the generated json file is still unable to be processed by the populate db script.
Steps to reproduce the problem
python manage.py populatedb --createsuperuser
python manage.py flush
python manage.py dumpdata product > saleor/static/populatedb_data.json

What I expected to happen
python manage.py populatedb --createsuperuser  # Should result in no errors

What happens on my end
Random fields are missing, fields have different outputs (i.e. weight is "1.0:kg" instead of "1.0 kg") etc...

populatedb_data.json wasn't expected to work out of the box with dumpdata command; it was generated with some additional flags if I remember correctly. I agree it would be helpful to have some easy way to update the file. But this file is really meant for our "demo" data and it's not intended to be used in any other way. Why do you need to use this file and not just dump data to some other json file and load it from there?

@maarcingebala We are using the populatedb command on our end to be able to easily test on demo data as well. We totally can just dump the whole database and load it back in but saw using this as the more correct way to programmatically seed the database for testing. (similar to rake db:seed in rails) If you could pass along the flags for generating that file, that would be much appreciated!

My mistake - I asked @IKarbowiak who made some changes in that file recently and it seems we were using the same command as you wrote. There is an issue with weights, but you also said some random fields are missing - what fields? Maybe we've made some changes in models that were not reflected in populatedb_data.json?

I'm not sure why the files are not invariant. I've added the output of the command and linked it to a gist below. There is around a ~1k line difference between what is generated and what exists in master right now. I started to go through and try to edit the random_data file to properly parse my output but paused to check-in to see if maybe I was generating the file incorrectly. (the file was generated using the command listed above)
https://gist.github.com/adithyabsk/caf28403039596a15e74a0b688d9e314

We've investigated the issue and the main problem is that after adding warehouses models (#4986) we didn't change the data file, but only the populatedb to keep working with an outdated file. I would consider it a bug - the exported data should include warehouses and stock info.

@maarcingebala Got it, so in the meantime if I'm looking to repeatably load sample data for our system, what approach would you suggest. Should I simply just dump the database and load that back in? We're just looking for a an approach that can be extended as we modify our sample data.

@adithyabsk Yes, in this case I would recommend using dumpdata and loaddata.

Okay, I can go that route as a stopgap. @maarcingebala any idea how high this lands on your priority list? (so I can figure out an eta from our end)

@maarcingebala I fixed the bug downstream, if you would like to accept the change, I've created a PR to fix the issue: https://github.com/mirumee/saleor/pull/5500


Fix Structured Data Classification type

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Resource registry

The Resource Registry allows for ansible services to register shared resources that are required to be maintained in sync between each other. This PR implements the Resource Registry and it's corresponding API endpoints.
Resource Registry
Service can register resources using the ResourceRegistry object provided by this PR. An example implementation can be found here: https://github.com/ansible/aap-gateway/pull/170/files.
Resources API
Models registered as resources can be managed via the new resources API. This API includes the following new endpoints
/resources/
CRUD operations for resources. Resources can be updated here using a transaction to allow for two phase commits.
Example: create resource using transaction:
POST /resources/
{
    "resource_type": "shared.organization",
    "resource_data": {"name": "my third organization"},
    "transaction_id": "967be504-f8ea-42a8-a1e1-68ea98a05331"
}

Example: resource list
GET /resources/?resource_type=shared.user

{
    "count": 1,
    "next": null,
    "previous": null,
    "results": [
        {
            "object_id": "1",
            "name": "admin",
            "ansible_id": "f1ab4457:306152bc-8146-4605-9360-adaa310af646",
            "resource_type": "shared.user",
            "is_externally_managed": false,
            "shared_resource_type": "user",
            "resource_data": {
                "username": "admin",
                "email": "admin@localhost",
                "first_name": "",
                "last_name": "",
                "is_superuser": true,
                "is_system_auditor": false
            },
            "detail_url": "[/api/gateway/v1/users/1/](https://localhost/api/gateway/v1/users/1/)",
            "url": "[/api/gateway/services/self/resources/f1ab4457:306152bc-8146-4605-9360-adaa310af646/](https://localhost/api/gateway/services/self/resources/f1ab4457:306152bc-8146-4605-9360-adaa310af646/)"
        }
    ]
}

/resource-types/
List available resource types on the service
GET /resource-types/

{
    "count": 4,
    "next": null,
    "previous": null,
    "results": [
        {
            "id": 1,
            "resource_type": "shared.organization",
            "externally_managed": false,
            "shared_resource_type": "organization",
            "url": "[/api/gateway/services/self/resource-types/shared.organization/](https://localhost/api/gateway/services/self/resource-types/shared.organization/)"
        },
        {
            "id": 2,
            "resource_type": "shared.user",
            "externally_managed": false,
            "shared_resource_type": "user",
            "url": "[/api/gateway/services/self/resource-types/shared.user/](https://localhost/api/gateway/services/self/resource-types/shared.user/)"
        },
        {
            "id": 3,
            "resource_type": "shared.team",
            "externally_managed": false,
            "shared_resource_type": "team",
            "url": "[/api/gateway/services/self/resource-types/shared.team/](https://localhost/api/gateway/services/self/resource-types/shared.team/)"
        },
        {
            "id": 4,
            "resource_type": "aap.servicecluster",
            "externally_managed": false,
            "shared_resource_type": null,
            "url": "[/api/gateway/services/self/resource-types/aap.servicecluster/](https://localhost/api/gateway/services/self/resource-types/aap.servicecluster/)"
        }
    ]
}

/transactions/
Commit or rollback pending transactions

GET /transactions/: list pending transactions.
POST /transactions/<id>/commit/: commit the selected transaction.
POST /transactions/<id>/rollback/: rollback the selected transaction.
POST /transactions/<id>/flush_transactions/: rollback all pending transactions and release their database locks.

Thanks for spearheading the effort. I would like to try to get the transaction management bits into an Minimum Viable Product demo with AWX as soon as possible. We have ansible_base added as a requirement now https://github.com/ansible/awx/pull/14705 so we can just switch to the branch and experiment. Code is needed on the AWX side, but showing this would really help shore up the contract needed with the app that's using this. At the first level, we could mock the requests coming from Gateway. I'm really interested to see what that API contract will be looking like, and get broader feedback on it.

I'm a bit confused by service_id. Currently service_id looks like what AWX calls INSTALL_UUID; it uniquely identifies an AWX installation cluster, lives in the DB across upgrades/migrations.
I maybe expected service_id to be stable per service_type. Since service_type is a string and unique I imagined the service_id being generated via hash(service_type). This would limit 1 service of any given type in a registry, but that reflects the reality of this being a library. This also aligns with gateways restriction of 1 service of any given type.
^^ I actually like service_id be being like INSTALL_UUID. But shouldn't each service tell gateway their chosen service_id? I reckon it's not strictly a requirement. Gateway can reach into the service's api to discover their service_id once the service is registered.

I think I understand the usage of postgres prepared transactions in this PR. But I don't think I understand the greater problem they are attempting to solve. Let me see if I can describe the problem.
Gateway will be the source of truth for Organizations. An Organization that is created in Gateway will be synced to other services (Controller, and Hub for example). The semantics for "synced" is where the problem comes in. What is the "synced" guarantee? We have decided that we prefer ConsistencyAP. This is the problem statement.
Now for solutioning. We decided that Gateway will ensure consistency. For the Org creation example, Gateway will use the Resource API to create the Org in both Controller and Hub. Doing so will generate a transaction in each service. At this point I see a problem. For the happy path, Gateway needs to do two things

Create the new Org in it's DB
COMMIT the pending transaction on Controller and Hub

Which does Gateway do first, which does it do second? Either way, you can get into an inconsistent state when a failure happens.

In the aap-gateway PR associated with this PR that shows the usage of this new resource registry, you register a ServiceCluster without an associated shared_resource. What is the use case for this?

@chrismeyersfsu This was intended for use by the two phase commit protocol (https://en.wikipedia.org/wiki/Two-phase_commit_protocol). Basically:

Create a new org in each service in a transaction.
Wait for each service to ACK the transaction.
If all the services ACK the transaction, send a separate API request to commit it.
If any service fails to ACK, rollback the transaction on each service.

Sadly we can't use this because prepared transactions aren't enabled by default in Postgres and per @matburt we don't have a guarantee that we can change the postgres config in every environment, so I will be removing this feature before we merge the PR.

Two phase commit requires the second phase to have an atomic commit. The separate API request(s) are where you want/need an atomic commit and it doesn't exist.
Let's say you have Gateway, Hub, and Controller.

If all the services ACK the transaction, send a separate API request to commit it.

All services ACK
commit API request SUCCCESS to Hub
commit API request FAIL Controller

If any service fails to ACK, rollback the transaction on each service.

Abort Controller
Rollback Hub <-- Say hub isn't contactable by Gateway. The system is now in a state where Hub has the resource created and thinks everything is OK.

The root of the problem is that there isn't a system wide ATOMIC commit NEEDED for the 2-phase commit to work.

@newswangerd are we going to implement ansible collection for resources? Does it make sense?

I have concerns about the resource API in general.   I am not sure a new API is needed that abstracts over the existing data types.   If we can add ansible_id UUIDs to the existing APIs then we might not need a separate API at all and we can use the existing APIs.

@AlanCoding I'll fix up the documentation, and then I think this should be good to merge.


How to use setFullScreenOnly

Can you explain how to use setFullScreenOnly in README example?
When do I need to call it?

@xvonabur sure, here

@ghondar , link is broken. Github returns 404

@xvonabur updated

Thanks!


sf project convert mdapi removes comment placeholders from objectTranslation files

Summary
sf project convert mdapi is removing comment placeholders from objectTranslation files.  This causes errors in the subsequent deploy.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

with object translations in src/objectTranslations, the translation file contains:
<picklistValues> <masterLabel>Aging with Dignity</masterLabel> <translation><!-- Aging with Dignity  --></translation> </picklistValues>
Run sf project convert mdapi --root-dir src --output-dir source
check any translation file in the new source folder.  And see the translation is now:
<picklistValues> <masterLabel>Aging with Dignity</masterLabel> <translation></translation> </picklistValues>

Expected result
Expected the file to match what was in the source folder:
<picklistValues>    <masterLabel>Aging with Dignity</masterLabel>    <translation><!-- Aging with Dignity  --></translation> </picklistValues>
Actual result
<picklistValues>     <masterLabel>Aging with Dignity</masterLabel>     <translation></translation> </picklistValues>
This results in a deployment/validation error:
Invalid picklist value: Aging with Dignity in field: Contact.NRI_Interest_Tagging_Journeys__c
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
cmd.exe

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version --verbose --json

{
"cliVersion"<EMAIL_ADDRESS>"architecture": "win32-x64",
"nodeVersion": "node-v18.16.0",
"osVersion": "Windows_NT 10.0.19044",
"shell": "C:\Program Files\Git\usr\bin\bash.exe",
"rootPath": "C:\Progra~1\sfdx\sf",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.1.9 (core)",
"@oclif/plugin-commands 2.2.14 (core)",
"@oclif/plugin-help 5.2.9 (core)",
"@oclif/plugin-not-found 2.3.23 (core)",
"@oclif/plugin-plugins 2.4.7 (core)",
"@oclif/plugin-search 0.0.16 (core)",
"@oclif/plugin-update 3.1.13 (core)",
"@oclif/plugin-version 1.3.3 (core)",
"@oclif/plugin-warn-if-update-available 2.0.36 (core)",
"@oclif/plugin-which 2.2.19 (core)",
"@salesforce/cli 1.77.1 (core)",
"apex 2.2.14 (core)",
"auth 2.7.14 (core)",
"data 2.3.12 (core)",
"deploy-retrieve 1.8.18 (core)",
"info 2.6.8 (core)",
"limits 2.3.13 (core)",
"login 1.2.7 (core)",
"org 2.7.2 (core)",
"schema 2.3.10 (core)",
"settings 1.4.5 (core)",
"sobject 0.1.18 (core)",
"source 2.10.5 (core)",
"telemetry 2.1.6 (core)",
"templates 55.4.11 (core)",
"trust 2.4.12 (core)",
"user 2.3.9 (core)"
]
}
Additional information
This also happens if I run with sfdx:
{
"cliVersion": "sfdx-cli/7.199.7",
"architecture": "win32-x64",
"nodeVersion": "node-v18.16.0",
"osVersion": "Windows_NT 10.0.19044",
"shell": "C:\Program Files\Git\usr\bin\bash.exe",
"rootPath": "C:\Progra~1\sfdx",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.1.9 (core)",
"@oclif/plugin-commands 2.2.14 (core)",
"@oclif/plugin-help 5.2.9 (core)",
"@oclif/plugin-not-found 2.3.23 (core)",
"@oclif/plugin-plugins 2.4.7 (core)",
"@oclif/plugin-search 0.0.16 (core)",
"@oclif/plugin-update 3.1.13 (core)",
"@oclif/plugin-version 1.3.3 (core)",
"@oclif/plugin-warn-if-update-available 2.0.36 (core)",
"@oclif/plugin-which 2.2.19 (core)",
"apex 2.2.14 (core)",
"auth 2.7.13 (core)",
"community 2.2.11 (core)",
"custom-metadata 2.1.17 (core)",
"data 2.3.11 (core)",
"deploy-retrieve 1.8.18 (core)",
"info 2.6.8 (core)",
"limits 2.3.13 (core)",
"org 2.7.2 (core)",
"packaging 1.16.8 (core)",
"schema 2.3.10 (core)",
"settings 1.4.5 (core)",
"signups 1.4.13 (core)",
"source 2.10.6 (core)",
"telemetry 2.1.6 (core)",
"templates 55.4.11 (core)",
"trust 2.4.12 (core)",
"user 2.3.9 (core)",
"sfdmu 4.26.13 (user)",
"sfdx-cli 7.199.7 (core)",
"sfdx-git-delta 5.19.0 (user)"
]
}

Hello @vandyk-nw, thanks for the issue. I think I know what is happening here. We recently updated our XML parser to a new major version. There is some configuration that needs to be done to support comments. Could you please put together a quick repository that reproduces this issue with translations on picklist values so that I can be certain the fix works? You can start with a fork of Dreamhouse if that is easier. Thanks

Adding some additional context here so that it does not get lost. Both the XMLParser and XMLBuilder in SDR will need the commentPropName option added (docs). However in some quick testing, I am worried that inline comments are not going to work well. For example:
<label><!-- a comment -></label>
transforms into
<label>
    <!-- a comment -->
</label>

I am worried the newlines will cause issues, this is why I am wanting a sample repo with objectTranslations so that we can properly test this.


Investigate the delay between the call starting ITDE returns and the Docker DB becomes connectable

Apparently, there is 10-20 seconds delay.
At the very least this should be documented. Ideally, we should implement some sort of status pinging and display an hourglass until the DB becomes connectable.

@ahsimb , please retest this and close if the problem does not persist anymore.
Otherwise, please elaborate situation in detail. @tkilias and @ckunki both think this should not be possible.

Yes, this is something we don't see now.


related slides and presentations

A place to post related slides and presentations
CMDpipeline.pptx

Full presentation I gave at Columbia 12/01/2016.
2016-11-24_Columbia_curatedMetagenomicData.pptx


frame_size fixed

if got_frame is not set, set frame_size to 0.

@freerdp-bot test

@uplusplus what kind of issue does your pull solve?

In case of len>0 and got_frame==0,
if  frame_size is not assigned to 0,   invalid data will be copied into dst.

@freerdp-bot test


[Question] Retrieve Skype user profile picture

Can the Skype user profile picture (the user who's chatting with the bot) be retrieved using Bot Framework. I don't see any documentation related to the same.

@indiandragon Are you using .NET or Node.js SDK?

@nwhitmont Hi, I'm using Node.js SDK.

Not currently a feature of the BotBuilder SDK. You would need to query the Skype API directly.
see: https://superuser.com/a/860803

@nwhitmont Thanks for the confirmation, I assume the Skype API could use authentication via botframework to get the profile. But considering, there's no way to obtain original skype id via botframework; obtaining user profile picture is not possible.
Considering all other bot platforms provide user profile picture, is this planned for future?