set_base_prng_seed does nothing to prng state as viewed by fn passed to with_test_contract_frame

What version are you using?
2674d867d7c6aa4212abab05ff30e5804ff1db90
What did you do?
Called set_base_prng_seed before using the prng inside a function passed to with_test_contract_frame.
What did you expect to see?
I expected to see calling set_base_prng_seed to change the results I get back from the prng.
What did you see instead?
No change. Setting the base prng seed appears to have no impact on contract code running inside a with_test_contract_frame.
Example
This is an example written in the SDK. The call to as_contract calls with_test_contract_frame with the given function.
#[test]
fn test_prng_seed() {
    let e = Env::default();
    e.host().set_base_prng_seed([0; 32]).unwrap();
    let id = e.register_contract(None, TestPrngContract);
    e.as_contract(&id, || {
        assert_eq!(e.prng().u64_in_range(0..=90), 78);
    });

    let e = Env::default();
    let id = e.register_contract(None, TestPrngContract);
    e.host().set_base_prng_seed([2; 32]).unwrap();
    e.as_contract(&id, || {
        assert_eq!(e.prng().u64_in_range(0..=90), 78);
    });
}

cc @anupsdf

Ok this is .. slightly strange.

If I write a version of this test that draws, say, decently-large byte buffers from each PRNG, no problem, they differ.
If I write a version of this test exactly as written (drawing only one number and clamping it to a tiny range) then they collide!
If I expand the range from 0..90 to 0..900, they .. don't collide anymore, but they're also still surprisingly close numbers (776 and 779)
if I expand the range even more (0.9000) they are still close, and "closer" as a percentage (7760 and 7786)

This is perplexing enough that I need to look into it more. It seems like there's really intense bias in at least the first byte out of the PRNG, or at least when doing uniform sampling.

Digging in a little more, I'm not sure whether this is happening in the Uniform sampler (biasing the number by doing wrong arithmetic) or if it's a phenomenon arising from bytes coming out of ChaCha itself. The bytes look kinda different in the "array of decimals" sense, but if you interpret the first 8 bytes out as a little-endian u64 (i.e. with the high byte of the u64 coming from the 8th byte out) they are uncomfortably similar-looking bit patterns (arising from bytes 220 vs. 221 in the output byte sequence):
buf1: [105, 12, 228, 36, 199, 57, 187, 220, 255, 181, 66, 167, 114, 167, 73, 136, 126, 229, 99, 124, 156, 9, 231, 42, 211, 148, 110, 234, 189, 179, 224, 119]
buf2: [236, 190, 9, 126, 102, 199, 118, 221, 202, 82, 42, 176, 45, 33, 101, 151, 75, 175, 29, 114, 10, 213, 208, 105, 207, 35, 93, 191, 15, 224, 13, 72]

u64 LE:<PHONE_NUMBER>6469238889
u64 LE:<PHONE_NUMBER>2649090796

u64 LE bits: 1101_1100_1011_1011_0011_1001_1100_0111_0010_0100_1110_0100_0000_1100_0110_1001
u64 LE bits: 1101_1101_0111_0110_1100_0111_0110_0110_0111_1110_0000_1001_1011_1110_1110_1100

Well, I've opened https://github.com/stellar/rs-soroban-env/pull/1232 which does something that seems not-entirely-unsupported by the evidence I can find. But I'm not especially certain about it. Comments welcome.


Startup script does not fail if the order of the arguments is incorrect #125

Fixes #125
Startup script fixed so it correctly returns an error when an argument is unknown.

Could you provide a shell command we can execute to compare the master version with this branch?


Fix false-positive validation for Swift initializer returns value documentation

Bug/issue #, if applicable: rdar://134552183
Summary
This fixes a false positive validation about the return value documentation for Swift initializers.
The function signature information in the symbol graph specifies that these initializers don't have a return value. However, from the caller's perspective they have a "conceptual" return value that there's sometimes a reason to document (for example to describe the situations when a failable initializer returns nil).
Dependencies
None
Testing
Document the return value of a Swift initializer. For example:
public struct Something {
    /// - Returns: Some description.
    public init() {}
}

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[ ] ~Updated documentation if necessary~ Not necessary

@swift-ci please test


fix the parsing of the response of the PadWalker version request

The version string was previously retrieved improperly which made getPadwalkerVersion wrongly report that PadWalker is not installed.

thanks @rgeorgiev583 but tests are failing due to missing padwalker version - could it a change in per DB or padwalker providing another output?


Can't run firestore-algolia-search in bash script

Hello everyone,
I've been trying to run the restore script for firestore-algolia-search. According to other issues, decided to run it from a bash script:
#!/bin/bash

LOCATION=us-central1\
PROJECT_ID=project-id\
ALGOLIA_APP_ID=111111\
ALGOLIA_API_KEY=111111\
ALGOLIA_INDEX_NAME=index\
COLLECTION_PATH=path\
FIELDS=fields\
GOOGLE_APPLICATION_CREDENTIALS=./key.json\
npx firestore-algolia-search

But then the output is firestore-algolia-search: command not found . I'm writing this issue here because other npx script would work in bash scripts. npx is installed globally and the command is working outside of bash (but no with parameters  declared beforehand)
Thanks a lot

What was the solution for this? I am having this issue


qu seems to remove the player skin overlay

everything works in singleplayer, skin overlay is only gone when i join a server, even if this server has this mod, idk why it does happen.
without qu

with qu

it took a long time 'till i found it, tried also to disable every mods besides qu and fabric-api to see if it might be a conflict with another mod but.. sadly nope.
tried it also with cloth config enabled and disabled.
1.20.1, non-specific server, but i tested it on a fabric server, the other server should have been a modless server.

That's very strange. My mod doesn't touch skin overlays. The only thing it does on the rendering side is allow horse armor to have enchantment tint. I'll look into this and see if I can reproduce.

That's very strange. My mod doesn't touch skin overlays. The only thing it does on the rendering side is allow horse armor to have enchantment tint. I'll look into this and see if I can reproduce.

yes, i also wondered why a enchanting mod touches skins, but if you cant reproduce i'll also can look again and make a video what and how exactly i do (not really much, just putting the mod in and starting mc lol)

I just created my own independent server and joined it, my skin's overlay was there and functioning, so as of right now I can't reproduce. Was this your skin or another player's skin that wasn't displaying right?
Also could you send me what other mods you were using alongside it?

I just created my own independent server and joined it, my skin's overlay was there and functioning, so as of right now I can't reproduce. Was this your skin or another player's skin that wasn't displaying right?
Also could you send me what other mods you were using alongside it?

that's weird, well it's my skin and the skin from other ppl, so everyone hasn't the skin overlay.
https://youtu.be/HXICC-iEDaQ
more information: modrinth, fabric & quilt, their apis (for quilt the quilt ones for farbic the fabric one) + cloth config.
unmodded server. 1.20.1
also removed flags just in case, didn't help.
i'll have an idea, i'll test something, but this could take me another 10-20 minutes.
i'll use graalvm ee, could break mods but never happened to me maybe until now? back in a few minutes

Yeah idk. My setup was functionally similar. Is there anything in the MC logs that show any sort of rendering error?
Also you shouldn't need to manually have cloth config, it's bundled into my mod now.

idk if those are the right logs, i would need some guidance to provide better informations
also some mods still use cloth config, isn't the ressource usage higher when having cloth config and a mod that also has it bundled into it? i also seem switching to yetanotherconfig because cloth doesn't won't (let me lie) fix some of it's issues?
[15:41:46] [main/INFO]: Loading Minecraft 1.20.1 with Fabric Loader 0.14.22
[15:41:46] [main/INFO]: Loading 59 mods:
	- cloth-config 11.1.106
	   \-- cloth-basic-math 0.6.1
	- fabric-api 0.87.0+1.20.1
	   |-- fabric-api-base 0.4.30+7abfd51577
	   |-- fabric-api-lookup-api-v1 1.6.35+4d8536c977
	   |-- fabric-biome-api-v1 13.0.10+b3afc78b77
	   |-- fabric-block-api-v1 1.0.9+e022e5d177
	   |-- fabric-blockrenderlayer-v1 1.1.40+b3afc78b77
	   |-- fabric-client-tags-api-v1 1.1.1+97bb207577
	   |-- fabric-command-api-v1 1.2.33+f71b366f77
	   |-- fabric-command-api-v2 2.2.12+b3afc78b77
	   |-- fabric-commands-v0 0.2.50+df3654b377
	   |-- fabric-containers-v0 0.1.63+df3654b377
	   |-- fabric-content-registries-v0 4.0.9+b3afc78b77
	   |-- fabric-convention-tags-v1 1.5.4+a1a980da77
	   |-- fabric-crash-report-info-v1 0.2.18+aeb40ebe77
	   |-- fabric-data-generation-api-v1 12.2.2+1e61dba177
	   |-- fabric-dimensions-v1 2.1.53+8536527b77
	   |-- fabric-entity-events-v1 1.5.22+b3afc78b77
	   |-- fabric-events-interaction-v0 0.6.1+e91849a877
	   |-- fabric-events-lifecycle-v0 0.2.62+df3654b377
	   |-- fabric-game-rule-api-v1 1.0.38+b04edc7a77
	   |-- fabric-item-api-v1 2.1.27+b3afc78b77
	   |-- fabric-item-group-api-v1 4.0.10+23d9108177
	   |-- fabric-key-binding-api-v1 1.0.36+fb8d95da77
	   |-- fabric-keybindings-v0 0.2.34+df3654b377
	   |-- fabric-lifecycle-events-v1 2.2.21+b3afc78b77
	   |-- fabric-loot-api-v2 1.1.39+b3afc78b77
	   |-- fabric-loot-tables-v1 1.1.43+9e7660c677
	   |-- fabric-message-api-v1 5.1.7+3265161977
	   |-- fabric-mining-level-api-v1 2.1.49+b3afc78b77
	   |-- fabric-model-loading-api-v1 1.0.2+709a987177
	   |-- fabric-models-v0 0.4.1+9386d8a777
	   |-- fabric-networking-api-v1 1.3.10+eeb8eb3677
	   |-- fabric-networking-v0 0.3.50+df3654b377
	   |-- fabric-object-builder-api-v1 11.1.1+6beca84877
	   |-- fabric-particles-v1 1.1.1+201a23a077
	   |-- fabric-recipe-api-v1 1.0.20+b3afc78b77
	   |-- fabric-registry-sync-v0 2.3.2+4df89eb277
	   |-- fabric-renderer-api-v1 3.1.2+6bdb2ed077
	   |-- fabric-renderer-indigo 1.4.2+6bdb2ed077
	   |-- fabric-renderer-registries-v1 3.2.45+df3654b377
	   |-- fabric-rendering-data-attachment-v1 0.3.34+b3afc78b77
	   |-- fabric-rendering-fluids-v1 3.0.27+b3afc78b77
	   |-- fabric-rendering-v0 1.1.48+df3654b377
	   |-- fabric-rendering-v1 3.0.7+b3afc78b77
	   |-- fabric-resource-conditions-api-v1 2.3.5+ea08f9d877
	   |-- fabric-resource-loader-v0 0.11.9+132c48c177
	   |-- fabric-screen-api-v1 2.0.7+b3afc78b77
	   |-- fabric-screen-handler-api-v1 1.3.29+b3afc78b77
	   |-- fabric-sound-api-v1 1.0.12+b3afc78b77
	   |-- fabric-transfer-api-v1 3.3.0+cdf060b277
	   \-- fabric-transitive-access-wideners-v1 4.3.0+6c31357e77
	- fabricloader 0.14.22
	- java 17
	- minecraft 1.20.1
	- qu-enchantments 1.3.6-1.20
	   |-- com_github_llamalad7_mixinextras 0.1.1
	   \-- mm 2.3
[15:41:46] [main/INFO]: SpongePowered MIXIN Subsystem Version=0.8.5 Source=file:/C:/Users/{COMPUTER_USERNAME}/AppData/Roaming/com.modrinth.theseus/meta/libraries/net/fabricmc/sponge-mixin/0.12.5+mixin.0.8.5/sponge-mixin-0.12.5+mixin.0.8.5.jar Service=Knot/Fabric Env=CLIENT
[15:41:47] [main/INFO]: Compatibility level set to JAVA_16
[15:41:47] [main/INFO]: Compatibility level set to JAVA_17

Do a trail run where you log into the server and observe the bug, then quit. In your Minecraft instance folder (In the modrinth app, you can find "open folder" when you click on the instance), go to logs then upload latest.txt. Uploading the file would be better than copying and pasting.

latest.log

I believe I see what could be causing it. Though I'm not entirely sure if there's much I can do about it.  Have you tried connecting to a vanilla server? Or a server that also only has my mod active and nothing else?

I believe I see what could be causing it. Though I'm not entirely sure if there's much I can do about it.  Have you tried connecting to a vanilla server? Or a server that also only has my mod active and nothing else?

none, no mods, i did also try with only fabric api than with qu-enchant and fabric api and than fabric, cloth, qu
there also are different servers i joined, every time there was no skin overlay, i'll try a paper server.

I guess I should explain what the primary cause seems to be.
java.lang.IllegalStateException: Invalid entity data item type for field 9 on entity class_746['ReiWasHere'/271, l='ClientLevel', x=-6.50, y=82.00, z=0.50]: old=0(class java.lang.Byte), new=20.0(class java.lang.Float)
	at net.minecraft.class_2945.method_12785(class_2945.java:204) ~[client-intermediary.jar:?]
	at net.minecraft.class_2945.method_12779(class_2945.java:191) ~[client-intermediary.jar:?]
	at net.minecraft.class_634.method_11093(class_634.java:529) ~[client-intermediary.jar:?]
	at net.minecraft.class_2739.method_11808(class_2739.java:46) ~[client-intermediary.jar:?]
	at net.minecraft.class_2739.method_11054(class_2739.java:10) ~[client-intermediary.jar:?]
	at net.minecraft.class_2600.method_11072(class_2600.java:22) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_18859(class_1255.java:156) ~[client-intermediary.jar:?]
	at net.minecraft.class_4093.method_18859(class_4093.java:23) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_16075(class_1255.java:130) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_5383(class_1255.java:115) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1523(class_310.java:1175) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1514(class_310.java:802) ~[client-intermediary.jar:?]
	at net.minecraft.client.main.Main.main(Main.java:250) ~[1.20.1-0.14.22.jar:?]
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:468) ~[fabric-loader-0.14.22.jar:?]
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) ~[fabric-loader-0.14.22.jar:?]
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23) ~[fabric-loader-0.14.22.jar:?]
[19:46:14] [Render thread/INFO]: Loaded 2 advancements
[19:46:14] [Render thread/ERROR]: Error executing task on Client
java.lang.IllegalStateException: Invalid entity data item type for field 17 on entity class_746['ReiWasHere'/271, l='ClientLevel', x=-6.50, y=82.00, z=0.50]: old=0(class java.lang.Integer), new=127(class java.lang.Byte)
	at net.minecraft.class_2945.method_12785(class_2945.java:204) ~[client-intermediary.jar:?]
	at net.minecraft.class_2945.method_12779(class_2945.java:191) ~[client-intermediary.jar:?]
	at net.minecraft.class_634.method_11093(class_634.java:529) ~[client-intermediary.jar:?]
	at net.minecraft.class_2739.method_11808(class_2739.java:46) ~[client-intermediary.jar:?]
	at net.minecraft.class_2739.method_11054(class_2739.java:10) ~[client-intermediary.jar:?]
	at net.minecraft.class_2600.method_11072(class_2600.java:22) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_18859(class_1255.java:156) ~[client-intermediary.jar:?]
	at net.minecraft.class_4093.method_18859(class_4093.java:23) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_16075(class_1255.java:130) ~[client-intermediary.jar:?]
	at net.minecraft.class_1255.method_5383(class_1255.java:115) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1523(class_310.java:1175) ~[client-intermediary.jar:?]
	at net.minecraft.class_310.method_1514(class_310.java:802) ~[client-intermediary.jar:?]
	at net.minecraft.client.main.Main.main(Main.java:250) ~[1.20.1-0.14.22.jar:?]
	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:468) ~[fabric-loader-0.14.22.jar:?]
	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74) ~[fabric-loader-0.14.22.jar:?]
	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23) ~[fabric-loader-0.14.22.jar:?]

Something is causing desynced mod loading on either the client or server, which when the client tries to sync the world entities, including the player, with the server, its causing mismatches in several fields. This does seem to have funky rendering effects.
So basically, I believe connecting to a server that has my mod running on it would see it be fine. Connecting to a server that doesn't have my mod loaded possibly would result in this mismatch as the client is expecting to populate some of my mods fields but the server doesn't supply it.
But you say that connecting to a server with my mod installed as well still has the issue?

everything works in singleplayer, skin overlay is only gone when i join a server, even if this server has this mod, idk why it does happen.

yes, i did try it with the mod on my server

Could you grab the log file when you connect to your server that has my mod installed and upload it?

alright it works, idk what happened BUT, if i have multiple mods on my server, without the client-side only mods it seems to also happen? and it does cache it? i need to look further into it i think, seems i had a brain fart

btw just in case, i would like to put in the mod list here, where do i get the text format of which mods are in?

nah idk, i did setup it again carefully and it seems to work now, maybe an outdated file, cannot be but who knows..
or i forgot to put in a lib/api/config on my client (some don't get auto-downloaded and do not get names in the logs until i put those mods on the server), maybe i had a lib/config/api on the server but not on my client, but it would be weird, since this weird owo-lib would tell me that there's a missmatch. (and than there's also something called cache)
i'm gonna close this issue for now.
thank you for taking your time, much appreciated!


Fix NoMethodError on Ruby 3.2

Hi there!
Thank you for the gem 😄 Here's a very small (1 char) PR which fixes the face that Ruby has now deprecated the File.exists? method.
See this commit
I replaced it with File.exist? which does exactly the same thing.
Thanks!
Nik

Hey @nikz,
Thanks for the contribution! Published v1.2.3 with this fix.

Awesome, thanks for doing that so quickly @kirillplatonov!


Release a new version containing "add test run autoсlosing"

Hi,
When all tests in the run pass, it is preferable to auto close the run to avoid extra manual interventions.
A human would only need to make manual interventions when one or more of the tests failed so only then leaving the run open make sense.
The autoclose feature is already added, can you simply release it to PyPI?

@tlvu has been released


Added documentation for the newly added methods.

Hi @chemerisuk, here comes the documentation of the newly added methods. I kept it the same style as you did on your other firebase plugins. Cheers!

@JulianSanio thank you sir!

You're welcome :)


Runboat label

Super low priority at this stage, but we probably need a label controller to add it to the repo's readme, like we have on runbot

There is a PR for that in the OCA add-ons repo template. Not sure we need a dedicated controller, though


Incorrectly stating a valid URL is invalid

Issue exists where overlapping suffixes aren't handled correctly, and state URL as invalid.
For example:
gov.uk - valid URL since "gov" is the sld, and ".uk" is the tld.  However, this incorrectly states the URL is invalid, since "gov.uk" is also a tld in its own right (e.g. "data.gov.uk", where "data" is the sld and "gov.uk" is the tld).
Same goes for other overlapping tlds, such as github.io.

Hi @willigogs, apologies for the delay in getting back to you.
I noticed that psl.parse('github.io') (for example) would result in the following object:
{ input: 'github.io',
  tld: null, // this was wrong!
  sld: null,
  domain: null,
  subdomain: null,
  listed: true }

I have now updated psl.parse so that you should get:
{ input: 'github.io',
  tld: 'github.io', // note that `tld` is now set to `github.io`
  sld: null,
  domain: null,
  subdomain: null,
  listed: true }

On the other hand, psl.isValid('github.io') will return false, because the domain is not under a public suffix, github.io is the suffix itself. By definition, a "public suffix" is one under which Internet users can directly "register" names, and a valid domain name will be one that is a "subdomain" of a public suffix.
Does this address the issue?


Code hands on backtest when dates are added.

Hi there,
As the title says, it hangs, never finishes, when I use this:
from oanda_bot import Bot

class MyBot(Bot):
    def strategy(self):
        rsi = self.rsi(period=5)
        ema = self.ema(period=10)
        lower = ema - (ema * 0.001)
        upper = ema + (ema * 0.001)
        self.buy_entry = (rsi < 40) & (self.df.C < lower)
        self.sell_entry = (rsi > 60) & (self.df.C > upper)
        self.sell_exit = ema > self.df.C
        self.buy_exit = ema < self.df.C
        self.units = 1000 # currency unit (default=10000)
        self.take_profit = 20 # take profit pips (default=0 take profit none)
        self.stop_loss = 10 # stop loss pips (default=0 stop loss none)

MyBot(
    account_id='<acc id>',
    access_token='<token>',
    instrument='USD_JPY',
    granularity='H1', # 1 hour candlestick
).backtest(from_date="2020-12-31", to_date="2021-1-31", filename="backtest.png")

When I CTRL+C, it returns this:
Traceback (most recent call last):
  File "F:\...\advancedBacktest.py", line 18, in <module>
    MyBot(
  File "F:\Python3\...\oanda_bot.py", line 380, in backtest
    self._candles(from_date=from_date, to_date=to_date)
  File "F:\Python3\...\oanda_bot.py", line 125, in _candles
    time.sleep(0.5)
KeyboardInterrupt

If I run without time constraints, it runs to completion in a matter of seconds.
Any ideas what the issue might be?

Hi biochemman!
I was having a similar issue, and if you removed filename="backtest.png option the code will complete with the included date range.
Something like .backtest(from_date="2020-07-07", to_date="2020-07-21") worked for me. I could then save the file (if wanted) from the Matplotlib visualization.
I'm haven't dug into any of the possible underlying causes, but that solved it in the short term for me.

Hi biochemman!
I was having a similar issue, and if you removed filename="backtest.png option the code will complete with the included date range.
Something like .backtest(from_date="2020-07-07", to_date="2020-07-21") worked for me. I could then save the file (if wanted) from the Matplotlib visualization.
I'm haven't dug into any of the possible underlying causes, but that solved it in the short term for me.

That worked, many thanks!

That worked, many thanks!


Upgrade react-user-feedback extension to 1.0.9

Description
Improves some internals and build processes, no outward changes that we currently use.
Keeping up with the head of the extension's development, because it is not officially stable, and we are one of its earliest consumers.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
Manual testing and CI

The UI tests failed on master: https://github.com/stackrox/stackrox/actions/runs/4891147511/jobs/8731299850
Could we give this another look?
(I noticed that this test started failing on another branch after rebasing)


Explicity include OpenCV header file <opencv2/opencv.hpp>

… without which, the luck of include-file ordering can otherwise make using this file problematically nondeterministic

Thanks for noticing


No polish diacritic symbols ĄĘŁŃÓŚŻŹ ąęłńóśżź

NO model can generate Polish diacritical marks
ĄĘŁŃÓŚŻŹ ąęłńóśżź

From a few tests, it seems like the models are generally bad at writing non-ascii or uncommon characters, including e.g. these Polish diacritical marks, German Umlauts, French accents, Greek letters, and mathematical symbols

That models cope badly (not sure why) with non-ascii or uncommon characters is what I know. The question is when there will finally be a model that can handle it. We have been waiting for this for several years.


Form for leaving comments

Under the current website, we do not have a form and potential customers have to send an email. Instead we could have a form  clients can leave queries and or feedback.

This from will have to take Name, Email, Phone Number (optional), Message. Also it should have a submit button and a cancel or reset button.

The name, email and message should not be empty. So when clicking submit it should do form validation for those fields.

Also for handling the form and other information this is the goto place; https://www.gatsbyjs.org/docs/building-a-contact-form/

Challenge here will be to find a way to send the emails in a reliable and cost efficient manner since we don't have a server. :smile:

We'll close this for now since we are doing it at OpenLearnr (https://github.com/OpenArchitex/OpenLearnr/issues/391). But we'll revisit this when the client wants to have this here. :smile:


Getting this error after cloning from this repo

'Simple Face Recognition App.exe' (CLR v4.0.30319: DefaultDomain): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\mscorlib\v4.0_<IP_ADDRESS>__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 Symbols loaded.
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Windows.Forms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_<IP_ADDRESS>__b03f5f7f11d50a3a\System.Drawing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\Users\nikol\Source\Repos\Simple-Face-Recognition-App-CS4\Simple Face Recognition App\bin\Debug\Emgu.CV.World.dll'. Module was built without symbols.
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Exception thrown: 'System.IO.FileNotFoundException' in Emgu.CV.World.dll
An unhandled exception of type 'System.IO.FileNotFoundException' occurred in Emgu.CV.World.dll
File '{0}' not found
'Simple Face Recognition App.exe' (CLR v4.0.30319: Simple Face Recognition App.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_<IP_ADDRESS>__b77a5c561934e089\System.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Unhandled Exception: System.IO.FileNotFoundException: File '{0}' not found
at Emgu.CV.CascadeClassifier..ctor(String fileName)
at Simple_Face_Recognition_App.Form1..ctor() in C:\Users\nikol\Source\Repos\Simple-Face-Recognition-App-CS4\Simple Face Recognition App\Form1.cs:line 28
at Simple_Face_Recognition_App.Program.Main() in C:\Users\nikol\Source\Repos\Simple-Face-Recognition-App-CS4\Simple Face Recognition App\Program.cs:line 19
The program '[18708] Simple Face Recognition App.exe' has exited with code 0 (0x0).

You have missing dependencies


Add .spec.ignoreMissingValuesFiles to HelmChartTemplate API

This PR introduces the option to ignore missing values files referenced in generated HelmCharts. Full backward compatibility is maintained.
I can't see any meaningful surface to test, as this is simply exposing underlying functionality from the source-controller API.
Depends upon https://github.com/fluxcd/source-controller/pull/1447

@stefanprodan : will you create a new release tag on github.com/fluxcd/source-controller/api (v1.3.0?) so that I can update go.mod and get the tests passing?


Syntax error in a map with if expression without brackets

When using an if expression in a map without brackets it is reported as a problem while it's a valid XPATH expression:

XPath: Expression context - unexpected token here [line,column]

where [line,column] in this example points to the last colon
<xsl:variable name="example" select="map {
      'a' : if (true()) then 1 else 2,
      'b' : 2
  }"/>

A workaround is to use brackets around the if expression:
  <xsl:variable name="example" select="map {
      'a' : (if (true()) then 1 else 2),
      'b' : 2
  }"/>

Thanks for reporting this issue, it appears related to how the ifElse expression is handled which I'm already seeking to improve. I'll report back when I have more.

This issue has been fixed in Release 0.3.16


feat(create-turbo): support bun (beta)

Description
Support bun in create-turbo and turbo/workspaces. This will allow users to start from any example using bun as a package manager.
Requires https://github.com/vercel/turbo/pull/5934
Tasks still TODO:

[x] Bun specific tests
[x] Validation when converting to bun (bun only supports single level globs, so not all projects can be converted to bun workspaces, we need to check this)

Related to https://github.com/vercel/turbo/issues/4762

@mehulkar yep turbo core won't work with bun yet until @nathanhammond's PR lands (this PR does not include that one, but it is marked as required in the description)


2 new options

Option to turn off the head unit LCD display
Option to turn on Frost Protection (FP mode), it allows heating to 10 deg C.

The LCD switch is already added to the plugin. You can enable it in the config.

Ok I will give it a try thanks
I see FP is discussed here in the midea_ac_lan group also:
https://github.com/georgezhao2010/midea_ac_lan/issues/141

Ok I tried just about every combination of true/true, true/false, false etc.
Do have have the correct parameter?
"switchDisplay": {
"flag": true,
"command": true
},
What values would I set to turn off the LED display after a change, or have it off completely?

What do mean? The flag field decides if a switch will be created in the Home app or not. The command field is only need to be set to true if the switch does nothing when it's on false (which is the default).

ok mabe I missunderstood, I'm looking for the option in the config to chnage the LED :)

Well I'm a idiot! I had some how reenable the old plugin! I see see the 2 extra switches now and everything works!


Pydantic Validation Errors for QA response

It appears that Brave API has changed the Web Response making several fields optional in the QA response spec.  The current Pydantic model defines answer as a str, which doesn't appear to be the case for some responses.  I'm playing around with a submitting a PR if I can get it sorted, but I wanted to bring up the issue in case someone else is also working on it.
pydantic_core._pydantic_core.ValidationError: 3 validation errors for WebSearchApiResponse
web.results.0.qa.title
  Field required [type=missing, input_value={'question': 'uvicorn is ...ra', 'upvoteCount': 44}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.6/v/missing
web.results.0.qa.url
  Field required [type=missing, input_value={'question': 'uvicorn is ...ra', 'upvoteCount': 44}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.6/v/missing
web.results.0.qa.meta_url
  Field required [type=missing, input_value={'question': 'uvicorn is ...ra', 'upvoteCount': 44}}, input_type=dict]
    For further information visit https://errors.pydantic.dev/2.6/v/missing

@kayvane1 I submitted PR #26 to fix this issue.  I did quite a few tests and this PR fixed all the issues I was running into.  Happy to discuss if you'd like.  Let me know.


Inconsistent check on EVP_PKEY_new

@mattcaswell
Referring to https://github.com/openssl/openssl/issues/7374#issuecomment-429918919, here is another example that somewhere check is done in function while in another locations an additional check is done at the parent level as well:
https://github.com/openssl/openssl/blob/master/apps/dsa.c#L224
pk = EVP_PKEY_new();
if (pk == NULL)
goto end;
EVP_PKEY_set1_DSA(pk, dsa);
https://github.com/openssl/openssl/blob/master/apps/rsa.c#L272
pk = EVP_PKEY_new();
EVP_PKEY_set1_RSA(pk, rsa);
pk is checked inside EVP_PKEY_assign which is called inside both EVP_PKEY_set1_DSA and EVP_PKEY_set1_RSA
Thank you!

Neither of these are "wrong" exactly - just inconsistent. The explicit check in the "dsa" app looks more obvious to me (i.e. it is not obvious that there is a redundant check in EVP_PKEY_set1_DSA()), so I prefer that approach.

I second Matt's opinion on preferring the approach used for DSA.
@Bugcheckers would you be so kind to open a PR to "fix" the code in apps/rsa.c to conform to the style used in apps/dsa.c?

Thank you guys @mattcaswell @romen for your comments!
I provided a pull request.
Thanks!


waypoint_planner/velocity_set fails to avoid hitting a stationary object while making a turn

Bug report
Required information:

Operating system and version: Ubuntu 18.04
Autoware installation type: Docker image autoware/autoware:1.14.0-melodic-cuda, as specified in the Dockerfile of https://github.com/carla-simulator/carla-autoware at commit 975b6f3.
Autoware version or commit hash - 1.14.0
ROS distribution and version:

ROS Melodic (pre-installed in the docker image)

ROS installation type:

Pre-installed in the docker image

Description of the bug

I am running Autoware 1.14.0 (docker image: autoware/autoware:1.14.0-melodic-cuda), Carla <IP_ADDRESS> (docker image: carlasim/carla:<IP_ADDRESS>) as a simulator and carla-autoware-bridge at 975b6f3 as a bridge.

When a curved path is partially blocked by a stationary object, the ego-vehicle stops too late and hits the object.

velocity_set seems to be setting the stop line based on the location of the obstacle, not considering the width of the ego-vehicle.
This is alright if the obstacle is straight ahead. However, at a curve, the stop line is too deep, making the ego-vehicle stop too late.

Please refer to the diagrams below.

When the object is far enough, ego-vehicle drives without crashing (obviously) - cases (a) and (b).
When the object is close enough, ego-vehicle stops (again, obviously) - cases (e) and (f).
This bug is only observed when the object is placed at a moderate distance where the ego-vehicle would attempt to turn - cases (c) and (d).

Please refer to the Front-facing camera, rear-facing camera and rosbag for detailed analysis.

velocity_set configuration

  <include file='$(find waypoint_planner)/launch/velocity_set.launch'>
    <arg name='use_crosswalk_detection' default='false' />
    <arg name='points_topic' default='points_no_ground' />
    <arg name='velocity_offset' default='4' />
    <arg name='decelerate_vel_min' default='1.3' />
    <arg name='remove_points_upto' default='0.5' />
    <arg name='enable_multiple_crosswalk_detection' default='true' />
    <arg name='stop_distance_obstacle' default='15.0' />
    <arg name='stop_distance_stopline' default='5.0' />
    <arg name='detection_range' default='1.3' />
    <arg name='points_threshold' default='10' />
    <arg name='detection_height_top' default='2.5' />
    <arg name='detection_height_bottom' default='-1.7' />
    <arg name='deceleration_obstacle' default='1.5' />
    <arg name='deceleration_stopline' default='0.6' />
    <arg name='velocity_change_limit' default='15' />
    <arg name='deceleration_range' default='0' />
    <arg name='temporal_waypoints_size' default='100' />
  </include>

Steps to reproduce the bug

Replay the rosbag file attached above.

Expected behavior
Ego-vehicle should stop before an obstacle.
Actual behavior
Ego-vehicle stops late, hitting an obstacle.

@squizz617 Please see our support guidelines for how to get support for Autoware.ai. This should start with a post to ROS Answers with the autoware tag. If this results in a confirmed bug, it can then be escelated to an issue here.


Generate Hover, Focused, Disabled Button Background from theme.palette.action...

This is an question regarding v1.0
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Hi folks.
Hi @oliviertassinari
in line https://github.com/mui-org/material-ui/blob/103ab9b535a1724c5c394f0b3b48190446ed27c9/packages/material-ui/src/Button/Button.js#L129
there is theme.palette.primary.dark used as hover color.
Do you think we could utilize the theme.palette.action.hover value instead and use a backgroundImage to complement the theme.palette.primary.main color?

@valorize We are discussing how we can update the implementation to match the specification in #9526.


Tutorials behave strangely if you restart after clearing a section

If you clear a tutorial section and quickly restart, the tutorial will behave strangely, restarting from the middle of the tutorial.
This is because we're using yield statements which don't reset their state when the tutorial resets. We shouldn't use yield statements, we should use something like timers.

Upgraded to a priority 2 -- this is no longer a rare edge case, others in the community are running into it as well. In some cases it soft locks their games.


AVPro Video Trial not exposing MediaPlayer to SDK?

Describe the issue
I have downloaded the free trial of AVPro Video and added both that package and the Vimeo Unity SDK to a demo scene. The Vimeo SDK doesn't seem to recognise the existence of the player, since I cannot select it as my main Video Player in the [VimeoPlayer] component.
We would like to stream Vimeo Live via the combination of these two packages in a Unity Scene (AR, eventually). Any ideas on what is going wrong?
Steps to reproduce the problem

New Unity project

add Vimeo SDK

add AVPro Video free trail package

VimeoPlayer GameObject doesn't have a Video Player prop to switch to the MediaPlayer from AVPro Video

(see my screenshot for the current setup)

Unity version
v2018.1.4f1
Operating system
macOS High Sierra 10.13.6

That's very odd. As soon as the MediaPlayer is added to your project, the Vimeo Plugin should automatically detect it.
What is happening behind the scenes is that we are using the AssetPostprocessor to automatically add a custom define in your Unity project. This define tells the VimeoPlayer to expose a new option in the GUI.
See: https://github.com/vimeo/vimeo-unity-sdk/blob/master/Assets/Vimeo/Scripts/Editor/VimeoPlugin.cs#L20
We tested it locally and it is working well in 2018.2.1f1 and 2018.1.6f1.
Can you try manually adding VIMEO_AVPRO_VIDEO_SUPPORT to your list of defines and see what happens?

@caseypugh thanks for the quick reply.

Hi - I am having the same issue, AvPro video not being a player option after installing the vimeo sdk in a project. When I create a NEW project, yes, it works. However I don't quite understand how to make it work in the existing project with the vimeo SDK. You mentioned adding VIMEO_AVPRO_VIDEO_SUPPORT to the list of defines. How does one do that?
I'm attaching a screenshot showing that I have the SDK installed yet the player is not an option.
I'm using Unity version 2018.3.0f2 Personal.

Thanks,
Jonathan


Too high memory and cpu usage

Issue Type: Bug
RAM usage is more than 3GB without any files open and CPU usage is 30-40%.
VS Code version: Code 1.21.0 (9a199d77c82fcb82f39c68bb33c614af01c111ba, 2018-03-07T11:01:43.521Z)
OS version: Linux x64 4.14.24-1-MANJARO

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz (4 x 3467)

Load (avg)
2, 2, 2

Memory (System)
7.69GB (0.12GB free)

Process Argv
/opt/visual-studio-code/code

Screen Reader
no

VM
0%

Extensions: none
Reproduces without extensions

Pls have a look at https://github.com/Microsoft/vscode/wiki/Performance-Issues. This helps us tracking down the problem.

I'm also getting this issue recently, the code helper uses almost 2GB of memory with one file open. This is with all the extensions disabled.
System:
macOS High Sierra MacBook Pro (Retina, 13-inch, Early 2015)
CPU: 2.7GHz Intel Core i5
Memory: 8GB 1867 MHz DDR3

Same issue here, after I open a JS file the extension sub-process "typescript-language-features" appears, which uses 2GB ram and >40% CPU usage.
Version 1.22.2
Date 2018-04-12T16:34:44.222Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
Ubuntu: 17.10
CPU: 2.20GHz Intel Core i7
Memory: 8GB

Closing, as https://github.com/Microsoft/vscode/issues/45357#issuecomment-371684450 was never answered. New issues should be filed as such.


Move dataset related fixtures to conftest.

So that we can avoid the chain of unused imports in test files

not super cool that dataset.conftest stuff is used in test modules/packages level(s) up, but it's for another PR.
Indeed some of the fixtures should be pushed up one more level but I want to wait for another pr to do that


Alerts via DzVents

          I will further investigate the speed issue.

Maybe off topic, but I will create a script in dzvents to give me the same alerts Life360 gives me, when someone is arriving and leaving a named place stored in the locations file. Maybe someone already did this ?
Just asking, can I post the script somewhere for testing... here or other topic ?
Originally posted by @Sloeber71 in https://github.com/TurnOfAFriendlyCard/Domoticz-GPSLogger-Plugin/issues/6#issuecomment-2033626804

I am testing my script in the field... Looks promising. No more bugs so far.
The goal is to provide the same kind of alerts that Life360 generates. Push to phone and/or email
Also included a counter for the TomTomAPI calls and provided a warning when requests reach more then 2300 calls. Reset is at midnight.
Created also a shell script to produce the needed script from the locations file.
Still testing and will start to document from next Monday. So first release would be next week on Friday.

That's great news. Once ready let's integrate into the functionality.

HI,
the script works and has been thoroughly tested and is ready for publication. I will publish all the necessary code here.

Just came back from holidays, so delayed response. Will wait for the script and integrate into the main solution with your name as reference of couse.


openshift-applier doesn't support ConfigMaps

Does it make sense for the openshift-applier to support configmaps?

@AndresAbdo the openshift-applier itself doesn't get involved with what's in the static, or template, files used with OpenShift, so you can easily have a ConfigMap in your files and apply it with the openshift-applier. Hope that make sense.

@rohanmars the openshift-applier does NOT do anything special for projects, deployments and builds. In fact, the openshift-applier is very very little hands on with anything as all it does is to process static files or templates with content... the content of these files can be any of the above, or a ConfigMap definition.
Please have a look at the sample inventories in the tests area for some examples if you haven't already looked. Also, in case I'm just misunderstanding your question, please elaborate on what kind of functionality you have seen for the above that you are wanting the ConfigMap to follow + provide an example of it.

@oybed, this is what I want todo within a seed-hosts.yml:
openshift_cluster_content:

object: configmap
content:

name: "apply configuration"
file: "{{ inventory_dir }}/../.openshift/config/dev-config.yml"

@jibbe yes, and you can do that as-is.  Have you tried it?

I tried it, doesn't work.

@jibbe @rohanmars I think maybe the main concept of the openshift-applier isn't understood here. The openshift-applier just takes a collection of files and process/apply them (or create). In essence, it would be like if you did these steps manually:
oc process -f file1.yml --params-file=param1 | oc apply -f -
oc process -f file2.yml --params-file=param2 | oc apply -f -
oc process -f file3.yml --params-file=param3 | oc apply -f -
oc create -f file4.yml
oc process -f file5.yml --params-file=param5 | oc apply -f -

But instead of doing these 5 steps manually (or through a bash script), it can be specified in an inventory which the openshift-applier iterates through and perform the process/apply or create. Hence, the openshift-applier does not have any knowledge itself around ConfigMaps, BuildConfigurations, Routes, etc. etc. It's pretty much as dumb as it can be and just loops over what you give it.

@oybed yes, that was our assumption.  We'll try an figure out why it didn't work. Unfortunately, you can't run a "oc process" on a configmap so not sure that makes sense.

@rohanmars @jibbe in case it helps, here's a quick example I just put together for ConfigMaps. This shows both a static ConfigMap as well as a template based ConfigMap:
Inventory:
openshift_cluster_content:
- object: configmap
  content:
  - name: "Create ConfigMap1"
    file: "{{ inventory_dir }}/../files/configmap1.yml"
    action: "create"
  - name: "Apply ConfigMap2"
    template: "{{ inventory_dir }}/../files/configmap2.yml"
    params: "{{ inventory_dir }}/../files/params2"

Files:
$ cat files/configmap1.yml
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: map1
data:
  foo1: bar1

$ cat files/configmap2.yml
---
apiVersion: v1
kind: Template
metadata:
  name: ConfigMap-Example
objects:
- kind: ConfigMap
  apiVersion: v1
  metadata:
    name: map2
  data:
    foo1: "${VALUE}"
parameters:
- name: "VALUE"
  displayName: "The Value"

$ cat files/params2
VALUE=file-value-2

Post openshift-applier run:
> oc get configmap
NAME      DATA      AGE
map1      1         5m
map2      1         3m

>oc get configmap map1 -o yaml | grep -A1 '^data:'
data:
  foo1: bar1

> oc get configmap map2 -o yaml | grep -A1 '^data:'
data:
  foo1: file-value-2

Note the action: create on the static file - as documented here: https://github.com/redhat-cop/openshift-applier/blob/master/roles/openshift-applier/README.md#override-default-actions-with-action

Okay great @oybed . We'll try that, I think the "action: create" was the missing piece.
Thanks.

The create shouldn't be needed (I've successfully run without it), but it is good to know about in case you need to do such an override. apply is the default, but in some rare cases it cannot be used (e.g.: ProjectRequest). For ConfigMaps, however, you should be able to just leave it at default apply.


Unit tests when ran together do not provide helpful information upon failure

When running unit tests together, like through the make unit-test command, the failure is difficult to find. The summary of the test results do not contain any information on which test(s) failed. For example:
There were failures detected in the following suites:
  config ./internal/mode/static/nginx/config

Test Suite Failed
exit status 1
make: *** [unit-test] Error 1

Although logs are printed, these are difficult to parse as they are extremely lengthy. The test failure is buried in this output and is hard to find.
=== NAME  TestExecuteMainIncludesConfig/complete_configuration
    main_includes_test.go:67:
        Expected
            <int>: 1
        to equal
            <int>: 0

Examples:

https://github.com/nginxinc/nginx-gateway-fabric/actions/runs/11019924001/job/30603633017?pr=2522

Acceptance Criteria:

Name of failed test is printed in an easy to find location
Stack trace is printed (if possible)

Dev Notes:

Issue started to occur when we started running all our unit tests with ginkgo. Can we just run our ginkgo tests using ginkgo and the rest of our tests with go test?
Running the tests in parallel has made fixing this issue more of a priority.

Opened https://github.com/onsi/ginkgo/issues/1461


do you have plan to release the base model?

Due diligence

[X] I have done my due diligence in trying to find the answer myself.

Topic
The paper
Question
In the paper, the audio generation model was trained on millions of hours of data and it seems this model is well capable of generating any voice and speaking styles, while the released models were only finetuned with a single speaker. Is there any plan to release the base model before finetuning? I think it will be very significant to have such a big model available for the TTS community, although I understand the ethical concerns and it may not be possible to release a model capable of high fidelity voice cloning.

The short answer is "not immediately". I agree with you that it would be very helpful for the community to release the whole model but also share the safety concerns that you mentioned so overall it's not entirely clear to us what the best way forward is. We have no plans on releasing the weights for the base model in the very near future but may well revisit if we believe it's a safe thing to do.


consistency between entering domains as lists or not

sometimes domains need to be entered as a list and sometimes they don't. make this consistent across classes.
potentially relax check on the variable r so that it's domain can be anyting (but keep check on r_n should be neg particle and same for r_p

Any idea where this fails other than in SpatialVariable?


Support for creating custom tokens without service account credentials

Currently the SDK must be initialized with service account credentials in order to be able to call FirebaseAuth.createCustomToken(). With this PR, the SDK will attempt to sign custom tokens by calling the IAM service in the cloud when the service account credentials are not provided.
// Following will work in GCP managed runtimes where the Metadata service is present
admin.initializeApp();
admin.auth().createCustomToken(uid).then(...);

// Following will work anywhere
FirebaseApp.initializeApp({
  // need to only specify the service account email here...
  serviceAccountId<EMAIL_ADDRESS>});
admin.auth().createCustomToken(uid).then(...);

As a part of this implementation I'm also refactoring the existing FirebaseTokenGenerator abstraction by removing all the token verification logic out of it.
go/firebase-admin-sign
go/firebase-admin-iam-sign

Resolves #224

I'm posting a decoded custom token generated against the master branch and this branch for comparison. Notice that other than the order of some claims (which has no significance in JSON and JWT), nothing has changed. During the last code review round I noticed that the typ header was missing which I have now added (interestingly, Firebase Auth did not fail on that).
Tokens decoded via https://jwt.io/
JWT Header
Before:
{
  "alg": "RS256",
  "typ": "JWT"
}

After:
{
  "alg": "RS256",
  "typ": "JWT"
}

JWT Body
Before:
{
  "claims": {
    "isAdmin": true
  },
  "uid": "testuser",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "aud": "https://identitytoolkit.googleapis.com/google.identity.identitytoolkit.v1.IdentityToolkit",
  "iss"<EMAIL_ADDRESS>  "sub"<EMAIL_ADDRESS>}

After:
{
  "aud": "https://identitytoolkit.googleapis.com/google.identity.identitytoolkit.v1.IdentityToolkit",
  "iat":<PHONE_NUMBER>,
  "exp":<PHONE_NUMBER>,
  "iss"<EMAIL_ADDRESS>  "sub"<EMAIL_ADDRESS>  "uid": "testuser",
  "claims": {
    "isAdmin": true
  }
}

Resolves #224


org.apache.solr.common.SolrException: Unknown query type 'bmax'

Hey Torsten,
My name is Satya. Sorry for reaching out to hear from Github.
I would like to use your plugin in my project.
And I did configure in schema.xml , solrconfig.xml exactly the way you directed in ReadMe.doc.
Once I place the jar(plugin) in solr/lib folder, I restarted the solr.
I tried to access the plugin by hitting this URL:
http://localhost:8983/solr/select/?q=dog&defType=bmax
But I am getting below error
org.apache.solr.common.SolrException: Unknown query type 'bmax'
can you please give me some urls(examples like query builders) to access the plugin.
Thanks in advance
@satyababu

Thanks for creating the issue and looking for the issue which I have.
Please let me know How I can achieve this problem.
And thanks for creating the plugin.
Thanks,
Satyababu

Sorry for the late answer, I'll add some examples to the project. this may take some days.

I added a simple example schema.xml and solrconfig.xml with a working bmax setup: https://github.com/shopping24/solr-bmax-queryparser/tree/master/src/test/resources/solr/collection1/conf

I close this issue by now. For further help, please create an new issue with a reference on this one.


Uncaught TypeError: feature.getStyle is not a function

TypeError: feature.getStyle is not a function
Select.applySelectedStyle_
/src/interaction/Select.js:410
407 |  * @private
408 |  */
409 | Select.prototype.removeFeatureLayerAssociation_ = function (feature) {

410 |     delete this.featureLayerAssociation_[getUid(feature)];
| ^  411 | };
412 | /**
413 |  * Handles the {@link module:ol/MapBrowserEvent map browser event} and may change the
View compiled
Select.addFeature_
/src/interaction/Select.js:381
378 | Select.prototype.applySelectedStyle_ = function (feature) {
379 |     var key = getUid(feature);
380 |     if (!(key in originalFeatureStyles)) {
381 |         originalFeatureStyles[key] = feature.getStyle();
| ^  382 |     }
383 |     feature.setStyle(this.style_);
384 | };
View compiled
Collection.Target.dispatchEvent
/src/events/Target.js:110
107 |     dispatching[type] = 0;
108 |     pendingRemovals[type] = 0;
109 | }
110 | ++dispatching[type];
| ^  111 | for (var i = 0, ii = listeners.length; i < ii; ++i) {
112 |     if ('handleEvent' in listeners[i]) {
113 |         propagate = /** @type {import("../events.js").ListenerObject} / (listeners[i]).handleEvent(evt);
View compiled
Collection.insertAt
src/Collection.js:203
200 |     this.array_.splice(index, 0, elem);
201 |     this.updateLength_();
202 |     this.dispatchEvent(new CollectionEvent(CollectionEventType.ADD, elem, index));
203 | };
| ^  204 | /*
205 |  * Remove the last element of the collection and return it.
206 |  * Return undefined if the collection is empty.
View compiled
Collection.push
https://localhost:3000/static/js/vendors~main.chunk.js:201006:10
201003 |   }
201004 |
201005 |   var n = this.getLength();
201006 |   this.insertAt(n, elem);
|        ^  201007 |   return this.getLength();
201008 | };
201009 | /**
View source
Collection.extend
src/Collection.js:140
137 |  * to the end of the collection.
138 |  * @param {!Array} arr Array.
139 |  * @return {Collection} This collection.
140 |  * @api
| ^  141 |  /
142 | Collection.prototype.extend = function (arr) {
143 |     for (var i = 0, ii = arr.length; i < ii; ++i) {
View compiled
Select.handleEvent
/src/interaction/Select.js:502
499 |             this.dispatchEvent(new SelectEvent(SelectEventType.SELECT, selected, deselected, mapBrowserEvent));
500 |         }
501 |         return true;
502 |     };
503 |     return Select;
504 | }(Interaction));
505 | /*
View compiled
▼ 3 stack frames were expanded.
Map.PluggableMap.handleMapBrowserEvent
node_modules/@corpsmap/corpsmap/lib/dev.js:45810
MapBrowserEventHandler.Target.dispatchEvent
node_modules/@corpsmap/corpsmap/lib/dev.js:6604
MapBrowserEventHandler.
node_modules/@corpsmap/corpsmap/lib/dev.js:42423
▲ 3 stack frames were expanded.

Replicable by fast clicking on different states.

TypeError: feature.setStyle is not a function
Select.restorePreviousStyle_
/src/interaction/Select.js:435
432 | // Replace the currently selected feature(s) with the feature(s) at the
433 | // pixel, or clear the selected feature(s) if there is no feature at
434 | // the pixel.

435 | clear(this.featureLayerAssociation_);
| ^  436 | map.forEachFeatureAtPixel(mapBrowserEvent.pixel,
437 | /**
438 |  * @param {import("../Feature.js").FeatureLike} feature Feature.
View compiled
Select.removeFeature_
/src/interaction/Select.js:392
389 | Select.prototype.restorePreviousStyle_ = function (feature) {
390 |     var interactions = this.getMap().getInteractions().getArray();
391 |     for (var i = interactions.length - 1; i >= 0; --i) {
392 |         var interaction = interactions[i];
| ^  393 |         if (interaction !== this &&
394 |             interaction instanceof Select &&
395 |             interaction.getStyle() &&
View compiled
Collection.Target.dispatchEvent
/src/events/Target.js:110
107 |     dispatching[type] = 0;
108 |     pendingRemovals[type] = 0;
109 | }
110 | ++dispatching[type];
| ^  111 | for (var i = 0, ii = listeners.length; i < ii; ++i) {
112 |     if ('handleEvent' in listeners[i]) {
113 |         propagate = /** @type {import("../events.js").ListenerObject} / (listeners[i]).handleEvent(evt);
View compiled
Collection.removeAt
src/Collection.js:260
257 |  * Set the element at the provided index.
258 |  * @param {number} index Index.
259 |  * @param {T} elem Element.
260 |  * @api
| ^  261 |  /
262 | Collection.prototype.setAt = function (index, elem) {
263 |     var n = this.getLength();
View compiled
Collection.remove
src/Collection.js:243
240 |     return undefined;
241 | };
242 | /
243 |  * Remove the element at the provided index and return it.
| ^  244 |  * Return undefined if the collection does not contain this index.
245 |  * @param {number} index Index.
246 |  * @return {T|undefined} Value.
View compiled
Select.handleEvent
/src/interaction/Select.js:497
494 |         features.remove(deselected[j]);
495 |     }
496 |     features.extend(selected);
497 | }
| ^  498 | if (selected.length > 0 || deselected.length > 0) {
499 |     this.dispatchEvent(new SelectEvent(SelectEventType.SELECT, selected, deselected, mapBrowserEvent));
500 | }
View compiled
▼ 3 stack frames were expanded.
Map.PluggableMap.handleMapBrowserEvent
node_modules/@corpsmap/corpsmap/lib/dev.js:45810
MapBrowserEventHandler.Target.dispatchEvent
node_modules/@corpsmap/corpsmap/lib/dev.js:6604
MapBrowserEventHandler.
node_modules/@corpsmap/corpsmap/lib/dev.js:42423
▲ 3 stack frames were expanded.

Also this error. Both are thrown simultaneously

i think this is in cm3 - i have seen it before. Is that right that it is in a cm3 js file?

The ultimate error is in ol. It's pointing to node_modules/ol/src/interaction/Select.js. The call did start from corpsmap though.

Could be from the async handling. I think the error has less chance of showing up when you click slower.

oy. Ok. Do you have a path to resolution on the bug? We could do a double click selection action which would change the code path (from our current single click action for selecting and downloading a state?

I was thinking of introducing a time delay between each selection or see if there's a way to refresh just the map component on error, but the double click could work too.

I was wrong, the issue was witch clicking on the VTL points


Fix curl header

Fixes #12
This uses the improved single quote escaper from #13 to fix #12

Any thoughts on this guy?


Display banner with cloud connection result

What type of Pull Request is this? (check all applicable)

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update

Describe your changes in brief
Checklist

[x] Tested locally
[ ] Added new dependencies
[ ] Updated documentation
[ ] Added tests

Related Issues

Related Issue #
Closes #

We could potentially include a specific error message in the banner when the connection fails.
It's not too much more work. Y'all can decide if that should be in this PR or on the backlog.


Replace aliased imports of logrus.

Replace all imports like:
log "github.com/Sirupsen/logrus"

with just
"github.com/Sirupsen/logrus"

and reformat files accordingly.

#dibs


Add tests

This PR adds tests for config flow.  Fixes #8
Some notes:

The aiotruenas-client library requirement now has to be included in requirements-dev.txt so that it brings it in for testing.  Bumps to this version now has to occur in two places.

In going to pin pytest-homeassistant-custom-component to version 0.1.0, which brings stability to your testing, or you can let it float which will alert you more quickly to changes in the upstream homeassistant testing library, but at the expense of more breakages in testing.  There are pros and cons to both approaches.

One question I had writing the tests since I'm unfamiliar with websockets, does InvalidURI capture all connection problems?  This reminds me that I should raise this error instead of the error that is reraised.
https://github.com/sdwilsh/hass-truenas/blob/9202bc8688c8dedbe6d65c835eecc13be91b5a0b/custom_components/truenas/config_flow.py#L38

One question I had writing the tests since I'm unfamiliar with websockets, does InvalidURI capture all connection problems?  This reminds me that I should raise this error instead of the error that is reraised.
https://github.com/sdwilsh/hass-truenas/blob/9202bc8688c8dedbe6d65c835eecc13be91b5a0b/custom_components/truenas/config_flow.py#L38

I don't know how familiar you are with the home assistant testing model, but these tests are essentially taken directly from the scaffold scripts from homeassistant/core.
See https://github.com/home-assistant/core/blob/dev/script/scaffold/templates/config_flow/tests/test_config_flow.py
This may aide in the review of the tests added.

I don't know how familiar you are with the home assistant testing model, but these tests are essentially taken directly from the scaffold scripts from homeassistant/core.
See https://github.com/home-assistant/core/blob/dev/script/scaffold/templates/config_flow/tests/test_config_flow.py
This may aide in the review of the tests added.

Apparently I wasn't watching my own repository, and therefore didn't get emails about this :)

Apparently I wasn't watching my own repository, and therefore didn't get emails about this :)


elm package install fails on Windows 10

I have this particular error when I try to launch a elm package install on Windows 10. I tried it on powershell, cmd and gitbash. Same results when I launched them as an administrator.
`elm-package install
Some new packages are needed. Here is the upgrade plan.
Install:
elm-lang/core 4.0.1
elm-lang/html 1.0.0
elm-lang/virtual-dom 1.0.2
evancz/elm-graphics 1.0.0
Do you approve of this plan? (y/n) y
Downloading elm-lang/core
elm-package.exe: elm-lang-core-fd9e702: MoveFileEx "elm-lang-core-fd9e702" "4.0.1": permission denied (Access is denied.)
`
Here is my elm-package.json :
{
"version": "1.0.0",
"summary": "Procedural Content Generation",
"repository": "https://github.com/FunkySoft45/elm-pcg.git",
"license": "BSD3",
"source-directories": [
"src"
],
"exposed-modules": [],
"dependencies": {
"elm-lang/core": "4.0.1 <= v < 5.0.0",
"elm-lang/html": "1.0.0 <= v < 2.0.0",
"evancz/elm-graphics": "1.0.0 <= v < 2.0.0"
},
"elm-version": "0.17.0 <= v < 0.18.0"
}
Any idea ? I know this particular problem has been discussed here in previous threads. But I couldn't find any suitable solution.

FYI - I am seeing similar errors on Windows 8.1 and elm package 0.17.0. The problem is intermittent and happens maybe 1 out of 4 times when adding a new package. When I get the error, I rerun "elm package install" again until it succeeds (usually on the first try).
This problem is similar to what was reported in issues: #139 and #23.

Sorry for the trouble. The way things are downloaded changed a bit with the 0.17.1 patch release that is out today, so this may be resolved.
If this can still happen with 0.17.1, please open a new issue with the print out from that.

FYI - I ran into the same intermittent errors using 0.17.1, but determined that the problem was being caused by a conflict between the iDrive cloud backup software (https://www.idrive.com/) that was running on my PC and elm-package.exe. The iDrive service was holding a handle open to a temporary file that elm-package.exe was trying to rename, causing the access denied errors. With iDrive's service stopped, I can no longer reproduce the errors.

Same issue in 0.18.0 caused by Dropbox. Worked immediately when I closed Dropbox before running elm-package install


LOG_TIME = ['/usr/bin/time', '-v'] in retdec-config.py option "-v" not valid on macOS

The version in /usr/bin/time on macOS does not accept the '-v' option. The workaround is to install gnu-time from homebrew which would then be under /usr/local/bin/gtime. If I get time, I may post a fix for this, but for now just reporting the issue.

This command gets used only with option --generate-log. This is an internal option that was not meant to be used by the users. I hid it in commit d871f1e. We use it in internal tests that run on Linux servers and track decompilator's time and memory consumption. It was never meant to be run on macOS or Windows.
This issue can stay open if someone wants to make it portable to macOS (send a pull request), but we (RetDec team) will not be fixing this ourselves.

Thanks for the response. I only came across this while debugging. I thought it might be useful for anyone wishing to contribute/develop in the future. Thanks!

A note for people who try to fix this issue: Removing the -v parameter on macOS does not represent a full solution as our scripts assume that /usr/bin/time is run with -v. Apart from other information, the -v parameter makes /usr/bin/time produce memory usage of the tracked program, which we then parse in our scripts. Without -v, the used memory will always be 0, which will make results incorrect.


remove RSA_NULL

next major release, when we can break ABI.

the build flag is gone, and RSA_get_null_method always returns NULL.  That's in #2244 .  So closing this.


portability.dd: assert should be static assert

This can be asserted at compile time, and that is generally want you want.
(should I open a bugzilla issue before submitting these kinds of changes?)

LGTM


MINOR PATCH: Avoid fragmented resources on supervisor creation in nimbus

What is the purpose of the change
If the underlying scheduler is not ResourceAwareScheduler and scheduler has no resources to register, then it does not have to calculate or report  any resources.
(Explain why we should have this change)
How was the change tested
local unit tests.
(Explain what tests did you do to verify the code change)

I believe we should prefix MINOR to the commit message as well


[TextView_1048] Fix focus mode

Bug 6: https://adevinta.slack.com/archives/C07A29DQE6N/p1719996427031419
Bug 9: https://adevinta.slack.com/archives/C07A29DQE6N/p1719996775213659
Bug 12: https://adevinta.slack.com/archives/C07A29DQE6N/p1719997099897659
Bug 14: https://adevinta.slack.com/archives/C07A29DQE6N/p1719998557707169

Move to the new component repository


[MODDCB-20]-Added Checkout status process.

Purpose
Describe the purpose of the pull request. Include background information if necessary.
Approach
How does this change fulfill the purpose?
TODOS and Open Questions

[ ] Use GitHub checklists. When solved, check the box and explain the answer.

Learning
Describe the research stage. Add links to blog posts, patterns, libraries or addons used to solve this problem.

PLEASE ignore code smell , its because we are using switch with 1 case only . it will be fixed automatically in future when we will have more roles ,


Update "Add" function to support Module model

Implement new "add" function for modules

PR is at #46


Finalize the checkout experience

Add to cart
View cart
Checkout
Promo code/coupon
Big spender campaign
Billing/Shipping address
Choose delivery method
Payment information
Thank you message

This was fixed in v2.0.0


TypeError: adminConnection.createProfile is not a function

Hi !! help me
npm test

<EMAIL_ADDRESS>test /root/BlockchainNetwork-CompositeJourney
mocha --recursive

Commodity Trading
1) "before all" hook
0 passing (142ms)
1 failing

Commodity Trading
"before all" hook:
TypeError: adminConnection.createProfile is not a function
at Context.before (test/sample.js:36:32)

@tung0811 - try it now as the pattern has been updated to HPL V1.1 and it works all the way through.


Feature Request: Auto-Mute PC Audio on Connect

Could you implement this feature please? The pc audio should be muted ONLY when actially streaming. Not when SteamVR is running.

This is a bit hard to do, since ALVR uses the system audio device. If you mute it you mute also the audio stream to the Quest.

If i mute the PC audio i still hear the Quest audio

Probably you are using a different audio device for streaming. In this case we need to figure out how to change windows settings for audio. It could be done.

The selected audio device in ALVR is the same default audio device used by windows (NVIDIA HD Audio).

I usually mute PC audio through SteamVR overlay - that doesn't affect volume of the audio stream to the headset (though I've only ever did this with one audio interface).
So I think this should be doable.

The question is whether to do it before the audio streaming rewrite, or after.

I don't think there is a cross-platform way of muting an audio device (CPAL is not help), we could implement it sooner in C++ (or Rust+winapi, as you prefer).

@maxer456 Wouldnt this cause the PC to not play sound so if you are using it to cast for people it will now be muted? This seems like an optional thing to set. And seems fairly easy to just do yourself on windows with the mute button.

Muting the Windows audio endpoint shouldn't affect software that captures the stream to that endpoint. So speakers will be muted but software like OBS should still be able to capture sound.
It will be optional, yes. It's just a convenience option so you don't have to remember to mute your speakers every time.

Implemented as of v14.0.0.


progress not updated when building supply depots

The SCV with orders to build a supply depot will go about building the depot through completion, but the orders list will show the progress as zero the whole time.
The code below is a snippet of the code illustrating the problem: with const *iUnit pointing to the SCV that is doing the building
 if (iUnit != NULL)
       {
           if (!iUnit->orders.empty())
           {
               auto &o = *iUnit->orders.begin();
               std::cout << "\nprogress on " << AbilityTypeToName(o.ability_id) << " " << o.progress;
           }
       }

I also have problems with it. Current.y the only way to monitor build progress is to track the structure scv is building by tag. However here we encounter #32


win + pure clang (not clang-cl) build error

Error:
d:\dev\cppan2\client2\.sw\rsp>8169297309854606892.bat -w
[sw.client.manager-0.4.0]/src/sw/manager/source.cpp
In file included from D:/dev/cppan2/client2/src/sw/manager/source.cpp:12:
In file included from D:/dev/cppan2/client2/.s/pkg/07/63/651e/src/sdir/src/date_time/include\primitives/date_time.h:9:
In file included from D:/dev/cppan2/client2/.s/pkg/d5/f9/3578/src/sdir/include\boost/date_time/posix_time/posix_time.hpp:24:
In file included from D:/dev/cppan2/client2/.s/pkg/d5/f9/3578/src/sdir/include\boost/date_time/posix_time/time_formatters.hpp:12:
In file included from D:/dev/cppan2/client2/.s/pkg/d5/f9/3578/src/sdir/include\boost/date_time/gregorian/gregorian.hpp:31:
In file included from D:/dev/cppan2/client2/.s/pkg/d5/f9/3578/src/sdir/include\boost/date_time/gregorian/gregorian_io.hpp:16:
In file included from D:/dev/cppan2/client2/.s/pkg/d5/f9/3578/src/sdir/include\boost/date_time/date_facet.hpp:17:
In file included from D:/dev/cppan2/client2/.s/pkg/f7/7f/7cb2/src/sdir/include\boost/algorithm/string/replace.hpp:16:
In file included from D:/dev/cppan2/client2/.s/pkg/7d/f2/028d/src/sdir/include\boost/range/iterator_range_core.hpp:27:
In file included from D:/dev/cppan2/client2/.s/pkg/c0/af/5f1e/src/sdir/include\boost/iterator/iterator_facade.hpp:11:
In file included from D:/dev/cppan2/client2/.s/pkg/c0/af/5f1e/src/sdir/include\boost/iterator/interoperable.hpp:11:
In file included from D:/dev/cppan2/client2/.s/pkg/3d/f2/f30f/src/sdir/include\boost/mpl/or.hpp:43:
D:/dev/cppan2/client2/.s/pkg/3d/f2/f30f/src/sdir/include\boost/mpl/aux_/include_preprocessed.hpp:37:13: fatal error: 'boost/mpl/aux_/preprocessed/plain/||.hpp' file not found
#   include BOOST_PP_STRINGIZE(boost/mpl/aux_/preprocessed/AUX778076_PREPROCESSED_HEADER)
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
D:/dev/cppan2/client2/.s/pkg/ba/e0/f079/src/sdir/include\boost/preprocessor/stringize.hpp:28:38: note: expanded from macro 'BOOST_PP_STRINGIZE'
#    define BOOST_PP_STRINGIZE(text) BOOST_PP_STRINGIZE_I(text)
                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~
D:/dev/cppan2/client2/.s/pkg/ba/e0/f079/src/sdir/include\boost/preprocessor/stringize.hpp:32:36: note: expanded from macro 'BOOST_PP_STRINGIZE_I'
# define BOOST_PP_STRINGIZE_I(...) #__VA_ARGS__
                                   ^~~~~~~~~~~~
<scratch space>:104:1: note: expanded from here
"boost/mpl/aux_/preprocessed/plain/||.hpp"
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

This is caused by following line in files: and.hpp, bitand.hpp, or.hpp, bitor.hpp:
#if defined(_MSC_VER) && !defined(__clang__)

This is not true anymore today. Commenting out the second conditions helps.
Pure clang defines _MSC_VER plus __clang__ on windows.

This need to be solved urgently

@Milerius MPL has no dedicated maintainer and the issue is not a regression, you best bet is to develop a fix and file it via pull request

This is for clang on Windows targeting vc++.  I have clang on Windows targeting vc++ and am able to test this using a the clang-win.jam file, but I need a simple example to test this issue. If just run the mpl tests with clang-win and the latest clang-10.0 on Windows targeting vc++ I see no failures in the tests. Please give a command line and some code where this bug is manifest. Whatever is the code you give in your initial post above I have no idea what is being compiled and  what trhe clang command line is.

Seems this was fixed with newer boost.
The fix is in this commit https://github.com/matbech/mpl/commit/d5fc194ce164301250f6feea9f194ccffdafb4f0


BUG: fix for GH9010

This is an update of PR #9024.
closes #9010

@PollyP can you rebase, and update according to comments by @shoyer

OK, will do by Saturday at the latest.
On Sun, Jan 18, 2015 at 1:00 PM, jreback<EMAIL_ADDRESS>wrote:

@PollyP https://github.com/PollyP can you rebase, and update according
to comments by @shoyer https://github.com/shoyer
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/pull/9198#issuecomment-70425684.

Looks like dstephens99 went ahead and fixed this.

yes, @dstephens99 fixed it in pandas-datareader, but until we decide what exactly to do with the code in pandas, this can maybe still be merged in pandas? (@jreback)

see comments here: https://github.com/pydata/pandas-datareader/issues/15

@jorisvandenbossche are we merging this?

I think we should close this in favor of #9358 (which brings the changes made in pandas-datareader to back to pandas, including this)
@PollyP Thanks for your work on this! If you want to do more fixes in the future, you can submit them directly to pandas-datareader.


Trying to export an imported video with filter/overlay.

So im trying to export a video that's imported via the photo library and applying a filter onto it. My code looks like below
let documentsPath = NSSearchPathForDirectoriesInDomains(.DocumentDirectory, .UserDomainMask, true)[0] as NSString
let formatter = NSDateFormatter()
formatter.dateFormat = "yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'"
let date = NSDate()
let outputPath = "\(documentsPath)/\(formatter.stringFromDate(date)).mp4"
let outputURL = NSURL(fileURLWithPath: outputPath)

let asset = AVAsset(URL: self.video.url)
let exportSession = SCAssetExportSession()
exportSession.inputAsset = asset
exportSession.outputUrl = outputURL
exportSession.outputFileType = AVFileTypeMPEG4
exportSession.videoConfiguration.filter = SCFilter(CIFilterName: "CIPhotoEffectInstant")
exportSession.videoConfiguration.preset = SCPresetHighestQuality
exportSession.audioConfiguration.preset = SCPresetMediumQuality
exportSession.exportAsynchronouslyWithCompletionHandler {
  if exportSession.error == nil {
    self.video.url.saveToCameraRollWithCompletion({ (string, error) -> Void in
      print(string)
    })
  }else {
    print(exportSession.error?.localizedDescription)
  }
}

So the saving works. It's just not applying the filter that i've specified.
Bug, feature or am i doing it wrong?
Edit:
I also tried to export with an overlay, didn't work either.

As you can see on this line:
self.video.url.saveToCameraRollWithCompletion({ (string, error) -> Void in

I am saving the input source instead of the exported source..

You stated "self.video.url.saveToCameraRollWithCompletion({ (string, error) -> Void in". What did you connect to the word video? recordSession? exportSession?

Could you please upload code of the working copy? Thanks


Migrated the project to the Rust 2018 edition

The following command was used from the project root for the migration:
$ cargo fix --all --edition-idioms --allow-dirty

It took me a while to read up into why this is a good thing (TM). Thank you for your contribution!


chinese attachment name is not right

when i send a mail with a chinese name attachment,the chinese name look like this "tcmime.2078.2333.2494.bin" in some email server, e.g mail.qq.com,but it's ok in mail.163.com

the problem as this:
https://github.com/andris9/Nodemailer/issues/416

This has been updated in v1.6.0. Nodemailer now uses QQ compatible filename headers


Remove dependency of ray-tracing on files

Ray-tracing classes RayTracing and SimtelRunnerRayTracing are reading their default configuration values from files in ./data/parameters. File names are hard wired in the class inits. Parameter files for both classes are almost identical.
Changed this:

default parameters are defined in SimtelRunnerRayTracing
removed files in data/parameters

This will allow to run those tools without having the github repo cloned.
There should be no changes in results, printouts, or configuration of these tools.

Thanks for the quick feedback!


Preparse throwing issue in C3

Since updating a site from Craft 2 to Craft 3, I am getting this error
Call to a member function setAttributes() on null
1. craft/vendor/craftcms/cms/src/base/Plugin.php at line 199

    /**
     * @inheritdoc
     */
    public function setSettings(array $settings)
    {
        $this->getSettings()->setAttributes($settings, false);
    }

2. in craft/vendor/yiisoft/yii2/base/Component.php at line 180 – craft\base\Plugin::setSettings(['disableElementTables' => '1'])

3. in craft/vendor/yiisoft/yii2/BaseYii.php at line 546 – yii\base\Component::__set('settings', ['disableElementTables' => '1'])

4. in craft/vendor/yiisoft/yii2/base/BaseObject.php at line 107 – yii\BaseYii::configure(aelvan\preparsefield\PreparseField, ['name' => 'Preparse Field', 'version' => '1.0.0', 'schemaVersion' => '1.0.0', 'description' => 'A fieldtype that parses Twig whe...', ...])

This issue ended up being a setting being stored from the C2 plugin and being carried over to the C3 install.
In the plugins table the prepare-field row had {"disableElementTables": "1"}. I removed this, as it works fine now.
I am closing this issue.

hello, i have the same issue, could you please explain more detailed how to resolve the issue, thank you.

@krizzzly After you have done the update from C2 to C3, if you have a look at your database, go to the plugins table and find the PreparseField row and see if it contains {"disableElementTables": "1"}.
I removed this, and it fixed my issue.

unfortunately the "settings" column in "plugins" table is not there anymore. I think all the settings went into 'info' table and get compiled into a string there.

Interesting, maybe it has changed since I did it with an earlier version of C3.
I will reopen this.


Update discovery_schemas.py for Aeotec Smart Switches

Aeotec's Smart Switch 6 and 7 has a light on the switch itself,
which can be controlled via COLOR_SWITCH_CC and MULTILEVEL_SWITCH_CC
as usual with other light entities.
Since the proper generic/specific types were missing HomeAssistant
did not create a light entity for these devices.

Hi @electrofloat,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

@electrofloat could you please sign the CLA? Thanks and btw welcome to the Home Assistant Community! 🎉✌

@electrofloat could you please sign the CLA? Thanks and btw welcome to the Home Assistant Community! 🎉✌

Sorry, I have to consult with my lawyers on that one. (which won't happen until next year) In the meantime someone should just make this commit and release it in the next cycle, so I don't have to edit this file every time I update Home Assistant.

From 0.103: Happy Holidays, Service calls, StarLine, GeoNet NZ and Proxmox:

We wish you happy holidays! As always, we skip a release cycle at the end of the year, making this the final, major release of 2019. This gives all of us time to enjoy the holidays with our families as well. The first release of 2020, will be on 15 January.

Since the next release will be next year either way I would suggest you continue and talk to your lawyer in the next year. Or what do you think?

Please open a new PR when you're ready to sign the CLA.

Does this mean that this will never be fixed?

It means you haven't signed the CLA after 90 days, which means we cannot merge your code. There is no indication at this point you will be signing this, so there is no use to keep the PR open and clutter our work environment.
Nevertheless, you are still welcome to contribute your code, as soon as you are ready to sign the CLA.
Nevertheless, thank you for your contributions.

It means you haven't signed the CLA after 90 days, which means we cannot merge your code. There is no indication at this point you will be signing this, so there is no use to keep the PR open and clutter our work environment.
You are still welcome to contribute your code, as soon as you are ready to sign the CLA.
Nevertheless, thank you for your contributions.

Of course I won't be signing anything.
Are you a politician? Because you have not answered my question.

I've explained we cannot merge your PR without the signing.
As a result of this, your PR will not fix it right now.
I think that this is a pretty clear answer to the current situation.
I guess you are looking for an answer to this question:

Does this mean that this will never be fixed?

It depends if someone will contribute it, however, we cannot predict the future.


Topics: UI minor fixes for Create new Topic form

Describe the bug (Actual behavior)
Error message about Topic Name requiredness is "name is a required field"
"e" letter is not fully displayed within "Maximum message size in bytes" field's placeholder
Error message of "Number of Partitions" starts with lower case
Expected behavior
Display all placeholders fully
Error messages should include the field name fully and start with upper cases\
Set up
https://www.kafka-ui.provectus.io/
Steps to Reproduce

Login to kafka-ui
Navigate to Topics
Press "Add a Topic"

Screenshots

@Haarolean I would like to contribute to this issue.


[obserstate] the observs have a property now, which provide a possibi…

…lity to get the current state

Pull Request Test Coverage Report for Build 590

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 588:
0.0%

Covered Lines:
572

Relevant Lines:
572

💛  - Coveralls


Domain expires at 13 Jun 2015

I just renewed the mahapps.com domain because to be honest, I was too lazy to check if I'm using it anywhere else. This is just a reminder that it'll expire sometime next year if somebody wants to take over ownership.
No rush on this.

done


Allow specifying customized port in url.

Sorry for the late response. Closing because of https://github.com/akorchev/odata2openapi/issues/12#issuecomment-344315701


Add ocaml_release, ocaml_patch and ocaml_revision

Adds a few more variables based on ocaml_version.
The original motivation was to be able to get the main OCaml version (4.02, 4.03, etc.) for use in rules picking up compatibility layers.

The original motivation was to be able to get the main OCaml version (4.02, 4.03, etc.) for use in rules picking up compatibility layers.

Does that work well in practice though? In general you have choices per range of versions, for instance between <= 4.04 or > 4.04.

That's the subject for a further question!
I presently have this:
(rule
  ((targets (opamCompat.ml))
   (deps    (opamCompat.ml.${ocaml_release}))
   (action  (copy ${^} ${@}))))

(rule
  ((targets (opamCompat.mli))
   (deps    (opamCompat.mli.${ocaml_release}))
   (action  (copy ${^} ${@}))))

; These are unfortunate...
(rule
  ((targets (opamCompat.ml.4.04))
   (deps    (opamCompat.ml.4.03))
   (action  (copy ${^} ${@}))))

(rule
  ((targets (opamCompat.mli.4.04))
   (deps    (opamCompat.mli.4.03))
   (action  (copy ${^} ${@}))))

(rule
  ((targets (opamCompat.ml.4.05))
   (deps    (opamCompat.ml.4.03))
   (action  (copy ${^} ${@}))))

(rule
  ((targets (opamCompat.mli.4.05))
   (deps    (opamCompat.mli.4.03))
   (action  (copy ${^} ${@}))))

so there's a tiny bit of duplication because of not having patterns and then the unfortunate duplications. It has to be said that the duplication could be solved with a pattern rule (so you have a general pattern which has lower precedence than a specific target) - but that's a can of worms. My other thought was whether being able to operate on version numbers is something jbuilder should be able to do - it obviously can't be done easily outside jbuilder as soon as you want to use contexts. I'm not totally sure I want to be doomed to have to use cppo for everything!

So, I've been adding a few things in the development version that should many open more possibilities. Inside actions, you can now write ${read:<file>} and this will expand to the contents of the file. This essentially allows you to have dynamic dependencies:
(rule
 ((targets (opamCompat.ml))
  (action  (copy opamCompat.ml.${read:selected-version} opamCompat.ml))))

And because I got fed up of writing targets and deps when it's just obvious, I added a shorter version of rule where jbuilder infers both targets and dependencies for you:
(do (copy opamCompat.ml.${read:selected-version} opamCompat.ml))

Now all you need to do is write a rule to produce selected-version. Writing a dedicated script for it is a bit painful, but really if we could pass a string to ocaml we could do:
(do (with-output-to selected-version (run ocaml -e "
Scanf.sscanf {|%d.%d|} {|${ocaml_version}|} (fun a b ->
   print_string
    (if a, b >= (4, 03) then
       {|ge403|}
     else
       {|lt403|})")))

Maybe jbuilder could add an (ocaml ...) form and call the toplevel on a temporary file, that could be quite nice, the only thing is that it would be hard to preserve locations properly.
All that said, it does feel like sometimes you want to make decision based on static parameters of the build context at arbitrary position in the description. Adding a small meta-language would allow that. I'm still in between two minds about this.
Basically this is adding more syntax and at some point you wonder whether it's worth pushing in this direction or just providing an OCaml API to write jbuild files in ml syntax, like topkg does for instance. One thing that is nice about having a static description language is that at least you can open any jbuild file and understand it immediately, while understanding OCaml code requires more effort. This mean that fixing the build of a broken package is easier. Moreover the S-expression syntax adds very little overhead, you don't even need to quote strings most of the time.
But back to the small meta-language, I guess it really depends on how often we need this and how hard it is to do without. So far I've needed to switch to the ml syntax in two places:

a jbuild in ocaml-migrate-parsetree to produce a different jbuild file based on the version of OCaml. The new features I described here allow to go back to a normal jbuild
a jbuild in lambda-term to produce a different jbuild based on the variable system in the output of ocamlc -config. Really I could have done it with (:include ...) but I was a bit lazy...

@bobot the thing is it's hard to determine the version of a library in general. Many package don't properly the version field in their META file. Moreover determining the version of a package inside the workspace might require running some commands, so this becomes complicated, and during development the version might just be left blank or set to %%VERSION%%, which won't help much.

Temporarily putting its other awesomenesses to the side, the feature which excites me the most about jbuilder at the moment is the build contexts, which I think leads towards wanting very limited meta-programming, because the platform differences will just always be there. That said, I hadn't so far looked at the ocaml syntax, and those two examples are very easy to follow.
Extending your thoughts from Slack, I do think this is much clearer for the lambda-term example (assuming a translation of the other bit to :include!)

(jbuild_version 1)

(library
 ((name lambda_term)
  (public_name lambda-term)
  (wrapped false)
  (libraries (lwt lwt.unix lwt_react zed))
  (synopsis "Cross-platform library for terminal manipulation")
  (c_names (lTerm_term_stubs (:if (= %{os} win32) (lTerm_windows_stubs) (lTerm_unix_stubs)))
  (:if (= %{system} openbsd)
    ((c_flags (:standard -I/usr/local/include))
     (c_library_flags (:standard -L/usr/local/lib -lcharset))))))

Possibly with the extension that some fields may be defined twice - for example, c_names just adding to any previous c_names. It depends whether it would be better to have multiple (:if ...) or have some kind of (:select ...)

I just pushed the code and documentation (will need to add more tests as well). ${read:...} can appear anywhere in actions, but you can't use it to produce a target. Basically in (do ...) stanzas jbuilder will complain if you use it in a target position, for instance (do (copy a b.${read:fn})). In (rule ...) stanzas, you simply can't use it in the (targets (...))` field.
${read:...} is essentially the equivalent of Build.contents.

@dra27 yh that's true that's it's not too bad as long as we don't abuse of it.

Possibly with the extension that some fields may be defined twice

Meh, you could just do:
(c_names (a (:if foo b) (:if bar c)))

no need to complicate things further.

So, one question about the meta-language is whether we really want it everywhere or just extend the set language available in a few fields. Allowing it everywhere gives you a lot of power, however tools can no longer understand a jbuild file directly, at least to find the overall structure.
Allowing it only on a field by field basis gives you everything you want, I think. For lambda-term for instance you would write, which is not too bad, and IMO cleaner:
(jbuild_version 1)

(library
 ((name lambda_term)
  (public_name lambda-term)
  (wrapped false)
  (libraries (lwt lwt.unix lwt_react zed))
  (synopsis "Cross-platform library for terminal manipulation")
  (c_names (lTerm_term_stubs (:if (= ${os} win32) (lTerm_windows_stubs) (lTerm_unix_stubs)))
  (c_flags         (:standard (:if (= ${system} openbsd) -I/usr/local/include)))
  (c_library_flags (:standard (:if (= ${system} openbsd) -L/usr/local/lib -lcharset)))))


mixxx does not build on unstable after an upgrade

Issue description
When I try to build , I get:
In file included from src/library/trackcollection.cpp:7:0:
/nix/store/zbv02z6amzm90k874288cvm182ifvaf3-sqlite-3.19.3-dev/include/sqlite3.h:3712:16: error: using typedef-name 'sqlite3_value' after 'struct'
 typedef struct sqlite3_value sqlite3_value;
                ^
In file included from src/library/trackcollection.cpp:4:0:
src/library/trackcollection.h:38:20: note: 'sqlite3_value' has a previous declaration here
 typedef struct Mem sqlite3_value;
                    ^
In file included from src/library/trackcollection.cpp:7:0:
/nix/store/zbv02z6amzm90k874288cvm182ifvaf3-sqlite-3.19.3-dev/include/sqlite3.h:3712:30: error: conflicting declaration 'typedef int sqlite3_value'
 typedef struct sqlite3_value sqlite3_value;
                              ^
In file included from src/library/trackcollection.cpp:4:0:
src/library/trackcollection.h:38:20: note: previous declaration as 'typedef struct Mem sqlite3_value'
 typedef struct Mem sqlite3_value;
                    ^
scons: *** [lin64_build/library/trackcollection.o] Error 1
scons: building terminated because of errors.
builder for ‘/nix/store/db0rqqylzxnz682m5r218ix187d43x5y-mixxx-2.0.0.drv’ failed with exit code 2
error: build of ‘/nix/store/db0rqqylzxnz682m5r218ix187d43x5y-mixxx-2.0.0.drv’ failed

Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
17.09pre111447.a7c8f5e419 (Hummingbird)
Nix version: (run nix-env --version)
nix-env (Nix) 1.11.13
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)
"17.09pre111447.a7c8f5e419"
Sandboxing enabled: (run grep build-use-sandbox /etc/nix/nix.conf)
build-use-sandbox = true

@aszlig @cillianderoiste Any ideas?

fixed by https://github.com/NixOS/nixpkgs/pull/28210

It's still not working.

@tasmo it builds here on unstable.
Travis seems to time out.

@magnetophon Got the same error while trying to install sqlite. Unstable works fine now. Thank you!


Wrong description to GroupId.

"To get the GroupId, sign in to the Microsoft Intune admin center and select Groups > Copy the Object ID."
The GroupId which will be used in OMA-URI should match to the GroupId in xml rather than AzureAD Group Object ID.

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

ID: 19b5fda8-c875-aac3-385d-43c88feed731
Version Independent ID: 19b5fda8-c875-aac3-385d-43c88feed731
Content: Deploy and manage Removable Storage Access Control using Intune
Content Source: microsoft-365/security/defender-endpoint/deploy-manage-removable-storage-intune.md
Service: defender-endpoint
Sub-service: asr
GitHub Login: @Dansimp
Microsoft Alias: dansimp

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!

@sparkf1 Thank you for your feedback. That is correct, The groupid from the OMA-URI, Intune admin center and the XLMl would all match.
Hope this helps!
Thanks
Sri


fix version.md link

fix version.md link

This change is

/lgtm
This broken link is due to the recent PR kubernetes/community#1010


ISY994 Lights not showing dimmer slide in 0.36.1

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.36.1
Python release (python3 --version):
3.5.2+
Component/platform:
ISY
Description of problem:
ISY imported Lights do not show brightness slider below journal chart. Instead a dropdown labelled 'Effect' is in its place.

Expected:
Rolling back to 0.35.3 restored functionality.

Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

@Teagan42 @rmkraus @fabaff @randellhodges @OverloadUT
Any of you try the latest release and observe the same?

@jbcodemonkey could you go to /dev-state and paste here all the attributes of this device?
Is this light/isy994.py ?

A change I have done for light UI in 36.x was to show the brightness slider if the device supports it via supported_features attribute and not if brightness attribute exists.
(This still doesn't explain the appearance of "Effects" header)

Yes, light/isy994.py
Attributes for light.1dr_floods:
brightness: 127
friendly_name: Dining Room Floods
icon: mdi:spotlight-beam

Found the bug:
isy994 indeed declares supported_features but it overrides state_attributes without exporting it:
@property
def state_attributes(self):
    """Flag supported attributes."""
    return {ATTR_BRIGHTNESS: self.value}

in light/__init__.py :+1:
    @property
    def state_attributes(self):
        """Return optional state attributes."""
        data = {}

        if self.is_on:
            for prop, attr in PROP_TO_ATTR.items():
                value = getattr(self, prop)
                if value is not None:
                    data[attr] = value

            if ATTR_RGB_COLOR not in data and ATTR_XY_COLOR in data and \
               ATTR_BRIGHTNESS in data:
                data[ATTR_RGB_COLOR] = color_util.color_xy_brightness_to_RGB(
                    data[ATTR_XY_COLOR][0], data[ATTR_XY_COLOR][1],
                    data[ATTR_BRIGHTNESS])
        else:
            data[ATTR_SUPPORTED_FEATURES] = self.supported_features

        return data

Created a Fix PR

@jbcodemonkey Your feedback is required on the fix PR

Hijacked @andrey-git's PR like a pirate. ☠

Tested with commit from 5433, works again. Thank you!!