Update wp-data-loss-prevention.md

Microsoft FormsPro has been renamed to Dynamics 365 Customer Voice https://docs.microsoft.com/en-us/connectors/microsoftformspro/
The Dataverse connector is still called Common Data Service in the product https://docs.microsoft.com/en-us/connectors/commondataservice/

Will take to live via my working branch.


Fix single-threaded event-loop deadlock by using recursive_mutex

Fixed single-threaded event-loop deadlock by using recursive_mutex for AsyncEventBus's _callbacksMutex.
A single thread executed the event loop:
        while (!stop)
        {
            if (bus.waitFor(timeout))
            {
                bus.consume(100);
            }
        }

I discovered that when an event-handler was invoked that a deadlock would occur when I put another event on the bus from within that same event-handler callback method. With this change it works.

Thanks! I will prepare test shortly and I will merge. I need to check this also with develop branch as some big changes are happening :)

Hey so I revived your PR. I think that your fix can introduce other type of issues. I prepared proper test for this case on the development branch. New approach how EventBus should work eliminate this issue.
Other issues that I see:

If you use recursive mutex it means that processing of event may happen on other thread that was intended by calling process this may lead to data race.

Thanks!


[SMALLFIX] Fix wasb ufs and update docs

@aaudiber

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20251/
Test PASSed.

Please cherry-pick to branch-1.8


DXE-1960 --srcver option doesn't work

After using the following command, the "based on" value in the Property Manager UI doesn't show "Version 1" but the latest version.
akamai property-manager property-update -p <property> --srcprop <srcprop> --srcver 1
It seems --srcver option doesn't work.
Thank you in advance.

I'm from Akatec. Please let me know if you have any questions.

Hello @naraumi
Thank You for opening the issue. Can You confirm (or correct if any mistakes) steps to reproduce this issue?

Have some property (let's call it prop_1) with at least two versions (1 and 2).
You create a new property e.g. named prop_2:
akamai property-manager property-update -p prop_2 --srcprop prop_1 --srcver 1
The property is created correctly but it looks (in UI) that property was created from version 2. Is that correct understanding?

Thanks and best regards,
Wojciech

Hi @wzagrajcz
Thank you for checking my post.

The property is created correctly but it looks (in UI) that property was created from version 2. Is that correct understanding?

Yes, your understanding is correct.
In my test, I created a new version of the property with --srcver 1 but UI shows it is based on Version 202 (the latest version).

Regards,
naraumi

Hello @naraumi
Thanks for confirming that. After brief check it seems that indeed there is something wrong with this options.
We will go back to You if we have any update.
best regards,
Wojciech

Hello @naraumi
After some deeper investigation, I conclude that cli-pm works as expected: it's copying correct rules from correct property version to correct property. At this moment API does not directly allow to clone versions of other properties but to clone the latest version of target property and put rules from source property into newly created one.
Maybe it will help you to understand it better, learning what happens under the hood (at this moment) when running:
akamai property-manager property-update -p prop_2 --srcprop prop_1 --srcver 1
In this case, since user didn't specify --propver, cli would create new property version, by first cloning latest version of prop_2 and then updating its rules to the ones from prop_1 version 1. UI is showing the actual source of the property. So as we cloning the latest version of prop_2, then UI is showing that.
This works this way because, although PAPI allows creating new property version based on some version of the same property, it does not directly allow to clone versions of other properties. Therefore rules need to be copied "by hand" from one prop version to the other.
Thanks and best regards,
Wojciech

Hi, I'm noticing the same too:

I have a property with versions, for example version 1 through 10
I want to create a new version, based on the last deployed to "Production" version, let's say that's version 5
So I try

akamai pm property-update \
  --srcprop "example.com-UAT" \
  --srcver "5" \
  -p "example.com-UAT" \
  --message "Message test"

In the UI this creates a new version based of version 10, not 5


Setters don't set

First off, awesome work on this project! It really looks great.
I am running a modified version of the squareNumbers example (I have tried this on the original code as well):
const monkey = WebMonkeys()

monkey.set('res', [1, 2, 3, 4, 5])
monkey.work(5, 'res(i) := res(i) * res(i);')

console.log(monkey.get('res'))

But the final output seems to be the original 'res' array instead of the squares.
This happens with all of the examples. None of the 'set' statements seem to work for me.

That is unexpected. That same code as you wrote works for me. I even tested on the browser to make sure.
<head>
  <script src="WebMonkeys.js"></script>
</head>
<body>
  <script>
  const monkey = WebMonkeys();

  monkey.set('res', [1, 2, 3, 4, 5])
  monkey.work(5, 'res(i) := res(i) * res(i);')

  console.log(monkey.get('res'))
  </script>
</body>

The HTML above outputs [1, 4, 9, 16, 25] on the console. Does that not happen to you?

It prints [1, 2, 3, 4, 5] for me (in both the browser as well as node).
Device: MacBook Pro (mid-2012)
Graphics: Intel HD Graphics 4000
Browser: Chrome 52.0.2743.116 (64-bit)

I'm puzzled. No errors on console? Anyone with a similar problem?

Tested with node v6.2.0 and v4.4.7 on the same machine and no luck.
Safari 9.1.1, same machine, no luck.

It seems to work on my iPhone 5S in Chrome. I'm viewing the dev console via weinre.

I admit without being able to replicate I'm completely clueless. I'm not the most WebGL expert, chances somewhere on the code there are things that aren't 100% cross-platform. I know that because often I see some #ifdefs in other people codes that I didn't know are necessary. I'd love someone with WebGL experience to help me on those.
About your problem, I'll keep testing and wait it show up in a computer I can access to debug.

I think I've managed to recreate the bug. I've set up this CodePen to easily test on various devices:
https://codepen.io/omarshe7ta/full/rrOdAB/
On one windows laptop, I see:
1.0000052452087402,
4,
9,
16,
25

Windows 8.
Platform:    Win32
Browser User Agent:    Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
Context Name:    webgl
GL Version:    WebGL 1.0 (OpenGL ES 2.0 Chromium)
(According to http://webglreport.com)
On another, I get just:
1,
2,
3,
4,
5

Windows 10.
Platform: 	Win32
Browser User Agent: 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Context Name: 	webgl
GL Version: 	WebGL 1.0
I'm still looking into it, but I thought I'd post this here to collect more data.

Any news on this issue?
I've got the same problem, it doesn't set.


Implement provisioning callback

Connect #249.

Coverage decreased (-0.2%) to 90.581% when pulling e9cab5a3bbb40a80c27118f3758a3c0a8c3200d4 on jangsutsr:issue249_implement_provisioning_callback into fb6540b605fab703307c11f4544ba6c3e4ad5e1c on ansible:master.

Coverage decreased (-0.02%) to 89.526% when pulling a3cd4219e359e2aa0096ce9618278fa42e278134 on jangsutsr:issue249_implement_provisioning_callback into a40d0bed35b963506c18cd7b457715dfce92cf8d on ansible:master.


docs: AutoCon1 Documentation Updates

This implements all of the high priority documentation that we wanted to get done in advance of AutoCon1.
This re-uses a lot of existing docs but also adds in the following new things:

mkdocstrings which allows us to pull in documentation from our actual code and use our docstrings and code examples instead of re-writing or copy/pasting them in our documentation.
mkdocs-macros-plugin Allows us to add jinja (lol) templates into our docs. We can then use this to pull in examples of implementations from the example orchestrator's main branch. With this, we can show real running examples of code but not have to maintain it in two places.
abbr Allows us to add abbreviations to mkdocs that show up anywhere that abbreviation is used as a tooltip.
I also went ahead and added all of the skeleton files for all of the medium and low priority documentation that we want to add in the future.

Reminder: the full list of things we wanted docuemented is here.

I guess I added a bunch of docs or something too.

Domain Models
Forms
Subscriptions (Lives on the domain model docs)
App.py
Workflow Steps
I cleaned up and refactored a bunch of docs along the way.

Closes #529, #532, #539, #540, #543, and #545.

Thanks for the review @tjeerddie ! I think I addressed all of your comments, which are all great feedback. I think I linked the issues appropriately via this comment, but I'm not 100% sure on that.
https://github.com/workfloworchestrator/orchestrator-core/pull/616#issuecomment-2059110995


Ubuntu 24.04 userver

Note: by creating a PR or an issue you automatically agree to the CLA. See CONTRIBUTING.md. Feel free to remove this note, the agreement holds.

docker build -t ghcr.io/userver-framework/ubuntu-22.04-userver-base:latest -f scripts/docker/base-ubuntu-22.04.dockerfile .
docker build -t ghcr.io/userver-framework/ubuntu-22.04-userver:latest -f scripts/docker/ubuntu-22.04.dockerfile .

Падает
74.40 CMake Error: install(EXPORT "userver-targets" ...) includes target "userver-clickhouse" which requires target "clickhouse-cpp-lib" that is not in any export set.
74.43 CMake Error: install(EXPORT "userver-targets_d" ...) includes target "userver-clickhouse" which requires target "clickhouse-cpp-lib" that is not in any export set.


⚠ Bofrost.be has degraded performance

In 36d8c32, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1088 ms

Resolved: Bofrost.be performance has improved in 1c4e492 after 6 minutes.


MAINT: Endorse SPECs

cc @drammock there is https://scientific-python.org/specs/ , I assume you have thoughts/ideas/knowledge from the conference but wanted to get it on our radar.

SPEC0: The minimum version one I haven't ready but I assume is close to what we do anyway, and if that's the case we should endorse/officially adopt it
SPEC4: Nightly wheels I guess we could do but we're pure Python so seems unnecessary.

The interesting one is that might deserve some discussion is SPEC1 lazy loading. The lazy_load package idea seems great. We could maybe get rid of all of our nested imports except maybe matplotlib, and still have the nested import test pass. And import mne would be faster because @verbose creating functions does have a non-zero overhead, which I think accounts for most of this:
$ time python -c "import numpy, scipy"
real	0m0.123s
$ time python -c "import mne"
real	0m0.464s

But this would be another package to add to MNE-Python's dependency list (which has a high adoption cost as discussed before) or we'd have to vendor it, which would make the conda-forge people unhappy. Or we'd have to do some hybrid where we try: import lazy_loader; except Exception: <import our vendored one>.
@agramfort would vendoring a BSD module be problematic from the industry-adoption end?

Great idea! SPEC0 seems doable without much effort (in fact, if we drop support as per this spec, we will actually have less maintenance effort). I also like lazy loading, which we do anyway. For me, adding an additional dependency is worth the benefit of a 4x speedup. Although I'm not sure what the high adoption cost you're referring to means.

I'm not sure what the high adoption cost you're referring to means.

https://github.com/mne-tools/mne-python/pull/11565#issuecomment-1474453591
Hence my question to @agramfort about whether a vendored (BSD-compatible of course) dependency is a workaround. It seems like it should be since we take/adapt BSD-compatible code all the time in releases...

@larsoner are you talking about nibabel? I thought you were talking about the lazy-loader package. The question is if we really need it, because it is yet another layer that makes things more complicated (for devs). Maybe it is sufficient to import (large) modules inside function, like we already do.

@larsoner are you talking about nibabel? I thought you were talking about the lazy-loader package.

I linked to a thread where the discussion was originally about nibabel, but it's generally applicable to adding any new dependency, including the lazy_loader package that we're discussing here.

The question is if we really need it, because it is yet another layer that makes things more complicated (for devs).

I think in the end it might actually make it less complicated. Basically I think we can change our __init__.pys to use lazy_loader (or whatever), which is a tiny complexity increase for us. But it has three advantages:

SPEC4/ecosystem compliance
Reduced import mne time
No longer need to nest imports to stuff like scipy.linalg, etc. to keep import speed down

I'd expect point (3) to improve/simplify our code/contribution/maintenance requirements more than the __init__.py changes will worsen them.

I linked to a thread where the discussion was originally about nibabel, but it's generally applicable to adding any new dependency, including the lazy_loader package that we're discussing here.

I agree, but pure-Python lightweight packages with zero dependencies like lazy_loader shouldn't be a huge burden.
Re using lazy_loader vs. our current nested imports, we could try and see what it looks like. Your points 1 and 2 can be achieved without the package, just to be clear. Re point 3, if scipy already implements lazy import, then we can just import it without using lazy_loader ourselves, no?

@cbnr Just weighing in here as lazy_loader author: I think it's perfectly fine to use built in mechanisms (like we did for SciPy). The advantage of lazy_loader is that you can define imports as pyi files (so that code type completion still works in editors, which it won't otherwise). We have an environment variable for disabling lazy loading that's useful in testing. And we have informative deferred import errors.
But, none of that is needed; we're just trying to make it easy for libraries to switch to a lazy import strategy, since we think it's a good idea :) In particular: faster imports for users, and the ability to expose submodules without cost so that libraries can be explored interactively in, e.g. IPython.
Whatever route you choose, I'd be happy to review the changes for common gotchas!

I agree, but pure-Python lightweight packages with zero dependencies like lazy_loader shouldn't be a huge burden.

I don't think that was the consensus/conclusion we came to in #11565. I'll ask @agramfort about vendoring over there as well, so let's move discussion about adding additional dependencies there.

But, none of that is needed; we're just trying to make it easy for libraries to switch to a lazy import strategy, since we think it's a good idea :)

Indeed to me the standardization is nice. Similar to how everyone could have used try/except easily for Python 2-3 transition but six just made things easier and more standard for everyone.

SciPy being SciPy, don't really count on it I am afraid 😅 we have a tendency to want to do our own magic 🪄

@larsoner I had forgotten that only "core" projects can endorse SPECs, but I've opened https://github.com/scientific-python/specs/pull/271 to add us to the list of "adopters" of SPEC001 (lazy loading).  Depending on how they respond to that one I'll look deeper into what we should do re: SPEC000 and 004

Okay I think that's probably good enough to close the issue at our end for now, then!

Just to emphasize one point from above: unless lazy loading happens in .pyi files, type checkers won't know about those functions. See:
https://scientific-python.org/specs/spec-0001/#type-checkers


update template to fix active page

Switching from highlighting active elements based on a partial match to needing a full match for /kubernetes as that is a substring in other URLs.
If we prefer to update everything to need a full match to keep up with consistency, I can do that as well. But I think I will make a follow-up PR cleaning up templates a little bit.

Will update the PR to have wider clean ups and make this more consistent across all templates.

Will be sure to check this is fully resolved as part of the v3_ToC work.
Looks like there are other PR associated with this; but will test to be sure.


Delayed Job process, liquid_droppable.rb exception causes a warning.

The Delayed Job process occasionally throws an exception about having an already initialized constant:
19:11:47 dj2.1      | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: already initialized constant Kernel::AgentDrop
19:11:47 dj2.1      | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: previous definition of AgentDrop was here
19:11:47 dj.1       | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: already initialized constant Kernel::AgentDrop
19:11:47 dj.1       | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: previous definition of AgentDrop was here
19:11:47 dj2.1      | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: already initialized constant Kernel::EventDrop
19:11:47 dj2.1      | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: previous definition of EventDrop was here
19:11:47 dj.1       | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: already initialized constant Kernel::EventDrop
19:11:47 dj.1       | /home/drwho/huginn/app/concerns/liquid_droppable.rb:24: warning: previous definition of EventDrop was here

I've configured Huginn to run multiple Delayed Job processes so this may have something to do with it but I'm not sure.  Is there something I can do to get better debugging information?

/cc @knu @dsander

Thos are just warnings, nothing to worry about. I will try to get rid of them.

I remember seeing those warning locally before, but now I can't reproduce them.

I think that was f886bdf00d2cfb0b60ac63016679e3dacb16d9ad

Interestingly enough, if had the same issue again today :smile:
@virtadpt  It looks like you are running your workers in the development environment. It might help the memory usage and overall performance to run them in production via export RAILS_ENV=production; bundle exec script/delayed_job run

Hmmm... are there official instructions for kicking into production mode?  I tried a few weeks ago (after doing some research) and hosed my instanance pretty badly.

I think there is none for 'manual' deployment. All that needs to be done is to copy your development settings in the database.yml to the production section and then starting delayed_job with the command above.

Don't you need to bundle assets too?

@cantino Not if you just run delayed job in production

Oh, interesting.  Do you think we should somehow make that a default?

Unsure, it might be nice to have the verbose development log by default.


Implement match ergonomics (binding modes) in type inference

E.g.
let x = Some(1);
match &x {
    Some(n) => n, // n should be &i32
}
match &mut x {
    Some(n) => n, // n should be &mut i32
}

and so on. We currently just infer wrong types in this situation. To fix this, when walking through patterns with infer_pat, we need to keep track of the 'binding mode' and apply it when creating bindings. This is also explained in the rust reference; and I think rustc handles it here.

I'll try it :)


A pointer cursor that can be rotated to determine a new facing direction

Similar to the existing pointer direction indicator prefab

The existing pointers should be able to have their cursor rotated already. Just need to provide a mechanism for accepting input to rotate the cursor i think.

duplicate #47


Didn't delete files in proj folder

Describe the bug
I delete dialogs in composer, but files in my project folder remain.
Because creating and deleting files are frequent things. There will be many files leaving in my disk.

Browser

[x] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

I think we resolved one issue like this before, looks like a regression, @lei9444  @liweitian  can you help check is there recent changes brought this?

Try to reproduce this and find only directory is left but all the files have already been deleted.
For the dialog delete action. only first time (eg. delete dialog 'abc'),  hit following error.
 but no errors for the upcoming delete action.

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2587


Separate module for exceptions

What does this PR do?
Separate module for exceptions.
Motivation
Cleaner code.
Additional Notes
Anything else we should know when reviewing?
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

it just looks like a read timeout, 4s which might be too onerous
shall i make a separate PR for that?

Sure

Can we merge this for now? Thanks!

@ofek Please see related #3182.


Correct the @context description and examples

The @context is described as below in the spec.

Fixed to https://openvex.dev/ns before 1.0 is released.

However, go-vex seems to assume v0.0.1 if the version is not specified in the @context field.
https://github.com/openvex/go-vex/blob/eb8ba79cc7f8bc61f5fe76f0ba37e1b3c51099b268/pkg/vex/functions_files.go#L96-L105
Then, it tries the legacy parser.
https://github.com/openvex/go-vex/blob/eb8ba797f8bc61f5fe76f0ba37e1b3c51099b268/pkg/vex/functions_files.go#L107
The test data actually uses this schema.
https://github.com/openvex/go-vex/blob/78e7ed9e613876b1e8948191a4c96dd79760f2ab/pkg/vex/testdata/v0.2.0.json#L2
It is not documented as far as I know. This PR corrects the description and examples. Please correct me if I'm wrong.

Great catch @knqyf263! Thanks for fixing this. I think it is ready to merge, can you just  git commit  --amend --signoff and repush the commit so that the DCO check passes?


feat: Add Pdb struct and PdbBuilder

Description
Part of https://github.com/stackabletech/issues/issues/435
Definition of Done Checklist

Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
Please make sure all these things are done and tick the boxes

# Author
- [x] Changes are OpenShift compatible
- [x] CRD changes approved - In ADR
- [ ] Integration tests passed (for non trivial changes)

# Reviewer
- [ ] Code contains useful comments
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)

# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added

Fixed the abbreviation. Only thing missing are docs

@Techassi feedback addressed, please have another look

Thanks a lot for the review!


Users on beta distribution lists should not be required to create App Center accounts

I am migrating my Mac beta app from Hockey App to App Center:
Previously, Hockey App allowed users to be on a beta distribution list, and download beta builds, without requiring them to create a Hockey App account. This made it easy to recruit beta testers for my app.
However, App Center requires users on a beta distribution list to create Microsoft/App Center accounts. This raises the diffuculty bar in recruiting users to for semi-public/private beta testing becuase it forces users (who are volunteering their time to beta test my app) to now create accounts.
There is the option to create a public download link, but this is not secure because it can be shared with users outside the ditribution list. Alternatively, continue to use Hockey App until it's EOL.

@tinrocket thanks for bringing this up. We're aware and have "allow to download releases from public distribution groups without authentication" on our list.

@tinrocket just to be sure I understand you correctly. On HockeyApp there's a private and a public page. The private one can be accessed by users of the app only and the public one by anyone who has the link. Despite the authentication for the public links on App Center, everything works the same.

@tinrocket public distribution groups are also available without authentication now. Would that resolve your issue?

@derpixeldan Thank you; I will take a look tonight. I have not been able to follow up on your earlier questions yet.
(Yes, a support member (Alex E.) did mentioned that it was on your todo list, and suggested making a user-request.)

@derpixeldan Yes, I think public distribution groups is working solution for my current situation. I did the following:

I enabled the public link option in a distribution group
I sent a reminder to a tester in the group (who had not registered) to download the last release
They were able to access the build without logging in.

Is this what you mean by public distribution groups?

@tinrocket great! Yes, that's exactly what I meant. I'm closing the ticket, feel free to re-open when you have additional questions on that topic.


Question on handling promises.

Dear Daurnimator, may I cross-post my question on reddit about promises ?
Any clues very much appreciated, thank you, Jon.C.

Looks like you figured it out. https://www.reddit.com/r/lua/comments/x3mqkc/comment/imx93tn/?utm_source=reddit&utm_medium=web2x&context=3


Affine transformation

We would like to contribute "affine" code to nifti-rs. A part of the code is in our private compagnie codebase and the rest is here.
I think it belongs in nifti-rs because:

it doesn't belong in trk-io, nor in our private codebase :)
it totally depends on NiftiHeader struct.
some people might need it and this is where they will search first.

In fact, I consider nifti-rs to be the Rust version of NiBabel, so of course it should be in nifti-rs. What's your opinion on this?
Disclaimer: Most of the code has been ported from NiBabel. I don't know much about licensing and I don't like to care about it.

That sounds quite interesting, and could narrow the gap towards other features of this library.  :+1:

I consider nifti-rs to be the Rust version of NiBabel, so of course it should be in nifti-rs. What's your opinion on this?

To my understanding, NiBabel can handle a plethora of other neural imaging formats, whereas I wish to focus this library on NIfTI. We can add that logic anyway, and perhaps consider making it an opt-in or separate component if it becomes large enough to stand on its own.

Disclaimer: Most of the code has been ported from NiBabel. I don't know much about licensing and I don't like to care about it.

NiBabel is covered by the MIT license, so we can use it as long as we include their copyright + permission notices in the ported module .rs file.

Indeed, that is fair and nice. :) Feel free to send in the PRs and I'll do the usual reviewing when possible.


lexer design for performance

Hi,
I am really looking forward to using your library.
I suggest using a a traditional lexer (w/o goroutines) now that the library is young so that is eventually production ready (i.e. able to get best performance).
See references:
https://medium.com/@farslan/a-look-at-go-scanner-packages-11710c2655fc
https://groups.google.com/forum/#!msg/golang-nuts/q--5t2cxv78/Vkr9bNuhP5sJ
That talk was about a lexer, but the deeper purpose was to demonstrate how concurrency can make programs nice even without obvious parallelism in the problem. And like many such uses of concurrency, the code is pretty but not necessarily fast.
I think it's a fine approach to a lexer if you don't care about performance. It is significantly slower than some other approaches but is very easy to adapt. I used it in ivy, for example, but just so you know, I'm probably going to replace the one in ivy with a more traditional model to avoid some issues with the lexer accessing global state. You don't care about that for your application, I'm sure.
So: It's pretty and nice to work on, but you'd probably not choose that approach for a production compiler.
-rob

Apologize for the bad formatting. I will figure out markdown syntax next time

Fixed the syntax for you.
I'm not entirely sure what point you're trying to make btw

(updated comments)


Cannot GET & Certificate Expired

It looks like the LetsEncrypt Certificate expired for https://remote.craftos-pc.cc/
The URLs generated don't seem to work, in CC wget fails to load the anything from the URL
In browser (with a new link) results come back like Cannot GET /server.lua%20oWl-kTU1whiFjXG8yM75QjmvPrJeXbvQti4d5PQT.

Argh, certbot really annoys me sometimes.


error 523 while accessing rehike.hiew.me since yesterday

I tried recently to access the rehike.hiew.me client but the site don't load, it just display a cloudflare message.

Server down, it should be up now!


when plane disarmed , motor is disarmed ,but rudders are not disarmed

hi
when plane is disarmed , why rudders are active?
I don't want this，what can i do ?
thanks!

The safety switch enables/disables servo control.
Being able to run servos is important for a ground test prior to arming.

So in other words: If you use the PX4 safety switch on the plane you can disable everything. So no need to change anything.


Tidy dotnetcore logging messages sent to Elastic

Multiline log entries in Elastic from dotnetcore applications are being treated as separate log entries (e.g. 4 lines = 4 separate messages).
I have encountered this before and it was a case of changing the output format of logs.

This is something we want for the Scala apps too – so if you can provide pointers to how to do this, we'd be interested!
https://github.com/wellcomecollection/platform/issues/4546

Found some docs I had from previously handling this, which was slightly different as it was using Filebeat rather than Fluentbit but the same premise seems to stand.
I recall configuring app logs to adhere to a predefined format but I'd forgotten the need to configure Filebeat/Fluentbit to look for that "predefined format" and treat that as multiline. I think we'd need to make a change to the Wellcome/fluentbit image to contain this config (see https://coralogix.com/log-analytics-blog/parsing-multiline-logs-the-complete-guide/ and https://stackoverflow.com/questions/51645296/fluentbit-with-mycat-multiline-parsing).
cc/ @alexwlchan

Leave open but take off critical path.


Upgrade ElasticSearch framework to version 0.4

Continuing where mesosphere/universe#210 left off.
I tried this on a newly created DCOS cluster and couldn't seem to find any issues.

@mwl I'll test again

@mwl  it is failing to startup... here is stderr
mesos-docker-executor: /lib64/libcurl.so.4: no version information available (required by /opt/mesosphere/packages/mesos--15eedb84c2130af4b4b7cb0a3da7581ec54f244e/lib/libmesos-0.24.1.so)
I1008 18:01:02.295522  2152 exec.cpp:133] Version: 0.24.1
I1008 18:01:02.298290  2155 exec.cpp:207] Executor registered on slave 20151008-173533-1828978698-5050-1416-S4
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/tmp/elasticsearch-mesos-scheduler.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/tmp/elasticsearch-mesos-scheduler.jar!/lib/slf4j-log4j12-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@716: Client environment:host.name=ip-10-0-0-84.us-west-2.compute.internal
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@723: Client environment:os.name=Linux
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@724: Client environment:os.arch=4.1.7-coreos
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@725: Client environment:os.version=#2 SMP Wed Sep 16 22:54:37 UTC 2015
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@733: Client environment:user.name=(null)
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@741: Client environment:user.home=/root
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@log_env@753: Client environment:user.dir=/
2015-10-08 18:01:12,023:6(0x7fcb38cb2700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=master.mesos:2181 sessionTimeout=20000 watcher=0x7fcb899d2a60 sessionId=0 sessionPasswd=<null> context=0x7fcb0c000930 flags=0
2015-10-08 18:01:12,026:6(0x7fcb327fc700):ZOO_INFO@check_events@1703: initiated connection to server [<IP_ADDRESS>:2181]
2015-10-08 18:01:12,029:6(0x7fcb327fc700):ZOO_INFO@check_events@1750: session establishment complete on server [<IP_ADDRESS>:2181], sessionId=0x15048862e760018, negotiated timeout=20000
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@712: Client environment:zookeeper.version=zookeeper C client 3.4.5
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@716: Client environment:host.name=ip-10-0-0-84.us-west-2.compute.internal
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@723: Client environment:os.name=Linux
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@724: Client environment:os.arch=4.1.7-coreos
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@725: Client environment:os.version=#2 SMP Wed Sep 16 22:54:37 UTC 2015
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@733: Client environment:user.name=(null)
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@741: Client environment:user.home=/root
I1008 18:01:12.038957    21 sched.cpp:157] Version: 0.22.1
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@log_env@753: Client environment:user.dir=/
2015-10-08 18:01:12,038:6(0x7fcb3b4b7700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=master.mesos:2181 sessionTimeout=10000 watcher=0x7fcb899d2a60 sessionId=0 sessionPasswd=<null> context=0x7fcb14000c10 flags=0
2015-10-08 18:01:12,042:6(0x7fcb317fa700):ZOO_INFO@check_events@1703: initiated connection to server [<IP_ADDRESS>:2181]
2015-10-08 18:01:12,044:6(0x7fcb317fa700):ZOO_INFO@check_events@1750: session establishment complete on server [<IP_ADDRESS>:2181], sessionId=0x15048862e760019, negotiated timeout=10000
I1008 18:01:12.044502    37 group.cpp:313] Group process (group(1)@<IP_ADDRESS>:36882) connected to ZooKeeper
I1008 18:01:12.044533    37 group.cpp:790] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0)
I1008 18:01:12.044548    37 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
I1008 18:01:12.047902    37 detector.cpp:138] Detected a new leader: (id='1')
I1008 18:01:12.048106    32 group.cpp:659] Trying to get '/mesos/json.info_0000000001' in ZooKeeper
Failed to detect a master: Failed to parse data of unknown label 'json.info'

Ah, yeah that'll why
I1008 18:01:02.295522  2152 exec.cpp:133] Version: 0.24.1

I'll start working on mesos/elasticsearch/issues#338 tomorrow. Sorry for that!

ah... good point

LGTM for multiverse... tested on our stable dcos!


Move slang-test to use the new compilation API.

I am very interested in working on this.
It will be a good chance for me to learn more about our reflection APIs, which I am not very familiar at this point.

I think this is more about the compilation API, the reflection logic can most likely remain unchanged. But this is a good opportunity to get familiar with the compilation API.


update mobile phone location and carrier identification data for China, ...

...fixes #608

Have you signed the contributor agreement already?
https://github.com/googlei18n/libphonenumber/wiki/ContributeToTheProject
Thanks!

Thanks for your notice. I have signed it. Please review my submission.

Thanks @chaoaero! We recently did a complete revision of the China metadata, but we will look at this patch and apply anything we may have missed out.
We stopped accepting PRs for metadata updates but we have no document to reference for this request, so I'm keeping it open to reference the changes.

Closing this PR.

We aren't adding 149 because nothing has changed since we closed issue #608.
Carrier data has been updated in the meantime.
We will update the extra geographical data ourselves, and reference it as being contributed by you in the metadata file.

Ah, just noticed the extra geographical data is also for this prefix.
Okay, when/if the prefix starts getting used in real life we will update it and reference it as your contribution :)

ok
2017-07-14 16:52 GMT+08:00 lararennie<EMAIL_ADDRESS>
Ah, just noticed the extra geographical data is also for this prefix.
Okay, when/if the prefix starts getting used in real life we will update
it and reference it as your contribution :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/libphonenumber/pull/609#issuecomment-315307694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB85sg0wJOLBYmbjQnIsRWXUbKClYY-Oks5sNyw4gaJpZM4Dex3m
.


Please support https://www.rmcbfmplay.com/ tv channels

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I'm running yt-dlp version 2022.09.01 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and am willing to share it if required

Region
France
Example URLs
https://www.rmcbfmplay.com/video/rmc-decouverte/retour-a-linstinct-primaire-s6/s6e1-lune-de-miel-dans-la-jungle?contentId=Product::NEUF_RMCDEC_RMC00174485&universe=PROVIDER
Provide a description that is worded well enough to be understood
Please support downloading replays from https://www.rmcbfmplay.com/ as their player is ads bloated to the point of not working.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--xattrs', '--add-metadata', '--embed-thumbnail', '--embed-subs', '--no-continue', '--hls-prefer-native', '--audio-quality', '0', '--all-subs', 'https://www.rmcbfmplay.com/video/rmc-decouverte/retour-a-linstinct-primaire-s6/s6e1-lune-de-miel-dans-la-jungle']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.09.01 [5d7c7d656]
[debug] Lazy loading extractors is disabled
[debug] Python 3.11.0rc2 (CPython 64bit) - Linux-3.18.115-17011592-aarch64-with-glibc2.36.9000 (glibc 2.36.9000)
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 5.1.1 (setts), ffprobe 5.1.1
[debug] Optional libraries: Cryptodome-3.15.0, brotli-1.0.9, certifi-2021.10.08, mutagen-1.45.1, pyxattr-0.7.2, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
[debug] Loaded 1670 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.09.01, Current version: 2022.09.01
yt-dlp is up to date (2022.09.01)
[debug] [generic] Extracting URL: https://www.rmcbfmplay.com/video/rmc-decouverte/retour-a-linstinct-primaire-s6/s6e1-lune-de-miel-dans-la-jungle
[generic] s6e1-lune-de-miel-dans-la-jungle: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] s6e1-lune-de-miel-dans-la-jungle: Extracting information
[debug] Looking for Brightcove embeds
[debug] Looking for embeds
ERROR: Unsupported URL: https://www.rmcbfmplay.com/video/rmc-decouverte/retour-a-linstinct-primaire-s6/s6e1-lune-de-miel-dans-la-jungle
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1459, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/yt_dlp/YoutubeDL.py", line 1535, in __extract_info
    ie_result = ie.extract(url)
                ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/yt_dlp/extractor/common.py", line 670, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/yt_dlp/extractor/generic.py", line 3078, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.rmcbfmplay.com/video/rmc-decouverte/retour-a-linstinct-primaire-s6/s6e1-lune-de-miel-dans-la-jungle

Duplicate: https://github.com/yt-dlp/yt-dlp/issues/3594
It looks like content of this site has DRM, so we cannot support it.

@coletdjnz some videos have drm but other ones can be played on my rooted Android device. Please reopen!


Update Angular Version in peer dependencies

Hi,
Trying to upgrade my application to Angular 17, but need the angular dependencies' versions listed in ngx-three's package.json to be bumped up.
Thanks!

@AnyFinCanHappen thanks for the PR totally missed that


Add support for focus

Thanks for this little gem! Please consider adding focus support, so we could add the image inside a <label> element to create some cool interaction in HTML forms.

Hi @pagelab,
I've been looking into this. I have it working but only on Chrome. Apparently Firefox doesn't support focusing images. I ended up on this stack overflow question but it doesn't seem to work on Firefox.
I'll keep investigating when I have time.
Thanks for suggesting this!

It kinda works in Firefox with contenteditable applied.
https://codepen.io/PageLab/pen/mddZedd

What about focusing some other element (say its container or adjacent element, like a button)? Add an attribute like data-focus-target to the image element we need an effect for that accepts a selector, and whenever an element that matches the selector gets focused the effect would get executed.

Since it's not clear how an image can be focused I am inclined to think that Creepyface should not support this by default. However it is not hard to do it from your own code:
const img = document.querySelector('img')
img.addEventListener('focus', () => img.src = 'img/focus.jpg')
img.addEventListener('blur', () => img.src = 'img/serious.jpg')

What do you think?

It seems good enough for me.

I'll close the issue then. I might get back to this once the bug is fixed on Firefox.
Thanks!


Added Hyperlinking for Phone Numbers

This and #49 handles different pages and they're not duplicates.

Noted , Will Merge


Architecture: should Interactor and Presenter be coupled?

Reference [2] (The Source of our Principles and Assumptions) presents Interactor component as defining two interfaces:

InputPort aka InputBoundary, which is owned and implemented by the Interactor; this is an obvious part of the pattern and it's easy to implement.
OutputPort aka OutputBoundary, which is owned by the Interactor, but implemented by the Presenter, outside of the application layer.

I'm fine with the design, but I find it tricky to meet all the assumptions in the latter boundary. The key question is: should Interactor and Presenter be coupled? The [1] delves into details and I just sumarize it below.
References:

SO question: Clean Architecture: Use case containing the presenter or returning data?
The Uncle Bob: The Clean Architecture (figures)

An Interactor which calls the presenter
The second solution: an Interactor which calls a Presenter.
def controller(presenter, some_data):
    request_model = RequestModel(some_data)
    interactor = Interactor(presenter, some_dependency, other_dependency)
    # ... and here's the application layer call
    interactor(request_model)

Benefits:

No close coupling between controllers and presenters. Building request models and orchestrating components by the controller has nothing to do with presentation process.

Drawbacks:

This is not functional at all. Any test on the controller has to check side effects made on the presenter. I don't find it clean and easy to read.
All web frameworks I know implement "return the response" pattern for their controllers. They don't print anything like CLI frameworks, send any data via message broker like microservices used to do. Should we align to this imperative pattern?

@jakos, would you like to state your opinion about this topic? I recommend reading [2] as it gives quite nice analysis.

Lately I've heard an argument that makes me almost convinced to design nr 2 (an Interactor which calls the presenter). It goes like this:

We [web developers] are quite familiar and used to a pattern where an Interactor just returns data and respective Controller just passes them somewhere (i.e. to a renderer, a View, etc). This is a simple case due to synchronous and stateless nature of HTTP protocol. The rest of the world does not have such simplicity: desktop or mobile applications, asynchronous microservices or any interactive interface have to support concurrent and/or distributed request processing. It may mean that the Presenter may work on a different thread (e.g. UI thread) or publish to a different machine than the Controller works. Orchestrating the Presenter and the Controller as independent Components contributes to The Clean Architecture design at the layer of integration Interactors into different application environments.

@lhaze
After reading discussion [1] I'm for the second solution. I think i'ts exactly what Uncle Bob said:

For example, consider that the use case needs to call the presenter. However, this call must not be direct because that would violate The Dependency Rule: No name in an outer circle can be mentioned by an inner circle. So we have the use case call an interface (Shown here as Use Case Output Port) in the inner circle, and have the presenter in the outer circle implement it.

But what about the drawbacks? Testing is very important for me and I can't just ignore this issue. Maybe Interactor could just return the Presenter? Then it could be tested or maybe even used to return response like in classic web framework. That would be only an option, because like you stated in last comment Presenter could do something totally independent - publish to different machine etc. We could just examine it's state during tests.

Ok, I think I'm convinced to solution # 2. Adequate pull request is welcomed, maybe it is my responsibility though.
I think clean design of test process would lead to TestPresenter implementation, which would just collect response data. It would have test helper methods as well. It could be not do bad.


Correct types in WorkflowStep.ts

Summary
This pull request fixes the types in WorkflowStep.ts.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

The build appears to be failing for formatting reasons

Applied prettier

great catch @seratch!


Approaches to managing development flow?

** Which Category is your question related to? **
amplify-cli
** What AWS Services are you utilizing? **
appsync, amplify, amplify-cli
** Provide additional details e.g. code snippets **
I've started a side project with appsync and started using the CLI to create resources. It's simple and helpful in a nice way. But to be honest, I am confused about how it fits into a development workflow... one that can standup in a production environment. Based on research and articles it seems the options are:
Option 1: Handle everything through the CLI
This means that the resources are created. But once they are created, you need to update and manage everything in the AWS console (besides the schema.graphql. If you want to modify the resolvers, you have to do that in the console. If you modify the schema in the console and then run amplify push locally your changes are overridden with what you had locally even though it's out of sync.
So: good for getting started but little flexibility because most things are abstracted and if you need to update, you're in the AWS console. You wouldn't want to check the backend api into your repo because it gets out of sync.
Question about this option: is there a better way to manage things locally? to keep it in sync with changes in the console?
Option 2: Manage yourself via cloudformation, terraform, serverless
Take most of the abstraction out of it and handle resources yourself. The schema is local, the mapping templates (resolvers) are local and deployed based on your configuration. This provides more control and can handle different stages (dev, release, prod).  The downside is you don't have some of the abstraction magic... all of the resolvers aren't created for you. My understanding, though, is that once you push the schema to appsync.. you could run amplify codegen and get all of the queries, mutations, subscriptions locally.
Question about this option: If you don't attach a mapping template to a field, does appsync create it for you or does it just not have a one attached? For example, if I has an @aws_auth directive as part of my schema, would I get that for free if I push up my schema without a resolver or do I need to handle that myself?

Thanks to the team for all the work you are putting in. It's an impressive product and I'm sure will only get better.

@rcwestlake Just to give you an idea, we're close to complete with the beta version of team-workflows and CI/CD flows as part of the Amplify CLI and working actively on our documentation. As soon as we launch it, I'll update this thread (expect an announcement sometime next week).
This release should answer all your questions above.

@kaustavghosh06 any progress?

@cojack Please take a look at #508

Yeah, but the #508 is more about how to provide a flow and not about how to locally create a datasource map them to specific source type like Lambda and then attach field to resolver that we create in a step before. This part is missing in amplify @kaustavghosh06 and it has to be done manually in amazon console if you don't follow the CloudFormation schema.

Looking for a way to modify resolvers locally and push to amplify.

Hey guys, we released support for custom resolvers as part of the CLI versions > 1.0.0. please feel free to check it out and let me know if you've suggestions regarding the same. Looking forward to your feedback.

Hey guys, I'd like to harken back to the original question by @rcwestlake as I still feel some questions are unclear.
My situations is as follows
I'm managing a project that consists of an iOS App, an Android App and a ReactJS based WebApp. They all connect via AppSync to existing DynamoDB tables. In the future new tables may be added or removed. MobileHub doesn't fit that requirement, so I've been experimenting with Amplify/AppSync. The only way I managed to get to the aforementioned setup is by creating an AppSync API and adding the tables via the console, autogenerating the graphql statements, and then running

amplify init
and
amplify add codegen --apiId

in each of the local directories (iOS, Android, React JS).
So I ended up with three separate amplify projects locally with separate Coudformation stacks connecting to one AppSync API endpoint, while the AppSync API and DynamoDB tables could only be managed via the AWS console. Obviously, this is not a setup suitable for production. I am trying to wrap my head around if there's an option to get to a production setup without having our development environments reference the production API endpoint or replicating the a mirror image of the API and manually changing the endpoints in all of the local directories.
Overall I'm very impressed with Amplify, so I hope there is a way to use it for production.

@SebastianKirsch123 believe they've come up with something that solves that... I remember reading about it when it first came out. Because I didn't have the time to wait, I went ahead and used Serverless to manage all the infrastructure and stages (dev/prod). It has worked well so far.
A couple resources:
https://github.com/sid88in/serverless-appsync-plugin
https://read.acloud.guru/deploy-a-graphql-service-on-aws-with-the-serverless-framework-7af8fc22a01d
I might come back to amplify-cli once it's a bit more proven / I have the time to dig in.

I've come up with a configuration that, while far from perfect, works for my scenario. I've only tried it using an API key for authentication and iOS/Android/ReactJS
I'll detail the process. May help some people who need to maintain a separation of environments across multiple frontends:
Pick one of the local directories (I chose iOS/Xcode )
Create a new amplify project on the command line:
amplify init
-> choose dev as environment in the setup client
Create the api locally with:
amplify create api
Now create the schema for the dynamoDB tables locally in your "schema.graphql" file (located at /amplify/backend/api/your_project )
Repeat the same process for all the other amplify features you need
Push to the cloud with:
amplify push
This autogenerates the api and database tables according to your local schema and any other resources you've created locally.
Create the test environment:
amplify env add
-> choose test as environment in the setup client
Then run:
amplify push
repeat the same steps for your prod environment.
This creates a mirror image of the dev resources in the cloud: new api, new db tables, etc.
DO NOT add any resources locally while you are in test or prod, since your environments will be out of sync.
Now you can go to the AppSync console. You'll see three different environments. Head into the dev  simply follow the steps listed there for integration with your other frontends.
In this setup one project holds the cloud backend locally, whereas the others only get the API endpoint.
This way you can work in the dev environment
Once you move into the testing/production stages, you'll go to your project with the cloud backend, change into your desired environment and run amplify push.
In your other projects you need to change the API endpoint and access key in your local awsconfiguration.json or aws-exports.js files.
Once you go back to development, change the endpoints and keys back to dev. To make the process safer you should probably version control the local backend via git. I left this out for simplicity's sake


Merge only works when trigger phrase is present

The code at https://github.com/jenkinsci/ghprb-plugin/blob/master/src/main/java/org/jenkinsci/plugins/ghprb/GhprbPullRequestMerge.java#L129-L135
        // If merge can only be triggered by a comment and there is a
        // comment
        if (commentBody == null || !helper.isTriggerPhrase(commentBody)) {
            logger.println("The comment does not contain the required trigger phrase.");
        } else {
            intendToMerge = true;
        }

Is preventing a merge if the trigger phrase is not present in the comment. Nowhere in the configuration does it say anything about a trigger phrase for merging, and "Only use trigger phrase for build triggering" in the Build Trigger config has no effect on this behavior.
I think we should be able to allow Jenkins to merge a pull request, regardless of the content of the comment.

I should also add that this even prevents the merge if the trigger phrase is in the initial comment when the pull request is created. It only allows a merge if there is a later comment with the trigger phrase.

Definitely a +1 here.
This is causing the auto-merge feature to essentially be useless for our group.

With the latest version it shouldn't matter when you add the trigger comment anymore.

@DavidTanner But is still requires one to auto-merge even if I don't have one set, correct? That is what I'm seeing at least.

+1. Please let's have this. It doesn't make any sense to not allow merging if the jenkins job admin explicitly checked the box that says it should.

@DavidTanner, could you have a look at https://github.com/jenkinsci/ghprb-plugin/pull/381 please?

@dulvac I don't have a good way to test or verify this, but on the surface it looks good.

The PR was merged, Thanks @DavidTanner. You can close the issue.

👍
This works great! Thanks @dulvac and @DavidTanner!


Publishing workflow

Publishing to the VS Code marketplace should be automated with a task. This task should do some bundling to reduce the size and loading time of the extension.

[x] Create azure organization
[x] Create personal access token
[x] Create publisher in VS Code marketplace
[x] Task to publish extension
https://code.visualstudio.com/api/working-with-extensions/publishing-extension
[ ] Proper bundling
https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Fixed


[docs] Sync translations with Crowdin

edits from @oliviertassinari: I'm testing the Crowdin workflow and making a few fixes in anticipation for resuming the effort for going after the Chinese market with hopefully a x2-x3 bigger core team. For now, I'm using this to leave a feedback to the Crowdin's team on what they could improve.

I'm giving it up, it breaks too many things.


this requires 1.20.1

ive been asking around and trying to learn fabric just to get the stepup mod in 1.20 and i was so happy to see you did it already but its saying that i need to have 1.20.1 like many other mods so it seems like an issue in the system but ty sooo much for making this, i cant wait to use it, theres so many mods in the same spot and might die. now im waiting on invintory tabs, mod settings, rpg hud and so many more that might not be ported

Hmm, it wasn't my intention for this to be 1.20.1 only. I'll see if I can get that sorted, thanks


Lighthouse create account for mainnet

The create account should target the mainnet not the pyrmont testnet.

Thanks for this fix!


Interaction with react components

Currently we are switching our old app to one based on React. In a menu we have a react component in which we need to type some letters and the a dropdown opens with some suggestions. After this happens we need to select one of the options that appeared by clicking on it.
When trying to interact with this component we encountered difficulties in typing some characters in the react-select component as well as selecting the options that appeared in the dropdown.
Does anyone have any suggestion on how I can better interact with such components.
Here are some examples of react-select components: https://jedwatson.github.io/react-select/
Thanks in advance.

A little bit hacky but works for us. In Behat Syntax:
`
When I click on the element "#select .Select-arrow-zone"
When I wait for element "#select .Select-menu-outer" to appear
And I click on the element "#select .Select-option[title='L001']"
or if title not filed:
And I click on the element "#select .Select-option:nth-child(2)"

`


DBZ-3605 Add support for several Oracle data types

https://issues.redhat.com/browse/DBZ-3605
Data Types:

[x] XMLTYPE
[x] RAW
[ ] LONG - Not likely supported due to complications with LogMiner.
[ ] LONG RAW - Not likely supported due to the same complications with LogMiner as LONG types.
[x] Documentation
[x] Fix dependencies on XDB and SAX environment variables

So LONG (replaced by CLOB) and LONG RAW (replaced by BLOB) are data types provided by LogMiner in two different ways depending on the data length in those columns.  The use case where this becomes problematic is when these data types are updated with a new value.
If the length of the character data (LONG) or byte data (LONG RAW) is short enough, Oracle inlines the column values in the re-constructed SQL so the SQL statements appear as follows:
UPDATE table SET long_col = 'the long text' WHERE long_col = 'the old long text value';
UPDATE table SET long_raw_col = HEXTORAW('new hex value') WHERE long_raw_col = HEXTORAW('old hex value');

This works well, but unfortunately, once the character or binary data length reaches a specific threshold, Oracle will re-construct the SQL differently, using what is called LONG DATA operations (or opcode 24) event types.  The event stream becomes the following:
UPDATE table set long_col = 'LONG DATA' WHERE long_col = 'LONG DATA';
[a series of LONG DATA events]

or
UPDATE table set long_raw_col = 'LONG DATA' WHERE long_raw_col = 'LONG DATA';
[a series of LONG DATA events]

These LONG DATA operation events are a continuous stream of character or binary data representing both the old and new values.  For LONG RAW, we can only determine the breakpoint between the old/new values because the stream is the concatenation of HEXTORAW('...')HEXTORAW('...') where the former function call is old, and the latter is new; however when working with LONG data types, this distinction doesn't exist.
The only reason that RAW works is that it is explicitly restricted to a maximum length of 2000, which allows Oracle to inline the value, and therefore its always directly available in the re-constructed SQL without any secondary event types that require merge semantics.
We can safely support LONG and LONG RAW via Xstream because GoldenGate can differentiate the break point in the LONG DATA redo entries, but unfortunately LogMiner does not.  This means that the OpenLogReplicator implementation should be more than capable of doing precisely what GoldenGate does for Xstream, so if we wanted to pursue this support, it would be non-LogMiner only for these two.

@roldanbob could you take a peak at the recent commit for the documentation changes, and suggest or add whatever changes are needed for the product side around the new XDB library dependency?

@Naros Applied, thanks!

@roldanbob I'll follow-up the documentation changes in a follow PR later this week.


Installation Error : invalid user: ‘www-data’

Hi,
i got an error when i run : sudo dpkg -i libapache2-mod-auth-openidc_1.8.2-1ubuntu1.trusty.1_amd64.deb
i got this error :
(Reading database ... 83645 files and directories currently installed.)
Preparing to unpack libapache2-mod-auth-openidc_1.8.2-1ubuntu1.trusty.1_amd64.deb ...
Unpacking libapache2-mod-auth-openidc (1.8.2-1ubuntu1~trusty+1) over (1.8.2-1ubuntu1~trusty+1) ...
Setting up libapache2-mod-auth-openidc (1.8.2-1ubuntu1~trusty+1) ...
chown: invalid user: ‘www-data’
dpkg: error processing package libapache2-mod-auth-openidc (--install):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
libapache2-mod-auth-openidc
How i can install the package with a different user ?
Thank you

Are you on a non-standard Trusty environment? If so, you can execute the postinstall commands manually:
    chown -R <user> /var/cache/apache2/mod_auth_openidc
    chmod -R go= /var/cache/apache2/mod_auth_openidc

Thank you, yes i have a non-standard Trusty

you're on your own then; you can either apply the commands manually and/or don't install it as a package but as a .so only (either by building yourself or by extracting it from the .deb)


hg_proc size pass

Was thinking about the proc issues talked about in #79 and had the following idea:

have a new type of proc operation - HG_GET_SIZE, which increments two (new) size values in the proc data structure - the type's size and, if applicable, the variable-length size of any (containing) bulk handles. The var-length is expected to be attached to a bulk handle
repurpose the proc workflow to:

call proc on the input type(s) with HG_GET_SIZE
determine whether to use eager mode or not (the size counters provide the necessary info)
allocate needed data
call proc again with HG_ENCODE

(the decode path would just need to track whether eager mode was used and otherwise be unchanged I think...)
There's a few benefits to this:

no need to repeatedly check buffer sizes and do reallocation and such. You have exactly one alloc
the HG_GET_SIZE implementation for most types we're interested in (C structs with some light variable-length data) is trivial.
eager mode issues are resolved for arbitrary types

Is this a reasonable approach?

Sorry for not responding earlier, that's interesting I like the idea. Although that's still 2 passes :)
Yes the proc component needs to be improved to get rid of the if size etc as much as we can I think.


Call rebalance API once all pods are updated

Timid attempt to fix #615
It works on my machine, it seems to fix the problem, but:

I have no tests. Yet. I have a feeling this is the hard part 🙂
I guess I'll need to update managed-updates.md a bit as well.
There are a couple of TODOes in my patch where I'm not sure if things are right - any feedback there would be great!
Last but not least, with or without my patch, I always got a DOWN shard at the end of my rolling update. That's a separate issue, right? Still, it's always reproducible in my environment, maybe due to the fact that I'm testing with some docs in my collection and I'm having my IDE (with Solr Operator) talk to Kubernetes via a port forward to the "common" service, which sometimes fails because the underlying pod gets restarted, so I get a few "connection refused" errors until I put it back. Still, it should be something that the Operator handles gracefully, IMO.

Any feedback is welcome, I'd be glad to push this forward!

Looks good to me, too, thanks a lot @HoustonPutman!
I already had a look yesterday, too, and noticed you couldn't help yourself and fixed your 2) above 🙂

I already had a look yesterday, too, and noticed you couldn't help yourself and fixed your 2) above 🙂

Haha I remembered that we had the lovely readinessConditions that told us if the cloud was ephemeral, so it was very easy to do it!


Do the beacon base datapacks require Fabric?

I'm not clear on the beacon base descriptions on Modrinth.  I have a Fabric server, and would like to add the beacon base datapacks to it, so I should be OK, but I'd like to document the requirements properly.  Installing as a datapack means you don't need a modloader, so are there other prerequisites with the datapack like Fabric, or does it work with vanilla?

Oh, you have a header and the modloader is under a "when using as a mod".... der....


Full Date please!

I have entered several Items together with their Expiration-Dates.
The List unfortunately does not show the Year!
Please show  the full Date – preferably in standardized ISO-Date-Format: 2025-12-17

Hi,
Thank you for opening this issue. I have been thinking about what date format would be best for this project and thought that since most food expiration dates are weeks or months from the time of product purchase, there was no need to specify the year.
I realize, however, that this applies to products to be stored in the fridge, but so many other products that can be stored outside the fridge have expiration dates even longer than a year.
I will add the possibility to select a custom date format in the app settings.

Hi @cocker-cc, I finished the implementation of the functionality you've requested.
It will be available in the next release.

Thanks for this Improvement.
(I only now pulled the Foss-Version from IzzyOnDroid)


Adding Entities recognition using haptik (preprocess suggestion)

Hello, Im amazed at this implementation of GPT-3.
I would love to add an extra later to theprompt by preprocessing the text and adding entities with metalabel while passing prompt to GPT-3
An example would be:
Buy [Brand] Adidas shoes from Amazon [company] India [location] under $200 [numeric]
We could achieve this using the hello haptik repository (link: https://github.com/hellohaptik/chatbot_ner)
Im not completely sure if this will help the output. What do you think?
Kudos!

i'm just guessing but i personally dont think annotating using entity types would help in terms of gpt-3 understanding, because it wasn't trained on this NER style, unless you do specific things with the detected entities unrelated to gpt-3 e.g. handle the location in a specific way via google map search and pull out the location for it etc.

Yeah I wouldn't expect this to help either. The NER model will almost certainly be worse at understanding the words than GPT-3, so it would only add some noise and extra tokens.


Lightline will not load

I am running into what is most likely a configuration problem.
I am using "set statusline=2"
The problem I am running into is that Lightline will not be open on the file I edit until I re-edit it. Specifically I do this by
":e" on the current vim file.
Note: I am using gruvbox as my general colorscheme and I have noticed this particular issue not being directly tied to this.
My vimrc is a little messy as I am still pretty new to vim and plugins, but here is what it is as follows:
set statusline=2
set nocompatible              " be iMproved, required
filetype off                  " required

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
" " alternatively, pass a path where Vundle should install plugins
" "call vundle#begin('~/some/path/here')
"
" " let Vundle manage Vundle, required
Plugin 'VundleVim/Vundle.vim'
Plugin 'Valloric/YouCompleteMe'
Plugin 'scrooloose/nerdtree'
Plugin 'morhetz/gruvbox'
Plugin 'itchyny/lightline.vim'

"" All of your Plugins must be added before the following line
call vundle#end()            " required
filetype plugin indent on    " required

:command RunPy !/mnt/c/Python3.7/python.exe '%:p'

" Open nerdtree on vim startup
autocmd vimenter * NERDTree
" Set to right side position
let g:NERDTreeWinPos = "right"
" Unfocus nerdtree
autocmd vimenter * wincmd p
set mouse=a
set number
set relativenumber
set background=dark
" Makes movement between splits easier
map <C-j> <C-W>j
map <C-k> <C-W>k
map <C-h> <C-W>h
map <C-l> <C-W>l
" Makes nice closing braces
inoremap " ""<left>
inoremap ' ''<left>
inoremap ( ()<left>
inoremap [ []<left>
inoremap { {}<left>
inoremap {<CR> {<CR>}<ESC>O
inoremap {;<CR> {<CR>};<ESC>O
" Set tab size
:set tabstop=4
:set shiftwidth=4
:set expandtab
highlight ColorColumn ctermbg=DarkGray guibg=lightgray
set colorcolumn=80
syntax on
" Start Lightline status bar
let g:lightline = {}
let g:lightline.colorscheme='powerline'
"gruvbox color scheme config
let g:gruvbox_contrast_dark = 'hard'
:colorscheme gruvbox

set laststatus=2 is correct instead of set statusline=2.

set laststatus=2 is correct instead of set statusline=2.

Upon fixing that mistake I still am running into the same issue -- here is some visuals to help out
Before using ":e"

After using ":e"

I tried to bodge it together in a way earlier by having vim run  the command ":e" after any time I open a file but was unsuccessful at this.

Could you remove the line "autocmd vimenter * NERDTree" and see if it'll fix the issue?

AH -- I see -- this was something I thought might be the case. It appears to me that upon "autocmd vimenter * NERDTree" it loads the lightline information on the NERDTree split*(I think its technically a split) before the current file split.
Is there anything you would suggest doing to allow for me to continue haveing "autocmd vimenter * NERDTree" while having lightline be based on the current file that I am editing?

Try autocmd VimEnter * ++nested NERDTree .

Could you try with:
augroup NERD
     au!
     autocmd VimEnter * NERDTree
     autocmd VimEnter * wincmd p
     autocmd VimEnter * call lightline#update()
augroup END

yhu266's response worked for me whereas itchyny's response did not for those who might be in a similar situation as I am. Make sure to recall his statement of potential performance issue.

Try autocmd VimEnter * ++nested NERDTree .

It really worked for me . For those who want the cursor in the other window rather than on the nerdtree try this
autocmd VimEnter * ++nested NERDTree | wincmd p
I think this command will not affect performace rather than the other command suggested by yhu266


Typings install fails.

The npm typings script has a typo.
Currently, it read typings install --ambiant
It should read typings install --ambient

This will also need to be pushed to NPM after it's fixed.

I take it back. It's a deeper issue. The typo is still a valid fix, but the issue actually revolves around configstore trying to access ~/.config/configstore/typings.json and there being an innate permissions issue there, even installing with sudo.

The error itself:
><EMAIL_ADDRESS>typings /usr/local/lib/node_modules/angular2-dependencies-graph
> typings install --ambient

/usr/local/lib/node_modules/angular2-dependencies-graph/node_modules/configstore/index.js:54
				throw err;
				^

Error: EACCES: permission denied, open '/Users/mko/.config/configstore/typings.json'
You don't have access to this file.

    at Error (native)
    at Object.fs.openSync (fs.js:634:18)
    at Object.fs.readFileSync (fs.js:502:33)
    at Object.create.all.get (/usr/local/lib/node_modules/angular2-dependencies-graph/node_modules/configstore/index.js:35:26)
    at Object.Configstore (/usr/local/lib/node_modules/angular2-dependencies-graph/node_modules/configstore/index.js:28:44)
    at Object.<anonymous> (/usr/local/lib/node_modules/angular2-dependencies-graph/node_modules/typings-core/dist/utils/store.js:5:19)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)

It should be noted that simply changing the typings.json file in ~/.config/configstore/ to read/writable doesn't fix the issue.

It looks like you have to set the entire .config directory to read/writable. Might be worth looking for an alternative to configstore.

This creating trouble suddenly after upgrading it to typings version

this issue seems to be related to typings. See related issue https://github.com/typings/typings/issues/269


tensorboard question

Hello,I want to use tensorboard to show the image of weight of that layer,but I found there is only graphy and loss in the tensorboard .
What is wrong ,and how can I visualize my weight

Does somebody know how to display not just the loss but also the accuracy in Tensorboard?
Thanks in advance :)

Does somebody know how to display not just the loss but also the accuracy in Tensorboard?
Thanks in advance :)

Have you figured it out? I'd be interested too.


Text Overlapping On Map Page

It appears that there is some overlapping of the module/section names over the estimated completion time. This does not happen on Chome when I tested it, only on Firefox Dev Edition and regular Firefox.
Common issue? Or my own browsers?
My dimensions are:
Browser window width:	1920
Browser window height:	905
Screen width:	1920
Screen height:	1080

@hallaathrad Can you please take a look at this one?

The issue is that Lato is not being loaded... like on many other issues I've seen before, this is a common issue (for this and other fonts) while using some linux distros

@hallaathrad
Could we have a "safer" fallback font?

This is worth some testing. The site is serving it's own ttf files.
Please see #6679 serving woff2 files directly from google's font cdn and I'd have @OriBon test it, if he'd be so kind.

@hallaathrad To test it do I just check beta? If so, it looks better on there.

Not quite, my friend. Beta is not showing the changes. Let me see if I can figure out a way for you to try it there.
I'll edit this comment on my progress.

Seems this issue is fixed. @OriBon thanks for posting.


About ‘Audience Retention curve’ also named ‘高能进度条’

To be more github style，please allow me to use English。
I am very interesting in how bilibili implement “高能进度条”，Youtube and a indescribable site P have the same curve,which was named Audience Retention curve，but none of them release the detail about how they achieve this function.
so I wondering will you lovely guys release some detail info on this function?like how to collect data,where does it store,and data structure you guys use. etc.
I am pretty sure you guys will earn a lot reputation by doing so on github or anywhere else.

Hello, I am the creator of "高能进度条".It is also called
PBP(Progress Bar Plus) in our development procedure.
It's based on 3 elements:

User's seekend behavior.
Barrage density.
Spetial barrage works like "前方高能", "空降成功", etc.
PBP aims to improve user experience.


Remove deleted theme

https://github.com/kongdivin/hugo-theme-okayish-blog no longer exists.
It's causing the update-themes action to fail.

@bep Thanks for merging. Could you please kick off a manual run of update-themes to catch up with the past few days' changes?

@bep It looks like the build still breaks on github.com/kongdivin/hugo-theme-okayish-blog. Perhaps the cache needs to be rebuilt? I see you made a separate commit for that after removing a theme, but I don't know what you did to rebuild it.


Improve tus error

Previously the error returned from tus by skynet-js was too long and technical.
Now we will return the most salient information.
Before:
Error: tus: unexpected response while creating upload, originated from request (method: POST, url: https://siasky.xyz/skynet/tus, response code: 413, response text: upload exceeds maximum size:<PHONE_NUMBER> ><PHONE_NUMBER>
, request id: n/a)

After:
Error: upload exceeds maximum size:<PHONE_NUMBER>0 ><PHONE_NUMBER>

SWEET <3


Upgrade to rust beta

Upgrade rust to 1.0.0-beta, and update cargo so that it will build with the -beta compiler.
Add snapshots to SRC_URI to avoid network traffic during do_compile
Break rust-cross' dependency on rust-native.  This reduces by half the amount of time needed to build the cross compiler.

I'm not sure I understand why the patches for libdir & bindir support aren't used any more.
I was fairly certain bitbake puts -cross packages in the same prefix as native ones but with different bindir's and libdirs, which means rust-native package will conflict with rust-cross.
I suppose it's possible you didn't run into this due to using snapshots for everything.

The patches I removed were for some combination of not applying, being unnecessary, and being actively harmful.  I think you'd agree that it's ideal to patch rust as minimally as possible for ease of maintenance.  The bindir patch in particlar was somewhat invasive, just due to having to plumb that value all through the build system.
I did test building rust-native and rust-cross in the same workspace.  Both worked, and I got no errors.  I would have expected bitbake to warn/error out if both recipes tried to install the same file to the sysroot.  In general that is bitbake's behavior.
Note that I actually maintained the same installed behavior of putting rust-cross in ${bindir}/${TARGET_SYS}, see the lines I added to do_install.  It's simply much less invasive to let rust install however it wants, then move the files around to our desired layout.

Fixes pushed

I went through this today and cherry-picked a few commits, modified and commited a few, and dropped a couple.
Notably, I've stuck with my changes to teach rustc about libdirs and bindirs rather than using RUST_SYSROOT. While I do think it would be a good idea to keep the patches as simple as possible, I was running into problems with the sysroot related changes where rust would link itself agaist the system rustlib instead of the local one being built, leading to unexpected failures. Additionally, while the changes to support bindir and libdir properly are more invasive, I'm more comfortable dealing with them at this point and fairly confident they correctly handling things.
Thanks for this PR, please take a look at the latest master and see if it functions as expected for you, and let me know if I've inadvertantly not pulled something in that I should have.


Is there Bitcoin transaction building functionality planned?

Check out https://github.com/cmdruid/tapscript


Fix links

Solves the following:
https://trello.com/c/tcZApdnW/111-dougs-github-link-goes-to-cr-github
https://trello.com/c/QzVeC1xX/107-mateo-barazzas-github-also-goes-to-cr-github
Big fix here: If we don't have a twitter/github of a person, it doesn't render the icon anymore.

Sorry, I need the updated json file for my next PR

PS: ^ that guy is dead inside


chore(github-actions): remove lighthouse from auto-updates

I also changed the time this task starts to separate updating packages and inputs in time.
Close #218

@aldoborrero nix-update can't update vscode-plugin-ackee-blockchain-solidity-tools and vscode-plugin-consensys-vscode-solidity-visual-editor, so I disabled them too


Prepare regions for CN

Description
Changes proposed in this pull request:

branch for China

Related issue(s)

/hold


Pass SQLCMD variable with dotnet publish

I believe it’s possible to pass the value of a SQLCMD variable with dotnet publish. What’s the syntax?

@brettrowberry I guess it depends on how you've setup your SQLCMD variables in your project file. For example, let's consider the following example:
    <SqlCmdVariable Include="TasksDb">
      <DefaultValue>Tasks</DefaultValue>
      <Value>$(SqlCmdVar__1)</Value>
    </SqlCmdVariable>

In this scenario you should be able to set SqlCmdVar__1 from the command line using dotnet publish /p:SqlCmdVar__1=SomeValue. This should set the TaskDb SQLCMD variable to the value SomeValue at deployment time.
Please note that currently we don't use the DefaultValue. So in this scenario, if you do not specify SqlCmdVar__1 on the command line it will have no value (unless it is specified in the project file somewhere). If this is something you need I suggest opening a separate issue for that.
@ErikEJ @jeffrosenberg Perhaps we should add this to the docs?

In this scenario you should be able to set SqlCmdVar__1 from the command line using dotnet publish /p:SqlCmdVar__1=SomeValue.

This exactly solved my issue! I definitely think this should be added to the docs. I can put together a PR if you like.

Please note that currently we don't use the DefaultValue. So in this scenario, if you do not specify SqlCmdVar__1 on the command line it will have no value (unless it is specified in the project file somewhere).

That's what I was seeing. That's something I didn't notice in the docs (it might have been there, bit I missed it anyway). I think the <DefaultValue>SomeValue</DefaultValue> should be omitted from docs/samples if it isn't supported.

If this is something you need I suggest opening a separate issue for that.

I'm not sure if I need DefaultValue. It was being ignored and I couldn't figure out how to pass it in - but now I know how to pass it in. Then, looking though some of the scripts in my project, it turns out that I didn't need the variable at all and just hardcoded the value (doesn't need to be configurable).
Before I open an issue, is there a reason you decided not to support DefaultValue (maybe to encourage people not to put secrets into source code?). I don't have strong opinions on this and it only came up because some legacy project I was converting used SqlCmdVar (and now it doesn't). Part of the value of this project is the good opinions you bring to it - which things to include and leave out. You are wise to avoid feature parity with the old .sqlproj files.
@ErikEJ @jeffrosenberg Perhaps we should add this to the docs?

@brettrowberry I don't think there's a particular reason not to support the DefaultValue option other than not having the time to actually implement it. That being said I feel that you still set a default value in the project file if you want using something like this:
<PropertyGroup>
  <MySqlCMDVariable Condition="$(MySQLCmdVariable)==''">SomeValue</MySqlCMDVariable>
</PropertyGroup>

<ItemGroup>
  <SqlCmdVariable Include="MySqlCMDVariable" Value="$(MySQLCMDVariable)">
</ItemGroup>

Note I haven't actually tried this, but I'm fairly confident that it will work.

Using this, you can still set an alternate value for that variable if you want by passing it on the command line. We wouldn't have to add support for the DefaultValue item metadata this way I think.

I tried this out quickly and it worked. I'd like to play with it a little longer and make a PR to add to the README.

@brettrowberry As of version 1.11.0 we now support the DefaultValue element (or attribute) as a fallback value and it is also explained in the README. Closing this as I don't think there's much more here that we can do.

@brettrowberry As of version 1.11.0 we now support the DefaultValue element (or attribute) as a fallback value and it is also explained in the README. Closing this as I don't think there's much more here that we can do.


Web hook adjustments

Some adjustments in the web hooks in this PR

Implemented missing events member_added and member_removed #66
Set content type of requests to JSON
Invert order of gproc.goodbye and disconnection notification.

I also tested the whole web hook support with the Pusher ruby gem as you suggested and everything is working fine now :dancer:

That's fantastic! It closes https://github.com/edgurgel/poxa/issues/66


Feature/dev harrel impl

Labels
Mark your PRs with the following labels, as appropriate:

breaking-change: if the PR includes a breaking change
enhancement: if the PR enables / completes a new feature
bug: if the PR fixes a bug.
dependencies: if the PR updates dependencies
documentation **: If the PR doc-only changes
subtask **: If the PR is only part of a new feature. Ensure final PR is marked with enhancement.
chore **: a maintenance / non-feature released task of no interest to users.

Labels marked with ** are excluded from release notes
Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Hi, let me know if there is something missing. I have no suggestion though: could you somehow separate spec compliance to required & optional? Because now it feels a little bit unfair as I have the highest score for required and the lowest score for overall. I just don't support format assertions (yet?) which is most of the optional tests are checking.
Also I think the serde tests might be a bit unfair? E.g. "Medeia" doesn't support newest drafts so it is run with draft7 and it cannot really be compared to implementations which are run with draft2020-12. Probably this also should be grouped by specs?

And just out of curiosity: how long does it take you to run all benchmarks? :P It looks like it might take a whole night or so

Thanks @harrel56, I'll take a look at this.

could you somehow separate spec compliance to required & optional?

Results are split between required and optional. Though currently the graph is not.
The table summarising the functional results breaks them down into pass/fail counts on optional and rrequired features.
The over all score treats blends both required and optional, with required test cases making up 75% of the score.
It would be possible to add a graph comparing only required functional coverage. Feel free to raise an issue, and ideally work on it.

Also I think the serde tests might be a bit unfair? E.g. "Medeia" doesn't support newest drafts so it is run with draft7 and it cannot really be compared to implementations which are run with draft2020-12.

Yes, I'm aware of this.
I'm currently working on making the charts and tables of results be driven from the latest test runs, so that results update as new versions of validator libraries come out.  As part of this work, I have a todo to call out which draft version the serde benchmark is using, what this means, and to potentially break it down by spec.
Time is always a limiting factor though ;)

When the benchmarks and graphs are going to be automatically generated I'll be happy to help out with splitting this graph - I just don't wanna do it manually. Gonna report this as a separate issue then

Sorry - forgot I moved those files!

First off, a big apology for committing a refactor while you were in the middle of your work. My bad. I'm just trying to finish off a few things to make results more data driven.

Yeah, that really wasn't a problem so no worries :)
I think I addressed all your comments - let me know if there's anything left

Ok, completed another iteration - it's getting a little messy, hopefully didn't omit anything

Performance results are up: https://github.com/json-schema-org/website/pull/225


adding updateSize function

What
a new function to update the size of the canvas
Why
There is an open issue at Viewers https://github.com/OHIF/Viewers/issues/550 which says that Viewport is resizing incorrectly when the sidebars are changed. It appears to be resizing in CSS but not calling a redraw of the rendering on the Canvas. Note how the actual cell aspect ratios are being changed. This is not what should be happening.

Why the setTimeout? Seems like we should just call map.updateSize() directly and if the developer using the library wants to put it inside a timeout async they can do that.

After changing the consumer of updateSize, there is no need to use setTimeout anymore.

LGTM - @swederik any other issues or is this ready to merge?

Yep it's fine for me unless @hackermd has an issue with it.


State test is broken, and this PR does not fix it

Description
The Oops people are making up test just to highlight some minor issues in soca. This PR ignore the new test. The issue will be investigated next week (from the time you are reading that PR/issue description).
Issue(s) NOT addressed
Does not close #449

The Oops people are making up test just to highlight some minor issues in soca

Errors in soca? nope, fake news

@travissluka: a github bot that would automatically merge issue "revert commit" PRs in oops/other repo!


Adding most of scipy.linalg.special_matrices.

This adds 17 out of 20 of the functions in scipy.linalg.special_matrices. The only missing ones are currently implemented in scipy with scipy.special.comb which is currently not implemented in cupy (and would also run into integer overflow issues on the GPU quickly as well). Additionally, the tri function actually just calls the already efficiently implemented cupy.tri function.
Will be adding tests shortly, however, what is the earliest still-supported scipy version? These functions were added later:

0.8.0 - circulant, hadamard, leslie, companion
0.10.0 - hilbert
0.14.0 - dft
1.3.0 - fiedler, fiedler_companion
1.5.0 - convolution_matrix

Looking through the tests, the requirement "scipy>=" is used at earliest with 0.19.0 so I added testing rules for only the final 3 special matrix functions.

I don't see a specific SciPy version listed as supported in the docs, but I think scipy 0.18 is the oldest version tested on CI:
https://github.com/chainer/chainer-test/blob/master/run_multi_test.py#L22

Could you split the PR for each function?
Regarding SciPy version support, we discussed and planning to only support 1.3+. (#3631)

@kmaehashi I can split it up a bit, but some of them are related to each other so I would probably still keep them together (like tri/tril/triuandtoeplitz/circulant/hankel`). However, currently the tests are currently a bit intertwined.
How should I proceed? Do I make 15 different branches and submit 15 PRs right now for all of them, or do I do it one PR at a time and can reuse the same branch? Will the merging handle it just fine if they are done as 15 separate branches? It seems like it will think they should all be the "first" function in the file.

Could you update docs/source/reference/linalg.rst?

Using a custom an ElementwiseKernel for hadamard has great results (old is the version with a loop and new is the ElementwiseKernel version):

n
scipy (µs)
old (µs)
new (µs)

256
151
306
12.9

512
517
339
15.6

1024
3600
391
25.5

2048
24600
521
65.4

4096
120 ms
994
224

8192
513 ms
2880
861

16384
2.08 s
10.4 ms
3.4 ms

The cupy function is now faster than scipy for all values of n except 1 (but previously it was only faster n>=512).

@coderforlife Could you fix for Travis failure?

Fixed documentation issues.

Jenkins, test this please.

Jenkins CI test (for commit 86073d3ec7a34c6de10a729db9565c72ab396c95, target branch master) succeeded!

LGTM.


derive(GraphQLView) should generate entries starting with _

We do this systematically for the code written by hand but the trick was apparently not picked in the generated code:
https://github.com/linera-io/linera-protocol/blob/main/linera-execution/src/graphql.rs#L36

It has been resolved.


Exchange Online doesn't support shared inboxes in the service

It should be called out that Power BI Service only supports Exchange Online if the connection is to a user's individual account, not shared inboxes. We've had multiple teams in our company run into this limitation and be frustrated as it is not documented anywhere.

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

ID: 3c34c249-033f-4156-0abc-8d16cbe355a0
Version Independent ID: 20dc29c2-9cb7-2322-e80b-3f801bc34cfe
Content: Power BI data sources - Power BI
Content Source: powerbi-docs/power-bi-data-sources.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @kfollis
Microsoft Alias: kfollis

Thanks for your comment, @klinejordan - we’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Hi @klinejordan ,
Thank you for your suggestion.  We've made the update and set the article to republish.
All the best,
The DOCS team


generic thermostat current_temperature is null after hass restart

Home Assistant release with the issue:

0.101.0
Last working Home Assistant release (if known):
Never.
Configured for the first time on 0.100.2 and it was not working on that level either.
Operating environment (Hass.io/Docker/Windows/etc.):

Raspberry pi 4 running a Raspbian
Home Assistant is running within Docker: homeassistant/raspberrypi4-homeassistant
$ uname -a
Linux raspberrypi 4.19.75-v7l+ #1270 SMP Tue Sep 24 18:51:41 BST 2019 armv7l GNU/Linux

Integration:

https://www.home-assistant.io/integrations/generic_thermostat/
Description of problem:
I have a problem that after the Home Assistant is restarted (from the GUI) the generic thermostat does not show any current temperature, while this time the target temperature sensor already has a value. On the GUI "States" page I see that the current_temperature attribute has null as value.
After a while (assume that on the next target sensor update) the current_temperature is updated and the value is taken from the target sensor and shown correctly in the generic thermostat as well.
Target sensor is an Aqara temperature sensor (WSDCGQ11LM) connecting through a Conbee II USB stick + deCONZ.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
climate:
  - platform: generic_thermostat
    name: Nappali termosztát
    heater: light.light_7
    target_sensor: sensor.temperature_2
    min_temp: 15
    max_temp: 27
    ac_mode: false
    target_temp: 22.5
    min_cycle_duration:
      minutes: 15
    initial_hvac_mode: "heat"

Traceback (if applicable):
No related traceback is seen.
Additional information:

I am not so good in python and I don't know how to correct it, but I assume that this line could be the root cause in climate.py:
"""Initialize the thermostat."""
[...]
self._cur_temp = None

The issue is still outstanding on 0.105.1.


missing latex logic dictionary definitions

If I try to parse the latex string x \lor x
The compute engine fails to parse the string with the following error:
["Sequence","x",["Error",["ErrorCode","'unexpected-command'","'\\lor'"],["Latex","'\\lor'"]],"x"]

It seems like the DEFINITIONS_LOGIC dictionary is missing logic operators like (OR, NOT, AND, IMPLIES, EQUIVALENT).

This has now been fixed.


EyeTV 4 AppleScript errors

The EyeTV script no longer works with EyeTV 4. It seems this version of EyeTV has broken AppleScript support. I've logged an issue with Geniatech support.

EyeTV 4.0.0 (8524) seems to have fixed the issue.  Running on macOS Big Sur 11.2.2.


Various docs fixes: Copy (from|to), configuration, and psql

Current coverage is 80.97% (diff: 100%)

Merging #4193 into master will decrease coverage by 0.01%

@@             master      #4193   diff @@
==========================================
  Files          1299       1299
  Lines         44289      44289
  Methods           0          0
  Messages          0          0
  Branches       7056       7056
==========================================
- Hits          35870      35863     -7
+ Misses         5777       5775     -2
- Partials       2642       2651     +9

Powered by Codecov. Last update ec9a0d9...9b7c219


fixed #4 logf0rmse missing sr decleration

I have addressed the issue #4. Also I have added a test code for logf0rmse.
Please check the content

Thanks a lot! LGTM.


docs: changelog update for 1.16.0

Codecov Report
Base: 38.96% // Head: 38.96% // No change to project coverage :thumbsup:

Coverage data is based on head (790366a) compared to base (a391708).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #784   +/-   ##
=======================================
  Coverage   38.96%   38.96%
=======================================
  Files          88       88
  Lines       10127    10127
=======================================
  Hits         3946     3946
  Misses       5794     5794
  Partials      387      387

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.