Kerberos on MacOS

Hi
After installing newest version of go-mssqldb repository (from 2022-10-26 - with 3 latest kerberos update) I tried to connect to sql server via kerberos (kbr5 provider) on Mac OS Monterey.
I tried all kind of connect string, and the best I got is error provider krb5 not found.
My Azure Data Studio connection operating correctly (via /etc/krb5.conf), but golang application is unable to connect.
What I tried so far.
authenticator=krb5;server=db.address.local;database=DWH;user id=myusername;password=mypassword;realm=address.local;krb5conffile=/etc/krb5.conf;
authenticator=krb5;server=db.address.local;database=DWH;user id=myusername;realm=domain.com;krb5conffile=/etc/krb5.conf;keytabfile=~/MyUserName.keytab
authenticator=krb5;server=db.address.local;port=1433;krb5conffile=/etc/krb5.conf;krbcache=/tmp/krb5cc_1000
If I try to remove authenticator then I got user message user=. not found, etc...
What I'm missing?

After the battle I was able to connect. This is my path:
KERBEROS
To use kerberos security on golang MAC application you need to run kinit with cache file
kinit -c /tmp/SomeNameCachedCreds
(To call kinit or klist you need to create /etc/krb5.conf which is not part of this text)
This will create cache file at specified location, which then can be used in connection string
Connect string version which use Cache file. Both version of connect string are correct
authenticator=krb5;server=somedbserver;port=1433;user=someuser;krb5conffile=/etc/krb5.conf;krbcache=/tmp/SomeNameCachedCreds"
authenticator=krb5;server=somedbserver;port=1433;user=SOMEDOMAIN.LOCAL\someuser;krb5conffile=/etc/krb5.conf;krbcache=/tmp/SomeNameCachedCreds"
Following does not work - missing parameter:atleast krbcache or keytab is required
authenticator=krb5;server=someserver;database=DWH;user id=someuser;password=somepassword;realm=SOMEDOMAIN.LOCAL;krb5conffile=/etc/krb5.conf;"
I do not have keytab file so I did not test 3rd kind of connection string
Error provider krb5 not found means that krb5 Integrated authorization is not initialized
To initialize it you need to call some functions inside e.g.
I do not like that, but it works (some register function will be more nice)
import (
  ia "github.com/microsoft/go-mssqldb/integratedauth/krb5"
)
func main() {
   if ia.AuthProviderFunc == nil {
    fmt.Printf("Kerberos AuthProviderFunc is not set: %v\n", ia.AuthProviderFunc)
}

.....
This will initialize krb5 auth provider. It will be better to have some Register function which can be called

Hi all.
Heres the PR https://github.com/microsoft/go-mssqldb/pull/65
Please note the connection string parameter naming convention. It differs from the previous implementation.
Please give it a test and let me know how you go. If there are issues I can jump on.
Thanks

@shueybubbles You merged the PR on March 13; can this Issue be closed?


Dynamic terminologies

Goal here is to solve the following set of related problems:

A big job of the viewer is rendering “codes” into human-consumable text, typically using the FHIR structure CodeableConcept or similar.
Sometimes these codes have “display” values pre-set in the structure itself, but other times they are just terminology+code pairs (e.g., for COVID SHCs you’re supposed to strip out display values to minimize the size of the data package). So we have to look up useful text for the code in a map somewhere.
Because the viewer can render lots of different data types (IPS, COVID/Immunization, SHIC, hopefully more to come) --- which specific terminologies are needed changes from use-to-use, and some of them are pretty big. So we don’t want to just pre-load every terminology possible into the browser --- we want to use some kind of load-on-demand approach.
BUT in ReactJS, the render method itself can’t perform async methods, so loading on demand gets complicated.

The code in this PR tries to optimize all of this using the following approach:

The top-level of the render in Data.js allocates a “DeferringCodeRenderer” object (see codes.js) and passes it down to the type-specific renderers.
Every time a code is rendered, it’s done with SYNC methods on this object that render the data as best they can using only what data is loaded at the moment. If a terminology is needed but not yet available, the methods kick off a download, remember the promise and get out of dodge (synchronously).
Back at the top of the stack in Data.js, after rendering completes, an Effect checks to see if any terminologies were queued up, and if so it waits on completion and triggers a re-render --- which displays any updated codes. (There’s some logic in here to prevent us from trying to download a failed terminology set more than once.)

The only downside I can see with this approach is that for a large terminology there can be a “flicker” on the first scan of a card --- but most of the time it’s pretty imperceptible. It also has the side benefit of never downloading anything in the cases like IPS where display values are usually going to be present in the original data.
Adding new terminologies to this is pretty simple --- a config exercise for FHIR Code Systems and just a bit of code for others. Patrick, per your earlier note about CVX, the Docket set is super-complete so I just ended up using the one Joe added earlier for everything.

Way to go for externalizing the data. Exciting progress.
In the future, React has several fetch options that could nicely fit into its lifecycle.
So separating data retrieval and  minimizing  impacted components  while showing generic skeleton component
Could be one way.
I left suggestion of caching result in LocalStorage.

Redux / ReduxThunk
https://www.digitalocean.com/community/tutorials/redux-redux-thunk
SWR Or more simple approach is swr https://swr.vercel.app/

Skelton reference:
https://www.smashingmagazine.com/2020/04/skeleton-screens-react/

Thanks for feedback everyone! I've done two things in response to comments; please let me know what you think.
@cp-yfukuda I didn't add full Skeleton rendering --- the output of the code function is text and not jsx, so having a smart swap in/out of that ux would require a bit more refactoring. Would love your thoughts on this seeing the new behavior.

I set it up so the "safe" text shown is dependent on the terminology (see the "placeHolder" elements in the config at the top of codes.js) ... some code systems (many of the FHIR-specific ones) have human-readable codes and that works fine; the ones like CPT and CVX that are just random numbers are far better off as @turgid-tributary pointed out. I used "..." for these rather than a full "loading..." or similar because it looks a lot better.
Per @cp-yfukuda note I am now caching the terminologies in local storage so after a first load they're available synchronously anyways. I set a 30 day cache max on those and have code at the bottom of codes.js to prune out as needed. Had to make a lot of assumptions here so specific values may have to change as we get real-world usage.

Really appreciate the feedback!


Panic in WAL  proposer

The following test:
pkill -9 postgres; pkill -9 pageserver; pkill -9 safekeeper;
rm -rf .zenith
zenith init

zenith start

res=`./target/release/zenith tenant list`
tenant=`echo $res | cut -f 1 -d ' '`
port=55432
parent=0

zenith pg start main

psql -h <IP_ADDRESS> -p $port -U zenith_admin postgres -c "create table t(x integer)"
zenith timeline branch  --branch-name b$parent --ancestor-branch-name main

for ((i = 1; i <= 10; i++))
do
    zenith timeline branch  --branch-name b$i --ancestor-branch-name b$parent
	zenith pg start b$i
	let port+=1
	psql -h <IP_ADDRESS> -p $port -U zenith_admin postgres -c "insert into t values (generate_series(1,10000))"
	parent=$i
done

psql -h <IP_ADDRESS> -p $port -U zenith_admin postgres -c "select count(*) from t"

cause generation of several thousands core files with the following stack:
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140380490041152) at pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140380490041152) at pthread_kill.c:80
#2  __GI___pthread_kill (threadid=140380490041152, signo=signo@entry=6) at pthread_kill.c:91
#3  0x00007face1425476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007face140b7b7 in __GI_abort () at abort.c:79
#5  0x00005640dd46a6d7 in errfinish (filename=<optimized out>, lineno=<optimized out>, funcname=0x5640dd5b63a0 <__func__.5> "DetermineEpochStartLsn")
    at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/utils/error/elog.c:680
#6  0x00005640dd030703 in DetermineEpochStartLsn () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:1273
#7  HandleElectedProposer () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:1093
#8  RecvVoteResponse (sk=<optimized out>) at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:1079
#9  AdvancePollState (events=<optimized out>, sk=<optimized out>)
    at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:758
#10 WalProposerPoll () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:298
#11 0x00005640dd3095d7 in WalProposerLoop () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:473
#12 WalProposerStart () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:466
#13 0x00005640dd30968b in WalProposerMain (main_arg=<optimized out>)
    at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/replication/walproposer.c:190
#14 0x00005640dd2bdb4c in StartBackgroundWorker () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/bgworker.c:879
#15 0x00005640dd2ca17f in do_start_bgworker (rw=<optimized out>) at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/postmaster.c:5872
#16 maybe_start_bgworkers () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/postmaster.c:6097
#17 0x00005640dd2ca45f in reaper (postgres_signal_arg=<optimized out>)
    at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/postmaster.c:3069
#18 <signal handler called>
#19 0x00007face14fd670 in __GI___select (nfds=nfds@entry=7, readfds=readfds@entry=0x7fffee2393e0, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0,
    timeout=timeout@entry=0x7fffee239330) at ../sysdeps/unix/sysv/linux/select.c:69
#20 0x00005640dd2cb1dc in ServerLoop () at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/postmaster.c:1715
#21 0x00005640dd2ccb21 in PostmasterMain (argc=argc@entry=3, argv=argv@entry=0x5640de95c480)
    at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/postmaster/postmaster.c:1423
#22 0x00005640dd05f251 in main (argc=3, argv=0x5640de95c480) at /home/knizhnik/zenith/tmp_install/build/../../vendor/postgres/src/backend/main/main.c:216

Similar test in python failed without producing cores (see only data from one branch):
import psycopg2.extras
import pytest
from fixtures.log_helper import log
from fixtures.utils import print_gc_result
from fixtures.zenith_fixtures import ZenithEnvBuilder

def test_many_branches(zenith_env_builder: ZenithEnvBuilder, zenbenchmark):

    branches = 50
    records = 10000

    # Use safekeeper in this test to avoid a subtle race condition.
    # Without safekeeper, walreceiver reconnection can stuck
    # because of IO deadlock.
    #
    # See https://github.com/zenithdb/zenith/issues/1068
    zenith_env_builder.num_safekeepers = 1
    env = zenith_env_builder.init_start()

    env.zenith_cli.create_branch('b0')
    pg = env.postgres.create_start('b0')

    conn = pg.connect()
    cur = conn.cursor()
    cur.execute('create table t(x integer)');

    for i in range(branches):
        env.zenith_cli.create_branch('b{}'.format(i + 1), 'b{}'.format(i))
        pg = env.postgres.create_start('b{}'.format(i + 1))
        conn = pg.connect()
        cur = conn.cursor()
        cur.execute(f'insert into t values (generate_series(1,{records}))');
        #cur.execute('SELECT count(*) from t')
        #rows = cur.fetchone()[0]
        #print('Iteration {i} rows {rows}')
    cur.execute('vacuum t')
    with zenbenchmark.record_duration('test_query'):
        cur.execute('SELECT count(*) from t')
        assert cur.fetchone()[0] == branches*records

Uncommenting select inside loop makes this test work.

There may be two unrelated bugs.
First problem is "solved" by inserting sleep 1 between creating branch and starting new instance.
The second problem also solved by sleep 1 after insert.
There can be quite simple explanation to this fact: when command is terminated (like insert)changes are not yet reached page server. So following create branch command use wrong LSN (before inserted data).
But dumping cores seems to be unacceptable behavior in any case.

Maybe this explains some flakiness in test_restart_compute is well?
For example, this run fails with connection to server at "localhost" (<IP_ADDRESS>), port 15046 failed: server closed the connection unexpectedly, and the compute logs (pg.log) panic repeatedly:
2022-05-18 21:39:05.562 GMT [35885] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.575 GMT [35878] LOG:  background worker "WAL proposer" (PID 35885) was terminated by signal 6: Aborted
2022-05-18 21:39:05.575 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.575 GMT [35878] LOG:  all server processes terminated; reinitializing
...
2022-05-18 21:39:05.592 GMT [35900] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.605 GMT [35878] LOG:  background worker "WAL proposer" (PID 35900) was terminated by signal 6: Aborted
2022-05-18 21:39:05.605 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.606 GMT [35878] LOG:  all server processes terminated; reinitializing
...
2022-05-18 21:39:05.624 GMT [35913] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.667 GMT [35920] LOG:  [ZENITH_SMGR] libpqpagestore: connected to 'postgresql://no_user:eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJ0ZW5hbnRfaWQiOiJkMTliYjYwYTllMGE0OGEzYmUxZWRlMGFhMmVmNGZmZSIsInNjb3BlIjoidGVuYW50In0.FNm0GhyWvU5btY8UGfebxFWIkDocE7VDjA_mSVFXjFNrZBVCZjexhzkVienBUCiWG8iXX1ScyZN4dOJkcbkGo_-oikoLbk0IIrT4RlE4-2iG5EYJ1CrY1edkb5tbcMc3WjoNj2Y20yz0Cf8L6pb_NkfBRIn6-rko83hPsIusZIOpaBe2r_sZyBaGcqv1qodlQWiR_CykVpG2BJpt67u7QEZb0ZAqRT1G6RibYdszLzdf3itOaHmhBU3aqaDgByC38IUGYhAk0WkxXEl822nagViK3qQb5kpc3IT3GhF9Z_t-FWxZ_yb1xoV6UuM7TF4f6GHYtNWtYy13jiQju9HpiQ@localhost:15042'
2022-05-18 21:39:05.668 GMT [35878] LOG:  background worker "WAL proposer" (PID 35913) was terminated by signal 6: Aborted
2022-05-18 21:39:05.668 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.669 GMT [35878] LOG:  all server processes terminated; reinitializing
...
2022-05-18 21:39:05.688 GMT [35928] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.704 GMT [35878] LOG:  background worker "WAL proposer" (PID 35928) was terminated by signal 6: Aborted
2022-05-18 21:39:05.704 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.705 GMT [35878] LOG:  all server processes terminated; reinitializing
...
2022-05-18 21:39:05.766 GMT [35942] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.783 GMT [35878] LOG:  background worker "WAL proposer" (PID 35942) was terminated by signal 6: Aborted
2022-05-18 21:39:05.783 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.783 GMT [35878] LOG:  all server processes terminated; reinitializing
...
2022-05-18 21:39:05.800 GMT [35956] PANIC:  collected propEpochStartLsn 0/241E000, but basebackup LSN 0/241E018
2022-05-18 21:39:05.863 GMT [35878] LOG:  background worker "WAL proposer" (PID 35956) was terminated by signal 6: Aborted
2022-05-18 21:39:05.864 GMT [35878] LOG:  terminating any other active server processes
2022-05-18 21:39:05.864 GMT [35878] LOG:  all server processes terminated; reinitializing
...

Of course, if the compute node restarts by itself all the same, the test loses connection and fails.
A successful run yields much shorter log and no panics.


Whether you can add payment lists and market prices.

Whether you can add payment lists and market prices.
like this http://luckpool.org/payments

Untested commits to look at...
https://github.com/hellcatz/z-nomp/commit/1df375e9d101112eb8ce95d0c7b69de3fc0f7d3c
https://github.com/hellcatz/z-nomp/commit/214856def84fba98a835a680cf8b9c275c6efb65

@hellcatz  is not good....

you need to do a bit of styling on your table i guess..


⚠ Bofrost.de has degraded performance

In 618a3ed, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 962 ms

Resolved: Bofrost.de performance has improved in 5e1b0ab after 59 minutes.


luci-app-firewall: broken the rule if selected "Device (input)" destination zone on MS Edge

If "Device (input)" is selected as destination zone in the setting of
rule, an incorrect value "1" will be input to dest.
I confirmed that this problem occurs on Microsoft Edge on Windows 10,
and it does not occur in Firefox.
root@OpenWrt:/# uci show firewall.@rule[10]
firewall.cfg1092bd=rule
firewall.cfg1092bd.target='ACCEPT'
firewall.cfg1092bd.src='wan'
firewall.cfg1092bd.proto='tcp'
firewall.cfg1092bd.dest_port='22'
firewall.cfg1092bd.name='ssh'
firewall.cfg1092bd.dest='1'	<- this

Thank you!


.yaml file for component config

Instead of a toml file, i would love to have the ability to use a yaml file for the config.
When using 11ty/jekyll, this is way more in line with the SSG's developer experience.
It would also save a lot of time when copying the data items/tags from the config file to a .md file or frontmatter

Hi @silveltman!
This is a great request.
An upcoming project will require making some changes to the component config to align with the new input configuration options in CloudCannon (for example: how to make a field in the bookshop.toml a number slider rather than an input), so I might wait until that body of work has been done before expanding the set of supported types.
I'll keep you posted 🙏

Hello! This has been implemented in 3.0 😄
See the Migration Guide for the change between the files.
Running npx @bookshop/up@latest can also migrate all of your files to yml for you 🙌


Update the readme that MSA accounts are fine closes #96

@vladdypwnz pointed out the documentation is confusing about MSA accounts not working. I tested one and it seemed fine, are the docs are out of date or am I missing something else?

Ah the live: prefix would not be for logging in but returned on the account type itself.   You do need to use the full MSA login (ie<EMAIL_ADDRESS>if not using older skype only usernames.

@mitchcapper Right, I was suggesting that maybe that's worth including in this PR because it's not entirely obvious for the uninitiated 😀 (as long as that section is being updated anyway)

@mitchcapper I naively assumed it would show up properly in Skype itself. I think the live prefix new to the most recent version of Skype. Here's what the profile for the test account looks like: (keep in mind that vladcansignup in this case, even without live:, is still not a valid username)

OK I updated the PR to add a sample under quickstart for an MSA login, beyond that while MS shows MSA's with the live: prefix as when you login to skype it still requires<EMAIL_ADDRESS>for the login flow I think it should be fine.


Optionally disable issuer URL check

This allows oidc-client to work with Microsoft AD. Microsoft returns a different issuer url (iss in the JWT token) for every organization. However, the user's organization can't necessarily be known until after the user has signed in. This prevents users of oidc-client from providing an issuer or suitable metadata endpoint up-front in the UserManager configuration. This PR allows users to explicitly disable the issuer URL check by setting issuer = null. This does not effect any other JWT validation steps since the keys themselves ARE available ahead of time.

didn't someone else already provide a PR to work around this? i can't remember

There was a PR to add a custom validation function which was scraped in favor of customizing the entire ResponseValidator (which was also scraped). This PR makes the issuer metadata setting nullable (since Microsoft's org system prevents it being known ahead of time) and disables the check in such a case.

Miss-clicked the close button.

Ping. We recently met with Microsoft and verified that the issuer can't be known until the JWT is parsed. I don't know how we can use oidc-client without this PR or some other fix for #338, #724, #626. As far as I can tell, Microsoft is spec compliant in regard to specific tenants.
Note that IdentityModel2 already allows the user to disable issuer validation. Docs

As far as I can tell, Microsoft is spec compliant in regard to specific tenants.

They're not since it's one common URL, but multiple issuers. The issuer must match the token server URL: https://openid.net/specs/openid-connect-core-1_0.html#IssuerIdentifier
As for the rest, I'm traveling so I've not had any time to look into this.

The issuer must match the token server URL: https://openid.net/specs/openid-connect-core-1_0.html#IssuerIdentifier

Thanks for the link! It pointed me on to some more useful resources.

I'm traveling so I've not had any time to look into this.

All good. This PR changes a single line of code in the main source (plus a couple more for typings and tests) so it shouldn't take too long to review once you have a chance.

Thanks for the link! It pointed me on to some more useful resources.

 I wonder if the AAD devs know that :)

Ping again on this. Is there any chance of this getting merged in the next couple of weeks?

Hi @samsartor,
I also had the problem with the "wrong" issuer https://sts.windows.net//. Then after diving deeper in the topic I found out that it is actually pretty logical (for my case) to get the access token from this issuer and not from the one I expected, namely https://login.microsoftonline.com//v2.0.
Here what I believe is the case, although I'm far from being an expert on the subject.

There are two versions for the issued tokens - v1.0 and v2.0
The resources/APIs you authorize against have also a version. The version of the issued access token matches the version of the resource/API
Depending of the access token's version the issuer is:

For v1.0 https://sts.windows.net/
For v2.0 https://login.microsoftonline.com

The Microsoft Graph API has v1.0. and is added per default with the claim User.Read when you register an App on portal.azure.com
Even if you delete the Microsoft Graph API, it will still be set as the resource/API to authorize against. I was still getting an access token with aud = 00000003-0000-0000-c000-000000000000, which is this API's application id. That drove me mad for longer than I'm willing to admit :)
- The issued access token is of the version of the API one authorizes for.

This is how I was getting an v1.0 access tokens with my authorization calls until I started to authorize against our own Web API (v.2.0) instead of the Microsoft Graph.
Hope the information helps.
Helpful resources for the topic:

https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/560 - although setting the version in the manifest to 2 does not bring anything if you still authorize for Microsoft Graph.
https://docs.microsoft.com/en-us/azure/active-directory/develop/access-tokens

Hi @samsartor -- in your app do you plan to validate issuer at all?

To re-iterate, the issuer can not be known until the JWT is parsed when using the /common or /organization endpoints. This has to do with those endpoints multiplexing over independent "tenants" and not the graph API version. For this reason, most OIDC libraries have a setting to ignore (or add custom validation rules for) the issuer including other IdentityModel libraries. This PR was just to add the same functionality here but due to lack of progress we now use MSAL for authenticating our Microsoft users.

Hitting the same problem, we are using this library to authenticate to azure AD https://login.microsoftonline.com/common/v2.0 and the library is rejecting the id_tokens because the issuer is not https://login.microsoftonline.com/common/v2.0 but https://login.microsoftonline.com/<our_tenant_id>/v2.0.

Hitting the same problem, we are using this library to authenticate to azure AD https://login.microsoftonline.com/common/v2.0 and the library is rejecting the id_tokens because the issuer is not https://login.microsoftonline.com/common/v2.0 but https://login.microsoftonline.com/<our_tenant_id>/v2.0.

As I mentioned above, the issuer check is mandatory in OIDC and the spec says exactly how to do it. AAD doesn't follow the spec.

Hi @brockallen, thanks for taking the time to answer. You also mentioned allowing to pass an inherited ResponseValidatorCtor in the settings, could you give pointers on how to do that exactly ?
Thanks in advance,
Jon

Closing since we won't be doing this. Thanks.

Hi @brockallen, thanks for taking the time to answer. You also mentioned allowing to pass an inherited ResponseValidatorCtor in the settings, could you give pointers on how to do that exactly ?
Thanks in advance,
Jon

Did you find a solution for custom validation/ ignoring issuer? Or perhaps move to another library. Either hacky or trough the ResponseValidatorCtor  (wich I can’t seem to find any example for)

Our workaround is to modify the oidc-client-js saved state in localstorage before initializing the library.

Our workaround is to modify the oidc-client-js saved state in localstorage before initializing the library.

What are you modifying about the state before knowing the token - that can circumvent issuer validantion?
Ive come to a solution where i swap the attributeJWTValidator method (dont remember  exact name) on UserManager for my custom method that parses the JWT, and passes the issuer from that to the original validation method, so it compares it to itself, instead of the issuer from settings. About 5-10 lines of code

Our workaround is here : https://github.com/gridsuite/commons-ui/blob/master/src/utils/AuthService.js#L28
when we get a token, we basically replace the authority that was saved in localstorage in the previous page load library initialization with the authority coming from the jwt token and save it for subsequent library initializations


Adds dependencies test

This adds a dependencies test, which will need further refactoring to support storage types that require dependency-aggregation. However, this works and keeps the first pass small.

thanks for the look @anuraaga!


Handling multiple push / pop operations

As discussed in #2:
What if the user wants to pop() two screens from the current screen? Imagine something like this: You have a game screen, the player opens an inventory screen and in that screen he opens an compare items screen. For the player it would be convenient to just press 'i' to close the inventory screen.
This wouldn't be possible with https://github.com/rm-code/screenmanager/commit/c27ea3d3ccbe68f8c36e07045ecf22d7de386443 if I'm not mistaken. But it's not a hard issue to fix. We could simply use a "queue" for the actions.
I'm thinking about something like this:
local changes = {};

...
function ScreenManager.switch( screen, ... )
    validateScreen( screen );
    changes[#changes + 1] = { action = 'switch', screen = screen, args = { ... } };
end
...

function ScreenManager.performChange()
    if #changes == 0 then
        return
    end

    for _, change in ipairs( changes ) do
        if change.action == 'pop' then
            pop();
        elseif change.action == 'switch' then
            clear();
            push( change.screen, change.args );
        elseif change.action == 'push' then
            push( change.screen, change.args );
        end
    end

    changes = {};
end

Could you check this changes and tell me what you think?

The problem with that is that if you switch and then pop we have no way to know that we popped the last state and that an error should be raised. You could pop 10 times when there are only 3 states in the stack...

The user shouldn't be able to pop / push after a switch action anyway so we could discard those after the switch has been performed.
So if we use a loop we could simply break after the switch:
for _, change in ipairs( changes ) do
    if change.action == 'pop' then
        pop();
    elseif change.action == 'switch' then
        clear();
        push( change.screen, change.args );
        break; -- Discard any actions after the switch.
    elseif change.action == 'push' then
        push( change.screen, change.args );
    end
end

IMO it's the responsibility of the coder to keep track of his screens, but as you said we could simply ignore a pop action if only one screen is on the stack.

I think what I did fixes this issue, I have a counter that actually knows the height of the stack after performChanges has been called

I don't think we need a second variable to keep track of the stack's height. We can use #stack in the pop function directly:
---
-- Close and pop the current active state and activate the one beneath it
--
local function pop()
    if #stack == 1 then
        -- Do something.
        return;
    end
    -- ...
end

I'm currently just thinking about what to do in this case. As I said IMO it's the programmers job to keep track of the screens and I think if you call pop three times in your code, but only have two screens on the stack it might be a bug you don't want to ignore... hmm no clue.
I gotta go now though. I'll implement it in OTR later today and see how it feels.

Well #stack will only hold a valid value after you call ScreenManager.performChange() and we want a valid value when we call ScreenManager.pop() so I think that having a separate variable is not that bad, it should also be more performant, since getting the length of a table is way more complicated than grabbing a number variable.
My solution gives an error when you call ScreenManager.pop() the second time and there were only 2 screens telling you that you can remove the last screen in the stack.
If you don't want a second variable then we can put it into the stack table as stack.height but it would be the same...

I don't think that the user of the library should know perfectly what the stack holds since we are not even letting him access the stack himself, (the stack is a private variable). We don't even tell the user the length of the stack, and the only access the user has is ScreenManager.peek()
I also consider that not erroring when you pop more than what you can will actually lead to undefined behaviour and people will find it really hard to debug.
I think my solution (which you can find here) addresses all this problems, with the cost of one extra variable called height that could be part of one of the tables like I said before (stack.height).
Please check that out whenever you implement this in OTR and tell me if there is anything wrong.

I merged your changes, but I think we could simply do it like this:
https://github.com/rm-code/screenmanager/commit/98ab92529598e4e9e8465a010f91fbb22fc00a09

Well #stack will only hold a valid value after you call ScreenManager.performChange()
I'm not sure what you mean by that. If we check the #stack in the local pop function it will always have the correct size. Of course we can't use it in the public pop function like that :)

I think the error should go in the public ScreenManager.pop function, because that is the expected behaviour (at least for me).
Putting the error in the private pop and making it level 2 means that I will get an stackoverflow like this:
ScreenManager.lua:119: Can't close the last screen. Use switch() to clear the screen manager and add a new screen.
stack traceback:
ScreenManager.lua:112: In function ScreenManager.performChange
ScreenManager.lua:212: In function ScreenManager.draw
main.lua:20: In function love.draw
...

With the error in the public pop you get pointed to the line where you popped more than what you should. I think that is better

Ok that makes sense. Let's leave it like this for now.


[SPARK-46504][PS][TESTS] Factor slow tests out of IndexesTests

What changes were proposed in this pull request?
Factor slow tests out of IndexesTests
Why are the changes needed?
for testing parallelism
Does this PR introduce any user-facing change?
no, test-only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

merged to master


Disallowing PDBs from blocking voluntary disruptions

Related to: https://github.com/ministryofjustice/cloud-platform/issues/3926

Closing this PR but keeping the branch for future reference.
Decision has been taken to redo the same after moving to gatekeeper


Show full-screen

Hi guys
First of all, thanks for this awesome package
I need to show carousel full-screen, that means carousel set height automatically by size of client monitor, how I do this?

Perhaps this can be done thru the fullscreen api in html5? That would be awesome!

is it doable ?


Bot does not start

Uncaught TypeError: Cannot read property 'addListener' of undefined at background.js:1080.
An error occurred when adding a fragment of localization initialization code.

Fixed. Added check before initializing the global array when installing or updating.


Parser error when loading latest 1.0.6 version

Issue:
Did a bulk yarn upgrade, and upgraded storybook-react-router to 1.0.6 from 1.0.5.
When running the storybook, I was showen the following error when running as before.
ERROR in ./node_modules/storybook-react-router/react.js 19:2
Module parse failed: Unexpected token (19:2)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|   // a story to another one and so you cannot implement a back or forward button which
|   // works among stories.
>   <MemoryRouter {...routerProps}>
|     <Route
|       render={({ history, location }) => (
 @ ./.storybook/config.js 11:0-49 22:13-24
 @ multi<EMAIL_ADDRESS><EMAIL_ADDRESS>./.storybook/config.js (webpack)-hot-middleware/client.js?reload=true

Installed 1.0.5 again, and storybook loaded as expected.
I am loading the router in my global .storybook/config.js file:
addDecorator(StoryRouter())

I'm unsure what part of my setup might be causing this. I am overidding the default config, to use typescript, as follows, which may contribute. I couldn't see what was different that could be causing it.
module.exports = ({ config }) => {
    config.devtool = "eval-source-map";
    config.module.rules.push({
        test: /\.(ts|tsx)$/,
        include: ['../'],
        exclude: ['../node_modules'],
        use: {
            loader: 'babel-loader',
            options: {
                presets: [
                    "@babel/preset-env",
                    "@babel/preset-typescript",
                    "@babel/preset-react"
                ],
                plugins: [
                    "emotion",
                    "@babel/proposal-class-properties",
                    "@babel/proposal-object-rest-spread"
                ]
            }
        },
    });
    config.resolve.extensions.push('.ts', '.tsx');
    return config;
};

I can confirm, same issue here.

I can confirm the same error, with a fresh storybook setup using Typescript. Downgrading to 1.0.5 resolved the issue.


Changed casing to reflect actual UI

Changes:

Casing: "Connection Type" --> "Connection type"
Casing: "Server Group" --> "Server group"

Current UI:

@NenoLoje : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@markingmyname
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

#sign-off


Scalars in response body not correctly supported.

Bug description
When returning a scalar from a graphql backend, it is expecting a string, although the schema states scalar.
How to reproduce
A Wundergraph server configured to reproduce the error:
wgtest.zip
A simple graphql server which acts as a backend (I could not reproduce with the built-in graph-ql server unfortunately):
graphql-test.zip
Run the graphql server with yarn && node server.js
Run the Wundergraph server with 'yarn && npx wunderctl up --debug`
Open the Wundergraph graphql server at: http://<IP_ADDRESS>:9991/graphql and send the following request:
query {   b1_bar(foo: 222) {     foo   } }
You will receive as response:
{   "errors": [     {       "message": "could not resolve response"     }   ] }
And something similar to this is the Wundergraph console:
2023-04-06T14:34:01+10:00 ERROR apihandler/apihandler.go:888 ResolveGraphQLResponse {"component": "@wundergraph/node", "reqId": "8fbe8a40-a609-ef52-bb7a-1fd94f8132a0", "error": "invalid value type 'number' for path /data/b1_bar/foo, expecting string, got: 123. You can fix this by configuring this field as Int/Float/JSON Scalar"}
Expected behavior
The scalar is correctly returned from the GraphQL backend to the client making the request to Wundergraph.
WunderGraph information
See attached example program.
Environment & setup
Linux Mint 20
Go 1.13.8
Node 18.12.1
WunderCtl Version
See attached example program.

What is the encoding of the custom scalar?

Hi @jensneuse, thanks!
When I do that, the type is removed, and I need to define any operations using Int,
For example, in the project I provided, the following operation was defined:
query b1GetIt($id: b1_BigInty!) { 	b1_bar(foo: $id) { 		foo 	} }
However after adding the customIntScalars configuration, my operation becomes as follows because the scalar is no longer available:
query b1GetIt($id: Int!) { 	b1_bar(foo: $id) { 		foo 	} }
The values being passed via the BigInty type are larger than a 32 bit number, so this solution seems inappropriate.
I've just noticed that if I define the scalar in customJSONScalars, the typename is used correctly and everyhing works.
I'm happy to close this now, as it seems I can do what I need to defining the scalar as a customJSONScalar. This makes sense, as by default, scalars in GraphQL must be able to be represented in JSON.
Thinking more about this, It may make sense to suggest users to add all their graphql scalars as customJSONScalars (with a warning during the generate phase) or even automatically add them if not added explicitly to customIntScalars or customStringScalars for example.

Completed under https://github.com/wundergraph/wundergraph/issues/846.
Please update your SDK to 0.167.1.


⚠ Adacta-fintech.com has degraded performance

In e899884, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1608 ms

Resolved: Adacta-fintech.com performance has improved in 6000174 after 7 minutes.


Unsure how edit sessions persist in list

Testing #156211

Stored 3 edit sessions in vscode.dev
Resume Edit Session for one of them
The selected edit session is removed from the Edit Sessions view
If I resume another, that one is also removed, and the other session isn't added back
I resume the third, and now there are no edit sessions listed in the Edit Sessions view

I had thought my edit sessions would persist in the list until I either committed the change or took some specific action to remove them. I thought there would be a way to jump between edit sessions to see which one I want to resume, similar to how I can jump between branches and they aren't deleted.

We delete edit sessions from the service after they have been resumed because we don't want to be storing them forever (storage is expensive). @andreamah also reported that this was unexpected https://github.com/microsoft/vscode/issues/153566, maybe we need some way to inform the user of this behavior.

Closing as duplicate of https://github.com/microsoft/vscode/issues/156368


NullPointerException in ShardingRule class

There are methods in the createBindingTableRules of the 82 lines in the ShardingRule class that use the broadcastTables property.
At this time, broadcastTables is empty, so it will report NullPointerException

Can you fill necessary information followed by template below?

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
Which project did you use? Sharding-JDBC or Sharding-Proxy?
Expected behavior
Actual behavior
Reason analyze (If you can)
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
Example codes for reproduce this issue (such as a github link).

the version I used is 4.0.0-RC1 and the project is Sharding-JDBC . I think the reason is that no short judgment in the isBroadcastTable method in the ShardingRule class.

what's mean for short judgment?

null judgment

@F191919
broadcastTables has empty linked list as default value in ShardingRuleConfiguration.
I think there are some configuration mistakes in your sharding configuration.
Can you provide your sharding configuration?

Yes, there are some configuration mistakes in my sharding configuration. I have solved it. I think it is better to throw an exception hint here.


Camera config management

This PR adds a way to enumerate all video input options for a camera device.
As of now, it only supports DShow and V4l2 input formats, but maybe more will be supported in the future.

[x] DShow
[ ] VfWCap
[ ] GdiGrab
[x] V4l2
[ ] X11Grab
[ ] AVFoundation
[ ] QTKit

I am not sure at all if other formats even need it... Until then, this is what we've got.

I tested camera configuration with OBS virtual camera and it works. Tomorrow I'll test with my real webcam.

It apparently is trying to use yuv420 while its name is yuv420p


Feature/doobie implementation

Some formatting and style consistency issues. Otherwise looks good. Does Doobie has a connection pool? Or can use HickariDB ?

yes, doobie has HikariCP transactor.


Expose CompileTools#runCommand in export API

Not the entirety of CompileTools, just runCommand.
Thinking either add it to:

IBMiContent.ts
Instance.ts

Actually, it might be possible if we do it inside of IBMi.ts! remoteCommand is a little outdated and using a deprecated API. Since IBMi.ts already includes instance, we can use it to invoke runCommand - I've got this covered!

Also expose https://github.com/halcyon-tech/vscode-ibmi/blob/master/src/instantiate.ts#L337


Indice/Range for yielded/async sequences

Hey there, quick question: Is it possible to use the new indices/ranges with async or yielded sequences?
Is there a way to do that? Since both features are new here, would be nice if it was mentioned here, too.

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

ID: a94537c5-754e-9dea-94a8-7573011f588c
Version Independent ID: aba09118-22c5-2c6a-954a-b9659a9644ae
Content: What's new in C# 8.0 - C# Guide
Content Source: docs/csharp/whats-new/csharp-8.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Not really, since an index or a range can be from the end and those can't be efficiently supported for a general IEnumerable<T> or IAsyncEnumerable<T>.
Though if you want, you can write something like that yourself, e.g.:
public static IEnumerable<T> Slice<T>(this IEnumerable<T> source, Range range)
{
    if (range.Start.IsFromEnd || range.End.IsFromEnd)
        throw new ArgumentException("Ranges with 'from end' indices are not supported.", nameof(range));

    var start = range.Start.Value;
    var end = range.End.Value;

    return source.Skip(start).Take(end - start);
}

And then use it like this:
enumerable.Slice(1..5)

You could also write a similar extension method for IAsyncEnumerable<T>, to make that easier, you could use System.Linq.Async.

Thanks @svick, I didn't register that yet the indices/ranges not work on IEnumerable.
Thanks also for the suggested Extension.


How to color a point cloud？

Required Info

Camera Model
D400

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10

Platform
PC

SDK Version
{ legacy / 2.. }

Language
MATLAB

Issue Description
My shooting scene is shown below：

The result of running 'pointcloud_example.m' in MATLAB is shown below：

How do I color it so that it looks like the image below：

The figure of below is the code in pointcloud_example. The code in the red box appears to be coloring the pointcloud, but when I uncomment it and run it, I get the same result as before.

Hi @pgswag  Adding the colorizer code from lines 5 and 26 of the depth_example.m example to the appropriate places in the pointcloud_example.m script may work.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/matlab/depth_example.m
Line 5
pipe = realsense.pipeline();
% Make Colorizer object to prettify depth output
colorizer = realsense.colorizer();

Line 26
depth = fs.get_depth_frame();
% Colorize depth frame
color = colorizer.colorize(depth);

Here's the code I changed, but it doesn't seem to be working
function pointcloud_example()
    % Make Pipeline object to manage streaming
    pipe = realsense.pipeline();
    % Make Colorizer object to prettify depth output
    colorizer = realsense.colorizer();
    pointcloud = realsense.pointcloud();

    % Start streaming on an arbitrary camera with default settings
    profile = pipe.start();

    figure('visible','on');  hold on;
    figure('units','normalized','outerposition',[0 0 1 1])

    % Main loop
    for i = 1:10000

        % Obtain frames from a streaming device
        fs = pipe.wait_for_frames();

        % Select depth frame
        depth = fs.get_depth_frame();
        color = fs.get_color_frame();
        % Colorize depth frame
        color = colorizer.colorize(depth);
        % Produce pointcloud
        if (depth.logical() && color.logical())

            pointcloud.map_to(color);
            points = pointcloud.calculate(depth);

            % Adjust frame CS to matlab CS
            vertices = points.get_vertices();
            X = vertices(:,1,1);
            Y = vertices(:,2,1);
            Z = vertices(:,3,1);

            plot3(X,Z,-Y,'.');
            grid on
            hold off;
            view([45 30]);

            xlim([-0.5 0.5])
            ylim([0.3 1])
            zlim([-0.5 0.5])

            xlabel('X');
            ylabel('Z');
            zlabel('Y');

            pause(0.01);
        end
        pcshow(vertices);
    end

     % Stop streaming
    pipe.stop();

end

I wonder if this line is causing confusion for the program:
color = colorizer.colorize(depth);
Because you are already using the 'color' variable name for the RGB color stream.
Does it make a difference if you change the name of the colorizer variable to 'colorized'
 colorized = colorizer.colorize(depth);

Thank you very much for your patient answer, but it still hasn't worked.

You are very welcome.  It's excellent to hear that the script resolved your problem and I am pleased that I was able to help.  :)


Investigate whether PDF/HTML generated for all versions are in git repo history

I am not sure, but I think that the way that PDF/HTML is generated for the language spec, the p4lang/p4-spec repository grows in size every time a commit is made to the repo.  I believe some other p4lang spec repos, e.g. p4runtime, do auto-generate PDF/HTML on every commit, but in a way that only the most recent PDF/HTML are ever in the git repo, not the history of all revisions.  I believe that binary PDF does not compress well with git across small changes in the source text.

Here is a change made in 2022-Nov to the repo https://github.com/p4lang/pna recommended to me by Antonin Bas that helps keep only the latest version of auto-generated PDF and HTML docs for the PNA specification in the gh-pages branch of that repo: https://github.com/p4lang/pna/commit/a791747b3aa3ea033771fd082b6887f17ed92ddb
The p4runtime repo also uses the --amend option for this purpose.
As far as I can tell, the p4-spec repo does not use this --amend option when committing new generated HTML and PDF files to the gh-pages branch, thus it has full history of all generated versions stored in its commit history.

I do not know how to calculate the precise quantitative effect of this, but as a rough kind of evidence that storage is creeping up on the p4-spec repository:

The p4c repository totals 105 MBytes of size in its .git directory, containing compressed deltas/versions of all files of the repo's entire history covering 3457 commits, and has 81 MBytes of files in its most recent version (outside of the .git directory).  This averages 105MB/3457commits = 30KBytes/commit

The p4-spec repository totals 177 MBytes of size in its .git directory, with 1905 commits, and has 56 MBytes of files in its most recent version (outside of the .git directory).  This averages 177MB/1905commits = 93KBytes/commit


[Dubbo-7107] Reset TestProxyFactory.count after ServiceConfigTest.testProxy

What is the purpose of the change
The test org.apache.dubbo.config.ServiceConfigTest.testProxy is not idempotent and fails if run twice in the same JVM, because each of the tests pollutes state shared among tests. It may be good to clean this state pollution so that some other tests do not fail in the future due to the shared state polluted by these tests.
Brief changelog
Reset TestProxyFactory.count to 0 at the end of ServiceConfigTest.testProxy().
Verifying this change
With the proposed fix, the test does not pollute the shared state (and passes when run twice in the same JVM).
Link to issue: https://github.com/apache/dubbo/issues/7107

Thanks @AlbumenJ for the review. Is there anything I can do on my side before this can be merged?


Change "Important Dates"

To the best of my knowledge, the dates are:
Deadlines

Abstract Submission: April 10, 2020
Final Submission: April 17, 2020
Notification of Acceptance: June 12, 2020
Camera-ready Upload: July 6, 2020

Main Event:

Tutorials: October 11, 2020
Scientific Program: October 12–15, 2020

Social Program

Reception: October 11, 2020
WiMIR Reception: October 12, 2020
Concert: October 13, 2020
Banquet: October 14, 2020

Satellite Events

HAMR: October 9–10, 2020
WoRMS: October 10, 2020
DLfM: October 16, 2020

@emilyhopkins I did not find the latest dates we agreed on, on Teamwork. Could you please double-check these ones?


Feature request

I have a mac and when i open some apps it takes up like 1.5GB of memory so i should have an option to close the app  i no longer need instead of waiting for it to be closed automatically

There is a "background activity" hibernation option but it is greyed out on at least some apps – why, I do not know.

like the option to close them manually such as in activity monitor, sorry for the very late response

Could you please change the title of the issue to make it more descriptive?


Document relaxed index constraint on embedded entities (#5881)

Pull request opened by the merge tool on behalf of #5881

Merged into branches iso6 in aceb1acd126bfda68f1afb72ad9e97377b5acd59


UnimplementedError was thrown during paint

Bug
In the example app, the circle is not drawn around the Increment button.

To Reproduce
Build and Run the example app in web.
Desktop:

OS: Windows
Browser: Chrome
Version: 85.0.4183.121

Error:
════════ Exception caught by rendering library ═════════════════════════════════════════════════════
The following UnimplementedError was thrown during paint():
UnimplementedError

The relevant error-causing widget was:
  CustomPaint file:///C:/Users/I524760/StudioProjects/flutter_portal/example/lib/discovery.dart:86:13
When the exception was thrown, this was the stack:
C:/b/s/w/ir/cache/builder/src/out/host_debug/dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 212:49  throw_
C:/b/s/w/ir/cache/builder/src/out/host_debug/flutter_web_sdk/lib/ui/src/ui/path.dart 70:5                                  combine
packages/example/discovery.dart 140:12                                                                                paint
packages/flutter/src/rendering/custom_paint.dart 531:12                                                                    [_paintWithPainter]
packages/flutter/src/rendering/custom_paint.dart 572:7                                                                     paint
...
 It has made a big refactor.


CNDB-11317 Remove DSE name in favor of more generic DB

Converged/DataStax Cassandra embodies some of the advanced functionality from DSE Core but product-wise is not related with DSE anymore being used in Astra and HCD.
Hence, we should rename the artifacts to reflect this reality and prevent confusion when shipping them as part of HCD.
This has been discussed in https://datastax.slack.com/archives/C04SYTHAXL3/p1728922931035169 and it was agreed that artifact to be named com.datastax.db:db-all instead of com.datastax.dse:dse-db-all.
Previous change for reference: https://github.com/datastax/cassandra/pull/62/ (STAR-172)

@tiagomlalves The build results look better now in butler - have you tried to use this with CNDB main-5.0 yet?

@djatnieks no progress (and no changes) during this week. Weird that build results looks better :) I was planning to get back to it next week.


howto bind properties

can't use properties in the view like customer.firstName

That has to work. That's one of the main things I'm doing with this module

What I mean that x.y as object has Getter/Setter on y. As entity it doesn't

Well, no. An entity is an entity. It should be the closest thing to a pojo to make it easy to work with. Do you have a code example?

the edit.js/html
https://github.com/doktordirk/aurelia-orm-loopback-sample/tree/test/client/src/modules/customer

And, then what doesn't work?

no UI feedback from customer whereas otherCustomer gets live UI feedback


Prevent overlay from flickering when desktop switches

We can use the same trick formerly used for sticky windows.  I think we'll have to stop using SplashImage and re-implement the overlay with Gui commands.  Another benefit of re-implementation is that we can properly center the icon and tweak the colors and border and whatnot.

Would be cool if the "grid" represented the shape in the configuration also... E.g. I use a 6x1 grid that shows up as a 3x3 in the overlay

True, but that's a different issue.  Can you submit it separately?


jest_0 dir after test

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
If I run npm test which is "test": "jest -u" it creates folder jest_0 which contains jest-transform-cache-... dir and other files. But with yarn test everything is alright, so I don't know if it's NPM or Jest problem.

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.
Everything is described above.
What is the expected behavior?
With npm test which runs jest -u to don't create jest_0 folder like Yarn do.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
OS: Linux Ubuntu 16.04
Node: 7.9.0
NPM: 4.6.1
Yarn: 0.24.4
Jest: 20.0.1

Also it creates v8-compile-cache-0 folder.

Seems Yarn create v8-compile-cache-0 folder too.

What's the output of jest --showConfig?

When I run jest through npm inside docker I get this path "cacheDirectory": "/usr/src/app/jest_0" which explains why it saves the cache there. If I just execute the node /usr/src/app/node_modules/jest/bin/jest.js --showConfig it becomes /tmp/jest_0 which makes sense. I wonder why running through npm causes it to use that for cacheDirectory

It seems to be an old npm  npm/npm#4531
To work around I defined a explicit cache directory on jest config:
"cacheDirectory": "./node_modules/.cache/jest"

@terlar does it also work for you by updating NPM?
I can't repro it with this Dockerfile
FROM node:7.7-alpine

WORKDIR /app

RUN yarn add jest

I built it docker build  . -t jest-config-bug.
And then did
docker run -it jest-config-bug node_modules/.bin/jest jest --showConfig

and

They both show  "cacheDirectory": "/tmp/jest_0"

@rogeliog The problem was specifically with npm so your test with yarn does not really test the case.
See this for minimal reporducible setup:
package.json
{
  "name": "jest-config-bug",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "jest --showConfig"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "jest": "^20.0.4"
  }
}

Dockerfile
FROM node:7.7-alpine

WORKDIR /app
COPY package.json /app

RUN npm install

Build:
docker build . -t jest-config-bug

And test with:
docker run -it jest-config-bug npm test


Image build test release

PR Type

[ ] Breaking change
[ ] Feature
[X] Patch

Brief Description
Changed the name of the action to install packages into the base image.

Not In Scope

PR Checklist

[ ] Is documented
[X] Is tested
[ ] Adheres to applicable organization standards

TODOs

[ ] Task 1
[ ] Task 2

I only changed the action name but do not understand why I have so many files changed. Something wrong in creating this PR?

You got a conflict.

You got a conflict.

Thanks for pointing this out. The conflict has been resolved.

🚀 [bumpr] Bumped! New version:v0.1.7 Changes:v0.1.6...v0.1.7


Mistake in redirectUri description

In the description of redirectUri, the clause "except that it must be URL encoded" is mistaken. In fact, if the value is URL encoded, there is an error that it is not a valid URI. The value should exactly match the registered URI and not be URL encoded.

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

ID: 69b44d91-f31e-b934-dbb0-fc7e69954b44
Version Independent ID: 76a2ef76-270a-e6f9-d13a-88b04be315d7
Content: Initialize client applications (Microsoft Authentication Library for JavaScript)
Content Source: articles/active-directory/develop/msal-js-initializing-client-applications.md
Service: active-directory
Sub-service: develop
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

@Rick-Kirkham
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @Rick-Kirkham
I made a pull request to remove that line. https://github.com/MicrosoftDocs/azure-docs-pr/pull/86496
In the future feel free to make your own pull requests for small changes like this.


Pipelines: Showcase using new Power Pages CI/CD tooling #163

Adding code to support Power Portal upload/download functionality in the pipelines according to Issue
https://github.com/microsoft/coe-starter-kit/issues/163
In order to not change the canvas app, I look for a portal that has the same name as a given uniqueSoltuionName of a solution being deployed.
Done:

portal download, if a portal of a given solution name will be found on Dataverse
if pipeline contains variable named "WebsiteId" then its value will be used to search for a portal and not the solution name
portal upload pre/post hooks
portal dowload pre/post hooks

Not implemented:

support for deployment profiles
portal versioning

@jenschristianschroder and @devkeydet would like to get your eyes on this. I've reviewed most of this with @mawasile but let's talk through it for the August release and invite @mawasile.

We'll need to ensure we have a sample solution with a portal in it.  Probably makes sense to have a separate sample solution than our current one since this would force everyone to ensure Power Pages is deployed in their environment to install our current sample solution.  I think that's too much of a dependency to force on others.  Assuming we go the route of a separate sample solution for Power Pages, we will also need to ensure that the sample solution is added to our pr loop e2e test.  I view both of these as release criteria to get this into an upcoming acceelrator release.

Closes https://github.com/microsoft/coe-starter-kit/issues/163

We'll need to ensure we have a sample solution with a portal in it. Probably makes sense to have a separate sample solution than our current one since this would force everyone to ensure Power Pages is deployed in their environment to install our current sample solution. I think that's too much of a dependency to force on others. Assuming we go the route of a separate sample solution for Power Pages, we will also need to ensure that the sample solution is added to our pr loop e2e test. I view both of these as release criteria to get this into an upcoming acceelrator release.

I've implemented Portal process in such a way, that when no portal/no portal's solution are present the pipeline should skip my tasks and successfully finish and not throw some exception.
I agree on having two use cases to test; one with portal and one without to confirm that new tasks are not impacting existing logic. Let me know if I can help with that somehow.

Closing this out as the code has been incorporated into https://github.com/microsoft/coe-alm-accelerator-templates/pull/175. Thanks @mawasile for the great collaboration on this. Looking forward to more to come!


distribution: Add distros for Embrace Android and Apple

This adds Embrace Android distribution for Java language, and Embrace Apple distribution for Swift language.

/fix:refcache


alpha blending issue for layers?

Hi! @MarkelZ
I have notised that you get different results (in this case for a blur shader) if you blur directly onto the screen, or if you first blur it onto a layer, save it and then render this layer.texture. The difference in this case is you get a black outline or not (see attached figures). I have attached a simple script to reproduce these results (change blur_init to False or True).
Not really sure why. Could it be that alpha blending for layers work a little different?
blur.zip

Hey! @OlaKenji
Thanks for your feedback. You're right, at first I thought it was the issue mentioned here, but then I saw that your blur shader actually implements that solution, while you still get a black outline.
Indeed, this is happening because when you render the blurred texture onto the empty layer, the engine alpha blends these two, whereas you just want to override the empty layer with the blurred texture.
So, I suggest to disable alpha blending, check out this fix:
blur_fixed.zip
I made two changes:

I added the function use_alpha_blending to the RenderEngine class.
I do engine.use_alpha_blending(False) before rendering the blurred texture, and engine.use_alpha_blending(True) afterwards.

Does this look good to you?
I think I can push these changes to the main branch since it doesn't affect backwards compatibility and it's a nice feature to have.

@MarkelZ
That's great, it works nicely and is an easy solution! I also think it is a nice addition to your engine.


RC3 Version of Jsonapi

Update code to produce JSON that matches the current spec of jsonapi.org.

Thanks, I saw that the RC3 canidate had been released already. It will probably be a few weeks before I have any time to spend on this project again. Updating to RC3 will introduce breaking changes to the API, so I want to make sure I have the time to update the test cases and test thoroughly myself. Thanks for your input though!

We will be making this change in a fork. Will then provide a pull request.

Published release v5.0.0, which produces JSON that matches jsonapi 1.0.0.rc3 specs.


add testing with ats

This PR:

fixes .abs/main.yaml
adds ats

Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml and values.schema.json are valid.

the values.yaml / values.schema.json test is failing atm, though I haven't changed the two files. Could it be that the test is counting the tests/test-values.yaml file that I have added as such a change? Because the test checks against the string "values.yaml" which technically exists in test-values.yaml

the values.yaml / values.schema.json test is failing atm, though I haven't changed the two files. Could it be that the test is counting the tests/test-values.yaml file that I have added as such a change? Because the test checks against the string "values.yaml" which technically exists in test-values.yaml

Please update your branch to the lastest master, I think the required changes were introduced by https://github.com/giantswarm/cloudflared-app/pull/28/files#diff-c70a68e380af0b06885a3e05a8062ded335ec477479b13ebecfdc9f016d7b97d

In case you want to run tests also in CI, you'll need to add some lines to the circleCI config file (please see other projects for reference, cert-manager for example)

Is this still ongoing? 🧐

Reviewed this just to get it removed from my "Review requested" list.


Use range_keys for more efficient Prefix::keys

Closes #53
Solution
Currently, Prefixes gained from something like MultiIndex might perform key iteration by going into a complex, custom dance of deserializing values of index-specific storage keys just to determine keys to iterate over. This doesn't allow us to just plug in range_keys.
In an attempt to make this possible, I split Prefix into two types:

Prefix - returned from most storage abstractions (e.g. by Map::prefix), this is now simpler, uses range_keys under the hood, and doesn't support the whole de_fn_kv dance in the first place
IndexPrefix - returned from MultiIndex and UniqueIndex, it supports the whole de_fn_kv dance, allowing (seemingly costly) key iteration in these complex scenarios

Disadvantages

Code duplication, although there's probably potential to clean things up by either extracting common logic from Prefix/IndexPrefix, or maaaaybe (?) implementing the custom key accessors (de_fn_kv and the like) using composition rather than as an integral part of IndexPrefix. I haven't thought about it a lot yet.
The types returned by e.g. MultiIndex::prefix and Map::prefix are now always different, although I doubt that has any significance.

Breaking API?
Yes. This is for the 2.0.0 bump.
TODO

[x] changelog

@chipshort Thanks for the review! Simon had doubts regarding how much code and complexity this PR adds. How do you feel about the overall approach? I don't love it, but it's also the best I could come up with without rewriting half the codebase.

At first I was a bit afraid of the amount of code too, but in reality it's not that much new code, since the whole IndexPrefix is just a copy of the old Prefix. I think it's a good approach given the constraints.
I do agree with your initial post though:

there's probably potential to clean things up by [...] extracting common logic from Prefix/IndexPrefix

In a first step, a lot of the helper functions can easily be deduplicated.
Then the Prefix/IndexedPrefix methods should be checked for duplicates (one example I see immediately would be clear). The easiest path for these is probably adding another helper function for this that both can share.
I wouldn't go too crazy on it, but at least exact duplicates should be avoided, I think.
It might be easier to do that in a separate PR merging into this one (or just a follow-up) in case @hashedone wants to review this too, because I think it's easier to review the general approach and deduplication separately.


Extrahop: Upgraded the app to support for Extrahop cloud, implemented on-poll a…

…ction
Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

@crestdatasystems Currently, we are in the process of acquiring the asset of ExtraHop cloud, once done we will prioritize the PR for GA.

@crestdatasystems We now have the cloud asset and the development team has started working on the automated failures fixation.


Update guidance on RAIL

What's changed, or what was fixed?
This is an update to our RAIL guidance including affordances for our newer loading metrics. It also introduces a more explicit call out for goals and guidelines for each area.
The goals and guidelines call outs are something the Chrome Speed Metrics team felt would make for a more clear framing of RAIL.
Fixes: #5464 with more details on what changed
Target Live Date: December 15th

[ X] I have run gulp test locally and all tests pass.
[ X] I have added the appropriate type-something label.

R: @petele @Meggin @kaycebasques
Notes: This is my last day in the office for this year. If anyone would like to take on directly editing/addressing further changes before the new year, I'm more than happy for them to do so :)

Whoops!
There were 14 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/rail.md#L57 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L65 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L69 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L73 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L81 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L163 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L165 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L177 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L185 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L203 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L217 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L228 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L255 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L261 - Line must be at most 100 characters

Does anyone have feedback on this one? :)

I'll check it out, Addy
On Thu, Dec 14, 2017 at 11:49 AM, Addy Osmani<EMAIL_ADDRESS>wrote:

Does anyone have feedback on this one? :)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/google/WebFundamentals/pull/5465#issuecomment-351817015,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEfsDrXNOxMg2W-oQDaSv5dfwKLFSlTNks5tAXvGgaJpZM4Q735Y
.

Thanks, Kayce! :)

(just a note that I started updating the doc and it's incomplete, so no one else should push commits to this branch or merge this PR)

Whoops!
There were 5 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/rail.md#L70 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L175 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L221 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L248 - Line must be at most 100 characters
src/content/en/fundamentals/performance/rail.md#L254 - Line must be at most 100 characters

Added do not merge tag to make it clearer. Let us know when you are ready to land.

Thanks @PaulKinlan, don't know why I didn't think of that
Working on this now!

:+1:

Biggest updates:

I really like the "goals/guidelines" organization, but when I went through the doc, the sections for R, A, I, L weren't following the definitions for "goals" and "guidelines" that we set out. "Goals" are timeless, "guidelines" are practical tips designed for today's conditions, so they may change over time. So I updated each section to try to better match these definitions.
Added a lot of content to the tools sections.

Considering the size of the changes, I think we've got to hand this back to @addyosmani to review (when he gets back). I've also got a few Qs that we need to resolve (adding them to lines of code after this comment)
All in all I think his new organization and my polish will be a big improvement to the guidance

:+1:


Sometimes using / commands will crash discord.

Happens in some servers, and not others.

Yes, we know about this issue. I pushed some fixes to the dev branch, could you checkout if the issue still persists?

Make sure to run npm run dist when switching the branch.

This issue should be resolved in 969c298b3ae52ee8b1dd8ea715b219328e357e07.

No activity after a week. closing this for now. Feel free to reopen it afterwards.


Move runtime files to a separate directory

Move configuration and log files (omnidb.log, omnidb.db, etc.) to a separate directory that docker can mount so persistent state can be moved to a separate volume for long-term storage.

Hi randombk,
Yes, this has been requested before. The feature will probably be included in version 2.6.0.
2.5.0 is coming out next monday. As you may have noticed releases come out very often (every 4 weeks), so this should be included soon.
Thank you for reporting this.
Rafael.

Hi @randombk ,
We implemented argument -d for the omnidb-server, which allows you to specify a home directory, where such files will be stored.
It is released along with 2.6.0 we just published. Can you please try? We'd love to hear your feedback on this, please, so I'm keeping this issue open for now.
Thanks and regards,
William Ivanski

Hi @wind39,
I can confirm that this seems to work well with both Docker volumes as well as dropping container permissions to the nobody user.
Thanks!
David


Add region to events

As ZITADEL developers we want to have the regionality feature implemented on the events, so everything can be stored according to the regionality.
### Tasks
- [ ] ...

closing this as we will implement regionality differently


Does not appear to work

Does not appear to work.  I've tried removing all items from ST, Alexa, and removing them from IDE.  I then go back in add them and try to execute them and it does not work.  It shows the user account logging into Alarm.com but it never ends up executing the command.  Any suggestions, or troubleshooting would be appreciated.  It worked fine up until the alarm.com web changes.  Thanks.

Dude... go update the Smartapp & DH. Schwark has got this working nearly perfect now. You are using outdated versions.

I’ve done that pulled code directly from github

On Mar 28, 2018 at 11:05 PM,  <adrian97c (mailto:notifications@github.com)>  wrote:
Dude... go update the Smartapp  &  DH. Schwark has got this working nearly perfect now. You are using outdated versions.
—
You are receiving this because you authored the thread.
Reply to this email directly,   view it on GitHub (https://github.com/schwark/smartthings-alarmcom/issues/15#issuecomment-377106228), or   mute the thread (https://github.com/notifications/unsubscribe-auth/AeImr3bX6bV9Dff-s1eifavKG2Hm9N_Sks5tjE-BgaJpZM4S_q3P).

@adrian97c tell me how to fix it then if I'm getting the code directly from Github that shows his latest updates? I'm copying them from the raw data file.

Hmmm not sure how you are the only one still having issues... very strange. Delete it all, then try updating via github intergration in ST IDE instead... once done let me know

@adrian97c it did not work for me. I deleted everything and imported it directly from the github repository.  Is there a way to see if it's bringing in the right code?  I don't know where to go from here.  Any logs we can provide to get this resolved?  Any other suggestions? I don't get why I'm still having issues when others seem to have it working just fine. I would love to have it working again.

What is the error you are seeing in logs?

@schwark I'm not sure exactly what you are looking for.  I just sent the disarm command and in the ST IDE there were no errors that I could see in the logging.  It shows that the "disarm" command is "on", in both IDE and the ST app but my panel still shows as Arm Stay.  When I log into my alarm.com account, I can see that the ST user we setup is successfully logging in, but it does not appear to be doing any commands.
Anything I can provide to you or try that can help I would be happy to.

I'm experiencing the same as @ryant80 (so you're not alone):
Problem: Alarm.com devices in the ST iOS app (Stay, Away, Disarm) trigger within the app and the ‘events’ show up in logs, but the actual alarm is not changed.
Assumptions:
I’m signed up with Frontpoint (who use alarm.com platform), and I can log in at alarm.com
I’ve followed all directions and can see the three triggers (Stay, Away, Disarm) in the ST app
I disconnected, removed, and deleted all devices, handlers, and ST connections (including Alexa)
Events:
The alarm.com event log indicates:
Website	Successful Web Login ([myaccount])	6:16 pm, Apr-21-2018
ST IDE indicates:
Arm Away switch is on
date	2018-04-21 6:16:25.401 PM PDT (2018-04-22T01:16:25.401Z)
So the logs are recording the same timestamp for activity, but no actual change in security system happens…
Where else can I look to view ‘logs’ with more detail?

I wish I could get this working. I don’t see anything in the logs and really wanted it to work

On Apr 21, 2018 at 9:31 PM,  <ericediger (mailto:notifications@github.com)>  wrote:
I'm experiencing the same as  @ryant80 (https://github.com/ryant80)  (so you're not alone):
Problem: Alarm.com devices in the ST iOS app (Stay, Away, Disarm) trigger within the app and the ‘events’ show up in logs, but the actual alarm is not changed.
Assumptions:
I’m signed up with Frontpoint (who use alarm.com platform), and I can log in at alarm.com
I’ve followed all directions and can see the three triggers (Stay, Away, Disarm) in the ST app
I disconnected, removed, and deleted all devices, handlers, and ST connections (including Alexa)
Events:
The alarm.com event log indicates:
Website Successful Web Login ([myaccount]) 6:16 pm, Apr-21-2018
ST IDE indicates:
Arm Away switch is on
date 2018-04-21 6:16:25.401 PM PDT (2018-04-22T01:16:25.401Z)
So the logs are recording the same timestamp for activity, but no actual change in security system happens…
Where else can I look to view ‘logs’ with more detail?
—
You are receiving this because you were mentioned.
Reply to this email directly,   view it on GitHub (https://github.com/schwark/smartthings-alarmcom/issues/15#issuecomment-383347559), or   mute the thread (https://github.com/notifications/unsubscribe-auth/AeImr6uiSiCemY1O45nTnR3nKhUTTrWJks5tq92EgaJpZM4S_q3P).

I seem to be having the same issue as above. I had this set up, was working wonderfully but stopped for some reason.  I deleted and reinstalled everything but still no dice. Like above, it says its doing something, however nothing changes.

This had broken for me when alarm.com made their last change but today I removed and re-added it and everything seems to be working for me again!

I'm having the same problem with Alarm.com/Frontpoint integration. Deleted everything in the IDE and started over with the Github repo.
Re-added app but My Home -> Things -> Arm Away and Arm stay are both perpetually on even when the system is disarmed. Clicking on them does nothing.
There's nothing in the ide/logs when I press the Arm Away/Stay buttons, but I can see logging when I toggle other switches.
I can login fine to alarm.com with the credentials I'm using for this SmartApp.
Any other things to try to debug for a solution?

Ok, In regards to kyleb1115 post where in he said:

I am having a similar issue with this. Disarm always works fine. Arm stay and arm away sometimes work.

I was having a similar issue in that My Disarm always works but the Arm Stay did not. I found after digging in the logs that the error was caused on line 413 of the Alarm.com smart app code on the HTTP post. What I found was that having the Use Bypass Sensors enabled (in the SmartThings Arm Stay switch settings) was what was causing the issue. When I turned it off my alarm would arm sucessfully. In the code it is called the forceBypass:true as shown in the postboy debug statement and then the error pops with Unprocessable Entity. I assume that they error is on the Alarm.com side. So for now the Use Bypass Sensors is disabled.
d4a942f3-9e61-487d-b730-44cf588b4dbd  7:13:22 PM: error something went wrong: groovyx.net.http.HttpResponseException: Unprocessable Entity
d4a942f3-9e61-487d-b730-44cf588b4dbd  7:13:22 PM: debug postbody:https://www.alarm.com/web/api/devices/partitions/xxxxxx-xxx/armStay::{"forceBypass":true,"noEntryDelay":false,"silentArming":false,"statePollOnly":false}

Similar but different issue - the setup does not show a field for my username, only password.  Anyone have that issue?


Arg validation clean up

Get rid of using the Track 1 Fx/ExceptionUtilities in favor of using Azure Core Argument methods. Also deleted a few other unused files.

@JoshLove-msft PR looks good to me. Thanks for cleaning this up.


Chip with icon still clickable when disabled

The icon of the element chip can still be 'clicked' when chip is set as disabled
Code used:
import "./App.css";
import { Chip } from "practical-react-components-core";
function App() {
  return <Chip text="chip is disabled" disabled onRemove={() => {}} />;
}
export default App;

Output:
https://user-images.githubusercontent.com/67017215/120985355-d4cc5d80-c77b-11eb-97b1-3f586921d8e8.mp4

Not passing onRemove={() => {}}  when chip is disabled will get rid of the X icon , and that's enough to solve this issue.
I'll close the Issue


photo upload updates for July

Docs Build status updates of commit b7d6d90:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit dac383c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 7e5de4a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/concepts/direct-endpoint-differences.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 820f8e6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OneDrive/onedrive-api-docs, working directory: W:\qh5f-s, target branch: live, target branch commit: 942d5e6a6152841c70532bcbcb49e07fcd61ffd3, source commit: 820f8e62dabca9b5c5abbf14ef83e6127f1b84ac.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 26203c8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/concepts/direct-endpoint-differences.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/driveitem.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingbinaryupdate.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingoperations.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 5870cb4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/concepts/direct-endpoint-differences.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/driveitem.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingbinaryupdate.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingoperations.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 46e2cb0:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/rest-api/concepts/direct-endpoint-differences.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/rest-api/api/driveitem_createuploadsession.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_get.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_list_thumbnails.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/api/driveitem_restore.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/driveitem.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/geocoordinates.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/hashes.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingcontentupdate.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/pendingoperations.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/resources/photo.md
:white_check_mark:Succeeded
View (>= odsp-graph-online)

docs/rest-api/concepts/direct-endpoint-differences.md

Line 80: [Warning] Link https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols-implicit contains locale code en-us. For localizability, remove en-us from links to Microsoft sites. For more information, see https://aka.ms/LocaleSpecificLinks.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


very different translation

The translation in the game is very different from what I actually translate when I go to the google page.
I try to use the servise that enters google translation in the config, but it doesn't work, as long as I enter the URL translation will stop.
How can I translate to the accuracy of my web version of Google Translate.

try my server local server with cache system for translation
https://github.com/bbepis/XUnity.AutoTranslator/issues/396
he uses google api
and how the translation looks like in the browser to me
there is also a wonderful cache system that will reduce the number of requests


Bot API 5.3 (June 25, 2021)

Bot API 5.3
Personalized Commands

Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
Added the class BotCommandScope, describing the scope to which bot commands apply.
Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
Added the parameters scope and language_code to the method getMyCommands.
Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.

Custom Placeholders

Added the ability to specify a custom input field placeholder in the classes ReplyKeyboardMarkup and ForceReply.

And More

Improved documentation of the class ChatMember by splitting it into 6 subclasses.
Renamed the method kickChatMember to banChatMember. The old method name can still be used.
Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.

how to make such a menu? https://telegram.org/blog/animated-backgrounds#bot-menu

how to make such a menu? https://telegram.org/blog/animated-backgrounds#bot-menu

Something like that...

a small example, with the commands.


Renaming PDF fields doesn't seem to work on fields used more than once

I.e. if the there's two fields with the same name, the tool can't seem to rename any of them, even if all of the renames that you give to each are the same name. Gonna take a quick look at this now, it wasn't blocking, but did confuse me for a bit.

Realizing how light of a wrapper this is over FormFyxer. This issue is almost certainly something wrong on that side, so I'll move it to that repo.


Tweak bingsearch

Requires https://github.com/ChrisTitusTech/winutil/pull/576 to be imported. If there is a bunch of conflicts I can create a new pull request
Pulled from #348

@ChrisTitusTech all set


Browser bundle needs a single entry point

Right now we're producing 3 browser bundles; there should be a single entry point, so that a correct Bower package can be made.

Resolved in https://github.com/aaron-em/same-encoder/commit/64e2da8eacb6fd7e4ae8d0197a90e96ae555d5f2


Liquid templating support

Adding support for liquid template in exporting / downloading files.
Making room to support other engines in the future. Added liquid as it is support across languages pretty well.
For now we can pack the template in by doing cat kubernetes-cluster/export* | base64 | pbcopy and pasta it into place. We should add a step to the artifact definition compiler that packs this template into the artifact.
I think we should put on this for now tho as we might end up w/ more files in here like provisioning.terraform etc. We may want to actually support a file system behind artifact-definitions like we have for bundles/apps. Lets see what we need before modifying the mass cli.

This should be noop to release. We'll need to iterate over the export types in the front end.


Update google-auth-library-credentials to 1.9.0

Updates com.google.auth:google-auth-library-credentials from 1.8.1 to 1.9.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.auth", artifactId = "google-auth-library-credentials" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.google.auth", artifactId = "google-auth-library-credentials" }
}]

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

Superseded by #191.